
From nobody Wed Feb  1 03:24:16 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47C63129D1A; Wed,  1 Feb 2017 03:24:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.198
X-Spam-Level: 
X-Spam-Status: No, score=-5.198 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_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=yaCyDrRN; dkim=pass (1024-bit key) header.d=elandsys.com header.b=lMIftqIZ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRGAqOQuIMYj; Wed,  1 Feb 2017 03:24:10 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 44372129D18; Wed,  1 Feb 2017 03:24:10 -0800 (PST)
Received: from sm-THINK.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v11BO8be005615 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 03:24:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1485948249; x=1486034649; bh=6Vr7EG28xO2tdmcAeFwjiy3dxtJ/asFjGFkfesVRBOE=; h=Date:To:From:Subject:Cc; b=yaCyDrRN6qPUR8CRVVAaPUmiPMQ9S4KYzC55QOnxO8nuTUrMTeEkiYL/JtcaNCk3X ifecnaJ0UbAyvtydy99oZtrdZMLrrLTMNpAFkfvv9DJxFJXxVBnnEXvKHTGHHe6gQ1 AtIS9rT4zNoFuUZOjlxDl/9f5J9I557ECsyvVEpA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1485948249; x=1486034649; i=@elandsys.com; bh=6Vr7EG28xO2tdmcAeFwjiy3dxtJ/asFjGFkfesVRBOE=; h=Date:To:From:Subject:Cc; b=lMIftqIZbxCSGeUa7k6UJ+rG+LGZC9+A/amrNdaq4T+O85QTnh6wMc9MTomByVVBL mRoS43WEujqTB4FXSzbUX36JqI/P68vpu36PT/ssFHZZs7VURzsggpkTw9WGmtrT2E DgIHdnwIpDmOU8BL41vobd3pcshdccOF6ubo5R0w=
Message-Id: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Feb 2017 03:22:45 -0800
To: iaoc@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Barriers to entry
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G8EzHz6xFv2plBc3jO2EuSbWuys>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 11:24:11 -0000

Hello,

There is a blog article at 
https://www.ietf.org/blog/2017/01/barriers-to-entry/ about "barriers 
to entry".  Dave Burstein [1] suggested that the IETF considers 
refunding the IETF attendance fee for an attendee who is blocked from 
attending the next IETF meeting due to the barriers to entry.

Does the IAOC agree to refunding the attendance fee for such cases?

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg100934.html 


From nobody Wed Feb  1 03:57:42 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451A4129D1D; Wed,  1 Feb 2017 03:57:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UK6PCpZfSmFr; Wed,  1 Feb 2017 03:57:39 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 B275B129400; Wed,  1 Feb 2017 03:57:38 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id r141so35062765wmg.1; Wed, 01 Feb 2017 03:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=UeP0CmDUme0Q2JTUHkLbr4SpuM59uWwvMcU0LhwDT2s=; b=j21kZeLKD3D58Zj7WXAc31HS6bH7upmnKvX93FDaRUNdeQRE/7oznXBKy+foHfAVbR UEa3DzhFKoFCGLT1nuEK7RI/JPYjxSt1lWp6+CoGrFYe9VoWMmSSCh78t/uy5odxJqqV v9JZ+/mRHLY8Frz3s1+ggazEf7eqjIusN54hBYfkqtSwzRlDlka14cz/kHpQutmzAoB1 enB/G1cUEgtE1W6I3j6PKB+gaTTeoRcI+cGErnvjb5EkjHO0IWgUhdjnTYjBcK3Oq+MR Kv8FYV9whVthwfiW6OhP3TkfOLIFrD4c6OhjofRfcAdlfSr784QxLv8ubMCe86OCMEKD H3gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=UeP0CmDUme0Q2JTUHkLbr4SpuM59uWwvMcU0LhwDT2s=; b=AjCbEHpaSrk7d/CKt3m3JCPGPI4DpWVde8WGjD7TyetyS28AKDesMxkgZu4lWURu4y NPrvVPml2Izm0qW+d51kWu29IGPbT/ysf40ZLSt3OJFeZN1n7QAdMvO+uyrYeeyPuaQQ hj3VsbOMHRENt7K/6rdfNzzT1fzWravxyMovk06kZuBXA8t08tuisKNAKCYFeqvmO1xa 07YAM9aWW58BZvfh/Jz3673mKVtkaJhuOIC0c7DhCbuNehAbwFvvwagjh50qAEexBDyk Abg060IXb7x5UtxYCQcx4eGRLizmSqGjVTWdtYoaSGVJ+NHpgww6usu+9jYUv/o/kZJV xzTw==
X-Gm-Message-State: AIkVDXIIjkry9PH+vqGCXQGTv4D6zqvyATG44gOqL+9JV/A1eDUGw9pQ31/KtKixofOdDg==
X-Received: by 10.28.51.205 with SMTP id z196mr21842038wmz.22.1485950257115; Wed, 01 Feb 2017 03:57:37 -0800 (PST)
Received: from [172.24.250.167] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id s17sm33694481wrc.6.2017.02.01.03.57.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 01 Feb 2017 03:57:36 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <34E7C9A1-83EF-480A-ACC1-B84D2D97D373@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_E559A281-F30E-4E2C-80E0-F5F12255F8BB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Barriers to entry
Date: Wed, 1 Feb 2017 13:57:19 +0200
In-Reply-To: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IUAGdrY_T57JCR8ipuHX9EExHLE>
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 11:57:41 -0000

--Apple-Mail=_E559A281-F30E-4E2C-80E0-F5F12255F8BB
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_38921180-F84D-4BA3-88D0-4D66760A6E34"


--Apple-Mail=_38921180-F84D-4BA3-88D0-4D66760A6E34
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi, SM

I=E2=80=99m not sure if this is even up to the IAOC. However, the =
registration confirmation includes the following:

2. Refunds are subject to a 10% (ten percent) cancellation fee.

3. Cancellations and requests for refunds must be received by 2359 UTC =
Monday, March 20, 2017. Refund requests will not be honored beyond this =
point.

So it appears that refunds are available anyway, and what you are =
requesting is for someone (the IAOC?) to waive the 10% cancellation fee. =
Correct?

Yoav

> On 1 Feb 2017, at 13:22, S Moonesamy <sm+ietf@elandsys.com> wrote:
>=20
> Hello,
>=20
> There is a blog article at =
https://www.ietf.org/blog/2017/01/barriers-to-entry/ about "barriers to =
entry".  Dave Burstein [1] suggested that the IETF considers refunding =
the IETF attendance fee for an attendee who is blocked from attending =
the next IETF meeting due to the barriers to entry.
>=20
> Does the IAOC agree to refunding the attendance fee for such cases?
>=20
> Regards,
> S. Moonesamy
>=20
> 1. https://www.ietf.org/mail-archive/web/ietf/current/msg100934.html


--Apple-Mail=_38921180-F84D-4BA3-88D0-4D66760A6E34
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"">Hi, SM<div class=3D""><br class=3D""></div><div =
class=3D"">I=E2=80=99m not sure if this is even up to the IAOC. However, =
the registration confirmation includes the following:</div><div =
class=3D""><br class=3D""></div><blockquote style=3D"margin: 0 0 0 40px; =
border: none; padding: 0px;" class=3D""><div class=3D""><div =
class=3D""><font face=3D"Menlo" class=3D"">2. Refunds are subject to a =
10% (ten percent) cancellation fee.</font></div></div><div class=3D""><div=
 class=3D""><font face=3D"Menlo" class=3D""><br clear=3D"none" =
class=3D""></font></div></div><div class=3D""><div class=3D""><font =
face=3D"Menlo" class=3D"">3. Cancellations and requests for refunds must =
be received by 2359 UTC Monday, March 20, 2017. Refund requests will not =
be honored beyond this point.</font></div></div></blockquote><div =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">So it =
appears that refunds are available anyway, and what you are requesting =
is for someone (the IAOC?) to waive the 10% cancellation fee. =
Correct?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Yoav</div><div class=3D""><br class=3D""></div><div><blockquote=
 type=3D"cite" class=3D""><div class=3D"">On 1 Feb 2017, at 13:22, S =
Moonesamy &lt;<a href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Hello,<br class=3D""><br class=3D"">There is a blog article =
at <a href=3D"https://www.ietf.org/blog/2017/01/barriers-to-entry/" =
class=3D"">https://www.ietf.org/blog/2017/01/barriers-to-entry/</a> =
about "barriers to entry". &nbsp;Dave Burstein [1] suggested that the =
IETF considers refunding the IETF attendance fee for an attendee who is =
blocked from attending the next IETF meeting due to the barriers to =
entry.<br class=3D""><br class=3D"">Does the IAOC agree to refunding the =
attendance fee for such cases?<br class=3D""><br class=3D"">Regards,<br =
class=3D"">S. Moonesamy<br class=3D""><br class=3D"">1. <a =
href=3D"https://www.ietf.org/mail-archive/web/ietf/current/msg100934.html"=
 =
class=3D"">https://www.ietf.org/mail-archive/web/ietf/current/msg100934.ht=
ml</a> <br class=3D""></div></div></blockquote></div><br =
class=3D""></div></body></html>=

--Apple-Mail=_38921180-F84D-4BA3-88D0-4D66760A6E34--

--Apple-Mail=_E559A281-F30E-4E2C-80E0-F5F12255F8BB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYkc0uAAoJELhJCxUKWMyZqh4H/0CJARPxDN1kfHACYk3PMymK
7kgrA7HnNPXICbgfflycZ7fyJo/WaMlm5lRAQlMI7upZJKsYdb2gw8GFJyBA23Y1
2X7R6iTcROvgCs/X/MEjOGRR56tGbYJ+8hj/SfQNWx5TZd4YIno5PbydCIzZPFJk
6JQliMmYDG3/5PMRC3tCFe6hyAaoEIcAdMoilUy03e46B6iSHEp4lj832a0Mb+3q
wGAMOsCkLRCcpSF3YOsnEeeJhd3g26IDq8WmfYGOAmrhw/rwHzqeWJUuxgKCYJaW
BHhexIeCpRoGo/G+p8JqRzvLfkO+hiIzZ+lk3dc6q4BUUGNZk81mexY4TeeRmp4=
=7Eka
-----END PGP SIGNATURE-----

--Apple-Mail=_E559A281-F30E-4E2C-80E0-F5F12255F8BB--


From nobody Wed Feb  1 04:08:44 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0ADB129D38; Wed,  1 Feb 2017 04:08:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.989
X-Spam-Level: 
X-Spam-Status: No, score=-4.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=eA+V7Usj; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=AtJiUhpF
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U8pZGghsFuyI; Wed,  1 Feb 2017 04:08:38 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D38129D34; Wed,  1 Feb 2017 04:08:38 -0800 (PST)
Received: from sm-THINK.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v11C8WuP027496 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 04:08:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1485950914; x=1486037314; bh=QgkWB/a8qse30cq0oGKF8DFMDGdFcikGdHCfdlq/Qcg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=eA+V7UsjQHZbUVY5r97Lzv4SunGEDRrxf5vr3xKi0NMi746GT3UI/W31hoNp2ca0M jAiJoPD+fMI5MBP5vpl0eyd8K13FAQ5SVWcHLd0K7sPQBRZsVyD0NVrLq1YY4hQJei YUURzXOEzFzHtaO2Fi4GhoHoaXbJHkJdEQTPq2ns=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1485950914; x=1486037314; i=@elandsys.com; bh=QgkWB/a8qse30cq0oGKF8DFMDGdFcikGdHCfdlq/Qcg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AtJiUhpFAuzAUyPNSQU1GYf6hph+ee4Hg1q/NsVm7dSBisLAxNqCXZLw5mmiw+bYX Ywde1/rtHuGxRYpQHeYPL6z0W7LdBO/v+tAj+De2WG5B77SLtLBYb7l9pficPeMfFB siHjsSY3IiOwaw6ZOm/bQEKMEdSBAhVDstXNU0vM=
Message-Id: <6.2.5.6.2.20170201040018.0cd2a668@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Feb 2017 04:08:09 -0800
To: Yoav Nir <ynir.ietf@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Barriers to entry
In-Reply-To: <34E7C9A1-83EF-480A-ACC1-B84D2D97D373@gmail.com>
References: <6.2.5.6.2.20170201031607.0c259c28@elandnews.com> <34E7C9A1-83EF-480A-ACC1-B84D2D97D373@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P_BCV95tLximMfHWJgj4E_fCsas>
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 12:08:40 -0000

Hi Yoav,
At 03:57 AM 2/1/2017, Yoav Nir wrote:
>I'm not sure if this is even up to the IAOC. However, the 
>registration confirmation includes the following:
>
>2. Refunds are subject to a 10% (ten percent) cancellation fee.
>
>3. Cancellations and requests for refunds must be received by 2359 
>UTC Monday, March 20, 2017. Refund requests will not be honored 
>beyond this point.
>
>
>So it appears that refunds are available anyway, and what you are 
>requesting is for someone (the IAOC?) to waive the 10% cancellation 
>fee. Correct?

Thanks for catching my mistake.  Decisions about meetings were 
generally left to the IAOC.

I am suggesting that the IAOC waive the cancellation fee.

Regards,
S. Moonesamy 


From nobody Wed Feb  1 05:13:48 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8E53129DD6; Wed,  1 Feb 2017 05:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.988
X-Spam-Level: 
X-Spam-Status: No, score=-4.988 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-3.199, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=fFNyo988; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=J8GHS9Wj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id trGYGTdamGAB; Wed,  1 Feb 2017 05:13:45 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 67938129DD4; Wed,  1 Feb 2017 05:13:45 -0800 (PST)
Received: from sm-THINK.elandsys.com (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v11DDYmj019702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 05:13:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1485954817; x=1486041217; bh=OjtWcBUzulZNtQ8L4e3lyoR4wezI3rc1sfrsR7LRymk=; h=Date:To:From:Subject:In-Reply-To:References; b=fFNyo988rU73dVUMvteDguZ+JnhVMYUHQD1XZrst6k91tBhcr/B1C5N3ABNT+lX+v zjY4rhfwq362t5hqH1BUpffyuvZD1SjMKEtgNviVJFTOkI/sAiI59n1td8BA3W0HxF dz5AVybMrnMiiUYWqmEd5k/5yNczZuQWrmUPztfg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1485954817; x=1486041217; i=@elandsys.com; bh=OjtWcBUzulZNtQ8L4e3lyoR4wezI3rc1sfrsR7LRymk=; h=Date:To:From:Subject:In-Reply-To:References; b=J8GHS9Wj5EzKyqdHkUMMOankKDD+TmEiKGeFl8MN0n3JHqdgyef4VMCwNaxL5QMxk plWA3bCWlGFnzOH9YT5n89+iSmvZ9KA8hhZocI//mJIQ4Fgj+RfYbwl4iBVScP9uzZ LHW4AYv2KXAViA5eS9/HEZQjd657VdSbPPz3cecQ=
Message-Id: <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Feb 2017 05:12:11 -0800
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, ietf@ietf.org, iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: If categories of people are blocked by the U.S., should the IETF respond?
In-Reply-To: <0d60ed80-2183-e329-05ad-e0cd7ab77ac1@cs.tcd.ie>
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <CAHw9_iJ78ECZ5x8LsR53KhRFnbhi3gV7n8yzG07e1wbN-SG14Q@mail.gmail.com> <8f5ef9ac-b62b-863a-0a0e-f5d2b329de09@nostrum.com> <20170129134410.GA14422@gsp.org> <4D233FE8-6E84-446F-A8ED-604E4F7EAB99@piuha.net> <0d60ed80-2183-e329-05ad-e0cd7ab77ac1@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mDwUbIW10_kn8jnn_fRn6PGWNwY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 13:13:47 -0000

Hi Stephen,
At 05:31 PM 1/29/2017, Stephen Farrell wrote:
>In this case, and as mentioned previously, there is at
>least one aspect that goes beyond mtgvenue, in that those
>leaving from one place to come to a meeting might be
>restricted in returning home. That seems to me to be an
>order of magnitude more problematic than not being allowed
>entry. The "order of magnitude" aspect of that is maybe
>not relevant for IETF discussion, but the "not able to
>contribute since not able to return home" aspect would
>surely be, as would the "not able to travel to *any*
>'foreign' f2f meetings since not able to return home."

At the lower end, it is a visa problem.  The difference between this 
discussion and the one about Singapore is that the latter was not 
related to entry of IETF attendees.  Jari went through the statistics 
to see whether there were IETF attendees from the affected 
countries.  In terms of attendance, the impact is not 
significant.  The IAB appointed a person from RIPE NCC on the 
IAOC.  Based on the message which the person posted to Facebook, I 
guess that the person may not be able to attend the next IETF meeting 
in the U.S.  It is up to the IESG to assess whether the impact should 
be raised from not significant to something else.

>Anyway, and also speaking personally, I do think there
>may be a valid public IETF reaction here, in addition to
>mtgvenue considerations, which is that we, as with any
>scientific or technical organisation with participants
>welcome from all over the globe, depend on the rule of
>law as it relates to travel being somewhat rational and
>relatively stable. (*)
>
>I think the ACM text could be quite close to something
>on which we could garner IETF consensus as it mostly
>says just the above.

My preference is for the public IETF reaction to be based on open 
discussion instead of a discussion behind closed doors.  I don't 
think that IETF Consensus should be a matter of convenience.

>And yes, you may well be right that there will be more
>pressing matters on which we may need to consider comment
>in future. Personally, I think I'd argue that even if that's
>the case (which we all hope won't turn out true but fear
>might) then we'll be better off having had some discussion
>ahead of time as to where we do or do not have IETF consensus
>for relevant comment being within our scope.

I scanned the list quickly and I only found two IESG members, the 
IETF Chair and you, commenting on the issue.  Do the other IESG 
members have an opinion about the topic?  I'll Cc them to find out.

There was a comment a word which is fashionable nowadays [1].  That 
word sounds hollow given the silence of the persons who have been 
using that word.

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg100833.html 


From nobody Wed Feb  1 05:35:44 2017
Return-Path: <kivinen@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F95129E01; Wed,  1 Feb 2017 05:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 MclwyNod4Wwt; Wed,  1 Feb 2017 05:35:39 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.acr.fi [83.145.195.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B781295C1; Wed,  1 Feb 2017 05:35:38 -0800 (PST)
Received: from fireball.acr.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.15.2/8.15.2) with ESMTPS id v11DZYaQ010563 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 1 Feb 2017 15:35:34 +0200 (EET)
Received: (from kivinen@localhost) by fireball.acr.fi (8.15.2/8.14.8/Submit) id v11DZYDV023184; Wed, 1 Feb 2017 15:35:34 +0200 (EET)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <22673.58406.267887.80681@fireball.acr.fi>
Date: Wed, 1 Feb 2017 15:35:34 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [6tisch] Last Call: <draft-ietf-6tisch-minimal-17.txt> (Minimal 6TiSCH Configuration) to Best Current Practice
In-Reply-To: <0117261E-F63B-45CD-80E7-E6FD99435F0E@gmail.com>
References: <148103459764.1842.9947168180087183897.idtracker@ietfa.amsl.com> <D922CE22-B407-4B70-A9CB-D46DF81A338D@gmail.com> <CAMsDxWQ1r5nVbjZBYnbSDZjuf4XFf0=63oLvFWcU=U-7Q1HpOw@mail.gmail.com> <43CFAE07-24CA-48D5-BEE9-4EC5379B2F60@gmail.com> <1500237294.66092.1485795438510.JavaMail.root@canet.uoc.es> <CAC9+vPiuo0r4Tpw1vvum8NrvDyP-yJU-yGKckunWgj479N=bcA@mail.gmail.com> <0117261E-F63B-45CD-80E7-E6FD99435F0E@gmail.com>
X-Mailer: VM 8.2.0b under 25.1.1 (x86_64--netbsd)
X-Edit-Time: 20 min
X-Total-Time: 20 min
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UlWl_zNXRrFYRRWnUaXlv8VXesU>
Cc: draft-ietf-6tisch-minimal@ietf.org, 6tisch <6tisch@ietf.org>, IETF discussion list <ietf@ietf.org>, Xavi Vilajosana Guillen <xvilajosana@uoc.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 13:35:41 -0000

Ralph Droms writes:
>     The EB_PERIOD determines the join time and impacts energy consumption. The
>     value is a trade-off of this two elements according to the network
>     administrator, as shorter the EB period more energy is used but sooner the
>     nodes join the network. This number does not affect different vendor nodes
>     aiming to join the same network (in terms of inter-operability). For us
>     this is more a network policy, IMHO defining a default value would not fit
>     most of the cases. 
> 
> Is it necessary for all devices in a network to use the same value EB_PERIOD? 

Not really. The device wanting to join the network needs to listen to
each channel for certain time period to find enhanced beacons. The
needed depends on the EB_PERIOD, slotframe size, timeslot length and
number of channels.

As it cannot know any of those parameters it needs to guess values for
all of those, and use them, and if it does not hear any beacons during
the timeout period calculated based those guessed values, it can
assume that there is no network nearby, and go for extended sleep
waiting for network to appear.

If the typical values like timeslot length = 10ms, slotframe size =
101, number of channels = 16 and EB_PERIOD of 3 is used, then it knows
that:

  - Slot frame takes 10ms * 101 = 1.01 seconds.
  - Beacon is sent every 3rd slot frame so every 3.03 seconds.
  - Beacon is sent on random channel out of 16, so but most likely
    different channel for every time, so if it waits for one channel
    for 16*3.03 seconds = 48.48 seconds it should have seen one beacon
    on that channel
  - After that timeout it can move to the next channel, as it might be
    that not all 16 channels are in use, so it needs to listen other
    channels too, testing all 16 channels takes 16 * 48.48 seconds =
    775.68 seconds == abour 13 minutes.

So after 13 minutes it can assume that there is no network and go to
sleep. If EB_PERIOD is 10 then it needs to wait for 43 minutes...

On the other hand in most cases all channels are in use, and it will
find the beacon after 25 seconds or so on average with EB_PERIOD set
to 3, and 80 seconds if EB_PERIOD is 10...

This assumes that network has good parameters, i.e. if the slotframe
size would be 100, and number of channels 10, then beacons would
always end up on the same channel, and if that channel happened to be
the last one scanned it can take long time to find out that channel.
Also if that one channel ends up having issues, then beacons might be
lost completely.

Btw, all of the above do assume that none of the beacons are ever
lost, so in practice the device needs to wait for 2-3 times the
EB_PERIOD * slotframe size * timeslot length * number of channels
before moving to next channel, or it might repeat the process 2-3
times before giving up. On the other hand tsch is quite chatty
anyways, so the device should see at least some packets go over the
air during the scan, and if it does not hear any radio transmissions
during the scan it might skip to next channel must faster.

> If so, how is that value communicated or configured in all devices?

It is not communicated, and devices do not need to agree on value. 
-- 
kivinen@iki.fi


From nobody Wed Feb  1 05:44:29 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48DB4129E42; Wed,  1 Feb 2017 05:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.5
X-Spam-Level: 
X-Spam-Status: No, score=-7.5 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_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uu_ljDZXdImU; Wed,  1 Feb 2017 05:44:26 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25438129E37; Wed,  1 Feb 2017 05:44:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 99652BE56; Wed,  1 Feb 2017 13:44:23 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jHGz8GT3NCGH; Wed,  1 Feb 2017 13:44:23 +0000 (GMT)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 057F1BE51; Wed,  1 Feb 2017 13:44:23 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1485956663; bh=OaRmjcNTJRgDtiJyTXaQcYJbWPOU98Rvv4tr7cCWrgg=; h=Subject:To:References:From:Date:In-Reply-To:From; b=3fMS7gBPHWk1XiR8qBTvoIkj2KmEXEI2aTsI4Wpj/YcjR4s9Ws2+4oP4RxJM2H7TB cKjW+8J+akO1B1dBBVJ6wZOSPNSnR3pQTGUBSA/bQebmOV8q8dW6WnymP8IrH/cvog H5czBgJ+zJbKRqGxKvGezOTRl0qzqbQbQyXQD9/s=
Subject: Re: If categories of people are blocked by the U.S., should the IETF respond?
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org, iesg@ietf.org
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <CAHw9_iJ78ECZ5x8LsR53KhRFnbhi3gV7n8yzG07e1wbN-SG14Q@mail.gmail.com> <8f5ef9ac-b62b-863a-0a0e-f5d2b329de09@nostrum.com> <20170129134410.GA14422@gsp.org> <4D233FE8-6E84-446F-A8ED-604E4F7EAB99@piuha.net> <0d60ed80-2183-e329-05ad-e0cd7ab77ac1@cs.tcd.ie> <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <f8139562-4589-23b5-3503-0cff95b0617f@cs.tcd.ie>
Date: Wed, 1 Feb 2017 13:44:23 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms080600040703060400090700"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CAeuHAO-VNxwQ9l-PEZuUEoxzpU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 13:44:28 -0000

This is a cryptographically signed message in MIME format.

--------------ms080600040703060400090700
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hiya,

On 01/02/17 13:12, S Moonesamy wrote:
>=20
> I scanned the list quickly and I only found two IESG members, the IETF
> Chair and you, commenting on the issue.  Do the other IESG members have=

> an opinion about the topic?  I'll Cc them to find out.

I can help you there. The IESG and IAB (and I'm told the IAOC
and meetings ctte) have been actively discussing all of this.
I'm on one thread between IAB and IESG that has 84 messages in
total (though a good few of those are duplicates in my crappy
foldering scheme;-). And I think this topic may be on the agenda
for an upcoming IAB call and it is on the agenda for an IESG
call tomorrow. If something concrete results from those calls
it'll likely take at least a few days to be visible to the
community. Or maybe we'll need a bit longer. (That's another
reason why it was good that Jari/Andrew/Leslie posted that
blog, and yes they'd gotten some feedback from I* folks
before doing so.)

So while of course I* folks may respond to you if they've
stuff to say, I don't think there's much need for a slew of
"yeah we're aware of that" mails. But it is the case that quite
a few IESG/IAB folks have been actively engaged on this.

Cheers,
S.


--------------ms080600040703060400090700
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
CvIwggUIMIID8KADAgECAhBPzaE7pzYviUJyhmHTFBdnMA0GCSqGSIb3DQEBCwUAMHUxCzAJ
BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSkwJwYDVQQLEyBTdGFydENvbSBD
ZXJ0aWZpY2F0aW9uIEF1dGhvcml0eTEjMCEGA1UEAxMaU3RhcnRDb20gQ2xhc3MgMSBDbGll
bnQgQ0EwHhcNMTYwMjA5MDkyODE1WhcNMTcwMjA5MDkyODE1WjBOMSIwIAYDVQQDDBlzdGVw
aGVuLmZhcnJlbGxAY3MudGNkLmllMSgwJgYJKoZIhvcNAQkBFhlzdGVwaGVuLmZhcnJlbGxA
Y3MudGNkLmllMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtuC0rYze/2JinSra
C9F2RjGdQZjNALLcW9C3WKTwYII3wBslobmHuPEYE5JaGItmzuKnAW619R1rD/kfoNWC19N3
rBZ6UX9Cmb9D9exCwYIwVuSwjrCQWGxgCtNQTrwKzCCpI790GRiMTvxvO7UmzmBrCaBLiZW5
R0fBjK5Yn6hUhAzGBkNbkIEL28cLJqH0yVz7Kl92OlzrQqTPEts5m6cDnNdY/ADfeAX18c1r
dxZqcAxhLotrCqgsVA4ilbQDMMXGTLlB5TP35HeWZuGBU7xu003rLcFLdOkD8xvpJoYZy9Kt
3oABXPS5yqtMK+XCNdqmMn+4mOtLwQSMmPCSiQIDAQABo4IBuTCCAbUwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAJBgNVHRMEAjAAMB0GA1UdDgQWBBQJ
QhvwQ5Fl372Z6xqo6fdn8XejTTAfBgNVHSMEGDAWgBQkgWw5Yb5JD4+3G0YrySi1J0htaDBv
BggrBgEFBQcBAQRjMGEwJAYIKwYBBQUHMAGGGGh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbTA5
BggrBgEFBQcwAoYtaHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc2NhLmNsaWVudDEu
Y3J0MDgGA1UdHwQxMC8wLaAroCmGJ2h0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL3NjYS1jbGll
bnQxLmNybDAkBgNVHREEHTAbgRlzdGVwaGVuLmZhcnJlbGxAY3MudGNkLmllMCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzBGBgNVHSAEPzA9MDsGCysGAQQBgbU3AQIE
MCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeTANBgkqhkiG
9w0BAQsFAAOCAQEArzrSv2C8PlBBmGuiGrzm2Wma46/KHtXmZYS0bsd43pM66Pc/MsqPE0HD
C1GzMFfwB6BfkJn8ijNSIhlgj898WzjvnpM/SO8KStjlB8719ig/xKISrOl5mX55XbFlQtX9
U6MrqRgbDIATxhD9IDr+ryvovDzChqgQj7mt2jYr4mdlRjsjod3H1VY6XglRmaaNGZfsCARM
aE/TU5SXIiqauwt5KxNGYAY67QkOBs7O1FkSXpTk7+1MmzJMF4nP8QQ5n8vhVNseF+/Wm7ai
9mtnrkLbaznMsy/ULo/C2yuLUWTbZZbf4EKNmVdme6tUDgYkFjAFOblfA7W1fSPiQGagYzCC
BeIwggPKoAMCAQICEGunin0K14jWUQr5WeTntOEwDQYJKoZIhvcNAQELBQAwfTELMAkGA1UE
BhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFs
IENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MB4XDTE1MTIxNjAxMDAwNVoXDTMwMTIxNjAxMDAwNVowdTELMAkGA1UEBhMC
SUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmlj
YXRpb24gQXV0aG9yaXR5MSMwIQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL192vfDon2D9luC/dtbX64eG3XAtRmv
mCSsu1d52DXsCR58zJQbCtB2/A5uFqNxWacpXGGtTCRk9dEDBlmixEd8QiLkUfvHpJX/xKnm
VkS6Iye8wUbYzMsDzgnpazlPg19dnSqfhM+Cevdfa89VLnUztRr2cgmCfyO9Otrh7LJDPG+4
D8ZnAqDtVB8MKYJL6QgKyVhhaBc4y3bGWxKyXEtx7QIZZGxPwSkzK3WIN+VKNdkiwTubW5PI
dopmykwvIjLPqbJK7yPwFZYekKE015OsW6FV+s4DIM8UlVS8pkIsoGGJtMuWjLL4tq2hYQuu
N0jhrxK1ljz50hH23gA9cbMCAwEAAaOCAWQwggFgMA4GA1UdDwEB/wQEAwIBBjAdBgNVHSUE
FjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIBADAyBgNVHR8EKzAp
MCegJaAjhiFodHRwOi8vY3JsLnN0YXJ0c3NsLmNvbS9zZnNjYS5jcmwwZgYIKwYBBQUHAQEE
WjBYMCQGCCsGAQUFBzABhhhodHRwOi8vb2NzcC5zdGFydHNzbC5jb20wMAYIKwYBBQUHMAKG
JGh0dHA6Ly9haWEuc3RhcnRzc2wuY29tL2NlcnRzL2NhLmNydDAdBgNVHQ4EFgQUJIFsOWG+
SQ+PtxtGK8kotSdIbWgwHwYDVR0jBBgwFoAUTgvvGqRAW6UXaYcwyjRoQ9BBrvIwPwYDVR0g
BDgwNjA0BgRVHSAAMCwwKgYIKwYBBQUHAgEWHmh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Bv
bGljeTANBgkqhkiG9w0BAQsFAAOCAgEAi+P3h+wBi4StDwECW5zhIycjBL008HACblIf26HY
0JdOruKbrWDsXUsiI0j/7Crft9S5oxvPiDtVqspBOB/y5uzSns1lZwh7sG96bYBZpcGzGxpF
NjDmQbcM3yl3WFIRS4WhNrsOY14V7y2IrUGsvetsD+bjyOngCIVeC/GmsmtbuLOzJ606tEc9
uRbhjTu/b0x2Fo+/e7UkQvKzNeo7OMhijixaULyINBfCBJb+e29bLafgu6JqjOUJ9eXXj20p
6q/CW+uVrZiSW57+q5an2P2i7hP85jQJcy5j4HzA0rSiF3YPhKGAWUxKPMAVGgcYoXzWydOv
Z3UDsTDTagXpRDIKQLZo02wrlxY6iMFqvlzsemVf1odhQJmi7Eh5TbxI40kDGcBOBHhwnaOu
mZhLP+SWJQnjpLpSlUOj95uf1zo9oz9e0NgIJoz/tdfrBzez76xtDsK0KfUDHt1/q59BvDI7
RX6gVr0fQoCyMczNzCTcRXYHY0tq2J0oT+bsb6sH2b4WVWAiJKnSYaWDjdA70qHX4mq9MIjO
/ZskmSY8wtAk24orAc0vwXgYanqNsBX5Yv4sN4Z9VyrwMdLcusP7HJgRdAGKpkR2I9U4zEsN
JQJewM7S4Jalo1DyPrLpL2nTET8ZrSl5Utp1UeGp/2deoprGevfnxWB+vHNQiu85o6MxggPM
MIIDyAIBATCBiTB1MQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjEpMCcG
A1UECxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkxIzAhBgNVBAMTGlN0YXJ0
Q29tIENsYXNzIDEgQ2xpZW50IENBAhBPzaE7pzYviUJyhmHTFBdnMA0GCWCGSAFlAwQCAQUA
oIICEzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNzAyMDEx
MzQ0MjNaMC8GCSqGSIb3DQEJBDEiBCAYzgfaULfrZUy7Vc0/M28ewBC4ydDnNKUkVElFRh1r
5TBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcN
AwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMC
AgEoMIGaBgkrBgEEAYI3EAQxgYwwgYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMw
IQYDVQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzCB
nAYLKoZIhvcNAQkQAgsxgYyggYkwdTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29t
IEx0ZC4xKTAnBgNVBAsTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MSMwIQYD
VQQDExpTdGFydENvbSBDbGFzcyAxIENsaWVudCBDQQIQT82hO6c2L4lCcoZh0xQXZzANBgkq
hkiG9w0BAQEFAASCAQBo7Rn9yWXd+0GSCMILpG5OQZ8gq+vkmVESz2nv5Hczm17RCVsb839L
Uz8DzoDUIVfU9GRqBIpF3Glfr8TTk02h2pqHdMxW8H/uZJt/4PQnjPW52nNCAgYkDLwnATkK
ZUZmSihGl4Nno1r6UddZFBdx9CipU05baVU/SjHfD/5rL73myfOdQaaR09UiDwdq/525y/qU
sRuP2haiczQFiNBZCoEMeAtc4/BlQ0r3SMVPsBylK5AWgwc0JLuwpqt5okSAYMeJquj3fNZg
FFpG/nE0d2YyD4epcmz4bzzs92vBgkyTxpS2sG0tepsE3ziCdddk0XzNgmH6tr8Lh6w4XgeS
AAAAAAAA
--------------ms080600040703060400090700--


From nobody Wed Feb  1 07:28:31 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 338451293F3; Wed,  1 Feb 2017 07:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.498
X-Spam-Level: 
X-Spam-Status: No, score=-7.498 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, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKHTip4Gt8Xn; Wed,  1 Feb 2017 07:28:23 -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 9E676129494; Wed,  1 Feb 2017 07:28:22 -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 v11FS3pX005308; Wed, 1 Feb 2017 15:28:03 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v11FS3pX005308
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1485962884; bh=y9QgCJtIJ2iyhdaNDNR8/U2/u38=; h=From:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References; b=DyDRbeqcX3Ts3HeNv23K9lQx4b1KVb6WwZTYmkPK9QPOZxDzEJ9i4uhIsgsffnBN7 P5iDkR0avrTLNXY9pfSclAKLlTyVInNWnWJOrOgnAKNldpeitoLeKzVmPtkkdVP9Hq D6HXFXOTyOwntKut96Zyt3GWBnW0yq4D4MGiwnpI=
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 y10FS31512310152ea ret-id none; Wed, 01 Feb 2017 15:28:04 +0000
Received: from [10.99.107.130] (pat-231-107.external.eduroam.ucl.ac.uk [193.60.231.107]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v11FRt1H030393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Feb 2017 15:27:55 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Message-ID: <EMEW3|69b53897f034d9304337eb0b89dfca8fy10FS303tjc|ecs.soton.ac.uk|52D571CA-BAAB-4B8E-89F4-35BE45C09234@ecs.soton.ac.uk>
Content-Type: multipart/alternative; boundary="Apple-Mail=_36BFD371-6251-4780-A014-CDD44BAE0E74"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: If categories of people are blocked by the U.S., should the IETF respond?
Date: Wed, 1 Feb 2017 15:27:55 +0000
In-Reply-To: <f8139562-4589-23b5-3503-0cff95b0617f@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <CAHw9_iJ78ECZ5x8LsR53KhRFnbhi3gV7n8yzG07e1wbN-SG14Q@mail.gmail.com> <8f5ef9ac-b62b-863a-0a0e-f5d2b329de09@nostrum.com> <20170129134410.GA14422@gsp.org> <4D233FE8-6E84-446F-A8ED-604E4F7EAB99@piuha.net> <0d60ed80-2183-e329-05ad-e0cd7ab77ac1@cs.tcd.ie> <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com> <f8139562-4589-23b5-3503-0cff95b0617f@cs.tcd.ie> <52D571CA-BAAB-4B8E-89F4-35BE45C09234@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y10FS3151231015200; tid=y10FS31512310152ea; client=relay,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v11FS3pX005308
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DpOkpbmO3x0lUslYkqraZtvUZDE>
Cc: iesg@ietf.org, S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 15:28:25 -0000

--Apple-Mail=_36BFD371-6251-4780-A014-CDD44BAE0E74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

On 1 Feb 2017, at 13:44, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
>=20
> Hiya,
>=20
> On 01/02/17 13:12, S Moonesamy wrote:
>>=20
>> I scanned the list quickly and I only found two IESG members, the =
IETF
>> Chair and you, commenting on the issue.  Do the other IESG members =
have
>> an opinion about the topic?  I'll Cc them to find out.
>=20
> I can help you there. The IESG and IAB (and I'm told the IAOC
> and meetings ctte) have been actively discussing all of this.
> I'm on one thread between IAB and IESG that has 84 messages in
> total (though a good few of those are duplicates in my crappy
> foldering scheme;-). And I think this topic may be on the agenda
> for an upcoming IAB call and it is on the agenda for an IESG
> call tomorrow. If something concrete results from those calls
> it'll likely take at least a few days to be visible to the
> community. Or maybe we'll need a bit longer. (That's another
> reason why it was good that Jari/Andrew/Leslie posted that
> blog, and yes they'd gotten some feedback from I* folks
> before doing so.)
>=20
> So while of course I* folks may respond to you if they've
> stuff to say, I don't think there's much need for a slew of
> "yeah we're aware of that" mails. But it is the case that quite
> a few IESG/IAB folks have been actively engaged on this.

It seems the person who is being officially appointed as IAB=E2=80=99s =
liaison the the IAOC will now not be able to attend the Chicago IETF:

=
https://motherboard.vice.com/en_us/article/icann-trump-travel-ban-internet=
 =
<https://motherboard.vice.com/en_us/article/icann-trump-travel-ban-interne=
t>

(apologies if this has been mentioned already - so many emails on this =
important topic - but I also saw this directly on Facebook from the =
volume of shares on the post by people I trust, so I assume it=E2=80=99s =
genuine)

Tim=

--Apple-Mail=_36BFD371-6251-4780-A014-CDD44BAE0E74
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 class=3D"">Hi,</div><div class=3D""><br =
class=3D""></div>On 1 Feb 2017, at 13:44, Stephen Farrell &lt;<a =
href=3D"mailto:stephen.farrell@cs.tcd.ie" =
class=3D"">stephen.farrell@cs.tcd.ie</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br class=3D""><div =
class=3D""><div class=3D"">Hiya,<br class=3D""><br class=3D"">On =
01/02/17 13:12, S Moonesamy wrote:<br class=3D""><blockquote type=3D"cite"=
 class=3D""><br class=3D"">I scanned the list quickly and I only found =
two IESG members, the IETF<br class=3D"">Chair and you, commenting on =
the issue. &nbsp;Do the other IESG members have<br class=3D"">an opinion =
about the topic? &nbsp;I'll Cc them to find out.<br =
class=3D""></blockquote><br class=3D"">I can help you there. The IESG =
and IAB (and I'm told the IAOC<br class=3D"">and meetings ctte) have =
been actively discussing all of this.<br class=3D"">I'm on one thread =
between IAB and IESG that has 84 messages in<br class=3D"">total (though =
a good few of those are duplicates in my crappy<br class=3D"">foldering =
scheme;-). And I think this topic may be on the agenda<br class=3D"">for =
an upcoming IAB call and it is on the agenda for an IESG<br =
class=3D"">call tomorrow. If something concrete results from those =
calls<br class=3D"">it'll likely take at least a few days to be visible =
to the<br class=3D"">community. Or maybe we'll need a bit longer. =
(That's another<br class=3D"">reason why it was good that =
Jari/Andrew/Leslie posted that<br class=3D"">blog, and yes they'd gotten =
some feedback from I* folks<br class=3D"">before doing so.)<br =
class=3D""><br class=3D"">So while of course I* folks may respond to you =
if they've<br class=3D"">stuff to say, I don't think there's much need =
for a slew of<br class=3D"">"yeah we're aware of that" mails. But it is =
the case that quite<br class=3D"">a few IESG/IAB folks have been =
actively engaged on this.<br class=3D""></div></div></blockquote></div><br=
 class=3D""><div class=3D"">It seems the person who is being officially =
appointed as IAB=E2=80=99s liaison the the IAOC will now not be able to =
attend the Chicago IETF:</div><div class=3D""><br class=3D""></div><div =
class=3D""><a =
href=3D"https://motherboard.vice.com/en_us/article/icann-trump-travel-ban-=
internet" =
class=3D"">https://motherboard.vice.com/en_us/article/icann-trump-travel-b=
an-internet</a></div><div class=3D""><br class=3D""></div><div =
class=3D"">(apologies if this has been mentioned already - so many =
emails on this important topic - but I also saw this directly on =
Facebook from the volume of shares on the post by people I trust, so I =
assume it=E2=80=99s genuine)</div><div class=3D""><br =
class=3D""></div><div class=3D"">Tim</div></body></html>=

--Apple-Mail=_36BFD371-6251-4780-A014-CDD44BAE0E74--


From nobody Wed Feb  1 07:51:08 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BF0129496; Wed,  1 Feb 2017 07:51:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YEJjS67jh5vu; Wed,  1 Feb 2017 07:51:05 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::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 DD2A5129407; Wed,  1 Feb 2017 07:51:04 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id 73so293203012otj.0; Wed, 01 Feb 2017 07:51:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=b3G7OGOneZnM3JvRhU4ENwTcuf/euk03EKHPNxlHN7U=; b=p6Oti7Kbsmc+bh4VUgysRNPIcq5k2LqaqiHkCqf7CJYw6whtX8S1t/z2SlB1y/sq49 8UB4xDuHU/VQDLdIMHBKlyZNu46KXnEkrw9UKMk3yqloBuwGWdYlKDb8WkOIcGmKzqcP t8rcS1QIERDQtw/KNri6XGQJ8MCI4jxiAErFXNE8WCilQT1PzgTcY08d/6VVZcaMClMC HhDJTcBmsQo2DGUaqd6V46Qtr7HyWxnqo7NyOzzhAoSf+uAciVD6WW+DZxRuUW+MopeK FWTdlEN4FAICjl9B1G2/UbB5STiOIgjvq79Q6YaEDYpYFymF7Z41iiguYu5NFa93EnWw yhwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=b3G7OGOneZnM3JvRhU4ENwTcuf/euk03EKHPNxlHN7U=; b=R3uDflmKRmcn0cArYtnx56uu8jp7nzgYATfvX3bnF3gwbFk29diYPkfJsMFPg0MSlq ND/3QdOcMXdrIAGwq/ToteP2lmz4zMp6U03JrHrChmdwd6MTRCk4pDCE2XnsY2KvdrTF YHb4MyimI/Iqy+cEFsTzy98yrRt1gHCdSLP88pJgY9eGkd0q4BA6uVYbYzJFskD9F1hI +ChnYm4gj6+NyPSQfnndJvGaZiyDP92dN96xNGlYz1bAgBO/9x9a+tBzqEvXGuUtCPiA Z3hyUY/xFMxk39C+PNu2pBVip2X00m3bbtQILUZgyzZABFYjR+A8IhjZmHc3tlgDwltN YFYQ==
X-Gm-Message-State: AMke39n9+0zkIMLt2GPq5KJAJQqzwOMPpeJOkQcEsGYPHQUlqx9V1jBinSqoR5W0TbCD61zkjv+xKR/FdB19Ew==
X-Received: by 10.157.52.253 with SMTP id t58mr1784906otd.161.1485964264194; Wed, 01 Feb 2017 07:51:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Wed, 1 Feb 2017 07:50:23 -0800 (PST)
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com>
From: tianxiang li <peter416733@gmail.com>
Date: Wed, 1 Feb 2017 23:50:23 +0800
Message-ID: <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
To: Roni Even <roni.even@huawei.com>
Content-Type: multipart/alternative; boundary=001a1140a4621dc8a505477a049b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rrc6Dd4IsUFpaA-rT_Qu28wcnAU>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 15:51:07 -0000

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

Hi Roni,

Thank you for the response, please see inline.

Cheers,
Tianxiang

2017-02-01 15:02 GMT+08:00 Roni Even <roni.even@huawei.com>:

> Hi,
>
> See inline
>
> Roni
>
>
>
> *From:* Gen-art [mailto:gen-art-bounces@ietf.org] *On Behalf Of *tianxian=
g
> li
> *Sent:* =D7=99=D7=95=D7=9D =D7=92 31 =D7=99=D7=A0=D7=95=D7=90=D7=A8 2017 =
17:59
> *To:* Roni Even
> *Cc:* dhcwg; gen-art@ietf.org; ietf@ietf.org;
> draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
> *Subject:* Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-l
> ength-hint-issue-05
>
>
>
> Dear Roni,
>
>
>
> Thank you for providing a thorough review of this document.
>
>
>
> I have a few questions regarding the comments, please see inline.
>
>
>
> Best regards,
>
> Tianxiang
>
>
>
> 2017-01-29 17:02 GMT+08:00 Roni Even <roni.even@mail01.huawei.com>:
>
> Reviewer: Roni Even
> Review result: Almost Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
> Reviewer: Roni Even
> Review Date: 2017-01-29
> IETF LC End Date: 2017-02-09
> IESG Telechat date: 2017-02-16
>
> Summary: This draft is almost ready for publication as a standard
> track RFC.
>
>
> Major issues:
>
> Minor issues:
>
> 1.      I think that this document updates RFC3633 and it should be
> mentioned in the title and abstract
>
>
>
> [Tianxiang] This document does not change any of the text in RFC 3633, bu=
t
> specifies the client and server behavior when using the "prefix-length
> hint", which was not explained in RFC3633. Would it be suitable to state
> "this document updates RFC3633"?
>
> *[Roni Even] Yes, this is what I meant and it needs to be written in  the
> title and abstract, it will also point people looking at RFC3633 to this
> document*
>
>
>
[Tianxiang2] Okay, we could add a sentence in the end of the abstract
saying "This document updates RFC3633".

For the title, we followed a similar name with RFC7550 which updated
RFC3315 and RFC3633. It was titled "Issues and Recommendations with
Multiple Stateful DHCPv6 Options". Do you have some recommendations on how
to change the document title?

> 2.      In section 3.1 reference RFC3315 for solicit message and 3.3 for
> advertise messge
>
>
>
> [Tianxiang] Okay, we'll add reference to RFC3315 in section 3.1 and 3.3
> when mentioning Solicit and Advertise messgae.
>
> *[Roni Even] OK*
>
>
>
> 3.      In section 3.1 solution last paragraph is the order of the two
> IAPREFIX options important?
>
>
>
> [Tianxiang] There is no strict requirement for the order of the two
> options. Would you prefer if we added a sentence to specify this?
>
> *[Roni Even] I assumed this was the case but it will better to clarify*
>
>
>
> 4.      In section 3.2 solution why are you suing SHOULD and not MUST in
> all recommendations?
>
>
>
> [Tianxiang] In this document, we used "MUST" for some of the client
> behaviors, as they are mandatory to avoid client failure and necessary if
> the client wanted to express its prefix-length requirement.
>
>
>
> For server behavior, we used "SHOULD" because this document specifies the
> desired server behavior if the server wants to consider the prefix-length
> hint, but the server could have its own behavioral policy (e.g. neglect t=
he
> prefix-length hint).
>
> *[Roni Even] This make sense, but it will be good to clarify why it is a
> SHOULD using your explanation*
>
>
>
> 5.      In section 3.2 solution, what should the server do if cannot
> provide any of the requests
>
>
>
> [Tianxiang] If the server could not provide the requested prefix or
> prefix-length, it should provide a prefix closest to the prefix-length
> hint, as stated in the last sentence of section 3.2.
>
>
>
> Are you referring to what the sever should do of it simply could not
> provide ANY prefixes to the client? In that case, we could add a sentence
> at the end of the section 3.2:
>
>
>
> "If the server will not assign any prefixes to any IA_PDs in a subsequent
> Request from the client, the server MUST send an Advertise message to the
> client as described in section 11.2 of RFC 3633."
>
> *[Roni Even] This sentence is what I was looking for.*
>
>
>
> 6.      In section 3.2 solution last paragraph =E2=80=9CSHOULD try to pro=
vide=E2=80=9D and
> in the first paragraph =E2=80=9CSHOULD provide=E2=80=9D should be the sam=
e in both.
>
>
>
> [Tianxiang] Thanks for pointing that out, we'll change it to "SHOULD
> provide".
>
>
>
> *[Roni Even] OK*
>
>
>
> 7.      In section 3.4 =E2=80=9CIf the client decided to use  the prefix =
provided
> by the server despite being longer than the  prefix-length hint=E2=80=9D =
yet I
> did not see in section 3.2 that the server can provide a longer
> prefix.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2:
>
>
>
> "If the requested prefix is not available in the server's prefix pool, an=
d
> the client also included a prefix-length hint in the same IA_PD option,
> then the server SHOULD try to provide a prefix matching the prefix-length
> value, or the prefix with the shortest length possible which is closest t=
o
> the prefix-length hint value."
>
> *[Roni Even] I understood from 3.2 that it should provide a shorter lengt=
h
> prefix  closer to the request maybe =E2=80=9C*or the prefix with the clos=
est
> possible length to the prefix-length hint value=E2=80=9D
>
>
>
[Tianxiang2] The original sentence was a bit confusing, perhaps we could
change it like this:

OLD: "If the requested prefix is not available in the server's prefix pool,
and the client also included a prefix-length hint in the same IA_PD option,
then the server SHOULD try to provide a prefix matching the prefix-length
value, or the prefix with the shortest length possible which is closest to
the prefix-length hint value."

NEW:"If the requested prefix is not available in the server's prefix pool,
and the client also included a prefix-length hint in the same IA_PD option,
then the server SHOULD provide a prefix matching the prefix-length hint, or
a prefix which is length is shorter and as close as possible to the
prefix-length hint. If the server could not provide a prefix which length
is shorter or equal to the prefix-length hint, the server SHOULD provide
the prefix which length is longer and as close as possible to the
prefix-length hint."

8.      In section 3.5 solution the document use =E2=80=9Cas close as possi=
ble=E2=80=9D and
> section 3.2 only talk about smaller.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2.
>
> *[Roni Even] See above to point 7*
>
>
>
> 9.     In section 3.5 solution why offer options 3 and 4. The draft
> says that option 3 will break client connections and 4 talks about =E2=80=
=9Ca
> short non-zero valid-lifetime=E2=80=9D which may cause the  client to los=
e
> connection if "too short for the client" since =E2=80=9Cshort=E2=80=9D is=
 not an exact
> value
>
>
>
> [Tianxiang] The idea was to list all the options, and discuss their
> consequences. And the server could decide which option to use depending o=
n
> its policy.
>
>
>
> Option 3 avoids the complexity of handling multiple delegated prefixes,
> despite of breaking up all connections. Option 4 allows to server to
> configure a valid-lifetime for the old prefix depending on actual
> requirements, rather than let the old prefix expire on its own.
>
> *[Roni Even] OK, still option 4 may have similar result to 3 since =E2=80=
=9Ca
> short non-zero=E2=80=9D may be too short. Why not add a recommended value=
?*
>
>
>
[Tianxiang2] Agree, as this may vary for different services, we could
change the text to say "a specific valid-lifetime depending on the actual
requirement".


>
>
>
> Nits/editorial comments:
>
>
>
>

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

<div dir=3D"ltr">Hi Roni,<div><br></div><div>Thank you for the response, pl=
ease see inline.</div><div><br></div><div>Cheers,</div><div>Tianxiang</div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-02-01 15:02 =
GMT+08:00 Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:roni.even@huawe=
i.com" target=3D"_blank">roni.even@huawei.com</a>&gt;</span>:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmail-m_-49=
00649193753751102WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">See inline<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)">Roni<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border-top:none;border-right:none;border-bottom:none;border-l=
eft:1.5pt solid blue;padding:0cm 0cm 0cm 4pt">
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(181,196,223);padding:3pt 0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10pt;font-family:tahoma,=
sans-serif">From:</span></b><span style=3D"font-size:10pt;font-family:tahom=
a,sans-serif"> Gen-art [mailto:<a href=3D"mailto:gen-art-bounces@ietf.org" =
target=3D"_blank">gen-art-bounces@ietf.o<wbr>rg</a>]
<b>On Behalf Of </b>tianxiang li<br>
<b>Sent:</b> <span lang=3D"HE" dir=3D"RTL">=D7=99=D7=95=D7=9D=C2=A0=D7=92 3=
1 =D7=99=D7=A0=D7=95=D7=90=D7=A8 2017 17:59</span><br>
<b>To:</b> Roni Even<br>
<b>Cc:</b> dhcwg; <a href=3D"mailto:gen-art@ietf.org" target=3D"_blank">gen=
-art@ietf.org</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@=
ietf.org</a>; <a href=3D"mailto:draft-ietf-dhc-dhcpv6-prefix-length-hint-is=
sue.all@ietf.org" target=3D"_blank">draft-ietf-dhc-dhcpv6-prefix-l<wbr>engt=
h-hint-issue.all@ietf.org</a><br>
<b>Subject:</b> Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-l<wbr>=
ength-hint-issue-05<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div><div><div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246g=
mail-h5">
<p class=3D"MsoNormal">Dear Roni,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thank you for providing a thorough review of this do=
cument.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have a few questions regarding the comments, pleas=
e see inline.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Tianxiang<u></u><u></u></p>
</div>
</div></div><div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div><div><div class=3D"m_-6060726979536003119gmail-m_-6524802112207049246g=
mail-h5">
<p class=3D"MsoNormal">2017-01-29 17:02 GMT+08:00 Roni Even &lt;<a href=3D"=
mailto:roni.even@mail01.huawei.com" target=3D"_blank">roni.even@mail01.huaw=
ei.com</a>&gt;:<u></u><u></u></p>
<p class=3D"MsoNormal">Reviewer: Roni Even<br>
Review result: Almost Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_bl=
ank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
<br>
Document: draft-ietf-dhc-dhcpv6-prefix-l<wbr>ength-hint-issue-05<br>
Reviewer: Roni Even<br>
Review Date: 2017-01-29<br>
IETF LC End Date: 2017-02-09<br>
IESG Telechat date: 2017-02-16<br>
<br>
Summary: This draft is almost ready for publication as a standard<br>
track RFC.<br>
<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1.=C2=A0 =C2=A0 =C2=A0 I think that this document updates RFC3633 and it sh=
ould be<br>
mentioned in the title and abstract<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div><div><div><div class=3D"m_-6060726979536003119gmail-m_-65248021=
12207049246gmail-h5">
<p class=3D"MsoNormal">[Tianxiang] This document does not change any of the=
 text in RFC 3633, but specifies the client and server behavior when using =
the &quot;prefix-length hint&quot;, which was not explained in RFC3633. Wou=
ld it be suitable to state &quot;this document updates
 RFC3633&quot;?<u></u><u></u></p>
</div></div><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font=
-family:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] Yes, this is w=
hat I meant and it needs to be written in=C2=A0 the title and abstract, it =
will also point people looking at RFC3633 to this document</span></i></b><s=
pan style=3D"font-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,=
125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0</p></div></span></div></div></div></div></div=
></div></blockquote><div>[Tianxiang2] Okay, we could add a sentence in the =
end of the abstract saying &quot;This document updates RFC3633&quot;.</div>=
<div><br></div><div>For the title, we followed a similar name with RFC7550 =
which updated RFC3315 and RFC3633. It was titled &quot;Issues and Recommend=
ations with Multiple Stateful DHCPv6 Options&quot;. Do you have some recomm=
endations on how to change the document title?</div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-60607269795=
36003119gmail-m_-6524802112207049246gmail-m_-4900649193753751102WordSection=
1"><div style=3D"border-top:none;border-right:none;border-bottom:none;borde=
r-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt"><div><div><div><span class=
=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmail-"><div><p class=
=3D"MsoNormal"><u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">2.=C2=A0 =C2=A0 =C2=A0 In section 3.1 reference RFC3=
315 for solicit message and 3.3 for<br>
advertise messge=C2=A0<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] Okay, we&#39;ll add reference to RFC3315=
 in section 3.1 and 3.3 when mentioning Solicit and Advertise messgae.<u></=
u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK</span></i></b><s=
pan style=3D"font-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,=
125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">3.=C2=A0 =C2=A0 =C2=A0 In section 3.1 solution last =
paragraph is the order of the two<br>
IAPREFIX options important?<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] There is no strict requirement for the o=
rder of the two options. Would you prefer if we added a sentence to specify=
 this?<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] I assumed this was =
the case but it will better to clarify</span></i></b><span style=3D"font-si=
ze:11pt;font-family:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u>=
</span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">4.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution why a=
re you suing SHOULD and not MUST in<br>
all recommendations?<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] In this document, we used &quot;MUST&quo=
t; for some of the client behaviors, as they are mandatory to avoid client =
failure and necessary if the client wanted to express its prefix-length req=
uirement.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">For server behavior, we used &quot;SHOULD&quot; beca=
use this document specifies the desired server behavior if the server wants=
 to consider the prefix-length hint, but the server could have its own beha=
vioral policy (e.g. neglect the prefix-length
 hint).<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] This make sense, bu=
t it will be good to clarify why it is a SHOULD using your explanation</spa=
n></i></b><span style=3D"font-size:11pt;font-family:calibri,sans-serif;colo=
r:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">5.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution, what=
 should the server do if cannot<br>
provide any of the requests<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] If the server could not provide the requ=
ested prefix or prefix-length, it should provide a prefix closest to the pr=
efix-length hint, as stated in the last sentence of section 3.2.<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Are you referring to what the sever should do of it =
simply could not provide ANY prefixes to the client? In that case, we could=
 add a sentence at the end of the section 3.2:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">&quot;If the server will not assign any prefixes to =
any IA_PDs in a subsequent Request from the client, the server MUST send an=
 Advertise message to the client as described in section 11.2 of RFC 3633.&=
quot;<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] This sentence is wh=
at I was looking for.</span></i></b><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">6.=C2=A0 =C2=A0 =C2=A0 In section 3.2 solution last =
paragraph =E2=80=9CSHOULD try to provide=E2=80=9D and<br>
in the first paragraph =E2=80=9CSHOULD provide=E2=80=9D should be the same =
in both.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] Thanks for pointing that out, we&#39;ll =
change it to &quot;SHOULD provide&quot;.<u></u><u></u></p>
</div>
</span><div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-family:cali=
bri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK<u></u><u></u></span></i=
></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>=C2=A0<u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">7.=C2=A0 =C2=A0 =C2=A0 In section 3.4 =E2=80=9CIf th=
e client decided to use=C2=A0 the prefix provided<br>
by the server despite being longer than the=C2=A0 prefix-length hint=E2=80=
=9D yet I<br>
did not see in section 3.2 that the server can provide a longer<br>
prefix.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">&quot;If the requested prefix is not available in th=
e server&#39;s prefix pool, and the client also included a prefix-length hi=
nt in the same IA_PD option, then the server SHOULD try to provide a prefix=
 matching the prefix-length value, or the prefix
 with the shortest length possible which is closest to the prefix-length hi=
nt value.&quot;<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] I understood from 3=
.2 that it should provide a shorter length prefix =C2=A0closer to the reque=
st maybe =E2=80=9C</span></i></b>or the prefix with the closest
 possible length to the prefix-length hint value=E2=80=9D<span style=3D"fon=
t-size:11pt;font-family:calibri,sans-serif;color:rgb(31,73,125)"><u></u><u>=
</u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0</p></div></span></div></div></div></div></div=
></div></blockquote><div>[Tianxiang2] The original sentence was a bit confu=
sing, perhaps we could change it like this:</div><div><br></div><div>OLD:=
=C2=A0&quot;If the requested prefix is not available in the server&#39;s pr=
efix pool, and the client also included a prefix-length hint in the same IA=
_PD option, then the server SHOULD try to provide a prefix matching the pre=
fix-length value, or the prefix with the shortest length possible which is =
closest to the prefix-length hint value.&quot;</div><div><br></div><div>NEW=
:&quot;If the requested prefix is not available in the server&#39;s prefix =
pool, and the client also included a prefix-length hint in the same IA_PD o=
ption, then the server SHOULD provide a prefix matching the prefix-length h=
int, or a prefix which is length is shorter and as close as possible to the=
 prefix-length hint. If the server could not provide a prefix which length =
is shorter or equal to the prefix-length hint, the server SHOULD provide th=
e prefix which length is longer and as close as possible to the prefix-leng=
th hint.&quot;</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-6060726979536003119gmail-m_=
-6524802112207049246gmail-m_-4900649193753751102WordSection1"><div style=3D=
"border-top:none;border-right:none;border-bottom:none;border-left:1.5pt sol=
id blue;padding:0cm 0cm 0cm 4pt"><div><div><div><span class=3D"m_-606072697=
9536003119gmail-m_-6524802112207049246gmail-"><div><p class=3D"MsoNormal"><=
u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">8.=C2=A0 =C2=A0 =C2=A0 In section 3.5 solution the d=
ocument use =E2=80=9Cas close as possible=E2=80=9D and<br>
section 3.2 only talk about smaller.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2.=C2=A0<u></u><u></u></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] See above to point =
7</span></i></b><span style=3D"font-size:11pt;font-family:calibri,sans-seri=
f;color:rgb(31,73,125)"><u></u><u></u></span></p>
</div><span class=3D"m_-6060726979536003119gmail-m_-6524802112207049246gmai=
l-">
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal">9.=C2=A0 =C2=A0 =C2=A0In section 3.5 solution why of=
fer options 3 and 4. The draft<br>
says that option 3 will break client connections and 4 talks about =E2=80=
=9Ca<br>
short non-zero valid-lifetime=E2=80=9D which may cause the=C2=A0 client to =
lose<br>
connection if &quot;too short for the client&quot; since =E2=80=9Cshort=E2=
=80=9D is not an exact<br>
value=C2=A0<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] The idea was to list all the options, an=
d discuss their consequences. And the server could decide which option to u=
se depending on its policy.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"m_-6060726979536003119gmail-m_-65248021122070492=
46gmail-">
<p class=3D"MsoNormal">Option 3 avoids the complexity of handling multiple =
delegated prefixes, despite of breaking up all connections. Option 4 allows=
 to server to configure a valid-lifetime for the old prefix depending on ac=
tual requirements, rather than let
 the old prefix expire on its own.<span style=3D"color:rgb(31,73,125)"><u><=
/u><u></u></span></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11pt;font-fami=
ly:calibri,sans-serif;color:rgb(31,73,125)">[Roni Even] OK, still option 4 =
may have similar result to 3 since =E2=80=9Ca short non-zero=E2=80=9D may b=
e too short. Why not add a recommended value?<u></u><u></u></span></i></b><=
/p>
<p class=3D"MsoNormal">=C2=A0</p></div></div></div></div></div></div></div>=
</blockquote><div>[Tianxiang2] Agree, as this may vary for different servic=
es, we could change the text to say &quot;a specific valid-lifetime dependi=
ng on the actual requirement&quot;.=C2=A0</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div class=3D"m_-6=
060726979536003119gmail-m_-6524802112207049246gmail-m_-4900649193753751102W=
ordSection1"><div style=3D"border-top:none;border-right:none;border-bottom:=
none;border-left:1.5pt solid blue;padding:0cm 0cm 0cm 4pt"><div><div><div><=
div><p class=3D"MsoNormal"><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><br>
<br>
Nits/editorial comments:<br>
<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--001a1140a4621dc8a505477a049b--


From nobody Wed Feb  1 09:21:26 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A64791294C1; Wed,  1 Feb 2017 09:21:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: NomCom 2016-2017 Appointment (IAOC)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.41.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148596968464.19146.6026261990643791791.idtracker@ietfa.amsl.com>
Date: Wed, 01 Feb 2017 09:21:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/te9D3Dj-CR70H8A9pVl5cIOUAg4>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 17:21:24 -0000

The 2016-17 IETF Nominating Committee (Nomcom) is pleased to announce its
selection to serve on the IETF  Administrative Oversight Committee (IAOC)/
IETF Trust.

The Nomcom has selected Lou Berger for a second two year term on the 
IAOC. This  selection has been confirmed by the IESG in its role as the
confirming body for the Nomcom's IAOC selection.  

The members of the Nomcom thank many all of the members of the community 
who offered to serve on the IAOC. Additionally, our thanks go out to the 
many members of the community who have supported the Nomcom process.

Lucy Lynch
20160-2017 NomCom Chair


From nobody Wed Feb  1 09:53:03 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 123441294DD for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 09:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ogkgj9_UtwyS for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 09:52:59 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 BEF661294CF for <ietf@ietf.org>; Wed,  1 Feb 2017 09:52:58 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id t18so31159196wmt.0 for <ietf@ietf.org>; Wed, 01 Feb 2017 09:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:from:date:message-id:subject:to; bh=Dp1k30oAAxrUWD9fA8V6hR+AhrNuTwFbil30dRFgocg=; b=SvdHUmS0I1uPGg33bX/boqlNfj2VdBMpxe/vYHUYUoH+Mbs3bhjLTuvqO47Buv+dhG +rwc96Q1OUXKhKtTDEG7O+fkFegduU5LfQP7NxRjtdF3VHmn8WWGkIPJFd8Qp862yDIO dLnn4XB/CX51XNyG16xiIKOVAlgRebwG0UvkV4P+A+QUy+5yA+H6EMW7Ofi8mFxACMNW aUr+BenQA8H+DstBNZ0S2tNaqTADks1WpgorrytCvUVDPhom97Nx6f3AoqySQ8YJRtLp BHjqJoXXNAmk8coy5EW9P4Ui6Kw2acVNqTu0RIwRFcqyNfOn/6iqteBH64GoJuIl/e3Z B/sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=Dp1k30oAAxrUWD9fA8V6hR+AhrNuTwFbil30dRFgocg=; b=lDtqTGFtmwokB3/xcIXM6LmdIZlJRHpxAeBsBIcU6SOd3NQvuwR8826xMX01cr13kd 13oeIkts3xp5ktkEawoQCpOSpEoVdFp6iIijpxO0TEnvrPF2P9hkKPfLf29nGxnqptS4 cQWDcoQu9Noq1p26lJH812Xtn6dCMRjJKRUxVhWH9w+hDagN6jpUpEUa4ImEdCyXLOhb EIgmofjI+vDFazXcrbfuTH4+6J+6qjXFTJszFVC87RAk6KjYeNyBb3haYYYgDoQMhzTb RL9OZfU4A49MshfngSOicFZCt64ObK6vTQJBoX4Z3Os9SkxgM19W+JaFUnXuom6wqI8l Vx4Q==
X-Gm-Message-State: AIkVDXJeSIwokaggPqsrnVxPd1CbkbldCSEFfvww077WAyNJDhXQJt3gC0OWFORZnvdIoZSD9VqjXEq4PoH6eA==
X-Received: by 10.223.155.197 with SMTP id e5mr3671583wrc.133.1485971576853; Wed, 01 Feb 2017 09:52:56 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.194.221.6 with HTTP; Wed, 1 Feb 2017 09:52:56 -0800 (PST)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 1 Feb 2017 12:52:56 -0500
X-Google-Sender-Auth: tTXsCqn4MISox5RlQQC3gU4Se-Q
Message-ID: <CAMm+LwhYoEF=hsh-XuEWfU4eRgWrujzNgD2cdU3BGp8-YUucPQ@mail.gmail.com>
Subject: How to make the Internet secure
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1b4e60fc220a05477bb7b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PD6XmVtPW1vcSMKazOBcUofSYqw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 17:53:02 -0000

--94eb2c1b4e60fc220a05477bb7b1
Content-Type: text/plain; charset=UTF-8

One of the big problems I have found in trying to argue for ways we can
improve Internet security is that there are two camps. The incrementalists
will only look at solutions that provide an improvement on the status qujo
in one area and the perfectionists insist that any solution that does not
solve every possible problem isn't worth considering.

How about we do both?

Also to save time:

* Yes, I understand the deployment problem very well, I worked with the guy
who solved the network hypertext deployment problem after 20 years of
people failing.
* Yes, everything is end to end secure,
* Yes the transport is also secure to prevent metadata attacks.
* Yes it works with OpenPGP
* Yes it works with S/MIME
* Yes you can use it with SMTP/IMAP/POP
* Yes you can use it with Jabber
* No, you do not have to use a CA
* Yes, you may use a CA where a CA adds value
* Yes, I have considered the lock in problem
* Yes, you can bolt in your own trust model
* REST/HTTPS/JSON.
* AES/RSA/DiffieHelman, moving to CurveX for production.
* Yes it is unencumbered, apart from one part which will unlock this year.
* Yes I have a strategy for QRC
* No, it is not a walled garden
* Yes, you can adapt the system to use escrow cryptography but not without
the parties knowing so this is a frontdoor, not a backdoor.
* My employer sells endpoint protection systems, the Mesh is not a
substitute for endpoint protection, thank you for your interest.
* Reference code runs on Windows, Linux and should run on OSX. It is all
MIT license, so are the protocol compiler tools.

* Yes, it is easy to use. In fact it is exactly as easy to use as the
existing protocols because the user doesn't need to know that they are
doing security
* Yes it is easy to configure.
* Yes, I need help, a lot of help

OK so how is this possible?

First observation is that we now have several protocols that provide users
with end to end security that are really easy to use. The only real problem
I have with those systems is that they operate inside walled gardens. They
are not going to be a replacement for email.

Second is that public key cryptography is now cheap in terms of both cost
and performance. We couldn't do very interesting crypto in the 90s because
machines bogged


There are three contributions made by the Mathematical Mesh:

1) An infrastructure for managing and using client keypairs.

Adding cryptography to a protocol is actually quite easy when both parties
have public keypairs. So if we have an infrastructure that allows a user to
'glue' all their devices together into a personal mesh such that they all
have keypairs provisioned for each cryptographic purpose they might need
them for, cryptography becomes really easy for the user.

2) Extend a direct trust model into the DNS

We all know about TOR and onion routing. Well what if I could have an email
address that included my OpenPGP fingerprint? Well we can. Just use the
xx-- DNS label prefix to mark the fingerprint as not an ICANN DNS labnel
and we can make the fingerprint the TLD:

alice@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE

This means, 'only send mail to this address in compliance with a policy
signed under the fingerprint MBTVK...' Said policy could be an OpenPGP key
or it could be a Mesh mail profile.

3) Use of Proxy Re-Encryption (Recryption)

HTTPS provides end to end encryption between the user's client and the web
site serving the content. Using Proxy Re-Encryption we can provide end to
end encryption between the content creator and the user's client. This is
the part of the system that will be locked until late this year, (not that
I am sure the patent is valid, why bother checking when it expires)

We all know that two key cryptography is better than one. It is better
because encryption and decryption are different functions and using
separate keys for separate functions allows these to be done by different
parties. Recryption is three key cryptography and it is better than two key
for the same exact reason.

Using recryption allows us to develop protocols in which Alice is able to
publish a single encryption key but read her email on three different
devices, each of which has a separate decryption key so that she can
mitigate the risk if one of the devices is lost.


Job one is making it easy to manage client side keys.

Once we have that infrastructure, all else becomes straightforward. My
original goal with the Mesh was to make it easy to configure S/MIME and
OpenPGP. David Clark asked me to add SSH which I immediately realized could
be the killer app because the big problem with configuring SSH is that if
you do it to a machine at a remote site, 1000 miles away and you screw up,
someone has to get on a plane to fix it.

However, any infrastructure that allows mail application to say 'here are
the encryption keys to use to send mail to me and when to use them' can
also say 'I accept JSON format nextgen mail'. So this is an infrastructure
that allows us to lock down the legacy email systems as best as can be
managed but also eliminates the biggest barrier to deployment of a
successor system.


I am looking for help to make this happen.

http://prismproof.org/

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">One=
 of the big problems I have found in trying to argue for ways we can improv=
e Internet security is that there are two camps. The incrementalists will o=
nly look at solutions that provide an improvement on the status qujo in one=
 area and the perfectionists insist that any solution that does not solve e=
very possible problem isn&#39;t worth considering.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">How about we do both?</div><div class=3D"gmail_de=
fault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" sty=
le=3D"font-size:small">Also to save time:</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">* Yes, I understand the deployment problem very well, I wo=
rked with the guy who solved the network hypertext deployment problem after=
 20 years of people failing.=C2=A0</div><div class=3D"gmail_default" style=
=3D"font-size:small">* Yes, everything is end to end secure,=C2=A0</div><di=
v class=3D"gmail_default" style=3D"font-size:small">* Yes the transport is =
also secure to prevent metadata attacks.</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes it works with OpenPGP</div><div class=3D"gm=
ail_default" style=3D"font-size:small">* Yes it works with S/MIME</div><div=
 class=3D"gmail_default" style=3D"font-size:small">* Yes you can use it wit=
h SMTP/IMAP/POP</div><div class=3D"gmail_default" style=3D"font-size:small"=
>* Yes you can use it with Jabber</div><div class=3D"gmail_default" style=
=3D"font-size:small">* No, you do not have to use a CA</div><div class=3D"g=
mail_default" style=3D"font-size:small">* Yes, you may use a CA where a CA =
adds value</div><div class=3D"gmail_default" style=3D"font-size:small">* Ye=
s, I have considered the lock in problem</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes, you can bolt in your own trust model</div>=
<div class=3D"gmail_default" style=3D"font-size:small">* REST/HTTPS/JSON.</=
div><div class=3D"gmail_default" style=3D"font-size:small">* AES/RSA/Diffie=
Helman, moving to CurveX for production.</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes it is unencumbered, apart from one part whi=
ch will unlock this year.</div><div class=3D"gmail_default" style=3D"font-s=
ize:small">* Yes I have a strategy for QRC</div><div class=3D"gmail_default=
" style=3D"font-size:small">* No, it is not a walled garden</div><div class=
=3D"gmail_default" style=3D"font-size:small">* Yes, you can adapt the syste=
m to use escrow cryptography but not without the parties knowing so this is=
 a frontdoor, not a backdoor.</div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">* My employer sells endpoint protection systems, the Mesh is=
 not a substitute for endpoint protection, thank you for your interest.</di=
v><div class=3D"gmail_default" style=3D"font-size:small">* Reference code r=
uns on Windows, Linux and should run on OSX. It is all MIT license, so are =
the protocol compiler tools.</div><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">* Yes, it is easy to use. In fact it is exactly as easy to use as the e=
xisting protocols because the user doesn&#39;t need to know that they are d=
oing security</div><div class=3D"gmail_default" style=3D"font-size:small">*=
 Yes it is easy to configure.</div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">* Yes, I need help, a lot of help</div><div class=3D"gmail_d=
efault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-size:small">OK so how is this possible?</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small">First observation is that we now have several pr=
otocols that provide users with end to end security that are really easy to=
 use. The only real problem I have with those systems is that they operate =
inside walled gardens. They are not going to be a replacement for email.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">Second is that public key c=
ryptography is now cheap in terms of both cost and performance. We couldn&#=
39;t do very interesting crypto in the 90s because machines bogged</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">There are three contributions made by the M=
athematical Mesh:</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">1) An i=
nfrastructure for managing and using client keypairs.</div><div class=3D"gm=
ail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-size:small">Adding cryptography to a protocol is actually =
quite easy when both parties have public keypairs. So if we have an infrast=
ructure that allows a user to &#39;glue&#39; all their devices together int=
o a personal mesh such that they all have keypairs provisioned for each cry=
ptographic purpose they might need them for, cryptography becomes really ea=
sy for the user.</div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small">2) Exten=
d a direct trust model into the DNS</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">We all know about TOR and onion routing. Well what if I could ha=
ve an email address that included my OpenPGP fingerprint? Well we can. Just=
 use the xx-- DNS label prefix to mark the fingerprint as not an ICANN DNS =
labnel and we can make the fingerprint the TLD:</div><div class=3D"gmail_de=
fault" style=3D"font-size:small"><br></div><div class=3D"gmail_default">ali=
ce@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE<br></div><div class=
=3D"gmail_default"><br></div><div class=3D"gmail_default">This means, &#39;=
only send mail to this address in compliance with a policy signed under the=
 fingerprint MBTVK...&#39; Said policy could be an OpenPGP key or it could =
be a Mesh mail profile.</div><div class=3D"gmail_default"><br></div><div cl=
ass=3D"gmail_default">3) Use of Proxy Re-Encryption (Recryption)</div><div =
class=3D"gmail_default"><br></div><div class=3D"gmail_default">HTTPS provid=
es end to end encryption between the user&#39;s client and the web site ser=
ving the content. Using Proxy Re-Encryption we can provide end to end encry=
ption between the content creator and the user&#39;s client. This is the pa=
rt of the system that will be locked until late this year, (not that I am s=
ure the patent is valid, why bother checking when it expires)</div><div cla=
ss=3D"gmail_default"><br></div><div class=3D"gmail_default">We all know tha=
t two key cryptography is better than one. It is better because encryption =
and decryption are different functions and using separate keys for separate=
 functions allows these to be done by different parties. Recryption is thre=
e key cryptography and it is better than two key for the same exact reason.=
</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">U=
sing recryption allows us to develop protocols in which Alice is able to pu=
blish a single encryption key but read her email on three different devices=
, each of which has a separate decryption key so that she can mitigate the =
risk if one of the devices is lost.</div><div class=3D"gmail_default"><br><=
/div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">Jo=
b one is making it easy to manage client side keys.=C2=A0</div><div class=
=3D"gmail_default"><br></div><div class=3D"gmail_default">Once we have that=
 infrastructure, all else becomes straightforward. My original goal with th=
e Mesh was to make it easy to configure S/MIME and OpenPGP. David Clark ask=
ed me to add SSH which I immediately realized could be the killer app becau=
se the big problem with configuring SSH is that if you do it to a machine a=
t a remote site, 1000 miles away and you screw up, someone has to get on a =
plane to fix it.</div><div class=3D"gmail_default"><br></div><div class=3D"=
gmail_default">However, any infrastructure that allows mail application to =
say &#39;here are the encryption keys to use to send mail to me and when to=
 use them&#39; can also say &#39;I accept JSON format nextgen mail&#39;. So=
 this is an infrastructure that allows us to lock down the legacy email sys=
tems as best as can be managed but also eliminates the biggest barrier to d=
eployment of a successor system.</div><div class=3D"gmail_default"><br></di=
v><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">I am =
looking for help to make this happen.</div><div class=3D"gmail_default"><br=
></div><div class=3D"gmail_default"><a href=3D"http://prismproof.org/">http=
://prismproof.org/</a></div><div class=3D"gmail_default"><br></div></div>

--94eb2c1b4e60fc220a05477bb7b1--


From nobody Wed Feb  1 10:10:34 2017
Return-Path: <ycompanys@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E1231294EF for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:10:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vnqcw4E2pxVQ for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:10:31 -0800 (PST)
Received: from mail-wm0-x235.google.com (mail-wm0-x235.google.com [IPv6:2a00:1450:400c:c09::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 EFBD71294D2 for <ietf@ietf.org>; Wed,  1 Feb 2017 10:10:30 -0800 (PST)
Received: by mail-wm0-x235.google.com with SMTP id t18so31289741wmt.0 for <ietf@ietf.org>; Wed, 01 Feb 2017 10:10:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:from:date:message-id:subject:to; bh=KTDG8OwEYb+5AE8s9e3G8WONKRrGS8uxfR1HTi+tBcg=; b=Kf4JX3+ABjZ8YRjSQG2yNbhL7l1HUuQXbdbYJZf+WXKvtFrmlcTOlJbpaSvAcMySe+ aJBsx0ez97sZ3FFidIJ98VyQUM046pwT5q3u6FOJ5y0ATG9vt5mT6WGfyQzecGSdDZ50 rEz1c2wlHwx1aplnn5WSgo5+vb+6MBN1zd+yIdbx5MX7XJYQThmH3e4OyPXHUarV8dKl XlMRes0CzXsq8kpu9KWv5PqCul4eI+QuOaUMjCPeU07drXascB5r8RTwfe7/M+RrZDwY nmZpaxJjfhao/f20Q/HcTavJf5gjDzpneoMk0btgC9DlMIRPGkUrQE1ljji2hpPJS1rq vJZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=KTDG8OwEYb+5AE8s9e3G8WONKRrGS8uxfR1HTi+tBcg=; b=BeIOtOEE1y7Qv35mxJ6EqCgQYECrPYVhQ9GyGWXaAfhM/hvTh2JxVQQ1Fg8juCDjhI ib4nznLio9EdU+85D7PPm/nmItzcY9OlPU44Z9fFvv96J7xQsWBrmwy0OGTP5Syz+UV8 8ASA50ifFJqY56A1L4znJ2dhx9xoVgkX4JThP55LqIuyLRhEvUhZ4Nnby1LLhnrqNqla ksY7Zqcn7u95e2NVFuGSuyGb0wP+27ZTpgd56h1xo0xwG0fYNJH4Je3zjkaRbn30a9FD KDsk0DgIwa/KACGJsSNdBO9RVmnWy/CGTzKp9wxWe2AXzrHhYW5Vp8HA6MT2TWBJTzBt NjZw==
X-Gm-Message-State: AIkVDXIWKS4EhUMCjNsB+M1loX9f+9i9XCtb5MNP1fso24LlMHfcf4t8FA00WjtQ0AcDv7YSd7juEpJ5EP/CVA==
X-Received: by 10.223.134.253 with SMTP id 58mr4464746wry.46.1485972629002; Wed, 01 Feb 2017 10:10:29 -0800 (PST)
MIME-Version: 1.0
Sender: ycompanys@gmail.com
Received: by 10.28.33.4 with HTTP; Wed, 1 Feb 2017 10:10:08 -0800 (PST)
From: Yosem Companys <companys@stanford.edu>
Date: Wed, 1 Feb 2017 10:10:08 -0800
X-Google-Sender-Auth: KMxdJSo9lJz-QtAh-idEwNUroOQ
Message-ID: <CANhci9Ezow-owWX9sXkvaFWbBKpN5CSybeKBOC78V48-cc+wUg@mail.gmail.com>
Subject: Stanford Liberationtech
To: "To: IETF Discussion Mailing List" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1147d3a2b2a2de05477bf6ce
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kxCd0OKNariqwb74opzjCj4eoWc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 18:10:33 -0000

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

We are Stanford Liberationtech. We are housed in the Freeman Spogli
Institute in the Center for Democracy, Development, and the Rule of Law,
and our goal is to design technologies that offer cybersecurity and privacy
to people so that they may foster democracy, development, freedom, and
other public goods.

Our home page is here: http://cddrl.fsi.stanford.edu/libtech.

To sign up to our 4K-strong mailing list, click here:
https://mailman.stanford.edu/mailman/listinfo/liberationtech.

We have also curated a list of Liberationtech content at
https://twitter.com/Liberationtech.

If you prefer to read our list as a newspaper, you could always check our
Paper.li account: http://paper.li/Liberationtech#/

Our Liberationtech blog has been dead for a while, but we are working on
reviving it. If you are interested in helping out, please let us know.

We also have a series of mailing lists on topics related to Liberationtech.
The most important lists are the following:

   - Events: https://mailman.stanford.edu/mailman/listinfo/libera
   tiontech-events
   - Jobs: https://mailman.stanford.edu/mailman/listinfo/liberationtech-jobs
   - CfP: https://mailman.stanford.edu/mailman/listinfo/liberationtech-cfp

For the aforementioned lists, we try to compile a list of all events, job
opportunities, and call for papers related to Liberationtech from all over
the world.

It's not a comprehensive list, so your assistance would be helpful. If you
hear of a job, event, or cfp that would be of benefit to Liberationtech
subscribers, please let us know.

Finally, we want to take Liberationtech to the next level. What that means,
we don't know. But the world has changed a lot since we started back in
2008: Censorship is on the rise. Internet freedom is on the decline. And we
have become much more of a community of hackers and cybersecurity
professionals who seek to protect vulnerable communities around the world.

So if you have ideas of projects you would like to see us take on, please
let us know. We want the Liberationtech community to drive the process. Any
idea is welcome. Dream big or small. Just let us know how you think we can
best help.

Thanks,
Yosem
(One of the moderators)

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"=
gmail_quote"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><=
div class=3D"gmail_quote"><div class=3D"m_-2463210612001664209m_-8816761233=
13942326m_-7759726931774966050HOEnZb"><div class=3D"m_-2463210612001664209m=
_-881676123313942326m_-7759726931774966050h5"><div dir=3D"ltr"><div class=
=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"lt=
r"><div>We are Stanford Liberationtech. We are housed in the Freeman Spogli=
 Institute in the Center for Democracy, Development, and the Rule of Law, a=
nd our goal is to design technologies that offer cybersecurity and privacy =
to people so that they may foster democracy, development, freedom, and othe=
r public goods.</div><span><span><div><br></div><div>Our home page is here:=
=C2=A0<a href=3D"http://cddrl.fsi.stanford.edu/libtech" target=3D"_blank">h=
ttp://cddrl.fsi.stanfor<wbr>d.edu/libtech</a>.=C2=A0</div><div><br></div><d=
iv>To sign up to our 4K-strong mailing list, click here:=C2=A0<a href=3D"ht=
tps://mailman.stanford.edu/mailman/listinfo/liberationtech" target=3D"_blan=
k">https://mailman.stanford<wbr>.edu/mailman/listinfo/liberati<wbr>ontech</=
a>.</div><div><br></div>We have also curated a list of Liberationtech conte=
nt at <a href=3D"https://twitter.com/Liberationtech" target=3D"_blank">http=
s://twitter.com/Liberation<wbr>tech</a>.<br><br>If you prefer to read our l=
ist as a newspaper, you could always check our Paper.li account: <a href=3D=
"http://paper.li/Liberationtech#/" target=3D"_blank">http://paper.li/Libera=
tiontech<wbr>#/</a><div><br></div><div>Our Liberationtech blog has been dea=
d for a while, but we are working on reviving it. If you are interested in =
helping out, please let us know.</div><div><br></div><div>We also have a se=
ries of mailing lists on topics related to Liberationtech. The most importa=
nt lists are the following:</div><div><ul><li>Events:=C2=A0<a href=3D"https=
://mailman.stanford.edu/mailman/listinfo/liberationtech-events" target=3D"_=
blank">https://mailman.stanfo<wbr>rd.edu/mailman/listinfo/libera<wbr>tionte=
ch-events</a></li><li>Jobs:=C2=A0<a href=3D"https://mailman.stanford.edu/ma=
ilman/listinfo/liberationtech-jobs" target=3D"_blank">https://mailman.stanf=
ord<wbr>.edu/mailman/listinfo/liberati<wbr>ontech-jobs</a></li><li>CfP:=C2=
=A0<a href=3D"https://mailman.stanford.edu/mailman/listinfo/liberationtech-=
cfp" target=3D"_blank">https://mailman.stanford.<wbr>edu/mailman/listinfo/l=
iberatio<wbr>ntech-cfp</a></li></ul><div>For the aforementioned lists, we t=
ry to compile a list of all events, job opportunities, and call for papers =
related to Liberationtech from all over the world.=C2=A0</div><div><br></di=
v><div>It&#39;s not a comprehensive list, so your assistance would be helpf=
ul. If you hear of a job, event, or cfp that would be of benefit to Liberat=
iontech subscribers, please let us know.</div></div><div><br></div><div>Fin=
ally, we want to take Liberationtech to the next level. What that means, we=
 don&#39;t know. But the world has changed a lot since we started back in 2=
008: Censorship is on the rise. Internet freedom is on the decline. And we =
have become much more of a community of hackers and cybersecurity professio=
nals who seek to protect vulnerable communities around the world.</div><div=
><br></div><div>So if you have ideas of projects you would like to see us t=
ake on, please let us know. We want the Liberationtech community to drive t=
he process. Any idea is welcome. Dream big or small. Just let us know how y=
ou think we can best help.</div><div><br></div><div>Thanks,</div><div>Yosem=
</div><div>(One of the moderators)</div></span></span></div></div></div></d=
iv></div></div></div></div></div></div></div></div></div></div></div>

--001a1147d3a2b2a2de05477bf6ce--


From nobody Wed Feb  1 10:22:03 2017
Return-Path: <prvs=1205c15e24=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36E13129529 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cd870pT2a-Go for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:21:58 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39798128AC9 for <ietf@ietf.org>; Wed,  1 Feb 2017 10:21:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1485973315; x=1486578115; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=6Z7foZtR5+0TWaQz+DQs0iR5I ItLPLQih1BZp48rNSE=; b=Of+O9eRHucwI9E20qdU021XMI/nlXAWv3yvqDB0+g 16C8K440QhTPJs2OOXaccqX8Z2eRRGQKc66nCQxHaiQ83K4YdhyD+VqKJ1SfK9rc tLHQhPf11ItPYHmnH6gXilUMQbyXi8UWNBCkWKAuPvZ1C4O50a2unOwkoAqAnoVU ls=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=E1xBA5pOTzEvA3ASB/Aj0HtwJ7ybLm6DXbVLkCz07Vfeyw28i0Z6G7fuQ68Q G+qVMUfdOdmjwfRAY+hih03pXMJc+rRjfw8gfJ9cvgXwiIrVR9JtW2t+9 YAv4opYu3ieNUgsNNeXgfw0gvTKBfKznRO1sRGvTUAw0YXLq5GnidM=;
X-MDAV-Processed: mail.consulintel.es, Wed, 01 Feb 2017 19:21:55 +0100
X-Spam-Processed: mail.consulintel.es, Wed, 01 Feb 2017 19:21:51 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005359569.msg for <ietf@ietf.org>; Wed, 01 Feb 2017 19:21:51 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170201:md50005359569::DI06nOMPXDE/h8r1:000047G0
X-Return-Path: prvs=1205c15e24=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Wed, 01 Feb 2017 19:21:49 +0100
Subject: Re: Stanford Liberationtech
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <companys@stanford.edu>, "To: IETF Discussion Mailing List" <ietf@ietf.org>
Message-ID: <E01A4D8F-5D0F-486A-906B-D032CCEB7018@consulintel.es>
Thread-Topic: Stanford Liberationtech
References: <CANhci9Ezow-owWX9sXkvaFWbBKpN5CSybeKBOC78V48-cc+wUg@mail.gmail.com>
In-Reply-To: <CANhci9Ezow-owWX9sXkvaFWbBKpN5CSybeKBOC78V48-cc+wUg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8i3vS4ezqQ_eo_-6lkNLSoM6eWI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 18:22:01 -0000

Speaking as Sergeant at arms.

According to RFC3005, this posting is inappropriate for the IETF mail explo=
der:

Inappropriate postings include:
=E2=80=A6
    - Announcements of conferences, events, or activities that are not
      sponsored or endorsed by the Internet Society or IETF.

So please, make sure to avoid further announcements of this kind in this li=
st.

Regards,
Jordi


-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Yosem Companys <companys@stan=
ford.edu>
Responder a: <companys@stanford.edu>
Fecha: mi=C3=A9rcoles, 1 de febrero de 2017, 19:10
Para: "To: IETF Discussion Mailing List" <ietf@ietf.org>
Asunto: Stanford Liberationtech

    We are Stanford Liberationtech. We are housed in the Freeman Spogli Ins=
titute in the Center for Democracy, Development, and the Rule of Law, and o=
ur goal is to design technologies that offer cybersecurity and privacy to p=
eople so that they may foster democracy, development, freedom, and other pu=
blic goods.
   =20
    Our home page is here: http://cddrl.fsi.stanford.edu/libtech.=20
   =20
    To sign up to our 4K-strong mailing list, click here: https://mailman.s=
tanford.edu/mailman/listinfo/liberationtech.
   =20
    We have also curated a list of Liberationtech content at https://twitte=
r.com/Liberationtech.
   =20
    If you prefer to read our list as a newspaper, you could always check o=
ur Paper.li account: http://paper.li/Liberationtech#/
    Our Liberationtech blog has been dead for a while, but we are working o=
n reviving it. If you are interested in helping out, please let us know.
   =20
    We also have a series of mailing lists on topics related to Liberationt=
ech. The most important lists are the following:
   =20
    * Events: https://mailman.stanford.edu/mailman/listinfo/liberationtech-=
events
    * Jobs: https://mailman.stanford.edu/mailman/listinfo/liberationtech-jo=
bs
    * CfP: https://mailman.stanford.edu/mailman/listinfo/liberationtech-cfp
   =20
    For the aforementioned lists, we try to compile a list of all events, j=
ob opportunities, and call for papers related to Liberationtech from all ov=
er the world.=20
   =20
    It's not a comprehensive list, so your assistance would be helpful. If =
you hear of a job, event, or cfp that would be of benefit to Liberationtech=
 subscribers, please let us know.
   =20
   =20
    Finally, we want to take Liberationtech to the next level. What that me=
ans, we don't know. But the world has changed a lot since we started back i=
n 2008: Censorship is on the rise. Internet freedom is on the decline. And =
we have become much more of a community of hackers and cybersecurity profes=
sionals who seek to protect vulnerable communities around the world.
   =20
    So if you have ideas of projects you would like to see us take on, plea=
se let us know. We want the Liberationtech community to drive the process. =
Any idea is welcome. Dream big or small. Just let us know how you think we =
can best help.
   =20
    Thanks,
    Yosem
    (One of the moderators)
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Wed Feb  1 10:27:58 2017
Return-Path: <ycompanys@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4966129973 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:27:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ddB91YQDg3er for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 10:27:54 -0800 (PST)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 493E4129884 for <ietf@ietf.org>; Wed,  1 Feb 2017 10:27:54 -0800 (PST)
Received: by mail-wm0-x244.google.com with SMTP id r18so7389967wmd.3 for <ietf@ietf.org>; Wed, 01 Feb 2017 10:27:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ZKFCMUlEwlju2YH0DfI/mIsk2fSgKYbpSEHj1JfbymY=; b=ZAemHtHzBv00FI57CIGgWdUni+FQd48TkoXg+rj3IrnDRJ4rjcsP2IUzlIeIRnwQ+S fQcmtKWsn5VUrxCCYE1r0yV4ttAZj8RTNQTHazcSQnXfcQKYF8clWaVjkSCatwAPgz6C Uzeawrme63cRLzr2SCskaLCjjyAcSApZLZlAhJEGExv5jXlSYljLIdatE+FgnBW/MB2p X0a5J8rfEC0iTcEu5NY4N24ljS0WOrbg/INkWgsY8ns20IyWK3xBf5tA8g+0v2bnjlOX HiV47OPuMIsfss1NFIKfqQcklUtFFDsZG1N05SFqqtpOHy1U7qXDr8HAMSB3jHTMe0Rd FDRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ZKFCMUlEwlju2YH0DfI/mIsk2fSgKYbpSEHj1JfbymY=; b=FLN6eDYi+bDJLkwFgc3E3DJIQZWbnQLVRLzjgUPqPKRNF8ywTE5BrOsRxC8MOlS1Ok IiGuaNboT2wcxpQYsb21tcEN/hkkkEg11oEmZZ74ncorsUvw7kmlEidOtOS34qrbIeAN QjczQBuKi0ud1jKSD5eDQZjnrKP6cmhr0zsnETnHCopvfc4AQhH3FHitReF4OBePSdrM m/AbreFIUf69hpf2GVKyctIbpF563JX20sJG/8udgm75Qcz0mm+Nuj3jdHZmDJS6Uj6B 0CoHmKcnPHForpGdC4UExaeynFRUcWrS1x9Z3aTZFMlSkkK8guFPA4mZpPiqSJMi4VTh qgew==
X-Gm-Message-State: AIkVDXJGkSphERUMHPZJ8E0+XxgRgjHqG/yLLf2jwvX3+xD0lZMxUcWZ1drKhEpU9M3Ffgd44JA9xYr4gV63Yw==
X-Received: by 10.28.229.73 with SMTP id c70mr23256538wmh.82.1485973672780; Wed, 01 Feb 2017 10:27:52 -0800 (PST)
MIME-Version: 1.0
Sender: ycompanys@gmail.com
Received: by 10.28.33.4 with HTTP; Wed, 1 Feb 2017 10:27:31 -0800 (PST)
In-Reply-To: <E01A4D8F-5D0F-486A-906B-D032CCEB7018@consulintel.es>
References: <CANhci9Ezow-owWX9sXkvaFWbBKpN5CSybeKBOC78V48-cc+wUg@mail.gmail.com> <E01A4D8F-5D0F-486A-906B-D032CCEB7018@consulintel.es>
From: Yosem Companys <companys@stanford.edu>
Date: Wed, 1 Feb 2017 10:27:31 -0800
X-Google-Sender-Auth: x91Hw5NG3EbXmjJuUs-ONKFtCTw
Message-ID: <CANhci9G4kLyLtMQOgS1fJyvzTy4GkHBBuoLuC0yLJEpH8E1LBA@mail.gmail.com>
Subject: Re: Stanford Liberationtech
To: jordi.palet@consulintel.es
Content-Type: multipart/alternative; boundary=001a1145b1fee96c2205477c3446
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iXBviAbx2bBO167y0DbDuljHB0o>
Cc: "To: IETF Discussion Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 18:27:57 -0000

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

I apologize. I was not aware of the posting rules for the list.

Yosem

On Wed, Feb 1, 2017 at 10:21 AM, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> Speaking as Sergeant at arms.
>
> According to RFC3005, this posting is inappropriate for the IETF mail
> exploder:
>
> Inappropriate postings include:
> =E2=80=A6
>     - Announcements of conferences, events, or activities that are not
>       sponsored or endorsed by the Internet Society or IETF.
>
> So please, make sure to avoid further announcements of this kind in this
> list.
>
> Regards,
> Jordi
>
>
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de Yosem Companys <
> companys@stanford.edu>
> Responder a: <companys@stanford.edu>
> Fecha: mi=C3=A9rcoles, 1 de febrero de 2017, 19:10
> Para: "To: IETF Discussion Mailing List" <ietf@ietf.org>
> Asunto: Stanford Liberationtech
>
>     We are Stanford Liberationtech. We are housed in the Freeman Spogli
> Institute in the Center for Democracy, Development, and the Rule of Law,
> and our goal is to design technologies that offer cybersecurity and priva=
cy
> to people so that they may foster democracy, development, freedom, and
> other public goods.
>
>     Our home page is here: http://cddrl.fsi.stanford.edu/libtech.
>
>     To sign up to our 4K-strong mailing list, click here:
> https://mailman.stanford.edu/mailman/listinfo/liberationtech.
>
>     We have also curated a list of Liberationtech content at
> https://twitter.com/Liberationtech.
>
>     If you prefer to read our list as a newspaper, you could always check
> our Paper.li account: http://paper.li/Liberationtech#/
>     Our Liberationtech blog has been dead for a while, but we are working
> on reviving it. If you are interested in helping out, please let us know.
>
>     We also have a series of mailing lists on topics related to
> Liberationtech. The most important lists are the following:
>
>     * Events: https://mailman.stanford.edu/mailman/listinfo/
> liberationtech-events
>     * Jobs: https://mailman.stanford.edu/mailman/listinfo/
> liberationtech-jobs
>     * CfP: https://mailman.stanford.edu/mailman/listinfo/
> liberationtech-cfp
>
>     For the aforementioned lists, we try to compile a list of all events,
> job opportunities, and call for papers related to Liberationtech from all
> over the world.
>
>     It's not a comprehensive list, so your assistance would be helpful. I=
f
> you hear of a job, event, or cfp that would be of benefit to Liberationte=
ch
> subscribers, please let us know.
>
>
>     Finally, we want to take Liberationtech to the next level. What that
> means, we don't know. But the world has changed a lot since we started ba=
ck
> in 2008: Censorship is on the rise. Internet freedom is on the decline. A=
nd
> we have become much more of a community of hackers and cybersecurity
> professionals who seek to protect vulnerable communities around the world=
.
>
>     So if you have ideas of projects you would like to see us take on,
> please let us know. We want the Liberationtech community to drive the
> process. Any idea is welcome. Dream big or small. Just let us know how yo=
u
> think we can best help.
>
>     Thanks,
>     Yosem
>     (One of the moderators)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>
>

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

<div dir=3D"ltr">I apologize. I was not aware of the posting rules for the =
list.<div><br></div><div>Yosem</div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Wed, Feb 1, 2017 at 10:21 AM, JORDI PALET MARTI=
NEZ <span dir=3D"ltr">&lt;<a href=3D"mailto:jordi.palet@consulintel.es" tar=
get=3D"_blank">jordi.palet@consulintel.es</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Speaking as Sergeant at arms.<br>
<br>
According to RFC3005, this posting is inappropriate for the IETF mail explo=
der:<br>
<br>
Inappropriate postings include:<br>
=E2=80=A6<br>
=C2=A0 =C2=A0 - Announcements of conferences, events, or activities that ar=
e not<br>
=C2=A0 =C2=A0 =C2=A0 sponsored or endorsed by the Internet Society or IETF.=
<br>
<br>
So please, make sure to avoid further announcements of this kind in this li=
st.<br>
<br>
Regards,<br>
Jordi<br>
<br>
<br>
-----Mensaje original-----<br>
De: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org=
</a>&gt; en nombre de Yosem Companys &lt;<a href=3D"mailto:companys@stanfor=
d.edu">companys@stanford.edu</a>&gt;<br>
Responder a: &lt;<a href=3D"mailto:companys@stanford.edu">companys@stanford=
.edu</a>&gt;<br>
Fecha: mi=C3=A9rcoles, 1 de febrero de 2017, 19:10<br>
Para: &quot;To: IETF Discussion Mailing List&quot; &lt;<a href=3D"mailto:ie=
tf@ietf.org">ietf@ietf.org</a>&gt;<br>
Asunto: Stanford Liberationtech<br>
<span class=3D""><br>
=C2=A0 =C2=A0 We are Stanford Liberationtech. We are housed in the Freeman =
Spogli Institute in the Center for Democracy, Development, and the Rule of =
Law, and our goal is to design technologies that offer cybersecurity and pr=
ivacy to people so that they may foster democracy, development, freedom, an=
d other public goods.<br>
<br>
=C2=A0 =C2=A0 Our home page is here: <a href=3D"http://cddrl.fsi.stanford.e=
du/libtech" rel=3D"noreferrer" target=3D"_blank">http://cddrl.fsi.stanford.=
edu/<wbr>libtech</a>.<br>
<br>
=C2=A0 =C2=A0 To sign up to our 4K-strong mailing list, click here: <a href=
=3D"https://mailman.stanford.edu/mailman/listinfo/liberationtech" rel=3D"no=
referrer" target=3D"_blank">https://mailman.stanford.edu/<wbr>mailman/listi=
nfo/<wbr>liberationtech</a>.<br>
<br>
=C2=A0 =C2=A0 We have also curated a list of Liberationtech content at <a h=
ref=3D"https://twitter.com/Liberationtech" rel=3D"noreferrer" target=3D"_bl=
ank">https://twitter.com/<wbr>Liberationtech</a>.<br>
<br>
=C2=A0 =C2=A0 If you prefer to read our list as a newspaper, you could alwa=
ys check our Paper.li account: <a href=3D"http://paper.li/Liberationtech#/"=
 rel=3D"noreferrer" target=3D"_blank">http://paper.li/<wbr>Liberationtech#/=
</a><br>
=C2=A0 =C2=A0 Our Liberationtech blog has been dead for a while, but we are=
 working on reviving it. If you are interested in helping out, please let u=
s know.<br>
<br>
=C2=A0 =C2=A0 We also have a series of mailing lists on topics related to L=
iberationtech. The most important lists are the following:<br>
<br>
</span>=C2=A0 =C2=A0 * Events: <a href=3D"https://mailman.stanford.edu/mail=
man/listinfo/liberationtech-events" rel=3D"noreferrer" target=3D"_blank">ht=
tps://mailman.stanford.edu/<wbr>mailman/listinfo/<wbr>liberationtech-events=
</a><br>
=C2=A0 =C2=A0 * Jobs: <a href=3D"https://mailman.stanford.edu/mailman/listi=
nfo/liberationtech-jobs" rel=3D"noreferrer" target=3D"_blank">https://mailm=
an.stanford.edu/<wbr>mailman/listinfo/<wbr>liberationtech-jobs</a><br>
=C2=A0 =C2=A0 * CfP: <a href=3D"https://mailman.stanford.edu/mailman/listin=
fo/liberationtech-cfp" rel=3D"noreferrer" target=3D"_blank">https://mailman=
.stanford.edu/<wbr>mailman/listinfo/<wbr>liberationtech-cfp</a><br>
<span class=3D""><br>
=C2=A0 =C2=A0 For the aforementioned lists, we try to compile a list of all=
 events, job opportunities, and call for papers related to Liberationtech f=
rom all over the world.<br>
<br>
=C2=A0 =C2=A0 It&#39;s not a comprehensive list, so your assistance would b=
e helpful. If you hear of a job, event, or cfp that would be of benefit to =
Liberationtech subscribers, please let us know.<br>
<br>
<br>
=C2=A0 =C2=A0 Finally, we want to take Liberationtech to the next level. Wh=
at that means, we don&#39;t know. But the world has changed a lot since we =
started back in 2008: Censorship is on the rise. Internet freedom is on the=
 decline. And we have become much more of a community of hackers and cybers=
ecurity professionals who seek to protect vulnerable communities around the=
 world.<br>
<br>
=C2=A0 =C2=A0 So if you have ideas of projects you would like to see us tak=
e on, please let us know. We want the Liberationtech community to drive the=
 process. Any idea is welcome. Dream big or small. Just let us know how you=
 think we can best help.<br>
<br>
=C2=A0 =C2=A0 Thanks,<br>
=C2=A0 =C2=A0 Yosem<br>
=C2=A0 =C2=A0 (One of the moderators)<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</span>******************************<wbr>****************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" rel=3D"noreferrer" target=3D"_blank">=
http://www.consulintel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--001a1145b1fee96c2205477c3446--


From nobody Wed Feb  1 13:02:01 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A857B1299E8 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 13:02:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 jGS7GryIQZQM for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 13:01:57 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5615E1299D8 for <ietf@ietf.org>; Wed,  1 Feb 2017 13:01:57 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 591C8284E4D; Wed,  1 Feb 2017 21:01:56 +0000 (UTC)
Date: Wed, 1 Feb 2017 21:01:56 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170201210155.GI28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW"
Content-Disposition: inline
In-Reply-To: <20170124193109.68919.qmail@ary.lan>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4w85nya46byluRA9vlvwMgCchfw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:02:01 -0000

--0F1p//8PRICkK4MW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jan 24, 2017 at 07:31:09PM -0000, John Levine wrote:

> >My impression is that there is little problem with the intended
> >underlying spec, but the document text needs some tuning.
> 
> Agreed.  The subsequent section on comparing names would likely
> benefit from clearer instructions, e.g.
> 
> a) if the domain contains A-labels, turn them into U-labels
> b) if the domain still contains R-LDH labels, stop, not a valid name.
> c) if the domain contains NR-LDH labels, make them all the same case
> d) do a straight byte comparison of the addresses

I think that restricting R-LDH labels that are not A-labels is too
strict, see for example Phil Hallam-Baker's proposed encapsulation
of email addresses with "the mesh" (attached).

  TL;DR: alice@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE

The "mm" R-LDH namespace (if/when implemented) or some other future
namespace should probably not be excluded at this time.

If the intent is to canonicalize A-labels to U-labels, then perhaps
only "xn--" labels should be proscribed, if any.

On the other hand, I see there is some support for allowing
certificates to contain whatever form is actually used in email
headers, and perhaps more than just one such form.  If so, there
is no need to proscribe any names at all.  The client performs no
conversions, and the certificate would need to be inclusive of any
addresses that are in actual use.

-- 
	Viktor.

--0F1p//8PRICkK4MW
Content-Type: message/rfc822
Content-Disposition: inline

Return-Path: <ietf-bounces@ietf.org>
Received: from mail.ietf.org (mail.ietf.org [4.31.198.44])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mournblade.imrryr.org (Postfix) with ESMTPS id B7F26284E4C
	for <ietf-dane@dukhovni.org>; Wed,  1 Feb 2017 17:53:06 +0000 (UTC)
	(envelope-from ietf-bounces@ietf.org)
Received: from ietfa.amsl.com (localhost [IPv6:::1])
	by ietfa.amsl.com (Postfix) with ESMTP id 77B5F1294EF;
	Wed,  1 Feb 2017 09:53:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
	t=1485971583; bh=Dp1k30oAAxrUWD9fA8V6hR+AhrNuTwFbil30dRFgocg=;
	h=From:Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:
	 List-Post:List-Help:List-Subscribe;
	b=WbqcvWEyWE/8tSoYUJ2NdIYpjIRx0o4sPgji7wh69xFR+Gs4bz5v9tkqUtYqmfyEd
	 7g6x4l+yWE4q3N7LmHz8Ssj2ksIaNpMasjJF2X9kvcJXhJKgf2LcQZ5n9O+7yvouhE
	 VwAs8Y4TkBHk3r+0XNR4JXWHHANbADl0L2CWpCMg=
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 123441294DD
 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 09:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001,
 HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
 autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id Ogkgj9_UtwyS for <ietf@ietfa.amsl.com>;
 Wed,  1 Feb 2017 09:52:59 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com
 [IPv6:2a00:1450:400c:c09::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 BEF661294CF
 for <ietf@ietf.org>; Wed,  1 Feb 2017 09:52:58 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id t18so31159196wmt.0
 for <ietf@ietf.org>; Wed, 01 Feb 2017 09:52:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; 
 h=mime-version:sender:from:date:message-id:subject:to;
 bh=Dp1k30oAAxrUWD9fA8V6hR+AhrNuTwFbil30dRFgocg=;
 b=SvdHUmS0I1uPGg33bX/boqlNfj2VdBMpxe/vYHUYUoH+Mbs3bhjLTuvqO47Buv+dhG
 +rwc96Q1OUXKhKtTDEG7O+fkFegduU5LfQP7NxRjtdF3VHmn8WWGkIPJFd8Qp862yDIO
 dLnn4XB/CX51XNyG16xiIKOVAlgRebwG0UvkV4P+A+QUy+5yA+H6EMW7Ofi8mFxACMNW
 aUr+BenQA8H+DstBNZ0S2tNaqTADks1WpgorrytCvUVDPhom97Nx6f3AoqySQ8YJRtLp
 BHjqJoXXNAmk8coy5EW9P4Ui6Kw2acVNqTu0RIwRFcqyNfOn/6iqteBH64GoJuIl/e3Z
 B/sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:sender:from:date:message-id:subject
 :to; bh=Dp1k30oAAxrUWD9fA8V6hR+AhrNuTwFbil30dRFgocg=;
 b=lDtqTGFtmwokB3/xcIXM6LmdIZlJRHpxAeBsBIcU6SOd3NQvuwR8826xMX01cr13kd
 13oeIkts3xp5ktkEawoQCpOSpEoVdFp6iIijpxO0TEnvrPF2P9hkKPfLf29nGxnqptS4
 cQWDcoQu9Noq1p26lJH812Xtn6dCMRjJKRUxVhWH9w+hDagN6jpUpEUa4ImEdCyXLOhb
 EIgmofjI+vDFazXcrbfuTH4+6J+6qjXFTJszFVC87RAk6KjYeNyBb3haYYYgDoQMhzTb
 RL9OZfU4A49MshfngSOicFZCt64ObK6vTQJBoX4Z3Os9SkxgM19W+JaFUnXuom6wqI8l
 Vx4Q==
X-Gm-Message-State: AIkVDXJeSIwokaggPqsrnVxPd1CbkbldCSEFfvww077WAyNJDhXQJt3gC0OWFORZnvdIoZSD9VqjXEq4PoH6eA==
X-Received: by 10.223.155.197 with SMTP id e5mr3671583wrc.133.1485971576853;
 Wed, 01 Feb 2017 09:52:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.194.221.6 with HTTP; Wed, 1 Feb 2017 09:52:56 -0800 (PST)
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 1 Feb 2017 12:52:56 -0500
X-Google-Sender-Auth: tTXsCqn4MISox5RlQQC3gU4Se-Q
Message-ID: <CAMm+LwhYoEF=hsh-XuEWfU4eRgWrujzNgD2cdU3BGp8-YUucPQ@mail.gmail.com>
Subject: How to make the Internet secure
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c1b4e60fc220a05477bb7b1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PD6XmVtPW1vcSMKazOBcUofSYqw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
 <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
 <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org
Sender: "ietf" <ietf-bounces@ietf.org>

--94eb2c1b4e60fc220a05477bb7b1
Content-Type: text/plain; charset=UTF-8

One of the big problems I have found in trying to argue for ways we can
improve Internet security is that there are two camps. The incrementalists
will only look at solutions that provide an improvement on the status qujo
in one area and the perfectionists insist that any solution that does not
solve every possible problem isn't worth considering.

How about we do both?

Also to save time:

* Yes, I understand the deployment problem very well, I worked with the guy
who solved the network hypertext deployment problem after 20 years of
people failing.
* Yes, everything is end to end secure,
* Yes the transport is also secure to prevent metadata attacks.
* Yes it works with OpenPGP
* Yes it works with S/MIME
* Yes you can use it with SMTP/IMAP/POP
* Yes you can use it with Jabber
* No, you do not have to use a CA
* Yes, you may use a CA where a CA adds value
* Yes, I have considered the lock in problem
* Yes, you can bolt in your own trust model
* REST/HTTPS/JSON.
* AES/RSA/DiffieHelman, moving to CurveX for production.
* Yes it is unencumbered, apart from one part which will unlock this year.
* Yes I have a strategy for QRC
* No, it is not a walled garden
* Yes, you can adapt the system to use escrow cryptography but not without
the parties knowing so this is a frontdoor, not a backdoor.
* My employer sells endpoint protection systems, the Mesh is not a
substitute for endpoint protection, thank you for your interest.
* Reference code runs on Windows, Linux and should run on OSX. It is all
MIT license, so are the protocol compiler tools.

* Yes, it is easy to use. In fact it is exactly as easy to use as the
existing protocols because the user doesn't need to know that they are
doing security
* Yes it is easy to configure.
* Yes, I need help, a lot of help

OK so how is this possible?

First observation is that we now have several protocols that provide users
with end to end security that are really easy to use. The only real problem
I have with those systems is that they operate inside walled gardens. They
are not going to be a replacement for email.

Second is that public key cryptography is now cheap in terms of both cost
and performance. We couldn't do very interesting crypto in the 90s because
machines bogged


There are three contributions made by the Mathematical Mesh:

1) An infrastructure for managing and using client keypairs.

Adding cryptography to a protocol is actually quite easy when both parties
have public keypairs. So if we have an infrastructure that allows a user to
'glue' all their devices together into a personal mesh such that they all
have keypairs provisioned for each cryptographic purpose they might need
them for, cryptography becomes really easy for the user.

2) Extend a direct trust model into the DNS

We all know about TOR and onion routing. Well what if I could have an email
address that included my OpenPGP fingerprint? Well we can. Just use the
xx-- DNS label prefix to mark the fingerprint as not an ICANN DNS labnel
and we can make the fingerprint the TLD:

alice@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE

This means, 'only send mail to this address in compliance with a policy
signed under the fingerprint MBTVK...' Said policy could be an OpenPGP key
or it could be a Mesh mail profile.

3) Use of Proxy Re-Encryption (Recryption)

HTTPS provides end to end encryption between the user's client and the web
site serving the content. Using Proxy Re-Encryption we can provide end to
end encryption between the content creator and the user's client. This is
the part of the system that will be locked until late this year, (not that
I am sure the patent is valid, why bother checking when it expires)

We all know that two key cryptography is better than one. It is better
because encryption and decryption are different functions and using
separate keys for separate functions allows these to be done by different
parties. Recryption is three key cryptography and it is better than two key
for the same exact reason.

Using recryption allows us to develop protocols in which Alice is able to
publish a single encryption key but read her email on three different
devices, each of which has a separate decryption key so that she can
mitigate the risk if one of the devices is lost.


Job one is making it easy to manage client side keys.

Once we have that infrastructure, all else becomes straightforward. My
original goal with the Mesh was to make it easy to configure S/MIME and
OpenPGP. David Clark asked me to add SSH which I immediately realized could
be the killer app because the big problem with configuring SSH is that if
you do it to a machine at a remote site, 1000 miles away and you screw up,
someone has to get on a plane to fix it.

However, any infrastructure that allows mail application to say 'here are
the encryption keys to use to send mail to me and when to use them' can
also say 'I accept JSON format nextgen mail'. So this is an infrastructure
that allows us to lock down the legacy email systems as best as can be
managed but also eliminates the biggest barrier to deployment of a
successor system.


I am looking for help to make this happen.

http://prismproof.org/

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">One=
 of the big problems I have found in trying to argue for ways we can improv=
e Internet security is that there are two camps. The incrementalists will o=
nly look at solutions that provide an improvement on the status qujo in one=
 area and the perfectionists insist that any solution that does not solve e=
very possible problem isn&#39;t worth considering.</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">How about we do both?</div><div class=3D"gmail_de=
fault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" sty=
le=3D"font-size:small">Also to save time:</div><div class=3D"gmail_default"=
 style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"=
font-size:small">* Yes, I understand the deployment problem very well, I wo=
rked with the guy who solved the network hypertext deployment problem after=
 20 years of people failing.=C2=A0</div><div class=3D"gmail_default" style=
=3D"font-size:small">* Yes, everything is end to end secure,=C2=A0</div><di=
v class=3D"gmail_default" style=3D"font-size:small">* Yes the transport is =
also secure to prevent metadata attacks.</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes it works with OpenPGP</div><div class=3D"gm=
ail_default" style=3D"font-size:small">* Yes it works with S/MIME</div><div=
 class=3D"gmail_default" style=3D"font-size:small">* Yes you can use it wit=
h SMTP/IMAP/POP</div><div class=3D"gmail_default" style=3D"font-size:small"=
>* Yes you can use it with Jabber</div><div class=3D"gmail_default" style=
=3D"font-size:small">* No, you do not have to use a CA</div><div class=3D"g=
mail_default" style=3D"font-size:small">* Yes, you may use a CA where a CA =
adds value</div><div class=3D"gmail_default" style=3D"font-size:small">* Ye=
s, I have considered the lock in problem</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes, you can bolt in your own trust model</div>=
<div class=3D"gmail_default" style=3D"font-size:small">* REST/HTTPS/JSON.</=
div><div class=3D"gmail_default" style=3D"font-size:small">* AES/RSA/Diffie=
Helman, moving to CurveX for production.</div><div class=3D"gmail_default" =
style=3D"font-size:small">* Yes it is unencumbered, apart from one part whi=
ch will unlock this year.</div><div class=3D"gmail_default" style=3D"font-s=
ize:small">* Yes I have a strategy for QRC</div><div class=3D"gmail_default=
" style=3D"font-size:small">* No, it is not a walled garden</div><div class=
=3D"gmail_default" style=3D"font-size:small">* Yes, you can adapt the syste=
m to use escrow cryptography but not without the parties knowing so this is=
 a frontdoor, not a backdoor.</div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">* My employer sells endpoint protection systems, the Mesh is=
 not a substitute for endpoint protection, thank you for your interest.</di=
v><div class=3D"gmail_default" style=3D"font-size:small">* Reference code r=
uns on Windows, Linux and should run on OSX. It is all MIT license, so are =
the protocol compiler tools.</div><div class=3D"gmail_default" style=3D"fon=
t-size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:sma=
ll">* Yes, it is easy to use. In fact it is exactly as easy to use as the e=
xisting protocols because the user doesn&#39;t need to know that they are d=
oing security</div><div class=3D"gmail_default" style=3D"font-size:small">*=
 Yes it is easy to configure.</div><div class=3D"gmail_default" style=3D"fo=
nt-size:small">* Yes, I need help, a lot of help</div><div class=3D"gmail_d=
efault" style=3D"font-size:small"><br></div><div class=3D"gmail_default" st=
yle=3D"font-size:small">OK so how is this possible?</div><div class=3D"gmai=
l_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default"=
 style=3D"font-size:small">First observation is that we now have several pr=
otocols that provide users with end to end security that are really easy to=
 use. The only real problem I have with those systems is that they operate =
inside walled gardens. They are not going to be a replacement for email.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">Second is that public key c=
ryptography is now cheap in terms of both cost and performance. We couldn&#=
39;t do very interesting crypto in the 90s because machines bogged</div><di=
v class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D=
"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_def=
ault" style=3D"font-size:small">There are three contributions made by the M=
athematical Mesh:</div><div class=3D"gmail_default" style=3D"font-size:smal=
l"><br></div><div class=3D"gmail_default" style=3D"font-size:small">1) An i=
nfrastructure for managing and using client keypairs.</div><div class=3D"gm=
ail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defaul=
t" style=3D"font-size:small">Adding cryptography to a protocol is actually =
quite easy when both parties have public keypairs. So if we have an infrast=
ructure that allows a user to &#39;glue&#39; all their devices together int=
o a personal mesh such that they all have keypairs provisioned for each cry=
ptographic purpose they might need them for, cryptography becomes really ea=
sy for the user.</div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small">2) Exten=
d a direct trust model into the DNS</div><div class=3D"gmail_default" style=
=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"font-s=
ize:small">We all know about TOR and onion routing. Well what if I could ha=
ve an email address that included my OpenPGP fingerprint? Well we can. Just=
 use the xx-- DNS label prefix to mark the fingerprint as not an ICANN DNS =
labnel and we can make the fingerprint the TLD:</div><div class=3D"gmail_de=
fault" style=3D"font-size:small"><br></div><div class=3D"gmail_default">ali=
ce@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE<br></div><div class=
=3D"gmail_default"><br></div><div class=3D"gmail_default">This means, &#39;=
only send mail to this address in compliance with a policy signed under the=
 fingerprint MBTVK...&#39; Said policy could be an OpenPGP key or it could =
be a Mesh mail profile.</div><div class=3D"gmail_default"><br></div><div cl=
ass=3D"gmail_default">3) Use of Proxy Re-Encryption (Recryption)</div><div =
class=3D"gmail_default"><br></div><div class=3D"gmail_default">HTTPS provid=
es end to end encryption between the user&#39;s client and the web site ser=
ving the content. Using Proxy Re-Encryption we can provide end to end encry=
ption between the content creator and the user&#39;s client. This is the pa=
rt of the system that will be locked until late this year, (not that I am s=
ure the patent is valid, why bother checking when it expires)</div><div cla=
ss=3D"gmail_default"><br></div><div class=3D"gmail_default">We all know tha=
t two key cryptography is better than one. It is better because encryption =
and decryption are different functions and using separate keys for separate=
 functions allows these to be done by different parties. Recryption is thre=
e key cryptography and it is better than two key for the same exact reason.=
</div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">U=
sing recryption allows us to develop protocols in which Alice is able to pu=
blish a single encryption key but read her email on three different devices=
, each of which has a separate decryption key so that she can mitigate the =
risk if one of the devices is lost.</div><div class=3D"gmail_default"><br><=
/div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">Jo=
b one is making it easy to manage client side keys.=C2=A0</div><div class=
=3D"gmail_default"><br></div><div class=3D"gmail_default">Once we have that=
 infrastructure, all else becomes straightforward. My original goal with th=
e Mesh was to make it easy to configure S/MIME and OpenPGP. David Clark ask=
ed me to add SSH which I immediately realized could be the killer app becau=
se the big problem with configuring SSH is that if you do it to a machine a=
t a remote site, 1000 miles away and you screw up, someone has to get on a =
plane to fix it.</div><div class=3D"gmail_default"><br></div><div class=3D"=
gmail_default">However, any infrastructure that allows mail application to =
say &#39;here are the encryption keys to use to send mail to me and when to=
 use them&#39; can also say &#39;I accept JSON format nextgen mail&#39;. So=
 this is an infrastructure that allows us to lock down the legacy email sys=
tems as best as can be managed but also eliminates the biggest barrier to d=
eployment of a successor system.</div><div class=3D"gmail_default"><br></di=
v><div class=3D"gmail_default"><br></div><div class=3D"gmail_default">I am =
looking for help to make this happen.</div><div class=3D"gmail_default"><br=
></div><div class=3D"gmail_default"><a href=3D"http://prismproof.org/">http=
://prismproof.org/</a></div><div class=3D"gmail_default"><br></div></div>

--94eb2c1b4e60fc220a05477bb7b1--


--0F1p//8PRICkK4MW--


From nobody Wed Feb  1 13:38:13 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B11312957E; Wed,  1 Feb 2017 13:38:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, TVD_SPACE_RATIO=0.001] autolearn=ham autolearn_force=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 JIL_3OM5G0lj; Wed,  1 Feb 2017 13:38:06 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 18B06129446; Wed,  1 Feb 2017 13:38:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 66ED82D299; Wed,  1 Feb 2017 23:37:35 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XtqrGp0vHaqv; Wed,  1 Feb 2017 23:37:35 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 71F5E2CC9B; Wed,  1 Feb 2017 23:37:34 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Softwires] Review of draft-ietf-softwire-multicast-prefix-option-12
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148567501912.18000.17622999056704343003.idtracker@ietfa.amsl.com>
Date: Wed, 1 Feb 2017 22:37:31 +0100
Message-Id: <BFC2E000-BF81-4029-ABD0-748EFCFA789E@piuha.net>
References: <148567501912.18000.17622999056704343003.idtracker@ietfa.amsl.com>
To: Roni Even <roni.even@mail01.huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gcVBNplG8z1c0xTK2rERSCiEKx0>
Cc: softwires@ietf.org, gen-art@ietf.org, ietf@ietf.org, draft-ietf-softwire-multicast-prefix-option.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:38:07 -0000

--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks!

Jari


--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155
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

iQIcBAEBCgAGBQJYklUbAAoJEM80gCTQU46qyxkQAJaGUF11NdmDCY7VO184trEg
ny44h4w9sVSkqj7Az63K89Ke5KmR3iIFJ/b0wNcgQqQ3qOtUNjZMKMl7h11WtW1i
0ef0ENUsycc7jfmYfCctAtcXA74Fp+VTufNWE1p6SZ3nodGTTXOAnMi0bt4Y5XhQ
N4e85H6PMPlgvtTRVSKfsspQsuDV6w4qex3cdv4sbAGMgRbpYxCpzAdk7Riv0Psp
GVsfyJw/loM+bKHPBhfEluu7EAQG0wfTAyh/iHj0j+9imLyV4ArXe8AGeb/CvM51
4xMKUJ/9b9XFD7CNlU/tzcUiWJh34tVfRvZzw4KC2fcDAS0l4FyNONZpZnkj5QF4
oLCXKZaooR7zg/QRrHMFgCsOKjWXfAsg0KUnMh62edDGVhYZ5J6sVqnxLEbfcK7o
Imudwaii8r5KMBnuCzXRB8xFaKefeLEFx8MpMLMQY6cUpeVj1HswQairWUtZPAvI
KujlX67Hnrl3OMMz5XHwUy4WEUHEeq5y1rE3t73wA5AfFuRhsT0TRaJXY7Jog3/J
D2wS8SddJwWL1d3CaslDSMRVvatNSmXnVDWUlQHSilGEx47D1zfgaq1wtBuNt9Rf
Ecfmq+p4MAswZKW3Y6MihUNHkvcHID/ldEClezdK1kr1DgMevwyQ2fbnRNVzKZm/
sScz9Q9ebkDrpFBulIi5
=Mv3/
-----END PGP SIGNATURE-----

--Apple-Mail=_037ACD20-F4CF-4741-B183-49D9C7FB1155--


From nobody Wed Feb  1 13:42:49 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04D8B129A64; Wed,  1 Feb 2017 13:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=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 lGCh0irRjyjK; Wed,  1 Feb 2017 13:42:47 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 03DD11295DC; Wed,  1 Feb 2017 13:42:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 56AC32D299; Wed,  1 Feb 2017 23:42:33 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FmnQlkihM_DQ; Wed,  1 Feb 2017 23:42:32 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 7D5642CC9B; Wed,  1 Feb 2017 23:42:32 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: Review of draft-ietf-kitten-krb-auth-indicator-04
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20161225182404.GN8460@kduck.kaduk.org>
Date: Wed, 1 Feb 2017 22:42:32 +0100
Message-Id: <98EA1299-05B2-4AE2-A3AE-B88544CA4AE5@piuha.net>
References: <148243567232.26011.10783984451734200377.idtracker@ietfa.amsl.com> <20161225182404.GN8460@kduck.kaduk.org>
To: Benjamin Kaduk <kaduk@MIT.EDU>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/haMHBHJyqPvicfqiE8_ZDAkm7zg>
Cc: kitten@ietf.org, gen-art@ietf.org, draft-ietf-kitten-krb-auth-indicator.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:42:48 -0000

--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Many thanks for the review, Robert. These reviews are much appreciated,
and at least from my perspective, improve the quality of the RFCs. Happy
to hear from Benjamin that he=92s considering the editorial issues =
Robert
found in this case.

Jari


--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684
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

iQIcBAEBCgAGBQJYklZIAAoJEM80gCTQU46qGYsP/R6Iut6xUmWprcpZlSx8AoJ+
7MoZaw510bodje5COhRoFSH0dkqNlV0XE/LWlGytHx44TJlFxIWgasXo/hCvhQSr
KG4NS3Wi/ue12EkZPd5yDOw46oyHiKJ57c6ug/lkbcEDFKVG5B3tSIfJaKEwogDR
bByE+MMxriAf8wLSnJiS67eOJowoOSpVktzRQFPBLc08gG3Bep1uYFAqYY2x42PV
xmPmaV8OgaE+FGq3JLLDHcfL0IzkAKz3pJjiR05rXfV6onRGDhk9MDzbcg0kJyAM
SO5IcjLZDzkS37mL7aK370I5JRbrExng1+4muTMb+4rcn7fmGEDeNwcIWlwkwVjU
y9OV5luFfo00/H+oNEUo/iIrCtvv4PTbdbPXOsFEHG4UNAn+4FC3zir/IVKHviGo
9r1G++sA4Yd1AMVoYqtl8I0/ThsCQerpchyMf+ryCJLMMFviHTgaEyvX24QTzzwN
k9jUgVZ3dB+mV09nDBfHxKRskJ/P81PCWtQxJuYUEjjDlKfTQBndX200CpxSzz72
wFxQ9ypdNcmP1USuFaydbWXt40fleYtTMeLu2/fdsgkP9N1wZXrjaUF99SWghbzU
LOsrkXsf68puoGx9C+kqNdN/enuUAF4zCE/P0QZlbn3RzvLa/65NZ2x6/WpS7V1J
+V/O12NZQBr3nWZQOHJ5
=Sjy0
-----END PGP SIGNATURE-----

--Apple-Mail=_5DD3C1ED-684C-4A16-8944-49B1D744E684--


From nobody Wed Feb  1 13:46:41 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EDC712957E; Wed,  1 Feb 2017 13:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=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 yhfR941azJBF; Wed,  1 Feb 2017 13:46:34 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 960591295AA; Wed,  1 Feb 2017 13:46:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 065242D299; Wed,  1 Feb 2017 23:46:28 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpgY86z-195W; Wed,  1 Feb 2017 23:46:27 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 14B8A2CC9B; Wed,  1 Feb 2017 23:46:27 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Review of draft-ietf-mmusic-4572-update-11
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B4BFC08AC@ESESSMB209.ericsson.se>
Date: Wed, 1 Feb 2017 22:46:25 +0100
Message-Id: <80FA28DD-1CEE-44B0-B14C-AA991B5AB4CE@piuha.net>
References: <s9ubcupjutekv1baydfw2bpi.1485353373053@email.android.com> <7594FB04B1934943A5C02806D1A2204B4BFC08AC@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2_zUUSPztKeGlT5Iqr8ZmqCBAr8>
Cc: "draft-ietf-mmusic-4572-update.all@ietf.org" <draft-ietf-mmusic-4572-update.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 21:46:40 -0000

--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Elwyn, Christer =97 many thanks for the in-depth review and updates.

I have posted a =93no objection=94 position for this document for =
tomorrow=92s
IESG telechat.

Jari


--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052
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

iQIcBAEBCgAGBQJYklcxAAoJEM80gCTQU46qCecQAKTTljd03QyNy67KotiAfIvD
yyaAnNThfefM4/XhMpxXvYrHPEcHwBVJ87mWPOr0RAiIqAYJEhCgNyH1MXGT1Bkw
LZ+2m4xrxoX2U0e1WliLdCJIRgev5i/YIefJ3Q7XnESZfqSgUzzZhyLtTCoqPjf8
19YNuc+/0c/RqeOna8kPyGXB1+HkS/zF2v8or211eQUwuoqHBK9IYji2w3ZvRl1B
QeKLvmUmOUecvYtzZK4i1M6FHsj7atsKBfa3+JTgfjBXwqnFr84bKl9IimhGXKVr
yCzDhAb+qJwUhRAQC2v4fuVGsfazfL83eJ0ajBj3MLWv3WjNzIkenZWmUoVIxKP8
Osc0HAu5K2/uuzwFxibTuAeV/D+9BBIbQ3OrUimowp1i645cFusOwJNNgsTixAAf
EuywN1QeBh6MHr8xbwUZ69lL7uJ2LDSB0+pCB5HDDyp84UK0TkYq8qHx3PUT4g2W
QbQ1DZgT2IHj1nBPwHbyxdWeoneyBY60l/YLveGUHSvvJIK2kyAxKorvupbHEXAT
mEDBmg+uSIpjjuL5J+sCv3xUU++9IuDOU010w4UmMsVyg2ka+WYeb2JD+BPLBWrQ
bAY6noNNn05Zl4APYG64lPiHbrwA6ZPrWZMRtV5HPsMFdhilJkJZdCEnjQLNav+M
YbfKInfJ2sSJwWDi5W8s
=jIAc
-----END PGP SIGNATURE-----

--Apple-Mail=_6BDC5AD5-E9D4-44F3-AD23-01DB3D80A052--


From nobody Wed Feb  1 14:51:59 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E7212961A; Wed,  1 Feb 2017 14:51:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=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 K7GBjnBg4-Kt; Wed,  1 Feb 2017 14:51:57 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id AD64F1295D5; Wed,  1 Feb 2017 14:51:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 01CEE2D299; Thu,  2 Feb 2017 00:51:55 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pUl9muKjGzhj; Thu,  2 Feb 2017 00:51:54 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 425FD2CC9B; Thu,  2 Feb 2017 00:51:54 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: If categories of people are blocked by the U.S., should the IETF respond?
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_7E7F29E5-5B38-4ADE-AABF-B673195FDF5D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com>
Date: Wed, 1 Feb 2017 23:51:54 +0100
Message-Id: <6EBC4274-4981-40C4-ABDB-0A5BEFBCD4F4@piuha.net>
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <CAHw9_iJ78ECZ5x8LsR53KhRFnbhi3gV7n8yzG07e1wbN-SG14Q@mail.gmail.com> <8f5ef9ac-b62b-863a-0a0e-f5d2b329de09@nostrum.com> <20170129134410.GA14422@gsp.org> <4D233FE8-6E84-446F-A8ED-604E4F7EAB99@piuha.net> <0d60ed80-2183-e329-05ad-e0cd7ab77ac1@cs.tcd.ie> <6.2.5.6.2.20170201042624.0ce2aa40@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tR18fRUOTmT_VdXNv50u3-J0H9Y>
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 22:51:59 -0000

--Apple-Mail=_7E7F29E5-5B38-4ADE-AABF-B673195FDF5D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> I scanned the list quickly and I only found two IESG members, the IETF =
Chair and you, commenting on the issue.  Do the other IESG members have =
an opinion about the topic?

I think I may have discussed the topic by now with every person on the =
IESG, IAB, and IAOC. I can assure you that they care deeply about the =
topic :-)

Jari


--Apple-Mail=_7E7F29E5-5B38-4ADE-AABF-B673195FDF5D
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

iQIcBAEBCgAGBQJYkmaLAAoJEM80gCTQU46qhmwP/R6JqyGjnfCaBfYwi1ZEFswB
hMvp3WaBKuqu5Tbbqk6x6iMtN3+9Qfu+qDEtLqZmI96W/myJhQ0yG86QV4ZFHUyX
gkfjtsYpZej97BO4t16b3ceWWgsiP+w6U5UrCYJgDLn1ZXr9WP2575q7q/a1rUpY
YD9tO66BNC4zPc9cPHy6CatMt/2I8k45XrVi5saZFgWdsLTfMi/uQqcBHr5zZYFm
mRWz0eRO36HvCkFsp4Dw5YAJkdy57r6p4/NXK2QjxKxuBp+SNEsXBlZyOqlbY2Gx
PcEdfKnsRZdPuaZCAYcXLxBgdXxKQh/F3b9rNQzszyns2LTR74f/xEicf76Ci5aa
ePGg6x4d74rxbmnnRH4FK02/wSu0PfBo4jWBgbKjmcqAsCrABB5p/9U7dZTiuhYz
yTRvrH+1xHj4X4dLgQVpOx98pLLlfzSPD5lFFBP81cbD8r4AbkroWw2fN+OQWO84
A5cj3Q3GxpiG7s3KOiduZnE27Lh57hhKm3Y72Pr6WcWTviEHFJxZPTcvN5+tgl2f
wD6c7OEOvvLq/RGj4rmuw3f3p/GPh6brgZB7KLvppFKBurx1r1DzadtIRobF/0LN
oxzGeDFbtTbzye8bYu41Ty7mi3JfULnkV6Gc5H4b0qLWl2meKrJf0XZElka5DrXX
ExhkjwD37tfRZ01r0Ok8
=+Dpk
-----END PGP SIGNATURE-----

--Apple-Mail=_7E7F29E5-5B38-4ADE-AABF-B673195FDF5D--


From nobody Wed Feb  1 15:55:30 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0826129600 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 15:55:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.256
X-Spam-Level: 
X-Spam-Status: No, score=-3.256 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oiAe1SZ5tiIJ for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 15:55:28 -0800 (PST)
Received: from nm15-vm9.bullet.mail.gq1.yahoo.com (nm15-vm9.bullet.mail.gq1.yahoo.com [98.137.176.69]) (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 161391295EB for <ietf@ietf.org>; Wed,  1 Feb 2017 15:55:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1485993327; bh=Uky2dyLgNG3hUqgbVYV1ufK2lV4fTniElFisxNzLdkE=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=VbSoBFNO2GxTlsuXc7sMKwg+n+bJRopYLpcrlewYkMNGmT41pVk3ZeMmsPiZpSeoExaIE8wS21pR+kG3flyxI7crjtyGelPyUhwT56dhYyI9YP/cNrwlMKXX53uM6CbndDFI8SXqkr310nyvFVBK68/OyZBnTSsFK41hiCfpWREgrZ8uQey26J7L9/Rx88dudSjTi3jGhyICjapzH6aRwwZ3RDP0eCfzMbwq9yzSdpPUzjc5AfGcFU6/Q9a/qDSvvFCFzDXQm7FPTM+XIxKoSUwyAnJk7Gm5sWsJFWUw4qOUyzojGgdOiyZdeoOeTeD59J1B7wOQ/sTNKZxtqWC1uQ==
Received: from [98.137.12.188] by nm15.bullet.mail.gq1.yahoo.com with NNFMP; 01 Feb 2017 23:55:27 -0000
Received: from [98.137.12.243] by tm9.bullet.mail.gq1.yahoo.com with NNFMP; 01 Feb 2017 23:55:27 -0000
Received: from [127.0.0.1] by omp1051.mail.gq1.yahoo.com with NNFMP; 01 Feb 2017 23:55:27 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 758636.34030.bm@omp1051.mail.gq1.yahoo.com
X-YMail-OSG: Yt95vb0VM1l6r.ZvJ52kRvWQ2r3tYGBZtpwUCQeggHkVB8lGCKt6EFithnUyR3Y H8p6HeSOtdpWctyrOoI84J6wzOJF2C8Gcni74Yj.PBEpNd7xHuoU1neeo4j2__GansfOBf60eI_m fRrEGpTcaJF3vkNwyEKDEObaE.s5KuAH.Q__eN.DUrKJlKGkJnO4nl3sNUwJxRt4M9mYIDTOxKYn VY7GN.m0KPBSret1Wd1SWhQP.QT.44pA23A2MA5GWIeujlaEC1xbD77p1MUH9aHVYeT5ROiqyGEB 2FrNd8jVGYoQPsVJlR4q8O6tKYEgbnIjc_GPbnIVCc8nR2wj9UaFPqQKRTpSZmmIvQZ4Dv4uoUmR wW1OHaN5a4t4G1md8r9EA9NRDKma.tixXKnQ_IuE5W6zLO6DZjCEyKmftgmdaZy3Y6XRrwrRur56 bZ.nJSf5SYcXIfk_PHaS7dR4Dul7D3kNSg1vqZ4BXJDUlHlcXR_4t87GMlpq_mwUyxZfFojOY76t rhNjGU_CHp_0yZm5BYFziDOr.ndIXRz2eN76GuZFepw--
Received: from jws300063.mail.gq1.yahoo.com by sendmailws126.mail.gq1.yahoo.com; Wed, 01 Feb 2017 23:55:27 +0000; 1485993327.393
Date: Wed, 1 Feb 2017 23:55:27 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Jari Arkko <jari.arkko@piuha.net>
Message-ID: <216577619.2412027.1485993327131@mail.yahoo.com>
Subject: Re: If categories of people are blocked by the U.S., should the IETF respond?
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <216577619.2412027.1485993327131.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oLoc-K2K0cIGyt7iJtundGIE3Ck>
Cc: iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Feb 2017 23:55:29 -0000

=20
>> I scanned the list quickly and I only found two IESG members, the IETF C=
hair and you, commenting on the issue.=C2=A0 Do the other IESG members have=
 an opinion about
>> the topic?
=20
> I think I may have discussed the topic by now with every person on the IE=
SG, IAB, and IAOC. I can assure you that
> they care deeply about the topic :-)
=20
Thank you to everyone for their engagement in this area.

I wonder if you might also want to consider how we might act together with =
other tech organizations, if you feel that is appropriate.

I am getting questions from people as to what we might do and I really don'=
t have an answer for them.

Thanks,
Nalini


From nobody Wed Feb  1 16:09:52 2017
Return-Path: <pat.thaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 662351294F0 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 16:09:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=broadcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TlMEUix_fgZ1 for <ietf@ietfa.amsl.com>; Wed,  1 Feb 2017 16:09:48 -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 1F02812959A for <ietf@ietf.org>; Wed,  1 Feb 2017 16:09:48 -0800 (PST)
Received: by mail-vk0-x231.google.com with SMTP id t8so171578vke.3 for <ietf@ietf.org>; Wed, 01 Feb 2017 16:09:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=efCC3bfjpCaGjrw60cmYUtd66rXNrw5y9oxEc1YhUbw=; b=buQrJ818SiRM6oG+YamaBr8j7ehB/r3bKXlnpzsR1nzaq3Ai6GFPcTd23p+7SydhxG z4dMRYWUdbKT/4DdefV4rgAcS4fgRDIwfk4iNrCBSjQuUHq7Saqro7GQDKCqrSdgxJ2M MjLl+GTd/xK7u2VFiNrmknKkspgPuy9QzfjhA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=efCC3bfjpCaGjrw60cmYUtd66rXNrw5y9oxEc1YhUbw=; b=e8kHMDxczdLTjUkxMMlIL5uWr0IZ9be/LKHdYXtb1Z2zZLxvMt5YjZbpYTPHivKBbO fVLH7HuZEflhpS6dnXZp4SGf9VG+4RUNArHgvfUzrsP5UBaLWNfy3OM7v32efP43QGCc X7PT4Drb67vK5uqoi5d2l7SuxtAqH/xMMTS6w6YbkMLZH0NK60JQL1G31IECQ/HMmn3b KNDDZy5fh2vikU/1lIbO8BEhDAAAuQr/6MLWVq5A/Gkw79AuOrYLTZWCSFyGzjWTnNIV rM2WzfXAxspcF6UiossVgZ9HndZVSLGZNCtczfi65r8eS0QmpicXVW7ejJW5Jae3UvSg S9kQ==
X-Gm-Message-State: AIkVDXLegeMWIV1mwKYr4mxD3jQ+CtMYNau0hPus3ffAvPUznk3+6NQDGrG1hmiGXAux/9L7MhX0ncMb122KR2DS
X-Received: by 10.31.48.75 with SMTP id w72mr2808812vkw.69.1485994186917; Wed, 01 Feb 2017 16:09:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.69.226 with HTTP; Wed, 1 Feb 2017 16:09:46 -0800 (PST)
From: Pat Thaler <pat.thaler@broadcom.com>
Date: Wed, 1 Feb 2017 16:09:46 -0800
Message-ID: <CAJt_5EiSDWaT+SVJ7TMk4gDkV5uRXX5D8eby=gA3xz3KymyyQw@mail.gmail.com>
Subject: Re: Follow-up on the issue of IETF members being unable to attend.
To: Dave Burstein <daveb@dslprime.com>
Content-Type: multipart/alternative; boundary=001a11430ea6a6a947054780fb68
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YlLIf_B475yv2cm_9sTHw41l4BM>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 00:09:50 -0000

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

Just to clarify, there is IEEE (the whole organization) and many different
subgroups of IEEE of which IEEE 802 is one. IEEE in Dave's first bullet is,
I expect, referring to IEEE as a whole. The third bullet applies for IEEE
802. I've no idea what the refund policy will be applied by other IEEE
subgroups who are holding meetings, conferences and such.

IEEE at the top level has said, in an email to the subgroups, that a
statement from IEEE is forthcoming. They have asked the subgroups to
refrain from issuing independent statements until that happens.

The IEEE 802 Executive Committee has it's regular teleconference on Feb 7.
There is an agenda item to discuss impact of the immigration policy on us.
It has already been IEEE 802's practice to refund plenary meeting fees when
someone can't attend due to a visa issue. There may be discussion on
whether to confirm that policy with a motion.

Regards,
Pat



On Tue, Jan 31, 2017 at 11:53 PM, Dave Burstein <daveb@dslprime.com> wrote:

> Folks
>
> I want to thank Jari, Leslie, and Andrew for speaking rapidly and clearly.
> I believe they are wise to address the issues directly affecting IETF
> rather than discussing the merits of U.S. policy. I believe just about
> everyone following this knows the issues and nothing would be gained by
> political discussion.
>
> A few follow-up suggestions, carefully chosen to be procedural. I'm mostly
> a lurker here.:
>
>
>    - That the IETF liaisons courteously forward our blog to the
>    organizations we connect with. I just got a note in IEEE that they are
>    considering a policy and believe what we've decided could help their
>    discussion. I particularly would like to hear from Gonzalo with any
>    response we get from 3GPP, a European-based group that might have a
>    different perspective.
>    - That we take up the offer of support from ISOC that Kathy Brown
>    posted on the ISOC list. They have a communications staff of about a dozen
>    full-time people. I've heard from two ISOC Board members as well as Kathy
>    that they are deeply committed to doing what's right here. They might help
>    if we reach out and reiterate that IETF is open to all. That could be as
>    simple as a letter to the editor of leading publications in the countries
>    most directly involved. I assume that whoever signs the note will carefully
>    not present personal opinions as IETF policy. We could also send out the
>    blog we have.
>    - That we consider providing refunds to those blocked from attending.
>    I'm told that IEEE will almost definitely offer refunds. I'd suspect the
>    total would not be that large. It will be discussed at a teleconference
>    February 7 http://www.ieee802.org/minutes/Conference-calls/
>    Conference-calls.shtml . I believe there are many IEEE members here
>    and the call is open to all.
>
> I have been reporting on this at http://bit.ly/2kKIjY3, which I'm posting
> as a bit.ly link rather than with a title some might think subjective.
>
> Dave Burstein
>
>
>
> --
> Editor, Fast Net News, 5GW News, Net Policy News and DSL Prime
> Author with Jennie Bourne  DSL (Wiley) and Web Video: Making It Great,
> Getting It Noticed (Peachpit)
>

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

<div dir=3D"ltr">Just to clarify, there is IEEE (the whole organization) an=
d many different subgroups of IEEE of which IEEE 802 is one. IEEE in Dave&#=
39;s first bullet is, I expect, referring to IEEE as a whole. The third bul=
let applies for IEEE 802. I&#39;ve no idea what the refund policy will be a=
pplied by other IEEE subgroups who are holding meetings, conferences and su=
ch.<div><br></div><div>IEEE at the top level has said, in an email to the s=
ubgroups, that a statement from IEEE is forthcoming. They have asked the su=
bgroups to refrain from issuing independent statements until that happens.=
=C2=A0</div><div><br></div><div>The IEEE 802 Executive Committee has it&#39=
;s regular teleconference on Feb 7. There is an agenda item to discuss impa=
ct of the immigration policy on us. It has already been IEEE 802&#39;s prac=
tice to refund plenary meeting fees when someone can&#39;t attend due to a =
visa issue. There may be discussion on whether to confirm that policy with =
a motion.=C2=A0</div><div><br></div><div>Regards,</div><div>Pat</div><div><=
br></div><div><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Tue, Jan 31, 2017 at 11:53 PM, Dave Burstein <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:daveb@dslprime.com" target=3D"_blank">daveb@dslprime.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div s=
tyle=3D"font-family:verdana,sans-serif">Folks</div><div style=3D"font-famil=
y:verdana,sans-serif"><br></div><div style=3D"font-family:verdana,sans-seri=
f">I want to thank Jari, Leslie, and Andrew for speaking rapidly and clearl=
y. I believe they are wise to address the issues directly affecting IETF ra=
ther than discussing the merits of U.S. policy. I believe just about everyo=
ne following this knows the issues and nothing would be gained by political=
 discussion.=C2=A0</div><div style=3D"font-family:verdana,sans-serif"><br><=
/div><div style=3D"font-family:verdana,sans-serif">A few follow-up suggesti=
ons, carefully chosen to be procedural. I&#39;m mostly a lurker here.:=C2=
=A0</div><div style=3D"font-family:verdana,sans-serif"><br></div><div><ul><=
li style=3D"font-family:verdana,sans-serif">That the IETF liaisons=C2=A0cou=
rteously forward our blog to the organizations we connect with. I just got =
a note in IEEE that they are considering a policy and believe what we&#39;v=
e decided could help their discussion. I particularly would like to hear fr=
om Gonzalo with any response we get from 3GPP, a European-based group that =
might have a different perspective.=C2=A0</li><li>That we take up the offer=
 of support from ISOC that Kathy Brown posted on the ISOC list. They have a=
 communications staff of about a dozen full-time people. I&#39;ve heard fro=
m two ISOC Board members as well as Kathy that they are deeply committed to=
 doing what&#39;s right here. They might help if we reach out and reiterate=
 that IETF is open to all. That could be as simple as a letter to the edito=
r of leading publications in the countries most directly involved. I assume=
 that whoever signs the note will carefully not present personal opinions a=
s IETF policy. We could also send out the blog we have.</li><li>That we con=
sider providing refunds to those blocked from attending. I&#39;m told that =
IEEE will almost definitely offer refunds. I&#39;d suspect the total would =
not be that large. It will be discussed at a teleconference February 7 <a h=
ref=3D"http://www.ieee802.org/minutes/Conference-calls/Conference-calls.sht=
ml" target=3D"_blank">http://www.ieee802.org/<wbr>minutes/Conference-calls/=
<wbr>Conference-calls.shtml</a> .<span style=3D"font-family:verdana,sans-se=
rif"> I believe there are many IEEE members here and the call is open to al=
l.=C2=A0</span></li></ul><div><font face=3D"verdana, sans-serif">I have bee=
n reporting on this at=C2=A0<a href=3D"http://bit.ly/2kKIjY3" target=3D"_bl=
ank">http://bit.ly/2kKIjY3</a>, which I&#39;m posting as a <a href=3D"http:=
//bit.ly" target=3D"_blank">bit.ly</a> link rather than with a title some m=
ight think subjective.=C2=A0</font></div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div><font face=3D"verdana, sans-serif"><br></font></div><div>=
<font face=3D"verdana, sans-serif">Dave Burstein<br>=C2=A0</font></div></fo=
nt></span></div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></d=
iv><div><br></div>-- <br><div class=3D"m_2456183995605096215gmail_signature=
"><div dir=3D"ltr"><div><div dir=3D"ltr">Editor, Fast Net News, 5GW News, N=
et Policy News and DSL Prime<br>Author with Jennie Bourne =C2=A0DSL (Wiley)=
 and Web Video: Making It Great, Getting It Noticed (Peachpit)</div></div><=
/div></div>
</font></span></div>
</blockquote></div><br></div></div></div>

--001a11430ea6a6a947054780fb68--


From nobody Wed Feb  1 21:09:42 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82F60126579; Wed,  1 Feb 2017 21:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.721
X-Spam-Level: 
X-Spam-Status: No, score=-17.721 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qPTHz_7SXkpY; Wed,  1 Feb 2017 21:09:38 -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 B86B3128B38; Wed,  1 Feb 2017 21:09:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15803; q=dns/txt; s=iport; t=1486012177; x=1487221777; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=RXcYe8XEFbgJOe2pkyk2Xa03uI31b1HYArcRpuOUFSY=; b=TUAQ1WvrRPuQWZsUwtvLl+ZfAB5mQgimS/wOXwzPBEYY1Rq9pmASQ32x BUTHg6wF/obqHB78NZMZX+E/b5KYbidtQQbCl4bZt+IXGoRzX0fUxavdI t56A7xcjnxCIB0fqH8oGJNs7UXQ0UdStn6oQNwMkperp4XPb23zqDUCur 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BgAgBfvpJY/5ldJa1TAQkZAQEBAQEBA?= =?us-ascii?q?QEBAQEHAQEBAQGDU2GBCQeNWJExV5U1gg0fDYV2AoJAPxgBAgEBAQEBAQFiKIR?= =?us-ascii?q?qAgQBATgtBwsQAgEIEgIBIRAnCxcOAgQBDQMCiXEOrxyLLgEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAR2GS4NmgQmEJQEDXIUtBY82jCcBhmeDHogBgXtThESDTYYjiCe?= =?us-ascii?q?KXAEfOIFLFTuERB2BYUMyAYYsKoEGgQwBAQE?=
X-IronPort-AV: E=Sophos;i="5.33,323,1477958400"; d="scan'208";a="206564865"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Feb 2017 05:09:35 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1259ZLq009565 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 Feb 2017 05:09:35 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 1 Feb 2017 23:09:34 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Wed, 1 Feb 2017 23:09:34 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSfRKL4IsoqrqRR0ud1/efTVlacQ==
Date: Thu, 2 Feb 2017 05:09:34 +0000
Message-ID: <D4B7FC35.258902%sgundave@cisco.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F795399A3B3588449753A5BCCF4FA1AD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QhDEGd_zVAlQE7ASIXcqlAQ8Rds>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 05:09:40 -0000

Thank you Dale for a great review.


Charlie/Authors - Can you please respond to Dale and address these
comments.


Regards
Sri


On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
on behalf of worley@ariadne.com> wrote:

>Reviewer: Dale Worley
>Review result: Ready with Issues
>
>I am the assigned Gen-ART reviewer for this draft.  The General Area
>Review Team (Gen-ART) reviews all IETF documents being processed
>by the IESG for the IETF Chair.  Please treat these comments just
>like any other last call comments.
>
>For more information, please see the FAQ at
><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>Document:  draft-ietf-dmm-4283mnids-04
>Reviewer:  Dale R. Worley
>Review Date:  31 Jan 2017
>IETF LC End Date:  2 Feb 2017
>IESG Telechat date:  16 Feb 2017
>
>Summary:
>
>       This draft is on the right track but has open issues,
>described
>       in the review.
>
>Technical issues:
>
>1. The Introduction states
>
>   Other types of identifiers are in
>   common use, and even referenced in RFC 4283.
>
>For the reader's sanity, some sort of accounting needs to be made of
>these "other types of identifiers", especially because each type of
>identifier needs an identifier type number.  The text in 4283 is
>
>   Some examples of identifiers
>   include Network Access Identifier (NAI), Fully Qualified Domain
>Name
>   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>   Subscriber Number (MSISDN).
>
>Are there any other types "in common use"?
>
>- NAI (type 1) is defined by 4283.
>- Fully Qualified Domain Name (FQDN) seems not to be specified
>- International Mobile Station Identifier (IMSI) (type 3) is defined
>in
>  this draft
>- Mobile Subscriber Number (MSISDN) seems not to be specified
>
>2. Is it intended to have an IMEI identifier type?  The introduction
>mentions an IMEI type, but there is no specification for it, nor is
>there an identifier type number assigned for it.
>
>   ... types for IMSI
>   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>GUTI
>   [ThreeGPP-IDS].
>
>Initially I suspected it was it was present in an earlier revision
>and
>then later deleted without this reference being updated.  But all
>versions of draft-ietf-dmm-4283mnids and its predecessor
>draft-perkins-dmm-4283mnids mention IMEI in this way as one
>identifier
>type, but none specify it in any way.  The only discussion I can find
>on the DMM mailing list of IMEI is:
>
>  =20
>https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>=3Dd29575f767ce67a1e67a7767008ee6af
>
>    From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>    To: DMM
>    Date: Wed, 10 September 2014 13:29 UTC
>    Re: [DMM] regarding the re-chartering..
>
>    It seems the MNID is somehow overloaded to carry both,
>node-specific
>    IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>    There may be value in adding the IMEI to the list of possible
>types of
>    node-specific IDs.
>
>Either the presence of IMEI in this list is a simple mistake that has
>persisted in all versions of the draft, or specifying IMEI has always
>been intended but has always been overlooked.
>
>3. The definition of identifier types for both EUI-48 and EUI-64
>suggests that it might be desirable to define an identifier type for
>arbitrary hardware (link-level) addresses.  It seems that the natural
>differentiator for that purpose is the "hardware type" used in ARP,
>so
>a EUI-48 address would be represented as
>
>    MN identifier type (one octet) 5 (say)
>    hardware type (two octets) 1
>    EUI-48 (six octets)
>
>and an EUI-64 similarly, with hardware type 27.
>
>Although with only two subtypes in common use, generalizing this
>might
>not be worth the effort.
>
>4. Several of the identifier types can be represented as URNs:
>
>- IMEI can be represented as a URN as urn:gsma:imei:...
>- all of the RFID types have a URN representation (called the
>  "pure-identity URI" in the RFID specifications), which starts
>  urn:epc:id:...
>
>Since all URN types are ensured of being unique and persistent, it
>seems that we could define a MNID type for URNs generally, and then
>any RFID URI or an IMEI (as a URN) could be used as a value of that
>type.
>
>If this idea is adopted, it seems that the other 3GPP types (IMSI,
>P-TMSI, and GUTI) should be given defined encodings as URNs in new
>sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>of IMEIs defined in RFC 7254.
>
>This consolidation could be significantly beneficial.  It allows MNID
>to use any URN scheme as an identifier.  It reduces the three
>different RFID representations to one.  It incorporates any future
>expansion of RFID schemes (because all schemes will have a
>pure-identity URN representation).  A disadvantage is that the URN
>encodings are long, but the security considerations section states
>that MNIDs are used only on the first registration at the home agent,
>so there isn't much need for brevity.
>
>Similarly, this approach incorporates any future expansion of mobile
>identifiers that GSMA decides to define, as long as GSMA provides a
>URN representation for it.
>
>The most significant disadvantage is that some URN schemes allow
>several character strings to "mean" the same URN.  In most URN
>schemes, the allowed variation is limited to the case of letters, and
>the common convention is to always use lower-case when there is a
>choice, leading to a unique conventional canonical form for the URN.
>
>5. Regarding the encoding of a string of digits into octets, it is
>stated that "The last digit MUST be zero padded, if needed, for full
>octet size."  This seems very unwise unless there is a 3GPP decree
>that if a zero is appended to a valid IMSI, the resulting string is
>never a valid IMSI.  Instead, I would specify that padding is by
>filling the low-order 4 bits of the final octet with 0xF.  That
>ensures that the encoding can be uniquely decoded into an IMSI.
>
>6. There are four types of DUID specified, each with a distinct MNID
>value.  However, DUIDs contain an initial two-octet type field which
>distinguishes the various types of DUID, so providing them with
>distinct MNID values is redundant.
>
>Distinguishing the types and allowing only four of them to be used as
>MNIDs seems to be contrary to the philosophy of DUID construction
>(RFC
>3315 section 9):
>
>   Clients and servers MUST treat DUIDs as opaque values and MUST
>only
>   compare DUIDs for equality.  Clients and servers MUST NOT in any
>   other way interpret DUIDs.  Clients and servers MUST NOT restrict
>   DUIDs to the types defined in this document, as additional DUID
>types
>   may be defined in the future.
>
>Of course, MNID isn't a DHCP operation, so it isn't subject to those
>requirements, but I expect that devices will use the same DUID for
>both mobile identification, and we don't want mobile identification
>to
>restrict future developments of DHCP.
>
>I think this specification must treat DUIDs as opaque and use only
>one
>MNID type that allows all types of DUIDs as values.
>
>Editorial issues:
>
>Abstract
>
>   Additional Identifier Types are proposed for use with the Mobile
>Node
>   Identifier Option for IPv6 (RFC 4283).
>
>s/proposed/defined/
>This document will define the new types (once it is approved)!
>
>1.  Introduction
>
>   ... types for IMSI
>   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>GUTI
>   [ThreeGPP-IDS].
>
>There is no description of P-TMSI identifiers, although it is
>assigned
>identifier type 4.
>
>There is no description of GUTI identifiers, although it is assigned
>identifier type 7.
>
>3.  New Mobile Node Identifier Types
>
>   The following types of identifiers are commonly used to identify
>   mobile nodes.  For each type, references are provided with full
>   details on the format of the type of identifier.
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   including
>
>   o  RFID-GID (Global Identifier),
>   o  RFID-SGTIN (Serialized Global Trade Item Number),
>   o  RFID-SSCC (Serial Shipping Container),
>   o  RFID-SGLN (Global Location Number),
>   o  RFID-GRAI (Global Returnable Asset Identifier),
>   o  RFID-DOD (Department of Defense ID), and
>   o  RFID-GIAI (Global Individual Asset Identifier).
>
>   For each RFID scheme except GID, there are two variations: a
>64-bit
>   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>has
>   only a 96-bit scheme.  Within each scheme, an EPC identifier can
>be
>   represented in a binary form or other forms such as URI.
>
>   The following list includes the above RFID types as well as
>various
>   other common identifiers and several different types of DUIDs.
>
>The organization of the text here seems to be poor -- section 3
>enumerates the new identifier types, but much of the text at the
>beginning of the section is about the RFID-EPC set of types.  It
>seems
>like a better organization is to use just paragraph 1 followed by
>table 1, and move paragraphs 2-5 into section 4.9.
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   including
>
>The text is using "Tag Data", "EPC", and "RFID" in a way that is
>intertwined but not explained.  I can see that it might be useful to
>use all of the terms if they commonly used in the field (don't forget
>to make them keywords for the RFC!), but you need to explain their
>connection and distinction to the reader or make it clear that the
>reader does not need to understand the differences among the terms.
>E.g., this formulation ties all three terms together
>
>   The Tag Data standard promoted by Electronic Product Code(TM)
>   (abbreviated EPC) supports several encoding systems or schemes
>   which are commonly used in RFID (radio-frequency identification)
>   applications, including
>
>--
>
>   For each RFID scheme except GID, there are two variations: a
>64-bit
>   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>has
>   only a 96-bit scheme.  Within each scheme, an EPC identifier can
>be
>   represented in a binary form or other forms such as URI.
>
>The text uses "scheme" to mean the distinction between encoding
>systems (GID, SGTIN, etc.) and and also to mean the distinction
>between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>It matters here, because you say "within each scheme ... can be
>represented in a binary form or ... URI".  Which meaning of "scheme"
>are you using here?  I thought you meant the second meaning when I
>first read the paragraph, but after reading external documents about
>EPC, I now understand that that last sentence uses "scheme" to in the
>first sense.
>
>You need to be clearer here that there are three representations
>used,
>64-bit binary, 96-bit binary, and URI (URN, actually), and
>representation is orthogonal to the seven RFID schemes, with the
>exception that RFID-GID does not have a 96-bit binary representation.
>
>I'm assuming that the Tag Data standard unambiguously defines the
>serialization of the binary representations as a sequence of octets.
>If it does not, this document MUST do that, or you will have an
>endless nightmare of byte-order problems.
>
>4.  Descriptions of MNID types
>
>Identifier ownership is a general concern -- it's worth mentioning
>for
>each type of identifier where the assigner of the identifier obtains
>delegation.  For an EUI, I expect the reader will assume that it's an
>EUI assigned to the device under IEEE rules, and similarly for RFID
>and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>I'm
>guessing that the DUID is one that is, or could be, used by the
>device
>for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>the IPv6 architecture doesn't assume that the association of
>addresses
>with devices is permanent.
>
>4.1.  Description of the IPv6 address type
>
>It would be good if the document described what the semantics of this
>ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>between that address and the device?  I suspect the connection is
>"the
>device has been configured to expect that it will be assigned this
>address as a long-term interface address", but there are other
>possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>prefix (there are plenty of them!) and then assigning addresses out
>of
>it simply to create a sequence of unique identifiers for devices, but
>not using those addresses on packets.
>
>Then again, perhaps you want to allow flexibility.  But in any case,
>I
>think you need to specify what the rules are for what address is
>associated with what device.
>
>4.2.  Description of the IMSI MNID type
>
>What does "in network order" mean here?  As far as I know, there is
>no
>defined "network order" for 4-bit quantities, only for dividing
>integers into octets and placing sequences of bits into octets.  I
>assume you mean that in any octet, the high-order 4 bits are the
>first
>digit and the low-order 4 bits are the second digit, but I think you
>need to state that explicitly.
>
>4.3.  Description of the EUI-48 address type
>
>   The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>   string containing the IEEE EUI-48 address.
>
>Is "string" the correct word, this not being a sequence of
>characters?
>I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>
>4.9.  Description of the RFID types
>
>This section needs to be revised.  It provides a lot of detail about
>the RFID types, but it's not enough detail for a reader who doesn't
>understand RFID to learn how any particular RFID scheme works.  E.g.,
>the first paragraph says that GID contains three fields in the first
>sentence, and that it contains four fields in the third sentence.
>Despite this, the description isn't enough to allow the reader to
>construct GID identifiers manually.
>
>On the other hand, readers who already understand the RFID schemes
>will find this text redundant.
>
>I think that almost all of this text can be replaced by references to
>the EPC documents, since these identifiers are opaque from the point
>of view of mobile identification.
>
>5.  Security Considerations
>
>The base MNID specification, RFC 4283, gives these security
>considerations (sec 4), which ought to be referenced and probably
>summarized in this section:
>
>   Moreover, MNIDs containing sensitive identifiers might only be
>used
>   for signaling during initial network entry.  Subsequent binding
>   update exchanges might then rely on a temporary identifier
>allocated
>   during the initial network entry, perhaps using mechanisms not
>   standardized within the IETF.  Managing the association between
>long-
>   lived and temporary identifiers is outside the scope of this
>   document.
>
>What is the meaning of the word "might" in paragraph 3?  I suspect
>that the purpose is to qualify this paragraph with "One way to
>address
>these vulnerabilities is to only use MNIDs containing ...".  But if
>that is the meaning, that expanded wording should be used.  Otherwise
>the text reads as if it is hypothetical.
>
>[END]
>
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm


From nobody Wed Feb  1 22:10:25 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0D0F1293E9; Wed,  1 Feb 2017 22:10:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.888
X-Spam-Level: 
X-Spam-Status: No, score=-5.888 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_LOW=-0.7, RCVD_IN_MSPIKE_BL=0.01, RCVD_IN_MSPIKE_L4=0.001, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tSdI3YHjkYf3; Wed,  1 Feb 2017 22:10:18 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9B541293EB; Wed,  1 Feb 2017 22:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486015817; bh=x3HXDok/hHhnrTVX8MxFMbwSR5qc/TAYBNkK DaTz6OA=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=Adjph8i HRWUukzM+PAZenxSiRoJEFlc43bMa1HkqlDDouUO/MPdOVURNH5dUTSVVgbMjmFbTBJ rxIdcBoI686HJqPukvthzIjuYVcm1GZupOJ3TYIk3LfcGfgAijAV0rtR38leIuuZtaw CrWIpE+W0qsbdXdtcuusMw+YmZxntKkWc3A+btJL8iCIIAYFfGpxLWVezbKMQuAciez RtMwc3Zcy+IA3jsPmG21scNDjVPli01/XNgK2ZCN5IAJR6tt+WBmAsMupJ/cx8fJmUt KKQCxcEzVvnIioUB4HTouqjapIzxvmCrNYZUD9I9ztdWoZC+CabM8pCI+7zHYgGT01A ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=TcBMIhJbMY+uEKw7mtmEWPKj0m3/5Y2qKUsT9+tgGvDAfKsU7bU/AKdFxcAyvUfh9cdwuMDV+D+HykCG2ZJbh0p3eR4zNCtt9fC6luKDR3dOrRqWdMiAMKsqeuoNq2dS8yv1slqAmG/grwXx/nVGSKfZtSw2C9gRalFohqfPKPSSXEbaJxkHYeEUld+9YA2jWF45i7yXqim5tpgwY/i75GAw9iAjKd/SiS8x8/ej0SSQuu8To6XmpFYFnsHEALJwkg3BgqY+pnuHu/Y3UDRKMthvjTmjoI0PloMJ6oLegvAivWHvTdHq1z7xljPobtV1gr7bWM6SQyPS3s4cxQ+Ugg==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-junco.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1cZAb1-0000v3-7i; Thu, 02 Feb 2017 01:10:15 -0500
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
To: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
Date: Wed, 1 Feb 2017 22:10:06 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D4B7FC35.258902%sgundave@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac703c35547c62c55d8cd28b8f65ed96334350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nYxD0_BtgIRpW_NkjRlYhSa3RwM>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 06:10:21 -0000

Hello Sri,

The review was indeed super.  I'll respond sometime in the next few days.

Regards,
Charlie P.


On 2/1/2017 9:09 PM, Sri Gundavelli (sgundave) wrote:
> Thank you Dale for a great review.
>
>
> Charlie/Authors - Can you please respond to Dale and address these
> comments.
>
>
> Regards
> Sri
>
>
> On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
> on behalf of worley@ariadne.com> wrote:
>
>> Reviewer: Dale Worley
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft.  The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>
>> For more information, please see the FAQ at
>> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>> Document:  draft-ietf-dmm-4283mnids-04
>> Reviewer:  Dale R. Worley
>> Review Date:  31 Jan 2017
>> IETF LC End Date:  2 Feb 2017
>> IESG Telechat date:  16 Feb 2017
>>
>> Summary:
>>
>>        This draft is on the right track but has open issues,
>> described
>>        in the review.
>>
>> Technical issues:
>>
>> 1. The Introduction states
>>
>>    Other types of identifiers are in
>>    common use, and even referenced in RFC 4283.
>>
>> For the reader's sanity, some sort of accounting needs to be made of
>> these "other types of identifiers", especially because each type of
>> identifier needs an identifier type number.  The text in 4283 is
>>
>>    Some examples of identifiers
>>    include Network Access Identifier (NAI), Fully Qualified Domain
>> Name
>>    (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>>    Subscriber Number (MSISDN).
>>
>> Are there any other types "in common use"?
>>
>> - NAI (type 1) is defined by 4283.
>> - Fully Qualified Domain Name (FQDN) seems not to be specified
>> - International Mobile Station Identifier (IMSI) (type 3) is defined
>> in
>>   this draft
>> - Mobile Subscriber Number (MSISDN) seems not to be specified
>>
>> 2. Is it intended to have an IMEI identifier type?  The introduction
>> mentions an IMEI type, but there is no specification for it, nor is
>> there an identifier type number assigned for it.
>>
>>    ... types for IMSI
>>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>> GUTI
>>    [ThreeGPP-IDS].
>>
>> Initially I suspected it was it was present in an earlier revision
>> and
>> then later deleted without this reference being updated.  But all
>> versions of draft-ietf-dmm-4283mnids and its predecessor
>> draft-perkins-dmm-4283mnids mention IMEI in this way as one
>> identifier
>> type, but none specify it in any way.  The only discussion I can find
>> on the DMM mailing list of IMEI is:
>>
>>    
>> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>> =d29575f767ce67a1e67a7767008ee6af
>>
>>     From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>>     To: DMM
>>     Date: Wed, 10 September 2014 13:29 UTC
>>     Re: [DMM] regarding the re-chartering..
>>
>>     It seems the MNID is somehow overloaded to carry both,
>> node-specific
>>     IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>>     There may be value in adding the IMEI to the list of possible
>> types of
>>     node-specific IDs.
>>
>> Either the presence of IMEI in this list is a simple mistake that has
>> persisted in all versions of the draft, or specifying IMEI has always
>> been intended but has always been overlooked.
>>
>> 3. The definition of identifier types for both EUI-48 and EUI-64
>> suggests that it might be desirable to define an identifier type for
>> arbitrary hardware (link-level) addresses.  It seems that the natural
>> differentiator for that purpose is the "hardware type" used in ARP,
>> so
>> a EUI-48 address would be represented as
>>
>>     MN identifier type (one octet) 5 (say)
>>     hardware type (two octets) 1
>>     EUI-48 (six octets)
>>
>> and an EUI-64 similarly, with hardware type 27.
>>
>> Although with only two subtypes in common use, generalizing this
>> might
>> not be worth the effort.
>>
>> 4. Several of the identifier types can be represented as URNs:
>>
>> - IMEI can be represented as a URN as urn:gsma:imei:...
>> - all of the RFID types have a URN representation (called the
>>   "pure-identity URI" in the RFID specifications), which starts
>>   urn:epc:id:...
>>
>> Since all URN types are ensured of being unique and persistent, it
>> seems that we could define a MNID type for URNs generally, and then
>> any RFID URI or an IMEI (as a URN) could be used as a value of that
>> type.
>>
>> If this idea is adopted, it seems that the other 3GPP types (IMSI,
>> P-TMSI, and GUTI) should be given defined encodings as URNs in new
>> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>> of IMEIs defined in RFC 7254.
>>
>> This consolidation could be significantly beneficial.  It allows MNID
>> to use any URN scheme as an identifier.  It reduces the three
>> different RFID representations to one.  It incorporates any future
>> expansion of RFID schemes (because all schemes will have a
>> pure-identity URN representation).  A disadvantage is that the URN
>> encodings are long, but the security considerations section states
>> that MNIDs are used only on the first registration at the home agent,
>> so there isn't much need for brevity.
>>
>> Similarly, this approach incorporates any future expansion of mobile
>> identifiers that GSMA decides to define, as long as GSMA provides a
>> URN representation for it.
>>
>> The most significant disadvantage is that some URN schemes allow
>> several character strings to "mean" the same URN.  In most URN
>> schemes, the allowed variation is limited to the case of letters, and
>> the common convention is to always use lower-case when there is a
>> choice, leading to a unique conventional canonical form for the URN.
>>
>> 5. Regarding the encoding of a string of digits into octets, it is
>> stated that "The last digit MUST be zero padded, if needed, for full
>> octet size."  This seems very unwise unless there is a 3GPP decree
>> that if a zero is appended to a valid IMSI, the resulting string is
>> never a valid IMSI.  Instead, I would specify that padding is by
>> filling the low-order 4 bits of the final octet with 0xF.  That
>> ensures that the encoding can be uniquely decoded into an IMSI.
>>
>> 6. There are four types of DUID specified, each with a distinct MNID
>> value.  However, DUIDs contain an initial two-octet type field which
>> distinguishes the various types of DUID, so providing them with
>> distinct MNID values is redundant.
>>
>> Distinguishing the types and allowing only four of them to be used as
>> MNIDs seems to be contrary to the philosophy of DUID construction
>> (RFC
>> 3315 section 9):
>>
>>    Clients and servers MUST treat DUIDs as opaque values and MUST
>> only
>>    compare DUIDs for equality.  Clients and servers MUST NOT in any
>>    other way interpret DUIDs.  Clients and servers MUST NOT restrict
>>    DUIDs to the types defined in this document, as additional DUID
>> types
>>    may be defined in the future.
>>
>> Of course, MNID isn't a DHCP operation, so it isn't subject to those
>> requirements, but I expect that devices will use the same DUID for
>> both mobile identification, and we don't want mobile identification
>> to
>> restrict future developments of DHCP.
>>
>> I think this specification must treat DUIDs as opaque and use only
>> one
>> MNID type that allows all types of DUIDs as values.
>>
>> Editorial issues:
>>
>> Abstract
>>
>>    Additional Identifier Types are proposed for use with the Mobile
>> Node
>>    Identifier Option for IPv6 (RFC 4283).
>>
>> s/proposed/defined/
>> This document will define the new types (once it is approved)!
>>
>> 1.  Introduction
>>
>>    ... types for IMSI
>>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>> GUTI
>>    [ThreeGPP-IDS].
>>
>> There is no description of P-TMSI identifiers, although it is
>> assigned
>> identifier type 4.
>>
>> There is no description of GUTI identifiers, although it is assigned
>> identifier type 7.
>>
>> 3.  New Mobile Node Identifier Types
>>
>>    The following types of identifiers are commonly used to identify
>>    mobile nodes.  For each type, references are provided with full
>>    details on the format of the type of identifier.
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    including
>>
>>    o  RFID-GID (Global Identifier),
>>    o  RFID-SGTIN (Serialized Global Trade Item Number),
>>    o  RFID-SSCC (Serial Shipping Container),
>>    o  RFID-SGLN (Global Location Number),
>>    o  RFID-GRAI (Global Returnable Asset Identifier),
>>    o  RFID-DOD (Department of Defense ID), and
>>    o  RFID-GIAI (Global Individual Asset Identifier).
>>
>>    For each RFID scheme except GID, there are two variations: a
>> 64-bit
>>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>> has
>>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>> be
>>    represented in a binary form or other forms such as URI.
>>
>>    The following list includes the above RFID types as well as
>> various
>>    other common identifiers and several different types of DUIDs.
>>
>> The organization of the text here seems to be poor -- section 3
>> enumerates the new identifier types, but much of the text at the
>> beginning of the section is about the RFID-EPC set of types.  It
>> seems
>> like a better organization is to use just paragraph 1 followed by
>> table 1, and move paragraphs 2-5 into section 4.9.
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    including
>>
>> The text is using "Tag Data", "EPC", and "RFID" in a way that is
>> intertwined but not explained.  I can see that it might be useful to
>> use all of the terms if they commonly used in the field (don't forget
>> to make them keywords for the RFC!), but you need to explain their
>> connection and distinction to the reader or make it clear that the
>> reader does not need to understand the differences among the terms.
>> E.g., this formulation ties all three terms together
>>
>>    The Tag Data standard promoted by Electronic Product Code(TM)
>>    (abbreviated EPC) supports several encoding systems or schemes
>>    which are commonly used in RFID (radio-frequency identification)
>>    applications, including
>>
>> --
>>
>>    For each RFID scheme except GID, there are two variations: a
>> 64-bit
>>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>> has
>>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>> be
>>    represented in a binary form or other forms such as URI.
>>
>> The text uses "scheme" to mean the distinction between encoding
>> systems (GID, SGTIN, etc.) and and also to mean the distinction
>> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>> It matters here, because you say "within each scheme ... can be
>> represented in a binary form or ... URI".  Which meaning of "scheme"
>> are you using here?  I thought you meant the second meaning when I
>> first read the paragraph, but after reading external documents about
>> EPC, I now understand that that last sentence uses "scheme" to in the
>> first sense.
>>
>> You need to be clearer here that there are three representations
>> used,
>> 64-bit binary, 96-bit binary, and URI (URN, actually), and
>> representation is orthogonal to the seven RFID schemes, with the
>> exception that RFID-GID does not have a 96-bit binary representation.
>>
>> I'm assuming that the Tag Data standard unambiguously defines the
>> serialization of the binary representations as a sequence of octets.
>> If it does not, this document MUST do that, or you will have an
>> endless nightmare of byte-order problems.
>>
>> 4.  Descriptions of MNID types
>>
>> Identifier ownership is a general concern -- it's worth mentioning
>> for
>> each type of identifier where the assigner of the identifier obtains
>> delegation.  For an EUI, I expect the reader will assume that it's an
>> EUI assigned to the device under IEEE rules, and similarly for RFID
>> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>> I'm
>> guessing that the DUID is one that is, or could be, used by the
>> device
>> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>> the IPv6 architecture doesn't assume that the association of
>> addresses
>> with devices is permanent.
>>
>> 4.1.  Description of the IPv6 address type
>>
>> It would be good if the document described what the semantics of this
>> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>> between that address and the device?  I suspect the connection is
>> "the
>> device has been configured to expect that it will be assigned this
>> address as a long-term interface address", but there are other
>> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>> prefix (there are plenty of them!) and then assigning addresses out
>> of
>> it simply to create a sequence of unique identifiers for devices, but
>> not using those addresses on packets.
>>
>> Then again, perhaps you want to allow flexibility.  But in any case,
>> I
>> think you need to specify what the rules are for what address is
>> associated with what device.
>>
>> 4.2.  Description of the IMSI MNID type
>>
>> What does "in network order" mean here?  As far as I know, there is
>> no
>> defined "network order" for 4-bit quantities, only for dividing
>> integers into octets and placing sequences of bits into octets.  I
>> assume you mean that in any octet, the high-order 4 bits are the
>> first
>> digit and the low-order 4 bits are the second digit, but I think you
>> need to state that explicitly.
>>
>> 4.3.  Description of the EUI-48 address type
>>
>>    The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>>    string containing the IEEE EUI-48 address.
>>
>> Is "string" the correct word, this not being a sequence of
>> characters?
>> I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>>
>> 4.9.  Description of the RFID types
>>
>> This section needs to be revised.  It provides a lot of detail about
>> the RFID types, but it's not enough detail for a reader who doesn't
>> understand RFID to learn how any particular RFID scheme works.  E.g.,
>> the first paragraph says that GID contains three fields in the first
>> sentence, and that it contains four fields in the third sentence.
>> Despite this, the description isn't enough to allow the reader to
>> construct GID identifiers manually.
>>
>> On the other hand, readers who already understand the RFID schemes
>> will find this text redundant.
>>
>> I think that almost all of this text can be replaced by references to
>> the EPC documents, since these identifiers are opaque from the point
>> of view of mobile identification.
>>
>> 5.  Security Considerations
>>
>> The base MNID specification, RFC 4283, gives these security
>> considerations (sec 4), which ought to be referenced and probably
>> summarized in this section:
>>
>>    Moreover, MNIDs containing sensitive identifiers might only be
>> used
>>    for signaling during initial network entry.  Subsequent binding
>>    update exchanges might then rely on a temporary identifier
>> allocated
>>    during the initial network entry, perhaps using mechanisms not
>>    standardized within the IETF.  Managing the association between
>> long-
>>    lived and temporary identifiers is outside the scope of this
>>    document.
>>
>> What is the meaning of the word "might" in paragraph 3?  I suspect
>> that the purpose is to qualify this paragraph with "One way to
>> address
>> these vulnerabilities is to only use MNIDs containing ...".  But if
>> that is the meaning, that expanded wording should be used.  Otherwise
>> the text reads as if it is hypothetical.
>>
>> [END]
>>
>>
>> _______________________________________________
>> dmm mailing list
>> dmm@ietf.org
>> https://www.ietf.org/mailman/listinfo/dmm
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>


From nobody Wed Feb  1 22:42:37 2017
Return-Path: <roni.even@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEA3127735; Wed,  1 Feb 2017 22:42:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level: 
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 82R8R46u_R0i; Wed,  1 Feb 2017 22:42:25 -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 2E548127078; Wed,  1 Feb 2017 22:42:24 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DFQ60273; Thu, 02 Feb 2017 06:42:20 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 2 Feb 2017 06:42:18 +0000
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by nkgeml411-hub.china.huawei.com (10.98.56.70) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 2 Feb 2017 14:42:14 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.117]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0301.000; Thu, 2 Feb 2017 14:42:10 +0800
From: Roni Even <roni.even@huawei.com>
To: tianxiang li <peter416733@gmail.com>
Subject: RE: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
Thread-Topic: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
Thread-Index: AQHSfKMEGC59Kqb/I0a0hf43svJnhaFVREvg
Date: Thu, 2 Feb 2017 06:42:09 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com> <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
In-Reply-To: <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.201.150]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5892D4CD.030D, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.117, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c1ff7e23a5fb1d24d3ae21aa07c5b874
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GncqZXihpln_cXJu3F4ZiWxajhY>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 06:42:27 -0000

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQpJIHdpbGwgbGVhdmUgb25seSB0aGUgaXRlbXMgdGhhdCBuZWVkZWQgbXkgcmVzcG9uc2UN
Cg0KNy4gICAgICBJbiBzZWN0aW9uIDMuNCDigJxJZiB0aGUgY2xpZW50IGRlY2lkZWQgdG8gdXNl
ICB0aGUgcHJlZml4IHByb3ZpZGVkDQpieSB0aGUgc2VydmVyIGRlc3BpdGUgYmVpbmcgbG9uZ2Vy
IHRoYW4gdGhlICBwcmVmaXgtbGVuZ3RoIGhpbnTigJ0geWV0IEkNCmRpZCBub3Qgc2VlIGluIHNl
Y3Rpb24gMy4yIHRoYXQgdGhlIHNlcnZlciBjYW4gcHJvdmlkZSBhIGxvbmdlcg0KcHJlZml4Lg0K
DQpbVGlhbnhpYW5nXSBUaGlzIHdhcyBtZW50aW9uZWQgaW4gdGhlIGxhc3Qgc2VudGVuY2Ugb2Yg
c2VjdGlvbiAzLjI6DQoNCiJJZiB0aGUgcmVxdWVzdGVkIHByZWZpeCBpcyBub3QgYXZhaWxhYmxl
IGluIHRoZSBzZXJ2ZXIncyBwcmVmaXggcG9vbCwgYW5kIHRoZSBjbGllbnQgYWxzbyBpbmNsdWRl
ZCBhIHByZWZpeC1sZW5ndGggaGludCBpbiB0aGUgc2FtZSBJQV9QRCBvcHRpb24sIHRoZW4gdGhl
IHNlcnZlciBTSE9VTEQgdHJ5IHRvIHByb3ZpZGUgYSBwcmVmaXggbWF0Y2hpbmcgdGhlIHByZWZp
eC1sZW5ndGggdmFsdWUsIG9yIHRoZSBwcmVmaXggd2l0aCB0aGUgc2hvcnRlc3QgbGVuZ3RoIHBv
c3NpYmxlIHdoaWNoIGlzIGNsb3Nlc3QgdG8gdGhlIHByZWZpeC1sZW5ndGggaGludCB2YWx1ZS4i
DQpbUm9uaSBFdmVuXSBJIHVuZGVyc3Rvb2QgZnJvbSAzLjIgdGhhdCBpdCBzaG91bGQgcHJvdmlk
ZSBhIHNob3J0ZXIgbGVuZ3RoIHByZWZpeCAgY2xvc2VyIHRvIHRoZSByZXF1ZXN0IG1heWJlIOKA
nG9yIHRoZSBwcmVmaXggd2l0aCB0aGUgY2xvc2VzdCBwb3NzaWJsZSBsZW5ndGggdG8gdGhlIHBy
ZWZpeC1sZW5ndGggaGludCB2YWx1ZeKAnQ0KDQpbVGlhbnhpYW5nMl0gVGhlIG9yaWdpbmFsIHNl
bnRlbmNlIHdhcyBhIGJpdCBjb25mdXNpbmcsIHBlcmhhcHMgd2UgY291bGQgY2hhbmdlIGl0IGxp
a2UgdGhpczoNCg0KT0xEOiAiSWYgdGhlIHJlcXVlc3RlZCBwcmVmaXggaXMgbm90IGF2YWlsYWJs
ZSBpbiB0aGUgc2VydmVyJ3MgcHJlZml4IHBvb2wsIGFuZCB0aGUgY2xpZW50IGFsc28gaW5jbHVk
ZWQgYSBwcmVmaXgtbGVuZ3RoIGhpbnQgaW4gdGhlIHNhbWUgSUFfUEQgb3B0aW9uLCB0aGVuIHRo
ZSBzZXJ2ZXIgU0hPVUxEIHRyeSB0byBwcm92aWRlIGEgcHJlZml4IG1hdGNoaW5nIHRoZSBwcmVm
aXgtbGVuZ3RoIHZhbHVlLCBvciB0aGUgcHJlZml4IHdpdGggdGhlIHNob3J0ZXN0IGxlbmd0aCBw
b3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUu
Ig0KDQpORVc6IklmIHRoZSByZXF1ZXN0ZWQgcHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhl
IHNlcnZlcidzIHByZWZpeCBwb29sLCBhbmQgdGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJl
Zml4LWxlbmd0aCBoaW50IGluIHRoZSBzYW1lIElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVy
IFNIT1VMRCBwcm92aWRlIGEgcHJlZml4IG1hdGNoaW5nIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQs
IG9yIGEgcHJlZml4IHdoaWNoIGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBw
b3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5v
dCBwcm92aWRlIGEgcHJlZml4IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRo
ZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZp
eCB3aGljaCBsZW5ndGggaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUg
cHJlZml4LWxlbmd0aCBoaW50LiINCg0KW1JvbmkgRXZlbl0gSSBoYXZlIG5vIHByb2JsZW0gd2l0
aCB0aGlzIHRleHQgc2luY2UgaXQgd2lsbCBhbHNvIHdvcmsgd2l0aCB0aGUgcmVzdCBvZiB0aGUg
ZG9jdW1lbnQgYnV0IGlzIGl0IHdoYXQgd2FzIHJlYWxseSBtZWFudA0KDQpBbHNvIGEgbml0DQoN
CuKAnG9yIGEgcHJlZml4IHdoaWNoIGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBh
cyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxk
IG5vdCBwcm92aWRlIGEgcHJlZml4IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRv
IHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHBy
ZWZpeCB3aGljaCBsZW5ndGggaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0
aGUgcHJlZml4LWxlbmd0aCBoaW504oCdDQoNCnRvDQoNCuKAnG9yIGEgcHJlZml4IHdob3NlIGxl
bmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxl
bmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4IHdpdGgg
YSBzaG9ydGVyIG9yIGVxdWFsIGxlbmd0aCAgdG8gdGhlIHByZWZpeC1sZW5ndGggaGludCwgdGhl
IHNlcnZlciBTSE9VTEQgcHJvdmlkZSBhIHByZWZpeCB3aG9zZSBsZW5ndGggaXMgbG9uZ2VyIGFu
ZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxlbmd0aCBoaW504oCdDQoNCg0K
W1RpYW54aWFuZ10gVGhlIGlkZWEgd2FzIHRvIGxpc3QgYWxsIHRoZSBvcHRpb25zLCBhbmQgZGlz
Y3VzcyB0aGVpciBjb25zZXF1ZW5jZXMuIEFuZCB0aGUgc2VydmVyIGNvdWxkIGRlY2lkZSB3aGlj
aCBvcHRpb24gdG8gdXNlIGRlcGVuZGluZyBvbiBpdHMgcG9saWN5Lg0KDQpPcHRpb24gMyBhdm9p
ZHMgdGhlIGNvbXBsZXhpdHkgb2YgaGFuZGxpbmcgbXVsdGlwbGUgZGVsZWdhdGVkIHByZWZpeGVz
LCBkZXNwaXRlIG9mIGJyZWFraW5nIHVwIGFsbCBjb25uZWN0aW9ucy4gT3B0aW9uIDQgYWxsb3dz
IHRvIHNlcnZlciB0byBjb25maWd1cmUgYSB2YWxpZC1saWZldGltZSBmb3IgdGhlIG9sZCBwcmVm
aXggZGVwZW5kaW5nIG9uIGFjdHVhbCByZXF1aXJlbWVudHMsIHJhdGhlciB0aGFuIGxldCB0aGUg
b2xkIHByZWZpeCBleHBpcmUgb24gaXRzIG93bi4NCltSb25pIEV2ZW5dIE9LLCBzdGlsbCBvcHRp
b24gNCBtYXkgaGF2ZSBzaW1pbGFyIHJlc3VsdCB0byAzIHNpbmNlIOKAnGEgc2hvcnQgbm9uLXpl
cm/igJ0gbWF5IGJlIHRvbyBzaG9ydC4gV2h5IG5vdCBhZGQgYSByZWNvbW1lbmRlZCB2YWx1ZT8N
Cg0KW1RpYW54aWFuZzJdIEFncmVlLCBhcyB0aGlzIG1heSB2YXJ5IGZvciBkaWZmZXJlbnQgc2Vy
dmljZXMsIHdlIGNvdWxkIGNoYW5nZSB0aGUgdGV4dCB0byBzYXkgImEgc3BlY2lmaWMgdmFsaWQt
bGlmZXRpbWUgZGVwZW5kaW5nIG9uIHRoZSBhY3R1YWwgcmVxdWlyZW1lbnQiLg0KW1JvbmkgRXZl
bl0gT0sNCg0KDQoNCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQoNCg0KDQo=

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IkJhbGxvb24gVGV4dCBDaGFyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206
LjAwMDFwdDsNCglmb250LXNpemU6OC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRhaG9tYSIsInNhbnMt
c2VyaWYiO30NCnNwYW4ubS02MDYwNzI2OTc5NTM2MDAzMTE5Z21haWwtbS02NTI0ODAyMTEyMjA3
MDQ5MjQ2Z21haWwtDQoJe21zby1zdHlsZS1uYW1lOm1fLTYwNjA3MjY5Nzk1MzYwMDMxMTlnbWFp
bC1tXy02NTI0ODAyMTEyMjA3MDQ5MjQ2Z21haWwtO30NCnNwYW4uQmFsbG9vblRleHRDaGFyDQoJ
e21zby1zdHlsZS1uYW1lOiJCYWxsb29uIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJCYWxsb29uIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJUYWhv
bWEiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpw
ZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMtc2VyaWYiOw0KCWNv
bG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9u
bHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpAcGFnZSBXb3JkU2Vj
dGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIu
MHB0IDcyLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0t
Pjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0
PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4
dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4N
CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SGksPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPkkgd2lsbCBsZWF2ZSBvbmx5IHRoZSBpdGVtcyB0aGF0IG5lZWRlZCBteSBy
ZXNwb25zZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
JnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0Mg
MS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4t
cmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206
NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj43LiZuYnNwOyAmbmJzcDsgJm5ic3A7IElu
IHNlY3Rpb24gMy40IOKAnElmIHRoZSBjbGllbnQgZGVjaWRlZCB0byB1c2UmbmJzcDsgdGhlIHBy
ZWZpeCBwcm92aWRlZDxicj4NCmJ5IHRoZSBzZXJ2ZXIgZGVzcGl0ZSBiZWluZyBsb25nZXIgdGhh
biB0aGUmbmJzcDsgcHJlZml4LWxlbmd0aCBoaW504oCdIHlldCBJPGJyPg0KZGlkIG5vdCBzZWUg
aW4gc2VjdGlvbiAzLjIgdGhhdCB0aGUgc2VydmVyIGNhbiBwcm92aWRlIGEgbG9uZ2VyPGJyPg0K
cHJlZml4LjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPltUaWFueGlhbmddIFRoaXMgd2FzIG1lbnRpb25lZCBpbiB0aGUgbGFz
dCBzZW50ZW5jZSBvZiBzZWN0aW9uIDMuMjombmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZxdW90O0lmIHRoZSByZXF1ZXN0ZWQg
cHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhlIHNlcnZlcidzIHByZWZpeCBwb29sLCBhbmQg
dGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJlZml4LWxlbmd0aCBoaW50IGluIHRoZSBzYW1l
IElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVyIFNIT1VMRCB0cnkgdG8NCiBwcm92aWRlIGEg
cHJlZml4IG1hdGNoaW5nIHRoZSBwcmVmaXgtbGVuZ3RoIHZhbHVlLCBvciB0aGUgcHJlZml4IHdp
dGggdGhlIHNob3J0ZXN0IGxlbmd0aCBwb3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0IHRvIHRoZSBw
cmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxiPjxpPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5bUm9uaSBFdmVuXSBJIHVuZGVyc3Rvb2QgZnJvbSAzLjIgdGhhdCBpdCBzaG91bGQgcHJv
dmlkZSBhIHNob3J0ZXIgbGVuZ3RoIHByZWZpeCAmbmJzcDtjbG9zZXIgdG8NCiB0aGUgcmVxdWVz
dCBtYXliZSDigJw8L3NwYW4+PC9pPjwvYj5vciB0aGUgcHJlZml4IHdpdGggdGhlIGNsb3Nlc3Qg
cG9zc2libGUgbGVuZ3RoIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWXigJ08bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5b
VGlhbnhpYW5nMl0gVGhlIG9yaWdpbmFsIHNlbnRlbmNlIHdhcyBhIGJpdCBjb25mdXNpbmcsIHBl
cmhhcHMgd2UgY291bGQgY2hhbmdlIGl0IGxpa2UgdGhpczo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T0xEOiZuYnNwOyZxdW90O0lmIHRoZSBy
ZXF1ZXN0ZWQgcHJlZml4IGlzIG5vdCBhdmFpbGFibGUgaW4gdGhlIHNlcnZlcidzIHByZWZpeCBw
b29sLCBhbmQgdGhlIGNsaWVudCBhbHNvIGluY2x1ZGVkIGEgcHJlZml4LWxlbmd0aCBoaW50IGlu
IHRoZSBzYW1lIElBX1BEIG9wdGlvbiwgdGhlbiB0aGUgc2VydmVyIFNIT1VMRCB0cnkgdG8gcHJv
dmlkZSBhIHByZWZpeCBtYXRjaGluZyB0aGUgcHJlZml4LWxlbmd0aCB2YWx1ZSwgb3INCiB0aGUg
cHJlZml4IHdpdGggdGhlIHNob3J0ZXN0IGxlbmd0aCBwb3NzaWJsZSB3aGljaCBpcyBjbG9zZXN0
IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQgdmFsdWUuJnF1b3Q7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5FVzomcXVvdDtJZiB0aGUgcmVx
dWVzdGVkIHByZWZpeCBpcyBub3QgYXZhaWxhYmxlIGluIHRoZSBzZXJ2ZXIncyBwcmVmaXggcG9v
bCwgYW5kIHRoZSBjbGllbnQgYWxzbyBpbmNsdWRlZCBhIHByZWZpeC1sZW5ndGggaGludCBpbiB0
aGUgc2FtZSBJQV9QRCBvcHRpb24sIHRoZW4gdGhlIHNlcnZlciBTSE9VTEQgcHJvdmlkZSBhIHBy
ZWZpeCBtYXRjaGluZyB0aGUgcHJlZml4LWxlbmd0aCBoaW50LCBvciBhIHByZWZpeA0KIHdoaWNo
IGlzIGxlbmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJl
Zml4LWxlbmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4
IHdoaWNoIGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhp
bnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZpeCB3aGljaCBsZW5ndGggaXMg
bG9uZ2VyIGFuZCBhcyBjbG9zZSBhcw0KIHBvc3NpYmxlIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhp
bnQuJnF1b3Q7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9pPjwvYj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+W1JvbmkgRXZlbl0gSSBoYXZlIG5vIHBy
b2JsZW0gd2l0aCB0aGlzIHRleHQgc2luY2UgaXQgd2lsbCBhbHNvIHdvcmsgd2l0aCB0aGUgcmVz
dCBvZiB0aGUgZG9jdW1lbnQgYnV0IGlzIGl0IHdoYXQgd2FzIHJlYWxseSBtZWFudDxvOnA+PC9v
OnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvaT48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PGk+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtz
YW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFsc28gYSBuaXQ8bzpwPjwvbzpwPjwvc3Bh
bj48L2k+PC9iPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxpPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fu
cy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L2k+
PC9iPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPuKAnG9yIGEgcHJlZml4IHdoaWNoIGlzIGxl
bmd0aCBpcyBzaG9ydGVyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJlZml4LWxl
bmd0aCBoaW50LiBJZiB0aGUgc2VydmVyIGNvdWxkIG5vdCBwcm92aWRlIGEgcHJlZml4IHdoaWNo
IGxlbmd0aCBpcyBzaG9ydGVyIG9yIGVxdWFsIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQsIHRo
ZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgdGhlIHByZWZpeCB3aGljaA0KIGxlbmd0aCBpcyBsb25n
ZXIgYW5kIGFzIGNsb3NlIGFzIHBvc3NpYmxlIHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnTigJ08
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+dG88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+4oCcb3Ig
YSBwcmVmaXggd2hvc2UgbGVuZ3RoIGlzIHNob3J0ZXIgYW5kIGFzIGNsb3NlIGFzIHBvc3NpYmxl
IHRvIHRoZSBwcmVmaXgtbGVuZ3RoIGhpbnQuIElmIHRoZSBzZXJ2ZXIgY291bGQgbm90IHByb3Zp
ZGUgYSBwcmVmaXggd2l0aCBhIHNob3J0ZXIgb3IgZXF1YWwgbGVuZ3RoICZuYnNwO3RvIHRoZSBw
cmVmaXgtbGVuZ3RoIGhpbnQsIHRoZSBzZXJ2ZXIgU0hPVUxEIHByb3ZpZGUgYSBwcmVmaXggd2hv
c2UgbGVuZ3RoDQogaXMgbG9uZ2VyIGFuZCBhcyBjbG9zZSBhcyBwb3NzaWJsZSB0byB0aGUgcHJl
Zml4LWxlbmd0aCBoaW504oCdPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAw
Y20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEu
NXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPltUaWFueGlhbmddIFRoZSBpZGVhIHdhcyB0
byBsaXN0IGFsbCB0aGUgb3B0aW9ucywgYW5kIGRpc2N1c3MgdGhlaXIgY29uc2VxdWVuY2VzLiBB
bmQgdGhlIHNlcnZlciBjb3VsZCBkZWNpZGUgd2hpY2ggb3B0aW9uIHRvIHVzZSBkZXBlbmRpbmcg
b24gaXRzIHBvbGljeS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPk9wdGlvbiAzIGF2b2lkcyB0aGUgY29tcGxleGl0eSBvZiBo
YW5kbGluZyBtdWx0aXBsZSBkZWxlZ2F0ZWQgcHJlZml4ZXMsIGRlc3BpdGUgb2YgYnJlYWtpbmcg
dXAgYWxsIGNvbm5lY3Rpb25zLiBPcHRpb24gNCBhbGxvd3MgdG8gc2VydmVyIHRvIGNvbmZpZ3Vy
ZSBhIHZhbGlkLWxpZmV0aW1lIGZvciB0aGUgb2xkDQogcHJlZml4IGRlcGVuZGluZyBvbiBhY3R1
YWwgcmVxdWlyZW1lbnRzLCByYXRoZXIgdGhhbiBsZXQgdGhlIG9sZCBwcmVmaXggZXhwaXJlIG9u
IGl0cyBvd24uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPjxpPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5bUm9uaSBFdmVuXSBPSywg
c3RpbGwgb3B0aW9uIDQgbWF5IGhhdmUgc2ltaWxhciByZXN1bHQgdG8gMyBzaW5jZSDigJxhIHNo
b3J0IG5vbi16ZXJv4oCdIG1heSBiZQ0KIHRvbyBzaG9ydC4gV2h5IG5vdCBhZGQgYSByZWNvbW1l
bmRlZCB2YWx1ZT88L3NwYW4+PC9pPjwvYj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5bVGlhbnhpYW5nMl0gQWdyZWUsIGFzIHRoaXMgbWF5IHZhcnkgZm9y
IGRpZmZlcmVudCBzZXJ2aWNlcywgd2UgY291bGQgY2hhbmdlIHRoZSB0ZXh0IHRvIHNheSAmcXVv
dDthIHNwZWNpZmljIHZhbGlkLWxpZmV0aW1lIGRlcGVuZGluZyBvbiB0aGUgYWN0dWFsIHJlcXVp
cmVtZW50JnF1b3Q7LiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPltSb25pIEV2
ZW5dIE9LPC9zcGFuPjwvaT48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMx
RjQ5N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1i
b3R0b206MTIuMHB0Ij48YnI+DQo8YnI+DQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czo8YnI+DQo8
YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_6E58094ECC8D8344914996DAD28F1CCD771622DGGEMM506MBXchina_--


From nobody Thu Feb  2 01:15:19 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C482A120727; Thu,  2 Feb 2017 01:15: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 hSDtRUYavCo0; Thu,  2 Feb 2017 01:15: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 A58D21293F2; Thu,  2 Feb 2017 01:15:10 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 73D7E83627; Thu,  2 Feb 2017 10:15:06 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: ietf@ietf.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <6a4a3d23-b594-342c-ad83-678a58f0969a@si6networks.com>
Date: Thu, 2 Feb 2017 05:31:11 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qt0M2biTX5IeSuhKhbw8U3Bgiy4>
Cc: draft-ietf-6man-rfc1981bis@tools.ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 09:15:14 -0000

Folks,

I just read through this document and it looks ready to move forward,
modulo this:

* In the Security Considerations section, it says:
"  In the first attack, the false message indicates a PMTU much smaller
   than reality.  This should not entirely stop data flow, since the
   victim node should never set its PMTU estimate below the IPv6 minimum
   link MTU.  It will, however, result in suboptimal performance."

This is not really correct. If the node was employing extension headers
(e.g., lots of Destionation Options), then this actually could actually
stop the data flow. -- Yes, such a scenario doesn't happen in practice,
but, according to the specs is possible.


* In the same section, this paragraph:
"  In the second attack, the false message indicates a PMTU larger than
   reality.  If believed, this could cause temporary blockage as the
   victim sends packets that will be dropped by some router.  Within one
   round-trip time, the node would discover its mistake (receiving
   Packet Too Big messages from that router), but frequent repetition of
   this attack could cause lots of packets to be dropped.  A node,
   however, should never raise its estimate of the PMTU based on a
   Packet Too Big message, so should not be vulnerable to this attack."

Should probably be simplified to:
"  In the second attack, the false message indicates a PMTU larger than
   reality.  If believed, this could cause temporary blockage as the
   victim sends packets that will be dropped by some router. A node,
   however, should never raise its estimate of the PMTU based on a
   Packet Too Big message, so should not be vulnerable to this attack."


* In the same section, a reference to RFC5927 might be useful, since it
expands on PMTU attacks and also describes what some implementations do
to mitigate these attacks.

* Finally, given the work in RFC8021, RFC7915, and rfc2460bis, I think
it would be sensible for this document to note, somewhere, that ICMPv6
PTB messages advertising an MTU smaller than 1280 bytes should be
silently dropped.

Thanks!

Best regards,
Fernando




On 02/01/2017 08:52 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Path MTU Discovery for IP version 6'
>   <draft-ietf-6man-rfc1981bis-04.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document describes Path MTU Discovery for IP version 6.  It is
>    largely derived from RFC 1191, which describes Path MTU Discovery for
>    IP version 4.  It obsoletes RFC1981.
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc1981bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc1981bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information: 
>     rfc4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard - IETF stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
> 
> 
> --------------------------------------------------------------------
> 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 Thu Feb  2 01:15:30 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB605129624; Thu,  2 Feb 2017 01:15:17 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 YaI0-0h5QuQH; Thu,  2 Feb 2017 01:15: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 79A92129434; Thu,  2 Feb 2017 01:15:16 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 ECC1283621; Thu,  2 Feb 2017 10:15:12 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <504df145-2c28-7954-08e1-c53dced38e5d@si6networks.com>
Date: Thu, 2 Feb 2017 05:41:13 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4APvX_pKd3v8h-6o8B540NHE4rA>
Cc: 6man-chairs@ietf.org, ipv6@ietf.org, draft-ietf-6man-rfc4291bis@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 09:15:18 -0000

Folks,

Some comments:

* Section 4 (Sec Cons) says:
"  IPv6 addresses can
   be created using interface identifiers constructed with unique stable
   tokens.  The addresses created in this manner can be used to track
   the movement of devices across the Internet."

here you meant "constant", rather than stable. Constant IIDs (as
resulting from embedding constant MAC addresses in the IID) allow for
tracking devices across the Internet. Stable IIDs (as resulting from
RFC7217) do not.

Thanks,
Fernando




On 02/01/2017 08:51 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'IP Version 6 Addressing Architecture'
>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This specification defines the addressing architecture of the IP
>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
>    model, text representations of IPv6 addresses, definition of IPv6
>    unicast addresses, anycast addresses, and multicast addresses, and an
>    IPv6 node's required addresses.
> 
>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>    Architecture".
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> 
> 
> --------------------------------------------------------------------
> 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 Thu Feb  2 01:15:49 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E270129648; Thu,  2 Feb 2017 01:15:31 -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 autolearn_force=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 NXgrEni1btb9; Thu,  2 Feb 2017 01:15:29 -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 121B512963C; Thu,  2 Feb 2017 01:15:26 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 EED1783629; Thu,  2 Feb 2017 10:15:18 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com>
Date: Thu, 2 Feb 2017 06:14:46 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZCb-vxQ6AsjveevcXAA_jdTtjSY>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 09:15:31 -0000

Folks,

Some comments:


*  Section 4.8 ("Defining New Extension Headers and Options")

Specification of new EHs would bring problems. And, for instance,
recommending a specific format for new EHs does not really help.

A key problem with the Uniform Format for IPv6 Extension Headers
described in this section (originally specified in RFC6564) lies in that
both IPv6 Extension Headers and Transport Protocols share the same "Next
Header" registry/namespace.  Thus, given an "unknown Next Header value",
it is impossible to tell whether the aforementioned value refers to an
IPv6 Extension Header that employs the aforementioned uniform format, or
an "unknown" upper-layer protocol (e.g. an "unknown" transport
protocol).  That is, while this document (and RFC6564) specifies the
syntax for a Uniform Format for IPv6 Extension Headers, it does not
provide a mechanism for a node to identify whether the aforementioned
format is being employed in the first place.

The current impossibility to parse an IPv6 header chain that includes
unknown Next Header values results in concrete implications for the
extensibility of the IPv6 protocol, and the deployability of new
transport protocols.  Namely,

 o  New IPv6 extension headers cannot be incrementally deployed.

 o  New transport protocols cannot be incrementally deployed.


We've elaborated on this topic in draft-gont-6man-rfc6564bis. One
possible way to address this problem is simply to ban the specification
of new EHs. Another is to d something along the lines of
draft-gont-6man-rfc6564bis. However, the current text seems misleading
-- for instance as is, it doesn't buy much to have a "unified format"
for new EHs, since you don't really know how to parse that EH in the
first place.


* Section 3:

Regarding the "version" field, it might be useful to note that it should
be checked that, upon receipt of a packet, it is actually 6. It
shouldn't matter, but in practice, it might. Please see:
<http://blog.si6networks.com/2016/02/quiz-weird-ipv6-traffic-on-local-network.html>
for a real-world scenario.


* Security Considerations section

I think the security considerations section should be augmented.

For example, the Extension Headers have been known to be useful for the
evasion of security controls. While in theory this need not be the case,
in practice it is.


* Appendix B ("CHANGES SINCE RFC2460")

I think this section should summarize the changes since RFC2460 but
*not* on a "per I-D version basis". That is, "as is", it is hard to
figure out what has changed since RFC2460.

Thanks!

Best regards,
Fernando




On 02/01/2017 08:49 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Internet Protocol, Version 6 (IPv6) Specification'
>   <draft-ietf-6man-rfc2460bis-08.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies version 6 of the Internet Protocol (IPv6).
>    It obsoletes RFC2460
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information: 
>     rfc4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard - IETF stream)
>     rfc3168: The Addition of Explicit Congestion Notification (ECN) to IP (Proposed Standard - IETF stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
> 
> 
> --------------------------------------------------------------------
> 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 Thu Feb  2 01:38:30 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A0AB127078; Thu,  2 Feb 2017 01:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.12
X-Spam-Level: 
X-Spam-Status: No, score=-10.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fLhWNrXIt3RV; Thu,  2 Feb 2017 01:38:25 -0800 (PST)
Received: from mx142.netapp.com (mx142.netapp.com [216.240.21.19]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2F6F1293E4; Thu,  2 Feb 2017 01:38:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,323,1477983600";  d="asc'?scan'208";a="168855953"
Received: from vmwexchts03-prd.hq.netapp.com ([10.122.105.31]) by mx142-out.netapp.com with ESMTP; 02 Feb 2017 01:30:35 -0800
Received: from VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) by VMWEXCHTS03-PRD.hq.netapp.com (10.122.105.31) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 2 Feb 2017 01:37:14 -0800
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Thu, 2 Feb 2017 01:37:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=fdruvhxcodu8xWw4CLJ7ZCjR1NTNXXUfuxgankvsGxA=; b=RRfctlqeI+KmYtitoNEDXusk+PaZGpoNvT01wFwy0BEBBFzLxF3P+Wrrc7EVZRibeCEuu5qgFWSkLfJSuAkpmzDUn670L/OcLBKqCDu1qmI8OD1Dyyuue6E25drVM6IjOzvAWAW3J7LGt4u+oxXx4mJESOAyuK4ks9yITe7Al88=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1154.namprd06.prod.outlook.com (10.160.157.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Thu, 2 Feb 2017 09:37:16 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.024; Thu, 2 Feb 2017 09:37:16 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOA
Date: Thu, 2 Feb 2017 09:37:16 +0000
Message-ID: <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com>
In-Reply-To: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: 97d642a3-4512-49d7-3fe6-08d44b4f1370
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1154; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1154; 7:iFbZ4Tp5PXs9FB6A41n297PsdJ9Jlhlnpypfgqm3q+4F4etS+EqJzvWMX5LYKX1c/xAu+mthzBIPAKcAGoyJ0X1+pjTBxu99gIQqbhybaq+iwXFag/WvcCBSr/heS53yDo2cV71qJkgwgrpZcubpN8kmPtMMFtCxsQcSROfcApDvvDxJg16cVcFD+T95boCurqdYlg+7zsr97wO2+aYnQHLi4ZfNA5IsrvLjst8g8bw7nZXlsjcSuQXrIvefLs/mkAgWqhoQFUjaca7JsmPbunCgHCKBRRKcdeViWcp9G4zosJNl1Lmmf6y52O+dhQNREafkw1Wm3NHrMvFNnsZC35rC24jSOzDALAfV1vb3nSig1ckk4/T3UxxhkYnwj6+yNiYFlUWdZRCnHUtUAl7fxKFRb/L1LMj5EosdEENAz8RU+cFX5pYYGDFLk0iczIZosmM5r8Iixd/W3mBQnI0gAlMfJZ/0/Zf+kM/OO5otQ/CT1w3xsZvOvZ3TN1dIf9kTc11y/pvyNEZUlCHogT2DYeaNuXiZ9bRDrjGX9TeMOysOYSX4uXb0YyZsnlpPjVS4
x-microsoft-antispam-prvs: <BN3PR0601MB11547CBA10DD5287D821B272A74C0@BN3PR0601MB1154.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(6072148); SRVR:BN3PR0601MB1154; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1154; 
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(199003)(99936001)(305945005)(5660300001)(50986999)(229853002)(7736002)(76176999)(2906002)(6436002)(106116001)(106356001)(105586002)(6506006)(77096006)(189998001)(5640700003)(25786008)(33656002)(230783001)(122556002)(54906002)(3280700002)(101416001)(2351001)(97736004)(6486002)(6512007)(86362001)(99286003)(81166006)(81156014)(1730700003)(8676002)(68736007)(8936002)(2501003)(82746002)(38730400001)(57306001)(83716003)(92566002)(66066001)(50226002)(36756003)(3846002)(102836003)(6116002)(110136003)(2950100002)(3660700001)(4326007)(6916009)(53936002)(2900100001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1154; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_5B28CAC1-2224-438D-B823-71DDFFAF63CA"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Feb 2017 09:37:16.5768 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1154
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5TKW-P-5a8-16mqEyIrFDK1byQo>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "otroan@employees.org" <otroan@employees.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 09:38:26 -0000

--Apple-Mail=_5B28CAC1-2224-438D-B823-71DDFFAF63CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

the last paragraph of the introduction reads:

   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 over paths where delivery of
   ICMP messages to a host is not assured.

Given that ICMP delivery cannot be assured over the vast majority of =
paths in the current Internet, should this document make a =
recommendation to implement RFC4821?

Also, even if ICMP delivery is assured, there are additional =
complications for UDP, which has been seeing a lot of interest both as a =
tunneling encapsulation and for applications (e.g., QUIC). Many =
platforms do not provide UDP-sending applications any information about =
arriving ICMP messages that were triggered by their transmissions. So =
even if the path delivers ICMP, the OS makes ICMP-based PMTUD for UDP =
often impossible. Another reason to recommend 4821?

Lars

--Apple-Mail=_5B28CAC1-2224-438D-B823-71DDFFAF63CA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYkv3LAAoJEFS1wwm/cMFXRvAQALQU/vJswPUs46lxSUVrr43m
9Wfu/sctgqGJcvKDM3k5/EMspqc7md7meBavbmMqwz9DwQuSsPO4iZHrBF6246ZD
gk6nQ3eM4XBIcpaCuiUpkxLFyB9aBHjApO+u6FID/dDJLhG2WIvNA7e5NyMjo94v
KTqWpQXVCBhLAHxlgvB/4v0C7K8GTpfhgWB9m02aX+sd7HvxdCGNhDtGuJ9H8sAt
G+PnCtWPj1NI9lyZ9G8iemYhQPcP6+qRF3YcXF3i24n+qYNteYCPCZWlWaAiguMc
bZqJ4wQPhHP0p/FrixV1HP+5cxZWRLQRrO78s4K6isUFC4ETOsIQKv7w7ltm0k7R
6mv/6BYnZhokBr7NhXAzfAI6gOE4ZnHrEvc/fZdbWpVvtWpxCf16Dvt6wKgIaywP
6DnrfORu4mzaNxJRAsMstcbYKztohcoKt9536/ItOYX7V6cQI4m+OO5L+FF0BPZV
af5Sk30vaSYOu47Dr7tnZ4yVEBzODvJsFOax42QycCq91BJQimKrDAkvdsDAjVN6
Gtpt6reM7UTexR1xDo5bsqY9d0NXYenc1biu1ydEMI59sveQFVD0it1FaLgxx3H7
qJXVxRl4flvYChXYnym+OujorTMbnnsbBc1ZAu7w3Xrh8JaCYJ0X4os3T5EaingD
Y1m41HnEevq5/eWuSB4n
=BgGh
-----END PGP SIGNATURE-----

--Apple-Mail=_5B28CAC1-2224-438D-B823-71DDFFAF63CA--


From nobody Thu Feb  2 02:17:03 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B698B129437; Thu,  2 Feb 2017 02:16:57 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 Gbk0VQYzUp0t; Thu,  2 Feb 2017 02:16:53 -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 DB784129422; Thu,  2 Feb 2017 02:16:52 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 EAA2782BA4; Thu,  2 Feb 2017 11:16:46 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: "Eggert, Lars" <lars@netapp.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com>
Date: Thu, 2 Feb 2017 06:54:16 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3jAS_7nQn_RYggE5Xo2oSdXJKNw>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 10:16:58 -0000

Hi, Lars,

On 02/02/2017 06:37 AM, Eggert, Lars wrote:
> Hi,
> 
> the last paragraph of the introduction reads:
> 
> 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 over paths where
> delivery of ICMP messages to a host is not assured.
> 
> Given that ICMP delivery cannot be assured over the vast majority of
> paths in the current Internet, should this document make a
> recommendation to implement RFC4821?

I think that RFC4821 should be recommended, at least for dealing with
ICMP blackholes (i.e., use ICMP if you can, but be able to deal with
scenarios in which you don't receive them).


> Also, even if ICMP delivery is assured, there are additional
> complications for UDP, which has been seeing a lot of interest both
> as a tunneling encapsulation and for applications (e.g., QUIC). Many
> platforms do not provide UDP-sending applications any information
> about arriving ICMP messages that were triggered by their
> transmissions. So even if the path delivers ICMP, the OS makes
> ICMP-based PMTUD for UDP often impossible. Another reason to
> recommend 4821?

Agreed... although in this case this would be more of an app-layer
implementation than one at the transport layer?

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  2 02:22:51 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 317C1129404; Thu,  2 Feb 2017 02:22:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.12
X-Spam-Level: 
X-Spam-Status: No, score=-10.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kSepwes-_K1; Thu,  2 Feb 2017 02:22:40 -0800 (PST)
Received: from mx142.netapp.com (mx142.netapp.com [216.240.21.19]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FFA8127076; Thu,  2 Feb 2017 02:22:40 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,323,1477983600";  d="asc'?scan'208";a="168860564"
Received: from hioexcmbx01-prd.hq.netapp.com ([10.122.105.34]) by mx142-out.netapp.com with ESMTP; 02 Feb 2017 02:14:54 -0800
Received: from VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) by hioexcmbx01-prd.hq.netapp.com (10.122.105.34) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 2 Feb 2017 02:21:33 -0800
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Thu, 2 Feb 2017 02:21:33 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=xX9VijNbEq73c6GysNBXq/mYueK82/S/jHicfwutXK8=; b=RBF2OxuOsoHDTmxMRuc8D7pFIaxS6sfTskKqYpqk8VCIurQm9wTvcdDWR33ZaazPpE2Jjo3qYbZzbKauR7IhOs62ZIpzV1BM5I5/pFGz2XkXHOVJWYSGJTQpZK0DbOAZPUSLVhk7P+blvAA4v2xpxeRnDMl+rmJaz53Ud9nvxRA=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1154.namprd06.prod.outlook.com (10.160.157.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Thu, 2 Feb 2017 10:21:35 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.024; Thu, 2 Feb 2017 10:21:35 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAAEwQCAAAefgA==
Date: Thu, 2 Feb 2017 10:21:35 +0000
Message-ID: <5C876EB6-F2B6-4F2C-9A6B-2AC63D0115D3@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com>
In-Reply-To: <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: cbd9d015-3a34-4d58-65b4-08d44b55440c
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1154; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1154; 7:sUdlk7cI2jQ2ysThsmfR/M89SeVLgfQIA6pdwLwWHC7oAS9GIzpfZx46z+bydLMSvMVkDWyqNlbGWzI6imjD5apQloCrKHjzpJYIqddCfHAXF1USOwGU4h9qEAGOJtqS6qV4O5n6YGgn0pGbBynIMiAxSdjEtQToRZVdfWbJ8xNmEMBksSlAOwlFwcKWaDlVyFH/CcKJiCU4ehf6vRoFraaAfRioNBernDZvndNLUFrudd0sCrVZ46qFO+2d0/qB6EWik/jy46w07mdWinieF4Tj9TFS8gRgk3jgb+2RJrkWKgFyknMAjtJiujUJv4XPZTtBgsGQY/olccwwlkUrB9QqxKZEaa1bdT02oHK3O83vZmZvspjXbyHTUDNWZPxIY5MHQcW+Lr1uXPE2Z7rOzDA+6VnKwsv//qTkprgnB7hrGMEHJWIMwhcqHNW1Fj/k58umN9Hgv2U4PxQncjkgTbSSJYC8NmUDEVtWtCmOsLstrp0gZhCiJ/Ec2cvD8wvjqxRKEnDr0IhDfzcb2PUSPA2zw5COdyQ+1KqeMhsM/jPvfIgz+oY6lw0Ako4w+k5Z
x-microsoft-antispam-prvs: <BN3PR0601MB1154F9C99CED1DEECC44436AA74C0@BN3PR0601MB1154.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123560025)(20161123555025)(20161123562025)(20161123564025)(6072148); SRVR:BN3PR0601MB1154; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1154; 
x-forefront-prvs: 02065A9E77
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(24454002)(199003)(377454003)(189002)(377424004)(38730400001)(57306001)(82746002)(8936002)(92566002)(83716003)(86362001)(99286003)(6512007)(8676002)(68736007)(81156014)(81166006)(6116002)(3846002)(102836003)(110136003)(2900100001)(53936002)(6916009)(3660700001)(2950100002)(4326007)(36756003)(66066001)(50226002)(106116001)(106356001)(2906002)(6436002)(77096006)(105586002)(6506006)(7736002)(99936001)(305945005)(229853002)(76176999)(5660300001)(50986999)(4001150100001)(97736004)(6486002)(101416001)(54906002)(3280700002)(33656002)(230783001)(25786008)(189998001)(122556002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1154; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_5A7DAAE9-D80A-4DE8-BA93-D9F8DA7F2946"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Feb 2017 10:21:35.0642 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1154
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RZ6IWmi1qbAwU1WUBmPqGXXijyQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 10:22:42 -0000

--Apple-Mail=_5A7DAAE9-D80A-4DE8-BA93-D9F8DA7F2946
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-2, at 10:54, Fernando Gont <fgont@si6networks.com> wrote:
> On 02/02/2017 06:37 AM, Eggert, Lars wrote:
>> Also, even if ICMP delivery is assured, there are additional
>> complications for UDP, which has been seeing a lot of interest both
>> as a tunneling encapsulation and for applications (e.g., QUIC). Many
>> platforms do not provide UDP-sending applications any information
>> about arriving ICMP messages that were triggered by their
>> transmissions. So even if the path delivers ICMP, the OS makes
>> ICMP-based PMTUD for UDP often impossible. Another reason to
>> recommend 4821?
>=20
> Agreed... although in this case this would be more of an app-layer
> implementation than one at the transport layer?

There are two dimensions here, one is in kernel vs. in userspace, the =
other which "layer" something is at. It used to be that "transport =
layer" (or "network layer" always implied "in kernel", but those days =
are past.

Lars

--Apple-Mail=_5A7DAAE9-D80A-4DE8-BA93-D9F8DA7F2946
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYkwgtAAoJEFS1wwm/cMFXXQAQANdGo7nbA9Cpl4jLeRtvUvPd
0vsQKxl8Co18GL6q2QvMWoNtOHatIyZ3d5/aO8b8N5FTfL1HeOSYM0SPUamp6sqh
/f4ANGI6hywY0kK1DIE7QtC/oDhVQecQ9MA0J3sxWLhGqIGW2tEjgI7mHK1gAAgo
SoPkBYDZ1H/IgJN27v40adV/UFVjpLcxuRFXx/7UUaZqI9QImF4g7VWpl8yDWgLu
sx8JujYa7v7VfcIirewsHBWAjoj9DAY+7eZc0NHudnluyXtvEUlbk/gAqCQuxisW
ZAtQBDXMAzgIDWRFTAM+2maqHoONwQtNa9KTT55M3O/uqsp6XE6/fGrmlaDKOIjo
sjKo7bBoMnhBYsdzwsDom84m87B1iSrWFYeLXX4kT9I5l/cop7x0nmY8fnDUjU48
SWVvcjV8MQGXfY3v2OG7ZjuHMVMmUF1L6/ARJ5SLVT+x5YwEEMLq02n2OYtYdaHX
7kcJur56yKN3+bGf9VpRUcEDBGnJeGci/Um0GPOcnDl+pFH9sG1o6AYs056LqjQE
soq3TNNonv2tCUmc18jrzdbwJoWwsDBWLWmiDKKPR2kKAUsI0b4/1cU0PiAG2aAs
uIrh1XwXGMTZfGXD7t975KWjnHDGwmOlK7d+M/NcxaGozBzkDPm93Z0L6EODMXwW
TGEFF/opzfmwu5VXUNFX
=IHzK
-----END PGP SIGNATURE-----

--Apple-Mail=_5A7DAAE9-D80A-4DE8-BA93-D9F8DA7F2946--


From nobody Thu Feb  2 03:08:22 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92CBC129437; Thu,  2 Feb 2017 03:08: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 561yEwHHc7Wt; Thu,  2 Feb 2017 03:08:14 -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 9E4E7127076; Thu,  2 Feb 2017 03:08:14 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 36D8380A93; Thu,  2 Feb 2017 12:08:09 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <5C876EB6-F2B6-4F2C-9A6B-2AC63D0115D3@netapp.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <4de97844-6f79-058c-e284-2b9ae79147fe@si6networks.com>
Date: Thu, 2 Feb 2017 07:58:17 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <5C876EB6-F2B6-4F2C-9A6B-2AC63D0115D3@netapp.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kqy-YoQ8tI4HI5AkKDQqT6dh-fI>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 11:08:20 -0000

On 02/02/2017 07:21 AM, Eggert, Lars wrote:
> On 2017-2-2, at 10:54, Fernando Gont <fgont@si6networks.com> wrote:
>> On 02/02/2017 06:37 AM, Eggert, Lars wrote:
>>> Also, even if ICMP delivery is assured, there are additional 
>>> complications for UDP, which has been seeing a lot of interest
>>> both as a tunneling encapsulation and for applications (e.g.,
>>> QUIC). Many platforms do not provide UDP-sending applications any
>>> information about arriving ICMP messages that were triggered by
>>> their transmissions. So even if the path delivers ICMP, the OS
>>> makes ICMP-based PMTUD for UDP often impossible. Another reason
>>> to recommend 4821?
>> 
>> Agreed... although in this case this would be more of an app-layer 
>> implementation than one at the transport layer?
> 
> There are two dimensions here, one is in kernel vs. in userspace, the
> other which "layer" something is at. It used to be that "transport
> layer" (or "network layer" always implied "in kernel", but those days
> are past.

I was refering to "layer" as in a reference model. i.e., PMTU assumes
that you can repacketize your data. For TCP, that can be done at the
transport layer, since it's byte-stream oriented. OTOH, UDP is
essentially record-based... so any "re-packetization" must be done at
the upper (app) layer.

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  2 07:26:14 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79ACD12946D; Thu,  2 Feb 2017 07:26:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LqguKZ3bEL2p; Thu,  2 Feb 2017 07:26:03 -0800 (PST)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::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 17AC2129457; Thu,  2 Feb 2017 07:26:03 -0800 (PST)
Received: by mail-ot0-x22e.google.com with SMTP id f9so14190592otd.1; Thu, 02 Feb 2017 07:26:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DnF+s4vIkTb7fBFANeAtifhEqUtodV4CLlUYBpBZ9DM=; b=EnYUbYoIXvZn9mq5UPZ8uPAbZsooOixyLXPRRyWv89QRbsf6ICrWH/EucCzvXsTnk5 RuksITqGSVU7z4eSR9MDCLWPohw3e2xI4zd3zMqlQYlHOa+ouDJR8sp9IudaFUGhGbGu 5WQOKjJvHzkUxODHO/xjcAG03cY6sI3sY4XjWpcOGDMhRCPBrslxRU+B+O2+tMedm4YX XK6M+lP5YRj/iTEKcoULSAQNSQwq0/uJyCFG30ZTblm8cgByZDYnq1Hw/RdrR9O2TQXh S8LCHXUy6kjAURyo9xCiWABvFcxEu9W5SLYVwfossitw1i1RhO4hznjUDEmPQqGf/cY6 Y07Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DnF+s4vIkTb7fBFANeAtifhEqUtodV4CLlUYBpBZ9DM=; b=Pi/C7EOa1LZIVaLRIEUoRcUG/XaizSpvavV4aMPGfm15s8YtPnHSJw2WxDfuyiSVlv r5YYaZ8cx8SntJt0l+xlDmUao2zx+e6TroCjJcd7hPe9xqlj1+PJ6SujJLRIs3LmX6rB nfqAmaTKQgt/YAPm8mFJWm5PPXV8izMttnosSPufTVAUzp+ZRDihFmwA6tglFXuS48Ub 2lxpB0RTCv/z7Dke5RJ/KruCGAMkTp0terXJTLkvJzIbZiMxShcWPfeeqf15PCxu3MaR m5bNQTxFQZRgnU4AqZMkbk5oFUgGVyaftrlluDELxNSh60S6t8ujXVPoYHp9HCoxK3cX S68Q==
X-Gm-Message-State: AMke39llhjmuR/0ba06CoHmy9S5aIfn5/6xzkzLsKVPnUDYWudZwzD84B3F0VLlyLlusqpD8lLz7tjzafkJUsg==
X-Received: by 10.157.60.149 with SMTP id z21mr4074859otc.34.1486049162280; Thu, 02 Feb 2017 07:26:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Thu, 2 Feb 2017 07:25:21 -0800 (PST)
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <CAFx+hEPy0rzAa_QFu4wOBc2hpRqX-5MM0OtZfmuy82Ls7WRmAA@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD770018@DGGEMM506-MBX.china.huawei.com> <CAFx+hEO0x9EVCOgA1YDU7O-1wfRPnsiDzK5GB=MAHSqcir2JMw@mail.gmail.com> <6E58094ECC8D8344914996DAD28F1CCD771622@DGGEMM506-MBX.china.huawei.com>
From: tianxiang li <peter416733@gmail.com>
Date: Thu, 2 Feb 2017 23:25:21 +0800
Message-ID: <CAFx+hEOc_U4uPGYsE9whndfF3dyoiZxLxHoH+uaxCJ6McAq4_Q@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
To: Roni Even <roni.even@huawei.com>
Content-Type: multipart/alternative; boundary=94eb2c19018e6fc61805478dc8b4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fKcIiEISPiyjx7EogReBv1sDuK8>
Cc: dhcwg <dhcwg@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, Roni Even <roni.even@mail01.huawei.com>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org" <draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 15:26:04 -0000

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

Hi Roni,

Thank you for comments, we'll add the changes to the document in our next
updated version.
Please see inline.

Cheers,
Tianxiang

2017-02-02 14:42 GMT+08:00 Roni Even <roni.even@huawei.com>:

> Hi,
>
> I will leave only the items that needed my response
>
>
>
> 7.      In section 3.4 =E2=80=9CIf the client decided to use  the prefix =
provided
> by the server despite being longer than the  prefix-length hint=E2=80=9D =
yet I
> did not see in section 3.2 that the server can provide a longer
> prefix.
>
>
>
> [Tianxiang] This was mentioned in the last sentence of section 3.2:
>
>
>
> "If the requested prefix is not available in the server's prefix pool, an=
d
> the client also included a prefix-length hint in the same IA_PD option,
> then the server SHOULD try to provide a prefix matching the prefix-length
> value, or the prefix with the shortest length possible which is closest t=
o
> the prefix-length hint value."
>
> *[Roni Even] I understood from 3.2 that it should provide a shorter lengt=
h
> prefix  closer to the request maybe =E2=80=9C*or the prefix with the clos=
est
> possible length to the prefix-length hint value=E2=80=9D
>
>
>
> [Tianxiang2] The original sentence was a bit confusing, perhaps we could
> change it like this:
>
>
>
> OLD: "If the requested prefix is not available in the server's prefix
> pool, and the client also included a prefix-length hint in the same IA_PD
> option, then the server SHOULD try to provide a prefix matching the
> prefix-length value, or the prefix with the shortest length possible whic=
h
> is closest to the prefix-length hint value."
>
>
>
> NEW:"If the requested prefix is not available in the server's prefix pool=
,
> and the client also included a prefix-length hint in the same IA_PD optio=
n,
> then the server SHOULD provide a prefix matching the prefix-length hint, =
or
> a prefix which is length is shorter and as close as possible to the
> prefix-length hint. If the server could not provide a prefix which length
> is shorter or equal to the prefix-length hint, the server SHOULD provide
> the prefix which length is longer and as close as possible to the
> prefix-length hint."
>
>
>
> *[Roni Even] I have no problem with this text since it will also work wit=
h
> the rest of the document but is it what was really meant*
>
>
>
[Tianxiang3] This was the intended meaning of the original sentence, if the
server could not honor the hint, it should provide a prefix closest to the
hint, the client could then decide whether to accept or neglect this prefix=
.


> *Also a nit*
>
>
>
> =E2=80=9Cor a prefix which is length is shorter and as close as possible =
to the
> prefix-length hint. If the server could not provide a prefix which length
> is shorter or equal to the prefix-length hint, the server SHOULD provide
> the prefix which length is longer and as close as possible to the
> prefix-length hint=E2=80=9D
>
>
>
> to
>
>
>
> =E2=80=9Cor a prefix whose length is shorter and as close as possible to =
the
> prefix-length hint. If the server could not provide a prefix with a short=
er
> or equal length  to the prefix-length hint, the server SHOULD provide a
> prefix whose length is longer and as close as possible to the prefix-leng=
th
> hint=E2=80=9D
>

[Tianxiang3] Thanks for the suggestion, we will edit this sentence
accordingly.

>
>
>
>
> Nits/editorial comments:
>
>
>
>
>

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

<div dir=3D"ltr">Hi Roni,<div><br></div><div>Thank you for comments, we&#39=
;ll add the changes to the document in our next updated version.</div><div>=
Please see inline.=C2=A0</div><div><br></div><div>Cheers,</div><div>Tianxia=
ng</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-02-0=
2 14:42 GMT+08:00 Roni Even <span dir=3D"ltr">&lt;<a href=3D"mailto:roni.ev=
en@huawei.com" target=3D"_blank">roni.even@huawei.com</a>&gt;</span>:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5663720217037483393m_3777587516231959433WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I will leave only the ite=
ms that needed my response<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div><span>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<p class=3D"MsoNormal">7.=C2=A0 =C2=A0 =C2=A0 In section 3.4 =E2=80=9CIf th=
e client decided to use=C2=A0 the prefix provided<br>
by the server despite being longer than the=C2=A0 prefix-length hint=E2=80=
=9D yet I<br>
did not see in section 3.2 that the server can provide a longer<br>
prefix.<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Tianxiang] This was mentioned in the last sentence =
of section 3.2:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&quot;If the requested prefix is not available in th=
e server&#39;s prefix pool, and the client also included a prefix-length hi=
nt in the same IA_PD option, then the server SHOULD try to
 provide a prefix matching the prefix-length value, or the prefix with the =
shortest length possible which is closest to the prefix-length hint value.&=
quot;<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Roni Even] I under=
stood from 3.2 that it should provide a shorter length prefix =C2=A0closer =
to
 the request maybe =E2=80=9C</span></i></b>or the prefix with the closest p=
ossible length to the prefix-length hint value=E2=80=9D<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Tianxiang2] The original sentence was a bit confusi=
ng, perhaps we could change it like this:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">OLD:=C2=A0&quot;If the requested prefix is not avail=
able in the server&#39;s prefix pool, and the client also included a prefix=
-length hint in the same IA_PD option, then the server SHOULD try to provid=
e a prefix matching the prefix-length value, or
 the prefix with the shortest length possible which is closest to the prefi=
x-length hint value.&quot;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span>
<p class=3D"MsoNormal">NEW:&quot;If the requested prefix is not available i=
n the server&#39;s prefix pool, and the client also included a prefix-lengt=
h hint in the same IA_PD option, then the server SHOULD provide a prefix ma=
tching the prefix-length hint, or a prefix
 which is length is shorter and as close as possible to the prefix-length h=
int. If the server could not provide a prefix which length is shorter or eq=
ual to the prefix-length hint, the server SHOULD provide the prefix which l=
ength is longer and as close as
 possible to the prefix-length hint.&quot;<u></u><u></u></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u=
></span></i></b></p>
</span><p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">[Roni Even] =
I have no problem with this text since it will also work with the rest of t=
he document but is it what was really meant<u></u><u></u></span></i></b></p=
>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0</span=
></i></b></p></div></div></div></div></div></div></div></blockquote><div>[T=
ianxiang3] This was the intended meaning of the original sentence, if the s=
erver could not honor the hint, it should provide a prefix closest to the h=
int, the client could then decide whether to accept or neglect this prefix.=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" l=
ink=3D"blue" vlink=3D"purple"><div class=3D"m_5663720217037483393m_37775875=
16231959433WordSection1"><div style=3D"border:none;border-left:solid blue 1=
.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"MsoNormal">=
<b><i><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1f497d"><u></u></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Also a nit<u></u><u=
></u></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u=
></span></i></b></p>
<p class=3D"MsoNormal">=E2=80=9Cor a prefix which is length is shorter and =
as close as possible to the prefix-length hint. If the server could not pro=
vide a prefix which length is shorter or equal to the prefix-length hint, t=
he server SHOULD provide the prefix which
 length is longer and as close as possible to the prefix-length hint=E2=80=
=9D<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">to<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">=E2=80=9Cor a prefix whose length is shorter and as =
close as possible to the prefix-length hint. If the server could not provid=
e a prefix with a shorter or equal length =C2=A0to the prefix-length hint, =
the server SHOULD provide a prefix whose length
 is longer and as close as possible to the prefix-length hint=E2=80=9D</p><=
/div></div></div></div></div></div></div></blockquote><div><br></div><div>[=
Tianxiang3] Thanks for the suggestion, we will edit this sentence according=
ly.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-US" link=3D"b=
lue" vlink=3D"purple"><div class=3D"m_5663720217037483393m_3777587516231959=
433WordSection1"><div style=3D"border:none;border-left:solid blue 1.5pt;pad=
ding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"MsoNormal"><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1f497d"><u></u><u></u></span></p>
</div><span>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;pad=
ding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><div><div><div s=
tyle=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"=
><div><div><div><blockquote style=3D"border:none;border-left:solid #cccccc =
1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-r=
ight:0cm;margin-bottom:5.0pt"><p class=3D"MsoNormal" style=3D"margin-bottom=
:12.0pt"><br>
<br>
Nits/editorial comments:<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--94eb2c19018e6fc61805478dc8b4--


From nobody Thu Feb  2 07:39:38 2017
Return-Path: <rja.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9722129667; Thu,  2 Feb 2017 07:39:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4saBRtGMpeps; Thu,  2 Feb 2017 07:39:35 -0800 (PST)
Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (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 61E391293EE; Thu,  2 Feb 2017 07:39:35 -0800 (PST)
Received: by mail-qt0-x244.google.com with SMTP id w20so4702464qtb.1; Thu, 02 Feb 2017 07:39:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xvzHxNkUXk6ra2ZnfdLPeCM4V1eOEE3r4lUQro5mSjA=; b=Zv4CxcJ0YnqB21pb5Bw/6tHj/RtqF+dT0Ed1vA18996TThU54k+yFEHSNXskKqJQ6E BPufPKcJ0lam+AvylmC3J9W2v73Qyhl6c7BYHSdaV/3XKSMzMFVwL/IHt+n8mX1hmgCm NDptdir29iiIYImic3hFmF8Dbr7H3O0sC3JZFLc5EaGRl6gAdpuuXs4QosW7N4IZFRpo WqYWAk+0MwubqfJ9lrEPreWM0Kfl1hKIIy1e9nUY93mM7hvGIbTY2FyHMfcw41Pu6aG+ 8b1RBe6LkKIJ8k4IwLDlHHdetElq0tFS4jq68K2y5KUADm2J4Tj5EyMKyprUazMYpNa0 8h9w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xvzHxNkUXk6ra2ZnfdLPeCM4V1eOEE3r4lUQro5mSjA=; b=Y9OFzCvs/jYQXnlZz0tNgSLsKckL+r3/byyriIPZPIzpg0KI0rv5r47BlcHS6D4LOW OGpYFH4nPFXX7q8RDgw3WsVgr2vZ5sXU4ADLPjnef4iEidsc8kMOUaSPUKHIGduCbEkz n8x7CHqnlmQ+s7CZwA9DbJRqMoXC+kub/4E6P7/acwKyafORBy9X9H4bJekEcam8pBky xTAv1Az8eAPhunqg5i36AQDrHhQn5WamjufiESNS36cO4nCEXe9dJME2y2nRSaCbLTDc 5wHCutJMe5GCli+C6P8Mz+xUD4ETBEtnucWbR9aDW2DOqmHFx4S7b79/t+0pL6IiSdiJ HaHA==
X-Gm-Message-State: AIkVDXJtBFWctku6fKObWRboJcQ9CYskqCqiegmyPP9jdcAsgoKJkSy3bZtAhg1+OQY5oQ==
X-Received: by 10.200.56.164 with SMTP id f33mr9098910qtc.158.1486049974071; Thu, 02 Feb 2017 07:39:34 -0800 (PST)
Received: from [10.30.20.13] (pool-173-73-12-2.washdc.fios.verizon.net. [173.73.12.2]) by smtp.gmail.com with ESMTPSA id f128sm3840138qkb.3.2017.02.02.07.39.33 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 02 Feb 2017 07:39:33 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Randal Atkinson <rja.lists@gmail.com>
In-Reply-To: <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com>
Date: Thu, 2 Feb 2017 10:39:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/haHCrCRXGFats2Kh3iMDDAVNtsI>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 15:39:37 -0000

> On 31Jan2017, at 04:44, Naeem Khademi <naeem.khademi@gmail.com> wrote:
>=20
> The next IETF in the US after Chicago, would be in July 2018 in SF. I =
don't think it's even possible
> to buy a flight ticket for that time as of now (most airlines wouldn't =
do such pre-sale). So, it's pretty
> much possible to relocate that meeting elsewhere with causing no loss =
to anyone's already-made plans.

The claim above that "most airlines won=E2=80=99t sell 6 months in =
advance" is false. =20

Most airlines, including all or nearly all major full-service =
international airlines, start selling tickets=20
at least 12 months before the departure date for the 1st flight on an =
itinerary. =20

To my knowledge, there are some people who already have purchased =
tickets to go to IETF in SFO. =20
This really ought not be surprising as the lowest-cost fares often =
sell-out earliest.  A number of
IETF people don=E2=80=99t work for big companies and are traveling on =
their own money.   Those people
would suffer greatly from a change in location less than 12 months out.

I am aware that some have suggested the IETF do more remote meetings.  I =
think that is worth
exploring.=20

I certainly would support IETF making all future meetings more =
accessible remotely  =E2=80=94 and I think=20
that is a goal the IETF has been making progress on for some years now, =
using Jabber, VTC,=20
and so forth.  Expanding the remote access capabilities and coverage for =
all future meetings=20
(to the extent that is practical at a given point in time) only makes =
sense.

Yours,

Ran


From nobody Thu Feb  2 07:58:39 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC4112943E; Thu,  2 Feb 2017 07:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.5
X-Spam-Level: 
X-Spam-Status: No, score=-7.5 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_MED=-2.3, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRlCI3WCg6kq; Thu,  2 Feb 2017 07:58:34 -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 2F87112941A; Thu,  2 Feb 2017 07:58:32 -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 v12FwQY5019646; Thu, 2 Feb 2017 15:58:26 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v12FwQY5019646
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1486051106; bh=grgLkRHRSAcYL7qeFvkQOdZ5E+E=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=jKj7yabIRtfoBlGbCfA34DtA0jfZF8NpIjdh4yJAQQ/2S9ZWrKQYOAPAtX3HSBSLW yaZJxoaW+lWjDb41vEJaBcCE68IpqyTJCqXsvijoBwPagk5+w/R45UGaoMP/dUnPTQ Byjp25f7fncXdpazZV6LzSmzwGmt2wuNV+wk25V8=
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 y11FwQ23562107846j ret-id none; Thu, 02 Feb 2017 15:58:26 +0000
Received: from [10.1.11.126] (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 v12FwNeB032451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2017 15:58:23 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com>
Date: Thu, 2 Feb 2017 15:58:23 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|e79af8b0b5b4f94b1e7da0aa197d5644y11FwQ03tjc|ecs.soton.ac.uk|B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com> <B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk>
To: Randal Atkinson <rja.lists@gmail.com>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y11FwQ235621078400; tid=y11FwQ23562107846j; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v12FwQY5019646
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1cQa17ClYUV3XfguCqPYu4gbALU>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 15:58:37 -0000

Hi,

> On 2 Feb 2017, at 15:39, Randal Atkinson <rja.lists@gmail.com> wrote:
>=20
>=20
>> On 31Jan2017, at 04:44, Naeem Khademi <naeem.khademi@gmail.com> =
wrote:
>>=20
>> The next IETF in the US after Chicago, would be in July 2018 in SF. I =
don't think it's even possible
>> to buy a flight ticket for that time as of now (most airlines =
wouldn't do such pre-sale). So, it's pretty
>> much possible to relocate that meeting elsewhere with causing no loss =
to anyone's already-made plans.
>=20
> The claim above that "most airlines won=E2=80=99t sell 6 months in =
advance" is false. =20
>=20
> Most airlines, including all or nearly all major full-service =
international airlines, start selling tickets=20
> at least 12 months before the departure date for the 1st flight on an =
itinerary. =20
>=20
> To my knowledge, there are some people who already have purchased =
tickets to go to IETF in SFO. =20
> This really ought not be surprising as the lowest-cost fares often =
sell-out earliest.  A number of
> IETF people don=E2=80=99t work for big companies and are traveling on =
their own money.   Those people
> would suffer greatly from a change in location less than 12 months =
out.
>=20
> I am aware that some have suggested the IETF do more remote meetings.  =
I think that is worth
> exploring.=20
>=20
> I certainly would support IETF making all future meetings more =
accessible remotely  =E2=80=94 and I think=20
> that is a goal the IETF has been making progress on for some years =
now, using Jabber, VTC,=20
> and so forth.  Expanding the remote access capabilities and coverage =
for all future meetings=20
> (to the extent that is practical at a given point in time) only makes =
sense.

I just tried availability for flights from London to San Francisco for =
July 2018 IETF. =20
None of BA, Virgin or United would offer tickets beyond January 2018.=20
Perhaps it=E2=80=99s different for internal flights within the US?

I guess we simply can=E2=80=99t know how many people would be =
inconvenienced should=20
the IETF announce that the July 2018 IETF is relocating to (say) =
Vancouver. In practice,=20
there would be at least some moral obligation to refund those people if =
there=E2=80=99s no flexibility=20
in the tickets.

Certainly being better placed to support remote participation will be =
increasingly=20
important. The IETF has made great strides in recent years with =
MeetEcho, etc. But no=20
doubt more can be done, and now we have an additional very good reason =
to do so.

Tim=


From nobody Thu Feb  2 08:06:06 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 694AC12947A; Thu,  2 Feb 2017 08:06:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ipsecme-rfc4307bis-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148605156539.13830.6416316067398939320.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 08:06:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ct-K5Kl1Y5yi7vw7xH7j3uprD5I>
Cc: ipsec@ietf.org, draft-ietf-ipsecme-rfc4307bis.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 16:06:05 -0000

Reviewer: Pete Resnick
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments. (Apologies for the late
submission.)

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ipsecme-rfc4307bis-??
Reviewer: Pete Resnick
Review Date: 2017-02-02
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-02-16

Summary:

This document is basically ready, but there are a large number of
nits, so many that I would think additional review would be desired.

Major issues: None

Minor issues: None

Nits/editorial comments: 

[Note: I do not see any particular technical problems with the
document, but I don't have expertise in this area. I have listed below
many clarifications and fixes to typographical and grammatical errors.
(I did not note all of the punctuation errors as none of them left
ambiguity.) Normally, I would simply list these as nits/editorial
comments and leave it at that. But there are so many of these that I'm
a bit concerned that the document did not receive sufficient technical
review, given that it went through 15 versions and nobody fixed all of
these editorial issues. That said, that is an issue between the AD and
the WG.]

It seems like section 2 should be moved up above section 1 since these
specialized conventions are used in section 1.

1: The second to last sentence is ungrammatical and hard to read. Try
this:

OLD
   This document describes the parameters of the IKE protocol and
   updates the IKEv2 specification because it changes the mandatory
to
   implement authentication algorithms of the section 4 of the
RFC7296
   by saying RSA key lengths of less than 2048 are SHOULD NOT.
NEW
   This document describes the parameters of the IKE protocol. It
also
   updates the IKEv2 specification because it changes the mandatory
to
   implement authentication algorithms of section 4 of RFC 7296
   by saying RSA key lengths of less than 2048 SHOULD NOT be used.
END

1.1, first sentence: s/then/than

1.1, last sentence: s/in a separate document/in this separate
document.

1.2: The last sentence of the third paragraph repeats what is in the
last paragraph of 1.2 and therefore redundant. You can strike it. 

2: I suggest adding a sentence after the first paragraph for
clarification: "When used in the tables in this document, these terms
indicate that the listed algorithm MUST, MUST NOT, SHOULD, SHOULD NOT
or MAY be implemented as part of an IKEv2 implementation." 4307 never
said that specifically, and I've always found it weird.

3.1, first paragraph: s/an integrity algorithms in Section 3.3/one of
the integrity algorithms in Section 3.3

3.1, third paragraph: s/CRFG/the Crypto Forum Research Group (CFRG) of
the IRTF

(You not only didn't define it, you got the acronym backwards.)

3.1, third from last paragraph: s/on those cases/in those cases

3.1, second from last paragraph: s/implementation/implementations

3.1, last paragraph: s/of-the-shelves/off-the-shelf ;
s/therefor/therefore

3.3, last paragraph: s/status ware/statuses were

3.4, third paragraph: s/were/was

3.4, fourth paragraph: s/vulnerable to be broken/vulnerable to being
broken

3.4, last paragraph: s/thater/that; s/academia have/academia has

4: s/concerned on/concerned with

4.1, first paragraph: 

OLD
                                           RSA Digital Signature is
not
   recommended for keys smaller then 2048, but since these signatures
   only have value in real-time, and need no future protection,
smaller
   keys was kept at SHOULD NOT instead of MUST NOT.

NEW
	See section 4.1.1 for a discussion of key length recommendations for
	use in RSA Digital Signature.
END

(If you want, include some of the original text in 4.1.1.

4.1, third paragraph: s/it does not/they do not

4.2, paragraphs 1, 2, & 3: s/When Digital Signature
authentication/When a Digital Signature authentication ; also, strike
the word "then" in the first two paragraphs.


From nobody Thu Feb  2 08:12:50 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0DB91296EC for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2017 08:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.256
X-Spam-Level: 
X-Spam-Status: No, score=-3.256 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.156, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RiQwWAewEXkA for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2017 08:12:48 -0800 (PST)
Received: from nm37-vm8.bullet.mail.gq1.yahoo.com (nm37-vm8.bullet.mail.gq1.yahoo.com [98.136.217.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 594561296E3 for <ietf@ietf.org>; Thu,  2 Feb 2017 08:12:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1486051967; bh=Av2X3jcK5f/XztSfvnWzNgcM/Oi5ppTY2NyLfPxnLAs=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=kQPh9e9t0fsjd31zlvimJHniPMF/Mf0XXX5oRIM4od7j7V/qW4P8Z17iTo+zV65oaTc8u72zSvEB97h003jQYl17Z7tb/tT2awuThh7M2AekxwxZJtBbkHfSop4JZUnIUtANi0gx9F4wOjLmLsyA5PPJsLTgj8h93nVsaPwBWDT+JVedmHdGsieTvUr7W+KnlXpNO2HMLXXnmfMqswFOgfDde2NNR8spd981G1FVPoYz+fGGLtsCvjk7BjkjtuQQ29AdKsojgnSTXj7xyFeAGfDomMtr9gNvQ6PPwZUSKTRc+rxxVxomhsCfzkb67QbMp3Xhfeh4GEsOrLjLVtUSQQ==
Received: from [127.0.0.1] by nm37.bullet.mail.gq1.yahoo.com with NNFMP; 02 Feb 2017 16:12:47 -0000
Received: from [216.39.60.184] by nm37.bullet.mail.gq1.yahoo.com with NNFMP; 02 Feb 2017 16:08:44 -0000
Received: from [98.137.12.232] by tm20.bullet.mail.gq1.yahoo.com with NNFMP; 02 Feb 2017 16:08:44 -0000
Received: from [127.0.0.1] by omp1040.mail.gq1.yahoo.com with NNFMP; 02 Feb 2017 16:08:44 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 231278.95580.bm@omp1040.mail.gq1.yahoo.com
X-YMail-OSG: eK82bHYVRDtgfAoCqOIpFuQf7CXNzbPmvwqKAF0E6WpCYH8GW8U-
Received: from jws300043.mail.gq1.yahoo.com by sendmailws110.mail.gq1.yahoo.com; Thu, 02 Feb 2017 16:08:43 +0000; 1486051723.743
Date: Thu, 2 Feb 2017 16:08:43 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Randal Atkinson <rja.lists@gmail.com>, Tim Chown <tjc@ecs.soton.ac.uk>
Message-ID: <1550723323.3059434.1486051723341@mail.yahoo.com>
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1550723323.3059434.1486051723341.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vrtleV3M7U_bLO-90cUtexZy0JY>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 16:12:49 -0000

> Certainly being better placed to support remote participation will be increasingly 
> important. The IETF has made great strides in recent years with MeetEcho, etc. But no 
> doubt more can be done, and now we have an additional very good reason to do so.
 

I have just started a thread to discuss the existing drafts on remote hubs and to see what we need to do revise, throw away & start over, etc. on VMEET.   The drafts are: main, Latin America & India.

https://tools.ietf.org/html/draft-elkins-ietf-remote-hubs-00.html
https://tools.ietf.org/html/draft-oflaherty-ietf-remote-hubs-lac-00
https://tools.ietf.org/html/draft-hegde-remote-hubs-india-01

They are very much work in progress so my feelings will not be hurt at all if we want to start over.  I am volunteering to help with any such effort.

BTW, I have put some feelers out to people about starting a Silicon Valley remote hub.  (That is my local region.)   I think it may be a good thing to have before Prague.

If anyone would like to help with a Silicon Valley hub, please contact me unicast.

Nalini


From nobody Thu Feb  2 08:34:51 2017
Return-Path: <roland.bless@kit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 015671297CB for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2017 08:34:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.19
X-Spam-Level: 
X-Spam-Status: No, score=-4.19 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=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 r71dTNHcsPUQ for <ietf@ietfa.amsl.com>; Thu,  2 Feb 2017 08:34:47 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBDFC12973E for <ietf@ietf.org>; Thu,  2 Feb 2017 08:34:46 -0800 (PST)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  iface 141.3.10.81 id 1cZKLJ-0000pP-KW; Thu, 02 Feb 2017 17:34:41 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id C4262B004B5; Thu,  2 Feb 2017 17:34:35 +0100 (CET)
Subject: Re: Follow-up on the issue of IETF members being unable to attend.
To: Pat Thaler <pat.thaler@broadcom.com>, Dave Burstein <daveb@dslprime.com>
References: <CAJt_5EiSDWaT+SVJ7TMk4gDkV5uRXX5D8eby=gA3xz3KymyyQw@mail.gmail.com>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
Message-ID: <3c2f2913-335b-a686-94f6-d63e4d8e2a4e@kit.edu>
Date: Thu, 2 Feb 2017 17:34:35 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAJt_5EiSDWaT+SVJ7TMk4gDkV5uRXX5D8eby=gA3xz3KymyyQw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1486053281.
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FntP5KK5G0c69cMLKk37KAWPihw>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 16:34:50 -0000

Hi,

the IEEE statement is also out now:
http://www.ieee.org/about/bartleson_message_01_february_2017.html
For convenience:
----------------------------------------------
Special Message from IEEE President Karen Bartleson

IEEE President Karen Bartleson today released the following statement in
response to concerns expressed by IEEE members around the world:

IEEE, The Institute of Electrical and Electronics Engineers,
Incorporated, believes that governments of all countries must recognize
that, in a world of increasing global connectivity, science and
engineering are fundamental enterprises, for which openness,
international collaboration, and the free flow of ideas and talented
individuals are essential to advancement.

Every country benefits from attracting, and competing for, the best and
brightest scientists and engineers from around the world to study,
teach, conduct and collaborate on research, innovate new technologies,
and start commercial endeavors.  Science and engineering lead to
enhancements in quality of life and ultimately build economic prosperity
and security.  All countries should develop and maintain immigration and
visa policies that encourage, facilitate, and protect the ability of
people, from around the world, to engage in these types of science and
engineering activities.

Diversity is an important and valued strength; IEEE is committed to the
realization and maintenance of an environment in which scientists and
engineers, regardless of ethnicity, religion, gender, or nationality,
have the right to pursue their careers without discrimination.  Science,
engineering - and humanity - prosper where there is freedom of movement,
association, and communication.
----------------------------------------------

Am 02.02.2017 um 01:09 schrieb Pat Thaler:
> Just to clarify, there is IEEE (the whole organization) and many
> different subgroups of IEEE of which IEEE 802 is one. IEEE in Dave's
> first bullet is, I expect, referring to IEEE as a whole. The third
> bullet applies for IEEE 802. I've no idea what the refund policy will be
> applied by other IEEE subgroups who are holding meetings, conferences
> and such.
> 
> IEEE at the top level has said, in an email to the subgroups, that a
> statement from IEEE is forthcoming. They have asked the subgroups to
> refrain from issuing independent statements until that happens. 
> 
> The IEEE 802 Executive Committee has it's regular teleconference on Feb
> 7. There is an agenda item to discuss impact of the immigration policy
> on us. It has already been IEEE 802's practice to refund plenary meeting
> fees when someone can't attend due to a visa issue. There may be
> discussion on whether to confirm that policy with a motion. 
> 
> Regards,
> Pat
> 
> 
> 
> On Tue, Jan 31, 2017 at 11:53 PM, Dave Burstein <daveb@dslprime.com
> <mailto:daveb@dslprime.com>> wrote:
> 
>     Folks
> 
>     I want to thank Jari, Leslie, and Andrew for speaking rapidly and
>     clearly. I believe they are wise to address the issues directly
>     affecting IETF rather than discussing the merits of U.S. policy. I
>     believe just about everyone following this knows the issues and
>     nothing would be gained by political discussion. 
> 
>     A few follow-up suggestions, carefully chosen to be procedural. I'm
>     mostly a lurker here.: 
> 
>       * That the IETF liaisons courteously forward our blog to the
>         organizations we connect with. I just got a note in IEEE that
>         they are considering a policy and believe what we've decided
>         could help their discussion. I particularly would like to hear
>         from Gonzalo with any response we get from 3GPP, a
>         European-based group that might have a different perspective. 
>       * That we take up the offer of support from ISOC that Kathy Brown
>         posted on the ISOC list. They have a communications staff of
>         about a dozen full-time people. I've heard from two ISOC Board
>         members as well as Kathy that they are deeply committed to doing
>         what's right here. They might help if we reach out and reiterate
>         that IETF is open to all. That could be as simple as a letter to
>         the editor of leading publications in the countries most
>         directly involved. I assume that whoever signs the note will
>         carefully not present personal opinions as IETF policy. We could
>         also send out the blog we have.
>       * That we consider providing refunds to those blocked from
>         attending. I'm told that IEEE will almost definitely offer
>         refunds. I'd suspect the total would not be that large. It will
>         be discussed at a teleconference February 7
>         http://www.ieee802.org/minutes/Conference-calls/Conference-calls.shtml
>         <http://www.ieee802.org/minutes/Conference-calls/Conference-calls.shtml>
>         .I believe there are many IEEE members here and the call is open
>         to all. 
> 
>     I have been reporting on this at http://bit.ly/2kKIjY3, which I'm
>     posting as a bit.ly <http://bit.ly> link rather than with a title
>     some might think subjective. 
> 
>     Dave Burstein
>      
> 
> 
>     -- 
>     Editor, Fast Net News, 5GW News, Net Policy News and DSL Prime
>     Author with Jennie Bourne  DSL (Wiley) and Web Video: Making It
>     Great, Getting It Noticed (Peachpit)
> 
> 


From nobody Thu Feb  2 09:18:58 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 728541294C8; Thu,  2 Feb 2017 09:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level: 
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199] autolearn=ham autolearn_force=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 HOHnptb9APjG; Thu,  2 Feb 2017 09:18:56 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00AA61294C3; Thu,  2 Feb 2017 09:18:55 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cZL25-0008gt-HL; Thu, 02 Feb 2017 12:18:53 -0500
Date: Thu, 02 Feb 2017 12:18:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: Tim Chown <tjc@ecs.soton.ac.uk>, Randal Atkinson <rja.lists@gmail.com>
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
Message-ID: <928D2785E8119B2161F5D8E4@PSB>
In-Reply-To: <EMEW3|e79af8b0b5b4f94b1e7da0aa197d5644y11FwQ03tjc|ecs.soton.ac.uk|B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.c om> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreeti ngs.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com> <B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk> <EMEW3|e79af8b0b5b4f94b1e7da0aa197d5644y11FwQ03tjc|ecs.soton.ac.uk|B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_9sIzC4MgL8VWjinHhv3gv6oS_0>
Cc: recentattendees@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 17:18:57 -0000

Tim,

Apologies for singling out your note as an example.  It isn't
the only one.

--On Thursday, February 2, 2017 15:58 +0000 Tim Chown
<tjc@ecs.soton.ac.uk> wrote:

>> On 2 Feb 2017, at 15:39, Randal Atkinson
<rja.lists@gmail.com> wrote:

>> Most airlines, including all or nearly all major full-service
>> international airlines, start selling tickets  at least 12
>> months before the departure date for the 1st flight on an
>> itinerary.  
>...

> I just tried availability for flights from London to San
> Francisco for July 2018 IETF.   None of BA, Virgin or United
> would offer tickets beyond January 2018.  Perhaps it's
> different for internal flights within the US?

I may be suffering from an arithmetic failure, but according to
my calendar, January 2018 is 12 months out and anything past the
first week of February 2018, such as July 2018, is significantly
more than 12 months out.

I know that passions run high on this set of issues, but can we
all please try to read each other's comments carefully enough to
avoid confusing the discussions by (I presume accidentally)
creating straw men and then attacking them?

best,
     john
 


From nobody Thu Feb  2 09:42:04 2017
Return-Path: <sean@sn3rd.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C5DAC1298AC; Thu,  2 Feb 2017 09:41:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Sean Turner <sean@sn3rd.com>
To: <secdir@ietf.org>
Subject: Review of draft-ietf-bmwg-virtual-net-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148605731580.13933.16924639077387696348.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 09:41:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TA5Z7ZpAiJ0ZETT-PiRFymTC3lE>
Cc: draft-ietf-bmwg-virtual-net.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 17:41:56 -0000

Reviewer: Sean Turner
Review result: Ready

This draft investigates additional benchmarking considerations for
Virtualized Network Functions (VNF).

Comments: lgtm


From nobody Thu Feb  2 15:03:51 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 688FC1299A8; Thu,  2 Feb 2017 15:03:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-oauth-jwsreq-11
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 15:03:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mRTivxzUNtjkEoUf1kvkyoeHBAU>
Cc: ietf@ietf.org, draft-ietf-oauth-jwsreq.all@ietf.org, oauth@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 23:03:40 -0000

Reviewer: Joel Halpern
Review result: Not Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-oauth-jwsreq-??
Reviewer: Joel Halpern
Review Date: 2017-02-02
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-02-16

Summary: This document is ready for publication as a Proposed
Standard

Major issues: N/A

Minor issues:
    Why is the example if section 4 (and others later on) described
as
"non-normative"?  Is it incomplete?  incorrect?  An example is, by
definition, not a full specification.  The language seems designed to
reduce the value of the example.  I would recommend removing all the
"non-normative" notes from the examples.  They are clearly stated to
be examples. 

Nits/editorial comments: 



From nobody Thu Feb  2 15:21:35 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C3D81295CB; Thu,  2 Feb 2017 15:21:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level: 
X-Spam-Status: No, score=-5.2 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=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XGzH4miaLZeQ; Thu,  2 Feb 2017 15:21:28 -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 14D671295C6; Thu,  2 Feb 2017 15:21:27 -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 v12NLMqP007850; Thu, 2 Feb 2017 23:21:22 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v12NLMqP007850
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1486077684; bh=uUvvZkuF9GZqxfyLVBeWS/18zb8=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=S27A9UL1eFBuE7SyCz2HcUZL1AhTienbQib+Am/QVm5mNbejeQBj55hoTyYkVSSRa g2uDetoQO3eH6YplOigU+TopRJEx8V8Wd2190jJCiGwrWnsuZtXBCsO1ltLocuuI4O KrvOmxwHnhirZWfFl/8VR1bW86Komb9+hKpyJNB8=
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 y11NLM2356213823qF ret-id none; Thu, 02 Feb 2017 23:21:24 +0000
Received: from 20010a88d51011.ipv6.customer.clara.net (20010a88d51011.ipv6.customer.clara.net [IPv6:2001:a88:d510:1101:1a5:c480:a366:16e6] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v12NLFCE023225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2017 23:21:17 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <928D2785E8119B2161F5D8E4@PSB>
Date: Thu, 2 Feb 2017 23:21:14 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|8d15f1d9ef8beb42aef9899b200c9d24y11NLM03tjc|ecs.soton.ac.uk|89E9CDD1-76BC-48E6-BE59-CB9A9964AF68@ecs.soton.ac.uk>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.c om> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreeti ngs.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com> <B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk> <EMEW3|e79af8b0b5b4f94b1e7da0aa197d5644y11FwQ03tjc|ecs.soton.ac.uk|B2C50F36-F158-4BB4-BC5E-DE59166F1D5E@ecs.soton.ac.uk> <928D2785E8119B2161F5D8E4@PSB> <89E9CDD1-76BC-48E6-BE59-CB9A9964AF68@ecs.soton.ac.uk>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.3259)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-ECS-MailScanner-SpamScore: ss
X-smtpf-Report: sid=y11NLM235621382300; tid=y11NLM2356213823qF; 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: v12NLMqP007850
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5y7zLxg32xUsWRH9fTcaNrrS5Ik>
Cc: recentattendees@ietf.org, Randal Atkinson <rja.lists@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2017 23:21:33 -0000

John,

> On 2 Feb 2017, at 17:18, John C Klensin <john-ietf@jck.com> wrote:
>=20
> Tim,
>=20
> Apologies for singling out your note as an example.  It isn't
> the only one.
>=20
> --On Thursday, February 2, 2017 15:58 +0000 Tim Chown
> <tjc@ecs.soton.ac.uk> wrote:
>=20
>>> On 2 Feb 2017, at 15:39, Randal Atkinson
> <rja.lists@gmail.com> wrote:
>=20
>>> Most airlines, including all or nearly all major full-service
>>> international airlines, start selling tickets  at least 12
>>> months before the departure date for the 1st flight on an
>>> itinerary. =20
>> ...
>=20
>> I just tried availability for flights from London to San
>> Francisco for July 2018 IETF.   None of BA, Virgin or United
>> would offer tickets beyond January 2018.  Perhaps it's
>> different for internal flights within the US?
>=20
> I may be suffering from an arithmetic failure, but according to
> my calendar, January 2018 is 12 months out and anything past the
> first week of February 2018, such as July 2018, is significantly
> more than 12 months out.

You=E2=80=99ve selectively quoted Ran above. If you re-read his original
email, you=E2=80=99ll see that he said was that people *are* able to buy=20=

flights to San Francisco now, indeed that he knows people who have.
The bit you have included above claims most airlines sell tickets *at
least* 12 months in advance.

I was simply providing a data point contrary to that, i.e. I=E2=80=99m =
not able=20
to source a ticket to SanFrancisco for July 2018 now, because the
airlines I=E2=80=99d likely look to first don=E2=80=99t see more than =
11-12 months in
advance.

> I know that passions run high on this set of issues, but can we
> all please try to read each other's comments carefully enough to
> avoid confusing the discussions by (I presume accidentally)
> creating straw men and then attacking them?

I=E2=80=99m confused by your email John; all I was doing is giving a =
counter
point to Ran=E2=80=99s observation that people already have tickets to =
fly
in July 2018, but also that I agree that extending the IETF=E2=80=99s =
ability=20
to better support remote participation is now even more important. =20
Ran has since responded to both points politely and constructively.

Somewhat puzzled,
Tim

>=20
> best,
>     john
>=20
>=20


From nobody Thu Feb  2 16:17:48 2017
Return-Path: <jon.mitchell@microsoft.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C04E91299DC; Thu,  2 Feb 2017 16:17:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jon Mitchell <jon.mitchell@microsoft.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-bmwg-ipv6-nd-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148608106574.13846.5896586637971646869.idtracker@ietfa.amsl.com>
Date: Thu, 02 Feb 2017 16:17:45 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bgmj0Z_kzqU65qiqDp9CNe3-XOY>
Cc: draft-ietf-bmwg-ipv6-nd.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 00:17:46 -0000

Reviewer: Jon Mitchell
Review result: Ready


Document is ready, clearly written, and has limited operational
concerns due to nature of document and those I had were adequately
addressed by the security consideration section.



From nobody Thu Feb  2 16:18:42 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB5B41299DC; Thu,  2 Feb 2017 16:18:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MyQ7SYhwKxGT; Thu,  2 Feb 2017 16:18:25 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 A2EFD129A2A; Thu,  2 Feb 2017 16:18:24 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id e4so267740pfg.0; Thu, 02 Feb 2017 16:18:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=deEYrmpBvg11+JzjNRtxwV1Tsp8gPqKR4oNoJgnXoEA=; b=QYspm/+IdJmfnewoCYU3yPRcVN6etvbqMQd3yqmU6QjdJOdcS68S6fHBYgHI/f+EFF T5FAoYqFHNV0TWyhOyPYqEYX7U4XtfD4GcuT7ZaAC1U4oaO0V/Y5QSkEsDfjJ1rbg3YM qttkm8a7QLAQnEHC/qwGzs3EHJP7tMe0S8+BpQGvy1B31IsTSFw90JBy/isAWFlmZ+kg eeiSD36uPz4Yv6YL+SFTWofseuH1M8P2KjDB1MG2KRYGrjulJvJ58pwIS5D0cOPBGTv/ YVN0K/LcRGwoR5En0Tn+ZT+lp8nIBAMhONPXTViD2j8JGu+zOuqkbqYsRsT9OWZZdSbF G4Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=deEYrmpBvg11+JzjNRtxwV1Tsp8gPqKR4oNoJgnXoEA=; b=OPk7eWVaYwnsBDYoofn3GfzemG9aMG1oF89SngmCYTQBK3QHNWcKY7cCHpbmPx37XF UpwsEnQFOQVfHQ8c+t/XvVi0BH5QOG91uBBbB+wghhrtxDiAgJnBSntG3EejBLzH0MVo sCAGtLLkf50vVJ8JW0yhYZpH2ziall3UjI/byPDKwkQbND3qyBoD4AFdzZ4Py0QsdyJ+ bC/lfrzBED28n3ndghB7+cx4E8b0IQR9W/Oq5BI+JiNXhfX66aNoU7mfU+wb3gsTI6lf bHh67g2/bbMGxm90ufaXTojkEHnX5TpE8bh1CsHWUrXb6fdmoIhzuBvfQP1L7P+l/Rsw fXdg==
X-Gm-Message-State: AIkVDXIyOlk57oSEBbBVCxcTESvvEhZvyARlyi7oXEjXzffH0sUwbXdEuyTxXksVjjjZDw==
X-Received: by 10.99.127.71 with SMTP id p7mr14096551pgn.125.1486081104103; Thu, 02 Feb 2017 16:18:24 -0800 (PST)
Received: from ?IPv6:2406:e007:7909:1:28cc:dc4c:9703:6781? ([2406:e007:7909:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id p6sm61393109pfg.6.2017.02.02.16.18.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Feb 2017 16:18:23 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>, "Eggert, Lars" <lars@netapp.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com>
Date: Fri, 3 Feb 2017 13:18:27 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KZ4Ih-1vxoWZi2v1F_Ui5Q9iFWk>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 00:18:27 -0000

On 02/02/2017 22:54, Fernando Gont wrote:
> Hi, Lars,
> 
> On 02/02/2017 06:37 AM, Eggert, Lars wrote:
>> Hi,
>>
>> the last paragraph of the introduction reads:
>>
>> 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 over paths where
>> delivery of ICMP messages to a host is not assured.
>>
>> Given that ICMP delivery cannot be assured over the vast majority of
>> paths in the current Internet, should this document make a
>> recommendation to implement RFC4821?
> 
> I think that RFC4821 should be recommended, at least for dealing with
> ICMP blackholes (i.e., use ICMP if you can, but be able to deal with
> scenarios in which you don't receive them).

Many people think that, but this draft is constrained by the rules in
RFC6410 about "high degree of technical maturity" and "widespread
deployment" in the move from PS to Standard. Adding new stuff is not
supposed to happen. If I recall correctly, the WG tuned the language
to its present state for that reason.

    Brian


From nobody Thu Feb  2 16:26:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94BFF129621; Thu,  2 Feb 2017 16:26: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CC2laUhjOhyB; Thu,  2 Feb 2017 16:26:46 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 8AB4412956C; Thu,  2 Feb 2017 16:26:46 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 75so353861pgf.3; Thu, 02 Feb 2017 16:26:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=gt3dTuJyJp1XcssyPP9NRcpUJ7qdKxX+X0d4Ff+G5u4=; b=IeWftiZWkNKvSg/stAK0wFQGg4MmTaJjJ/NyOoELVHZdrqoQjQeTEixIwo/wuKcg25 fTwtTL6kX9y9J8kx1+hTBKGjtnbsWr9gYBfBe+gIHToDDafVmY9OflB3YDpzppL96WMu UVk0LIkj4HYllr+Ol7QuVCzdFtiyLooyhQDcOJTWgHMaswJJcZnkFBhAWZ/O/KevXhBQ IKIPISUd+nUombEfXKs7kygl/3Xo0VvF2GGtxmNG0YeBiEvIT0f3Xq3+3tw77ZXJwLDg iB2KWfYvyBgh+DBnOS1Zwgw+O4SZ7vwFmzYOezpWYzcUbbMycoUQ4/KDhmKAFPf28pkt hO9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=gt3dTuJyJp1XcssyPP9NRcpUJ7qdKxX+X0d4Ff+G5u4=; b=dB1hXMo9zvLoQE5lLqmusm6cS57Yab3H2S/GPFr9IjcIes1NSIQYTp6Myt+CqxPfn6 4umY9ImsuR+q6eVdGpfZass/8BQzHuDIExG4XNorAqvA0Y1CxolsGoZnEf2soacrWmYY QoPYMA/JPnbvI5xcWdNqQG1wIEavdZHxtcesa8oWpZSDg0U6f1VZJ2m7HSyC/bPdgIjD NrRFnRApCf6IoSXOYPw8dbyi9hPYmOzy2Kgi/REEWwKPr0ipt47lMROKU1/R5PrOp/2g 6kPynpgUwTnCUlVEOvihGcv6+yEdngriHOY6KYHvumySxtpLi2cviUkXFzPFm9qWUzkD pa0w==
X-Gm-Message-State: AIkVDXI0e+a/ZEIj9AGkZ4bhfQZ8uUdZDwpH4xZc0nAZCevEGHd7MZA2XGxhx8bTPx3jng==
X-Received: by 10.98.62.153 with SMTP id y25mr14382327pfj.162.1486081605984; Thu, 02 Feb 2017 16:26:45 -0800 (PST)
Received: from ?IPv6:2406:e007:7909:1:28cc:dc4c:9703:6781? ([2406:e007:7909:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k76sm61377499pfg.42.2017.02.02.16.26.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Feb 2017 16:26:45 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>, ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fbd92b47-5dba-909a-c0e5-e6430141d6dc@gmail.com>
Date: Fri, 3 Feb 2017 13:26:49 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SWF0uzXfba2BvOs9ThSlsVUy5v0>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 00:26:47 -0000

Hi Fernando,

On 02/02/2017 22:14, Fernando Gont wrote:
...
> The current impossibility to parse an IPv6 header chain that includes
> unknown Next Header values 

Wait... you're talking about parsing by intermediate systems. The destination
node either can understand the new Next Header or transport protocol,
or it can't. That's fine, and is the intended result.

> results in concrete implications for the
> extensibility of the IPv6 protocol, and the deployability of new
> transport protocols.  Namely,
> 
>  o  New IPv6 extension headers cannot be incrementally deployed.
> 
>  o  New transport protocols cannot be incrementally deployed.

In both cases, add "in the presence of interfering middleboxes".

This is not new. For a document moving from PS to Standard, it is
not something we can change.

Note, I am all for coming back to this problem, after we have the
Internet Standard in place. Maybe we can fix it or maybe we can't,
but it's IMHO off topic here.

Regards
    Brian


From nobody Thu Feb  2 16:38:16 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6478129A42; Thu,  2 Feb 2017 16:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VH4rClEGk1vJ; Thu,  2 Feb 2017 16:37:41 -0800 (PST)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (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 A7F781299F1; Thu,  2 Feb 2017 16:37:41 -0800 (PST)
Received: by mail-pf0-x242.google.com with SMTP id f144so288253pfa.2; Thu, 02 Feb 2017 16:37:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=kmRxbnBAxUXRGeuRCBw4ThRbxkANLNCkFlnF0viGqZo=; b=Zu8RwaJVWDx/a90Bb2KhO56ji8/04/WUkkbTXPgAJHVGMWrZmPqH6CUNb3weYZAzQq 5fqB7cnN6iBT8GD0Aau36SDJRH+I7yU0SLePTH9SD2+lXKvsthjTyXBAnMp+SMq/dazS LDFvdCw7q5EANJ5YjqaveUkcIhUAvDVxnjjAfqdnArekx4II8oPRiGaD/WkKUveuzCpJ kNA0CxLQC7Lg+GYc/wQJK9FcfxHj4fMdvmiKzbm7hGcvkUI+FnU6Y5Wimvv4Pa5IFWlg A7aDfhS9ZsY4wBy5lLsJSXlW1y7SgL03C6kx0Twe48fEV8U0i9jAQ8SCHNZx3mBe9vEa gMNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=kmRxbnBAxUXRGeuRCBw4ThRbxkANLNCkFlnF0viGqZo=; b=uayZk1p7uvC8r3FY97r3HgxqpoNZpGmvgyGeODvjAwniRwnSlcr2CvUK8wiYq8Xreq WRSmP8yxJ/e0UFdw+6jWJrNlIhb8t2Qt/saIhgSS/rMUNYZR5C5ZJh0UVqSpMEsrTIjD Au0PM1//U++9SxKP4a5AgYZ5JUGIi9yUOQLS5XStX61kQ3hoVCZsjc0XsofWDn7Sw2PO kJ38Fza64YTgXYQbq36A4nPJE0KNRmFnFp0Uq6FlIigQl6jRycCTy6LrFqpJHVkjLOod ulmPYh6I0hBr0D4jWRWbsLQgi/ujnQrAU2mkB60/9X5JR8VIQbcfxaeFUrLyELKnrmTk yMvg==
X-Gm-Message-State: AIkVDXK1G1f5dsGJ+j/OPryaCrRza6xXUyR+CUbc7LsnyzH4tLJlD5hG9vqhoL3nGfkW9A==
X-Received: by 10.98.217.88 with SMTP id s85mr14259095pfg.167.1486082261041; Thu, 02 Feb 2017 16:37:41 -0800 (PST)
Received: from ?IPv6:2406:e007:7909:1:28cc:dc4c:9703:6781? ([2406:e007:7909:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id l22sm61816540pgc.43.2017.02.02.16.37.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Feb 2017 16:37:40 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
Date: Fri, 3 Feb 2017 13:37:45 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/myyPO9b4dYfYeGQrdPjTNzIHArY>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 00:37:43 -0000

In Section 4 ("IPv6 Extension Headers") the draft says:

>    With one exception, extension headers are not processed by any node
>    along a packet's delivery path, until the packet reaches the node (or
>    each of the set of nodes, in the case of multicast) identified in the
>    Destination Address field of the IPv6 header.

(FYI, the exception is the hop-by-hop extension header.)

I do not dispute that this sentence reached WG consensus. However, I want
to ask if it has IETF consensus. In my opinion, this sentence should read

   With one exception, extension headers are not processed, inserted,
   deleted or modified by any node along a packet's delivery path, until
   the packet reaches the node (or each of the set of nodes, in the case
   of multicast) identified in the Destination Address field of the IPv6
   header.

I believe this was always the intended meaning of the word "processed"
from the earliest design phase of IPv6, but some people have read this
text as allowing insertion, deletion or modification of headers. IMHO
it needs to be clarified.

Regards
   Brian Carpenter


From nobody Thu Feb  2 17:45:08 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C6E129A84; Thu,  2 Feb 2017 17:45:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 8xZ75ewcTG3p; Thu,  2 Feb 2017 17:45:05 -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 C993B129A82; Thu,  2 Feb 2017 17:45:05 -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 v131j5Gq024190; Thu, 2 Feb 2017 18:45:05 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v131itsT024041 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 2 Feb 2017 18:44:55 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 2 Feb 2017 17:44:54 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1178.000; Thu, 2 Feb 2017 17:44:54 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AQHSfTVX3cTpaXTixEijFBMfWr8vTaFW9yqA//+KztA=
Date: Fri, 3 Feb 2017 01:44:54 +0000
Message-ID: <3bd957ff52cb4da5bdf9b842198d858d@XCH15-06-11.nw.nos.boeing.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
In-Reply-To: <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZzPNSdhfO1znp64D6Y3uG6Eig2Y>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 01:45:06 -0000

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian E Carpenter
=20
> In Section 4 ("IPv6 Extension Headers") the draft says:
>=20
> >    With one exception, extension headers are not processed by any node
> >    along a packet's delivery path, until the packet reaches the node (o=
r
> >    each of the set of nodes, in the case of multicast) identified in th=
e
> >    Destination Address field of the IPv6 header.
>=20
> (FYI, the exception is the hop-by-hop extension header.)
>=20
> I do not dispute that this sentence reached WG consensus. However, I want
> to ask if it has IETF consensus. In my opinion, this sentence should read
>=20
>    With one exception, extension headers are not processed, inserted,
>    deleted or modified by any node along a packet's delivery path, until
>    the packet reaches the node (or each of the set of nodes, in the case
>    of multicast) identified in the Destination Address field of the IPv6
>    header.
>=20
> I believe this was always the intended meaning of the word "processed"
> from the earliest design phase of IPv6, but some people have read this
> text as allowing insertion, deletion or modification of headers. IMHO
> it needs to be clarified.

I also prefer Brian's text. Just remembering that it took a long time to re=
ach consensus. My impression was that some people preferred to retain the a=
mbiguity. But not me, so I vote for Brian's clarified text. One extra comma=
, though: "... inserted, deleted, or modified ..."

Bert



From nobody Fri Feb  3 00:15:30 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA93E12951F; Fri,  3 Feb 2017 00:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.12
X-Spam-Level: 
X-Spam-Status: No, score=-10.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUfTHXHKEL4H; Fri,  3 Feb 2017 00:15:23 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C65129BCA; Fri,  3 Feb 2017 00:15:21 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,328,1477983600";  d="asc'?scan'208";a="174621007"
Received: from hioexcmbx02-prd.hq.netapp.com ([10.122.105.35]) by mx144-out.netapp.com with ESMTP; 03 Feb 2017 00:06:38 -0800
Received: from VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) by hioexcmbx02-prd.hq.netapp.com (10.122.105.35) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 00:14:09 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Fri, 3 Feb 2017 00:14:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=+Pyb76B1ZcbLhc8hMAqGA8FyaL35bgZ40dKO/rW3HNo=; b=gcjkSQDp02y2zliwgG1zEqJcMPLE0X5WvYYbr0CfdFSlPew6puR4P4UYk6Lg1PKd6NAs8Sc6EFRQEmOh80DNLjraMADvFFjG07an/127QCm2t1yVLub0Mzm+dgNGCRUNHfhnm3XMcf2HqeIh9GSYnN3FfwQqsfpydklSL83Kgvg=
Received: from BY1PR0601MB1158.namprd06.prod.outlook.com (10.160.196.21) by BY1PR0601MB1158.namprd06.prod.outlook.com (10.160.196.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.803.11; Fri, 3 Feb 2017 08:14:07 +0000
Received: from BY1PR0601MB1158.namprd06.prod.outlook.com ([10.160.196.21]) by BY1PR0601MB1158.namprd06.prod.outlook.com ([10.160.196.21]) with mapi id 15.01.0803.024; Fri, 3 Feb 2017 08:14:07 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAAEwQCAAPFzgIAAhOSA
Date: Fri, 3 Feb 2017 08:14:06 +0000
Message-ID: <B843C372-D521-47F1-A9BE-61CFB5E1D11A@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com>
In-Reply-To: <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: 9a568e16-a1ef-4fd7-5a66-08d44c0c9fee
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BY1PR0601MB1158; 
x-microsoft-exchange-diagnostics: 1; BY1PR0601MB1158; 7:oD6OfqHldt4waZmxFAqYvq0EjP1P9IvRA/qNGIy/BEbYuxCSdgzKedIL1YWigDSl1PKMzYZNuBhAcJ106poMKl321M2a4vEmX7DZdaZr7uOkZ6ixf/ZoSontGr8EULBjrtgWWme6DYneQ+uuEpyk6UnDIdemVYZsSiwWs4QHq11kf/DvAdCMynO7SPgu8NMYQhvIHk4Fd7yrnxUIVnkQgnbgKf+jLQ/wUKA902DGMrqkxaoy3OIV/QZ8uHxcb7DNX/A3VyNL0ZPT28YgT+NZVxaxd/ORBal53SLuLJe1Jm+/U1U1T+mzGO927woplK01EbGzy0Hstn9Hu3MZg7rGu35C8SWkshVazuIIencMYHSUmPQ0uP46Cstmy+l1e0mKmy6QMPcpx2msDSiwXhRSwbDs02HVnfb+Hn2vdi1EwI9obvfIo3Tnu/NGsWwEc3oe
x-microsoft-antispam-prvs: <BY1PR0601MB115857CB2152D7F49A6BCC12A74F0@BY1PR0601MB1158.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123562025)(20161123558025)(20161123560025)(20161123564025)(20161123555025)(6072148); SRVR:BY1PR0601MB1158; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0601MB1158; 
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(377454003)(51444003)(377424004)(189002)(24454002)(2906002)(93886004)(68736007)(39060400001)(81156014)(83716003)(3280700002)(230783001)(102836003)(3846002)(99286003)(2950100002)(54906002)(6116002)(4326007)(6916009)(3660700001)(189998001)(122556002)(6512007)(106356001)(82746002)(2900100001)(33656002)(8936002)(76176999)(50226002)(5660300001)(97736004)(53936002)(8676002)(110136003)(305945005)(106116001)(53546003)(105586002)(6506006)(4001150100001)(57306001)(77096006)(38730400001)(6436002)(25786008)(6486002)(50986999)(6246003)(86362001)(7736002)(36756003)(101416001)(66066001)(92566002)(229853002)(81166006)(99936001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR0601MB1158; H:BY1PR0601MB1158.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_5514083F-9D93-4A1A-98AB-F9B33976BD89"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 08:14:06.9942 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0601MB1158
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/11xs670JjXDJ3s5lhMj3j34NpfE>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 08:15:25 -0000

--Apple-Mail=_5514083F-9D93-4A1A-98AB-F9B33976BD89
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-3, at 1:18, Brian E Carpenter <brian.e.carpenter@gmail.com> =
wrote:
> On 02/02/2017 22:54, Fernando Gont wrote:
>> On 02/02/2017 06:37 AM, Eggert, Lars wrote:
>>> Given that ICMP delivery cannot be assured over the vast majority of
>>> paths in the current Internet, should this document make a
>>> recommendation to implement RFC4821?
>>=20
>> I think that RFC4821 should be recommended, at least for dealing with
>> ICMP blackholes (i.e., use ICMP if you can, but be able to deal with
>> scenarios in which you don't receive them).
>=20
> Many people think that, but this draft is constrained by the rules in
> RFC6410 about "high degree of technical maturity" and "widespread
> deployment" in the move from PS to Standard. Adding new stuff is not
> supposed to happen. If I recall correctly, the WG tuned the language
> to its present state for that reason.

So in that case IMO the WG has made the wrong decision by trying to take =
this to Standard. A rev at PS that had brought the content up-to-date =
with regards to Internet reality would have been the better choice.

Lars

--Apple-Mail=_5514083F-9D93-4A1A-98AB-F9B33976BD89
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYlDvNAAoJEFS1wwm/cMFXFzUP/idvOMoAA5yAbjNqQzbfzLCD
txIs/qhNvQbTgioiQFLTIj9Hggu3o/oxiVEbcx6YK54iv7BJDPVz8IzfGV7qWzo8
gQmPhj2kh/5fL68mE32HkcUUhpduSmYkQIFcJNv2DZWuepWAMjP/nylnwY7cTkxR
lshHKl8iHal2vYFKmXsb2ZeivPuP/aTPSFxoE3VUX8Ui7Dp0AuJYot+fV6/LUqgG
S+8mrELdUkb+xqXx6MDYhZxsBgQnlwLfnH4LhZ8LvX5oQYNOKCx2N8q6c50kD8Hl
6cgRy8jyQhZc/FiGw60RE5Zhz1ISvFflbrrNc9NhHHwGPwFAgTn960rK0YUy4sSr
8+eh67sbxJQOviW3wwh33sTTKKOYaw5ACLFPOV8n1D7f74VGUTvd1UV67BKSCWHB
Adhqf6f0B0mZ7MMgqKDG1Y9rR+SBWbAKM7AnIaHfTlF5LPe2qVFGMXmIT6CJjxu2
kQOXnvwPqSRA7+sossl63ApisUqLzVl233d6onrI0XkzxkARO5kSTiT2jET8/XAd
kJfBxJptZEG2qy7UvMn9Bc19bSIhelAGUIOwkyQeOck1Hen3CnBO3M/7VzxtL36k
vZp9cyJSusffP/o7tMksm0gd9OEOLV9kPraxI5mDnN/85lpjP94NbAg/kkit67dv
/ut9mIUX0JyYyzJ/SVy6
=Rs4m
-----END PGP SIGNATURE-----

--Apple-Mail=_5514083F-9D93-4A1A-98AB-F9B33976BD89--


From nobody Fri Feb  3 00:38:36 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77235129BC7; Fri,  3 Feb 2017 00:38:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GTb_jWvSSAAw; Fri,  3 Feb 2017 00:38:33 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1BF129614; Fri,  3 Feb 2017 00:38:32 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 03 Feb 2017 08:38:31 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id D111ED788B; Fri,  3 Feb 2017 00:38:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=6hnT1XCnzUhWYmVCYMLIX9AdQqs=; b= Tuu954lgKMXR9uEx6JwNUEw1x4G/nbGupietXI5MeNraeHKjvKZSJLeyWM34JUOM tfeD61p5oFNN+rKf1QzhLTmvOgwcYFBx8Us8THm0zhOkjIfbK6YkUx9Desu4pzZs 9gbvkAkss39cbQmkeqlVF98oPbiM7dYJwdFGAHAkvZI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=nvtjr1OlaQAFXcR4DQMQHXW whQLYLdFlLyxYLYwXW+XP3r0Q3EtRsrGfynHuUsJ40bIaGQaeauAOAreMe19cq+P 1ExOATajSFFtzCmsemH9sOFuaYI4woDGd//4r3TCnqIEQ1ia/oinXgfJkCQjWgeG gWOiMvt1rxL5lsNjEupE=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 9719CD788A; Fri,  3 Feb 2017 00:38:30 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B3D42835CCD3; Fri,  3 Feb 2017 09:38:28 +0100 (CET)
From: otroan@employees.org
Message-Id: <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_EF4ACE04-CDB3-4D4A-92A5-DCA87BE891AC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Fri, 3 Feb 2017 09:38:28 +0100
In-Reply-To: <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wM64yH80xDu_5QN3LyEsUBe_uTo>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 08:38:34 -0000

--Apple-Mail=_EF4ACE04-CDB3-4D4A-92A5-DCA87BE891AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lars,

> the last paragraph of the introduction reads:
>=20
>   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 over paths where delivery =
of
>   ICMP messages to a host is not assured.
>=20
> Given that ICMP delivery cannot be assured over the vast majority of =
paths in the current Internet, should this document make a =
recommendation to implement RFC4821?

Could you please substantiate that assertion?

Best regards,
Ole

--Apple-Mail=_EF4ACE04-CDB3-4D4A-92A5-DCA87BE891AC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYlEGEAAoJEL7aWKiYQt92HzMP/iJveKUbRBcw+AcC2fvG9odD
Mimh5vMjNTV+9+ffwK+kx2QBPbsByUtaQ8W5tp5Eiogc/ZiJUeFCW5JHIL+23b55
xfZP4YGBgiU1UD2clNw3CRGk+W8bDpe/Ip12mvMiYLc7vBrzZD/0Fe/G3LivLv8M
jDmbFKL1pzq6MXhdz5l3h8MLN1ARJrSro3U/SNvpA7CXr5KwmaKDx3/m8ClyTH5E
E1QUyHQslsZ0XhV7m98E34UDaAtLvL80FyX7yaBrmhP19J3ycbwS9KxIFMLUc0DT
8zZgTCHvCWWok95IWmbpRPgRJEeso9JdDTv6DwOLTXWHZoFso5vmODcuU12sGlQU
W8chUcrPpsTZH6D4PM6X/XhvYCAi5Lb67js08lznNfyHru8S33JnGqp9eP1QjAem
5OuLFjqGoJ6YpgXQ5nFAZnrbefqvPd3ANLgDyoNs6nB5S16wDfnRoRwIflunP8Gl
B9ehrFA1uDyUSdRAenLZseBnMCOeL42+Ha78lZBGDnzeXlHU96qWL4fFvMGcBwPd
9yyB0m8QAwZFbPe25MZacP4tF0nDnyTCtX83Y7KfAbzhnS+7OGEtoa8/9y1Ln5WA
C8bknOGfUGBSYmCsXuFMudHYuQDGz/B95Jx/DKZ4Slg6Z0NnXTCH95q4pEjmLRfU
lLVvryLXe4V7yVbPIbuv
=CpOC
-----END PGP SIGNATURE-----

--Apple-Mail=_EF4ACE04-CDB3-4D4A-92A5-DCA87BE891AC--


From nobody Fri Feb  3 00:51:26 2017
Return-Path: <sprevidi@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 769AA12951F; Fri,  3 Feb 2017 00:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.72
X-Spam-Level: 
X-Spam-Status: No, score=-17.72 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U2z6wFy3ekez; Fri,  3 Feb 2017 00:51:24 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09F60129503; Fri,  3 Feb 2017 00:51:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1624; q=dns/txt; s=iport; t=1486111884; x=1487321484; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=vqwMp/m47S5fzFPKbk0N22RpfWpg3jUwQhwExA6Q/ns=; b=R3+8tho/j6/ZJ7KV/8ux0OMCE+NY2eq1hm5esIDg3frrrkwbhF14ynSJ OGQknk+rvE46m+AJF9yv1fTq0Tx7O1u6ZPxCF6F0E5/vORJJ2wAjSxNYT 6EoWC3DPR1uKjd82ess5HijZay8CspSGbjKqvLv/K/NColxkgv+AQOTC/ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AeAQBTQ5RY/4MNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQkHjVmSCogNjSmCDR8LhXgCglg/GAECAQEBAQEBAWIohGk?= =?us-ascii?q?BAQEDAQEBODQLBQsCAQgYHgULIQYLJQIEDgWJWQMNCA6vFoc8DYNxAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBGAWGS4IFgmqCUYFMMIM0gjEFiQeSIjgBjW+EFwqBcYh?= =?us-ascii?q?khiOKLIhcAR84gUsVOxEBhGiBSHUBhmOBMIEMAQEB?=
X-IronPort-AV: E=Sophos;i="5.33,328,1477958400"; d="scan'208";a="193695574"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Feb 2017 08:51:23 +0000
Received: from XCH-RTP-010.cisco.com (xch-rtp-010.cisco.com [64.101.220.150]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v138pMWM025492 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 Feb 2017 08:51:23 GMT
Received: from xch-rtp-010.cisco.com (64.101.220.150) by XCH-RTP-010.cisco.com (64.101.220.150) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 03:51:22 -0500
Received: from xch-rtp-010.cisco.com ([64.101.220.150]) by XCH-RTP-010.cisco.com ([64.101.220.150]) with mapi id 15.00.1210.000; Fri, 3 Feb 2017 03:51:22 -0500
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AQHSffqxgH1E6/XKwki6PXlTKRp6/g==
Date: Fri, 3 Feb 2017 08:51:22 +0000
Message-ID: <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
In-Reply-To: <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.250.223]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7E4536BA5CDC0D4DA9E3A4610E5012AB@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OxKs6MNNI9428xjI3jlRqvG9vwk>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 08:51:25 -0000

> On Feb 3, 2017, at 1:37 AM, Brian E Carpenter <brian.e.carpenter@gmail.co=
m> wrote:
>=20
> In Section 4 ("IPv6 Extension Headers") the draft says:
>=20
>>   With one exception, extension headers are not processed by any node
>>   along a packet's delivery path, until the packet reaches the node (or
>>   each of the set of nodes, in the case of multicast) identified in the
>>   Destination Address field of the IPv6 header.
>=20
> (FYI, the exception is the hop-by-hop extension header.)
>=20
> I do not dispute that this sentence reached WG consensus. However, I want
> to ask if it has IETF consensus. In my opinion, this sentence should read
>=20
>   With one exception, extension headers are not processed, inserted,
>   deleted or modified by any node along a packet's delivery path, until
>   the packet reaches the node (or each of the set of nodes, in the case
>   of multicast) identified in the Destination Address field of the IPv6
>   header.
>=20
> I believe this was always the intended meaning of the word "processed"
> from the earliest design phase of IPv6, but some people have read this
> text as allowing insertion, deletion or modification of headers. IMHO
> it needs to be clarified.


are we re-spinning the debate on a WG-agreed text ?=20

s.


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


From nobody Fri Feb  3 02:06:01 2017
Return-Path: <naeem.khademi@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 860F2129415; Fri,  3 Feb 2017 02:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aZPlxVfK514u; Fri,  3 Feb 2017 02:05:59 -0800 (PST)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 3C8DC128AB0; Fri,  3 Feb 2017 02:05:59 -0800 (PST)
Received: by mail-io0-x230.google.com with SMTP id j13so13870050iod.3; Fri, 03 Feb 2017 02:05:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yLKtyn6mtaSjw9I6sNW9DaosZHhncnbTtCfCTeCSzuA=; b=ipon+crCX4t3CW1HttWN8desgwPbg7VaIiFSw9iejQRzxc3vUQH4WQ+QTu8TQTHVdg H5KKdm8mYkI9amzwOpcrHoFxkGy+BAiSFK8B5Jo9IFx61QA2nnaV3KwDhqj57/Jvas/d BxS4qbfuxRN5UvkIeZX/MHuZjvRXsRxIo/1oR2S96JZ12BHXUjUT06rF5Mz9iUlXvOc2 MuxPbwYnfaDRNWMfqnLwtNup2/tM/20ZacssvvwKqDa9G5XZisHXIVg1YzvFnRHikVYE YPe6eyNXUgfllfwye9itFUDM8qm2zbx26szGSmVTlNUgATKHaOmVvS83TNngK1lrr3aW llHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yLKtyn6mtaSjw9I6sNW9DaosZHhncnbTtCfCTeCSzuA=; b=YP+cPwv53O17U5vK9eo9gJWr8M0T61sBOg/t0+ivDUT1NDjV9IlcUMAi4hEh26aDY4 5ymObB8NiixCK6Z+ckt27ecJ+ruhWvviaXSL+5NQlZLoIkx+9Kcdf/xojFivud6xhdaU ikk/IRUA7u+Lg0YXutWoWCcpIT/EzuRHuIApIrtvF0DBEaKL9x8OExw1u+YnP5ul3tx4 OXrtiCrtVgJxalLl4vBAfSbXT2TVWGhN+aWzMYTKcCzp7dh/mujTCrhIdUybqZqAahyJ A1ve3VwojE3dWkfDmcGdyrXkqZY45RN37I4lfT883SE4FIWQp9Rr7Kfb52wIbuRE0+1f m1dQ==
X-Gm-Message-State: AIkVDXKDmAHT+foZjexlBb9ZlALuxGeiOOlp1lYanSAKb99etB3kicT+5T1k/RDuykL3QYplO7fx1Q/2NiMKYA==
X-Received: by 10.107.148.141 with SMTP id w135mr10967433iod.229.1486116358392;  Fri, 03 Feb 2017 02:05:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.178.210 with HTTP; Fri, 3 Feb 2017 02:05:57 -0800 (PST)
In-Reply-To: <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com>
From: Naeem Khademi <naeem.khademi@gmail.com>
Date: Fri, 3 Feb 2017 11:05:57 +0100
Message-ID: <CAEjQQ5Wn7ig+Cgh68SXdK5AYO478BpN-doNx5m-5K_ocuxWz9g@mail.gmail.com>
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
To: Randal Atkinson <rja.lists@gmail.com>
Content-Type: multipart/alternative; boundary=001a113f9fe2a3133c05479d6d06
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SKsTbQnTr7XR8-VlkHrTHqwWc6w>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 10:06:00 -0000

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

On Thu, Feb 2, 2017 at 4:39 PM, Randal Atkinson <rja.lists@gmail.com> wrote=
:

>
> > On 31Jan2017, at 04:44, Naeem Khademi <naeem.khademi@gmail.com> wrote:
> >
> > The next IETF in the US after Chicago, would be in July 2018 in SF. I
> don't think it's even possible
> > to buy a flight ticket for that time as of now (most airlines wouldn't
> do such pre-sale). So, it's pretty
> > much possible to relocate that meeting elsewhere with causing no loss t=
o
> anyone's already-made plans.
>
> The claim above that "most airlines won=E2=80=99t sell 6 months in advanc=
e" is
> false.
>

Since you're quoting me (calling it "claim above"), I have a hard time
finding the exact text you're referring to in my writing ;-). I stated that
most airlines wouldn't do such a pre-sale for July 2018 (IETF @SF) which
happens 16 months in the future, so I stay correct.

Regards,
Naeem


> Most airlines, including all or nearly all major full-service
> international airlines, start selling tickets
> at least 12 months before the departure date for the 1st flight on an
> itinerary.
>
> To my knowledge, there are some people who already have purchased tickets
> to go to IETF in SFO.
> This really ought not be surprising as the lowest-cost fares often
> sell-out earliest.  A number of
> IETF people don=E2=80=99t work for big companies and are traveling on the=
ir own
> money.   Those people
> would suffer greatly from a change in location less than 12 months out.
>
> I am aware that some have suggested the IETF do more remote meetings.  I
> think that is worth
> exploring.
>
> I certainly would support IETF making all future meetings more accessible
> remotely  =E2=80=94 and I think
> that is a goal the IETF has been making progress on for some years now,
> using Jabber, VTC,
> and so forth.  Expanding the remote access capabilities and coverage for
> all future meetings
> (to the extent that is practical at a given point in time) only makes
> sense.
>
> Yours,
>
> Ran
>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Feb 2, 2017 at 4:39 PM, Randal Atkinson <span dir=3D"ltr">&lt;<=
a href=3D"mailto:rja.lists@gmail.com" target=3D"_blank">rja.lists@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""><=
br>
&gt; On 31Jan2017, at 04:44, Naeem Khademi &lt;<a href=3D"mailto:naeem.khad=
emi@gmail.com">naeem.khademi@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The next IETF in the US after Chicago, would be in July 2018 in SF. I =
don&#39;t think it&#39;s even possible<br>
&gt; to buy a flight ticket for that time as of now (most airlines wouldn&#=
39;t do such pre-sale). So, it&#39;s pretty<br>
&gt; much possible to relocate that meeting elsewhere with causing no loss =
to anyone&#39;s already-made plans.<br>
<br>
</span>The claim above that &quot;most airlines won=E2=80=99t sell 6 months=
 in advance&quot; is false.<br></blockquote><div><br></div><div>Since you&#=
39;re quoting me (calling it &quot;claim above&quot;), I have a hard time f=
inding the exact text you&#39;re referring to in my writing ;-). I stated t=
hat most airlines wouldn&#39;t do such a pre-sale for July 2018 (IETF @SF) =
which happens 16 months in the future, so I stay correct.=C2=A0</div><div><=
br></div><div>Regards,</div><div>Naeem</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
Most airlines, including all or nearly all major full-service international=
 airlines, start selling tickets<br>
at least 12 months before the departure date for the 1st flight on an itine=
rary.<br>
<br>
To my knowledge, there are some people who already have purchased tickets t=
o go to IETF in SFO.<br>
This really ought not be surprising as the lowest-cost fares often sell-out=
 earliest.=C2=A0 A number of<br>
IETF people don=E2=80=99t work for big companies and are traveling on their=
 own money.=C2=A0 =C2=A0Those people<br>
would suffer greatly from a change in location less than 12 months out.<br>
<br>
I am aware that some have suggested the IETF do more remote meetings.=C2=A0=
 I think that is worth<br>
exploring.<br>
<br>
I certainly would support IETF making all future meetings more accessible r=
emotely=C2=A0 =E2=80=94 and I think<br>
that is a goal the IETF has been making progress on for some years now, usi=
ng Jabber, VTC,<br>
and so forth.=C2=A0 Expanding the remote access capabilities and coverage f=
or all future meetings<br>
(to the extent that is practical at a given point in time) only makes sense=
.<br>
<br>
Yours,<br>
<br>
Ran<br>
<br>
</blockquote></div><br></div></div>

--001a113f9fe2a3133c05479d6d06--


From nobody Fri Feb  3 02:22:58 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A563129B8A; Fri,  3 Feb 2017 02:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.119
X-Spam-Level: 
X-Spam-Status: No, score=-10.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TJpY0cRuWuue; Fri,  3 Feb 2017 02:22:52 -0800 (PST)
Received: from mx142.netapp.com (mx142.netapp.com [216.240.21.19]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23693129A82; Fri,  3 Feb 2017 02:22:52 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,328,1477983600";  d="asc'?scan'208";a="169079977"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx142-out.netapp.com with ESMTP; 03 Feb 2017 02:15:00 -0800
Received: from VMWEXCCAS09-PRD.hq.netapp.com (10.122.105.27) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 02:21:47 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS09-PRD.hq.netapp.com (10.122.105.27) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Fri, 3 Feb 2017 02:21:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=DXl8b6Gck+R+sbZRn+o3X1bIPoogSTz1S9nZvbrqjNU=; b=HrzuxIlwxiaVhNYtbS5FYBTJXevhp7sY4oFogv342HdlUD1qYmc9WO5T9GawDfwNyWUh0VFzL7e+3ttwH5tp5DXH7MKaojXC1lMDlAu0nnraIvsscbIIG00dslDe00ayxeOy+qX9V8qHqKyCMIvjl7LYNl44LcpAIrzipc7eAxc=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Fri, 3 Feb 2017 10:21:47 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.025; Fri, 3 Feb 2017 10:21:47 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAGB6ACAABzbgA==
Date: Fri, 3 Feb 2017 10:21:47 +0000
Message-ID: <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org>
In-Reply-To: <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: 5486baec-7d8c-4d15-767e-08d44c1e75a9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1153; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1153; 7:d5ywUeIGYbov9lCXABrLXiUdUbjpoWxSP57m7RNmfxL0IUghZZvgxSAnTB6jCDaJZrDDwj+oPo9/rvknLdI9kMaG0tum33pNMgK1DUM3K3xLYAT1bErB2WGQQrFJUyiCbR+/l06cM7Isj/7+1bMCk1QJD52L07/Gj8zYNsSMUXwsNTs2S/Yj2wwSTvLKK8FghN7vGdDFe6oGAlFBfA8hIMuYx+PP+hHpDLSPJMQ0Ce7X0mvBnJhA72tzcNh9jZuvnoOC085audKT+XH7FyHd0JFFwafMByJZ0D04/RI1yCNJWAXWZ9HPE8L0Gh5g6XxsLj3Mw1SCt/LHLBKNde/jyeTm241pLWKXuyqPuGiVOL0WQhmwLxT0scMbxHAsoU8Cq/uqRii9N2fF7zzUsDuxTMflohYR0GFWrmBM2YOxSFEucr8t3wZIuY1B6wCOfZZzFoSC0rwUIL2PXnLj3GLPWfnGAqgFvTSo9xcRJMcZVybWgd5rgv9qRzxXLfhLTpIGMnOoZYdnF5FfwN654DI1JA==
x-microsoft-antispam-prvs: <BN3PR0601MB1153D2301C0CA6FAB8B92BFDA74F0@BN3PR0601MB1153.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(76576733993138)(165104125076784);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:BN3PR0601MB1153; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1153; 
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(377424004)(199003)(24454002)(189002)(83716003)(53936002)(6512007)(92566002)(3660700001)(6506006)(229853002)(99286003)(2351001)(4326007)(6246003)(3846002)(106116001)(105586002)(6306002)(106356001)(82746002)(2501003)(66066001)(122556002)(54906002)(53546003)(86362001)(102836003)(6116002)(230783001)(33656002)(57306001)(5660300001)(110136003)(99936001)(38730400001)(2900100001)(2906002)(68736007)(8676002)(6916009)(2950100002)(5640700003)(81156014)(81166006)(1730700003)(6436002)(50986999)(76176999)(25786008)(4001150100001)(8936002)(305945005)(7736002)(77096006)(101416001)(6486002)(97736004)(36756003)(50226002)(3280700002)(189998001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1153; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_86CC7C58-C35D-42AF-9A24-173113CEEEE6"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 10:21:47.0352 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1153
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iyjAN2sGN5mEQKzTK64V02J_Twc>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 10:22:53 -0000

--Apple-Mail=_86CC7C58-C35D-42AF-9A24-173113CEEEE6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-3, at 9:38, otroan@employees.org wrote:
>> Given that ICMP delivery cannot be assured over the vast majority of =
paths in the current Internet, should this document make a =
recommendation to implement RFC4821?
>=20
> Could you please substantiate that assertion?

Matthew Luckie and Ben Stasiewicz. 2010. Measuring path MTU discovery =
behaviour. In Proceedings of the 10th ACM SIGCOMM conference on Internet =
measurement (IMC '10). ACM, New York, NY, USA, 102-108. =
DOI=3Dhttp://dx.doi.org/10.1145/1879141.1879155

PDF here: https://www.caida.org/~mjl/pubs/measuring-pmtud.pdf

"This paper measures PMTUD behaviour for
50,000 popular websites and finds the failure rate in IPv4
is much less than previous studies. We measure the overall
failure rate between 5% and 18%, depending on the MTU of
the constraining link."

5-18% is pretty bad. I would expect that the widespread deployment of =
CGNs since this was published in 2010 to not have improved things.

Lars

--Apple-Mail=_86CC7C58-C35D-42AF-9A24-173113CEEEE6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYlFm5AAoJEFS1wwm/cMFXyYgP/0dugje7dbWNU6VoN2PgVpA2
Jhb9P03D2xNwoyzg/KAzLeIzqIE4nn5JyTLUCRV+tD2vmF9TnqD4VKlmt7yZNg5r
yIXMrJn8D/nPa10rw2mSdEjvWMok1hGo55TyDWtpByGMFuCnM95aXDih3F+4M2Pn
YEH4CE9Lqpj9a8zmxu3b7noQeeDYbFXrv8uLT8hphOJWVAX2Mmm7KKaR0CZtyO/V
N1upn6/TOwPjlu49zkyfpEpLUlBdwwzb8wqmsLSvKdLKDIZTicIwkjL5Vu+1Uqbx
uDcMXHrSQSgss9psitk1435DiG01nUXNnsEnne4c/kAMDWdj5Ihtc2R2uROst4C9
krMSSqJymCgRVVHdp2f32IEIddJw5vHdVwMWIXEb7l/8AVaGpzQW7QYHTSaz63Gl
oZ1rvQcmoO3mRZDpyUhwEaSyez93Hddt3WhkILncOePAl9n9uksk0p3wklSiFuhC
mewa7bu7PzDMIhTSWFfHi+6IsIL/UfHhohCb93ZrvHtywNtAt4o+Zu0kWRC0qZU6
owTaHj6CNCn5YR4t71BJlNHYu5d1mIiLxY3SNLrZKpcL2U+SzRWIhc+tJfPLT2uF
/CQ40iyKuVprbuZNSkZjBgiT4/D12FbxUQcvaIhcXrxN38MW8XQbDyV+Qg2dWBaH
4v4ohI2mDam4yhjQULYW
=QGz6
-----END PGP SIGNATURE-----

--Apple-Mail=_86CC7C58-C35D-42AF-9A24-173113CEEEE6--


From nobody Fri Feb  3 02:23:22 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34C01129BEE; Fri,  3 Feb 2017 02:23:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.119
X-Spam-Level: 
X-Spam-Status: No, score=-10.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fw3zO6OLsBbg; Fri,  3 Feb 2017 02:23:04 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B190129BE7; Fri,  3 Feb 2017 02:23:01 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,328,1477983600";  d="asc'?scan'208";a="174636846"
Received: from vmwexchts04-prd.hq.netapp.com ([10.122.105.32]) by mx144-out.netapp.com with ESMTP; 03 Feb 2017 02:15:12 -0800
Received: from VMWEXCCAS01-PRD.hq.netapp.com (10.122.105.11) by VMWEXCHTS04-PRD.hq.netapp.com (10.122.105.32) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 02:22:44 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS01-PRD.hq.netapp.com (10.122.105.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Fri, 3 Feb 2017 02:22:44 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=hs5BSrAlhJ1Fh6YOCA8j/L9Dn+ivCDgf8ng05DgAa3o=; b=ayl9F46HfjiemYc4LOozdUbGRhIBIXu0rk1s5uYmfSKtIPR3REdLeCoUxSr4T3DlsRIAf6qBM/9pE5JLrQoDhXD+5ianOPdaQOZr65pSsHrm/IyVgM1tz70fUjtAT3gvbHEqEOjXh3VaTez/OHUDT/uk+MbkWAunv7mV0a+gzLw=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Fri, 3 Feb 2017 10:22:43 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.025; Fri, 3 Feb 2017 10:22:43 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAGB6ACAABzbgIAAAEOA
Date: Fri, 3 Feb 2017 10:22:42 +0000
Message-ID: <1C5B54BD-1D6D-46F6-81A7-89ADF9A72792@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org> <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com>
In-Reply-To: <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: 630f737f-5cee-4cb5-684a-08d44c1e96e4
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1153; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1153; 7:ex6Vqx5hfuTo4bJ8ThiAyXdFiMe9grT0wZz6VUQWfSozWdMBWKgWjNvnBeBN4xRWCFqA7dbiE3vRfWXZGTWOSygBMwH8KAvOwWWBGXa4c+JQMjtwZme3k7DuyAIAJC4tDsNC+pYyMPof0xQbBqdZ25ZEL7+6ZhCQ8zq3jJ089MeGN970fMoSAr/a6J1d1wNWKpThHwfTk2jAny20k/gcPVaLkGkzffraNTwTKt0mQcrQ/F2csCPXN/ilCnojk6++nPCYoPxkHia+q5nlP54mInrP5lrJZNovTB/XwQjML5SjIUSLipFuvaqRJfpc9B+cOuZKW1a70xEi2w1xcZXW0MjSpqW1XgeyagHzW+LJiLih3Zf0oQEHjy44eggyCm9Mki8w4pFrhXsDIbIHJhGCim34EcJU473dXC4DnzPBoKdahncy27jwebEWU9hbSz/YF54bL4qq6ZmWW1vCuF5e2Cw0wECVMuAAvdj64DdlCe3U7wssFbkrdQYeYPIkY+o3imlgbfNCWLrhVVDNTu3jIA==
x-microsoft-antispam-prvs: <BN3PR0601MB1153208D9FD844B36C3D2DFCA74F0@BN3PR0601MB1153.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:BN3PR0601MB1153; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1153; 
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(377424004)(199003)(24454002)(189002)(83716003)(53936002)(6512007)(92566002)(3660700001)(6506006)(229853002)(99286003)(2351001)(4326007)(6246003)(3846002)(106116001)(105586002)(6306002)(106356001)(82746002)(2501003)(66066001)(122556002)(54906002)(53546003)(86362001)(102836003)(6116002)(230783001)(33656002)(57306001)(5660300001)(110136003)(99936001)(38730400001)(2900100001)(2906002)(93886004)(68736007)(8676002)(6916009)(2950100002)(5640700003)(81156014)(81166006)(1730700003)(6436002)(50986999)(76176999)(25786008)(4001150100001)(8936002)(305945005)(7736002)(77096006)(101416001)(6486002)(97736004)(36756003)(50226002)(3280700002)(189998001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1153; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_0F11CB5B-7BFC-405D-9EC7-C492084588F2"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 10:22:42.7551 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1153
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rvvdWZDCkVsKNHSBAVTVXDVVqXk>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 10:23:08 -0000

--Apple-Mail=_0F11CB5B-7BFC-405D-9EC7-C492084588F2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-3, at 11:21, Lars Eggert <lars@netapp.com> wrote:
> PDF here: https://www.caida.org/~mjl/pubs/measuring-pmtud.pdf
>=20
> "This paper measures PMTUD behaviour for
> 50,000 popular websites and finds the failure rate in IPv4
> is much less than previous studies. We measure the overall
> failure rate between 5% and 18%, depending on the MTU of
> the constraining link."
>=20
> 5-18% is pretty bad. I would expect that the widespread deployment of =
CGNs since this was published in 2010 to not have improved things.

And yeah, this is for v4. I'm not aware of v6 measurements in this =
space.

Lars

--Apple-Mail=_0F11CB5B-7BFC-405D-9EC7-C492084588F2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYlFnxAAoJEFS1wwm/cMFXz+cP/3ebOct1xO/ceSGPEaCdrMov
1H3IUW85gZuTuTL4k3vxQ77eP28lIqsoVYKuXfZBqaASnh0OW3D5MJVn86WAMg68
0oHs2wvn5A2Cmgjjvk2QllcFHcNHhEv0/k5ALTJS12OGGTFprKuCEDc7Eisr2T1q
GCDDssTKE3DXRvY4fSArFFP/ZzjeD/oqmMHpzQQyzTXHNbXnLEQ1K+DsZVpE5noE
D3UikxsKbgf6Ak9y4GFGFcWL5//Fxo+wg9vvdcfxLiC5s5LgvkvpmSYtY5Y7C5Ja
XurjuZhkJlrKNPQanuxY5WTopw1rTbggRxTcdDsLMI4b2eMgjeZDz8K1RZu4/FAn
1d/FCq/GWFDXJ3/oWW86TzFXqrFEevTecobdA961F6bhmoexObk7ezjmLWl7zxXG
FqAgIwRRN5P9DlD5pv9FCEWXgLFvHAF5x7Ne4NZKR1BOXD+gv6eE8mrqvvAMpCjJ
7a3Pt/8mEiAxcx5npWLMtZvwZ8X7SvNYIXMC+KVFBL1pS0Yw22oDzFfnLYQJmXEa
k40FIbE2vYuJRsZ0hI48nvrjEi254t7xtqC5U02XZm81vdx3/udw421x5HxgAQiq
1gwh8alTI3jzLfGJHyBPj3G0tRTxqfRLQtuybgU+kk/SQWoyuSw0Juc7Tx3wH9aY
jY085og/lP/QQ90/0iYu
=BElZ
-----END PGP SIGNATURE-----

--Apple-Mail=_0F11CB5B-7BFC-405D-9EC7-C492084588F2--


From nobody Fri Feb  3 02:28:40 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1215129BCB; Fri,  3 Feb 2017 02:28:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.119
X-Spam-Level: 
X-Spam-Status: No, score=-10.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uAOPZMXSXVkd; Fri,  3 Feb 2017 02:28:37 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 454A1129B4E; Fri,  3 Feb 2017 02:28:37 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,328,1477983600";  d="asc'?scan'208";a="174637276"
Received: from hioexcmbx08-prd.hq.netapp.com ([10.122.105.41]) by mx144-out.netapp.com with ESMTP; 03 Feb 2017 02:20:45 -0800
Received: from VMWEXCCAS11-PRD.hq.netapp.com (10.122.105.29) by hioexcmbx08-prd.hq.netapp.com (10.122.105.41) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 02:28:17 -0800
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS11-PRD.hq.netapp.com (10.122.105.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Fri, 3 Feb 2017 02:28:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=acII5BzO/Bhc0B5v3+8ZXL4+rLVdT+JLIj1VCcGeN5w=; b=a6xHUUXQUU6X+9nwra4vBx1W0pN74j9XQwkh/ZvI7In/VNOwOF2Un4SB2fYuTh///O92nkwsPpWtfhxpIa9nFYvmXfnSvXCR1GdVRJGypPPyFra/UFoi7YFr8xTZi5R63rd+TiAvDGMpkRIuGqLyGGctHVMXNLSkfTt+4Er0Z4g=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Fri, 3 Feb 2017 10:28:16 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.025; Fri, 3 Feb 2017 10:28:16 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAGB6ACAABzbgIAAAEOAgAABjoA=
Date: Fri, 3 Feb 2017 10:28:16 +0000
Message-ID: <4D3921DF-F2E3-4021-8F0F-B389B5DA0371@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org> <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com> <1C5B54BD-1D6D-46F6-81A7-89ADF9A72792@netapp.com>
In-Reply-To: <1C5B54BD-1D6D-46F6-81A7-89ADF9A72792@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: ece50729-4dd1-4eb0-de78-08d44c1f5daf
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1153; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1153; 7:97f67ZdM71+oYz9h9L+ZYWi/ayBYKTCR1JPKOxD3KOuEo8V2Kxkg7vdf4r5WHpYp3yQGmHR01IqAz4UMVhEnTNdUFg5sHD6pFAJzBIU1VmGiGhku61bgvE8YDXCaL1UTxhVNhhjux5aRcaMXat33rG9c2GADxpa8gbpj/zwK2AhZcOhdflPSqw3Zngz/GMUmdXJTi395TX88HsGYKcC9vmrRxssI9wjC20+nm23H7YQ3j/i1Ki2wXEj63y51cjQtswEknJiOd3rxIueMWHdA0xzFGOYa6U8JdqBEF6DbYAGxt2O6FGOv6cFmjKXje5MiRVotmdD+nNpKoEWmXbIL/GCUKzfwDdBHC/ONIbigMjGEk/8jcRW9Hsdcn4ZlQFsTPk8lsmTbfacUt9BtLz4ow2D+TyhVhAiAukORN/7fkBdyU4Wds7lvXHXp9QPUmrl2Ts2mTGjFQwLcqQTsmCdz23rKiU02blgedqqd+Rc/GfsZpVj0gfsPd0iQ7kjv5F1PbdmWKR+F3MIQNl4m3hjP5A==
x-microsoft-antispam-prvs: <BN3PR0601MB115381477AB571AABE77960CA74F0@BN3PR0601MB1153.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123562025)(20161123564025)(20161123560025)(6072148); SRVR:BN3PR0601MB1153; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1153; 
x-forefront-prvs: 02070414A1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(377424004)(199003)(24454002)(2950100002)(6916009)(8676002)(5640700003)(93886004)(68736007)(6436002)(50986999)(76176999)(25786008)(81156014)(81166006)(1730700003)(5660300001)(110136003)(99936001)(558084003)(230783001)(57306001)(33656002)(2906002)(38730400001)(2900100001)(97736004)(50226002)(36756003)(3280700002)(189998001)(4001150100001)(8936002)(77096006)(6486002)(101416001)(305945005)(7736002)(92566002)(93376004)(6506006)(229853002)(3660700001)(83716003)(6512007)(53936002)(122556002)(966004)(66066001)(102836003)(6116002)(86362001)(54906002)(53546003)(6246003)(3846002)(2351001)(99286003)(4326007)(2501003)(105586002)(6306002)(106116001)(106356001)(82746002)(104396002)(15302535012); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1153; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_4898182E-AFB2-4AB7-99E3-2021193162C3"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Feb 2017 10:28:16.2930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1153
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O76QOTrq3LcDGXSHjTeVqskXfH4>
Cc: 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 10:28:38 -0000

--Apple-Mail=_4898182E-AFB2-4AB7-99E3-2021193162C3
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-3, at 11:22, Eggert, Lars <lars@netapp.com> wrote:
> I'm not aware of v6 measurements in this space.

But Google is: http://tma.ifip.org/2016/papers/tma2016-final51.pdf

Lars

--Apple-Mail=_4898182E-AFB2-4AB7-99E3-2021193162C3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYlFs/AAoJEFS1wwm/cMFXoLUP/3Hzy8bx3z3pKTduuV0eLZCS
OnHQqFoh5B3JySgdwiep/B/2Q1kFi06WNjdpOo0BeAeVNUZHtWfi8Z2nkzISvuJq
Z8mrZtpNd16HJs2I90dmxwC4mvpKel4PoOC/Frz3EVeRppltU1yQZku0ymfl51Eg
AkevDGCakiz9/PHjn6YzD61BN62dHuWdsj40spw4x6VfNoi8CGCLfMrWbfzZKn0T
SwziwEUSY0YB404dALt0t8JZ2MkKE3do7ippsYrK94DBjfvxZLun7x3EQbTgJD+l
2vGFHTOIIM8Xv7nZxPph8i7Uc4s41GDhUrtely6BEQ8hA5IuNxBwRL0E3zJYFoTC
izqmV+SxWBPHmikVmjvvKQbu0KwaJ3i3nk4KzIsiKpFhf7z1DBOZzftySRuEgXy5
hst1YRc1tuKmaP2Uuw2PgR1ddpCGojLY8YhMxPqltmT7Pw3IniRIeQMyW5aYdOtO
+R1TKmSHQSVdl8jGCtec0iXfyegPuD1cO/3wGMqVku5GMfYUxFgrMSuKGK/GZN4d
7PwtwRFWXI42sncVA08dGN2PSB4QlSBjTSwAk5KItfWFFLYLMunyTSwe1yBNKHnB
igXcVUoxUffqCPt3CQleXiEjj8eEzmuMVvKMy7iteWpRRgQbCDVDwdMk8HJLKg1G
ZaXAc0p2hO1YIpF/igFl
=3T6c
-----END PGP SIGNATURE-----

--Apple-Mail=_4898182E-AFB2-4AB7-99E3-2021193162C3--


From nobody Fri Feb  3 02:52:28 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A321129BCD; Fri,  3 Feb 2017 02: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dvGlmsEynT6; Fri,  3 Feb 2017 02:52:20 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id D65B4127078; Fri,  3 Feb 2017 02:52:20 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 03 Feb 2017 10:52:20 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id BCFD6D788B; Fri,  3 Feb 2017 02:52:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=WLVTZzl/UkBVNerehzLjeLcHc7o=; b= DbbN4pv/PAvLVFY2CjteBhREqnGIV66LrVvyE5Rce4BguVsJmlj5mCq0sqsG9mh3 VB94YDmYpg2DS+sslf44KW6oWCRag9PIegYYWnh79nBqiUX35tNuJu3wr9PLokZs Bvve6mkmwHCM9yeqA5OXggWtbAHbzBsax3tLz6BaRT4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=RRykAQr/3+d/+k5Q8+jIpIn 75I5fGGuIsaYkBaAOE1j4EWNWnbGCw7WdUqXnWj62Z1NlaVrSlyWOnAW28DAk/a0 M3ONQCemQBdgzjXEPG6TGiejq9UhjkUtzyAUNFxvcLC89NVyJ1Iw6H5xGMeNBDhk B+qryWfiygFAdHgxvcqI=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3DE44D788A; Fri,  3 Feb 2017 02:52:19 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8CC538384171; Fri,  3 Feb 2017 11:52:15 +0100 (CET)
From: otroan@employees.org
Message-Id: <B6DD0238-3D98-400E-865D-EC32FD6F22EA@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_094FAC1C-73B5-4845-A68C-D88D0438C1AD"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Fri, 3 Feb 2017 11:52:14 +0100
In-Reply-To: <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <014D8A7C-449E-4849-9F49-990FF8B39DEF@employees.org> <88A7C2AD-8D33-4AFF-8AF4-A1B8718C47BD@netapp.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IRNNoHWTz0tyiD3UprCfv6hG2Io>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 10:52:22 -0000

--Apple-Mail=_094FAC1C-73B5-4845-A68C-D88D0438C1AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lars,

> Matthew Luckie and Ben Stasiewicz. 2010. Measuring path MTU discovery =
behaviour. In Proceedings of the 10th ACM SIGCOMM conference on Internet =
measurement (IMC '10). ACM, New York, NY, USA, 102-108. =
DOI=3Dhttp://dx.doi.org/10.1145/1879141.1879155
>=20
> PDF here: https://www.caida.org/~mjl/pubs/measuring-pmtud.pdf
>=20
> "This paper measures PMTUD behaviour for
> 50,000 popular websites and finds the failure rate in IPv4
> is much less than previous studies. We measure the overall
> failure rate between 5% and 18%, depending on the MTU of
> the constraining link."
>=20
> 5-18% is pretty bad. I would expect that the widespread deployment of =
CGNs since this was published in 2010 to not have improved things.

Emilie also did some work on this:
https://labs.ripe.net/Members/emileaben/ripe-atlas-packet-size-matters

If you took this argument to it's extreme logical conclusion, wouldn't =
you then just state that the only thing that works in the Internet is =
TCP port 443 and UDP port 53?
I'm not sure how much sense it makes to let broken middlebox behaviour =
steer standardisation.
1981 is proven to work well. If a network operator has chosen to pull =
the plug on ICMP then there really isn't much IETF can do about that.

PLMTUD is better, and it is even better combined with PMTUD. But PLMTUD =
isn't deployed everywhere, nor used for UDP etc..
I don't see how that has any bearing on making 1981 an Internet =
standard.

I would really encourage more work on the Path MTU discovery problem =
though. Possibly combined with removing fragmentation from the IP layer. =
But that's far outside of the context of taking 1981 to Internet =
standard.

Best regards,
Ole





--Apple-Mail=_094FAC1C-73B5-4845-A68C-D88D0438C1AD
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYlGDfAAoJEL7aWKiYQt925lQP/0CAD4kVfR4yefFZ54jQrtuY
0U7tN1Gyo3HW2V1djQHFhpynv8vEWEsu43lIlq+nPcmwl+6SzYcAMzg8G8mla90a
dz1avA8bsrNErRc8OATg6gm+pmzEuK7ahILQhAQWBSUqQ9WQtoTv5Mr0KQdh0sIE
QURTzqvfFiTCGrsBNQtKvgdeh8hFJ1BaTTp9dIC8/ccUmgHA+UuhlfmGQPyp2LMJ
laMw6YhKB1m5zSM1Hl81c7CxaCBbzoewmglDC9rumGG9L7jzyrlAUk0BnHaKKhE+
H4WFDbyiKVBLbBjXI3ylOwoDauLEMGc+ZqfNpwZnQedcLKdrrEwz5g0GhrMAj2Eb
f76EWbhXEAwErSu28j0rZgNftRj/NbD973avq2ma1huXNjO+5CvWkJnpwnGjIsIg
WSGFEfnVLIGq4XHs4GuwGeOITBLGL3nSQrgTvRVkB9CPcWy7H6e8C9PwJVte3UV6
XGwF+v7bajoXeUSH3DunTNRNd7ZsfIyLHpZ73orcWEJPM1aKyLXC8bRsDM24NmCT
50aT/WkNGc0Xgp7MfpGMQz72Zs9lB2zcwRS/V/q8z5wJE/L24ero0AoIZzURei9J
aERIFAmr4/NwMHp063o6Fj5YWk7q5olrKtOeuIWNVVWo4OQ2Jx3WMRmRW34bj4sF
o2mneZzG/WNJfoPNZsno
=U0hG
-----END PGP SIGNATURE-----

--Apple-Mail=_094FAC1C-73B5-4845-A68C-D88D0438C1AD--


From nobody Fri Feb  3 03:11:02 2017
Return-Path: <denis.ietf@free.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67A91129588; Fri,  3 Feb 2017 03:11:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.617
X-Spam-Level: 
X-Spam-Status: No, score=-2.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 WhbqpzHiJtss; Fri,  3 Feb 2017 03:10:57 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (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 E1B8C129404; Fri,  3 Feb 2017 03:10:56 -0800 (PST)
Received: from [192.168.0.13] (unknown [88.182.125.39]) by smtp6-g21.free.fr (Postfix) with ESMTP id A97A57803D3; Fri,  3 Feb 2017 12:10:54 +0100 (CET)
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-11.txt> (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
References: <148581788158.29828.4591033587037530374.idtracker@ietfa.amsl.com>
From: Denis <denis.ietf@free.fr>
Message-ID: <3a6b8cee-ff29-323e-9042-5df6e71a8d81@free.fr>
Date: Fri, 3 Feb 2017 12:10:57 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148581788158.29828.4591033587037530374.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------30BE242EF2C22EC06C360265"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h0t3btS-1U9gi2fqCYDERNrraQE>
Cc: oauth-chairs@ietf.org, oauth@ietf.org, draft-ietf-oauth-jwsreq@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 11:11:00 -0000

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

*Comments on I-D Action: draft-ietf-oauth-jwsreq-11.txt*

Two editorial comments first :

1. Guidance is a mass noun, not a count noun, plural doesn't make sense. 
Please change "guidances" into "guidance" twice in Section 11.

2. In Section 12 : Please remove my name (Denis Pinkas) from this section.

Other comments:

3. Section 1.1 (from boiler plate) states: The key words "MUST", "MUST 
NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are 
to be interpreted as described in RFC 2119 [RFC2119].

There is not a single other occurrence of the word SHALL within this 
document. In such case, I wonder how this document can be normative.
There are however many (useful) "non-normative examples. A non-normative 
example does not replace requirements.

Section 4 states:

*A Request Object (Section 2.1) is used to provide authorization*

*request parameters for an OAuth 2.0 authorization request.It*

*contains OAuth 2.0 [RFC6749] authorization request parameters*

*including extension parameters**.*

**

RFC 6749 contains 75 pages, but does not contain a single occurrence of 
the wording "authorization request parameter" nor of "extension parameter".
There should be either references to one or more specific sections of 
this document or, even better, a list of the mandatory/recommended/possible
authorization request parameters as well as a list of 
mandatory/recommended/possible extension parameters should be included 
in this document.


A clear distinction should be made between the parameters used to 
authenticate the request and the other ones.

4. The introduction states on page 4:

      (a) (integrity protection) The request can be signed so that the 
integrity of the request can be checked;

This should be changed into:

      (a) (integrity protection) The request can be authenticated either 
using a digital signature or using encryption under a secret key
           so that the integrity of the request can be checked;

5. The introduction states on page 4:

(d) (collection minimization) The request can be *signed* by a third 
party attesting that the authorization request is compliant tocertain 
policy.

The request is not /signed/ by a third party.


However, later on, there is the following explanation:

In addition, it allows requests to be prepared by a third party so that 
a client application cannot request
    more permissions than previously agreed.

If it is the intent, the sentence should be rephrased as:

(d) (collection minimization) The request can be *verified* by a third 
party attesting that the authorization request is compliant tocertain 
policy.

6. Section 10.1. the text states:

*When sending the authorization request object through "request"*

*parameter, it MUST either be signed using JWS [RFC7515] or encrypted*

*using JWE [RFC7516] with then considered appropriate algorithm.*

The wording"with then considered appropriate algorithm"is too vague. 
This should be changed into:

*When sending the authorization request object through "request"*

*parameter, it MUST either be signed using JWS [RFC7515] or encrypted*

*using JWE [RFC7516] using a symmetric key algorithm.*

7. Section 10.2 states:

This means that the request object is going to be prepared fresh each

time an authorization request is madeand caching cannot be used.

What are the implications ? Is it required/recommended to use a nonce ? 
The text should be made clearer.

8. Section 10.3 states:

10.3.Request Source Authentication

The source of the Authorization Request MUST always be verified.

There are several ways to do it in this specification.

(a)Verifying the JWS Signature of the Request Object.

It seems that the case of using a JWE encrypted using a secret key 
algorithm has been forgotten here. Please add it.

9. Section 10.3 states at its very end:

An extension specification

should be created as a preventive measure to address potential

vulnerabilities that have not yet been identified.

Writing a document for vulnerabilities that have not yet been identified 
is speculative. It would rather be better
either to remove this sentence or to explain what is meant by it.

10. Section 11.1 states:

*11.1.Collection limitation*

**

*When the Client is being granted access to a protected resource*

*containing personal data, the Client SHOULD limit the collection of*

*personal data to that which is within the bounds of applicable law*

*and strictly necessary for the specified purpose(s).***

The /presentation/ of personal data should be limited whether or not the 
protected resource contains personal data.

It is proposed to change this text into:

*When the Client requests an access to a protected resource, the Client*

*SHOULD limit the presentation of personal data to that which is within *

*the bounds of applicable law and strictly necessary for the specified *

*purpose(s).***

11. Section 11.2.1 states:

11.2.1.Request Disclosure

This specification allows extension parameters.

It would be useful to name either all of them or some of them. RFC 6749 
is not crystal clear about this.


Denis Pinkas (DP Security Consulting SAS)

==============================================================




> The IESG has received a request from the Web Authorization Protocol WG
> (oauth) to consider the following document:
> - 'The OAuth 2.0 Authorization Framework: JWT Secured Authorization
>     Request (JAR)'
>    <draft-ietf-oauth-jwsreq-11.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-02-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     The authorization request in OAuth 2.0 described in RFC 6749 utilizes
>     query parameter serialization, which means that Authorization Request
>     parameters are encoded in the URI of the request and sent through
>     user agents such as web browsers.  While it is easy to implement, it
>     means that (a) the communication through the user agents are not
>     integrity protected and thus the parameters can be tainted, and (b)
>     the source of the communication is not authenticated.  Because of
>     these weaknesses, several attacks to the protocol have now been put
>     forward.
>
>     This document introduces the ability to send request parameters in a
>     JSON Web Token (JWT) instead, which allows the request to be JWS
>     signed and/or JWE encrypted so that the integrity, source
>     authentication and confidentiality property of the Authorization
>     Request is attained.  The request can be sent by value or by
>     reference.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>      rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (Informational - IETF stream)
>      rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informational - IETF stream)
>      rfc6973: Privacy Considerations for Internet Protocols (Informational - IAB stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth



--------------30BE242EF2C22EC06C360265
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><b>Comments on I-D
            Action:
            draft-ietf-oauth-jwsreq-11.txt</b><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US">Two editorial
          comments first :<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="tab-stops:207.4pt 322.55pt"><span
          style="font-family:Arial;mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;mso-ansi-language:
          EN-US" lang="EN-US">1. </span><span
          style="font-family:Arial;mso-ansi-language:
          EN-US" lang="EN-US">Guidance is a mass noun, not a count noun,
          plural doesn't make sense.
          Please change "guidances" into "guidance" twice in Section
          11.<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US">2. In Section 12 :
          Please remove my name (Denis
          Pinkas) from this section. <o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US">Other comments:<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">3.
          Section 1.1 (from boiler
          plate) states: </span><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;font-family:Arial;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:
          EN-GB" lang="EN-GB">The key words "MUST", "MUST NOT",
          "REQUIRED", "SHALL", "SHALL NOT",
          "SHOULD", <br>
          "SHOULD NOT", "RECOMMENDED",
          "MAY", and "OPTIONAL" in this document are to be
          interpreted as described in RFC 2119 [RFC2119].<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB">There is not a
          single other occurrence of the
          word SHALL within this document. In such case, I wonder how
          this document can be
          normative. <br>
          There are however many (useful) "</span><span
          style="font-family:Arial;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:
          EN-GB" lang="EN-GB">non-normative examples. A non-normative
          example does not replace
          requirements.<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB">Section 4 states:<o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;font-family:Courier;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:
            EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>A
            Request Object (Section 2.1)
            is used to provide authorization<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;font-family:Courier;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:
            EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>request
            parameters for an
            OAuth 2.0 authorization request.<span style="mso-spacerun:
              yes">  </span><span
              style="background:aqua;mso-highlight:aqua">It<o:p></o:p></span></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;font-family:Courier;mso-fareast-font-family:&quot;MS
            Mincho&quot;;background:aqua;
            mso-highlight:aqua;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">  
            </span>contains OAuth 2.0 [RFC6749] authorization request
            parameters<o:p></o:p></span></b></p>
      <p class="MsoNormal"><b><span
            style="font-family:Courier;mso-fareast-font-family:
            &quot;MS
            Mincho&quot;;background:aqua;mso-highlight:aqua;mso-ansi-language:EN-GB"
            lang="EN-GB"><span style="mso-spacerun: yes">   </span>including
            extension parameters</span></b><b><span
            style="font-family:Courier;mso-fareast-font-family:&quot;MS
            Mincho&quot;;
            mso-ansi-language:EN-GB" lang="EN-GB">.<span
              style="mso-spacerun: yes">  </span><o:p></o:p></span></b></p>
      <p class="MsoNormal"><b><span
            style="font-family:Courier;mso-bidi-font-family:
            Arial;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></b></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB">RFC 6749 contains 75 pages, but does not
          contain a single occurrence of
          the wording "authorization request parameter" nor of
          "extension
          parameter". <br>
          There should be either references to one or more specific
          sections of this document or, even better, a list of the
          mandatory/recommended/possible <br>
          authorization request parameters as well as a
          list of mandatory/recommended/possible extension parameters
          should be included
          in this document.</span></p>
      <p class="MsoNormal"><font face="Arial"><br>
        </font></p>
      <p class="MsoNormal"><font face="Arial">A clear distinction should
          be made between the parameters used to authenticate the
          request and the other ones.</font><br>
        <span style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB">4. The
          introduction states on page 4:<o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:Arial"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-ansi-language:
          EN-US" lang="EN-US">     (a) (integrity protection) The
          request can be signed so that the
          integrity of the request can be checked<span class="delete"> </span>;
        </span><span
          style="font-family:Arial;mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;
          mso-ansi-language:EN-US" lang="EN-US"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-US"
          lang="EN-US">This should be changed into:<o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-ansi-language:
          EN-US" lang="EN-US">     (a) (integrity protection) The
          request can be authenticated either using
          a digital signature or using encryption under a secret key <br>
                    so that the
          integrity of the request can be checked<span class="delete"> </span>;
        </span><span
          style="font-family:Arial;mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;
          mso-ansi-language:EN-US" lang="EN-US"><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="margin-top:6.0pt"><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB">5. The
          introduction states on page 4:<o:p></o:p></span></p>
      <p class="MsoNormal"><span
          style="font-family:Arial;mso-fareast-font-family:
          &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="tab-stops:207.4pt 322.55pt"><span
          style="font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">(d)
          (collection minimization)
          The request can be <b>signed</b> by a third party attesting
          that the
          authorization request is compliant <span class="delete">to</span></span><span
          style="font-family:Arial;mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;
          mso-ansi-language:EN-US" lang="EN-US"> </span><span
          style="font-family:Arial;
          mso-ansi-language:EN-US" lang="EN-US">certain policy.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          11.0pt;font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">The
          request is not <i>signed</i>
          by a third party. <br>
        </span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          11.0pt;font-family:Arial;mso-ansi-language:EN-US" lang="EN-US"><br>
        </span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          11.0pt;font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">However,
          later on, there is the following explanation:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><span style="mso-spacerun: yes">   </span>In
          addition, it allows requests to be
          prepared by a third party so that a client application cannot
          request
          <br>
             more permissions than <span style="mso-spacerun: yes">pr</span>eviously
          agreed.<span style="mso-spacerun: yes">  </span><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Arial;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US">If it is the
          intent, the sentence should be rephrased as:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Arial;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoNormal" style="tab-stops:207.4pt 322.55pt"><span
          style="font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">(d)
          (collection minimization)
          The request can be <b>verified</b> by a third party attesting
          that the
          authorization request is compliant <span class="delete">to</span></span><span
          style="font-family:Arial;mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;
          mso-ansi-language:EN-US" lang="EN-US"> </span><span
          style="font-family:Arial;
          mso-ansi-language:EN-US" lang="EN-US">certain policy.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US">6. Section
          10.1. the text states:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>When sending the
            authorization request
            object through "request"<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>parameter, it MUST
            either be signed using
            JWS [RFC7515] or encrypted<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>using JWE [RFC7516]
            with then considered
            appropriate algorithm.<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Arial;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">The
          wording"</span><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"> with then
          considered appropriate algorithm"</span><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"> is too vague. This should
          be changed into:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>When sending the
            authorization request
            object through "request"<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>parameter, it MUST
            either be signed using
            JWS [RFC7515] or encrypted<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>using JWE [RFC7516] <span
              style="color:
              blue">using a symmetric key algorithm</span>.<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">7. Section
          10.2 states:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>This means that the
          request object is going
          to be <span style="background:aqua;mso-highlight:aqua">prepared
            fresh each<o:p></o:p></span></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;background:aqua;mso-highlight:aqua;
          mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>time an
          authorization request is made</span><span
          style="font-size:12.0pt;
          mso-bidi-font-size:10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:
          EN-GB" lang="EN-GB"> and caching cannot be used.<span
            style="mso-spacerun: yes">  </span><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">What are the
          implications ? Is it required/recommended to use a nonce ? The
          text should be
          made clearer. <o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">8. Section
          10.3 states:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">10.3.<span
            style="mso-spacerun: yes">  </span>Request Source
          Authentication<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>The source of the
          Authorization Request
          MUST always be verified.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>There are several ways
          to do it in this
          specification.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>(a)<span
            style="mso-spacerun: yes"> 
          </span>Verifying the JWS Signature of the Request Object.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US">It seems that
          the case of using a JWE encrypted using a secret key algorithm
          has been
          forgotten here. Please add it.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-US"
          lang="EN-US">9. Section
          10.3 states at its very end:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>An extension
          specification <o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>should be created as a
          preventive measure
          to address potential<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>vulnerabilities that
          have not yet been
          identified.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">Writing a
          document for vulnerabilities that have not yet been identified
          is speculative.
          It would rather be better <br>
          either to remove this sentence or to explain what is meant
          by it.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">10. Section 11.1
          states:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">11.1.<span
              style="mso-spacerun: yes">  </span>Collection limitation<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>When the Client is
            being granted access to
            a protected resource<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>containing personal
            data, the Client SHOULD
            limit the collection of<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>personal data to that
            which is within the
            bounds of applicable law<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>and strictly
            necessary for the specified
            purpose(s).</span></b><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
            lang="EN-GB"><o:p></o:p></span></b></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">The <i>presentation</i>
          of personal data should be limited whether or not the
          protected resource
          contains personal data.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">It is
          proposed to change this text into:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>When the Client
            requests an access to a
            protected resource, the Client<o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>SHOULD limit the
            presentation of personal
            data to that which is within <o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>the bounds of
            applicable law and strictly
            necessary for the specified <o:p></o:p></span></b></p>
      <p class="MsoPlainText"><b><span
            style="font-size:12.0pt;mso-bidi-font-size:
            10.0pt;mso-fareast-font-family:&quot;MS
            Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
              style="mso-spacerun: yes">   </span>purpose(s).</span></b><b><span
style="font-size:12.0pt;mso-bidi-font-size:11.0pt;font-family:Verdana;
            color:#222222;mso-ansi-language:EN-GB" lang="EN-GB"><o:p></o:p></span></b></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">11. Section
          11.2.1 states:<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">11.2.1.<span
            style="mso-spacerun: yes">  </span>Request Disclosure<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;MS
          Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>This specification
          allows extension
          parameters. </span><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">It would be
          useful to name either all of them or some of them. RFC 6749 is
          not crystal clear about this.<o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB"><br>
        </span></p>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
          lang="EN-GB">Denis Pinkas (DP Security Consulting SAS)</span></p>
      <span style="font-size:12.0pt;mso-bidi-font-size:
11.0pt;font-family:Verdana;color:#222222;mso-ansi-language:EN-GB"
        lang="EN-GB"> <!--[endif]--><o:p></o:p></span>
      <p class="MsoPlainText"><span
          style="font-size:12.0pt;mso-bidi-font-size:
          10.0pt;mso-fareast-font-family:&quot;Arial Unicode
          MS&quot;;mso-ansi-language:EN-US" lang="EN-US"><!--[if !supportEmptyParas]-->==============================================================
          <!--[endif]--><o:p></o:p></span></p>
      <meta name="ProgId" content="Word.Document">
      <meta name="Generator" content="Microsoft Word 9">
      <meta name="Originator" content="Microsoft Word 9">
      <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/02/clip_filelist.xml">
      <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
      <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:3 0 0 0 1 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-alt:"ＭＳ 明朝";
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1593833729 1073750107 16 0 415 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
span.delete
	{mso-style-name:delete;}
span.insert
	{mso-style-name:insert;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style><br>
      <br>
      <br>
    </div>
    <blockquote
cite="mid:148581788158.29828.4591033587037530374.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
The IESG has received a request from the Web Authorization Protocol WG
(oauth) to consider the following document:
- 'The OAuth 2.0 Authorization Framework: JWT Secured Authorization
   Request (JAR)'
  &lt;draft-ietf-oauth-jwsreq-11.txt&gt; as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-02-13. Exceptionally, comments may be
sent to <a class="moz-txt-link-abbreviated" href="mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The authorization request in OAuth 2.0 described in RFC 6749 utilizes
   query parameter serialization, which means that Authorization Request
   parameters are encoded in the URI of the request and sent through
   user agents such as web browsers.  While it is easy to implement, it
   means that (a) the communication through the user agents are not
   integrity protected and thus the parameters can be tainted, and (b)
   the source of the communication is not authenticated.  Because of
   these weaknesses, several attacks to the protocol have now been put
   forward.

   This document introduces the ability to send request parameters in a
   JSON Web Token (JWT) instead, which allows the request to be JWS
   signed and/or JWE encrypted so that the integrity, source
   authentication and confidentiality property of the Authorization
   Request is attained.  The request can be sent by value or by
   reference.




The file can be obtained via
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/">https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/</a>

IESG discussion can be tracked via
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/">https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/</a>


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


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (Informational - IETF stream)
    rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informational - IETF stream)
    rfc6973: Privacy Considerations for Internet Protocols (Informational - IAB stream)
Note that some of these references may already be listed in the acceptable Downref Registry.


_______________________________________________
OAuth mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OAuth@ietf.org">OAuth@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/oauth">https://www.ietf.org/mailman/listinfo/oauth</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------30BE242EF2C22EC06C360265--


From nobody Fri Feb  3 03:40:31 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3F0129C2F; Fri,  3 Feb 2017 03:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1-daCuf-xBA4; Fri,  3 Feb 2017 03:40:27 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0090.outbound.protection.outlook.com [104.47.0.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FA8E126D73; Fri,  3 Feb 2017 03:40:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rzc2f/8QkqvF8YajSWPMCzgX/ZO4PsJRjb/cRC+YmTs=; b=Oovq8aByA2P22VnIkXbS/zyWp0LsecQZeG7ltpZcwG+Evpra71NB7Mg8uNcrWbRb/+jqG0VyhkYuKpPIXbMKv1foE1yDBFIb0PZ2jeomkvfdsxcOLpEh6DYUTC74ONbbGX8yqDWswWBu5Q7Eq2qhJmT+/d6tCc+QTyHUyx+YD9o=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by HE1PR07MB1561.eurprd07.prod.outlook.com (10.169.123.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.6; Fri, 3 Feb 2017 11:40:23 +0000
Message-ID: <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 3 Feb 2017 11:22:58 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB5PR08CA0044.eurprd08.prod.outlook.com (10.166.166.140) To HE1PR07MB1561.eurprd07.prod.outlook.com (10.169.123.11)
X-MS-Office365-Filtering-Correlation-Id: fcfd6749-b7dd-4701-e4c2-08d44c29712d
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR07MB1561;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 3:Gsyu/cU7uiuV5Eb6jIyB6WeIsrLZDHcY9gcIVjv+r102NwEmfTqYyxClRjjUTmeJpJdDZq7Cs5ECfHEHf+NY75mgd6CvWfa+wceEqnGjQE34BRbsYplGWWXjFyAqCn++UKb7iOyXVzNasVEONy3ZHlx7I+09N6nDiG7WvNrBvrkd0kDYpURzgaK4j7MN+k7mgW3OSX0fIxesx95vp/uiOMmePBcz4Izn+C3qV8AGb3jzfJSgNzIofGXwB3PXliOm/mV2U487oif77lSJuSNI+g==; 25:oDlOqOyG6UzAHDpaKJpETT7NSt5LlbVSQuPs4KA1yCBM5YVDJdx/RxqfaNwfO6P5g2+U1U51Lpq1Wfm9d33RDoBWWZqa9QdZbtrQ3xp53WpxYc1gzFOpPKxxAw0/NeCbwghd0TDP1waxYqQHU0IpdljLuVLtKIsfPfqygP7OcQg4aF6uCzqRJ/b/nPszOB+FFLEMMzfV8lJXMdFdR+NyI0lpHlSy02n9R3STF7mXetHII18dTW3PPsk2P0DhITXVplVSQYdc9+GyqneDck9nSzHGiCRbbWGCqFq9oe2Gj/OSm5+i8rD0wYj5RAT5zEGCnKSHbzZnRxlvmkZMqTkZESQIyG5UOhQxaf/+gjTEmzE/2O2GzzoSZ1Av6Ng1qNwg4R7I9RWzACNuf9aDYvQ4u7Y494J9fMNWuHwbbctO2t/qrkxXP9thpNrbBXg32r31La2D1alx/cq1KQQ0n7KEyQ==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 31:RABX1EzEHYyTXvJomOXovb3XHZqcoFI6AanWUd2iiUMHu12Grcx5Cc7aKFsJmo7tRGuBrgsQMJQp+rlQOPCntw9JjwAdQoi5KKNi6fTtlllZycrrr/hb6jKCUSEMA7F5x69UsmTpuiu60cKcQA/0yORrAuHHV0q2qbexWWt1RKkMozpadDauXiGjXtVdwHhixRBly7yaeeeAoJwuqQxj1XRhApE1JFeiR6D8pF7+DIqL/Q1ztvsSkaBs3C4FWBk0Lqc741It4r32CM0Fan6Lcg==
X-Microsoft-Antispam-PRVS: <HE1PR07MB1561FB6F6AD08D8CC4B34F87C64F0@HE1PR07MB1561.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(100405760836317)(95692535739014);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6041248)(20161123562025)(20161123564025)(20161123558025)(20161123560025)(20161123555025)(6042181)(6072148); SRVR:HE1PR07MB1561; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1561; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 4:iGrYiexEGXCa6xVc7AhlOdPmCnOYOs2OFkoDbuYdcZ2sihkepU/PcxIguh2M7LxTjQrUj3pyORu4dwI6ygazlJxD5b50DQ8mg7NXRvGfvprMMsdSoLVzN3KpF2aGRA2sXn73VVWHW/WJsmWDvR+dVua3WUJv/Lc3kmOBv/gwhXf6WBwUAUPw8vZn9I/ZD0tn78rSWJugRoPEIY3rK9b5B5y7gQ30eycKRCbyakhRmbgBMfLAJSV72NeINrJ7c8siWYo4pA8gvfPZuofeiU4AZdjm2ftoDrlXnbjrayQi2qKwtg+qO14cJipw0XqLGhwOEamFBiBECuuuAFtZD/awvHs88AL1MzUmTahi+R+CPKh4/NV4b1ShlxQchaGIB1BWOlqakVBvEcSgpfisbN3M/l7EJ/ab44fja9+pxfFVOFnLxyv5nzWqyyl9wRVVZy26vBDS4B62bbPfPLnFH/u5o3TJFNGhOWmMvMQnSIdIZNtP1154gpH2S9z4xvgj5Ey5ZIUl1hr58l/wi+42hb/bR/xZ0hD7AywpSVRDbW30qfBU0cgORfNSnAPw2Xm0WV5PSIFTF+OlAM+XVNu9ULbJPj1sfi45rFHg5G5yJarXUHhTmXmEsx00naw0YkMFpbgZwxK9TMyHcsayLbJwkRTtnUIOlOvfHf6axklpZ73vjQYrFCs520vryaxDjoFtN5bmYCi08GorepVUiCmfo/goDQ==
X-Forefront-PRVS: 02070414A1
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(69234005)(377454003)(199003)(189002)(13464003)(24454002)(66066001)(44716002)(6116002)(3846002)(230700001)(101416001)(6666003)(5660300001)(47776003)(4720700003)(14496001)(105586002)(106356001)(33646002)(116806002)(61296003)(62236002)(42186005)(1556002)(76176999)(230783001)(81686999)(93886004)(81816999)(50986999)(44736005)(86362001)(229853002)(38730400001)(39060400001)(53936002)(68736007)(50466002)(92566002)(305945005)(1456003)(6486002)(7736002)(23756003)(25786008)(81156014)(81166006)(50226002)(6496005)(8676002)(2906002)(4326007)(84392002)(54906002)(9686003)(189998001)(5001770100001)(97736004)(6246003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1561; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; HE1PR07MB1561; 23:w4wwp+psaeLTymHi+2RhIERx4ETVO99WAzj+jOn?= =?iso-8859-1?Q?zfvvUVMKDMMGiqwcUr4bcMyp6HIrc6CVDlT1nLP3MwoTJ4DmhfYWl9iqI0?= =?iso-8859-1?Q?tUTCTYBxmTqr2SUzha5/0XcZyNxwZU2nUsU/SeMcAyW8FO4IllDZQfAWHQ?= =?iso-8859-1?Q?W0EfvfP++lqvGH0xuLpXWMVlyyTBJV0Y0NeX9za0ymzZpI71nLPlMUtdwo?= =?iso-8859-1?Q?vPpCWq8rMX3Nrsb1+/ALf6u0X31k+uuuU0GdHJ15OBYJn5aACjwA8+m2im?= =?iso-8859-1?Q?u4EdYQHq7AaXrTQEvQhNidxmKefaxY77sQZi89H0Brcu9V95mygh4XiV2f?= =?iso-8859-1?Q?C4jN1rjy4COlV0fNlsSZINO8fG8T+YGjN51zfhGSjY5jFGTeqB1QBRPBT5?= =?iso-8859-1?Q?eylY/TmY4sI55y3qzJjZJGF831YiJoToq4SPfeLx+CRHs3wlAR76Fb7T3b?= =?iso-8859-1?Q?EO9YA6oUTaUFFtzF07DWYS7M4UWeGG71WZKGR8m95giO9/lcG32dttJSu6?= =?iso-8859-1?Q?TwySCxybTESnQIxf+wqfOFoGariOtA7pKsKuFMT38R9NqWlvy8LNyaNmnZ?= =?iso-8859-1?Q?W6E+fy6RW4F8Kp7uNajL+dhLvEZ65PwkBI0mtW1J8sBDbN0LG1q8cmZKvO?= =?iso-8859-1?Q?vEpgGHZJZUQV95QiJYogOCNvAj8SzOdRAVLG2sm+NtbNQgFW3YMaKi/iKb?= =?iso-8859-1?Q?irZ63KKxEfNtov5WgNSES7nAuzFfgaBfZGo+ZpZQrArs5tQI9tx06ot+eh?= =?iso-8859-1?Q?0VThAsj/Bgn8j6kit/s5c93M38SGkcTLQMm5+AJ0KrIFbWD1FCC5QlV5Mh?= =?iso-8859-1?Q?SqGdEJ74CVHgUS56nKCr2kAmiwyCTcPUtkv0ahqudSXPLT+mnu8b6U6PzX?= =?iso-8859-1?Q?fS389MqOi0WWQR70JT9CXA4UKMhfHZNDapd175pYEmJOkXzhe4wfOy43k0?= =?iso-8859-1?Q?uFVARQ3x8bdYIp0wbhTcDCm0H761VzuPTdzmIGQn6X9memtriFxGy1tu18?= =?iso-8859-1?Q?1N8IQWK16mbNFZm14kH2+6bVUeEADOidex0Za2CC3iMs25sZWg9sP9Fvt/?= =?iso-8859-1?Q?tnOiRAv+InBiWXmLwZgAN8zZ62U/1VHHm/lPMwFEDvLC6k3TzyuR8N/1Up?= =?iso-8859-1?Q?emrT+WwEd7Mh2ia/glMwaL/1DSJzO+4YqQktuALy4B0imvSIUZO1U5yxi1?= =?iso-8859-1?Q?84b5eWmoefVEnldg97yUHhITnmqwXEhl8ZpzPpyTzenrH21nD/Qyy6K/O9?= =?iso-8859-1?Q?MQC/3gzgqa0ALBgJrbHkyMTekui2zJ6NSYFA0r1UsPaXWkfF3ttKgyNdNi?= =?iso-8859-1?Q?X8EdWapjYhSkbS8IQLj/PWX1XzteiQOd0tAhUiPNxqlvSRGdIWYbaZO7U5?= =?iso-8859-1?Q?vdcKMR2cXjIQCUVzQnPj5SBC4xhK1LRQN7HATjzkZGPVeW24oX0SQ3cj2U?= =?iso-8859-1?Q?G7oXgv0cHtXE5PT8/CYDztmVD33yA7rfGQVS88aX9bXu59dfMb057e2wdF?= =?iso-8859-1?Q?lcDe4KbPsGl+pFCrLwnizTFVvjUqaWbtakBgf9/s1G5o1SiUVQ/HwfiEmY?= =?iso-8859-1?Q?O4RZLHGUqgZ6EfoygbN9JK5yEw7Pvw0x5bAGXKoJzAkfL+S?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 6:/hA0p5raYqKUUtvvh4zKdxVPbWBYYgVSokfx5NJBhVj9bTiL0Bz73gNmGCNR3Tibf8gr97ye67xhpRBOmSp2+r6pDQfTM3HUEiOg0VrKNf/CBvWkAIVwvy5bK0KQcLN13wTOQeSyUmUxTVdBRphcew98e3vDNSvoHx3UThrHUwJgwMl8sThHy0XkFjwpm3jwVZOnQ7/LPaMMlHf0ldJBwHMybO2MHKjbWAs5CDYNgVaJ7yMfRHZJwJ30cToZMJZs0+SEgRGbZgvDNHKSCPgo/k2yrI7CDezklVD3auqeJbqcubPlyfRAPlY2JoevuZAUY9Yb/+14XKjKh+24CsEPV0VODilK6NBc0uS7YvxxYrX1pzqyDEqaGNEYrMRKxvv17gjIJNo1ZpZZF0MN9X+umw==; 5:dh0pNHAwWqwHJOnZueoNatNcCXPCc0XgnsTpd2nx0wUbpIlwJxEePhj3U7bZWGbTLfy3qLWnsRKyXzQjTTk0rEgzpY3aekTP2RIms/2WVPL+0+olchmcbkW7SvJIl78i3jaEBodkAGPRvoottwqWJQ==; 24:SYB6//1M0SoOx1qMVQ/b9cU6601eJQP6YnD82alffEJvR/8SoSxxJQIlv3+SCw+5SrVFSC4A3F/bEffAVg2GadF+UttZTLBDhoa2UEB+qjs=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1561; 7:ROgmMnouNh1Yo5zQUjGRmsQc5zY4aTwP5oSYoxPs2b3/Lg6zlAJZJ9Yuc5qaxkR/fqH3wbkg1oRVCcumMyx+YqpuQjb+5yZDE+mBfA1pq6f9i7O/lFktGt+vbUNJaYEtd2orJflCFrohH9vyrhjSf+8oLltydVrZDnmnCdPNpdmp+eG2MXz7xL/T66hAOhjD2+sPQq4g3XjLLOLjYSNmf+6i3nkSNfL8C7IqAICh8WDtWLCTTX6HcmMVpu/mR5h7059O6mLaJoLotq/NxJIK0k0p79zCElxWRY2X1QXMkgUQEVzGXKhzcUHObJnSuwG+V3KYs9Lhu/PLbKIsAopKVNwNqM9iwY7IkaMUhRZ6xvJ0fyajtFm6KNw5iUxqkfHhm6RpaMHbh69vZpipzBTEVTL3Y2Lp+RJ3Cl/W8BiXLwczh6/xoaS+ciiF21ooNT4bFocNxEiVchp4QqcklclPnl+P5SCXRD66zAUvPjHKE2I9K+VmO66K2vYC6XGW0NUd1p3c9/RVPrAk7QyXh15gaA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 03 Feb 2017 11:40:23.4979 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1561
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aJPchnaDqjCadr1zvasE5jVdrF0>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 11:40:30 -0000

----- Original Message -----
From: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
Sent: Friday, February 03, 2017 8:51 AM

> On Feb 3, 2017, at 1:37 AM, Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:
>
> In Section 4 ("IPv6 Extension Headers") the draft says:
>
>>   With one exception, extension headers are not processed by any node
>>   along a packet's delivery path, until the packet reaches the node
(or
>>   each of the set of nodes, in the case of multicast) identified in
the
>>   Destination Address field of the IPv6 header.
>
> (FYI, the exception is the hop-by-hop extension header.)
>
> I do not dispute that this sentence reached WG consensus. However, I
want
> to ask if it has IETF consensus. In my opinion, this sentence should
read
>
>   With one exception, extension headers are not processed, inserted,
>   deleted or modified by any node along a packet's delivery path,
until
>   the packet reaches the node (or each of the set of nodes, in the
case
>   of multicast) identified in the Destination Address field of the
IPv6
>   header.
>
> I believe this was always the intended meaning of the word "processed"
> from the earliest design phase of IPv6, but some people have read this
> text as allowing insertion, deletion or modification of headers. IMHO
> it needs to be clarified.

are we re-spinning the debate on a WG-agreed text ?

<tp>

Yes, and I am sure that that is exactly what is intended.

Some, many perhaps, may not like it but it is the consensus of the IETF
that is sought and that trumps anything that a WG may say or do.  Not
long ago, an I-D with good WG support, more so than this one, got thrown
out by the IETF Last Call and has sunk; the traces are there but it will
never make RFC.

I also expected the challenge, on another of this set, as to whether
IPv6 is ready for Standard status; the WG discussions, which I have
tracked, convince me that it is not.

Tom Petch

s.

> Regards
>   Brian Carpenter
>


From nobody Fri Feb  3 03:55:42 2017
Return-Path: <brford@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26160129405; Fri,  3 Feb 2017 03:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.719
X-Spam-Level: 
X-Spam-Status: No, score=-17.719 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DyiCO40lEWyJ; Fri,  3 Feb 2017 03:55:35 -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 191EF128B44; Fri,  3 Feb 2017 03:55:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6449; q=dns/txt; s=iport; t=1486122935; x=1487332535; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=FxY0slJXvRr62VqjL5jYhwRtKdNkeha8AOBRQp0bSm8=; b=JGy7fUopFgMrJH7mTZfhiY+Il8MkGsnExa+u5x5wuKMriiN7UXf/nuBf nc4PiPNQa3sxZDiB8netOqXW+m1zY3QPySmun9PciaS+E+zo+swi5C8Ms kpw8Ueh7+7H5bvBud/6RJRXKNTDXFR1L/ofV3oWlBJr57tIbttOjcDVYz k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtAQA9bpRY/4oNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQmNYJIKiBKHfoUrgg0fAQqFLkoCglo/GAECAQEBAQEBAWI?= =?us-ascii?q?ohGkBAQEDAQEBbAsFCwIBCBgnByEGAQoUEQIEDgUfiToDDQgOr1GHOQ2DcQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBARgFhkuCBQiCYoE8gRWBbINEgjEFmys4AYxwgQC?= =?us-ascii?q?EF5ECii2IXAEfOIFLFTsRAYQ/gXF1iSABAQE?=
X-IronPort-AV: E=Sophos;i="5.33,328,1477958400";  d="scan'208,217";a="380218660"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Feb 2017 11:55:33 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v13BtX9b022523 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 3 Feb 2017 11:55:33 GMT
Received: from xch-rcd-009.cisco.com (173.37.102.19) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 3 Feb 2017 05:55:32 -0600
Received: from xch-rcd-009.cisco.com ([173.37.102.19]) by XCH-RCD-009.cisco.com ([173.37.102.19]) with mapi id 15.00.1210.000; Fri, 3 Feb 2017 05:55:32 -0600
From: "Brian Ford (brford)" <brford@cisco.com>
To: Naeem Khademi <naeem.khademi@gmail.com>
Subject: Re: [Recentattendees] Background on Singapore go/no go for IETF 100
Thread-Topic: [Recentattendees] Background on Singapore go/no go for IETF 100
Thread-Index: AQHSemMdtz+BYbM/YUyZmAb3LjspL6FRbwdAgADps4mABL0G54AAHlEp
Date: Fri, 3 Feb 2017 11:55:32 +0000
Message-ID: <A149FF2A-B866-4839-9422-BDE77905EC7D@cisco.com>
References: <20160525220818.18333.71186.idtracker@ietfa.amsl.com> <700D9CB7-4EFD-459B-AA12-133A6BB04E90@senki.org> <1C8639E6-1058-4D04-84ED-0C354E6567D1@cisco.com> <9CBABA69-1814-4676-9C69-E129F04AD24C@cisco.com> <5DFDEA43-8156-491D-A300-2BCED1AED1A4@gmail.com> <5747909C.20403@si6networks.com> <955df2106aa2e12cefbd450be022e779.squirrel@www.trepanning.net> <D36D49EE.35116%jefft0@remap.ucla.edu> <CE39F90A45FF0C49A1EA229FC9899B05266663BF@USCLES544.agna.amgreetings.com> <CA+ruDECdMAC2PQqibqQijc-nLHUxOGw0h-ZYyh8FnZZaeZ8sTA@mail.gmail.com> <CA+ruDEBHyzk5cg5Vmq-anKJTxLkZpHrb9APwkfbDGn6FeFzR_w@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B052BD4B85D@USCLES544.agna.amgreetings.com> <A0BBD037-851F-4F47-A7F2-44EFC73166AD@consulintel.es> <CAEjQQ5Wbxi0_fEVf3uh1_K=o02KK11jRgGhdpeiBhAojhtt76g@mail.gmail.com> <7B01DE73-2908-4602-9D76-9056215033DA@gmail.com>, <CAEjQQ5Wn7ig+Cgh68SXdK5AYO478BpN-doNx5m-5K_ocuxWz9g@mail.gmail.com>
In-Reply-To: <CAEjQQ5Wn7ig+Cgh68SXdK5AYO478BpN-doNx5m-5K_ocuxWz9g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_A149FF2AB86648399422BDE77905EC7Dciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CbMaf5ydZEk1LJQyaaESphbJ0-A>
Cc: "recentattendees@ietf.org" <recentattendees@ietf.org>, Randal Atkinson <rja.lists@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 11:55:37 -0000

--_000_A149FF2AB86648399422BDE77905EC7Dciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Is it really necessary to punish the entire list with this garbage?

Sent from my iPhone

On Feb 3, 2017, at 5:07 AM, Naeem Khademi <naeem.khademi@gmail.com<mailto:n=
aeem.khademi@gmail.com>> wrote:



On Thu, Feb 2, 2017 at 4:39 PM, Randal Atkinson <rja.lists@gmail.com<mailto=
:rja.lists@gmail.com>> wrote:

> On 31Jan2017, at 04:44, Naeem Khademi <naeem.khademi@gmail.com<mailto:nae=
em.khademi@gmail.com>> wrote:
>
> The next IETF in the US after Chicago, would be in July 2018 in SF. I don=
't think it's even possible
> to buy a flight ticket for that time as of now (most airlines wouldn't do=
 such pre-sale). So, it's pretty
> much possible to relocate that meeting elsewhere with causing no loss to =
anyone's already-made plans.

The claim above that "most airlines won't sell 6 months in advance" is fals=
e.

Since you're quoting me (calling it "claim above"), I have a hard time find=
ing the exact text you're referring to in my writing ;-). I stated that mos=
t airlines wouldn't do such a pre-sale for July 2018 (IETF @SF) which happe=
ns 16 months in the future, so I stay correct.

Regards,
Naeem


Most airlines, including all or nearly all major full-service international=
 airlines, start selling tickets
at least 12 months before the departure date for the 1st flight on an itine=
rary.

To my knowledge, there are some people who already have purchased tickets t=
o go to IETF in SFO.
This really ought not be surprising as the lowest-cost fares often sell-out=
 earliest.  A number of
IETF people don't work for big companies and are traveling on their own mon=
ey.   Those people
would suffer greatly from a change in location less than 12 months out.

I am aware that some have suggested the IETF do more remote meetings.  I th=
ink that is worth
exploring.

I certainly would support IETF making all future meetings more accessible r=
emotely  - and I think
that is a goal the IETF has been making progress on for some years now, usi=
ng Jabber, VTC,
and so forth.  Expanding the remote access capabilities and coverage for al=
l future meetings
(to the extent that is practical at a given point in time) only makes sense=
.

Yours,

Ran


_______________________________________________
Recentattendees mailing list
Recentattendees@ietf.org<mailto:Recentattendees@ietf.org>
https://www.ietf.org/mailman/listinfo/recentattendees

--_000_A149FF2AB86648399422BDE77905EC7Dciscocom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div>Is it really necessary to punish the entire list with this garbage?<br=
>
<br>
Sent from my iPhone</div>
<div><br>
On Feb 3, 2017, at 5:07 AM, Naeem Khademi &lt;<a href=3D"mailto:naeem.khade=
mi@gmail.com">naeem.khademi@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<blockquote type=3D"cite">
<div>
<div dir=3D"ltr"><br>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Thu, Feb 2, 2017 at 4:39 PM, Randal Atkinson =
<span dir=3D"ltr">
&lt;<a href=3D"mailto:rja.lists@gmail.com" target=3D"_blank">rja.lists@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<span class=3D""><br>
&gt; On 31Jan2017, at 04:44, Naeem Khademi &lt;<a href=3D"mailto:naeem.khad=
emi@gmail.com">naeem.khademi@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The next IETF in the US after Chicago, would be in July 2018 in SF. I =
don't think it's even possible<br>
&gt; to buy a flight ticket for that time as of now (most airlines wouldn't=
 do such pre-sale). So, it's pretty<br>
&gt; much possible to relocate that meeting elsewhere with causing no loss =
to anyone's already-made plans.<br>
<br>
</span>The claim above that &quot;most airlines won&#8217;t sell 6 months i=
n advance&quot; is false.<br>
</blockquote>
<div><br>
</div>
<div>Since you're quoting me (calling it &quot;claim above&quot;), I have a=
 hard time finding the exact text you're referring to in my writing ;-). I =
stated that most airlines wouldn't do such a pre-sale for July 2018 (IETF @=
SF) which happens 16 months in the future,
 so I stay correct.&nbsp;</div>
<div><br>
</div>
<div>Regards,</div>
<div>Naeem</div>
<div><br>
</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Most airlines, including all or nearly all major full-service international=
 airlines, start selling tickets<br>
at least 12 months before the departure date for the 1st flight on an itine=
rary.<br>
<br>
To my knowledge, there are some people who already have purchased tickets t=
o go to IETF in SFO.<br>
This really ought not be surprising as the lowest-cost fares often sell-out=
 earliest.&nbsp; A number of<br>
IETF people don&#8217;t work for big companies and are traveling on their o=
wn money.&nbsp; &nbsp;Those people<br>
would suffer greatly from a change in location less than 12 months out.<br>
<br>
I am aware that some have suggested the IETF do more remote meetings.&nbsp;=
 I think that is worth<br>
exploring.<br>
<br>
I certainly would support IETF making all future meetings more accessible r=
emotely&nbsp; &#8212; and I think<br>
that is a goal the IETF has been making progress on for some years now, usi=
ng Jabber, VTC,<br>
and so forth.&nbsp; Expanding the remote access capabilities and coverage f=
or all future meetings<br>
(to the extent that is practical at a given point in time) only makes sense=
.<br>
<br>
Yours,<br>
<br>
Ran<br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>Recentattendees mailing list</span><br>
<span><a href=3D"mailto:Recentattendees@ietf.org">Recentattendees@ietf.org<=
/a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/recentattendees">htt=
ps://www.ietf.org/mailman/listinfo/recentattendees</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_A149FF2AB86648399422BDE77905EC7Dciscocom_--


From nobody Fri Feb  3 08:07:44 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37C2C12965B for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 08:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.098
X-Spam-Level: 
X-Spam-Status: No, score=-5.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-3.199, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ew4JubU6tuW4 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 08:07:41 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91AAF12965F for <ietf@ietf.org>; Fri,  3 Feb 2017 08:07:41 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cZgOi-000Auj-Au for ietf@ietf.org; Fri, 03 Feb 2017 11:07:40 -0500
Date: Fri, 03 Feb 2017 11:07:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <D45CE6A5317D4B373CD90742@PSB>
In-Reply-To: <20170201210155.GI28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BdFiEq_7hg9TIx0rZ-QbKLD3i-I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 16:07:43 -0000

Victor, Wei Chuang, and IESG,

The more this discussion goes on, the more I become convinced
that this document should make an explicit reference to the IDNA
2008 and SMTPUTF8 documents, say that strings in certificates
MUST conform to whatever is allowed there and then, other than
making a statement about preference for U-labels over A-labels
(or vice versa), say as little as possible.  The problem is that
use of forms that might have coded meanings without knowing what
those meanings are is an opportunity for mischief, something
that should be of special concern for a piece of work that is
security-specific.   

I note that "prohibit everything that has a prefix consisting of
two ASCII letters followed by '--' unless the letter sequence is
specifically allowed" has been discussed at length and then
agreed on in at least three WGs specialized about the
identifiers, not just their embeddings (original IDN, IDNbis,
and PRECIS).  Even if there were a growing consensus that a
different rule would be more appropriate (and, AFAICT, there
definitely is not), it would be a bad idea for LAMPS or other
certificate-related work to get ahead of that consensus and
specify something inconsistent with the identifier standards
themselves.

Phill's proposal, independent of its merits, is almost
irrelevant to the question.  From the standpoint of the present
work, it is one of many proposals to do interesting things with
the DNS by using ACE-style (or trick-prefix) labels.  If the
community concludes that it is a good idea and has a plausible
chance of global deployment, the DNS/IDNA and SMTP (or SMTPUTF8)
specs will need to be modified to allow the prefix.  The LAMPS
"eai" spec should be written so that, if those specifications
are modified, whatever they allow should be allowed in certs,
but should, again, not be allowed to get ahead.   If that means
we are now in need of an IANA registry of such prefixes (with
exactly one initial entry plus maybe one long-deprecated one),
that ought to be easy to do.

As to "put all the alternate forms in the cert", we've been
there too and it hasn't ended happily.  Fully-qualified DNS
names are part of a hierarchy.   Transcoding between A-labels
and U-labels is an algorithmic matter, not a hierarchy of
choices but, if there are even two choices for the form of a
label at each of several different levels of the hierarchy, one
rapidly gets to a combinatorial explosion.  I trust everyone
here can do the arithmetic.  If listing all of the possible
variations on an FQDN in the certificate is the solution, then
the WG -- on behalf of those who issue, certify, validate, and
check certificates -- needs to be prepared for certs with
dozens, sometimes hundreds, of names in them, not just the
examples that have been floated with perhaps two or three.  

Remembering that, if, as Porky Pig, I can get a cert issued to
me with Mickey Mouse as an alternate name that is treated as a
synonym for all purposes, much of the value of certification is
lost and, IMO, we are all in big trouble.   If the WG wants to
encourage alternate name behavior, I think it is imperative that:

	(i) The document contain explicit instructions to
	certificate issuers and CAs about what should be checked
	and to client systems about what should be
	believed/trusted and under what circumstances.
	
	(ii) Certificate provisions to specify certification
	levels and exactly what is being certified need to be
	reexamined and probably expanded to identify trust
	levels and accountability around alternate names.
	
	(iii) The "Security Considerations" section of the I-D
	should be expanded to explicitly discuss these cases and
	the risks.

The document should not be approved until that work is complete
and reaches consensus.

   best,
      john


--On Wednesday, February 1, 2017 21:01 +0000 Viktor Dukhovni
<ietf-dane@dukhovni.org> wrote:

> On Tue, Jan 24, 2017 at 07:31:09PM -0000, John Levine wrote:
> 
>> > My impression is that there is little problem with the
>> > intended underlying spec, but the document text needs some
>> > tuning.
>> 
>> Agreed.  The subsequent section on comparing names would
>> likely benefit from clearer instructions, e.g.
>> 
>> a) if the domain contains A-labels, turn them into U-labels
>> b) if the domain still contains R-LDH labels, stop, not a
>> valid name. c) if the domain contains NR-LDH labels, make
>> them all the same case d) do a straight byte comparison of
>> the addresses
> 
> I think that restricting R-LDH labels that are not A-labels is
> too strict, see for example Phil Hallam-Baker's proposed
> encapsulation of email addresses with "the mesh" (attached).
> 
>   TL;DR:
> alice@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE
> 
> The "mm" R-LDH namespace (if/when implemented) or some other
> future namespace should probably not be excluded at this time.
> 
> If the intent is to canonicalize A-labels to U-labels, then
> perhaps only "xn--" labels should be proscribed, if any.
> 
> On the other hand, I see there is some support for allowing
> certificates to contain whatever form is actually used in email
> headers, and perhaps more than just one such form.  If so,
> there is no need to proscribe any names at all.  The client
> performs no conversions, and the certificate would need to be
> inclusive of any addresses that are in actual use.





From nobody Fri Feb  3 08:49:34 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86697129691 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 08:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 XkAPdlFDI-nK for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 08:49:31 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C22C129669 for <ietf@ietf.org>; Fri,  3 Feb 2017 08:49:31 -0800 (PST)
Received: from [IPv6:2604:2000:1382:81a2:a15d:7573:e5c2:bb3f] (unknown [IPv6:2604:2000:1382:81a2:a15d:7573:e5c2:bb3f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 556BB284E4B for <ietf@ietf.org>; Fri,  3 Feb 2017 16:49:29 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <D45CE6A5317D4B373CD90742@PSB>
Date: Fri, 3 Feb 2017 11:49:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6248F87-C061-44D7-91A1-C99C06B0571E@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VRaFX6DM-ppS8Lpfs1pOK43fmPk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 16:49:32 -0000

> On Feb 3, 2017, at 11:07 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> As to "put all the alternate forms in the cert", we've been
> there too and it hasn't ended happily.

I must say that I am quite sympathetic to many of the points
you raise.  As is often the case in discussions of the finer
points of an issue, we're not as far apart as it may seem.
That said, I do want to comment on the objection to having
to deal with "all the alternative forms".

My suggestion is not to publish a combinatorial explosion.
Rather, my suggestion is to publish precisely the verbatim
forms that users will emit as their purported email addresses
in message origin headers.  If they use an address form that
is not published in the certificate (without any coversions)
then the certificate will not match the purported author.

Thus I would expect that for a user with an all-ASCII localpart
name, there might in be a need to use one of two addresses.
For me that might be (neither address is currently provisioned):

	ietf-dane@=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.org
	ietf-dane@xn--b1adqpd3ao5c.org

I might then use the former in email with peers whose systems
support "EAI" and the latter with peers whose systems do not.
Had I, hypotheticall, registered a related domain under a
Cyrillic TLD, I would still use one of two address forms

	ietf-dane@xn--b1adqpd3ao5c.xn--p1ai
	ietf-dane@=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.=D1=80=D1=
=84

and these (or whatever the user actually needs to be known
as) would be the only ones in the certificate.  This is not
very different from a certificate with two addresses in
domains that are simply distinct, rather than just being
variant encodings of the same thing:

	ietf-dane@dukhovni.org
	ietf-dane@=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.org
	...

Such a certificate (like many a PGP public key) carries
multiple personae.  Putting multiple extant address forms
in a certificate can free the verifier from performing any
encoding conversions.  Perhaps that's worthwhile.

A certificate that lists multiple address forms, whether
semantically distinct, or just variant encodings, may be
more likely to work with verifiers that predate the
specification and do no conversions.  Forbidding variant
forms can close off interoperability options.

--=20
	Viktor.


From nobody Fri Feb  3 09:21:00 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47F32129407; Fri,  3 Feb 2017 09:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.4
X-Spam-Level: 
X-Spam-Status: No, score=-5.4 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_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XDfPKmSLxTNb; Fri,  3 Feb 2017 09:20:57 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BA38129678; Fri,  3 Feb 2017 09:20:53 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 4AA2462708; Fri,  3 Feb 2017 12:20:50 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=YSV qVQlzrT/OgZPaK+xeyUHt3Kg=; b=XS8owOJ7puuqFtEZKi4tX6iN1PSsz9tOcca LOgJbLyR3+Zbp3tJdHQ5i8o6NNnIQgkAeqafF2rA5azsBZpIG5gjH0GpSnno2QBb z8CO9NhSsp+D98G1S5HVUJMi2XplErP9q6p00pssrGhQZWl0uSrBJ1l/4QOQryeb +o+Z1+xU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= KH0ORbrgz5hA5ndy3/kkQICa9ifFDVLOh0fuQQNt2MZ9UIUKLLRJWElw64pnfgpF J46N5/5Yl05FwgWJMDcLs7lb3PVz3TLftL3FPcu1zi5FUbm5R91k/ZqGgAOYn/nx YmPN+uKn5GTcAN80/UjRewggXhaySw86IuilBCe3/vE=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 4242062707; Fri,  3 Feb 2017 12:20:50 -0500 (EST)
Received: from mail-qt0-f170.google.com (unknown [209.85.216.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id C10DD62706; Fri,  3 Feb 2017 12:20:49 -0500 (EST)
Received: by mail-qt0-f170.google.com with SMTP id k15so44917991qtg.3; Fri, 03 Feb 2017 09:20:49 -0800 (PST)
X-Gm-Message-State: AIkVDXIRn/XPNyrPvdBikw6fP1NilN8CU9wujQv7ZyN3n+sXFQD5YtCIy4Bz/mypPrb/ptPs6ReA2mWDVpF5Nw==
X-Received: by 10.200.39.35 with SMTP id g32mr15525354qtg.265.1486142448990; Fri, 03 Feb 2017 09:20:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Fri, 3 Feb 2017 09:20:28 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Fri, 3 Feb 2017 09:20:28 -0800
X-Gmail-Original-Message-ID: <CACL_3VGL5ecO=-7gqiEKxHtqoTFXpZd6+hQd7FtT9Qc2F11Paw@mail.gmail.com>
Message-ID: <CACL_3VGL5ecO=-7gqiEKxHtqoTFXpZd6+hQd7FtT9Qc2F11Paw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: 1B91960A-EA35-11E6-A4A5-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sceulrn7WcryuhF_8YPQOnAMJKk>
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man WG <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 17:20:59 -0000

On Fri, Feb 3, 2017, at 1:37 AM, Brian E Carpenter wrote:
> In Section 4 ("IPv6 Extension Headers") the draft says:
>
>>    With one exception, extension headers are not processed by any node
>>    along a packet's delivery path, until the packet reaches the node (or
>>    each of the set of nodes, in the case of multicast) identified in the
>>    Destination Address field of the IPv6 header.
>
> (FYI, the exception is the hop-by-hop extension header.)
>
> I do not dispute that this sentence reached WG consensus. However, I want
> to ask if it has IETF consensus. In my opinion, this sentence should read
>
>    With one exception, extension headers are not processed, inserted,
>    deleted or modified by any node along a packet's delivery path, until
>    the packet reaches the node (or each of the set of nodes, in the case
>    of multicast) identified in the Destination Address field of the IPv6
>    header.
>
> I believe this was always the intended meaning of the word "processed"
> from the earliest design phase of IPv6, but some people have read this
> text as allowing insertion, deletion or modification of headers. IMHO
> it needs to be clarified.

I, too, am of the opinion that the WG consensus on this point was wrong.

>From the outset it has been fundamental to the IPv6 architecture that
an ICMPv6 message triggered by a particular packet will be sent back to
the source of that packet. If an intermediate node inserts an extension
header or makes an alteration in one that triggers an ICMPv6 error
message -- for example, Packet Too Big or Parameter Problem -- that
error message will be sent back to the source of the packet, not to
the node responsible for inserting the offending header or alteration.
That is fundamentally broken.

On that basis, I don't think that there is any doubt that Brian's
construction of the intent of RFC 2460 is the correct one, and
the language of RFC 2460bis should unambiguously reflect that.

Mike Heard


From nobody Fri Feb  3 09:21:22 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C0F129693 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 09:21: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 autolearn_force=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 NrmV7sZLmeDr for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 09:21:10 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E119D129683 for <ietf@ietf.org>; Fri,  3 Feb 2017 09:21:09 -0800 (PST)
Received: (qmail 3605 invoked from network); 3 Feb 2017 17:21:09 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 3 Feb 2017 17:21:09 -0000
Date: 3 Feb 2017 17:20:47 -0000
Message-ID: <20170203172047.13653.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
In-Reply-To: <D45CE6A5317D4B373CD90742@PSB>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KTzQunjIeFLldyMkzTCq6EKmDNY>
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 17:21:21 -0000

In article <D45CE6A5317D4B373CD90742@PSB> you write:
>Victor, Wei Chuang, and IESG,
>
>The more this discussion goes on, the more I become convinced
>that this document should make an explicit reference to the IDNA
>2008 and SMTPUTF8 documents, say that strings in certificates
>MUST conform to whatever is allowed there and then, other than
>making a statement about preference for U-labels over A-labels
>(or vice versa), say as little as possible. ...

I'd like to endorse John's point -- if these things look like e-mail
addresses, they should *be* e-mail addresses, with the same rules.
Particularly in a security context, we're not doing people any favors
by allowing strings that look almost like addresses but aren't, or
alternate forms where users have to decide whether they're equivalent.

If people want to do experiments with other kinds of names, that
is fine, but they don't go into a standards track document.  If
they turn out to be useful, we can add them to the spec later.

R's,
John



From nobody Fri Feb  3 10:22:23 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB2661294CD; Fri,  3 Feb 2017 10:22: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PeJRqRuxAN-7; Fri,  3 Feb 2017 10:22:21 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id A3A5612967F; Fri,  3 Feb 2017 10:22:20 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 03 Feb 2017 18:22:20 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id F3C8CD788A; Fri,  3 Feb 2017 10:22:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; s=selector1; bh=KBp/7CGwcB6V6QWFHcswc lwGyR8=; b=HiZQtqdwM1k9yxCgfO+dgTVUxuXRzDXX2ItpRL7un16ddbIvdqim6 KAU1urjOGmJjQwsOypBkm/HhO9VC3Sbh/7kuKyvAp0UUVFhlaqbPPduNv2Vtzo5h DkViG/JSvt3kvvwtM+ipiBxzdf/jcpoUlHM0boNfligPykCPhU16+E=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; q=dns; s=selector1; b=ebKeS/yQcqktyc2 KOpH1EcxvAtRM23lUfsB/KqsV7VWnMXaArgqXimuqLT+sMju+SSnXxqZPb8+D7cF qc+EqvtyRay9QpwStfy9pG7MlW8aGtp1RxEPX7JvX8T174JgWs2NupQqC5670ing wde955pDKcy6Gk996Yw2sjUuQBHY=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id BF8E5D788D; Fri,  3 Feb 2017 10:22:19 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B9CC383AD28A; Fri,  3 Feb 2017 19:22:17 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_54C0312F-8A01-4C9A-973B-525713281E0E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
From: otroan@employees.org
X-Priority: 3
In-Reply-To: <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net>
Date: Fri, 3 Feb 2017 19:22:16 +0100
Message-Id: <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net>
To: "tom p." <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h44m6cnUYRM4ArCEmoZAdH_GxcQ>
Cc: 6man-chairs@ietf.org, draft-ietf-6man-rfc2460bis@tools.ietf.org, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 18:22:23 -0000

--Apple-Mail=_54C0312F-8A01-4C9A-973B-525713281E0E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> are we re-spinning the debate on a WG-agreed text ?
>=20
> <tp>
>=20
> Yes, and I am sure that that is exactly what is intended.

Then let's encourage people outside of 6man, with other points of view, =
and other arguments to come forward.

A re-run of the discussions already had in 6man with the same arguments =
and the same participants doesn't seem useful.

For a brief (sic) overview take a look at 672 messages already on the =
topic:
https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&f_list=3Dip=
v6

O.

--Apple-Mail=_54C0312F-8A01-4C9A-973B-525713281E0E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYlMpZAAoJEL7aWKiYQt92sNAQAKLC7039tuoOhoRLTUV+zUtT
fZlr0ndARq/8FbvAHGRayqs6zHaN78yI/C1Vrsy+x4SfyrIBpnUb2E8xn8YHlUHV
G2yQfinenC1wgSA+0NUufSfxNzWPJgSGtmVh2fbucNlY7BScvOAoglkEuVPpOiCm
urkmdqyVhKTytEuzWqM1sdiKqsCXO5C9I6j/K9eNlo6HMHjR/BqgaDQEV5Qhs4cf
s6yLNf3wgEwJmkE4l2j17xlMhjNmfYyos3dFXihYpiEf5OtQOoynM3yNYTCqiopT
/Wu7BGb62+mBPegY1RR2M6pap7fEc5kArOpnyg4npSbOSLtG4aU5YYynvj1AtVzd
YLsiVTjMcjk81hqRwYPmx0Z44jiDa8MTDOU8iX6n/nquKTqKKFXay+X8nEn5Gydj
b0FDt80MfP/prIrE4Pl0bz+m6+qBqYYFBmPHa3wmQMCVMJpA5MCO3/WU4IhyXqBp
KGmgFHo8Ev5r346gBgzHALUEbvKbXRM4yjO6bljeuRw01m+jt/FGlNVwAfX4JGG6
3aY7lXmOJXnUgdf2rvf4SnuaXQjjx18C6CIaffaB8FXscfpAz5AeMmx7ggrsrT9j
OL+LhqBte+5I9+1CqoDPKDdsPlSVqb7jmmCoFL4HR4LswY3WF+KnzHsF8kAGx4Dt
iHeizRJUNB4DlneZYEKt
=UDXA
-----END PGP SIGNATURE-----

--Apple-Mail=_54C0312F-8A01-4C9A-973B-525713281E0E--


From nobody Fri Feb  3 10:48:56 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC45A1294EB; Fri,  3 Feb 2017 10:48:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcRzsbB_WUv3; Fri,  3 Feb 2017 10:48:49 -0800 (PST)
Received: from mail-qt0-x242.google.com (mail-qt0-x242.google.com [IPv6:2607:f8b0:400d:c0d::242]) (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 E6DB71294D5; Fri,  3 Feb 2017 10:48:48 -0800 (PST)
Received: by mail-qt0-x242.google.com with SMTP id s58so6118915qtc.2; Fri, 03 Feb 2017 10:48:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=P/+uy83y4EydEgJ3ULTvUx52RmWHgyOrq92KWXsuhVY=; b=uxpvWGI8KbH/q1AZSpULCtgfPbSVPrCQJdn5YiEy6ws0a0djjpeVm6ds0HaoCU4ve8 MLiTjWQnsW/moc+cKGrieM2dVsHapcPrzdmcZk/NhcgncP6All0rq3NLRl0wh7kAl6oY jWx5+QKwLq1at4CANUbwFtDFKRVzkpF4qhGUSZW2xyUqQWuU+XqI8d0Xl4ll0LxTOOb6 DUQkLHLwMMelRV7QshCirlMbNCLiXG4exBiXCDlgLX6VH+cxXOQKTzj092ZTmsyAT5FW 69hGd2oD0UebEVxNPAmq9+1rFcq0YtlzEebhxV+jwPmVEDqyuRVSzzVcwo7k43rLy6la VgnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=P/+uy83y4EydEgJ3ULTvUx52RmWHgyOrq92KWXsuhVY=; b=CDAhcbtAePnLYP1QymAGdct5SWr6KcyQQIf7veo09X7K8Sa2aWQGsBBvXgp6uqt4S7 hYNfL4zAOdP1JlQTmlp5SuQTkTLg535tJMK8IUbRqIR4M0vFZ3vGXnM4UGNUibjSovIV 1f09GK/QEc7HaSu54xV29UiZK2Z28LOne3ZP1Q/UdQCGfQ66+iirxmVPvZ6/XAbi7Vgb Opaa5I4sdJoim8F3BdJnzB50sTLUqF5xZSRS/eqtngFkbqQLPt2DYnjLTK8uLWNZOEN6 I3RwJy1kZuo4VIx6rorCj7GOpgabonrXSIR6E0kM4PU2wULYkojXo3ToPMtsvtlBzptN K4ig==
X-Gm-Message-State: AIkVDXKiR3+6yrGMPqYyNxijQl+DDsCa+f/+Rb2niSYgjiBMzT2JVuwiiuyrXx1hm5c2jVtdF+BQ7DXkNW5zFg==
X-Received: by 10.55.189.130 with SMTP id n124mr15209952qkf.235.1486147727904;  Fri, 03 Feb 2017 10:48:47 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.29 with HTTP; Fri, 3 Feb 2017 10:48:47 -0800 (PST)
In-Reply-To: <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Fri, 3 Feb 2017 10:48:47 -0800
X-Google-Sender-Auth: 2YOFO7RBCcAx_oVmpAf4vy4Rnzg
Message-ID: <CAJE_bqem9219YiV_iY3JXZmTjAH4+eGfoVTRhXbD0Pw_m-ypVg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P0mZ7Lfnmr8tKzrDXwd3V7P93fc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, IPv6 IPv6 List <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 18:48:51 -0000

At Fri, 3 Feb 2017 13:37:45 +1300,
Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> >    With one exception, extension headers are not processed by any node
> >    along a packet's delivery path, until the packet reaches the node (or
> >    each of the set of nodes, in the case of multicast) identified in the
> >    Destination Address field of the IPv6 header.
>
> (FYI, the exception is the hop-by-hop extension header.)
>
> I do not dispute that this sentence reached WG consensus. However, I want
> to ask if it has IETF consensus. In my opinion, this sentence should read
>
>    With one exception, extension headers are not processed, inserted,
>    deleted or modified by any node along a packet's delivery path, until
>    the packet reaches the node (or each of the set of nodes, in the case
>    of multicast) identified in the Destination Address field of the IPv6
>    header.
>
> I believe this was always the intended meaning of the word "processed"
> from the earliest design phase of IPv6, but some people have read this
> text as allowing insertion, deletion or modification of headers. IMHO
> it needs to be clarified.

I'd also like to see if it has IETF consensus.  I've never understood
why we can't correct text when it has been misunderstood and while
(almost?) everyone agrees it's really misunderstanding according to
the intent of the author of the text.
I stated it in a bit more detail at the time of WGLC:
https://www.ietf.org/mail-archive/web/ipv6/current/msg25489.html

Brian hinted that the wg probably just got stuck about this discussion
and realistically we can only discuss it in the IETF last call:
https://www.ietf.org/mail-archive/web/ipv6/current/msg25490.html

My understanding is that that's why we're now having this thread and I
fully support and appreciate it.  I guess this also answers the
question of whether we're re-spinning it here.  In fact, in my
understanding that's exactly the point of having both WG and IETF last
calls.

As for the actual text, I support the suggested text by Brian.  I
would probably propose something slightly different myself, but I'm
fine as long as the clarity issue is resolved/improved.

--
JINMEI, Tatuya


From nobody Fri Feb  3 10:59:20 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FEC51294D5 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 10:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.898
X-Spam-Level: 
X-Spam-Status: No, score=-5.898 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8tgIpRr1tVK9 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 10:59:17 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::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 CBA7F1294C8 for <ietf@ietf.org>; Fri,  3 Feb 2017 10:59:16 -0800 (PST)
Received: by mail-oi0-x230.google.com with SMTP id s203so16342999oie.1 for <ietf@ietf.org>; Fri, 03 Feb 2017 10:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=91ejOLoooey9E5wH6YkD2BZwXtvecamp8O2rYMcoHUk=; b=YXbluRNhc7v5CobCc6l4es+UB4Frms3N13LOS2usRHYMRtw0K3RJ6jE97U/yblfS47 5lNKiqDFWponIvK5Eix7immcGIBb28zCWS++bPO8hNz8BPJznKRfsOU39T2w2OJAC2Vt XG0mZM6+LFSca17c5QTuNHASZdDEj7hDdtHKP/caRh7HQUnwwnGl7EaknXb1KAheBxgM U6SbHzpTy3vf/GewdKTq2BJXdhWhZlKxmUKn2R4iw98lv+P+IL671+CRWEnb9mAeMnby ppOOkL3QB2aTmNery+Te4A/ISn0bIN6WaLOiXDTVFlD6eAwgIUPls2AjrkXOeICbm+Ib vSHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=91ejOLoooey9E5wH6YkD2BZwXtvecamp8O2rYMcoHUk=; b=L9ei9nLeXhA24tioAqtden5hhUnmmnSW01aFuJhq3qxnf94UjkX/wkozVTU5aoYI/B kE2HKNA+4SEZ3GzFBmK8Spn/HHKNwLGlDczFA6wedfZm5lQOm2CviXPzeFPies1/NwxS j34CqujJib7UXNqWW57KK0rYEHgrmUVAstFXDzIrwowAsxfWwzKnveoZXfFkTWuc3A5L QEpnUyQPiX0afJ/x01hWS6R1THkZR+8ugV6jvr4W4SjX7S9J77s6oicAPqhgy/HM7163 yvPEk/ekfVCOxMvUes4rvLOpgBK9GdSY/I6CUnAHn4IOlL9OUiExvhIflF0GgAX8Jp9l Zflw==
X-Gm-Message-State: AIkVDXIhVW107T39UU8sFUqCYP2Vu23HNqJlVsu30VpEHdQS6HHr/PqwBFwgF8YF+ELixiIyR2qiBtZ9YR8GVnFV
X-Received: by 10.202.178.11 with SMTP id b11mr8171813oif.101.1486148356006; Fri, 03 Feb 2017 10:59:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Fri, 3 Feb 2017 10:59:15 -0800 (PST)
In-Reply-To: <D45CE6A5317D4B373CD90742@PSB>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB>
From: Wei Chuang <weihaw@google.com>
Date: Fri, 3 Feb 2017 10:59:15 -0800
Message-ID: <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113cd284dd624b0547a4e041"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5aWIRcPQ458vnL0pRp7eHWnydas>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 18:59:19 -0000

--001a113cd284dd624b0547a4e041
Content-Type: multipart/alternative; boundary=001a113cd284d83acc0547a4e02c

--001a113cd284d83acc0547a4e02c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Fri, Feb 3, 2017 at 8:07 AM, John C Klensin <john-ietf@jck.com> wrote:

> Victor, Wei Chuang, and IESG,
>
> The more this discussion goes on, the more I become convinced
> that this document should make an explicit reference to the IDNA
> 2008 and SMTPUTF8 documents,


There is a recently posted 06 draft now, that calls out the IDNA 2008
requirement (RFC 5890) for the domain of the email address explicitly.
This is for SmtpUtf8Name and rfc822Name.  In the very brief time its been
up, we haven't gotten feedback in the WG for that proposal.  It currently
and previously called out that the format of SmtpUtf8Name is SmtpUtf8Mailbox,
and that is a modified form of Internationalized Mailbox defined in Section
3.3 of (RFC6531).

say that strings in certificates
> MUST conform to whatever is allowed there and then, other than
> making a statement about preference for U-labels over A-labels
> (or vice versa), say as little as possible.


The document calls for SmtpUtf8Name to use U-labels or NR-LDH ASCII labels
for domain but not A-labels.  We got advice to minimize alternative domain
forms as some implementations have had bugs doing the transform.  We chose
U-labels to be consistent as the local-part is already UTF8 form and to
simplify implementations.  The document recommends that SmtpUtf8Name only
be used when the local-part requires UTF8 and otherwise use rfc822Name.

-Wei


> The problem is that
> use of forms that might have coded meanings without knowing what
> those meanings are is an opportunity for mischief, something
> that should be of special concern for a piece of work that is
> security-specific.
>
> I note that "prohibit everything that has a prefix consisting of
> two ASCII letters followed by '--' unless the letter sequence is
> specifically allowed" has been discussed at length and then
> agreed on in at least three WGs specialized about the
> identifiers, not just their embeddings (original IDN, IDNbis,
> and PRECIS).  Even if there were a growing consensus that a
> different rule would be more appropriate (and, AFAICT, there
> definitely is not), it would be a bad idea for LAMPS or other
> certificate-related work to get ahead of that consensus and
> specify something inconsistent with the identifier standards
> themselves.
>
> Phill's proposal, independent of its merits, is almost
> irrelevant to the question.  From the standpoint of the present
> work, it is one of many proposals to do interesting things with
> the DNS by using ACE-style (or trick-prefix) labels.  If the
> community concludes that it is a good idea and has a plausible
> chance of global deployment, the DNS/IDNA and SMTP (or SMTPUTF8)
> specs will need to be modified to allow the prefix.  The LAMPS
> "eai" spec should be written so that, if those specifications
> are modified, whatever they allow should be allowed in certs,
> but should, again, not be allowed to get ahead.   If that means
> we are now in need of an IANA registry of such prefixes (with
> exactly one initial entry plus maybe one long-deprecated one),
> that ought to be easy to do.
>
> As to "put all the alternate forms in the cert", we've been
> there too and it hasn't ended happily.  Fully-qualified DNS
> names are part of a hierarchy.   Transcoding between A-labels
> and U-labels is an algorithmic matter, not a hierarchy of
> choices but, if there are even two choices for the form of a
> label at each of several different levels of the hierarchy, one
> rapidly gets to a combinatorial explosion.  I trust everyone
> here can do the arithmetic.  If listing all of the possible
> variations on an FQDN in the certificate is the solution, then
> the WG -- on behalf of those who issue, certify, validate, and
> check certificates -- needs to be prepared for certs with
> dozens, sometimes hundreds, of names in them, not just the
> examples that have been floated with perhaps two or three.
>
> Remembering that, if, as Porky Pig, I can get a cert issued to
> me with Mickey Mouse as an alternate name that is treated as a
> synonym for all purposes, much of the value of certification is
> lost and, IMO, we are all in big trouble.   If the WG wants to
> encourage alternate name behavior, I think it is imperative that:
>
>         (i) The document contain explicit instructions to
>         certificate issuers and CAs about what should be checked
>         and to client systems about what should be
>         believed/trusted and under what circumstances.
>
>         (ii) Certificate provisions to specify certification
>         levels and exactly what is being certified need to be
>         reexamined and probably expanded to identify trust
>         levels and accountability around alternate names.
>
>         (iii) The "Security Considerations" section of the I-D
>         should be expanded to explicitly discuss these cases and
>         the risks.
>
> The document should not be approved until that work is complete
> and reaches consensus.
>
>    best,
>       john
>
>
> --On Wednesday, February 1, 2017 21:01 +0000 Viktor Dukhovni
> <ietf-dane@dukhovni.org> wrote:
>
> > On Tue, Jan 24, 2017 at 07:31:09PM -0000, John Levine wrote:
> >
> >> > My impression is that there is little problem with the
> >> > intended underlying spec, but the document text needs some
> >> > tuning.
> >>
> >> Agreed.  The subsequent section on comparing names would
> >> likely benefit from clearer instructions, e.g.
> >>
> >> a) if the domain contains A-labels, turn them into U-labels
> >> b) if the domain still contains R-LDH labels, stop, not a
> >> valid name. c) if the domain contains NR-LDH labels, make
> >> them all the same case d) do a straight byte comparison of
> >> the addresses
> >
> > I think that restricting R-LDH labels that are not A-labels is
> > too strict, see for example Phil Hallam-Baker's proposed
> > encapsulation of email addresses with "the mesh" (attached).
> >
> >   TL;DR:
> > alice@example.com.mm--MBTVK-ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE
> >
> > The "mm" R-LDH namespace (if/when implemented) or some other
> > future namespace should probably not be excluded at this time.
> >
> > If the intent is to canonicalize A-labels to U-labels, then
> > perhaps only "xn--" labels should be proscribed, if any.
> >
> > On the other hand, I see there is some support for allowing
> > certificates to contain whatever form is actually used in email
> > headers, and perhaps more than just one such form.  If so,
> > there is no need to proscribe any names at all.  The client
> > performs no conversions, and the certificate would need to be
> > inclusive of any addresses that are in actual use.
>
>
>
>
>

--001a113cd284d83acc0547a4e02c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 8:07 AM, John C Klensin <span dir="ltr">&lt;<a href="mailto:john-ietf@jck.com" target="_blank">john-ietf@jck.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Victor, Wei Chuang, and IESG,<br>
<br>
The more this discussion goes on, the more I become convinced<br>
that this document should make an explicit reference to the IDNA<br>
2008 and SMTPUTF8 documents, </blockquote><div><br></div><div>There is a recently posted 06 draft now, that calls out the IDNA 2008 requirement (RFC 5890) for the domain of the email address explicitly.  This is for SmtpUtf8Name and rfc822Name.  In the very brief time its been up, we haven&#39;t gotten feedback in the WG for that proposal.  It currently and previously called out that the format of SmtpUtf8Name is <span style="color:rgb(0,0,0);font-size:13.3333px">SmtpUtf8Mailbox, and that is a modified form of </span><font color="#000000"><span style="font-size:13.3333px">Internationalized Mailbox defined in</span></font><span style="font-size:13.3333px;color:rgb(0,0,0)"> Section 3.3 of (RFC6531).</span></div><div><span style="color:rgb(0,0,0);font-size:13.3333px"><br></span></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">say that strings in <!--
-->certificates<br>
MUST conform to whatever is allowed there and then, other than<br>
making a statement about preference for U-labels over A-labels<br>
(or vice versa), say as little as possible.  </blockquote><div><br></div><div>The document calls for SmtpUtf8Name to use U-labels or NR-LDH ASCII labels for domain but not A-labels.  We got advice to minimize alternative domain forms as some implementations have had bugs doing the transform.  We chose U-labels to be consistent as the local-part is already UTF8 form and to simplify implementations.  The document recommends that SmtpUtf8Name only be used when the local-part requires UTF8 and otherwise use rfc822Name.</div><div><br></div><div>-Wei</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">The problem is that<br>
use of forms that might have coded meanings without knowing what<br>
those meanings are is an opportunity for mischief, something<br>
that should be of special concern for a piece of work that is<br>
security-specific.<br>
<br>
I note that &quot;prohibit everything that has a prefix consisting of<br>
two ASCII letters followed by &#39;--&#39; unless the letter sequence is<br>
specifically allowed&quot; has been discussed at length and then<br>
agreed on in at least three WGs specialized about the<br>
identifiers, not just their embeddings (original IDN, IDNbis,<br>
and PRECIS).  Even if there were a growing consensus that a<br>
different rule would be more appropriate (and, AFAICT, there<br>
definitely is not), it would be a bad idea for LAMPS or other<br>
certificate-related work to get ahead of that consensus and<br>
specify something inconsistent with the identifier standards<br>
themselves.<br>
<br>
Phill&#39;s proposal, independent of its merits, is almost<br>
irrelevant to the question.  From the standpoint of the present<br>
work, it is one of many proposals to do interesting things with<br>
the DNS by using ACE-style (or trick-prefix) labels.  If the<br>
community concludes that it is a good idea and has a plausible<br>
chance of global deployment, the DNS/IDNA and SMTP (or SMTPUTF8)<br>
specs will need to be modified to allow the prefix.  The LAMPS<br>
&quot;eai&quot; spec should be written so that, if those specifications<br>
are modified, whatever they allow should be allowed in certs,<br>
but should, again, not be allowed to get ahead.   If that means<br>
we are now in need of an IANA registry of such prefixes (with<br>
exactly one initial entry plus maybe one long-deprecated one),<br>
that ought to be easy to do.<br>
<br>
As to &quot;put all the alternate forms in the cert&quot;, we&#39;ve been<br>
there too and it hasn&#39;t ended happily.  Fully-qualified DNS<br>
names are part of a hierarchy.   Transcoding between A-labels<br>
and U-labels is an algorithmic matter, not a hierarchy of<br>
choices but, if there are even two choices for the form of a<br>
label at each of several different levels of the hierarchy, one<br>
rapidly gets to a combinatorial explosion.  I trust everyone<br>
here can do the arithmetic.  If listing all of the possible<br>
variations on an FQDN in the certificate is the solution, then<br>
the WG -- on behalf of those who issue, certify, validate, and<br>
check certificates -- needs to be prepared for certs with<br>
dozens, sometimes hundreds, of names in them, not just the<br>
examples that have been floated with perhaps two or three.<br>
<br>
Remembering that, if, as Porky Pig, I can get a cert issued to<br>
me with Mickey Mouse as an alternate name that is treated as a<br>
synonym for all purposes, much of the value of certification is<br>
lost and, IMO, we are all in big trouble.   If the WG wants to<br>
encourage alternate name behavior, I think it is imperative that:<br>
<br>
        (i) The document contain explicit instructions to<br>
        certificate issuers and CAs about what should be checked<br>
        and to client systems about what should be<br>
        believed/trusted and under what circumstances.<br>
<br>
        (ii) Certificate provisions to specify certification<br>
        levels and exactly what is being certified need to be<br>
        reexamined and probably expanded to identify trust<br>
        levels and accountability around alternate names.<br>
<br>
        (iii) The &quot;Security Considerations&quot; section of the I-D<br>
        should be expanded to explicitly discuss these cases and<br>
        the risks.<br>
<br>
The document should not be approved until that work is complete<br>
and reaches consensus.<br>
<br>
   best,<br>
      john<br>
<br>
<br>
--On Wednesday, February 1, 2017 21:01 +0000 Viktor Dukhovni<br>
<div class="gmail-CSS_CV_TRIMMABLE_"><div class="gmail-CSS_CV_ELIDED_TEXT_">&lt;<a href="mailto:ietf-dane@dukhovni.org">ietf-dane@dukhovni.org</a>&gt; wrote:<br>
<br>
&gt; On Tue, Jan 24, 2017 at 07:31:09PM -0000, John Levine wrote:<br>
&gt;<br>
&gt;&gt; &gt; My impression is that there is little problem with the<br>
&gt;&gt; &gt; intended underlying spec, but the document text needs some<br>
&gt;&gt; &gt; tuning.<br>
&gt;&gt;<br>
&gt;&gt; Agreed.  The subsequent section on comparing names would<br>
&gt;&gt; likely benefit from clearer instructions, e.g.<br>
&gt;&gt;<br>
&gt;&gt; a) if the domain contains A-labels, turn them into U-labels<br>
&gt;&gt; b) if the domain still contains R-LDH labels, stop, not a<br>
&gt;&gt; valid name. c) if the domain contains NR-LDH labels, make<br>
&gt;&gt; them all the same case d) do a straight byte comparison of<br>
&gt;&gt; the addresses<br>
&gt;<br>
&gt; I think that restricting R-LDH labels that are not A-labels is<br>
&gt; too strict, see for example Phil Hallam-Baker&#39;s proposed<br>
&gt; encapsulation of email addresses with &quot;the mesh&quot; (attached).<br>
&gt;<br>
&gt;   TL;DR:<br>
&gt; alice@example.com.mm--MBTVK-<wbr>ZKCWT-KHMTE-XM3I7-GSQNK-MLFYE<br>
&gt;<br>
&gt; The &quot;mm&quot; R-LDH namespace (if/when implemented) or some other<br>
&gt; future namespace should probably not be excluded at this time.<br>
&gt;<br>
&gt; If the intent is to canonicalize A-labels to U-labels, then<br>
&gt; perhaps only &quot;xn--&quot; labels should be proscribed, if any.<br>
&gt;<br>
&gt; On the other hand, I see there is some support for allowing<br>
&gt; certificates to contain whatever form is actually used in email<br>
&gt; headers, and perhaps more than just one such form.  If so,<br>
&gt; there is no need to proscribe any names at all.  The client<br>
&gt; performs no conversions, and the certificate would need to be<br>
&gt; inclusive of any addresses that are in actual use.<br>
<br>
<br>
<br>
<br>
</div></div></blockquote></div><br></div></div>

--001a113cd284d83acc0547a4e02c--

--001a113cd284dd624b0547a4e041
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCDv+v7opGdiXX3RN5BGXpgn
lWk4wH2QjoqK39ZIwyT31zAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMDMxODU5MTZaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAODo/99mqfsb1Ez6JIrmT3+W8DmwaF6AAKH4dhMMw
SVWY0N9135UxZKYe+Rzz3XMoXMFJ5zZUbwIkndfxP7zKuJmqgFkwMBk9KWl5NRa2P/8PAM4QG/tp
Xmru4gVa043Aq/yMbMfd5hrtPXjAaetB/gx0IWJozj72MzPKM0aPkoA1d+boibKLnulM4/7UU/Ke
4NQ3139Vmtbp59TYQocNh4eJ/CAMQocYvO8jpaXHSNdevHhnk3dYSIiJUagbUsLaz5WltLp51tUR
F8cQt0yRbcUjTVXPFgRYokGwc6Q7r453eD5P4HrwReqhvZ1NLRqFnjtny4uVlrZUCZ0tSG3J2g==
--001a113cd284dd624b0547a4e041--


From nobody Fri Feb  3 11:05:53 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E0851296AA; Fri,  3 Feb 2017 11:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.851
X-Spam-Level: 
X-Spam-Status: No, score=-0.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 HduRBI6i5n83; Fri,  3 Feb 2017 11:05:46 -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 78F431296A6; Fri,  3 Feb 2017 11:05:46 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 2A70A8361F; Fri,  3 Feb 2017 20:05:41 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <fbd92b47-5dba-909a-c0e5-e6430141d6dc@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <e52d671b-97a4-6d64-67e2-54d3326480a0@si6networks.com>
Date: Thu, 2 Feb 2017 22:38:58 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <fbd92b47-5dba-909a-c0e5-e6430141d6dc@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YocjBXcRIv5sZGry0NWiU4Z7sUc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ipv6@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:05:48 -0000

On 02/02/2017 09:26 PM, Brian E Carpenter wrote:
> 
> On 02/02/2017 22:14, Fernando Gont wrote:
> ...
>> The current impossibility to parse an IPv6 header chain that includes
>> unknown Next Header values 
> 
> Wait... you're talking about parsing by intermediate systems. The destination
> node either can understand the new Next Header or transport protocol,
> or it can't. That's fine, and is the intended result.

If it can, it already knows the syntax, so what's the point of a uniform
syntax? -- it could be anything, and wouldn't change anything.




>> results in concrete implications for the
>> extensibility of the IPv6 protocol, and the deployability of new
>> transport protocols.  Namely,
>>
>>  o  New IPv6 extension headers cannot be incrementally deployed.
>>
>>  o  New transport protocols cannot be incrementally deployed.
> 
> In both cases, add "in the presence of interfering middleboxes".
> 
> This is not new. For a document moving from PS to Standard, it is
> not something we can change.
> 
> Note, I am all for coming back to this problem, after we have the
> Internet Standard in place. Maybe we can fix it or maybe we can't,
> but it's IMHO off topic here.

Ok. Makes sense.

Cheers,
-- 
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  3 11:06:02 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B47C1294D5; Fri,  3 Feb 2017 11:06:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.851
X-Spam-Level: 
X-Spam-Status: No, score=-0.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 ZuRCYLoEHChk; Fri,  3 Feb 2017 11:05:57 -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 7BD401296AD; Fri,  3 Feb 2017 11:05:57 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 1F1288362C; Fri,  3 Feb 2017 20:05:51 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Eggert, Lars" <lars@netapp.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com>
Date: Thu, 2 Feb 2017 23:00:27 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EOkm4v-079UBmSTZe1GHiwYECSg>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:06:00 -0000

On 02/02/2017 09:18 PM, Brian E Carpenter wrote:
> On 02/02/2017 22:54, Fernando Gont wrote:
>> Hi, Lars,
>>
>> On 02/02/2017 06:37 AM, Eggert, Lars wrote:
>>> Hi,
>>>
>>> the last paragraph of the introduction reads:
>>>
>>> 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 over paths where
>>> delivery of ICMP messages to a host is not assured.
>>>
>>> Given that ICMP delivery cannot be assured over the vast majority of
>>> paths in the current Internet, should this document make a
>>> recommendation to implement RFC4821?
>>
>> I think that RFC4821 should be recommended, at least for dealing with
>> ICMP blackholes (i.e., use ICMP if you can, but be able to deal with
>> scenarios in which you don't receive them).
> 
> Many people think that, but this draft is constrained by the rules in
> RFC6410 about "high degree of technical maturity" and "widespread
> deployment" in the move from PS to Standard. Adding new stuff is not
> supposed to happen. If I recall correctly, the WG tuned the language
> to its present state for that reason.

My apologies: my comments were probably misleading. Certainly, this
document is simply RFC1981 to Std, and hence recommending RFC4821 would
be kind of ou of scope, here.

That say, one might wonder to what extent, and for the general Internet,
RFC1981 can be considered succesful (given the filtering of ICMP
messages). -- i.e., at this point in time you wouldn't rely on RFC1981
(icmp-based pmtud) for path-mtu discovery.

Cheers,

-- 
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  3 11:24:07 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678B612973E for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 w71NqMqE57kq for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:23:57 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49AC6129721 for <ietf@ietf.org>; Fri,  3 Feb 2017 11:23:57 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 8264F284E4B for <ietf@ietf.org>; Fri,  3 Feb 2017 19:23:55 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com>
Date: Fri, 3 Feb 2017 14:23:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-i9SfIemZYDlXN1MAuSZNEiONRs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:23:58 -0000

> On Feb 3, 2017, at 1:59 PM, Wei Chuang <weihaw@google.com> wrote:
>=20
> The document calls for SmtpUtf8Name to use U-labels or NR-LDH ASCII =
labels
> for domain but not A-labels.  We got advice to minimize alternative =
domain
> forms as some implementations have had bugs doing the transform.  We =
chose
> U-labels to be consistent as the local-part is already UTF8 form and =
to
> simplify implementations.  The document recommends that SmtpUtf8Name =
only
> be used when the local-part requires UTF8 and otherwise use =
rfc822Name.

Can you clarify what this means for addresses such as:

	U: ietf-dane@=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.org
	A: ietf-dane@xn--b1adqpd3ao5c.org

The local part is all ASCII, so should the "U" or "A" variant be used?

--=20
	Viktor.


From nobody Fri Feb  3 11:34:59 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA041297EE; Fri,  3 Feb 2017 11:34:54 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wVBGUZSdD3-D; Fri,  3 Feb 2017 11:34:53 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e: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 581C31297E9; Fri,  3 Feb 2017 11:34:53 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id 204so8991976pge.0; Fri, 03 Feb 2017 11:34:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=+bQZuTd8sdWUo2JNI/3FRh3JqLl8QnTntUa9ia6Xihc=; b=kXEXkf5Eog0Hyfay7PyBtf4dp+U029XIveqdUWun4ou7GKEU64w0k91C4l1/ruyabw SEQwOuTQRbO9/ceKxAS/OBJEzzXFu19qHIOdV4CNCyBlA9ihrPutPaoqEutwxIcsWqup PDGhbP7iVVfnwHgs6AHoE8yEsAPe6LamL6THDErUT5Lizii1jcu/2AG+xqacrvwexnqW SWWIZkVrgcfA1aMYvYpz4PEU+UhG99tAGVEcUajrnrOC/LldE8AHwGOBPsyAGa+sCp2Q jJnjM0yrO2kvGLp6KiRTLfx3Vehc1wXOTvlzc6tSCUTOz0SVmu2HJA47pSIe+N5ffVBq 67aQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=+bQZuTd8sdWUo2JNI/3FRh3JqLl8QnTntUa9ia6Xihc=; b=Qzt+RtzP9Izs3hJPfDxIWrHQ7si6sgvp+gFkocvEoaA4VYXarXJD56HlgQZRJ0A+K1 PpZ4hvLyXzS3oSpu1bavV0Oyci54NsP0cMMFZ2FRyOB/HfrrGsmM+dzxRoUUQKaHrvD2 e+S+oLMIfL97wirF4zi2Zar6VMFcjJMTMZ7L6rrJRxBJTPg7DsDf3D//FxSHtYN4Vf4N 9yoDIL9Y1SIa+zkurO5w3YEkdJceu/DOnuTxtA8LfzniyAq40zF0f73ds1st5gY3s71E DWtYqZqc9q8HNPY8kLtybvLH04f7+YGXTCFAuSiVqNLUT8ISkZ3Tauu+U3qDE0cyCbz9 8d/g==
X-Gm-Message-State: AIkVDXIFrbeopDGqEEWzOisQOt7w4PN9T2TkaSMZ9nIijjPpdACquBjw57ydyrxVbbrHRQ==
X-Received: by 10.98.55.66 with SMTP id e63mr20253307pfa.156.1486150492747; Fri, 03 Feb 2017 11:34:52 -0800 (PST)
Received: from [192.168.178.21] ([118.149.101.21]) by smtp.gmail.com with ESMTPSA id j185sm69571740pgd.35.2017.02.03.11.34.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Feb 2017 11:34:52 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: "Stefano Previdi (sprevidi)" <sprevidi@cisco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <811306aa-a8c5-e1cb-38ac-5bc9723ebe67@gmail.com>
Date: Sat, 4 Feb 2017 08:34:58 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SY8A_W0UyjzfcJ2ns2zzHkn84Bo>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:34:54 -0000

On 03/02/2017 21:51, Stefano Previdi (sprevidi) wrote:
> 
>> On Feb 3, 2017, at 1:37 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>
>> In Section 4 ("IPv6 Extension Headers") the draft says:
>>
>>>   With one exception, extension headers are not processed by any node
>>>   along a packet's delivery path, until the packet reaches the node (or
>>>   each of the set of nodes, in the case of multicast) identified in the
>>>   Destination Address field of the IPv6 header.
>>
>> (FYI, the exception is the hop-by-hop extension header.)
>>
>> I do not dispute that this sentence reached WG consensus. However, I want
>> to ask if it has IETF consensus. In my opinion, this sentence should read
>>
>>   With one exception, extension headers are not processed, inserted,
>>   deleted or modified by any node along a packet's delivery path, until
>>   the packet reaches the node (or each of the set of nodes, in the case
>>   of multicast) identified in the Destination Address field of the IPv6
>>   header.
>>
>> I believe this was always the intended meaning of the word "processed"
>> from the earliest design phase of IPv6, but some people have read this
>> text as allowing insertion, deletion or modification of headers. IMHO
>> it needs to be clarified.
> 
> 
> are we re-spinning the debate on a WG-agreed text ? 

Yes. That's what an IETF Last Call is about.

   Brian


From nobody Fri Feb  3 11:38:45 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7078C12948C for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:38:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.898
X-Spam-Level: 
X-Spam-Status: No, score=-5.898 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ZNI_4ISakBQ for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:38:43 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::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 CDBED12940B for <ietf@ietf.org>; Fri,  3 Feb 2017 11:38:42 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id j15so16960092oih.2 for <ietf@ietf.org>; Fri, 03 Feb 2017 11:38:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=x6E8EZlzihNaRnDMiqtGIn37lJZDl1RIvAmERi5R7h8=; b=MVa1pqHMMnV4B8YlYoDx/m4d2KzgqN2fmtUsCrT0PkBp7vDeA5p2u9WwnBH9GuSwal j+uriZRfSwHDV2xFDixEIWzekFt/yaI8MAiOcqwHdOzbXhOqoazi4hImLV5/vqMgAl7y mad41hjdmkgRBefbYUU+WCXT5FYRr5qMGYJKPuCZwylm7L3h4OEqGPQMf8ohZS5slXCF RSHdReatEn8HgULjtFRuw10R+lCi8fw0+4HBJYvAnxuRRcTdsWtsofKLivZe13uAm9O2 F99Tc7kL5aytCinA3wfmZz5y/MIRItbK9nhLPhXZKB6dXDtXolPLrs/s+RP5//GRXB7y 6A9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=x6E8EZlzihNaRnDMiqtGIn37lJZDl1RIvAmERi5R7h8=; b=UD8vp8JWSGjyFw1A9LQAd7QU1YJpsh3DB2GTSqBoHvxG/kxQFQgH7r0pFqsUpAFCVL +VgYfqZDGq4mP/DqjGWVEQIyh3SBC3owJ3xbfaIYyqhqayFX0gvjvV8tgKZkpJOPQ2wc uBirWkJXFbI4dFiZHg44hJPO3FulXL+R9VVM49/8H42RiKhqxC/1vpr1lS02f6PL//qW X2dVkEAwU3SHpwDdpgCU6Kq4PVJE1dD96V2qc3KC8NN8vaf0cSzwQ3xrxmNfqhZczZMl junrxEU2fssSHXf7WW+ShvS1jwHLb8A6osN1FAYLAUCntk1TW4JGAROA/ZKqSWL2XL+1 nQcg==
X-Gm-Message-State: AIkVDXKunChTmVD80b+W3IQ/UGC0VRNIrN3hjHjNqGAxJwSW0y0TOK+qvBCdENyvEXaXVkNkb8bhU08ONCSLG5tm
X-Received: by 10.202.245.214 with SMTP id t205mr7237599oih.52.1486150721788;  Fri, 03 Feb 2017 11:38:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Fri, 3 Feb 2017 11:38:40 -0800 (PST)
In-Reply-To: <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org>
From: Wei Chuang <weihaw@google.com>
Date: Fri, 3 Feb 2017 11:38:40 -0800
Message-ID: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113df090dffad70547a56d53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D_dxLAGI2Pea-0GNqkMvO_7nnSw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:38:44 -0000

--001a113df090dffad70547a56d53
Content-Type: multipart/alternative; boundary=001a113df090db35690547a56d3f

--001a113df090db35690547a56d3f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Fri, Feb 3, 2017 at 11:23 AM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Feb 3, 2017, at 1:59 PM, Wei Chuang <weihaw@google.com> wrote:
> >
> > The document calls for SmtpUtf8Name to use U-labels or NR-LDH ASCII
> labels
> > for domain but not A-labels.  We got advice to minimize alternative
> domain
> > forms as some implementations have had bugs doing the transform.  We
> chose
> > U-labels to be consistent as the local-part is already UTF8 form and to
> > simplify implementations.  The document recommends that SmtpUtf8Name only
> > be used when the local-part requires UTF8 and otherwise use rfc822Name.
>
> Can you clarify what this means for addresses such as:
>
>         U: ietf-dane@духовный.org


Not recommended but supported by SmtpUtf8Name.


>
>         A: ietf-dane@xn--b1adqpd3ao5c.org


Use rfc822Name.  This is recommended.

-Wei


>
>
> The local part is all ASCII, so should the "U" or "A" variant be used?
>
> --
>         Viktor.
>
>

--001a113df090db35690547a56d3f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 11:23 AM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
&gt; On Feb 3, 2017, at 1:59 PM, Wei Chuang &lt;<a href="mailto:weihaw@google.com">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; The document calls for SmtpUtf8Name to use U-labels or NR-LDH ASCII labels<br>
&gt; for domain but not A-labels.  We got advice to minimize alternative domain<br>
&gt; forms as some implementations have had bugs doing the transform.  We chose<br>
&gt; U-labels to be consistent as the local-part is already UTF8 form and to<br>
&gt; simplify implementations.  The document recommends that SmtpUtf8Name only<br>
&gt; be used when the local-part requires UTF8 and otherwise use rfc822Name.<br>
<br>
</span>Can you clarify what this means for addresses such as:<br>
<br>
        U: <a href="mailto:ietf-dane@%D0%B4%D1%83%D1%85%D0%BE%D0%B2%D0%BD%D1%8B%D0%B9.org">ietf-dane@духовный.org</a></blockquote><div><br></div><div>Not recommended but supported by SmtpUtf8Name.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
        A: <a href="mailto:ietf-dane@xn--b1adqpd3ao5c.org">ietf-dane@xn--b1adqpd3ao5c.org</a></blockquote><div><br></div><div>Use rfc822Name.  This is recommended.</div><div><br></div><div>-Wei</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
The local part is all ASCII, so should the &quot;U&quot; or &quot;A&quot; variant be used?<br>
<span class="gmail-CSS_CV_TRIMMABLE_"><font color="#888888"><br>
--<br>
        Viktor.<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a113df090db35690547a56d3f--

--001a113df090dffad70547a56d53
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCBBsZv5dEYlG5qBT1iPdA6o
3WE0clvpbYWRM53y9F+p2jAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMDMxOTM4NDJaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAIH9eovE57CnTQE2iXGBzEnHg8UyD+B8CdqrNCpI0
rkoPATtpw6QMINp3XB+5Y03DivEpLbYUY4YpXprE/qslhMfD8S4lp1BMcDtKCvRU7jt00J4e4plg
mp4GhVBbn2h7YtPzl99j0+mG5TxxJqgXDScG/1MliLGZMs+N2KP8DzvuJU7EOTGgq4RVgzoDqcqE
YXFWDlxxRvM0n6zC9FSoPNrqSllJ9lQyZj8nhhZve0aobODhhN9PBmG1rwOeJwNXK+59cp/ov2LX
I65pwqRspVXttD/xHcQJHf8VK9MiKVHSXgHCfNC1hGGUTvtvF45UVdyWbk0rwewT6NXDsV/3sg==
--001a113df090dffad70547a56d53--


From nobody Fri Feb  3 11:41:41 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9F8A1293F5; Fri,  3 Feb 2017 11:41:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.198
X-Spam-Level: 
X-Spam-Status: No, score=-10.198 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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1E7rhGEXaNk; Fri,  3 Feb 2017 11:41:38 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 236C1128B37; Fri,  3 Feb 2017 11:41:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486150898; x=1517686898; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=3qnX0uxaVGDj7YWz9/y8cBqWhIH8QEA1GrVmnGvVEEQ=; b=UeVI+zQEdlZvS+sDSv4jCbZ9MNZlC6kv6nJFa7ABpMOHeTEHSSYOCeRb d6/ygW1vHlNKVtSJLlKIC2DWEPR3M2kc5NdWryZg92VetKjRAbTXvzZgp 1zXtVIT1cgEHZbCrhYpRwg2jKFKLZAxT5y7WpAZOcXwxC3QuSRVIwwujm Q=;
X-IronPort-AV: E=Sophos;i="5.33,330,1477983600";  d="scan'208,217";a="355581646"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 03 Feb 2017 11:41:37 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8428"; a="1307002315"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Feb 2017 11:41:36 -0800
Received: from [10.64.125.251] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 3 Feb 2017 11:41:35 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 3 Feb 2017 13:41:34 -0600
Message-ID: <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com>
In-Reply-To: <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_64B0929F-8E95-4727-8DFA-04A31A3FE6A2_="
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01G.na.qualcomm.com (10.85.0.33) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pdbghjwFa3Z70bnK9jcP-k85ijg>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:41:40 -0000

--=_MailMate_64B0929F-8E95-4727-8DFA-04A31A3FE6A2_=
Content-Type: text/plain; format=flowed; markup=markdown

On 3 Feb 2017, at 12:22, otroan@employees.org wrote:

>> are we re-spinning the debate on a WG-agreed text ?
>>
>> <tp>
>>
>> Yes, and I am sure that that is exactly what is intended.
>
> Then let's encourage people outside of 6man, with other points of 
> view, and other arguments to come forward.
>
> A re-run of the discussions already had in 6man with the same 
> arguments and the same participants doesn't seem useful.
>
> For a brief (sic) overview take a look at 672 messages already on the 
> topic:
> https://mailarchive.ietf.org/arch/search/?q=header+insertion&f_list=ipv6
>
> O.

Might I, as a relatively disinterested observer of this discussion, 
humbly[1] suggest that pointing the IETF list to a 672-message thread is 
not a way to avoid re-running the discussion "with the same arguments 
and the same participants". It would be significantly more useful if 
you, as chair and the caller of the (apparently rough) consensus 
summarized the issue, explained what you took the objection to be, and 
told us what you saw as the replies to those objections that convinced 
you that WG had properly considered the issue and that there was (rough) 
WG consensus to go with the text you ended up with. Then folks who think 
you called it wrong can explain the essential point they think you 
missed when you made that call. Having the rest of us re-create your 
evaluation of the consensus by reading 672 messages is, at best, 
inefficient.

Cheers,

pr

[1] The non-humble version includes a reference to RFC 7282, sections 2 
and 3.

-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_64B0929F-8E95-4727-8DFA-04A31A3FE6A2_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 3 Feb 2017, at 12:22, <a href=3D"mailto:otroan@employe=
es.org" style=3D"color:#3983C4">otroan@employees.org</a> wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">are we re-spinning the debate on a WG-agreed text ?</p>

<p dir=3D"auto">&lt;tp&gt;</p>

<p dir=3D"auto">Yes, and I am sure that that is exactly what is intended.=
</p>
</blockquote>

<p dir=3D"auto">Then let's encourage people outside of 6man, with other p=
oints of view, and other arguments to come forward.</p>

<p dir=3D"auto">A re-run of the discussions already had in 6man with the =
same arguments and the same participants doesn't seem useful.</p>

<p dir=3D"auto">For a brief (sic) overview take a look at 672 messages al=
ready on the topic:<br>
<a href=3D"https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion=
&amp;f_list=3Dipv6" style=3D"color:#777">https://mailarchive.ietf.org/arc=
h/search/?q=3Dheader+insertion&amp;f_list=3Dipv6</a></p>

<p dir=3D"auto">O.</p>
</blockquote>

<p dir=3D"auto">Might I, as a relatively disinterested observer of this d=
iscussion, humbly[1] suggest that pointing the IETF list to a 672-message=
 thread is not a way to avoid re-running the discussion "with the same ar=
guments and the same participants". It would be significantly more useful=
 if you, as chair and the caller of the (apparently rough) consensus summ=
arized the issue, explained what you took the objection to be, and told u=
s what you saw as the replies to those objections that convinced you that=
 WG had properly considered the issue and that there was (rough) WG conse=
nsus to go with the text you ended up with. Then folks who think you call=
ed it wrong can explain the essential point they think you missed when yo=
u made that call. Having the rest of us re-create your evaluation of the =
consensus by reading 672 messages is, at best, inefficient.</p>

<p dir=3D"auto">Cheers,</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto">[1] The non-humble version includes a reference to RFC 72=
82, sections 2 and 3.</p>

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_64B0929F-8E95-4727-8DFA-04A31A3FE6A2_=--


From nobody Fri Feb  3 11:51:29 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA6841297F7 for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 e7PBBwFFILNz for <ietf@ietfa.amsl.com>; Fri,  3 Feb 2017 11:51:26 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E98012951E for <ietf@ietf.org>; Fri,  3 Feb 2017 11:51:26 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 95403284E4B for <ietf@ietf.org>; Fri,  3 Feb 2017 19:51:25 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com>
Date: Fri, 3 Feb 2017 14:51:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mMPN3mmD-qYA2tcidsVv6mDzQ2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 19:51:28 -0000

> On Feb 3, 2017, at 2:38 PM, Wei Chuang <weihaw@google.com> wrote:
>=20
> Can you clarify what this means for addresses such as:
>=20
>         U: ietf-dane@=D0=B4=D1=83=D1=85=D0=BE=D0=B2=D0=BD=D1=8B=D0=B9.or=
g
>=20
> Not recommended but supported by SmtpUtf8Name.
> =20
>=20
>         A: ietf-dane@xn--b1adqpd3ao5c.org
>=20
> Use rfc822Name.  This is recommended.

So, to be clear, for the same domain, some addresses will be
represented as rfc822Name SAN elements (with the domain in
A-label form), and other addresses (those with non-ASCII
localparts) will be represented as SmtpUtf8Name SAN elements
(with the domain in U-label form).

A verifier checking for an address with a non-ASCII localpart
will compare against SmtpUtf8Name elements with U-label domain
encodings, while a verifier checking for an address with an all
ASCII localpart will check against rfc822Name elements using an
A-label domain encoding (of the same domain).

Is that right?  Thus the verifier would sometimes need to convert
from U-labels to A-labels (when the localpart is all ASCII), and
at other times from A-labels to U-labels (when the localpart is not
all ASCII)...

--=20
	Viktor.


From nobody Fri Feb  3 12:43:12 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B41C3129970; Fri,  3 Feb 2017 12:43:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cooperw.in header.b=JqRZGuVK; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=kgTr8/ZH
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLIH-fdtkrr9; Fri,  3 Feb 2017 12:43:10 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 50052129474; Fri,  3 Feb 2017 12:43:10 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id BE26D207A8; Fri,  3 Feb 2017 15:43:09 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 03 Feb 2017 15:43:09 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=Ce6BOTmYZP2qB07 H5iBfv9uBuDI=; b=JqRZGuVKp3upl5IgtsaqaM+IAsqvEPYCjfh1J0p8FcR0P+b 5faYJAIRWZevxPWYosv+OfAgM29wDzteuZByc2G5M73x8Gxm1j9J34K8cxWryO6X vg1tEyN/q01DmgMpTUPgDI+d5ZfXnh0buY+RIfU02l5EBnk8qJK+MAk3Wf4A=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=Ce6BOTmYZP2qB07H5iBfv9uBuDI=; b=kgTr8/ZH1zOqT3ODYYWn aFiyyD8GZoiEo5uRs7gyjeiC4nYv+Y3wsIByWRtBCNrnMwwlDKxOE4eWqbPfD+Gw YEzoRYOTHvpZvtev0DbawzuAbrPwG7kbURHULF//WTaQ0YfR0/Zrb0Yu+EFTZATI bQda2flldFittoGumDv3yoY=
X-ME-Sender: <xms:XeuUWCBSmCyiVz6pwBYYBZYodQohPmxJXl8MF4a5PLWC7PBKOKqD3A>
X-Sasl-enc: 2AGj4QxJG4ym7kpV3yc4SgyCJZbPnkLc8UFKmasq3uLP 1486154589
Received: from dhcp-10-150-9-217.cisco.com (unknown [173.38.117.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 793C77E077; Fri,  3 Feb 2017 15:43:09 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: NomCom 2016-2017 - Announcement of IESG selections 
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <148587974445.2515.18166506880398063252.idtracker@ietfa.amsl.com>
Date: Fri, 3 Feb 2017 15:43:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9992FFFF-F17A-4712-AE4C-2354CDE3C287@cooperw.in>
References: <148587974445.2515.18166506880398063252.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0VZSW01uz6m4swcAAsIvS0Yudxw>
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 20:43:12 -0000

In light of this announcement, I will be resigning as ART AD effective =
during IETF 98 when I assume the Gen AD/IETF Chair position. I am =
willing to overlap with an incoming ART AD should the vacancy be filled =
prior to then.

Alissa

> On Jan 31, 2017, at 11:22 AM, NomCom Chair 2016 =
<nomcom-chair-2016@ietf.org> wrote:
>=20
> As chair of the 2016-2017 NomCom, it is my pleasure to announce the=20
> selection of IESG members to serve in the 2017-2019 cycle.
>=20
> The selected candidates are:
>=20
> Alissa Cooper, Chair
> Ben Campbell, ART AD=20
> Terry Manderson, INT AD=20
> Warren Kumari, OPS AD=20
> Alvaro Retana, RTG AD
> Deborah Brungard, RTG AD=20
> Eric Rescorla, SEC AD=20
> Spencer Dawkins, TSV AD=20
>=20
> The resulting IESG will consist of:
>=20
> Alissa Cooper, Cisco, Chair
> Ben Campbell, Oracle, ART AD
> Alexey Melnikov, Isode, ART AD
> Suresh Krishnan, Ericsson, Internet AD
> Terry Manderson, ICANN, Internet AD
> Benoit Claise, Cisco, Management AD (O&M AD)
> Warren Kumari, Google, Operations AD (O&M AD)
> Alia Atlas, Juniper Networks, Routing AD
> Deborah Brungard, AT&T, Routing AD
> Alvaro Retana, Cisco, Routing AD
> Kathleen Moriarty, EMC Corporation, Security AD
> Eric Rescorla, Mozilla, SEC AD
> Mirja Kuhlewind, ETH Zurich, Transport AD
> Spencer Dawkins, Wonder Hamster Internetworking, Transport AD
>=20
> The Nomcom of one year ago noted that the IESG would have 3=20
> members from Cisco. This year's IESG makes no changes in this regard.=20=

> We have had no reports that this has caused any issues over the past=20=

> year, and hope that this continues  to remain true in the coming year.
>=20
> The IAB and IAOC selections will be announced after completing the=20
> confirmation procedure.
>=20
> The Nomcom wishes to thank everyone who volunteered, everyone who
> nominated, and everyone who provided feedback to the process. Your=20
> input was vital in coming to this set of decisions.
>=20
> Lucy Lynch
> Nomcom chair 2016-2016
> llynch @ civil-tongue.net
>=20


From nobody Fri Feb  3 12:50:43 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BBA1712997D; Fri,  3 Feb 2017 12:50:35 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Internet Hall of Fame Nominations Open
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148615503572.4157.15179326746633148411.idtracker@ietfa.amsl.com>
Date: Fri, 03 Feb 2017 12:50:35 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4jMx2---0cVegiYOMZiTCRmKgTk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: chair@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 20:50:36 -0000

I was asked share the following message from ISOC to the IETF community.

Jari Arkko, IETF Chair

———

Internet Hall of Fame Nominations Open

Do you know someone who has played a major role in the development and
advancement of the Internet? Now is the time to recognize their contribution.

We are looking for:

• Pioneers who were instrumental in the Internet's evolution;

• Innovators who made outstanding technological, commercial,
   regulatory or policy advances;

• Global Connectors who contributed to the growth, connectivity,
   and use of the Internet that resulted in global impact.

The Internet Hall of Fame honors individuals who have pushed the boundaries
to bring the Internet to life and make it an essential resource for billions
of people.

For more information on how to submit your nomination, please visit:
http://internethalloffame.org/nominations

The deadline for nominations is March 15, 2017.

If you have any questions, please contact internethalloffame@isoc.org.


From nobody Fri Feb  3 12:56:27 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 73BDD129561; Fri,  3 Feb 2017 12:56:26 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Remote hubs for IETF 98
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148615538643.4137.4956475137238651973.idtracker@ietfa.amsl.com>
Date: Fri, 03 Feb 2017 12:56:26 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/77CPLDdUY0eRarIJtgWuVVFuUE4>
Cc: ted.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: chair@ietf.org, ted.ietf@gmail.com, warren@kumari.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 20:56:26 -0000

I’m happy to report that Ted Hardie and Warren Kumari and Google have
stepped up to make alternate arrangements for people who might have
difficulty travelling due to the recent travel restrictions. Thank you! 

Please see the details below:

-------

Hi Jari,

Warren and I have arranged for Google to provide two remote hubs for
participants who won't be able to attend IETF 98 in Chicago because
of the recent travel restrictions.  While we understand that many folks
might prefer to simply attend remotely from their home or office,
experience with the IGF and the Latin American remote IETF hubs
suggests that there may be folks who prefer to be with others for
the events.  We hope that providing this option makes things a bit
easier for them.

The current plan is to use two Google offices, one in eastern Canada
(so as to be in a nearby time zone) and one in Europe (which seems
to have the highest percentage of affected participants).  These
offices will be staffed by volunteers and will provide local conference
room facilities, wireless network, and snacks.

We have some flexibility on which offices to use, and we'd be happy
to take email from potential remote participants on their preferences.
Alternatively, we've also set up a form at

  https://goo.gl/forms/pbuaDdhS2xyKpcps1

to collect this data, if people prefer not to use email for this.  (The
form does not require a Google login to complete).  

We understand, of course, that situation is fluid, but given the need
to coordinate with local volunteers, it would be great to have an 
early insight into who many of the affected people might use this
option.  If you could share this option with the community so we
can get that insight, we'd appreciate it.

thanks,

Ted Hardie
Warren Kumari


From nobody Fri Feb  3 14:03:23 2017
Return-Path: <llynch@civil-tongue.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AADF1294CD; Fri,  3 Feb 2017 14:03:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 O8a1L1F9DTHz; Fri,  3 Feb 2017 14:03:20 -0800 (PST)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1::42]) by ietfa.amsl.com (Postfix) with ESMTP id 7845E1299AB; Fri,  3 Feb 2017 14:03:19 -0800 (PST)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1:0:0:0:0:42]) (authenticated bits=0) by hans.rg.net (8.15.2/8.15.2) with ESMTPSA id v13M3Fd0020659 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Feb 2017 22:03:16 GMT (envelope-from llynch@civil-tongue.net)
Date: Fri, 3 Feb 2017 22:03:15 +0000 (UTC)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hans.rg.net
To: Alissa Cooper <alissa@cooperw.in>
Subject: Re: NomCom 2016-2017 - Announcement of IESG selections
In-Reply-To: <9992FFFF-F17A-4712-AE4C-2354CDE3C287@cooperw.in>
Message-ID: <alpine.BSF.2.20.1702032153220.7799@hans.rg.net>
References: <148587974445.2515.18166506880398063252.idtracker@ietfa.amsl.com> <9992FFFF-F17A-4712-AE4C-2354CDE3C287@cooperw.in>
User-Agent: Alpine 2.20 (BSF 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lI04timbHSqHhuNZbUQOe0kF3Wk>
Cc: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 22:03:21 -0000

On Fri, 3 Feb 2017, Alissa Cooper wrote:

> In light of this announcement, I will be resigning as ART AD effective 
> during IETF 98 when I assume the Gen AD/IETF Chair position. I am 
> willing to overlap with an incoming ART AD should the vacancy be filled 
> prior to then.

Thanks for this confirmation Alissa. The NomCom will convene this next 
week to begin the process to appoint a replacement for the up-coming 
vacancy.

We will post an open call for nominations after our meeting and we believe 
that we can meet the conditions as outlined in RFC 7437 Section 3.5. We 
will also post our six week calendar allowing time for nominations, 
feedback, interviews, selection, and confirmation.

Best -

Lucy Lynch
NomCom Chair 2016-2017


> Alissa
>
>> On Jan 31, 2017, at 11:22 AM, NomCom Chair 2016 <nomcom-chair-2016@ietf.org> wrote:
>>
>> As chair of the 2016-2017 NomCom, it is my pleasure to announce the
>> selection of IESG members to serve in the 2017-2019 cycle.
>>
>> The selected candidates are:
>>
>> Alissa Cooper, Chair
>> Ben Campbell, ART AD
>> Terry Manderson, INT AD
>> Warren Kumari, OPS AD
>> Alvaro Retana, RTG AD
>> Deborah Brungard, RTG AD
>> Eric Rescorla, SEC AD
>> Spencer Dawkins, TSV AD
>>
>> The resulting IESG will consist of:
>>
>> Alissa Cooper, Cisco, Chair
>> Ben Campbell, Oracle, ART AD
>> Alexey Melnikov, Isode, ART AD
>> Suresh Krishnan, Ericsson, Internet AD
>> Terry Manderson, ICANN, Internet AD
>> Benoit Claise, Cisco, Management AD (O&M AD)
>> Warren Kumari, Google, Operations AD (O&M AD)
>> Alia Atlas, Juniper Networks, Routing AD
>> Deborah Brungard, AT&T, Routing AD
>> Alvaro Retana, Cisco, Routing AD
>> Kathleen Moriarty, EMC Corporation, Security AD
>> Eric Rescorla, Mozilla, SEC AD
>> Mirja Kuhlewind, ETH Zurich, Transport AD
>> Spencer Dawkins, Wonder Hamster Internetworking, Transport AD
>>
>> The Nomcom of one year ago noted that the IESG would have 3
>> members from Cisco. This year's IESG makes no changes in this regard.
>> We have had no reports that this has caused any issues over the past
>> year, and hope that this continues  to remain true in the coming year.
>>
>> The IAB and IAOC selections will be announced after completing the
>> confirmation procedure.
>>
>> The Nomcom wishes to thank everyone who volunteered, everyone who
>> nominated, and everyone who provided feedback to the process. Your
>> input was vital in coming to this set of decisions.
>>
>> Lucy Lynch
>> Nomcom chair 2016-2016
>> llynch @ civil-tongue.net
>>
>
>
>


From nobody Fri Feb  3 14:09:48 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5951299D3; Fri,  3 Feb 2017 14:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 kkWvPXxF8TZQ; Fri,  3 Feb 2017 14:09:40 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 9AF111299D1; Fri,  3 Feb 2017 14:09:40 -0800 (PST)
X-AuditID: c6180641-c53ff70000000a06-a4-5894b94c9e70
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id 43.03.02566.C49B4985; Fri,  3 Feb 2017 18:09:35 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0319.002; Fri, 3 Feb 2017 17:09:34 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AQHSfkqC7kxOxt1H90G9KbZhJyAgxKFYAkkAgAApWYA=
Date: Fri, 3 Feb 2017 22:09:33 +0000
Message-ID: <7CB1AF8D-F98B-4C8B-AE03-EE936D547DC5@ericsson.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com>
In-Reply-To: <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.12]
Content-Type: multipart/signed; boundary="Apple-Mail=_E659B882-2261-45B4-BAD6-2C86F5358052"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHIsWRmVeSWpSXmKPExsUyuXRPgq7/zikRBov3WVjsnjKNzWL3oh5W i2cb57NYvDz7nslictsKNosrV1uYLdbvfsTkwO4x5fdGVo+Dxz4yeixZ8pPJY9HUZ4weXy5/ ZgtgjeKySUnNySxLLdK3S+DK6JjylrngQXJFwyS5Bsa1UV2MnBwSAiYSV7+9Ze1i5OIQEljP KHH0ai8rSEJIYBmjxI1uHxCbDahow87PTCC2iICOxJS5O5lBGpgFupkkWp7+AesWFmhjlJh6 4SkjiCMi0M4osa7lB1CGA8ixknh9E6ybRUBF4vf67YwgNq+AvcTqs++ZIVZPZpZ4vnMB2GpO AReJVS8eMYPYjAJiEt9PrQFrZhYQl7j1ZD4TxN0iEg8vnmaDsEUlXj7+xwphK0nMeX0N6rwp QEe8uscMsU1Q4uTMJywTGEVmIZk1C1ndLCR1EEVJEjfarjBC2NoSyxa+BqrhALJ1JCYvRBOG sD+eP8IEYZtKvD76EarGWmLGr4NsELaixJTuh+wLGLlXMXKUFhfk5KYbGW5iBMb8MQk2xx2M e3s9DzEKcDAq8fBuSJoSIcSaWFZcmXuIUQWo9dGG1RcYpVjy8vNSlUR4C78DpXlTEiurUovy 44tKc1KLDzFKc7AoifNeD7kfLiSQnliSmp2aWpBaBJNl4uCUamBcNOXHBsV7upZT+oxqvx7P C5DXSTp8eZLHY8udcnxT31WVTd5sF+6sM0uhrmy/5apA9wb7Rbt/zLrKvzZGOy/OkkekXfb9 /LAZqU6tP6UTNocpzV59K1I56K7XmoqaQ50l6Y+MtCdKTn37MTZm1sZdJtu+MnIFHTgcXzn5 2paabaZfM+5umtauxFKckWioxVxUnAgANuOLlgEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TFF62BYnxm_m2dcVaI83U7-A9tc>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Stefano Previdi <sprevidi@cisco.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 22:09:43 -0000

--Apple-Mail=_E659B882-2261-45B4-BAD6-2C86F5358052
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A79F5ECD-FBCA-4615-B6AB-5FB16F600C1F"


--Apple-Mail=_A79F5ECD-FBCA-4615-B6AB-5FB16F600C1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Pete,

> On Feb 3, 2017, at 2:41 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
>=20
> On 3 Feb 2017, at 12:22, otroan@employees.org =
<mailto:otroan@employees.org> wrote:
>=20
> are we re-spinning the debate on a WG-agreed text ?
>=20
> <tp>
>=20
> Yes, and I am sure that that is exactly what is intended.
>=20
> Then let's encourage people outside of 6man, with other points of =
view, and other arguments to come forward.
>=20
> A re-run of the discussions already had in 6man with the same =
arguments and the same participants doesn't seem useful.
>=20
> For a brief (sic) overview take a look at 672 messages already on the =
topic:
> =
https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&f_list=3Dip=
v6 =
<https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&f_list=3Di=
pv6>
> O.
>=20
> Might I, as a relatively disinterested observer of this discussion, =
humbly[1] suggest that pointing the IETF list to a 672-message thread is =
not a way to avoid re-running the discussion "with the same arguments =
and the same participants". It would be significantly more useful if =
you, as chair and the caller of the (apparently rough) consensus =
summarized the issue, explained what you took the objection to be, and =
told us what you saw as the replies to those objections that convinced =
you that WG had properly considered the issue and that there was (rough) =
WG consensus to go with the text you ended up with. Then folks who think =
you called it wrong can explain the essential point they think you =
missed when you made that call. Having the rest of us re-create your =
evaluation of the consensus by reading 672 messages is, at best, =
inefficient.
>=20
>=20

Thanks for the suggestion. Ole will be working on summarizing the WG =
discussion. I also want to point out the IESG statement on IETF Last =
Calls at https://www.ietf.org/iesg/statement/last-call-guidance.html =
<https://www.ietf.org/iesg/statement/last-call-guidance.html> which =
states

"If substantive discussion of a technical comment is needed, it is often =
appropriate to move that discussion to the WG list, once the comment has =
been made on the IETF list. "

I think the comment(s) under question fall(s) under that category. For =
this reason, I would like to loop the 6man WG mailing list into this =
discussion going forward.

Regards
Suresh=

--Apple-Mail=_A79F5ECD-FBCA-4615-B6AB-5FB16F600C1F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Hi Pete,<div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Feb 3, 2017, at 2:41 PM, =
Pete Resnick &lt;<a href=3D"mailto:presnick@qti.qualcomm.com" =
class=3D"">presnick@qti.qualcomm.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">


<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8" =
class=3D"">

<div class=3D"">
<div style=3D"font-family:sans-serif" class=3D""><div =
style=3D"white-space:normal" class=3D""><p dir=3D"auto" class=3D"">On 3 =
Feb 2017, at 12:22, <a href=3D"mailto:otroan@employees.org" =
style=3D"color:#3983C4" class=3D"">otroan@employees.org</a> wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 =
5px; padding-left:5px" class=3D"">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 =
5px; padding-left:5px; border-left-color:#999" class=3D""><p dir=3D"auto" =
class=3D"">are we re-spinning the debate on a WG-agreed text ?</p><p =
dir=3D"auto" class=3D"">&lt;tp&gt;</p><p dir=3D"auto" class=3D"">Yes, =
and I am sure that that is exactly what is intended.</p>
</blockquote><p dir=3D"auto" class=3D"">Then let's encourage people =
outside of 6man, with other points of view, and other arguments to come =
forward.</p><p dir=3D"auto" class=3D"">A re-run of the discussions =
already had in 6man with the same arguments and the same participants =
doesn't seem useful.</p><p dir=3D"auto" class=3D"">For a brief (sic) =
overview take a look at 672 messages already on the topic:<br class=3D"">
<a =
href=3D"https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&amp=
;f_list=3Dipv6" style=3D"color:#777" =
class=3D"">https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&=
amp;f_list=3Dipv6</a></p><p dir=3D"auto" class=3D"">O.</p>
</blockquote><p dir=3D"auto" class=3D"">Might I, as a relatively =
disinterested observer of this discussion, humbly[1] suggest that =
pointing the IETF list to a 672-message thread is not a way to avoid =
re-running the discussion "with the same arguments and the same =
participants". It would be significantly more useful if you, as chair =
and the caller of the (apparently rough) consensus summarized the issue, =
explained what you took the objection to be, and told us what you saw as =
the replies to those objections that convinced you that WG had properly =
considered the issue and that there was (rough) WG consensus to go with =
the text you ended up with. Then folks who think you called it wrong can =
explain the essential point they think you missed when you made that =
call. Having the rest of us re-create your evaluation of the consensus =
by reading 672 messages is, at best, inefficient.</p><div class=3D""><br =
class=3D""></div></div></div></div></div></blockquote><div><br =
class=3D""></div>Thanks for the suggestion. Ole will be working on =
summarizing the WG discussion. I also want to point out the IESG =
statement on IETF Last Calls at&nbsp;<a =
href=3D"https://www.ietf.org/iesg/statement/last-call-guidance.html" =
class=3D"">https://www.ietf.org/iesg/statement/last-call-guidance.html</a>=
&nbsp;which states</div><div><br class=3D""></div><div><span =
style=3D"font-family: Verdana, Arial, Helvetica, sans-serif; font-size: =
12.666666984558105px; background-color: rgb(255, 255, 255);" =
class=3D"">"If substantive discussion of a technical comment is needed, =
it is often appropriate to move that discussion to the WG list, once the =
comment has been made on the IETF list. "</span></div><div><br =
class=3D""></div></div><div>I think the comment(s) under question =
fall(s) under that category. For this reason, I would like to loop the =
6man WG mailing list into this discussion going forward.</div><div><br =
class=3D""></div><div>Regards</div><div>Suresh</div></body></html>=

--Apple-Mail=_A79F5ECD-FBCA-4615-B6AB-5FB16F600C1F--

--Apple-Mail=_E659B882-2261-45B4-BAD6-2C86F5358052
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjAzMjIwOTM0WjAjBgkqhkiG9w0B
CQQxFgQUzoDQTZM2PZgfV1NMyRS356oKuKcwXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQBRYFQ/lT22w3xb2noaDIrtGdiBMKVs/82clHcUnw+UyAfiG0ypnM9Xp3QlRRL3
DRzmTL7DAocyDacFMVe6WDNJY3xBffR7n8mvlowI2F3J9Tf+IRejPRVbjNzKQ2pcDM0p7GyWCuJV
P7/IactLNPwTiRG7tCRAnWM/aIvqitx5dSx7ko8hrm10p9wbKaQvSUa+d/KnVjJ7P+kk5IEBLBGV
Q3zTso3DFelm3gdpm+qYGhU2xia3HXWFFRSKWNnmWgRBZHkFFBx5pARSfPPdf8D/y4RB582ms7mF
0mfEBD5TS1mRBWpUOvXubZeXbDrAPCRxL/yiLqj5BzZoeM81YxSzAAAAAAAA

--Apple-Mail=_E659B882-2261-45B4-BAD6-2C86F5358052--


From nobody Fri Feb  3 15:08:04 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 490ED129A38; Fri,  3 Feb 2017 15:08:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.198
X-Spam-Level: 
X-Spam-Status: No, score=-10.198 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, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vFuY_hLHPha9; Fri,  3 Feb 2017 15:08:00 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 619A5129A30; Fri,  3 Feb 2017 15:08:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486163280; x=1517699280; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=riJQUa3uTwrax9dJdDnZqykKPr5rpBDdIhdUUkVv6Ig=; b=rBlcAoBW3WFFFNF6BRuR1+BxyfrDCET/XveRJc8mSV7MnzJdYNPi8RPv ZYgpLWGc/l+F2C3L6DJVlGuTRQjpmeaWC+VDKIpx/boyUcqtITc3MvUmi IXk3JzKLFnghqrmEnUjJ6b2E7j/P8K4k4np9hzdADhnw5bcMRu4f/sZ2f Y=;
X-IronPort-AV: E=Sophos;i="5.33,331,1477983600";  d="scan'208,217";a="260211534"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by wolverine01.qualcomm.com with ESMTP; 03 Feb 2017 15:07:59 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8428"; a="893934287"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Feb 2017 15:07:59 -0800
Received: from [10.64.125.251] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 3 Feb 2017 15:07:58 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Suresh Krishnan <suresh.krishnan@ericsson.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 3 Feb 2017 17:07:56 -0600
Message-ID: <FB4982B2-EA8A-48BA-B6F0-140044A4B849@qti.qualcomm.com>
In-Reply-To: <7CB1AF8D-F98B-4C8B-AE03-EE936D547DC5@ericsson.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <7CB1AF8D-F98B-4C8B-AE03-EE936D547DC5@ericsson.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_4ECBD3BD-2A48-411A-AC43-FF37BBE6AB58_="
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7kECMpLB8B9_1wMD9mucur232DU>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Stefano Previdi <sprevidi@cisco.com>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 23:08:02 -0000

--=_MailMate_4ECBD3BD-2A48-411A-AC43-FF37BBE6AB58_=
Content-Type: text/plain; format=flowed

On 3 Feb 2017, at 16:09, Suresh Krishnan wrote:

> Hi Pete,
>
>> On Feb 3, 2017, at 2:41 PM, Pete Resnick <presnick@qti.qualcomm.com> 
>> wrote:
>>
>> On 3 Feb 2017, at 12:22, otroan@employees.org 
>> <mailto:otroan@employees.org> wrote:
>>
>> are we re-spinning the debate on a WG-agreed text ?
>>
>> <tp>
>>
>> Yes, and I am sure that that is exactly what is intended.
>>
>> Then let's encourage people outside of 6man, with other points of 
>> view, and other arguments to come forward.
>>
>> A re-run of the discussions already had in 6man with the same 
>> arguments and the same participants doesn't seem useful.
>>
>> For a brief (sic) overview take a look at 672 messages already on the 
>> topic:
>> https://mailarchive.ietf.org/arch/search/?q=header+insertion&f_list=ipv6 
>> <https://mailarchive.ietf.org/arch/search/?q=header+insertion&f_list=ipv6>
>> O.
>>
>> Might I, as a relatively disinterested observer of this discussion, 
>> humbly[1] suggest that pointing the IETF list to a 672-message thread 
>> is not a way to avoid re-running the discussion "with the same 
>> arguments and the same participants". It would be significantly more 
>> useful if you, as chair and the caller of the (apparently rough) 
>> consensus summarized the issue, explained what you took the objection 
>> to be, and told us what you saw as the replies to those objections 
>> that convinced you that WG had properly considered the issue and that 
>> there was (rough) WG consensus to go with the text you ended up with. 
>> Then folks who think you called it wrong can explain the essential 
>> point they think you missed when you made that call. Having the rest 
>> of us re-create your evaluation of the consensus by reading 672 
>> messages is, at best, inefficient.
>>
>>
>
> Thanks for the suggestion. Ole will be working on summarizing the WG 
> discussion.

Excellent. Thanks Ole.

> I also want to point out the IESG statement on IETF Last Calls at 
> https://www.ietf.org/iesg/statement/last-call-guidance.html 
> <https://www.ietf.org/iesg/statement/last-call-guidance.html> which 
> states
>
> "If substantive discussion of a technical comment is needed, it is 
> often appropriate to move that discussion to the WG list, once the 
> comment has been made on the IETF list. "
>
> I think the comment(s) under question fall(s) under that category. For 
> this reason, I would like to loop the 6man WG mailing list into this 
> discussion going forward.

If it's a *new* substantive technical comment, I absolutely agree, that 
should go back to the WG list. However, if this is an old topic that the 
WG has already come to a conclusion on, bringing it back to the list is 
not useful unless something has changed; that just becomes a "pile on" 
session. That's why I suggested Ole summarize the issue first, and that 
should be copied to the IETF list. That way we can see whether the issue 
is "The WG missed this important aspect of the issue" (which should go 
back to the WG to discuss once it's properly formulated) or "The chair 
misevaluated the consensus" (which should probably be handled by you and 
the chair). Either way, we agree that a protracted rehash of the topic 
on the IETF list is not the right choice.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_4ECBD3BD-2A48-411A-AC43-FF37BBE6AB58_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 3 Feb 2017, at 16:09, Suresh Krishnan wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i Pete,<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">On Feb 3, 2=
017, at 2:41 PM, Pete Resnick &lt;presnick@qti.qualcomm.com&gt; wrote:<br=
>
<br>
On 3 Feb 2017, at 12:22, otroan@employees.org &lt;<a href=3D"mailto:otroa=
n@employees.org" style=3D"color:#999">mailto:otroan@employees.org</a>&gt;=
 wrote:<br>
<br>
are we re-spinning the debate on a WG-agreed text ?<br>
<br>
&lt;tp&gt;<br>
<br>
Yes, and I am sure that that is exactly what is intended.<br>
<br>
Then let's encourage people outside of 6man, with other points of view, a=
nd other arguments to come forward.<br>
<br>
A re-run of the discussions already had in 6man with the same arguments a=
nd the same participants doesn't seem useful.<br>
<br>
For a brief (sic) overview take a look at 672 messages already on the top=
ic:<br>
<a href=3D"https://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion=
&amp;f_list=3Dipv6" style=3D"color:#999">https://mailarchive.ietf.org/arc=
h/search/?q=3Dheader+insertion&amp;f_list=3Dipv6</a> &lt;<a href=3D"https=
://mailarchive.ietf.org/arch/search/?q=3Dheader+insertion&amp;f_list=3Dip=
v6" style=3D"color:#999">https://mailarchive.ietf.org/arch/search/?q=3Dhe=
ader+insertion&amp;f_list=3Dipv6</a>&gt;<br>
O.<br>
<br>
Might I, as a relatively disinterested observer of this discussion, humbl=
y[1] suggest that pointing the IETF list to a 672-message thread is not a=
 way to avoid re-running the discussion "with the same arguments and the =
same participants". It would be significantly more useful if you, as chai=
r and the caller of the (apparently rough) consensus summarized the issue=
, explained what you took the objection to be, and told us what you saw a=
s the replies to those objections that convinced you that WG had properly=
 considered the issue and that there was (rough) WG consensus to go with =
the text you ended up with. Then folks who think you called it wrong can =
explain the essential point they think you missed when you made that call=
=2E Having the rest of us re-create your evaluation of the consensus by r=
eading 672 messages is, at best, inefficient.<br>
<br>
</p>
</blockquote><p dir=3D"auto">Thanks for the suggestion. Ole will be worki=
ng on summarizing the WG discussion.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Excellent. Thanks Ole.</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">I=
 also want to point out the IESG statement on IETF Last Calls at <a href=3D=
"https://www.ietf.org/iesg/statement/last-call-guidance.html" style=3D"co=
lor:#777">https://www.ietf.org/iesg/statement/last-call-guidance.html</a>=
 &lt;<a href=3D"https://www.ietf.org/iesg/statement/last-call-guidance.ht=
ml" style=3D"color:#777">https://www.ietf.org/iesg/statement/last-call-gu=
idance.html</a>&gt; which states<br>
<br>
"If substantive discussion of a technical comment is needed, it is often =
appropriate to move that discussion to the WG list, once the comment has =
been made on the IETF list. "<br>
<br>
I think the comment(s) under question fall(s) under that category. For th=
is reason, I would like to loop the 6man WG mailing list into this discus=
sion going forward.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">If it's a <em>new</em> substantive technical comment, I a=
bsolutely agree, that should go back to the WG list. However, if this is =
an old topic that the WG has already come to a conclusion on, bringing it=
 back to the list is not useful unless something has changed; that just b=
ecomes a "pile on" session. That's why I suggested Ole summarize the issu=
e first, and that should be copied to the IETF list. That way we can see =
whether the issue is "The WG missed this important aspect of the issue" (=
which should go back to the WG to discuss once it's properly formulated) =
or "The chair misevaluated the consensus" (which should probably be handl=
ed by you and the chair). Either way, we agree that a protracted rehash o=
f the topic on the IETF list is not the right choice.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_4ECBD3BD-2A48-411A-AC43-FF37BBE6AB58_=--


From nobody Fri Feb  3 15:22:22 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0EB3129980; Fri,  3 Feb 2017 15:22:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
Date: Fri, 03 Feb 2017 15:22:19 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CPNZluVav5kr6txm10kDFiUThyc>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2017 23:22:20 -0000

Reviewer: Pete Resnick
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ccamp-flexible-grid-ospf-ext-07
Reviewer: Pete Resnick
Review Date: 2017-02-03
IETF LC End Date: 2017-01-31
IESG Telechat date: 2017-02-16

Summary:

Looks good from a non-expert point of view. A few things I found
ambiguous or confusing that should be easily clarified, but nothing
that should stop the document from moving forward.

Major issues:

None.

Minor issues:

4.1.1:

The figure is a bit confusing: There might not exist a "Max Slot Width
at Priority 7" if bit 7 is clear in the Priority field, correct?
Perhaps it would be better to just show that as "..." or "Max Slot
Width at Priority n". The thing is, it might only be a single value,
followed by the padding, so having the second value in there might be
misleading. (Perhaps similar constructs are used in other MPLS docs
and people will understand. But it took me a while to figure it out.)

The discussion of Priority was very confusing for me. In the third
sentence, do you mean, "A bit is set (1) corresponding to each
priority represented in the sub-TLV, and clear (0) for each priority
not represented in the sub-TLV"? I don't understand the MUST/MUST NOT
as you had it. And I don't understand the last sentence at all. Are
you trying to say, "The leftmost bit (priority level 0) MUST be set,
and priority level 0 MUST be advertised in the sub-TLV."? Otherwise, I
don't get it.

I don't understand the MAY in the last sentence. Does that mean that I
MAY also set it to the highest possible nominal central frequency
supported by the link? I don't understand what that sentence is trying
to tell me.

Nits/editorial comments: 

3, last paragraph:

OLD
   That is, the additional information
NEW
   That is, this section defines the additional information
END

As it is, it is ungrammatical.

3.1:

   On a DWDM link, the allocated or in-use frequency slots must not 
   overlap with each other.

I think perhaps it's clearer to simply say "frequency slots do not
overlap each other", assuming that's what you mean. I don't think
you're trying to say something normative there; it's just a fact. But
people often read "must" (whether it's uppercased or not) to be
imposing a requirement. I don't think that's what you're doing here,
so better to make it clear. (As you may know, I'm not a fan of overuse
of MUSTs and SHOULDs, but I do like it when documents are clear.)

As an opposite example:

   Hence, in order to clearly show which LSPs can be supported and
what 
   frequency slots are unavailable, the available frequency ranges
MUST 
   be advertised by the routing protocol for the flexi-grid DWDM
links.  
   A set of non-overlapping available frequency ranges MUST be 
   disseminated in order to allow efficient resource management of 
   flexi-grid DWDM links and RSA procedures which are described in 
   Section 4.8 of [RFC7698]. 

Those MUSTs look weird to me. I think instead of "MUST be" you mean
"are", since it doesn't look like an implementation really has a
choice here.

3.2:

   Hence, in order to support all possible applications and 
   implementations the following information should be advertised for
a 
   flexi-grid DWDM link:
   
Is that "should" in there meant to be normative? That is, do bad
things happen if I don't advertise one of those items? Or do you just
mean "the following information is advertised..."? 

3.3:

   For this reason, the available frequency slot/ranges need to be 
   advertised for a flexi-grid DWDM link instead of the specific 
   "wavelengths" points that are sufficient for a fixed-grid link.  

Where you say "needs to be advertised", are you making a normative
statement, or are you just describing, in which case "are advertised"
would be clearer?

(By the way: Typo in the following sentence. Change "thus" to
"this".)

4.1:

   When Switching Capability and Encoding fields are set to values as

   stated above, the Interface Switching Capability Descriptor MUST be

   interpreted as in [RFC4203] with the optional inclusion of one or 
   more Switching Capability Specific Information sub-TLVs.  

Same question as earlier about "MUST be" vs. "is".

4.1.1:

   The technology specific part of the Flexi-grid ISCD should include


Same question as earlier about "should include" vs. "includes".

   Length (16 bits): The length of the value field of this sub-TLV. 

Perhaps obvious to an MPLS person, but is this the length in bits or
bytes, and does it include the Type and Length fields?

   Max Slot Width
   
I think the first "MUST be" should be "is". In the rest, I think you
mean that if bits 0, 3, and 6 are set in Priority, then there should
be 3 Max Slot Width entries, and the first one is the max slot width
for priority level 0, the second one is the width for priority level
3, and the last is the priority slot width for priority level 7. Do I
understand that correctly? If so, it might be useful to say that. And
the last sentence would be clearer if it said, "The number of Max Slot
Width fields MUST be identical to the number of bits set in the
Priority field." Saying it with the MUST NOT confused me.

   Unreserved Padding

Shouldn't this say, "MUST be set to 0 and MUST be ignored on
receipt"?

   The Reserved field

Why is this a "SHOULD be ignored on receipt" whereas the Padding Bits
"MUST be ignored"? (And I think it would be better to move this up in
order so it's right after Priority.)

4.2:

In Switching Cap, you say "MUST be consistent with" and in Encoding,
you say "must be consistent with". Either make them both "MUST be", or
just strike the words and simply make it, "consistent with".



From nobody Sat Feb  4 00:32:43 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56C83129464; Sat,  4 Feb 2017 00:32:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zonjCVekCSzr; Sat,  4 Feb 2017 00:32:39 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 96AE7129451; Sat,  4 Feb 2017 00:32:39 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 04 Feb 2017 08:32:39 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id BF074D788D; Sat,  4 Feb 2017 00:32:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=3iZcSrtPjtq/NhMnB39Oe4WcN7M=; b= M7jx0EOgq3/5CaOVdQw0syCtbJOJYk2xFy/FYFq18JpcMNr2cuVqNhp3S2lRIPb8 o97tDnrr4QTih07t8IzodyezmWMxfL3CXNs4syAw9nrxSUPaM6cC+D2bZyj4Ad8a /UPCqSkSVqtmr3Hgh615n6fbZ+HycKxzQ3ejRsNDfYU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=eWnjXwam4DPu/yyanzpdeUD AUUnDiPVgNCiMRCOYsjFJd5eCcRcwdSpmtHVm/mA4wJ1A2kxONNcyN3nTVeISuQn Q4TeeTIOy8v2j5l/hx2VdM2/bv+qzVRFFrleZjQ33D6F6B2JzI46KWURI6PkgYmO VNd/O8/Zx5sE5davtj78=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 61E03D788B; Sat,  4 Feb 2017 00:32:38 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 25D3A83DE987; Sat,  4 Feb 2017 09:32:38 +0100 (CET)
From: otroan@employees.org
Message-Id: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7551FFB2-5870-4FE9-A24F-602551AEAF8B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Sat, 4 Feb 2017 09:32:37 +0100
In-Reply-To: <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MJexpTisUTSN2XrkkYVVLPJrjFM>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 08:32:41 -0000

--Apple-Mail=_7551FFB2-5870-4FE9-A24F-602551AEAF8B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thank you Pete! You are of course right.

Let me try to provide some background of the issue.

The contentious text is the following paragraph from 2460:

  With one exception, extension headers are not examined or processed
  by any node along a packet's delivery path, until the packet reaches
  the node (or each of the set of nodes, in the case of multicast)
  identified in the Destination Address field of the IPv6 header.

Essentially the question is:
- Does the IPv6 architecture permit insertion of extension headers =
and/or header options by a node along the packet's delivery path?

This question came up triggered by discussions around some recent =
proposals:
- draft-ietf-conex-destopt,
- RFC4782 (does header deletion)
- draft-ietf-6man-segment-routing-header
- draft-brockners-inband-oam-transport

The IP architecture (IPv4 and IPv6) supports _modifying_ IP options in =
flight, but it is unclear if it could permit changing the IP datagram's =
size.
Increasing a packets size in flight would break PMTUD (RFC1981), AH, and =
might results in other ICMP error messages being sent to an unsuspecting =
source.

There were three main positions argued in the working group.

1) Ban header insertion outright.
2) Describe the problems with header insertion.
3) No changes to RFC2460 text.

Permitting header insertion in the sense of specifying how header =
insertion could possibly work is of course outside the scope of =
advancing RFC2460.

The chairs tried various approaches to find a consensus without luck. =
The approach finally chosen was a poll between the three options. And =
the (rough) consensus was based on the data from the poll.

Excerpt from the shepherds writeup:

A working group last call for moving this and the other two documents to =
Internet Standard was started on 30 May 2016. Reviews were also =
requested. Issues found during the last call and reviews were entered =
into the 6MAN ticket system. These are now closed. The biggest issue =
raised was how to handle the issue of Extension Header insertion in this =
document. After many discussion on the mailing list and face to face =
meeting, there wasn=E2=80=99t a clear consensus. The chairs conducted an =
online survey that provided three choices: Ban header insertion, =
describe the problems with header insertion, or say nothing. The result =
of the survey was to describe the solution. The results and methodology =
used to evaluate the results can be seen at: =
https://mailarchive.ietf.org/arch/msg/ipv6/_gG2foiugk5B7w3TpnPvBbjHDzs =
This was discussed at the 6MAN session at IETF97 and on the mailing list =
after the meeting. The chairs believe there is a consensus to go forward =
with the text that is in draft-ietf-6man-rfc2460bis-08.

The summary given to the working group calling for the poll:
=
https://mailarchive.ietf.org/arch/msg/ipv6/AtY92TpJ3vvmiidzcPkJdXKZQIA/?qi=
d=3D84de5e109c8f8f255d03c4c98ff3e50c

Best regards,
Ole, 6man co-chair

--Apple-Mail=_7551FFB2-5870-4FE9-A24F-602551AEAF8B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYlZGlAAoJEL7aWKiYQt92YHIP/jz9Z/iAA8d444m/uVi6Ta+U
pBgbWJbCgLkQWks8xWaB+BC2lnzx3BB6YQlWCYzqN1on8Te4ZivuIOSlkYaS9fLl
QaySI2NNrFRut9/7lWxdImbPWFEubNGG2q/ZxdaY3DRS1VinASloZreHCzsqv/PB
AdMybaDq1Xw8/fSVfIHRDbzLBtlU1ybwtIvlv/yZ66Z8hG6LF0FteaqcUwtoQb6i
uGmfTqzGWX3m7D+IIIFm1/5B/bqTNhH7aVbCTN+ZtVBhMmXeOgFUEvK33SxfXZAF
G4VbK+xx1NnUaiiDrZ4hWjs4jGnZR8vL0HW7FXOf70m2+XstT1kOhSqpbz24tVJL
/RyrsABeVbKNUqFRo6D2usUeF8KjRATA90WFN04AGTlZiNF2Pb+NErfP8K74WsEm
jq0BcUq+5Tk3LQZYJ+m+hstUNekxS+g/AExrEeVPN6iPUPLhX0K4/WTNcDSOqCby
ntSxiT9NnlF9T2y9UhIg3lmOmzw3N5Yn/hf4mQ16H9rwACs+7j1VoewJn+Ra7+6C
fRgmL0q+xJNls0yoJ27hK71s1XMCs61FYZtArq8faEd5nPnSNN9A+Zt7SfjTEmWR
dnh+jBJ/Dcao4WOmqGpGTtaCk0vu0egfvdeUS5ua4rZvdED6ugZy89KuShvU58i2
FYDalwhVqinIMAeNeQbQ
=KWhE
-----END PGP SIGNATURE-----

--Apple-Mail=_7551FFB2-5870-4FE9-A24F-602551AEAF8B--


From nobody Sat Feb  4 01:10:31 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27AE31294F8; Sat,  4 Feb 2017 01:10: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 QOjeQbid17Vz; Sat,  4 Feb 2017 01:10:26 -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 240E31293DF; Sat,  4 Feb 2017 01:10:26 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 5459083656; Sat,  4 Feb 2017 10:10:20 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, Pete Resnick <presnick@qti.qualcomm.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com>
Date: Sat, 4 Feb 2017 06:04:46 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1
MIME-Version: 1.0
In-Reply-To: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8xUwRLMswum8c_PSHXvULLbrI_o>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 09:10:28 -0000

On 02/04/2017 05:32 AM, otroan@employees.org wrote:
> Thank you Pete! You are of course right.
> 
> Let me try to provide some background of the issue.
> 
> The contentious text is the following paragraph from 2460:
> 
> With one exception, extension headers are not examined or processed 
> by any node along a packet's delivery path, until the packet reaches 
> the node (or each of the set of nodes, in the case of multicast) 
> identified in the Destination Address field of the IPv6 header.
> 
> Essentially the question is: - Does the IPv6 architecture permit
> insertion of extension headers and/or header options by a node along
> the packet's delivery path?
> 
> This question came up triggered by discussions around some recent
> proposals: - draft-ietf-conex-destopt, - RFC4782 (does header
> deletion) - draft-ietf-6man-segment-routing-header -
> draft-brockners-inband-oam-transport
> 
> The IP architecture (IPv4 and IPv6) supports _modifying_ IP options
> in flight, but it is unclear if it could permit changing the IP
> datagram's size. 

The only case that can be made for that is that the spec doesn't say
"insertion of EHs is forbidden" -- but then, if you were to have to
write a spec explicitly noting everything that is forbidden, you
wouldn't be able to achive that in your lifetime.

Everyone has agreed (including the authors of RFC2460) that EH insertion
has never been allowed.



> Increasing a packets size in flight would break
> PMTUD (RFC1981), AH, and might results in other ICMP error messages
> being sent to an unsuspecting source.
> 
> There were three main positions argued in the working group.
> 
> 1) Ban header insertion outright. 2) Describe the problems with
> header insertion. 3) No changes to RFC2460 text.
> 
> Permitting header insertion in the sense of specifying how header
> insertion could possibly work is of course outside the scope of
> advancing RFC2460.

Explicitly allowing EH insertion would most likely be out of scope, too:
It completely changes a very basic aspect of IPv6.

FWIW, I think that publishing a spec with what some have considered to
be ambiguous text (subsequently leading to 600+ messages on the very
group that specifies the protocol) would be a lousy job on our side.
Either explicitly ban extension header insertion, or explicitly allow it.

Whether EH insertion is allowed (or not) seems to me like a very basic
question that the protocol spec should be able to answer -- particularly
since we're moving it to Standard.

Given that the question has been "raised", it deserves an answer in the
spec. Otherwise, when asked "Are intermediate systems allowed to mangle
with IPv6 packets as they please?", I guess we'd have to answer "We
don't know... but neither did the group that wrote the spec".

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





From nobody Sat Feb  4 03:05:17 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC94212706D; Sat,  4 Feb 2017 03:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.022
X-Spam-Level: 
X-Spam-Status: No, score=-5.022 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6UedtKOjVjeB; Sat,  4 Feb 2017 03:05:05 -0800 (PST)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDEF51296B0; Sat,  4 Feb 2017 03:05:02 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.33,333,1477983600";  d="asc'?scan'208";a="173811165"
Received: from hioexcmbx08-prd.hq.netapp.com ([10.122.105.41]) by mx143-out.netapp.com with ESMTP; 04 Feb 2017 02:52:58 -0800
Received: from VMWEXCCAS12-PRD.hq.netapp.com (10.122.105.30) by hioexcmbx08-prd.hq.netapp.com (10.122.105.41) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 4 Feb 2017 02:59:57 -0800
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS12-PRD.hq.netapp.com (10.122.105.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Sat, 4 Feb 2017 02:59:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zsElXndgq2uJdJPcp72zUgjY1ZxEU8VDVFglYA8BHWY=; b=aSCBK8vej1fSipX5FdeDWNmhf6c7otNUy7qGGVV/svqMaW3cuPEwNDIfZ3+uaIYO2wkpIuytCtfVU+3p92QzrL8slhq9ymrO6Qp8pNXCy8kiPtaP39G7h5zdXNqxu4y5m08XSQ5Eq+VQaChj9v0a9kf/UTmEHBeZIdSGC48/ft8=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.874.12; Sat, 4 Feb 2017 10:59:56 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0874.025; Sat, 4 Feb 2017 10:59:56 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAAEwQCAAPFzgIAAHICAgAIpDQA=
Date: Sat, 4 Feb 2017 10:59:56 +0000
Message-ID: <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com>
In-Reply-To: <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2001:a61:31e0:2601:d5e4:7bac:a4b7:a8c5]
x-ms-office365-filtering-correlation-id: 34afb560-ba11-41f8-0581-08d44cecf463
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1153; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1153; 7:0sPFousmR2jl1iHirrbrU4onP+w8RuSilx2E4Q4S4TRIoU6NGslSw5VUFxFFFGA6hq1kGb3+8YO8Z0j7lZM6B90M01kqmwQjqQlptrdOLVOiCofQmoddB00bKVpSPIHxYZQN4ZAhVYkxDpdG7+/DOq/8a92bdbOn6+lYMViq2IyTvuy9zjdx4iaJ+75y8QyTRhDtQiqx+kezjyljAVfpBE8/knbCQWl+INeVy+uj4er4WAaTKaT4kc3eOk/dZf7CkTqMwTx5WaU0l+knjHhdQ2n2FbYHBT+tRqfbPOv6afwYNDT8Feh61lZrh6BoOS0uMUg79UuKSA1P+if+fWV4/H0GsUFNOoYKA1c2/271of5moMA8CSqqyQUZaRsVVnRywgVfr6gRZqEKtVAnOVR9CmOtEbQyy1buZaOsXdvhXk4Ol+5H8cBO/fCHnQA9jXHyexvzLMkzBwk70wye2sCVkvUs2l5b4upaXfe+JJcQybg/h01KL31D9Lq1dMNmbgjxHdPGIVjZz1hii9wj0KvRdA==
x-microsoft-antispam-prvs: <BN3PR0601MB1153E517D7A48B1C7BFA91DEA74E0@BN3PR0601MB1153.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:BN3PR0601MB1153; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1153; 
x-forefront-prvs: 020877E0CB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(377424004)(199003)(24454002)(8676002)(2950100002)(93886004)(68736007)(81156014)(25786008)(6436002)(81166006)(76176999)(6916009)(33656002)(99936001)(110136003)(57306001)(230783001)(38730400001)(5660300001)(2900100001)(2906002)(3280700002)(36756003)(50226002)(50986999)(305945005)(189998001)(77096006)(4001150100001)(8936002)(97736004)(101416001)(6486002)(7736002)(92566002)(3660700001)(6506006)(229853002)(99286003)(39060400001)(105586002)(83716003)(6512007)(86362001)(102836003)(54906002)(6116002)(122556002)(106116001)(53546003)(53936002)(6246003)(106356001)(82746002)(4326007)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1153; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_A4D80AFE-E61D-4602-A53B-6FA376969F5F"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Feb 2017 10:59:56.0643 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1153
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JEQ7Prj_uFF4lOAn6xQboIQ6Ytc>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 11:05:07 -0000

--Apple-Mail=_A4D80AFE-E61D-4602-A53B-6FA376969F5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-3, at 3:00, Fernando Gont <fgont@si6networks.com> wrote:
> My apologies: my comments were probably misleading. Certainly, this
> document is simply RFC1981 to Std, and hence recommending RFC4821 =
would
> be kind of ou of scope, here.
>=20
> That say, one might wonder to what extent, and for the general =
Internet,
> RFC1981 can be considered succesful (given the filtering of ICMP
> messages). -- i.e., at this point in time you wouldn't rely on RFC1981
> (icmp-based pmtud) for path-mtu discovery.

What Fernando said: I'm certainly not opposed to lifting this to =
Standard, but it is painting an incorrect picture - PLPMTUD is de facto =
mandatory these days, and has been for years.

Lars

--Apple-Mail=_A4D80AFE-E61D-4602-A53B-6FA376969F5F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYlbQqAAoJEFS1wwm/cMFXMnEQAM6tw7omVmxQFiqHNSQLa5Wc
9K+aWN2UjaVpneWUX+Fx4HiRFuAvj5CHiMdTq9Pt0aSekS8iy4FBWUZSC0shJJsc
gLzD9EmCANfNbjwLFsLtPtZSO4PPf0YaU+cLJv5cWD+9FECvubwEVVFZUof1pO9b
jvUG7f9f4WqqOyMRr5wEXVQrcvffmW3ovR9BAHdnh7HL47oFEBsmQ8KnlktjTAkJ
mXsIb81RrKX7tAfxi3n/vFPOLW1xmDd47nDHDa6y/Uj4gwcv7MKR+bN491eD0ffG
6P9JPH/VVTEQXCB/OueIDRh/cvNSknArIC7uGRPXB5MoRit426vie0OF3pbcTpGq
C3Zz8VeKeBnTrDVllVashBFCgCOLjtBz1Yxnh1xc5ZsDJWiURF+9S6eddi6NPbDT
BV92H7G2+tmF3NrPdrF8v1hrbJZ6hKcmDj5zlWCnVN1Vj0FSLG7HV0zPdmS2n+HM
xl5RgAfxuwrU/Ys/vepWWWC8mggMPgJMKtDDN24rvCdMROmqWnIRv8Xc0xHezIE4
6VxgjVHwV0iYFcANif/+0SESA8fc6eA2wxHzzAFYSXxhdW0vBRvfxIA7s1IiMPy2
1vz9/STeYWYPrr7VYMIaR3yoyoFX2zXwL1Pm61+XhBjNaqJbecP8y3DHavGwCQX/
QkUhM5XS1MZ8gkFV+92R
=mh9S
-----END PGP SIGNATURE-----

--Apple-Mail=_A4D80AFE-E61D-4602-A53B-6FA376969F5F--


From nobody Sat Feb  4 04:12:52 2017
Return-Path: <leifj@mnt.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9E2129A57 for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 04:12:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.7
X-Spam-Level: 
X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PC9SGXJbMbE0 for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 04:12:50 -0800 (PST)
Received: from mail-lf0-x244.google.com (mail-lf0-x244.google.com [IPv6:2a00:1450:4010:c07::244]) (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 1FB19129A58 for <ietf@ietf.org>; Sat,  4 Feb 2017 04:12:48 -0800 (PST)
Received: by mail-lf0-x244.google.com with SMTP id x1so167810lff.0 for <ietf@ietf.org>; Sat, 04 Feb 2017 04:12:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UnrTur6fLROR3ZeRl1K2mmqQmzutW2XGgjLp1AA1N3U=; b=oLWAIc+5xLHzcd93qqtFquINWTzaW3enjlfadXj74nk+dyhquVU+eSA89vMW/hN/op JJ/HdKkgKHdUEvgxiZOfUZ6fKhUbxCwvXcP2j+bpgB1Jq57dKrWesGaggUdQFIdODSg+ L22xkGOOPztp7SQQz1pNLpzxKHRoGjFgMN9kForszxu1B790oiKqLYx1JbmdLrp1Pmut KJKh3xefp5iEYjMaoT4+M4kWgp9sU5IOKo1fbcsuBhC/r6sL7XX+RBURpP6dIkXVTXXJ z4fmNVmRT1ng4kRBEfkBnefLZesOz1cmEwAa5sT7RAY8cYQoNq2Dhr0wBaXa4eXoPL90 Mcvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UnrTur6fLROR3ZeRl1K2mmqQmzutW2XGgjLp1AA1N3U=; b=IUocEkVgEhE1meqqmjgZHkvaSvBsUq07zhz/UNlpgMkieXoKjd1R+zO1rAaT13oF0m rt31sJ5IVldjUb0BjY2EMLSV1Mw71+pWC5cFzXxgKuU8E7VCZFXpDq52gbWIzTzxPkle SmZHML2ZdPRILmim7gyJ0W6G2Xkx/4jr8KYPE26f7uyLtwIFPo5jutTJNDn0LUP+NqXJ H/ZgH4GBuWnZjyCG82vKQrk53O6Aa9y1ZGDTRiaC9yQ7jJqLrvmh/3++k6se3EDpQ/Dp 0ZaRmgcDR7shXLRHRveKk/DgE/MXUK9N1p+m/H5psHX/u4vD3AwVW+Qclx2MyaTK/mMX gQFA==
X-Gm-Message-State: AIkVDXJkpHs+TQ1FXbgvANeY5DRXGbguAIoabCbA0k4uGQCeEOTLu7zFXD2HY9H8vyevXw==
X-Received: by 10.25.204.197 with SMTP id c188mr549189lfg.107.1486210366222; Sat, 04 Feb 2017 04:12:46 -0800 (PST)
Received: from [2.67.89.92] (2.67.89.92.mobile.tre.se. [2.67.89.92]) by smtp.gmail.com with ESMTPSA id h76sm8491878lfg.39.2017.02.04.04.12.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Feb 2017 04:12:45 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Remote hubs for IETF 98
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <148615538643.4137.4956475137238651973.idtracker@ietfa.amsl.com>
Date: Sat, 4 Feb 2017 13:12:44 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD7B6C65-178D-494A-BAD8-F37F00539DA0@mnt.se>
References: <148615538643.4137.4956475137238651973.idtracker@ietfa.amsl.com>
To: chair@ietf.org, ted.ietf@gmail.com, warren@kumari.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TpJWAvL1j4hlxJ9zz35DAp4RZMA>
Cc: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 12:12:51 -0000

Skickat fr=C3=A5n min iPhone

> 3 feb. 2017 kl. 21:56 skrev IETF Chair <chair@ietf.org>:
>=20
> I=E2=80=99m happy to report that Ted Hardie and Warren Kumari and Google h=
ave
> stepped up to make alternate arrangements for people who might have
> difficulty travelling due to the recent travel restrictions. Thank you!=20=

>=20

Way to go Warren & Ted!


> Please see the details below:
>=20
> -------
>=20
> Hi Jari,
>=20
> Warren and I have arranged for Google to provide two remote hubs for
> participants who won't be able to attend IETF 98 in Chicago because
> of the recent travel restrictions.  While we understand that many folks
> might prefer to simply attend remotely from their home or office,
> experience with the IGF and the Latin American remote IETF hubs
> suggests that there may be folks who prefer to be with others for
> the events.  We hope that providing this option makes things a bit
> easier for them.
>=20
> The current plan is to use two Google offices, one in eastern Canada
> (so as to be in a nearby time zone) and one in Europe (which seems
> to have the highest percentage of affected participants).  These
> offices will be staffed by volunteers and will provide local conference
> room facilities, wireless network, and snacks.
>=20
> We have some flexibility on which offices to use, and we'd be happy
> to take email from potential remote participants on their preferences.
> Alternatively, we've also set up a form at
>=20
>  https://goo.gl/forms/pbuaDdhS2xyKpcps1
>=20
> to collect this data, if people prefer not to use email for this.  (The
> form does not require a Google login to complete). =20
>=20
> We understand, of course, that situation is fluid, but given the need
> to coordinate with local volunteers, it would be great to have an=20
> early insight into who many of the affected people might use this
> option.  If you could share this option with the community so we
> can get that insight, we'd appreciate it.
>=20
> thanks,
>=20
> Ted Hardie
> Warren Kumari
>=20


From nobody Sat Feb  4 05:01:25 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92990129A6A; Sat,  4 Feb 2017 05:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sT2YfUUaRI2i; Sat,  4 Feb 2017 05:01:21 -0800 (PST)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30093.outbound.protection.outlook.com [40.107.3.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B588129A66; Sat,  4 Feb 2017 05:01:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=d04nY2SDclXqZ+bXYQKC8auCa2zxO/JdXrvQJeEK33k=; b=E4gV49xKduIC/kz2E16oAS0W8tH3HxcS8l8TkRp8niR1YqqnwaGne+Ru9Ko/NG/QZBdf6/m7epNyEnVnQevI8g57UAHXuLTaZP0Scx5zXhlnPzBj2H5+1BgHhqd9kH3JrXvgHpkSRMBfp7Me58rB0Y8E5akZb2CyIO5lU8CeTLQ=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Sat, 4 Feb 2017 13:01:18 +0000
Message-ID: <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <otroan@employees.org>, Pete Resnick <presnick@qti.qualcomm.com>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
Date: Sat, 4 Feb 2017 12:48:15 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: AM5PR0501CA0015.eurprd05.prod.outlook.com (10.164.187.25) To HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13)
X-MS-Office365-Filtering-Correlation-Id: 5d4636c5-66e1-4e13-077b-08d44cfde966
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR07MB1563;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 3:3fiC0CUOFPT2c/EyhAIfR8gDTDPhtS8Sc4m3j2PS/E8JLIKA9UZ0I4PQWGq+nDx0bEPzEDH5iCu2Fzu9qPgUMff1LF+TaDVqJr86PAYrSU+cFK59WrLuduRHk98465fwp6zzvjdk8o0asdfOBqpvVfXxeMEWQEFqs9N32xYv7qZAj0q10LN0OjogIymy/8PBs/wP3PfAafFSVaTTCAJVru/z/6m7WL3otHU1q067NpArcwcN0phBULm8N3llIjfgG0kk2MG7TOTGgWKBBI/G4A==; 25:G2VroLltxLAyhkbHMrlXQ9sPTuO7SR8KXCUsEgPE01TnQhIzprCrU+gnN7rCmYxVr3nigPjQszQJwK8FaxJlWAyVMtTD22M0MkbAVR8f20yAbVUSW/JqHoywoIGj7mnA03VFQOVo3eV8K84L3h0QsIBGSyZ4L7Ngqn4mkL4ZUPNDTxjDXOGw+yM8l59RtxJLvIETSnMWce/OfNKySJD89F+8+pubCSAF1/IdcrQ5CJ2k7sJqU9UyzCQuPLg75+vZplfqrCeyqL+4DjyJs0e5BHg0K+2pe55HVqyNoTaxFtalUS4w83zY2tQSSiePBTjcVfM4MbxHdCykcme042PmCNVBkn0CmD7fh2KYhiDFofhsiULpOOUR1s8oqnD5zRBDmNS5LrRLJItgDIu3TzlfffO5vBvUyr13uFUXAcFzc3dhM/NeZPVEJlw31JnU8WTA9HzsyMv6qSURsrhAheuBrw==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 31:dsbMqxs046dvqraPVtX3UL1Si1cb8x6zIfQxpI84KCrV0U9Skh/5VJza944bt6IqvQH3Nx1TBg+L7gNVqwXnLbYo7al41aGe9KMWqVrQDopyJxLPHiQoRbWAK0XsgzofGNxvoZVnkZiQLuLNlxXjBHpUeKlxs0j3Ls1UrE9PYlJq/G4SemGSH4xqH5RflXbF+ER2/eyAUtaa2sF+cm+PZ02n04LOx9GM2jy2CX7MnhGRVfR0Xz6qN8wvOw38FDjK4mV8bqu1xSN54gjNDSkmAg==
X-Microsoft-Antispam-PRVS: <HE1PR07MB15633F4A13097837448DC0FBC64E0@HE1PR07MB1563.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(178726229863574)(209352067349851)(100405760836317)(95692535739014); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123558025)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(6072148); SRVR:HE1PR07MB1563; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 4:Pk60RGRY7CeGw5PRdo3EVzUSQWsnCJU/cDqb53qhOehmkMWlcZ2NsF9o+41z6vPkuQgio21jrEv02dX1r/gQ4+vcVcIIP7sVV4MtYwfGUUiJEl3b3iv6JvqC9XW+HPL1pzpYx8LVIJosqTskZFi3dsuUjudrlhv/ome6UHgkyZlUpEl4W6qsxs/c2yrkK0kPmshSVZTwM803+PLpSWn8UlqMrVzFfTVYPkCnKlvXzPGHU7w9CHaNnt+Ky3+iqafSU5NjuLYBIHUTLSpZSFwaBn/IYGDsm1irqdw0MXKo0xCyUjQ58DsMlTr6PlCk3dam/Md27s/q5W7AeUmcKOpmZBhIJWkIXDAlzKM3TGkZjquu9sghh7k/0bKWpX1fyrRPIjKgZH+kOgK9QoPgQgD8RfjTG6GSlF5Ev6SBLFSDm1Hdh22TP08N596qdJMLcQlmhMsdQBGY58ilYcqcH6tgb9bTGMZ/4/e0CTe4GW7h/THaMGnXWTQuEGzYRw5vrkYUpcNdNpnLgp4LyzE2JvcmfQdG31GK3Xbv2K9FhNOtCAcVu5UsRQ0v82xTycFlLiy3kyCf5gGR+h+BIelbOpvrYZii8ItvLQUPKk2UKyOxqhaCbbRpzkVp/XKNk3NXLdJiuYgaZ3Ejp+WFj1Q6zxYWO7LJlIy+7uaP7LPkl7/3zHpTk5ShG1h8ykFlt4vfSDdejZngrAkeNDMrZjMfM0KHtfgKhyCuLdisdb0Qic85dX1dDZYpNTNOEDw7Il/JgG0O
X-Forefront-PRVS: 020877E0CB
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(199003)(13464003)(189002)(377454003)(47776003)(66066001)(5660300001)(81156014)(81166006)(86362001)(8676002)(50226002)(4720700003)(50466002)(84392002)(4326007)(2906002)(44716002)(62236002)(2870700001)(6666003)(42186005)(68736007)(61296003)(33646002)(305945005)(7736002)(14496001)(116806002)(230783001)(92566002)(6116002)(3846002)(23676002)(106356001)(6246003)(6496005)(105586002)(53936002)(1456003)(5820100001)(5001770100001)(97736004)(1556002)(6306002)(9686003)(81816999)(229853002)(101416001)(54906002)(38730400001)(25786008)(76176999)(6486002)(189998001)(81686999)(44736005)(50986999)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1563; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzIzOlRnbGJQS0ZvMURyUEE0bVRVaDczZUhEZEdC?= =?utf-8?B?NlM1cUR4Znh4UUVVeDkzY1Y0K1Nua0VRTnRlNzF6RUx5QWx3UHUwZE1IUW82?= =?utf-8?B?azJLMUIrd1Vza3gyTjJzWmtnRlI5UjJXVzVzWEpQaEVGVGVyRy9FbDJYSjVT?= =?utf-8?B?SkxxVDlNdGo2OU9rRlZBaGpXYUhoSGJ1dVBHaW9pelRWSmppMkpxd0ppbU1R?= =?utf-8?B?N2NBTnc5c2dHMG4xMTRkSVBVY0hNclVjaDNCNi9IRGxvbWxQLzBRaDBrbjZV?= =?utf-8?B?aU1LN0c4M1RQMUdydjkxcGZneEVYMjhEQ3VPTGsrRlFQdWdkRjVYaERYeXJX?= =?utf-8?B?TUtVRDNpQUxMQ0NibGVydU1sa0NoOXFOdVAvd3dzNGpGUWRlaVloM3hYcHl4?= =?utf-8?B?d2MxRHpqOUtJRGc3MFJScGlRTGFFNzBFWVA3cWNHcW0vMmR3K0hZNFlnWXdp?= =?utf-8?B?SVBSS0NnVlpMTG42U1o3eTBqa2s1cTZsTzkvZElad1NJclRiNm9GcEoraDZO?= =?utf-8?B?c0JqODhXTnpVOTdid1NtaEZ3QmluTXlzTktlMk5vazZxdjRrWFFOY09oMWly?= =?utf-8?B?N1l0ZUdXR2djbDkrbjc3ekpPREFMZ294dWFFaVhXU1cwemlIMEZtamJKZmpU?= =?utf-8?B?MUtEMFV5L3RORlNrczJhRXM0c2x6S1JTakJqejBBdDFTZSt0MStIell3V0NT?= =?utf-8?B?d05rb2ZRbTVrYjE1NWUxNzZPbVJPRXZyMDF3R09ENW02WWUwdUZKY1FMN3Ry?= =?utf-8?B?NHpmM0JzVFRTcjZ1S3hnVGlyQjFjbHpwOXBPYkxLN2c1djA0TCsvQ1JBWGh5?= =?utf-8?B?VW1VL0dzU2ZuQUY4UDhvNndOeHR1aGtoVTA2VUIvc2ZkTzRVVG1yc09hQkVY?= =?utf-8?B?Z3piWmJQSWVnZ0tEa24yREFsZ2piMUYyc3ZCYU95NEdSMHY0WG5RSnZOdTYr?= =?utf-8?B?Z1hiTFpMZmIyWDRDMWlGOWxWN1RWWEhOSGZUTGJITmxwTUE0MXB2UzJDaS9X?= =?utf-8?B?azA0ODl2S2F4WUJ1TDlQMEpGTFlhZUUvV0tSbTNwUnN4T0xrQjdqT2pzc1VE?= =?utf-8?B?eFJuUld2bTQ5NDc0em82ODFIR3IrNzEzM1MycHJqalJFWXZzNmpjY21aWmNk?= =?utf-8?B?aW9HWmo1VFVZMGlSc2NJd0ZyL050VGdweXE0TWVpMHpmZGhiaE82VXhjVXNF?= =?utf-8?B?NkNKNWtHRDE2WnlEVFBVMkoyNW45VmxrK2hkR3NZZDJSZDliY3lyTmYxVWpj?= =?utf-8?B?eHhLdHFGcTE1bERpOVBMa0x3cE9TU1d6MDJsSStESGtRdXpUTkliRW9mUWwr?= =?utf-8?B?ajdmZHV6cFl1MTl0U3BYbUNMQng3M2xZYVRReFROVG02YUhDWERPZU5VRzlV?= =?utf-8?B?dmZXMXRuY08rK2txeTI2U2ozWTJWSWtBK1N6VWg3OHYwRk1jWmJXUGhXa2Mx?= =?utf-8?B?dFpXMUpiakYvSWVDcnduZTZUbGJJenNYc3J1NFQ0V0ZGdnFNTnRXNDFMMlFm?= =?utf-8?B?RVduQi9uamVOdlJXQk5KSm1VYXV5ZGZ0MXpsZmVYUU5XOUcxbm0zWGVadUJU?= =?utf-8?B?OTJnRmM0czUrRldEK3lPUkJ0QTc4WERVNHdTWWdnWkVjcXo4RWNGR1c2R3hH?= =?utf-8?B?MWdSRzlVVHpsRm9WcTFFekorT1dYcXdlQ0I5Q1Vad29lOUlsV2FkS0R5Q3Mx?= =?utf-8?B?VE1IVG5sRjNjUGs2RzBUZ2pLUnVyazdwZ1hidThTbFZWRGJpaTB3ZDdaWENz?= =?utf-8?B?NUhkUzJia0lralVuTWpmZmNDbzRiVVNTd3VRUXZJc1dlSWxlQjNBUDVyR3Uv?= =?utf-8?B?KzZzdks4a2k3N2lzekJBZUxtajhIZW1UR3k5TW1PenRBeDQ4NVZXVlk2NENU?= =?utf-8?B?ZjhOQmduSFZZam5uT1ZtQ3Q4NVF5WkFEbVNtSVBJYjhEMUNWRTFwdCtZOGpo?= =?utf-8?B?QWs5Y3FhS0dQYm9VK3Nvc1Z1WWdvMDhzczZIOHc5bk1sMm15bjU5c0FTbWZx?= =?utf-8?B?RmNjbFdpLzZJRXZCY3V5M01JS00rQ0ZxSjE5dnVWK1Vzc3FjN3NveFFMZFIz?= =?utf-8?Q?ck/g=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 6:x2+/Zj7f5YBmj2drwVqjEPjRvFrBwy3LUX8wp3YvmhDmFmxQ8qQ8ZjM+uToSmDHzTOT7k9xKGiGoT5tWwlarIjY9sTdCuT2E+q7phgYMRx1Rz+qGcBafMm9f+2BOmdxNgXYbs6LaujavHQWIY4KpaQ3b/dO8RST+lgycaWFso6QHVhpBPJznzb3RUG20Z74xqoheMdCKU4doO00fbr3aFhmp7QaMz4QQ0Rxu97QLwXDRTSN3tcg5egZbapqT4fWfd0eHjLdO/cl5e1q8FAt0NKqfxqPxfqCN3d0LFOsTep5H8Mr0uHrr6KRfqRIUcmXcUs9UrY4b6/LQhUAw8YEIJqt7UIOUwsQnciXdKGA84r7BZYy5fQ/sDrleWx7TvoNXVxZj2TB05Z55dNow9GrqxQ==; 5:tnZOiIjTdj1og5RZqSW8b2voLYHsrqraZkwLY38hfj3ttSyi+zzL3bw4AV1DOMce306sgb2C1T9qD0c4Udt3ICHkwrIV/G2kQvzRP8JHXZMrJZWR/nZIpS7zcA3AzM4PEMYNSHekLBVj1+bJiGppJw==; 24:uMyHDMmplo8L72LKDPFoYK2asw0X31WpKIcE1FosRNSr+IE2o898fuYqd3txx3DfAETa8QmX+gdcu/WFLbwrgj1n8UlzKPoPx59F5rT7OIc=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 7:C+T9l6g2ti2cRpeSkxC+xJcy2Q4IPC+g0mP0ji9SxCGyUE9p6IP4Nwh309bkQmrIFCFnTiyhuo6dM5AzEpiLuf/gHAd3O8XW33paYSsKza+mYMarqCF0N1keBE0jAG2nUHDX4b375dfqKgjTS8Nt3RhbEqKlJpqlIdRp2guAZuga0ZcrQpAtYK6gGHlzV+/LFWSjzdz2xKs/3VhjgLbxrRFCjI32DyryINVHIr2KoLGKDlTghLafJPzw0btrUpGbd1GVF4yDyPNN7jS8pG9D+PqpObJ85a4h7XhMwa+GzOv+xgEiW2wUIBZI9V5eaivzueUrVv8HSUB7xZB0e6G9gWMa8Bcl38tHBLeh3PGF04dbgJ339flJRfT1ABmFW4m+Roxpgrx72Nf6ZhnTwvut+xpwF8y6A7jWvmCPpJiVV8zhQNHnbZOnfvDwlri8sbavTzo3a84MkfqoAEHIZvP7qmSSBVne+E2FVym6smd3dVN50H2tT2JqT/5C+DlPnsLZPbIq3fssqiBhZwBezRGD8Q==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 04 Feb 2017 13:01:18.4821 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1563
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4bhW_HJcgqxoVp2L0Kud46-S8SY>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 13:01:23 -0000

I do not know how to make it happen but I would like to see considered
opinions on this rather important issue from those I see active on lists
such as tcpm, arch-d and intarea whom I do not see active on v6(ops).

Tom Petch


----- Original Message -----
From: <otroan@employees.org>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Cc: "tom p." <daedulus@btconnect.com>; <6man-chairs@ietf.org>;
<draft-ietf-6man-rfc2460bis@tools.ietf.org>; "Stefano Previdi"
<sprevidi@cisco.com>; <ietf@ietf.org>
Sent: Saturday, February 04, 2017 8:32 AM
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
Protocol, Version 6 (IPv6) Specification) to Internet Standard


Thank you Pete! You are of course right.

Let me try to provide some background of the issue.

The contentious text is the following paragraph from 2460:

  With one exception, extension headers are not examined or processed
  by any node along a packet's delivery path, until the packet reaches
  the node (or each of the set of nodes, in the case of multicast)
  identified in the Destination Address field of the IPv6 header.

Essentially the question is:
- Does the IPv6 architecture permit insertion of extension headers
and/or header options by a node along the packet's delivery path?

This question came up triggered by discussions around some recent
proposals:
- draft-ietf-conex-destopt,
- RFC4782 (does header deletion)
- draft-ietf-6man-segment-routing-header
- draft-brockners-inband-oam-transport

The IP architecture (IPv4 and IPv6) supports _modifying_ IP options in
flight, but it is unclear if it could permit changing the IP datagram's
size.
Increasing a packets size in flight would break PMTUD (RFC1981), AH, and
might results in other ICMP error messages being sent to an unsuspecting
source.

There were three main positions argued in the working group.

1) Ban header insertion outright.
2) Describe the problems with header insertion.
3) No changes to RFC2460 text.

Permitting header insertion in the sense of specifying how header
insertion could possibly work is of course outside the scope of
advancing RFC2460.

The chairs tried various approaches to find a consensus without luck.
The approach finally chosen was a poll between the three options. And
the (rough) consensus was based on the data from the poll.

Excerpt from the shepherds writeup:

A working group last call for moving this and the other two documents to
Internet Standard was started on 30 May 2016. Reviews were also
requested. Issues found during the last call and reviews were entered
into the 6MAN ticket system. These are now closed. The biggest issue
raised was how to handle the issue of Extension Header insertion in this
document. After many discussion on the mailing list and face to face
meeting, there wasn’t a clear consensus. The chairs conducted an online
survey that provided three choices: Ban header insertion, describe the
problems with header insertion, or say nothing. The result of the survey
was to describe the solution. The results and methodology used to
evaluate the results can be seen at:
https://mailarchive.ietf.org/arch/msg/ipv6/_gG2foiugk5B7w3TpnPvBbjHDzs
This was discussed at the 6MAN session at IETF97 and on the mailing list
after the meeting. The chairs believe there is a consensus to go forward
with the text that is in draft-ietf-6man-rfc2460bis-08.

The summary given to the working group calling for the poll:
https://mailarchive.ietf.org/arch/msg/ipv6/AtY92TpJ3vvmiidzcPkJdXKZQIA/?
qid=84de5e109c8f8f255d03c4c98ff3e50c

Best regards,
Ole, 6man co-chair



From nobody Sat Feb  4 06:14:30 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D68D4129AEE for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 06:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 QJ8GzV5utGkj for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 06:14:25 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8373A129AF2 for <ietf@ietf.org>; Sat,  4 Feb 2017 06:14:25 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ca16e-000DHQ-8P for ietf@ietf.org; Sat, 04 Feb 2017 09:14:24 -0500
Date: Sat, 04 Feb 2017 09:14:17 -0500
From: John C Klensin <john-ietf@jck.com>
To: IETF general list <ietf@ietf.org>
Subject: Diversity, writing systems, identifiers, and protocols (was:  Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard)
Message-ID: <F4675E5282458BCBABDBDBCE@PSB>
In-Reply-To: <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/syKFSOC32H4e3NDfFdGJiQyE-Yw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 14:14:27 -0000

--On Friday, February 3, 2017 14:51 -0500 Viktor Dukhovni
<ietf-dane@dukhovni.org> wrote:

>...
> Is that right?  Thus the verifier would sometimes need to
> convert from U-labels to A-labels (when the localpart is all
> ASCII), and at other times from A-labels to U-labels (when the
> localpart is not all ASCII)...

Victor,

I think there is another issue hidden behind this that is worth
mentioning and that interacts with your concern above.  While it
may or may not be important for any given protocol in the
abstract (it will be for some, but not others), using strings
containing non-ASCII characters in ways that interface with
users is always going to involve tricky issues that require
understanding and understanding, not just plugging code points,
possibly with an encoding specified, into slots.  People who
"just" want to be told what to do so they don't need to think
about it, or who want to apply a package they don't understand,
are going to sooner or later find themselves or their users in
trouble, whether the issues are identified as security problems,
matching/equivalence errors of various kinds, user confusion due
to violation of the law of least astonishment, or something
else.   The underlying issues are the result of the wide and
very rich diversity of human writing systems and languages --
systems that are diverse enough that almost any simple statement
or rule one can come up with will have exceptions.

In general, that diversity is something we should celebrate
rather than trying to find quick fixes or tricks to get around,
only partially because those fixes or tricks aren't going to
work well for some group of people.  Narrow views of the
situation just lead to other traps.  In particular, while useful
lessons can be learned, one cannot extrapolate from knowledge or
experience of Latin-based scripts (even if one knows more than
one language that uses them differently) to all others, from
very closely related scripts (e.g., Greek-Latin-Cyrillic, some
subsets of Indic (or neo-Brahmi) scripts, or so-called CJK) to
writing system outside those groups without missing important
cases and causing problems elsewhere.

Like the kinds of diversity we deal with in some other areas,
the differences did not show up overnight.  A large fraction of
the human population has been cr4ating and practicing them for
centuries and, in many cases, tens of centuries.  

If IDNA enters the mix, another layer of knowledge and
understanding is required.  It is actually easier to grasp (or
grok) than the above, but may have even greater impact in
protocol design.  Unlike the above, IDNA is artificial and a
recent invention to solve a very specific problem with
incremental deployment, a decision most of us, including most of
those in the IDN business and those who use non-Latin scripts on
a daily basis, think was probably a good idea.    People simply
need to understand how it works and is intended to evolve, with
the U-label <-> A-label symmetry and checking requirements as
particularly important.  In particular for this case, protocols
which reach the user simply need to be ready to handle U-labels
and A-labels interchangeably.  Because of the combinatorial
explosion problem, trying to do that by enumerating the possible
FQDNs just won't work -- people may know what, e.g., they intend
to push out in email or use in the text of an HTML "a" element,
but there are going to be just too many things in the network
toat will change things back and forth for their own (perfectly
rational) reasons.   At least IMO, that makes a very strong
argument for protocols, where it is possible, defining and using
a single canonical form and expecting user interfaces to do
conversions as needed.

You may reasonably disagree with that last conclusion because it
is just a protocol design preference, but most of the rest
almost certainly must to be treated as immutable facts, at least
until and unless we all agree to use the same language and the
same orthography and writing system for that language.

   best,
      john


From nobody Sat Feb  4 08:36:31 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0E7112964E for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 08:36:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIokC546m44E for <ietf@ietfa.amsl.com>; Sat,  4 Feb 2017 08:36:29 -0800 (PST)
Received: from nm39.bullet.mail.gq1.yahoo.com (nm39.bullet.mail.gq1.yahoo.com [98.136.217.22]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E93412964F for <ietf@ietf.org>; Sat,  4 Feb 2017 08:36:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1486226187; bh=3cRhP9wWlCXHH7oOxIhPfFgPaCjd3GRzognGKqNiRsA=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=CtoJoACoXO7IYuyT+7Uv7gJ9cxKx4VGTec4GTrdZwgcCKjwGWwuZSZR9Qgg8bmbK/vLYhytrP8cL6MIB2eKJz1JyO5kBGpPfhcZFlACpNDS7tEhXAoHEEgkZa2jxQ4Xn6KvmV9+p3FcxAjtd6RyjFHaWqO4gK0duzhcCR0+iMrop613bwzhCFe6mjZ/7hbqsyJKsI3mWH12DT89goiCf/yvNbIOSo/ZGtBj0GtD1V2x7cC+SV//cNOaRjfrABzLSYc55RKg4TCsEaiuqv2NulyOOF6zvHt8gJkCrvljc5sjdHmfjp+w8zu0gaIrUxy9GwGrR7+1Oy+1NnWObV3AvjQ==
Received: from [127.0.0.1] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:36:27 -0000
Received: from [98.137.12.59] by nm39.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:33:46 -0000
Received: from [98.137.12.215] by tm4.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:32:46 -0000
Received: from [127.0.0.1] by omp1023.mail.gq1.yahoo.com with NNFMP; 04 Feb 2017 16:32:46 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 516516.64437.bm@omp1023.mail.gq1.yahoo.com
X-YMail-OSG: H52lNU4VM1k4TMdWtvP54EvgUQXkDxKY.x7_mfDU4riPJA.umskEhyP5gPabruW _ZFUpJPKhR34gwAI4y7_euiq5VMUF2Oe1RJt_hPAIm6zfuZ0GkKXDj0ltWPkb7TGEVM4R.mW6Gv. w4RCiOrxRz2MpAF0zMWf6NBosqp8M7WXZl3L_ddS8nKBWoN5e4uPJy3kKk8W.Yv5qZnfLppW9Phw upm5bo6SgnJKyFAVW_0cS0kdOm3UP0cofrlT2Hc7.uupFRQCscu_8.RdZoiUXRdq9Is_93NlsYGL .lrUPnPAlgIZk6_IlSgerGkOBXsv2MlzH.xh6LUHfobUv_HoWc9_qE2liMMJ_b1BHH.exdQZNI78 DbsSaXGlqxU6hjUmvYuEBatCZsNyIoW1xtbnHx7p30EfdMAK6tqE5JmUEpTP09TzhdLm7nALiZXQ 6z7Y5BoXJ6sQok6SRCL6UEmdoqowkrAwS80UBejXuf1b3h0m9pr2JW1YNp6GNiNVqxCNgE3cJl7t FaCHo2SfanfUaFuIYjPU9XTxeXtcOUtdKaQB4WQ--
Received: from jws300066.mail.gq1.yahoo.com by sendmailws104.mail.gq1.yahoo.com; Sat, 04 Feb 2017 16:32:46 +0000; 1486225966.156
Date: Sat, 4 Feb 2017 16:32:45 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF Announcement List <ietf-announce@ietf.org>,  <chair@ietf.org>,  <ted.ietf@gmail.com>,  <warren@kumari.net>
Message-ID: <1810751398.1259948.1486225965881@mail.yahoo.com>
Subject: Re: Remote hubs for IETF 98
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <1810751398.1259948.1486225965881.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rpLlIUJOgUU-clQcUD7Cs0vFHC4>
Cc: ted.ietf@gmail.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 16:36:30 -0000

Thank you, Ted, Warren and Google for doing this.

You are setting a precedent for others to follow.

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360

--------------------------------------------
On Fri, 2/3/17, IETF Chair <chair@ietf.org> wrote:

 Subject: Remote hubs for IETF 98
 To: "IETF Announcement List" <ietf-announce@ietf.org>
 Cc: ted.ietf@gmail.com, ietf@ietf.org
 Date: Friday, February 3, 2017, 12:56 PM
=20
 I=E2=80=99m happy to report that Ted Hardie
 and Warren Kumari and Google have
 stepped up to make alternate arrangements for people who
 might have
 difficulty travelling due to the recent travel restrictions.
 Thank you!=20
=20
 Please see the details below:
=20
 -------
=20
 Hi Jari,
=20
 Warren and I have arranged for Google to provide two remote
 hubs for
 participants who won't be able to attend IETF 98 in Chicago
 because
 of the recent travel restrictions.=C2=A0 While we understand
 that many folks
 might prefer to simply attend remotely from their home or
 office,
 experience with the IGF and the Latin American remote IETF
 hubs
 suggests that there may be folks who prefer to be with
 others for
 the events.=C2=A0 We hope that providing this option makes
 things a bit
 easier for them.
=20
 The current plan is to use two Google offices, one in
 eastern Canada
 (so as to be in a nearby time zone) and one in Europe (which
 seems
 to have the highest percentage of affected
 participants).=C2=A0 These
 offices will be staffed by volunteers and will provide local
 conference
 room facilities, wireless network, and snacks.
=20
 We have some flexibility on which offices to use, and we'd
 be happy
 to take email from potential remote participants on their
 preferences.
 Alternatively, we've also set up a form at
=20
 =C2=A0 https://goo.gl/forms/pbuaDdhS2xyKpcps1
=20
 to collect this data, if people prefer not to use email for
 this.=C2=A0 (The
 form does not require a Google login to complete).=C2=A0=20
=20
 We understand, of course, that situation is fluid, but given
 the need
 to coordinate with local volunteers, it would be great to
 have an=20
 early insight into who many of the affected people might use
 this
 option.=C2=A0 If you could share this option with the
 community so we
 can get that insight, we'd appreciate it.
=20
 thanks,
=20
 Ted Hardie
 Warren Kumari
=20
=20


From nobody Sat Feb  4 10:40:51 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00F4612950B; Sat,  4 Feb 2017 10:40:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 500VxY8EfptD; Sat,  4 Feb 2017 10:40:40 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id A2AEF1294BA; Sat,  4 Feb 2017 10:40:39 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 04 Feb 2017 18:40:39 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 3379DD788B; Sat,  4 Feb 2017 10:40:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=+nAUwmE2HDzkl7YJ2+pb6FB3QpA=; b= Ylmy9+UCTP6dgRPgtWieNw/+Ud1fYq8fCoyeoqXl5w+sa9yXEmPZ8Ho+7xm1R1k1 +ZXXsAE76RtSR8HVTpNBJoPsepHgoKrrXcBWMcVsCCE60FYsdLAFqa8DqbYKTEFU /9Volp09jDInXbOz5zVhwzHhcAonlnq7CC6An6q3ucc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=lln2//4v/pzbCrq2E1ER9qI lgT3/+HgNxrfiyUot+SFwv8zkXJbig06R1uvYGRex/mejWQFpO4X6v3JPRP3oNcS O3tbedYI3rEybWLjbJkEeJhSohlzZmtl8GsILp7/W99zI+LlKEF7L8SbWMhgFPfx F7Up+/BtJxYPSopEnspg=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 073CBD788A; Sat,  4 Feb 2017 10:40:39 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id A1D8E841116F; Sat,  4 Feb 2017 19:40:36 +0100 (CET)
From: otroan@employees.org
Message-Id: <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_DD8FD33D-FE8D-4C53-B8E5-620BE77F2552"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Sat, 4 Feb 2017 19:40:36 +0100
In-Reply-To: <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com>
To: "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sMHoXglEAXO5YvtB5qchoRRiRyg>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 18:40:42 -0000

--Apple-Mail=_DD8FD33D-FE8D-4C53-B8E5-620BE77F2552
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Lars,

>> My apologies: my comments were probably misleading. Certainly, this
>> document is simply RFC1981 to Std, and hence recommending RFC4821 =
would
>> be kind of ou of scope, here.
>>=20
>> That say, one might wonder to what extent, and for the general =
Internet,
>> RFC1981 can be considered succesful (given the filtering of ICMP
>> messages). -- i.e., at this point in time you wouldn't rely on =
RFC1981
>> (icmp-based pmtud) for path-mtu discovery.
>=20
> What Fernando said: I'm certainly not opposed to lifting this to =
Standard, but it is painting an incorrect picture - PLPMTUD is de facto =
mandatory these days, and has been for years.

While I'm all in favour of PLMTUD. It doesn't seem like a complete =
solution.
PMTUD on the other hand supports all protocols on top of IP.

Looking just at our specifications, we cannot state that PLMTUD can =
replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.

O.

--Apple-Mail=_DD8FD33D-FE8D-4C53-B8E5-620BE77F2552
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYliAkAAoJEL7aWKiYQt92X3YP/1VUq1O0wQ7ingkwU3B/NwvG
wIN2OnXLUEN/ffQqIg+fM4VZu45fS45PVbELeiXu7fnts4GUb5osnpfwDeNRROrs
/+yhmvG0YzmJVDlFjcwRG66WyIEtgJjLpQsryeTgQk1rD3nRdzfg1ZA+ysznK2h2
g22DvlnPnbPIAIsjBaVBWwQIqz1JHhzATBQ6e1d0uHcYiNuBWFUz+6tAnL3Q3Giv
bHtgImeydxvpFzle1hVQ7IoPo7WFrHYpPIciTitT05AGQZEs41SnWCxJPgGRBydO
su3g7U7nGCThN341laq6G6CU50KtCTfuFIFZTG/xp5f48hNkXa7m08tmIe6VgCT+
yUOwys010OTVU19wrzVuTsrS1J6Ka+RgUrCP+bCREsupDdXg/hFaRZzZC68HPBTr
WALx8lRhcWBdtSkWe/78P3BJjgQAB7BRzaRE1IfJpmMZ119zKmRqtzal/6fQ8g6f
6OOEN2n3LGAPbBgfBsbsF0BxKDWC6hcnRxJCI/LlOwJrFmewHghCQACsfUs6vCEv
aq0Vt/uRA+VVKRVVpd/OFboO6v8uV8WRL/z4OuH50/qjfaKc2n3l33m805tlA3O5
GjifuZTOb8vISRxSXtVE1SADqxGbpQ92jYBi52qXsHwvmWI1IIHRrIsvidZI4gG0
0JtC3EyHRnK7vY5Vq8Rc
=vYbV
-----END PGP SIGNATURE-----

--Apple-Mail=_DD8FD33D-FE8D-4C53-B8E5-620BE77F2552--


From nobody Sat Feb  4 11:06:42 2017
Return-Path: <erey@ernw.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 081F0129C1A; Sat,  4 Feb 2017 11:06:41 -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 autolearn_force=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 iBYacc1oWsQ4; Sat,  4 Feb 2017 11:06:38 -0800 (PST)
Received: from mx1.ernw.net (mx1.ernw.net [IPv6:2003:60:4010:10a0::11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4080129C1D; Sat,  4 Feb 2017 11:06:37 -0800 (PST)
Received: from mail1.ernw.net (unknown [172.31.1.30]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail1.ernw.net", Issuer "ernw ca1" (verified OK)) by mx1.ernw.net (Postfix) with ESMTPS id 9AFDF2730F; Sat,  4 Feb 2017 20:06:35 +0100 (CET)
Received: from ws26.ernw.net (unknown [172.31.1.70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ws26.ernw.net", Issuer "ernw ca1" (verified OK)) by mail1.ernw.net (Postfix) with ESMTPS id 7752F357D6; Sat,  4 Feb 2017 20:06:35 +0100 (CET)
Received: by ws26.ernw.net (Postfix, from userid 1002) id 3878139796; Sat,  4 Feb 2017 20:06:35 +0100 (CET)
Date: Sat, 4 Feb 2017 20:06:35 +0100
From: Enno Rey <erey@ernw.de>
To: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Message-ID: <20170204190635.GC80290@ernw.de>
References: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com> <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KGfHVQ6Hazb5NJkaGxG8WL3kYS0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 19:06:41 -0000

Hi,

On Sat, Feb 04, 2017 at 09:32:37AM +0100, Fernando Gont wrote:


> Everyone has agreed (including the authors of RFC2460) that EH insertion
> has never been allowed.
> [...]
> > Permitting header insertion in the sense of specifying how header
> > insertion could possibly work is of course outside the scope of
> > advancing RFC2460.
> 
> Explicitly allowing EH insertion would most likely be out of scope, too:
> It completely changes a very basic aspect of IPv6.
> 
> FWIW, I think that publishing a spec with what some have considered to
> be ambiguous text (subsequently leading to 600+ messages on the very
> group that specifies the protocol) would be a lousy job on our side.
> Either explicitly ban extension header insertion, or explicitly allow it.
> 

The first talk I gave about IPv6 was in 1999 (with an experimental IPv6 stack of Windows NT and being connected to the 6Bone). I don't remember much of it but I'm pretty sure I explained that the desire to restore the pre-middlebox, pre-NAT end-to-end character of the Internet was one of the main design drivers of IPv6 (hint: you may also look at the "Acknowledgments" section of RFC 2460).
Quite a few IPv6 books of the time (we still have them in the library, feel free to reach out for examples) explicitly mentioned end-to-end as a major property of IPv6 and many guys giving IPv6 talks & trainings since 15+ years now have it on their introductory slides. Furthermore several adjustments of the main IPv6 header (e.g. removing the checksum) and barring fragmentation performed by intermediate points clearly indicate the message: "in general we don't want devices to mangle with packets in transit".
So, from my personal perspective, it's painfully obvious that there was never any intent to allow the modification of IPv6 packets in transit (besides very specific exceptions which were clearly described), and this has been an undisputed principle of IPv6 for a long time.

So one may be tempted to ask: why do we have this discussion at all?
Well I think the answer is quite simple: as so often in life, it's about agendas and politics. Before I comment on this in a bit more detail, let me add two disclaimers:

Disclaimer (1): in the following rant on how certain things are happening at the IETF I can only speak for IPv6-related stuff. 
Disclaimer (2): addressing such a rant in direct to an IETF mailing list means I will tap on the feet of many people. Feel free to personally let me know your strong opinion or just ignore me/stare into another direction from now on when we meet. There's only a small chance this will happen at an IETF meeting anyway, for reasons laid out below. 

Let's look at how the actual discussion (and subsequent specification) work is done at the IETF, similar to other voluntary organizations: on mailing lists and in (f2f) meetings. As we all know, these meetings take place three times a year, each on a different continent (yes, I'm aware of remote participation, but let's be honest: at the end of the day how much impact on specification did this have this in past, in particular in heavily old boys' clubs dominated WGs like 6man?).

Further fact is: if you look at the lists of participants of the meetings, the vast majority of it is vendor personnel. This is not surprising when reflecting on the incentives different parties may have to send people to IETF meetings. How would, say, an enterprise person argue in front of her boss to attend the 51st (!) IETF meeting since the publication of RFC 2460 (especially considerung the ongoing [non-]state of deployment in large parts of that space. it's up to the reader to connect that state with the things I describe here...)?

But it's not like vendor people don't have to justify these nice trips to their bosses. Of course they have to. 
Here's two prevalent strategies:
- "we have that new feature. let's try to push it into an RFC, as this strengthens our market position (in general and for selling the specific thing)"
- "you know, there's this future thing called IPv6. I'm in one of the working groups where we come up with lots of creative ideas how to even make it better. my name is on one of the draft documents so I'll have to be there, at the next meeting (and we, as a vendor, demonstrated our contribution also)".

For quite some of the stakeholders (namely both the vendor in question and the respective participant[s]) these are not only legitimate but fully understandable. It's just: does this drive things in the right direction of the greater good & community? Me seems we have a classic tragedy of the commons here...

I'm in the very privileged position that my employer would (and did so several times in the past) actually pay for week-long trips to nice cities and expensive hotels (and release me from other tasks contributing to short-term productivity, let alone revenue) three times per year. Still I do know many people *very* unhappy with the current state of IPv6 specs - and scratching their heads in light of the present discussion - who are not.
We/you guys don't have to care about the esteem of IPv6 community (at least the part I myself can speak for) and you might even feel obliged to ignore it ("we know better what's good for them").
But we should at least be honest as for the obvious agenda quite some vendor guys are pushing as for EH insertion (I don't have to mention SR, do I?) and you Ole, as a 6man chair, have probably noticed that there's not much support for the idea from anybody outside Cisco space (yes, I'm aware of the poll. but I followed the mailing list discussions as well).

There you have it. I don't even think that this was anything new for most of you. Still at times it helps to name the obvious.
If any socio anthropologist wanted to find a textbook example for "how voluntary bodies claiming to be open for anyone get compromised over time by vested interests" the EH insertion thing would be one.

best

Enno

For the protocol: given the fundamental role of RFC 2460 I, too, think that an implementor must be able to get a clear answer to the question "is EH insertion allowed or not?" during its lecture, without going through 600+ e-mails in an archive (just to find out that "even the experts didn't agree on that, at the time"). So I support Fernando's request of 
> Either explicitly ban extension header insertion, or explicitly allow it.




-- 
Enno Rey

ERNW GmbH - Carl-Bosch-Str. 4 - 69115 Heidelberg - www.ernw.de
Tel. +49 6221 480390 - Fax 6221 419008 - Cell +49 173 6745902 

Handelsregister Mannheim: HRB 337135
Geschaeftsfuehrer: Enno Rey

=======================================================
Blog: www.insinuator.net || Conference: www.troopers.de
Twitter: @Enno_Insinuator
=======================================================


From nobody Sat Feb  4 11:22:52 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BBCD129678; Sat,  4 Feb 2017 11:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMRcMQHD5ARO; Sat,  4 Feb 2017 11:22:50 -0800 (PST)
Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (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 1FC6A1294D4; Sat,  4 Feb 2017 11:22:50 -0800 (PST)
Received: by mail-pf0-x242.google.com with SMTP id y143so3925170pfb.1; Sat, 04 Feb 2017 11:22:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=zTS45thHhNXd1ztD7tXCpF4uoXg2d4nVQ0znGefmI80=; b=M8butEzly4OgC4gdSGnqIP8L8QTW0qqTc+LCAmxAmXEImjxUqMrHe7+fSqW2/GB4hj /47XCBwsOap7Xdnx6ZqEqvD8AKOj+ljY439ZBxRXlR56XpF7XC6wxyH0fpolivkHhGz2 mWSPmwYhHRw8O5uCBMwPGCnt/he3uEUtV8tvhYof/vIuydVmQRQw3+KPXByyS2miB1HH MTBqZHcMTzFK/qEukyLag+9ng70lGLxUX2jXtNqbAenvIlFFTDygWliskq5uqqH490bY dQvyWbv+vhq/SlNB4rDzDh7bHfoK5CCmCKUVLvs26V0mA0Nmvot9kyZIxTNRgTTYaDub k2gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=zTS45thHhNXd1ztD7tXCpF4uoXg2d4nVQ0znGefmI80=; b=duMR8eZZC/EYIaUqaJswPeOa+8yHUXCX1RKNJnSQokd6jh3LQJTUkYxLnnWwyGmdvg ADPWdEgR1I/I5nAdRDcKzm75h0MHt3M47+WRYu78Vz6BYX7ieAgV1MVjYxjgp2/68TU9 Cggt3rDKFgrUDm7HMsdQWSPALdrBF3LDtzyBwv23lrOZZLKwyaeebvEgH5V8vVSC3qAk X08/R9bQx8iAJHKXC2KfUV5Ml5JUh5nW8e/DzU8UrPq6PYji8mrSJrV51M+mB3wfBaEh s/cNbGp7op/zb2rQV4tJKgWZThJh6QzCnV2ZnMQDzN/Ts+5hGr2FmiPeWPE4jjYIZ+d5 1uGw==
X-Gm-Message-State: AIkVDXJFXOEQURHuoxRxziZtB39t5NdU/K9ZV+DPaIrYPxxHbPQTp+Jamr/H3P3hW9z3pg==
X-Received: by 10.98.202.139 with SMTP id y11mr4134449pfk.98.1486236169672; Sat, 04 Feb 2017 11:22:49 -0800 (PST)
Received: from [192.168.178.21] ([118.148.124.204]) by smtp.gmail.com with ESMTPSA id x2sm77045359pfa.71.2017.02.04.11.22.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Feb 2017 11:22:49 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Enno Rey <erey@ernw.de>, draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
References: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com> <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com> <20170204190635.GC80290@ernw.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8163e830-65ff-cd02-971b-6f26171c8635@gmail.com>
Date: Sun, 5 Feb 2017 08:22:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170204190635.GC80290@ernw.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h2mhNnNPTKX7OviDBQuMV0bRSqU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 19:22:51 -0000

Hi Enno,

On 05/02/2017 08:06, Enno Rey wrote:
...
> Still I do know many people *very* unhappy with the current state of IPv6 specs...

Where do I find their analysis and proposed changes?

    Brian


From nobody Sat Feb  4 11:34:05 2017
Return-Path: <erey@ernw.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F25D7129C49; Sat,  4 Feb 2017 11:34: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 autolearn_force=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 P2UGqaTlNYws; Sat,  4 Feb 2017 11:34:02 -0800 (PST)
Received: from mx1.ernw.net (mx1.ernw.net [IPv6:2003:60:4010:10a0::11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E6FF129C48; Sat,  4 Feb 2017 11:34:01 -0800 (PST)
Received: from mail1.ernw.net (unknown [IPv6:fd00:2001:0:d001::30]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail1.ernw.net", Issuer "ernw ca1" (verified OK)) by mx1.ernw.net (Postfix) with ESMTPS id 7425D27327; Sat,  4 Feb 2017 20:33:59 +0100 (CET)
Received: from ws26.ernw.net (unknown [172.31.1.70]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ws26.ernw.net", Issuer "ernw ca1" (verified OK)) by mail1.ernw.net (Postfix) with ESMTPS id 4C6EC35835; Sat,  4 Feb 2017 20:33:59 +0100 (CET)
Received: by ws26.ernw.net (Postfix, from userid 1002) id 137D6397A7; Sat,  4 Feb 2017 20:33:59 +0100 (CET)
Date: Sat, 4 Feb 2017 20:33:59 +0100
From: Enno Rey <erey@ernw.de>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Message-ID: <20170204193359.GA80939@ernw.de>
References: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com> <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com> <20170204190635.GC80290@ernw.de> <8163e830-65ff-cd02-971b-6f26171c8635@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8163e830-65ff-cd02-971b-6f26171c8635@gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kWXS0EnUqK4YYL1GC_cQ_yzpuww>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 19:34:04 -0000

Hi Brian,

On Sun, Feb 05, 2017 at 08:22:44AM +1300, Brian E Carpenter wrote:
> Hi Enno,
> 
> On 05/02/2017 08:06, Enno Rey wrote:
> ...
> > Still I do know many people *very* unhappy with the current state of IPv6 specs...
> 
> Where do I find their analysis and proposed changes?

the very fact that draft-ietf-v6ops-dhcpv6-slaac-problem created a 100+ messages thread over the last few weeks in v6ops might serve as an indication (and in that thread statements very similar to mine have been voiced, btw).
You might reject the following statement as similarly broad and unjust: many guys with a genuine interest in driving IPv6 (and being involved on a daily basis) have been repelled by what's happening in 6man and v6ops in the last yrs and have subsequently lost any interest in contributing. 
which creates the exact loop your question is directed to.

happy to discuss in more detail over a beer at RIPE74.

best

Enno


-- 
Enno Rey

ERNW GmbH - Carl-Bosch-Str. 4 - 69115 Heidelberg - www.ernw.de
Tel. +49 6221 480390 - Fax 6221 419008 - Cell +49 173 6745902 

Handelsregister Mannheim: HRB 337135
Geschaeftsfuehrer: Enno Rey

=======================================================
Blog: www.insinuator.net || Conference: www.troopers.de
Twitter: @Enno_Insinuator
=======================================================


From nobody Sat Feb  4 14:38:54 2017
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59EA812954C; Sat,  4 Feb 2017 14:38:53 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 UQ4kaJDO1S58; Sat,  4 Feb 2017 14:38:51 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id BCD4B129415; Sat,  4 Feb 2017 14:38:51 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 5665E909AFB; Sat,  4 Feb 2017 17:38:48 -0500 (EST)
Date: Sat, 4 Feb 2017 17:38:48 -0500
From: John Leslie <john@jlc.net>
To: "tom p." <daedulus@btconnect.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Message-ID: <20170204223848.GL10525@verdi>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/csWlRHrCNdVgpsp1M_Bo4UEKhEk>
Cc: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, Stefano Previdi <sprevidi@cisco.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 22:38:53 -0000

tom p. <daedulus@btconnect.com> wrote:
> 
> I do not know how to make it happen but I would like to see considered
> opinions on this rather important issue from those I see active on lists
> such as tcpm, arch-d and intarea whom I do not see active on v6(ops).

   Disclaimer: I was quite inactive in IETF stuff until about ten years
ago. (How time flies when you're having fun!)

   When I resumed activity, it became obvious to me that IPv6 had quite
a number of flaws that some folks were trying to fix, unsuccesssfully.
It was even more obvious that IPv6 _couldn't_ see enough deployment
until it settled down. Thus, I joined the group encouraging settling
down.

   I have since realized that the flaws were more serious than I had
realized; and that _only_ exhaustion of IPv4 address space could incent
widespread deployment.

   IPv4 space _is_ exhausted; IPv6 deployment _is_ happening... But
we're seeing two Internets: one IPv4, and another IPv6.

   This, of course was always the most significant flaw: no smooth
transition path. I didn't know how to fix it then; and I still don't
know how today. But of course, a "fix" _is_ being deployed: and that
is middleboxes.

   Perhaps the most glaring disconnect today about IPv6 is the folks
who insist it will cure us of middleboxes. Alas! many of us are too
polite to laugh out loud.

   As to the header-insertion question: IMHO middleboxes will never
disappear (nor come under protocol control); and some of them _will_
insert headers. We _can_ certainly ignore this in our protocol design:
the middleboxes in question will be happy to return the favor.

   This is a perfectly legitimate way to proceed -- and it is certainly
better than trying to adapt IPv6 to every middlebox out there today.

   Is there a practical alternative?

   I like to imagine a WG studying what it is that each middlebox
accomplishes in the view of the folks deploying it; then come up with
a better way to do that through a standardized protocol. (Only then
can we discuss how to squeeze that into IPv6.)

   I've decided to act as if I don't have a horse in this race...

   (One particularly silly flaw is that we allow _most_ nodes to
have a hard limit of 1500 bytes per packet: requiring IPv6 nodes to
handle packets ten times that limit would help a lot!)

   Sorry I can't be more helpful!

--
John Leslie <john@jlc.net>


From nobody Sat Feb  4 18:07:14 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACC15129443; Sat,  4 Feb 2017 18:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RjTsr5uZzZ7f; Sat,  4 Feb 2017 18:07:11 -0800 (PST)
Received: from mail-ua0-x244.google.com (mail-ua0-x244.google.com [IPv6:2607:f8b0:400c:c08::244]) (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 BEAC3127A90; Sat,  4 Feb 2017 18:07:11 -0800 (PST)
Received: by mail-ua0-x244.google.com with SMTP id f2so4547299uaf.3; Sat, 04 Feb 2017 18:07:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=M1GYaV7vPpEC/jz5zwIqRbTQ6dppZXWUeGRGIKs3Ork=; b=JahnIx+46/DoTQbJgxTiCIZLz7vZOxWoD8S596zvsBCccNUV+0VtuP0XzB9n6FKWZ+ ncVZ2Z4Oq6YLANkJjRBbU7lyi7+OiWseg/gMMFj4t4bdbb04AznrkUzGYeL46XFg3yG1 dKsgcEyCKOXxgt9eOfGgWcpnKGMbmTAUAVqE8U/RlbtAbzengzRZu76+i3kZ/hFziaGX TngMNOL89pz4gez+qwyTMpXhmhiUChtiIjrJq8y7H99l89XExDL6sP78ZyVP9NWljbDu Sh9kFI0kwFshS3IGg+haGtCsnnuxFqBrnrFDDKjTpEB2Jp76I2s+x+cSkLn1oAoupeM5 lkMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=M1GYaV7vPpEC/jz5zwIqRbTQ6dppZXWUeGRGIKs3Ork=; b=nC7F1G0z3YeLFB866JIQWV2qE1tx4XfQQMN/vw450YFMEth+McFvjPOKpzq8xVmPBx 1UT+O4swhh/Lefc0uXXdCYsEvCeQE0FQKfGDaHNTfgOYlzYhPignsHGotLXos+doXYW+ YY9ml43N8YRqpcbNaDmCnrmCVSHGB2/L3mxB/3zpBx59OPP4AvThtA6+iAR5RlSOsdJK ojw6Bc+4641ar48O6Xz4OtpvNwICgT41B16HbTM2j7XHgZOmWeLoZyqN6gO/60+3bIn/ JxbYDTt7lusn/ykJO/3t88MmTEj2+88z/ETAj1MFBQ6umWAjqWWQp1+fM2zkNjSMkQny ub6g==
X-Gm-Message-State: AMke39limyXc00BEYHRZ30poAIY6T1hy2kQmFiHSL1YCJLeekrpMiZTPIg3SLo+ct5EGtgnmhimmUddihu4jAA==
X-Received: by 10.159.40.201 with SMTP id d67mr2102686uad.98.1486260430786; Sat, 04 Feb 2017 18:07:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.33.173 with HTTP; Sat, 4 Feb 2017 18:06:40 -0800 (PST)
In-Reply-To: <20170204190635.GC80290@ernw.de>
References: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com> <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com> <20170204190635.GC80290@ernw.de>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Sun, 5 Feb 2017 13:06:40 +1100
Message-ID: <CAO42Z2zt40=Cb+ZLS-7nAooO7=neY03A=O4OpPBo-x598T6uVg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Enno Rey <erey@ernw.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L3qB1oLhY5c75ygCxm61mO1gwhw>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, IETF <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 02:07:12 -0000

On 5 February 2017 at 06:06, Enno Rey <erey@ernw.de> wrote:
> Hi,
>
> On Sat, Feb 04, 2017 at 09:32:37AM +0100, Fernando Gont wrote:
>
>
>> Everyone has agreed (including the authors of RFC2460) that EH insertion
>> has never been allowed.
>> [...]
>> > Permitting header insertion in the sense of specifying how header
>> > insertion could possibly work is of course outside the scope of
>> > advancing RFC2460.
>>
>> Explicitly allowing EH insertion would most likely be out of scope, too:
>> It completely changes a very basic aspect of IPv6.
>>
>> FWIW, I think that publishing a spec with what some have considered to
>> be ambiguous text (subsequently leading to 600+ messages on the very
>> group that specifies the protocol) would be a lousy job on our side.
>> Either explicitly ban extension header insertion, or explicitly allow it=
.
>>
>
> The first talk I gave about IPv6 was in 1999 (with an experimental IPv6 s=
tack of Windows NT and being connected to the 6Bone). I don't remember much=
 of it but I'm pretty sure I explained that the desire to restore the pre-m=
iddlebox, pre-NAT end-to-end character of the Internet was one of the main =
design drivers of IPv6 (hint: you may also look at the "Acknowledgments" se=
ction of RFC 2460).
> Quite a few IPv6 books of the time (we still have them in the library, fe=
el free to reach out for examples) explicitly mentioned end-to-end as a maj=
or property of IPv6 and many guys giving IPv6 talks & trainings since 15+ y=
ears now have it on their introductory slides. Furthermore several adjustme=
nts of the main IPv6 header (e.g. removing the checksum) and barring fragme=
ntation performed by intermediate points clearly indicate the message: "in =
general we don't want devices to mangle with packets in transit".
> So, from my personal perspective, it's painfully obvious that there was n=
ever any intent to allow the modification of IPv6 packets in transit (besid=
es very specific exceptions which were clearly described), and this has bee=
n an undisputed principle of IPv6 for a long time.
>
> So one may be tempted to ask: why do we have this discussion at all?
> Well I think the answer is quite simple: as so often in life, it's about =
agendas and politics.

I think it is much simpler than that.

People have put quite a lot of work into EH insertion and they don't
want to throw it away. That is entirely understandable, however the
specification is clear.

"With one exception, extension headers are not examined or processed
   by any node along a packet's delivery path, until the packet reaches
   the node (or each of the set of nodes, in the case of multicast)
   identified in the Destination Address field of the IPv6 header."

"The exception referred to in the preceding paragraph is the Hop-by-
   Hop Options header, which carries information that must be examined
   and processed by every node along a packet's delivery path, including
   the source and destination nodes.  The Hop-by-Hop Options header,
   when present, must immediately follow the IPv6 header."

The only modifications of an IPv6 packet in flight allowed are:

- decrement the Hop Limit
- change the Traffic Class
- change the Flow Label if the value is zero
- Hop-by-Hop EH processing.

In none of these cases is new information added to the packet,
changing the size of the packet. In all of these the negative
consequences of a failed update are the packet gets dropped, gets
lower priority per-hop handling, or is delivered to the incorrect
destination. These types of failures do not conflict with any
semantics that other protocols rely on, specifically that the source
address identifies the originator of the entire structure and initial
contents of the packet, with the possible and permitted in-flight
changes in packet contents values being explicitly identified in
RFC2460 and published updates to it.

Claiming the spec is ambiguous is trying to create a loophole that
permits the violation of the specification. That is probably viewed as
having lower cost, if successful, than redoing the work to use
encapsulation to add information to packet while also preserving the
packet's original semantics.

I think claiming "not examined or processed by any node along a
packet's delivery path" is ambiguous is pretending to know less about
something than one really does.

Regards,
Mark.


From nobody Sat Feb  4 21:04:47 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF5A1294F7; Sat,  4 Feb 2017 21:04:46 -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 autolearn_force=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 AVEuUmbtsX3v; Sat,  4 Feb 2017 21:04:44 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 86FEE1270B4; Sat,  4 Feb 2017 21:04:44 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1caF08-0008TK-M6; Sun, 05 Feb 2017 05:04:36 +0000
Date: Sun, 05 Feb 2017 14:04:33 +0900
Message-ID: <m21svd449q.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John Leslie <john@jlc.net>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
In-Reply-To: <20170204223848.GL10525@verdi>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net> <20170204223848.GL10525@verdi>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S1ftL6EJiMq2u7LE_l7-Z1M9ADQ>
Cc: ietf@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, Stefano Previdi <sprevidi@cisco.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 05:04:46 -0000

>    I have since realized that the flaws were more serious than I had
> realized; and that _only_ exhaustion of IPv4 address space could incent
> widespread deployment.

it will also take the destruction of nats, and that ain't gonna happen.

we shot ourselves in the foot and now we're left with shooting the
messengers.

randy


From nobody Sun Feb  5 01:43:01 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E91631294C6; Sun,  5 Feb 2017 01:42:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gxvI44VRbRKq; Sun,  5 Feb 2017 01:42:58 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 437221293F2; Sun,  5 Feb 2017 01:42:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 29BA649; Sun,  5 Feb 2017 10:42:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1486287773; bh=UXSnU1+4bvdqn1rSjxl hIptwPWJCm/RTmP04VoCSPDI=; b=FVQVJl0yTPeWWOEv+monXKyBM2fwVXouBxn AHe4shbPIxj0qduWF0i4IId6ZIGyvlrJLsK30FqxTiHmLYmayuu8IaZyBRVSTXHh 6ul5wMjot/4M947we37xm3y6w7xNMkLC2mnEKXZYmU0U58qYFHkyxhMmM8EC6xjr tNOCtj+4=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id g_UESnvxZCWf; Sun,  5 Feb 2017 10:42:53 +0100 (CET)
Received: from [10.22.79.216] (unknown [89.248.140.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 314AD48; Sun,  5 Feb 2017 10:42:53 +0100 (CET)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <D8DD56B7-21CF-4175-B906-FB803D119F8A@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_240FE3CE-9C4F-4E11-B73F-38CDCCEBE50E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Sun, 5 Feb 2017 10:42:49 +0100
In-Reply-To: <20170204190635.GC80290@ernw.de>
To: Enno Rey <erey@ernw.de>
References: <9c3abcb7-81f4-e23f-3b1a-3d4e97b15314@si6networks.com> <9b8383cd-f0aa-3ea2-1521-ab9cba8e50a5@si6networks.com> <20170204190635.GC80290@ernw.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dhsc_q-jmYirelC6f0PLOUEg1Jc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 09:43:00 -0000

--Apple-Mail=_240FE3CE-9C4F-4E11-B73F-38CDCCEBE50E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Enno,

> For the protocol: given the fundamental role of RFC 2460 I, too, think =
that an implementor must be able to get a clear answer to the question =
"is EH insertion allowed or not?" during its lecture, without going =
through 600+ e-mails in an archive (just to find out that "even the =
experts didn't agree on that, at the time"). So I support Fernando's =
request of
>> Either explicitly ban extension header insertion, or explicitly allow =
it.

+1

Personally I think middleboxes should not insert or remove extensions =
headers. But whatever happens, it should be explicitly stated.

Cheers,
Sander


--Apple-Mail=_240FE3CE-9C4F-4E11-B73F-38CDCCEBE50E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYlvOZAAoJEB7hi8LTyHy2rPMH/iJJAFOsmwrRPuGf6F9jRwEU
n91nZb0wfJbTw0cTjmaaPmqmQSBWIMBQdhSk8zeV1uJsbGG0E5Mka5dsHg45osRd
g7GIFqurRKLbKQHyKOnFrwq9bBLOnwOXQxP41xSWa35/LrvUzP6lCzMnV4eyPvzV
u6G5Y+ePC0OMwq0D8tIxLJu1gT12wcP5F2pqk0KqQ6/KmVy7PGXVXaxon77m2B3x
xAO/NBdMSzouOI4MJq/7Q7OIUtWKEUv/RcmfENdrj7hXInBqXIMvMuv6/0WocAzL
lleQVtT7XuMGNa0YNgSf9t3zqeuaD4t/YzM1B20OlSP17xTDLvGxCY3RJ+pV1sM=
=QfB3
-----END PGP SIGNATURE-----

--Apple-Mail=_240FE3CE-9C4F-4E11-B73F-38CDCCEBE50E--


From nobody Sun Feb  5 13:43:53 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39DA7129705; Sun,  5 Feb 2017 13:43:44 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-bmwg-virtual-net-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
Date: Sun, 05 Feb 2017 13:43:44 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NV6CXs95XlEbKV6Ru2pWwlgnJsA>
Cc: draft-ietf-bmwg-virtual-net.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Feb 2017 21:43:44 -0000

Reviewer: Joel Halpern
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-bmwg-virtual-net-??
Reviewer: Joel Halpern
Review Date: 2017-02-05
IETF LC End Date: 2017-02-15
IESG Telechat date: Not scheduled for a telechat

Summary: This document is ready for publication as an Informational
RFC.

Major issues:

Minor issues:
    The second figure in section 4.4 talks about the use of multiple
3x3 tables, but appears to show the use of multiple 4x4 tables.  This
reader found himself confused.

Nits/editorial comments: 



From nobody Sun Feb  5 18:00:02 2017
Return-Path: <gregskinner0@icloud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C30F129A80 for <ietf@ietfa.amsl.com>; Sun,  5 Feb 2017 18:00:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0fA9J_i-kMHU for <ietf@ietfa.amsl.com>; Sun,  5 Feb 2017 18:00:00 -0800 (PST)
Received: from mr11p00im-asmtp001.me.com (mr11p00im-asmtp001.me.com [17.110.69.252]) (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 66CC7129502 for <ietf@ietf.org>; Sun,  5 Feb 2017 18:00:00 -0800 (PST)
Received: from process-dkim-sign-daemon.mr11p00im-asmtp001.me.com by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OKX00H00JY5R500@mr11p00im-asmtp001.me.com> for ietf@ietf.org; Mon, 06 Feb 2017 02:00:00 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=4d515a;  t=1486346400; bh=Wq0ITX++s1TJdgSiDK+Bof2jeCTmtpcJoSBDQoNOKJM=;  h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=Mu40Fcnu9KxjUNlm/ViZURZgi/dWl/ysejTssps2Aeo67hFa4yAvideiJevIjxHcj DNxC9S3FZfCHxBzjTTKCjpj1u1DoXzKKHvt0JbE0g16mY8e4iC9mfcQBp132rZXd37 etLCVNjwGgpHeIyjpvUvszxFW2yjfd7dvS+dfLrIWNbNxWtitdDoOf99ePQONBQh8C HJcjGzNR8NFwvjU4bO1ReXmbHKK33F72qsye44IncSCrF6KPTi/c/WzCLgTHQm5p+O ADcgm0002TjgZSD3XItBcujUXSfIkgb0+UNL2rpWu9QFJ20Vid0hS/VVEMeUsB3Gt3 6YBGGezl5IwDA==
Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp001.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OKX00O9AK7Y3I00@mr11p00im-asmtp001.me.com>; Mon, 06 Feb 2017 01:59:59 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-06_01:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=3 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1603290000 definitions=main-1702060017
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
From: Greg Skinner <gregskinner0@icloud.com>
In-reply-to: <m21svd449q.wl-randy@psg.com>
Date: Sun, 05 Feb 2017 17:59:58 -0800
Content-transfer-encoding: quoted-printable
Message-id: <4A2483E9-D5B6-493D-95E7-4D095925B040@icloud.com>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net> <20170204223848.GL10525@verdi> <m21svd449q.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/voMS925FGG3FnoCxXaZgrOHeLBk>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John Leslie <john@jlc.net>, Stefano Previdi <sprevidi@cisco.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 02:00:01 -0000

On Feb 4, 2017, at 9:04 PM, Randy Bush <randy@psg.com> wrote (in =
response to John Leslie):

>=20
>>   I have since realized that the flaws were more serious than I had
>> realized; and that _only_ exhaustion of IPv4 address space could =
incent
>> widespread deployment.
>=20
> it will also take the destruction of nats, and that ain't gonna =
happen.
>=20
> we shot ourselves in the foot and now we're left with shooting the
> messengers.
>=20
> randy
>=20
>=20

Tussle in Cyberspace: Defining Tomorrow=E2=80=99s Internet

=
https://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle%20in%20Cybers=
pace%20Defining%20Tomorrows%20Internet%202005's%20Internet.pdf=


From nobody Mon Feb  6 01:27:27 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFCF127058; Mon,  6 Feb 2017 01:27:21 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Shucheng LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-harkins-owe-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148637324115.18869.12400409523655556669.idtracker@ietfa.amsl.com>
Date: Mon, 06 Feb 2017 01:27:21 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g_SEgfUdj2HrGIDAtqwPEM78wvc>
Cc: ietf@ietf.org, draft-harkins-owe.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 09:27:21 -0000

Reviewer: Shucheng LIU
Review result: Has Nits

(testing. first time using the new website tool) 

Hi all,

Sorry for being late due to vacation. Here is my review. 

I have reviewed /draft-harkins-owe-06 as part of the Operational
directorate's ongoing effort to review all IETF documents being
processed by the IESG.  These comments were written with the intent of
improving the operational aspects of the IETF drafts. Comments that
are not addressed in last call may be included in AD reviews during
the IESG review.  Document editors and WG chairs should treat these
comments just like any other last call comments.

“This memo specifies an extension to IEEE Std 802.11 to provide for
   opportunistic (unauthenticated) encryption to the wireless media.”

My overall view of the document is 'Ready with nits' for publication.

Some small ones: 

**** Technical ****

* Section 1, page 1:

>	Opportunistic Wireless Encryption

“Opportunistic” is an odd word in this context the common English
definition is “to do at every opportunity” i.e. “whenever you can” if
this is the 6th draft it may be understood, but will raise questions
about when to apply it and when not to apply it.

* Section 1.3, page 3:
>	As the name implies, OWE provides opportunistic encryption, or
>	encryption of traffic without authentication of endpoints.  OWE was
>	presented to the IEEE 802.11 Working Group for consideration but an
>	"all or nothing" approach to cryptographic protection has been
>	adopted by that body, and OWE is a stop in between "all" and
>	"nothing".

Here explains the opportunity is defined by un-authenticated endpoints
this may define the title better but could lead to claims of once
hacked synthetic or hidden data for the hackers benefit is offered.

* Section 2, page 4:
Seems to contradict the sentence in 1.3; Implying the AP is trusted at
least by SSID. Clause 1.3 appears not totally correct. 

* Section 3, page 5:
This section makes sense to me but confirms it is not totally
opportunistic. As it is only applied when the SSID and BSSID are
confirmed and either open (not encrypted) or not fully trusted (or the
encryption may be known). Seems to contradict the sentence in 1.3.
Clause 1.3 appears need to say a bit more, it only to ask the reader
to read sections 2 & 3.

The technical details seem correct; It may protect against hacker
eavesdropping. 

This does not protect against AP spoofing or piggy-in-the-middle
attacks. It makes authorized eavesdropping harder. So once the AP is
copied it may be harder to find the culprit. Good business should
change the public SSID regularly or employ layer 3 end-to-end
encryption. 


**** Editorial ****

* Section 4.4, page 8:
s/concatentation/concatenation/

* Section 7, page 10:
s/wirless/wireless/


Regards,
Will



From nobody Mon Feb  6 03:32:39 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A695C12952F; Mon,  6 Feb 2017 03:32: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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 Deh-izE0Nkc6; Mon,  6 Feb 2017 03:32:31 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 48696129522; Mon,  6 Feb 2017 03:32:31 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C90A62CCFF; Mon,  6 Feb 2017 13:32:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4pStH5ftdeJI; Mon,  6 Feb 2017 13:32:29 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 5DBC92CC9B; Mon,  6 Feb 2017 13:32:29 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
Date: Mon, 6 Feb 2017 13:32:29 +0200
Message-Id: <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cIzyiD9P2Sk23A71o-ZBzvzx_iI>
Cc: draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org, gen-art@ietf.org, ccamp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 11:32:33 -0000

--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Pete. Authors, any comments?

Jari


--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E
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

iQIcBAEBCgAGBQJYmF7NAAoJEM80gCTQU46qFGoP/1b4R8OjCZxXHEB929EL2QaT
jgV6eZoJCCY8b1gQU7YrzSpfNEYD8KJvpbXJOC4xFsvu644S8m4VSTjEAX/DJ2TQ
pOakW/itbv50uwrcYAoKNMQ3qRryAjI66YM1NfHDiL7II15vc9DFy7KMS4grWdGT
h+hIhfefaLCa1cxpGE1rsGAsKW+zpHnEt4wm5hP1BKv9UtDuI6DZ0f+yAbAtRstH
J60Ovd0v8/4Lxqf/CnrI4gI713iYhOCQEv0+TjtsWtWAY6/UNG27dlKgAxpg7qcg
j9scb63grTM8uLNf8rUCYjTe7z3YIaAry6c2bnjuGvin1rVkRzF0I8jz719c6ZND
t78xEQwvEcZmwPhlnb9+6xgpgHDYQAgNsbv6nn6bsQWs7Dt/DYtyG/aLEYHST5Jy
HvSYFxU9ObmYG2ss8pqltJALbBkadYcSW04z3vPGM6Odglq72+d44w6pvl1Eu4Ow
QBDOXH6xuHBh0TJh/4kpg5QJo4706E+30x5Oy1z/hOZnYaDIErHBueWDfp86pHrG
Gq5Aye9jhpeBUuCjiAz60etcXMFCUKunO77o3sClCYWknKpb1LKscy4/BBbqfnO8
yJAZYuftq0qxPZyQR+egw/dmNFWotC/MrfPpQudQ/27/9TX5Kvt88ueUtLHFZN+E
jvxZCm++jeinYqGaXlaU
=MqAt
-----END PGP SIGNATURE-----

--Apple-Mail=_11418C2A-B04B-46EB-B579-9C9D8C7A495E--


From nobody Mon Feb  6 05:37:53 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01ABC129D7A; Mon,  6 Feb 2017 05:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2a0ezxfJ04mf; Mon,  6 Feb 2017 05:37:43 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 B0AE5129D6B; Mon,  6 Feb 2017 05:37:42 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-42-58987c242f2a
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.183.63]) by  (Symantec Mail Security) with SMTP id 54.70.22993.42C78985; Mon,  6 Feb 2017 14:37:40 +0100 (CET)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.63) with Microsoft SMTP Server (TLS) id 14.3.319.2; Mon, 6 Feb 2017 14:36:48 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=PSkq5iPphyhTo00k+E8Rdo2mzZVEUzFRw0yBt7u7l/o=; b=jacihOEUHHyRqP/h7NTRJNr8MeN0GTLCTnrACZJ8oa/mIKvegYxxQVUhXjf6dx3w+Ijl89WEqj7V7px1qc/WsOv1bNHg1hGq71I6Tm55F7ZXBlV1UCQ+yr1NT5V9adSWQiXNIJvPop2Oj8RiZ+QYMK5wxyCFIReN04yf0RRvQ50=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0996.eurprd07.prod.outlook.com (10.162.37.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Mon, 6 Feb 2017 13:36:46 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Mon, 6 Feb 2017 13:36:46 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Jari Arkko <jari.arkko@piuha.net>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9A=
Date: Mon, 6 Feb 2017 13:36:46 +0000
Message-ID: <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
In-Reply-To: <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 2528a4d3-45de-45cb-4f9f-08d44e953246
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0996;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0996; 7:WZxsaZH8S8PYhlhZR3FPmyS0eybqwum5QuN8YMhlGqnni70vB1Y1qfEOo9lJCdF2hc+Do36Zu45RK5JpPdg5BgkHup/O+gDJED5ZeKfv9pXqyNH/aUC5lbC1tNnQfSJEhJVcpJsVCZFcoxn5gUTjJRQFjxkNd9+M5qkHeGfu7GsJ77itEO2GceVF+ZFIQ1blP0CuKIWVCGGlnwdHI+lt1VpbJI9Y0KIAjGj0WZ8yINCHYk0Nobhgl/0v+lmw1nNkrABYJ8ncvBlkaIbEG9QVc901GJG053c7ClRYSAl61yFLc2Hh74uri4+GD0VoIcpcbTw1UdAiiAoRucAOGvx0tCxnc4Pw0IIHghKZOSILyn4lMOtQ5Jso8lPjwVSTw3cG4zsnGb+XPB3Ld8rBOUXebaYNVso57YN9RyHSehIBWBcCmWI4raFo9DoF/bVwDbhedqCaIoRb8g5oeeO6itUYbm7eCqf5ktT9e8DB6ydDVoshshN4Y+S07jyZU+O1tUDv4/ZXMlarCIP48GzYca/HxA==
x-microsoft-antispam-prvs: <AM2PR07MB099690999327245292673B4EF0400@AM2PR07MB0996.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(20170203043)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123558025)(20161123562025)(20161123560025)(20161123555025)(6072148); SRVR:AM2PR07MB0996; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0996; 
x-forefront-prvs: 0210479ED8
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(51914003)(13464003)(189002)(2900100001)(81156014)(8936002)(74316002)(81166006)(2950100002)(53936002)(8676002)(50986999)(38730400001)(6436002)(76176999)(54356999)(6506006)(25786008)(77096006)(189998001)(7696004)(5001770100001)(97736004)(9686003)(99286003)(54906002)(55016002)(229853002)(92566002)(5660300001)(230783001)(86362001)(6116002)(3280700002)(102836003)(7736002)(6246003)(3846002)(2906002)(105586002)(4326007)(122556002)(68736007)(305945005)(3660700001)(101416001)(66066001)(33656002)(106116001)(106356001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0996; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2017 13:36:46.4613 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0996
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfSzUcRzH9/39fnf9ztz2dZ4+roetm7+EirKbQq2H2WKqf7LK6spvno/u xw3VkshD1JXOY4W6RYQxOkXEKDWhRiTFuHm61SxTmSJ3X2399/5+Xu/v+/P5fPdlaUmRQMqG KWM5lVIRKRNaMAWBeh8Xxwv5gdt+6DzkhjtDjPze72pKPjA7z8gna4sZeX5LuVDeP5BC7xH6 6nSLlG+DLk/oe187iQ7Txy12B3ORYWpOtdX7tEXoQo4oZlIa35FbjJKQxjYTiVjAO2ClZVqY iSxYCa5GUGJsRuTwCsHl4npkcjE4m4bvuZYE5FBgzOoyAwnuRPCpYFWzrBB7gqHdz1S2wUeg O0VPmfw0Hl8NWs6mTMAaH4IXH+rWEZMfLD7tpYn2hAXjLEOaOYJm/r05X4xPQmVtj4D0ugS/ ajQCUy8R9oJnE86mMsJ28PPNY3M8je1h2FBMkc0w6JpJPGBbmJlYFhD/GahJbVzzbIa+ikLK FAnYH+qaNpGyPyxd7zSPD7ibgda3RkRABOhTe9fuOkF6R+GaqYyCha9jDAEbQNvUwxAwIYCU oo8MWYCDsqpURB5CCp/7M5AGORX+NzjRrjCkvS0kegs8LDXShea3sILXBQamBDEVyJbneD4q xM3dlVOFneX5aKWrkoutQ6tfpq1+yaURVRr3tiPMIpmleM4rL1AiUKj5hKh2BCwtsxEHqfMD JeJgRUIip4o+pYqL5Ph2tJ5lZPZij0ejxyQ4RBHLRXBcDKf6RylWJE1CArc0Q+UTD034zvHk pvKjaVcPODqMdl5UcSN3z6UmX7NK58VBpZ12wye+6bVL+l3e6beSqpwHB/JvzMW39mX7J85Y P+9yaGie2v+gLUbtXB/k5PqH2Sidc1+8kpF88DznNxUw0s0HjNmH2mRpfV6W1Azkxd2c7xjc p12ZDs991/tFxvChiu1OtIpX/AVgPjrgLgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LsADx-BVpEWFIkfEg4s4PPjjMEM>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 13:37:45 -0000

Hi Jari, Pete,

First of all thanks for the accurate review.

All the nits/editorial comments are correct and will be fixed.

Regarding the minor issue:=20

> 4.1.1:
>=20
> The figure is a bit confusing: There might not exist a "Max Slot Width at=
 Priority
> 7" if bit 7 is clear in the Priority field, correct?
> Perhaps it would be better to just show that as "..." or "Max Slot Width =
at
> Priority n". The thing is, it might only be a single value, followed by t=
he
> padding, so having the second value in there might be misleading. (Perhap=
s
> similar constructs are used in other MPLS docs and people will understand=
. But
> it took me a while to figure it out.)
>=20

it was difficult to express in the figure the fact that only some of the pr=
iorities are advertised. As you said it could be one, two or any number up =
to 8.=20
What about a single field (with ~ on the borders to indicate that it can ha=
ve variable length) saying "Max Slot Width at Prio n" and then say that 16 =
bits are used for each prio and when an odd number of priorities is used th=
e field is padded to line up with multiples of 32 bits?

> The discussion of Priority was very confusing for me. In the third senten=
ce, do
> you mean, "A bit is set (1) corresponding to each priority represented in=
 the
> sub-TLV, and clear (0) for each priority not represented in the sub-TLV"?=
 I don't
> understand the MUST/MUST NOT as you had it. And I don't understand the
> last sentence at all. Are you trying to say, "The leftmost bit (priority =
level 0)
> MUST be set, and priority level 0 MUST be advertised in the sub-TLV."?
> Otherwise, I don't get it.

It means that if the priority field is set to e.g. 10010010 in the followin=
g you would find 4 fields indicating respectively: Max Slot Width at Priori=
ty 0, Max Slot Width at Priority 3, Max Slot Width at Priority 6 and since =
they are 3 a 16 bits padding to 32 bits.=20
It also means that at least one priority must be advertised (i.e. priority =
00000000 is not allowed).

>=20
> I don't understand the MAY in the last sentence. Does that mean that I MA=
Y
> also set it to the highest possible nominal central frequency supported b=
y the
> link? I don't understand what that sentence is trying to tell me.
>

An example is provided in section 4.1.2, where the available range goes fro=
m -2 to +8 but the range supported by the link goes from -9 to +11. The sen=
tence means that even if not available it could be possible to indicate als=
o n=3D-9 to indicate the starting point of the range supported by the link.=
=20

  " In this example, it is assumed that the lowest nominal central
   frequency supported is n=3D -9 and the highest is n=3D11. Note they
   cannot be used as a nominal central frequency for setting up a LSP,
   but merely as the way to express the supported frequency range."

I'm ok with dropping the sentence.

Thank you
Daniele=20

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: luned=EC 6 febbraio 2017 12:32
> To: Pete Resnick <presnick@qti.qualcomm.com>
> Cc: gen-art@ietf.org; draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.or=
g;
> ccamp@ietf.org; ietf@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-=
07
>=20
> Thanks for your review, Pete. Authors, any comments?
>=20
> Jari


From nobody Mon Feb  6 06:08:56 2017
Return-Path: <sakimura@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BAF129D9E; Mon,  6 Feb 2017 06:08:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGFlx4iSpGID; Mon,  6 Feb 2017 06:08:51 -0800 (PST)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 92370129D9B; Mon,  6 Feb 2017 06:08:47 -0800 (PST)
Received: by mail-wm0-x241.google.com with SMTP id u63so22148660wmu.2; Mon, 06 Feb 2017 06:08:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A4rhqcW25zvyCoENP7OoIdv6Zho/7dwIh2/yN0yP9BY=; b=q4AA87o5KvhbPCo8DNGGh35B0t7pl5B1SxCZafGGlsoSIGuequFnZXlPLjgi0IyCuz JXwZCeTs2b2FvI8C45ouwsOIBWDJWoQE6CD1TGE6pbCTmZDVeyMoSdkiFDBDik2cxOZu VZrYtjSfB0KBnQ+P44Uyv69vQcqn40ZKgc7GfD6R25A4FxdVM/kBZOqCOyfdUbICM7xV TY9ij9MaFVP4V5JbOsH92EMZv/BsVhd2zOMwxlubz1TNxq3swoKPfwe+30XYQqMk9/dk kz9ctqdWokjuCRkk8FRetjBpU2Lefcn+gmEN+T6NIodCA/UEYQx7bkWRKsmAwhFQgtyr Sp1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A4rhqcW25zvyCoENP7OoIdv6Zho/7dwIh2/yN0yP9BY=; b=nFdbVyrJpt8rZvUcesUa70gniScSQ0jrQgvl0WgZpxmUSJ/NHvTGM8JeY/gMuLmXlx eEOfTVdOYW6ZhYFxNMmlJhmdi1c9FMjfqD80/locfoncuYpT2mIr1j9jDOLvx0mxdUl7 IA89x6pg7KLF95k4ql5ljHkyMCIhw5nNUcpP33iagsOWrReJydu8RahJ2Si6rJCrZmJD da3K9h3phKzQfgBymw1hmrJ4UUpyiimavI9YNBFr1Nt5oTLo/2xWPzUObc6buNd7y/ft THJ+kIsEwLcLTxNMPLwZHSs/q04/slXYT2RgevS7Q0pxIb0e75s4x3M7lYRtW7K7Wbr5 HhVA==
X-Gm-Message-State: AMke39mzS1mywk73Y8lVg7I6TGXxeOPlc5V1fx/MVFI+0TjEU0CwjNtRhg7z2pS5gPFc4wXbzLQH5UUvPr2Zaw==
X-Received: by 10.28.38.2 with SMTP id m2mr8390283wmm.44.1486390125875; Mon, 06 Feb 2017 06:08:45 -0800 (PST)
MIME-Version: 1.0
References: <148581788158.29828.4591033587037530374.idtracker@ietfa.amsl.com> <3a6b8cee-ff29-323e-9042-5df6e71a8d81@free.fr>
In-Reply-To: <3a6b8cee-ff29-323e-9042-5df6e71a8d81@free.fr>
From: Nat Sakimura <sakimura@gmail.com>
Date: Mon, 06 Feb 2017 14:08:34 +0000
Message-ID: <CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com>
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-11.txt> (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard
To: Denis <denis.ietf@free.fr>, ietf@ietf.org,  IETF-Announce <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c03fb967359de0547dd2b76
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oURo-vRKTKMxT5jycl96k1mbX88>
Cc: draft-ietf-oauth-jwsreq@ietf.org, oauth-chairs@ietf.org, oauth@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 14:08:54 -0000

--94eb2c03fb967359de0547dd2b76
Content-Type: text/plain; charset=UTF-8

Thanks Denis. Here is my proposed disposition on your comments.

On Fri, Feb 3, 2017 at 8:11 PM Denis <denis.ietf@free.fr> wrote:

> *Comments on I-D Action: draft-ietf-oauth-jwsreq-11.txt*
>
>
>
> Two editorial comments first :
>
>
>
> 1. Guidance is a mass noun, not a count noun, plural doesn't make sense.
> Please change "guidances" into "guidance" twice in Section 11.
>

Accepted.
Thanks.

>
>
> 2. In Section 12 : Please remove my name (Denis Pinkas) from this section.
>

Accepted.

>
>
> Other comments:
>
>
>
> 3. Section 1.1 (from boiler plate) states: The key words "MUST", "MUST
> NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
> "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
> be interpreted as described in RFC 2119 [RFC2119].
>
> There is not a single other occurrence of the word SHALL within this
> document. In such case, I wonder how this document can be normative.
> There are however many (useful) "non-normative examples. A non-normative
> example does not replace requirements.
>
> Noted.
There are bunch of MUST. At IETF we usually prefer MUST to SHALL, unlike in
ISO.

>
>
> Section 4 states:
>
>
>
> *   A Request Object (Section 2.1) is used to provide authorization*
>
> *   request parameters for an OAuth 2.0 authorization request.  It*
>
> *   contains OAuth 2.0 [RFC6749] authorization request parameters*
>
> *   including extension parameters**.  *
>
>
>
> RFC 6749 contains 75 pages, but does not contain a single occurrence of
> the wording "authorization request parameter" nor of "extension parameter".
> There should be either references to one or more specific sections of this
> document or, even better, a list of the mandatory/recommended/possible
> authorization request parameters as well as a list of
> mandatory/recommended/possible extension parameters should be included in
> this document.
>
>
> A clear distinction should be made between the parameters used to
> authenticate the request and the other ones.
>

Reject.
There are 4 flows in RFC6749. In each flow, there is a sub-section
dedicated to the Authorization request.
In them, the parameters used in the authorization request are very clearly
indicated. For example,

4.1.1 <https://tools.ietf.org/html/rfc6749#section-4.1.1>.
Authorization Request

   The client constructs the request URI by adding the following
   parameters to the query component of the authorization endpoint URI ...


It is very difficult to miss.

Then, the possibility for the extension parameters are discussed in 8.2.
Needless to say, those extension parameters are going to be discussed in
other specifications.
Thus, it would be misleading just to say the parameters defined in 4.1.1,
4.2.1, etc.
As an editor, I feel better with the current language because it is at
least not wrong nor misleading.


>
>
> 4. The introduction states on page 4:
>
>
>
>      (a) (integrity protection) The request can be signed so that the
> integrity of the request can be checked ;
>
>
>
> This should be changed into:
>
>
>
>      (a) (integrity protection) The request can be authenticated either
> using a digital signature or using encryption under a secret key
>           so that the integrity of the request can be checked ;
>

Reject.
This paragraph is talking about the integrity protection and not the source
authentication.
And even for source authentication, saying that encryption under a secret
key is not accurate as it was discussed earlier in the WG mail.

I am not sure if "Introduction" needs to state everything that is explained
later. The idea of introduction probably is to give main points. The list
is not an exhaustive list of the benefit of using JWT as the authorization
request format. For example, being able to encrypt the request, which is
not listed there, has an advantage of preventing MITB to eavesdrop the
request. So I think it is ok as is.



>
>
> 5. The introduction states on page 4:
>
>
>
> (d) (collection minimization) The request can be *signed* by a third
> party attesting that the authorization request is compliant to certain
> policy.
>
> The request is not *signed* by a third party.
>
However, later on, there is the following explanation:
>
>
>
>    In addition, it allows requests to be prepared by a third party so
> that a client application cannot request
>    more permissions than previously agreed.
>
>
>
> If it is the intent, the sentence should be rephrased as:
>
>
>
> (d) (collection minimization) The request can be *verified* by a third
> party attesting that the authorization request is compliant to certain
> policy.
>
>
>
Reject
The third party indeed signs the request on behalf of the client as the
result of verification that the permission is the same as previously
agreed.

>
>
> 6. Section 10.1. the text states:
>
>
>
> *   When sending the authorization request object through "request"*
>
> *   parameter, it MUST either be signed using JWS [RFC7515] or encrypted*
>
> *   using JWE [RFC7516] with then considered appropriate algorithm.*
>
>
>
> The wording" with then considered appropriate algorithm" is too vague.
> This should be changed into:
>
>
>
> *   When sending the authorization request object through "request"*
>
> *   parameter, it MUST either be signed using JWS [RFC7515] or encrypted*
>
> *   using JWE [RFC7516] using a symmetric key algorithm.*
>
>
>
Reject.
In the above sentence, "*with then considered appropriate algorithm*"
 applies both on JWS and JWE.
The intent of the phrase is that a vulnerable algorithm should not be used.

Also, I do not understand why the algorithm has to be symmetric key
algorithm.

>
>
> 7. Section 10.2 states:
>
>
>
>    This means that the request object is going to be prepared fresh each
>
>    time an authorization request is made and caching cannot be used.
>
>
>
> What are the implications ? Is it required/recommended to use a nonce ?
> The text should be made clearer.
>
> Reject.
The implication is given right after the sentence. There is no variable
called "nonce" in RFC6749. Since this document is just defining another
encoding method for OAuth 2.0 authorization request as a framework, it does
not mandate these. An extension specification should define those
requirements.

>
>
> 8. Section 10.3 states:
>
>
>
> 10.3.  Request Source Authentication
>
>
>
>    The source of the Authorization Request MUST always be verified.
>
>    There are several ways to do it in this specification.
>
>
>
>    (a)  Verifying the JWS Signature of the Request Object.
>
>
>
> It seems that the case of using a JWE encrypted using a secret key
> algorithm has been forgotten here. Please add it.
>
Accepted with modification.
You mean, symmetric key algorithm, is that right? I would add "or verifying
that the symmetric key for the JWE encryption is a correct one"

>
>
> 9. Section 10.3 states at its very end:
>
>
>
>    An extension specification
>
>    should be created as a preventive measure to address potential
>
>    vulnerabilities that have not yet been identified.
>
>
>
> Writing a document for vulnerabilities that have not yet been identified
> is speculative. It would rather be better
> either to remove this sentence or to explain what is meant by it.
>
Reject.
It is referring to the first paragraph of the sub-section. Also, precaution
when security is in question is a good thing.

> 10. Section 11.1 states:
>
>
>
> *11.1.  Collection limitation*
>
>
>
> *   When the Client is being granted access to a protected resource*
>
> *   containing personal data, the Client SHOULD limit the collection of*
>
> *   personal data to that which is within the bounds of applicable law*
>
> *   and strictly necessary for the specified purpose(s).*
>
>
>
> The *presentation* of personal data should be limited whether or not the
> protected resource contains personal data.
>

> It is proposed to change this text into:
>
>
>
> *   When the Client requests an access to a protected resource, the Client*
>
> *   SHOULD limit the presentation of personal data to that which is within
> *
>
> *   the bounds of applicable law and strictly necessary for the specified *
>
> *   purpose(s).*
>
Reject.
You are not getting what OAuth does. The party that holds personal data is
the authorization server / resource.
It is not the client. The client is the party who is getting those
"resources" which may contain personal data.
Yes, the client can provide some personal data to the resource depending on
what that resource endpoint is, but that is out of scope for OAuth.
As far as OAuth is concerned, what is being sent from the client to the
resource is the access token.

>
>
> 11. Section 11.2.1 states:
>
>
>
> 11.2.1.  Request Disclosure
>
>
>
>    This specification allows extension parameters.
>
>
>
> It would be useful to name either all of them or some of them. RFC 6749 is
> not crystal clear about this.
>
Noted.
RFC6749 only defines how to define extension parameters.
This specification draws from OpenID Connect for some examples of extension
parameters such as nonce.
See section 4 for example.

>
>
>
> Denis Pinkas (DP Security Consulting SAS)
>
>
> ==============================================================
>
>
>
> The IESG has received a request from the Web Authorization Protocol WG
> (oauth) to consider the following document:
> - 'The OAuth 2.0 Authorization Framework: JWT Secured Authorization
>    Request (JAR)'
>   <draft-ietf-oauth-jwsreq-11.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to theietf@ietf.org mailing lists by 2017-02-13. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    The authorization request in OAuth 2.0 described in RFC 6749 utilizes
>    query parameter serialization, which means that Authorization Request
>    parameters are encoded in the URI of the request and sent through
>    user agents such as web browsers.  While it is easy to implement, it
>    means that (a) the communication through the user agents are not
>    integrity protected and thus the parameters can be tainted, and (b)
>    the source of the communication is not authenticated.  Because of
>    these weaknesses, several attacks to the protocol have now been put
>    forward.
>
>    This document introduces the ability to send request parameters in a
>    JSON Web Token (JWT) instead, which allows the request to be JWS
>    signed and/or JWE encrypted so that the integrity, source
>    authentication and confidentiality property of the Authorization
>    Request is attained.  The request can be sent by value or by
>    reference.
>
>
>
>
> The file can be obtained viahttps://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/
>
> IESG discussion can be tracked viahttps://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (Informational - IETF stream)
>     rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informational - IETF stream)
>     rfc6973: Privacy Considerations for Internet Protocols (Informational - IAB stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
>
>
> _______________________________________________
> OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
-- 

Nat Sakimura

Chairman of the Board, OpenID Foundation

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

<div dir=3D"ltr">Thanks Denis. Here is my proposed disposition on your comm=
ents.=C2=A0<br><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Fri, Feb =
3, 2017 at 8:11 PM Denis &lt;<a href=3D"mailto:denis.ietf@free.fr">denis.ie=
tf@free.fr</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg">
    <div class=3D"m_5262665161593131067moz-cite-prefix gmail_msg">
     =20
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg"><b class=3D"gma=
il_msg">Comments on I-D
            Action:
            draft-ietf-oauth-jwsreq-11.txt</b><u class=3D"gmail_msg"></u><u=
 class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">Two editorial
          comments first :<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"=
></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span lang=3D"EN-US" class=3D"gmail_=
msg">1. </span><span style=3D"font-family:Arial" lang=3D"EN-US" class=3D"gm=
ail_msg">Guidance is a mass noun, not a count noun,
          plural doesn&#39;t make sense.
          Please change &quot;guidances&quot; into &quot;guidance&quot; twi=
ce in Section
          11.</span></p></div></div></blockquote><div><br></div><div>Accept=
ed.=C2=A0</div><div>Thanks.=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_52=
62665161593131067moz-cite-prefix gmail_msg"><p class=3D"MsoNormal gmail_msg=
"><span style=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg"><u c=
lass=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">2. In Section 1=
2 :
          Please remove my name (Denis
          Pinkas) from this section.</span></p></div></div></blockquote><di=
v><br></div><div>Accepted. =C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_52=
62665161593131067moz-cite-prefix gmail_msg"><p class=3D"MsoNormal gmail_msg=
" style=3D"margin-top:6.0pt"><span style=3D"font-family:Arial" lang=3D"EN-U=
S" class=3D"gmail_msg"> <u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">Other comments:=
<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=
3.
          Section 1.1 (from boiler
          plate) states: </span><span lang=3D"EN-GB" class=3D"gmail_msg">Th=
e key words &quot;MUST&quot;, &quot;MUST NOT&quot;,
          &quot;REQUIRED&quot;, &quot;SHALL&quot;, &quot;SHALL NOT&quot;,
          &quot;SHOULD&quot;, <br class=3D"gmail_msg">
          &quot;SHOULD NOT&quot;, &quot;RECOMMENDED&quot;,
          &quot;MAY&quot;, and &quot;OPTIONAL&quot; in this document are to=
 be
          interpreted as described in RFC 2119 [RFC2119].<u class=3D"gmail_=
msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg">There is not a
          single other occurrence of the
          word SHALL within this document. In such case, I wonder how
          this document can be
          normative. <br class=3D"gmail_msg">
          There are however many (useful) &quot;</span><span lang=3D"EN-GB"=
 class=3D"gmail_msg">non-normative examples. A non-normative
          example does not replace
          requirements.<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></=
u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg"></span></p></di=
v></div></blockquote><div>Noted.=C2=A0</div><div>There are bunch of MUST. A=
t IETF we usually prefer MUST to SHALL, unlike in ISO. =C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"g=
mail_msg"><div class=3D"m_5262665161593131067moz-cite-prefix gmail_msg"><p =
class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span style=3D"fon=
t-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_=
msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg">Section 4 state=
s:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>A
            Request Object (Section 2.1)
            is used to provide authorization<u class=3D"gmail_msg"></u><u c=
lass=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>request
            parameters for an
            OAuth 2.0 authorization request.<span class=3D"gmail_msg">=C2=
=A0 </span><span style=3D"background:aqua" class=3D"gmail_msg">It<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0
            </span>contains OAuth 2.0 [RFC6749] authorization request
            parameters<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></b></p>
      <p class=3D"MsoNormal gmail_msg"><b class=3D"gmail_msg"><span lang=3D=
"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </span>i=
ncluding
            extension parameters</span></b><b class=3D"gmail_msg"><span lan=
g=3D"EN-GB" class=3D"gmail_msg">.<span class=3D"gmail_msg">=C2=A0 </span><u=
 class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"MsoNormal gmail_msg"><b class=3D"gmail_msg"><span style=
=3D"font-family:Courier" lang=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-GB" class=3D"gmail_msg">RFC 6749 contains 75 pages, but does not
          contain a single occurrence of
          the wording &quot;authorization request parameter&quot; nor of
          &quot;extension
          parameter&quot;. <br class=3D"gmail_msg">
          There should be either references to one or more specific
          sections of this document or, even better, a list of the
          mandatory/recommended/possible <br class=3D"gmail_msg">
          authorization request parameters as well as a
          list of mandatory/recommended/possible extension parameters
          should be included
          in this document.</span></p>
      <p class=3D"MsoNormal gmail_msg"><font face=3D"Arial" class=3D"gmail_=
msg"><br class=3D"gmail_msg">
        </font></p>
      <p class=3D"MsoNormal gmail_msg"><font face=3D"Arial" class=3D"gmail_=
msg">A clear distinction should
          be made between the parameters used to authenticate the
          request and the other ones.</font></p></div></div></blockquote><d=
iv><br></div><div>Reject.=C2=A0</div><div>There are 4 flows in RFC6749. In =
each flow, there is a sub-section dedicated to the Authorization request.=
=C2=A0</div><div>In them, the parameters used in the authorization request =
are very clearly indicated. For example,=C2=A0</div><div><br></div><div><pr=
e class=3D"inbox-inbox-newpage" style=3D"font-size:13.3333px;margin-top:0px=
;margin-bottom:0px"><span class=3D"inbox-inbox-h4" style=3D"line-height:0pt=
;display:inline;font-size:1em;font-weight:bold"><h4 style=3D"line-height:0p=
t;display:inline;font-size:1em"><a class=3D"inbox-inbox-selflink" href=3D"h=
ttps://tools.ietf.org/html/rfc6749#section-4.1.1" style=3D"color:black;text=
-decoration:none">4.1.1</a>.  Authorization Request</h4></span>

   The client constructs the request URI by adding the following
   parameters to the query component of the authorization endpoint URI ... =
</pre><pre class=3D"inbox-inbox-newpage" style=3D"font-size:13.3333px;margi=
n-top:0px;margin-bottom:0px"><br></pre>It is very difficult to miss. </div>=
<div><br></div><div>Then, the possibility for the extension parameters are =
discussed in 8.2. Needless to say, those extension parameters are going to =
be discussed in other specifications.=C2=A0</div><div>Thus, it would be mis=
leading just to say the parameters defined in 4.1.1, 4.2.1, etc.=C2=A0</div=
><div>As an editor, I feel better with the current language because it is a=
t least not wrong nor misleading.=C2=A0</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_=
msg"><div class=3D"m_5262665161593131067moz-cite-prefix gmail_msg"><p class=
=3D"MsoNormal gmail_msg">
        <span style=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg=
"><u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg">4. The
          introduction states on page 4:<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"><=
/u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">=C2=A0=C2=A0=C2=A0=C2=A0 (a) (integrity pr=
otection) The
          request can be signed so that the
          integrity of the request can be checked<span class=3D"m_526266516=
1593131067delete gmail_msg"> </span>;
        </span><span lang=3D"EN-US" class=3D"gmail_msg"><u class=3D"gmail_m=
sg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">This should be changed into:<u class=3D"gm=
ail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">=C2=A0=C2=A0=C2=A0=C2=A0 (a) (integrity pr=
otection) The
          request can be authenticated either using
          a digital signature or using encryption under a secret key <br cl=
ass=3D"gmail_msg">
          =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 so that th=
e
          integrity of the request can be checked<span class=3D"m_526266516=
1593131067delete gmail_msg"> </span>;</span></p></div></div></blockquote><d=
iv><br></div><div>Reject.=C2=A0</div><div><div>This paragraph is talking ab=
out the integrity protection and not the source authentication.=C2=A0</div>=
<div>And even for source authentication, saying that encryption under a sec=
ret key is not accurate as it was discussed earlier in the WG mail.=C2=A0</=
div></div><div><br></div><div>I am not sure if &quot;Introduction&quot; nee=
ds to state everything that is explained later. The idea of introduction pr=
obably is to give main points. The list is not an exhaustive list of the be=
nefit of using JWT as the authorization request format. For example, being =
able to encrypt the request, which is not listed there, has an advantage of=
 preventing MITB to eavesdrop the request. So I think it is ok as is.=C2=A0=
</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div b=
gcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_526=
2665161593131067moz-cite-prefix gmail_msg"><p class=3D"MsoNormal gmail_msg"=
><span style=3D"font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">
        </span><span lang=3D"EN-US" class=3D"gmail_msg"><u class=3D"gmail_m=
sg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">=C2=A0</span><span style=3D"font-family:Ar=
ial">=C2=A0</span></p>
      <p class=3D"MsoNormal gmail_msg" style=3D"margin-top:6.0pt"><span sty=
le=3D"font-family:Arial" lang=3D"EN-GB" class=3D"gmail_msg">5. The
          introduction states on page 4:<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">(d)
          (collection minimization)
          The request can be <b class=3D"gmail_msg">signed</b> by a third p=
arty attesting
          that the
          authorization request is compliant <span class=3D"m_5262665161593=
131067delete gmail_msg">to</span></span><span lang=3D"EN-US" class=3D"gmail=
_msg"> </span><span style=3D"font-family:Arial" lang=3D"EN-US" class=3D"gma=
il_msg">certain policy.<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></=
u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Arial" lang=3D"EN-US" class=3D"gmail_msg">=
The
          request is not <i class=3D"gmail_msg">signed</i>
          by a third party. <br class=3D"gmail_msg"></span></p></div></div>=
</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=
=3D"#000000" class=3D"gmail_msg"><div class=3D"m_5262665161593131067moz-cit=
e-prefix gmail_msg"><p class=3D"m_5262665161593131067MsoPlainText gmail_msg=
"><span style=3D"font-size:12.0pt;font-family:Arial" lang=3D"EN-US" class=
=3D"gmail_msg">However,
          later on, there is the following explanation:<u class=3D"gmail_ms=
g"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </span>In
          addition, it allows requests to be
          prepared by a third party so that a client application cannot
          request
          <br class=3D"gmail_msg">
          =C2=A0=C2=A0 more permissions than <span class=3D"gmail_msg">pr</=
span>eviously
          agreed.<span class=3D"gmail_msg">=C2=A0 </span><u class=3D"gmail_=
msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Arial;color:#222222" lang=3D"EN-US" class=
=3D"gmail_msg">If it is the
          intent, the sentence should be rephrased as:<u class=3D"gmail_msg=
"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Arial;color:#222222" lang=3D"EN-US" class=
=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u>=
</span></p>
      <p class=3D"MsoNormal gmail_msg"><span style=3D"font-family:Arial" la=
ng=3D"EN-US" class=3D"gmail_msg">(d)
          (collection minimization)
          The request can be <b class=3D"gmail_msg">verified</b> by a third=
 party attesting
          that the
          authorization request is compliant <span class=3D"m_5262665161593=
131067delete gmail_msg">to</span></span><span lang=3D"EN-US" class=3D"gmail=
_msg"> </span><span style=3D"font-family:Arial" lang=3D"EN-US" class=3D"gma=
il_msg">certain policy.<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></=
u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0</span></p></div></div></blockquote><div>Reject</div>=
<div>The third party indeed signs the request on behalf of the client as th=
e result of verification that the permission is the same as previously agre=
ed. =C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" tex=
t=3D"#000000" class=3D"gmail_msg"><div class=3D"m_5262665161593131067moz-ci=
te-prefix gmail_msg"><p class=3D"m_5262665161593131067MsoPlainText gmail_ms=
g"><span style=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=
=3D"EN-US" class=3D"gmail_msg"><u class=3D"gmail_msg"></u><u class=3D"gmail=
_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">6. Section
          10.1. the text states:<u class=3D"gmail_msg"></u><u class=3D"gmai=
l_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>When sending the
            authorization request
            object through &quot;request&quot;<u class=3D"gmail_msg"></u><u=
 class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>parameter, it MUST
            either be signed using
            JWS [RFC7515] or encrypted<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>using JWE [RFC7516]
            with then considered
            appropriate algorithm.<u class=3D"gmail_msg"></u><u class=3D"gm=
ail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Arial;color:#222222" lang=3D"EN-GB" class=
=3D"gmail_msg">The
          wording&quot;</span><span lang=3D"EN-GB" class=3D"gmail_msg"> wit=
h then
          considered appropriate algorithm&quot;</span><span style=3D"font-=
size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" class=3D"gmai=
l_msg"> is too vague. This should
          be changed into:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"=
></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>When sending the
            authorization request
            object through &quot;request&quot;<u class=3D"gmail_msg"></u><u=
 class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>parameter, it MUST
            either be signed using
            JWS [RFC7515] or encrypted<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>using JWE [RFC7516] <span style=3D"color:blue" class=
=3D"gmail_msg">using a symmetric key algorithm</span>.<u class=3D"gmail_msg=
"></u><u class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0</span></p></div></div></blockquote><div>Reject.=C2=
=A0</div><div>In the above sentence, &quot;<b class=3D"gmail_msg"><span lan=
g=3D"EN-GB" class=3D"gmail_msg">with then considered appropriate algorithm<=
/span></b>&quot; =C2=A0applies both on JWS and JWE.=C2=A0</div><div>The int=
ent of the phrase is that a vulnerable algorithm should not be used.=C2=A0<=
/div><div><br></div><div>Also, I do not understand why the algorithm has to=
 be symmetric key algorithm.=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_5=
262665161593131067moz-cite-prefix gmail_msg"><p class=3D"m_5262665161593131=
067MsoPlainText gmail_msg"><span style=3D"font-size:12.0pt;font-family:Verd=
ana;color:#222222" lang=3D"EN-GB" class=3D"gmail_msg"><u class=3D"gmail_msg=
"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">7. Section
          10.2 states:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>This means that the
          request object is going
          to be <span style=3D"background:aqua" class=3D"gmail_msg">prepare=
d
            fresh each<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>time an
          authorization request is made</span><span lang=3D"EN-GB" class=3D=
"gmail_msg"> and caching cannot be used.<span class=3D"gmail_msg">=C2=A0 </=
span><u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">What are the
          implications ? Is it required/recommended to use a nonce ? The
          text should be
          made clearer. <u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg"></span></p></div></div></blockquote><div>Reject.=C2=A0</div=
><div>The implication is given right after the sentence. There is no variab=
le called &quot;nonce&quot; in RFC6749. Since this document is just definin=
g another encoding method for OAuth 2.0 authorization request as a framewor=
k, it does not mandate these. An extension specification should define thos=
e requirements.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor=3D"#=
FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_52626651615931=
31067moz-cite-prefix gmail_msg"><p class=3D"m_5262665161593131067MsoPlainTe=
xt gmail_msg"><span style=3D"font-size:12.0pt;font-family:Verdana;color:#22=
2222" lang=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><=
u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">8. Section
          10.3 states:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">10.3.<span class=3D"gmail_msg">=C2=A0 </span=
>Request Source
          Authentication<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D=
"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>The source of the
          Authorization Request
          MUST always be verified.<u class=3D"gmail_msg"></u><u class=3D"gm=
ail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>There are several ways
          to do it in this
          specification.<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D=
"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>(a)<span class=3D"gmail_msg">=C2=A0
          </span>Verifying the JWS Signature of the Request Object.<u class=
=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">It seems that
          the case of using a JWE encrypted using a secret key algorithm
          has been
          forgotten here. Please add it.</span></p></div></div></blockquote=
><div>Accepted with modification.=C2=A0</div><div>You mean, symmetric key a=
lgorithm, is that right? I would add &quot;or verifying that the symmetric =
key for the=C2=A0<span style=3D"font-size:13.3333px">JWE encryption is a co=
rrect one&quot;=C2=A0</span></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgc=
olor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_52626=
65161593131067moz-cite-prefix gmail_msg"><p class=3D"m_5262665161593131067M=
soPlainText gmail_msg"><span style=3D"font-size:12.0pt;font-family:Verdana;=
color:#222222" lang=3D"EN-US" class=3D"gmail_msg"><u class=3D"gmail_msg"></=
u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-US" clas=
s=3D"gmail_msg">9. Section
          10.3 states at its very end:<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D=
"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>An extension
          specification <u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>should be created as a
          preventive measure
          to address potential<u class=3D"gmail_msg"></u><u class=3D"gmail_=
msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>vulnerabilities that
          have not yet been
          identified.<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u>=
</span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">Writing a
          document for vulnerabilities that have not yet been identified
          is speculative.
          It would rather be better <br class=3D"gmail_msg">
          either to remove this sentence or to explain what is meant
          by it.</span></p></div></div></blockquote><div>Reject.=C2=A0</div=
><div>It is referring to the first paragraph of the sub-section. Also, prec=
aution when security is in question is a good thing.=C2=A0<span style=3D"co=
lor:rgb(34,34,34);font-family:Verdana;font-size:12pt">=C2=A0</span></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000" clas=
s=3D"gmail_msg"><div class=3D"m_5262665161593131067moz-cite-prefix gmail_ms=
g">
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">10. Section 11.1
          states:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></sp=
an></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg">11.1.<span class=3D"gma=
il_msg">=C2=A0 </span>Collection limitation<u class=3D"gmail_msg"></u><u cl=
ass=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail=
_msg"></u><u class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>When the Client is
            being granted access to
            a protected resource<u class=3D"gmail_msg"></u><u class=3D"gmai=
l_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>containing personal
            data, the Client SHOULD
            limit the collection of<u class=3D"gmail_msg"></u><u class=3D"g=
mail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>personal data to that
            which is within the
            bounds of applicable law<u class=3D"gmail_msg"></u><u class=3D"=
gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>and strictly
            necessary for the specified
            purpose(s).</span></b><b class=3D"gmail_msg"><span style=3D"fon=
t-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" class=3D"gm=
ail_msg"><u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></b><=
/p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">The <i class=3D"gmail_msg">presentation</i>
          of personal data should be limited whether or not the
          protected resource
          contains personal data.</span>=C2=A0</p></div></div></blockquote>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div bgcolor=3D"#FFFFFF" text=3D"#000000" cl=
ass=3D"gmail_msg"><div class=3D"m_5262665161593131067moz-cite-prefix gmail_=
msg"><p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg"><u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></spa=
n></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><br></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">It is
          proposed to change this text into:<u class=3D"gmail_msg"></u><u c=
lass=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>When the Client
            requests an access to a
            protected resource, the Client<u class=3D"gmail_msg"></u><u cla=
ss=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>SHOULD limit the
            presentation of personal
            data to that which is within <u class=3D"gmail_msg"></u><u clas=
s=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>the bounds of
            applicable law and strictly
            necessary for the specified <u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><b class=3D"=
gmail_msg"><span lang=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_ms=
g">=C2=A0=C2=A0 </span>purpose(s).</span></b></p></div></div></blockquote><=
div>Reject.=C2=A0</div><div>You are not getting what OAuth does. The party =
that holds personal data is the authorization server / resource.=C2=A0</div=
><div>It is not the client. The client is the party who is getting those &q=
uot;resources&quot; which may contain personal data.=C2=A0</div><div>Yes, t=
he client can provide some personal data to the resource depending on what =
that resource endpoint is, but that is out of scope for OAuth.=C2=A0</div><=
div>As far as OAuth is concerned, what is being sent from the client to the=
 resource is the access token.=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m=
_5262665161593131067moz-cite-prefix gmail_msg"><p class=3D"m_52626651615931=
31067MsoPlainText gmail_msg"><b class=3D"gmail_msg"><span style=3D"font-siz=
e:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" class=3D"gmail_m=
sg"><u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></b></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">11. Section
          11.2.1 states:<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"><=
/u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">11.2.1.<span class=3D"gmail_msg">=C2=A0 </sp=
an>Request Disclosure<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u>=
</span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D=
"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-GB" class=3D"gmail_msg"><span class=3D"gmail_msg">=C2=A0=C2=A0 </spa=
n>This specification
          allows extension
          parameters. </span><span style=3D"font-size:12.0pt;font-family:Ve=
rdana;color:#222222" lang=3D"EN-GB" class=3D"gmail_msg"><u class=3D"gmail_m=
sg"></u><u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">It would be
          useful to name either all of them or some of them. RFC 6749 is
          not crystal clear about this.</span></p></div></div></blockquote>=
<div>Noted.=C2=A0</div><div>RFC6749 only defines how to define extension pa=
rameters.=C2=A0</div><div>This specification draws from OpenID Connect for =
some examples of extension parameters such as nonce.=C2=A0</div><div>See se=
ction 4 for example. =C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolo=
r=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_msg"><div class=3D"m_52626651=
61593131067moz-cite-prefix gmail_msg"><p class=3D"m_5262665161593131067MsoP=
lainText gmail_msg"><span style=3D"font-size:12.0pt;font-family:Verdana;col=
or:#222222" lang=3D"EN-GB" class=3D"gmail_msg"><u class=3D"gmail_msg"></u><=
u class=3D"gmail_msg"></u></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u=
></span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg"><br class=3D"gmail_msg">
        </span></p>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span style=
=3D"font-size:12.0pt;font-family:Verdana;color:#222222" lang=3D"EN-GB" clas=
s=3D"gmail_msg">Denis Pinkas (DP Security Consulting SAS)</span></p>
      <span style=3D"font-size:12.0pt;font-family:Verdana;color:#222222" la=
ng=3D"EN-GB" class=3D"gmail_msg">=C2=A0<u class=3D"gmail_msg"></u><u class=
=3D"gmail_msg"></u></span>
      <p class=3D"m_5262665161593131067MsoPlainText gmail_msg"><span lang=
=3D"EN-US" class=3D"gmail_msg">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
          <u class=3D"gmail_msg"></u><u class=3D"gmail_msg"></u></span></p>
     =20
     =20
     =20
     =20
     =20
      <br class=3D"gmail_msg">
      <br class=3D"gmail_msg">
      <br class=3D"gmail_msg">
    </div></div><div bgcolor=3D"#FFFFFF" text=3D"#000000" class=3D"gmail_ms=
g">
    <blockquote type=3D"cite" class=3D"gmail_msg">
      <pre class=3D"gmail_msg">The IESG has received a request from the Web=
 Authorization Protocol WG
(oauth) to consider the following document:
- &#39;The OAuth 2.0 Authorization Framework: JWT Secured Authorization
   Request (JAR)&#39;
  &lt;draft-ietf-oauth-jwsreq-11.txt&gt; as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a class=3D"m_5262665161593131067moz-txt-link-abbreviated gmail_msg" href=
=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailing lists=
 by 2017-02-13. Exceptionally, comments may be
sent to <a class=3D"m_5262665161593131067moz-txt-link-abbreviated gmail_msg=
" href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a> instead=
. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The authorization request in OAuth 2.0 described in RFC 6749 utilizes
   query parameter serialization, which means that Authorization Request
   parameters are encoded in the URI of the request and sent through
   user agents such as web browsers.  While it is easy to implement, it
   means that (a) the communication through the user agents are not
   integrity protected and thus the parameters can be tainted, and (b)
   the source of the communication is not authenticated.  Because of
   these weaknesses, several attacks to the protocol have now been put
   forward.

   This document introduces the ability to send request parameters in a
   JSON Web Token (JWT) instead, which allows the request to be JWS
   signed and/or JWE encrypted so that the integrity, source
   authentication and confidentiality property of the Authorization
   Request is attained.  The request can be sent by value or by
   reference.




The file can be obtained via
<a class=3D"m_5262665161593131067moz-txt-link-freetext gmail_msg" href=3D"h=
ttps://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/" target=3D"_blank"=
>https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/</a>

IESG discussion can be tracked via
<a class=3D"m_5262665161593131067moz-txt-link-freetext gmail_msg" href=3D"h=
ttps://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/" target=3D"=
_blank">https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/</a=
>


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


The document contains these normative downward references.
See RFC 3967 for additional information:=20
    rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (I=
nformational - IETF stream)
    rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informatio=
nal - IETF stream)
    rfc6973: Privacy Considerations for Internet Protocols (Informational -=
 IAB stream)
Note that some of these references may already be listed in the acceptable =
Downref Registry.


_______________________________________________
OAuth mailing list
<a class=3D"m_5262665161593131067moz-txt-link-abbreviated gmail_msg" href=
=3D"mailto:OAuth@ietf.org" target=3D"_blank">OAuth@ietf.org</a>
<a class=3D"m_5262665161593131067moz-txt-link-freetext gmail_msg" href=3D"h=
ttps://www.ietf.org/mailman/listinfo/oauth" target=3D"_blank">https://www.i=
etf.org/mailman/listinfo/oauth</a>
</pre>
    </blockquote>
    <p class=3D"gmail_msg"><br class=3D"gmail_msg">
    </p>
  </div>

_______________________________________________<br class=3D"gmail_msg">
OAuth mailing list<br class=3D"gmail_msg">
<a href=3D"mailto:OAuth@ietf.org" class=3D"gmail_msg" target=3D"_blank">OAu=
th@ietf.org</a><br class=3D"gmail_msg">
<a href=3D"https://www.ietf.org/mailman/listinfo/oauth" rel=3D"noreferrer" =
class=3D"gmail_msg" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/oauth</a><br class=3D"gmail_msg">
</blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-smartmail=
=3D"gmail_signature"><p dir=3D"ltr">Nat Sakimura</p>
<p dir=3D"ltr">Chairman of the Board, OpenID Foundation</p>
</div>

--94eb2c03fb967359de0547dd2b76--


From nobody Mon Feb  6 06:14:37 2017
Return-Path: <sakimura@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC69A129DA3; Mon,  6 Feb 2017 06:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9ULawRVM7Xc; Mon,  6 Feb 2017 06:14:34 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::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 F3EA1129D9A; Mon,  6 Feb 2017 06:14:33 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id b65so122241168wmf.0; Mon, 06 Feb 2017 06:14:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iqBblcxBJpi94r0QkcVPXBz5Ak3RnGNdiseim23l63Y=; b=Z4qk0H28s5x8/cN2gCOX44yygp7owC4OexSZsEoBArWKs3RhFD1Gw6mWEdcibR2SpT r94lCuL1OWezUxOzv6Z47p6LLK9GKe/yZlEAuHSAMfq0yDFH25gVp5sCZtG/Yb/xo6QZ JScaGEhDnnzDFec7Ag8aN/VJvD797L81OsNKRV/nRzbrvc6GZo8belSbdauQhnRenvUh VPMRIXhL4gyLOiAunGkQ2UuBh+4oCC7kh/Gm2ASkBARODWLqaRUlKVHmFp4la3/+epvD a6yE5tnjtKmahIXokC8N0UqMdtWcTxxFPBg5B0YVg0PqgJ80XEhcT1eOaE2Gy0Sm6nex 16hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iqBblcxBJpi94r0QkcVPXBz5Ak3RnGNdiseim23l63Y=; b=iejT9xN/M+KOr9LvdafiOXyGTX734BA406hRbLqy2Hcohw0pZrzi7pjpoyA2bTZyVM R9O7ff6oaqWl1SOwjda/cwkZEzyQNjywtgyUHKgy8lPxOA5cb6nEm9OCCXK3kGcbICPL HZPm1cZDH3QMpRWFUWrInDP8NP2qUaTaDk7ta+XtaU9GAZHZ1QnA2/CUTHLYpBMnD5iA /6/Sq+6IyVqmXtM4PQLlxvYn+guRvAFUSAVQS+1/N07FNSVPsxfS0GHTViG7jz/EOqjv 1D5aI5YA7do+5DURY5estCDBt/+QKLFpumo0QdVfaiDtXPgHt7CuBBX2ZqpuWYupCgWl 88wA==
X-Gm-Message-State: AMke39kvq8OKJYdiF24k5eIH2AwAj4GRUEeELVJTxWA9HLJ2sEtzx7MmN1p2Vsqiem4N6rj639Cq8XdmuFCDmQ==
X-Received: by 10.28.1.216 with SMTP id 207mr9593070wmb.7.1486390472437; Mon, 06 Feb 2017 06:14:32 -0800 (PST)
MIME-Version: 1.0
References: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
In-Reply-To: <148607662042.13885.2832003093930390561.idtracker@ietfa.amsl.com>
From: Nat Sakimura <sakimura@gmail.com>
Date: Mon, 06 Feb 2017 14:14:22 +0000
Message-ID: <CABzCy2AUXh5kW_+-0T4r2HWqyhrmQ5DLQ6-GPiXdwqzE5ZOHmA@mail.gmail.com>
Subject: Re: [OAUTH-WG] Review of draft-ietf-oauth-jwsreq-11
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
Content-Type: multipart/alternative; boundary=001a113c73f81b78bd0547dd4018
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hGkyiyZgg9LCyqf9A_pDwHK-s6A>
Cc: ietf@ietf.org, draft-ietf-oauth-jwsreq.all@ietf.org, oauth@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 14:14:36 -0000

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

Thanks Joel,

-11 only contains the fixes to the comments received by Jan. 17. I am now
applying all the edits needed for the comments received after that.
The next version will fix the problem you have pointed out.

Best,

Nat

On Fri, Feb 3, 2017 at 8:03 AM Joel Halpern <jmh@joelhalpern.com> wrote:

> Reviewer: Joel Halpern
> Review result: Not Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-oauth-jwsreq-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-02
> IETF LC End Date: 2017-02-13
> IESG Telechat date: 2017-02-16
>
> Summary: This document is ready for publication as a Proposed
> Standard
>
> Major issues: N/A
>
> Minor issues:
>     Why is the example if section 4 (and others later on) described
> as
> "non-normative"?  Is it incomplete?  incorrect?  An example is, by
> definition, not a full specification.  The language seems designed to
> reduce the value of the example.  I would recommend removing all the
> "non-normative" notes from the examples.  They are clearly stated to
> be examples.
>
> Nits/editorial comments:
>
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>
-- 

Nat Sakimura

Chairman of the Board, OpenID Foundation

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

<div dir=3D"ltr">Thanks Joel,=C2=A0<div><br></div><div>-11 only contains th=
e fixes to the comments received by Jan. 17. I am now applying all the edit=
s needed for the comments received after that.=C2=A0</div><div>The next ver=
sion will fix the problem you have pointed out.=C2=A0</div><div><br></div><=
div>Best,=C2=A0</div><div><br></div><div>Nat</div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr">On Fri, Feb 3, 2017 at 8:03 AM Joel Halpern &l=
t;<a href=3D"mailto:jmh@joelhalpern.com">jmh@joelhalpern.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Reviewer: Joel Halpern<br class=3D=
"gmail_msg">
Review result: Not Ready<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
I am the assigned Gen-ART reviewer for this draft. The General Area<br clas=
s=3D"gmail_msg">
Review Team (Gen-ART) reviews all IETF documents being processed<br class=
=3D"gmail_msg">
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br c=
lass=3D"gmail_msg">
like any other last call comments.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
For more information, please see the FAQ at<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" class=3D"gmail_msg" target=3D"_blank">https://trac.ietf.org/trac/gen/=
wiki/GenArtfaq</a>&gt;.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Document: draft-ietf-oauth-jwsreq-??<br class=3D"gmail_msg">
Reviewer: Joel Halpern<br class=3D"gmail_msg">
Review Date: 2017-02-02<br class=3D"gmail_msg">
IETF LC End Date: 2017-02-13<br class=3D"gmail_msg">
IESG Telechat date: 2017-02-16<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Summary: This document is ready for publication as a Proposed<br class=3D"g=
mail_msg">
Standard<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Major issues: N/A<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Minor issues:<br class=3D"gmail_msg">
=C2=A0 =C2=A0 Why is the example if section 4 (and others later on) describ=
ed<br class=3D"gmail_msg">
as<br class=3D"gmail_msg">
&quot;non-normative&quot;?=C2=A0 Is it incomplete?=C2=A0 incorrect?=C2=A0 A=
n example is, by<br class=3D"gmail_msg">
definition, not a full specification.=C2=A0 The language seems designed to<=
br class=3D"gmail_msg">
reduce the value of the example.=C2=A0 I would recommend removing all the<b=
r class=3D"gmail_msg">
&quot;non-normative&quot; notes from the examples.=C2=A0 They are clearly s=
tated to<br class=3D"gmail_msg">
be examples.<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
Nits/editorial comments:<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
<br class=3D"gmail_msg">
_______________________________________________<br class=3D"gmail_msg">
OAuth mailing list<br class=3D"gmail_msg">
<a href=3D"mailto:OAuth@ietf.org" class=3D"gmail_msg" target=3D"_blank">OAu=
th@ietf.org</a><br class=3D"gmail_msg">
<a href=3D"https://www.ietf.org/mailman/listinfo/oauth" rel=3D"noreferrer" =
class=3D"gmail_msg" target=3D"_blank">https://www.ietf.org/mailman/listinfo=
/oauth</a><br class=3D"gmail_msg">
</blockquote></div><div dir=3D"ltr">-- <br></div><div data-smartmail=3D"gma=
il_signature"><p dir=3D"ltr">Nat Sakimura</p>
<p dir=3D"ltr">Chairman of the Board, OpenID Foundation</p>
</div>

--001a113c73f81b78bd0547dd4018--


From nobody Mon Feb  6 07:28:04 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B3E0129E80 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 07:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HcEDNqYjb7wn for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 07:27:55 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 1A3CF129E70 for <ietf@ietf.org>; Mon,  6 Feb 2017 07:27:55 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id r141so118451460wmg.1 for <ietf@ietf.org>; Mon, 06 Feb 2017 07:27:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=a1MhW0AGIeWebi/WbK/5qfLASKOv5stj8XNe3mxPj7E=; b=gMZHWgpILv2YhLKmUVixrnHCKgnhuXKbKbp5pqmVt36FM/liwAhydwJF4EoRcH26t9 qa8IY9c4tJZVwIiejTQwaxA5STGF6QegJ8wC012zFdPj6YOGDRqBz0+6d18eHy5ZeVC/ mDOA404qvUKQXTjW/2KjernBCHy3A6HcbJIU7NdW6hQ+84pHRppLpSOhq4Ba1uHt4WTf mQM1VFk+2/riU7CbUTViMXNUjFiiaooYkZYqSGIANFhSx9kSztuF4HOB2id+TjpISPg4 iKtxHLnTqJzJcqibEBj9rljFVgrB6Oe8kLR9gsjKflxTI05WvCdpRFFUdIa5Bo+pblz1 DCSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=a1MhW0AGIeWebi/WbK/5qfLASKOv5stj8XNe3mxPj7E=; b=Lh4qkA4Y4hldm/Av2uabjKuoJJQ1rcYXQEeyrjKWlAAVvo2At9M9IDpnixW0jRPDjc EeRqTwgioAQvfJww0JRslfiQYQu8ltLEgxkIGuRyFspINWRMmRO0rPKxZvdUNBJrrN4f AIJgMQJvg/7aMBCW8PBE1RQQjs9sZRG3rRDpaC5V8sW6IpyCn4QjGd5OjVsctP1G0PlS zfvjKn3qMBg5/Y/Ciz93u4OY/6AU9MIlVrwCVeMz+tiahr3r2HEKHGx1X+ouu/0H/fTK O/3V6kFXaoMmZa7z+IiGMKKtHORaYcksyciSFvSt/6eD05Y864jIX0cVw4sUaB1l/cky D0kg==
X-Gm-Message-State: AIkVDXJOl1LS+nRu6aLJmASL0LNNO4g6gEJxOfU6iOzJiplHc9NrL4v0JWo968+RdoT/xF/tj5QdLw9jhr+X9g==
X-Received: by 10.223.150.118 with SMTP id c51mr9300359wra.190.1486394872085;  Mon, 06 Feb 2017 07:27:52 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.194.221.6 with HTTP; Mon, 6 Feb 2017 07:27:51 -0800 (PST)
In-Reply-To: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 6 Feb 2017 10:27:51 -0500
X-Google-Sender-Auth: eqQVdMQOz5jBgxAcGumnL8FUxFo
Message-ID: <CAMm+LwjW=D_6EeVFOYPGhX-0rjs=0YMh2cBzx5AXZ14caS4caA@mail.gmail.com>
Subject: Re: WG Review: JSON Mail Access Protocol (jmap)
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a1147d0f258c5910547de4689
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HD-9wzeDoyUR-IPmPrLz2FDuiPg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 15:27:57 -0000

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

I don't see much point if all that we do is simply re-invent IMAP in JSON.
To add value, a new protocol in this space needs to advance on the old.

Today we have many things that look like mail that are not mail but could
benefit from IMAP type interface. These include:

* Mailing lists
* Newsgroups
* Blog comments
* Git Pull requests

Note that all of these are messages that are frequently transported over
SMTP but handled very poorly as mail.

Mailing lists are not mail. They look like mail but they are not because
they represent a discussion that frequently begins before the user has
joined. They have semantics for subscription and unsubscription. There is
frequently an external archive.


I don't think it unreasonable to ask folk doing an 'X in JSON' project to
extend it. Because if the move to JSON does not make such extensions easier
to introduce, what was the point of varying the syntax in the first place.

Being able to connect to discussion forums via an IMAP like interface would
be very useful and allow a lot of mail volume to be culled.



On Fri, Feb 3, 2017 at 7:26 PM, The IESG <iesg-secretary@ietf.org> wrote:

> A new IETF WG has been proposed in the Applications and Real-Time Area.
> The IESG has not made any determination yet. The following draft charter
> was submitted, and is provided for informational purposes only. Please
> send your comments to the IESG mailing list (iesg@ietf.org) by
> 2017-02-13.
>
> JSON Mail Access Protocol (jmap)
> -----------------------------------------------------------------------
> Current status: Proposed WG
>
> Chairs:
>   TBD
>
> Assigned Area Director:
>   Alexey Melnikov <aamelnikov@fastmail.fm>
>
> Applications and Real-Time Area Directors:
>   Ben Campbell <ben@nostrum.com>
>   Alissa Cooper <alissa@cooperw.in>
>   Alexey Melnikov <aamelnikov@fastmail.fm>
>
> Mailing list:
>   Address: jmap@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/jmap
>   Archive: https://mailarchive.ietf.org/arch/search/?email_list=jmap
>
> Group page: https://datatracker.ietf.org/group/jmap/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/
>
> A number of JSON-based representations of email have been developed
> that are proprietary, non-standard, and incompatible with each other.
> These protocols are proliferating due
> to existing standards being insufficient or poorly suited to the
> environments they are operating in, particularly mobile and webmail.
>
> The use of multiple protocols
> to perform actions within a single application creates significant
> support challenges, as users may get a variety of partial failure modes
> (for example, can receive email, but can not send new messages).
> This is further exacerbated if the different protocols are
> authenticated separately.
>
> The JMAP working group will specify a mechanism to allow clients to
> both view and send email from a server over a single stateless HTTPS
> channel with minimal round trips. A single protocol for receipt and
> submission will resolve long-standing difficulties users face
> setting up clients to talk to servers.
>
> The protocol will support
> push notification of changes using the mechanism defined in RFC 8030.
> This will give mobile clients benefits in terms of battery life and
> network usage. It will also support push notifications via server-sent
> events (https://www.w3.org/TR/eventsource/) for direct connection to
> clients that can support persistent TCP connections.
>
> The work of this group is limited to developing a protocol for a client
> synchronising data with a server. Any server-to-server issues
> are out of scope for this working group.
> New end-to-end encryption mechanisms are out of scope, but the work
> should
> consider how to integrate with existing standards such as S/MIME and
> OpenPGP.
>
> The working group will coordinate with the Security Area on credential
> management and authentication.
>
> Input to working group discussions shall include:
>
> - CONDSTORE and QRESYNC
> [RFC 7162]
>
> - Collection Synchronisation for WebDav
> [RFC 6578]
>
> - LEMONADE and experiences from adoption of its output
> [https://datatracker.ietf.org/wg/lemonade/charter/]
>
> - SMTP SUBMISSION
> [RFC 6409]
>
> - SMTP BURL
> [RFC 4468]
>
> The working group will deliver the following:
>
> - A problem statement detailing the deployment environment and
>   situations that motivate work on a new protocol for client to
>   server email synchronisation.  The working group may choose
>   not to publish this as an RFC.
>
> - A document describing an extensible protocol and data structures, with
>   support for flood control and batched operations, and operating over
>   a stateless connection such as HTTPS.
>
> - A document describing how to use the extensible protocol over HTTPS
>   with the data structures expressed as JSON.
>
> - A document describing a data model for email viewing, management,
>   searching, and submission on top of the extensible protocol.
>
> - An executable test suite and documented test cases to assist
>   developers of JMAP servers to ensure they conform to the
>   specifications.
>
> Milestones:
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">I d=
on&#39;t see much point if all that we do is simply re-invent IMAP in JSON.=
 To add value, a new protocol in this space needs to advance on the old.</d=
iv><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div cl=
ass=3D"gmail_default" style=3D"font-size:small">Today we have many things t=
hat look like mail that are not mail but could benefit from IMAP type inter=
face. These include:</div><div class=3D"gmail_default" style=3D"font-size:s=
mall"><br></div><div class=3D"gmail_default" style=3D"font-size:small">* Ma=
iling lists</div><div class=3D"gmail_default" style=3D"font-size:small">* N=
ewsgroups</div><div class=3D"gmail_default" style=3D"font-size:small">* Blo=
g comments</div><div class=3D"gmail_default" style=3D"font-size:small">* Gi=
t Pull requests</div><div class=3D"gmail_default" style=3D"font-size:small"=
><br></div><div class=3D"gmail_default" style=3D"font-size:small">Note that=
 all of these are messages that are frequently transported over SMTP but ha=
ndled very poorly as mail.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
">Mailing lists are not mail. They look like mail but they are not because =
they represent a discussion that frequently begins before the user has join=
ed. They have semantics for subscription and unsubscription. There is frequ=
ently an external archive.</div><div class=3D"gmail_default" style=3D"font-=
size:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small=
"><br></div><div class=3D"gmail_default" style=3D"font-size:small">I don&#3=
9;t think it unreasonable to ask folk doing an &#39;X in JSON&#39; project =
to extend it. Because if the move to JSON does not make such extensions eas=
ier to introduce, what was the point of varying the syntax in the first pla=
ce.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><=
div class=3D"gmail_default" style=3D"font-size:small">Being able to connect=
 to discussion forums via an IMAP like interface would be very useful and a=
llow a lot of mail volume to be culled.</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small"><br></div><div class=3D"gmail_default" style=3D"fo=
nt-size:small"><br></div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Fri, Feb 3, 2017 at 7:26 PM, The IESG <span dir=3D"ltr">&l=
t;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secreta=
ry@ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">A new I=
ETF WG has been proposed in the Applications and Real-Time Area.<br>
The IESG has not made any determination yet. The following draft charter<br=
>
was submitted, and is provided for informational purposes only. Please<br>
send your comments to the IESG mailing list (<a href=3D"mailto:iesg@ietf.or=
g">iesg@ietf.org</a>) by<br>
2017-02-13.<br>
<br>
JSON Mail Access Protocol (jmap)<br>
------------------------------<wbr>------------------------------<wbr>-----=
------<br>
Current status: Proposed WG<br>
<br>
Chairs:<br>
=C2=A0 TBD<br>
<br>
Assigned Area Director:<br>
=C2=A0 Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm">aameln=
ikov@fastmail.fm</a>&gt;<br>
<br>
Applications and Real-Time Area Directors:<br>
=C2=A0 Ben Campbell &lt;<a href=3D"mailto:ben@nostrum.com">ben@nostrum.com<=
/a>&gt;<br>
=C2=A0 Alissa Cooper &lt;<a href=3D"mailto:alissa@cooperw.in">alissa@cooper=
w.in</a>&gt;<br>
=C2=A0 Alexey Melnikov &lt;<a href=3D"mailto:aamelnikov@fastmail.fm">aameln=
ikov@fastmail.fm</a>&gt;<br>
<br>
Mailing list:<br>
=C2=A0 Address: <a href=3D"mailto:jmap@ietf.org">jmap@ietf.org</a><br>
=C2=A0 To subscribe: <a href=3D"https://www.ietf.org/mailman/listinfo/jmap"=
 rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>lis=
tinfo/jmap</a><br>
=C2=A0 Archive: <a href=3D"https://mailarchive.ietf.org/arch/search/?email_=
list=3Djmap" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.=
org/<wbr>arch/search/?email_list=3Djmap</a><br>
<br>
Group page: <a href=3D"https://datatracker.ietf.org/group/jmap/" rel=3D"nor=
eferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>group/jmap/</a=
><br>
<br>
Charter: <a href=3D"https://datatracker.ietf.org/doc/charter-ietf-jmap/" re=
l=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/ch=
arter-ietf-jmap/</a><br>
<br>
A number of JSON-based representations of email have been developed<br>
that are proprietary, non-standard, and incompatible with each other.<br>
These protocols are proliferating due<br>
to existing standards being insufficient or poorly suited to the<br>
environments they are operating in, particularly mobile and webmail.<br>
<br>
The use of multiple protocols<br>
to perform actions within a single application creates significant<br>
support challenges, as users may get a variety of partial failure modes<br>
(for example, can receive email, but can not send new messages).<br>
This is further exacerbated if the different protocols are<br>
authenticated separately.<br>
<br>
The JMAP working group will specify a mechanism to allow clients to<br>
both view and send email from a server over a single stateless HTTPS<br>
channel with minimal round trips. A single protocol for receipt and<br>
submission will resolve long-standing difficulties users face<br>
setting up clients to talk to servers.<br>
<br>
The protocol will support<br>
push notification of changes using the mechanism defined in RFC 8030.<br>
This will give mobile clients benefits in terms of battery life and<br>
network usage. It will also support push notifications via server-sent<br>
events (<a href=3D"https://www.w3.org/TR/eventsource/" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.w3.org/TR/<wbr>eventsource/</a>) for direct co=
nnection to<br>
clients that can support persistent TCP connections.<br>
<br>
The work of this group is limited to developing a protocol for a client<br>
synchronising data with a server. Any server-to-server issues<br>
are out of scope for this working group.<br>
New end-to-end encryption mechanisms are out of scope, but the work<br>
should<br>
consider how to integrate with existing standards such as S/MIME and<br>
OpenPGP.<br>
<br>
The working group will coordinate with the Security Area on credential<br>
management and authentication.<br>
<br>
Input to working group discussions shall include:<br>
<br>
- CONDSTORE and QRESYNC<br>
[RFC 7162]<br>
<br>
- Collection Synchronisation for WebDav<br>
[RFC 6578]<br>
<br>
- LEMONADE and experiences from adoption of its output<br>
[<a href=3D"https://datatracker.ietf.org/wg/lemonade/charter/" rel=3D"noref=
errer" target=3D"_blank">https://datatracker.ietf.org/<wbr>wg/lemonade/char=
ter/</a>]<br>
<br>
- SMTP SUBMISSION<br>
[RFC 6409]<br>
<br>
- SMTP BURL<br>
[RFC 4468]<br>
<br>
The working group will deliver the following:<br>
<br>
- A problem statement detailing the deployment environment and<br>
=C2=A0 situations that motivate work on a new protocol for client to<br>
=C2=A0 server email synchronisation.=C2=A0 The working group may choose<br>
=C2=A0 not to publish this as an RFC.<br>
<br>
- A document describing an extensible protocol and data structures, with<br=
>
=C2=A0 support for flood control and batched operations, and operating over=
<br>
=C2=A0 a stateless connection such as HTTPS.<br>
<br>
- A document describing how to use the extensible protocol over HTTPS<br>
=C2=A0 with the data structures expressed as JSON.<br>
<br>
- A document describing a data model for email viewing, management,<br>
=C2=A0 searching, and submission on top of the extensible protocol.<br>
<br>
- An executable test suite and documented test cases to assist<br>
=C2=A0 developers of JMAP servers to ensure they conform to the<br>
=C2=A0 specifications.<br>
<br>
Milestones:<br>
<br>
<br>
</blockquote></div><br></div>

--001a1147d0f258c5910547de4689--


From nobody Mon Feb  6 07:40:49 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A39D129E76 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 07:40:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yaQVTBkG57Ub for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 07:40:42 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 34B25129E72 for <ietf@ietf.org>; Mon,  6 Feb 2017 07:40:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486395641; d=isode.com; s=june2016; i=@isode.com; bh=iakLvHCoqePpd8hBXoFGI345kKyFNijGgmjWx9BI+UQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=foo2OjGde8NJxPLaot/jLzBXBRzHU49XkBspY4DHzbcj6h5DODeM7lN6CqRqtjhEKNum/2 Kbdw+GdgSPMUDD/1UG/QLwi5EU1QggKB43QqPBoktAKTnyVsH+1RVK7Dsel5GPk0XdyWGO OzvqFXPFW8p2NGss+IY90VpIylOYPsI=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJiY-AAY158r@statler.isode.com>; Mon, 6 Feb 2017 15:40:41 +0000
Subject: Re: WG Review: JSON Mail Access Protocol (jmap)
To: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <CAMm+LwjW=D_6EeVFOYPGhX-0rjs=0YMh2cBzx5AXZ14caS4caA@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <9ce10b67-dde7-34b8-c05d-90e9d2b407ec@isode.com>
Date: Mon, 6 Feb 2017 15:40:40 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <CAMm+LwjW=D_6EeVFOYPGhX-0rjs=0YMh2cBzx5AXZ14caS4caA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------5622135885C90A322FE82DF8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZM41G9TtapDrlaqliU5xnzA1NOg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 15:40:48 -0000

--------------5622135885C90A322FE82DF8
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Phillip,

On 06/02/2017 15:27, Phillip Hallam-Baker wrote:

> I don't see much point if all that we do is simply re-invent IMAP in 
> JSON. To add value, a new protocol in this space needs to advance on 
> the old.
The current proposal is "advancing on the old". It is improving on some 
IMAP use cases and there is also a proposal how to add calendaring. 
However calendaring is currently out of scope in order to avoid boiling 
the ocean.
> Today we have many things that look like mail that are not mail but 
> could benefit from IMAP type interface. These include:
>
> * Mailing lists
> * Newsgroups
> * Blog comments
> * Git Pull requests
>
> Note that all of these are messages that are frequently transported 
> over SMTP but handled very poorly as mail.
>
> Mailing lists are not mail. They look like mail but they are not 
> because they represent a discussion that frequently begins before the 
> user has joined. They have semantics for subscription and 
> unsubscription. There is frequently an external archive.
>
>
> I don't think it unreasonable to ask folk doing an 'X in JSON' project 
> to extend it.
It is not unreasonable to ask to extend, but we should be careful about 
not asking for too much.

Best Regards,
Alexey
> Because if the move to JSON does not make such extensions easier to 
> introduce, what was the point of varying the syntax in the first place.
>
> Being able to connect to discussion forums via an IMAP like interface 
> would be very useful and allow a lot of mail volume to be culled.
>
>
>
> On Fri, Feb 3, 2017 at 7:26 PM, The IESG <iesg-secretary@ietf.org 
> <mailto:iesg-secretary@ietf.org>> wrote:
>
>     A new IETF WG has been proposed in the Applications and Real-Time
>     Area.
>     The IESG has not made any determination yet. The following draft
>     charter
>     was submitted, and is provided for informational purposes only. Please
>     send your comments to the IESG mailing list (iesg@ietf.org
>     <mailto:iesg@ietf.org>) by
>     2017-02-13.
>
>     JSON Mail Access Protocol (jmap)
>     -----------------------------------------------------------------------
>     Current status: Proposed WG
>
>     Chairs:
>       TBD
>
>     Assigned Area Director:
>       Alexey Melnikov <aamelnikov@fastmail.fm
>     <mailto:aamelnikov@fastmail.fm>>
>
>     Applications and Real-Time Area Directors:
>       Ben Campbell <ben@nostrum.com <mailto:ben@nostrum.com>>
>       Alissa Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>>
>       Alexey Melnikov <aamelnikov@fastmail.fm
>     <mailto:aamelnikov@fastmail.fm>>
>
>     Mailing list:
>       Address: jmap@ietf.org <mailto:jmap@ietf.org>
>       To subscribe: https://www.ietf.org/mailman/listinfo/jmap
>     <https://www.ietf.org/mailman/listinfo/jmap>
>       Archive:
>     https://mailarchive.ietf.org/arch/search/?email_list=jmap
>     <https://mailarchive.ietf.org/arch/search/?email_list=jmap>
>
>     Group page: https://datatracker.ietf.org/group/jmap/
>     <https://datatracker.ietf.org/group/jmap/>
>
>     Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/
>     <https://datatracker.ietf.org/doc/charter-ietf-jmap/>
>
>     A number of JSON-based representations of email have been developed
>     that are proprietary, non-standard, and incompatible with each other.
>     These protocols are proliferating due
>     to existing standards being insufficient or poorly suited to the
>     environments they are operating in, particularly mobile and webmail.
>
>     The use of multiple protocols
>     to perform actions within a single application creates significant
>     support challenges, as users may get a variety of partial failure
>     modes
>     (for example, can receive email, but can not send new messages).
>     This is further exacerbated if the different protocols are
>     authenticated separately.
>
>     The JMAP working group will specify a mechanism to allow clients to
>     both view and send email from a server over a single stateless HTTPS
>     channel with minimal round trips. A single protocol for receipt and
>     submission will resolve long-standing difficulties users face
>     setting up clients to talk to servers.
>
>     The protocol will support
>     push notification of changes using the mechanism defined in RFC 8030.
>     This will give mobile clients benefits in terms of battery life and
>     network usage. It will also support push notifications via server-sent
>     events (https://www.w3.org/TR/eventsource/
>     <https://www.w3.org/TR/eventsource/>) for direct connection to
>     clients that can support persistent TCP connections.
>
>     The work of this group is limited to developing a protocol for a
>     client
>     synchronising data with a server. Any server-to-server issues
>     are out of scope for this working group.
>     New end-to-end encryption mechanisms are out of scope, but the work
>     should
>     consider how to integrate with existing standards such as S/MIME and
>     OpenPGP.
>
>     The working group will coordinate with the Security Area on credential
>     management and authentication.
>
>     Input to working group discussions shall include:
>
>     - CONDSTORE and QRESYNC
>     [RFC 7162]
>
>     - Collection Synchronisation for WebDav
>     [RFC 6578]
>
>     - LEMONADE and experiences from adoption of its output
>     [https://datatracker.ietf.org/wg/lemonade/charter/
>     <https://datatracker.ietf.org/wg/lemonade/charter/>]
>
>     - SMTP SUBMISSION
>     [RFC 6409]
>
>     - SMTP BURL
>     [RFC 4468]
>
>     The working group will deliver the following:
>
>     - A problem statement detailing the deployment environment and
>       situations that motivate work on a new protocol for client to
>       server email synchronisation.  The working group may choose
>       not to publish this as an RFC.
>
>     - A document describing an extensible protocol and data
>     structures, with
>       support for flood control and batched operations, and operating over
>       a stateless connection such as HTTPS.
>
>     - A document describing how to use the extensible protocol over HTTPS
>       with the data structures expressed as JSON.
>
>     - A document describing a data model for email viewing, management,
>       searching, and submission on top of the extensible protocol.
>
>     - An executable test suite and documented test cases to assist
>       developers of JMAP servers to ensure they conform to the
>       specifications.
>
>     Milestones:
>
>
>


--------------5622135885C90A322FE82DF8
Content-Type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type"=
>
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Hi Phillip,</p>
    <p>On 06/02/2017 15:27, Phillip Hallam-Baker wrote:<br>
    </p>
    <blockquote
cite=3D"mid:CAMm+LwjW=3DD_6EeVFOYPGhX-0rjs=3D0YMh2cBzx5AXZ14caS4caA@mail.gma=
il.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_default" style=3D"font-size:small">I don't see
          much point if all that we do is simply re-invent IMAP in JSON.
          To add value, a new protocol in this space needs to advance on
          the old.</div>
      </div>
    </blockquote>
    The current proposal is "advancing on the old". It is improving on
    some IMAP use cases and there is also a proposal how to add
    calendaring. However calendaring is currently out of scope in order
    to avoid boiling the ocean.<br>
    <blockquote
cite=3D"mid:CAMm+LwjW=3DD_6EeVFOYPGhX-0rjs=3D0YMh2cBzx5AXZ14caS4caA@mail.gma=
il.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_default" style=3D"font-size:small">Today we have
          many things that look like mail that are not mail but could
          benefit from IMAP type interface. These include:</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small">* Mailing
          lists</div>
        <div class=3D"gmail_default" style=3D"font-size:small">* Newsgroups<=
/div>
        <div class=3D"gmail_default" style=3D"font-size:small">* Blog
          comments</div>
        <div class=3D"gmail_default" style=3D"font-size:small">* Git Pull
          requests</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small">Note that all
          of these are messages that are frequently transported over
          SMTP but handled very poorly as mail.</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small">Mailing lists
          are not mail. They look like mail but they are not because
          they represent a discussion that frequently begins before the
          user has joined. They have semantics for subscription and
          unsubscription. There is frequently an external archive.</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small">I don't think
          it unreasonable to ask folk doing an 'X in JSON' project to
          extend it.</div>
      </div>
    </blockquote>
    It is not unreasonable to ask to extend, but we should be careful
    about not asking for too much.<br>
    <br>
    Best Regards,<br>
    Alexey<br>
    <blockquote
cite=3D"mid:CAMm+LwjW=3DD_6EeVFOYPGhX-0rjs=3D0YMh2cBzx5AXZ14caS4caA@mail.gma=
il.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div class=3D"gmail_default" style=3D"font-size:small">Because if
          the move to JSON does not make such extensions easier to
          introduce, what was the point of varying the syntax in the
          first place.</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small">Being able to
          connect to discussion forums via an IMAP like interface would
          be very useful and allow a lot of mail volume to be culled.</div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
        <div class=3D"gmail_default" style=3D"font-size:small"><br>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Fri, Feb 3, 2017 at 7:26 PM, The
          IESG <span dir=3D"ltr">&lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg=
-secretary@ietf.org</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">A new IETF
            WG has been proposed in the Applications and Real-Time Area.<br>
            The IESG has not made any determination yet. The following
            draft charter<br>
            was submitted, and is provided for informational purposes
            only. Please<br>
            send your comments to the IESG mailing list (<a
              moz-do-not-send=3D"true" href=3D"mailto:iesg@ietf.org">iesg@ie=
tf.org</a>)
            by<br>
            2017-02-13.<br>
            <br>
            JSON Mail Access Protocol (jmap)<br>
            ------------------------------<wbr>-----------------------------=
-<wbr>-----------<br>
            Current status: Proposed WG<br>
            <br>
            Chairs:<br>
            =C2=A0 TBD<br>
            <br>
            Assigned Area Director:<br>
            =C2=A0 Alexey Melnikov &lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:aamelnikov@fastmail.fm">aamelnikov@fastmail.fm<=
/a>&gt;<br>
            <br>
            Applications and Real-Time Area Directors:<br>
            =C2=A0 Ben Campbell &lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:ben@nostrum.com">ben@nostrum.com</a>&gt;<br>
            =C2=A0 Alissa Cooper &lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:alissa@cooperw.in">alissa@cooperw.in</a>&gt;<br=
>
            =C2=A0 Alexey Melnikov &lt;<a moz-do-not-send=3D"true"
              href=3D"mailto:aamelnikov@fastmail.fm">aamelnikov@fastmail.fm<=
/a>&gt;<br>
            <br>
            Mailing list:<br>
            =C2=A0 Address: <a moz-do-not-send=3D"true"
              href=3D"mailto:jmap@ietf.org">jmap@ietf.org</a><br>
            =C2=A0 To subscribe: <a moz-do-not-send=3D"true"
              href=3D"https://www.ietf.org/mailman/listinfo/jmap"
              rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mail=
man/<wbr>listinfo/jmap</a><br>
            =C2=A0 Archive: <a moz-do-not-send=3D"true"
              href=3D"https://mailarchive.ietf.org/arch/search/?email_list=
=3Djmap"
              rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.=
org/<wbr>arch/search/?email_list=3Djmap</a><br>
            <br>
            Group page: <a moz-do-not-send=3D"true"
              href=3D"https://datatracker.ietf.org/group/jmap/"
              rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/<wbr>group/jmap/</a><br>
            <br>
            Charter: <a moz-do-not-send=3D"true"
              href=3D"https://datatracker.ietf.org/doc/charter-ietf-jmap/"
              rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/<wbr>doc/charter-ietf-jmap/</a><br>
            <br>
            A number of JSON-based representations of email have been
            developed<br>
            that are proprietary, non-standard, and incompatible with
            each other.<br>
            These protocols are proliferating due<br>
            to existing standards being insufficient or poorly suited to
            the<br>
            environments they are operating in, particularly mobile and
            webmail.<br>
            <br>
            The use of multiple protocols<br>
            to perform actions within a single application creates
            significant<br>
            support challenges, as users may get a variety of partial
            failure modes<br>
            (for example, can receive email, but can not send new
            messages).<br>
            This is further exacerbated if the different protocols are<br>
            authenticated separately.<br>
            <br>
            The JMAP working group will specify a mechanism to allow
            clients to<br>
            both view and send email from a server over a single
            stateless HTTPS<br>
            channel with minimal round trips. A single protocol for
            receipt and<br>
            submission will resolve long-standing difficulties users
            face<br>
            setting up clients to talk to servers.<br>
            <br>
            The protocol will support<br>
            push notification of changes using the mechanism defined in
            RFC 8030.<br>
            This will give mobile clients benefits in terms of battery
            life and<br>
            network usage. It will also support push notifications via
            server-sent<br>
            events (<a moz-do-not-send=3D"true"
              href=3D"https://www.w3.org/TR/eventsource/" rel=3D"noreferrer"
              target=3D"_blank">https://www.w3.org/TR/<wbr>eventsource/</a>)
            for direct connection to<br>
            clients that can support persistent TCP connections.<br>
            <br>
            The work of this group is limited to developing a protocol
            for a client<br>
            synchronising data with a server. Any server-to-server
            issues<br>
            are out of scope for this working group.<br>
            New end-to-end encryption mechanisms are out of scope, but
            the work<br>
            should<br>
            consider how to integrate with existing standards such as
            S/MIME and<br>
            OpenPGP.<br>
            <br>
            The working group will coordinate with the Security Area on
            credential<br>
            management and authentication.<br>
            <br>
            Input to working group discussions shall include:<br>
            <br>
            - CONDSTORE and QRESYNC<br>
            [RFC 7162]<br>
            <br>
            - Collection Synchronisation for WebDav<br>
            [RFC 6578]<br>
            <br>
            - LEMONADE and experiences from adoption of its output<br>
            [<a moz-do-not-send=3D"true"
              href=3D"https://datatracker.ietf.org/wg/lemonade/charter/"
              rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.=
org/<wbr>wg/lemonade/charter/</a>]<br>
            <br>
            - SMTP SUBMISSION<br>
            [RFC 6409]<br>
            <br>
            - SMTP BURL<br>
            [RFC 4468]<br>
            <br>
            The working group will deliver the following:<br>
            <br>
            - A problem statement detailing the deployment environment
            and<br>
            =C2=A0 situations that motivate work on a new protocol for clien=
t
            to<br>
            =C2=A0 server email synchronisation.=C2=A0 The working group may
            choose<br>
            =C2=A0 not to publish this as an RFC.<br>
            <br>
            - A document describing an extensible protocol and data
            structures, with<br>
            =C2=A0 support for flood control and batched operations, and
            operating over<br>
            =C2=A0 a stateless connection such as HTTPS.<br>
            <br>
            - A document describing how to use the extensible protocol
            over HTTPS<br>
            =C2=A0 with the data structures expressed as JSON.<br>
            <br>
            - A document describing a data model for email viewing,
            management,<br>
            =C2=A0 searching, and submission on top of the extensible
            protocol.<br>
            <br>
            - An executable test suite and documented test cases to
            assist<br>
            =C2=A0 developers of JMAP servers to ensure they conform to the<=
br>
            =C2=A0 specifications.<br>
            <br>
            Milestones:<br>
            <br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------5622135885C90A322FE82DF8--


From nobody Mon Feb  6 08:32:31 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BB7129448; Sat,  4 Feb 2017 10:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O_qqbTtIBBBd; Sat,  4 Feb 2017 10:50:14 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 A523D1293FE; Sat,  4 Feb 2017 10:50:13 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v77so73981617wmv.0; Sat, 04 Feb 2017 10:50:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YbVdLTWPozJiLnXSmDSJDBTCcjv73Zt//r73E9xeSw0=; b=FXbLCLwSP+0RPdZ53QYZ1cJ3ve0rE6+rAyIt8+a2kSWuIR3ktz57FwBW1JHwgphn59 ObPuPt7/AYvVUQdpsYsMAvwyz5QTy29yqbHQIjz7UB6cVgJ31O9JJOmm1Jn+CVIbsFug qBIY7lJEAtKsqg/kUYAyHVgWX6R3BI/D/5A3GRNjiYWZo0po4XHm3mPCOYI26dNHYHwN 25R4VOn+rkKy25xwzWyKhCQwZl3pbtInTgAldsJRvTZNk3V8x22EYd5RmHDrZKyUFVIy oV9WJp6qDAOsxvITZUGfdrg4vYT0Qv63tu4RJ+sUmBIFh+h9YSyt/QSu3k43lLTpJ55A HSSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YbVdLTWPozJiLnXSmDSJDBTCcjv73Zt//r73E9xeSw0=; b=oY/s+ljQShoMIO7VBzkZLgxgYqd8pDM0OMpwSnHoaaPu6JP/Y71t0+4BQmyJO+qQMm IITEJI2VBDfVU4KEymw2gtnap7tfqvDlQp9xgsr0h2r1XZgfNA3JA+0hT0nmYfjCNcPU twi063Qg8DwhGWRS4KTgV7WNO5iHjBAOkBPy9TCRh9eEah5KKEiIa5fzuDETvODubZqy z5mjJubHM/YWJXXIc2LvbGOKh46//5ABwy2Qf2Vij1i0EIsdshRR3i9GGSgn4Fmv0OM+ bQV5Axuq1iAR4uP5ewTi8b5kgsgdN5qVtbxUSb3RFf1S5wvv3fOwkyW2cBMTe6RYPk9e u6Dg==
X-Gm-Message-State: AMke39mt+CHz0CuzDAHLTgNtHKTpByAHhZ18FSj8rNSc3Gq842OqY3edyKMZFnZmVeQg8Q==
X-Received: by 10.28.129.147 with SMTP id c141mr2988413wmd.12.1486234212151; Sat, 04 Feb 2017 10:50:12 -0800 (PST)
Received: from ?IPv6:2601:647:4d01:db10:9541:744d:33b2:2904? ([2601:647:4d01:db10:9541:744d:33b2:2904]) by smtp.gmail.com with ESMTPSA id k4sm3783889wmf.22.2017.02.04.10.50.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Feb 2017 10:50:11 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <3BF2F820-65B7-4151-BD35-F07B132C9F1E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_78F5415F-3BD7-4F43-92C3-919784D39E49"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Sat, 4 Feb 2017 10:50:04 -0800
In-Reply-To: <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org>
To: "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CzxAyDLE_kH1D9vd3pM-DRApP3c>
X-Mailman-Approved-At: Mon, 06 Feb 2017 08:32:30 -0800
Cc: IPv6 List <ipv6@ietf.org>, IETF <ietf@ietf.org>, Bob Hinden <bob.hinden@gmail.com>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Feb 2017 18:50:15 -0000

--Apple-Mail=_78F5415F-3BD7-4F43-92C3-919784D39E49
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Lars,

> On Feb 4, 2017, at 10:40 AM, otroan@employees.org wrote:
>=20
> Lars,
>=20
>>> My apologies: my comments were probably misleading. Certainly, this
>>> document is simply RFC1981 to Std, and hence recommending RFC4821 =
would
>>> be kind of ou of scope, here.
>>>=20
>>> That say, one might wonder to what extent, and for the general =
Internet,
>>> RFC1981 can be considered succesful (given the filtering of ICMP
>>> messages). -- i.e., at this point in time you wouldn't rely on =
RFC1981
>>> (icmp-based pmtud) for path-mtu discovery.
>>=20
>> What Fernando said: I'm certainly not opposed to lifting this to =
Standard, but it is painting an incorrect picture - PLPMTUD is de facto =
mandatory these days, and has been for years.
>=20
> While I'm all in favour of PLMTUD. It doesn't seem like a complete =
solution.
> PMTUD on the other hand supports all protocols on top of IP.
>=20
> Looking just at our specifications, we cannot state that PLMTUD can =
replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.

In addition to what Ole says here, I don=E2=80=99t think rfc1981bis is =
the right place to describe this.  6MAN is working on an update to IPv6 =
Node Requirements ( https://tools.ietf.org/html/draft-clw-rfc6434-bis-00 =
).  I think is a better place to describe the relationship between PMTUD =
and PLMTUD, where they work and don=E2=80=99t, and what the current =
recommendations are.  I hope you will contribute to that work.

Thanks,
Bob




--Apple-Mail=_78F5415F-3BD7-4F43-92C3-919784D39E49
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJYliJdAAoJEK7rdBF357uofEMH+gKcMDoL4qp+S+xGDcc+4Fhh
WZsLSxMbvJ6XkA0g/WYwrjEgp35fk1oQ6SUU7c9Z7ukGf8J6xRAYNoIb1tP1UUo6
YkRRsnriCUcHGMKdwKBoY+8mLxVBj/5+nW1IJ98S5swiFAvf3/tmu+l9rI2EYjkF
2143r2xlzNbi2UCTFGTiWbPNCmAG3PN9mpQaTsOgpvSa6wWBm9ZRVpn+xMTb60xM
GqH86irKZ20b98XghDSrT3isZkxeLPoePH9RECz35Er6bL5nGdnhAcTK0HjfKSE4
ZcGP+eG9P27AViOv6Cz0f9ggrByuz62LlMpWVCz8ZPC1QGhKDuJPvu3pE+wNaxg=
=XwZ0
-----END PGP SIGNATURE-----

--Apple-Mail=_78F5415F-3BD7-4F43-92C3-919784D39E49--


From nobody Mon Feb  6 09:37:55 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A27129418; Mon,  6 Feb 2017 09:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LvvZ10Mgjgt; Mon,  6 Feb 2017 09:37:52 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0420E1293D8; Mon,  6 Feb 2017 09:37:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486402672; x=1517938672; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=8CUooSX7jNZmLb4sycMKsdyMVTjQUMs+U9S55/nlvxM=; b=rvUXdQEE8kNkTPeDOTwB6Q/FIArktiaci7Gn5XUZMLZ3aqCl8FLH47Dl /vFq7vyV9D7QTpI4iz4qLsouAlKZLFSidDO1zqdO3zFf7gH6s+ZT3L9ZH Bxz06nG3cPWWdczljRJg0Zxese+3jCmve72HFSDeAiihjdAbEm1ZSIuFD c=;
X-IronPort-AV: E=Sophos;i="5.33,342,1477983600";  d="scan'208,217";a="356023463"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine02.qualcomm.com with ESMTP; 06 Feb 2017 09:37:51 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8431"; a="861405932"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Feb 2017 09:37:51 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 6 Feb 2017 09:37:50 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Date: Mon, 6 Feb 2017 11:37:48 -0600
Message-ID: <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YSA0KFQ5asAwJhu8IOqrPYXj8hk>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 17:37:53 -0000

--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

On 6 Feb 2017, at 7:36, Daniele Ceccarelli wrote:

> Hi Jari, Pete,
>
> First of all thanks for the accurate review.
>
> All the nits/editorial comments are correct and will be fixed.
>
> Regarding the minor issue:
>
>> 4.1.1:
>>
>> The figure is a bit confusing: There might not exist a "Max Slot 
>> Width at Priority
>> 7" if bit 7 is clear in the Priority field, correct?
>> Perhaps it would be better to just show that as "..." or "Max Slot 
>> Width at
>> Priority n". The thing is, it might only be a single value, followed 
>> by the
>> padding, so having the second value in there might be misleading. 
>> (Perhaps
>> similar constructs are used in other MPLS docs and people will 
>> understand. But
>> it took me a while to figure it out.)
>>
>
> it was difficult to express in the figure the fact that only some of 
> the priorities are advertised. As you said it could be one, two or any 
> number up to 8.
> What about a single field (with ~ on the borders to indicate that it 
> can have variable length) saying "Max Slot Width at Prio n" and then 
> say that 16 bits are used for each prio and when an odd number of 
> priorities is used the field is padded to line up with multiples of 32 
> bits?

Yes, I think that would make more sense to me.

>> The discussion of Priority was very confusing for me. In the third 
>> sentence, do
>> you mean, "A bit is set (1) corresponding to each priority 
>> represented in the
>> sub-TLV, and clear (0) for each priority not represented in the 
>> sub-TLV"? I don't
>> understand the MUST/MUST NOT as you had it. And I don't understand 
>> the
>> last sentence at all. Are you trying to say, "The leftmost bit 
>> (priority level 0)
>> MUST be set, and priority level 0 MUST be advertised in the 
>> sub-TLV."?
>> Otherwise, I don't get it.
>
> It means that if the priority field is set to e.g. 10010010 in the 
> following you would find 4 fields indicating respectively: Max Slot 
> Width at Priority 0, Max Slot Width at Priority 3, Max Slot Width at 
> Priority 6 and since they are 3 a 16 bits padding to 32 bits.

OK, then I think my sentence is clearer for that: "A bit is set (1) 
corresponding to each priority represented in the sub-TLV, and clear (0) 
for each priority not represented in the sub-TLV."

> It also means that at least one priority must be advertised (i.e. 
> priority 00000000 is not allowed).

I get that part ("At least one priority level MUST be advertised"). It's 
the end I don't understand: "that, unless overridden by local policy, 
SHALL be at priority level 0." What does that mean?

>> I don't understand the MAY in the last sentence. Does that mean that 
>> I MAY
>> also set it to the highest possible nominal central frequency 
>> supported by the
>> link? I don't understand what that sentence is trying to tell me.
>>
>
> An example is provided in section 4.1.2, where the available range 
> goes from -2 to +8 but the range supported by the link goes from -9 to 
> +11. The sentence means that even if not available it could be 
> possible to indicate also n=-9 to indicate the starting point of the 
> range supported by the link.
>
>   " In this example, it is assumed that the lowest nominal central
>    frequency supported is n= -9 and the highest is n=11. Note they
>    cannot be used as a nominal central frequency for setting up a LSP,
>    but merely as the way to express the supported frequency range."
>
> I'm ok with dropping the sentence.

I think dropping the sentence would make the most sense.

> Thank you
> Daniele

Thanks for considering my suggested changes.

pr

>> -----Original Message-----
>> From: Jari Arkko [mailto:jari.arkko@piuha.net]
>> Sent: lunedì 6 febbraio 2017 12:32
>> To: Pete Resnick <presnick@qti.qualcomm.com>
>> Cc: gen-art@ietf.org; 
>> draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org;
>> ccamp@ietf.org; ietf@ietf.org
>> Subject: Re: [Gen-art] Review of 
>> draft-ietf-ccamp-flexible-grid-ospf-ext-07
>>
>> Thanks for your review, Pete. Authors, any comments?
>>
>> Jari


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 6 Feb 2017, at 7:36, Daniele Ceccarelli wrote:</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">H=
i Jari, Pete,<br>
<br>
First of all thanks for the accurate review.<br>
<br>
All the nits/editorial comments are correct and will be fixed.<br>
<br>
Regarding the minor issue:<br>
</p>
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999"><p dir=3D"auto">4.1.1:<br>
<br>
The figure is a bit confusing: There might not exist a "Max Slot Width at=
 Priority<br>
7" if bit 7 is clear in the Priority field, correct?<br>
Perhaps it would be better to just show that as "..." or "Max Slot Width =
at<br>
Priority n". The thing is, it might only be a single value, followed by t=
he<br>
padding, so having the second value in there might be misleading. (Perhap=
s<br>
similar constructs are used in other MPLS docs and people will understand=
=2E But<br>
it took me a while to figure it out.)<br>
</p>
</blockquote><p dir=3D"auto">it was difficult to express in the figure th=
e fact that only some of the priorities are advertised. As you said it co=
uld be one, two or any number up to 8.<br>
What about a single field (with ~ on the borders to indicate that it can =
have variable length) saying "Max Slot Width at Prio n" and then say that=
 16 bits are used for each prio and when an odd number of priorities is u=
sed the field is padded to line up with multiples of 32 bits?</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Yes, I think that would make more sense to me.</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">The discussion of Priority w=
as very confusing for me. In the third sentence, do<br>
you mean, "A bit is set (1) corresponding to each priority represented in=
 the<br>
sub-TLV, and clear (0) for each priority not represented in the sub-TLV"?=
 I don't<br>
understand the MUST/MUST NOT as you had it. And I don't understand the<br=
>
last sentence at all. Are you trying to say, "The leftmost bit (priority =
level 0)<br>
MUST be set, and priority level 0 MUST be advertised in the sub-TLV."?<br=
>
Otherwise, I don't get it.</p>
</blockquote><p dir=3D"auto">It means that if the priority field is set t=
o e.g. 10010010 in the following you would find 4 fields indicating respe=
ctively: Max Slot Width at Priority 0, Max Slot Width at Priority 3, Max =
Slot Width at Priority 6 and since they are 3 a 16 bits padding to 32 bit=
s.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">OK, then I think my sentence is clearer for that: "A bit =
is set (1) corresponding to each priority represented in the sub-TLV, and=
 clear (0) for each priority not represented in the sub-TLV."</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">I=
t also means that at least one priority must be advertised (i.e. priority=
 00000000 is not allowed).</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">I get that part ("At least one priority level MUST be adv=
ertised"). It's the end I don't understand: "that, unless overridden by l=
ocal policy, SHALL be at priority level 0." What does that mean?</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">I don't understand the MAY i=
n the last sentence. Does that mean that I MAY<br>
also set it to the highest possible nominal central frequency supported b=
y the<br>
link? I don't understand what that sentence is trying to tell me.<br>
</p>
</blockquote><p dir=3D"auto">An example is provided in section 4.1.2, whe=
re the available range goes from -2 to +8 but the range supported by the =
link goes from -9 to +11. The sentence means that even if not available i=
t could be possible to indicate also n=3D-9 to indicate the starting poin=
t of the range supported by the link.<br>
<br>
  " In this example, it is assumed that the lowest nominal central<br>
   frequency supported is n=3D -9 and the highest is n=3D11. Note they<br=
>
   cannot be used as a nominal central frequency for setting up a LSP,<br=
>
   but merely as the way to express the supported frequency range."<br>
<br>
I'm ok with dropping the sentence.</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">I think dropping the sentence would make the most sense.<=
/p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir=3D"auto">T=
hank you<br>
Daniele</p>
</blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">Thanks for considering my suggested changes.</p>

<p dir=3D"auto">pr</p>

<p dir=3D"auto"></p></div>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px"><blockquote style=
=3D"border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:=
5px; border-left-color:#999"><p dir=3D"auto">-----Original Message-----<b=
r>
From: Jari Arkko [<a href=3D"mailto:jari.arkko@piuha.net" style=3D"color:=
#999">mailto:jari.arkko@piuha.net</a>]<br>
Sent: luned=C3=AC 6 febbraio 2017 12:32<br>
To: Pete Resnick &lt;presnick@qti.qualcomm.com&gt;<br>
Cc: gen-art@ietf.org; draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.or=
g;<br>
ccamp@ietf.org; ietf@ietf.org<br>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-=
07<br>
<br>
Thanks for your review, Pete. Authors, any comments?<br>
<br>
Jari</p>
</blockquote></blockquote></div>
<div style=3D"white-space:normal">

<p dir=3D"auto">-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_E4255D2C-0F36-426B-BE18-AFE4318EFCAF_=--


From nobody Mon Feb  6 10:03:34 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66B1F1295A4 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 10:03:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZKsZ--fBTa3f for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 10:03:30 -0800 (PST)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::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 438F31295A5 for <ietf@ietf.org>; Mon,  6 Feb 2017 10:03:30 -0800 (PST)
Received: by mail-ot0-x22d.google.com with SMTP id 65so67926297otq.2 for <ietf@ietf.org>; Mon, 06 Feb 2017 10:03:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=X6wcIvyIOkGdtFHFd5zrdOQRhMgwyNLy2jgJ1A8beRo=; b=dRONQlOgFo7DqmeaRPaxlF62+WgjT15oqmnKKA9hp6XnJa1VJ9sflc9nXz4Q5TcTXj +mxdqG5eDRNqcxaDEUlq6hFgf5oFIrLpZB82JOT5CDVwrdFZy/4bX549whnfLdkWRnng xbxSETTBAk9he7Q0JNb5VUSlvfulnam+bbhnnEQ7QWlcQnfyl1CJlQ/oHNwFZXJo1eSy xj1VqJ8z1qmUid29es5Et+GMBjxWeLQBYWmg17d9U5zVy2L57EhosbQf0aKTlE1DFCoq kYJlAuumoFMZGkS1THq3cUBfE6jm5i5vPfEMe5p7pY+u+wRVpJoILcVL97SIH/t0Sm2T QrHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=X6wcIvyIOkGdtFHFd5zrdOQRhMgwyNLy2jgJ1A8beRo=; b=cw7h5W2jZpUWAbqHduiuIh6VQ92zncRS1u+UAQeYOVVFqV9HGOsptyRT4257z6nrYi UvhSpE/Vn3EuN1Yv0Z6qeegGIcVJA1kWYI7cJ6w6u3tzpk3A86sqvsRJ4qvUtRZb5lby tfjtrDsIIxNppcp/piItcvp1u+TN9ZnmbLtotlLqdzP/uxswjxBwRzWXXRTg2GAvPos6 NRADS8VibEW3UH9V7dddRh4BlnSqmFAB6uBqo5hyqwsNFMKAooXilKEjR7KxOX8junvk Vf0+ovafJAulAtRVFjZDVqNE4+pzoD3zZNGDHr/u8kfKws1lC2Hk99uR350HlJ8z0DDK cpcA==
X-Gm-Message-State: AMke39kTKC/aXPgt8s7esD3z2hnFyYm0bhMFRlgreTADa22de2V5EMtJebWCJEx19s3Hf1ZStdfBpl6BUOwS1uLV
X-Received: by 10.157.43.22 with SMTP id o22mr6355052otb.33.1486404208947; Mon, 06 Feb 2017 10:03:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Mon, 6 Feb 2017 10:03:27 -0800 (PST)
In-Reply-To: <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org>
From: Wei Chuang <weihaw@google.com>
Date: Mon, 6 Feb 2017 10:03:27 -0800
Message-ID: <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a1141d730e47c1b0547e07239"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J6J_TcYFUcLJeiPHLEraCChNTAQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 18:03:32 -0000

--001a1141d730e47c1b0547e07239
Content-Type: multipart/alternative; boundary=001a1141d730de75bb0547e072ec

--001a1141d730de75bb0547e072ec
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Fri, Feb 3, 2017 at 11:51 AM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Feb 3, 2017, at 2:38 PM, Wei Chuang <weihaw@google.com> wrote:
> >
> > Can you clarify what this means for addresses such as:
> >
> >         U: ietf-dane@духовный.org
> >
> > Not recommended but supported by SmtpUtf8Name.
> >
> >
> >         A: ietf-dane@xn--b1adqpd3ao5c.org
> >
> > Use rfc822Name.  This is recommended.
>
> So, to be clear, for the same domain, some addresses will be
> represented as rfc822Name SAN elements (with the domain in
> A-label form), and other addresses (those with non-ASCII
> localparts) will be represented as SmtpUtf8Name SAN elements
> (with the domain in U-label form).
>

Yes that right.


>
> A verifier checking for an address with a non-ASCII localpart
> will compare against SmtpUtf8Name elements with U-label domain
> encodings, while a verifier checking for an address with an all
> ASCII localpart will check against rfc822Name elements using an
> A-label domain encoding (of the same domain).
>
> Is that right?  Thus the verifier would sometimes need to convert
> from U-labels to A-labels (when the localpart is all ASCII), and

at other times from A-labels to U-labels (when the localpart is not
> all ASCII)...
>

Yes that right.

Now that said what we've done is an extension of current practice keeping
them in place.  Conversions have been what's being done with rfc822Name
comparison for awhile, and that hasn't been changed by this document.  What
we've done is taken a new unhandled circumstance (UTF8 local part) and
specified its behavior.  With the SmtpUtf8Form we kept its scope and form
limited to reduce implementation overhead and limit the likelihood of
bugs.  As noted before we got advice to minimize conversions so we opted
for consistency and for the form where we think email will move towards.
In time those conversions will becomes fewer and fewer.  Yes the verifier
has to do conversions but that's already been practice now for many years
now.

If we focused solely on eliminating conversion as the objective, yes, we
could have done things differently but that would been disruptive to
existing practices.  The approach in the draft is incremental over those
practices since there's a large amount of deployed software.

While the draft does not preclude different email "personae" in a PKIX
certificate, I don't think this would be a good to specify in this draft.
I can see confusion between whether those "personae" represents a single
single person or multiple persons and that should be thought through in its
own draft.

-Wei

--001a1141d730de75bb0547e072ec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 3, 2017 at 11:51 AM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-m_5935343322912641582gmail-"><br>
&gt; On Feb 3, 2017, at 2:38 PM, Wei Chuang &lt;<a href="mailto:weihaw@google.com" target="_blank">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Can you clarify what this means for addresses such as:<br>
&gt;<br>
&gt;         U: <a href="mailto:ietf-dane@%D0%B4%D1%83%D1%85%D0%BE%D0%B2%D0%BD%D1%8B%D0%B9.org" target="_blank">ietf-dane@духовный.org</a><br>
&gt;<br>
&gt; Not recommended but supported by SmtpUtf8Name.<br>
&gt;<br>
&gt;<br>
&gt;         A: <a href="mailto:ietf-dane@xn--b1adqpd3ao5c.org" target="_blank">ietf-dane@xn--b1adqpd3ao5c.org</a><br>
&gt;<br>
&gt; Use rfc822Name.  This is recommended.<br>
<br>
</span>So, to be clear, for the same domain, some addresses will be<br>
represented as rfc822Name SAN elements (with the domain in<br>
A-label form), and other addresses (those with non-ASCII<br>
localparts) will be represented as SmtpUtf8Name SAN elements<br>
(with the domain in U-label form).<br></blockquote><div><br></div><div>Yes that right.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
A verifier checking for an address with a non-ASCII localpart<br>
will compare against SmtpUtf8Name elements with U-label domain<br>
encodings, while a verifier checking for an address with an all<br>
ASCII localpart will check against rfc822Name elements using an<br>
A-label domain encoding (of the same domain).<br>
<br>
Is that right?  Thus the verifier would sometimes need to convert<br>
from U-labels to A-labels (when the localpart is all ASCII), and</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
at other times from A-labels to U-labels (when the localpart is not<br>
all ASCII)...<br></blockquote><div> </div><div>Yes that right.<br></div><div><br></div><div>Now that said what we&#39;ve done is an extension of current practice keeping them in place.  Conversions have been what&#39;s being done with rfc822Name comparison for awhile, and that hasn&#39;t been changed by this document.  What we&#39;ve done is taken a new unhandled circumstance (UTF8 local part) and specified its behavior.  With the SmtpUtf8Form we kept its scope and form limited to reduce implementation overhead and limit the likelihood of bugs.  As noted before we got advice to minimize conversions so we opted for consistency and for the form where we think email will move towards.  In time those conversions will becomes fewer and fewer.  Yes the verifier has to do conversions but that&#39;s already been practice now for many years now.  </div><div><br></div><div>If we focused solely on eliminating conversion as the <!--
-->objective, yes, we could have done things differently but that would been disruptive to existing practices.  The approach in the draft is incremental over those practices since there&#39;s a large amount of deployed software.</div><div><br></div><div>While the draft does not preclude different email &quot;personae&quot; in a PKIX certificate, I don&#39;t think this would be a good to specify in this draft.  I can see confusion between whether those &quot;personae&quot; represents a single single person or multiple persons and that should be thought through in its own draft.</div><div> </div><div>-Wei</div></div></div></div>

--001a1141d730de75bb0547e072ec--

--001a1141d730e47c1b0547e07239
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCCo7pApQsoSfeyVj22PkHrc
qtE9sB1UQoWtgOVfbjwiUTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMDYxODAzMjlaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEABOGom/EOyNYjxmx5rXUWe00skOvAaTy3GUv7zysy
Q69k9ylwEBxW0q1Di9i4Y7NI8dqdSl30W1xq4+PlsTIHsxCV8A4cnQ1bPpnR5DEdZ6eQv+EVXW9B
YrLyrpTOUXS6tIElhcQPC0U0bYPG0y49WNlURp+B7fw2Qnx1ROg9xCoKqc+2Z9Ly73N9jvRyg0O2
u5h/Oq2ydM93VehlDEl2vrCBTX93LmWgCPOkxAAn5wvSIf7q5OxSM7VWqRv7NtRKHwRH9W14ZyRN
H2SiCMpIv1hXbAmdxbxRzw9DCBqHqvOc5FIv8vwfpLeaukuW0520qHPqknVqUbePfgZtVrIPxQ==
--001a1141d730e47c1b0547e07239--


From nobody Mon Feb  6 10:20:27 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A9941295AE for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 10:20:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 ZnF-qWYyvYdR for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 10:20:25 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16A231295A9 for <ietf@ietf.org>; Mon,  6 Feb 2017 10:20:25 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id C978F284E4C; Mon,  6 Feb 2017 18:20:23 +0000 (UTC)
Date: Mon, 6 Feb 2017 18:20:23 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170206182023.GN28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZFiqtYBH2xYZ5psmBVz_RzU8i1g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 18:20:26 -0000

On Mon, Feb 06, 2017 at 10:03:27AM -0800, Wei Chuang wrote:

> > Is that right?  Thus the verifier would sometimes need to convert
> > from U-labels to A-labels (when the localpart is all ASCII), and
> > at other times from A-labels to U-labels (when the localpart is not
> > all ASCII)...
> 
> Yes that right.

Understood.  As I mentioned, I think that avoiding all conversions,
and checking for whatever verbatim address is found in message
headers is less likely to lead to problems at the cost of some more
names in the certificate (all the names that the author uses in
practice, no combinatorial explosion).

We'll see how this plays out in practice.  It will take some time,
as adoption of SMTPUTF8 is still quite low.

-- 
	Viktor.


From nobody Mon Feb  6 10:23:19 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E935A1295BF; Mon,  6 Feb 2017 10:23:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-nfsv4-rpcrdma-bidirection-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148640539293.18910.12490747279422914146.idtracker@ietfa.amsl.com>
Date: Mon, 06 Feb 2017 10:23:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LrDaUYaXy3zhDpfkAH3r-XH0-rI>
Cc: draft-ietf-nfsv4-rpcrdma-bidirection.all@ietf.org, ietf@ietf.org, nfsv4@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 18:23:13 -0000

Reviewer: Jouni Korhonen
Review result: Ready

I am no NFS expert, which makes my review very superficial. The
document itself was good read and did not spot anything
controversial.

The only complaint I have is on the editorial side. There are a number
of abbreviations that are never expanded or referenced where they
originate from. The reader is just assumed to be familiar with
RFC5666, 4506, etc. I would either expand everything (take ULP and XDR
as an example) or have a section/sentence pointing out that this
document uses the terminology established in RFCs x, y and z.


From nobody Mon Feb  6 11:25:37 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D74E129471; Mon,  6 Feb 2017 11:25:31 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PRNybIS64PZS; Mon,  6 Feb 2017 11:25:24 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 6344E12950B; Mon,  6 Feb 2017 11:25:24 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v16JR2k8022994 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 6 Feb 2017 11:27:02 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486409222; bh=FF0cLK87WZq2XNAAewc3vTz0lPGDObJbtIVLBebigAI=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=olLciwATfLs4s7MExqj+vED+42/1J7Pug3ikowFbK6YruUHr8riULkUgxhaCzzXkz mYb4aSmPo/futh/+E5AwGcoI3H37lP7hFEGXQOwKDQaNZwLyAN8Q4Dd5kRetUigLmS xR3NC6WTcpFoAb13wDiYMy+mstj4211koDYg8xdM=
Subject: Re: WG Review: JSON Mail Access Protocol (jmap)
To: ietf@ietf.org, jmap@ietf.org
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net>
Date: Mon, 6 Feb 2017 11:25:15 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wk9CVNHDdW2lm7NXldCcTH_jToc>
Cc: iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 19:25:31 -0000

On 2/3/2017 4:26 PM, The IESG wrote:
> A new IETF WG has been proposed in the Applications and Real-Time Area.

A November version of this charter was circulated and while there have 
been some changes to produce the current draft charter, some issues 
noted earlier have not been reflected here (and did not receive comments 
in November.)


> JSON Mail Access Protocol (jmap)
> -----------------------------------------------------------------------
> Current status: Proposed WG
>
> Chairs:
>   TBD
>
> Assigned Area Director:
>   Alexey Melnikov <aamelnikov@fastmail.fm>
>
> Applications and Real-Time Area Directors:
>   Ben Campbell <ben@nostrum.com>
>   Alissa Cooper <alissa@cooperw.in>
>   Alexey Melnikov <aamelnikov@fastmail.fm>
>
> Mailing list:
>   Address: jmap@ietf.org
>   To subscribe: https://www.ietf.org/mailman/listinfo/jmap
>   Archive: https://mailarchive.ietf.org/arch/search/?email_list=jmap
>
> Group page: https://datatracker.ietf.org/group/jmap/
>
> Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/
>
> A number of JSON-based representations of email have been developed
> that are proprietary, non-standard, and incompatible with each other.
> These protocols are proliferating due
> to existing standards being insufficient or poorly suited to the
> environments they are operating in, particularly mobile and webmail.

 From my November comments:

      As with others, I take 'representations' to mean formats.  And 
given what JSON is[0] that seems an appropriate interpretation even 
without that word.  So I take this asserted need as having a form of 
email data format that is an alternative to RFC 5322/MIME.

      Prior to chartering, we should document just how extensive the 
current problem of multiple JSON email formats is, to establish the 
practical benefit of unifying it. The theoretical benefit should be 
obvious, but that's not enough to justify the cost of a working group. 
We should establish real market need.

      Having spent quite a bit of my early career on email gatewaying, 
I'll comment that getting a common interchange format is especially 
powerful.  The active protocols aren't irrelevant, but stabilizing the 
message object itself is, IMO, far more important. I'm more than a 
little biased about this strategic approach: It provided the unifying 
base for email, during the Internet's early growth into commercial 
markets.  And it happens that focusing on this narrow requirement 
permits end-to-end -- and I mean the real kind:  author to recipient, 
not just originating operator to receiving operator -- benefits without 
having to change the infrastructure, other than insertion of gateways.

      Working groups need task serialization.  So I'll suggest that 
having an effort to standardize an JSON representation of an 
RFC5322/MIME object would be the highest-leverage first task.

Adding to this:

JSON is a meta-format.  It isn't a 'protocol'.  Something encoded in 
JSON is a format, not a protocol.  Hence one of the tasks apparently 
being chartered would be to create a new message access protocol, 
encoded in JSON.  While that might be worth doing, there needs to be 
clarity that this is more than a 'representation'.  There also needs to 
be clarity about the relationship between the JSON encodings and the 
encodings in 'native' Internet Mail.


> The use of multiple protocols
> to perform actions within a single application creates significant
> support challenges, as users may get a variety of partial failure modes
> (for example, can receive email, but can not send new messages).
> This is further exacerbated if the different protocols are
> authenticated separately.

 From my November comments:

      There is no justification given for this approach.  For each 
activity, there needs to be a clear and solid need documented, based on 
actual industry activities or at least industry statements.  Besides 
clarifying /what/ needs doing, it should serve to indicate likely 
industry uptake after the work is done.

Adding to this:

The IETF email technical community looked at the question of making 
email submission part of IMAP or keeping it separate.  It took an entire 
year to debate this point extensively and (imo) constructively, and 
decided to keep them separate.  The current charter draft appears to 
have decided otherwise, but offers only the barest of justifications, 
which I suspect has not factored in the earlier evaluation.


> The JMAP working group will specify a mechanism to allow clients to
> both view and send email from a server over a single stateless HTTPS
> channel with minimal round trips. A single protocol for receipt and
> submission will resolve long-standing difficulties users face
> setting up clients to talk to servers.
>
> The protocol will support
> push notification of changes using the mechanism defined in RFC 8030.
> This will give mobile clients benefits in terms of battery life and
> network usage. It will also support push notifications via server-sent
> events (https://www.w3.org/TR/eventsource/) for direct connection to
> clients that can support persistent TCP connections.
>
> The work of this group is limited to developing a protocol for a client
> synchronising data with a server. Any server-to-server issues
> are out of scope for this working group.
> New end-to-end encryption mechanisms are out of scope, but the work
> should
> consider how to integrate with existing standards such as S/MIME and
> OpenPGP.

Why not TLS, also?


...

> The working group will deliver the following:
>
> - A problem statement detailing the deployment environment and
>   situations that motivate work on a new protocol for client to
>   server email synchronisation.  The working group may choose
>   not to publish this as an RFC.
>
> - A document describing an extensible protocol and data structures, with
>   support for flood control and batched operations, and operating over
>   a stateless connection such as HTTPS.

'flood control'?  what does this mean, since I assume the target 
protocol won't be using a flooding algorithm.  If it really means 
'congestion control', that's not typically part of an application 
protocol, so why would it be an issue here?

 From the November comments

      Since client/server email access typically benefits from having 
the server retain state about the client's activities, I can't tell 
whether this actually means stateless lower-level transport or whether 
it really does mean a stateless email protocol.  So this needs to be 
made much more clear, as to the what and the why, as well as to the 
benefit that will accrue.

      Given the considerable complexity of HTTP, I continue to fail to 
see why making it be a universal, lower-layer transport is so popular. 
Again, the need and the benefit need to be documented.

Adding to this:

    HTTP/HTTPS are not stateless, since they are connection-based.


> - A document describing how to use the extensible protocol over HTTPS
>   with the data structures expressed as JSON.
>
> - A document describing a data model for email viewing, management,
>   searching, and submission on top of the extensible protocol.
>
> - An executable test suite and documented test cases to assist
>   developers of JMAP servers to ensure they conform to the
>   specifications.

 From the November comments:

      This last is useful, but I think it's not typically an IETF work 
product?



d/

[0] http://www.json.org/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Mon Feb  6 11:42:11 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7645F129478; Mon,  6 Feb 2017 11:42:01 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yuzOZHMQ9gEF; Mon,  6 Feb 2017 11:41:59 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 6DD6C129458; Mon,  6 Feb 2017 11:41:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486410118; d=isode.com; s=june2016; i=@isode.com; bh=MREtn65r3SpwC8tbGiEeDlVVZMhD8aUefQQ6alGndcU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=nsfHCJDcNk6rcN8Sw7MwtApGub3iTzkI+SDPDRV6C1aExr6XN1DZSIGFf/709W71LuxYOx 94X/ccpGrRZyJvSISqVcXdt+6ZjDBy6FzoecuStzal8/kslTaQgtsw5llSs4NI7QXfcnIB PiBJ72n5em5bpA2QEkRwLNNDxEY1IFQ=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJjRhQAY16Ou@statler.isode.com>; Mon, 6 Feb 2017 19:41:58 +0000
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: dcrocker@bbiw.net, ietf@ietf.org, jmap@ietf.org
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com>
Date: Mon, 6 Feb 2017 19:41:57 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YcWw0XdOkg7jVhfZqeJZavxH1IA>
Cc: iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 19:42:01 -0000

Hi Dave,

I am mostly proxying proponents of the Charter, but I did some editing 
pass over it, so I am replying to some of your comments.


On 06/02/2017 19:25, Dave Crocker wrote:
> On 2/3/2017 4:26 PM, The IESG wrote:
>> A new IETF WG has been proposed in the Applications and Real-Time Area.
>
> A November version of this charter was circulated and while there have 
> been some changes to produce the current draft charter, some issues 
> noted earlier have not been reflected here (and did not receive 
> comments in November.)
>
>
>> JSON Mail Access Protocol (jmap)
>> -----------------------------------------------------------------------
>> Current status: Proposed WG
>>
>> Chairs:
>>   TBD
>>
>> Assigned Area Director:
>>   Alexey Melnikov <aamelnikov@fastmail.fm>
>>
>> Applications and Real-Time Area Directors:
>>   Ben Campbell <ben@nostrum.com>
>>   Alissa Cooper <alissa@cooperw.in>
>>   Alexey Melnikov <aamelnikov@fastmail.fm>
>>
>> Mailing list:
>>   Address: jmap@ietf.org
>>   To subscribe: https://www.ietf.org/mailman/listinfo/jmap
>>   Archive: https://mailarchive.ietf.org/arch/search/?email_list=jmap
>>
>> Group page: https://datatracker.ietf.org/group/jmap/
>>
>> Charter: https://datatracker.ietf.org/doc/charter-ietf-jmap/
>>
>> A number of JSON-based representations of email have been developed
>> that are proprietary, non-standard, and incompatible with each other.
>> These protocols are proliferating due
>> to existing standards being insufficient or poorly suited to the
>> environments they are operating in, particularly mobile and webmail.
>
> From my November comments:
>
>      As with others, I take 'representations' to mean formats. And 
> given what JSON is[0] that seems an appropriate interpretation even 
> without that word.  So I take this asserted need as having a form of 
> email data format that is an alternative to RFC 5322/MIME.
>
>      Prior to chartering, we should document just how extensive the 
> current problem of multiple JSON email formats is, to establish the 
> practical benefit of unifying it. The theoretical benefit should be 
> obvious, but that's not enough to justify the cost of a working group. 
> We should establish real market need.
>
>      Having spent quite a bit of my early career on email gatewaying, 
> I'll comment that getting a common interchange format is especially 
> powerful.  The active protocols aren't irrelevant, but stabilizing the 
> message object itself is, IMO, far more important. I'm more than a 
> little biased about this strategic approach: It provided the unifying 
> base for email, during the Internet's early growth into commercial 
> markets.  And it happens that focusing on this narrow requirement 
> permits end-to-end -- and I mean the real kind:  author to recipient, 
> not just originating operator to receiving operator -- benefits 
> without having to change the infrastructure, other than insertion of 
> gateways.
>
>      Working groups need task serialization.  So I'll suggest that 
> having an effort to standardize an JSON representation of an 
> RFC5322/MIME object would be the highest-leverage first task.
I don't think there is intent to specify full mapping of RFC5322/MIME to 
JSON. IMAP has BODYSTRUCTURE element that contains parsed representation 
of message structure and most commonly used header fields for different 
body parts. The intent is to do the same here.
Additionally, it is still possible to retrieve full RFC5322/MIME 
payloads over JMAP.

I have tried to reflect your comments in the Charter, but I struggled a 
bit. If you can suggest how to make the above clearer, that would be 
much appreciated.
>
> Adding to this:
>
> JSON is a meta-format.  It isn't a 'protocol'.  Something encoded in 
> JSON is a format, not a protocol.  Hence one of the tasks apparently 
> being chartered would be to create a new message access protocol, 
> encoded in JSON.  While that might be worth doing, there needs to be 
> clarity that this is more than a 'representation'.
No, it is a representation. See above.
> There also needs to be clarity about the relationship between the JSON 
> encodings and the encodings in 'native' Internet Mail.

See drafts (and above).
>
>> The use of multiple protocols
>> to perform actions within a single application creates significant
>> support challenges, as users may get a variety of partial failure modes
>> (for example, can receive email, but can not send new messages).
>> This is further exacerbated if the different protocols are
>> authenticated separately.
>
> From my November comments:
>
>      There is no justification given for this approach.  For each 
> activity, there needs to be a clear and solid need documented, based 
> on actual industry activities or at least industry statements.  
> Besides clarifying /what/ needs doing, it should serve to indicate 
> likely industry uptake after the work is done.

I am not sure what kind of justification is needed. This is a clear 
deployment problem.
> Adding to this:
>
> The IETF email technical community looked at the question of making 
> email submission part of IMAP or keeping it separate.  It took an 
> entire year to debate this point extensively and (imo) constructively, 
> and decided to keep them separate.  The current charter draft appears 
> to have decided otherwise, but offers only the barest of 
> justifications, which I suspect has not factored in the earlier 
> evaluation.
There was a followup discussion about doing an IMAP extension for 
submission and how it should look like to remain compatible with SMTP 
Submission. I don't think this is an attempt to just ignore earlier 
discussions.

>> The JMAP working group will specify a mechanism to allow clients to
>> both view and send email from a server over a single stateless HTTPS
>> channel with minimal round trips. A single protocol for receipt and
>> submission will resolve long-standing difficulties users face
>> setting up clients to talk to servers.
>>
>> The protocol will support
>> push notification of changes using the mechanism defined in RFC 8030.
>> This will give mobile clients benefits in terms of battery life and
>> network usage. It will also support push notifications via server-sent
>> events (https://www.w3.org/TR/eventsource/) for direct connection to
>> clients that can support persistent TCP connections.
>>
>> The work of this group is limited to developing a protocol for a client
>> synchronising data with a server. Any server-to-server issues
>> are out of scope for this working group.
>> New end-to-end encryption mechanisms are out of scope, but the work
>> should
>> consider how to integrate with existing standards such as S/MIME and
>> OpenPGP.
>
> Why not TLS, also?

TLS is assumed. I think the Charter text says HTTPS elsewhere.
>
>
> ...
>
>> The working group will deliver the following:
>>
>> - A problem statement detailing the deployment environment and
>>   situations that motivate work on a new protocol for client to
>>   server email synchronisation.  The working group may choose
>>   not to publish this as an RFC.
>>
>> - A document describing an extensible protocol and data structures, with
>>   support for flood control and batched operations, and operating over
>>   a stateless connection such as HTTPS.
>
> 'flood control'?  what does this mean, since I assume the target 
> protocol won't be using a flooding algorithm.  If it really means 
> 'congestion control', that's not typically part of an application 
> protocol, so why would it be an issue here?
>
> From the November comments
>
>      Since client/server email access typically benefits from having 
> the server retain state about the client's activities, I can't tell 
> whether this actually means stateless lower-level transport or whether 
> it really does mean a stateless email protocol. 

Stateless lower level transport. The addition of "such as HTTPS" was 
trying to make this clearer.

> So this needs to be made much more clear, as to the what and the why, 
> as well as to the benefit that will accrue.
>
>      Given the considerable complexity of HTTP, I continue to fail to 
> see why making it be a universal, lower-layer transport is so popular. 
> Again, the need and the benefit need to be documented.

Presence of tools for manipulating JSON and ease of development. This 
was mentioned on the JMAP mailing list. I don't think this needs to be 
said here.

> Adding to this:
>
>    HTTP/HTTPS are not stateless, since they are connection-based.
Yeah, I struggled with this a bit. Each request/response can be sent on 
a separate connection and it is stateless in that sense.

>
>> - A document describing how to use the extensible protocol over HTTPS
>>   with the data structures expressed as JSON.
>>
>> - A document describing a data model for email viewing, management,
>>   searching, and submission on top of the extensible protocol.
>>
>> - An executable test suite and documented test cases to assist
>>   developers of JMAP servers to ensure they conform to the
>>   specifications.
>
> From the November comments:
>
>      This last is useful, but I think it's not typically an IETF work 
> product?

I don't mind deleting this, but I would like to see if IESG approves 
this as is ;-).

Best Regards,
Alexey
>
>
>
> d/
>
> [0] http://www.json.org/


From nobody Mon Feb  6 11:59:32 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D391295E4 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 11:59:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VJWTuhlbiNsB for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 11:59:30 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 68C511295E1 for <ietf@ietf.org>; Mon,  6 Feb 2017 11:59:30 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id v23so115606238qtb.0 for <ietf@ietf.org>; Mon, 06 Feb 2017 11:59:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=isZm93nigLSvKFFSVRHTv74jIgc7enbg2HSQhR+IDSw=; b=nTcG7P7H6FWHPFRdszT4qeZsj7+04M6Onz9lerYFgW+uhi6SGgMN5abqh4IM8/6gBK wPNE27zSfdxuKevCAlUCSD2+62yPF37CTHJ+c29gbIR4/UEU4pgHu/Tr1XI/GANe05RF DGeX2qUQdeX+Phw+t3JnhPID+85HT+XaSPozRqdmgz35Q+RMkSrSANTDI8tFRq5Z/LJP bgSB0zxgJ7fVsSaWNyrgQQAMoWru8oxsQpJePNLATFvWyaq2PWjGIxQhWXt0DSHKiCgQ Pkqd/MkXYL0BlgbHBoP9nlVlxiyvikyhSZys7JVB5Hbi6zjFiQQLjE7lQD8q+IKs8/cJ 2Msg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=isZm93nigLSvKFFSVRHTv74jIgc7enbg2HSQhR+IDSw=; b=DCISAn7Zg0CKixSjlI5mVojS4c55ZdEE62bveXR4Hh9USqnbiU5NA/F1uzqAfe2U35 FEoGaFeodpgtABuOL0aTWv0dBhZ0w6zQfz4EgVsNwLN6dmTH059LDp0OpcyNV55wjltP A+m+xCAvXzt+Ur/dImFSF81FiM6u4yoiusSIsEK/ystVFwdJXKYA4PeeRx0Fy9wl+/57 vQAbB+JmZhzwtcNzdy8GZD4qYeRKMpT43fA9Hd5LHATOS+ROxY1NqtOFPSP64saq3YVV Tz0O+mSOQj6af9BDrLuwOAVplzzOfTHgfomgYqXnml9H5YeTDSljma71R69G44lLz4q7 z+tg==
X-Gm-Message-State: AMke39l2Gs55frXelaUNMYdr6tUwayNzO4DhfvI881OK2HlZIxExlUuLDt4kV4Axqp5GxwtkwKb5BbE5gT7xBA==
X-Received: by 10.200.56.211 with SMTP id g19mr10647233qtc.177.1486411169241;  Mon, 06 Feb 2017 11:59:29 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.140.19.72 with HTTP; Mon, 6 Feb 2017 11:59:28 -0800 (PST)
In-Reply-To: <148640984525.18879.14222110335591335067.idtracker@ietfa.amsl.com>
References: <148640984525.18879.14222110335591335067.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 6 Feb 2017 14:59:28 -0500
X-Google-Sender-Auth: 6GFkHw-Z0phKsS6BGH0qofYcL4c
Message-ID: <CALaySJJALzYE_dUyXX7fmhMHaGZpwY7my5Q-J8gNqNCk0yy=LQ@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-01.txt
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qwi48WuCtUycfRShDeBor3DLM5U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 19:59:32 -0000

It's been a while since we had the discussion about the -00 version of
this document.  I've updated it, and I think -01 reflects the result
of that discussion.  I've asked Ben to last call it, but, of course,
we don't have to wait for that if there's discussion on the -01
version.

What I did here was (1) remove the deprecation of the synonyms,
because we did not have consensus to do that, and (2) re-word the
replacement text and most references to "capitalized" to clarify.

I do think this is ready and useful.  Y'all?

Barry


On Mon, Feb 6, 2017 at 2:37 PM,  <internet-drafts@ietf.org> wrote:
>
> A new version of I-D, draft-leiba-rfc2119-update-01.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Name:           draft-leiba-rfc2119-update
> Revision:       01
> Title:          Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
> Document date:  2017-02-06
> Group:          Individual Submission
> Pages:          4
> URL:            https://www.ietf.org/internet-drafts/draft-leiba-rfc2119-update-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-leiba-rfc2119-update/
> Htmlized:       https://tools.ietf.org/html/draft-leiba-rfc2119-update-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-leiba-rfc2119-update-01
>
> Abstract:
>    RFC 2119 specifies common key words that may be used in protocol
>    specifications.  This document aims to reduce the ambiguity by
>    clarifying that only UPPERCASE usage of the key words have the
>    defined special meanings.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>


From nobody Mon Feb  6 12:04:46 2017
Return-Path: <adrien@qbik.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB75129411; Mon,  6 Feb 2017 12:04:44 -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 autolearn_force=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 JTcPHgvBn23l; Mon,  6 Feb 2017 12:04:43 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5CAB12960E; Mon,  6 Feb 2017 12:04:42 -0800 (PST)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.4 (Build 5913)) with SMTP id <0000957243@smtp.qbik.com>; Tue, 07 Feb 2017 09:04:39 +1300
From: "Adrien de Croy" <adrien@qbik.com>
To: "Alexey Melnikov" <alexey.melnikov@isode.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>, "jmap@ietf.org" <jmap@ietf.org>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
Date: Mon, 06 Feb 2017 20:04:39 +0000
Message-Id: <em865c99db-6292-4000-90a1-066159ed2b76@bodybag>
In-Reply-To: <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com>
User-Agent: eM_Client/6.0.24928.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LYjn5hiRBO6JNzahF4zJND7vzzE>
Cc: iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Adrien de Croy <adrien@qbik.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 20:04:45 -0000

>>Adding to this:
>>
>>    HTTP/HTTPS are not stateless, since they are connection-based.
A lot of the people on the HTTP WG would have an issue with this=20
statement.

In fact there has been a lot of discussion about the evils of=20
connection-oriented anything in regard to HTTP, especially around=20
authentication (e.g. NTLM).

There are proxies that reuse upstream connections between different=20
clients, the protocol (1.1 at least) is designed to be stateless in=20
terms of each message being independent of others, whether on the same=20
connection or not.

So I wouldn't start a new protocol based on the presumption that=20
HTTP/HTTPS is connection-oriented and not stateless.


>>


From nobody Mon Feb  6 12:12:03 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3BA91294A6; Mon,  6 Feb 2017 12:11:58 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4PujrhF4OTw3; Mon,  6 Feb 2017 12:11:57 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 65E16129606; Mon,  6 Feb 2017 12:11:57 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v16KDYbh026375 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 6 Feb 2017 12:13:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486412015; bh=KbTWi4RP2Dd3wyRANIzfL4FFE7v9hCmbETFL7/4fKh8=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=PiWkaid2hPyYo8cmGGApLGB78oPMajC90V7JbAPMA/I8jmNBaPnPSSThtznpBLm+c ayC5iEJo+g2dwFsu+P4MxAB94oPkTWrdiBboc+Aw5LCsR6/VM75j2tXIF2yy4lN9O5 DklvWgaKfWQCv+lNW+vl6P7wtFZJODJxPRwv2e7A=
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
Date: Mon, 6 Feb 2017 12:11:47 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4N10XAAP54fFylGVc607bvlXhw8>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 20:11:59 -0000

Alexey, thanks for the quick followup.

inline...

On 2/6/2017 11:41 AM, Alexey Melnikov wrote:
>>      Working groups need task serialization.  So I'll suggest that
>> having an effort to standardize an JSON representation of an
>> RFC5322/MIME object would be the highest-leverage first task.
> I don't think there is intent to specify full mapping of RFC5322/MIME to
> JSON. IMAP has BODYSTRUCTURE element that contains parsed representation
> of message structure and most commonly used header fields for different
> body parts. The intent is to do the same here.
> Additionally, it is still possible to retrieve full RFC5322/MIME
> payloads over JMAP.

This highlights the need to have far more clarity about what specific 
work is to be done and what is not.  The existing text has some generic 
out-of-scope text, but nothing as frankly useful as your above comment. 
Given that comment, I can't text what parts of the resulting jmap 
service will use 'native' Internet Mail technical details and what parts 
will be new-for-JSON.


> I have tried to reflect your comments in the Charter, but I struggled a
> bit. If you can suggest how to make the above clearer, that would be
> much appreciated.

I make a point of offering candidate text when I think I understand the 
context and needs well enough.  Unfortunately I don't have that here. 
Hence, questions and general suggestions is the best I can offer.  Sorry.


>> Adding to this:
>>
>> JSON is a meta-format.  It isn't a 'protocol'.  Something encoded in
>> JSON is a format, not a protocol.  Hence one of the tasks apparently
>> being chartered would be to create a new message access protocol,
>> encoded in JSON.  While that might be worth doing, there needs to be
>> clarity that this is more than a 'representation'.
> No, it is a representation. See above.

As soon as one says that the task is client/server interaction, one is 
declaring the goal of a protocol.  So it is more than just a format 
(representation.)


 >> There also needs to be clarity about the relationship between the JSON
 >> encodings and the encodings in 'native' Internet Mail.
> See drafts (and above).

Drafts?  What drafts?  Perhaps you mean:

    https://tools.ietf.org/html/draft-jenkins-jmap

Except that no draft is cited in the charter.


>>> The use of multiple protocols
>>> to perform actions within a single application creates significant
>>> support challenges, as users may get a variety of partial failure modes
>>> (for example, can receive email, but can not send new messages).
>>> This is further exacerbated if the different protocols are
>>> authenticated separately.
>>
>> From my November comments:
>>
>>      There is no justification given for this approach.  For each
>> activity, there needs to be a clear and solid need documented, based
>> on actual industry activities or at least industry statements.
>> Besides clarifying /what/ needs doing, it should serve to indicate
>> likely industry uptake after the work is done.
>
> I am not sure what kind of justification is needed. This is a clear
> deployment problem.

As I said, there was a year-long, serious and diligent debate about this 
in the IETF and it came to a different conclusion.  So it's not nearly 
as 'clear' as you are asserting.


>> Adding to this:
>>
>> The IETF email technical community looked at the question of making
>> email submission part of IMAP or keeping it separate.  It took an
>> entire year to debate this point extensively and (imo) constructively,
>> and decided to keep them separate.  The current charter draft appears
>> to have decided otherwise, but offers only the barest of
>> justifications, which I suspect has not factored in the earlier
>> evaluation.
> There was a followup discussion about doing an IMAP extension for
> submission and how it should look like to remain compatible with SMTP
> Submission. I don't think this is an attempt to just ignore earlier
> discussions.

Discussion is different than deployment.  The fact that it isn't used 
now suggests that the benefit(s) you are asserting aren't as clear-cut 
as is being implied here.  To the extent that the current proposal does 
indeed represent a consideration of the prior, extended IETF work in 
this realm, the charter should indicate the basis for making a different 
choice here, in terms of the points considered earlier.



>>> The working group will deliver the following:
>>>
>>> - A problem statement detailing the deployment environment and
>>>   situations that motivate work on a new protocol for client to
>>>   server email synchronisation.  The working group may choose
>>>   not to publish this as an RFC.
>>>
>>> - A document describing an extensible protocol and data structures, with
>>>   support for flood control and batched operations, and operating over
>>>   a stateless connection such as HTTPS.
>>
>> 'flood control'?  what does this mean, since I assume the target
>> protocol won't be using a flooding algorithm.  If it really means
>> 'congestion control', that's not typically part of an application
>> protocol, so why would it be an issue here?
>>
>> From the November comments
>>
>>      Since client/server email access typically benefits from having
>> the server retain state about the client's activities, I can't tell
>> whether this actually means stateless lower-level transport or whether
>> it really does mean a stateless email protocol.
>
> Stateless lower level transport. The addition of "such as HTTPS" was
> trying to make this clearer.

Didn't succeed, given that HTTP runs over TCP.


>> So this needs to be made much more clear, as to the what and the why,
>> as well as to the benefit that will accrue.
>>
>>      Given the considerable complexity of HTTP, I continue to fail to
>> see why making it be a universal, lower-layer transport is so popular.
>> Again, the need and the benefit need to be documented.
>
> Presence of tools for manipulating JSON and ease of development. This
> was mentioned on the JMAP mailing list. I don't think this needs to be
> said here.

A new protocol is choosing to operate over a very complex substrate. 
Having some basic justification for that choice, in the charter, seems 
somewhere between appropriate and obligatory.


>> Adding to this:
>>
>>    HTTP/HTTPS are not stateless, since they are connection-based.
> Yeah, I struggled with this a bit. Each request/response can be sent on
> a separate connection and it is stateless in that sense.

In other words, jmap will be stateless.  That's what the charter should say.

...Except that that seems odd, since it means that every exchange would 
have to self-identify and self-authorize.

I suspect that's not what's going to be defined.  So, really, it isn't 
obvious to me at all what will be stateless.

d/


-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Mon Feb  6 13:02:07 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A25DA1294D7; Mon,  6 Feb 2017 13:02:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3KWVXtxjUBey; Mon,  6 Feb 2017 13:02:01 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 F16FA1293F9; Mon,  6 Feb 2017 13:02:00 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v77so131945995wmv.0; Mon, 06 Feb 2017 13:02:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=cbJLfx0dw+3Oudf2DAt7k9Xm83PCNGCdn5QV1ZMbElU=; b=YFxD7s9tDLOK3IyvWli6l29kTI/kA9T2E6NzJiA2DVmLQZc7NGFnxUEsS0mxCf2Qjv Uof22cypfACdonQ27OD+LQpVj1a3sxBaz+TMGLNW6e8XMMWEe0t10eiLYffMaKAAHzpf 4MWxrHiFtn2w+zNqUCbGvA0hJVr9BCFQwiLEMvuFvVkVgvrVrytF6lPRa5KaL1WPPLGX yY/Hf08gdg+RzwNWTOKkRUfsrFcRaVXND/SvLDhdfu19nu+mIvaFhqfZ8kW8tt6rxqwv /VOmPajB0rgYEfeqWgQ6xR7yA1e9pY5LQFFntCNo+PtNT9O+4IDgKDBFOGB2BK8TnaTJ n2Dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=cbJLfx0dw+3Oudf2DAt7k9Xm83PCNGCdn5QV1ZMbElU=; b=YisjFDtAnWhRr+7HAxs4FQncCpMT6xfjbgkwzHtaDXeqZd+rqV+Tt7vSpE57R/s8bT VFr+h+x/kINHpjHgpcvPTSKN8UdyGj5nOzfXmiW7s4N/+9aTn0jwKNotrvenz3XBvLNG v5Qwi5+NPs7h4GJrw7Nv09gduII/nU935xWUmr9+6wsG36y4VAFoYCqbd/R9ja7fJGKR YBQmAi/XG+VurIywUyJnsOl3QouI3B3kRdV99bxe7nPjzNvGPEqXNTyfHtOqQIc9OkOL 4CB33HMM8k2q98vtthq/i3gMDTqEwB0piFuIJXOrWZy1W5xrH2Ud4oK/e8eNhLIaK51U 717Q==
X-Gm-Message-State: AIkVDXLulhl13fUklwDi1k417iN+HcbeJtL3iIiX7Lmo7t4orMCG4H5FotgCjuggs9vx5vAjUU3v6QM2eWnuXQ==
X-Received: by 10.223.135.43 with SMTP id a40mr12489937wra.197.1486414919391;  Mon, 06 Feb 2017 13:01:59 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.194.221.6 with HTTP; Mon, 6 Feb 2017 13:01:58 -0800 (PST)
In-Reply-To: <em865c99db-6292-4000-90a1-066159ed2b76@bodybag>
References: <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <em865c99db-6292-4000-90a1-066159ed2b76@bodybag>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 6 Feb 2017 16:01:58 -0500
X-Google-Sender-Auth: saIxC86FeK_DimMlnFpn5B8I6A4
Message-ID: <CAMm+LwgoxX4pOZfGhg0-Xw_XiYttzR8MHrEi+GyyB_9wTN-_5w@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: Adrien de Croy <adrien@qbik.com>
Content-Type: multipart/alternative; boundary=001a114981324260c60547e2f196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iP6V4guiSjesjnQYioZnPriW06Q>
Cc: "jmap@ietf.org" <jmap@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, iesg <iesg@ietf.org>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 21:02:02 -0000

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

On Mon, Feb 6, 2017 at 3:04 PM, Adrien de Croy <adrien@qbik.com> wrote:

>
>
>
> Adding to this:
>>>
>>>    HTTP/HTTPS are not stateless, since they are connection-based.
>>>
>> A lot of the people on the HTTP WG would have an issue with this
> statement.
>
> In fact there has been a lot of discussion about the evils of
> connection-oriented anything in regard to HTTP, especially around
> authentication (e.g. NTLM).
>
> There are proxies that reuse upstream connections between different
> clients, the protocol (1.1 at least) is designed to be stateless in terms
> of each message being independent of others, whether on the same connecti=
on
> or not.
>
> So I wouldn't start a new protocol based on the presumption that
> HTTP/HTTPS is connection-oriented and not stateless.
>

=E2=80=8B+1

I was hoping we could go a different route here:

1) Write the QUIC protocol. Gives us a multiplexed TCP capability
2) Write a thin shim on QUIC for Web services to replace HTTP presentation
3) Use the result and JSON encoding as the presentation layer for AppsNG=E2=
=80=8B

=E2=80=8BDoing JMAP on QUIC right now is error 32: Research on Research. Bu=
t doing
JMAP on HTTP means inventing a second MUX layer. Also bad.=E2=80=8B

=E2=80=8BThere is clearly potential =E2=80=8Bto improve on IMAP user experi=
ence. GMAIL
isn't very much different but it is a lot more responsive because the
protocol does things like return the overviews for the 20 latest headers
that the app is trying to present to the user rather than the client going
into hyperspace as it downloads 15 years of messages.

Yes, I know it is possible to do some of the same stuff if the
application's IMAP foo is really good. But being able to optimize the round
trips because you control both ends of the protocol is very powerful.

HTTP has a lot of cruft in it to support browsers running on the 1990s
Internet when the whole continent of Australia was connected by a 56Kb
dialup and T1 was considered lightning fast. And one of the problems with
that sort of cruft is that no matter how rubbish it is or how many problems
it creates, there will always be people who squeak if you try to take it
out.

I am profoundly unimpressed by arguments about using HTTP features like
caching in Web services. If HTTP caching works for your Web Service it is
probably because what you are doing is re-implementing HTTP in HTTP badly.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Fe=
b 6, 2017 at 3:04 PM, Adrien de Croy <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:adrien@qbik.com" target=3D"_blank">adrien@qbik.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Adding to this:<br>
<br>
=C2=A0 =C2=A0HTTP/HTTPS are not stateless, since they are connection-based.=
<br>
</blockquote></blockquote></span>
A lot of the people on the HTTP WG would have an issue with this statement.=
<br>
<br>
In fact there has been a lot of discussion about the evils of connection-or=
iented anything in regard to HTTP, especially around authentication (e.g. N=
TLM).<br>
<br>
There are proxies that reuse upstream connections between different clients=
, the protocol (1.1 at least) is designed to be stateless in terms of each =
message being independent of others, whether on the same connection or not.=
<br>
<br>
So I wouldn&#39;t start a new protocol based on the presumption that HTTP/H=
TTPS is connection-oriented and not stateless.<br></blockquote><div><div cl=
ass=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gma=
il_default" style=3D"font-size:small">=E2=80=8B+1</div><div class=3D"gmail_=
default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">I was hoping we could go a different route here:</=
div><div class=3D"gmail_default" style=3D"font-size:small"><br></div><div c=
lass=3D"gmail_default" style=3D"font-size:small">1) Write the QUIC protocol=
. Gives us a multiplexed TCP capability</div><div class=3D"gmail_default" s=
tyle=3D"font-size:small">2) Write a thin shim on QUIC for Web services to r=
eplace HTTP presentation</div><div class=3D"gmail_default" style=3D"font-si=
ze:small">3) Use the result and JSON encoding as the presentation layer for=
 AppsNG=E2=80=8B</div><br></div><div><div class=3D"gmail_default" style=3D"=
font-size:small">=E2=80=8BDoing JMAP on QUIC right now is error 32: Researc=
h on Research. But doing JMAP on HTTP means inventing a second MUX layer. A=
lso bad.=E2=80=8B</div><br></div><div><div class=3D"gmail_default" style=3D=
"font-size:small">=E2=80=8BThere is clearly potential =E2=80=8Bto improve o=
n IMAP user experience. GMAIL isn&#39;t very much different but it is a lot=
 more responsive because the protocol does things like return the overviews=
 for the 20 latest headers that the app is trying to present to the user ra=
ther than the client going into hyperspace as it downloads 15 years of mess=
ages.</div><div class=3D"gmail_default" style=3D"font-size:small"><br></div=
><div class=3D"gmail_default" style=3D"font-size:small">Yes, I know it is p=
ossible to do some of the same stuff if the application&#39;s IMAP foo is r=
eally good. But being able to optimize the round trips because you control =
both ends of the protocol is very powerful.</div><div class=3D"gmail_defaul=
t" style=3D"font-size:small"><br></div><div class=3D"gmail_default" style=
=3D"font-size:small">HTTP has a lot of cruft in it to support browsers runn=
ing on the 1990s Internet when the whole continent of Australia was connect=
ed by a 56Kb dialup and T1 was considered lightning fast. And one of the pr=
oblems with that sort of cruft is that no matter how rubbish it is or how m=
any problems it creates, there will always be people who squeak if you try =
to take it out.</div></div><div class=3D"gmail_default" style=3D"font-size:=
small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">I a=
m profoundly unimpressed by arguments about using HTTP features like cachin=
g in Web services. If HTTP caching works for your Web Service it is probabl=
y because what you are doing is re-implementing HTTP in HTTP badly.</div><d=
iv><br></div></div></div></div>

--001a114981324260c60547e2f196--


From nobody Mon Feb  6 13:20:45 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 73EBD12949E; Mon,  6 Feb 2017 13:20:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms.ietf@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-nfsv4-rfc5666bis-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148641603043.18879.10370223612053997606.idtracker@ietfa.amsl.com>
Date: Mon, 06 Feb 2017 13:20:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vx9AnqWl3Fce1_dwF5_VGZ_iEVo>
Cc: ietf@ietf.org, draft-ietf-nfsv4-rfc5666bis.all@ietf.org, nfsv4@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 21:20:30 -0000

Reviewer: Ralph Droms
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-rfc5666bis-09
Reviewer: Ralph Droms
Review Date: 2017-02-06
IETF LC End Date: 2017-02-07
IESG Telechat date: Not scheduled for a telechat

Summary: draft-ietf-nfsv4-rfc5666bis-09 is ready for publication; it
is a well-written document that I found readable and understandable
based on my basic (and, likely, quite out of date!) knowledge of ONS
RPC, XDR and NFS.

Major issues: None

Minor issues: None

Nits/editorial comments:  None



From nobody Mon Feb  6 16:52:15 2017
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE6D12954F for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 16:52:14 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 yDKTBOIPEzjX for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 16:52:13 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 4F56012954C for <ietf@ietf.org>; Mon,  6 Feb 2017 16:52:13 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 38CC9909F9F; Mon,  6 Feb 2017 19:52:12 -0500 (EST)
Date: Mon, 6 Feb 2017 19:52:12 -0500
From: John Leslie <john@jlc.net>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-01.txt
Message-ID: <20170207005212.GP10525@verdi>
References: <148640984525.18879.14222110335591335067.idtracker@ietfa.amsl.com> <CALaySJJALzYE_dUyXX7fmhMHaGZpwY7my5Q-J8gNqNCk0yy=LQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALaySJJALzYE_dUyXX7fmhMHaGZpwY7my5Q-J8gNqNCk0yy=LQ@mail.gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NuCUgYuYL7kl2vpuBk-cORUfQms>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 00:52:14 -0000

Barry Leiba <barryleiba@computer.org> wrote:
> 
> I do think this is ready and useful.  Y'all?

   Looks good to me.

--
John Leslie <john@jlc.net>


From nobody Mon Feb  6 17:31:51 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19FE7129576 for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 17:31:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cF5bQ-cnEX8Q for <ietf@ietfa.amsl.com>; Mon,  6 Feb 2017 17:31:49 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 01C1A129573 for <ietf@ietf.org>; Mon,  6 Feb 2017 17:31:49 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id e4so28219102pfg.1 for <ietf@ietf.org>; Mon, 06 Feb 2017 17:31:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=PjFyFYR1XQ6hoambC8oVgVr0hawf6wgL/cc4mlGhZ0U=; b=CdYXDCi71oZWPFTKEx0KDrGw928MDsaU7tSpHDx2hfvZmW0az6q+H0b8ha7XTBWAUw xiHkjiTIgma3+MIIM9paLuFrFBrDyVegqhDG/q9+KdJZ1VFTSme0t6sak67cLvMu1/mB HTJNpSMPcqfwn8TmYcY0XO3LSE6brJ3MRhAxqTLv5uABQt0ZpCDQIrDLbDuMChjAwzkG /Ll0fZrLM5UjmWcc5DFCFqgH0NG/GQSMzyprWzf05pHAOrgMuDB58+QI88UBtt0L0VTn JX5+I5cdizZzQriaMM2Wj+9iwEMhZlRm9wzA/2yU8ogOE4dPpSAyZVUhxlwu6hXIHDhk NjxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=PjFyFYR1XQ6hoambC8oVgVr0hawf6wgL/cc4mlGhZ0U=; b=Y5OAaWXYOMLDdJOSJ4d/4l6WqvI1NwN9twx8LCBCMTycRzGlAM4nlMzjE1UsUK8xP8 jixMwlrHn1GEjM4ZsIoKF8V02RW3G/xnbrEiFaQvSUHueL7/KAC7NS/+ncN85PUhe8Xw mpuJnFPt85cJi3huq9k/dLws1V2GfdEtnKJhcqE70M0xCwUaRPdUR4KyfRCeoSKbOiQc aRi2IJwouDCAmvnPnJZL2vriIQ8jnu7mNJjFDmhD5lN0TgORq1Xk8ZugRYExMEMSCJS1 Wols6ilQudASzi7Sn1f7RP5Jxb8v0D2yYUbGXMkWBdgVHrnS4oZIfMa3vOk2DuaUYSLw bHsQ==
X-Gm-Message-State: AIkVDXKqWnfeK2H7G+Z48AbUzlZzY8sO5LiDZ/Gu73n99VbtbLtjFSXhO7U6HPQ1wd8zBA==
X-Received: by 10.99.127.28 with SMTP id a28mr16770974pgd.60.1486431108645; Mon, 06 Feb 2017 17:31:48 -0800 (PST)
Received: from ?IPv6:2406:e007:6fdd:1:28cc:dc4c:9703:6781? ([2406:e007:6fdd:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id f188sm5613042pfa.35.2017.02.06.17.31.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Feb 2017 17:31:48 -0800 (PST)
Subject: Re: New Version Notification for draft-leiba-rfc2119-update-01.txt
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148640984525.18879.14222110335591335067.idtracker@ietfa.amsl.com> <CALaySJJALzYE_dUyXX7fmhMHaGZpwY7my5Q-J8gNqNCk0yy=LQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <970cea35-d599-94ca-78be-e7769c4b9c59@gmail.com>
Date: Tue, 7 Feb 2017 14:31:46 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CALaySJJALzYE_dUyXX7fmhMHaGZpwY7my5Q-J8gNqNCk0yy=LQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7WmxAy9bqTE03au2LNVcjjpXA2c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 01:31:50 -0000

On 07/02/2017 08:59, Barry Leiba wrote:
> It's been a while since we had the discussion about the -00 version of
> this document.  I've updated it, and I think -01 reflects the result
> of that discussion.  I've asked Ben to last call it, but, of course,
> we don't have to wait for that if there's discussion on the -01
> version.
> 
> What I did here was (1) remove the deprecation of the synonyms,
> because we did not have consensus to do that, and (2) re-word the
> replacement text and most references to "capitalized" to clarify.
> 
> I do think this is ready and useful.  Y'all?

Yes.
     Brian


From nobody Mon Feb  6 18:53:01 2017
Return-Path: <neilj@fastmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD5911297E8; Mon,  6 Feb 2017 18:52:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.718
X-Spam-Level: 
X-Spam-Status: No, score=-2.718 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.com header.b=WzNOwq0e; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=TveEP980
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZLgku-b3pa3t; Mon,  6 Feb 2017 18:52:50 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00EF21297E7; Mon,  6 Feb 2017 18:52:49 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 69AA1206E0; Mon,  6 Feb 2017 21:52:49 -0500 (EST)
Received: from betaweb1 ([10.202.2.10]) by compute1.internal (MEProxy); Mon, 06 Feb 2017 21:52:49 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=QGiY8NT5nby9k92Yy7lCTrcLE+ I=; b=WzNOwq0ey2azEsXdeau6G7j+xhgG7o7KDpq5tSD/fTfBAcILt2NyI/NxV3 6KhRc+1ErLomBqjRON2nZvg+NZM793dL/gXCM2J+Ygv6+A9Y/Za31dInIsmx+equ WBMiFnNEx1m9l9UjioL6hXQcMqmLgKuEp5+4HAn9GqDTPdWhA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=QG iY8NT5nby9k92Yy7lCTrcLE+I=; b=TveEP980PkImJgW8Qa8qw+qoOuJw94Nowh B9bXQYUX5SEtddu2T2uCQKkNU4nrGkUY3jvAjA8ReenRfJ540wGJ9p4XXy9+RKRE F2nhqVY4zGgfvYlxl89y+vrWfLNgCTm39DhWJhmybcDQ7KthjcY37xZkQHSTLtjA nzWbaK1Tg=
X-ME-Sender: <xms:gTaZWCgpagNbqcI1fb_wrWHrL19UZXkUeYqcFewzkonM1amyoWypkQ>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id 28085E23C8; Mon,  6 Feb 2017 21:52:49 -0500 (EST)
Message-Id: <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com>
From: Neil Jenkins <neilj@fastmail.com>
To: dcrocker@bbiw.net, Alexey Melnikov <alexey.melnikov@isode.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_148643596923140630"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-fdb7c997
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
In-Reply-To: <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
Date: Tue, 07 Feb 2017 13:52:49 +1100
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jptLUpPizBx-7mTWG4d8Hq5zIkw>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 02:52:52 -0000

This is a multi-part message in MIME format.

--_----------=_148643596923140630
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Hi



I'll try to clarify a few of these points.



*Message representation*



JMAP defines a JSON structure that represents in a consistent and
structured way all the information that the vast majority of clients
need from an RFC5322 message. The server deals with the complexities of
MIME, encoding issues, parsing headers etc. The intention is that the
server will still operate with RFC5322 messages for storage and
certainly transmission; the JSON representation is not intended to
replace RFC5322, just relieve client authors from having to deal with
it. Clients can also just fetch the properties they need, reducing
bandwidth overhead.


Clients that want to or need to (for example those doing PGP in the
client) can still fetch the RFC5322 if needed.


*Industry need*



A number of proprietary protocols have been popping up as
alternatives to IMAP, which all also have their own JSON
representation of message objects. Here are a few examples, the
latter two being from whole companies that formed just to try to help
people not have to deal with IMAP:

 * Gmail[1]
 * Outlook[2]
 * Nylas[3]
 * Context.io[4]



In addition, we=E2=80=99re seeing most new mobile email clients proxy every=
thing
via their own server rather than talking directly to the user=E2=80=99s mail
store. Examples include Mailbox (now defunct), Alto, Outlook and Newton.
This is bad for security and privacy, and also bad for the client
authors as they have to run server infrastructure in addition to just
building their clients.


Despite not only being proprietary but patented (and expensive!),
ActiveSync has seen a big increase in adoption, and not just with
Microsoft servers, due to its better support for mobile environments and
ease of setup (one login for mail receive/send, contacts and calendars).


*Protocol vs representation*



JMAP is a protocol. It primarily defines a way of syncing data objects
in a network-efficient, developer friendly way. Objects are defined to
represent mailboxes, threads and messages in a consistent manner. These
are encoded as JSON for transmission over HTTPS.


*Message submission*



> There is no justification given for this approach.  For each

> activity, there needs to be a clear and solid need documented, based

> on actual industry activities or at least industry statements.

> Besides clarifying /what/ needs doing, it should serve to indicate

> likely industry uptake after the work is done.



This *is* based on industry statements. This is a very common support
problem we see here at FastMail, and from our conversations with other
mailbox vendors, we don't think this is just us.


*Flood control*



In IMAP, suppose you have a mailbox with 1,000,000 messages in it
selected, and another client expunges the lot. You get * 1 EXPUNGE
sent to you 1 million times (and you don't even know how many you are
going to receive); the only option is to drop the connection if it
gets too much. By flood control, we mean the client can ensure it does
not get flooded with data, especially important on low-bandwidth
connections like many mobile networks and in developing countries.
Reducing data usage is of course vital for saving battery, another key
concern for mobile.


Similarly, the server has well defined ways of rate limiting the
amount of work the client can ask it to do to ensure it too does
not get flooded and either accidentally or deliberately DOSed by
client requests.


*Why HTTP underneath*



The short answer is it=E2=80=99s good enough, widely understood and it=E2=
=80=99s by far
the easiest thing for developers to adopt. There=E2=80=99s support in basic=
ally
all OSes and programming languages. It=E2=80=99s easy to read and debug.


HTTP doesn=E2=80=99t tend to run into firewall issues, and is so commonly u=
sed
it has integrations which can help with optimisation (for example, iOS
has built-in support for optimising radio usage by batching HTTP calls
from different apps where possible, which their mail team have told us
they would like to be able to use). This isn=E2=80=99t an innate advantage =
of
HTTP, but rather an advantage of its ubiquity.


*Statelessness*



The protocol does not make use of any connection persistence to the
server. HTTPS may establish this underneath, but the protocol on top
is agnostic to it. Each request to the server contains an
authorisation token (in the Authorization header) to identify and
authenticate the request.


Neil.


Links:

  1. https://developers.google.com/gmail/api/v1/reference/
  2. https://msdn.microsoft.com/office/office365/APi/mail-rest-operations
  3. https://nylas.com/cloud/docs
  4. https://context.io/docs/lite

--_----------=_148643596923140630
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>Hi<br></div>
<div><br></div>
<div>I'll try to clarify a few of these points.<br></div>
<div><br></div>
<div><b>Message representation</b><br></div>
<div><br></div>
<div>JMAP defines a JSON structure that represents in a consistent and stru=
ctured way all the information that the vast majority of clients need from =
an RFC5322 message. The server deals with the complexities of MIME, encodin=
g issues, parsing headers etc. The intention is that the server will still =
operate with RFC5322 messages for storage and certainly transmission; the J=
SON representation is not intended to replace RFC5322, just relieve client =
authors from having to deal with it. Clients can also just fetch the proper=
ties they need, reducing bandwidth overhead.<br></div>
<div><br></div>
<div>Clients that want to or need to (for example those doing PGP in the cl=
ient) can still fetch the RFC5322 if needed.<br></div>
<div><br></div>
<div><b>Industry need</b><br></div>
<div><br></div>
<div>A number of proprietary protocols have been popping up as alternatives=
 to IMAP, which all also have their own JSON representation of message obje=
cts. Here are a few examples, the latter two being from whole companies tha=
t formed just to try to help people not have to deal with IMAP:<br></div>
<div><br></div>
<ul><li><a href=3D"https://developers.google.com/gmail/api/v1/reference/">G=
mail</a><br></li><li><a href=3D"https://msdn.microsoft.com/office/office365=
/APi/mail-rest-operations">Outlook</a><br></li><li><a href=3D"https://nylas=
.com/cloud/docs">Nylas</a><br></li><li><a href=3D"https://context.io/docs/l=
ite">Context.io</a><br></li></ul><div><br></div>
<div>In addition, we=E2=80=99re seeing most new mobile email clients proxy =
everything via their own server rather than talking directly to the user=E2=
=80=99s mail store. Examples include Mailbox (now defunct), Alto, Outlook a=
nd Newton. This is bad for security and privacy, and also bad for the clien=
t authors as they have to run server infrastructure in addition to just bui=
lding their clients.<br></div>
<div><br></div>
<div>Despite not only being proprietary but patented (and expensive!), Acti=
veSync has seen a big increase in adoption, and not just with Microsoft ser=
vers, due to its better support for mobile environments and ease of setup (=
one login for mail receive/send, contacts and calendars).<br></div>
<div><br></div>
<div><b>Protocol vs representation</b><br></div>
<div><br></div>
<div>JMAP is a protocol. It primarily defines a way of syncing data objects=
 in a network-efficient, developer friendly way. Objects are defined to rep=
resent mailboxes, threads and messages in a consistent manner. These are en=
coded as JSON for transmission over HTTPS.<br></div>
<div><br></div>
<div><b>Message submission</b><br></div>
<div><br></div>
<blockquote type=3D"cite"><div>There is no justification given for this app=
roach.&nbsp; For each<br></div>
<div>activity, there needs to be a clear and solid need documented, based<b=
r></div>
<div>on actual industry activities or at least industry statements.<br></di=
v>
<div>Besides clarifying /what/ needs doing, it should serve to indicate<br>=
</div>
<div>likely industry uptake after the work is done.<br></div>
</blockquote><div><br></div>
<div>This <i>is</i> based on industry statements. This is a very common sup=
port problem we see here at FastMail, and from our conversations with other=
 mailbox vendors, we don't think this is just us.<br></div>
<div><br></div>
<div><b>Flood control</b><br></div>
<div><br></div>
<div>In IMAP, suppose you have a mailbox with 1,000,000 messages in it sele=
cted, and another client expunges the lot. You get * 1 EXPUNGE sent to you =
1 million times (and you don't even know how many you are going to receive)=
; the only option is to drop the connection if it gets too much. By flood c=
ontrol, we mean the client can ensure it does not get flooded with data, es=
pecially important on low-bandwidth connections like many mobile networks a=
nd in developing countries. Reducing data usage is of course vital for savi=
ng battery, another key concern for mobile.<br></div>
<div><br></div>
<div>Similarly, the server has well defined ways of rate limiting the amoun=
t of work the client can ask it to do to ensure it too does not get flooded=
 and either accidentally or deliberately DOSed by client requests.<br></div>
<div><br></div>
<div><b>Why HTTP underneath</b></div>
<div><br></div>
<div>The short answer is it=E2=80=99s good enough, widely understood and it=
=E2=80=99s by far the easiest thing for developers to adopt. There=E2=80=99=
s support in basically all OSes and programming languages. It=E2=80=99s eas=
y to read and debug.<br></div>
<div><br></div>
<div>HTTP doesn=E2=80=99t tend to run into firewall issues, and is so commo=
nly used it has integrations which can help with optimisation (for example,=
 iOS has built-in support for optimising radio usage by batching HTTP calls=
 from different apps where possible, which their mail team have told us the=
y would like to be able to use). This isn=E2=80=99t an innate advantage of =
HTTP, but rather an advantage of its ubiquity.<br></div>
<div><br></div>
<div><b>Statelessness</b><br></div>
<div><br></div>
<div>The protocol does not make use of any connection persistence to the se=
rver. HTTPS may establish this underneath, but the protocol on top is agnos=
tic to it. Each request to the server contains an authorisation token (in t=
he Authorization header) to identify and authenticate the request.<br></div>
<div><br></div>
<div>Neil.</div>
</body>
</html>

--_----------=_148643596923140630--


From nobody Tue Feb  7 01:37:06 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76B501295EA; Tue,  7 Feb 2017 01:37:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6AdllDks58B; Tue,  7 Feb 2017 01:36:58 -0800 (PST)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 3554C127058; Tue,  7 Feb 2017 01:36:57 -0800 (PST)
X-AuditID: c1b4fb25-4bbfb70000006c88-d7-589995350d22
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id 6B.D4.27784.53599985; Tue,  7 Feb 2017 10:36:55 +0100 (CET)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.27) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 7 Feb 2017 10:36:53 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=kZaYWAl40rP3n3/bUUfi0wLpE1XqIQDW8UlOj3+SVyU=; b=TinfBy0/czOCPRM0tPaClf0Lv1iO6P8i0+MhbF85PxU9n2Wcs7S0iaWW+Y2QtuUK6mw61x6uCJI/LwWUU2Ze/vrGxTmx95Gr2bmvhvFzpnqmmKMb+GMR43zxHcJrv43ZnyM+ATPrDUIa+iHbt7uwLM3psIhiDwO1dLvLyASI5jE=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0993.eurprd07.prod.outlook.com (10.162.37.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Tue, 7 Feb 2017 09:36:51 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Tue, 7 Feb 2017 09:36:51 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2A
Date: Tue, 7 Feb 2017 09:36:51 +0000
Message-ID: <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
In-Reply-To: <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 89430744-6d54-4be3-76e9-08d44f3cd89c
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0993;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0993; 7:0TVbv4OBIJIOxY/wkMj88yoBi/co9Sv26VhsCevf+F0KHR7IYR/nZiqxabH4VwCYCoy25fM0fqcWxwN2QVh7fWGKSFtx4mBQdNxg7wNqKYT2VlSfjFMj4bNzguB7LAjoo6F3kxbNTwJe7GiWOgr+kT/mbXTzB2jJpHDCNkrDty4Jn5EhumLvBQY1FdwcU7P4b1wcwuzDlZsV5Nv05/8MPwcb+ny340cffoR0bPrrit8wyOGAA01rQVl1SkLlb6XioCiCqk/5xztibE9l9qd+HtG7Q0BpRC8LrVOzmzJphKoLEzIcjR41kPN+xcw09tj/vIP/jbI3qSf7wxsgcZvkgRCOC0ZpMK+tWHXSOgOfz8DIYhQBLtZIw1DT+WMXZFOTXjqDWmf8r9T5J+fobQZcH82tzlafm4mbiYxbQld5gk5vKt4p/svQlFDYQdzEUvl7eBWrhhFJnzNye8Gg3tthE0bdc/c8HI8l4j8Iv/6naS+QsC50aMd4OjN0V4O5eQ9lhHYXYPFtLXU22tG7LO4pXA==
x-microsoft-antispam-prvs: <AM2PR07MB099336B339C9009A6FD040C8F0430@AM2PR07MB0993.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(2017020603029)(20170203043)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123564025)(20161123555025)(20161123560025)(20161123558025)(20161123562025)(6072148); SRVR:AM2PR07MB0993; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0993; 
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(24454002)(199003)(189002)(13464003)(51914003)(51444003)(93886004)(2950100002)(230783001)(122556002)(6916009)(6246003)(2900100001)(229853002)(66066001)(3660700001)(53546003)(54906002)(92566002)(74316002)(68736007)(110136004)(38730400002)(6306002)(53936002)(54896002)(9686003)(5660300001)(86362001)(8676002)(8936002)(77096006)(4326007)(3280700002)(105586002)(76176999)(25786008)(106116001)(54356999)(7696004)(6506006)(236005)(790700001)(102836003)(2906002)(7906003)(3846002)(7736002)(55016002)(6116002)(189998001)(33656002)(966004)(106356001)(606005)(81166006)(101416001)(81156014)(97736004)(6436002)(99286003)(50986999); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0993; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Feb 2017 09:36:51.5597 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0993
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02SfUhTURjGOffe3V2l0WlqvmlBrsI0tQ9LZ5oUSEga6F+uMG3mTefXZJuV UbIwy2bWiC2dmZoZptX8oI9lFjYsKSyzNGwoFq5AMTCdyPIr513gf7/3fR6e85zDYUhhJ8+L keWoWEWONEtEu1IGyTPvwFC9QbLD1LBObK0coMRVc0ZC3D82RYl/tVRT4vJX92lxX/9Fcj8d XVdnJ6Kf1JXR0bX6XyiOPOoakcpmyU6xiu2Rx13T1U2v6NyHZnTm49QDWo3KXyINcmEA74aa FgOpQa6MEBsRzHaN8LihC8G3XhtyDBQuJeFtY7VT0RFQardR3PAGge1aJa1BDEPjvWA1xzpy 3XEA6G4/X84lcREBVl0V5RDccAx0fG3lc6ZYsD/vITk+CPrC7uVSFN4M7QudhCNTgBPhsiae O+sqAXN/KnkOjwuOgr8N88t+hNfCzPuHhINJ7AkWazXBXQ5DXTuXD9gDRkcWeJw/BZqKTE6P D3xqrHDyYdB3VKH//Nt0k89xNwXFdsxxJgxbSiiOD8Gtge+EoxzgpwQM6PudQeuhvrnMKbyg YfRF83KSELNQ/6gIcS/hBUN9V5AW+VWsKM6xHIxDdykHC/AaeGewLjGztPeDprbtnMUHdCU/ +BxvhaLK2/yV+xrEb0QeSlaZkp22KziIVchOKJXynKAcVtWKlv7W68ezW0zoy/gBM8IMEq0S 5F4vlwh50lPK/GwzAoYUuQvOaw0SoSBVmn+WVciTFXlZrNKMvBlK5CkIaRhOEOI0qYrNZNlc VvFfJRgXLzWit2WGBoR8jpv2HZEXHpOoLQUxSRlVdy603ZBDseXDhsmw1aO9s/4TzzZZ8hYn Ijsyrs4sxl8KmJ8zT5/eGBlh8tXrA8fcf6q1lgfDPQlwLlU2aasJLn2f2J4ctsXl3p6TSfvc tM22imxJQUP9eMxgljz8+uCRcE2UUTVU6yOeEVHKdOlOf1KhlP4DFhUDpVcDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DExKVCT9oUgx0kgk1_XteGHNnDE>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 09:37:00 -0000

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGV0ZSwNCg0KV2XigJlyZSBnZXR0aW5nIHRoZXJlLg0KUGxlYXNlIHNlZSBpbiBsaW5lIGZv
ciBmdXJ0aGVyIGV4cGxhbmF0aW9uLg0KDQpUaGFua3MgYSBsb3QNCkRhbmllbGUNCg0KRnJvbTog
UGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbV0NClNlbnQ6IGx1
bmVkw6wgNiBmZWJicmFpbyAyMDE3IDE4OjM4DQpUbzogRGFuaWVsZSBDZWNjYXJlbGxpIDxkYW5p
ZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24uY29tPg0KQ2M6IEphcmkgQXJra28gPGphcmkuYXJra29A
cGl1aGEubmV0PjsgZ2VuLWFydEBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1n
cmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzsgY2NhbXBAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcN
ClN1YmplY3Q6IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtZmxleGli
bGUtZ3JpZC1vc3BmLWV4dC0wNw0KDQoNCk9uIDYgRmViIDIwMTcsIGF0IDc6MzYsIERhbmllbGUg
Q2VjY2FyZWxsaSB3cm90ZToNCg0KSGkgSmFyaSwgUGV0ZSwNCg0KRmlyc3Qgb2YgYWxsIHRoYW5r
cyBmb3IgdGhlIGFjY3VyYXRlIHJldmlldy4NCg0KQWxsIHRoZSBuaXRzL2VkaXRvcmlhbCBjb21t
ZW50cyBhcmUgY29ycmVjdCBhbmQgd2lsbCBiZSBmaXhlZC4NCg0KUmVnYXJkaW5nIHRoZSBtaW5v
ciBpc3N1ZToNCg0KNC4xLjE6DQoNClRoZSBmaWd1cmUgaXMgYSBiaXQgY29uZnVzaW5nOiBUaGVy
ZSBtaWdodCBub3QgZXhpc3QgYSAiTWF4IFNsb3QgV2lkdGggYXQgUHJpb3JpdHkNCjciIGlmIGJp
dCA3IGlzIGNsZWFyIGluIHRoZSBQcmlvcml0eSBmaWVsZCwgY29ycmVjdD8NClBlcmhhcHMgaXQg
d291bGQgYmUgYmV0dGVyIHRvIGp1c3Qgc2hvdyB0aGF0IGFzICIuLi4iIG9yICJNYXggU2xvdCBX
aWR0aCBhdA0KUHJpb3JpdHkgbiIuIFRoZSB0aGluZyBpcywgaXQgbWlnaHQgb25seSBiZSBhIHNp
bmdsZSB2YWx1ZSwgZm9sbG93ZWQgYnkgdGhlDQpwYWRkaW5nLCBzbyBoYXZpbmcgdGhlIHNlY29u
ZCB2YWx1ZSBpbiB0aGVyZSBtaWdodCBiZSBtaXNsZWFkaW5nLiAoUGVyaGFwcw0Kc2ltaWxhciBj
b25zdHJ1Y3RzIGFyZSB1c2VkIGluIG90aGVyIE1QTFMgZG9jcyBhbmQgcGVvcGxlIHdpbGwgdW5k
ZXJzdGFuZC4gQnV0DQppdCB0b29rIG1lIGEgd2hpbGUgdG8gZmlndXJlIGl0IG91dC4pDQoNCml0
IHdhcyBkaWZmaWN1bHQgdG8gZXhwcmVzcyBpbiB0aGUgZmlndXJlIHRoZSBmYWN0IHRoYXQgb25s
eSBzb21lIG9mIHRoZSBwcmlvcml0aWVzIGFyZSBhZHZlcnRpc2VkLiBBcyB5b3Ugc2FpZCBpdCBj
b3VsZCBiZSBvbmUsIHR3byBvciBhbnkgbnVtYmVyIHVwIHRvIDguDQpXaGF0IGFib3V0IGEgc2lu
Z2xlIGZpZWxkICh3aXRoIH4gb24gdGhlIGJvcmRlcnMgdG8gaW5kaWNhdGUgdGhhdCBpdCBjYW4g
aGF2ZSB2YXJpYWJsZSBsZW5ndGgpIHNheWluZyAiTWF4IFNsb3QgV2lkdGggYXQgUHJpbyBuIiBh
bmQgdGhlbiBzYXkgdGhhdCAxNiBiaXRzIGFyZSB1c2VkIGZvciBlYWNoIHByaW8gYW5kIHdoZW4g
YW4gb2RkIG51bWJlciBvZiBwcmlvcml0aWVzIGlzIHVzZWQgdGhlIGZpZWxkIGlzIHBhZGRlZCB0
byBsaW5lIHVwIHdpdGggbXVsdGlwbGVzIG9mIDMyIGJpdHM/DQoNClllcywgSSB0aGluayB0aGF0
IHdvdWxkIG1ha2UgbW9yZSBzZW5zZSB0byBtZS4NCg0KW0RDXSBPSw0KDQpUaGUgZGlzY3Vzc2lv
biBvZiBQcmlvcml0eSB3YXMgdmVyeSBjb25mdXNpbmcgZm9yIG1lLiBJbiB0aGUgdGhpcmQgc2Vu
dGVuY2UsIGRvDQp5b3UgbWVhbiwgIkEgYml0IGlzIHNldCAoMSkgY29ycmVzcG9uZGluZyB0byBl
YWNoIHByaW9yaXR5IHJlcHJlc2VudGVkIGluIHRoZQ0Kc3ViLVRMViwgYW5kIGNsZWFyICgwKSBm
b3IgZWFjaCBwcmlvcml0eSBub3QgcmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYiPyBJIGRvbid0
DQp1bmRlcnN0YW5kIHRoZSBNVVNUL01VU1QgTk9UIGFzIHlvdSBoYWQgaXQuIEFuZCBJIGRvbid0
IHVuZGVyc3RhbmQgdGhlDQpsYXN0IHNlbnRlbmNlIGF0IGFsbC4gQXJlIHlvdSB0cnlpbmcgdG8g
c2F5LCAiVGhlIGxlZnRtb3N0IGJpdCAocHJpb3JpdHkgbGV2ZWwgMCkNCk1VU1QgYmUgc2V0LCBh
bmQgcHJpb3JpdHkgbGV2ZWwgMCBNVVNUIGJlIGFkdmVydGlzZWQgaW4gdGhlIHN1Yi1UTFYuIj8N
Ck90aGVyd2lzZSwgSSBkb24ndCBnZXQgaXQuDQoNCkl0IG1lYW5zIHRoYXQgaWYgdGhlIHByaW9y
aXR5IGZpZWxkIGlzIHNldCB0byBlLmcuIDEwMDEwMDEwIGluIHRoZSBmb2xsb3dpbmcgeW91IHdv
dWxkIGZpbmQgNCBmaWVsZHMgaW5kaWNhdGluZyByZXNwZWN0aXZlbHk6IE1heCBTbG90IFdpZHRo
IGF0IFByaW9yaXR5IDAsIE1heCBTbG90IFdpZHRoIGF0IFByaW9yaXR5IDMsIE1heCBTbG90IFdp
ZHRoIGF0IFByaW9yaXR5IDYgYW5kIHNpbmNlIHRoZXkgYXJlIDMgYSAxNiBiaXRzIHBhZGRpbmcg
dG8gMzIgYml0cy4NCg0KT0ssIHRoZW4gSSB0aGluayBteSBzZW50ZW5jZSBpcyBjbGVhcmVyIGZv
ciB0aGF0OiAiQSBiaXQgaXMgc2V0ICgxKSBjb3JyZXNwb25kaW5nIHRvIGVhY2ggcHJpb3JpdHkg
cmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYsIGFuZCBjbGVhciAoMCkgZm9yIGVhY2ggcHJpb3Jp
dHkgbm90IHJlcHJlc2VudGVkIGluIHRoZSBzdWItVExWLiINCg0KW0RDXSBBZ3JlZS4gV2XigJls
bCB1c2UgeW91ciB0ZXh0Lg0KDQpJdCBhbHNvIG1lYW5zIHRoYXQgYXQgbGVhc3Qgb25lIHByaW9y
aXR5IG11c3QgYmUgYWR2ZXJ0aXNlZCAoaS5lLiBwcmlvcml0eSAwMDAwMDAwMCBpcyBub3QgYWxs
b3dlZCkuDQoNCkkgZ2V0IHRoYXQgcGFydCAoIkF0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBN
VVNUIGJlIGFkdmVydGlzZWQiKS4gSXQncyB0aGUgZW5kIEkgZG9uJ3QgdW5kZXJzdGFuZDogInRo
YXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwgU0hBTEwgYmUgYXQgcHJpb3Jp
dHkgbGV2ZWwgMC4iIFdoYXQgZG9lcyB0aGF0IG1lYW4/DQoNCltEQ10gSXQgbWVhbnMgdGhhdCBp
ZiBvbmx5IG9uZSBwcmlvcml0eSBpcyBzdXBwb3J0ZWQgaXQgaGFzIHRvIGJlIHByaW9yaXR5IDAu
IEZvciBhbnkgcGFydGljdWxhciBhZG1pbmlzdHJhdGl2ZSBwdXJwb3NlIGl0IGNvdWxkIGJlIHBv
c3NpYmxlIHRvIHNldCBpdCB0byBhIGRpZmZlcmVudCB2YWx1ZSwgYnV0IHRoYXQgc2hvdWxkbuKA
mXQgYmUgZG9uZS4NCg0KSSBkb24ndCB1bmRlcnN0YW5kIHRoZSBNQVkgaW4gdGhlIGxhc3Qgc2Vu
dGVuY2UuIERvZXMgdGhhdCBtZWFuIHRoYXQgSSBNQVkNCmFsc28gc2V0IGl0IHRvIHRoZSBoaWdo
ZXN0IHBvc3NpYmxlIG5vbWluYWwgY2VudHJhbCBmcmVxdWVuY3kgc3VwcG9ydGVkIGJ5IHRoZQ0K
bGluaz8gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgdGhhdCBzZW50ZW5jZSBpcyB0cnlpbmcgdG8g
dGVsbCBtZS4NCg0KQW4gZXhhbXBsZSBpcyBwcm92aWRlZCBpbiBzZWN0aW9uIDQuMS4yLCB3aGVy
ZSB0aGUgYXZhaWxhYmxlIHJhbmdlIGdvZXMgZnJvbSAtMiB0byArOCBidXQgdGhlIHJhbmdlIHN1
cHBvcnRlZCBieSB0aGUgbGluayBnb2VzIGZyb20gLTkgdG8gKzExLiBUaGUgc2VudGVuY2UgbWVh
bnMgdGhhdCBldmVuIGlmIG5vdCBhdmFpbGFibGUgaXQgY291bGQgYmUgcG9zc2libGUgdG8gaW5k
aWNhdGUgYWxzbyBuPS05IHRvIGluZGljYXRlIHRoZSBzdGFydGluZyBwb2ludCBvZiB0aGUgcmFu
Z2Ugc3VwcG9ydGVkIGJ5IHRoZSBsaW5rLg0KDQoiIEluIHRoaXMgZXhhbXBsZSwgaXQgaXMgYXNz
dW1lZCB0aGF0IHRoZSBsb3dlc3Qgbm9taW5hbCBjZW50cmFsDQpmcmVxdWVuY3kgc3VwcG9ydGVk
IGlzIG49IC05IGFuZCB0aGUgaGlnaGVzdCBpcyBuPTExLiBOb3RlIHRoZXkNCmNhbm5vdCBiZSB1
c2VkIGFzIGEgbm9taW5hbCBjZW50cmFsIGZyZXF1ZW5jeSBmb3Igc2V0dGluZyB1cCBhIExTUCwN
CmJ1dCBtZXJlbHkgYXMgdGhlIHdheSB0byBleHByZXNzIHRoZSBzdXBwb3J0ZWQgZnJlcXVlbmN5
IHJhbmdlLiINCg0KSSdtIG9rIHdpdGggZHJvcHBpbmcgdGhlIHNlbnRlbmNlLg0KDQpJIHRoaW5r
IGRyb3BwaW5nIHRoZSBzZW50ZW5jZSB3b3VsZCBtYWtlIHRoZSBtb3N0IHNlbnNlLg0KDQpbRENd
IE9rIGZvciBtZQ0KDQpUaGFuayB5b3UNCkRhbmllbGUNCg0KVGhhbmtzIGZvciBjb25zaWRlcmlu
ZyBteSBzdWdnZXN0ZWQgY2hhbmdlcy4NCg0KcHINCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEphcmkgQXJra28gW21haWx0bzpqYXJpLmFya2tvQHBpdWhhLm5ldF0NClNlbnQ6
IGx1bmVkw6wgNiBmZWJicmFpbyAyMDE3IDEyOjMyDQpUbzogUGV0ZSBSZXNuaWNrIDxwcmVzbmlj
a0BxdGkucXVhbGNvbW0uY29tPG1haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPj4NCkNj
OiBnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0QGlldGYub3JnPjsgZHJhZnQtaWV0Zi1j
Y2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJhZnQtaWV0
Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZz47DQpjY2FtcEBpZXRm
Lm9yZzxtYWlsdG86Y2NhbXBAaWV0Zi5vcmc+OyBpZXRmQGlldGYub3JnPG1haWx0bzppZXRmQGll
dGYub3JnPg0KU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft
cC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA3DQoNClRoYW5rcyBmb3IgeW91ciByZXZpZXcsIFBl
dGUuIEF1dGhvcnMsIGFueSBjb21tZW50cz8NCg0KSmFyaQ0KDQotLQ0KUGV0ZSBSZXNuaWNrIGh0
dHA6Ly93d3cucXVhbGNvbW0uY29tL35wcmVzbmljay88aHR0cDovL3d3dy5xdWFsY29tbS5jb20v
JTdFcHJlc25pY2svPg0KUXVhbGNvbW0gVGVjaG5vbG9naWVzLCBJbmMuIC0gKzEgKDg1OCk2NTEt
NDQ3OA0K

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IklUIiBsaW5rPSJibHVl
IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSBQZXRlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
Pldl4oCZcmUgZ2V0dGluZyB0aGVyZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5QbGVhc2Ugc2VlIGluIGxpbmUgZm9yIGZ1cnRoZXIgZXhwbGFuYXRpb24uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+VGhhbmtzIGEgbG90PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+RGFuaWVsZSZuYnNwOyAmbmJzcDs8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMu
MHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNl
cmlmIj4gUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbV0NCjxi
cj4NCjxiPlNlbnQ6PC9iPiBsdW5lZMOsIDYgZmViYnJhaW8gMjAxNyAxODozODxicj4NCjxiPlRv
OjwvYj4gRGFuaWVsZSBDZWNjYXJlbGxpICZsdDtkYW5pZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24u
Y29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7amFyaS5hcmtrb0BwaXVoYS5u
ZXQmZ3Q7OyBnZW4tYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRmLWNjYW1w
LWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj5PbiA2IEZlYiAyMDE3LCBhdCA3OjM2LCBEYW5pZWxlIENlY2NhcmVsbGkgd3Jv
dGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzow
Y20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4t
Ym90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5IaSBKYXJpLCBQZXRlLDxicj4NCjxicj4N
CkZpcnN0IG9mIGFsbCB0aGFua3MgZm9yIHRoZSBhY2N1cmF0ZSByZXZpZXcuPGJyPg0KPGJyPg0K
QWxsIHRoZSBuaXRzL2VkaXRvcmlhbCBjb21tZW50cyBhcmUgY29ycmVjdCBhbmQgd2lsbCBiZSBm
aXhlZC48YnI+DQo8YnI+DQpSZWdhcmRpbmcgdGhlIG1pbm9yIGlzc3VlOjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCAjOTk5OTk5IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNt
O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izk5OTk5OSI+
NC4xLjE6PGJyPg0KPGJyPg0KVGhlIGZpZ3VyZSBpcyBhIGJpdCBjb25mdXNpbmc6IFRoZXJlIG1p
Z2h0IG5vdCBleGlzdCBhICZxdW90O01heCBTbG90IFdpZHRoIGF0IFByaW9yaXR5PGJyPg0KNyZx
dW90OyBpZiBiaXQgNyBpcyBjbGVhciBpbiB0aGUgUHJpb3JpdHkgZmllbGQsIGNvcnJlY3Q/PGJy
Pg0KUGVyaGFwcyBpdCB3b3VsZCBiZSBiZXR0ZXIgdG8ganVzdCBzaG93IHRoYXQgYXMgJnF1b3Q7
Li4uJnF1b3Q7IG9yICZxdW90O01heCBTbG90IFdpZHRoIGF0PGJyPg0KUHJpb3JpdHkgbiZxdW90
Oy4gVGhlIHRoaW5nIGlzLCBpdCBtaWdodCBvbmx5IGJlIGEgc2luZ2xlIHZhbHVlLCBmb2xsb3dl
ZCBieSB0aGU8YnI+DQpwYWRkaW5nLCBzbyBoYXZpbmcgdGhlIHNlY29uZCB2YWx1ZSBpbiB0aGVy
ZSBtaWdodCBiZSBtaXNsZWFkaW5nLiAoUGVyaGFwczxicj4NCnNpbWlsYXIgY29uc3RydWN0cyBh
cmUgdXNlZCBpbiBvdGhlciBNUExTIGRvY3MgYW5kIHBlb3BsZSB3aWxsIHVuZGVyc3RhbmQuIEJ1
dDxicj4NCml0IHRvb2sgbWUgYSB3aGlsZSB0byBmaWd1cmUgaXQgb3V0Lik8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5pdCB3YXMgZGlmZmljdWx0
IHRvIGV4cHJlc3MgaW4gdGhlIGZpZ3VyZSB0aGUgZmFjdCB0aGF0IG9ubHkgc29tZSBvZiB0aGUg
cHJpb3JpdGllcyBhcmUgYWR2ZXJ0aXNlZC4gQXMgeW91IHNhaWQgaXQgY291bGQgYmUgb25lLCB0
d28gb3IgYW55IG51bWJlciB1cCB0byA4Ljxicj4NCldoYXQgYWJvdXQgYSBzaW5nbGUgZmllbGQg
KHdpdGggfiBvbiB0aGUgYm9yZGVycyB0byBpbmRpY2F0ZSB0aGF0IGl0IGNhbiBoYXZlIHZhcmlh
YmxlIGxlbmd0aCkgc2F5aW5nICZxdW90O01heCBTbG90IFdpZHRoIGF0IFByaW8gbiZxdW90OyBh
bmQgdGhlbiBzYXkgdGhhdCAxNiBiaXRzIGFyZSB1c2VkIGZvciBlYWNoIHByaW8gYW5kIHdoZW4g
YW4gb2RkIG51bWJlciBvZiBwcmlvcml0aWVzIGlzIHVzZWQgdGhlIGZpZWxkIGlzIHBhZGRlZCB0
byBsaW5lIHVwIHdpdGgNCiBtdWx0aXBsZXMgb2YgMzIgYml0cz88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+WWVzLCBJIHRoaW5rIHRoYXQgd291
bGQgbWFrZSBtb3JlIHNlbnNlIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+W0RDXSBPSzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1y
aWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41cHQ7cGFkZGluZzowY20gMGNtIDBj
bSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMu
NzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojOTk5OTk5Ij5UaGUgZGlzY3Vzc2lvbiBvZiBQcmlvcml0eSB3YXMgdmVy
eSBjb25mdXNpbmcgZm9yIG1lLiBJbiB0aGUgdGhpcmQgc2VudGVuY2UsIGRvPGJyPg0KeW91IG1l
YW4sICZxdW90O0EgYml0IGlzIHNldCAoMSkgY29ycmVzcG9uZGluZyB0byBlYWNoIHByaW9yaXR5
IHJlcHJlc2VudGVkIGluIHRoZTxicj4NCnN1Yi1UTFYsIGFuZCBjbGVhciAoMCkgZm9yIGVhY2gg
cHJpb3JpdHkgbm90IHJlcHJlc2VudGVkIGluIHRoZSBzdWItVExWJnF1b3Q7PyBJIGRvbid0PGJy
Pg0KdW5kZXJzdGFuZCB0aGUgTVVTVC9NVVNUIE5PVCBhcyB5b3UgaGFkIGl0LiBBbmQgSSBkb24n
dCB1bmRlcnN0YW5kIHRoZTxicj4NCmxhc3Qgc2VudGVuY2UgYXQgYWxsLiBBcmUgeW91IHRyeWlu
ZyB0byBzYXksICZxdW90O1RoZSBsZWZ0bW9zdCBiaXQgKHByaW9yaXR5IGxldmVsIDApPGJyPg0K
TVVTVCBiZSBzZXQsIGFuZCBwcmlvcml0eSBsZXZlbCAwIE1VU1QgYmUgYWR2ZXJ0aXNlZCBpbiB0
aGUgc3ViLVRMVi4mcXVvdDs/PGJyPg0KT3RoZXJ3aXNlLCBJIGRvbid0IGdldCBpdC48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5JdCBtZWFucyB0
aGF0IGlmIHRoZSBwcmlvcml0eSBmaWVsZCBpcyBzZXQgdG8gZS5nLiAxMDAxMDAxMCBpbiB0aGUg
Zm9sbG93aW5nIHlvdSB3b3VsZCBmaW5kIDQgZmllbGRzIGluZGljYXRpbmcgcmVzcGVjdGl2ZWx5
OiBNYXggU2xvdCBXaWR0aCBhdCBQcmlvcml0eSAwLCBNYXggU2xvdCBXaWR0aCBhdCBQcmlvcml0
eSAzLCBNYXggU2xvdA0KIFdpZHRoIGF0IFByaW9yaXR5IDYgYW5kIHNpbmNlIHRoZXkgYXJlIDMg
YSAxNiBiaXRzIHBhZGRpbmcgdG8gMzIgYml0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Js
b2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+T0ssIHRoZW4gSSB0aGluayBteSBzZW50ZW5jZSBp
cyBjbGVhcmVyIGZvciB0aGF0OiAmcXVvdDtBIGJpdCBpcyBzZXQgKDEpIGNvcnJlc3BvbmRpbmcg
dG8gZWFjaCBwcmlvcml0eSByZXByZXNlbnRlZCBpbiB0aGUgc3ViLVRMViwgYW5kIGNsZWFyICgw
KSBmb3IgZWFjaCBwcmlvcml0eSBub3QgcmVwcmVzZW50ZWQgaW4gdGhlIHN1Yi1UTFYuJnF1b3Q7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+
W0RDXSBBZ3JlZS4gV2XigJlsbCB1c2UgeW91ciB0ZXh0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxl
ZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+SXQgYWxzbyBtZWFucyB0aGF0IGF0IGxlYXN0IG9uZSBwcmlvcml0eSBtdXN0IGJlIGFk
dmVydGlzZWQgKGkuZS4gcHJpb3JpdHkgMDAwMDAwMDAgaXMgbm90IGFsbG93ZWQpLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5JIGdldCB0aGF0
IHBhcnQgKCZxdW90O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBNVVNUIGJlIGFkdmVydGlz
ZWQmcXVvdDspLiBJdCdzIHRoZSBlbmQgSSBkb24ndCB1bmRlcnN0YW5kOiAmcXVvdDt0aGF0LCB1
bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNIQUxMIGJlIGF0IHByaW9yaXR5IGxl
dmVsIDAuJnF1b3Q7IFdoYXQgZG9lcyB0aGF0IG1lYW4/PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+W0RDXSBJdCBtZWFucyB0aGF0IGlmIG9u
bHkgb25lIHByaW9yaXR5IGlzIHN1cHBvcnRlZCBpdCBoYXMgdG8gYmUgcHJpb3JpdHkgMC4gRm9y
IGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZlIHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2li
bGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZhbHVlLCBidXQNCiB0aGF0IHNob3VsZG7igJl0
IGJlIGRvbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTtt
YXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgIzk5OTk5OSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O21h
cmdpbi1sZWZ0OjBjbTttYXJnaW4tcmlnaHQ6MGNtO21hcmdpbi1ib3R0b206My43NXB0Ij4NCjxw
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2Nv
bG9yOiM5OTk5OTkiPkkgZG9uJ3QgdW5kZXJzdGFuZCB0aGUgTUFZIGluIHRoZSBsYXN0IHNlbnRl
bmNlLiBEb2VzIHRoYXQgbWVhbiB0aGF0IEkgTUFZPGJyPg0KYWxzbyBzZXQgaXQgdG8gdGhlIGhp
Z2hlc3QgcG9zc2libGUgbm9taW5hbCBjZW50cmFsIGZyZXF1ZW5jeSBzdXBwb3J0ZWQgYnkgdGhl
PGJyPg0KbGluaz8gSSBkb24ndCB1bmRlcnN0YW5kIHdoYXQgdGhhdCBzZW50ZW5jZSBpcyB0cnlp
bmcgdG8gdGVsbCBtZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojNzc3Nzc3Ij5BbiBleGFtcGxlIGlzIHByb3ZpZGVkIGluIHNlY3Rpb24gNC4xLjIsIHdoZXJl
IHRoZSBhdmFpbGFibGUgcmFuZ2UgZ29lcyBmcm9tIC0yIHRvICYjNDM7OCBidXQgdGhlIHJhbmdl
IHN1cHBvcnRlZCBieSB0aGUgbGluayBnb2VzIGZyb20gLTkgdG8gJiM0MzsxMS4gVGhlIHNlbnRl
bmNlIG1lYW5zIHRoYXQgZXZlbiBpZiBub3QgYXZhaWxhYmxlIGl0IGNvdWxkDQogYmUgcG9zc2li
bGUgdG8gaW5kaWNhdGUgYWxzbyBuPS05IHRvIGluZGljYXRlIHRoZSBzdGFydGluZyBwb2ludCBv
ZiB0aGUgcmFuZ2Ugc3VwcG9ydGVkIGJ5IHRoZSBsaW5rLjxicj4NCjxicj4NCiZxdW90OyBJbiB0
aGlzIGV4YW1wbGUsIGl0IGlzIGFzc3VtZWQgdGhhdCB0aGUgbG93ZXN0IG5vbWluYWwgY2VudHJh
bDxicj4NCmZyZXF1ZW5jeSBzdXBwb3J0ZWQgaXMgbj0gLTkgYW5kIHRoZSBoaWdoZXN0IGlzIG49
MTEuIE5vdGUgdGhleTxicj4NCmNhbm5vdCBiZSB1c2VkIGFzIGEgbm9taW5hbCBjZW50cmFsIGZy
ZXF1ZW5jeSBmb3Igc2V0dGluZyB1cCBhIExTUCw8YnI+DQpidXQgbWVyZWx5IGFzIHRoZSB3YXkg
dG8gZXhwcmVzcyB0aGUgc3VwcG9ydGVkIGZyZXF1ZW5jeSByYW5nZS4mcXVvdDs8YnI+DQo8YnI+
DQpJJ20gb2sgd2l0aCBkcm9wcGluZyB0aGUgc2VudGVuY2UuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPkkgdGhpbmsgZHJvcHBpbmcgdGhlIHNl
bnRlbmNlIHdvdWxkIG1ha2UgdGhlIG1vc3Qgc2Vuc2UuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj5bRENdIE9rIGZvciBtZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxl
ZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4g
c3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+VGhhbmsgeW91PGJyPg0KRGFuaWVsZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxv
Y2txdW90ZT4NCjwvZGl2Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFua3MgZm9yIGNvbnNpZGVyaW5nIG15IHN1Z2dl
c3RlZCBjaGFuZ2VzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5wcjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFy
Z2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41
cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXJpZ2h0
OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij4tLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IEphcmkgQXJra28gWzxhIGhyZWY9Im1haWx0bzpqYXJp
LmFya2tvQHBpdWhhLm5ldCI+PHNwYW4gc3R5bGU9ImNvbG9yOiM5OTk5OTkiPm1haWx0bzpqYXJp
LmFya2tvQHBpdWhhLm5ldDwvc3Bhbj48L2E+XTxicj4NClNlbnQ6IGx1bmVkw6wgNiBmZWJicmFp
byAyMDE3IDEyOjMyPGJyPg0KVG86IFBldGUgUmVzbmljayAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBy
ZXNuaWNrQHF0aS5xdWFsY29tbS5jb20iPnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb208L2E+Jmd0
Ozxicj4NCkNjOiA8YSBocmVmPSJtYWlsdG86Z2VuLWFydEBpZXRmLm9yZyI+Z2VuLWFydEBpZXRm
Lm9yZzwvYT47IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnIj4NCmRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1v
c3BmLWV4dC5hbGxAaWV0Zi5vcmc8L2E+Ozxicj4NCjxhIGhyZWY9Im1haWx0bzpjY2FtcEBpZXRm
Lm9yZyI+Y2NhbXBAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86aWV0ZkBpZXRmLm9yZyI+
DQppZXRmQGlldGYub3JnPC9hPjxicj4NClN1YmplY3Q6IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9m
IGRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC0wNzxicj4NCjxicj4NClRo
YW5rcyBmb3IgeW91ciByZXZpZXcsIFBldGUuIEF1dGhvcnMsIGFueSBjb21tZW50cz88YnI+DQo8
YnI+DQpKYXJpPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Fy
aWFsJnF1b3Q7LHNhbnMtc2VyaWYiPi0tIDxicj4NClBldGUgUmVzbmljayA8YSBocmVmPSJodHRw
Oi8vd3d3LnF1YWxjb21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0eWxlPSJjb2xvcjojMzk4
M0M0Ij5odHRwOi8vd3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9zcGFuPjwvYT48YnI+DQpR
dWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2NTEtNDQ3ODxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430AM2PR07MB0994eurp_--


From nobody Tue Feb  7 02:01:54 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCB3129506 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 02:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GxUX-BNadnhY for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 02:01:47 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::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 5C0E7129451 for <ietf@ietf.org>; Tue,  7 Feb 2017 02:01:47 -0800 (PST)
Received: by mail-wm0-x232.google.com with SMTP id c85so153360026wmi.1 for <ietf@ietf.org>; Tue, 07 Feb 2017 02:01:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:message-id:date:user-agent:mime-version :content-transfer-encoding; bh=jKvk3i3qzRcv/NWbrENlaXGDWWnhjB3jFQQqY/sZ+Kg=; b=DQlHjKKN6vKWyhrYHKHrhT0uwEPykY57PeqV2rsay2MJuK5bsIrSLRn34iE0xNNWog f5HuPX+8OcxLKRL/j/5HEmLlla2RC2WJmg2z0xf7+KokHrOUXKAhJslW6taMBugzy00Y 8T9yCqVInKiXWUolW4VIK9vcSW/62hCJqJyeQiWvgaZ8Qsqfwtppa+O3/sbD9GI4HsoI UFkw/skpJk5+13btq2IeePEX2yRoR0V5LXOvic/yEDgzMWbyh8vx0KxQLLvQspE6/QPO qyT8IiTmmsr7Cz05gKSsK6jlVDSlflP2XmRSWLMmXxQmpb5x6QRg1U+8/c5jwrDozyeL xcOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:message-id:date:user-agent :mime-version:content-transfer-encoding; bh=jKvk3i3qzRcv/NWbrENlaXGDWWnhjB3jFQQqY/sZ+Kg=; b=bZiXebhRPhokAfz0s6Da1nd95iQjKlNbVwASYKqcsHpbWwmtmuKcpcFP5xxD+red9n ZCU2hz2VnaUsANMbz114l4bdKg0m05wHqNEqUo/LaWzUqC8u44Lk9CTDOhpkoemnEq7k 7xdnzV0TBn2/XhC2UNf+RjMixOk44OdjV76FXbODr2V+qRmAyWoWl7trU9prh8XNhtPd UmkhILEgjDZWgqo5J+lltVDqskfm2UU1AdXFIsNUtzLnNgqsIJiy/EnyYMfAllz+Pjom /FZXOk7nA1DY/y24Pz/gJqWhifMpVwAKwFqf/0mgrJ2a4SoGw54Yh4spwaF1OCO8CsSa 5Kyw==
X-Gm-Message-State: AMke39kmjk5hAmP2obJzGClS4ZpQwcV9t7obbTNkmKZZpWAhnt5I21iHhBge2QAe0wXxVQ==
X-Received: by 10.28.105.68 with SMTP id e65mr11683210wmc.44.1486461705754; Tue, 07 Feb 2017 02:01:45 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 186sm17806389wmw.24.2017.02.07.02.01.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 02:01:45 -0800 (PST)
From: Stewart Bryant <stewart.bryant@gmail.com>
To: Barry Leiba <barryleiba@computer.org>, IETF Discussion <ietf@ietf.org>
Subject: An observation on draft-leiba-rfc2119-update-01
Message-ID: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com>
Date: Tue, 7 Feb 2017 10:01:41 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UwfcvbZvLsr-l4Hb0JFdjkCP04g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 10:01:54 -0000

Barry,

Your proposed text says:

       The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
       NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED",
       "MAY", and "OPTIONAL" in this document are to be interpreted as
       described in BCP 14 [RFC2119],[RFCxxxx] when, and only when, they
       appear in all capitals, as shown here.

The above text raises an interesting problem. If the update system works 
then
the text should read [RFC2119]. If the update system does not work than
the text needs to be [RFC2119],[RFCxxxx] as shown, but we also need to move
to a system where we always list the update set at the time of 
publication, for
example in RFC5462:

Updates: 3032, 3270, 3272, 3443, 3469,
                  3564, 3985, 4182, 4364, 4379,
                  4448, 4761, 5129

If your text is right, then whenever I would write [RFC3032], I should 
in future
write [RFC3032],[RFC5462] etc, alternatively your text is incorrect and
should simply say [RFC2119].

I am also somewhat curious about the practical implication of 
misinterpreting
MUST as must, and must as MUST.

For example: if A receives a foo packet, it MUST/must reply with a bar 
packet

The interoperability considerations are identical, with but with the 
advantage
that  MUST draws the eye of the reader to  the point and reducing the 
chance
that they will miss it. Similarly with the other keywords. So is there 
really
a problem to be fixed here?

- Stewart




From nobody Tue Feb  7 03:27:04 2017
Return-Path: <fatkudu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9100D129B50 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 03:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.676
X-Spam-Level: 
X-Spam-Status: No, score=-1.676 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, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8WjUCzD-wBQT for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 03:26:48 -0800 (PST)
Received: from mail-yw0-x244.google.com (mail-yw0-x244.google.com [IPv6:2607:f8b0:4002:c05::244]) (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 BA4EB129B4E for <ietf@ietf.org>; Tue,  7 Feb 2017 03:26:47 -0800 (PST)
Received: by mail-yw0-x244.google.com with SMTP id v73so9199584ywg.1 for <ietf@ietf.org>; Tue, 07 Feb 2017 03:26:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:cc;  bh=JZ1LcDLMFtYf/pms0OomSQlhu/5hbi8pGZWFzxy/PQo=; b=Cz8+/uXBz25zX4R0Ris0RIylI/2Xi4+p2wWPaWstdxwo6atHnI2nrpC+FdpWtCoItX TXEyyfBVjNpknZwT9H9UPsR3JFwuyfeaYw7DJcRsAnwxX+nFFurxEvScTvOfEzIkf5nE wNZMVXjbSAwRqvDtSeSmRpAiYgvyA4Ir2WNw9imgu/WLn2ZRLimQM/51Oo0h0O29G5FX T/K3hGmaUWPkHu4EasgQU1GCJ/dcfIznmRJTCsg/10w40KgpEKTJxDzrhI+LDiYyQnYC GNK8lU+QPoBh/DX/y+2NVfHne5bJDQyPK2Q0USpwEevqM4ocQycLz50pOQbfJOeBU/XT 49iQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:cc; bh=JZ1LcDLMFtYf/pms0OomSQlhu/5hbi8pGZWFzxy/PQo=; b=qOhN0ybRSs5kgz+kbbMZtcz40R1j4sSTN9I22ibXvOGZdAekN9kVcxb0gN51yDo7t8 d4I4Cn+DBXlQ7Lcz2SF0nWADcOyNNTV+/gaTyX7+jHRdrg8Z+cBvz3eAlqwzftLu/9BD uW9VqIZwOsnfKF4HlM5iCXhQtg0HXqgp0f6z0HeHQ3f6MQjVobmHZLOTST+AiGm0RmKy VN1liD19tsAPtTih5yPTZMpXRboT+HIR/UYGtEv1Fo3He9Et+j7GNwIfukuZa4kD48R4 GXZCjG4uaGpA/31/AIJ5dWNhizZxbfrMvgQ4EhttInI42cH/1B0YW5M0DBi4QWJ1OSO7 mr8w==
X-Gm-Message-State: AMke39m1PLA+XdhqR9Viypyoi+6Vcp2udpy5JEI1nbRKzaE7hLw/cnFelmNK1nOF4nqDs/7D1PVCDszNL7OHcg==
X-Received: by 10.13.193.68 with SMTP id c65mt10909933ywd.88.1486466806915; Tue, 07 Feb 2017 03:26:46 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 7 Feb 2017 03:26:45 -0800
From: Gren Elliot <fatkudu@gmail.com>
In-Reply-To: <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com>
X-Mailer: Airmail (397)
MIME-Version: 1.0
Date: Tue, 7 Feb 2017 03:26:45 -0800
Message-ID: <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Content-Type: multipart/alternative; boundary=001a114e6c00ff45dc0547ef05c1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UgZDOBULwdHAQKHqrG7E40qTHlA>
Cc: jmap@ietf.org, iesg <iesg@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 11:26:49 -0000

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

Hi,

Just to add my voice to the call for easier configuration where we don=E2=
=80=99t
force users to configure countless different things.  Trying to setup a new
device for use with open protocols is a complete nightmare - you end up
needing to configure 2 things for mail (IMAP and SMTP) plus something for
Contacts (CardDAV - perhaps LDAP as well) plus something for Calendar
(CalDAV).  Many users, myself included are also at the mercy of frequent
forced password changes, which necessitate modifying the configuration of
each of these on each device.  Bizarrely, I suspect across 99% odd of use
cases, this separation is completely artificial as the same password is
used on the server for all services (and cannot be different because most
servers regard them as all relating to the same account).  This
configuration complexity must waste countless hours across the world and is
a major reason why businesses welcome ActiveSync - just to solve this one
huge problem with the open protocol landscape. There may be some good
esoteric academic reasons why keeping IMAP and message submission protocols
separate but I think the real world has clearly showed that the added
complexity is too expensive.

I believe JMAP is intending to extend from just Mail to encompass Calendar
and Contacts too and I truly hope it will (in a way that doesn=E2=80=99t re=
quire
servers to offer everything)

Folks at Calconnect and the IETF have been working on
https://tools.ietf.org/html/draft-daboo-aggregated-service-discovery-03 whi=
ch
attempts to ease the configuration burden but that looks like being a long
process and needs buy in from device vendors to be really successful.  I
see most of the need behind this work as a sticky plaster trying to cover
up the un-necessary mess we have created :-(

It would be nice to see config dialogs where user=E2=80=99s are asked for m=
inimal
information (user name, perhaps server name) and then the device discovers
what is available there (Mail/Contacts/Calendar/=E2=80=A6) and offers the u=
ser a
way to select them and perhaps a choice of preferred client(s) to handle
each service.  The way Android handles some things, where a single bit of
software is responsible for server access and perhaps local caching and
other clients can provide UIs to access this is kind of neat too.

Regards,
Gren Elliot
Zimbra Software Engineer at Synacor

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

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto">Hi,</div><div id=3D"bloop_customfont" style=3D"fo=
nt-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;l=
ine-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-famil=
y:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heig=
ht:auto">Just to add my voice to the call for easier configuration where we=
 don=E2=80=99t force users to configure countless different things.=C2=A0 T=
rying to setup a new device for use with open protocols is a complete night=
mare - you end up needing to configure 2 things for mail (IMAP and SMTP) pl=
us something for Contacts (CardDAV - perhaps LDAP as well) plus something f=
or Calendar (CalDAV).=C2=A0 Many users, myself included are also at the mer=
cy of frequent forced password changes, which necessitate modifying the con=
figuration of each of these on each device.=C2=A0 Bizarrely, I suspect acro=
ss 99% odd of use cases, this separation is completely artificial as the sa=
me password is used on the server for all services (and cannot be different=
 because most servers regard them as all relating to the same account).=C2=
=A0 This configuration complexity must waste countless hours across the wor=
ld and is a major reason why businesses welcome ActiveSync - just to solve =
this one huge problem with the open protocol landscape. There may be some g=
ood esoteric academic reasons why keeping IMAP and message submission proto=
cols separate but I think the real world has clearly showed that the added =
complexity is too expensive.</div><div id=3D"bloop_customfont" style=3D"fon=
t-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;li=
ne-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heigh=
t:auto">I believe JMAP is intending to extend from just Mail to encompass C=
alendar and Contacts too and I truly hope it will (in a way that doesn=E2=
=80=99t require servers to offer everything)</div><div><br></div><div id=3D=
"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;colo=
r:rgba(0,0,0,1.0);margin:0px;line-height:auto">Folks at Calconnect and the =
IETF have been working on=C2=A0<a href=3D"https://tools.ietf.org/html/draft=
-daboo-aggregated-service-discovery-03">https://tools.ietf.org/html/draft-d=
aboo-aggregated-service-discovery-03</a>=C2=A0which attempts to ease the co=
nfiguration burden but that looks like being a long process and needs buy i=
n from device vendors to be really successful.=C2=A0 I see most of the need=
 behind this work as a sticky plaster trying to cover up the un-necessary m=
ess we have created :-(</div><div id=3D"bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-he=
ight:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">It would be nice to see config dialogs where user=E2=80=99s are asked fo=
r minimal information (user name, perhaps server name) and then the device =
discovers what is available there (Mail/Contacts/Calendar/=E2=80=A6) and of=
fers the user a way to select them and perhaps a choice of preferred client=
(s) to handle each service.=C2=A0 The way Android handles some things, wher=
e a single bit of software is responsible for server access and perhaps loc=
al caching and other clients can provide UIs to access this is kind of neat=
 too.</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Aria=
l;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></d=
iv> <div id=3D"bloop_sign_1486463613119693056" class=3D"bloop_sign"><div st=
yle=3D"font-family:helvetica,arial;font-size:13px">Regards,</div><div style=
=3D"font-family:helvetica,arial;font-size:13px">Gren Elliot<br></div><div s=
tyle=3D"font-family:helvetica,arial;font-size:13px">Zimbra Software Enginee=
r at Synacor</div></div></body></html>

--001a114e6c00ff45dc0547ef05c1--


From nobody Tue Feb  7 06:11:49 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D365129C42; Tue,  7 Feb 2017 06:11:47 -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 autolearn_force=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 g8Qj-hMwumwF; Tue,  7 Feb 2017 06:11:45 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 D4803129C38; Tue,  7 Feb 2017 06:11:45 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cb6Uh-00007t-HB; Tue, 07 Feb 2017 14:11:43 +0000
Date: Tue, 07 Feb 2017 23:11:41 +0900
Message-ID: <m28tpiytsy.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gren Elliot <fatkudu@gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com> <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Nk9_WaasLb2bkG0wIkW6aIj24kA>
Cc: jmap@ietf.org, iesg <iesg@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 14:11:47 -0000

> Trying to setup a new device for use with open protocols is a complete
> nightmare - you end up needing to configure 2 things for mail (IMAP
> and SMTP)

and now, because we will have to be backward compatible, it will be
three.  so that third had best be a really massive win.  and i am not
seeing it.  what i am seeing is second system syndrome in a wrapper of
whatever today's wrapping fashion is.

randy


From nobody Tue Feb  7 06:21:17 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C993B129C64; Tue,  7 Feb 2017 06:21:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S81QAEutkQRy; Tue,  7 Feb 2017 06:21:10 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 C4E72129C62; Tue,  7 Feb 2017 06:21:10 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v17EMmEM004300 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Feb 2017 06:22:48 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486477368; bh=KxWKYDKe37ta0S9CO9qjMz63xjjlUfEX5Rl2ZpdE41o=; h=Subject:To:References:Cc:Reply-To:From:Date:In-Reply-To:From; b=juaw9FbJfF9Pg8Oijqy3XVFoRnWR8BUj6jo/G7BMO0TcORXMqGb+ZyphX0TZ94Jx5 J0+H++CAXHspYISvHMQUwovSzjaxvTcNMPI4tXy1pFDi3e2V0f8W+XhON6uTZCA+BA X2tAGqN8ES/COwAc2RF0Ga4AH45blhlWLQgnukC0=
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Gren Elliot <fatkudu@gmail.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com> <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <c2e15625-2241-603e-080d-8593b87e0bca@dcrocker.net>
Date: Tue, 7 Feb 2017 06:21:00 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cNhAiRDGYZizEHPcByqJEmn_1uI>
Cc: jmap@ietf.org, iesg <iesg@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 14:21:12 -0000

On 2/7/2017 3:26 AM, Gren Elliot wrote:
> Just to add my voice to the call for easier configuration where we don’t
> force users to configure countless different things.  Trying to setup a
> new device for use with open protocols is a complete nightmare - you end
> up needing to configure 2 things for mail (IMAP and SMTP)
...
> It would be nice to see config dialogs where user’s are asked for
> minimal information (user name, perhaps server name) and then the device
> discovers what is available there (Mail/Contacts/Calendar/…) and offers
> the user a way to select them and


This issue is for user interface design, not underlying protocol design. 
  Hence while it is extremely important in terms of usability, it is 
outside the scope of the IETF.

Having these functions embedded into a single protocol implicitly 
requires that these different functions share the same configuration 
data.  While such sharing might be common practice, requiring the 
sharing limits operational choices.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Tue Feb  7 07:18:59 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3111129CB2 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 07:18:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kg7uWcJFRZC9 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 07:18:51 -0800 (PST)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 A952D129CB3 for <ietf@ietf.org>; Tue,  7 Feb 2017 07:18:51 -0800 (PST)
Received: by mail-qt0-x231.google.com with SMTP id x49so137062300qtc.2 for <ietf@ietf.org>; Tue, 07 Feb 2017 07:18:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=upxyFFSs8w1zOzixauNrrHtqMwX1OVNYfhUVmXMqd3c=; b=nrTlhYFQLwe5hkiiJr+jFM3eToS5rHA1syXt30/n5oHpch59aAJ+66o62QIYdqG1BI eNkHCfY4oeLr3LzbpKM/pL/XWe/OyY+vbYN4Hrjeu7MtoESmNLL1cH06KDiW6RlFokYA edTt8yMJCPw9nqnsXYvbFX/2idbNH5G/sTER+EgkQQW71n10/ZM+hEQ1FDwgsaDDoInQ JsKqv5qfs8vi5Sak9HQaIWsZgxESMC8sA95NYQCEcSzq7aqapkOCf7+sAWlIChr7UlPz +x9YHX9kymW3OESKP4O3tZIPo3EkFtTMWYQU900EUXbqr2SEFOHHPFiNGKqrGiU5KW1s 9rMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=upxyFFSs8w1zOzixauNrrHtqMwX1OVNYfhUVmXMqd3c=; b=iic3AB+UiiBP13oPzdvDx4AMYl37yw9LsdnxYyo4BZpOvGoDaw021vYfsXe5PzjL4W nSXORy4XvG+oajyqoLhFl11+tx+HFX3/GiyLv4iCijzP/Szjc+ICGgr2gVX5nXSMutXk 36b59dr00x89VTGnbP/Dcq7M9oN7ZKXkPQwmweRQO8K42ht2dQWpaAZtOkrN1b2QxmXL Yjhs/XXoVOEpU2uK7o6mXrN+sx0S38PlakK8WjZUndvtqCGOE0whCEGqt+W7trFH47Km 4lbBI5oE1gtfH2LSee8K+mq+PiFhfMa1bqnLX735cBU088wszGVfkaTQP9VClB3mnWIj pfJA==
X-Gm-Message-State: AMke39nn15GN6n8DbCoyZeUzhoh64bdMIHE4sHHoflMM+gVaBG3zne8vbnxRCC5wxofKmQ==
X-Received: by 10.200.47.129 with SMTP id l1mr14308854qta.148.1486480730382; Tue, 07 Feb 2017 07:18:50 -0800 (PST)
Received: from [10.0.20.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id k8sm3590624qke.29.2017.02.07.07.18.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 07:18:48 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <8B24068E-6EA6-404B-AFEC-76C9A0029954@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6FB82B1A-B4F8-4B93-B738-2880351BC4F6"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Tue, 7 Feb 2017 10:18:45 -0500
In-Reply-To: <c2e15625-2241-603e-080d-8593b87e0bca@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com> <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com> <c2e15625-2241-603e-080d-8593b87e0bca@dcrocker.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fBU-eDN-O3kig6cfblROhc-ngiQ>
Cc: jmap@ietf.org, iesg <iesg@ietf.org>, Gren Elliot <fatkudu@gmail.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 15:18:53 -0000

--Apple-Mail=_6FB82B1A-B4F8-4B93-B738-2880351BC4F6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 7, 2017, at 9:21 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>> It would be nice to see config dialogs where user=E2=80=99s are asked =
for
>> minimal information (user name, perhaps server name) and then the =
device
>> discovers what is available there (Mail/Contacts/Calendar/=E2=80=A6) =
and offers
>> the user a way to select them and
>=20
> This issue is for user interface design, not underlying protocol =
design.  Hence while it is extremely important in terms of usability, it =
is outside the scope of the IETF.

I must beg to differ.   While it's true that we don't care explicitly =
about UI, we certainly care about enabling UIs that work.   Providing a =
query that returns the information required to send mail is definitely =
worth doing.   Of course, that could be just allowing a message to be =
uploaded, and having a command that says "deliver this message".   It's =
not clear to me that submission by way of SMTP is actually a win =
here=E2=80=94it's really an extra step, since you probably were going to =
save the draft using the mailbox protocol anyway.


--Apple-Mail=_6FB82B1A-B4F8-4B93-B738-2880351BC4F6
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"">On Feb 7, 2017, at 9:21 AM, Dave Crocker &lt;<a =
href=3D"mailto:dhc@dcrocker.net" class=3D"">dhc@dcrocker.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"Singleton"><blockquote type=3D"cite" style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">It would be nice to see =
config dialogs where user=E2=80=99s are asked for<br class=3D"">minimal =
information (user name, perhaps server name) and then the device<br =
class=3D"">discovers what is available there =
(Mail/Contacts/Calendar/=E2=80=A6) and offers<br class=3D"">the user a =
way to select them and<br class=3D""></blockquote><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">This issue is for user interface design, not =
underlying protocol design. &nbsp;Hence while it is extremely important =
in terms of usability, it is outside the scope of the =
IETF.</span></div></div></blockquote></div><br class=3D""><div =
class=3D"">I must beg to differ. &nbsp; While it's true that we don't =
care explicitly about UI, we certainly care about enabling UIs that =
work. &nbsp; Providing a query that returns the information required to =
send mail is definitely worth doing. &nbsp; Of course, that could be =
just allowing a message to be uploaded, and having a command that says =
"deliver this message". &nbsp; It's not clear to me that submission by =
way of SMTP is actually a win here=E2=80=94it's really an extra step, =
since you probably were going to save the draft using the mailbox =
protocol anyway.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_6FB82B1A-B4F8-4B93-B738-2880351BC4F6--


From nobody Tue Feb  7 07:33:40 2017
Return-Path: <fatkudu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B2F0129CB7; Tue,  7 Feb 2017 07:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cw6g32d0n0eg; Tue,  7 Feb 2017 07:33:29 -0800 (PST)
Received: from mail-yw0-x241.google.com (mail-yw0-x241.google.com [IPv6:2607:f8b0:4002:c05::241]) (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 B14B1129CD1; Tue,  7 Feb 2017 07:33:18 -0800 (PST)
Received: by mail-yw0-x241.google.com with SMTP id l16so9692020ywb.2; Tue, 07 Feb 2017 07:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=XbnzsFGbqVilLiXt/HhxGtqyr9+ge9FO4HglZWeRRgw=; b=mLRkRxRJOGj5Za8O7eBJ4Rxl3YvL+kfbwFh8TdCasffNz6SEUXElO1DmG747nSL1YY sO7+dLuA29XAKRFCgw/6/bGTnlbWDLVomkdt9yaO9SCd+iGVPfzIZ0QNnyHC95B5zrGU 3ImLVoaSOQsZVbbRkEIyUrDzwBBIlPIIx3DH0pU1PCnkE0mUG4B8VedCEudsj6LaXSmt ThhdgIgj+j6+OW1Lzob8hDrKzqeI89cDJAS43XsxERNTiB6r9RjRpp8QIhPJXE4rePHO bR0xnZjlHFhKfFzwQp5JQRDVg5rVzNJSR8o/3FCsyyN8GR0991tRTLL6YCeuMO9Rk5iN Bc2Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=XbnzsFGbqVilLiXt/HhxGtqyr9+ge9FO4HglZWeRRgw=; b=BtUAoI2aa5NDiPklRS7CI9D9dq0Nk6w1IAc4xBRaUK3jYiiezMuBD6h3fe4fHg0QGO ARiZIC6GMiHSjVe8Jc4imuObNJ5DqE9ax1dn3ywvEq0qJHA4EC51mnIdRSPjZ0N8LxgZ qYkvv/1+zccWSgBLDv3guo63C4TLI2eHci9n3UAhMPm/qXAwAB41TYHkPOPk+Epop3JF Eu3dcKvOBd3o5cxVAptqbJzbEL6NuaG2MyZvSwFEDsTTBWUSk2ABhVTv0GqSjRfjali6 PLCMvENsOTvU8/3oVLfneXWOMGZV8j4REJgmvVl6kF6ym+uLi5JV6IprO+UDBv9SJoDE pIJw==
X-Gm-Message-State: AIkVDXK9VSPwUmRvQ5tecVFyLHlw0F83zsGo5x9gweTJBSA1CwwU2cc+78XjmiHabsjp+9JredM1D8Tkkw0iSw==
X-Received: by 10.129.123.197 with SMTP id w188mr11306383ywc.267.1486481597981;  Tue, 07 Feb 2017 07:33:17 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 7 Feb 2017 07:33:16 -0800
From: Gren Elliot <fatkudu@gmail.com>
In-Reply-To: <c2e15625-2241-603e-080d-8593b87e0bca@dcrocker.net>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <1486435969.2314063.872594064.21072F60@webmail.messagingengine.com> <CAMQk0F-Xgkd7D8k1KmzpGdUKV7q8FERCrSh_weJ6MaioAE=dbQ@mail.gmail.com> <c2e15625-2241-603e-080d-8593b87e0bca@dcrocker.net>
X-Mailer: Airmail (397)
MIME-Version: 1.0
Date: Tue, 7 Feb 2017 07:33:16 -0800
Message-ID: <CAMQk0F_EyVN+NsUJ6JfBGH55-yQe5G_D-Ow23Fo+UEuyPf5wjA@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Dave Crocker <dhc@dcrocker.net>, dcrocker@bbiw.net
Content-Type: multipart/alternative; boundary=001a114948789cebff0547f2776e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Sk0jJM8EVs-ueuBzKzeBzQzapvY>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 15:33:31 -0000

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

From: Dave Crocker <dhc@dcrocker.net> <dhc@dcrocker.net>
Reply: dcrocker@bbiw.net <dcrocker@bbiw.net> <dcrocker@bbiw.net>
Date: 7 February 2017 at 14:21:10
To: Gren Elliot <fatkudu@gmail.com> <fatkudu@gmail.com>
Cc: jmap@ietf.org <jmap@ietf.org> <jmap@ietf.org>, iesg <iesg@ietf.org>
<iesg@ietf.org>, ietf@ietf.org <ietf@ietf.org> <ietf@ietf.org>
Subject:  Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing
configuration complexity

On 2/7/2017 3:26 AM, Gren Elliot wrote:
> Just to add my voice to the call for easier configuration where we don=E2=
=80=99t
> force users to configure countless different things. Trying to setup a
> new device for use with open protocols is a complete nightmare - you end
> up needing to configure 2 things for mail (IMAP and SMTP)
...
> It would be nice to see config dialogs where user=E2=80=99s are asked for
> minimal information (user name, perhaps server name) and then the device
> discovers what is available there (Mail/Contacts/Calendar/=E2=80=A6) and =
offers
> the user a way to select them and


This issue is for user interface design, not underlying protocol design.
Hence while it is extremely important in terms of usability, it is
outside the scope of the IETF.

With the current standards landscape, there is no way round the fact that
users (often not tech savvy ones) need to specify separate hostnames and
ports for IMAP and message submission, plus potentially URLs for CalDAV /
CardDAV (the latter 2 could reasonably be combined without IETF help but
sadly seldom are).  Without further standardisation, no wonderful interface
design can escape from that.  I certainly think that it should be within
the scope of the IETF to improve the standards to the point where good
interface design is possible.  That doesn=E2=80=99t actually require moving=
 to a
single protocol.  As mentioned before in relation to aggregated service
discovery, this could be achieved by standardising a bootstrapping
mechanism where the user only provides minimal information which points to
a store of detailed configuration information that the user never needs to
be aware of.  Alternatively, or perhaps in addition, having a single
protocol would achieve most of the same aims - much as ActiveSync achieves
and I hope JMAP will achieve.

Having these functions embedded into a single protocol implicitly
requires that these different functions share the same configuration
data. While such sharing might be common practice, requiring the
sharing limits operational choices.

Requiring sharing would indeed limit operational choices - so it shouldn=E2=
=80=99t
be required.  I think it is important that a JMAP service should be able to
offer (and advertise) whatever subset of full services it wants to.  In the
most common situation, a single JMAP service would provide mail access,
mail submission, contacts access, calendar access etc, but there is no
reason why multiple, dedicated JMAP services couldn=E2=80=99t be used, one =
just
doing mail access, one doing mail submission etc.  In the most common
situation, you would be much better off than you are now.  In the other
case, you would be no worse off than you are currently and at least there
would be consistency in how you configure each service.
Regards,
Gren Elliot

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

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto"><div class=3D"airmail_ext_on">From:=C2=A0Dave Cro=
cker=C2=A0<a href=3D"mailto:dhc@dcrocker.net">&lt;dhc@dcrocker.net&gt;</a><=
br>Reply:=C2=A0<a href=3D"mailto:dcrocker@bbiw.net">dcrocker@bbiw.net</a>=
=C2=A0<a href=3D"mailto:dcrocker@bbiw.net">&lt;dcrocker@bbiw.net&gt;</a><br=
>Date:=C2=A07 February 2017 at 14:21:10<br>To:=C2=A0Gren Elliot=C2=A0<a hre=
f=3D"mailto:fatkudu@gmail.com">&lt;fatkudu@gmail.com&gt;</a><br>Cc:=C2=A0<a=
 href=3D"mailto:jmap@ietf.org">jmap@ietf.org</a>=C2=A0<a href=3D"mailto:jma=
p@ietf.org">&lt;jmap@ietf.org&gt;</a>,=C2=A0iesg=C2=A0<a href=3D"mailto:ies=
g@ietf.org">&lt;iesg@ietf.org&gt;</a>,=C2=A0<a href=3D"mailto:ietf@ietf.org=
">ietf@ietf.org</a>=C2=A0<a href=3D"mailto:ietf@ietf.org">&lt;ietf@ietf.org=
&gt;</a><br>Subject:=C2=A0=C2=A0Re: [Jmap] WG Review: JSON Mail Access Prot=
ocol (jmap) - reducing configuration complexity=C2=A0<br></div><br><div><di=
v><blockquote type=3D"cite" class=3D"clean_bq"><div></div><div>On 2/7/2017 =
3:26 AM, Gren Elliot wrote:=C2=A0<br>&gt; Just to add my voice to the call =
for easier configuration where we don=E2=80=99t=C2=A0<br>&gt; force users t=
o configure countless different things. Trying to setup a=C2=A0<br>&gt; new=
 device for use with open protocols is a complete nightmare - you end=C2=A0=
<br>&gt; up needing to configure 2 things for mail (IMAP and SMTP)=C2=A0<br=
>...=C2=A0<br>&gt; It would be nice to see config dialogs where user=E2=80=
=99s are asked for=C2=A0<br>&gt; minimal information (user name, perhaps se=
rver name) and then the device=C2=A0<br>&gt; discovers what is available th=
ere (Mail/Contacts/Calendar/=E2=80=A6) and offers=C2=A0<br>&gt; the user a =
way to select them and=C2=A0<br><br><br>This issue is for user interface de=
sign, not underlying protocol design.=C2=A0<br>Hence while it is extremely =
important in terms of usability, it is=C2=A0<br>outside the scope of the IE=
TF.=C2=A0<br><br></div></blockquote><p>With the current standards landscape=
, there is no way round the fact that users (often not tech savvy ones) nee=
d to specify separate hostnames and ports for IMAP and message submission, =
plus potentially URLs for CalDAV / CardDAV (the latter 2 could reasonably b=
e combined without IETF help but sadly seldom are).=C2=A0 Without further s=
tandardisation, no wonderful interface design can escape from that.=C2=A0 I=
 certainly think that it should be within the scope of the IETF to improve =
the standards to the point where good interface design is possible.=C2=A0 T=
hat doesn=E2=80=99t actually require moving to a single protocol.=C2=A0 As =
mentioned before in relation to aggregated service discovery, this could be=
 achieved by standardising a bootstrapping mechanism where the user only pr=
ovides minimal information which points to a store of detailed configuratio=
n information that the user never needs to be aware of.=C2=A0 Alternatively=
, or perhaps in addition, having a single protocol would achieve most of th=
e same aims - much as ActiveSync achieves and I hope JMAP will achieve.</p>=
<blockquote type=3D"cite" class=3D"clean_bq">Having these functions embedde=
d into a single protocol implicitly=C2=A0<br>requires that these different =
functions share the same configuration=C2=A0<br>data. While such sharing mi=
ght be common practice, requiring the=C2=A0<br>sharing limits operational c=
hoices.=C2=A0</blockquote></div><p>Requiring sharing would indeed limit ope=
rational choices - so it shouldn=E2=80=99t be required.=C2=A0 I think it is=
 important that a JMAP service should be able to offer (and advertise) what=
ever subset of full services it wants to.=C2=A0 In the most common situatio=
n, a single JMAP service would provide mail access, mail submission, contac=
ts access, calendar access etc, but there is no reason why multiple, dedica=
ted JMAP services couldn=E2=80=99t be used, one just doing mail access, one=
 doing mail submission etc.=C2=A0 In the most common situation, you would b=
e much better off than you are now.=C2=A0 In the other case, you would be n=
o worse off than you are currently and at least there would be consistency =
in how you configure each service.</p></div></div> <div id=3D"bloop_sign_14=
86479656909039104" class=3D"bloop_sign"><div style=3D"font-family:helvetica=
,arial;font-size:13px">Regards,</div><div style=3D"font-family:helvetica,ar=
ial;font-size:13px">Gren Elliot<br></div></div> <div class=3D"airmail_ext_o=
n" style=3D"color:black"><br></div></body></html>

--001a114948789cebff0547f2776e--


From nobody Tue Feb  7 07:38:36 2017
Return-Path: <fatkudu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF7B129CB8; Tue,  7 Feb 2017 07:38:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g8vsx-urIq7w; Tue,  7 Feb 2017 07:38:28 -0800 (PST)
Received: from mail-yb0-x230.google.com (mail-yb0-x230.google.com [IPv6:2607:f8b0:4002: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 D77D3129C9E; Tue,  7 Feb 2017 07:38:27 -0800 (PST)
Received: by mail-yb0-x230.google.com with SMTP id w194so36351286ybe.0; Tue, 07 Feb 2017 07:38:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:date:message-id:subject:to; bh=fflSiA+DXbFbHui+PXMXK6LyijM3DYbrUxU3sK0wBAE=; b=D9fBZWKonB2BBodVR9bay0dD9Ly0Hcw6rTZ+2aPwACVJLjrdjDx1QD4B6GG7PXIxg7 M7lRHf8LUYcH1Ejd4KRYE3qM9rrO4JPjF7ONmpXDz4C5Kumu1QQgeTNG1z8wGMfKQvl0 6obvRAGj9xsKzaRG89PUX7XcxR5EWfh7fTwqAduv4mpkmRfhC0RO5HhT8xAehu3HtnxN Z5vd0f85VKTk3DryD84OqLQqAjNr5JcBul6fObPWKCRdHwNJKQaFPSGdIrPBMpC6dMBW PjoIccV6xqH3SjDxPfF0OzXmHaZnClTuQc5P0xats/PkNWWJoGJKHtau6rj6Z/iSv/ey NoHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=fflSiA+DXbFbHui+PXMXK6LyijM3DYbrUxU3sK0wBAE=; b=W/X1NIUIcKA0vObAVt+Um08WzoDPD0DLhoxkPFCTj2DYsNt1F/qo8YyGY2zmih/0gM uBXL7aEHUL9XjDMMT7VbhAMOrvhtO5r1vr9hPUEQ16LLa8VwXvto6bTz5lNQ72T+0Tiu fkNhPwbgWieYH0Av0DsRfX9O/soFiuruyDKRtDgZmZMl6rerdC1ikQy2dyfERH2S1eQz 7uKF8RvEvuENGZgocLerbYurZ+ksdlEu4NbHGrz/IeDmBDK3QAGp0f6+q0tx3ehw21N6 4I2+2McviI29IJ5cAbevfd8uPK15ysN//3yNfTdFPEHvXRB8vvvRkHeEdxtxO3wSWlEy 1Ysw==
X-Gm-Message-State: AMke39lOtDQrhj8aSZ13/iOnRQsHePxdUmDzu7aeSl/VEF6lQ5pKpr0AsYyzMNYOBLyscy7XmCgkxJbju88BHg==
X-Received: by 10.37.51.215 with SMTP id z206mr11618321ybz.88.1486481906881; Tue, 07 Feb 2017 07:38:26 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 7 Feb 2017 07:38:26 -0800
From: Gren Elliot <fatkudu@gmail.com>
X-Mailer: Airmail (397)
MIME-Version: 1.0
Date: Tue, 7 Feb 2017 07:38:26 -0800
Message-ID: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
Subject: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: jmap@ietf.org, iesg@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1148a1180670d50547f28a95
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PLHpmmd74LWn5EZzZ6KdMMtPjcg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 15:38:31 -0000

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

> Trying to setup a new device for use with open protocols is a complete
> nightmare - you end up needing to configure 2 things for mail (IMAP
> and SMTP)

and now, because we will have to be backward compatible, it will be
three. so that third had best be a really massive win. and i am not
seeing it. what i am seeing is second system syndrome in a wrapper of
whatever today <http://airmail.calendar/2017-02-07%2012:00:00%20GMT>'s
wrapping fashion is.

randy

Why?  You will either be using IMAP/SMTP to access your mail/submit your
messages or you will be using JMAP.  If you have the option of the latter,
you=E2=80=99ve just halved the number of things that need configuring.

Regards,
Gren Elliot
(forgot to include the mailing lists in reply to Randy earlier)

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

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word"><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto"><div style=3D"font-family:&#39;helvetica Neue&#39=
;,helvetica;font-size:14px"><blockquote class=3D"clean_bq">&gt; Trying to s=
etup a new device for use with open protocols is a complete=C2=A0<br>&gt; n=
ightmare - you end up needing to configure 2 things for mail (IMAP=C2=A0<br=
>&gt; and SMTP)=C2=A0<br><br>and now, because we will have to be backward c=
ompatible, it will be=C2=A0<br>three. so that third had best be a really ma=
ssive win. and i am not=C2=A0<br>seeing it. what i am seeing is second syst=
em syndrome in a wrapper of=C2=A0<br>whatever=C2=A0<a href=3D"http://airmai=
l.calendar/2017-02-07%2012:00:00%20GMT">today</a>&#39;s wrapping fashion is=
.=C2=A0<br><br>randy=C2=A0</blockquote></div><p style=3D"font-family:&#39;h=
elvetica Neue&#39;,helvetica;font-size:14px">Why?=C2=A0 You will either be =
using IMAP/SMTP to access your mail/submit your messages or you will be usi=
ng JMAP.=C2=A0 If you have the option of the latter, you=E2=80=99ve just ha=
lved the number of things that need configuring.</p></div> <br> <div id=3D"=
bloop_sign_1486481684578511872" class=3D"bloop_sign"><div style=3D"font-fam=
ily:helvetica,arial;font-size:13px">Regards,</div><div style=3D"font-family=
:helvetica,arial;font-size:13px">Gren Elliot</div><div style=3D"font-family=
:helvetica,arial;font-size:13px">(forgot to include the mailing lists in re=
ply to Randy earlier)</div></div></body></html>

--001a1148a1180670d50547f28a95--


From nobody Tue Feb  7 07:46:03 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82A0F129CE1 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 07:46:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zki2GDmgzoVv for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 07:46:00 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 7C18C129CD9 for <ietf@ietf.org>; Tue,  7 Feb 2017 07:45:57 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id v23so138239160qtb.0 for <ietf@ietf.org>; Tue, 07 Feb 2017 07:45:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=H8psY/5xXXtb/K8+QEN9abnG2Ws2U4MduyiY0OQBicU=; b=h/8KJP3YptJehPyvvCbL/h9WER/9U4qFuh3Tu7NXZetayOE7AsCvUsexv6vVN2nPao WnK1Ds2cJBqsmZvxjTevrgX3nEMg/HmPvlkh5+F7095J014deiEGrMyz9q9h8IP9eqxq v82se4HmUHJ+sTOfHOrOTpTRm6oNQRHFUtfRKrVvNZOnqbHdLlNQSpq2e4rxhBeV4VAx yqSI5cPdykQLT/K8v5RNeKLxgHFjURHuvs9sgpfa4Z2M6nIjalxDxes6n46ZkaVeGQX7 Ti25WjLELABu+WBM8RrUXAIwgpoUxc9Jufy7/k272oWtfeDbcLRNGybroDMEJkftSOlf sfRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=H8psY/5xXXtb/K8+QEN9abnG2Ws2U4MduyiY0OQBicU=; b=aqqnfP+pByeNx97R3H4ya7VZujNfpWaZ2R/ca+JGTXMUv//r/7ZvOAG/3AfitzyUns rcG4WCgqLePojpPr2XYZjlhmJjkGAr5Te1r+PE9E7LAUZe/Fh9bbJdzzeI8o/oslkZ1c tMOEHbG5Na5N5Xgy5VBnKU6r0z0a+4V1VDgyS/UKWDWcBH0WuflidZl2SODMQYt//Eph /krVdUZOzXLtm9RQzqbUm7/WeUJitGrPzNoHgxvq+nQZh3VkSCpabB8yFqsOIIrPlOk4 0xK+DbxPB+Tr77E1slqRTjtTw3EVaOaWW37h2DxvbIGQpKkdoN5EwlSYzCXN68PokQSw AmkA==
X-Gm-Message-State: AMke39nyYIhxUfHW/JhfdWdj/UZs3/EQv5JwwoADMXRQx3GZhrJQfuHrDgllY8XKChfxQ5h/xR32KfBVXDnQOA==
X-Received: by 10.237.44.228 with SMTP id g91mr14633418qtd.184.1486482356612;  Tue, 07 Feb 2017 07:45:56 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.140.19.72 with HTTP; Tue, 7 Feb 2017 07:45:56 -0800 (PST)
In-Reply-To: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com>
References: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 7 Feb 2017 10:45:56 -0500
X-Google-Sender-Auth: Kh5VElArVrCuMfjujhSytFVNOJY
Message-ID: <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
Subject: Re: An observation on draft-leiba-rfc2119-update-01
To: Stewart Bryant <stewart.bryant@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mGakkvJaYHwEnRt7RAM93WQZpho>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 15:46:01 -0000

Hi, Stewart.

> The above text raises an interesting problem. If the update system works
> then
> the text should read [RFC2119]. If the update system does not work than
> the text needs to be [RFC2119],[RFCxxxx] as shown, but we also need to move
> to a system where we always list the update set at the time of publication,

It took me a while to get what you mean here, but I think I have it:
you're saying that because this document (RFC xxxx) UPDATES RFC 2119,
*any* document that cites RFC 2119 and is published after this one
must automatically be taken to refer to this one and must follow the
terms of this one.  So why have the double citation?

You're right, as far as that goes, but if it's important to know for
sure whether a document is following the terms of RFC xxxx or not (and
see below about that), then I think it's important to be explicit
about it.  It's a question of clarity: the reader of another document
should not have to wonder, should not have to check publication dates,
should not be uncertain.  Having the citation there explicitly is good
for clarity.

In fact, we *do* often (though not always) cite update documents when
we're explicitly talking about a feature that was updated.  I think we
do it when calling the reader's attention to the update is
particularly important.

Now, as to the other point:

> I am also somewhat curious about the practical implication of
> misinterpreting
> MUST as must, and must as MUST.
>
> For example: if A receives a foo packet, it MUST/must reply with a bar
> packet
>
> The interoperability considerations are identical, with but with the
> advantage
> that  MUST draws the eye of the reader to  the point and reducing the chance
> that they will miss it. Similarly with the other keywords. So is there
> really
> a problem to be fixed here?

This did come up in earlier discussion about "MUST".  Sure, it's
possible that there really isn't a reason to define "MUST" in BCP 14
because the English meaning is clear enough.  But "SHOULD" and "MAY"
do need these definitions: the English meanings don't accurately
convey the BCP 14 meaning.  And even with "MUST", the BCP 14 meaning
explicitly says that it's a protocol requirement that affects
interoperability or security, and we do seem to think that making that
distinction is important.

In any case, the current BCP 14 defines "MUST", and it's specifically
not a goal of this document to change that older decision.

Barry


From nobody Tue Feb  7 08:06:34 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D837129CEE for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:06:31 -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 autolearn_force=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 RJ8G-oo02YrY for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:06:30 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AAAD129CEC for <ietf@ietf.org>; Tue,  7 Feb 2017 08:06:30 -0800 (PST)
Received: (qmail 67499 invoked from network); 7 Feb 2017 16:06:29 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Feb 2017 16:06:29 -0000
Date: 7 Feb 2017 16:06:06 -0000
Message-ID: <20170207160606.9563.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [Jmap] service discovery, was WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <CAMQk0F_EyVN+NsUJ6JfBGH55-yQe5G_D-Ow23Fo+UEuyPf5wjA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qz4NDdmiKb9df8JCqPgG9j9fgGk>
Cc: fatkudu@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:06:31 -0000

> It would be nice to see config dialogs where user’s are asked for
> minimal information (user name, perhaps server name) and then the device
> discovers what is available there (Mail/Contacts/Calendar/…) and offers
> the user a way to select them and

Of course.  The way you do that is with service discovery, not by
glomming everything into one swiss-army-knife protocol.

We have RFC 6186 which provides a straightforward way to discover
submission, pop, and imap servers for a domain.  Nobody uses it, and
people who run large mail systems tell me that's because it's not
granular enough, they put different users on different servers so they
need to be able to provide per-mailbox configuration info.  That
doesn't seem to me to be a terribly difficult problem, but it's not
one that I believe JMAP does or should try to solve.

R's,
John


From nobody Tue Feb  7 08:10:32 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D2C9129D00 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YcUYnj2y9TwZ for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:10:29 -0800 (PST)
Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::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 93FA1129CFE for <ietf@ietf.org>; Tue,  7 Feb 2017 08:10:27 -0800 (PST)
Received: by mail-wm0-x22b.google.com with SMTP id r141so158246315wmg.1 for <ietf@ietf.org>; Tue, 07 Feb 2017 08:10:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=tYBO44AsTuWUBkXHH0qw84NHB9e/riQ/OMhVqyAG0jE=; b=mZbZlZxlM92C9PfJmJ7p4mN6SEkqy/dievgfGK+COr+ktnFBEadwsE2RcacSJ1OqUY QU3kPvG1lNt5Xnnj+F8fSf1yXe5MxQD6cYH1zKktnuGod3GlBz1896Bm0yuMhmQgAvvF 2zB99aJtQR5BwUJDnxoN29HqZzJXWT9LQM1Krdc3SpXDmpNxbQdJZP20v8vjR4mWa7zX DxLgJHsV2nOTNTWpXMmXvAIL5eFcgUAnX5NJYjnnRICEkJWHm/L7byoWKQ0LQQMsSaE7 dWwzMD1ZE96Uhk/Y5gEtVMNC8OjLLuoYxT0AJHVwD6kdOPqrjkrbaRcZGe1UdPyyKYl7 2GTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=tYBO44AsTuWUBkXHH0qw84NHB9e/riQ/OMhVqyAG0jE=; b=lgg9yKueJ4OAgskvRYy0NfGNwvbK64zf8lyebYlNbMCtRUanlH8CatQ8k5UaYnG8qz pJJRngN64N2h+ZZ8rb0G4knxy1e/9aALO2XAqSCJEnfhLgE9vTXgupGqGQuCM4TwVtZ5 1fF5jIPYjuUBWvlrog1yV3yGzaJgSbh5CZfUCMwv/zPbOfGJpTn27OniotUvXGBVEKS+ yDSIW+HN/SFir0zuRQGCqt+RSqIRJ+PI4p4mVFgByTS7klCi30vrlgWFGHLpdOOpVbZI SGKpY4mrF5MKcJtXVbvITSnCJAVRPDJLUN7CFDtdl7vxCOmJfPBUP2oN1cJfnPoB7DyD y3pg==
X-Gm-Message-State: AMke39lsOl4cr0TOB+XFSc4RlQQzD1zl8449Dji1S42XE9AY4NFktW4fms+T8CooY134VQ==
X-Received: by 10.28.55.199 with SMTP id e190mr12793608wma.92.1486483824545; Tue, 07 Feb 2017 08:10:24 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id e74sm19557344wmd.2.2017.02.07.08.10.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 08:10:24 -0800 (PST)
Subject: Re: An observation on draft-leiba-rfc2119-update-01
To: Barry Leiba <barryleiba@computer.org>
References: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com> <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <d3d29686-ce17-3cbd-2693-6a1334092f44@gmail.com>
Date: Tue, 7 Feb 2017 16:10:23 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q2AEa_A93zS144OreqerXoDXhcs>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:10:30 -0000

On 07/02/2017 15:45, Barry Leiba wrote:
> Hi, Stewart.
>
>> The above text raises an interesting problem. If the update system works
>> then
>> the text should read [RFC2119]. If the update system does not work than
>> the text needs to be [RFC2119],[RFCxxxx] as shown, but we also need to move
>> to a system where we always list the update set at the time of publication,
> It took me a while to get what you mean here, but I think I have it:
> you're saying that because this document (RFC xxxx) UPDATES RFC 2119,
> *any* document that cites RFC 2119 and is published after this one
> must automatically be taken to refer to this one and must follow the
> terms of this one.  So why have the double citation?
>
> You're right, as far as that goes, but if it's important to know for
> sure whether a document is following the terms of RFC xxxx or not (and
> see below about that), then I think it's important to be explicit
> about it.  It's a question of clarity: the reader of another document
> should not have to wonder, should not have to check publication dates,
> should not be uncertain.  Having the citation there explicitly is good
> for clarity.
>
> In fact, we *do* often (though not always) cite update documents when
> we're explicitly talking about a feature that was updated.  I think we
> do it when calling the reader's attention to the update is
> particularly important.

I am afraid I disagree. Either the update system works or it does not. 
If you think
people do not follow through the updates, then we need to always include 
update
list, or we need a system that always gives them the update when they 
request the
base document. So for example someone asking for RFC2119 would find this
automatically but distinctly appended to it.

Ironically in this case the result is no text change to the document 
making the
reference since a MUST is a MUST.

>
> Now, as to the other point:
>
>> I am also somewhat curious about the practical implication of
>> misinterpreting
>> MUST as must, and must as MUST.
>>
>> For example: if A receives a foo packet, it MUST/must reply with a bar
>> packet
>>
>> The interoperability considerations are identical, with but with the
>> advantage
>> that  MUST draws the eye of the reader to  the point and reducing the chance
>> that they will miss it. Similarly with the other keywords. So is there
>> really
>> a problem to be fixed here?
> This did come up in earlier discussion about "MUST".  Sure, it's
> possible that there really isn't a reason to define "MUST" in BCP 14
> because the English meaning is clear enough.  But "SHOULD" and "MAY"
> do need these definitions: the English meanings don't accurately
> convey the BCP 14 meaning.  And even with "MUST", the BCP 14 meaning
> explicitly says that it's a protocol requirement that affects
> interoperability or security, and we do seem to think that making that
> distinction is important.
>
> In any case, the current BCP 14 defines "MUST", and it's specifically
> not a goal of this document to change that older decision.

No, the point is that either type of must is exactly the same 
instruction - "do it or it's broken".

Similarly when should is given it is advisory, and there is no forcing 
how seriously the
individual takes that advice.

So if someone mistakes a MUST for a must, I don't see how the on the 
wire behaviour
can possibly change. Same for the other key words.

- Stewart

>
> Barry


From nobody Tue Feb  7 08:19:20 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A87E129D28 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:19:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable autolearn_force=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 ITlNDart1uS3 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:19:16 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 998B4129D27 for <ietf@ietf.org>; Tue,  7 Feb 2017 08:19:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id ED8C8300425 for <ietf@ietf.org>; Tue,  7 Feb 2017 11:19:15 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id EbVsYZAQx2Tg for <ietf@ietf.org>; Tue,  7 Feb 2017 11:19:14 -0500 (EST)
Received: from [192.168.2.100] (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 5D81D3002C7; Tue,  7 Feb 2017 11:19:14 -0500 (EST)
Subject: Re: Last Call: <draft-bradner-rfc3979bis-10.txt> (Intellectual Property Rights in IETF Technology) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_4E4DF457-7F37-4472-8F8B-588AE8F004CA"; protocol="application/pgp-signature"; micalg=pgp-sha1
X-Pgp-Agent: GPGMail
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <41823891-E490-4A75-B707-114721B40996@piuha.net>
Date: Tue, 7 Feb 2017 11:16:56 -0500
Message-Id: <7F1FD168-3588-4B3C-98D6-4CEE6BE5C430@vigilsec.com>
References: <148474911031.2261.11881119527780959351.idtracker@ietfa.amsl.com> <875519DD-685D-4642-A1D4-0F5D82502E21@piuha.net> <27F46F35-2E43-4BB8-A246-3516DA90A89D@vigilsec.com> <73B2C33B-EC3F-411E-8F2D-959C4996A3D3@piuha.net> <D536B36A-B8A6-4B89-A2CE-7AFB38C6DCE0@vigilsec.com> <41823891-E490-4A75-B707-114721B40996@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5jrO8hvFSJPEDhGhqp4sHgUCJOI>
Cc: draft-bradner-rfc3979bis@ietf.org, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:19:19 -0000

--Apple-Mail=_4E4DF457-7F37-4472-8F8B-588AE8F004CA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I reviewed draft-bradner-rfc3979bis-11, and I have come comments and =
some nits.

Comments =85

In Section 1, definition b, please  update the bullet about deign teams =
to:

	o any WG design teams [see BCP 25] and other design teams that =
intend to deliver an output to the IETF,

In Section 1, definition j, please be more specific in the reference.  I =
think the intention is to reference Section 2.2 of [RFC2026].

In Section 5.5, paragraph D, I suggest a different wording:

      D. Licensing declarations must be made by people with appropriate
          authorization as discussed in Section 5.6 of this document.

In Section 7, please provide pointers for FRAND, RAND, and RAND-z.

In Section 11, please drop =93legal=94 from the first sentence in the =
second paragraph:

   The rules that apply ...


Nits =85

I see =93this memo=94 and =93this document=94.  Either one is fine with =
me, but please pick one and use it throughout.

Section 2: s/IETF and its Participants/IETF and IETF Participants/

Section 5.2.3:  s/IETF area directors/IETF Area Directors/

Section 5.3: s/RFC-Editor/RFC Editor/

Please remove the period at the end of the heading for Section 5.4.2.

Section 5.4.2: s/drafts/Internet-Drafts/

Section 5.4.2, paragraph A:
   s/application (3)/application, (3)/
   s/application ), (4)/application, (4)/

Section 5.4.2, paragraph D:
   s/submit to IETF an update/submit an update/
   s/Secretariat/IETF Secretariat/ (several places)

Section 5.5, paragraph A: s/non- discriminatory/non-discriminatory/

Section 5.6:
   s/IPR that is (a) owned/IPR that (a) is owned/
   s/ or (b) that such persons/; or (b) persons/
   s/ or (c) that such persons/; or (c) persons/
   s/, or (d) in the case of an individual, the individual/; or (d) an =
individual/

Section 6: s/violation of IETF process/violation of the IETF Standards =
Process/

Section 7: s/Working groups and areas may/IETF Areas and IETF working =
groups/

Russ


--Apple-Mail=_4E4DF457-7F37-4472-8F8B-588AE8F004CA
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

iEYEARECAAYFAliZ8xMACgkQiuTu0PWcEcvHqwCfdTl6bnquofPD2agYeOsoGsFQ
LOkAoNAoC6XQ9ZvxwXJJ0wgaKFFGpOsR
=Kzit
-----END PGP SIGNATURE-----

--Apple-Mail=_4E4DF457-7F37-4472-8F8B-588AE8F004CA--


From nobody Tue Feb  7 08:39:21 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEAEA129D71 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:39: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 autolearn_force=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 TXrEf60tuwPj for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 08:39:20 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0C30129D14 for <ietf@ietf.org>; Tue,  7 Feb 2017 08:39:19 -0800 (PST)
Received: (qmail 71416 invoked from network); 7 Feb 2017 16:39:18 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Feb 2017 16:39:18 -0000
Date: 7 Feb 2017 16:38:56 -0000
Message-ID: <20170207163856.9667.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: An observation on draft-leiba-rfc2119-update-01
In-Reply-To: <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SmzgIz9rY5G92B7-s7FfQnk4IEs>
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:39:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In article <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com> you write:
>In fact, we *do* often (though not always) cite update documents when
>we're explicitly talking about a feature that was updated.  I think we
>do it when calling the reader's attention to the update is
>particularly important.

Agreed, since this update is not backward compatible.  It would have
been a lot cleaner to replace 2119 with, say, 8119, but I can see why
you didn't want to open that particular institutional size can of
worms.

> even with "MUST", the BCP 14 meaning
>explicitly says that it's a protocol requirement that affects
>interoperability or security, and we do seem to think that making that
>distinction is important.

That is surprisingly unclear to a lot of people, particularly ones not
deeply embedded in the IETF.  We know that MUST means "do this if you
want to interoperate" but I know people who imagine it means "do this
or else."

R's,
John
-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQSVwJVU9sGa3lHFnZyQSIVF14L+RQUCWJn4MwAKCRCQSIVF14L+
RaGVAKClNRLd3etWBc66VVYpcrBf0AEzYgCgiKewpNuqVcXB0fn9J8DWc49c1c0=
=O3f4
-----END PGP SIGNATURE-----


From nobody Tue Feb  7 09:05:06 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24488129D78; Tue,  7 Feb 2017 09:05:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level: 
X-Spam-Status: No, score=-7.02 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Klejm2yJ325S; Tue,  7 Feb 2017 09:04:59 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E683129444; Tue,  7 Feb 2017 09:04:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486487099; x=1518023099; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=Vt5NGl4TxA7moqo/JKPQ2JXWcVIJ5FKzbBDjVw22ssk=; b=skMgGY9Pzt0H6f1zNqzuJOmWoaeFlUNf3uoomyWxyVtpTb7q9Loi+BDc NIrS7i2Fd4tvi4q6MHXAGh0fPsk9K6grUq0OvjxLU1O0YSh3rnlAWLYA+ KyaNBTVzR+4ZfqYVqgH2g6u0r1ta+L1Zy54C8A8c5pm0uY8XakHa2uqN3 Q=;
X-IronPort-AV: E=Sophos;i="5.33,346,1477983600";  d="scan'208,217";a="356310173"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine02.qualcomm.com with ESMTP; 07 Feb 2017 09:04:59 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8432"; a="1304809432"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Feb 2017 09:04:58 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 09:04:57 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Date: Tue, 7 Feb 2017 11:04:56 -0600
Message-ID: <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_="
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01B.na.qualcomm.com (10.85.0.82) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oRu1Qv3qC-A9j-2oBgoFqm7Wf1c>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 17:05:01 -0000

--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit

Hi Daniele,

Thanks for addressing everything. There's only one issue left in section 
4.1.1 on Priority, below. I've trimmed out all the rest.

On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:

>> I get that part ("At least one priority level MUST be advertised"). 
>> It's the end I don't understand: "that, unless overridden by local 
>> policy, SHALL be at priority level 0." What does that mean?
>
> [DC] It means that if only one priority is supported it has to be 
> priority 0.

So, let me see if I have this right: It's OK to have 01100000 but not 
01000000 or 00100000? If so, why is that?

> For any particular administrative purpose it could be possible to set 
> it to a different value, but that shouldn’t be done.

Well, it doesn't say that shouldn't be done, but it probably doesn't 
need to say anything about local configurations.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Hi Daniele,</p>

<p dir=3D"auto">Thanks for addressing everything. There's only one issue =
left in section 4.1.1 on Priority, below. I've trimmed out all the rest.<=
/p>

<p dir=3D"auto">On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">I get that part ("At least one priority level MUST be adv=
ertised"). It's the end I don't understand: "that, unless overridden by l=
ocal policy, SHALL be at priority level 0." What does that mean?</p>
</blockquote>

<p dir=3D"auto">[DC] It means that if only one priority is supported it h=
as to be priority 0.</p>
</blockquote>

<p dir=3D"auto">So, let me see if I have this right: It's OK to have 0110=
0000 but not 01000000 or 00100000? If so, why is that?</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">For any particular administrative purpose it could be pos=
sible to set it to a different value, but that shouldn=E2=80=99t be done.=
</p>
</blockquote>

<p dir=3D"auto">Well, it doesn't say that shouldn't be done, but it proba=
bly doesn't need to say anything about local configurations.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_71FDF75B-5D69-4EFD-BBD0-0A04EEBA38D2_=--


From nobody Tue Feb  7 10:13:22 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B390B129DCA; Tue,  7 Feb 2017 10:13:20 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-pals-mpls-tp-dual-homing-protection-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
Date: Tue, 07 Feb 2017 10:13:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gv3fLx0F0LmqQghwgb3-4fuOL7Y>
Cc: draft-ietf-pals-mpls-tp-dual-homing-protection.all@ietf.org, ietf@ietf.org, pals@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 18:13:21 -0000

Reviewer: Russ Housley
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-protection-05
Reviewer: Russ Housley
Review Date: 2017-02-07
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary: Ready

Major Concerns:  None

Minor Concerns:  None

Nits:

In the last sentence of the first paragraph of Section 1, the
document
says: "This mechanism is only applicable ..."  I believe that this is
a reference to the repair mechanism that is defined in
[I-D.ietf-pals-endpoint-fast-protection], not the mechanism that is
defined in this document.  Please replace "This mechanism" with a
clear reference.

Notes:

I see that draft-cheng-pwe3-mpls-tp-dual-homing-protection the
earlier
Internet-Draft file name for this document.  An IPR declaration was
issued against that earlier name.  The shepherd write-up indicates
that
"The WG were not concerned about the IPR disclosure." However, it is
unclear to me whether we should ask for the IPR declaration to be
issued
against the current Internet-Draft file name.


From nobody Tue Feb  7 10:26:25 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E242129480; Tue,  7 Feb 2017 10:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VtyVZrQkRt8G; Tue,  7 Feb 2017 10:26:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 419951293D8; Tue,  7 Feb 2017 10:26:15 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17IPW9J027257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 10:25:32 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org, "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu>
Date: Tue, 7 Feb 2017 10:25:33 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4IpfDTzwxr7dSx0snQI4I4a6bCc>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 18:26:16 -0000

On 2/4/2017 10:40 AM, otroan@employees.org wrote:
> Lars,
>
>>> My apologies: my comments were probably misleading. Certainly, this
>>> document is simply RFC1981 to Std, and hence recommending RFC4821 would
>>> be kind of ou of scope, here.
>>>
>>> That say, one might wonder to what extent, and for the general Internet,
>>> RFC1981 can be considered succesful (given the filtering of ICMP
>>> messages). -- i.e., at this point in time you wouldn't rely on RFC1981
>>> (icmp-based pmtud) for path-mtu discovery.
>> What Fernando said: I'm certainly not opposed to lifting this to Standard, but it is painting an incorrect picture - PLPMTUD is de facto mandatory these days, and has been for years.
> While I'm all in favour of PLMTUD. It doesn't seem like a complete solution.
> PMTUD on the other hand supports all protocols on top of IP.
If by "supports" you mean "doesn't work", then yes. That's why we now
have PLPMTUD.

> Looking just at our specifications, we cannot state that PLMTUD can replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2

(yes, that doc has expired while we're preparing the 04 update, which
should be issued shortly)

Joe


From nobody Tue Feb  7 11:08:45 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88C0F1295B0; Tue,  7 Feb 2017 11:08:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 sk8-2nGlNhnn; Tue,  7 Feb 2017 11:08:43 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 2F910120725; Tue,  7 Feb 2017 11:08:43 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17J7eaG003111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:07:42 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, "tom p." <daedulus@btconnect.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <b07dcffe-107a-a777-2d03-57931088d842@isi.edu>
Date: Tue, 7 Feb 2017 11:07:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org>
Content-Type: multipart/alternative; boundary="------------CDF5BCBCF48D19481D6FACD2"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/clC9k6WmBap6TnWR8N8ziS88pD8>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:08:44 -0000

This is a multi-part message in MIME format.
--------------CDF5BCBCF48D19481D6FACD2
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Hi, all,

Can anyone give those of us not tracking 672 messages a brief summary?

IMO, without diving into that thread deeply, I agree with the new
proposed text below from Brian:

>    With one exception, extension headers are not processed, inserted,
>    deleted or modified by any node along a packet's delivery path, until
>    the packet reaches the node (or each of the set of nodes, in the case
>    of multicast) identified in the Destination Address field of the IPv6
>    header.
In fact, I'd go further to say that that non-HBH EHs should not even be
*viewed* or used as context by intermediate nodes.

And any limits on what can be done with HBH EHs should be stated
explicitly. I'd be glad if at least the EH lengths didn't change.

Joe


On 2/3/2017 10:22 AM, otroan@employees.org wrote:
>> are we re-spinning the debate on a WG-agreed text ?
>>
>> <tp>
>>
>> Yes, and I am sure that that is exactly what is intended.
> Then let's encourage people outside of 6man, with other points of view, and other arguments to come forward.
>
> A re-run of the discussions already had in 6man with the same arguments and the same participants doesn't seem useful.
>
> For a brief (sic) overview take a look at 672 messages already on the topic:
> https://mailarchive.ietf.org/arch/search/?q=header+insertion&f_list=ipv6


--------------CDF5BCBCF48D19481D6FACD2
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, all,</p>
    <p>Can anyone give those of us not tracking 672 messages a brief
      summary?<br>
    </p>
    <p>IMO, without diving into that thread deeply, I agree with the new
      proposed text below from Brian:</p>
    <p>
      <blockquote type="cite">
        <pre wrap="">   With one exception, extension headers are not processed, inserted,
   deleted or modified by any node along a packet's delivery path, until
   the packet reaches the node (or each of the set of nodes, in the case
   of multicast) identified in the Destination Address field of the IPv6
   header.</pre>
      </blockquote>
      In fact, I'd go further to say that that non-HBH EHs should not
      even be *viewed* or used as context by intermediate nodes.</p>
    <p>And any limits on what can be done with HBH EHs should be stated
      explicitly. I'd be glad if at least the EH lengths didn't change.<br>
    </p>
    <p>Joe<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/3/2017 10:22 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
    </div>
    <blockquote
      cite="mid:60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">are we re-spinning the debate on a WG-agreed text ?

&lt;tp&gt;

Yes, and I am sure that that is exactly what is intended.
</pre>
      </blockquote>
      <pre wrap="">Then let's encourage people outside of 6man, with other points of view, and other arguments to come forward.

A re-run of the discussions already had in 6man with the same arguments and the same participants doesn't seem useful.

For a brief (sic) overview take a look at 672 messages already on the topic:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/search/?q=header+insertion&amp;f_list=ipv6">https://mailarchive.ietf.org/arch/search/?q=header+insertion&amp;f_list=ipv6</a></pre>
    </blockquote>
    <br>
  </body>
</html>

--------------CDF5BCBCF48D19481D6FACD2--


From nobody Tue Feb  7 11:13:37 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08569129E12; Tue,  7 Feb 2017 11:13:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 P1CqfhwdCEpc; Tue,  7 Feb 2017 11:13:35 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 4A4091295BC; Tue,  7 Feb 2017 11:13:35 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17JCxBq003843 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:13:00 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: John Leslie <john@jlc.net>, "tom p." <daedulus@btconnect.com>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net> <20170204223848.GL10525@verdi>
From: Joe Touch <touch@isi.edu>
Message-ID: <fdc025ec-bb9c-3e41-58e1-0609f46abbb9@isi.edu>
Date: Tue, 7 Feb 2017 11:13:00 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170204223848.GL10525@verdi>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V-u5_P9bTygDvaOv9RJ9SFeke4o>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:13:36 -0000

On 2/4/2017 2:38 PM, John Leslie wrote:
>    (One particularly silly flaw is that we allow _most_ nodes to
> have a hard limit of 1500 bytes per packet: requiring IPv6 nodes to
> handle packets ten times that limit would help a lot!)

Given we have no way to signal that an *endpoint* can do better, what's
the point?

Joe


From nobody Tue Feb  7 11:15:10 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE711295BF for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:15:09 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UFOETv29SqGD for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:15:08 -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 1F0F41295B6 for <ietf@ietf.org>; Tue,  7 Feb 2017 11:15:08 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id y143so35253764pfb.0 for <ietf@ietf.org>; Tue, 07 Feb 2017 11:15:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=8GgIlQ3F+bf9HVi1ckxSJLaPOw5bSm3wU6DJFR1XlGk=; b=Bf3XfRzgn0rKAiSKWlWL+XHo1jMc72QG6vCb2hxmJ/aQaSSK/8kZc2BBIHBQJmoXyc Ilj3BVPWCrE9F0jEG5KPA2eJVKOsu9LDub+euX+3OeLN+wVcwElNGcN9f5m3T7wQsXyY KUKJXUGHwuTuwF1onsliwUvlZyR9wRBOr6RdlF2f+Hpxe7h6D0s3rnmjZjAO6Ctc1oh/ KoVaiJk3FRb7nSVA7pFHDaexLSxEUZI+/D/oAApPKS8lyieb50XMyo/Hbs+lYE2SBvL6 DLMvjpXU27e/ZZq1YoMWVN0rR3DlrspU65jH6oM9iRy8TxZMj4VGmZ4U3C7lRHoyIfP7 gEUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=8GgIlQ3F+bf9HVi1ckxSJLaPOw5bSm3wU6DJFR1XlGk=; b=grroTXhtChr0nhnLgWa7dLYFook+VAf84MaGnXI+vPn+WE3nN/ZdslORB4gz+S1kSW smsPTfk8YxmGSodFqkFHIaT+3cqCJcNSYbTVkRp2EJYt5IHqJckm1OPGJoy49USFDuQ8 ku/S5xltJ8pkIyIsCdLEO0lMTiRrZuFnSLUUVv/MvR4iPJviI3Sktw0zOmr/2DTI+hrk Hv1wB+4QEyPlhwEVt9avRtv3FJUOaP+IQp81XUdXU0fAsPw00wF9Bqt+aUHRCUG2CsD9 P8tmJJPl74b15KKzAOs6qSzDdPdEBhf7oNIWFxArWFWzgCC5HVpFnjRJehF6n2/TzQgi bxYw==
X-Gm-Message-State: AIkVDXLgjLOyoAu05J9X4XH3DUfr6LneYySpRfHyxn0e77SmcidI7A3qlMK3AFYYYNbxgQ==
X-Received: by 10.99.167.10 with SMTP id d10mr22207558pgf.19.1486494907758; Tue, 07 Feb 2017 11:15:07 -0800 (PST)
Received: from [192.168.178.21] ([118.148.124.205]) by smtp.gmail.com with ESMTPSA id z74sm13407944pfd.70.2017.02.07.11.15.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 11:15:07 -0800 (PST)
Subject: Re: An observation on draft-leiba-rfc2119-update-01
To: Barry Leiba <barryleiba@computer.org>, Stewart Bryant <stewart.bryant@gmail.com>
References: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com> <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3a2f751d-aeb2-2705-9b27-bf95558eb835@gmail.com>
Date: Wed, 8 Feb 2017 08:15:06 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oKfgRUhqkqpcnuyt0FBjb2v5jcs>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:15:09 -0000

On 08/02/2017 04:45, Barry Leiba wrote:
> Hi, Stewart.
> 
>> The above text raises an interesting problem. If the update system works
>> then
>> the text should read [RFC2119]. If the update system does not work than
>> the text needs to be [RFC2119],[RFCxxxx] as shown, but we also need to move
>> to a system where we always list the update set at the time of publication,
> 
> It took me a while to get what you mean here, but I think I have it:
> you're saying that because this document (RFC xxxx) UPDATES RFC 2119,
> *any* document that cites RFC 2119 and is published after this one
> must automatically be taken to refer to this one and must follow the
> terms of this one. 

Huh? If a document refers to RFC2119, it refers to 2119. That might be
a bug in the document, but I don't think we've ever said that updates
propagate by magic in that way. (We have said that the current system
is broken, because implementers have to follow a daisy chain to find out
the latest versions of everything, but that's a different problem.)

Recommending that future documents cite [BCP14] would simplify life.
The RFC Editor knows how to handle that.

   Brian


From nobody Tue Feb  7 11:20:42 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F9D61295A0; Tue,  7 Feb 2017 11:20:33 -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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MG6WYa_oQfI9; Tue,  7 Feb 2017 11:20:32 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id CA2C6129461; Tue,  7 Feb 2017 11:20:31 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 07 Feb 2017 19:20:31 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 115CCD788B; Tue,  7 Feb 2017 11:20:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=Ul8b8AlinbEJb/sx2BP5BdhvN1A=; b= kGRNfq7EeTTCOlITv1IiCUjMXj4Q7uai4bKUj2oendjSgY2N4CBQOfP9cXNe/eFx QWHj+5RyIrmZ/AhshqLfw6W8C/2hcdkb+5mzAOZOjuFkJNSxa4UoFeHJxS2hIofY lZKBfCxweJj1p/9fr0O1vyVqJjlTzqGyM0NPjfim7r4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=pdFNFoCFLwj1ADaakUyWe1o /8YeR8NABkKyN7+Ohv3cleaMwZfVHopLhMZSmv2pW2D8EGFCRZzvbcojXbqGrWU/ rlJU8ngm+KRADEOfmJTgPKG98lKA+EdHT7DFEISL5aK3dH9R3V6cgdSN1sQd8wNI 1f84XS0HL51t6v3p9N1M=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 986F3D788E; Tue,  7 Feb 2017 11:20:30 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 68C47865E62B; Tue,  7 Feb 2017 20:20:27 +0100 (CET)
From: otroan@employees.org
Message-Id: <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_80CF1CA3-844D-451D-8AC2-B679B5C2B9DA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Tue, 7 Feb 2017 20:20:26 +0100
In-Reply-To: <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu>
To: Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rgKZP5kPxG12ZiCj9y7QVyegZaQ>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:20:33 -0000

--Apple-Mail=_80CF1CA3-844D-451D-8AC2-B679B5C2B9DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joe,

>>>> My apologies: my comments were probably misleading. Certainly, this
>>>> document is simply RFC1981 to Std, and hence recommending RFC4821 =
would
>>>> be kind of ou of scope, here.
>>>>=20
>>>> That say, one might wonder to what extent, and for the general =
Internet,
>>>> RFC1981 can be considered succesful (given the filtering of ICMP
>>>> messages). -- i.e., at this point in time you wouldn't rely on =
RFC1981
>>>> (icmp-based pmtud) for path-mtu discovery.
>>> What Fernando said: I'm certainly not opposed to lifting this to =
Standard, but it is painting an incorrect picture - PLPMTUD is de facto =
mandatory these days, and has been for years.
>> While I'm all in favour of PLMTUD. It doesn't seem like a complete =
solution.
>> PMTUD on the other hand supports all protocols on top of IP.
> If by "supports" you mean "doesn't work", then yes. That's why we now
> have PLPMTUD.

PLMTUD is unfortunately not a (complete) replacement of PMTUD.

>> Looking just at our specifications, we cannot state that PLMTUD can =
replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
>=20
> (yes, that doc has expired while we're preparing the 04 update, which
> should be issued shortly)

Is this the paragraph you are referring to?

   PLPMTUD requires a separate,
   direct control channel from the egress to the ingress that provides
   positive feedback; the direct channel is not blocked by policy
   filters and the positive feedback ensures fail-safe operation if
   feedback messages are lost [RFC4821].

I'm very much in favour of working on better ways of doing Path MTU =
discovery.
A blanket statement of "use "PLMTUD" seems very premature though.

RFC1981 has 70 citations:
http://www.arkko.com/tools/allstats/citations-rfc1981.html

Could you expand on your view of how this pertains to advancing RFC1981?

Best regards,
Ole

--Apple-Mail=_80CF1CA3-844D-451D-8AC2-B679B5C2B9DA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmh37AAoJEL7aWKiYQt92ZSUQAKYRtwt9j3ovfkplaMKzAcud
HZmDJ+Yb9t/empELhf1rGNoQve5aOA9p58ICUITqeGnsSYZtPDFfIjZG50WZTBt0
qcdDmQ7wejiVVjeB/7Gf7lFGB45gdcpWpyDt2mCV0wD8B3D8vvTsYIxpSyuip6kA
fjRjG7ZDtfPYkBfrPljA5Xe9laqzFJs9aoyj9xOn9qvv7WzMitn7D9nmQCynP486
4gEMMeb+C2CosT4m3HTSXMFB2jnmoN29Nee/MaQYSpUKYzkbdaGdvbUwu3HQIUKg
+6Y/tDZm0Z6uFXrrEdFedMQ9I3PWe/uVB5GPkYyJU69X7UoMX08RJNkNKyLzkhIP
MJmywfijlfkPace9WhWTFbFc4VWdTHOxe1CsI5jHsyPWPq2RAnwh2iRoSzPSbsp6
5UQUGcpr31br7T48fpHygGYlwC0QH08apexsvkLEzSJBxwvFXsu+UqIA3IlHL3PS
XB6dz/Z0m6UdDtpaRvY7hiGcU5JNsBS8GgPsybHLSm5AZthCcr089OdSrZ2gRRZP
EUdVFsqQzojKrZye2FW28F7YSQfwNSgfBWTrscNPavN5n6jC65jkebIRIKBLhC/K
yLLyo2CeiWr3GpUhLjPzoysYU78pg1LvojRlyTgnJ7eYS/gsQw3y0bJeEJnqKl4B
GXBNdz6tI+Yhok2NyMeq
=wuwT
-----END PGP SIGNATURE-----

--Apple-Mail=_80CF1CA3-844D-451D-8AC2-B679B5C2B9DA--


From nobody Tue Feb  7 11:23:44 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD280129E25 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:23:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u4qxUtQtjPTd for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:23:41 -0800 (PST)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 891FC129E1D for <ietf@ietf.org>; Tue,  7 Feb 2017 11:23:41 -0800 (PST)
Received: by mail-qk0-x234.google.com with SMTP id u25so98650693qki.2 for <ietf@ietf.org>; Tue, 07 Feb 2017 11:23:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lkXK9z6HBA/dhx/+2mxH0nCemU3Eiv4Pv8biqKSbNsE=; b=m8C2LSEDSGavowPk8/aAbJSDJQaDF08+kFrqKdttk48UQH4wMGdod2lFHAn9FmJfxP W905H0M0J2ojl2kpkKeY30mllRxRJVuP/0mIqbv995SiiQAXy5LXOpLVWdquNhqbvRB4 iHeOw42vmZbc4uJj+SS3o1Wf6qgdv8jdL/8TYMtQG5mv6fcvsS1ahGLgghICcHX4SjXL 2reP3QYjw5n2jzSHiHeV1xLOum3h152eMSrfbZcCj5aAik1Q/kFxTjFR4alykwNGl7r0 D//aGe4Is+SE8lvREpjN1LpTsbIJ2701tpQ4682hOviSbNjGnPVra+9AF1goUgxGLX7g wejQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lkXK9z6HBA/dhx/+2mxH0nCemU3Eiv4Pv8biqKSbNsE=; b=iWrETP8CYvQZwMqHEaYI6f2Y1ADHakRsN6MqZwhH7U2yGTlOHG5Funsz/d6Abeko+Q k7Oih4hm9WRNgTyc2Pc919R/2raNBaZQgwlKywFXfWyZZ7zQky++OT/kE96+2IhjAsW5 L8EifGQM6TQx/ID+PGNvnP9g8UfPC1nBHyVjZNkcawMK2b4hvcB+BVIyza+v5E74rtWS 8rFKGMICgCc7IkXgTNJYJBPEDbbFWaL5fa853Zkg8nzIGyty8YJ5Ubb+4kgjhDzAnnaj 13qgoKeO9ho3VhRnEcU21+YFUn6EHHFbmiSktQ5opJ0u7DSGypnxQSPbo4M0Tw+msGM0 /x3g==
X-Gm-Message-State: AMke39mU59Fip5PxSFIAPrswIev8Wn8j81iAyu1Mve/w21AFxcFmbufEQhA9HsdoI2I4Eo//WMSN0KP/KF8DFg==
X-Received: by 10.55.181.6 with SMTP id e6mr15247566qkf.298.1486495420702; Tue, 07 Feb 2017 11:23:40 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.140.19.72 with HTTP; Tue, 7 Feb 2017 11:23:40 -0800 (PST)
In-Reply-To: <3a2f751d-aeb2-2705-9b27-bf95558eb835@gmail.com>
References: <d55a5027-b01a-8891-5e6e-4c519b5b9801@gmail.com> <CALaySJL-kfjQO=P3aVWwu6zEz6y5k7bngqEf0eqShWjAKAZ7Ug@mail.gmail.com> <3a2f751d-aeb2-2705-9b27-bf95558eb835@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 7 Feb 2017 11:23:40 -0800
X-Google-Sender-Auth: PFoXICKzdrPwLyDXrCZnBreuoFk
Message-ID: <CALaySJJCN5o-U+CBYc0nVXiMVTHCdhy5GPJmpD7y_KPKPTTj1w@mail.gmail.com>
Subject: Re: An observation on draft-leiba-rfc2119-update-01
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/43fkPhbgt1XEBNiJhW6MdFBv5M0>
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:23:43 -0000

> Recommending that future documents cite [BCP14] would simplify life.
> The RFC Editor knows how to handle that.

I thought about that, but then there's the "publication date" problem
again: you'd have to look at what BCP 14 was at the time the document
you're reading was published.  That's why I've suggested using "BCP
14" in the text, but explicitly citing the two RFCs.  Looking for
strong clarity.

Of course, one could argue that the BCP 14 boilerplate text makes it
clear enough, so....

Barry


From nobody Tue Feb  7 11:30:49 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57E0129E4C for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id njNLe_lstUUP for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 11:30:46 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::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 307B8129E47 for <ietf@ietf.org>; Tue,  7 Feb 2017 11:30:46 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id v186so25299825wmd.0 for <ietf@ietf.org>; Tue, 07 Feb 2017 11:30:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=ziUKuQ9Tuy2W1y6QM0eLlJacG7O0Q4gdP3yqPleCcTw=; b=K2eBz9nZrD4FWBSkCazqGx6vaSP3xCbmG/wm6DCzlBqL2m3vxyNQ/I/8nFPpNz5CmL NZ6zsRBAkKB7GX1xH+ZAAwwkLSpPB6IdLYu2UKEi+uJjovMMKaNUnBFu7lB824E1TtOk hVQW8ilwVH5nhkL3HI6GBIjPF6kEBlJxnMW+wjSDhZi4bjG5NfcARkFU5hyJmRoqTcbN 1bKouiAFBRRP5PZVVSfu4A3Yz/Tt5LHR3bgw2S3fJOnZ/6mbxKpmL8W+rdejs+JsgJPg k3ZyJK6WumMh0SH5pXwddBtgUFFu+VsBYpSrwvhGgGrfz7KL9M8V+p2IN/L3lkvTm5OQ nB0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=ziUKuQ9Tuy2W1y6QM0eLlJacG7O0Q4gdP3yqPleCcTw=; b=WT7WrK6KR/+hP55DbjDEigiOlULsau72L1LdA0fXcPM8tZg/HcufF0rJLCbyn+Ahql mKhGKnW/Xf46kTyWyfEuKX2suREpff+rUy5jxcUHWwFPPLT74iyhyUyj9uWFvBNqqg5b 4rVBfmWTCPUI47lrQk/yqbpcE0y/oHonIz6ioZyf/SiQhxD45ykgA5gPbArUDCL07sIo DxLTZlvsMt8C9/HdvlidNP7gM0zsZmQ5a7QnsU3TGf+3iCiO1l+LUtxzfG/ezJZwnOmr 1rJiLqi8i97RoLN4y1LI6xcm2LeXWH/ZnC6tNjB9ll+ptMy9iBuzNcji1eatxeznQNO/ EzAA==
X-Gm-Message-State: AIkVDXLyhigWKmYT8ORaNdHNBSKhW8CZNKJ6bqN656SP0rPb8NcpCdQp13ORBBBA8QuUiCPurGsFc8AxBQEbYA==
X-Received: by 10.223.146.39 with SMTP id 36mr15768123wrj.85.1486495844523; Tue, 07 Feb 2017 11:30:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.142.108 with HTTP; Tue, 7 Feb 2017 11:30:44 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Tue, 7 Feb 2017 14:30:44 -0500
Message-ID: <CAG4d1re-o2jBJQhs+C51Xw-T1yV7UmQY86wrq0THikm6WDgQ1A@mail.gmail.com>
Subject: tools forum idea for IETF 98
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0d29b4c5e7b20547f5c8be
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9poeAK-eb8rsOTixfr014HNe7_U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:30:48 -0000

--94eb2c0d29b4c5e7b20547f5c8be
Content-Type: text/plain; charset=UTF-8

There have been some discussions about having a meeting at IETF 98 to
discuss existing experimental tools and encourage discussion among those
working on tools to handle specific issues.  The basic meeting description
is

Tools are a critical mechanism through which IETF work can be done with
less effort.  Some IETF tools (e.g. datatracker, xml2rfc, etc.) are at a
high level of maturity and deployment.  Many other tools have either not
yet reached a maturity suitable for wide-spread use or struggle to spread
knowledge of their existence and use.   Still other potential tools are
merely partially brainstormed ideas looking for others motivated to
discuss, implement and try.  This meeting provides a mechanism to spread
knowledge of experimental tools to those interested and get feedback on
those tools.  It also provides time and focus for finding others interested
in particular tool ideas and discussing how to progress them.   It should
be augmented before IETF 98 with a wiki of experimental tool pointers and
tool ideas.


              Agenda:  30 minutes of new tools lightning talks
                            60 minutes of small group discussion on
different tool areas

If you would be interested in doing a lightning talk for a tool which
hasn't gained IETF-wide use, please let us know in the next week.

If you would be interested in facilitating discussion for a particular tool
area, please let us know in the next week.  If you are interested in
suggesting a tool area for discussion and want to be involved in that,
please let us know.

Once we understand what the interest level is in active participation, then
we can figure out how is best to organize this.

Thanks,
Alia Atlas & Robert Sparks

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

<div dir=3D"ltr"><div style=3D"font-size:12.8px">There have been some discu=
ssions about having a meeting at IETF 98 to discuss existing experimental t=
ools and encourage discussion among those working on tools to handle specif=
ic issues.=C2=A0 The basic meeting description is=C2=A0</div><div style=3D"=
font-size:12.8px"><br></div><blockquote style=3D"font-size:12.8px;margin:0p=
x 0px 0px 40px;border:none;padding:0px"><div style=3D"font-size:12.8px">Too=
ls are a critical mechanism through which IETF work can be done with less e=
ffort.=C2=A0 Some IETF tools (e.g. datatracker, xml2rfc, etc.) are at a hig=
h level of maturity and deployment.=C2=A0 Many other tools have either not =
yet reached a maturity suitable for wide-spread use or struggle to spread k=
nowledge of their existence and use. =C2=A0 Still other potential tools are=
 merely partially brainstormed ideas looking for others motivated to discus=
s, implement and try.=C2=A0 This meeting provides a mechanism to spread kno=
wledge of experimental tools to those interested and get feedback on those =
tools.=C2=A0 It also provides time and focus for finding others interested =
in particular tool ideas and discussing how to progress them. =C2=A0 It sho=
uld be augmented before IETF 98 with a wiki of experimental tool pointers a=
nd tool ideas.</div></blockquote><div style=3D"font-size:12.8px"><br></div>=
<div style=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Agenda: =C2=A030 minutes of new tools lightning talks</div><div styl=
e=3D"font-size:12.8px">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 60 minutes of small group dis=
cussion on different tool areas</div><div style=3D"font-size:12.8px"><br></=
div><div style=3D"font-size:12.8px">If you would be interested in doing a l=
ightning talk for a tool which hasn&#39;t gained IETF-wide use, please let =
us know in the next week.</div><div style=3D"font-size:12.8px"><br></div><d=
iv style=3D"font-size:12.8px">If you would be interested in facilitating di=
scussion for a particular tool area, please let us know in the next week.=
=C2=A0 If you are interested in suggesting a tool area for discussion and w=
ant to be involved in that, please let us know.</div><div style=3D"font-siz=
e:12.8px"><br></div><div style=3D"font-size:12.8px">Once we understand what=
 the interest level is in active participation, then we can figure out how =
is best to organize this.</div><div style=3D"font-size:12.8px"><br></div><d=
iv style=3D"font-size:12.8px">Thanks,</div><div style=3D"font-size:12.8px">=
Alia Atlas &amp; Robert Sparks</div></div>

--94eb2c0d29b4c5e7b20547f5c8be--


From nobody Tue Feb  7 11:31:25 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21395129E50; Tue,  7 Feb 2017 11:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 jhz67DDJejaf; Tue,  7 Feb 2017 11:31:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 745C9129E47; Tue,  7 Feb 2017 11:31:22 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17JV2E2006947 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:31:03 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: "tom p." <daedulus@btconnect.com>, otroan@employees.org, Pete Resnick <presnick@qti.qualcomm.com>
References: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <49e46b3e-1f23-4465-2528-4057da21cead@isi.edu>
Date: Tue, 7 Feb 2017 11:31:03 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <01c901d27ee6$754994a0$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ER116Fx4L8ikTP2F7m3P0p6aoYc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:31:24 -0000

Hi, all,

I suppose I'm in the group below.

IMO:

    - the IPv6 base header and HBH EHs are the only ones that
intermediate nodes should even *look* at

    - everything else should be prohibited

    - there's little point in talking about middlebox behavior at all
until we have compliance verification in place

One other observation:

    - frag processing doesn't say what to do with an exact overlap that
isn't a exact duplicate (e.g., when the content differs). AFAICT, that
should be treated the same as an overlapping fragment - i.e., only
*exact* duplicates should be (optional, as already noted) silent
discards (but this does then create a potential DOS vector because of
the additional processing for dup frags - and that should be noted).

AFAICT, the only way a "middlebox" can legitimately get away doing more
than above is when it can claim it is doing so on behalf of an endpoint,
i.e., to claim that the endpoint services are distributed upstream. IMO,
that argument is OK for devices under the same control as the endpoint,
but not otherwise. However, that's all just a philosophical argument
without compliance verification anyway.

Joe

On 2/4/2017 4:48 AM, tom p. wrote:
> I do not know how to make it happen but I would like to see considered
> opinions on this rather important issue from those I see active on lists
> such as tcpm, arch-d and intarea whom I do not see active on v6(ops).
>
> Tom Petch
>
>
> ----- Original Message -----
> From: <otroan@employees.org>
> To: "Pete Resnick" <presnick@qti.qualcomm.com>
> Cc: "tom p." <daedulus@btconnect.com>; <6man-chairs@ietf.org>;
> <draft-ietf-6man-rfc2460bis@tools.ietf.org>; "Stefano Previdi"
> <sprevidi@cisco.com>; <ietf@ietf.org>
> Sent: Saturday, February 04, 2017 8:32 AM
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
> Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
>
> Thank you Pete! You are of course right.
>
> Let me try to provide some background of the issue.
>
> The contentious text is the following paragraph from 2460:
>
>   With one exception, extension headers are not examined or processed
>   by any node along a packet's delivery path, until the packet reaches
>   the node (or each of the set of nodes, in the case of multicast)
>   identified in the Destination Address field of the IPv6 header.
>
> Essentially the question is:
> - Does the IPv6 architecture permit insertion of extension headers
> and/or header options by a node along the packet's delivery path?
>
> This question came up triggered by discussions around some recent
> proposals:
> - draft-ietf-conex-destopt,
> - RFC4782 (does header deletion)
> - draft-ietf-6man-segment-routing-header
> - draft-brockners-inband-oam-transport
>
> The IP architecture (IPv4 and IPv6) supports _modifying_ IP options in
> flight, but it is unclear if it could permit changing the IP datagram's
> size.
> Increasing a packets size in flight would break PMTUD (RFC1981), AH, and
> might results in other ICMP error messages being sent to an unsuspecting
> source.
>
> There were three main positions argued in the working group.
>
> 1) Ban header insertion outright.
> 2) Describe the problems with header insertion.
> 3) No changes to RFC2460 text.
>
> Permitting header insertion in the sense of specifying how header
> insertion could possibly work is of course outside the scope of
> advancing RFC2460.
>
> The chairs tried various approaches to find a consensus without luck.
> The approach finally chosen was a poll between the three options. And
> the (rough) consensus was based on the data from the poll.
>
> Excerpt from the shepherds writeup:
>
> A working group last call for moving this and the other two documents to
> Internet Standard was started on 30 May 2016. Reviews were also
> requested. Issues found during the last call and reviews were entered
> into the 6MAN ticket system. These are now closed. The biggest issue
> raised was how to handle the issue of Extension Header insertion in this
> document. After many discussion on the mailing list and face to face
> meeting, there wasn’t a clear consensus. The chairs conducted an online
> survey that provided three choices: Ban header insertion, describe the
> problems with header insertion, or say nothing. The result of the survey
> was to describe the solution. The results and methodology used to
> evaluate the results can be seen at:
> https://mailarchive.ietf.org/arch/msg/ipv6/_gG2foiugk5B7w3TpnPvBbjHDzs
> This was discussed at the 6MAN session at IETF97 and on the mailing list
> after the meeting. The chairs believe there is a consensus to go forward
> with the text that is in draft-ietf-6man-rfc2460bis-08.
>
> The summary given to the working group calling for the poll:
> https://mailarchive.ietf.org/arch/msg/ipv6/AtY92TpJ3vvmiidzcPkJdXKZQIA/?
> qid=84de5e109c8f8f255d03c4c98ff3e50c
>
> Best regards,
> Ole, 6man co-chair
>


From nobody Tue Feb  7 11:38:21 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F157A129599; Tue,  7 Feb 2017 11:38: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9NMPxtO1urB; Tue,  7 Feb 2017 11:38:18 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 6C20C129449; Tue,  7 Feb 2017 11:38:18 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 07 Feb 2017 19:38:18 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 1D77CD788A; Tue,  7 Feb 2017 11:38:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=l5OX5FOYlEpBPplGmr1OiT94SZ8=; b= f1DYK3szmkV0XtgiyFoxJYODZZQ2DA4amMXAr98PQf1NeIATjerfAPHrCoGpzjA+ WaIM0oG7r9aMiJwUVK1CPsG0ZN1B9LKXLSiyfK3wG8CC/ZcvSqEywdbrAqK9D2YG 4iwA9fzz/I6Rh0k4Ya3vBAGoNVWDWMldt/+w4plLUR4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=f/M8GPch23xgTeddMsNE4LV nW85WKN78w9Pnxr49IcgFgMmPZMrlevV5VtmnP7NnmzMbsUfR4d3kqbbEJgkqISd ZstqeO0xJyLVFiHqru9jMXMtX6UoEtUUitgtF81kAui/cvXO02bV8DnCclGzPVCX sKOMNt23q7UTkq4sh3fQ=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id DCD63D788E; Tue,  7 Feb 2017 11:38:17 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 018FD865E9F1; Tue,  7 Feb 2017 20:38:15 +0100 (CET)
From: otroan@employees.org
Message-Id: <757E0263-7801-49D3-8A3D-8B5E2BD9C96D@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_2001CC1C-F1C0-4DF3-BB06-90280A1A8F86"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Tue, 7 Feb 2017 20:38:15 +0100
In-Reply-To: <b07dcffe-107a-a777-2d03-57931088d842@isi.edu>
To: Joe Touch <touch@isi.edu>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <b07dcffe-107a-a777-2d03-57931088d842@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EEfJvN1I1kicBtR3Obir6Tei6jM>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:38:20 -0000

--Apple-Mail=_2001CC1C-F1C0-4DF3-BB06-90280A1A8F86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joe,

> Can anyone give those of us not tracking 672 messages a brief summary?
> IMO, without diving into that thread deeply, I agree with the new =
proposed text below from Brian:

Posted to list on Satuday.
=
https://mailarchive.ietf.org/arch/msg/ietf/MJexpTisUTSN2XrkkYVVLPJrjFM/?qi=
d=3D8e4597241d656835af9f01439581f375

>>    With one exception, extension headers are not processed, inserted,
>>    deleted or modified by any node along a packet's delivery path, =
until
>>    the packet reaches the node (or each of the set of nodes, in the =
case
>>    of multicast) identified in the Destination Address field of the =
IPv6
>>    header.
>>=20
> In fact, I'd go further to say that that non-HBH EHs should not even =
be *viewed* or used as context by intermediate nodes.
>=20
> And any limits on what can be done with HBH EHs should be stated =
explicitly. I'd be glad if at least the EH lengths didn't change.

The original intent of the IPv6 design was certainly that. Routers =
should have no need to look beyond the first 40 byte header (with one =
exception) and everything else was end to end encrypted so there =
wouldn't be any purpose looking there anyway.

We might get into trouble with the implementation report.
If anyone knows of any implementation, software or hardware that is =
compliant with that, I'd certainly like to know. :-)

Best regards,
Ole

--Apple-Mail=_2001CC1C-F1C0-4DF3-BB06-90280A1A8F86
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmiInAAoJEL7aWKiYQt92DnoQAIWtZGGCsl7q5gRmDSzsLpzf
k1cjyIeDptGhRiya66xOEF+fxxsj7q/HJNFCXbPRVUTQy5MIAwZLWDkGbI7c+1E/
M1b9OIhe8evevTCChqtJcD5yKoDQpGPm2O07apRmPbp2xaoQp8pEHIQ3ZjktnZvH
PS/SuleNl+peeUCHE/2KwHdIF0YpitsrYJNE2rq5H7ZZtSOxOFakorWQuEh3vn1B
gz6qNHl4bYJqf/e9qaldhCs+5FjmB4fqV0ta03Tbk7bX7iULOmguLgGKFmdUTusZ
YpfonTBovdDIcJ4mRxBaXEBCfnGyoODvbtoh5bDHv1vcWstRMG6oV6rTOzWsncnm
1mt4yvnLZ4xRounlwaAyMeXWqN73HjW61th+3HMGUVhFU6w+mNWKQOt/Aroa7Qx7
gnRYZQS6MxzTQFyZ1FUi3XqcsdyyHks6aio9cq8BRlAodXgr5SdadlnPkczsjeLd
seCZ09UIELKeIx5vphbu7RNbCecmCRBiPIG5+pn/a+PDeHEdjDqsix9pYElQr7rj
mdDyEFwhv6Dym2jbsGbFFGbUyZwZrZup6J0LOHinkGk5wLhBKH1ti5tMU1lTDpVI
lO4fi3/ExmTjBy8vuSyEldUn6St25IYLOh9VTvqGBHBn98GIxzVyUhZh03TavqZK
43ZUa/WaAtPS6kRugxtH
=JIja
-----END PGP SIGNATURE-----

--Apple-Mail=_2001CC1C-F1C0-4DF3-BB06-90280A1A8F86--


From nobody Tue Feb  7 11:42:54 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C54B129E62; Tue,  7 Feb 2017 11:42:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 KxKkV7ncjxCd; Tue,  7 Feb 2017 11:42:47 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 EEB4F129E5B; Tue,  7 Feb 2017 11:42:46 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17JgVpO008880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:42:32 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu>
Date: Tue, 7 Feb 2017 11:42:29 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org>
Content-Type: multipart/alternative; boundary="------------07D681C8AAE849D500F6504E"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9dKVcG_0e1FczUQTgsWNy8z8qXo>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:42:48 -0000

This is a multi-part message in MIME format.
--------------07D681C8AAE849D500F6504E
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit



On 2/7/2017 11:20 AM, otroan@employees.org wrote:
> Joe,
>
>>>>> My apologies: my comments were probably misleading. Certainly, this
>>>>> document is simply RFC1981 to Std, and hence recommending RFC4821 would
>>>>> be kind of ou of scope, here.
>>>>>
>>>>> That say, one might wonder to what extent, and for the general Internet,
>>>>> RFC1981 can be considered succesful (given the filtering of ICMP
>>>>> messages). -- i.e., at this point in time you wouldn't rely on RFC1981
>>>>> (icmp-based pmtud) for path-mtu discovery.
>>>> What Fernando said: I'm certainly not opposed to lifting this to Standard, but it is painting an incorrect picture - PLPMTUD is de facto mandatory these days, and has been for years.
>>> While I'm all in favour of PLMTUD. It doesn't seem like a complete solution.
>>> PMTUD on the other hand supports all protocols on top of IP.
>> If by "supports" you mean "doesn't work", then yes. That's why we now
>> have PLPMTUD.
> PLMTUD is unfortunately not a (complete) replacement of PMTUD.

PLMTUD is a directive to protocols above the IP layer; it isn't a single
protocol, so it wouldn't replace anything.

>
>>> Looking just at our specifications, we cannot state that PLMTUD can replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
>> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
>>
>> (yes, that doc has expired while we're preparing the 04 update, which
>> should be issued shortly)
> Is this the paragraph you are referring to?
>
>    PLPMTUD requires a separate,
>    direct control channel from the egress to the ingress that provides
>    positive feedback; the direct channel is not blocked by policy
>    filters and the positive feedback ensures fail-safe operation if
>    feedback messages are lost [RFC4821].
That is nowhere near section 5.5.2.

5.5.2 indicates places where RFC2473 has errors, esp. in how it
interprets the MTU of the tunnel as being defined by the MTU of the path
within the tunnel, rather than by the tunnel egress reassembly limit.

> I'm very much in favour of working on better ways of doing Path MTU discovery.
> A blanket statement of "use "PLMTUD" seems very premature though.
The point is that this document fails to indicate the current state of
PMTUD. It correctly notes that:

   An extension to Path MTU Discovery defined in this document can be
   found in [RFC4821 <https://tools.ietf.org/html/rfc4821>].  It defines a method for Packetization Layer Path
   MTU Discovery (PLPMTUD) designed for use over paths where delivery of
   ICMP messages to a host is not assured.


IMO, it fails to note that this case - where ICMP messages are assured
along a path - is effectively a unicorn except within systems maintained
by a single entity.

> RFC1981 has 70 citations:
> http://www.arkko.com/tools/allstats/citations-rfc1981.html
>
> Could you expand on your view of how this pertains to advancing RFC1981?
It's called last call input. My input is that this document needs to be
more realistic in noting that, for all intents, ICMP-based MTU discovery
isn't viable and that other methods need to be *expected*, not just that
they're available.

Joe

--------------07D681C8AAE849D500F6504E
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/7/2017 11:20 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
    </div>
    <blockquote
      cite="mid:7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org"
      type="cite">
      <pre wrap="">Joe,

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <blockquote type="cite">
            <blockquote type="cite">
              <pre wrap="">My apologies: my comments were probably misleading. Certainly, this
document is simply RFC1981 to Std, and hence recommending RFC4821 would
be kind of ou of scope, here.

That say, one might wonder to what extent, and for the general Internet,
RFC1981 can be considered succesful (given the filtering of ICMP
messages). -- i.e., at this point in time you wouldn't rely on RFC1981
(icmp-based pmtud) for path-mtu discovery.
</pre>
            </blockquote>
            <pre wrap="">What Fernando said: I'm certainly not opposed to lifting this to Standard, but it is painting an incorrect picture - PLPMTUD is de facto mandatory these days, and has been for years.
</pre>
          </blockquote>
          <pre wrap="">While I'm all in favour of PLMTUD. It doesn't seem like a complete solution.
PMTUD on the other hand supports all protocols on top of IP.
</pre>
        </blockquote>
        <pre wrap="">If by "supports" you mean "doesn't work", then yes. That's why we now
have PLPMTUD.
</pre>
      </blockquote>
      <pre wrap="">
PLMTUD is unfortunately not a (complete) replacement of PMTUD.</pre>
    </blockquote>
    <br>
    PLMTUD is a directive to protocols above the IP layer; it isn't a
    single protocol, so it wouldn't replace anything.<br>
    <br>
    <blockquote
      cite="mid:7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org"
      type="cite"><br>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Looking just at our specifications, we cannot state that PLMTUD can replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
</pre>
        </blockquote>
        <pre wrap="">See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2

(yes, that doc has expired while we're preparing the 04 update, which
should be issued shortly)
</pre>
      </blockquote>
      <pre wrap="">
Is this the paragraph you are referring to?

   PLPMTUD requires a separate,
   direct control channel from the egress to the ingress that provides
   positive feedback; the direct channel is not blocked by policy
   filters and the positive feedback ensures fail-safe operation if
   feedback messages are lost [RFC4821].</pre>
    </blockquote>
    That is nowhere near section 5.5.2.<br>
    <br>
    5.5.2 indicates places where RFC2473 has errors, esp. in how it
    interprets the MTU of the tunnel as being defined by the MTU of the
    path within the tunnel, rather than by the tunnel egress reassembly
    limit.<br>
    <br>
    <blockquote
      cite="mid:7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org"
      type="cite">
      <pre wrap="">I'm very much in favour of working on better ways of doing Path MTU discovery.
A blanket statement of "use "PLMTUD" seems very premature though.</pre>
    </blockquote>
    The point is that this document fails to indicate the current state
    of PMTUD. It correctly notes that:<br>
    <pre class="newpage">   An extension to Path MTU Discovery defined in this document can be
   found in [<a href="https://tools.ietf.org/html/rfc4821" title="&quot;Packetization Layer Path MTU Discovery&quot;">RFC4821</a>].  It defines a method for Packetization Layer Path
   MTU Discovery (PLPMTUD) designed for use over paths where delivery of
   ICMP messages to a host is not assured.


</pre>
    IMO, it fails to note that this case - where ICMP messages are
    assured along a path - is effectively a unicorn except within
    systems maintained by a single entity.<br>
    <br>
    <blockquote
      cite="mid:7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org"
      type="cite">
      <pre wrap="">RFC1981 has 70 citations:
<a class="moz-txt-link-freetext" href="http://www.arkko.com/tools/allstats/citations-rfc1981.html">http://www.arkko.com/tools/allstats/citations-rfc1981.html</a>

Could you expand on your view of how this pertains to advancing RFC1981?
</pre>
    </blockquote>
    It's called last call input. My input is that this document needs to
    be more realistic in noting that, for all intents, ICMP-based MTU
    discovery isn't viable and that other methods need to be *expected*,
    not just that they're available.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------07D681C8AAE849D500F6504E--


From nobody Tue Feb  7 11:47:21 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2945129E67; Tue,  7 Feb 2017 11:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Hh7_TOMa-aqj; Tue,  7 Feb 2017 11:47:18 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 6BE7E129E5E; Tue,  7 Feb 2017 11:47:18 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17JkEQt009519 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:46:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <b07dcffe-107a-a777-2d03-57931088d842@isi.edu> <757E0263-7801-49D3-8A3D-8B5E2BD9C96D@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <5411446e-abd1-c445-e3b8-70c0c0c80660@isi.edu>
Date: Tue, 7 Feb 2017 11:46:15 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <757E0263-7801-49D3-8A3D-8B5E2BD9C96D@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/09eTO3fli-O_GNvrVUmdZORkKuM>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, "Stefano Previdi \(sprevidi\)" <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:47:19 -0000

Thanks.

FWIW, AFAICT inserting headers on the fly also breaks PLPMTUD too
(though PLPMTUD will eventually recover).

Joe


On 2/7/2017 11:38 AM, otroan@employees.org wrote:
> Joe,
>
>> Can anyone give those of us not tracking 672 messages a brief summary?
>> IMO, without diving into that thread deeply, I agree with the new proposed text below from Brian:
> Posted to list on Satuday.
> https://mailarchive.ietf.org/arch/msg/ietf/MJexpTisUTSN2XrkkYVVLPJrjFM/?qid=8e4597241d656835af9f01439581f375
>
>>>    With one exception, extension headers are not processed, inserted,
>>>    deleted or modified by any node along a packet's delivery path, until
>>>    the packet reaches the node (or each of the set of nodes, in the case
>>>    of multicast) identified in the Destination Address field of the IPv6
>>>    header.
>>>
>> In fact, I'd go further to say that that non-HBH EHs should not even be *viewed* or used as context by intermediate nodes.
>>
>> And any limits on what can be done with HBH EHs should be stated explicitly. I'd be glad if at least the EH lengths didn't change.
> The original intent of the IPv6 design was certainly that. Routers should have no need to look beyond the first 40 byte header (with one exception) and everything else was end to end encrypted so there wouldn't be any purpose looking there anyway.
>
> We might get into trouble with the implementation report.
> If anyone knows of any implementation, software or hardware that is compliant with that, I'd certainly like to know. :-)
>
> Best regards,
> Ole


From nobody Tue Feb  7 11:47:58 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5273E129E76; Tue,  7 Feb 2017 11:47:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 GmhbMOdCJmKP; Tue,  7 Feb 2017 11:47:51 -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 C31B2129E5E; Tue,  7 Feb 2017 11:47:51 -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 v17JlpDp040223; Tue, 7 Feb 2017 12:47:51 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v17Jjv7j036982 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2017 12:45:57 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 11:45:55 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Tue, 7 Feb 2017 11:45:56 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>,  "Eggert, Lars" <lars@netapp.com>
Subject: RE: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSgW+yaUQDcUzHwUaWWd7FFympqaFd8O5w
Date: Tue, 7 Feb 2017 19:45:56 +0000
Message-ID: <ac0876415348463296df9bc4ca171141@XCH15-06-08.nw.nos.boeing.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu>
In-Reply-To: <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/udMCOLymqfAVepKYK_HMmuIR-Sw>
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:47:53 -0000

Hi Joe,

In my understanding, RFC4821 does not adequately address scenarios where th=
e
probe packets may (for legitimate reasons) take a different path than the d=
ata
packets, e.g., when Equal-Cost Multi Path (ECMP) is present. This is not on=
ly a
consideration for tunnels, but also for path MTU sharing between transport =
layer
sessions where an MTU learned by a first session is shared with a second se=
ssion
bound for the same destination. In that case, the probes of the first sessi=
on may
take a different path than the data packets of the second session, and a bl=
ack
hole is possible.

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

> -----Original Message-----
> From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Joe Touch
> Sent: Tuesday, February 07, 2017 10:26 AM
> To: otroan@employees.org; Eggert, Lars <lars@netapp.com>
> Cc: tsv-area@ietf.org; 6man-chairs@ietf.org; 6man WG <ipv6@ietf.org>; iet=
f@ietf.org; draft-ietf-6man-rfc1981bis@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Dis=
covery for IP version 6) to Internet Standard
>=20
>=20
>=20
> On 2/4/2017 10:40 AM, otroan@employees.org wrote:
> > Lars,
> >
> >>> My apologies: my comments were probably misleading. Certainly, this
> >>> document is simply RFC1981 to Std, and hence recommending RFC4821 wou=
ld
> >>> be kind of ou of scope, here.
> >>>
> >>> That say, one might wonder to what extent, and for the general Intern=
et,
> >>> RFC1981 can be considered succesful (given the filtering of ICMP
> >>> messages). -- i.e., at this point in time you wouldn't rely on RFC198=
1
> >>> (icmp-based pmtud) for path-mtu discovery.
> >> What Fernando said: I'm certainly not opposed to lifting this to Stand=
ard, but it is painting an incorrect picture - PLPMTUD is de facto
> mandatory these days, and has been for years.
> > While I'm all in favour of PLMTUD. It doesn't seem like a complete solu=
tion.
> > PMTUD on the other hand supports all protocols on top of IP.
> If by "supports" you mean "doesn't work", then yes. That's why we now
> have PLPMTUD.
>=20
> > Looking just at our specifications, we cannot state that PLMTUD can rep=
lace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
>=20
> (yes, that doc has expired while we're preparing the 04 update, which
> should be issued shortly)
>=20
> Joe
>=20



From nobody Tue Feb  7 11:53:25 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554FC12947F; Tue,  7 Feb 2017 11:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 bWP9F8RG3rNQ; Tue,  7 Feb 2017 11:53:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 ED6F2129E5E; Tue,  7 Feb 2017 11:53:21 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17JqW93010479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 11:52:34 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "otroan@employees.org" <otroan@employees.org>, "Eggert, Lars" <lars@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <ac0876415348463296df9bc4ca171141@XCH15-06-08.nw.nos.boeing.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <9836c58c-e533-a69f-a1b7-ed20ce4801e6@isi.edu>
Date: Tue, 7 Feb 2017 11:52:33 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <ac0876415348463296df9bc4ca171141@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6fIOenA6dQmBGMd8aRiYgy6DFQ0>
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:53:23 -0000

Hi, Fred,

This is a separate issue with RFC4821, though.

My point for 1981bis is that it needs to be more clear that ICMP
blocking renders this technique ineffective for the most part. I'm not
saying that PLPMTUD is perfect or the only alternative, but this doc
should be more clear about its own viability.

Joe


On 2/7/2017 11:45 AM, Templin, Fred L wrote:
> Hi Joe,
>
> In my understanding, RFC4821 does not adequately address scenarios where the
> probe packets may (for legitimate reasons) take a different path than the data
> packets, e.g., when Equal-Cost Multi Path (ECMP) is present. This is not only a
> consideration for tunnels, but also for path MTU sharing between transport layer
> sessions where an MTU learned by a first session is shared with a second session
> bound for the same destination. In that case, the probes of the first session may
> take a different path than the data packets of the second session, and a black
> hole is possible.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Joe Touch
>> Sent: Tuesday, February 07, 2017 10:26 AM
>> To: otroan@employees.org; Eggert, Lars <lars@netapp.com>
>> Cc: tsv-area@ietf.org; 6man-chairs@ietf.org; 6man WG <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis@ietf.org
>> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
>>
>>
>>
>> On 2/4/2017 10:40 AM, otroan@employees.org wrote:
>>> Lars,
>>>
>>>>> My apologies: my comments were probably misleading. Certainly, this
>>>>> document is simply RFC1981 to Std, and hence recommending RFC4821 would
>>>>> be kind of ou of scope, here.
>>>>>
>>>>> That say, one might wonder to what extent, and for the general Internet,
>>>>> RFC1981 can be considered succesful (given the filtering of ICMP
>>>>> messages). -- i.e., at this point in time you wouldn't rely on RFC1981
>>>>> (icmp-based pmtud) for path-mtu discovery.
>>>> What Fernando said: I'm certainly not opposed to lifting this to Standard, but it is painting an incorrect picture - PLPMTUD is de facto
>> mandatory these days, and has been for years.
>>> While I'm all in favour of PLMTUD. It doesn't seem like a complete solution.
>>> PMTUD on the other hand supports all protocols on top of IP.
>> If by "supports" you mean "doesn't work", then yes. That's why we now
>> have PLPMTUD.
>>
>>> Looking just at our specifications, we cannot state that PLMTUD can replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
>> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
>>
>> (yes, that doc has expired while we're preparing the 04 update, which
>> should be issued shortly)
>>
>> Joe
>>
>


From nobody Tue Feb  7 11:58:06 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1B3B1295E9; Tue,  7 Feb 2017 11:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 zziAo3g2q6Ai; Tue,  7 Feb 2017 11:57:59 -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 9464F1295EB; Tue,  7 Feb 2017 11:57:59 -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 v17JvwHo030810; Tue, 7 Feb 2017 12:57:59 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v17JvrZE030728 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2017 12:57:54 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 11:57:53 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Tue, 7 Feb 2017 11:57:53 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, "otroan@employees.org" <otroan@employees.org>,  "Eggert, Lars" <lars@netapp.com>
Subject: RE: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSgW+yaUQDcUzHwUaWWd7FFympqaFd8O5wgACJwID//3pYkA==
Date: Tue, 7 Feb 2017 19:57:53 +0000
Message-ID: <0343dd6744e24beb9c6ea4ace333d239@XCH15-06-08.nw.nos.boeing.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <ac0876415348463296df9bc4ca171141@XCH15-06-08.nw.nos.boeing.com> <9836c58c-e533-a69f-a1b7-ed20ce4801e6@isi.edu>
In-Reply-To: <9836c58c-e533-a69f-a1b7-ed20ce4801e6@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1LU0kh8xXz8-gkLZhcUVsONH3uI>
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 19:58:02 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, February 07, 2017 11:53 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; otroan@employees.org; Eg=
gert, Lars <lars@netapp.com>
> Cc: tsv-area@ietf.org; 6man-chairs@ietf.org; 6man WG <ipv6@ietf.org>; iet=
f@ietf.org; draft-ietf-6man-rfc1981bis@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Dis=
covery for IP version 6) to Internet Standard
>=20
> Hi, Fred,
>=20
> This is a separate issue with RFC4821, though.

Agreed. Fred Baker and I were discussing about whether an erratum
should be filed.

> My point for 1981bis is that it needs to be more clear that ICMP
> blocking renders this technique ineffective for the most part. I'm not
> saying that PLPMTUD is perfect or the only alternative, but this doc
> should be more clear about its own viability.

I could agree if suitable language could be adopted.

Thanks - Fred

> Joe
>=20
>=20
> On 2/7/2017 11:45 AM, Templin, Fred L wrote:
> > Hi Joe,
> >
> > In my understanding, RFC4821 does not adequately address scenarios wher=
e the
> > probe packets may (for legitimate reasons) take a different path than t=
he data
> > packets, e.g., when Equal-Cost Multi Path (ECMP) is present. This is no=
t only a
> > consideration for tunnels, but also for path MTU sharing between transp=
ort layer
> > sessions where an MTU learned by a first session is shared with a secon=
d session
> > bound for the same destination. In that case, the probes of the first s=
ession may
> > take a different path than the data packets of the second session, and =
a black
> > hole is possible.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: tsv-area [mailto:tsv-area-bounces@ietf.org] On Behalf Of Joe Tou=
ch
> >> Sent: Tuesday, February 07, 2017 10:26 AM
> >> To: otroan@employees.org; Eggert, Lars <lars@netapp.com>
> >> Cc: tsv-area@ietf.org; 6man-chairs@ietf.org; 6man WG <ipv6@ietf.org>; =
ietf@ietf.org; draft-ietf-6man-rfc1981bis@ietf.org
> >> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU =
Discovery for IP version 6) to Internet Standard
> >>
> >>
> >>
> >> On 2/4/2017 10:40 AM, otroan@employees.org wrote:
> >>> Lars,
> >>>
> >>>>> My apologies: my comments were probably misleading. Certainly, this
> >>>>> document is simply RFC1981 to Std, and hence recommending RFC4821 w=
ould
> >>>>> be kind of ou of scope, here.
> >>>>>
> >>>>> That say, one might wonder to what extent, and for the general Inte=
rnet,
> >>>>> RFC1981 can be considered succesful (given the filtering of ICMP
> >>>>> messages). -- i.e., at this point in time you wouldn't rely on RFC1=
981
> >>>>> (icmp-based pmtud) for path-mtu discovery.
> >>>> What Fernando said: I'm certainly not opposed to lifting this to Sta=
ndard, but it is painting an incorrect picture - PLPMTUD is de
> facto
> >> mandatory these days, and has been for years.
> >>> While I'm all in favour of PLMTUD. It doesn't seem like a complete so=
lution.
> >>> PMTUD on the other hand supports all protocols on top of IP.
> >> If by "supports" you mean "doesn't work", then yes. That's why we now
> >> have PLPMTUD.
> >>
> >>> Looking just at our specifications, we cannot state that PLMTUD can r=
eplace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
> >> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
> >>
> >> (yes, that doc has expired while we're preparing the 04 update, which
> >> should be issued shortly)
> >>
> >> Joe
> >>
> >
>=20



From nobody Tue Feb  7 12:03:49 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DE7129E80; Tue,  7 Feb 2017 12:03:48 -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 autolearn_force=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 mxeOFI-kjpWt; Tue,  7 Feb 2017 12:03:47 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 1866A129E7B; Tue,  7 Feb 2017 12:03:47 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cbBzN-0001oH-GX; Tue, 07 Feb 2017 20:03:45 +0000
Date: Wed, 08 Feb 2017 05:03:42 +0900
Message-ID: <m2poitydi9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gren Elliot <fatkudu@gmail.com>
Subject: Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-7
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y1yF5Rpht061gIiqNye_9c8K7QU>
Cc: jmap@ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:03:48 -0000

>> Trying to setup a new device for use with open protocols is a
>> complete nightmare - you end up needing to configure 2 things for
>> mail (IMAP and SMTP)
>=20
> and now, because we will have to be backward compatible, it will be
> three. so that third had best be a really massive win. and i am not
> seeing it. what i am seeing is second system syndrome in a wrapper of
> whatever today <http://airmail.calendar/2017-02-07%2012:00:00%20GMT>'s
> wrapping fashion is.
>=20
> randy
>=20
> Why?  You will either be using IMAP/SMTP to access your mail/submit
> your messages or you will be using JMAP.  If you have the option of
> the latter, you=A2ve just halved the number of things that need
> configuring.

how does the server forward the submitted mail to the global internet?

how does the server migrate 200 or 2,000 imap users at human speed,
i.e. over months?

yet another protocol that requires a flag day.  that has worked out
so well for ipv6.

randy


From nobody Tue Feb  7 12:07:00 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC53129479; Tue,  7 Feb 2017 12:06:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5w2zLhM_smVV; Tue,  7 Feb 2017 12:06:56 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id ED6A3129469; Tue,  7 Feb 2017 12:06:55 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 07 Feb 2017 20:06:55 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id BCE0DD788B; Tue,  7 Feb 2017 12:06:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=jOU8v6ZBAvPbtl+xZiGNGsoCG4s=; b= id8bWcgjCeedR41fu2d0c8Inq+V3XePcaJJCJHX94JbiWqurVopCAoQ4+uha+M/7 ITV8X7YLUSI77BlxzY4BXGRAAXaNq6sn06u1I7bc22CROJwW2E2FdIegs+Gc6pfM D0KgoF9JEXO/q/sqkBmjDlx0YhowllTB9LKzml46WYQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=OqLXn/wzV+DhONXHo/wG+dn B1HalaZxtELShFeSmpkZ/PmZsE/JgIg77/KqV/9SCNYV+smyH61lbFYbPjoJ1f7+ B7FDd8d9ssOidLENTyzLPrYx8MVor8U4XBPg9ffRPPj6XzRsW1LAYacuk6w76ck/ TlhR6Y+lGJkvYEV08XvY=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 5C3DED788A; Tue,  7 Feb 2017 12:06:54 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 5AE32865EDDD; Tue,  7 Feb 2017 21:06:52 +0100 (CET)
From: otroan@employees.org
Message-Id: <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_8956E3FC-51F0-4D13-B11D-5926009E0DE7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Tue, 7 Feb 2017 21:06:51 +0100
In-Reply-To: <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu>
To: Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u6uqJQEdBvIgif_5_hO-tyVAFbY>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:06:57 -0000

--Apple-Mail=_8956E3FC-51F0-4D13-B11D-5926009E0DE7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joe,

[...]

>>> If by "supports" you mean "doesn't work", then yes. That's why we =
now
>>> have PLPMTUD.
>>>=20
>> PLMTUD is unfortunately not a (complete) replacement of PMTUD.
>=20
> PLMTUD is a directive to protocols above the IP layer; it isn't a =
single protocol, so it wouldn't replace anything.
>=20
>>=20
>>>> Looking just at our specifications, we cannot state that PLMTUD can =
replace PMTUD. Take RFC2473 (IPv6 tunnelling) for example.
>>>>=20
>>> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
>>>=20
>>> (yes, that doc has expired while we're preparing the 04 update, =
which
>>> should be issued shortly)
>>>=20
>> Is this the paragraph you are referring to?
>>=20
>>    PLPMTUD requires a separate,
>>    direct control channel from the egress to the ingress that =
provides
>>    positive feedback; the direct channel is not blocked by policy
>>    filters and the positive feedback ensures fail-safe operation if
>>    feedback messages are lost [RFC4821].
>>=20
> That is nowhere near section 5.5.2.

No, but it was unfortunately all that was written about how to use =
PLMTUD for tunnels.

> 5.5.2 indicates places where RFC2473 has errors, esp. in how it =
interprets the MTU of the tunnel as being defined by the MTU of the path =
within the tunnel, rather than by the tunnel egress reassembly limit.
>=20
>> I'm very much in favour of working on better ways of doing Path MTU =
discovery.
>> A blanket statement of "use "PLMTUD" seems very premature though.
>>=20
> The point is that this document fails to indicate the current state of =
PMTUD. It correctly notes that:
>    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 over paths where delivery =
of
>    ICMP messages to a host is not assured.
>=20
>=20
>=20
> IMO, it fails to note that this case - where ICMP messages are assured =
along a path - is effectively a unicorn except within systems maintained =
by a single entity.
>=20
>> RFC1981 has 70 citations:
>>=20
>> http://www.arkko.com/tools/allstats/citations-rfc1981.html
>>=20
>>=20
>> Could you expand on your view of how this pertains to advancing =
RFC1981?
>>=20
> It's called last call input. My input is that this document needs to =
be more realistic in noting that, for all intents, ICMP-based MTU =
discovery isn't viable and that other methods need to be *expected*, not =
just that they're available.

Right, but if you are correct that ICMP-based MTU discovery is not =
viable then this document should not be advanced.
At the same time for many protocols we have nothing else. An operator =
can break any protocol if that's their policy. And that's the breakage =
we're talking about here, not any issues with the protocol =
specification.

There is a philosophical aspect of this. (Which I'm not the best person =
to represent as I skipped my University studies in philosophy and used =
the student loan to buy a motorcycle... (and only read the art of =
motorcycle maintenance years later) )
This is a tussle. The IETF specifies protocols under the assumption that =
operators treat those protocols largely as specified. The 5-10% failure =
of PMTUD messages may be caused by misconfiguration, misunderstanding or =
mis-intent... Many of our protocols are suffering from the same fate. =
Should the IETF adjust all its protocols to be as middlebox friendly as =
possible? You can make this argument about IPv6 fragments, any packet =
with IPv6 extension headers, IPv4 fragments. Or anything but TCP port =
443/80 and UDP port 53 for that matter. Are we as the IETF going to =
continue standardising protocols to work as best as they possible can, =
ignoring protocol abuse, or are we going to bend over and do whatever it =
takes to make it work for those 5-10% who've actively broken the =
protocol? What about the 90-90% where the protocols work as expected?

Best regards,
Ole



--Apple-Mail=_8956E3FC-51F0-4D13-B11D-5926009E0DE7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmijcAAoJEL7aWKiYQt92ZF0P+weSw/8C4j+v9IfLeQ6GKlWB
QEJzVdY3VWWF+Wim2pLnshyYpkyiaZXG3uEh8aCAUQ5MX6nTbDE667XM4UOwl/5H
KBIM/JjLKXs+Sa5b4y7cb60ogpRR0QNKo3ov1rsI+fhtOf3of8owSfZ9CeN8RlWT
8E8KHrJFodWmDKSyoODXO/MUriLqqb/tDGt00S436TTEzZvkQb/YZZmdzRALeajv
WalhMXWvCfGkydWf0qYRzV60weH/xYhSOUCFbk+E1FlCObQqPf9eCL0ZbbqYfw1c
PTal39THaLxNfAVAKMlHHknXqnaIigGB6eW7tifCukcrD0m8z7gNKt8mi3sKYjRK
eNtQ3EjhcD7WFOa7BL1Xg+15D4B77boU8sxKTQJGDZP1L1qCg2FcIC3lfdcTfjL+
4d+ppfj/Id4XRot8XI2kZPfZjNCHMIVAwvdgTvGbqgBjciO8wwFqzmkWSwdSSNdN
oLp/svu3R6P/lzqojRo1xlnHMvXbS4stP/WfOWut/A6XpbOQ19IdPAS0LlFkIDhe
9eXi/vnVy0fFnQ9uyzGn0+vMqtRTS8IiaCT9KPN2Oy4eJr7mvigSbhitn2U8ygOD
T1KFnURLt6EA2x0hw48iE1ArGKfTFGC2pOFHr3FkylcgTpUkjyvRjKUdzneQXMFF
7ROIZXRCkavFXLb6YTP6
=8K/j
-----END PGP SIGNATURE-----

--Apple-Mail=_8956E3FC-51F0-4D13-B11D-5926009E0DE7--


From nobody Tue Feb  7 12:12:48 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B876129579; Tue,  7 Feb 2017 12:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HQ_uBgjY1rsJ; Tue,  7 Feb 2017 12:12:42 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 0700E1294AB; Tue,  7 Feb 2017 12:12:42 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v17KEJQ6017221 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Feb 2017 12:14:20 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486498460; bh=EMgmRx/oNDJcCwpoixrc4Ot1rtspvWSaST1Qe839Ztg=; h=Subject:To:References:Reply-To:Cc:From:Date:In-Reply-To:From; b=kscXkCpr103bHivOHbi1QchPGIRnfYU9MM4oPaZhq04DVMA2mB1k8ZBjht76bgjl5 a3M0fZKZYXO4IdVbuZ4Lhge6+qDhL6x7vNCvCThpHMj6NMmSZxviku05aY5YRz3M3U yN4uSBs80dui1w4PqQLNm9YSzK4GvAPaiTeHjiPc=
Subject: Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Gren Elliot <fatkudu@gmail.com>, ietf@ietf.org
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
Date: Tue, 7 Feb 2017 12:12:31 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2eqTpAmUOWoRp51ZLBQLKf3AYyM>
Cc: jmap@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:12:43 -0000

On 2/7/2017 7:38 AM, Gren Elliot wrote:
> You will either be using IMAP/SMTP to access your mail/submit your
> messages or you will be using JMAP.  If you have the option of the
> latter, you’ve just halved the number of things that need configuring.


The primary argument being put forward here is simplification of 
end-user configuration effort.

While that has an intuitive appeal, a basic question for any effort to 
replace and existing technology is how big the benefit will be and for 
how much of the market?

In this case, for most people, the configuration effort is quite rare. 
So while it might be a bit of a hassle, it has no effect on daily life.

Well, ok, there are some folk who have to make this change more often, 
due to Draconian and misguided local policies -- the current advice 
about password changes, from the UX community, is not to make changes 
often, since this becomes a serious attack surface.

But how large a community is this and why is this problem not mitigated 
simply by having the user interface take one password specification and 
map it to the two, underlying (and existing) protocols?

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Tue Feb  7 12:14:52 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121C41294C7; Tue,  7 Feb 2017 12:14:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 NbOFWVzHs_w0; Tue,  7 Feb 2017 12:14:49 -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 0EAE6129471; Tue,  7 Feb 2017 12:14:49 -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 v17KEmD7021247; Tue, 7 Feb 2017 13:14:48 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v17KEemE021141 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 7 Feb 2017 13:14:40 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 12:14:39 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Tue, 7 Feb 2017 12:14:39 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, Joe Touch <touch@isi.edu>
Subject: RE: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSgX24aUQDcUzHwUaWWd7FFympqaFd+j3Q
Date: Tue, 7 Feb 2017 20:14:39 +0000
Message-ID: <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
In-Reply-To: <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w4P1JKHmJsoQ3mJAZ5L3U1eXvRA>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:14:51 -0000

Hi Ole and Joe,

Also not to be lost in this discussion is the potential for spoofed ICMP me=
ssages
that would report a size that is either too large or too small.

Thanks - Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.o=
rg
> Sent: Tuesday, February 07, 2017 12:07 PM
> To: Joe Touch <touch@isi.edu>
> Cc: 6man WG <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis@ie=
tf.org; tsv-area@ietf.org; Eggert, Lars
> <lars@netapp.com>; 6man-chairs@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Dis=
covery for IP version 6) to Internet Standard
>=20
> Joe,
>=20
> [...]
>=20
> >>> If by "supports" you mean "doesn't work", then yes. That's why we now
> >>> have PLPMTUD.
> >>>
> >> PLMTUD is unfortunately not a (complete) replacement of PMTUD.
> >
> > PLMTUD is a directive to protocols above the IP layer; it isn't a singl=
e protocol, so it wouldn't replace anything.
> >
> >>
> >>>> Looking just at our specifications, we cannot state that PLMTUD can =
replace PMTUD. Take RFC2473 (IPv6 tunnelling) for
> example.
> >>>>
> >>> See draft-ietf-intarea-tunnels, esp. v03 Section 5.5.2
> >>>
> >>> (yes, that doc has expired while we're preparing the 04 update, which
> >>> should be issued shortly)
> >>>
> >> Is this the paragraph you are referring to?
> >>
> >>    PLPMTUD requires a separate,
> >>    direct control channel from the egress to the ingress that provides
> >>    positive feedback; the direct channel is not blocked by policy
> >>    filters and the positive feedback ensures fail-safe operation if
> >>    feedback messages are lost [RFC4821].
> >>
> > That is nowhere near section 5.5.2.
>=20
> No, but it was unfortunately all that was written about how to use PLMTUD=
 for tunnels.
>=20
> > 5.5.2 indicates places where RFC2473 has errors, esp. in how it interpr=
ets the MTU of the tunnel as being defined by the MTU of the
> path within the tunnel, rather than by the tunnel egress reassembly limit=
.
> >
> >> I'm very much in favour of working on better ways of doing Path MTU di=
scovery.
> >> A blanket statement of "use "PLMTUD" seems very premature though.
> >>
> > The point is that this document fails to indicate the current state of =
PMTUD. It correctly notes that:
> >    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 over paths where delivery o=
f
> >    ICMP messages to a host is not assured.
> >
> >
> >
> > IMO, it fails to note that this case - where ICMP messages are assured =
along a path - is effectively a unicorn except within systems
> maintained by a single entity.
> >
> >> RFC1981 has 70 citations:
> >>
> >> http://www.arkko.com/tools/allstats/citations-rfc1981.html
> >>
> >>
> >> Could you expand on your view of how this pertains to advancing RFC198=
1?
> >>
> > It's called last call input. My input is that this document needs to be=
 more realistic in noting that, for all intents, ICMP-based MTU
> discovery isn't viable and that other methods need to be *expected*, not =
just that they're available.
>=20
> Right, but if you are correct that ICMP-based MTU discovery is not viable=
 then this document should not be advanced.
> At the same time for many protocols we have nothing else. An operator can=
 break any protocol if that's their policy. And that's the
> breakage we're talking about here, not any issues with the protocol speci=
fication.
>=20
> There is a philosophical aspect of this. (Which I'm not the best person t=
o represent as I skipped my University studies in philosophy
> and used the student loan to buy a motorcycle... (and only read the art o=
f motorcycle maintenance years later) )
> This is a tussle. The IETF specifies protocols under the assumption that =
operators treat those protocols largely as specified. The 5-10%
> failure of PMTUD messages may be caused by misconfiguration, misunderstan=
ding or mis-intent... Many of our protocols are suffering
> from the same fate. Should the IETF adjust all its protocols to be as mid=
dlebox friendly as possible? You can make this argument about
> IPv6 fragments, any packet with IPv6 extension headers, IPv4 fragments. O=
r anything but TCP port 443/80 and UDP port 53 for that
> matter. Are we as the IETF going to continue standardising protocols to w=
ork as best as they possible can, ignoring protocol abuse, or
> are we going to bend over and do whatever it takes to make it work for th=
ose 5-10% who've actively broken the protocol? What about
> the 90-90% where the protocols work as expected?
>=20
> Best regards,
> Ole
>=20



From nobody Tue Feb  7 12:19:14 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37A6129E9B; Tue,  7 Feb 2017 12:19:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 DlnGh4kQ3RFE; Tue,  7 Feb 2017 12:19:03 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 30A39129579; Tue,  7 Feb 2017 12:19:03 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17KIEFX013871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 12:18:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu>
Date: Tue, 7 Feb 2017 12:18:16 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q8gq5uteBtZU5xNCjk5sBFbbOCU>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:19:05 -0000

On 2/7/2017 12:06 PM, otroan@employees.org wrote:
> Joe,
...
>>> I'm very much in favour of working on better ways of doing Path MTU discovery.
>>> A blanket statement of "use "PLMTUD" seems very premature though.
>>>
>> The point is that this document fails to indicate the current state of PMTUD. It correctly notes that:
>>    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 over paths where delivery of
>>    ICMP messages to a host is not assured.
>>
>>
>>
>> IMO, it fails to note that this case - where ICMP messages are assured along a path - is effectively a unicorn except within systems maintained by a single entity.
>>
>>> RFC1981 has 70 citations:
>>>
>>> http://www.arkko.com/tools/allstats/citations-rfc1981.html
>>>
>>>
>>> Could you expand on your view of how this pertains to advancing RFC1981?
>>>
>> It's called last call input. My input is that this document needs to be more realistic in noting that, for all intents, ICMP-based MTU discovery isn't viable and that other methods need to be *expected*, not just that they're available.
> Right, but if you are correct that ICMP-based MTU discovery is not viable then this document should not be advanced.
Not necessarily. It's fine to update a protocol that works inside an
enterprise or other controlled environment.

> At the same time for many protocols we have nothing else. An operator can break any protocol if that's their policy. And that's the breakage we're talking about here, not any issues with the protocol specification.

Well, it's a problem with the protocol spec that it's susceptible to
operator interference.

> There is a philosophical aspect of this. (Which I'm not the best person to represent as I skipped my University studies in philosophy and used the student loan to buy a motorcycle... (and only read the art of motorcycle maintenance years later) )
> This is a tussle. The IETF specifies protocols under the assumption that operators treat those protocols largely as specified. The 5-10% failure of PMTUD messages may be caused by misconfiguration, misunderstanding or mis-intent... Many of our protocols are suffering from the same fate. Should the IETF adjust all its protocols to be as middlebox friendly as possible? You can make this argument about IPv6 fragments, any packet with IPv6 extension headers, IPv4 fragments. Or anything but TCP port 443/80 and UDP port 53 for that matter. Are we as the IETF going to continue standardising protocols to work as best as they possible can, ignoring protocol abuse, or are we going to bend over and do whatever it takes to make it work for those 5-10% who've actively broken the protocol? What about the 90-90% where the protocols work as expected?

What I'm suggesting is a lot simpler - just text that makes it clear
what the current state of deployment of support (or interference) for
this protocol is.

I appreciate that you want to not point at PLPMTUD because it's not
widely supported, but **for the same reason** this doc should not hold
up this solution without pointing out very clearly that it basically
isn't going to be work.

Joe


From nobody Tue Feb  7 12:27:11 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4B11294B3; Tue,  7 Feb 2017 12:27:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir <ynir.ietf@gmail.com>
To: <secdir@ietf.org>
Subject: Review of draft-hardie-privsec-metadata-insertion-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148649922555.26656.10191520146576198408.idtracker@ietfa.amsl.com>
Date: Tue, 07 Feb 2017 12:27:05 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CpNMJ_Xqg5nO5PFuGMuwNEEAlHM>
Cc: ietf@ietf.org, draft-hardie-privsec-metadata-insertion.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:27:05 -0000

Reviewer: Yoav Nir
Review result: Has Nits

Hi

The document is well-written and understandable, but a few things
about it seem wrong:

Section 3 describes data minimization as "one of the core mitigations
for the loss of confidentiality". However, the only example given
where data minimization is used to mitigate confidentiality loss is
when browsers suppress cookies in private mode. The rest of the
examples given (HTTP proxies, recursive DNS, VPN) are such where the
data minimization is incidental to some other function. Nobody
deployed the HTTP proxy or the DNS server in order to enhance
privacy.

The HTTP proxy example in particular is not convincing. HTTP is
designed to work without proxies. Any data minimization provided
incidentally by a proxy is nothing that can be counted on, so a
prohibition on restoring said data (especially in the case of a
server-side load balancer) is just not convincing. OTOH in DNS
recursive resolvers that hide the origin IP of the client are the norm
- Authoritative servers hardly ever get to see real addresses of
clients. In that case exposing the real IP address of the client shows
data that was not there before.

I believe the text should differentiate between cases where a network
element is not part of the normal function of the protocol and works
to undo the accidental data minimization that it causes, and cases
where the network element is expected in the protocol and thus the
minimization is expected as well. I think the prescription in the text
applies to the latter. I am not convinced about the former

The VPN example is a strange one. If the subject is a corporate VPN,
then restoring the original IP addresses is the function of the VPN. 
If, OTOH, VPN is that service that allows people to watch Hulu outside
of the US, then restoring the IP address would be counter-productive.
It is also strange to see VPN used as an example of "systems whose
primary function is not to provide confidentiality"


From nobody Tue Feb  7 12:32:39 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB82B129EC6; Tue,  7 Feb 2017 12:32:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4BFpy0xdoEt; Tue,  7 Feb 2017 12:32:36 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 68CBF129EC5; Tue,  7 Feb 2017 12:32:36 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 07 Feb 2017 20:32:36 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0B2ECD788B; Tue,  7 Feb 2017 12:32:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=D/LEo8f7CoVmbcDEvo5/bqRlz3g=; b= agphqJRgFLQaiXi5HXAMDMVt6DtNZwKUN6o5FMk8Ej3C9H0odFWWkV0W9WrcXBW9 glSBHfOLKGndPj0nGE8cOabnRy+rMJqQr6c9zJeCWVUFf6crkkuOVvBc092QvgaQ 262Mp9T6WJE35AFTLMfpvvxK+96lVPG3KQVULXGUhSU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=CCsqhv+DU4LKOWSjOkdyYll h9FPMBOKi6QArpwBmvxALODee8ud3DWmkd6i0vZRxZ/K8XkKv3AR/aIElaeLmoTR ItxskdkaILykSElHBiGz/pEvqBXGArVQ5A6lfH6Eg9YZsHV0iW/qWpMzvNDezHjB MKmujOby5DvqdK4gaMTI=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id CAC03D788A; Tue,  7 Feb 2017 12:32:35 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id DFC6C865F294; Tue,  7 Feb 2017 21:32:33 +0100 (CET)
From: otroan@employees.org
Message-Id: <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_1D7F7009-AABF-47BD-9E9B-7082F79C9295"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Tue, 7 Feb 2017 21:32:33 +0100
In-Reply-To: <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu>
To: Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/auCCfw5V4bOLtWVba8dAuZQKoEQ>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:32:38 -0000

--Apple-Mail=_1D7F7009-AABF-47BD-9E9B-7082F79C9295
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Joe,

Thanks!

> I appreciate that you want to not point at PLPMTUD because it's not
> widely supported, but **for the same reason** this doc should not hold
> up this solution without pointing out very clearly that it basically
> isn't going to be work.

Would something like this help?
(borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)

"Many network security devices block all ICMP messages for perceived
 security benefits, including the errors that are necessary for the proper
 operation of PMTUD. This can result in connections that complete the
 TCP three-way handshake correctly, but then hang when data is transferred.
 This state is referred to as a black hole connection."


Best regards,
Ole

--Apple-Mail=_1D7F7009-AABF-47BD-9E9B-7082F79C9295
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmi7hAAoJEL7aWKiYQt92x8IP/A3kfnv47podTO7Zrm/Kb7Su
1X6XK32mzxnhLRGFz71LcTnZDy1LOade9oEADD0GJufcgRyAPkv2LuacW7ALFhwf
P20aL262tXPySDS2k7rZFFIGmMxNqy9AVNvDrRfQxRnpAbi5nPtuKGUTzFP9AXOj
0AWHzNyU84ItR2rNTGnVQqfazLa/trNbgruFk9KLxuhDC6GuZIWadJFhr6cC2p/S
zd9/+k7iF3sz/zO2JwVcbm0TMjrNORYQ3aCjztz3hmH26innZ6lQOuT5tTBllP3B
irk+FHM8LrLeQfhciFi/8N4kWOPdlqObzz3M/S/SF2vo0Hmdk5dQ8P71WzmgjQIY
MahDzHTfwc173+jda/me1hgFieIBM+ztd4gN9m5P4LL7mO4j5Gdz47urbIfrS2/Z
Mg3P77+NZz2QvT/BusEOAwVvfcspoSjjhR2tKCBrIn132mtnuyXp3X84XlXDlOoq
swqs6TPCnPh/wUvksN0JWJdSSblQ/N3uQinWdHIAWRxwei9gyKQnTH+HrPVTV5jf
3sHu41ui5UlDS7W8PqgXn6J9Hm7m9lTbrgFZC3wyyRiz+Ylyclyj45zoeZ7IvYm/
rstjguXIHjbhDILQ4rDsGL29AmWVRU1nK07e+Iz1GtfIx5gcu3Gc8psq77Ofs7eS
dYCs+1J0d1xWHl5Vkxya
=Xw+/
-----END PGP SIGNATURE-----

--Apple-Mail=_1D7F7009-AABF-47BD-9E9B-7082F79C9295--


From nobody Tue Feb  7 12:54:27 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61AE1129613; Tue,  7 Feb 2017 12:54:21 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 TABe48b23GSS; Tue,  7 Feb 2017 12:54:19 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE56B1294A5; Tue,  7 Feb 2017 12:54:19 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cbCmG-000NRc-9V; Tue, 07 Feb 2017 15:54:16 -0500
Date: Tue, 07 Feb 2017 15:54:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Randy Bush <randy@psg.com>, Gren Elliot <fatkudu@gmail.com>
Subject: Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <9D66E5E7619E1C55F1DEB959@PSB>
In-Reply-To: <m2poitydi9.wl-randy@psg.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qVkNRhFfqqRz7h7A6GT5D7FIMMY>
Cc: jmap@ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 20:54:21 -0000

I agree with most of Dave Crocker's comments and don't have much
time to spend on a proposal that, if approved, I believe (for
reasons that overlap those he cites) will, like many of its
predecessors, die a quiet death after wasting a lot of time.
However, the exchange surrounding one of Randy's comments
prompts a further remark or two...

--On Wednesday, February 8, 2017 05:03 +0900 Randy Bush
<randy@psg.com> wrote:

>> Why?  You will either be using IMAP/SMTP to access your
>> mail/submit your messages or you will be using JMAP.  If you
>> have the option of the latter, you=CA=BCve just halved the =
number
>> of things that need configuring.
>=20
> how does the server forward the submitted mail to the global
> internet?
>=20
> how does the server migrate 200 or 2,000 imap users at human
> speed, i.e. over months?

So, suppose I have a mail server that, because it is configured
in the real world, has to support SMTP and IMAP (and maybe POP3)
for existing users while trying to support new MUAs that use
this JMAP stuff.   Randy suggests that requires configuring
three kinds of systems.  I suggest that he underestimates the
problem.

First, there is not just "configuring" but "supporting".
Working with configurations may be an infrequent activity.
Providing support is a continuing one and takes time, even if
one's idea of support is saying "what do you want for nothing,
figure it out yourself" in a firm tone and at frequent
intervals.  A change from an IMAP/SMTP base to supporting a new
model or representation and systems that provide it vastly
increases that job, and increases it by at least a factor of
three (old one, new one, people considering or trying to make
the transition).

Second, there is an issue that Randy and Dave both hinted at in
different ways.  Unless the proposal is to use Jmap end to end,
replacing SMTP, conversion issues have to be worked out.  The
community made a series of decisions around the time MIME was
adopted that essentially require that the SMTP payload be either
unstructured messages (essentially conformant to 822) or MIME.
The previous (albeit controversial) idea that, other than trace
fields inserted by SMTP MTAs, SMTP could treat the message as
header-free and opaque and carry material that was not at least
822-conformant is history.  That means one needs to configure,
maintain, support, and debug:

	SMTP
	IMAP
	JMAP
	SMTP/Standard Message Headers -> JMAP for inbound
	     messages
	JMAP -> Message Submission for outbound messages.
	
That is a big deal.  There better be a lot of added value to
justify it or it will go nowhere (a slightly different negative
analogy to the rapid and overwhelming success of IPv6 is perhaps
obvious), just as a variety of grand solutions to real or
imagined problems with email have gone nowhere.    With this
proposal, I see some small incremental improvements for systems
that are working in JSON environments anyway, but nothing that
would justify widespread implementation and deployment.

The answer might be different for a mail system that assumed
that all users would be using the same mail store and either
webmail or JSON-based clients/MUAs.  But such mail systems exist
only in proprietary walled gardens and should not be IETF topics
except possibly for mail gateways to and from them.  And those
gateway raise most of the issues outlined above.

TL;DR summary: Just say 'no'.

    john


From nobody Tue Feb  7 13:24:54 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA669129499; Tue,  7 Feb 2017 13:24:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 aVChaKyucpBN; Tue,  7 Feb 2017 13:24:51 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 702EA128874; Tue,  7 Feb 2017 13:24:51 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17LOMfc024098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 13:24:23 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <1d3c4a88-8c50-a0e2-f852-798d671c8750@isi.edu>
Date: Tue, 7 Feb 2017 13:24:23 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x_d7pU5C_fV8NlWhhUqPLX4D64o>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:24:53 -0000

I'd add one sentence about Fred's observation too:

In addition, spoofed ICMP messages can also affect the correct operation
of PMTUD.

That'd do it...

Joe


On 2/7/2017 12:32 PM, otroan@employees.org wrote:
> Joe,
>
> Thanks!
>
>> I appreciate that you want to not point at PLPMTUD because it's not
>> widely supported, but **for the same reason** this doc should not hold
>> up this solution without pointing out very clearly that it basically
>> isn't going to be work.
> Would something like this help?
> (borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)
>
> "Many network security devices block all ICMP messages for perceived
>  security benefits, including the errors that are necessary for the proper
>  operation of PMTUD. This can result in connections that complete the
>  TCP three-way handshake correctly, but then hang when data is transferred.
>  This state is referred to as a black hole connection."
>
>
> Best regards,
> Ole


From nobody Tue Feb  7 13:25:29 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445711295D5; Tue,  7 Feb 2017 13:25:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rp6QPhSJ9yWs; Tue,  7 Feb 2017 13:25:17 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 44EF41294E4; Tue,  7 Feb 2017 13:25:17 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id w20so142603013qtb.1; Tue, 07 Feb 2017 13:25:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6tDw1+v982SFpHTSQV1kbUCiEVF9RiYVPSaGGV23X3k=; b=EaJqQVEHIg1q9pKPKypnAorJdhenBPgNjdhcPIy4L8Iied9N9EvCdQJ6Zfy0S1qkS8 M3mCGiFXzYfJ2nvlEpp7Wb9TjcZpHI6PXyPHexo2Gt0dfdT5BcL29FzbIXA1XyWfREGR tKJKxJk36rB5Wv3Bi6+WsHFlYrhgUQdg5N1q9WyCmN5vTR8Jk0Sk7x48xJ883PXOaWER C63jZtZwfvAH0UOXQqCl4E+/IeourhOE75Na18mZA10wcxecD81a8Nbpc3fHp45DYapm xdR80ozpUUCHq3Ji7MO4K6idkc2WJCCzVoliiHYVD1W3ppXLuzx9OlpbCuIk/DDHKN3K ifHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6tDw1+v982SFpHTSQV1kbUCiEVF9RiYVPSaGGV23X3k=; b=jPKBdvRysqU2Q3W/2Xq6f3A9rDx9mrLJsdlgynEJoN5FYLQzCvNM9wQzf4yuW/67Pl WteEpP78zO4AW+NQ32XJmq1HnUz5XzlCWc3CaZi0OluvqFUxmouXbLZYYktbXINZrA+d HKwPhnp0Q/DZhcwuRyylDhuYlPDEaYG5XreZ2K35PDVs2tpGqQ3UoMWupFYqEUh0ERg8 nE+qMUtPPC2n+eDGpCXrndhiN71q9qg2Ee/C04cs0ptu0Xf3fagKzIzSQgWtvmJqpxXJ 4wnG3HV3oM7kz4E0a8Xcimh2xOhVPrXV94SF82XBfWc+ul0D2ar2rZyePwLlHmJoPSei GbCg==
X-Gm-Message-State: AMke39nPhBhlE3dO4X8vwkPL5M2Ey8WfHwZur43lXawB06vG78MW3kJ9q+QpZJiuUDM2OG/1XzgkrGQQ3G/oaw==
X-Received: by 10.237.35.130 with SMTP id j2mr18360527qtc.45.1486502716388; Tue, 07 Feb 2017 13:25:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.174.226 with HTTP; Tue, 7 Feb 2017 13:24:46 -0800 (PST)
In-Reply-To: <148649922555.26656.10191520146576198408.idtracker@ietfa.amsl.com>
References: <148649922555.26656.10191520146576198408.idtracker@ietfa.amsl.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 7 Feb 2017 13:24:46 -0800
Message-ID: <CA+9kkMCss+V2uAC9CYEQpe9FAwh3-F8EbRRCCtsgZYGhUpu=Dg@mail.gmail.com>
Subject: Re: Review of draft-hardie-privsec-metadata-insertion-05
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=001a113914425e47750547f762e6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-n2HAYcuClrmFFr_-ki6RbZfg4Q>
Cc: draft-hardie-privsec-metadata-insertion.all@ietf.org, IETF <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:25:20 -0000

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

On Tue, Feb 7, 2017 at 12:27 PM, Yoav Nir <ynir.ietf@gmail.com> wrote:

> Reviewer: Yoav Nir
> Review result: Has Nits
>
> Hi
>
> The document is well-written and understandable, but a few things
> about it seem wrong:
>
> Section 3 describes data minimization as "one of the core mitigations
> for the loss of confidentiality". However, the only example given
> where data minimization is used to mitigate confidentiality loss is
> when browsers suppress cookies in private mode. The rest of the
> examples given (HTTP proxies, recursive DNS, VPN) are such where the
> data minimization is incidental to some other function. Nobody
> deployed the HTTP proxy or the DNS server in order to enhance
> privacy.
>

So, I would challenge "nobody" on the HTTP proxy front, but that's not the
important piece here.  The important piece is they generally do have a net
privacy positive effect.  That privacy positive effect is eliminated when
metadata that would be concealed by normal operation is added back in.
That's the converse of your statement:  no one built an HTTP proxy or
recursive DNS server in order to supply metadata.

Is there a specific place in the doc where more text would make this point
clearer?


>
> The HTTP proxy example in particular is not convincing. HTTP is
> designed to work without proxies. Any data minimization provided
> incidentally by a proxy is nothing that can be counted on,


I'm not sure what you mean by "counted on" here.  Do you mean that you
can't know the pool of other users and thus the number of times you'll be
served from cache rather than getting new data?


> so a
> prohibition on restoring said data (especially in the case of a
> server-side load balancer) is just not convincing. OTOH in DNS
> recursive resolvers that hide the origin IP of the client are the norm
> - Authoritative servers hardly ever get to see real addresses of
> clients. In that case exposing the real IP address of the client shows
> data that was not there before.
>
> I believe the text should differentiate between cases where a network
> element is not part of the normal function of the protocol and works
> to undo the accidental data minimization that it causes,


So, I think "accidental" is a tricky word here. The use of a proxy or
recursive resolver is generally speaking not "accidental".  Data
minimization is a consequence of normal operation, and what we're talking
about is changing operations in order to change that data minimization.
The core of the advice is that instead of changing the operation of the
middlebox, change the operation of the device about which you desire data.

What would make that clearer?


> and cases
> where the network element is expected in the protocol and thus the
> minimization is expected as well. I think the prescription in the text
> applies to the latter. I am not convinced about the former
>
> The VPN example is a strange one. If the subject is a corporate VPN,
> then restoring the original IP addresses is the function of the VPN.
> If, OTOH, VPN is that service that allows people to watch Hulu outside
> of the US, then restoring the IP address would be counter-productive.
> It is also strange to see VPN used as an example of "systems whose
> primary function is not to provide confidentiality"
>
> Well, it does two things:  shifts the network locality of the endpoint
using the VPN and masks who is shifting.  I believe the first is the
primary function and the second a common secondary property.  If you would
like different language on this, though, please let me know.

thanks for the review,

Ted

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

<div dir=3D"ltr">On Tue, Feb 7, 2017 at 12:27 PM, Yoav Nir <span dir=3D"ltr=
">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank">ynir.ietf@gm=
ail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"g=
mail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Reviewer: Yoav Nir<br>
Review result: Has Nits<br>
<br>
Hi<br>
<br>
The document is well-written and understandable, but a few things<br>
about it seem wrong:<br>
<br>
Section 3 describes data minimization as &quot;one of the core mitigations<=
br>
for the loss of confidentiality&quot;. However, the only example given<br>
where data minimization is used to mitigate confidentiality loss is<br>
when browsers suppress cookies in private mode. The rest of the<br>
examples given (HTTP proxies, recursive DNS, VPN) are such where the<br>
data minimization is incidental to some other function. Nobody<br>
deployed the HTTP proxy or the DNS server in order to enhance<br>
privacy.<br></blockquote><div><br></div><div>So, I would challenge &quot;no=
body&quot; on the HTTP proxy front, but that&#39;s not the important piece =
here.=C2=A0 The important piece is they generally do have a net privacy pos=
itive effect.=C2=A0 That privacy positive effect is eliminated when metadat=
a that would be concealed by normal operation is added back in.=C2=A0 That&=
#39;s the converse of your statement:=C2=A0 no one built an HTTP proxy or r=
ecursive DNS server in order to supply metadata.=C2=A0 <br><br></div><div>I=
s there a specific place in the doc where more text would make this point c=
learer?<br></div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The HTTP proxy example in particular is not convincing. HTTP is<br>
designed to work without proxies. Any data minimization provided<br>
incidentally by a proxy is nothing that can be counted on, </blockquote><di=
v><br></div><div>I&#39;m not sure what you mean by &quot;counted on&quot; h=
ere.=C2=A0 Do you mean that you can&#39;t know the pool of other users and =
thus the number of times you&#39;ll be served from cache rather than gettin=
g new data?<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">so a<b=
r>
prohibition on restoring said data (especially in the case of a<br>
server-side load balancer) is just not convincing. OTOH in DNS<br>
recursive resolvers that hide the origin IP of the client are the norm<br>
- Authoritative servers hardly ever get to see real addresses of<br>
clients. In that case exposing the real IP address of the client shows<br>
data that was not there before.<br>
<br>
I believe the text should differentiate between cases where a network<br>
element is not part of the normal function of the protocol and works<br>
to undo the accidental data minimization that it causes,</blockquote><div><=
br></div><div>So, I think &quot;accidental&quot; is a tricky word here. The=
 use of a proxy or recursive resolver is generally speaking not &quot;accid=
ental&quot;.=C2=A0 Data minimization is a consequence of normal operation, =
and what we&#39;re talking about is changing operations in order to change =
that data minimization.=C2=A0 The core of the advice is that instead of cha=
nging the operation of the middlebox, change the operation of the device ab=
out which you desire data.<br><br></div><div>What would make that clearer?<=
br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> and cases<br>
where the network element is expected in the protocol and thus the<br>
minimization is expected as well. I think the prescription in the text<br>
applies to the latter. I am not convinced about the former<br>
<br>
The VPN example is a strange one. If the subject is a corporate VPN,<br>
then restoring the original IP addresses is the function of the VPN.<br>
If, OTOH, VPN is that service that allows people to watch Hulu outside<br>
of the US, then restoring the IP address would be counter-productive.<br>
It is also strange to see VPN used as an example of &quot;systems whose<br>
primary function is not to provide confidentiality&quot;<br>
<br></blockquote><div>Well, it does two things:=C2=A0 shifts the network lo=
cality of the endpoint using the VPN and masks who is shifting.=C2=A0 I bel=
ieve the first is the primary function and the second a common secondary pr=
operty.=C2=A0 If you would like different language on this, though, please =
let me know.<br><br></div><div>thanks for the review,<br><br></div><div>Ted=
<br></div><div>=C2=A0</div></div><br></div></div>

--001a113914425e47750547f762e6--


From nobody Tue Feb  7 13:25:35 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23BAD12962A; Tue,  7 Feb 2017 13:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.02
X-Spam-Level: 
X-Spam-Status: No, score=-7.02 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MR67V0BT4IJj; Tue,  7 Feb 2017 13:25:23 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CD3521295D5; Tue,  7 Feb 2017 13:25:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486502720; x=1518038720; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=D2zc5eopqs2xZekQq5mVK/GTKZN92tbPxxWDpFsnvMg=; b=dCey8iU8j1E8EikbIaA9rRxQCUZNd7jwq9vfSonvu8OIJUQ+aIPHUS8V zWrycOwktysv18jZAT++gOzzt4/EsGpxYBJSpwH1sO1SCXiZz9Fc+ygB3 KUzmJzMpa91BhZW5C8J9Q1zYFCyvvyoWuMRFJ+5gawmZ+ySZm9WJNmeE8 8=;
X-IronPort-AV: E=Sophos;i="5.33,346,1477983600";  d="scan'208,217";a="260962660"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine01.qualcomm.com with ESMTP; 07 Feb 2017 13:25:19 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8432"; a="1304961735"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Feb 2017 13:25:19 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 7 Feb 2017 13:25:18 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Tue, 7 Feb 2017 15:25:17 -0600
Message-ID: <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com>
In-Reply-To: <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_AF1123C9-A45F-4E9A-8F06-0401F0CF76DD_="
X-Mailer: MailMate (1.9.6r5319)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01E.na.qualcomm.com (10.85.0.31) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MKBGFYxeBmt6gjqdZQ4fL-wmYTI>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:25:29 -0000

--=_MailMate_AF1123C9-A45F-4E9A-8F06-0401F0CF76DD_=
Content-Type: text/plain; format=flowed; markup=markdown

Ole,

After reading the replies, I wonder if you could amend your summary with 
one point in particular:

On 4 Feb 2017, at 2:32, otroan@employees.org wrote:

> There were three main positions argued in the working group.
>
> 1) Ban header insertion outright.
> 2) Describe the problems with header insertion.
> 3) No changes to RFC2460 text.

What did you see as the objections to going with (1) (which I presume to 
be the equivalent of Brian's proposed text)? Why was it that people 
thought the protocol could not be clarified to say that? And was your 
assessment that those arguments were correct, or that they simply were 
not addressed by the WG? I've seen several people argue on this list 
that (1) was always the intent of the protocol, and that damage occurs 
if you don't follow that directive. I haven't seen anyone here argue 
otherwise. Could you summarize?

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_AF1123C9-A45F-4E9A-8F06-0401F0CF76DD_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">Ole,</p>

<p dir=3D"auto">After reading the replies, I wonder if you could amend yo=
ur summary with one point in particular:</p>

<p dir=3D"auto">On 4 Feb 2017, at 2:32, <a href=3D"mailto:otroan@employee=
s.org" style=3D"color:#3983C4">otroan@employees.org</a> wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">There were three main positions argued in the working gro=
up.</p>

<p dir=3D"auto">1) Ban header insertion outright.<br>
2) Describe the problems with header insertion.<br>
3) No changes to RFC2460 text.</p>
</blockquote>

<p dir=3D"auto">What did you see as the objections to going with (1) (whi=
ch I presume to be the equivalent of Brian's proposed text)? Why was it t=
hat people thought the protocol could not be clarified to say that? And w=
as your assessment that those arguments were correct, or that they simply=
 were not addressed by the WG? I've seen several people argue on this lis=
t that (1) was always the intent of the protocol, and that damage occurs =
if you don't follow that directive. I haven't seen anyone here argue othe=
rwise. Could you summarize?</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_AF1123C9-A45F-4E9A-8F06-0401F0CF76DD_=--


From nobody Tue Feb  7 13:32:10 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 418091293FB; Tue,  7 Feb 2017 13:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sDgrZf4mKko1; Tue,  7 Feb 2017 13:32:00 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id CB9641288B8; Tue,  7 Feb 2017 13:32:00 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 07 Feb 2017 21:32:00 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 6CE45D788B; Tue,  7 Feb 2017 13:32:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=y0h/ZAObWEk7n7caOQxPMGUOjRM=; b= PyaC00YtHZIQabGP53V5drCgx9NFjQ9Ef9yE9Dek/9a/s32QVWYSM6ppVsgd6tvl /RmwB305g1qvccAYA9tk8ga06tRaVrucYeUHk+7u3Df4RM9io4pn1uMIaOkPRLzG AsL8E+xziUxwj5hcINok8Yf8VEfuXGuoWyBmnbgc72Q=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=bKKoZ45I4rRDG+DShY8C36/ 82XNQ79UhQi9hdzZruBvaivK9IZ/L+HazRYgynWY166R4QvbSnU4nF6sMZ/GjIHZ rTb7jYkGkx1WLj9FxU1smxN0ZXA8C6UtvUtkUCvHY2r0j6KrBAtlNUuEiXKNccAR tQjxKLyt0OeFVAVgJL/g=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id EAE0BD788A; Tue,  7 Feb 2017 13:31:59 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id CF2148662B88; Tue,  7 Feb 2017 22:31:57 +0100 (CET)
From: otroan@employees.org
Message-Id: <931F16A4-BF00-4695-857E-F90703A09D32@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_B28B8140-75C7-4779-B2FF-EC5A0E59E649"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Tue, 7 Feb 2017 22:31:57 +0100
In-Reply-To: <1d3c4a88-8c50-a0e2-f852-798d671c8750@isi.edu>
To: Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <1d3c4a88-8c50-a0e2-f852-798d671c8750@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1s4o661WL4A9PjspdwcM7CmzaBE>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:32:02 -0000

--Apple-Mail=_B28B8140-75C7-4779-B2FF-EC5A0E59E649
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks Joe.

> I'd add one sentence about Fred's observation too:
> 
> In addition, spoofed ICMP messages can also affect the correct operation
> of PMTUD.

You don't think that's covered by the existing security considerations:

   This Path MTU Discovery mechanism makes possible two denial-of-
   service attacks, both based on a malicious party sending false Packet
   Too Big messages to a node.

   In the first attack, the false message indicates a PMTU much smaller
   than reality.  This should not entirely stop data flow, since the
   victim node should never set its PMTU estimate below the IPv6 minimum
   link MTU.  It will, however, result in suboptimal performance.

   In the second attack, the false message indicates a PMTU larger than
   reality.  If believed, this could cause temporary blockage as the
   victim sends packets that will be dropped by some router.  Within one
   round-trip time, the node would discover its mistake (receiving
   Packet Too Big messages from that router), but frequent repetition of
   this attack could cause lots of packets to be dropped.  A node,
   however, should never raise its estimate of the PMTU based on a
   Packet Too Big message, so should not be vulnerable to this attack.

Best regards,
Ole


--Apple-Mail=_B28B8140-75C7-4779-B2FF-EC5A0E59E649
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmjzNAAoJEL7aWKiYQt927zwP/1gxyQ01UAmpJwhw8CVunvgs
YH9ZLQLvty44pjEcgWmSrnTXDFvAkjLFYfAaFRMg+bQTW5peD7eUZzU10p4dhekW
j+XlbUurRzwDFixudIcRCXOCU2Ntm9DsqSIz22pvseSdykNHUiZKFAz+zbq2QZry
dciIHoo0xOvHkjKdJ9miQ4/hou/B4ovhXs3JIa2e2m2jKDPdY4wfY7r44BxUgVPC
ImOtNZS9J7J2rw305uCQBlpu6m9SWn88CRjuJfCmD4n7OvrqyKjM4BxFFAKY5LXC
Y1a6AtANk7uCLc6y7VISRPdBkzG4KQDSpgWoEdd1ZjNgud05Lnh3/i3NkVM+jFmj
i3G87b9mwPQ3HjJfiyYhGx37LEIUHPdX1y4afQyaATTzquF75uVx0F6oL0SmUqef
rN0euHdZRNGgMMfzteVd9wAp/rPSooP9Q502cUEvHSBYjbErtcE/O1HkeZwk5hsk
5aaaYcY7rif7apv7eV7dF0pqCeKIAVpY/Xfc6SNb78t0CQO/LlmnQfmhjkaeF8jA
6k4+BDQSbi6K1VIMxazxBbnzBO0jKxQmfiXm11RoYc5raxl5t+LBvBsC3xmyDZiA
lBo5dJgBxTrufDgbGKyaY3ToK6yIBI1awqp1EkZmqOkXVZgpbdEihmciChScRpQt
7PTj55tS6I8ObK+c4aH8
=hwP4
-----END PGP SIGNATURE-----

--Apple-Mail=_B28B8140-75C7-4779-B2FF-EC5A0E59E649--


From nobody Tue Feb  7 13:36:45 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61851294A4; Tue,  7 Feb 2017 13:36:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VyLeFauxzLVD; Tue,  7 Feb 2017 13:36:42 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 2630212955E; Tue,  7 Feb 2017 13:36:42 -0800 (PST)
Received: from [128.9.184.104] ([128.9.184.104]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v17LZpE1025700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 7 Feb 2017 13:35:52 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <1d3c4a88-8c50-a0e2-f852-798d671c8750@isi.edu> <931F16A4-BF00-4695-857E-F90703A09D32@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <4673f71e-11d9-699e-7a15-1d1fd095a6e8@isi.edu>
Date: Tue, 7 Feb 2017 13:35:50 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <931F16A4-BF00-4695-857E-F90703A09D32@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FY1WcIt7YM8GAMSCxSwXStFGDNU>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:36:44 -0000

IMO it's worth including a sentence that highlights these things
elsewhere in the doc.

But if others disagree, the existing text is sufficient.

Joe


On 2/7/2017 1:31 PM, otroan@employees.org wrote:
> Thanks Joe.
>
>> I'd add one sentence about Fred's observation too:
>>
>> In addition, spoofed ICMP messages can also affect the correct operation
>> of PMTUD.
> You don't think that's covered by the existing security considerations:
>
>    This Path MTU Discovery mechanism makes possible two denial-of-
>    service attacks, both based on a malicious party sending false Packet
>    Too Big messages to a node.
>
>    In the first attack, the false message indicates a PMTU much smaller
>    than reality.  This should not entirely stop data flow, since the
>    victim node should never set its PMTU estimate below the IPv6 minimum
>    link MTU.  It will, however, result in suboptimal performance.
>
>    In the second attack, the false message indicates a PMTU larger than
>    reality.  If believed, this could cause temporary blockage as the
>    victim sends packets that will be dropped by some router.  Within one
>    round-trip time, the node would discover its mistake (receiving
>    Packet Too Big messages from that router), but frequent repetition of
>    this attack could cause lots of packets to be dropped.  A node,
>    however, should never raise its estimate of the PMTU based on a
>    Packet Too Big message, so should not be vulnerable to this attack.
>
> Best regards,
> Ole
>


From nobody Tue Feb  7 13:42:38 2017
Return-Path: <adrien@qbik.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C31E8129630; Tue,  7 Feb 2017 13:42:32 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 WBE8gwe9m0mf; Tue,  7 Feb 2017 13:42:30 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CE28C1294D7; Tue,  7 Feb 2017 13:42:29 -0800 (PST)
Received: From [192.168.1.146] (unverified [192.168.1.146]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.0.4 (Build 5913)) with SMTP id <0000958230@smtp.qbik.com>; Wed, 08 Feb 2017 10:42:27 +1300
From: "Adrien de Croy" <adrien@qbik.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "Gren Elliot" <fatkudu@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Tue, 07 Feb 2017 21:42:27 +0000
Message-Id: <ema13d7631-8c2b-4a0c-a229-a78437bc944d@bodybag>
In-Reply-To: <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
User-Agent: eM_Client/6.0.24928.0
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6-h6beCfzEl1KKKdhulPSSt1hnk>
Cc: "jmap@ietf.org" <jmap@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: Adrien de Croy <adrien@qbik.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:42:33 -0000

I've dealt with a lot of customer support issues relating to inability=20
to send mail where reading was available.

the first point I'd make is that most users wouldn't imagine in a=20
million years that you would have a different system for sending mail vs=
=20
reading it, and they are often incredulous when we point that out.  I=20
actually have a lot of sympathy for that POV.

Apart from that, the main issues we see people battling are, in no=20
particular order

* issues with ISPs.  Common to block port 25, many admins don't know=20
about Submit port (587)
* issues with firewalls, need to open / map additional ports
* issues with incorrect user data entry due to double the configuration
* various client software issues exacerbated by this

We (since our SMTP + IMAP is integrated) don't see so many issues=20
relating to dealing with 2 different products (or more) to support mail=20
(e.g. separate vendor for SMTP vs IMAP), but I would expect those would=20
come with admin problems as well, especially if they use locked-in user=20
databases that other products can't access, different support for=20
different auth methods, different support for different crypto=20
algorithms (recent changes to OpenSSL to deprecate RC4 and 3-DES=20
highlighted some of these).

In short, managing 1 port and endpoint requires work.  Managing 2=20
requires more.

I don't know how many people get SMTP and IMAP from the same place, but=20
I would expect it to be the majority of users.  It would be interesting=20
if someone could get some answers on that.

Adrien


------ Original Message ------
From: "Dave Crocker" <dhc@dcrocker.net>
To: "Gren Elliot" <fatkudu@gmail.com>; "ietf@ietf.org" <ietf@ietf.org>
Cc: "jmap@ietf.org" <jmap@ietf.org>; "iesg@ietf.org" <iesg@ietf.org>
Sent: 8/02/2017 9:12:31 AM
Subject: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap)=
=20
- reducing configuration complexity

>On 2/7/2017 7:38 AM, Gren Elliot wrote:
>>You will either be using IMAP/SMTP to access your mail/submit your
>>messages or you will be using JMAP.  If you have the option of the
>>latter, you=E2=80=99ve just halved the number of things that need configu=
ring.
>
>
>The primary argument being put forward here is simplification of=20
>end-user configuration effort.
>
>While that has an intuitive appeal, a basic question for any effort to=20
>replace and existing technology is how big the benefit will be and for=20
>how much of the market?
>
>In this case, for most people, the configuration effort is quite rare.=20
>So while it might be a bit of a hassle, it has no effect on daily life.
>
>Well, ok, there are some folk who have to make this change more often,=20
>due to Draconian and misguided local policies -- the current advice=20
>about password changes, from the UX community, is not to make changes=20
>often, since this becomes a serious attack surface.
>
>But how large a community is this and why is this problem not mitigated=
=20
>simply by having the user interface take one password specification and=
=20
>map it to the two, underlying (and existing) protocols?
>
>d/
>
>--
>   Dave Crocker
>   Brandenburg InternetWorking
>   bbiw.net
>
>_______________________________________________
>Jmap mailing list
>Jmap@ietf.org
>https://www.ietf.org/mailman/listinfo/jmap


From nobody Tue Feb  7 13:49:58 2017
Return-Path: <njhaveri@apple.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F09311294A4 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 13:49:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level: 
X-Spam-Status: No, score=-4.321 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_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cW7hJ4IbaXQR for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 13:49:51 -0800 (PST)
Received: from mail-in4.apple.com (mail-out4.apple.com [17.151.62.26]) (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 392391288B8 for <ietf@ietf.org>; Tue,  7 Feb 2017 13:49:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple; q=dns/txt; i=@apple.com; t=1486504191; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ass4ghwNJiSXB5439qtfdLaSRE6vltu7jl6LbO1tOKw=; b=TLn7EarDpfipDr/YA/q9tK5DdBgFtVY+Y/bXTm566Hnx5IwGm9//gjuL+VrMlVwo U8clbqG+FR5uf4s0pxshVwf8687HTLJGU5tP4V9RWszNu481HnmMD6uZgCAYDMmV 11jiRg7Kb4nSN35iQR5Ny9biiYY/UXtqtRCvTNvZ7GLlZn9TtusgVtVm/UH3DSYc T4QQZHNWbIYBO5M1BoRv5WHnPa5A6WM/2oVLZEpT/eS+AXxatg//GPFbHhHugGoJ cKewHAEMPbnoVyso6UEwBPSMfJXyP47DZ2RY5Ee3u+Zt23zDZ5sPi7FJw0RAzO4X nm8JfdXegRhYZrHuSTe76g==;
Received: from relay8.apple.com (relay8.apple.com [17.128.113.102]) by mail-in4.apple.com (Apple Secure Mail Relay) with SMTP id DA.64.10104.EF04A985; Tue,  7 Feb 2017 13:49:51 -0800 (PST)
X-AuditID: 11973e12-5adff70000002778-af-589a40fe050d
Received: from mailex13.apple.com (nwk-mbx16p-w02.pex.exch.apple.com [17.146.17.21]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by relay8.apple.com (Apple SCV relay) with SMTP id 21.2E.12381.DF04A985; Tue,  7 Feb 2017 13:49:49 -0800 (PST)
Received: from nwk-mbx16p-w01.pex.exch.apple.com (17.146.17.20) by nwk-mbx16p-w02.pex.exch.apple.com (17.146.17.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.544.27; Tue, 7 Feb 2017 13:49:48 -0800
Received: from nwk-mbx16p-w01.pex.exch.apple.com ([17.146.17.20]) by nwk-mbx16p-w01.pex.exch.apple.com ([17.146.17.20]) with mapi id 15.01.0544.027; Tue, 7 Feb 2017 13:49:48 -0800
From: Neil Jhaveri <njhaveri@apple.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Thread-Topic: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Thread-Index: AQHSgYwaHBfYLmOncEKXZixKGs2vHQ==
Date: Tue, 7 Feb 2017 21:49:48 +0000
Message-ID: <2042C2E0-7F86-47AA-800B-3E4E50E66259@apple.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
In-Reply-To: <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [17.202.38.69]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6DA6D5E99794E44A862D66B7DDE35E19@pex.exch.apple.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsUi2FCYpvvfYVaEwY8dLBa/P31gs3jwdyaL xYw/E5ktnm2cz2LRe38GmwOrx6WdJ9k8ds66y+6xZMlPpgDmKC6blNSczLLUIn27BK6MF79P sRd8E6mYs42ngXGDSBcjJ4eEgInE1Kt7WLsYuTiEBPYxSqxYep8JJnF75k82iMQiJomP704w QzjtTBIHuzdBOdsZJebumcPexcjBwSagLrH5XBpIt4iAtsS9/leMIDXMAh2MEtMnnGcHSQgL pErMmfWbEaIoTWLnt4vMELaexJxbf8BWswioSPT8+cIGYvMK2Ehc7jjPArGsjVFi4b4+sEGc Ag4SSy7tACtiFBCT+H5qDVgzs4C4xK0n86F+EJBYsuc8M4QtKvHy8T9WCFtH4uz1J4wQtoJE y8bnjCAPMAtoSqzfpQ8xxlHi5vppzBC2osSU7ofsEPcISpyc+QTsHgmBfnaJnf/amCYwSs9C snoWwqhZSEbNQjJqFpJRCxhZVzEK5SZm5uhm5pnoJRYU5KTqJefnbmIERf10O6EdjKdWWR1i FOBgVOLhzeiYESHEmlhWXJl7iFGag0VJnFfIZGaEkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6p BkaLCf9EUy5fU90b9WC32vIvLpLv25/KNuo8T+/93yRWYzq3Le/v4qLwTdOld0nGXH5VyfFC KKxu5zkuh4f3Nq2WFN+61cYmPubjVu8181pSfn23/JrZtM+4UVdUZsZ1hkuXNr/utz8bteYr yxfngLk3WQxvx63/uXuD4PRyns1Lf+pY3724/vIVJZbijERDLeai4kQA6Ye+fNsCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOIsWRmVeSWpSXmKPExsUiOElQVPevw6wIg1uN1ha/P31gs3jwdyaL xYw/E5ktnm2cz2LRe38GmwOrx6WdJ9k8ds66y+6xZMlPpgDmKC6blNSczLLUIn27BK6MF79P sRd8E6mYs42ngXGDSBcjJ4eEgInE7Zk/2SBsMYkL99YD2VwcQgKLmCQ+vjvBDOG0M0kc7N4E 5WxnlJi7Zw57FyMHB5uAusTmc2kg3SIC2hL3+l8xgtQwC3QwSkyfcJ4dJCEskCoxZ9ZvRoii NImd3y4yQ9h6EnNu/WECsVkEVCR6/nwBO4NXwEbicsd5FohlbYwSC/f1gQ3iFHCQWHJpB1gR I9Ct30+tAWtmFhCXuPVkPhPEDwISS/acZ4awRSVePv7HCmHrSJy9/oQRwlaQaNn4nBHkAWYB TYn1u/QhxjhK3Fw/jRnCVpSY0v2QHeIeQYmTM5+wTGCUnIVk2yyE7llIumch6Z6FpHsBI+sq RoGi1JzESgu9xIKCnFS95PzcTYyg6G0oTNvB2LTc6hCjAAejEg9vRseMCCHWxLLiytxDjBIc zEoivJe0Z0UI8aYkVlalFuXHF5XmpBYfYpTmYFES5/XcD1QtkJ5YkpqdmlqQWgSTZeLglGpg bON/8PPCigehbB8zm/kErpY8advS6K2rbqS6TmnT3nNnl61/qdr3wv2wzqRzh2p1mAN9tsfO /bVWtOduT5iDh9Csok173QW99a98djrsNT/n3B0d8b7FV5milVZJ1iYt/Tz38znxQgupTrXt xs/i7uu2vvyq1v8ppqL32dq+F3MrbZf7XqyZpsRSnJFoqMVcVJwIAOYsUbTaAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AhMoDl3h5XoNA8l57MGumAToG1M>
Cc: "jmap@ietf.org" <jmap@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Gren Elliot <fatkudu@gmail.com>, "iesg@ietf.org" <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 21:49:55 -0000

PiBPbiBGZWIgNywgMjAxNywgYXQgMTI6MTIgUE0sIERhdmUgQ3JvY2tlciA8ZGhjQGRjcm9ja2Vy
Lm5ldD4gd3JvdGU6DQo+IA0KPiBCdXQgaG93IGxhcmdlIGEgY29tbXVuaXR5IGlzIHRoaXMgYW5k
IHdoeSBpcyB0aGlzIHByb2JsZW0gbm90IG1pdGlnYXRlZCBzaW1wbHkgYnkgaGF2aW5nIHRoZSB1
c2VyIGludGVyZmFjZSB0YWtlIG9uZSBwYXNzd29yZCBzcGVjaWZpY2F0aW9uIGFuZCBtYXAgaXQg
dG8gdGhlIHR3bywgdW5kZXJseWluZyAoYW5kIGV4aXN0aW5nKSBwcm90b2NvbHM/DQoNCg0KSSBh
Z3JlZSB0aGF0IHRoaXMgY2FuIGdvIGEgbG9uZyB3YXkuICBPbiBpT1MgYW5kIG1hY09TLCB3ZSd2
ZSBkb25lIHRoaXMgdG8gYSBsaW1pdGVkIGRlZ3JlZSwgYnkgYnVpbGRpbmcgYSBjZW50cmFsIGRh
dGFiYXNlIG9mIGFjY291bnRzIHRoYXQgZWFjaCBhcHAgdXNlcy4g4oCcQnJhbmRlZCBwYXJ0bmVy
4oCdIGFjY291bnRzIGxpa2UgR29vZ2xlL1lhaG9vIS9Bb2wvZXRjIGhhdmUgdGhlIGNyZWRlbnRp
YWxzIGNlbnRyYWxseSBzdG9yZWQsIGFuZCBjaGlsZCBhY2NvdW50cyAoSU1BUCwgU01UUCwgZXRj
KSBpbmhlcml0IHRoZW0sIHdpdGggYSBzaW5nbGUgVUkgZnJhbWV3b3JrIHRvIHJlLWF1dGhlbnRp
Y2F0ZS4NCg0KVW5mb3J0dW5hdGVseSwgcmVndWxhciBhY2NvdW50cyBzdGlsbCBkb27igJl0IGhh
dmUgdGhpcyB0cmVhdG1lbnQsIGFuZCBpdCBzdGlsbCBkcml2ZXMgYSBsb3Qgb2YgY2FsbHMgdG8g
QXBwbGVDYXJlLiBUaGVyZSBhcmUgYSBidW5jaCBvZiByZWFzb25zIHdoeSwgYnV0IG9uZSBpcyB0
aGF0IGl04oCZcyB0cmlja3kgdG8gYmUgc3VyZSB0aGF0IHRoZSB2YXJpb3VzIHByb3RvY29scy9o
b3N0bmFtZXMgaGF2ZSBiZWVuIGFwcHJvcHJpYXRlbHkgYnVuZGxlZCB0b2dldGhlciBpbnRvIHdo
YXQgaXMgdHJ1bHkgdGhlIHNhbWUgc2VydmljZSwgd2hlcmUgdGhlIHNhbWUgdXNlcm5hbWUvcGFz
c3dvcmQgdHJ1bHkgYXBwbGllcywgYW5kIHRoZXJlIGlzbuKAmXQgYSBzZWN1cml0eSBpc3N1ZSBm
cm9tIHRha2luZyB5b3VyIHVzZXItdXBkYXRlZCBJTUFQIHBhc3N3b3JkIGFuZCBzZW5kaW5nIGl0
IG9mZiB0byBhIENhbERBViBzZXJ2ZXIgd2l0aCBhIGRpZmZlcmVudCBob3N0bmFtZS4gVGhpcyBk
b2VzIHNlZW0gbGlrZSBhbiBpbmNyZW1lbnRhbGx5IHNvbHZhYmxlIHByb2JsZW0sIHRob3VnaCwg
d2l0aCBzb21lIG9mIHRoZSBvdGhlciB3b3JrIGJlaW5nIGRvbmUgaW4gdGhlIGFjY291bnQgY29u
ZmlndXJhdGlvbiBzcGFjZS4NCg0KSG93ZXZlciwgdGhlcmUgYXJlIHN0aWxsIHNvbWUgb3BlcmF0
aW9uYWwgaXNzdWVzIHRoYXQgYXJpc2UsIGV2ZW4gd2l0aCB0aGlzIGtpbmQgb2YgVUksIGZvciBl
eGFtcGxlOg0KKGEpIFR3byBkaWZmZXJlbnQgcHJvdG9jb2xzL3NlcnZlcnMgb2Z0ZW4gbGVhZCB0
byB2ZXJ5IGNvbmZ1c2luZyBwYXJ0aWFsIGZhaWx1cmVzIChJIGNhbiBjaGVjayBmb3IgbXkgTWFp
bCwgYnV0IEkgY2Fu4oCZdCBzZW5kIGFueSkuDQooYikgUG9ydCBmaXJlLXdhbGxpbmcuIEl0IHdh
cyBhIG1vcmUgY29tbW9uIHN1cHBvcnQgaXNzdWUgZm9yIHVzIDgtMTAgeWVhcnMgYWdvLCBidXQg
aGFzIHN1YnNpZGVkIGluIHJlY2VudCB5ZWFycy4NCg0KVGhhdCBhbGwgYmVpbmcgc2FpZCwgSSB0
aGluayB0aGVyZSBhcmUgc29tZSB2ZXJ5IGNvbXBlbGxpbmcgYXNwZWN0cyBoZXJlLCBwYXJ0aWN1
bGFybHkgdGhlIHN0YXRlbGVzcyBuYXR1cmUgb2YgdGhlIHByb3RvY29sLCBhbmQgdXNpbmcgSFRU
UCB1bmRlcm5lYXRoLiBGcm9tIGEgY2xpZW504oCZcyBwZXJzcGVjdGl2ZSwgSSBjYW4gc2F5IHRo
YXQgdGhpcyB3b3VsZCBsZWFkIHRvIGEgZmFyIHNpbXBsZXIgaW1wbGVtZW50YXRpb24sIHdpdGgg
cHJlLWV4aXN0aW5nIEVXUy9FQVMgaW1wbGVtZW50YXRpb25zIGJlaW5nIHRoZSBiYWNraW5nIG9m
IHRoYXQgc3RhdGVtZW50Lg==


From nobody Tue Feb  7 15:03:06 2017
Return-Path: <fatkudu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D59751294F9; Tue,  7 Feb 2017 15:02:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvOciXkoJVkS; Tue,  7 Feb 2017 15:02:55 -0800 (PST)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::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 6EEDB1294EF; Tue,  7 Feb 2017 15:02:55 -0800 (PST)
Received: by mail-yb0-x235.google.com with SMTP id 123so40167746ybe.3; Tue, 07 Feb 2017 15:02:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bKxMHOQmQma/B3fuAIlsHWChl4v1bRpJBBRMpN4xX88=; b=cjheKVYx0JA8d7gI6o9MshIsHOdZbs3fzcOwVlEXiVmrx9psge0LqICP8LcSnAVmX7 c1o3oWeA6PuUhCArfFiq/1ZlM6ZCiSiEFCtbwLmg7YzE/qNM7vXp9NbYld5gSAfV6hCJ Ut/Fha4v/E6ho7oM6L2032QPX5IF5dikG5owYNnXGhZ8YaGU1Z4SJohHW7OjmSONqyN8 QMVyANfX0ijG1t9XZ8jISjaHlA6GCZ6crZD4bn2kGkIlFcmzVZ0Cc/FXgUb2xSDyQ8Od YsQLPLiU8Cty0aoByaujd4yn3yGBtKQXbSp7NvaOleivSz2XVjx0nU0DaRzKaTfrX7O6 nCPQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=bKxMHOQmQma/B3fuAIlsHWChl4v1bRpJBBRMpN4xX88=; b=Uh97TyEPwBXkW5OXnKgDdf8ZNLrpHOk+/k56vz/be3gVKFE5jFTjsCLx6heIWDYQDk FgGLpYnanE1fRXgNwZk4f94yTR39hLL6gOc+UfkVzXStzX3+8mgCu4kDUTv8NIjlahcb ni1CTXI8aMeWfxt6DZwOSp54EbSdYyupD59DehGNcDQb/V+dfxObvJANwB66sXGtqF8p PshC0udCpdQZIZDdiorx8HZd7d9IvCzFP3aFAj/S3ihtgg7Sx2vAvC2514PIoxXkaaKR 7BXX6ABsfljtXlf/6GRCMJa0KdeDgaljWvPd7k2KLBrxT5sQ0Y7VN6Vdx1VBt+0RYdwa k2CQ==
X-Gm-Message-State: AMke39kWGajfkmTi232tJVAuleJvj1GsJPTbgmHhk6AzxZk9SgIZ/AoexjzLXJTw1vtgP9PiJOUAXzWGyVhE4A==
X-Received: by 10.37.173.83 with SMTP id l19mr13330026ybe.84.1486508574695; Tue, 07 Feb 2017 15:02:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.13.250.7 with HTTP; Tue, 7 Feb 2017 15:02:53 -0800 (PST)
Received: by 10.13.250.7 with HTTP; Tue, 7 Feb 2017 15:02:53 -0800 (PST)
In-Reply-To: <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <b83068ad-602b-8feb-f808-35befd13ae29@dcrocker.net>
From: Gren Elliot <fatkudu@gmail.com>
Date: Tue, 7 Feb 2017 23:02:53 +0000
Message-ID: <CAMQk0F8BFZj5LOra=PmpPryc5831Tnsy52kwFugr8xfY8+OvPQ@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: dcrocker@bbiw.net
Content-Type: multipart/alternative; boundary=f403045ec9f88d03930547f8bf74
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TLDIEp9L0S80aYENNi3vHniMJ4I>
Cc: jmap@ietf.org, iesg@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: fatkudu@gmail.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 23:02:57 -0000

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

In answer to the UI question below, for the simple reason that you don't
know whether the same password applies, because the standards have
deliberately separated them and there is no standard provided which can
convey the information that in this case, they're the same. You could
perhaps just try the same credentials for each service but that would be a
clear leak of private information if they weren't the same.

On 7 Feb 2017 20:12, "Dave Crocker" <dhc@dcrocker.net> wrote:


But how large a community is this and why is this problem not mitigated
simply by having the user interface take one password specification and map
it to the two, underlying (and existing) protocols?

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

<div dir=3D"auto"><div>In answer to the UI question below, for the simple r=
eason that you don&#39;t know whether the same password applies, because th=
e standards have deliberately separated them and there is no standard provi=
ded which can convey the information that in this case, they&#39;re the sam=
e. You could perhaps just try the same credentials for each service but tha=
t would be a clear leak of private information if they weren&#39;t the same=
.=C2=A0<br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 7 F=
eb 2017 20:12, &quot;Dave Crocker&quot; &lt;<a href=3D"mailto:dhc@dcrocker.=
net">dhc@dcrocker.net</a>&gt; wrote:<br type=3D"attribution"><blockquote cl=
ass=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div class=3D"quoted-text">=C2=A0<br></div>
But how large a community is this and why is this problem not mitigated sim=
ply by having the user interface take one password specification and map it=
 to the two, underlying (and existing) protocols?</blockquote></div></div><=
/div><div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote=
"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><br></blockquote><blockquote class=3D"quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br></=
blockquote><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><br></blockquote></div></div></div></di=
v>

--f403045ec9f88d03930547f8bf74--


From nobody Tue Feb  7 16:56:34 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACEC81296F3; Tue,  7 Feb 2017 16:56:27 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ySTkG-tXHUFN; Tue,  7 Feb 2017 16:56:26 -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 DD9831296F0; Tue,  7 Feb 2017 16:56:25 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 B394A80371; Wed,  8 Feb 2017 01:56:20 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "otroan@employees.org" <otroan@employees.org>, Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com>
Date: Tue, 7 Feb 2017 21:45:55 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lWtrsER5yNcnXYn0_PxHpOHlqjo>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 00:56:28 -0000

On 02/07/2017 05:14 PM, Templin, Fred L wrote:
> Hi Ole and Joe,
> 
> Also not to be lost in this discussion is the potential for spoofed ICMP messages
> that would report a size that is either too large or too small.

RFC5927 is all about this.

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





From nobody Tue Feb  7 16:56:42 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78232129702; Tue,  7 Feb 2017 16:56: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 autolearn_force=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 5vqfPg8qAxEC; Tue,  7 Feb 2017 16:56:32 -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 D61A51296F9; Tue,  7 Feb 2017 16:56:31 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 97687828DB; Wed,  8 Feb 2017 01:56:27 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Pete Resnick <presnick@qti.qualcomm.com>, otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <6e3ff88d-1954-3dbb-1bd9-aa262ea79192@si6networks.com>
Date: Tue, 7 Feb 2017 21:48:03 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zdWil5AnrGGxpwMhgUvfs8jXrKc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 00:56:33 -0000

On 02/07/2017 06:25 PM, Pete Resnick wrote:
> Ole,
> 
> After reading the replies, I wonder if you could amend your summary with
> one point in particular:
> 
> On 4 Feb 2017, at 2:32, otroan@employees.org
> <mailto:otroan@employees.org> wrote:
> 
>     There were three main positions argued in the working group.
> 
>     1) Ban header insertion outright.
>     2) Describe the problems with header insertion.
>     3) No changes to RFC2460 text.
> 
> What did you see as the objections to going with (1) (which I presume to
> be the equivalent of Brian's proposed text)? Why was it that people
> thought the protocol could not be clarified to say that?

Because if we did, the loophole for people to violate the standard would
disappear (talk about Segment Routing).

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  7 16:56:53 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3241296F0; Tue,  7 Feb 2017 16:56:41 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 nX10ZA7xyeG8; Tue,  7 Feb 2017 16:56:40 -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 67C7C12971E; Tue,  7 Feb 2017 16:56:38 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 EDD39828F9; Wed,  8 Feb 2017 01:56:33 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: Joe Touch <touch@isi.edu>, otroan@employees.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <1d3c4a88-8c50-a0e2-f852-798d671c8750@isi.edu> <931F16A4-BF00-4695-857E-F90703A09D32@employees.org> <4673f71e-11d9-699e-7a15-1d1fd095a6e8@isi.edu>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <e3129449-f9cd-a427-2abb-fa48127a3547@si6networks.com>
Date: Tue, 7 Feb 2017 21:52:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4673f71e-11d9-699e-7a15-1d1fd095a6e8@isi.edu>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TSHiziQoru6gHorzTJs0aNp6ECM>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 00:56:42 -0000

Hi, Joe,

On 02/07/2017 06:35 PM, Joe Touch wrote:
> IMO it's worth including a sentence that highlights these things
> elsewhere in the doc.
> 
> But if others disagree, the existing text is sufficient.

The text is actually incorrect (see below).



>>> I'd add one sentence about Fred's observation too:
>>>
>>> In addition, spoofed ICMP messages can also affect the correct operation
>>> of PMTUD.
>> You don't think that's covered by the existing security considerations:
>>
>>    This Path MTU Discovery mechanism makes possible two denial-of-
>>    service attacks, both based on a malicious party sending false Packet
>>    Too Big messages to a node.
>>
>>    In the first attack, the false message indicates a PMTU much smaller
>>    than reality.  This should not entirely stop data flow, since the
>>    victim node should never set its PMTU estimate below the IPv6 minimum
>>    link MTU.  It will, however, result in suboptimal performance.

If you are employing EHs this could indeed stop the data flow.



>>    In the second attack, the false message indicates a PMTU larger than
>>    reality.  If believed, this could cause temporary blockage as the
>>    victim sends packets that will be dropped by some router.  Within one
>>    round-trip time, the node would discover its mistake (receiving
>>    Packet Too Big messages from that router), but frequent repetition of
>>    this attack could cause lots of packets to be dropped.  A node,
>>    however, should never raise its estimate of the PMTU based on a
>>    Packet Too Big message, so should not be vulnerable to this attack.

This one is probably not worth elaborating: at the end of the day, it
doesn't work.


There are many other things to note here, e.g.:
*  many stacks don't even check that the ICMPv6 PTB referes to e.g. an
ongoing TCP connection

* Some stacks cache the PMTU for all packets sent to the target IPv6
address (i.e., the attack might affect multiple flows)

etc.

Much of this is covered in RFC5927.

-- 
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  7 17:47:51 2017
Return-Path: <hildjj@cursive.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F030A126D73 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 17:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_LOW=-0.7, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=cursive.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IUaFd4DPQgHH for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 17:47:48 -0800 (PST)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 441D912948C for <ietf@ietf.org>; Tue,  7 Feb 2017 17:47:48 -0800 (PST)
Received: by mail-it0-x233.google.com with SMTP id c7so93184299itd.1 for <ietf@ietf.org>; Tue, 07 Feb 2017 17:47:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google;  h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=CBzYPuRG/ZoOo9uik6vekkUrTMoVWccit0mfMc0nJHE=; b=M1bRQ73QRnJzGeAhqA5sKtAZXT06pJFN5KNAXZ3NCImuqacipSpJ8S0Noml7MAj4IG JreVOUxBb0nd7wFUgPyx2FdtFKMmCOjWgYYfc/tuu/1uXyQB3Sf6a3tF6Yhy1Aim1gCQ HS2iTPhCl2Ce92ryJU0QZAY3N4srI+yvR6xqI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=CBzYPuRG/ZoOo9uik6vekkUrTMoVWccit0mfMc0nJHE=; b=io7fQzR1X0PvSccgBNEMmTwxe0/xkdpjYsy6TwJI/eXqkB2yDWAC5UyidphFy9Csvb UjB9mXKKkAjx+FCmGJsQfhmLYGmoOkIMDmjO5dSdPtRAY04Jn0Yo1OYJd7sChT7GZcK0 g/8p7SvxFxtf/NZ+1gmOUUQW3y01fvbd74ZdubI7tqfBXMKnWOmFEeVYOBelfxAf8BUu iyeiKHek2OKqvNDZUB7WwmeVbLZT6Q0pTit19bLoX6E9tnN7I5HuoyevM1BvjispHhRe e6BkmfzUdGG+JPvjg00LK7KZE3qs+Wc5zR+d1Q0U6Qv9n2D1+Mdf6qJOgLp1RE6nY5dI 2ueQ==
X-Gm-Message-State: AMke39m0X53JtjLyQ6qMU2kw+CTNHssKWTDlkZsO197OFL3ilrHCTQDAP/dguVi9+Pv1aw==
X-Received: by 10.36.206.2 with SMTP id v2mr6145218itg.74.1486518467593; Tue, 07 Feb 2017 17:47:47 -0800 (PST)
Received: from ?IPv6:2601:282:200:9150:dc3e:edc3:f0b5:a0dd? ([2601:282:200:9150:dc3e:edc3:f0b5:a0dd]) by smtp.gmail.com with ESMTPSA id y42sm10517806ioi.21.2017.02.07.17.47.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 17:47:46 -0800 (PST)
From: Joe Hildebrand <hildjj@cursive.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Tue, 7 Feb 2017 18:47:45 -0700
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB>
To: jmap@ietf.org, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
In-Reply-To: <9D66E5E7619E1C55F1DEB959@PSB>
Message-Id: <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j-avskKtcMlLESSV34WVCtRMH0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 01:47:50 -0000

> On Feb 7, 2017, at 1:54 PM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> TL;DR summary: Just say 'no'.

No hats, personal opinion only, and in response to several of the =
messages in this thread, not directly to John.


Will it ever be possible for new work to be proposed at the IETF without =
drowning out a chorus of nitpickers?  You may not want to help =
standardize it.  You may not want to implement it.  You may not want to =
deploy it.  You may not want to use it.

So don't.

This work won't hurt the Internet, particularly if done with productive =
input from a couple of people with experience in the existing system, =
and some cross-area review.

You may not like that all application developers want to use HTTPS (and =
derivatives like QUIC), WebSockets, JSON, etc.  However, forcing =
everyone who wants to standardize a modern protocol to justify their =
desire to use a set of modern building blocks has gotten tiring, and =
makes people avoid bringing good technical work to the IETF that would =
benefit from cross-area review.

Every time we make this sort of work difficult at the IETF, we reinforce =
the message that the IETF only exists to pay homage to the protocols of =
our forefathers.  When it comes to email in particular, the system that =
accreted over the years is baroque at best.  We should not stand in the =
way of any attempt to simplify the steaming pile of cruft we preside =
over because the work might be hard.

Several of the concerns that have been raised in this thread are =
interesting, useful, and might make the work better over time.  Had they =
not been phrased with an implied "so therefore your whole idea is dumb =
and you should go away", I probably would have been able to keep myself =
from writing this note.

TL;DR summary: Just say 'yes'.

=E2=80=94=20
Joe Hildebrand


From nobody Tue Feb  7 17:57:42 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA3E1296F7 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 17:57:40 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8ISDjx7Ix8im for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 17:57:38 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e: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 AAEC8129562 for <ietf@ietf.org>; Tue,  7 Feb 2017 17:57:38 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id 204so43790710pge.0 for <ietf@ietf.org>; Tue, 07 Feb 2017 17:57:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=23fQ6Kg5cfI/L8+lIcmTO6PkKD4MPrJ9qeqXhs1Iu8A=; b=jv3F+sATfDQHxEUaLg+fbSSWehzplJ9ZLY2gxUSlqLLi46hLNO741NSk7OjEgb6/tD KtXnRGy6GLR+spE8DTnf5nQ3T45/J9NxGcYH1jrVJowgyOBVah3Wg7TvVwW7OUxiiDxB lqPLDn0Fb5KGljWUvAWwZ3T641wcZLimEt0WxI4RnW4Yv+d3kwiv4sK3SlVuuLG3R9/y VIEObeH13+ju7mpQ1QQ7jcyQ/RpqyGyj4uPFVzZZhcHHziWV4uCO9s+/eXahrAkJ9eqJ 6GBwELnm+0dkqvQGXPFRMtdqUyJQyw/suVW7PUpIkbUfBevAfcRjp8oTO31cxPRecnSE IHqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=23fQ6Kg5cfI/L8+lIcmTO6PkKD4MPrJ9qeqXhs1Iu8A=; b=lk8o2KwCnm2KCLx4Fz7cPbSnwoCzd3ceRmPnIDZWX/DGFWvWpdpNv+9CQjfwkOhbMj Yxt5zU1aCGSU0Tmw9aBK4thIbdNpC0sYR7pcGcCYmjtheraD7xuahyZJ3sStS1AA9HPq gWvnUwYNkiD82xhrDWwnHTfTBkMKsbwnZom4kCCRe8OiVvh7evB/KE/KWTNr/c+IwHo6 DlPtgoZQ9YwxHP6yqt36IEEoujFjbDytXRIrg/6NcRMoufKwgVRqz69Qej0U9zDOP+yE jG39+56+Jd7bo2auzA6j+IGv7xJafb1dqMp6CMILnLPyu81LlbdD1hFd6EWyNwuNpowA CbcA==
X-Gm-Message-State: AIkVDXKz32E5jYQyHltPGgbNj7kYLZR+niJP3oZODfi6rJlAAqcDmeDHfaix2SMANYmYwg==
X-Received: by 10.84.197.131 with SMTP id n3mr29779471pld.69.1486519058121; Tue, 07 Feb 2017 17:57:38 -0800 (PST)
Received: from [192.168.178.21] ([118.148.124.205]) by smtp.gmail.com with ESMTPSA id a24sm14603212pfh.33.2017.02.07.17.57.36 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 17:57:37 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: ietf@ietf.org
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com>
Date: Wed, 8 Feb 2017 14:57:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wweE6aFIplI9w174HBH3HNEdf4Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 01:57:40 -0000

On 08/02/2017 09:32, otroan@employees.org wrote:
> Joe,
> 
> Thanks!
> 
>> I appreciate that you want to not point at PLPMTUD because it's not
>> widely supported, but **for the same reason** this doc should not hold
>> up this solution without pointing out very clearly that it basically
>> isn't going to be work.
> 
> Would something like this help?
> (borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)
> 
> "Many network security devices block all ICMP messages for perceived
>  security benefits, including the errors that are necessary for the proper
>  operation of PMTUD. This can result in connections that complete the
>  TCP three-way handshake correctly, but then hang when data is transferred.
>  This state is referred to as a black hole connection."

Yes. What we are asked to do for Internet Standard is show that a protocol
is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
The fact that it also has an important failure mode should certainly be
documented, but I suspect that every Internet Standard has at least
one important failure mode.

This is not the document in which to fight the battle of interfering firewalls.

    Brian



From nobody Tue Feb  7 18:47:51 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 922E71294D8 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 18:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHRxGwuk79oX for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 18:47:45 -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 AB3481294FF for <ietf@ietf.org>; Tue,  7 Feb 2017 18:47:43 -0800 (PST)
Received: by mail-qk0-x230.google.com with SMTP id u25so108749499qki.2 for <ietf@ietf.org>; Tue, 07 Feb 2017 18:47:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=19rU2uFz7E8ta5+oxsfnGd3N0oDEUhpXukm5KKLE5s4=; b=OS2G/77OX0pQjAOtIjiOw/5Kbk8TJxy5CQZ+zPS7VuX3EaGI1240yvdTfgPi+pca1k QVXqJFcPPwudXtCL6drU5PmIVrSslY0e4Xj871pMhIlTgOk56mWKq+sBLNzg6oEAhccu ixqF7qWQ42ZBK1UMsfW9Z8P5vsRku3qlAtx2hHuWL7byuqeiQojt6ZJSMSyaOFHjifKZ F6+1HAb/lrSAA821vv3eCG2QuKnwG/tO/coTL3eMyhUDv76ayuV8N9XYElUYdLaHhhDX +eJdLInUeg8jN6LuhdlsBtYRa8oivzIUFxr0YV2a38gaY8vGe66mn3qXoOSaIHV0VU7j kNgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=19rU2uFz7E8ta5+oxsfnGd3N0oDEUhpXukm5KKLE5s4=; b=a4ZQEXPdCqOag0MOeQI26g4JDPmIV8+zVE7YVvAzZgq+tReKzMbX4hR2bQvLiF86XS amgITKTE4sWzk4z3DYc9U1hwU6PZrrIiYA/rnx4Oi6pCk/DNagH8fO7R2Z/d/TkTEp1C DLSpCLkqNIKKUo8YsvNUja0IaNsHujg4rUpT7ICo5fWWbRmNRkPYVoAuSgxuT00E+RPq fFWP+VvMXPFZj4KruNplHI/oz6V5usb2nWSFhV0jFz2N6nFKeIH/jtzOBsDTgrBc0dkV y4XGQKUwUDoHqGYWwmfRb229dCP5z1/BjRx3qNbklo75SzzyFM23CsjTv5d5R3SwLYa9 QdPA==
X-Gm-Message-State: AMke39mg1FLZV7l2n4Xf2Aovkc+UKIso1u1CdA/fC8rvfQkGtlxSpp0VDJ4S8EUIPLQRFg==
X-Received: by 10.55.83.71 with SMTP id h68mr16800259qkb.259.1486522062855; Tue, 07 Feb 2017 18:47:42 -0800 (PST)
Received: from [10.0.20.229] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id e3sm5071948qtg.7.2017.02.07.18.47.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 18:47:41 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <3A1DFD1E-E675-47CB-AE54-756C6CD5FF2E@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_7F01E586-A2EB-4970-8B1A-4FCAFFB4BACD"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Tue, 7 Feb 2017 21:47:39 -0500
In-Reply-To: <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net>
To: Joe Hildebrand <hildjj@cursive.net>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CTZDTUOLut2-FSVthc1txqaM-wU>
Cc: jmap@ietf.org, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 02:47:45 -0000

--Apple-Mail=_7F01E586-A2EB-4970-8B1A-4FCAFFB4BACD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 7, 2017, at 8:47 PM, Joe Hildebrand <hildjj@cursive.net> wrote:
> TL;DR summary: Just say 'yes'.

+1

If this winds up having a clean design, it will probably be enough of an =
improvement to be well worth deploying.   That's what it takes for a =
protocol to be successful.   I am not yet convinced that it will be a =
clean design, but if we don't try to design it, it won't matter.


--Apple-Mail=_7F01E586-A2EB-4970-8B1A-4FCAFFB4BACD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 7, 2017, at 8:47 PM, Joe Hildebrand &lt;<a =
href=3D"mailto:hildjj@cursive.net" class=3D"">hildjj@cursive.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">TL;DR summary: Just say 'yes'.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div =
class=3D"">+1</div><div class=3D""><br class=3D""></div><div class=3D"">If=
 this winds up having a clean design, it will probably be enough of an =
improvement to be well worth deploying. &nbsp; That's what it takes for =
a protocol to be successful. &nbsp; I am not yet convinced that it will =
be a clean design, but if we don't try to design it, it won't =
matter.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_7F01E586-A2EB-4970-8B1A-4FCAFFB4BACD--


From nobody Tue Feb  7 18:58:40 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280F51297A8; Tue,  7 Feb 2017 18:58:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, LOTS_OF_MONEY=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0dDtQqTboGy; Tue,  7 Feb 2017 18:58:36 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 59D5B1297A7; Tue,  7 Feb 2017 18:58:36 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1830E9I028997 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 7 Feb 2017 19:00:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486522814; bh=kSvBHNwcNmc5k6QghzGQvAZ5H7ThFj286B1DeB2b0WQ=; h=Subject:To:References:From:Reply-To:Cc:Date:In-Reply-To:From; b=X9s9XltL0zbSkYNmB9/SjdHX4+sqV1SxE449M7UtVdsaJDVDG0tEkq38xHJksdtQt TuYYXorqgl35BdWWFAnPJYHiL/Ua3GBNhYfHOwC/3EXAvUfIiBHZmGvM55N584Vvn/ LrkW/xwSIt1eb45tzRBbSBzB9ILuEMhIyyBVovow=
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Joe Hildebrand <hildjj@cursive.net>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net>
Date: Tue, 7 Feb 2017 18:58:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ubdanksWEMduZ-BGMOxgx3sskOk>
Cc: jmap@ietf.org, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 02:58:37 -0000

On 2/7/2017 5:47 PM, Joe Hildebrand wrote:
>> On Feb 7, 2017, at 1:54 PM, John C Klensin <john-ietf@jck.com>
>> wrote:
>>
>> TL;DR summary: Just say 'no'.
>
> No hats, personal opinion only, and in response to several of the
> messages in this thread, not directly to John.
>
>
> Will it ever be possible for new work to be proposed at the IETF
> without drowning out a chorus of nitpickers?  You may not want to
> help standardize it.  You may not want to implement it.  You may not
> want to deploy it.  You may not want to use it.

Joe,

Sorry, no.

Basic questions about basic utility are not nitpicking.  Basic questions 
about the justifications for basic technical choices are not nitpicking.

And authorizing an IETF working group is not free.  Even the most modest 
IETF working group standards effort had an aggregate cost of around 
US$1M, back when I did a calculation more than 20 years ago, and I would 
love to see someone formulate a claim that it has gone down since then...

So here's an entirely un-novel suggestion:  get the organizations who 
are expecting to implement and deploy this to say so.  From that we can 
get a measure of likely uptake.  Get them also to explain what benefits 
they expect to accrue from this work.

Standards work cannot be a random walk through arbitrary features, no 
matter how intuitively appealing those features might be  There needs to 
be clear and legitimate justifications for each effort and a clear 
indication that there is a market out there wanting the work.

A mild sense that something is benign is not nearly good enough.  Given 
the actual costs of such work.


> This work won't hurt the Internet, particularly if done with

A statement like that ignores issues such as opportunity costs.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Tue Feb  7 19:15:16 2017
Return-Path: <neilj@fastmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB0B51293E9; Tue,  7 Feb 2017 19:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastmail.com header.b=OiNy+Tkt; dkim=pass (1024-bit key) header.d=messagingengine.com header.b=MQPxv+7j
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2XBjF_H4ts6; Tue,  7 Feb 2017 19:15:05 -0800 (PST)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7B2D1293E8; Tue,  7 Feb 2017 19:15:05 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 219CB209AE; Tue,  7 Feb 2017 22:15:05 -0500 (EST)
Received: from betaweb1 ([10.202.2.10]) by compute1.internal (MEProxy); Tue, 07 Feb 2017 22:15:05 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=DQ8juEuzi3EJV2P7hqohPwh0eX I=; b=OiNy+TktU/tDNVBTU34pmiVQNfjPam94XDirtZEgNg18qzA10mmRKJcjkj TXPXyePAyabWFcwVnfMTFu/PhmMoE49wr6Zwfk0LeXFj1oYe5meqMeo3ytRVVQRL aZmHU/PaFlIBOkj/NZy4OP7AuhV95VestJr7E0Pm/yvDVD/7w=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=DQ 8juEuzi3EJV2P7hqohPwh0eXI=; b=MQPxv+7j28OBx9cCZLjiqu4M0JmJCsUFg4 wc4I8AMIBo5KkzEedD/UwHaRA4qQ8oZIi6vNUiXIVWRgQhjBXq9O4N4JBPhI93Vx hyg70RGxtEMGLKfsWHLNCKDZBgNypmdyAOodgKZ1ihMrlcziG+zPZbB3LN5HGr82 //aHIPc5o=
X-ME-Sender: <xms:OY2aWAbsXm5BHL_dGTWUjVHBpmORMZO8MnS-jW-7Z0BxAMvNIK0Dtg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id D37AEE2406; Tue,  7 Feb 2017 22:15:04 -0500 (EST)
Message-Id: <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com>
From: Neil Jenkins <neilj@fastmail.com>
To: jmap@ietf.org, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: multipart/alternative; boundary="_----------=_148652370437114232"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-fdb7c997
Date: Wed, 08 Feb 2017 14:15:04 +1100
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net> <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net>
In-Reply-To: <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/krqIFHAmBiQxabPU4goGHUrKxLQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 03:15:07 -0000

This is a multi-part message in MIME format.

--_----------=_148652370437114232
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"

On Wed, 8 Feb 2017, at 01:58 PM, Dave Crocker wrote:

> So here's an entirely un-novel suggestion:  get the organizations who
> are expecting to implement and deploy this to say so.



Sure! So, FastMail[1], Atmail[2], Linagora[3] are all developing
clients and server based around the current draft proposed to the IETF.
There is implementation work happening in both Cyrus[4] and Dovecot[5]
the two largest open-source IMAP servers. So far in this thread we've
had representatives from Apple and Zimbra both expressing positive
interest in JMAP.


The other side of this, which I mentioned earlier, is the many
proprietary protocols that are popping up, invariably HTTP/JSON based,
to replace the need for IMAP/SMTP (submission). Things like Nylas[6],
Context.io[7] and the Gmail API[8].


There are many benefits to the work we're proposing over IMAP/SMTP
submission; the current thread seems to have got a bit hung up on the
configuration bit, but while this is certainly an improvement it's just
one of many[9].


You may think IMAP/SMTP are great solutions to this problem space, but
it would appear industry disagrees.


Neil.


Links:

  1. https://www.fastmail.com/
  2. https://www.atmail.com/
  3. https://www.linagora.com/
  4. https://cyrusimap.org/
  5. https://www.dovecot.org/
  6. https://nylas.com/cloud/docs
  7. Context.iohttps://context.io/docs/lite
  8. https://developers.google.com/gmail/api/v1/reference/
  9. http://jmap.io/#why-is-jmap-better-than-imap?

--_----------=_148652370437114232
Content-Transfer-Encoding: 7bit
Content-Type: text/html; charset="utf-8"

<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div>On Wed, 8 Feb 2017, at 01:58 PM, Dave Crocker wrote:<br></div>
<blockquote type="cite"><div>So here's an entirely un-novel suggestion:&nbsp; get the organizations who<br></div>
<div>are expecting to implement and deploy this to say so.<br></div>
</blockquote><div><br></div>
<div>Sure! So, <a href="https://www.fastmail.com/">FastMail</a>, <a href="https://www.atmail.com/">Atmail</a>, <a href="https://www.linagora.com/">Linagora</a>&nbsp;are all developing clients and server based around the current draft proposed to the IETF. There is implementation work happening in both <a href="https://cyrusimap.org/">Cyrus</a> and <a href="https://www.dovecot.org/">Dovecot</a> the two largest open-source IMAP servers. So far in this thread we've had representatives from Apple and Zimbra both expressing positive interest in JMAP.<br></div>
<div><br></div>
<div>The other side of this, which I mentioned earlier, is the many proprietary protocols that are popping up, invariably HTTP/JSON based, to replace the need for IMAP/SMTP (submission). Things like <a href="https://nylas.com/cloud/docs">Nylas</a>, <a href="Context.iohttps://context.io/docs/lite">Context.io</a> and the <a href="https://developers.google.com/gmail/api/v1/reference/">Gmail API</a>.<br></div>
<div><br></div>
<div>There are many benefits to the work we're proposing over IMAP/SMTP submission; the current thread seems to have got a bit hung up on the configuration bit, but while this is certainly an improvement it's just one of <a href="http://jmap.io/#why-is-jmap-better-than-imap?">many</a>.<br></div>
<div><br></div>
<div>You may think IMAP/SMTP are great solutions to this problem space, but it would appear industry disagrees.<br></div>
<div><br></div>
<div>Neil.<br></div>
</body>
</html>

--_----------=_148652370437114232--


From nobody Tue Feb  7 21:05:21 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9280129955 for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 21:05:19 -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 autolearn_force=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 FBSyLkPyWahH for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 21:05:18 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 620ED1298D2 for <ietf@ietf.org>; Tue,  7 Feb 2017 21:05:18 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cbKRQ-0004mD-DY; Wed, 08 Feb 2017 05:05:16 +0000
Date: Wed, 08 Feb 2017 14:05:14 +0900
Message-ID: <m2lgthw9v9.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
In-Reply-To: <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-jHuCQTlhZ8EaLic3QLhm8OKIsQ>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 05:05:19 -0000

>> Would something like this help?
>> (borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)
>> 
>> "Many network security devices block all ICMP messages for perceived
>>  security benefits, including the errors that are necessary for the proper
>>  operation of PMTUD. This can result in connections that complete the
>>  TCP three-way handshake correctly, but then hang when data is transferred.
>>  This state is referred to as a black hole connection."
> 
> Yes. What we are asked to do for Internet Standard is show that a protocol
> is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
> The fact that it also has an important failure mode should certainly be
> documented, but I suspect that every Internet Standard has at least
> one important failure mode.

the problem is that this particular failure mode is essentially "does
not work on the real internet."  perhaps documenting that is useful.
but i guess this is ipv6.

randy


From nobody Tue Feb  7 21:13:16 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 582A212996D for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 21:13: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 autolearn_force=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 YDzz3zMjbTqH for <ietf@ietfa.amsl.com>; Tue,  7 Feb 2017 21:13:12 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD4F5129969 for <ietf@ietf.org>; Tue,  7 Feb 2017 21:13:12 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id C4D03284E4C; Wed,  8 Feb 2017 05:13:11 +0000 (UTC)
Date: Wed, 8 Feb 2017 05:13:11 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170208051311.GP28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170206182023.GN28349@mournblade.imrryr.org>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5FRh3awGQpKP_3PO75ymapvqhxQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 05:13:14 -0000

On Mon, Feb 06, 2017 at 06:20:23PM +0000, Viktor Dukhovni wrote:

> Understood.  As I mentioned, I think that avoiding all conversions,
> and checking for whatever verbatim address is found in message
> headers is less likely to lead to problems at the cost of some more
> names in the certificate (all the names that the author uses in
> practice, no combinatorial explosion).
> 
> We'll see how this plays out in practice.  It will take some time,
> as adoption of SMTPUTF8 is still quite low.

There's already a complication, in a pull request for OpenSSL,
Dmitry Belyavsky proposes an implementation of SmtpUtf8 in OpenSSL.
In this proposed implementation OpenSSL acquires a new dependency
on libicu (a widely used IDNA conversion library).  Such a new
dependency is a significant barrier to adoption of the pull request.

[ Donning OpenSSL team-menber hat ]

I am asking the author to remove that dependency, leaving construction
of the normal form of the reference identifier to the application
rather than the X.509 stack.  If he is unsuccessful, and there is
a fundamental requirement for X.509 certificate validation code to
become IDNA aware, that'd be a major barrier to widespread support
for this specification.

Review of the pull-request brings us to another (perhaps the main)
issue.  The security considerations section of the draft fails to
note a significant name-constraint issue.  Suppose an existing CA
is constrained to email addresses in a particular DNS subtree:

       CA Cert
         Name Constraint Extension
           Permitted
             rfc822Name: example.com
             rfc822Name: .example.com

with "example.com" an ordinary LDH domain.  Prior to the proposed
specification, this precludes, e.g., issuance of valid EE certificates
with rfc822 email addresses with a domain part of "example.net".

This draft breaks the existing name constraint restrictions, because
the same CA can now issue EE certificates with SmtpUtf8 addresses
outside the permitted rfc822Name tree.  Possibly including all-ASCII
addresses that just happen to be found in an SmtpUtf8 subjectAltName.

The problem is that the namespaces of the existing "rfc822Name"
constraints and the new "SmtpUtf8Name" constraints substantially
overlap leading to unexpected behaviour.

I therefore propose that:

    When validating an EE certificate that contains SmtpUtf8Name
    subjectAltName values, all such subjectAltName values must
    match any rfc822Name name constraints in each issuer certificate
    that does not also include SmtpUtf8Name constraints.  In
    particular, an issuer CA with only rfc822Name permitted subtrees
    cannot issue EE certificates with SmtpUtf8Name altNames bearing
    (non-ASCII) UTF-8 domains.

I don't recall seeing language in the draft that expains whether
addresses that are valid rfc822Name values can be instead presented
in the certificate as SmtpUtf8Name values, or whether any SmtpUtf8Name
value MUST contain either a non-ASCII localpart or a valid non-ASCII
UTF-8 domain.

It should also be possible to evaluate name constraints and match
an EE certificate against an email address reference identifier
without imposing a dependency on libraries that convert domain
names between A-label and U-label forms.

-- 
	Viktor.


From nobody Tue Feb  7 23:27:08 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A39181295DA; Tue,  7 Feb 2017 23:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xlsZffoIV6SB; Tue,  7 Feb 2017 23:27:05 -0800 (PST)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 C3FC7129410; Tue,  7 Feb 2017 23:27:04 -0800 (PST)
Received: by mail-wm0-x22a.google.com with SMTP id v77so179931639wmv.0; Tue, 07 Feb 2017 23:27:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=dwBNSVc30dT6T9Piy0u9rs8uvXuvqUcSZpihtM+wJTM=; b=eEczFjFCd7h/jgtgO+CP4fXV/E6o5viWXyME8iuR+ow1dBGDpUySuCsgTLYtTSHDT3 AeJk/f2kMQUyZEhdbfSxWM/kWPVrpk5GRw6IL8Ee89kjbE0wqrasz/VAj/EiDoefjRzS 1ll+9tP6sudQ9eSYqclM0ES+jwZE/UxWYJIKiMRKgm1JsGIiHfb/kEcxmjAHZJbgSrOi SzZ+8urYPw8xdTgq/TcZP4j6DZB15PeZLOuxMFMxkvSM0FbGHrPdbcsB9DCxHg8FsZMW HHEAkdtz7sN6ElhcIikzlFCu0bm3sqEVYcsm4Zm51zyGsN1ndP2bnVPKUfWNds2MpIae o9BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=dwBNSVc30dT6T9Piy0u9rs8uvXuvqUcSZpihtM+wJTM=; b=QvVVks32zRHqyhgpP1v7TnKuLrfkfw32wGARI+du3t2VOJOApkPRw060ZE5W8I6GRy UxEs8uXOHI09yRadrNGclck6efrMKUDtX4n+4ysA/ICLLfaXG3S3NnFG8eUwwQnq7VEA QfHEo629JksbE9zK4vMyhRlNN8mZdRJ8bdxaMX5lAGwkw1miY5T13GE4a2UCs9ZK6BFZ 1Yi7gkPlvKhYv8+Zo0TKS4rlY/1+SvF/hroSy1bK5ue28G+njaabH3bw5HB6qfY2jt+a 5SA/X2fQHjIxhmI912SypJaGr1qfUynhIBrsQYUF9k8SLWPKaYrK7nZH5Hk6bNkI5P3h QPYQ==
X-Gm-Message-State: AMke39kiT9xKQOYYmXPZ1Bi2VfEVZ8KQM0QGJc/c6uoXO6sOBXksacD5r+W/fQN24IIh4A==
X-Received: by 10.28.129.5 with SMTP id c5mr15197229wmd.23.1486538823297; Tue, 07 Feb 2017 23:27:03 -0800 (PST)
Received: from users-mbp.mshome.net ([109.253.228.86]) by smtp.gmail.com with ESMTPSA id i73sm1736875wmd.11.2017.02.07.23.27.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Feb 2017 23:27:02 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_270DA9F7-9C3C-4A95-8F28-D48A7D005EF8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Wed, 8 Feb 2017 09:26:59 +0200
In-Reply-To: <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com>
To: Neil Jenkins <neilj@fastmail.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net> <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net> <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ksEDr3Vvw77c6klaXAI6TBWsNX0>
Cc: jmap@ietf.org, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 07:27:06 -0000

--Apple-Mail=_270DA9F7-9C3C-4A95-8F28-D48A7D005EF8
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_B9BE9959-459A-4FDE-B40B-60E950A887FA"


--Apple-Mail=_B9BE9959-459A-4FDE-B40B-60E950A887FA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 8 Feb 2017, at 5:15, Neil Jenkins <neilj@fastmail.com> wrote:
>=20
> On Wed, 8 Feb 2017, at 01:58 PM, Dave Crocker wrote:
>> So here's an entirely un-novel suggestion:  get the organizations who
>> are expecting to implement and deploy this to say so.
>=20
> Sure! So, FastMail <https://www.fastmail.com/>, Atmail =
<https://www.atmail.com/>, Linagora <https://www.linagora.com/> are all =
developing clients and server based around the current draft proposed to =
the IETF. There is implementation work happening in both Cyrus =
<https://cyrusimap.org/> and Dovecot <https://www.dovecot.org/> the two =
largest open-source IMAP servers. So far in this thread we've had =
representatives from Apple and Zimbra both expressing positive interest =
in JMAP.

That=E2=80=99s good to know. I=E2=80=99m wondering if implementing a =
generic email client (rather than a specific =E2=80=9Cgmail=E2=80=9D or =
=E2=80=9Clive=E2=80=9D client) isn=E2=80=99t becoming ever harder. With =
so many older and newer services, a client has to support pop3, imap, =
smtp, EWS, ActiveSync, and maybe a few of the others you mentioned. This =
effort proposes to add yet another one.

Same for a server. A server (even a corporate server, but also public =
ones like gmail) exposes all kinds of protocols: SMTP, IMAP, POP3 and =
some proprietary ones. This is yet another one, and it comes with the =
additional support headache. What do you do if the JMAP clients get =
disconnected but the IMAP works fine and we can=E2=80=99t get that one =
POP3 guy on the phone to say if that one is working. And you can=E2=80=99t=
 just =E2=80=9Cpick one=E2=80=9D unless it=E2=80=99s pop3, because of =
older clients out there.

Not saying that this is not a worthy effort, but it has costs not just =
for the people doing the actual work.

Yoav


--Apple-Mail=_B9BE9959-459A-4FDE-B40B-60E950A887FA
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""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 8 Feb 2017, at 5:15, Neil Jenkins &lt;<a =
href=3D"mailto:neilj@fastmail.com" class=3D"">neilj@fastmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">


<title class=3D""></title>

<div class=3D""><div class=3D"">On Wed, 8 Feb 2017, at 01:58 PM, Dave =
Crocker wrote:<br class=3D""></div>
<blockquote type=3D"cite" class=3D""><div class=3D"">So here's an =
entirely un-novel suggestion:&nbsp; get the organizations who<br =
class=3D""></div>
<div class=3D"">are expecting to implement and deploy this to say so.<br =
class=3D""></div>
</blockquote><div class=3D""><br class=3D""></div>
<div class=3D"">Sure! So, <a href=3D"https://www.fastmail.com/" =
class=3D"">FastMail</a>, <a href=3D"https://www.atmail.com/" =
class=3D"">Atmail</a>, <a href=3D"https://www.linagora.com/" =
class=3D"">Linagora</a>&nbsp;are all developing clients and server based =
around the current draft proposed to the IETF. There is implementation =
work happening in both <a href=3D"https://cyrusimap.org/" =
class=3D"">Cyrus</a> and <a href=3D"https://www.dovecot.org/" =
class=3D"">Dovecot</a> the two largest open-source IMAP servers. So far =
in this thread we've had representatives from Apple and Zimbra both =
expressing positive interest in JMAP.<br =
class=3D""></div></div></div></blockquote><div><br =
class=3D""></div></div>That=E2=80=99s good to know. I=E2=80=99m =
wondering if implementing a generic email client (rather than a specific =
=E2=80=9Cgmail=E2=80=9D or =E2=80=9Clive=E2=80=9D client) isn=E2=80=99t =
becoming ever harder. With so many older and newer services, a client =
has to support pop3, imap, smtp, EWS, ActiveSync, and maybe a few of the =
others you mentioned. This effort proposes to add yet another one.<div =
class=3D""><br class=3D""></div><div class=3D"">Same for a server. A =
server (even a corporate server, but also public ones like gmail) =
exposes all kinds of protocols: SMTP, IMAP, POP3 and some proprietary =
ones. This is yet another one, and it comes with the additional support =
headache. What do you do if the JMAP clients get disconnected but the =
IMAP works fine and we can=E2=80=99t get that one POP3 guy on the phone =
to say if that one is working. And you can=E2=80=99t just =E2=80=9Cpick =
one=E2=80=9D unless it=E2=80=99s pop3, because of older clients out =
there.</div><div class=3D""><br class=3D""></div><div class=3D"">Not =
saying that this is not a worthy effort, but it has costs not just for =
the people doing the actual work.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Yoav</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_B9BE9959-459A-4FDE-B40B-60E950A887FA--

--Apple-Mail=_270DA9F7-9C3C-4A95-8F28-D48A7D005EF8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYmshEAAoJELhJCxUKWMyZhrUH/2MaP4S6rwV45ZYEuuFCA2So
e7Jipdl6ZgB5E8wDrNnW9c0FGVnYupsH8W9qyex3nAuQZCsRQsgV4wGZxDRrQpoc
xca1dAWlTuSQnWzUYBUGotfdcUHF2H7ZLFnPiuLfg4KqD5szgNKe/S8xYzagywwT
2IjLJhMTJS87w3k2HtYGPD8Lvr0sGa2eRfY3JYX1lYMCn4/t+4j0pb2qX+zBQhyp
ZNMSNnw9/bTuCaRibkQfMaG/9LGvTEP1ZuzJ+GrpBl/OI0GS5MTyzxRVg326k/E9
y6p9apmneipqbyxBaqu0oMfncKykb2sCMo1bhO7OrceoXee4alLBAl9cQRidjZc=
=VOF0
-----END PGP SIGNATURE-----

--Apple-Mail=_270DA9F7-9C3C-4A95-8F28-D48A7D005EF8--


From nobody Wed Feb  8 02:15:18 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DE88129504; Wed,  8 Feb 2017 02:15:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vd_R8HYAL0X8; Wed,  8 Feb 2017 02:15:14 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 EFC5F128E18; Wed,  8 Feb 2017 02:15:13 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-d6-589aefb09e8c
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by  (Symantec Mail Security) with SMTP id 47.F6.22993.FAFEA985; Wed,  8 Feb 2017 11:15:12 +0100 (CET)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.78) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 8 Feb 2017 11:14:49 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=8yxydEOt4q5+mxKh+fFjVpyuM0hQUh3gpUi6J6bm3cU=; b=gi+1nhOhcIOFNP5cYCUm9J1I990TdeohICzSJGt23SefU+hc/Z76eC/qE66/fQzhABCEfShAuIW+9HNXmvzlhVPacX3uxgeT26ABwQsfQfvu+jfgR1snglF52h3N6dMqxpC0dV/k8DHsY03lKim2WxSNdLAMGDLA5X6GDPVh5jA=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0996.eurprd07.prod.outlook.com (10.162.37.17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Wed, 8 Feb 2017 10:14:48 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Wed, 8 Feb 2017 10:14:48 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2AgACGiQCAARhlUA==
Date: Wed, 8 Feb 2017 10:14:48 +0000
Message-ID: <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
In-Reply-To: <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 3afe353e-0e8b-4951-da89-08d4500b5066
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0996;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0996; 7:2knK6iJrRA0VQlNCD3a1s3NatztQ0S7zqKrPwr2rTUufrUm3AoXT0vn0Uv622bjjUc7stFxSs9/tAwmO1NWokRPkmr7vtIwDbF6eittiGbQBVqb1zj+n60H7aKBbZw2G7khFV4HSJu2cXbQDTRy74rVPTscSGgt7GziJbtmDx/gnB6XFmBPG1OXMKM3RQ5KHXNUJdab5qC772NKkxxzEjX3NbcOOSr9IbnXx34iyEzlQiem/uw8jUrr2E12TIRGuL5JE606m+QG1SCBx8oOo0BZxhFyQokJfhNvYh+25yU+TQfTDy3EgES3cm07RdQhvpKxnP+0rZUq1EMaKowxNaZXw5Yi+qvYac7pSj+9HKQZzavW+tMqYPKER92mjH9Bq8hKhnjZp4lELmQDpv+LxGWZdztdmYyjLI/jsxpb29FLyiBWCbzEQdehdzlJN7J4h6x7attOLGrKt9hQiGnohhYKG8I4epDLDNx0jhVqWcVkNPZpEIyMTJjC52W03IJsvE/BDwAG+k4CB4H2dbDbAHg==
x-microsoft-antispam-prvs: <AM2PR07MB09960DD2B3432E79DF078BB5F0420@AM2PR07MB0996.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(20170203043)(8121501046)(5005006)(2017020702029)(3002001)(10201501046)(6041248)(20161123560025)(20161123564025)(20161123555025)(20161123558025)(20161123562025)(6072148); SRVR:AM2PR07MB0996; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0996; 
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(189002)(199003)(24454002)(790700001)(6246003)(5660300001)(6116002)(3280700002)(102836003)(93886004)(110136004)(33656002)(7736002)(53546003)(966004)(86362001)(230783001)(3846002)(3660700001)(106356001)(106116001)(66066001)(4326007)(101416001)(7906003)(68736007)(122556002)(105586002)(2906002)(53936002)(54356999)(76176999)(25786008)(606005)(50986999)(6506006)(77096006)(8936002)(74316002)(2950100002)(81156014)(2900100001)(81166006)(8676002)(6916009)(6436002)(38730400002)(92566002)(99286003)(229853002)(9686003)(54906002)(6306002)(54896002)(236005)(97736004)(189998001)(55016002)(7696004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0996; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Feb 2017 10:14:48.8925 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0996
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA01Sa0hTYRjuO+dsO1qDr6X5qhE4orxrKjIkIsMfUtrlRyVR6cyTmjptxyzt j4iLVDQhTbe8jDlQl6kNLRXxMpUoFhpeWopYORd5S5BK0ySPZ4H/nvd5nu95vu/lo0lJv8CN TlZkMkqFPFUqdKTUMa/P+bX+0MQEmn+JZdYqCyWr2WwmZOPzq5TM9rKWklX2NAhlY+P55Clh pF6/TkS26yuEkbpyG7pAXnU8kcCkJmcxyoCTcY5Jmw1aUcaf+PuG8QEqF2njCpEDDTgE1hYH qELkSEtwM4JPrTYBP7xBUGIxi7iBwsUkrI7aEK88IaD8o5bizkvwEIK86qBCRNNCHAZWUxRH O2FfKKvuJDk/iVUEWMtqdvwH8FnomzCKeFMUrHcOkzy+DMapZcTlUPgIdM97c7QYXwNDSRPJ 96pJeGibEnCCA46AisqnOxjhg/D7XRPBYRK7wKS1luDfhkHfzecDdobvs1t2fzy0qDrsHg8Y MWgIrhdwNCyognk6GjZKhgiuF7CZgk3jrD0nBVa68wU8PgPPLJ/tplcEvFct2EMPwVhtH+KF aiHoLQ+F/LYYqH+hQvwm3GB6rACVIi/NrovzOB3KdDOUZmcD++Gt2rqN6W3eC1q6AniLB5QV fRHx2BNUVdWi3bwWiQzImWVYNi0xKNifUSbfZNl0hb+CyTSi7Y/V37bh14GeL4SbEKaRdJ+4 tUATIxHIs9jsNBMCmpQ6ib8ublPiBHl2DqNMj1XeTWVYE3KnKamLOLRx5ooEJ8ozmRSGyWCU /1WCdnDLRXWhNwKNvfU/z8+FrLGT6uk4r9HoAssgClPrHtXe8ywfPHax98OEZ7GuLrst/YGD CqeE3Tp92Ef1LcgjYY/Z4KtdCRf7xF76uzCwlWNwjegICM7LaRwqDG8XPy66058/o+k66t2/ 1LlMxexNbBP0eMwPuyqWyr3nSjXX9SPut1ulFJskP+5NKln5PyRjc65UAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PsH4ZXrf4pXrOE2ZYlln-7w1H00>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 10:15:16 -0000

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgUGV0ZSwNCg0KVGhpcyBpcyBhbiDigJxpbmhlcml0YW5jZeKAnSBmcm9tIEdNUExTLCB3aGVy
ZSBzdXBwb3J0aW5nIGEgc2luZ2xlIHByaW9yaXR5IGVxdWFscyBub3Qgc3VwcG9ydGluZyBwcmlv
cml0aWVzLiBJZiB5b3UgZG9u4oCZdCB3YW50IHRvIHN1cHBvcnQgcHJpb3JpdGllcyB5b3UgZG9u
4oCZdCB3YW50IHlvdXIgdHJhZmZpYyB0byBiZSBwcmVlbXB0ZWTigKZoZW5jZSBwcmlvcml0eSAw
Lg0KDQoNCj5XZWxsLCBpdCBkb2Vzbid0IHNheSB0aGF0IHNob3VsZG4ndCBiZSBkb25lLCBidXQg
aXQgcHJvYmFibHkgZG9lc24ndCBuZWVkIHRvIHNheSBhbnl0aGluZyBhYm91dCBsb2NhbCBjb25m
aWd1cmF0aW9ucy4NCkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBvbiB0aGF0
Lg0KDQpUaGFua3MNCkRhbmllbGUNCg0KRnJvbTogUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25p
Y2tAcXRpLnF1YWxjb21tLmNvbV0NClNlbnQ6IG1hcnRlZMOsIDcgZmViYnJhaW8gMjAxNyAxODow
NQ0KVG86IERhbmllbGUgQ2VjY2FyZWxsaSA8ZGFuaWVsZS5jZWNjYXJlbGxpQGVyaWNzc29uLmNv
bT4NCkNjOiBKYXJpIEFya2tvIDxqYXJpLmFya2tvQHBpdWhhLm5ldD47IGdlbi1hcnRAaWV0Zi5v
cmc7IGRyYWZ0LWlldGYtY2NhbXAtZmxleGlibGUtZ3JpZC1vc3BmLWV4dC5hbGxAaWV0Zi5vcmc7
IGNjYW1wQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0dlbi1hcnRdIFJl
dmlldyBvZiBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDcNCg0KDQpI
aSBEYW5pZWxlLA0KDQpUaGFua3MgZm9yIGFkZHJlc3NpbmcgZXZlcnl0aGluZy4gVGhlcmUncyBv
bmx5IG9uZSBpc3N1ZSBsZWZ0IGluIHNlY3Rpb24gNC4xLjEgb24gUHJpb3JpdHksIGJlbG93LiBJ
J3ZlIHRyaW1tZWQgb3V0IGFsbCB0aGUgcmVzdC4NCg0KT24gNyBGZWIgMjAxNywgYXQgMzozNiwg
RGFuaWVsZSBDZWNjYXJlbGxpIHdyb3RlOg0KDQpJIGdldCB0aGF0IHBhcnQgKCJBdCBsZWFzdCBv
bmUgcHJpb3JpdHkgbGV2ZWwgTVVTVCBiZSBhZHZlcnRpc2VkIikuIEl0J3MgdGhlIGVuZCBJIGRv
bid0IHVuZGVyc3RhbmQ6ICJ0aGF0LCB1bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ks
IFNIQUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuIiBXaGF0IGRvZXMgdGhhdCBtZWFuPw0KDQpb
RENdIEl0IG1lYW5zIHRoYXQgaWYgb25seSBvbmUgcHJpb3JpdHkgaXMgc3VwcG9ydGVkIGl0IGhh
cyB0byBiZSBwcmlvcml0eSAwLg0KDQpTbywgbGV0IG1lIHNlZSBpZiBJIGhhdmUgdGhpcyByaWdo
dDogSXQncyBPSyB0byBoYXZlIDAxMTAwMDAwIGJ1dCBub3QgMDEwMDAwMDAgb3IgMDAxMDAwMDA/
IElmIHNvLCB3aHkgaXMgdGhhdD8NCg0KRm9yIGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZl
IHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2libGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZh
bHVlLCBidXQgdGhhdCBzaG91bGRu4oCZdCBiZSBkb25lLg0KDQpXZWxsLCBpdCBkb2Vzbid0IHNh
eSB0aGF0IHNob3VsZG4ndCBiZSBkb25lLCBidXQgaXQgcHJvYmFibHkgZG9lc24ndCBuZWVkIHRv
IHNheSBhbnl0aGluZyBhYm91dCBsb2NhbCBjb25maWd1cmF0aW9ucy4NCg0KcHINCi0tDQpQZXRl
IFJlc25pY2sgaHR0cDovL3d3dy5xdWFsY29tbS5jb20vfnByZXNuaWNrLzxodHRwOi8vd3d3LnF1
YWxjb21tLmNvbS8lN0VwcmVzbmljay8+DQpRdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAr
MSAoODU4KTY1MS00NDc4DQo=

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7fQ0Kc3Bh
bi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hw
RGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0
O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46
NzAuODVwdCA3MC44NXB0IDcwLjg1cHQgNzAuODVwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFb
ZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0i
ZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91
dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IklUIiBsaW5rPSJibHVl
IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5IaSBQZXRlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTom
cXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlRoaXMgaXMgYW4g4oCcaW5oZXJpdGFuY2XigJ0gZnJvbSBHTVBMUywgd2hlcmUgc3VwcG9ydGlu
ZyBhIHNpbmdsZSBwcmlvcml0eSBlcXVhbHMgbm90IHN1cHBvcnRpbmcgcHJpb3JpdGllcy4gSWYg
eW91IGRvbuKAmXQgd2FudCB0byBzdXBwb3J0DQogcHJpb3JpdGllcyB5b3UgZG9u4oCZdCB3YW50
IHlvdXIgdHJhZmZpYyB0byBiZSBwcmVlbXB0ZWTigKZoZW5jZSBwcmlvcml0eSAwLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+Jmd0O1dlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hv
dWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBwcm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRo
aW5nIGFib3V0IGxvY2FsIGNvbmZpZ3VyYXRpb25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBv
biB0aGF0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlRoYW5rczxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkRhbmllbGUmbmJzcDsNCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
IGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4w
cHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPiBQZXRlIFJlc25pY2sgW21haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tXQ0KPGJy
Pg0KPGI+U2VudDo8L2I+IG1hcnRlZMOsIDcgZmViYnJhaW8gMjAxNyAxODowNTxicj4NCjxiPlRv
OjwvYj4gRGFuaWVsZSBDZWNjYXJlbGxpICZsdDtkYW5pZWxlLmNlY2NhcmVsbGlAZXJpY3Nzb24u
Y29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7amFyaS5hcmtrb0BwaXVoYS5u
ZXQmZ3Q7OyBnZW4tYXJ0QGlldGYub3JnOyBkcmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQt
b3NwZi1leHQuYWxsQGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRmLWNjYW1w
LWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDc8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
Pg0KPGRpdj4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmIj5IaSBEYW5pZWxlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0
eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5UaGFua3MgZm9y
IGFkZHJlc3NpbmcgZXZlcnl0aGluZy4gVGhlcmUncyBvbmx5IG9uZSBpc3N1ZSBsZWZ0IGluIHNl
Y3Rpb24gNC4xLjEgb24gUHJpb3JpdHksIGJlbG93LiBJJ3ZlIHRyaW1tZWQgb3V0IGFsbCB0aGUg
cmVzdC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+T24gNyBGZWIgMjAxNywgYXQgMzozNiwgRGFu
aWVsZSBDZWNjYXJlbGxpIHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNC4wcHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFy
Z2luLWJvdHRvbTozLjc1cHQiPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICM5OTk5OTkgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJn
aW4tbGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xv
cjojOTk5OTk5Ij5JIGdldCB0aGF0IHBhcnQgKCZxdW90O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBs
ZXZlbCBNVVNUIGJlIGFkdmVydGlzZWQmcXVvdDspLiBJdCdzIHRoZSBlbmQgSSBkb24ndCB1bmRl
cnN0YW5kOiAmcXVvdDt0aGF0LCB1bmxlc3Mgb3ZlcnJpZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNI
QUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuJnF1b3Q7IFdoYXQgZG9lcyB0aGF0IG1lYW4/PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+W0RDXSBJ
dCBtZWFucyB0aGF0IGlmIG9ubHkgb25lIHByaW9yaXR5IGlzIHN1cHBvcnRlZCBpdCBoYXMgdG8g
YmUgcHJpb3JpdHkgMC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZiI+U28s
IGxldCBtZSBzZWUgaWYgSSBoYXZlIHRoaXMgcmlnaHQ6IEl0J3MgT0sgdG8gaGF2ZSAwMTEwMDAw
MCBidXQgbm90IDAxMDAwMDAwIG9yIDAwMTAwMDAwPyBJZiBzbywgd2h5IGlzIHRoYXQ/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1s
ZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdDttYXJnaW4t
bGVmdDowY207bWFyZ2luLXJpZ2h0OjBjbTttYXJnaW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjoj
Nzc3Nzc3Ij5Gb3IgYW55IHBhcnRpY3VsYXIgYWRtaW5pc3RyYXRpdmUgcHVycG9zZSBpdCBjb3Vs
ZCBiZSBwb3NzaWJsZSB0byBzZXQgaXQgdG8gYSBkaWZmZXJlbnQgdmFsdWUsIGJ1dCB0aGF0IHNo
b3VsZG7igJl0IGJlIGRvbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PldlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBwcm9i
YWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFib3V0IGxvY2FsIGNvbmZpZ3VyYXRp
b25zLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5wcjxicj4NCi0tIDxicj4NClBldGUgUmVzbmlj
ayA8YSBocmVmPSJodHRwOi8vd3d3LnF1YWxjb21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0
eWxlPSJjb2xvcjojMzk4M0M0Ij5odHRwOi8vd3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9z
cGFuPjwvYT48YnI+DQpRdWFsY29tbSBUZWNobm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2
NTEtNDQ3ODxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_AM2PR07MB0994B673F4904750FC2746B1F0420AM2PR07MB0994eurp_--


From nobody Wed Feb  8 02:18:31 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99EE129590 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 02:18:30 -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 autolearn_force=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 COF705rf4TZf for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 02:18:29 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1C40128E18 for <ietf@ietf.org>; Wed,  8 Feb 2017 02:18:29 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cbPKW-000PEv-Rh for ietf@ietf.org; Wed, 08 Feb 2017 05:18:28 -0500
Date: Wed, 08 Feb 2017 05:18:22 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <291B1050C3EE53B9DB4D8BF4@PSB>
In-Reply-To: <20170208051311.GP28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D_10tO1dZVdZlJrdPyxYyWbx03I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 10:18:31 -0000

--On Wednesday, February 8, 2017 05:13 +0000 Viktor Dukhovni
<ietf-dane@dukhovni.org> wrote:

>...
> I am asking the author to remove that dependency, leaving
> construction of the normal form of the reference identifier to
> the application rather than the X.509 stack.  If he is
> unsuccessful, and there is a fundamental requirement for X.509
> certificate validation code to become IDNA aware, that'd be a
> major barrier to widespread support for this specification.

As you and others have pointed out, SMTPUTF8 is deploying rather
slowly.   That should not be a surprise to anyone who
participated in the WG discussions and understands the issues --
there are a complex sequencing and support tradeoffs involved
although with a number of problems some would describe as
involving "chicken and egg" relationships and others would claim
would benefit from a flag day.

So, as I understand it, you want to shift the issues to the
application in order to get more rapid deployment.  I prefer to
keep the decisions, including a single canonical form, bound to
the X.509 certificate because I think, especially given the
security implications of either false positives or false
negatives, that getting implementations right (and consistent)
is more important than getting quick deployment.   A preference
for "right" over "quick" is particularly important where IDNs
are concerned given the number of inconsistent implementations
of things claiming to be IDNA in the wild.

best,
   john




From nobody Wed Feb  8 04:31:11 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73696129A04 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 04:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xO_nGHEUygzu for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 04:31:05 -0800 (PST)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c: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 E0DF9128E18 for <ietf@ietf.org>; Wed,  8 Feb 2017 04:31:04 -0800 (PST)
Received: by mail-wm0-x230.google.com with SMTP id r141so185156486wmg.1 for <ietf@ietf.org>; Wed, 08 Feb 2017 04:31:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=LwDgrJGQ+kH1QTxJnMZiIzUp5zyfao20oFw9nMa7WLo=; b=kNt0pfyHVXO4ZWE3b6gef0zNIoQ9lXaM1DOZ2MV9p6u7zhapRUMqgGW8PQiPJyqQZ4 FK/TyqKq5dFL5Tb7ew87HTmSg4afxPt2cLQ+FgcoxoM09Lc1PgnntAWBNK04SDC2M4tn S0Wwxmks9N0NYfUZQpjmia4XR/YxB+4o2pcyY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=LwDgrJGQ+kH1QTxJnMZiIzUp5zyfao20oFw9nMa7WLo=; b=LyLUuxC4pK7kQcPMvPxQjK3bw9se3hC1lpfcjCAyoYxwMG79eOblXUbGBeBvgxeWkT PGhHHOqHEwzquDKJP/hLV8BCRKYmXFcYVFxahNBTyhxm01zbsRrYeETdbMuFUQ6mxxsl 1H0K0KCU3B2YBoE6LiofFnMDg2ZOw2wov16/aw4J7GEQmJxPyfbGFOokyfKbYh/JvOhQ sWsriUb1HhKkjtFQKJN3seC/WLvCa3dVC2azPu66Uhygo3P/VRL9dTPBub/+b0kliMX/ Fua5wcjCZHGvmQ9cNZ3Nb3eMBqCWEjU4R5Ei8TgkGMVoKqqY33ieAauK/nyNUYXgw6Ku TJhA==
X-Gm-Message-State: AMke39myhMiW7iG0WBTkaAcH9fx5vhNhtjM2lSrCKLlyyY03dSFhhdAth5kzfg4FJIa1kV5XCHq6L3uDnRXDTtA6
X-Received: by 10.28.191.79 with SMTP id p76mr16948651wmf.21.1486557063415; Wed, 08 Feb 2017 04:31:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.136.199 with HTTP; Wed, 8 Feb 2017 04:31:02 -0800 (PST)
In-Reply-To: <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net> <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net> <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com> <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com>
From: Dave Cridland <dave@cridland.net>
Date: Wed, 8 Feb 2017 12:31:02 +0000
Message-ID: <CAKHUCzxgv2UO99UfSvgSZOEkgnu722GiBCskP_DfZio5WDzBfg@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z5074iW2g9S6KUc2LXVaLvldT6w>
Cc: jmap@ietf.org, Neil Jenkins <neilj@fastmail.com>, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 12:31:07 -0000

On 8 February 2017 at 07:26, Yoav Nir <ynir.ietf@gmail.com> wrote:
> That=E2=80=99s good to know. I=E2=80=99m wondering if implementing a gene=
ric email client
> (rather than a specific =E2=80=9Cgmail=E2=80=9D or =E2=80=9Clive=E2=80=9D=
 client) isn=E2=80=99t becoming ever
> harder. With so many older and newer services, a client has to support po=
p3,
> imap, smtp, EWS, ActiveSync, and maybe a few of the others you mentioned.
> This effort proposes to add yet another one.
>

It does; but as someone who has had to implement IMAP from both sides,
I think it's worthwhile to revisit IMAP's space and look at a
green-field rewrite.

JMAP works well particularly for web-based, client-centric
development; that's a space I've seen a lot of, and particularly a
considerable amount of more innovative deployments of existing
protocol work (such as XMPP, which is also very web-friendly).

I would suspect that if we can pull JMAP together and see reasonable
deployment, we'll see an increasing demand for its use for all manner
of things we have yet to think of.

It seems to be well-thought through for mobile, too.

While I agree, with feeling, that writing a generic desktop MUA has
become increasingly hard in recent years, I also note that this isn't
what consumers seem to want either. Consumers respond much better to
Web and/or Mobile - and JMAP makes it considerably simpler to write
either.

TL;DR: Yes.

Dave.


From nobody Wed Feb  8 05:35:25 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E61B0129A38; Wed,  8 Feb 2017 05:35:15 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o7RnXlMSy-UY; Wed,  8 Feb 2017 05:35:14 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 811D0129A21; Wed,  8 Feb 2017 05:35:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486560913; d=isode.com; s=june2016; i=@isode.com; bh=vO6lDZmEov1k+sdWXvpEYmOBvYU6jdAVFLd+udMlg5I=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=drMEImk78QlDE4RSNCWkhM8UwrZcw+jkHVlZHtkGaPGJtbnWj0RsoOZa0vq6z+lZCg84n2 SRruXNGx0Os8rDE2IllzrvBxofXwXI4hGRNsvK7JZ8qKgRMcmrUemLRe+RaBQt0gZDRZYd J7NjnqGx8wRF2ReilbzPd7lIL8Xq1FA=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJsekAAY1zyf@statler.isode.com>; Wed, 8 Feb 2017 13:35:13 +0000
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: dcrocker@bbiw.net
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <125d54fa-eb60-cf14-db93-0c5602be58ad@isode.com>
Date: Wed, 8 Feb 2017 13:34:55 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3g9GGUyiyaJStXwoytvOwIgw7Lk>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:35:16 -0000

Hi Dave,


On 06/02/2017 20:11, Dave Crocker wrote:
> Alexey, thanks for the quick followup.
>
> inline...
>
> On 2/6/2017 11:41 AM, Alexey Melnikov wrote:

> >> There also needs to be clarity about the relationship between the JSON
> >> encodings and the encodings in 'native' Internet Mail.
>> See drafts (and above).
>
> Drafts?  What drafts?  Perhaps you mean:
>
>    https://tools.ietf.org/html/draft-jenkins-jmap
>
> Except that no draft is cited in the charter.

I realized that I accidentally deleted an important sentence from the 
Charter while doing editing. One of the paragraphs should have read:

The work of this group is limited to developing a protocol for a client
synchronising data with a server. The work will be based on
draft-jenkins-jmap and draft-jenkins-jmapmail. Any server-to-server issues
are out of scope for this working group.
New end-to-end encryption mechanisms are out of scope, but the work should
consider how to integrate with existing standards such as S/MIME and 
OpenPGP.

Best Regards,
Alexey


From nobody Wed Feb  8 05:36:36 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6715D129A4F; Wed,  8 Feb 2017 05:36:31 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 tBLFKVG927mS; Wed,  8 Feb 2017 05:36:28 -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 22FA9129536; Wed,  8 Feb 2017 05:36:28 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 949CC80F86; Wed,  8 Feb 2017 14:36:21 +0100 (CET)
From: Fernando Gont <fgont@si6networks.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org, Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
X-Enigmail-Draft-Status: N1110
Message-ID: <f5644482-698b-9b9a-962f-3b4512b72172@si6networks.com>
Date: Wed, 8 Feb 2017 10:07:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Yb-jbeBUKMJZp7gQnUXW4ByrB7g>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:36:31 -0000

On 02/07/2017 05:06 PM, otroan@employees.org wrote:
>
>>> Could you expand on your view of how this pertains to advancing
>>> RFC1981?
>>> 
>> It's called last call input. My input is that this document needs
>> to be more realistic in noting that, for all intents, ICMP-based
>> MTU discovery isn't viable and that other methods need to be
>> *expected*, not just that they're available.
> 
> Right, but if you are correct that ICMP-based MTU discovery is not
> viable then this document should not be advanced. At the same time
> for many protocols we have nothing else. An operator can break any
> protocol if that's their policy. And that's the breakage we're
> talking about here, not any issues with the protocol specification.
> 
> There is a philosophical aspect of this. (Which I'm not the best
> person to represent as I skipped my University studies in philosophy
> and used the student loan to buy a motorcycle... (and only read the
> art of motorcycle maintenance years later) ) This is a tussle. The
> IETF specifies protocols under the assumption that operators treat
> those protocols largely as specified. The 5-10% failure of PMTUD
> messages may be caused by misconfiguration, misunderstanding or
> mis-intent... Many of our protocols are suffering from the same fate.
> Should the IETF adjust all its protocols to be as middlebox friendly
> as possible? You can make this argument about IPv6 fragments, any
> packet with IPv6 extension headers, IPv4 fragments. Or anything but
> TCP port 443/80 and UDP port 53 for that matter. Are we as the IETF
> going to continue standardising protocols to work as best as they
> possible can, ignoring protocol abuse, or are we going to bend over
> and do whatever it takes to make it work for those 5-10% who've
> actively broken the protocol? What about the 90-90% where the
> protocols work as expected?

There are two things to note here:

1) the folk breaking PMTUD is probably not the guy suffering from that
breakage. So the had that "bad-hevaed" nodes hurt the "well behaved"
nodes (i.e., you cannot claim "you're shooting your own foot).

2) Being an engineering group I would expect our protocols to work in
the real world -- that's the point of engineering: solving problems.  At
the end of the day, you can build stuff that works, or complain that way
too many people are doing dumb things (for some meaning of "dumb"). --
But the later will not make protocols work, nor solve problems.

In that sense, I agree with Joe, and Randy Bush here.

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  8 05:39:56 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2371D129A59; Wed,  8 Feb 2017 05:39:39 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tIhBRsBp4vjX; Wed,  8 Feb 2017 05:39:37 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id A16AF129A4F; Wed,  8 Feb 2017 05:39:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486561176; d=isode.com; s=june2016; i=@isode.com; bh=ySc+N2mjFStBNxbV36zhF2B+70IKXZoQLLMuVWIxJ2Q=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Df4YdHNvtugxgGzrL8MF+PXEi/S3iqJ2iJWFNUVE50q4hgNSUHYEtVw6Y9ExnlwMu88ORi OwKcPLpaG7L3yxV1BoRFpysjeQGEr2yY0LSCwm98P7Fy7BVxyX252t8Q5dG5a5JeixXQIU wjHYUVQ4RpoJe4F1+kD3M/lFm3/WeV8=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJsfmAAY1zWv@statler.isode.com>; Wed, 8 Feb 2017 13:39:36 +0000
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: dcrocker@bbiw.net
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <03152892-3987-145c-8206-e3ccfe3a7510@isode.com>
Date: Wed, 8 Feb 2017 13:39:19 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TiddtUZFnFjZavH9-wGOO1ChLqY>
Cc: jmap@ietf.org, ietf@ietf.org, iesg <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:39:39 -0000

Dave,


On 06/02/2017 20:11, Dave Crocker wrote:
> Alexey, thanks for the quick followup.
>
> inline...
>
> On 2/6/2017 11:41 AM, Alexey Melnikov wrote:
>>>      Working groups need task serialization.  So I'll suggest that
>>> having an effort to standardize an JSON representation of an
>>> RFC5322/MIME object would be the highest-leverage first task.
>> I don't think there is intent to specify full mapping of RFC5322/MIME to
>> JSON. IMAP has BODYSTRUCTURE element that contains parsed representation
>> of message structure and most commonly used header fields for different
>> body parts. The intent is to do the same here.
>> Additionally, it is still possible to retrieve full RFC5322/MIME
>> payloads over JMAP.
>
> This highlights the need to have far more clarity about what specific 
> work is to be done and what is not.  The existing text has some 
> generic out-of-scope text, but nothing as frankly useful as your above 
> comment. Given that comment, I can't text what parts of the resulting 
> jmap service will use 'native' Internet Mail technical details and 
> what parts will be new-for-JSON.
>
>
>> I have tried to reflect your comments in the Charter, but I struggled a
>> bit. If you can suggest how to make the above clearer, that would be
>> much appreciated.
>
> I make a point of offering candidate text when I think I understand 
> the context and needs well enough.  Unfortunately I don't have that 
> here. Hence, questions and general suggestions is the best I can 
> offer.  Sorry.
>
>
>>> Adding to this:
>>>
>>> JSON is a meta-format.  It isn't a 'protocol'.  Something encoded in
>>> JSON is a format, not a protocol.  Hence one of the tasks apparently
>>> being chartered would be to create a new message access protocol,
>>> encoded in JSON.  While that might be worth doing, there needs to be
>>> clarity that this is more than a 'representation'.
>> No, it is a representation. See above.
>
> As soon as one says that the task is client/server interaction, one is 
> declaring the goal of a protocol.  So it is more than just a format 
> (representation.)
>
>
> >> There also needs to be clarity about the relationship between the JSON
> >> encodings and the encodings in 'native' Internet Mail.
>> See drafts (and above).
>
> Drafts?  What drafts?  Perhaps you mean:
>
>    https://tools.ietf.org/html/draft-jenkins-jmap
>
> Except that no draft is cited in the charter.
>
>
>>>> The use of multiple protocols
>>>> to perform actions within a single application creates significant
>>>> support challenges, as users may get a variety of partial failure 
>>>> modes
>>>> (for example, can receive email, but can not send new messages).
>>>> This is further exacerbated if the different protocols are
>>>> authenticated separately.
>>>
>>> From my November comments:
>>>
>>>      There is no justification given for this approach.  For each
>>> activity, there needs to be a clear and solid need documented, based
>>> on actual industry activities or at least industry statements.
>>> Besides clarifying /what/ needs doing, it should serve to indicate
>>> likely industry uptake after the work is done.
>>
>> I am not sure what kind of justification is needed. This is a clear
>> deployment problem.
>
> As I said, there was a year-long, serious and diligent debate about 
> this in the IETF and it came to a different conclusion.  So it's not 
> nearly as 'clear' as you are asserting.
>
>
>>> Adding to this:
>>>
>>> The IETF email technical community looked at the question of making
>>> email submission part of IMAP or keeping it separate.  It took an
>>> entire year to debate this point extensively and (imo) constructively,
>>> and decided to keep them separate.  The current charter draft appears
>>> to have decided otherwise, but offers only the barest of
>>> justifications, which I suspect has not factored in the earlier
>>> evaluation.
>> There was a followup discussion about doing an IMAP extension for
>> submission and how it should look like to remain compatible with SMTP
>> Submission. I don't think this is an attempt to just ignore earlier
>> discussions.
>
> Discussion is different than deployment.  The fact that it isn't used 
> now suggests that the benefit(s) you are asserting aren't as clear-cut 
> as is being implied here.  To the extent that the current proposal 
> does indeed represent a consideration of the prior, extended IETF work 
> in this realm, the charter should indicate the basis for making a 
> different choice here, in terms of the points considered earlier.
>
>
>
>>>> The working group will deliver the following:
>>>>
>>>> - A problem statement detailing the deployment environment and
>>>>   situations that motivate work on a new protocol for client to
>>>>   server email synchronisation.  The working group may choose
>>>>   not to publish this as an RFC.
>>>>
>>>> - A document describing an extensible protocol and data structures, 
>>>> with
>>>>   support for flood control and batched operations, and operating over
>>>>   a stateless connection such as HTTPS.
>>>
>>> 'flood control'?  what does this mean, since I assume the target
>>> protocol won't be using a flooding algorithm.  If it really means
>>> 'congestion control', that's not typically part of an application
>>> protocol, so why would it be an issue here?
>>>
>>> From the November comments
>>>
>>>      Since client/server email access typically benefits from having
>>> the server retain state about the client's activities, I can't tell
>>> whether this actually means stateless lower-level transport or whether
>>> it really does mean a stateless email protocol.
>>
>> Stateless lower level transport. The addition of "such as HTTPS" was
>> trying to make this clearer.
>
> Didn't succeed, given that HTTP runs over TCP.

The protocol is HTTP version agnostic, for the most part.
The original thought was that it is less stateful than IMAP, which 
requires a mailbox to be opened for some operation. But the server still 
needs to maintain state (for example to track flag modifications). So 
saying "stateless" is incorrect, so I deleted it in 2 places in the Charter.

  [...]

>>> Adding to this:
>>>
>>>    HTTP/HTTPS are not stateless, since they are connection-based.
>> Yeah, I struggled with this a bit. Each request/response can be sent on
>> a separate connection and it is stateless in that sense.
>
> In other words, jmap will be stateless.  That's what the charter 
> should say.
>
> ...Except that that seems odd, since it means that every exchange 
> would have to self-identify and self-authorize.
True.
> I suspect that's not what's going to be defined.  So, really, it isn't 
> obvious to me at all what will be stateless.

As you pointed out, saying stateless is not really correct.

Best Regards,
Alexey


From nobody Wed Feb  8 05:52:00 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18E85129A9D; Wed,  8 Feb 2017 05:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yNysvL6APz9o; Wed,  8 Feb 2017 05:51:57 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id D0C48129A98; Wed,  8 Feb 2017 05:51:57 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 08 Feb 2017 13:51:57 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id D9B2ED788E; Wed,  8 Feb 2017 05:51:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=Yc7AspPepYgtbcfh+2At4YyR4i8=; b= DI2sKIwOj0GEofTKdz0SlCTtpVVJxknULcg8LM6ju68X/eogQuiFn4YInTStHSpZ Xffa41jnIb7VRV+Kkyigtae4wLUPh1DKCvmgRcJ7eSrPBKyvUOD+M9l9OfbTD1UL yg79WEPIf8BuQFQiInu27h4sBFD8kP0oKuz+DYFv4Gc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=sa6Oeo8CkHnFwwuTjXda7oC CV6nkYSwtCneZfY/YoILGfbEUpJvJ7UO4meEp6w2tTmV+ZQRZ5xXUVumYK5nt/9i zulyJ4haDwEFaI+AGJmmlm/qjrFNgLCnrjCQXmIBhNAmARFu/rlp9mj9SlATynyq t+ByEvC5/yib90oRUmWw=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 7C403D788D; Wed,  8 Feb 2017 05:51:56 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D108D86B89F8; Wed,  8 Feb 2017 14:51:53 +0100 (CET)
From: otroan@employees.org
Message-Id: <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_5B2ACA68-EA98-405C-B185-F42866D0A3CC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Wed, 8 Feb 2017 14:51:52 +0100
In-Reply-To: <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wFHKhfAurxB1kUuOaKZLVZXH83I>
Cc: 6man@ietf.org, draft-ietf-6man-rfc2460bis@tools.ietf.org, IETF Discussion <ietf@ietf.org>, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:51:59 -0000

--Apple-Mail=_5B2ACA68-EA98-405C-B185-F42866D0A3CC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Pete,

> After reading the replies, I wonder if you could amend your summary =
with one point in particular:
>=20
> On 4 Feb 2017, at 2:32, otroan@employees.org wrote:
>=20
> There were three main positions argued in the working group.
>=20
> 1) Ban header insertion outright.
> 2) Describe the problems with header insertion.
> 3) No changes to RFC2460 text.
>=20
> What did you see as the objections to going with (1) (which I presume =
to be the equivalent of Brian's proposed text)? Why was it that people =
thought the protocol could not be clarified to say that? And was your =
assessment that those arguments were correct, or that they simply were =
not addressed by the WG? I've seen several people argue on this list =
that (1) was always the intent of the protocol, and that damage occurs =
if you don't follow that directive. I haven't seen anyone here argue =
otherwise. Could you summarize?

I can try. It has been difficult to distill the essence out of all the =
mailing list discussions.
This is _my_ take of the discussion and arguments as I understood them. =
Please chime in with corrections.

The arguments of what would break are correct. The counter-arguments =
given would be that this is done within a controlled domain and the =
potential for damage could be controlled.

The discussion went something like (paraphrasing):

 - Inserting headers will break Path MTU discovery, AH and may result in =
unsuspecting hosts receiving ICMP error messages.
 - We will do this in a controlled domain only.
 - Even if you can guarantee it will not leak, it is not appropriate to =
specify that in the core IPv6 specification
 - We don't need that, we just need 2460 not to ban it. IPv6 is used in =
many networks not only the capital I Internet.

There was also quite a bit of discussion on the intent of the original =
authors. I don't know how much value it is correct to give that =
argument. "This is what I intended, but not what I wrote...". Given that =
this is in any case the output of the IETF and not two individual =
authors.

1) Ban header insertion outright.

Objections:
a)  There are proposals wanting to insert headers:
   - draft-ietf-6man-segment-routing-header
   - draft-brockners-inband-oam-transport
   - Just now: draft-francois-dots-ipv6-signal-option-01

i) Out of scope: Argue the point of header insertion or alternatives in =
the context of those proposals, not in the context of the core IPv6 =
specification. Do not try to make a preemptive strike in the core =
specification.

ii) Use encapsulation alternative has problems. In e.g. inband-oam some =
meta-data is attached to a packet on ingress into a domain and removed =
at egress of the domain. The ingress doesn't necessarily know the =
egress, normal destination routing is supposed to happen. That is hard =
to achieve with a encapsulation solution.

iii) Use encapsulation alternative has problems 2. A packet with =
extension headers would be processed normally by an unmodified end host,
while an encapsulated packet would not.

b) RFC2460 is already clear and no clarification is needed. No =
interoperability issue has been shown caused by this perceived =
ambiguity.

2) Describe the problems with header insertion.

Objections:
a) The list of problems with header insertion can never be complete. It =
might be misconstrued as the only set of problems required to be solved =
to allow header insertion.

b) Speculating about something we don't know how to do (header =
insertion) is not appropriate when bringing the specification to =
internet standard.

c) Leaves the ambiguity in place.

3) No changes to RFC2460 text.

Objections:
a) Leaves the ambiguity in place.

There was hard to find consensus on either of the alternatives. As the =
poll shows there was a clear preference (if people couldn't get their =
first choice) to describe the problem, over banning it, or over saying =
nothing.

Best regards,
Ole


--Apple-Mail=_5B2ACA68-EA98-405C-B185-F42866D0A3CC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmyJ5AAoJEL7aWKiYQt92AlEP/2tQYymlUBIIRAm8L6MObI0K
JO24LoX3My++eEwpmDsP6y74GYCZtJNooSsaWI6uGyih3vrSwBXIarEMsfCsCLn1
TJN07DIX9a7uqNuBhJlctDkT4eITUY2uc9waO8ywSmazLviQhrp+pyU6w4TnxlUM
BkxxrtrNF597F6FNtAerpEONvLJrCTMaeTZrI1NQOjb5hhmXTn35Zi0JS+irBKcC
MdjKKPBuFLvMB6NZaPdDtsq6lrW0n3zCqmH1Q9/p5qomCKWOZAR9BNy2OGqQXyWN
KDSk66THNrZUuZ3rx4qEZBv1x8EQBjmNEeVKhkJXp3aJK/dUz6OYeqbIQoD0bNSo
0oG3kPFQqSAJ90P3S0GY7PjWUmn+WBQ68Pp4ivmL9J3WT4FPyzu+k0B2O7y2lpPL
bkF2q8v/9xm74UGPRlk8CyJVb5+wLt6944RlZaSL3FqHrdMULgEtZl3Dg05haPQ/
GZkJZQjitKQ6bILF+uLbFDmIe44iY2ugJw5I+NeDH08RU2jYUATeXHhqQujFXgNT
oSs6JNZ6DD65fAXIlr/NKGtatiYl5FsyBUCwOC8ZQI6HN9Sifw2eFIGMlgnUfqQA
hgJrM6AP/nWFD9JlSyWcZUvwzV2tvnYvvOBj+3v2q70RVqqwZ62JhJ4xNNBM5kPD
mBstKAnf9D6bChvG3fG8
=VKYA
-----END PGP SIGNATURE-----

--Apple-Mail=_5B2ACA68-EA98-405C-B185-F42866D0A3CC--


From nobody Wed Feb  8 05:52:33 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D180129A98 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 05:52:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xwKLzA9w4FFc for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 05:52:30 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 9A988129AA3 for <ietf@ietf.org>; Wed,  8 Feb 2017 05:52:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486561937; d=isode.com; s=june2016; i=@isode.com; bh=yqgb8NdI0TG+dAAZp2mBI4cuUSozVza/N9g0r6c5AxY=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=MrWXiTTr8QXRkBqW79V83+JEVQtT6BYhfa/HxVFB/QjwmrJHdh4NlS7koJ/HUm50rjBhRg 71eDI9nZR5HSSKEQwnAlgNl1nW8l82Obptig9wTtrf3G5ba1R6THBRMurzcaFUX7Z897+j qMgsUHEWlOzcIhqRrvMeKPhnXmPSVX0=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WJsikQA6w2cd@waldorf.isode.com>; Wed, 8 Feb 2017 13:52:17 +0000
Subject: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com>
To: "ietf@ietf.org" <ietf@ietf.org>
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Forwarded-Message-Id: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com>
Message-ID: <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com>
Date: Wed, 8 Feb 2017 13:52:00 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------3E365E928797EF858A491BE5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vGLq-A-WEQaSjQO6AclGpGs8zF4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:52:31 -0000

This is a multi-part message in MIME format.
--------------3E365E928797EF858A491BE5
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Forwarding here, because Arnt only replied to the JMAP mailing list and 
my reply to him went to the same place.


-------- Forwarded Message --------
Subject: 	Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol 
(jmap) - reducing configuration complexity
Date: 	Wed, 8 Feb 2017 13:48:54 +0000
From: 	Alexey Melnikov <alexey.melnikov@isode.com>
To: 	Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>, jmap@ietf.org



On 08/02/2017 12:56, Arnt Gulbrandsen wrote:

> Randy Bush writes:
>> yet another protocol that requires a flag day.  that has worked out
>> so well for ipv6.
>
> JMAP does not, AFAICT, require a flag day, any more than IMAP required
> a flag day over POP. If Fastmail's deployment of JMAP-in-spe was
> noticed by its customers, the noise certainly hasn't been loud enough
> that I've heard about it.

Agreed. JMAP and IMAP are likely to co-exist for long time.


--------------3E365E928797EF858A491BE5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=windows-1252">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Forwarding here, because Arnt only replied to the JMAP mailing
      list and my reply to him went to the same place.<br>
    </p>
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol
              (jmap) - reducing configuration complexity</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Wed, 8 Feb 2017 13:48:54 +0000</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Alexey Melnikov <a class="moz-txt-link-rfc2396E" href="mailto:alexey.melnikov@isode.com">&lt;alexey.melnikov@isode.com&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td>Arnt Gulbrandsen <a class="moz-txt-link-rfc2396E" href="mailto:arnt@gulbrandsen.priv.no">&lt;arnt@gulbrandsen.priv.no&gt;</a>,
              <a class="moz-txt-link-abbreviated" href="mailto:jmap@ietf.org">jmap@ietf.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>On 08/02/2017 12:56, Arnt Gulbrandsen wrote:

&gt; Randy Bush writes:
&gt;&gt; yet another protocol that requires a flag day.  that has worked out
&gt;&gt; so well for ipv6.
&gt;
&gt; JMAP does not, AFAICT, require a flag day, any more than IMAP required 
&gt; a flag day over POP. If Fastmail's deployment of JMAP-in-spe was 
&gt; noticed by its customers, the noise certainly hasn't been loud enough 
&gt; that I've heard about it.

Agreed. JMAP and IMAP are likely to co-exist for long time.

</pre>
    </div>
  </body>
</html>

--------------3E365E928797EF858A491BE5--


From nobody Wed Feb  8 05:55:35 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 747BA129A83; Wed,  8 Feb 2017 05:55:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r3qFiWDVSL5R; Wed,  8 Feb 2017 05:55:32 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 7682D1293EB; Wed,  8 Feb 2017 05:55:32 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 08 Feb 2017 13:55:32 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 367F9D788A; Wed,  8 Feb 2017 05:55:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=+g0OTkJ/Z3PEItOoCbTYaa4ID5A=; b= EeNNw3w/Xgiy/BUapnBOb7fmG73qgpRmdb01KIpbdlB6xIq3z63RsDxwOzmjoiqt k/G7GIx70ujSwrYC45XUvkYsZ30GGlNn394LYfMRZMquKZJUcSS7Tj4dYT8N8Z8W rT1UZlP5x73xRD+uFhnQoMNkHjTUSL89gakCioQZXbs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=YcIwomg9TPK/SDpzF7tMf0/ +Du44N2h/49Ef7nFEovuqXoG9vpItsVK6snh2NGzbc3nC/0ZeJcdsmNpRDWP57qo aulEFTJJbVCWMBpaFQ6bHhchgqoASGvKqvnP7AAE3iOyRFHg5HSmUyx3yU/tmSXP CzPUUANK/7IrEPgPVVhY=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 0ADE1D788D; Wed,  8 Feb 2017 05:55:32 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8144286B90E7; Wed,  8 Feb 2017 14:55:30 +0100 (CET)
From: otroan@employees.org
Message-Id: <F731A0EC-F402-4847-BCE5-89ED6F08FE45@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_18E44E21-06BF-4B44-9426-FF2BA12DFF61"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Wed, 8 Feb 2017 14:55:30 +0100
In-Reply-To: <6e3ff88d-1954-3dbb-1bd9-aa262ea79192@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <6e3ff88d-1954-3dbb-1bd9-aa262ea79192@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P4si0b-4q6-1EayS13JW48kvwSw>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 13:55:34 -0000

--Apple-Mail=_18E44E21-06BF-4B44-9426-FF2BA12DFF61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

> Because if we did, the loophole for people to violate the standard =
would
> disappear (talk about Segment Routing).

There is nothing stopping a future IETF from publishing a document =
specifying header insertion, even if 2460bis where to ban it.

Best regards,
Ole


--Apple-Mail=_18E44E21-06BF-4B44-9426-FF2BA12DFF61
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYmyNSAAoJEL7aWKiYQt924boP/0Oj4DCdm18JxXfP+9jSjo9w
3H+0jM/dbW1mDfpFNvyEYVHP7gUKKdX14h25WBCPwMmP5NIZE8ZCSGa8f6E69v5g
ZBsCFV2f89yG9P6ABS+35inko5OGR24pz6g6G+QMYgj5NTY0IFdfFgvOOsDhV8//
1rDBiGGDS69p8gtg8C0qNnezRC+b/g5oMywKfc4lw+PRRlrKMU8AkN1RcpwkMH/M
j8vb6gkRR8LjPeHHSQCNj49s3xDm/PGtzDr0qzE6d8fQTzqU9cugar8fB8I5ndwL
RXjJYA2qtH0mJ8lRW9IVpMcWJ/kJ6My2Y5/Hpn31G5gaHGiTwRZBSnG7K7tW9FiG
iBNTJ67h2d7CATzYVy63lTYlUhowXQv/IX9qE40v6fhYUhBwackvQPtp57kN7TOl
BojqYjtH8/qMVGb8tXt1vmu4K5tFHSa/NjlE2Z6eIaeU/SLxTUN0DO7kXd7mLkXl
EXAKJ21ZrdiRrqIMw5xug6RivN/7X0KDPhLmXrY+IXDYwSojHzQyZkvdQ9yZ0MY2
w+hlzqUzObEmROU6Sr2iPwRFci9bKUAzOeS/GS+dHy0w0Wltmn8GB5KMiccvRaga
o2966qkHVFoAdr5wp5dLYWTtJfKcnT1D+ivSekebz+vKeR4Fh68DE7lHUQYroT1T
ElwBkKu4A4xJn/N1r1Ga
=el5k
-----END PGP SIGNATURE-----

--Apple-Mail=_18E44E21-06BF-4B44-9426-FF2BA12DFF61--


From nobody Wed Feb  8 06:23:17 2017
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54161129B14 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:23:16 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yitter.info header.b=hn7Rq26z; dkim=pass (1024-bit key) header.d=yitter.info header.b=AfJRKf7m
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hKCTx1kgtUVh for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:23:15 -0800 (PST)
Received: from mx4.yitter.info (mx4.yitter.info [159.203.56.111]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CF54129AE7 for <ietf@ietf.org>; Wed,  8 Feb 2017 06:23:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id BF2ABBD554 for <ietf@ietf.org>; Wed,  8 Feb 2017 14:22:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1486563764; bh=qWgMfhExooknikK+82BzMBrr0jxKinq24aItckG9soc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=hn7Rq26z8ci8kszUuC5b+ngIizqZlKT7NA8gNtTIpeln5+YlvjQNVCfvg+FuInPBt gS0fQKixcVpmFEgLbIgryAe7drOh6waTOZ3iFtxBzUyj4s0gSUoUNdK88jj9zO7Tiq ma4UfhkI7ZkMWUMb4zp1XEOI/0pZGXzHegH06mCo=
X-Virus-Scanned: Debian amavisd-new at crankycanuck.ca
Received: from mx4.yitter.info ([127.0.0.1]) by localhost (mx4.yitter.info [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHbWifGMrcKu for <ietf@ietf.org>; Wed,  8 Feb 2017 14:22:43 +0000 (UTC)
Date: Wed, 8 Feb 2017 09:22:41 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1486563763; bh=qWgMfhExooknikK+82BzMBrr0jxKinq24aItckG9soc=; h=Date:From:To:Subject:References:In-Reply-To:From; b=AfJRKf7mYATgsWpSRl2e1ILBTyUHQfBrDUvBT/ImK00X0fj6KaaSDFuw4xh8/vW3/ lLmgtofZ+o/g1CJkz5pOd78SsbeQ/CNvz/+Uj1YxCkVZHbGd4rZTmK+zkn+m0vOVV7 dr1zNOa9EapxcHRtejxylpm+w1xbarokCclCm3hE=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <20170208142241.GB84460@mx4.yitter.info>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Qc7g6iisIC82ZJLiyo_-5OdzUks>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:23:16 -0000

On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov wrote:
> 
> Agreed. JMAP and IMAP are likely to co-exist for long time.
> 

Isn't that exactly the complaint?  Something like, "Long periods of
co-existence need to have lots of benefits or an existential one, or
else they're not a good idea."

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Feb  8 06:25:42 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37A61129AE5; Wed,  8 Feb 2017 06:25:40 -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 autolearn_force=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 Vtluy5X68gLQ; Wed,  8 Feb 2017 06:25:39 -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 F1BB8129AF7; Wed,  8 Feb 2017 06:25:38 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 0034D806B1; Wed,  8 Feb 2017 15:25:33 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <6e3ff88d-1954-3dbb-1bd9-aa262ea79192@si6networks.com> <F731A0EC-F402-4847-BCE5-89ED6F08FE45@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <330f0b5e-bc67-9f42-fd4c-8de7ce77f52d@si6networks.com>
Date: Wed, 8 Feb 2017 11:10:01 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <F731A0EC-F402-4847-BCE5-89ED6F08FE45@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h_MkJL2M9BBsTl9t4yF91K_4OQ8>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, ietf@ietf.org, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:25:40 -0000

On 02/08/2017 10:55 AM, otroan@employees.org wrote:
> Fernando,
> 
>> Because if we did, the loophole for people to violate the standard
>> would disappear (talk about Segment Routing).
> 
> There is nothing stopping a future IETF from publishing a document
> specifying header insertion, even if 2460bis where to ban it.

There's a "small" difference: If the standard clearly states that header
insertion is forbidden, then, a proposal to insert EHs would need to
update the corresponding standard.

Since RFC2460 is being moved to (full) Standard, that would not be minor.

I guess we all know what, and why we even got to rather ridiculous
arguments of the form "we can do EH insertion because RFC2460 does not
prohibit it"   (well, yes, :-)  RFC2460 does not prohibit that upon
receipt of an IPv6 packet, a router drops the IPv6 packet, and forwards
a TCP packet instead... )

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  8 06:25:54 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124C8129B1A; Wed,  8 Feb 2017 06:25:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 iN_rAq3TRMwv; Wed,  8 Feb 2017 06:25: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 F0FCC129B20; Wed,  8 Feb 2017 06:25:45 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 4726A809C0; Wed,  8 Feb 2017 15:25:40 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, Pete Resnick <presnick@qti.qualcomm.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com>
Date: Wed, 8 Feb 2017 11:25:25 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xhswK_Ep-btKTmWBorJMV9VYTpo>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man@ietf.org, IETF Discussion <ietf@ietf.org>, Stefano Previdi <sprevidi@cisco.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:25:53 -0000

On 02/08/2017 10:51 AM, otroan@employees.org wrote:
>> 
>> There were three main positions argued in the working group.
>> 
>> 1) Ban header insertion outright. 2) Describe the problems with
>> header insertion. 3) No changes to RFC2460 text.
>> 
>> What did you see as the objections to going with (1) (which I
>> presume to be the equivalent of Brian's proposed text)? Why was it
>> that people thought the protocol could not be clarified to say
>> that? And was your assessment that those arguments were correct, or
>> that they simply were not addressed by the WG? I've seen several
>> people argue on this list that (1) was always the intent of the
>> protocol, and that damage occurs if you don't follow that
>> directive. I haven't seen anyone here argue otherwise. Could you
>> summarize?
> 
> I can try. It has been difficult to distill the essence out of all
> the mailing list discussions. This is _my_ take of the discussion and
> arguments as I understood them. Please chime in with corrections.
> 
> The arguments of what would break are correct. The counter-arguments
> given would be that this is done within a controlled domain and the
> potential for damage could be controlled.

There need not be "counter arguments". It was clear to everyone that
IPv6 never allowed EH insertion. If you want to change that, you have to
update RFC2460 (and if you do it before rfc2460bis is published, good
luck with moving it to Standard).

OTOH, if the argument is that you want to break a protocol in your own
environment, in which you can "control the damage"... why do you need an
RFC for that? why should we rubberstamp it?



> The discussion went something like (paraphrasing):
> 
> - Inserting headers will break Path MTU discovery, AH and may result

You miss the most important point: EH insertion was never allowed in
IPv6.  Quite a lot of us find the argument that "we're doing EH
insertion because RFC2460 doesn't explicitly prohibit *insertion*" quite
funny.

I'm not against EH-insertion per se. I'm against what looks like a
procedural hack.

If people want EH insertion, fine: write a proposal that updates
RFC2460, and let's have the discussion. But please do not pretend that
RFC2460 allows EH insertion.



> in unsuspecting hosts receiving ICMP error messages. - We will do
> this in a controlled domain only. - Even if you can guarantee it will
> not leak, it is not appropriate to specify that in the core IPv6
> specification - We don't need that, we just need 2460 not to ban it.
> IPv6 is used in many networks not only the capital I Internet.
> 
> There was also quite a bit of discussion on the intent of the
> original authors. I don't know how much value it is correct to give
> that argument. "This is what I intended, but not what I wrote...".
> Given that this is in any case the output of the IETF and not two
> individual authors.
> 
> 1) Ban header insertion outright.
> 
[...]
> 
> b) RFC2460 is already clear and no clarification is needed. No
> interoperability issue has been shown caused by this perceived
> ambiguity.

RFC2460 already bans EH insertion. Only when SR wa published people
started to argue otherwise.

Given that for some guys there was room for EH insertion, we clearly
need to make the point clear.


> There was hard to find consensus on either of the alternatives. As
> the poll shows there was a clear preference (if people couldn't get
> their first choice) to describe the problem, over banning it, or over
> saying nothing.

Based on the mailing-list discussion, it was quite clear that most of
the folks arguing in favor of "ambiguity" were from the same company
pushing a proposal with EH insertion. That's not a minor datapoint.

Besides, moving a document to Standard with "ambiguity" on an item that
led to 600+ messages discussion at the same group that specifies the
protocol would be really bad.

We're moving RFC2460 to standard. I think it should be able to answer
the very basic question "Is it possible to insert EHs in the middle of
the network?"  -- or, framed in a different way: "is IPv6 and end-to-end
protocol?"

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  8 06:28:16 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88594129B18 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:28:14 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9CBqDnr0Wug4 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:28:09 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 6C0CB129B1E for <ietf@ietf.org>; Wed,  8 Feb 2017 06:28:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486564088; d=isode.com; s=june2016; i=@isode.com; bh=C43+uNZg19yfo4S0BxBLjDakpg6FlNuQ4ECgkdSPUyc=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=gxnDkZJ0MRAnZUP1Nult7/2oe4mefGkiFGHXZ9AtUrOAzkOW7fOg0Jhbud+/pN+zZi5xQC ygrsJsXRQbd6lTj0us7DTFGGWmmnpxxJcEOTzx1zwV5oMbPN6B9RdoIhPS6N0/kQMvlS8Z 8bUwwHKJS8Ja1EttzXxGWKYqiVMV7X8=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WJsq-AA6wymW@waldorf.isode.com>; Wed, 8 Feb 2017 14:28:08 +0000
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com>
Date: Wed, 8 Feb 2017 14:27:50 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <20170208142241.GB84460@mx4.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BSZWVcQ63bRipQGVKmfBpH3YjGw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:28:14 -0000

Hi Andrew,

On 08/02/2017 14:22, Andrew Sullivan wrote:

> On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov wrote:
>> Agreed. JMAP and IMAP are likely to co-exist for long time.
> Isn't that exactly the complaint?  Something like, "Long periods of
> co-existence need to have lots of benefits or an existential one, or
> else they're not a good idea."
They have slightly different audiences. People who want to do something 
like JMAP are already doing something like JMAP. They might or might not 
care about IMAP. People who are doing IMAP and not webmail might not 
care about JMAP.
It is not yet clear to me that JMAP will replace IMAP. But I don't think 
this is a reason not to let JMAP progress.

Best Regards,
Alexey



From nobody Wed Feb  8 06:46:47 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDA92129B92 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FYrxwiSf3XAK for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:46:43 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003: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 ABCD7129B8F for <ietf@ietf.org>; Wed,  8 Feb 2017 06:46:43 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id j15so83035188oih.2 for <ietf@ietf.org>; Wed, 08 Feb 2017 06:46:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tAv4ysi+cxmfQCeEnE/2Ua8kk103fJl3rfonVU6toFk=; b=aUhRpELTjZY23zzXRV5zKpxwaAQhoFtFlYrJ/rWOUivtiJzPUF2vUqG0CChMdYmDJ4 kzPq3xUw9pWxu7BI0AvdWY1diAQVvDharAA187mLln19wBfySZxeMTpNHWwgiYt86kxv rhtmz5jnIipIJiPxLgkvbmxvdinrxiWLtbbCg59qsL8aDw8Ut4eMydtbus5VenOz9hZe 0Fhk+wYw0hTm5JKiGlOJK9tWaa7r8uOf6eTFqf6EiKaCJo36Hlm8vi5eWl13FBnlQsLK oqkt/sB5RE/Ko83hBfCxjxKX2bYkqS42Ehm0zT/7FM3kRDtLu6tJJ3lbNsb1bu/wMsUs UqNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=tAv4ysi+cxmfQCeEnE/2Ua8kk103fJl3rfonVU6toFk=; b=ELreQhXm8DqqdsI8Ph5n/W2vJTbMHntKKy476AMEg5ySahpR+9gZ+jBJjnV696lcoq YDaPFBE1mdizJgnMuFvbGeQ4RQSErQo0LypSoEQxvtB08bZX+vphhQFGBFWpbQzh6B5w gmgPTYBab4ns8mxUetORygH6xDSXa0MedFHe9dCClLM76lCHjdEVwub5aWJGrK7oXL4G qGdKqTouaPgJgyQkBye4YiMfac4OIWm5HJR7FgJttvSL/2f3ylWEuew76AGzh2tlblsZ UwjTEyl3aS/InOsloFTOlE98U2gLYnbsdHDNTu8qFmvuOmoVCx7Gr5oeSUI3IeMKMdT6 Yelw==
X-Gm-Message-State: AMke39noS/PHswmpTKe5718O8BMDeIviDtz/RRh6eyEjqiU8icaKmSq4ZQvG7LYrvmidzTlI3NVeK8fwfdSDTX+O
X-Received: by 10.202.102.71 with SMTP id a68mr10207432oic.106.1486565202665;  Wed, 08 Feb 2017 06:46:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Wed, 8 Feb 2017 06:46:41 -0800 (PST)
In-Reply-To: <20170208051311.GP28349@mournblade.imrryr.org>
References: <B9F32633ED13374379C6E0D1@PSB> <20170124193109.68919.qmail@ary.lan> <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org>
From: Wei Chuang <weihaw@google.com>
Date: Wed, 8 Feb 2017 06:46:41 -0800
Message-ID: <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a1140b784db93c4054805ee6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AVwpZWw-aDPQwUssd6qVbbZdmK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:46:46 -0000

--001a1140b784db93c4054805ee6d
Content-Type: multipart/alternative; boundary=001a1140b784d76cdd054805ee4f

--001a1140b784d76cdd054805ee4f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Tue, Feb 7, 2017 at 9:13 PM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

> On Mon, Feb 06, 2017 at 06:20:23PM +0000, Viktor Dukhovni wrote:
>
> > Understood.  As I mentioned, I think that avoiding all conversions,
> > and checking for whatever verbatim address is found in message
> > headers is less likely to lead to problems at the cost of some more
> > names in the certificate (all the names that the author uses in
> > practice, no combinatorial explosion).
> >
> > We'll see how this plays out in practice.  It will take some time,
> > as adoption of SMTPUTF8 is still quite low.
>
> There's already a complication, in a pull request for OpenSSL,
> Dmitry Belyavsky proposes an implementation of SmtpUtf8 in OpenSSL.
> In this proposed implementation OpenSSL acquires a new dependency
> on libicu (a widely used IDNA conversion library).  Such a new
> dependency is a significant barrier to adoption of the pull request.
>
> [ Donning OpenSSL team-menber hat ]
>
> I am asking the author to remove that dependency, leaving construction
> of the normal form of the reference identifier to the application
> rather than the X.509 stack.  If he is unsuccessful, and there is
> a fundamental requirement for X.509 certificate validation code to
> become IDNA aware, that'd be a major barrier to widespread support
> for this specification.
>
> Review of the pull-request brings us to another (perhaps the main)
> issue.  The security considerations section of the draft fails to
> note a significant name-constraint issue.  Suppose an existing CA
> is constrained to email addresses in a particular DNS subtree:
>
>        CA Cert
>          Name Constraint Extension
>            Permitted
>              rfc822Name: example.com
>              rfc822Name: .example.com
>
> with "example.com" an ordinary LDH domain.  Prior to the proposed
> specification, this precludes, e.g., issuance of valid EE certificates
> with rfc822 email addresses with a domain part of "example.net".
>
> This draft breaks the existing name constraint restrictions, because
> the same CA can now issue EE certificates with SmtpUtf8 addresses
> outside the permitted rfc822Name tree.  Possibly including all-ASCII
> addresses that just happen to be found in an SmtpUtf8 subjectAltName.
>
> The problem is that the namespaces of the existing "rfc822Name"
> constraints and the new "SmtpUtf8Name" constraints substantially
> overlap leading to unexpected behaviour.
>

I wouldn't say unexpected.  The draft says the rfc822Name and SmtpUtf8Name
name constraints are applied separately, and don't affect other results
(see section 6).  It is followed by examples illustrating the behavior of
the overlap case.  The reason for separating the rfc822Name and
SmtpUtf8Name constraints was to minimize the domain A-label to U-label
conversions (and vice versa) (which I believe you're asking for too).

The assumption being made in the draft is that a SmtpUtf8Name aware issuer
will also be aware of the name constraints on that type.


>
> I therefore propose that:
>
>     When validating an EE certificate that contains SmtpUtf8Name
>     subjectAltName values, all such subjectAltName values must
>     match any rfc822Name name constraints in each issuer certificate
>     that does not also include SmtpUtf8Name constraints.


As mentioned the draft is trying to avoid this comparison.


>     In
>     particular, an issuer CA with only rfc822Name permitted subtrees
>     cannot issue EE certificates with SmtpUtf8Name altNames bearing
>     (non-ASCII) UTF-8 domains.
>

This could be added.


>
> I don't recall seeing language in the draft that expains whether
> addresses that are valid rfc822Name values can be instead presented
> in the certificate as SmtpUtf8Name values, or whether any SmtpUtf8Name
> value MUST contain either a non-ASCII localpart or a valid non-ASCII
> UTF-8 domain.
>

This is mentioned in section 7 and says: "This document RECOMMENDS using
SmtpUtf8Name when local-part contains non-ASCII characters, and otherwise
rfc822Name."


>
> It should also be possible to evaluate name constraints and match
> an EE certificate against an email address reference identifier
> without imposing a dependency on libraries that convert domain
> names between A-label and U-label forms.
>

-Wei

--001a1140b784d76cdd054805ee4f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 7, 2017 at 9:13 PM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Mon, Feb 06, 2017 at 06:20:23PM +0000, Viktor Dukhovni wrote:<br>
<br>
&gt; Understood.  As I mentioned, I think that avoiding all conversions,<br>
&gt; and checking for whatever verbatim address is found in message<br>
&gt; headers is less likely to lead to problems at the cost of some more<br>
&gt; names in the certificate (all the names that the author uses in<br>
&gt; practice, no combinatorial explosion).<br>
&gt;<br>
&gt; We&#39;ll see how this plays out in practice.  It will take some time,<br>
&gt; as adoption of SMTPUTF8 is still quite low.<br>
<br>
</span>There&#39;s already a complication, in a pull request for OpenSSL,<br>
Dmitry Belyavsky proposes an implementation of SmtpUtf8 in OpenSSL.<br>
In this proposed implementation OpenSSL acquires a new dependency<br>
on libicu (a widely used IDNA conversion library).  Such a new<br>
dependency is a significant barrier to adoption of the pull request.<br>
<br>
[ Donning OpenSSL team-menber hat ]<br>
<br>
I am asking the author to remove that dependency, leaving construction<br>
of the normal form of the reference identifier to the application<br>
rather than the X.509 stack.  If he is unsuccessful, and there is<br>
a fundamental requirement for X.509 certificate validation code to<br>
become IDNA aware, that&#39;d be a major barrier to widespread support<br>
for this specification.<br>
<br>
Review of the pull-request brings us to another (perhaps the main)<br>
issue.  The security considerations section of the draft fails to<br>
note a significant name-constraint issue.  Suppose an existing CA<br>
is constrained to email addresses in a particular DNS subtree:<br>
<br>
       CA Cert<br>
         Name Constraint Extension<br>
           Permitted<br>
             rfc822Name: <a href="http://example.com" rel="noreferrer" target="_blank">example.com</a><br>
             rfc822Name: .<a href="http://example.com" rel="noreferrer" target="_blank">example.com</a><br>
<br>
with &quot;<a href="http://example.com" rel="noreferrer" target="_blank">example.com</a>&quot; an ordinary LDH domain.  Prior to the proposed<br>
specification, this precludes, e.g., issuance of valid EE certificates<br>
with rfc822 email addresses with a domain part of &quot;<a href="http://example.net" rel="noreferrer" target="_blank">example.net</a>&quot;.<br>
<br>
This draft breaks the existing name constraint restrictions, because<br>
the same CA can now issue EE certificates with SmtpUtf8 addresses<br>
outside the permitted rfc822Name tree.  Possibly including all-ASCII<br>
addresses that just happen to be found in an SmtpUtf8 subjectAltName.<br>
<br>
The problem is that the namespaces of the existing &quot;rfc822Name&quot;<br>
constraints and the new &quot;SmtpUtf8Name&quot; constraints substantially<br>
overlap leading to unexpected behaviour.<br></blockquote><div><br></div><div>I wouldn&#39;t say unexpected.  The draft says the rfc822Name and SmtpUtf8Name name constraints are applied separately, and don&#39;t affect other results (see section 6).  It is followed by examples illustrating the behavior of the overlap case.  The reason for separating the rfc822Name and SmtpUtf8Name constraints was to minimize the domain A-label to U-label conversions (and vice versa) (which I believe you&#39;re asking for too).</div><div><br></div><div>The assumption being made in the draft is that a SmtpUtf8Name aware issuer will also be aware of the name constraints on that type.   </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I therefore propose that:<br>
<br>
    When validating an EE certificate that contains SmtpUtf8Name<br>
    subjectAltName values, all such subjectAltName values must<br>
    match any rfc822Name name constraints in each issuer certificate<br>
    that does not also include SmtpUtf8Name constraints.  </blockquote><div><br></div><div>As mentioned the draft is trying to avoid this comparison.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">    In<br>
    particular, an issuer CA with only rfc822Name permitted subtrees<br>
    cannot issue EE certificates with SmtpUtf8Name altNames bearing<br>
    (non-ASCII) UTF-8 domains.<br></blockquote><div><br></div><div>This could be added.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
I don&#39;t recall seeing language in the draft that expains whether<br>
addresses that are valid rfc822Name values can be instead presented<br>
in the certificate as SmtpUtf8Name values, or whether any SmtpUtf8Name<br>
value MUST contain either a non-ASCII localpart or a valid non-ASCII<br>
UTF-8 domain.<br></blockquote><div><br></div><div>This is mentioned in section 7 and says: &quot;This document RECOMMENDS using SmtpUtf8Name when local-part contains non-ASCII characters, and otherwise rfc822Name.&quot;  </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
It should also be possible to evaluate name constraints and match<br>
an EE certificate against an email address reference identifier<br>
without imposing a dependency on libraries that convert domain<br>
names between A-label and U-label forms.<br></blockquote><div><br></div><div>-Wei</div></div></div></div>

--001a1140b784d76cdd054805ee4f--

--001a1140b784db93c4054805ee6d
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCC2w7hd0+6CcOWMR2FSSvK2
VaADt6rx+M82ljUPimd/tjAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMDgxNDQ2NDJaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAK3zY5fFB3id9272LUatZuTeawsv1wnJZhbedmHL2
0bT70NeShdNv/2GvlWMW0Sxw4JjiL907jTiAE9MCQ+W1Y/HgEa2SFkZaJAJkGkcgCNnX6pYtQ2Af
2DF00tIUhv+nFLmF2GcbxmOZ2fAH3aFgUN7ekY/OmEzl8TjLnMFz7ZfHE3ZriKY1X4AlV0n/U5uv
nyM4Nccg3tqH9sLa6+MSRaUalelSJeBoLt1iPf0uXIM9r63QY8NUGnJ0N1ZbzuoN6PQtu+V4dfxN
G60KoCdzFf6Q+Zw+HQE8VgTUnZG8VttSnc6feKk4SAo/TMq0gvi8Z9cJ1Y/ZX2Y0hslZoBLqvg==
--001a1140b784db93c4054805ee6d--


From nobody Wed Feb  8 06:51:17 2017
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35CF1129547 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:51:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E2jawTSaXmBn for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 06:51:11 -0800 (PST)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002: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 0508C1299E1 for <ietf@ietf.org>; Wed,  8 Feb 2017 06:51:11 -0800 (PST)
Received: by mail-yw0-x22f.google.com with SMTP id l19so87136165ywc.2 for <ietf@ietf.org>; Wed, 08 Feb 2017 06:51:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HR/E7ku7riQvXzErhSvi/uJJDCDDoiX0kul/Fdv+oc0=; b=BIoczYed3ZL6WD0CdqQkWrLW/ieh8BH5KSCMt2YQfrmxUXRsGm7zEEAFQGMxTh+zCW R5Ffecx1GiZ1BMg2qR08bRLgwtswcXW4ySPHOPmRcB2DJbFbtml6zCdJhC4TUx41aHq1 UCBde5rOxgieRvL7UxQnnk7uE+gf7kQA9p3caOVwBIv+2kVQBgSIbbYjj6UTBvutKS9H zZShcbraZSCwTDebYPJCoU4+6msw064109dINSClo3qBbEJN2Bkhh5VadJ7MFJ5bAwbT 8/gxoFVJHNbAbpLowW23bVRiFixyjCmHo9sK/kuk2cCt0OK8SnyUwDuDOaE8mZ0814ij n+hA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HR/E7ku7riQvXzErhSvi/uJJDCDDoiX0kul/Fdv+oc0=; b=tXzxZv84fft1xp1tAE7I86XjYYTVkw5LzPc5+lpmuWN/yhJjzFx5oN30ab84ZiO9D1 iMpG+mTTbveBJrJY/+wal4K5CikKJmYp0WMmS4sAjy93dwbhPF1FILk/WV6hCAEJp749 V38ncSrQmLt3rWegYNyGVGI7TEgql6do8bHHPIPUsGoiJWIn0zaIgLb9t9TSwqGkMhnU phjKVZZOBJ6TcJhnQcdjoh5sCfArEGUmOvIJ1zvohigmNmK+sr9e5Tis71OtYg+diaLa T8U7AubFt8pZNnZYX7auw+SjxbW1TbkMhw8KnncNp1UmzBOcGvTbDinsLuEZ0pIxiGVE Gasg==
X-Gm-Message-State: AMke39mPiAClHHgGSSy9mCeAq9zdG3/WZWkb3c144590IQ2iP70CEe7uZLKLx2J+9U4joezyNkdy6ZIbAzqlig==
X-Received: by 10.129.162.130 with SMTP id z124mr16378170ywg.276.1486565470340;  Wed, 08 Feb 2017 06:51:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.234.9 with HTTP; Wed, 8 Feb 2017 06:51:09 -0800 (PST)
In-Reply-To: <20170208142241.GB84460@mx4.yitter.info>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 8 Feb 2017 08:51:09 -0600
Message-ID: <CAKKJt-ftk_vXiQBhemRQqv0q4exNoE=FC1ZYi5QmrmbJXjvjmQ@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=94eb2c129292cbbf89054805feb7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v8IObGe7xFDebvCqK4NFJeVKjB0>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 14:51:14 -0000

--94eb2c129292cbbf89054805feb7
Content-Type: text/plain; charset=UTF-8

FWIW ...

On Wed, Feb 8, 2017 at 8:22 AM, Andrew Sullivan <ajs@anvilwalrusden.com>
wrote:

> On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov wrote:
> >
> > Agreed. JMAP and IMAP are likely to co-exist for long time.
> >
>
> Isn't that exactly the complaint?  Something like, "Long periods of
> co-existence need to have lots of benefits or an existential one, or
> else they're not a good idea."


Andrew didn't point this out, but since TSVAREA has been paying attention
to it for the past couple of IETF cycles, the IAB does have
https://datatracker.ietf.org/doc/draft-iab-protocol-transitions/ in active
development.

We're finding it helpful. Your mileage may vary, of course.

Spencer

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

<div dir=3D"ltr">FWIW ...<div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Wed, Feb 8, 2017 at 8:22 AM, Andrew Sullivan <span dir=3D"ltr">&=
lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwal=
rusden.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><span class=3D"gmail-">On Wed, Feb 08, 2017 at 01:52:00PM +0000,=
 Alexey Melnikov wrote:<br>
&gt;<br>
&gt; Agreed. JMAP and IMAP are likely to co-exist for long time.<br>
&gt;<br>
<br>
</span>Isn&#39;t that exactly the complaint?=C2=A0 Something like, &quot;Lo=
ng periods of<br>
co-existence need to have lots of benefits or an existential one, or<br>
else they&#39;re not a good idea.&quot;</blockquote><div><br></div><div>And=
rew didn&#39;t point this out, but since TSVAREA has been paying attention =
to it for the past couple of IETF cycles, the IAB does have <a href=3D"http=
s://datatracker.ietf.org/doc/draft-iab-protocol-transitions/">https://datat=
racker.ietf.org/doc/draft-iab-protocol-transitions/</a> in active developme=
nt.=C2=A0</div><div><br></div><div>We&#39;re finding it helpful. Your milea=
ge may vary, of course.</div><div><br></div><div>Spencer=C2=A0</div></div><=
/div></div>

--94eb2c129292cbbf89054805feb7--


From nobody Wed Feb  8 07:04:05 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36798129BBE for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:04:04 -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 autolearn_force=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 PB2DzLCOa6xH for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:03:57 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A0D5129B93 for <ietf@ietf.org>; Wed,  8 Feb 2017 07:03:57 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cbTml-000PX9-65; Wed, 08 Feb 2017 10:03:55 -0500
Date: Wed, 08 Feb 2017 10:03:49 -0500
From: John C Klensin <john-ietf@jck.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
Message-ID: <32D2801528D191A01AD4D3B2@PSB>
In-Reply-To: <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EjlK8yHltHCOlHu3UPJg-lJkzbs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 15:04:04 -0000

--On Wednesday, February 8, 2017 14:27 +0000 Alexey Melnikov
<alexey.melnikov@isode.com> wrote:

> Hi Andrew,
> 
> On 08/02/2017 14:22, Andrew Sullivan wrote:
> 
>> On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov
>> wrote:
>>> Agreed. JMAP and IMAP are likely to co-exist for long time.

>> Isn't that exactly the complaint?  Something like, "Long
>> periods of co-existence need to have lots of benefits or an
>> existential one, or else they're not a good idea."

It is certainly my main complaint.

> They have slightly different audiences. People who want to do
> something like JMAP are already doing something like JMAP.
> They might or might not care about IMAP. People who are doing
> IMAP and not webmail might not care about JMAP.
> It is not yet clear to me that JMAP will replace IMAP. But I
> don't think this is a reason not to let JMAP progress.

Alexey, I think you are missing the point.  Except for the small
minority of users who switch MUAs back and forth (see below), I
would expect any given user to use either an IMAP approach, a
JSON or JSON-like one, or neither.    No long transition as far
as they are concerned.    However, from the perspective of
someone trying to maintain servers or a mailstore, the fact that
there will be both types of users (for a long time if not
forever), it implies the need to maintain (and configure,
support, etc.) both IMAP/SMTP and JMAP facilities in parallel
and to support, also for a long time, the ability to convert
between the two formats.  Also, if that conversion is not
absolutely lossless, there will be a large collection of ongoing
problems, for an equally long time.

Those _are_  reasons to not let JMAP progress because it could
easily make the mail system work worse.  Not, as Andrew (and
several others) have suggested, not a risk we should encourage
unless the benefits and improvements are significant.

     best,
      john




From nobody Wed Feb  8 07:19:49 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54A0F129B83 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:19:47 -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 autolearn_force=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 HGHMyyr_ih4d for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:19:45 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 983D012997E for <ietf@ietf.org>; Wed,  8 Feb 2017 07:19:45 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 71291284E4C; Wed,  8 Feb 2017 15:19:43 +0000 (UTC)
Date: Wed, 8 Feb 2017 15:19:43 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170208151943.GQ28349@mournblade.imrryr.org>
References: <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6HkSQALQp8crn_EMZcqX3l5-mwk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 15:19:47 -0000

On Wed, Feb 08, 2017 at 06:46:41AM -0800, Wei Chuang wrote:

> > This draft breaks the existing name constraint restrictions, because
> > the same CA can now issue EE certificates with SmtpUtf8 addresses
> > outside the permitted rfc822Name tree.  Possibly including all-ASCII
> > addresses that just happen to be found in an SmtpUtf8 subjectAltName.
> >
> > The problem is that the namespaces of the existing "rfc822Name"
> > constraints and the new "SmtpUtf8Name" constraints substantially
> > overlap leading to unexpected behaviour.
> 
> I wouldn't say unexpected.

It may well be expected as a consequence of decisions in the draft,
but it is objectively unwanted new behaviour for a name constrained
CA, to suddenly be able to issue certificates for previously excluded
addresses.  Software that allows such violations of previously
enforced constraints would IMHO be CVE-worthy.

> The draft says the rfc822Name and SmtpUtf8Name
> name constraints are applied separately, and don't affect other results
> (see section 6). 

Yes, that's what I'm objecting to.  This is a design error in the
draft.  The namespaces are *not* separate, and orthogonal constraints
are not desirable.

> It is followed by examples illustrating the behavior of
> the overlap case.  The reason for separating the rfc822Name and
> SmtpUtf8Name constraints was to minimize the domain A-label to U-label
> conversions (and vice versa) (which I believe you're asking for too).

This is not a valid reason to violate the meaning of existing name
constraints.  It is not even clear why any conversions would be
required.  All that one needs to do is satisfy rfc822Name constraints
when no SmtpUtf8Name constraints are present in the same certificate.
When the domain is a non-ASCII domain, no permitted tree or excluded
sub-tree matches without conversion.  Thus the address is acceptable
only if the rfc822Name constraints contain only excluded sub-trees.

The only corner case is when an all-ASCII address (both localpart
and domainpart) for some reason appears in SmtpUtf8Name.  Such
names could match a full address in rfc822Name constraints (not
just a domainpart sub-tree).  This is why it is important to be
clear about whether all-ASCII names are valid in that context.

> The assumption being made in the draft is that a SmtpUtf8Name
> aware issuer will also be aware of the name constraints on that type.

The issuer may be SmtpUtf8 aware, but the parent CA that sets the
issuer's constraints (possibly some time ago in the past) may not.
The issuer should not be able to evade name constraints.

> > I therefore propose that:
> >
> >     When validating an EE certificate that contains SmtpUtf8Name
> >     subjectAltName values, all such subjectAltName values must
> >     match any rfc822Name name constraints in each issuer certificate
> >     that does not also include SmtpUtf8Name constraints.
> 
> As mentioned the draft is trying to avoid this comparison.

This comparison MUST happen to avoid evasion of name constraints.
I see no need for "conversions" to implement these comparisons.
An issuer with only rfc822Name constraints present should only be
able to issue email altNames with ASCII domains that satisfy the
rfc822Name constraints.


> >     In
> >     particular, an issuer CA with only rfc822Name permitted subtrees
> >     cannot issue EE certificates with SmtpUtf8Name altNames bearing
> >     (non-ASCII) UTF-8 domains.
> 
> This could be added.

This needs to be added, and also language about how to match
SmtpUtf8Name elements against rfc822Name constraints in the
case that the domainpart is all-ASCII.

> > I don't recall seeing language in the draft that expains whether
> > addresses that are valid rfc822Name values can be instead presented
> > in the certificate as SmtpUtf8Name values, or whether any SmtpUtf8Name
> > value MUST contain either a non-ASCII localpart or a valid non-ASCII
> > UTF-8 domain.
> 
> This is mentioned in section 7 and says: "This document RECOMMENDS using
> SmtpUtf8Name when local-part contains non-ASCII characters, and otherwise
> rfc822Name."

This effectively makes all-ASCII names valid in SmtpUtf8Name, which
increases scope for implementation errors.  I would prefer that
the draft prohibit use of SmtpUtf8Name when rfc822Name is an option.

-- 
	Viktor.


From nobody Wed Feb  8 07:34:09 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E8A129BCA for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rP9uokUaXyUi for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:34:06 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 A3C4F129BBD for <ietf@ietf.org>; Wed,  8 Feb 2017 07:34:06 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v18FZhan021120 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 8 Feb 2017 07:35:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486568143; bh=uLCVmbISl9hIK0qSf2q/VbK3W/q6VJ/VMVKSR5IsfUs=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=UoQTCaxo/HI8m6NJTPyU8ZU61rsAsqAvkZ35UQVgU0qSS7Xu2tWlZog8NkedRGw7Q rWNfvLxzl+FI1FHZxTZmfRdgbxgMSgminrkMA4RNeY+4CPFvshZT5qrABBpXQ5Vx7M +DEL7UwgHDroZu5C5Qz6E1yTlON30wf5D+IoQjh8=
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net>
Date: Wed, 8 Feb 2017 07:33:53 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <32D2801528D191A01AD4D3B2@PSB>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BOgMxqsgnUOXzr6awjlO-AtLid0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 15:34:08 -0000

On 2/8/2017 7:03 AM, John C Klensin wrote:
> However, from the perspective of someone trying to maintain servers
> or a mailstore, the fact that there will be both types of users (for
> a long time if not forever), it implies the need to maintain (and
> configure, support, etc.) both IMAP/SMTP and JMAP facilities in
> parallel and to support, also for a long time, the ability to convert
> between the two formats.  Also, if that conversion is not absolutely
> lossless, there will be a large collection of ongoing problems, for
> an equally long time.

+1

This creates a dual-stack operational environment.  They always have
real -- and often problematic -- operational effects.

Given the long-standing complaints about IMAP's complexity, it still
might be worth doing.  But as has already been noted, what is required
here is a very compelling value statement that justifies the second
'stack'.

The posted list of folk who are expected to implement this helps quite a
bit, IMO.  However we seem to be missing the compelling
/technical-operations/ value proposition.  Will the resulting protocol 
be simpler, more efficient, faster, ... and what is the basis for 
asserting such improvements?


On 2/6/2017 7:40 AM, Alexey Melnikov wrote:
> The current proposal is "advancing on the old". It is improving on
> some IMAP use cases

Where is this explained in the charter -- with enough detail to make it
possible to assess it?  This seems to me foundational for the effort's
value proposition.


On 2/8/2017 5:34 AM, Alexey Melnikov wrote:
>> Drafts?  What drafts?  Perhaps you mean:
>>
>> https://tools.ietf.org/html/draft-jenkins-jmap
>>
>> Except that no draft is cited in the charter.
>
> I realized that I accidentally deleted an important sentence from
> the Charter while doing editing. One of the paragraphs should have
> read:
>
> The work of this group is limited to developing a protocol for a
> client synchronising data with a server. The work will be based on
> draft-jenkins-jmap and draft-jenkins-jmapmail. Any server-to-server
> issues are out of scope for this working group. New end-to-end
> encryption mechanisms are out of scope, but the work should consider
> how to integrate with existing standards such as S/MIME and OpenPGP.

Ahh.  Yes, very helpful.  Thanks!

This then raises a point of nuance about a charter's reference to the 
documents that are foundational to a working group effort:  indicating 
constraints on their role.  That is, what is the working group 
authorized to do with the document. This can be extremely helpful with 
working group management and helping participants to focus.

Roughly the choices are a continuum between having no constraints -- the 
doc is simply used as input and advice -- all the way to only being 
permitted to fix bugs and improve editorial writing.

The text you've provided here says 'based on'.  In a more benign world, 
clarifying what that means wouldn't be necessary, but in the current 
reality, I urge adding text that indicates why degree of modification 
the wg is allowed to make on the drafts.

d/



-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Wed Feb  8 07:52:51 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 762D0129BF8 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:52:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V8P9lWGsaBqA for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 07:52:48 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 49054129BC8 for <ietf@ietf.org>; Wed,  8 Feb 2017 07:52:48 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id k15so169289883qtg.3 for <ietf@ietf.org>; Wed, 08 Feb 2017 07:52:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z1m5EOclSmibcd7g+cl87DhdXOZ7GOFKiabw6NyhULg=; b=JFXm4CR4kHbGWJ8Qp9ERxuwjOvLyhxIHY5JO9tMiEhEsyGQj+XTcDtdP4omDxwKlO2 InDxtl2lU5/PIpkbK0FPbifDyz52mEqFbR6KfSMu5ikNU4+pa61LGGVixK//HN4wgnFh XIOLAudmx9zJ/LurY1fK0hJtVOEIu/PZsuo9+J8lIbKb2CGp36hZ/jMCioROGgmsq/jW Vg7f4meSRSpv1QQU9BnngU5f6oNR2SpQZd4vfCleqTzItdizdp7JakCbdZaT3e03MGNk klg79OxffGNkUfr0CHk3cszCtFWcBKseHR1lfGW3pSsChD2K0qTP1DX5vv0SAhjwxaC+ dYoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z1m5EOclSmibcd7g+cl87DhdXOZ7GOFKiabw6NyhULg=; b=cKAF1If7niZd615HVfsnbQo01teUctHOJ7KfiTyU7QlKTaLVBJ6z+14TI7HFZdX/XD jZ3uomUDjT61P/mnPYkd6CRR7OPHPPmRTK2tqFxaK082gTGKV4r+UfKMUyaCBl3D1nqz n6dq0Kq7suZYH12Xv6E5h6md9I8kzKEAWLT5QrOWOd5xi8ohswR4IUnfqi9WvDVnTs2L pgFAfeLWn5o1ucems+MxSNCFL6ayXVCGLAPmz8/CXMZ/mFrM9kncRpdrXx7+zZ0IpciP T+YvmEEWrk+HegaVBZPFhH2IMU8lVJXSKUoSYmQ2IiliytjPXVXOJ6+ejF0wvEKt/5SU mfIg==
X-Gm-Message-State: AMke39m6/lFTCCh3A/3qcNBuk3UloPlX2R6dwfHAcKdy2wdTQXS16CaBUVF4F18AVKWfVQ==
X-Received: by 10.237.38.65 with SMTP id z59mr20099565qtc.5.1486569167387; Wed, 08 Feb 2017 07:52:47 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id s20sm6451027qtc.39.2017.02.08.07.52.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 07:52:46 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com>
Date: Wed, 8 Feb 2017 10:52:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A86D15F6-59C1-4AE3-BA56-2747DD7345CC@fugue.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net> <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net> <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com> <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JSkj5s0rn2w6PQU-zL-2hmrhg4c>
Cc: jmap@ietf.org, Neil Jenkins <neilj@fastmail.com>, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 15:52:49 -0000

On Feb 8, 2017, at 2:26 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> That=E2=80=99s good to know. I=E2=80=99m wondering if implementing a =
generic email client (rather than a specific =E2=80=9Cgmail=E2=80=9D or =
=E2=80=9Clive=E2=80=9D client) isn=E2=80=99t becoming ever harder. With =
so many older and newer services, a client has to support pop3, imap, =
smtp, EWS, ActiveSync, and maybe a few of the others you mentioned. This =
effort proposes to add yet another one.

The protocol and database backend parts of implementing a mail client =
are only difficult in the sense that ActiveSync is not a standard.   =
IMAP, SMTP and POP protocol implementations are readily available.   The =
problem is not that they are hard to implement.   It's that they don't =
work very well.   SMTP works great, don't get me wrong, but IMAP and POP =
both use the wrong data abstraction, and consequently are very hard to =
get right, and generally aren't gotten right.

So a new protocol that has the data abstraction right is actually a =
substantial improvement.   I don't know if that's the case with =
JMAP=E2=80=94if it's the same data abstraction as IMAP, it's not worth =
bothering with, but that's something that at least in theory can be =
discussed.

What JMAP does afford is the opportunity to have an embedded web client =
that doesn't suck, and a way to escape it if you want something more =
stateful.   Doing IMAP in a web browser is painful.   I've seen it done. =
  It wasn't pretty, and the company that did it corkscrewed in and left =
a crater.   So practically speaking, if you want to do email that way, =
you are already implementing something like JMAP, but you are doing it =
by yourself, and it's not standard, so your customers are stuck with =
what you did.

Even if the data abstraction is wrong in JMAP, you still get a =
substantial win from that one improvement.


From nobody Wed Feb  8 08:36:15 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E846129C59; Wed,  8 Feb 2017 08:36:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 FQmjFAujUIl5; Wed,  8 Feb 2017 08:36:05 -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 3B9D8129C58; Wed,  8 Feb 2017 08:36:05 -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 v18Ga4GR019862; Wed, 8 Feb 2017 09:36:04 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v18GZxLE019407 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Wed, 8 Feb 2017 09:35:59 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 8 Feb 2017 08:35:58 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1178.000; Wed, 8 Feb 2017 08:35:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Fernando Gont <fgont@si6networks.com>, "otroan@employees.org" <otroan@employees.org>, Joe Touch <touch@isi.edu>
Subject: RE: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSgX24aUQDcUzHwUaWWd7FFympqaFd+j3QgADSTICAAIH0gA==
Date: Wed, 8 Feb 2017 16:35:58 +0000
Message-ID: <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com>
In-Reply-To: <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T6p1w5Dv59Su_xrm_W1JbVQWTqI>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 16:36:06 -0000

Hi Fernando,

> -----Original Message-----
> From: Fernando Gont [mailto:fgont@si6networks.com]
> Sent: Tuesday, February 07, 2017 4:46 PM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; otroan@employees.org; Jo=
e Touch <touch@isi.edu>
> Cc: 6man WG <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis@ie=
tf.org; tsv-area@ietf.org; 6man-chairs@ietf.org
> Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Dis=
covery for IP version 6) to Internet Standard
>=20
> On 02/07/2017 05:14 PM, Templin, Fred L wrote:
> > Hi Ole and Joe,
> >
> > Also not to be lost in this discussion is the potential for spoofed ICM=
P messages
> > that would report a size that is either too large or too small.
>=20
> RFC5927 is all about this.

Right. The point is that these data points would seem to indicate that stan=
dard
PMTUD per rfc1981bis is not reliable nor secure enough for operation on ope=
n
internetworks such as the global public Internet. Maybe the security sectio=
n
should say that?

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 Wed Feb  8 08:37:05 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B1D6129C4D for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 08:37:05 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UbCRjGWv9x0I for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 08:37:04 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 3536B129C58 for <ietf@ietf.org>; Wed,  8 Feb 2017 08:37:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486571823; d=isode.com; s=june2016; i=@isode.com; bh=Gk0lNtUEaFIROoMuFtHESZnYTVI0xC+SUBQc70RMc5g=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=Z1+WLSBVaGdtq7OwqWr1wV1Rtr/S9h2cesYKoADjoC4ZT0oi0esqevyQMxcOZay4tGili8 bYm4oLcplZIFbCJbevfUYNe9/ca6eMyRaJ9TR/r63ofEbE15AXVy/59iL4v61jmWpCSNlX gV/f01Nj6JeaOAa+CvaSlxH8UeMWnP8=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJtJLwAY1wQv@statler.isode.com>; Wed, 8 Feb 2017 16:37:03 +0000
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com>
Date: Wed, 8 Feb 2017 16:36:45 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <32D2801528D191A01AD4D3B2@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/elu2J0_bnVmYolr5cqn-7eHSsvg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 16:37:05 -0000

John,


On 08/02/2017 15:03, John C Klensin wrote:
> --On Wednesday, February 8, 2017 14:27 +0000 Alexey Melnikov
> <alexey.melnikov@isode.com> wrote:
>
>> Hi Andrew,
>>
>> On 08/02/2017 14:22, Andrew Sullivan wrote:
>>
>>> On Wed, Feb 08, 2017 at 01:52:00PM +0000, Alexey Melnikov
>>> wrote:
>>>> Agreed. JMAP and IMAP are likely to co-exist for long time.
>>> Isn't that exactly the complaint?  Something like, "Long
>>> periods of co-existence need to have lots of benefits or an
>>> existential one, or else they're not a good idea."
> It is certainly my main complaint.
>
>> They have slightly different audiences. People who want to do
>> something like JMAP are already doing something like JMAP.
>> They might or might not care about IMAP. People who are doing
>> IMAP and not webmail might not care about JMAP.
>> It is not yet clear to me that JMAP will replace IMAP. But I
>> don't think this is a reason not to let JMAP progress.
> Alexey, I think you are missing the point.
That is entirely possible :-).
> Except for the small
> minority of users who switch MUAs back and forth (see below), I
> would expect any given user to use either an IMAP approach, a
> JSON or JSON-like one, or neither.    No long transition as far
> as they are concerned.    However, from the perspective of
> someone trying to maintain servers or a mailstore, the fact that
> there will be both types of users (for a long time if not
> forever), it implies the need to maintain (and configure,
> support, etc.) both IMAP/SMTP and JMAP facilities in parallel
As far as deployments are concerned, if there is a case of 
co-existentence, then it would fall into one of two categories:

1). JMAP is just a a proxy and uses IMAP on the backend. Configuring 
JMAP server is the same as configuring a MUA.

2). Both are supported by the same software (i.e. Cyrus and Dovecot use 
case). I doubt that incremental cost of configuring both is much higher 
than just configuring one of them.

In either case configuring JMAP clients is a simple(r) proposition: just 
distribute HTTP URI for a JMAP instance.

> and to support, also for a long time, the ability to convert
> between the two formats.
There are no 2 formats, both IMAP and JMAP operate on RFC 5322 objects, 
so the rest of your argument is invalid.
> Also, if that conversion is not
> absolutely lossless, there will be a large collection of ongoing
> problems, for an equally long time.
There is a single message format, so no need to convert.

Best Regards,
Alexey
> Those _are_  reasons to not let JMAP progress because it could
> easily make the mail system work worse.  Not, as Andrew (and
> several others) have suggested, not a risk we should encourage
> unless the benefits and improvements are significant.
>
>       best,
>        john
>


From nobody Wed Feb  8 09:02:06 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EDFF9129C9B; Wed,  8 Feb 2017 09:02:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: NomCom 2016-2017: Proposed Timeline for filling the ART AD Vacancy
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148657332494.4254.15072067268872692938.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2017 09:02:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fTRJ_SmGcZU641PPyO-2bzkBYxk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 17:02:05 -0000

All -

The 2016-2017 NomCom will act to fill the current ART AD vacancy in accord 
with the procedures outlined in RFC 7437. We propose to fill the vacancy
before IETF 98 in Chicago using the following schedule:
 
 ART AD Vacancy Selection Time Line
 
 Open Call for Nominations:	        2/8/17
 Nominations Close:			2/17/17
 Feedback Opens:			2/18/17
 Community Feedback Due:		2/24/17
 NomCom Interviews:			2/27/17 - 3/3/17
 NomCom Selection Completed:	        3/10/17
 IAB Confirmation By:		        3/24/17
 Announcement:				3/24/17

This schedule meets the six week requirement and allows two weeks for the
IAB confirmation process. While the time line is aggressive, we believe 
that we can meet our obligations and select a strong candidate with the
help of the IETF community.

Lucy Lynch
NomCom Chair 2016-2017


Some additional details -

RFC 7437 3.5.  Mid-term Vacancies
https://tools.ietf.org/html/rfc7437#section-3.5.2

"If it is the case that the nominating committee is reconvening to
 fill the mid-term vacancy, then the completion of the candidate
 selection and confirmation process is due within six weeks, with
 all other time periods otherwise unspecified prorated accordingly."

Our proposed schedule includes:
 
 10 days for nominations
 1 week for community feedback
 1 week for NomCom interviews
 1 week for the NomCom selection process.
 2 weeks for IAB confirmation

This timeline allows us to meet the Term Limits conditions of section 3.4

"For confirmed candidates of the IESG, the terms begin no later than
when the currently sitting members' terms end on the last day of the
meeting.  A term may begin or end no sooner than the first day of the
meeting and no later than the last day of the meeting as determined
by the mutual agreement of the currently sitting member and the
confirmed candidate.  A confirmed candidate's term may overlap the
sitting member's term during the meeting as determined by their
mutual agreement." 

and section 3.5.4

"The term of the confirmed candidate will be either:

  A.  the remainder of the term of the open position if that
       remainder is not less than one year"


From nobody Wed Feb  8 09:04:18 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C9CA2129C9B; Wed,  8 Feb 2017 09:04:12 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: NomCom 2016-2017: Call for Nominations to fill the ART AD Vacancy
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148657345278.4391.7886665273772302944.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2017 09:04:12 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rs6be_dx9FhNxgk-ShlP7jg-bjY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 17:04:13 -0000

The 2016-17 Nominating Committee (Nomcom) is seeking nominations from
now until February 17, 2017 for the position of ART AD. This appoint
will fill the 1 year vacancy created by Alissa Cooper's resignation as she
moves to the IETF Chair seat.

https://datatracker.ietf.org/nomcom/2016/

Nominations may be made by selecting the Nominate link at the top of
the Nomcom 2016 home page, or by visiting the following URL:

https://datatracker.ietf.org/nomcom/2016/nominate/

  {Note that nominations made using the web tool require an ietf.org
   datatracker account. You can create a datatracker ietf.org account
   if you don't have one already by visiting the following URL:
   https://datatracker.ietf.org/accounts/create/ }

If you are unable to use the web form, nominations may instead be made
by email to nomcom-16@ietf.org. If using email, please include the word
"Nominate" in the Subject and indicate in the email who is being
nominated and their email address (to confirm acceptance of the
nomination).

If you are nominating someone other than yourself, please tell us if
we may tell the nominee that you were the one who made the nomination.

Self-nomination is welcome!

Willing nominees will be asked to fill out a questionnaire for the ART AD
position. The questionnaires will be available February 8, 2017 and have a 
submission deadline of February 17, 2017.

NomCom 2016-17 will follow the policy for "Open Disclosure of Willing
Nominees" described in BCP 10/RFC 7437.  As stated in RFC 7437: "The
list of nominees willing to be considered for positions under review
in the current Nomcom cycle is not confidential". Willing nominees for
the ART AD position will be listed in a publicly accessible way - anyone
with a datatracker account may access the lists.  Additionally, the
nomination form asks if we may share your own name with the
nominee. In all other ways, the confidentiality requirements of BCP10
remain in effect.  All feedback and all Nomcom deliberations will
remain confidential and will not be disclosed.

There is a field on the form you can mark in order to allow the Nomcom
to tell the nominee that you were the one who made the
nomination. This defaults to “no” - so if you don't mark the field
we won’t tell.

In order to ensure time to collect sufficient community feedback about
each of the willing nominees, nominations must be received by the
NomCom on or before February 17, 2017.

Please submit your nominations as early as possible for the sake of
your nominees. Note that nominations should not wait for management
permission, as it is easier to decline the nomination than put one in
late.


From nobody Wed Feb  8 10:33:56 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 363DA129D36 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 10:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31UnLNkAu735 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 10:33:53 -0800 (PST)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::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 B2124129D34 for <ietf@ietf.org>; Wed,  8 Feb 2017 10:33:53 -0800 (PST)
Received: by mail-qt0-x22c.google.com with SMTP id k15so174168655qtg.3 for <ietf@ietf.org>; Wed, 08 Feb 2017 10:33:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GKERFyD2Ezkzhffz+UMFTu0flDMXpJAfruenUEFZ69Y=; b=tnpj9ymoORVwGDXST9LvCDddrlLCUj/eHdVvVkpHRwYYVNvjfEqTtT2U4sa0FuFRU4 ZPF5A12Kv4HZfBL541R/89aRalEKHkcD3rBdBfvMp4l/2SAZSCX7Scd+O9MsU336cyQD dqHh4UjHKZs09k7uL+dm7ir8LrUtjqY42lwVGaM0EYCOdb2S9XEs3PTj7t6ODxUKHBns 7PBUKvMCSMs/lndhgC6L4e0oDQ7zV5EM6VtoiI8X0dFGX2uRMW/zFlguL569Amfsqy1K VlHhcFVGCTR7p0lWKpc2Ckt4ZlJlmzRAvLZwfeBLeoC+FZNfWtZU9Rhv/E/HGNz7MUHO N7uw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GKERFyD2Ezkzhffz+UMFTu0flDMXpJAfruenUEFZ69Y=; b=NIaDou5fTRtE7Aq2v3c70DoZea3lwla1Rj1lE5N3dtNRxjcafulJxIKAhPvWrkjMC7 2mypcCcA9zeeYmLopZsrESndABRiKUfkGzUGmr0G/rq54PGQoXBbe7weCdQcyCXhIBqL 5QfbOEQiY3V61nyZLa8nDilK7kQAS9/gjCmnfnseXR1XXaMyBHvwP0ej8eGHVB7hZ/67 pbNeZvCTgT74CdCDiCxDEgW665DTXF63Go5Amd0L//tvRGspYUpK9R9ilMDWEwLHAtGa cGa9uX0q1c9wDizmn/ju9yLIyUBu/LiWVdHmrQDFZMbafRdPf0paiWfelmxjH/xzpces z9tw==
X-Gm-Message-State: AMke39kfpsKbURiy/retAEmdRgLmUa0jmq2eDggW/igAnt4Fj71AaXP7CPJawDi1DUMOOADkOHH5o93Bu2tfjQ==
X-Received: by 10.200.53.50 with SMTP id y47mr20711888qtb.114.1486578832477; Wed, 08 Feb 2017 10:33:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.12.174.226 with HTTP; Wed, 8 Feb 2017 10:33:22 -0800 (PST)
In-Reply-To: <32D2801528D191A01AD4D3B2@PSB>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 8 Feb 2017 10:33:22 -0800
Message-ID: <CA+9kkMCCQLhJ+dD7Ga2L4axQ51VjXKAsh+OyinW2M1zefKF7OQ@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11397f763dd6480548091be3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QaAAgg2Zpc3gOHs6rmAeo0wcHWs>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 18:33:55 -0000

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

On Wed, Feb 8, 2017 at 7:03 AM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> Except for the small minority of users who switch MUAs back and forth (see
> below), I
> would expect any given user to use either an IMAP approach, a
> JSON or JSON-like one, or neither.


I am confused by this claim.  There are substantial numbers of users who
access their mail from mobile and from laptop/desktop systems.  Those,
generally speaking, are different MUAs.


> No long transition as far
> as they are concerned.    However, from the perspective of
> someone trying to maintain servers or a mailstore, the fact that
> there will be both types of users (for a long time if not
> forever), it implies the need to maintain (and configure,
> support, etc.) both IMAP/SMTP and JMAP facilities in parallel
> and to support, also for a long time, the ability to convert
> between the two formats.

Also, if that conversion is not
> absolutely lossless, there will be a large collection of ongoing
> problems, for an equally long time.
>
> Those _are_  reasons to not let JMAP progress because it could
> easily make the mail system work worse.


I think you and the proponents fundamentally disagree about what the
current mail system is.  They see a welter of proprietary systems based on
JSON and HTTP, and they want to clean it up by standardizing on one
approach.  You see a standardized system of IMAP/SMTP and want to avoid
standardizing another system.  From the proponents perspective Andrew's
question of "long periods of coexistence" has to be seen in the context of
"long periods of coexistence" _of proprietary systems_ .

If you don't agree on what the mail system is, it's not particularly
surprising that you don't agree on the method for optimizing it.

Not, as Andrew (and
> several others) have suggested, not a risk we should encourage
> unless the benefits and improvements are significant.
>
>
The proponents seem to have demonstrated that there are proprietary systems
in place.  So I believe the calculus of benefits and improvements must be
done over a different set of data points.

regards,

Ted



>      best,
>       john
>
>
>
>

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

<div dir=3D"ltr">On Wed, Feb 8, 2017 at 7:03 AM, John C Klensin <span dir=
=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ie=
tf@jck.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>Except for the small minority of users who switch MUAs back and forth (=
see below), I<br>
would expect any given user to use either an IMAP approach, a<br>
JSON or JSON-like one, or neither.=C2=A0=C2=A0 </blockquote><div><br></div>=
<div>I am confused by this claim.=C2=A0 There are substantial numbers of us=
ers who access their mail from mobile and from laptop/desktop systems.=C2=
=A0 Those, generally speaking, are different MUAs.<br></div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">No long transition as far<br>
as they are concerned.=C2=A0 =C2=A0 However, from the perspective of<br>
someone trying to maintain servers or a mailstore, the fact that<br>
there will be both types of users (for a long time if not<br>
forever), it implies the need to maintain (and configure,<br>
support, etc.) both IMAP/SMTP and JMAP facilities in parallel<br>
and to support, also for a long time, the ability to convert<br>
between the two formats.=C2=A0 </blockquote><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Also, if that conversion is not<br>
absolutely lossless, there will be a large collection of ongoing<br>
problems, for an equally long time.<br>
<br>
Those _are_=C2=A0 reasons to not let JMAP progress because it could<br>
easily make the mail system work worse.=C2=A0 </blockquote><div><br></div><=
div>I think you and the proponents fundamentally disagree about what the cu=
rrent mail system is.=C2=A0 They see a welter of proprietary systems based =
on JSON and HTTP, and they want to clean it up by standardizing on one appr=
oach.=C2=A0 You see a standardized system of IMAP/SMTP and want to avoid st=
andardizing another system.=C2=A0 From the proponents perspective Andrew&#3=
9;s question of &quot;long periods of coexistence&quot; has to be seen in t=
he context of &quot;long periods of coexistence&quot; _of proprietary syste=
ms_ .<br><br></div><div>If you don&#39;t agree on what the mail system is, =
it&#39;s not particularly surprising that you don&#39;t agree on the method=
 for optimizing it.<br></div><div><br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
Not, as Andrew (and<br>
several others) have suggested, not a risk we should encourage<br>
unless the benefits and improvements are significant.<br>
<br></blockquote><div><br></div><div>The proponents seem to have demonstrat=
ed that there are proprietary systems in place.=C2=A0 So I believe the calc=
ulus of benefits and improvements must be done over a different set of data=
 points.<br><br></div><div>regards,<br><br></div><div>Ted<br></div><div><br=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 =C2=A0best,<br>
=C2=A0 =C2=A0 =C2=A0 john<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--001a11397f763dd6480548091be3--


From nobody Wed Feb  8 10:45:27 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CC83129D5F; Wed,  8 Feb 2017 10:45:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1IMlxQFGvj0c; Wed,  8 Feb 2017 10:45:22 -0800 (PST)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::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 A9AC6129D5A; Wed,  8 Feb 2017 10:45:16 -0800 (PST)
Received: by mail-wm0-x231.google.com with SMTP id v186so58857156wmd.0; Wed, 08 Feb 2017 10:45:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=OrUedj1qObAJC3HT2CAUKHthOOrhyJlWXWL7EpTCFVc=; b=KJasgwqvdrTCUd/jyLNl02dmKkF2Rr7rqwdEaLkFbUEX9LtEJkqyKLuPFnVQRRzOpO fM2xfhh8FTeXXLODFI5glG2Xakx7A4MgSnCObmX0zFTUuBLzdmNH/vP837ftmah8RF2i jWeme0vsKkeh6Cg6Onxi7H+hRYBHpY6/H29iqZoRFI66/42B5cmM3ELhAItLe3Uu9jHT +N206eYYsx7leqs/4Gey9dSAuErae0M51DoAhrZ3DQ5pZyr1QNrSx46YRLFysdovypYk AfaF3RqnXRlgwkLSgzx7zpWylI2ZM/AyvboAdIFe5u0hm/xkC5kIluKOWaYyV1Z3eL9o /uLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=OrUedj1qObAJC3HT2CAUKHthOOrhyJlWXWL7EpTCFVc=; b=K17nB3iNJXv+Odf1lJ1Ryg0PYwV3qMaTk8cp3qiR9imHSVnQy0orWDs12nrM0HRS4o MoteVZDx2ptmzEjsSjExUuF0UAwSy2DCmCmiUGbrArpYfTBJplkiffSTGeoHDTPR7vOo w5u3xiFympoWMYUqokRQkAcsHpUNxJSkviScu1n/hvM9aos9sbJ/FdG3APqgytFSSNP2 W6AXNIRnVCDeY5/DWq6k6pkt6crMl+0Lf9GCnzzOb2nyFZvhoj9XJZu4iYU8oelspr8q LzHCGtexQouYbu/syksL8z61s91CClo9vCZMKD6hBWqb+m3WEI3nA6VLy/Uwa0oOAEF9 eV/A==
X-Gm-Message-State: AMke39m+jLPsjkgxBeT0J/RHDOkmWxsCAmexqGRkzygWDu++TG97FF4MWr/23YB3/vBgNQ==
X-Received: by 10.28.229.193 with SMTP id c184mr20865500wmh.83.1486579515165;  Wed, 08 Feb 2017 10:45:15 -0800 (PST)
Received: from [192.168.1.14] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id e6sm14416601wrc.30.2017.02.08.10.45.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 10:45:13 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <7375E069-469A-4799-821E-684EEF885217@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2FA23AA9-C782-4202-9200-714F7259474A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-hardie-privsec-metadata-insertion-05
Date: Wed, 8 Feb 2017 20:45:10 +0200
In-Reply-To: <CA+9kkMCss+V2uAC9CYEQpe9FAwh3-F8EbRRCCtsgZYGhUpu=Dg@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
References: <148649922555.26656.10191520146576198408.idtracker@ietfa.amsl.com> <CA+9kkMCss+V2uAC9CYEQpe9FAwh3-F8EbRRCCtsgZYGhUpu=Dg@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4ZV4JoRc8HTUENypLT4eAeXEdi0>
Cc: draft-hardie-privsec-metadata-insertion.all@ietf.org, IETF <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 18:45:25 -0000

--Apple-Mail=_2FA23AA9-C782-4202-9200-714F7259474A
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_DE1FF170-8476-46FE-905C-2C6DA4653B69"


--Apple-Mail=_DE1FF170-8476-46FE-905C-2C6DA4653B69
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 7 Feb 2017, at 23:24, Ted Hardie <ted.ietf@gmail.com> wrote:
>=20
> On Tue, Feb 7, 2017 at 12:27 PM, Yoav Nir <ynir.ietf@gmail.com =
<mailto:ynir.ietf@gmail.com>> wrote:
> Reviewer: Yoav Nir
> Review result: Has Nits
>=20
> Hi
>=20
> The document is well-written and understandable, but a few things
> about it seem wrong:
>=20
> Section 3 describes data minimization as "one of the core mitigations
> for the loss of confidentiality". However, the only example given
> where data minimization is used to mitigate confidentiality loss is
> when browsers suppress cookies in private mode. The rest of the
> examples given (HTTP proxies, recursive DNS, VPN) are such where the
> data minimization is incidental to some other function. Nobody
> deployed the HTTP proxy or the DNS server in order to enhance
> privacy.
>=20
> So, I would challenge "nobody" on the HTTP proxy front, but that's not =
the important piece here.  The important piece is they generally do have =
a net privacy positive effect.  That privacy positive effect is =
eliminated when metadata that would be concealed by normal operation is =
added back in.  That's the converse of your statement:  no one built an =
HTTP proxy or recursive DNS server in order to supply metadata.
>=20
> Is there a specific place in the doc where more text would make this =
point clearer?

Perhaps an explanation of the phrase =E2=80=9Cother actors within a =
protocol=E2=80=9D in paragraph 2 of section 3. Is it just intermediaries =
(which according to the definition in RFC 6973 are necessary for the =
protocol) or are there any other entities? Is it existing middleboxes =
that new protocols seed to modify or entirely new middleboxes?

>=20
> The HTTP proxy example in particular is not convincing. HTTP is
> designed to work without proxies. Any data minimization provided
> incidentally by a proxy is nothing that can be counted on,
>=20
> I'm not sure what you mean by "counted on" here.  Do you mean that you =
can't know the pool of other users and thus the number of times you'll =
be served from cache rather than getting new data?

Just that I would never write a privacy considerations section that says =
=E2=80=9CThe source address of the client is obfuscated because NATs and =
proxies are everywhere=E2=80=9D. I can=E2=80=99t count on a proxy (or =
NAT) always being present, so I can=E2=80=99t count on them as the =
solution to the data minimization need. I *can* generally assume that =
clients will use a recursive DNS resolver.

> so a
> prohibition on restoring said data (especially in the case of a
> server-side load balancer) is just not convincing. OTOH in DNS
> recursive resolvers that hide the origin IP of the client are the norm
> - Authoritative servers hardly ever get to see real addresses of
> clients. In that case exposing the real IP address of the client shows
> data that was not there before.
>=20
> I believe the text should differentiate between cases where a network
> element is not part of the normal function of the protocol and works
> to undo the accidental data minimization that it causes,
>=20
> So, I think "accidental" is a tricky word here. The use of a proxy or =
recursive resolver is generally speaking not "accidental".  Data =
minimization is a consequence of normal operation, and what we're =
talking about is changing operations in order to change that data =
minimization.  The core of the advice is that instead of changing the =
operation of the middlebox, change the operation of the device about =
which you desire data.
>=20
> What would make that clearer?

Yes. Talking about changing the operation of the middlebox assumes that =
the middlebox already existed. So we already had a proxy, and now it=E2=80=
=99s adding new fields. Is the advice just about extending the =
functionality of existing intermediaries?

> and cases
> where the network element is expected in the protocol and thus the
> minimization is expected as well. I think the prescription in the text
> applies to the latter. I am not convinced about the former
>=20
> The VPN example is a strange one. If the subject is a corporate VPN,
> then restoring the original IP addresses is the function of the VPN.
> If, OTOH, VPN is that service that allows people to watch Hulu outside
> of the US, then restoring the IP address would be counter-productive.
> It is also strange to see VPN used as an example of "systems whose
> primary function is not to provide confidentiality"
>=20
> Well, it does two things:  shifts the network locality of the endpoint =
using the VPN and masks who is shifting.  I believe the first is the =
primary function and the second a common secondary property.  If you =
would like different language on this, though, please let me know.

To me VPN is mostly about providing confidentiality and data integrity =
while traversing the Internet.  How about

OLD
                            similarly a VPN system used to provide
   channel security may believe that origin IP should be restored.

NEW
                            similarly a VPN system restores all of
   the metadata associated with the IP packet at the tunnel egress.


Yoav

--Apple-Mail=_DE1FF170-8476-46FE-905C-2C6DA4653B69
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""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 7 Feb 2017, at 23:24, Ted Hardie &lt;<a =
href=3D"mailto:ted.ietf@gmail.com" class=3D"">ted.ietf@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"">On Tue, =
Feb 7, 2017 at 12:27 PM, Yoav Nir<span =
class=3D"Apple-converted-space">&nbsp;</span><span dir=3D"ltr" =
class=3D"">&lt;<a href=3D"mailto:ynir.ietf@gmail.com" target=3D"_blank" =
class=3D"">ynir.ietf@gmail.com</a>&gt;</span><span =
class=3D"Apple-converted-space">&nbsp;</span>wrote:<br class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;">Reviewer: Yoav Nir<br =
class=3D"">Review result: Has Nits<br class=3D""><br class=3D"">Hi<br =
class=3D""><br class=3D"">The document is well-written and =
understandable, but a few things<br class=3D"">about it seem wrong:<br =
class=3D""><br class=3D"">Section 3 describes data minimization as "one =
of the core mitigations<br class=3D"">for the loss of confidentiality". =
However, the only example given<br class=3D"">where data minimization is =
used to mitigate confidentiality loss is<br class=3D"">when browsers =
suppress cookies in private mode. The rest of the<br class=3D"">examples =
given (HTTP proxies, recursive DNS, VPN) are such where the<br =
class=3D"">data minimization is incidental to some other function. =
Nobody<br class=3D"">deployed the HTTP proxy or the DNS server in order =
to enhance<br class=3D"">privacy.<br class=3D""></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">So, I would challenge =
"nobody" on the HTTP proxy front, but that's not the important piece =
here.&nbsp; The important piece is they generally do have a net privacy =
positive effect.&nbsp; That privacy positive effect is eliminated when =
metadata that would be concealed by normal operation is added back =
in.&nbsp; That's the converse of your statement:&nbsp; no one built an =
HTTP proxy or recursive DNS server in order to supply =
metadata.&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><br =
class=3D""><br class=3D""></div><div class=3D"">Is there a specific =
place in the doc where more text would make this point clearer?<br =
class=3D""></div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>Perhaps an explanation of the phrase =E2=80=9Cother =
actors within a protocol=E2=80=9D in paragraph 2 of section 3. Is it =
just intermediaries (which according to the definition in RFC 6973 are =
necessary for the protocol) or are there any other entities? Is it =
existing middleboxes that new protocols seed to modify or entirely new =
middleboxes?</div><div><br class=3D""></div><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;"><br class=3D"">The HTTP =
proxy example in particular is not convincing. HTTP is<br =
class=3D"">designed to work without proxies. Any data minimization =
provided<br class=3D"">incidentally by a proxy is nothing that can be =
counted on,<span =
class=3D"Apple-converted-space">&nbsp;</span></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">I'm not sure what you =
mean by "counted on" here.&nbsp; Do you mean that you can't know the =
pool of other users and thus the number of times you'll be served from =
cache rather than getting new =
data?</div></div></div></div></blockquote><div><br =
class=3D""></div><div>Just that I would never write a privacy =
considerations section that says =E2=80=9CThe source address of the =
client is obfuscated because NATs and proxies are everywhere=E2=80=9D. I =
can=E2=80=99t count on a proxy (or NAT) always being present, so I =
can=E2=80=99t count on them as the solution to the data minimization =
need. I *can* generally assume that clients will use a recursive DNS =
resolver.</div><br class=3D""><blockquote type=3D"cite" class=3D""><div =
dir=3D"ltr" style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;">so a<br =
class=3D"">prohibition on restoring said data (especially in the case of =
a<br class=3D"">server-side load balancer) is just not convincing. OTOH =
in DNS<br class=3D"">recursive resolvers that hide the origin IP of the =
client are the norm<br class=3D"">- Authoritative servers hardly ever =
get to see real addresses of<br class=3D"">clients. In that case =
exposing the real IP address of the client shows<br class=3D"">data that =
was not there before.<br class=3D""><br class=3D"">I believe the text =
should differentiate between cases where a network<br class=3D"">element =
is not part of the normal function of the protocol and works<br =
class=3D"">to undo the accidental data minimization that it =
causes,</blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">So, I think "accidental" is a tricky word here. The use of a =
proxy or recursive resolver is generally speaking not =
"accidental".&nbsp; Data minimization is a consequence of normal =
operation, and what we're talking about is changing operations in order =
to change that data minimization.&nbsp; The core of the advice is that =
instead of changing the operation of the middlebox, change the operation =
of the device about which you desire data.<br class=3D""><br =
class=3D""></div><div class=3D"">What would make that clearer?<br =
class=3D""></div></div></div></div></blockquote><div><br =
class=3D""></div>Yes. Talking about changing the operation of the =
middlebox assumes that the middlebox already existed. So we already had =
a proxy, and now it=E2=80=99s adding new fields. Is the advice just =
about extending the functionality of existing =
intermediaries?</div><div><br class=3D""><blockquote type=3D"cite" =
class=3D""><div dir=3D"ltr" style=3D"font-family: Helvetica; font-size: =
12px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote =
class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex;">and cases<br =
class=3D"">where the network element is expected in the protocol and =
thus the<br class=3D"">minimization is expected as well. I think the =
prescription in the text<br class=3D"">applies to the latter. I am not =
convinced about the former<br class=3D""><br class=3D"">The VPN example =
is a strange one. If the subject is a corporate VPN,<br class=3D"">then =
restoring the original IP addresses is the function of the VPN.<br =
class=3D"">If, OTOH, VPN is that service that allows people to watch =
Hulu outside<br class=3D"">of the US, then restoring the IP address =
would be counter-productive.<br class=3D"">It is also strange to see VPN =
used as an example of "systems whose<br class=3D"">primary function is =
not to provide confidentiality"<br class=3D""><br =
class=3D""></blockquote><div class=3D"">Well, it does two things:&nbsp; =
shifts the network locality of the endpoint using the VPN and masks who =
is shifting.&nbsp; I believe the first is the primary function and the =
second a common secondary property.&nbsp; If you would like different =
language on this, though, please let me know.<br =
class=3D""></div></div></div></div></blockquote><div><br =
class=3D""></div>To me VPN is mostly about providing confidentiality and =
data integrity while traversing the Internet. &nbsp;How =
about</div><div><br class=3D""></div><div>OLD</div><div><pre =
class=3D"newpage" style=3D"font-size: 13.333333015441895px; margin-top: =
0px; margin-bottom: 0px; page-break-before: always;">                    =
        similarly a VPN system used to provide
   channel security may believe that origin IP should be =
restored.</pre><div class=3D""><br =
class=3D""></div></div><div>NEW</div><div><pre class=3D"newpage" =
style=3D"font-size: 13.333333015441895px; margin-top: 0px; =
margin-bottom: 0px; page-break-before: always;">                         =
   similarly a VPN system restores all of
   the metadata associated with the IP packet at the tunnel =
egress.</pre><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Yoav</div></div></body></html>=

--Apple-Mail=_DE1FF170-8476-46FE-905C-2C6DA4653B69--

--Apple-Mail=_2FA23AA9-C782-4202-9200-714F7259474A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYm2c2AAoJELhJCxUKWMyZqxQH/RWrUrtijLQgfiCsModM9m5M
LkWN3jiiQqzP3dX7GuqHDOxRGvN7u5o6h7KLEdvQRG20zVWdA+1XGWb09uV1MxEn
gu+bK0vHxxbvwAiE1wWDtr5INhZxCPru0ZUrYAw0BeZfj6E4TyIb8pU5Nwtlbht6
HJSlVtIN0eaXWsm7BzYzYwfSIZUD/hWaQMCrMeuykRhK4SxofdW63FX5CDZv/z4o
JCNmj3rVedohYif/GegTSlV1aAugqIMxuWJU4QQANHmYSukSksfXUd1N/WMysI7r
7RZfVd/36wgWhkpU7VmMn/Iy6QY2rCD8lJewDYp3mzQi01FipPAl8kW0vSUDLpE=
=DOMo
-----END PGP SIGNATURE-----

--Apple-Mail=_2FA23AA9-C782-4202-9200-714F7259474A--


From nobody Wed Feb  8 10:53:52 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9B1D129D5A; Wed,  8 Feb 2017 10:53:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4SnA9Qp83rIN; Wed,  8 Feb 2017 10:53:43 -0800 (PST)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 8C36912942F; Wed,  8 Feb 2017 10:53:40 -0800 (PST)
Received: by mail-wr0-x241.google.com with SMTP id 89so9580023wrr.1; Wed, 08 Feb 2017 10:53:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dSh5msw0htlLNOsZ/NeV73oOzEIZnCDE3zTnMjv/iQ8=; b=iI/ImBSHNj0YjSA7Cirb5WhKKkzGiqXhga3PfylThA4CRA4JphKtPYtVyuAqoVVVd4 u0kt1+h1c1Z8PHWF+cMVgm+MsEbeoM6N4IAFX9JPF6urM1T71sn/c2006omCXA80YLia PCSUI/WhXbDwY5hi/h0BQ2c9LLRrfNC76M3Y6j/8ATjfTV5EdPXzvsFkGSiphW1WyZZu YQPwY/hjYugiltGIOiN5nRcHlZKJ4hX1buV5MgOMoUt16x1dGPWJHXiNSOHZXJbDVxvM yySMyZAVNONSGT0aqy5IDH5OpfUkHW8EUh+9Wz6O0emF4D/vXIvdcpFPKHEflKiE76je Gwsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dSh5msw0htlLNOsZ/NeV73oOzEIZnCDE3zTnMjv/iQ8=; b=tTjV+Eyij9CKrf+tFyU0mpW0oSCiBnceDMfEBoXmcgMPHKftx+PRG8d5viTJgTwisr FaWx6VbxeLGhTuiGY+4uzJXadBTnKnsV7iZSaz8LVbqrzIuBDqf0w7KJpwR6eg9NCHBq moYEMQ0/r2MJh0JvFhpL/IO6uaovLCmt8PTjrmScjKoLgUuV1wginxFtjuXWFbxPEOqK bKLQ/1/1/5tnx03xswmyM6wZl44WvBRhRUbDN+iLCr8awfLLcTjiu8bl9hEqGQuqNv3R xmHgg3wkQuqtRtD3Qg9CzWYEVF0J9x2xPRGS9ZoBaE+f8t1UK/x11HmjH//Q6wnDCcWG BIvA==
X-Gm-Message-State: AIkVDXIHH8ojbzAQxZSk6NQVgMyZ6AXOFX4+K6DuCPZ3s8B1RT6QiAmWpirVLkW2d4htlQ==
X-Received: by 10.223.154.165 with SMTP id a34mr11930137wrc.193.1486580018862;  Wed, 08 Feb 2017 10:53:38 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id h3sm14502051wrb.31.2017.02.08.10.53.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 10:53:38 -0800 (PST)
Subject: Re: Review of draft-ietf-pals-mpls-tp-dual-homing-protection-05
To: Russ Housley <housley@vigilsec.com>, gen-art@ietf.org
References: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <baf6ae46-3d87-4930-9d9f-1e7febfb07e9@gmail.com>
Date: Wed, 8 Feb 2017 18:53:36 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <148649120072.19411.7489137402403290375.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RmsB7EnBY7jrxaHetGNtoS-oJAc>
Cc: draft-ietf-pals-mpls-tp-dual-homing-protection.all@ietf.org, ietf@ietf.org, pals@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 18:53:45 -0000

Hi Russ

Thank you for the review.

I would like to respond to one point:


> Notes:
>
> I see that draft-cheng-pwe3-mpls-tp-dual-homing-protection the
> earlier
> Internet-Draft file name for this document.  An IPR declaration was
> issued against that earlier name.  The shepherd write-up indicates
> that
> "The WG were not concerned about the IPR disclosure." However, it is
> unclear to me whether we should ask for the IPR declaration to be
> issued
> against the current Internet-Draft file name.
>

The authors all responded including of course the author from the 
company that
filed the IPR. All indicated that no additional IPR was known about.

The IPR disclosure shows up in datatracker.

We do not normally chase companies to update their IPR disclosures, as
documents progress, and indeed if we chase them to do this update we need
to chase them shortly for a further one as the draft becomes an RFC.

Since you pointed it out we have asked the author to ask his patent dept
to do the update, but I hope that this does not become an IETF policy
making it even harder to pass the IPR checks that we put in place in RTG.

Thanks

Stewart



From nobody Wed Feb  8 11:06:12 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C743129D9C for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 11:06:11 -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 autolearn_force=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 0dNm1qkPyCIj for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 11:06:10 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65680129DD0 for <ietf@ietf.org>; Wed,  8 Feb 2017 11:06:09 -0800 (PST)
Received: (qmail 25701 invoked from network); 8 Feb 2017 19:06:08 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 8 Feb 2017 19:06:08 -0000
Date: 8 Feb 2017 19:05:46 -0000
Message-ID: <20170208190546.15385.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4mGRyml5SLEPyr4ecKS-zs5fgnE>
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 19:06:11 -0000

>This creates a dual-stack operational environment.  They always have
>real -- and often problematic -- operational effects.

Well, we've survived with POP and IMAP for two decades.  

We might want to put something in the charter noting that the
underlying mail has to be RFC822/5322, but the drafts all seem to
assume that.

Re separating mail pickup from submission, I understand why we decided
to keep it separate when we did RFC4409, but that was a decade ago and
the mail world has changed.  In particular, I don't think anyone in
2006 expected that the majority of mail users would be sending and
receiving mail using apps on the phones in their pockets.  

At this point, if someone says that their POP/IMAP/JMAP and SUBMIT
servers need different credentials, I'd suggest that is a cruel joke
to play on your users, you should fix it, and while you're at it,
you should accept submission through JMAP, too.  If you can't fix
it, there will still be some IMAP and SUBMIT clients for a long time.

R's,
John


From nobody Wed Feb  8 13:09:08 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9421295E9 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:09:07 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NYd3bEX1vs1X for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:09:05 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id 6982D1294C7 for <ietf@ietf.org>; Wed,  8 Feb 2017 13:09:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1486588144; d=isode.com; s=june2016; i=@isode.com; bh=B6zrYqohtMAI666nne50Uxl6z7E4KUItKX0CYRK92bU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=mPPVy2j/ucF+nnhagmnupKGJyAZDOvIDMuoQSzynJht08lv592hzrQ+G/dubjbnosOhC4j m6iYgkdh48H7JMhWwsqOaOez/vtVAb+57qS3NLMdZVg/oD9uybhwe3WAua97/Op8al9nij lLIFJ543ur8DaqB9wnxhyt6NPKVYTLM=;
Received: from [192.168.0.14] (cpc5-nmal20-2-0-cust24.19-2.cable.virginm.net [92.234.84.25])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WJuI7gAY15ql@statler.isode.com>; Wed, 8 Feb 2017 21:09:04 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
To: dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net>
Message-ID: <589B88E4.4000208@isode.com>
Date: Wed, 8 Feb 2017 21:08:52 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/etn9Nv2U2XvU7V1ZZiCVDATSmF8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 21:09:07 -0000

Dave and John,

On 08/02/2017 15:33, Dave Crocker wrote:

> On 2/8/2017 7:03 AM, John C Klensin wrote:
>> However, from the perspective of someone trying to maintain servers
>> or a mailstore, the fact that there will be both types of users (for
>> a long time if not forever), it implies the need to maintain (and
>> configure, support, etc.) both IMAP/SMTP and JMAP facilities in
>> parallel and to support, also for a long time, the ability to convert
>> between the two formats.  Also, if that conversion is not absolutely
>> lossless, there will be a large collection of ongoing problems, for
>> an equally long time.
>
> +1
>
> This creates a dual-stack operational environment.  They always have
> real -- and often problematic -- operational effects.
>
> Given the long-standing complaints about IMAP's complexity, it still
> might be worth doing.  But as has already been noted, what is required
> here is a very compelling value statement that justifies the second
> 'stack'.
>
> The posted list of folk who are expected to implement this helps quite =
a
> bit, IMO.  However we seem to be missing the compelling
> /technical-operations/ value proposition.  Will the resulting protocol
> be simpler, more efficient, faster, ... and what is the basis for
> asserting such improvements?

Neil Jenkins did a very good summary of existing problems and how JMAP
is trying to improve over IMAP:
<https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html>
> On 2/6/2017 7:40 AM, Alexey Melnikov wrote:
>> The current proposal is "advancing on the old". It is improving on
>> some IMAP use cases
>
> Where is this explained in the charter -- with enough detail to make it=

> possible to assess it?  This seems to me foundational for the effort's
> value proposition.
See pointer to Neil's email above. The list of improvements is rather
long, so I didn't want to include it in the Charter. Instead, the
Charter already says:

The working group will deliver the following:

- A problem statement detailing the deployment environment and
  situations that motivate work on a new protocol for client to
  server email synchronisation.  The working group may choose
  not to publish this as an RFC.

This item was intended to cover exactly that.
> On 2/8/2017 5:34 AM, Alexey Melnikov wrote:
>>> Drafts?  What drafts?  Perhaps you mean:
>>>
>>> https://tools.ietf.org/html/draft-jenkins-jmap
>>>
>>> Except that no draft is cited in the charter.
>>
>> I realized that I accidentally deleted an important sentence from
>> the Charter while doing editing. One of the paragraphs should have
>> read:
>>
>> The work of this group is limited to developing a protocol for a
>> client synchronising data with a server. The work will be based on
>> draft-jenkins-jmap and draft-jenkins-jmapmail. Any server-to-server
>> issues are out of scope for this working group. New end-to-end
>> encryption mechanisms are out of scope, but the work should consider
>> how to integrate with existing standards such as S/MIME and OpenPGP.
>
> Ahh.  Yes, very helpful.  Thanks!
>
> This then raises a point of nuance about a charter's reference to the
> documents that are foundational to a working group effort:  indicating
> constraints on their role.  That is, what is the working group
> authorized to do with the document. This can be extremely helpful with
> working group management and helping participants to focus.
>
> Roughly the choices are a continuum between having no constraints --
> the doc is simply used as input and advice -- all the way to only
> being permitted to fix bugs and improve editorial writing.
>
> The text you've provided here says 'based on'.  In a more benign
> world, clarifying what that means wouldn't be necessary, but in the
> current reality, I urge adding text that indicates why degree of
> modification the wg is allowed to make on the drafts.

I think this is an excellent idea and I will add more text to the
charter about constraints/expected changes.

Best Regards,
Alexey



From nobody Wed Feb  8 13:09:39 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A88B129E42; Wed,  8 Feb 2017 13:09:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9IejeTjJQLUt; Wed,  8 Feb 2017 13:09:34 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A0901294C7; Wed,  8 Feb 2017 13:09:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486588173; x=1518124173; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=TQdbDC1CauWtGC4Qdc6wIWzATiXEji2tj4Up325uGDQ=; b=RRIr8vWDdOU4OlSfVg+Z8s+8iC68RwbbB/7rEkBsZgQFOobr9jJm+Oru wW+JKzzXdKEM3iAhmaPTEFm9x6in3x/ov0/AIt8/mXInVbM0aMy2CGXjh CSkkRVVSL7eUPwPd42S3cyXqv9700qtaMbIxx6z3SxAprrBHKXYXPfJuK M=;
X-IronPort-AV: E=Sophos;i="5.35,348,1484035200"; d="scan'208";a="261249695"
Received: from unknown (HELO Ironmsg04-R.qualcomm.com) ([10.53.140.108]) by wolverine01.qualcomm.com with ESMTP; 08 Feb 2017 13:09:33 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8433"; a="1359869645"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Feb 2017 13:09:32 -0800
Received: from [10.64.115.82] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 8 Feb 2017 13:09:32 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Ted Lemon <mellon@fugue.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Wed, 8 Feb 2017 15:09:30 -0600
Message-ID: <7822918B-0312-4EC5-A8F0-3F9BFEF54BBB@qti.qualcomm.com>
In-Reply-To: <A86D15F6-59C1-4AE3-BA56-2747DD7345CC@fugue.com>
References: <CAMQk0F-6CFLHKvTxSaPV20Lp-hVOSSk_WrHOGq6-LOUO8aDNww@mail.gmail.com> <m2poitydi9.wl-randy@psg.com> <9D66E5E7619E1C55F1DEB959@PSB> <1A1381DB-DF79-4FC8-88F4-60A0AF4FE3CA@cursive.net> <b482dda6-2db9-a64b-e31c-f1c07ab92269@dcrocker.net> <1486523704.3711423.873904592.78C4EAA8@webmail.messagingengine.com> <D983A02B-B530-454D-A8A6-9D9CF432D31E@gmail.com> <A86D15F6-59C1-4AE3-BA56-2747DD7345CC@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5344)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bbA41aGe7_8tdDTHxpXSgBy9KVM>
Cc: jmap@ietf.org, Neil Jenkins <neilj@fastmail.com>, IESG <iesg@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 21:09:35 -0000

On 8 Feb 2017, at 9:52, Ted Lemon wrote:

> IMAP and POP both use the wrong data abstraction, and consequently are 
> very hard to get right, and generally aren't gotten right.
>
> So a new protocol that has the data abstraction right is actually a 
> substantial improvement.   I don't know if that's the case with 
> JMAP—if it's the same data abstraction as IMAP, it's not worth 
> bothering with, but that's something that at least in theory can be 
> discussed.
>
> What JMAP does afford is the opportunity to have an embedded web 
> client that doesn't suck, and a way to escape it if you want something 
> more stateful.

Yep, this is the bit that convinces me that this effort should go 
forward. IMAP's problem has always been its combination of semantic 
bottleneck and leakage: It constrained the semantics that you could 
communicate across the pipe in some ways (hence the myriad of extensions 
required to have a workable IMAP implementation), but leaked a bunch of 
server-specific semantics (e.g., the storage model, the constraints on 
network resources) through to the client instead of having a clean 
protocol. Putting a rich and leak-free protocol in front of IMAP is an 
improvement, and being able to remove IMAP from the equation eventually 
is a laudable goal.

Yes, there are transition and conversion issues. But I haven't heard 
anyone come up with a solution to the problems inherent in IMAP that 
doesn't involve transition pain. The answer can't simply be, "Never 
attempt to solve the IMAP implementation problems" or "Only solve IMAP 
implementation problems within IMAP". Neither one of those answers leads 
to a solution.

(BTW: The submission issue seems a rather boring one to me. There's 
never been good deployment of BURL and the other LEMONADE mechanisms to 
make it happen. If this work just creates a decent protocol interface to 
those submission mechanisms, more power to them. I don't think there's 
anything magical here.)

I have no objection to clarifying the charter in many of the ways 
suggested to make clear what the motivations are and what the 
constraints are on the work, but overall I think this effort should go 
forward.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Feb  8 13:16:52 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB7E11295A9 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:16:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42l-ivddPtZO for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:16:49 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 33B10129472 for <ietf@ietf.org>; Wed,  8 Feb 2017 13:16:49 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id v23so178552166qtb.0 for <ietf@ietf.org>; Wed, 08 Feb 2017 13:16:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=CZDM119sv8cyItjr+mP84IEGJA2Dy8+LBV96AeUwpRA=; b=ueo+CfGBrU+wRFtdx4kX4KGuH8AcNV1Vbb9zA2qVbAdWxwsZz1L5e0ne+zX/bpgpho O1wmeMvvXWxsKukhNJgGbpxKDS9TH7b8YbD+gFe2CWwjVi6DIdxAgxqM7Vg8fTExCUBT Bx/VVNVFoIz6+1tNYlZ9Tmn/tq6xNDhJrIbl4+ih/MFJXJe4HgMx1Gvj0rvQfEpFZBwS pvPaItuk+YfEiRfaSCjzdENA36TSmpMy5NxEpuRNLUTEUFqVANtIyml2H5G4FzN95kup Zq0b0kK6VyDheyRHvSZQ9vtHScBxED/X1TR+8Xsr2TcWcRcHUR9iEIEFABpvypYyxmbg Obqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=CZDM119sv8cyItjr+mP84IEGJA2Dy8+LBV96AeUwpRA=; b=qX46fsigRQDxBvaFi7aFcG7q2kGMa9YlEzMuLdoXYnioXqmeYB7keCEsKs3iBkQE1S uu1kR+g13LKkISKq1HxGBfQ72umS+y6WJbj/5n8aX5simhJc0HH7WQwUk9OL6yr6S/BF ls7iK7PnoLUA9ANaRaqlvagFiO4LpFYH3BbL4hLWyCDeXT8ObFW6bMM0PwgRvToM2Zh9 5FSH6JI4tGIa5hMs+of6Zj4hbG27jItk0EyFstLDfycBYdteHVtfceHOU9mjgFWISdR2 wMSrRnZNh3L8Y13rqR75MiMPWJUBK66yRip9b01/meV5kAmyErafL36TW6Ae8aYstBS4 Nlog==
X-Gm-Message-State: AMke39kCzJUVaTakQ4S5mb4MAGOslPhJbB3IgWGrYm1j1wnsqLDfthfwJL4qy+PseZC+2Q==
X-Received: by 10.200.41.3 with SMTP id y3mr21029223qty.205.1486588608406; Wed, 08 Feb 2017 13:16:48 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 142sm7234959qkf.16.2017.02.08.13.16.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 13:16:47 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <3755CBD4-7614-48E1-BB80-F847934A787A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E3CFB9AE-B84B-4446-B767-F4FF805F4BE1"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Wed, 8 Feb 2017 16:16:45 -0500
In-Reply-To: <589B88E4.4000208@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net> <589B88E4.4000208@isode.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HFtxUdqYEA2QEbG1MlY1ieWSI5A>
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 21:16:51 -0000

--Apple-Mail=_E3CFB9AE-B84B-4446-B767-F4FF805F4BE1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 8, 2017, at 4:08 PM, Alexey Melnikov <alexey.melnikov@isode.com> =
wrote:
> Neil Jenkins did a very good summary of existing problems and how JMAP
> is trying to improve over IMAP:
> <https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html =
<https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html>>

Wow, this is _really_ useful.   Thank you for pointing it out.


--Apple-Mail=_E3CFB9AE-B84B-4446-B767-F4FF805F4BE1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 8, 2017, at 4:08 PM, Alexey Melnikov &lt;<a =
href=3D"mailto:alexey.melnikov@isode.com" =
class=3D"">alexey.melnikov@isode.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Neil Jenkins did a =
very good summary of existing problems and how JMAP</span><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">is trying to improve over IMAP:</span><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">&lt;</span><a =
href=3D"https://www.ietf.org/mail-archive/web/imapext/current/msg05820.htm=
l" style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mail-archive/web/imapext/current/msg05820.=
html</a><span style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">&gt;</span></div></blockquote></div><br =
class=3D""><div class=3D"">Wow, this is _really_ useful. &nbsp; Thank =
you for pointing it out.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_E3CFB9AE-B84B-4446-B767-F4FF805F4BE1--


From nobody Wed Feb  8 13:52:01 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B03631294DC for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:51:59 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAFwMbhPTY4S for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 13:51:58 -0800 (PST)
Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (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 2B1421293FB for <ietf@ietf.org>; Wed,  8 Feb 2017 13:51:58 -0800 (PST)
Received: by mail-it0-x243.google.com with SMTP id 203so405846ith.2 for <ietf@ietf.org>; Wed, 08 Feb 2017 13:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=A1xNVVj6OE2sP5m9jN+/vVlgBmxo0Lnj3++PHduyRVo=; b=eq642FdRwyy3RIozfzeIvEgGorOj/fYZN83hbeCDO9VvCC1uvnCQiHD0O4vOufdfLC eArl7nMKfunQbwm4W5HgRMPOYqhmxD3CO7t4xMbMRwTJU5eWF7D/Bab2dZ3JKSyjrSf7 SubEX285yaVa6Y/rr8GYvAbm8lrga58th2oCSESM4srnHDVmPsGCOdZs2jhtZ/KnZs7i wwAr1iYvtZlUtxRVOidxKjBDTbBpJApu8y0bGkLyTWDtgKo6ekm2Pk9rzmts0Ul66+Xz XPzBKolkN5aFKQxF95SGmIU6c7CI2DrKqL15KA1gWNVifqxQmf2i2pNd9N4ZaQoL5E4x fnSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=A1xNVVj6OE2sP5m9jN+/vVlgBmxo0Lnj3++PHduyRVo=; b=NWWO28DK51jpeoxbanlbbq0P2rFX1zlJxwCW8Xgp/xUPOq0arz09ajc950gtUq8sGp b8Cude4W2SrpK1FrmpasuzX60ysJKUaPEOsMdgc0L7JV8H+TOZ9SQWneygYwcX7ni7Y8 Oa3aspFGmfevkUxLMQQxc7KCWxTcZtMtpWxz6TynmKlbA2lefFD5OYPUI9q4oqX0F3Xo cIdAlgMiCpSRdXCTlPSAxB3i9AM/JN3cY6ElEI02WcB4TMNOrqjTwSRLAuBmLVbEOWzx z8rbikpQ8bURadrVm/MNLLUY8ObvwSEFSCGk+vx970MU+chYUfG6IHMLBvm3x3mfwPne myyg==
X-Gm-Message-State: AIkVDXL131RSjHj4KziAuyeuSF4PVknhYMsuUtsDpyhRwpyQSLBXdBJXv3hVwRIT/CRzxA==
X-Received: by 10.84.212.2 with SMTP id d2mr36570376pli.152.1486590717352; Wed, 08 Feb 2017 13:51:57 -0800 (PST)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by smtp.gmail.com with ESMTPSA id p15sm22759005pfk.58.2017.02.08.13.51.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Feb 2017 13:51:56 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: Randy Bush <randy@psg.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com> <m2lgthw9v9.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com>
Date: Thu, 9 Feb 2017 10:51:57 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <m2lgthw9v9.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UT-yVMayvlhwE9S8YJ-eDmtZr4k>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 21:51:59 -0000

On 08/02/2017 18:05, Randy Bush wrote:
>>> Would something like this help?
>>> (borrowed from https://en.wikipedia.org/wiki/Path_MTU_Discovery)
>>>
>>> "Many network security devices block all ICMP messages for perceived
>>>  security benefits, including the errors that are necessary for the proper
>>>  operation of PMTUD. This can result in connections that complete the
>>>  TCP three-way handshake correctly, but then hang when data is transferred.
>>>  This state is referred to as a black hole connection."
>>
>> Yes. What we are asked to do for Internet Standard is show that a protocol
>> is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
>> The fact that it also has an important failure mode should certainly be
>> documented, but I suspect that every Internet Standard has at least
>> one important failure mode.
> 
> the problem is that this particular failure mode is essentially "does
> not work on the real internet."  perhaps documenting that is useful.
> but i guess this is ipv6.

I fully agree that it should be documented, but the details are already
documented elsewhere. In this document it can be quite short.

It isn't just because it's IPv6, although I haven't noticed any recent
attempts to promote RFC 1191 to Internet Standard. There is RFC 1435 of
course, which says that RFC 1191 doesn't work. That went unanswered for
14 years, until RFC 4821.

   Brian


From nobody Wed Feb  8 14:16:29 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387D0129621 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:16:20 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xII1dlhauFB2 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:16:14 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 3871712955E for <ietf@ietf.org>; Wed,  8 Feb 2017 14:16:14 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v18MHpVX007076 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 8 Feb 2017 14:17:52 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1486592272; bh=LW074sGnUO9Q7MrUdc2lDpPpyhT5SXUtnm97equOam8=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=oeABQ25O3LhaAFIYkhciGislrddPqBBldzNaRo46Th1q6RCMB23TQybQ8dQ0sLlPC 9BYJKpW/m6qE+DT052Ks/fYW5iPp9aQurZE1yT+ifM+LcMEeTUykJB0cHXGby/jezQ yZOaKL6sogNR2hwto/+ZTFKSj69QTv+ZJiy8NxDw=
Subject: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Ted Lemon <mellon@fugue.com>, Alexey Melnikov <alexey.melnikov@isode.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <e9e8141f-0bc2-870e-c10e-d8894673e455@dcrocker.net> <589B88E4.4000208@isode.com> <3755CBD4-7614-48E1-BB80-F847934A787A@fugue.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <525252eb-1c38-5549-1725-594b539a606e@dcrocker.net>
Date: Wed, 8 Feb 2017 14:16:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <3755CBD4-7614-48E1-BB80-F847934A787A@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/udCF_Re47WvQsBh6q79BxjyG5zI>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 22:16:20 -0000

On 2/8/2017 1:16 PM, Ted Lemon wrote:
> On Feb 8, 2017, at 4:08 PM, Alexey Melnikov
> <alexey.melnikov@isode.com <mailto:alexey.melnikov@isode.com>>
> wrote:
>> Neil Jenkins did a very good summary of existing problems and how
>> JMAP is trying to improve over IMAP:
>> <https://www.ietf.org/mail-archive/web/imapext/current/msg05820.html>
>
>>
> Wow, this is _really_ useful.   Thank you for pointing it out.

Sure is.

This, and Pete's note, have finally given me enough to be able to
suggest specific changes to the charter.

The underlying concern I've been pressing is that a working group
charter needs to make its case in pragmatic terms, with enough detail to
aid someone who is not already onboard to assess the proposed effort.


So I suggest replacing:

> A number of JSON-based representations of email have been developed
> that are proprietary, non-standard, and incompatible with each other.
...
> The JMAP working group will specify a mechanism to allow clients to
> both view and send email from a server over a single HTTPS
> channel with minimal round trips. A single protocol for receipt and
...


with:

> JMAP specifies the interactions between email clients and mail
> stores, providing an alternative to IMAP and SMTP submission. JMAP
> allows clients to both view and send email via a server, over a
> single HTTPS channel, with significantly reduced computational and
> communication resource consumption.
 >
> Currently it is difficult to write a good MUA using standards; it is
> especially problematic for embedded web clients. IMAP suffers the
> combination of semantic bottleneck and leakage: It constrains the
> semantics that can be communicated across the pipe in some ways
> (hence the myriad of extensions required to have a workable IMAP
> implementation), but leaks various server-specific semantics (e.g.,
> the storage model, the constraints on network resources) through to
> the client instead of having a clean protocol. Further, the protocols
> perform poorly over constrained channels.


d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Wed Feb  8 14:32:51 2017
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC93C12A050 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 hiFmEv1L5CkZ for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:32:48 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 EC129129E5B for <ietf@ietf.org>; Wed,  8 Feb 2017 14:32:47 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QANBYRNVN4006UTI@mauve.mrochek.com> for ietf@ietf.org; Wed, 8 Feb 2017 14:27:44 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QAFLDF17XS0005AQ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 08 Feb 2017 14:27:39 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01QANBYPRC140005AQ@mauve.mrochek.com>
Date: Wed, 08 Feb 2017 12:39:30 -0800 (PST)
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-reply-to: "Your message dated Wed, 08 Feb 2017 16:36:45 +0000" <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2rmwRvUgEgGeCGcGPWiiR4Z37rQ>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 22:32:49 -0000

> That is entirely possible :-).
> > Except for the small
> > minority of users who switch MUAs back and forth (see below),

FWIW, this is not a small minority any more. A fair number of people own and
use multiple mobile devices and access their email from all of them.

> > I would expect any given user to use either an IMAP approach, a
> > JSON or JSON-like one, or neither.    No long transition as far
> > as they are concerned.    However, from the perspective of
> > someone trying to maintain servers or a mailstore, the fact that
> > there will be both types of users (for a long time if not
> > forever), it implies the need to maintain (and configure,
> > support, etc.) both IMAP/SMTP and JMAP facilities in parallel

> As far as deployments are concerned, if there is a case of
> co-existentence, then it would fall into one of two categories:

> 1). JMAP is just a a proxy and uses IMAP on the backend. Configuring
> JMAP server is the same as configuring a MUA.

This is a key point. A lot of people have criticized this proposal based on the
assumption that new clients will have to support both IMAP/SUBMIT and JMAP.

I think this is very unlikely to be the case. Once JMAP is out there I suspect
there will be a significant number of clients - perhaps the majority - that
will only support JMAP.

These clients will depend on a combination of (1) Large MSPs quickly moving to
deploy JMAP in addition to IMAP, (2) The availability of JMAP->IMAP/SUBMIT
proxies, and (3) The addition of JMAP support to at least some of the open
source message store implemenations.

(2) in particular creates additional requirements that need to be explicitly
called out in the charter. In particular, it's imperative that (a) It be
reasonable to implement JMAP->IMAP/SUBMIT proxies, even if that constrains JMAP
in ways some folks do not like, (b) The list of IMAP extensions needed to
properly implement JMAP be called out, and (c) The security considerations
involved in operating such a proxy need to be described in detail.

> 2). Both are supported by the same software (i.e. Cyrus and Dovecot use
> case). I doubt that incremental cost of configuring both is much higher
> than just configuring one of them.

> In either case configuring JMAP clients is a simple(r) proposition: just
> distribute HTTP URI for a JMAP instance.

> > and to support, also for a long time, the ability to convert
> > between the two formats.

> There are no 2 formats, both IMAP and JMAP operate on RFC 5322 objects,
> so the rest of your argument is invalid.

Agreed. I have to say I really don't understand the confusion surrounding this
point. IMAP has bodystructure plus a couple of other formats for returning
message data, and a means of creating new messages from pieces of other
messages, none of which look remotely like MIME/RFC 5322, and nobody cares.

This is effectively the same thing; why should anyone care here?

				Ned


From nobody Wed Feb  8 14:57:38 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC15E12A0A3 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:57:36 -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 autolearn_force=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 RRfO5DgY2bmc for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 14:57:36 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 EA0E31294E5 for <ietf@ietf.org>; Wed,  8 Feb 2017 14:57:35 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cbbB8-0003DC-6m; Wed, 08 Feb 2017 22:57:34 +0000
Date: Thu, 09 Feb 2017 07:57:32 +0900
Message-ID: <m2fujouw83.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
In-Reply-To: <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com> <m2lgthw9v9.wl-randy@psg.com> <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P_VWhJVhih8iP5FVwX1kzR7W4_A>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 22:57:37 -0000

>>>> "Many network security devices block all ICMP messages for perceived
>>>>  security benefits, including the errors that are necessary for the proper
>>>>  operation of PMTUD. This can result in connections that complete the
>>>>  TCP three-way handshake correctly, but then hang when data is transferred.
>>>>  This state is referred to as a black hole connection."
>>>
>>> Yes. What we are asked to do for Internet Standard is show that a protocol
>>> is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
>>> The fact that it also has an important failure mode should certainly be
>>> documented, but I suspect that every Internet Standard has at least
>>> one important failure mode.
>> 
>> the problem is that this particular failure mode is essentially "does
>> not work on the real internet."  perhaps documenting that is useful.
>> but i guess this is ipv6.
> 
> I fully agree that it should be documented, but the details are already
> documented elsewhere. In this document it can be quite short.

i have no problem with terse :)

"Unfortunately, this protocol does not actually work on the real
internet, see \cite{elsewhere}," seems fine to me.

randy


From nobody Wed Feb  8 16:08:32 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F219129646; Wed,  8 Feb 2017 16:08:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gbShXwbGEuG0; Wed,  8 Feb 2017 16:08:19 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 327F812951A; Wed,  8 Feb 2017 16:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486598899; x=1518134899; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=vsOmJqEWO3Dkn6FYyIjWtwAwGu1JQVd5NmFCVSfsNII=; b=OlTz4wmSdYTw2dh6axqLoFi1amhqp47VapRBaCL3Fv9k+MtCbppr+FP6 aUz8sJhNuZK6DnAwZgenUDFdu066R8O80UN6d+/wN3tgmO3qtItmWxnrD R7/U7RGARIDPd0NF8UxSq2AtbHp9XGA2w4QmU8VygaUjqh2u70UmZumGE o=;
X-IronPort-AV: E=Sophos;i="5.35,348,1484035200";  d="scan'208,217";a="356687977"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by wolverine02.qualcomm.com with ESMTP; 08 Feb 2017 16:08:18 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8433"; a="1287154124"
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 08 Feb 2017 16:08:18 -0800
Received: from [10.64.105.176] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Wed, 8 Feb 2017 16:08:17 -0800
From: Pete Resnick <presnick@qti.qualcomm.com>
To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
Subject: Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Date: Wed, 8 Feb 2017 18:08:15 -0600
Message-ID: <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
In-Reply-To: <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com> <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_="
Content-Transfer-Encoding: 8bit
Embedded-HTML: [{"HTML":[990, 8654], "plain":[549, 1805], "uuid":"2C0D4566-962E-40A2-9EFA-EED3C8ED12CE"}]
X-Mailer: MailMate (1.9.6r5344)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01F.na.qualcomm.com (10.85.0.32) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SeNji86aI4g5r2DK7bzvhxgLmag>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 00:08:21 -0000

--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit

If that's what you mean, let me suggest simplifying:

OLD
                                                At least one priority
    level MUST be advertised that, unless overridden by local policy,
    SHALL be at priority level 0.
NEW
                                                At least one priority
    level MUST be advertised. If only one priority level is advertised,
    it MUST be at priority level 0.

Thanks for the extended discussion of this. It all looks fine.

pr

On 8 Feb 2017, at 4:14, Daniele Ceccarelli wrote:

> Hi Pete,
>
> This is an “inheritance” from GMPLS, where supporting a single 
> priority equals not supporting priorities. If you don’t want to 
> support priorities you don’t want your traffic to be 
> preempted…hence priority 0.
>
>
>> Well, it doesn't say that shouldn't be done, but it probably doesn't 
>> need to say anything about local configurations.
> For me it’s ok not to say anything on that.
>
> Thanks
> Daniele
>
> From: Pete Resnick [mailto:presnick@qti.qualcomm.com]
> Sent: martedì 7 febbraio 2017 18:05
> To: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
> Cc: Jari Arkko <jari.arkko@piuha.net>; gen-art@ietf.org; 
> draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org; ccamp@ietf.org; 
> ietf@ietf.org
> Subject: Re: [Gen-art] Review of 
> draft-ietf-ccamp-flexible-grid-ospf-ext-07
>
>
> Hi Daniele,
>
> Thanks for addressing everything. There's only one issue left in 
> section 4.1.1 on Priority, below. I've trimmed out all the rest.
>
> On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:
>
> I get that part ("At least one priority level MUST be advertised"). 
> It's the end I don't understand: "that, unless overridden by local 
> policy, SHALL be at priority level 0." What does that mean?
>
> [DC] It means that if only one priority is supported it has to be 
> priority 0.
>
> So, let me see if I have this right: It's OK to have 01100000 but not 
> 01000000 or 00100000? If so, why is that?
>
> For any particular administrative purpose it could be possible to set 
> it to a different value, but that shouldn’t be done.
>
> Well, it doesn't say that shouldn't be done, but it probably doesn't 
> need to say anything about local configurations.
>
> pr
> --
> Pete Resnick 
> http://www.qualcomm.com/~presnick/<http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478



--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal"><=
p dir=3D"auto">If that's what you mean, let me suggest simplifying:</p>
<p dir=3D"auto">OLD<br>
                                               At least one priority     =
 <br>
   level MUST be advertised that, unless overridden by local policy,     =
 <br>
   SHALL be at priority level 0. <br>
NEW<br>
                                               At least one priority     =
 <br>
   level MUST be advertised. If only one priority level is advertised,<br=
>
   it MUST be at priority level 0.</p>
<p dir=3D"auto">Thanks for the extended discussion of this. It all looks =
fine.</p>
<p dir=3D"auto">pr</p>
<p dir=3D"auto">On 8 Feb 2017, at 4:14, Daniele Ceccarelli wrote:</p>
</div>
<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px"><div id=3D"2C0D4566-962E-40A2-9EFA-EED3C8ED12CE">
<div lang=3D"IT" link=3D"blue" vlink=3D"purple">
<div style=3D"page:WordSection1">
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Hi Pete,</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>This is an =E2=80=9Cinheritance=E2=80=9D from GMPLS=
, where supporting a single priority equals not supporting priorities. If=
 you don=E2=80=99t want to support
 priorities you don=E2=80=99t want your traffic to be preempted=E2=80=A6h=
ence priority 0.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span lang=3D"EN-US" style=3D'font-family:"Ari=
al",sans-serif'>&gt;Well, it doesn't say that shouldn't be done, but it p=
robably doesn't need to say anything about local configurations.</span></=
p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>For me it=E2=80=99s ok not to say anything on that.=
</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Thanks</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>Daniele=C2=A0
</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><span lang=3D=
"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fa=
reast-language:EN-US'>=C2=A0</span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0c=
m 4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0c=
m 0cm 0cm">
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'><b><span lan=
g=3D"EN-US" style=3D'font-size:11.0pt;font-family:"Calibri",sans-serif'>F=
rom:</span></b><span lang=3D"EN-US" style=3D'font-size:11.0pt;font-family=
:"Calibri",sans-serif'> Pete Resnick [mailto:presnick@qti.qualcomm.com]
<br>
<b>Sent:</b> marted=C3=AC 7 febbraio 2017 18:05<br>
<b>To:</b> Daniele Ceccarelli &lt;daniele.ceccarelli@ericsson.com&gt;<br>=

<b>Cc:</b> Jari Arkko &lt;jari.arkko@piuha.net&gt;; gen-art@ietf.org; dra=
ft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org; ccamp@ietf.org; ietf@i=
etf.org<br>
<b>Subject:</b> Re: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-os=
pf-ext-07</span></p>
</div>
</div>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99; margin:0; margin-bottom:0.0001pt'>=C2=A0</p>
<div>
<div>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Hi Daniele,</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Thanks for addressing everything. There's only one issue left in section=
 4.1.1 on Priority, below. I've trimmed out all the rest.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>On 7 Feb 2017, at 3:36, Daniele Ceccarelli wrote:</span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<blockquote style=3D"border:none;border-left:solid #999999 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#999999'>I get that part ("At least one priority level MUST be adve=
rtised"). It's the end I don't understand: "that, unless overridden by lo=
cal policy, SHALL be at priority level 0." What does that mean?</span></p=
>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#777777'>[DC] It means that if only one priority is supported it ha=
s to be priority 0.</span></p>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>So, let me see if I have this right: It's OK to have 01100000 but not 01=
000000 or 00100000? If so, why is that?</span></p>
<blockquote style=3D"border:none;border-left:solid #777777 1.5pt;padding:=
0cm 0cm 0cm 4.0pt;margin-left:0cm;margin-right:0cm;margin-bottom:3.75pt">=

<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif;=
color:#777777'>For any particular administrative purpose it could be poss=
ible to set it to a different value, but that shouldn=E2=80=99t be done.<=
/span></p>
</blockquote>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>Well, it doesn't say that shouldn't be done, but it probably doesn't nee=
d to say anything about local configurations.</span></p>
<p style=3D'font-family:"Times New Roman", serif; font-size:12pt; margin-=
left:0; margin-right:0; mso-margin-bottom-alt:auto; mso-margin-top-alt:au=
to; mso-style-priority:99'><span style=3D'font-family:"Arial",sans-serif'=
>pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D":v=
isited{color:purple; mso-style-priority:99; text-decoration:underline} :l=
ink{color:blue; mso-style-priority:99; text-decoration:underline}"><span =
style=3D"color:#3983C4">http://www.qualcomm.com/~presnick/</span></a><br>=

Qualcomm Technologies, Inc. - +1 (858)651-4478</span></p>
</div>
</div>
</div>
</div>
</div></div></blockquote>
<div style=3D"white-space:normal"><blockquote style=3D"border-left:2px so=
lid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote></div>
</div>
</body>
</html>

--=_MailMate_959A40E8-025C-4E03-8AC0-8F6A0DFA1DCA_=--


From nobody Wed Feb  8 19:52:16 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89C1D1295D9 for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 19:52: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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 XFM9He8tEAyV for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 19:52:12 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BC1E129446 for <ietf@ietf.org>; Wed,  8 Feb 2017 19:52:12 -0800 (PST)
Received: (qmail 94531 invoked from network); 9 Feb 2017 03:52:11 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 9 Feb 2017 03:52:11 -0000
Date: 9 Feb 2017 03:51:49 -0000
Message-ID: <20170209035149.17763.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-Reply-To: <01QANBYPRC140005AQ@mauve.mrochek.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B2bATRvCJ3K5mYm7OYXtDNwbhRI>
Cc: ned+ietf@mauve.mrochek.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 03:52:14 -0000

In article <01QANBYPRC140005AQ@mauve.mrochek.com> you write:
>> That is entirely possible :-).
>> > Except for the small
>> > minority of users who switch MUAs back and forth (see below),
>
>FWIW, this is not a small minority any more. A fair number of people own and
>use multiple mobile devices and access their email from all of them.

I can't emphasize this enough.  Everyone in my family from my 20 year
old daugher to my 95 year old father has both a computer (usually a
laptop) and a phone, and reads and sends mail from both.  I'd say that
multiple devices have become the norm, so if want to use your mail in
a sane way, you need to use IMAP or something else that manages a
server mail store shared by all the clients.

R's,
John


From nobody Wed Feb  8 22:40:44 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D3D1295B2; Wed,  8 Feb 2017 22:40:37 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
Subject: Review of draft-sgtatham-secsh-iutf8-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148662243771.4350.16301638874361801946.idtracker@ietfa.amsl.com>
Date: Wed, 08 Feb 2017 22:40:37 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SrFcYWZlxuK8ItBjN3Tex_Byopg>
Cc: draft-sgtatham-secsh-iutf8.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 06:40:38 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-sgtatham-secsh-iutf8-??
Reviewer: Roni Even
Review Date: 2017-02-08
IETF LC End Date: 2017-02-27
IESG Telechat date: 2017-03-02

Summary: This draft is ready for publication as a standard track RFC.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Wed Feb  8 23:39:51 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 171751298BF for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 23:39:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nW_0yoI8erLV for <ietf@ietfa.amsl.com>; Wed,  8 Feb 2017 23:39:49 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id B9F64129490 for <ietf@ietf.org>; Wed,  8 Feb 2017 23:39:49 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 09 Feb 2017 07:39:49 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 010C4D788D; Wed,  8 Feb 2017 23:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=duTUnbhCzDhaxHQLRMmI5KSYcDQ=; b= O+S5GJmPwIaGm/SvcZZkecA2L6bbfOxOnFD2UE3dyfzKLCrZkGZJhntPmjo+6zOL EfYrilLEfbMT2nT4j6Xg7bDOL3my11Hy6KXis08Oi5WeIdtGimH0JSs7xcr5vL4d kgdWvgSArErmuEWQD6k+DtQqZMuXyqeq7mgxh8HnoeA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=sM8As/5tyGHMDj0U7Zz4NDc rhdxSsyx9bywCU6X0f7dnXikC12TWf2aiSB0ZpS6i/jDJqzblEUC5XdXzC8cIDT/ 7RQmPqeF/a8E5PGVP1reXrjJtalDpSY2wjD1S6cLz+F2090Mk93CsYaOfkNp9MqO SDiFV3NR2kwV4TmA8vGc=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 8075BD788B; Wed,  8 Feb 2017 23:39:48 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id EE13587F5713; Thu,  9 Feb 2017 08:39:46 +0100 (CET)
From: otroan@employees.org
Message-Id: <61ADC897-E971-48B7-BCB3-BD352B644F98@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_DB202697-77D5-48C2-81E2-267A20C0AAA0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Date: Thu, 9 Feb 2017 08:39:46 +0100
In-Reply-To: <m2fujouw83.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com> <m2lgthw9v9.wl-randy@psg.com> <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com> <m2fujouw83.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ytg7QGyGHjpF2KbCkCLsPeChuuM>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 07:39:51 -0000

--Apple-Mail=_DB202697-77D5-48C2-81E2-267A20C0AAA0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>>>>> "Many network security devices block all ICMP messages for =
perceived
>>>>> security benefits, including the errors that are necessary for the =
proper
>>>>> operation of PMTUD. This can result in connections that complete =
the
>>>>> TCP three-way handshake correctly, but then hang when data is =
transferred.
>>>>> This state is referred to as a black hole connection."
>>>>=20
>>>> Yes. What we are asked to do for Internet Standard is show that a =
protocol
>>>> is widely deployed and is interoperable. That's undoubtedly true of =
RFC1981.
>>>> The fact that it also has an important failure mode should =
certainly be
>>>> documented, but I suspect that every Internet Standard has at least
>>>> one important failure mode.
>>>=20
>>> the problem is that this particular failure mode is essentially =
"does
>>> not work on the real internet."  perhaps documenting that is useful.
>>> but i guess this is ipv6.
>>=20
>> I fully agree that it should be documented, but the details are =
already
>> documented elsewhere. In this document it can be quite short.
>=20
> i have no problem with terse :)
>=20
> "Unfortunately, this protocol does not actually work on the real
> internet, see \cite{elsewhere}," seems fine to me.

In the discussion with Joe, we came up with something along the lines =
of:

"Many network security devices block all ICMP messages for perceived
security benefits, including the errors that are necessary for the =
proper
operation of PMTUD. This can result in connections that complete the
TCP three-way handshake correctly, but then hang when data is =
transferred.
This state is referred to as a black hole connection. This is one =
significant
example of how PMTUD is broken on the Internet."

Best regards,
Ole

--Apple-Mail=_DB202697-77D5-48C2-81E2-267A20C0AAA0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYnBzCAAoJEL7aWKiYQt92IzsQALbV3oVAGu0uxWwuxCrLl+eA
teyGZkeR6SCJwCjADzP4YVoRC2U6ZXKuWvHUCtrqRAltSB8vNb4FQRUwEswc6B3E
aBLPKcUnX6uukKCxQc0elUR272ThJSfB1QkLQDW6W3U1ZZTWyirFl+7v5ZSRDCPx
aD7pyvYxdKn+8zAm6MMm212/L3Yzasf9WaT1uUmrY5km4TtFjo+NHNAnOgQWB6ka
+TJbCEui5E+BqynqQ2XvdVQaD6IYM2FO1CVFHO0s6vX0/xa8FmPOt2Vy52bpz3Uf
XMkTy5KLATQfJQv7HUt/DatIdPJzZFgOAUXeysyiux+WqQZ1YgOWZyrHbuf0CH5D
HGX5uM6bDCGwy9rlQpFLO99UoEcltrkGuYE/BNUUdPY6nhHXyV/vYIMZChHRtr1w
WXpkLcvYmrysJtZ042u1zDPPsQyuY7nRkyr4tc3eNKn095mzwCFcZDQVcHjvYu1c
1KUKB6rBXK6vMofrFOywSpf4/nkf5tPqR/O8R5HfWuw1YKIyQOsJBTQvsXx/i/+O
BIZs6ICssJYAc7DzVfb2MUmlsz2e6R5cqAhX1rsrAnGClrMGa8z72pmJENnPM3fT
0Vml5KfQfzczDHpSGZJv1PxuRa5p2yMbSQtD/6jsYf9sZfUUTnAFPIb1Ezi1g86R
Q+302qzlTg3Arr0mVMOv
=UPTH
-----END PGP SIGNATURE-----

--Apple-Mail=_DB202697-77D5-48C2-81E2-267A20C0AAA0--


From nobody Thu Feb  9 00:22:55 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CB21298D5 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 00:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96LWHiSuYZyZ for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 00:22:52 -0800 (PST)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B3F71298D2 for <ietf@ietf.org>; Thu,  9 Feb 2017 00:22:51 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,349,1484035200";  d="asc'?scan'208";a="182303049"
Received: from hioexcmbx03-prd.hq.netapp.com ([10.122.105.36]) by mx141-out.netapp.com with ESMTP; 09 Feb 2017 00:14:56 -0800
Received: from VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) by hioexcmbx03-prd.hq.netapp.com (10.122.105.36) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 9 Feb 2017 00:21:47 -0800
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Thu, 9 Feb 2017 00:21:47 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=KBqDbgXpH/lUddqKwvzDpPZD0oQJZInmeSl8R2DyDgQ=; b=VXSXaUx3cQuiUSkUlC40SXv/ytjkv//12QGLQzE5ul1aSfpU6PEhUrgH4wNKzRZXxN+tZj7uZNCtXC7rNu1LE4ATksp4xXJ6OMmIAyWhXPo2xN3tQ43ghEcpmovZxL0JRVFQ6sVg5PdhHsDexKENSqu9Hzzwxt1irI2cN/lMmUE=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1155.namprd06.prod.outlook.com (10.160.157.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Thu, 9 Feb 2017 08:21:49 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0888.026; Thu, 9 Feb 2017 08:21:49 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
Thread-Index: AQHSfOZWQnyqff8qTkSuzK39n1gXQaFVdhOAgAAEwQCAAPFzgIAAHICAgAIpDQCAAIC4AIAEssqAgAAPVQCAAAYqgIAABs6AgAADMQCAAAP+gIAAWtMAgAA0awCAARlGgIAAElIAgACR6gCAAAu9gA==
Date: Thu, 9 Feb 2017 08:21:48 +0000
Message-ID: <77D69430-6DC3-412C-BDCE-99D94E62CD54@netapp.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com> <m2lgthw9v9.wl-randy@psg.com> <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com> <m2fujouw83.wl-randy@psg.com> <61ADC897-E971-48B7-BCB3-BD352B644F98@employees.org>
In-Reply-To: <61ADC897-E971-48B7-BCB3-BD352B644F98@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: dd54df2a-28f7-4bb0-c323-08d450c4b1a1
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1155; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1155; 7:N9wur3gae33Pyj/j4DGcAGl/N7NQKIYJSJ/z2wUc9ltbG1xzcFdp71ufCdhvO8d+biVbxrI43LGw5yVnLQmr/Ap94PqyN05k+pYK08nR6cy6NgCyA1QHsLQdD7+gcKXHE8tzJX9waIyz7pogJ1RSVmBuOHAXveFatpjpM4iy7CdY8ziunaXRQ2UXjY9yYemjaOtjPueqzOwP+Zk0UVwENpdCsBn5rief6krX9JJEcfOCxVaO5RmiQ74WMthkca3DH1z0CALzg6FaNC2FSwVMDQDqZ26SC91uRl5rQ66imC6ve9DCU1JAQml5wPcRoeSMS+p4IDS8hJzOuK50WIm/GetDGTJ0krq5EAqJeR+dOhALInK1jZDjXu5SA7cp9NzIckOFvR7JLu89KKjPhJWy57ZUvxa0PTWFSlj8qLzn2AulAMZPPQOTaPzTbmfpSBY2w8sN116Dapzb0Pi9909dWgkMqkzAaqe7c0EitT6mMYjMI6L6YdX9GrEeg2t9KJC1fsqkqLoooTZAYBKKG3Ekhg==
x-microsoft-antispam-prvs: <BN3PR0601MB115567A43BEB60DA77B0AA79A7450@BN3PR0601MB1155.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123558025)(20161123564025)(20161123555025)(20161123560025)(20161123562025)(6072148); SRVR:BN3PR0601MB1155; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1155; 
x-forefront-prvs: 02135EB356
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(377424004)(189002)(24454002)(199003)(6506006)(50226002)(2900100001)(6246003)(122556002)(6486002)(93886004)(66066001)(77096006)(86362001)(110136004)(36756003)(33656002)(5640700003)(38730400002)(25786008)(81156014)(6512007)(3846002)(6116002)(102836003)(99286003)(54906002)(4326007)(8676002)(7736002)(189998001)(6436002)(68736007)(305945005)(81166006)(57306001)(1730700003)(5660300001)(3660700001)(2906002)(3280700002)(53546003)(229853002)(92566002)(2950100002)(6916009)(8936002)(53936002)(105586002)(101416001)(97736004)(82746002)(106116001)(76176999)(50986999)(2351001)(106356001)(4001150100001)(230783001)(83716003)(2501003)(99936001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1155; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_03FFAF32-BB84-422B-A461-BAE5B8ED780C"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Feb 2017 08:21:48.7671 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1155
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1c70Bf2D2kaR4V7OU5kOczZ7BSU>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 08:22:53 -0000

--Apple-Mail=_03FFAF32-BB84-422B-A461-BAE5B8ED780C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-9, at 8:39, otroan@employees.org wrote:
>=20
> "Many network security devices block all ICMP messages for perceived
> security benefits, including the errors that are necessary for the =
proper
> operation of PMTUD. This can result in connections that complete the
> TCP three-way handshake correctly, but then hang when data is =
transferred.
> This state is referred to as a black hole connection. This is one =
significant
> example of how PMTUD is broken on the Internet."

Like it.

Might be worthwhile to point at PLPMTUD as something that works, if the =
app/service meets its requirements.

Lars

--Apple-Mail=_03FFAF32-BB84-422B-A461-BAE5B8ED780C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYnCabAAoJEFS1wwm/cMFXitgP/18KDPtgv7qgRxWXoeZFgRHi
A1fsY982bYkjtdZWTE3rpTQZP2kVh3+rNmM44k2+c0K8+tV6P/V5hJHWnR/5uiqz
+y4VkyPyXTyMr7qwv1KVLveU0quFuM4D1/X22Txsjzv9NUbIPWl8ui9W3tpC5MbC
tf/dEjV+rYkBNSiMe8NceHkwVY227R9cdU87p8YqQ1RoUQSuVcSMoePJ6Pka8YUu
S+/DgTNUxt8xcEus9hhpjBUAB29UrtK/0Onid8i+FzlJqo0N8CPjX7RqlAVlDE1u
LXXe+WtU7S9/HqZoYQ1ziCFsKw4pvtZu7aTBAsTZGaJ9EOFqbL1WsHthTX7aQXRy
qupQ6IzQtIWUP+tDMKY/NjSqxZbN3JXKL0S1eyuM5UTL4VgaD6b86mph8t+2ZR21
2KP5kqrh8D4cN9+kgBZTRty6c7Om3zftfj4QAOD6gKI7lldf4QpgL5iNGM4tqvss
xq69ZknfgmkdbspXWOiH7KBHxnrM9KQr0hlDdNmMS3H6CQYbQ9/O5+fAV1KHuf06
buTVOQ71zWdJpY9R0JG/pLsHwALcd9n8tEyp7tXUh+T7gk70IaTvfBH/LAkkgtQB
caZ3C3B0A12nOv4nP7mc2TgKS7haFVtUx3BT6i/E4pcOyD9cDg+gshSXyRhLTkNL
r4HB4caoPz4GgE1c6xW+
=Rkh5
-----END PGP SIGNATURE-----

--Apple-Mail=_03FFAF32-BB84-422B-A461-BAE5B8ED780C--


From nobody Thu Feb  9 00:31:56 2017
Return-Path: <daniele.ceccarelli@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0D2812989D; Thu,  9 Feb 2017 00:31:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H_32o8dPqB_w; Thu,  9 Feb 2017 00:31:44 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 B5BAF1295FE; Thu,  9 Feb 2017 00:31:43 -0800 (PST)
X-AuditID: c1b4fb2d-fb9fc980000059d1-8c-589c28ed39f4
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id D9.3B.22993.DE82C985; Thu,  9 Feb 2017 09:31:42 +0100 (CET)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (153.88.183.145) by oa.msg.ericsson.com (153.88.183.81) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 9 Feb 2017 09:31:23 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.onmicrosoft.com; s=selector1-ericsson-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Opzmum3vrTlDoMwN+f7/18te9S+O6jTfEreJn48V4qI=; b=Lx2iEP7y7jyLy+VS9kLNCJ04NPc12GfBaK3l3lK8TbL/wQOaBXCrFS29IvpThEVH1NYg/PvHdxS0A99DrynzXfxAImWgnPtAQaLaxJxvaR/bGmI76zII54GjhUGIVFT4BcXBwMq6Wu48u8de50JDNAkI1+Hv8yncx1NhBtPDuVU=
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) by AM2PR07MB0994.eurprd07.prod.outlook.com (10.162.37.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Thu, 9 Feb 2017 08:31:20 +0000
Received: from AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) by AM2PR07MB0994.eurprd07.prod.outlook.com ([10.162.37.152]) with mapi id 15.01.0888.025; Thu, 9 Feb 2017 08:31:20 +0000
From: Daniele Ceccarelli <daniele.ceccarelli@ericsson.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: RE: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Topic: [Gen-art] Review of draft-ietf-ccamp-flexible-grid-ospf-ext-07
Thread-Index: AQHSfnRknsTURaNSRU6G5sP6JBParKFb3HyAgAAVk9CAAFB/AIABAp2AgACGiQCAARhlUIAA8DWAgACMNTA=
Date: Thu, 9 Feb 2017 08:31:20 +0000
Message-ID: <AM2PR07MB0994E21E54B10F7AC0416452F0450@AM2PR07MB0994.eurprd07.prod.outlook.com>
References: <148616413998.4157.2652633501511666882.idtracker@ietfa.amsl.com> <2ACBB603-E990-4C86-BE83-4FCC741C254B@piuha.net> <AM2PR07MB0994EB1B4B526A4D7A385E8EF0400@AM2PR07MB0994.eurprd07.prod.outlook.com> <98F6A1A1-2444-4782-99A6-3F5532FE1F63@qti.qualcomm.com> <AM2PR07MB0994A0EE3F25F2BDF4FA20D4F0430@AM2PR07MB0994.eurprd07.prod.outlook.com> <74FF9057-1D46-4213-B4F0-CFEBC2AB0CA8@qti.qualcomm.com> <AM2PR07MB0994B673F4904750FC2746B1F0420@AM2PR07MB0994.eurprd07.prod.outlook.com> <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
In-Reply-To: <6DF6F8D6-53F9-4772-A2CB-A8B750C24EF9@qti.qualcomm.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=daniele.ceccarelli@ericsson.com; 
x-originating-ip: [151.0.200.100]
x-ms-office365-filtering-correlation-id: 64df4e46-ed44-4eb4-2671-08d450c60665
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM2PR07MB0994;
x-microsoft-exchange-diagnostics: 1; AM2PR07MB0994; 7:DNw9T7p5a3la330cgSesROo7dV2OVt4rPKmZGhsFy6LihfU6lv5Nc0cWuTJ7AxOJXRkWQ0WFnV0mNHqUyJHlno6KkLs/zolpxElDQwwhhIvtjDjzO4xfR6cy5wCPySCzw/gkIGnH+W7hf/AEp0yCQuvepCcqrGTJJOa60bVWdvqtBmLYjTtzow0Y4skp4BYm4142u7ZDWuZISsFCjRCom4TxBS2FE/iMzE3jsdAH0IzhLITU8hB/C1lm2YkwFkqPiQhgMkNny0ET2JNPgUKV1anf5oMLDrDf3bJZWkAC4rGgzCL3FMHo9L+Q7daB536laEDGEIZm3iWMrtZHWdN/IS/uL/iN0CNcv+53tyg3kiEIJl1BgAghGfc+NN+LIJIJf+3QzkowXhhZk6A/JkP+xJ/WCOKUhA2PCqIcHrryYU/zN8zusIB+zy+3JFXBXCtDycRGDH+Ym34GE+21e6qsbxMI/CA0yISUO3RGodbufOs3rNAKsiD1g6KxW+sPl/H+SI6hdJSGOa6XeepgSeWdgQ==
x-microsoft-antispam-prvs: <AM2PR07MB09941719747952AE384F01EDF0450@AM2PR07MB0994.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(20161123558025)(6072148); SRVR:AM2PR07MB0994; BCL:0; PCL:0; RULEID:; SRVR:AM2PR07MB0994; 
x-forefront-prvs: 02135EB356
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(51914003)(199003)(189002)(24454002)(101416001)(54356999)(74316002)(7696004)(3660700001)(81166006)(4326007)(7906003)(230783001)(7736002)(66066001)(93886004)(50986999)(105586002)(229853002)(54896002)(106356001)(81156014)(76176999)(55016002)(54906002)(33656002)(99286003)(5660300001)(236005)(8936002)(6306002)(9686003)(25786008)(122556002)(38730400002)(189998001)(102836003)(6436002)(77096006)(68736007)(6916009)(606005)(966004)(106116001)(6506006)(53936002)(8676002)(2950100002)(6116002)(6246003)(86362001)(92566002)(53546003)(97736004)(2900100001)(790700001)(110136004)(3280700002)(2906002)(3846002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM2PR07MB0994; H:AM2PR07MB0994.eurprd07.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Feb 2017 08:31:20.5246 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM2PR07MB0994
X-OriginatorOrg: ericsson.com
X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0hTYRjHec852zlbTl6n5oNG5IjQSO1qM8rM+iCpVPRBi6hmHi95bUdN I2JoghqiqAWbtzJRvG0lajrMUtNIKsW8pWlWw/AWlaUsbznPBL/9n/f/e97n/7y8DCnVC+yZ 8Og4VhmtiJQJxZQ68Nk5lx9OBYF7tYNb5IaCIUpetKQl5P1Tc5R84mkxJe/rv0t6CXxKS42E T8n9CXSWuCg+GsxGhiewSjfPq+KwcW0yFZtdjBILU+sJFfqpQRlIxAA+CA+WiwQZSMxIsRaB oWdKyBevEeQMaAkTReFMEnoWQ3gjj4DFninEFx0Iet910RmIYYT4CBja/EwNNngP5BU2kSaG xF8R1L8y0ibDGvvCy4Famof8wNjUTfI6CGaHGkl+2k5Y1s2t55PgS5DTXWLOV0bB9+fzQtMw ET4F6k8eJgbhrbDQVb2elMR2MGwoJvjdMJQ28/cDtoXJbysCng8CXWqjmXGEnkqNWftDR1q1 cEM3vEinTXMBv6VANzIv4I0ImElpoHl9GvKHxgke0hDwfrDZ3L0NcheqzN3lQiibWVyPIcUs lNekIv4p7GG0Lx1lI2fNpuS8joH2/PZ1LcFW8EZtoDRrS5PYGXR6Nx5xhLx7X2heO0FqQSG9 +fwhoiuRLcdyXFTo/gOurDL8GsfFRLtGs3G1aO1HtdYtujSiqukTbQgzSGYheXI9P1AqUCRw SVFtCBhSZiNxXvtwUkmwIukWq4y5ooyPZLk25MBQMjuJe8XnACkOVcSxESwbyyo3XIIR2avQ ruQP/1qyxI+8LFdqxWrPLIfk82ma6TNjC0Wdv1SRZSEFTIuvuHSssn7wtv/JmrnHAXesnFrU 4xcO/XXTqOz0I8NBxsOaybqU7e6Z3uk7+umPrd6iWSdJZ7WXtV6/tFpRd3mVzS0hEi0Hjwe3 3jhmke1RFP/nd2VMy83e6jlWNSqjuDDFvt2kklP8B5E2LGdNAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/46w4gxUa9QkYopYtneYyHWdVYkk>
Cc: "draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org" <draft-ietf-ccamp-flexible-grid-ospf-ext.all@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "ccamp@ietf.org" <ccamp@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 08:31:46 -0000

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

R29uZSEg4pi6DQoNClRoYW5rcyB0byB5b3UgZm9yIHRoZSBjYXJlZnVsIHJldmlldy4NCg0KQlIN
CkRhbmllbGUNCg0KRnJvbTogUGV0ZSBSZXNuaWNrIFttYWlsdG86cHJlc25pY2tAcXRpLnF1YWxj
b21tLmNvbV0NClNlbnQ6IGdpb3ZlZMOsIDkgZmViYnJhaW8gMjAxNyAwMTowOA0KVG86IERhbmll
bGUgQ2VjY2FyZWxsaSA8ZGFuaWVsZS5jZWNjYXJlbGxpQGVyaWNzc29uLmNvbT4NCkNjOiBkcmFm
dC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQuYWxsQGlldGYub3JnOyBnZW4tYXJ0
QGlldGYub3JnOyBjY2FtcEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtH
ZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0
LTA3DQoNCg0KSWYgdGhhdCdzIHdoYXQgeW91IG1lYW4sIGxldCBtZSBzdWdnZXN0IHNpbXBsaWZ5
aW5nOg0KDQpPTEQNCkF0IGxlYXN0IG9uZSBwcmlvcml0eQ0KbGV2ZWwgTVVTVCBiZSBhZHZlcnRp
c2VkIHRoYXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwNClNIQUxMIGJlIGF0
IHByaW9yaXR5IGxldmVsIDAuDQpORVcNCkF0IGxlYXN0IG9uZSBwcmlvcml0eQ0KbGV2ZWwgTVVT
VCBiZSBhZHZlcnRpc2VkLiBJZiBvbmx5IG9uZSBwcmlvcml0eSBsZXZlbCBpcyBhZHZlcnRpc2Vk
LA0KaXQgTVVTVCBiZSBhdCBwcmlvcml0eSBsZXZlbCAwLg0KDQpUaGFua3MgZm9yIHRoZSBleHRl
bmRlZCBkaXNjdXNzaW9uIG9mIHRoaXMuIEl0IGFsbCBsb29rcyBmaW5lLg0KDQpwcg0KDQpPbiA4
IEZlYiAyMDE3LCBhdCA0OjE0LCBEYW5pZWxlIENlY2NhcmVsbGkgd3JvdGU6DQoNCkhpIFBldGUs
DQoNCg0KDQpUaGlzIGlzIGFuIOKAnGluaGVyaXRhbmNl4oCdIGZyb20gR01QTFMsIHdoZXJlIHN1
cHBvcnRpbmcgYSBzaW5nbGUgcHJpb3JpdHkgZXF1YWxzIG5vdCBzdXBwb3J0aW5nIHByaW9yaXRp
ZXMuIElmIHlvdSBkb27igJl0IHdhbnQgdG8gc3VwcG9ydCBwcmlvcml0aWVzIHlvdSBkb27igJl0
IHdhbnQgeW91ciB0cmFmZmljIHRvIGJlIHByZWVtcHRlZOKApmhlbmNlIHByaW9yaXR5IDAuDQoN
Cg0KDQo+V2VsbCwgaXQgZG9lc24ndCBzYXkgdGhhdCBzaG91bGRuJ3QgYmUgZG9uZSwgYnV0IGl0
IHByb2JhYmx5IGRvZXNuJ3QgbmVlZCB0byBzYXkgYW55dGhpbmcgYWJvdXQgbG9jYWwgY29uZmln
dXJhdGlvbnMuDQoNCkZvciBtZSBpdOKAmXMgb2sgbm90IHRvIHNheSBhbnl0aGluZyBvbiB0aGF0
Lg0KDQoNCg0KVGhhbmtzDQoNCkRhbmllbGUNCg0KDQoNCkZyb206IFBldGUgUmVzbmljayBbbWFp
bHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb21dDQpTZW50OiBtYXJ0ZWTDrCA3IGZlYmJyYWlv
IDIwMTcgMTg6MDUNClRvOiBEYW5pZWxlIENlY2NhcmVsbGkgPGRhbmllbGUuY2VjY2FyZWxsaUBl
cmljc3Nvbi5jb208bWFpbHRvOmRhbmllbGUuY2VjY2FyZWxsaUBlcmljc3Nvbi5jb20+Pg0KQ2M6
IEphcmkgQXJra28gPGphcmkuYXJra29AcGl1aGEubmV0PG1haWx0bzpqYXJpLmFya2tvQHBpdWhh
Lm5ldD4+OyBnZW4tYXJ0QGlldGYub3JnPG1haWx0bzpnZW4tYXJ0QGlldGYub3JnPjsgZHJhZnQt
aWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZzxtYWlsdG86ZHJh
ZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZz47IGNjYW1w
QGlldGYub3JnPG1haWx0bzpjY2FtcEBpZXRmLm9yZz47IGlldGZAaWV0Zi5vcmc8bWFpbHRvOmll
dGZAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogW0dlbi1hcnRdIFJldmlldyBvZiBkcmFmdC1pZXRm
LWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQtMDcNCg0KDQoNCkhpIERhbmllbGUsDQoNClRo
YW5rcyBmb3IgYWRkcmVzc2luZyBldmVyeXRoaW5nLiBUaGVyZSdzIG9ubHkgb25lIGlzc3VlIGxl
ZnQgaW4gc2VjdGlvbiA0LjEuMSBvbiBQcmlvcml0eSwgYmVsb3cuIEkndmUgdHJpbW1lZCBvdXQg
YWxsIHRoZSByZXN0Lg0KDQpPbiA3IEZlYiAyMDE3LCBhdCAzOjM2LCBEYW5pZWxlIENlY2NhcmVs
bGkgd3JvdGU6DQoNCkkgZ2V0IHRoYXQgcGFydCAoIkF0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZl
bCBNVVNUIGJlIGFkdmVydGlzZWQiKS4gSXQncyB0aGUgZW5kIEkgZG9uJ3QgdW5kZXJzdGFuZDog
InRoYXQsIHVubGVzcyBvdmVycmlkZGVuIGJ5IGxvY2FsIHBvbGljeSwgU0hBTEwgYmUgYXQgcHJp
b3JpdHkgbGV2ZWwgMC4iIFdoYXQgZG9lcyB0aGF0IG1lYW4/DQoNCltEQ10gSXQgbWVhbnMgdGhh
dCBpZiBvbmx5IG9uZSBwcmlvcml0eSBpcyBzdXBwb3J0ZWQgaXQgaGFzIHRvIGJlIHByaW9yaXR5
IDAuDQoNClNvLCBsZXQgbWUgc2VlIGlmIEkgaGF2ZSB0aGlzIHJpZ2h0OiBJdCdzIE9LIHRvIGhh
dmUgMDExMDAwMDAgYnV0IG5vdCAwMTAwMDAwMCBvciAwMDEwMDAwMD8gSWYgc28sIHdoeSBpcyB0
aGF0Pw0KDQpGb3IgYW55IHBhcnRpY3VsYXIgYWRtaW5pc3RyYXRpdmUgcHVycG9zZSBpdCBjb3Vs
ZCBiZSBwb3NzaWJsZSB0byBzZXQgaXQgdG8gYSBkaWZmZXJlbnQgdmFsdWUsIGJ1dCB0aGF0IHNo
b3VsZG7igJl0IGJlIGRvbmUuDQoNCldlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0
IGJlIGRvbmUsIGJ1dCBpdCBwcm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFi
b3V0IGxvY2FsIGNvbmZpZ3VyYXRpb25zLg0KDQpwcg0KLS0NClBldGUgUmVzbmljayBodHRwOi8v
d3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPGh0dHA6Ly93d3cucXVhbGNvbW0uY29tLyU3RXBy
ZXNuaWNrLz4NClF1YWxjb21tIFRlY2hub2xvZ2llcywgSW5jLiAtICsxICg4NTgpNjUxLTQ0NzgN
Cg==

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdp
bi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6
MGNtOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
c2VyaWY7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXtt
c28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFy
Z2luLXJpZ2h0OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVm
dDowY207DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFu
IixzZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1y
ZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0
ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZv
bnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIu
MHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
SVQiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24x
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7bXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkdvbmUhDQo8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OldpbmdkaW5nczttc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+Sjwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj5UaGFua3MgdG8geW91IGZvciB0aGUgY2FyZWZ1bCByZXZpZXcuPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj5CUjxicj4NCkRhbmllbGUmbmJzcDsgJm5ic3A7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO21zby1mYXJlYXN0
LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6
c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fu
cy1zZXJpZiI+IFBldGUgUmVzbmljayBbbWFpbHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb21d
DQo8YnI+DQo8Yj5TZW50OjwvYj4gZ2lvdmVkw6wgOSBmZWJicmFpbyAyMDE3IDAxOjA4PGJyPg0K
PGI+VG86PC9iPiBEYW5pZWxlIENlY2NhcmVsbGkgJmx0O2RhbmllbGUuY2U8L3NwYW4+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Y2NhcmVsbGlAZXJpY3Nzb24uY29tJmd0Ozxicj4NCjxi
PkNjOjwvYj4gZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRm
Lm9yZzsgZ2VuLWFydEBpZXRmLm9yZzsgY2NhbXBAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc8YnI+
DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtHZW4tYXJ0XSBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1jY2Ft
cC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LTA3PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxkaXY+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDss
c2Fucy1zZXJpZiI+SWYgdGhhdCdzIHdoYXQgeW91IG1lYW4sIGxldCBtZSBzdWdnZXN0IHNpbXBs
aWZ5aW5nOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIHN0eWxlPSJmb250LWZhbWls
eTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmIj5PTEQ8YnI+DQpBdCBsZWFzdCBvbmUgcHJp
b3JpdHkgPGJyPg0KbGV2ZWwgTVVTVCBiZSBhZHZlcnRpc2VkIHRoYXQsIHVubGVzcyBvdmVycmlk
ZGVuIGJ5IGxvY2FsIHBvbGljeSwgPGJyPg0KU0hBTEwgYmUgYXQgcHJpb3JpdHkgbGV2ZWwgMC4g
PGJyPg0KTkVXPGJyPg0KQXQgbGVhc3Qgb25lIHByaW9yaXR5IDxicj4NCmxldmVsIE1VU1QgYmUg
YWR2ZXJ0aXNlZC4gSWYgb25seSBvbmUgcHJpb3JpdHkgbGV2ZWwgaXMgYWR2ZXJ0aXNlZCw8YnI+
DQppdCBNVVNUIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
PlRoYW5rcyBmb3IgdGhlIGV4dGVuZGVkIGRpc2N1c3Npb24gb2YgdGhpcy4gSXQgYWxsIGxvb2tz
IGZpbmUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5
OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYiPnByPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWYi
Pk9uIDggRmViIDIwMTcsIGF0IDQ6MTQsIERhbmllbGUgQ2VjY2FyZWxsaSB3cm90ZTo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjNzc3Nzc3IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQ7
bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0K
PGRpdiBpZD0iMkMwRDQ1NjYtOTYyRS00MEEyLTlFRkEtRUVEM0M4RUQxMkNFIj4NCjxkaXY+DQo8
cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPkhpIFBldGUsPC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3
Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiZuYnNwOzwvc3Bhbj48
c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5UaGlzIGlzIGFuIOKAnGluaGVyaXRhbmNl4oCdIGZyb20gR01QTFMsIHdoZXJl
IHN1cHBvcnRpbmcgYSBzaW5nbGUgcHJpb3JpdHkgZXF1YWxzIG5vdCBzdXBwb3J0aW5nIHByaW9y
aXRpZXMuIElmIHlvdSBkb27igJl0IHdhbnQgdG8gc3VwcG9ydCBwcmlvcml0aWVzDQogeW91IGRv
buKAmXQgd2FudCB5b3VyIHRyYWZmaWMgdG8gYmUgcHJlZW1wdGVk4oCmaGVuY2UgcHJpb3JpdHkg
MC48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3Nzttc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3
Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+
Jmd0O1dlbGwsIGl0IGRvZXNuJ3Qgc2F5IHRoYXQgc2hvdWxkbid0IGJlIGRvbmUsIGJ1dCBpdCBw
cm9iYWJseSBkb2Vzbid0IG5lZWQgdG8gc2F5IGFueXRoaW5nIGFib3V0IGxvY2FsIGNvbmZpZ3Vy
YXRpb25zLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5Gb3IgbWUgaXTigJlzIG9rIG5vdCB0byBzYXkgYW55
dGhpbmcgb24gdGhhdC48L3NwYW4+PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3Nzttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxl
PSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiM3Nzc3Nzc7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PlRoYW5rczwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHA+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3O21z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5EYW5pZWxlJm5ic3A7DQo8L3NwYW4+PHNwYW4gc3R5
bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3Nzttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+Jm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVl
IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBj
bSAwY20gMGNtIj4NCjxwPjxiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3
Nzc3NyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6
Izc3Nzc3NyI+IFBldGUgUmVzbmljayBbPGEgaHJlZj0ibWFpbHRvOnByZXNuaWNrQHF0aS5xdWFs
Y29tbS5jb20iPm1haWx0bzpwcmVzbmlja0BxdGkucXVhbGNvbW0uY29tPC9hPl0NCjxicj4NCjxi
PlNlbnQ6PC9iPiBtYXJ0ZWTDrCA3IGZlYmJyYWlvIDIwMTcgMTg6MDU8YnI+DQo8Yj5Ubzo8L2I+
IERhbmllbGUgQ2VjY2FyZWxsaSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRhbmllbGUuY2VjY2FyZWxs
aUBlcmljc3Nvbi5jb20iPmRhbmllbGUuY2VjY2FyZWxsaUBlcmljc3Nvbi5jb208L2E+Jmd0Ozxi
cj4NCjxiPkNjOjwvYj4gSmFyaSBBcmtrbyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmphcmkuYXJra29A
cGl1aGEubmV0Ij5qYXJpLmFya2tvQHBpdWhhLm5ldDwvYT4mZ3Q7Ow0KPGEgaHJlZj0ibWFpbHRv
Omdlbi1hcnRAaWV0Zi5vcmciPmdlbi1hcnRAaWV0Zi5vcmc8L2E+OyA8YSBocmVmPSJtYWlsdG86
ZHJhZnQtaWV0Zi1jY2FtcC1mbGV4aWJsZS1ncmlkLW9zcGYtZXh0LmFsbEBpZXRmLm9yZyI+DQpk
cmFmdC1pZXRmLWNjYW1wLWZsZXhpYmxlLWdyaWQtb3NwZi1leHQuYWxsQGlldGYub3JnPC9hPjsg
PGEgaHJlZj0ibWFpbHRvOmNjYW1wQGlldGYub3JnIj4NCmNjYW1wQGlldGYub3JnPC9hPjsgPGEg
aHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+PGJyPg0KPGI+U3Vi
amVjdDo8L2I+IFJlOiBbR2VuLWFydF0gUmV2aWV3IG9mIGRyYWZ0LWlldGYtY2NhbXAtZmxleGli
bGUtZ3JpZC1vc3BmLWV4dC0wNzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cD48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOiM3Nzc3NzciPiZuYnNwOzxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+SGkgRGFuaWVsZSw8L3NwYW4+
PHNwYW4gc3R5bGU9ImNvbG9yOiM3Nzc3NzciPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OiM3Nzc3NzciPlRoYW5rcyBmb3IgYWRkcmVzc2luZyBldmVyeXRoaW5nLiBUaGVyZSdzIG9ubHkg
b25lIGlzc3VlIGxlZnQgaW4gc2VjdGlvbiA0LjEuMSBvbiBQcmlvcml0eSwgYmVsb3cuIEkndmUg
dHJpbW1lZCBvdXQgYWxsIHRoZSByZXN0Ljwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3
NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZx
dW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+T24gNyBGZWIgMjAxNywg
YXQgMzozNiwgRGFuaWVsZSBDZWNjYXJlbGxpIHdyb3RlOjwvc3Bhbj48c3BhbiBzdHlsZT0iY29s
b3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJv
cmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICM3Nzc3NzcgMS41cHQ7cGFkZGluZzowY20gMGNt
IDBjbSA0LjBwdDttYXJnaW4tbGVmdDowY207bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6
MGNtO21hcmdpbi1ib3R0b206My43NXB0Ij4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjOTk5OTk5IDEuNXB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNC4w
cHQ7bWFyZ2luLWxlZnQ6MGNtO21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJn
aW4tYm90dG9tOjMuNzVwdCI+DQo8cD48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJp
YWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojOTk5OTk5Ij5JIGdldCB0aGF0IHBhcnQgKCZxdW90
O0F0IGxlYXN0IG9uZSBwcmlvcml0eSBsZXZlbCBNVVNUIGJlIGFkdmVydGlzZWQmcXVvdDspLiBJ
dCdzIHRoZSBlbmQgSSBkb24ndCB1bmRlcnN0YW5kOiAmcXVvdDt0aGF0LCB1bmxlc3Mgb3ZlcnJp
ZGRlbiBieSBsb2NhbCBwb2xpY3ksIFNIQUxMIGJlIGF0IHByaW9yaXR5IGxldmVsIDAuJnF1b3Q7
IFdoYXQgZG9lcyB0aGF0IG1lYW4/PC9zcGFuPjxzcGFuIHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD48c3BhbiBzdHlsZT0iZm9u
dC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3Ij5bRENd
IEl0IG1lYW5zIHRoYXQgaWYgb25seSBvbmUgcHJpb3JpdHkgaXMgc3VwcG9ydGVkIGl0IGhhcyB0
byBiZSBwcmlvcml0eSAwLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+U28sIGxldCBt
ZSBzZWUgaWYgSSBoYXZlIHRoaXMgcmlnaHQ6IEl0J3MgT0sgdG8gaGF2ZSAwMTEwMDAwMCBidXQg
bm90IDAxMDAwMDAwIG9yIDAwMTAwMDAwPyBJZiBzbywgd2h5IGlzIHRoYXQ/PC9zcGFuPjxzcGFu
IHN0eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90
ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgIzc3Nzc3NyAxLjVwdDtwYWRk
aW5nOjBjbSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjBjbTttYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTozLjc1cHQiPg0KPHA+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+Rm9y
IGFueSBwYXJ0aWN1bGFyIGFkbWluaXN0cmF0aXZlIHB1cnBvc2UgaXQgY291bGQgYmUgcG9zc2li
bGUgdG8gc2V0IGl0IHRvIGEgZGlmZmVyZW50IHZhbHVlLCBidXQgdGhhdCBzaG91bGRu4oCZdCBi
ZSBkb25lLjwvc3Bhbj48c3BhbiBzdHlsZT0iY29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHA+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90
O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6Izc3Nzc3NyI+V2VsbCwgaXQgZG9lc24ndCBz
YXkgdGhhdCBzaG91bGRuJ3QgYmUgZG9uZSwgYnV0IGl0IHByb2JhYmx5IGRvZXNuJ3QgbmVlZCB0
byBzYXkgYW55dGhpbmcgYWJvdXQgbG9jYWwgY29uZmlndXJhdGlvbnMuPC9zcGFuPjxzcGFuIHN0
eWxlPSJjb2xvcjojNzc3Nzc3Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBzdHls
ZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojNzc3Nzc3
Ij5wcjxicj4NCi0tIDxicj4NClBldGUgUmVzbmljayA8YSBocmVmPSJodHRwOi8vd3d3LnF1YWxj
b21tLmNvbS8lN0VwcmVzbmljay8iPjxzcGFuIHN0eWxlPSJjb2xvcjojMzk4M0M0Ij5odHRwOi8v
d3d3LnF1YWxjb21tLmNvbS9+cHJlc25pY2svPC9zcGFuPjwvYT48YnI+DQpRdWFsY29tbSBUZWNo
bm9sb2dpZXMsIEluYy4gLSAmIzQzOzEgKDg1OCk2NTEtNDQ3ODwvc3Bhbj48c3BhbiBzdHlsZT0i
Y29sb3I6Izc3Nzc3NyI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rp
dj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM2PR07MB0994E21E54B10F7AC0416452F0450AM2PR07MB0994eurp_--


From nobody Thu Feb  9 02:26:12 2017
Return-Path: <roland.bless@kit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57F0B129965 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 02:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 mUAuKVih1APj for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 02:26:09 -0800 (PST)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5B6B5129963 for <ietf@ietf.org>; Thu,  9 Feb 2017 02:26:09 -0800 (PST)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=i72vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25  iface 141.3.10.81 id 1cblvS-0006NT-Mt; Thu, 09 Feb 2017 11:26:06 +0100
Received: from [IPv6:::1] (ip6-localhost [IPv6:::1]) by i72vorta.tm.kit.edu (Postfix) with ESMTPS id 81350B0021B; Thu,  9 Feb 2017 11:26:06 +0100 (CET)
Subject: Re: If Muslims are blocked by the U.S., should the IETF respond?
To: Jari Arkko <jari.arkko@piuha.net>, IETF <ietf@ietf.org>
References: <CAAUuzMQwk5v+3HA+KFrsCZfbNSXFpgBE0XdKfJWHgDss9-VkTw@mail.gmail.com> <20170130183846.21994.qmail@server322.com> <AB7E9EDD-C313-4821-8BEC-D0AF57D80DA2@nohats.ca> <2D08A4C9-969C-4EFD-8782-84728C458EA3@piuha.net>
From: "Bless, Roland (TM)" <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology
Message-ID: <ba335767-49b5-3cb3-d459-5fd67a5144dc@kit.edu>
Date: Thu, 9 Feb 2017 11:26:06 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <2D08A4C9-969C-4EFD-8782-84728C458EA3@piuha.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1486635966.
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1zWrWkQ5iCJJVo0ZXd-LjNw8qH0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 10:26:11 -0000

Hi Jari,

see comments below...

Am 30.01.2017 um 20:39 schrieb Jari Arkko:
> I wanted to update people a bit on effects and numbers.
> 
> Adam had given earlier in this thread a list of affected
> people from past meetings. I run my own script on the
> attendee data though, and (I think) took into account
> who was actually on site. Out of the seven countries
> on the list, we’ve not had a single attendee on site from
> the beginning of the full records at IETF #80.
> 
> Obviously, that doesn’t make it right. Also,
> the registration data is still based on the country or
> region that people given when they register. And
> you can only enter one value.
> 
> I’m aware of at least two people (Kaveh and Naeem)
> who have dual citizenships for instance, and they are
> sadly affected. There’s likely some more. If you are
> affected and planning to attend future IETF meetings,
> drop me an e-mail.

The collateral damage and impact of current US policy on
immigration is probably broader than just counting the people
who are obviously affected by any ban.
I originally planned to attend the meeting in Chicago
and normally I'm always looking forward to visit the US.
Though I'm not affected by my citizenship (yet), I'm
refraining from attending this time. Why?
I'm deeply concerned about the current practices during
immigration:
http://www.cnbc.com/2017/02/08/us-visitors-may-have-to-hand-over-social-media-passwords-dhs.html

"We want to get on their social media, with passwords: What do you do,
what do you say?" he [John Kelly] told the House Homeland Security
Committee. "If they don't want to cooperate then you don't come in."

So just flying several hours across the ocean and then get denied on
entry, because one of your friends probably posted some US politics
criticism that the immigration officer didn't like is a risk that I
don't need this time.
Moreover, if someone gets full control over a social media account
he/she can also *write* - this is ridiculous. [*]
I refuse this highly privacy invading practice.

More stuff like this:
http://www.cbc.ca/news/canada/montreal/canadian-woman-turned-away-from-u-s-border-after-questions-about-religion-trump-1.3972019

https://www.aclu.org/blog/speak-freely/flying-home-abroad-border-agent-stopped-and-questioned-me-about-my-work-aclu

I really like to support the IETF by also physically attending the
meetings if possible, but under these circumstances I refrain from
doing so.

Regards,
 Roland

[*] it's clear that some "agencies" already have that access,
but this is even another dimension now...


From nobody Thu Feb  9 02:36:56 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB9812996F; Thu,  9 Feb 2017 02:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nceBm3P88maP; Thu,  9 Feb 2017 02:36:53 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 587BC129967; Thu,  9 Feb 2017 02:36:53 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 09 Feb 2017 10:36:51 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 08D90D788B; Thu,  9 Feb 2017 02:36:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=IS07E1Yut2AHUKB9g53++fkVFnA=; b= cTHzCpUvpUx78eJZICsgISlnD9sf2leYcwI1Eqgjxxni8g34D7e5924GER+1nfjG 0XDN3NjiBWqwrQObC/srVeUbbU3YhdovGZUzF7TQ9RJJp+8X2TqI7xfcMKttdk+T 7zH3Kt2oLtMS9e7VjTa83uGFDRa/5McY2ZVQu+hgFXY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=NkucE+KZ0xHHYibHFotg/O+ bC5iIlWuGG4VT6511iHvaJh+EUcYhqXYZ0eZO1jFz6JDj8dmgqe5Wx8ByFqk3jky OENarVZv/iB8qprLHxDjM27Z1Oh+MSOFqjIvphcZhuWgDY9At5jOR4p10bdHaC2m VWuLM/rT7VvvSIaK90og=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id A60B1D7890; Thu,  9 Feb 2017 02:36:50 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 41D1B88226BF; Thu,  9 Feb 2017 11:36:51 +0100 (CET)
From: otroan@employees.org
Message-Id: <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_460BAB5C-377D-4C7B-8984-D1E11437AE6E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Thu, 9 Feb 2017 11:36:50 +0100
In-Reply-To: <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WPDUhRAKc4SxrPuoVZ78ss8e0aQ>
Cc: 6man@ietf.org, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Stefano Previdi <sprevidi@cisco.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 10:36:55 -0000

--Apple-Mail=_460BAB5C-377D-4C7B-8984-D1E11437AE6E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

Pete asked me to summarize the objections to option 1 - banning header =
insertion explicitly.
I responded with the set of objections I've heard for all options, as I =
couldn't see a straightforward way of only summarising for option 1.

I don't understand your message.
Do you disagree with the summary itself? Are there arguments missing?
Or is your grief that the I have distilled the arguments wrongly or put =
them in a bad light?

Or are you just rehashing your position on the issue?

cheers,
Ole


> On 8 Feb 2017, at 15:25, Fernando Gont <fgont@si6networks.com> wrote:
>=20
> On 02/08/2017 10:51 AM, otroan@employees.org wrote:
>>>=20
>>> There were three main positions argued in the working group.
>>>=20
>>> 1) Ban header insertion outright. 2) Describe the problems with
>>> header insertion. 3) No changes to RFC2460 text.
>>>=20
>>> What did you see as the objections to going with (1) (which I
>>> presume to be the equivalent of Brian's proposed text)? Why was it
>>> that people thought the protocol could not be clarified to say
>>> that? And was your assessment that those arguments were correct, or
>>> that they simply were not addressed by the WG? I've seen several
>>> people argue on this list that (1) was always the intent of the
>>> protocol, and that damage occurs if you don't follow that
>>> directive. I haven't seen anyone here argue otherwise. Could you
>>> summarize?
>>=20
>> I can try. It has been difficult to distill the essence out of all
>> the mailing list discussions. This is _my_ take of the discussion and
>> arguments as I understood them. Please chime in with corrections.
>>=20
>> The arguments of what would break are correct. The counter-arguments
>> given would be that this is done within a controlled domain and the
>> potential for damage could be controlled.
>=20
> There need not be "counter arguments". It was clear to everyone that
> IPv6 never allowed EH insertion. If you want to change that, you have =
to
> update RFC2460 (and if you do it before rfc2460bis is published, good
> luck with moving it to Standard).
>=20
> OTOH, if the argument is that you want to break a protocol in your own
> environment, in which you can "control the damage"... why do you need =
an
> RFC for that? why should we rubberstamp it?
>=20
>=20
>=20
>> The discussion went something like (paraphrasing):
>>=20
>> - Inserting headers will break Path MTU discovery, AH and may result
>=20
> You miss the most important point: EH insertion was never allowed in
> IPv6.  Quite a lot of us find the argument that "we're doing EH
> insertion because RFC2460 doesn't explicitly prohibit *insertion*" =
quite
> funny.
>=20
> I'm not against EH-insertion per se. I'm against what looks like a
> procedural hack.
>=20
> If people want EH insertion, fine: write a proposal that updates
> RFC2460, and let's have the discussion. But please do not pretend that
> RFC2460 allows EH insertion.
>=20
>=20
>=20
>> in unsuspecting hosts receiving ICMP error messages. - We will do
>> this in a controlled domain only. - Even if you can guarantee it will
>> not leak, it is not appropriate to specify that in the core IPv6
>> specification - We don't need that, we just need 2460 not to ban it.
>> IPv6 is used in many networks not only the capital I Internet.
>>=20
>> There was also quite a bit of discussion on the intent of the
>> original authors. I don't know how much value it is correct to give
>> that argument. "This is what I intended, but not what I wrote...".
>> Given that this is in any case the output of the IETF and not two
>> individual authors.
>>=20
>> 1) Ban header insertion outright.
>>=20
> [...]
>>=20
>> b) RFC2460 is already clear and no clarification is needed. No
>> interoperability issue has been shown caused by this perceived
>> ambiguity.
>=20
> RFC2460 already bans EH insertion. Only when SR wa published people
> started to argue otherwise.
>=20
> Given that for some guys there was room for EH insertion, we clearly
> need to make the point clear.
>=20
>=20
>> There was hard to find consensus on either of the alternatives. As
>> the poll shows there was a clear preference (if people couldn't get
>> their first choice) to describe the problem, over banning it, or over
>> saying nothing.
>=20
> Based on the mailing-list discussion, it was quite clear that most of
> the folks arguing in favor of "ambiguity" were from the same company
> pushing a proposal with EH insertion. That's not a minor datapoint.
>=20
> Besides, moving a document to Standard with "ambiguity" on an item =
that
> led to 600+ messages discussion at the same group that specifies the
> protocol would be really bad.
>=20
> We're moving RFC2460 to standard. I think it should be able to answer
> the very basic question "Is it possible to insert EHs in the middle of
> the network?"  -- or, framed in a different way: "is IPv6 and =
end-to-end
> protocol?"
>=20
> 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


--Apple-Mail=_460BAB5C-377D-4C7B-8984-D1E11437AE6E
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYnEZCAAoJEL7aWKiYQt92ArIP/imn+Id5tzDd4KDzuUwuXcC/
cBZpeF37EK3OrmYFrF0iAvXDddcPpX52zWZ+wX2ykxp+kLWZylvP88eeVw3iO905
b//cbvt9WSLI10rKRQBcjODrYu5mEoi/hY1UUQrzwN5/JKRRKqQ6j+UtIHyur+Bd
UjcMXBtVEVDScCEF4t+7NVN4LNuM3h2rdJgJ77igMrsBlam07yfL0DlCttpf5d3T
kB1fQnGpuLis35CrWJ4h5D1yVMpQMmdCj5bnlS3MjAvdmFLHb1ZIyCsiMFEUahge
CwPB0FIP+uhTqbAgqhRHf73u85oMEsSLDZkXPLYBerIGiegCXfOtZjpLEuiUFyvv
bhMMpn1BAWZ7GjWUvMe3X0n89LNvnMZNN1urhFJKAJxPS/IhPB0ns2GKSKFxUDKY
LhScPpAfW7syiSXHYVX5K+Cti1r6xUeLbCgH6HN7ScVncqa5UGDnCCkQF1ggRggu
jgahqLYIz8CEunfJHNg8yrlU6Erp+1nmemXm767Nu40dtwsLV3RqE+Tuxu3lRJMC
WmR3sUNqJ0I41QH8/2eDyFgBZjTsHW8IjTriMmzZK7AtcYQYSrd3cYIYZpbct4U6
iv/w0DCxcGS2LrBnYf3uEY2C4gvuXaRmbeRp+8KsRt6htuLIx24VJ4Hq4Q19n8In
vVo6WymLk3THQHf+inuI
=S3PT
-----END PGP SIGNATURE-----

--Apple-Mail=_460BAB5C-377D-4C7B-8984-D1E11437AE6E--


From nobody Thu Feb  9 07:19:59 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED4D6129AB7; Thu,  9 Feb 2017 07:19:53 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-6man-rfc1981bis-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
Date: Thu, 09 Feb 2017 07:19:53 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xwe7uSNj_1SsA8Um8nRyK15Qfic>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 15:19:54 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc1981bis-04
Reviewer: Stewart Bryant
Review Date: 9/Feb/2017
IETF LC End Date: 1/Mar/2017
IESG Telechat date: unknown

Summary: This draft is on the right track but has open issues,
described in the review.

This review together with the lengthy discussion on the IETF list
suggest that this draft has a number of issues that need to be
addressed  before publication.

I wonder if we would best serve both our future and our heritage
if we declared RFC1981 as historic, and either left the idea there,
or declared it as historic and wrote a new text from a clean start?
 

Major issues:

Nits points out a number of faults with the document, but the only
one of substance is:

The text has a lot of RFC2119 language, but no RFC2119 declaration.

The document could use a thorough RFC2119 scrub

The document lists the three original authors one with an affiliation

change, but no email addresses. Has this been agreed with the
original
authors, and have arrangements been put in place for the RFC editor 
to process auth48?

It is concerning that the draft does not talk in any detail about
how modern ECMP works, i.e. using the five tuple, and noting that
the PMTU may be different depending on the transport layer port
numbers.

Given that a very large fraction of packets will traverse an MPLS
network at some point, I am surprised that there is no text talking
about the importance of providing support for this feature in the 
MPLS domain. RFC3988 talks to this point, but is only experimental.

======

   If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
   could use the flow id as the local representation of a path. 
Packets
   sent to a particular destination but belonging to different flows
may
   use different paths, with the choice of path depending on the flow
   id.  This approach will result in the use of optimally sized
packets
   on a per-flow basis, providing finer granularity than PMTU values
   maintained on a per-destination basis.

SB> How widely is flow-id supported in networks? I thought that the 
SB> current position was that it was unreliable as an ECMP indicator
SB> and thus routers tended to glean information from the packet
themselves.

======

      Note: if the original packet contained a Routing header, the
      Routing header should be used to determine the location of the
      destination address within the original packet.  If Segments
Left
      is equal to zero, the destination address is in the Destination
      Address field in the IPv6 header.  If Segments Left is greater
      than zero, the destination address is the last address
      (Address[n]) in the Routing header.

SB> So this has the effect that a traffic engineered packet and
SB> a non-traffic engineered packet will have the lower of the 
SB> two PMTUs. This was all harmless when source routing was a
curiosity
SB> as far as mainstream networking was concerned, but may be
SB> more of a problem as a result of the SPRING work.

=======


5.3.  Purging stale PMTU information

   Internetwork topology is dynamic; routes change over time.  While
the
   local representation of a path may remain constant, the actual
   path(s) in use may change.  Thus, PMTU information cached by a
node
   can become stale.

   If the stale PMTU value is too large, this will be discovered
almost
   immediately once a large enough packet is sent on the path.  No
such
   mechanism exists for realizing that a stale PMTU value is too
small,
   so an implementation should "age" cached values.  When a PMTU
value
   has not been decreased for a while (on the order of 10 minutes),
the
   PMTU estimate should be set to the MTU of the first-hop link, and
the
   packetization layers should be notified of the change.  This will
   cause the complete Path MTU Discovery process to take place again.

SB> Should that be an RFC2119 SHOULD?
SB> The impact of this advice is going to be a disruption to what
might
SB> be a critical service every 10 mins.
SB> Should there be some advice along the lines of noting the 
SB> importance of service delivery as part of deciding whether to
SB> test for bigger PMTU vs improving efficiency?

=======


Minor issues:

   IPv6 defines a standard mechanism for a node to discover the
   PMTU of an arbitrary path.

SB> Do you mean "This document defines ....."? Otherwise this needs
SB> a reference.

=======

   An extension to Path MTU Discovery defined in this document can be
   found in [RFC4821].  It defines a method for Packetization Layer
Path
SB> Rather than have the reader figure out what "It" is, perhaps
SB> s/It/RFC4821/
=======


   Upon receipt of such a
   message, the source node reduces its assumed PMTU for the path
based
   on the MTU of the constricting hop as reported in the Packet Too
Big
   message.

SB> We should perhaps state up front that this procedure
SB> hunts for the worst case of the ECMP set associated with the 
SB> ingress nodes PMTU classifier.
=======

   If a node receives a Packet Too Big message reporting a next-hop
MTU
   that is less than the IPv6 minimum link MTU, it should discard it.

SB> Should that be an RFC2119 SHOULD?
=======

5.2.  Storing PMTU information

   Ideally, a PMTU value should be associated with a specific path
   traversed by packets exchanged between the source and destination
   nodes.  However, in most cases a node will not have enough
   information to completely and accurately identify such a path.
   Rather, a node must associate a PMTU value with some local
   representation of a path.  It is left to the implementation to
select
   the local representation of a path.

SB> Is it worth noting the five tuple since that is how a lot of
SB> load balancers work?
=======

   The set of paths in use to a
   particular destination is expected to be small, in many cases
   consisting of a single path.  

SB> I am not sure that remains true in modern networks.
=======

   One approach to implementing PMTU aging is to associate a
timestamp
   field with a PMTU value.  This field is initialized to a
"reserved"
   value, indicating that the PMTU is equal to the MTU of the first
hop
   link.  Whenever the PMTU is decreased in response to a Packet Too
Big
   message, the timestamp is set to the current time.

   Once a minute, a timer-driven procedure runs through all cached
PMTU
   values, and for each PMTU whose timestamp is not "reserved" and is
   older than the timeout interval:

   -  The PMTU estimate is set to the MTU of the first hop link.

   -  The timestamp is set to the "reserved" value.

   -  Packetization layers using this path are notified of the
increase.


SB> Such detailed implementation advice is uncommon in modern RFCs. It
has
SB> the disadvantage of de-facto standardizing something that should
be left to
SB> the innovation of the implementer.

=======

5.4.  TCP layer actions

SB> TCP implementations have moved on a lot since this section was
SB> written. Is this still current best practise?

=======

5.5.  Issues for other transport protocols

   Some transport protocols (such as ISO TP4 [ISOTP]) are not allowed
to
   repacketize when doing a retransmission.  

SB> How much TP4 is there going over IPv6? Doesn't this example 
SB> show the IETF as not being in the modern age?

=======

Nits/editorial comments: 

   upper layer         a protocol layer immediately above IPv6.
                       Examples are transport protocols such as TCP
and
                       UDP, control protocols such as ICMP, routing
                       protocols such as OSPF, and internet or lower-
                       layer protocols being "tunneled" over (i.e.,
                       encapsulated in) IPv6 such as IPX, AppleTalk,
or
                       IPv6 itself.

SB> Everything in the list above is in the well known list, except
SB> IPX, so technically it needs expansion. However it might be nice
SB> to use some modern example in common use.
=======

   link                a communication facility or medium over which
                       nodes can communicate at the link layer, i.e.,
                       the layer immediately below IPv6.  Examples
are
                       Ethernets (simple or bridged); PPP links;
X.25,
                       Frame Relay, or ATM networks; and internet (or
                       higher) layer "tunnels", such as tunnels over
                       IPv4 or IPv6 itself.

SB> Technically X.25 needs a reference, since it is not "well known"
=======

   path                the set of links traversed by a packet between
a
                       source node and a destination node.

SB> Is it a set of links, or a set of links and nodes?

========
 
    the value of MMS_S, the "maximum send transport-message size". 
SB> The modern convention is full-name(abbreviation)

========

   The Sun Network File System (NFS) uses a Remote Procedure Call
(RPC)
   protocol [RPC] that, when used over UDP, in many cases will
generate
   payloads that must be fragmented even for the first-hop link. 
This
   might improve performance in certain cases, but it is known to
cause
   reliability and performance problems, especially when the client
and
   server are separated by routers.

SB> Perhaps this should point to RFC7530 (the current NFS Spec),
assuming
SB> the behaviour description is still correct.

=========

   The former can be accomplished by associating a flag with the
path;
   when a packet is sent on a path with this flag set, the IP layer
does
   not send packets larger than the IPv6 minimum link MTU.

SB> We do not normally give this level of implementation advice

========================




From nobody Thu Feb  9 09:05:41 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 382D8129C06; Thu,  9 Feb 2017 09:05:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nEZUpSvEb0fc; Thu,  9 Feb 2017 09:05:35 -0800 (PST)
Received: from mail-yw0-x243.google.com (mail-yw0-x243.google.com [IPv6:2607:f8b0:4002:c05::243]) (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 BAADA129C1A; Thu,  9 Feb 2017 09:05:21 -0800 (PST)
Received: by mail-yw0-x243.google.com with SMTP id l16so735222ywb.2; Thu, 09 Feb 2017 09:05:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NRN2xol7PfmEIbEWh3SAjpAM0aRz5WBDEBe4N/Y6mHQ=; b=smQBCeEfaT5v+fi+9uugZGBBTU/nVKhEOXZ415CXUNB+cao48/AmQ0GLmWhzjsn/tD KGFJJMJYQhylEfUy6fjXY622dIQitqom55FjR/k+cPgXJRBA8xtvyffS4s+PTfQ6mdFE viYMilcZLlN1Q0qz1/m8tenKRWBUpvBML07vApz4ZwIGt3qVhqWJn8ePGZBZJDam8FuY V9UoF+O4iLC+Aov27IIRiVOTiTGuHW5KAAH6Vt1zglFxxmR2AIlRTXwRtZugm8t2kI2y SLCzcKsQs4MWDKuLweHYRj2C6gIiDCHZq9e+Ev5RykGGyumCLc8DMf9HPW1FDK+f00Nl BFfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=NRN2xol7PfmEIbEWh3SAjpAM0aRz5WBDEBe4N/Y6mHQ=; b=oasFJgO9ctGdLRkAIAX8D/Csb6cpg83A0rHDeNY6/jirxkIRAssG4alzgMBO2pk6x2 +QEeNsVVIywz5ywxi2VzMxFH7L3ts8nN9rLlWeL4bpxkFDTM1T2zA+UlIBlsLPsM/Pql fnwxib+gQep7eYzn5CfmCn8Pv8BABdFf2yD5V7sshzDilT6qZMJvWikh1d/UsS2Jfyvg prgYuz2MyfS34wfBUG0ZJtjUD/KnPVt+yxu0ybAKX1VDWJCXSWosXvQ/8A5xSYfpsH5T uOT/pUZF/0+WFPzI+sEubkiYiy2IWKS8mKjGx2dGhXpS3ee4wsB+ecXdy4OBqfVa7MvM A1eA==
X-Gm-Message-State: AMke39lCPqUpi70ob558XxWMx8f9qesU6GEqxi2iVU6vx8TDaxYEMtk9h4FmI/jPRAZIUCUaM1BEiUCmmMgBbg==
X-Received: by 10.13.213.22 with SMTP id x22mr2966889ywd.165.1486659920857; Thu, 09 Feb 2017 09:05:20 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.17.213 with HTTP; Thu, 9 Feb 2017 09:05:20 -0800 (PST)
In-Reply-To: <03152892-3987-145c-8206-e3ccfe3a7510@isode.com>
References: <148616796247.4079.7104562493351135409.idtracker@ietfa.amsl.com> <11e900d0-553e-0635-06f4-8510bd80ecfd@dcrocker.net> <4ff42a3b-1f8e-3e25-14e7-b1d3ed2f69c2@isode.com> <368f2b68-8f10-9517-1edb-d213ff10563b@dcrocker.net> <03152892-3987-145c-8206-e3ccfe3a7510@isode.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 9 Feb 2017 12:05:20 -0500
X-Google-Sender-Auth: 5VU0znrrUn4yHuHewMbuKjBW_b8
Message-ID: <CAMm+Lwi=rD27tCJhgYv6RWg1SZ80LuvPRkW6CLQ53UZxxhBjbg@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap)
To: Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: multipart/alternative; boundary=001a114fbfca7c10a505481bfc99
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-YtelcmB9qDUPhEZErBi0S9enMw>
Cc: iesg <iesg@ietf.org>, jmap@ietf.org, Dave CROCKER <dcrocker@bbiw.net>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:05:36 -0000

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

One big improvement on the status quo would be to combine the functionality
of IMAP and SUBMIT.

Having two different protocols doesn't work folk. Particularly since
authentication remains a bad joke in SMTP and IMAP. I just sent three
copies of the same message to my CEO because my mail app thought it hadn't
been sent at all and kept retrying.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">One=
 big improvement on the status quo would be to combine the functionality of=
 IMAP and SUBMIT.=C2=A0</div><div class=3D"gmail_default" style=3D"font-siz=
e:small"><br></div><div class=3D"gmail_default" style=3D"font-size:small">H=
aving two different protocols doesn&#39;t work folk. Particularly since aut=
hentication remains a bad joke in SMTP and IMAP. I just sent three copies o=
f the same message to my CEO because my mail app thought it hadn&#39;t been=
 sent at all and kept retrying.</div></div>

--001a114fbfca7c10a505481bfc99--


From nobody Thu Feb  9 09:34:34 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7053129C2E for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:34:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qi5IkQ7BVwoc for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:34:30 -0800 (PST)
Received: from mail-ot0-x234.google.com (mail-ot0-x234.google.com [IPv6:2607:f8b0:4003:c0f::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 2624E129C28 for <ietf@ietf.org>; Thu,  9 Feb 2017 09:34:30 -0800 (PST)
Received: by mail-ot0-x234.google.com with SMTP id 65so8557676otq.2 for <ietf@ietf.org>; Thu, 09 Feb 2017 09:34:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=NTXhVMBAFbzRJN1BKF1/mcovsvT/xVInwWrir1jyikI=; b=OubRiY7dPT6IiaC/c5QUwTLPdF7sM+YTGuj+FsYrvCnpq0/Q0yg9gFoY1GcaozZU+w Kys8WxDttXM4dAFsC+uT+aWt1Tz+aFxa6/jwGxIJaYHCPGGP4KxgD5rij74UoDgvqEl+ DSMzbvRaAE81O3uy96i8VZZIyqTBRRv0h+LyfmzR2HY4uLOqTkNqRYvU+yfeqD1l7Fi5 w7rhXBTnNLeBbfEiAykqdCYsOV+TI0yKYh2QyKYeYcyv5iiT3rK5imFk48bw8Vx6e8Y0 LqAt/CyGiPM4Px1rNlTdUusF7k5wyVSvX9CKHp1k3rxIeDkSaXkCTJPJQ7XoFnNyzovX 4Dwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NTXhVMBAFbzRJN1BKF1/mcovsvT/xVInwWrir1jyikI=; b=fWxzHUENaV7jkwjjv4SOXrDRErAdcqyJibHZVxHXwMNDU2737xagIOVgOMm6zeJphF OaoC5AX542srAWZAvIJvN1kjQglPTG7tNg6Y2OcMYGzR3KDaye7z6zvyoJFO6o9b0U0D 1RtZBxJ9cy5EQ9HES4nORq57sXyyTDwiTrrymdyS4HJYLmHVGsnopBx1NTLkjO0eujGq ybL3kd+Dzf965xXh8lQAwYLIdz39Krn5MF+CUhp9AMcMumDIZvaMLr9kwakw1xwCUuqi eizqweVW6M2sSUtr/8wff1FP6D9khdtJ4jddARewnIY5lVjRcDSZccwH6di3d7LAwCka YHYQ==
X-Gm-Message-State: AMke39ljVDizJMz2aLNoV9aRC05y2RzP+UBexWSi/A8OlXb0VqvoE/ruVd/hogaSBeiKZUs4kAB/DyBS2bI+oehY
X-Received: by 10.157.6.46 with SMTP id 43mr2112744otn.143.1486661669174; Thu, 09 Feb 2017 09:34:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Thu, 9 Feb 2017 09:34:27 -0800 (PST)
In-Reply-To: <20170208151943.GQ28349@mournblade.imrryr.org>
References: <20170201210155.GI28349@mournblade.imrryr.org> <D45CE6A5317D4B373CD90742@PSB> <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org>
From: Wei Chuang <weihaw@google.com>
Date: Thu, 9 Feb 2017 09:34:27 -0800
Message-ID: <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="94eb2c09b6c4b57fd705481c647b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5hdJOTurD4FMEuvYGEwjxTx43N4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:34:33 -0000

--94eb2c09b6c4b57fd705481c647b
Content-Type: multipart/alternative; boundary=94eb2c09b6c4b1977705481c646c

--94eb2c09b6c4b1977705481c646c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Wed, Feb 8, 2017 at 7:19 AM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

> On Wed, Feb 08, 2017 at 06:46:41AM -0800, Wei Chuang wrote:
>
> > > This draft breaks the existing name constraint restrictions, because
> > > the same CA can now issue EE certificates with SmtpUtf8 addresses
> > > outside the permitted rfc822Name tree.  Possibly including all-ASCII
> > > addresses that just happen to be found in an SmtpUtf8 subjectAltName.
> > >
> > > The problem is that the namespaces of the existing "rfc822Name"
> > > constraints and the new "SmtpUtf8Name" constraints substantially
> > > overlap leading to unexpected behaviour.
> >
> > I wouldn't say unexpected.
>
> It may well be expected as a consequence of decisions in the draft,
> but it is objectively unwanted new behaviour for a name constrained
> CA, to suddenly be able to issue certificates for previously excluded
> addresses.  Software that allows such violations of previously
> enforced constraints would IMHO be CVE-worthy.
>
> > The draft says the rfc822Name and SmtpUtf8Name
> > name constraints are applied separately, and don't affect other results
> > (see section 6).
>
> Yes, that's what I'm objecting to.  This is a design error in the
> draft.  The namespaces are *not* separate, and orthogonal constraints
> are not desirable.
>

You are stretching the language used above.  They are "applied separately".


I think we're open to changing how name constraints are applied.  But its
worth spelling out the design concern clearly before going down that path.
The concern is that as we add a new representation for international email
address that we are seeing that combinatorial increase in comparisons
needed for name constraints.  An alternate design of SmtpUtf8Name would
have to check constraints for rfc822Name and legacy email address in
Distinguished Names in addition to SmtpUtf8Name and vice versa for those
forms.  This design chooses to simplify that by keeping rfc822Name name
constraint behavior and separately defining a new SmtpUtf8Name name
constraint behavior that works only on SmtpUtf8Name names.  That simplifies
the work of the path verifier and eliminates potential domain (A/U label)
conversions between the alternate forms.  Work is now shifted to the issuer
which must explicitly define SmtpUtf8Name name constraint.


>
> > It is followed by examples illustrating the behavior of
> > the overlap case.  The reason for separating the rfc822Name and
> > SmtpUtf8Name constraints was to minimize the domain A-label to U-label
> > conversions (and vice versa) (which I believe you're asking for too).
>
> This is not a valid reason to violate the meaning of existing name
> constraints.  It is not even clear why any conversions would be
> required.  All that one needs to do is satisfy rfc822Name constraints
> when no SmtpUtf8Name constraints are present in the same certificate.
> When the domain is a non-ASCII domain, no permitted tree or excluded
> sub-tree matches without conversion.  Thus the address is acceptable
> only if the rfc822Name constraints contain only excluded sub-trees.
>
> The only corner case is when an all-ASCII address (both localpart
> and domainpart) for some reason appears in SmtpUtf8Name.  Such
> names could match a full address in rfc822Name constraints (not
> just a domainpart sub-tree).  This is why it is important to be
> clear about whether all-ASCII names are valid in that context.
>
> > The assumption being made in the draft is that a SmtpUtf8Name
> > aware issuer will also be aware of the name constraints on that type.
>
> The issuer may be SmtpUtf8 aware, but the parent CA that sets the
> issuer's constraints (possibly some time ago in the past) may not.
> The issuer should not be able to evade name constraints.
>

Assuming we keep the current name constraint design, we can add a
requirement that name constraints on email addresses has to be consistently
applied on the certificate issuance path.  In other words, an issuer with
only rfc822Name name constraints in its path can only issue rfc822Name
subAltName email addresses.  Similarly SmptUtf8Name.  An issuer with both
SmtpUtf8Name and rfc822Name in its path can issue both subjectAltName name
form email addresses.

-Wei

--94eb2c09b6c4b1977705481c646c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 8, 2017 at 7:19 AM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On Wed, Feb 08, 2017 at 06:46:41AM -0800, Wei Chuang wrote:<br>
<br>
&gt; &gt; This draft breaks the existing name constraint restrictions, because<br>
&gt; &gt; the same CA can now issue EE certificates with SmtpUtf8 addresses<br>
&gt; &gt; outside the permitted rfc822Name tree.  Possibly including all-ASCII<br>
&gt; &gt; addresses that just happen to be found in an SmtpUtf8 subjectAltName.<br>
&gt; &gt;<br>
&gt; &gt; The problem is that the namespaces of the existing &quot;rfc822Name&quot;<br>
&gt; &gt; constraints and the new &quot;SmtpUtf8Name&quot; constraints substantially<br>
&gt; &gt; overlap leading to unexpected behaviour.<br>
&gt;<br>
&gt; I wouldn&#39;t say unexpected.<br>
<br>
</span>It may well be expected as a consequence of decisions in the draft,<br>
but it is objectively unwanted new behaviour for a name constrained<br>
CA, to suddenly be able to issue certificates for previously excluded<br>
addresses.  Software that allows such violations of previously<br>
enforced constraints would IMHO be CVE-worthy.<br>
<span class="gmail-"><br>
&gt; The draft says the rfc822Name and SmtpUtf8Name<br>
&gt; name constraints are applied separately, and don&#39;t affect other results<br>
&gt; (see section 6).<br>
<br>
</span>Yes, that&#39;s what I&#39;m objecting to.  This is a design error in the<br>
draft.  The namespaces are *not* separate, and orthogonal constraints<br>
are not desirable.<br></blockquote><div><br></div><div>You are stretching the language used above.  They are &quot;applied separately&quot;.  </div><div><br></div><div>I think we&#39;re open to changing how name constraints are applied.  But its worth spelling out the design concern clearly before going down that path.  The concern is that as we add a new representation for international email address that we are seeing that combinatorial increase in comparisons needed for name constraints.  An alternate design of SmtpUtf8Name would have to check constraints for rfc822Name and legacy email address in Distinguished Names in addition to SmtpUtf8Name and vice versa for those forms.  This design chooses to simplify that by keeping rfc822Name name constraint behavior and separately defining a new SmtpUtf8Name name constraint behavior that works only on SmtpUtf8Name names.  That simplifies the work of the path verifier and <!--
-->eliminates potential domain (A/U label) conversions between the alternate forms.  Work is now shifted to the issuer which must explicitly define SmtpUtf8Name name constraint.  </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<span class="gmail-"><br>
&gt; It is followed by examples illustrating the behavior of<br>
&gt; the overlap case.  The reason for separating the rfc822Name and<br>
&gt; SmtpUtf8Name constraints was to minimize the domain A-label to U-label<br>
&gt; conversions (and vice versa) (which I believe you&#39;re asking for too).<br>
<br>
</span>This is not a valid reason to violate the meaning of existing name<br>
constraints.  It is not even clear why any conversions would be<br>
required.  All that one needs to do is satisfy rfc822Name constraints<br>
when no SmtpUtf8Name constraints are present in the same certificate.<br>
When the domain is a non-ASCII domain, no permitted tree or excluded<br>
sub-tree matches without conversion.  Thus the address is acceptable<br>
only if the rfc822Name constraints contain only excluded sub-trees.<br>
<br>
The only corner case is when an all-ASCII address (both localpart<br>
and domainpart) for some reason appears in SmtpUtf8Name.  Such<br>
names could match a full address in rfc822Name constraints (not<br>
just a domainpart sub-tree).  This is why it is important to be<br>
clear about whether all-ASCII names are valid in that context.<br>
<span class="gmail-"><br>
&gt; The assumption being made in the draft is that a SmtpUtf8Name<br>
&gt; aware issuer will also be aware of the name constraints on that type.<br>
<br>
</span>The issuer may be SmtpUtf8 aware, but the parent CA that sets the<br>
issuer&#39;s constraints (possibly some time ago in the past) may not.<br>
The issuer should not be able to evade name constraints.<br></blockquote><div><br></div><div>Assuming we keep the current name constraint design, we can add a requirement that name constraints on email addresses has to be consistently applied on the certificate issuance path.  In other words, an issuer with only rfc822Name name constraints in its path can only issue rfc822Name subAltName email addresses.  Similarly SmptUtf8Name.  An issuer with both SmtpUtf8Name and rfc822Name in its path can issue both subjectAltName name form email addresses.</div><div> </div><div>-Wei</div></div></div></div>

--94eb2c09b6c4b1977705481c646c--

--94eb2c09b6c4b57fd705481c647b
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCDz1s5ZBwhS59dF8HG2v3EU
u/GfRzf3vI46IzNd3Cud+jAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMDkxNzM0MjlaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAXbAFNNXkxH7ZMqUWxgacVlZdHnfCwtQfuBo1x7il
QmXqpg7yU7TBOmlWeLPJS9Mm1Nq4qJoXV5oPxRGJLl6P6s1fpfX9A45EqxA04vXRF8gMqo1S/Qu8
eY9NNud0SHZawQhbM8CRrjl+neEwNErHWVU9PcXJuiyNsBg4P8aMHWqWBnmGvIf2XKvlyfqFveL7
2JzCTYY1uYqry+9gWyBwH+SXLioVEHG9QhDts0gNiUR0qnvZqRb9o1HEwLkHVTmhrV1opS/0PfkD
CVkQIMQSBPG+YFXMFteIf09fE1UuL4H9EoSxWRbmE8J2JKx5Dz7xJZz7vzNUhCFVEmNmdg7ttw==
--94eb2c09b6c4b57fd705481c647b--


From nobody Thu Feb  9 09:51:27 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD01D129C33 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:51:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=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 zIp5Si5la2GV for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:51:24 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77944129C32 for <ietf@ietf.org>; Thu,  9 Feb 2017 09:51:24 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 88EDA284E4C; Thu,  9 Feb 2017 17:51:22 +0000 (UTC)
Date: Thu, 9 Feb 2017 17:51:22 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170209175122.GU28349@mournblade.imrryr.org>
References: <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: attachment
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3OrlrpVkGfVwTB1w56s-3M9n-J4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:51:26 -0000

On Thu, Feb 09, 2017 at 09:34:27AM -0800, Wei Chuang wrote:

> > > The draft says the rfc822Name and SmtpUtf8Name
> > > name constraints are applied separately, and don't affect other results
> > > (see section 6).
> >
> > Yes, that's what I'm objecting to.  This is a design error in the
> > draft.  The namespaces are *not* separate, and orthogonal constraints
> > are not desirable.
> 
> You are stretching the language used above.  They are "applied separately".

Separate application is not sufficient when the issuer's certificate
contains only rfc822Name constraints.

> I think we're open to changing how name constraints are applied.  But its
> worth spelling out the design concern clearly before going down that path.
> The concern is that as we add a new representation for international email
> address that we are seeing that combinatorial increase in comparisons
> needed for name constraints.

My proposal creates no combinatorial increase of any kind.  When
the issuer CA has *only* rfc822Name constraints, any SmtpUtf8Name
subjectAltNames in the certificate, instead of getting a free ride,
would have to satisfy the rfc822Name constraints.  Each rfc822Name
constraint becomes (under the identity function) a valid SmtpUtf8
constraint.

> This design chooses to simplify that by keeping rfc822Name name
> constraint behavior and separately defining a new SmtpUtf8Name name
> constraint behavior that works only on SmtpUtf8Name names.

Yes, buts this evades rfc822Name constraints created SmtpUtf8-agnostic
parent issuers.  The namespaces are not disjoint.

> That simplifies
> the work of the path verifier and eliminates potential domain (A/U label)
> conversions between the alternate forms.  Work is now shifted to the issuer
> which must explicitly define SmtpUtf8Name name constraint.

The simplest thing for the verifier is to do no checks at all.
Presumably we make things as simple as possible, but no simpler.
The security requirements should be to correctly process existing
name constraints.  And I don't believe that *any* conversions are
required to do this.

Specifically, rfc822Name constraints that include a non-empty list
of permitted subtrees, in the absence of explicit SmtpUtf8Name
constraints would imply that the CA cannot issue *any* email altnames
for a non-ASCII domain.   If the domain is all-ASCII, no conversions
are required.  If the rfc822Name constraints have only excluded
subtrees, then no non-ASCII domain is excluded.

> > The issuer may be SmtpUtf8 aware, but the parent CA that sets the
> > issuer's constraints (possibly some time ago in the past) may not.
> > The issuer should not be able to evade name constraints.
> 
> Assuming we keep the current name constraint design, we can add a
> requirement that name constraints on email addresses has to be consistently
> applied on the certificate issuance path.  In other words, an issuer with
> only rfc822Name name constraints in its path can only issue rfc822Name
> subAltName email addresses.

No that's too limiting.  If the issuer is permitted to issue altnames
for "example.org", it should be able to issue "виктор@example.org".

-- 
	Viktor.


From nobody Thu Feb  9 09:57:42 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39ED5129C2E for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=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 f6WaaqxefkwK for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:57:38 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B827012943B for <ietf@ietf.org>; Thu,  9 Feb 2017 09:57:38 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 2180F284E4C; Thu,  9 Feb 2017 17:57:38 +0000 (UTC)
Date: Thu, 9 Feb 2017 17:57:38 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170209175737.GV28349@mournblade.imrryr.org>
References: <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yc-648WjF629sazn2RyCfBbPgaA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:57:40 -0000

[ Sorry about the duplicate post, Somehow the original body got
  "Content-Disposition: attachment", reposting as "inline". ]

On Thu, Feb 09, 2017 at 09:34:27AM -0800, Wei Chuang wrote:

> > > The draft says the rfc822Name and SmtpUtf8Name
> > > name constraints are applied separately, and don't affect other results
> > > (see section 6).
> >
> > Yes, that's what I'm objecting to.  This is a design error in the
> > draft.  The namespaces are *not* separate, and orthogonal constraints
> > are not desirable.
> 
> You are stretching the language used above.  They are "applied separately".

Separate application is not sufficient when the issuer's certificate
contains only rfc822Name constraints.

> I think we're open to changing how name constraints are applied.  But its
> worth spelling out the design concern clearly before going down that path.
> The concern is that as we add a new representation for international email
> address that we are seeing that combinatorial increase in comparisons
> needed for name constraints.

My proposal creates no combinatorial increase of any kind.  When
the issuer CA has *only* rfc822Name constraints, any SmtpUtf8Name
subjectAltNames in the certificate, instead of getting a free ride,
would have to satisfy the rfc822Name constraints.  Each rfc822Name
constraint becomes (under the identity function) a valid SmtpUtf8
constraint.

> This design chooses to simplify that by keeping rfc822Name name
> constraint behavior and separately defining a new SmtpUtf8Name name
> constraint behavior that works only on SmtpUtf8Name names.

Yes, buts this evades rfc822Name constraints created SmtpUtf8-agnostic
parent issuers.  The namespaces are not disjoint.

> That simplifies
> the work of the path verifier and eliminates potential domain (A/U label)
> conversions between the alternate forms.  Work is now shifted to the issuer
> which must explicitly define SmtpUtf8Name name constraint.

The simplest thing for the verifier is to do no checks at all.
Presumably we make things as simple as possible, but no simpler.
The security requirements should be to correctly process existing
name constraints.  And I don't believe that *any* conversions are
required to do this.

Specifically, rfc822Name constraints that include a non-empty list
of permitted subtrees, in the absence of explicit SmtpUtf8Name
constraints would imply that the CA cannot issue *any* email altnames
for a non-ASCII domain.   If the domain is all-ASCII, no conversions
are required.  If the rfc822Name constraints have only excluded
subtrees, then no non-ASCII domain is excluded.

> > The issuer may be SmtpUtf8 aware, but the parent CA that sets the
> > issuer's constraints (possibly some time ago in the past) may not.
> > The issuer should not be able to evade name constraints.
> 
> Assuming we keep the current name constraint design, we can add a
> requirement that name constraints on email addresses has to be consistently
> applied on the certificate issuance path.  In other words, an issuer with
> only rfc822Name name constraints in its path can only issue rfc822Name
> subAltName email addresses.

No that's too limiting.  If the issuer is permitted to issue altnames
for "example.org", it should be able to issue "виктор@example.org".

-- 
	Viktor.


From nobody Thu Feb  9 09:58:46 2017
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DCDC129C2F for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:58:45 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 rvQa7ANfVRTH for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 09:58:44 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4452212943B for <ietf@ietf.org>; Thu,  9 Feb 2017 09:58:44 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id CFB3F2009E; Thu,  9 Feb 2017 13:19:50 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9F4136381A; Thu,  9 Feb 2017 12:58:41 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alia Atlas <akatlas@gmail.com>
Subject: Re: tools forum idea for IETF 98
In-Reply-To: <CAG4d1re-o2jBJQhs+C51Xw-T1yV7UmQY86wrq0THikm6WDgQ1A@mail.gmail.com>
References: <CAG4d1re-o2jBJQhs+C51Xw-T1yV7UmQY86wrq0THikm6WDgQ1A@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 09 Feb 2017 12:58:41 -0500
Message-ID: <19251.1486663121@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xNMfAo8RplWmy3DTMra8AviQ6zk>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 17:58:45 -0000

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


Alia Atlas <akatlas@gmail.com> wrote:
    > There have been some discussions about having a meeting at IETF 98 to
    > discuss existing experimental tools and encourage discussion among
    > those working on tools to handle specific issues. The basic meeting
    > description is

I'm excited by this.
I probably know a dozen tools, but I don't know that I know about them.
Or rather, I'm probably ignorant that others don't know about them :-)

    > Agenda: 30 minutes of new tools lightning talks
    > 60 minutes of small group discussion on different tool areas

Scheduling for this might be difficult.

Suggestion: once we get a few lightning talks in the "can", that each
            WG chairs luncheon start with one such <5minute talk.


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




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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAlicrdEACgkQgItw+93Q
3WVNtQf9GA2OHiUmb2Y0+c+Pi8OiQjORXYaTp+pfOoOcTSXjd2f2zOulOI6MXdJy
btiZzIdsUY62kszEiZqYej8fWDP+xqC0K/1djo0Sg8EJ2cjnfI2o3N55VvtNvUui
Z+J5N65w7NGr18TjxWx3eoqSyMImwN8qTgQuGWDGf6tJ9oDkGfcCoa4Y0FuR+kRY
jXN/AXhsJL+0GF6RamHfzkwDAldXExuWdA9mSChEv1IvLpMio31MXsZFE7d1yiv0
AdpwTjFIb+YTOdyCsAhDPgeV42R7Hi0EI1YToojk7pA4TnLjTzjNmuApB+jb2Yf+
Fo70IFwtBaRkYaxAu5YpGsq+CC2oBw==
=Z0fH
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Feb  9 10:00:16 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476FC128E19; Thu,  9 Feb 2017 10:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBvaYhdzvB2c; Thu,  9 Feb 2017 10:00:11 -0800 (PST)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 2F4AE129C2F; Thu,  9 Feb 2017 09:59:47 -0800 (PST)
Received: by mail-qk0-x22e.google.com with SMTP id u25so12868712qki.2; Thu, 09 Feb 2017 09:59:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=5f/C241YrgffYrcxW1/6D67t5yx3rQYTOjKRjZEpLz4=; b=qYZdeEwq2dAhUW72y2Pi+KM4EuZYJ+NVSvSTwRaEFe6dSQR15h9WquIf6Zqu+IuHLg AioyfxVBOfO/WRSiDGQ5KEXRF/DoDSC7Y+S2dx5UN+mCQVrOrBZHSmcsBHFc7747ENXc /cU3KsQ8PrN5NtN/CxQQoOE1GQekdze9RyKEsLqpHsABDZ1jbFCrSoPbW2sbKLhX4/GU ruEEq+YSre42VWbqZ50FxaFAAN7wunBfPTYHxkA1tbHrUBtRLHuLTUo1yOg7e+Z/WvwT rf6lSfI05z34bwGRGofNDA1D9LTsTGZgRKDbCTMT0paQLjHZUd7xGP4pZCkQs6xj87gq 0yTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=5f/C241YrgffYrcxW1/6D67t5yx3rQYTOjKRjZEpLz4=; b=uIwB94KSZksjwTQF8JbC1zkkY5jl3i6qrGErOYVdZhftN8cOV5Ff7WCG7OEkJEIUju oWXBHRSB2sT5J/QKPHr3MBxAgo2f6NuNOPmgIVs6hx+qkUNlqE20bOSmWUGPjyK0mXKE Ev6AqwoaKup2jOn2E+DZ5V/OyKyQhtd1Ck3ccUiQ6WPiNZMCz8v1z4WRYWpBR6KytYqq 5OI8YtulJFZYm0RqN2npK/r8GKBWiyjvW0df9Ti40tQeFHFD32eQoVkjHX0EIrupw7mF sWnqGcEVQdjRL3t2XwGQA4Wjfqszee4m4FkhI283EbohNFapUci09JPFsx/KKxUYk2fZ 658g==
X-Gm-Message-State: AMke39lhUUnzgeAiMjREWWmihFRsVQJuIf0AhdXOk3Vq49nYIEqFHINUNMWd/mIuTNyt2H29vglRR3u3rXaE6Q==
X-Received: by 10.55.19.224 with SMTP id 93mr4560153qkt.198.1486663186005; Thu, 09 Feb 2017 09:59:46 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.140.19.72 with HTTP; Thu, 9 Feb 2017 09:59:45 -0800 (PST)
In-Reply-To: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 9 Feb 2017 09:59:45 -0800
X-Google-Sender-Auth: n9LGKBTxwLQT_uXNFiE1_d2QvPY
Message-ID: <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pjYn7WGXKqJv0RGMC0wAUxdw4YI>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 18:00:13 -0000

As a result of the discussion on the -19 version of the draft (where
"IANA" was replaced with "IANA Services" throughout, and related
changes were made), the IETF Trust agreed on the alternative of
putting a paragraph at the beginning (the second paragraph in the
Introduction in version -20), and then reverting most of the other
changes in -19.

Version -20 now only has the paragraph that explains that we call
<this stuff> "IANA" in this document, plus a few minor changes that
came out in IESG Evaluation.

We believe the document is now ready to publish, having been through
Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
send this version off.

Thanks, everyone, for the comments!

Barry, document editor

On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
>
> A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
> has been successfully submitted by Barry Leiba and posted to the
> IETF repository.
>
> Name:           draft-leiba-cotton-iana-5226bis
> Revision:       20
> Title:          Guidelines for Writing an IANA Considerations Section in RFCs
> Document date:  2017-02-08
> Group:          Individual Submission
> Pages:          41
> URL:            https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.txt
> Status:         https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
> Htmlized:       https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-leiba-cotton-iana-5226bis-20
>
> Abstract:
>    Many protocols make use of points of extensibility that use constants
>    to identify various protocol parameters.  To ensure that the values
>    used in these fields do not have conflicting uses, and to promote
>    interoperability, their allocation is often coordinated by a central
>    record keeper.  For IETF protocols, that role is filled by the
>    Internet Assigned Numbers Authority (IANA).
>
>    To make assignments in a given registry prudently, guidance is needed
>    for describing the conditions under which new values should be
>    assigned, as well as when and how modifications to existing values
>    can be made.  This document defines a framework for the documentation
>    of these guidelines by specification authors, in order to assure that
>    the provided guidance for the IANA Considerations is clear and
>    addresses the various issues that are likely in the operation of a
>    registry.
>
>    This is the third edition of this document; it obsoletes RFC 5226.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>


From nobody Thu Feb  9 10:06:39 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFD5A129C3A for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 10:06:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iv4mwgpkCWXG for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 10:06:35 -0800 (PST)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::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 26703129C3C for <ietf@ietf.org>; Thu,  9 Feb 2017 10:06:35 -0800 (PST)
Received: by mail-wr0-x230.google.com with SMTP id 89so89438916wrr.2 for <ietf@ietf.org>; Thu, 09 Feb 2017 10:06:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pRRn4xZeYW2KTzMHU4+mqURMukf1ItxlSdRy3ordaag=; b=r0AdA8qoVk54R3JLDKj3c6l1w2Z0AeN8ArKk91rJKdXqlhlVzW038Q57r8kgXaBsiq 0f7ucBSN/CuWwLOZ40UDoDIwbDKCFDFcbhQQ/n2K4Ksql6OgMIWa1ybHYRIXWSfyrFvf xo+0yeRd3Fhq5Zik/8fJnxsYC1T88IVTG4mjrrBtywwhgs49Z/oI8ZgCkAl9gLaD7Fbb V4USck0OPNnRgPDeYXYrUs9VD3mHyHrqGMsTr6lAakqIIzRDs7zI6ecjg+RJnPOWXQav nX2ItV85WNscq1vVvwlN5ZNqGALTePiIvqy/gH8CoRzAMsLoMt2MVxYT5a0nQaJAylee gj5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pRRn4xZeYW2KTzMHU4+mqURMukf1ItxlSdRy3ordaag=; b=rHQkh/aslZcVr9pVNA+Yhd2VWmwNGRKdrLNqZPkntZe6et0CrmSNkh7k1JU3OxZJTU hvcN7dZ7IpKUEweWW6cDf7mN5B/mC1NFMiAtxHtk77sSIQaypiuCLLKrrvEvdD8PMyWu woyaXKCJ61Gk1Lsmyolk0vH1X+kY+8iUZNT+n3JhXezrg4WibbQUAIr198xPjtmkTMZd srCh2hKl9JmDR1jAxGp4Iy71deVDkMrLo0Tx3m383qiztMK3kC3OcYa+FI2XT2go9E9o xkP6ekRbUcUXQg7QbIBzOT0+ULCiUzpTezevFMRCr9xhrHrqhpYirpff0+4ilcr/sZSh lwYQ==
X-Gm-Message-State: AMke39nArr4pMQgqlOxsp9dYWbNcMCfTS7wRRnpP7VU7ETm0hG/+YO5l+VzojHUbTVTn+xwKqb2N0YtbRjM8lA==
X-Received: by 10.223.147.225 with SMTP id 88mr4105648wrp.44.1486663593518; Thu, 09 Feb 2017 10:06:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.142.108 with HTTP; Thu, 9 Feb 2017 10:06:32 -0800 (PST)
In-Reply-To: <19251.1486663121@obiwan.sandelman.ca>
References: <CAG4d1re-o2jBJQhs+C51Xw-T1yV7UmQY86wrq0THikm6WDgQ1A@mail.gmail.com> <19251.1486663121@obiwan.sandelman.ca>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 9 Feb 2017 13:06:32 -0500
Message-ID: <CAG4d1resjBt_-Vou3Z26SvVUdD0Rj7WQt6kvydm1wbWFJspWkA@mail.gmail.com>
Subject: Re: tools forum idea for IETF 98
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=94eb2c0df21c646f9e05481cd74c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jUIqXK_XPiPwvWtR8QooOH91ltk>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 18:06:38 -0000

--94eb2c0df21c646f9e05481cd74c
Content-Type: text/plain; charset=UTF-8

Hi Michael,

On Thu, Feb 9, 2017 at 12:58 PM, Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Alia Atlas <akatlas@gmail.com> wrote:
>     > There have been some discussions about having a meeting at IETF 98 to
>     > discuss existing experimental tools and encourage discussion among
>     > those working on tools to handle specific issues. The basic meeting
>     > description is
>
> I'm excited by this.
> I probably know a dozen tools, but I don't know that I know about them.
> Or rather, I'm probably ignorant that others don't know about them :-)
>

Exactly - and for some of them, it has been a couple years at least where
the knowledge
and use isn't spreading organically.

Which tools are you thinking of?   Personally, I just started writing a
draft in markdown & then
discovered that the WYSWYG web translator isn't working for me and poking
at github led to lots of dependencies.

    > Agenda: 30 minutes of new tools lightning talks
>     > 60 minutes of small group discussion on different tool areas
>
> Scheduling for this might be difficult.
>
> Suggestion: once we get a few lightning talks in the "can", that each
>             WG chairs luncheon start with one such <5minute talk.
>

A goal of the small group discussion is to have folks find others
interested in the same
topic, understand what might be useful, and perhaps be motivated to do some
work on them
or volunteer to try them out as they are developed and so on.

So far, I've gotten a number of volunteers for lightning talks - certainly
more than 3 - and
a couple folks willing to facilitate small group discussion, but not
specific topics looking
like they have mass.   I'd be happy to see more discussion on this aspect.

I agree that scheduling is going to be tricky.  Options might include a
bring-your-own meal slot
or a before-dinner slot.  There's always scheduling it with lots of
conflicts like a non-WG-forming
BoF.

The audience isn't just WG chairs, of course, though I do hear your point
about having something
on-going about continuing tool experiments.  Let's see if this has enough
energy to try once and then see what makes sense afterwards.

Regards,
Alia




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

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

<div dir=3D"ltr">Hi Michael,<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Thu, Feb 9, 2017 at 12:58 PM, Michael Richardson <span dir=3D=
"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">mcr+ie=
tf@sandelman.ca</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><sp=
an class=3D""><br>
Alia Atlas &lt;<a href=3D"mailto:akatlas@gmail.com">akatlas@gmail.com</a>&g=
t; wrote:<br>
=C2=A0 =C2=A0 &gt; There have been some discussions about having a meeting =
at IETF 98 to<br>
=C2=A0 =C2=A0 &gt; discuss existing experimental tools and encourage discus=
sion among<br>
=C2=A0 =C2=A0 &gt; those working on tools to handle specific issues. The ba=
sic meeting<br>
=C2=A0 =C2=A0 &gt; description is<br>
<br>
</span>I&#39;m excited by this.<br>
I probably know a dozen tools, but I don&#39;t know that I know about them.=
<br>
Or rather, I&#39;m probably ignorant that others don&#39;t know about them =
:-)<br></blockquote><div><br></div><div>Exactly - and for some of them, it =
has been a couple years at least where the knowledge</div><div>and use isn&=
#39;t spreading organically.=C2=A0</div><div>=C2=A0</div><div>Which tools a=
re you thinking of? =C2=A0 Personally, I just started writing a draft in ma=
rkdown &amp; then</div><div>discovered that the WYSWYG web translator isn&#=
39;t working for me and poking at github led to lots of dependencies.</div>=
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
=C2=A0 =C2=A0 &gt; Agenda: 30 minutes of new tools lightning talks<br>
=C2=A0 =C2=A0 &gt; 60 minutes of small group discussion on different tool a=
reas<br>
<br>
</span>Scheduling for this might be difficult.<br>
<br>
Suggestion: once we get a few lightning talks in the &quot;can&quot;, that =
each<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 WG chairs luncheon start with one=
 such &lt;5minute talk.<br></blockquote><div><br></div><div>A goal of the s=
mall group discussion is to have folks find others interested in the same</=
div><div>topic, understand what might be useful, and perhaps be motivated t=
o do some work on them</div><div>or volunteer to try them out as they are d=
eveloped and so on.</div><div><br></div><div>So far, I&#39;ve gotten a numb=
er of volunteers for lightning talks - certainly more than 3 - and</div><di=
v>a couple folks willing to facilitate small group discussion, but not spec=
ific topics looking</div><div>like they have mass. =C2=A0 I&#39;d be happy =
to see more discussion on this aspect.</div><div><br></div><div>I agree tha=
t scheduling is going to be tricky.=C2=A0 Options might include a bring-you=
r-own meal slot</div><div>or a before-dinner slot.=C2=A0 There&#39;s always=
 scheduling it with lots of conflicts like a non-WG-forming</div><div>BoF. =
=C2=A0=C2=A0</div><div><br></div><div>The audience isn&#39;t just WG chairs=
, of course, though I do hear your point about having something</div><div>o=
n-going about continuing tool experiments.=C2=A0 Let&#39;s see if this has =
enough energy to try once and then see what makes sense afterwards.</div><d=
iv><br></div><div>Regards,</div><div>Alia</div><div><br></div><div><br></di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">mcr+IETF@=
sandelman.ca</a>&gt;, Sandelman Software Works<br>
=C2=A0-=3D IPv6 IoT consulting =3D-<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--94eb2c0df21c646f9e05481cd74c--


From nobody Thu Feb  9 10:19:27 2017
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC380129C48 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 10:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.596
X-Spam-Level: 
X-Spam-Status: No, score=-2.596 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PMZ8Ai8l-ND1 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 10:19:23 -0800 (PST)
Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 8EA2B127076 for <ietf@ietf.org>; Thu,  9 Feb 2017 10:19:23 -0800 (PST)
Received: by mail-yw0-x22a.google.com with SMTP id l19so7240853ywc.2 for <ietf@ietf.org>; Thu, 09 Feb 2017 10:19:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=tN9p0QsaQdvB498jUBa+OQXkp0ALGId5ZJoVZ+18ZuY=; b=deWLDALEVglnEFxCTdz5PA5X1aEIgRqPAPd/IAUOrMjvILKqFShAjt8BTQOqzLckoD 5b1v3vdrTJ94+g5kgk0NhzcqUU56WvAy/MzTGxL6/jSzzmXSivM0U0l/O2vV16UYnkZt u3eX9qtIKTf5XbneOS6b5+OmhHxpOYUyco9UugVqIKizHhr9YajqSjHZbXieyYSGsVQs 8iP8L6rcOspTh3NUNHsyETHCpKPB1Tgv4XmxzuiSVJ1CjKhfIeRi+O0rAmvhhNSHSDv9 GvaRq5kqHYzZqYXGrBiv5irDWPNsGp96R5zfCeOStFA1o9b0wqu2RAMqrbWZXQyGCbdu b+Qg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=tN9p0QsaQdvB498jUBa+OQXkp0ALGId5ZJoVZ+18ZuY=; b=cKyVZ05W+2m4Sf0MwpO6z3dHjSyALyFc6samUs0qarpwnAztV7jggo4kGiv55OUuQY +DkAvNwNunYTnJszD3CPD5Dk6YjkKOHZ+xXBh7dSIH5qN5XqiymzU7pWtq0fzyL0BM2T xNQol+mXMvoRowQ8h2XZvJZ3rTttc185rsb6gZARcxGx0RMZJd/+e0DoYaXBQ//qJK4J UnAaeBZ4JBeLgEIAYWGYrUjyRHW/eT/YC5KHbZ8AjbJfxzh9LGcGFZ2zSdp499jGHN3f G3UDROH72I5y4SJheJT/LWzquHYcm84GZ7hVLIbl5Xk8J5DJsifyexlSUR1OS4Xs17Ep nGnw==
X-Gm-Message-State: AMke39n6qaW0fN7VF/sTUgK4yNDE8OVPKbXIokV7rS3EQBrLv6qar8FMjUCrVjhbctzfsmB40IhjFhdqX/gSeQ==
X-Received: by 10.13.231.129 with SMTP id q123mr3282130ywe.202.1486664362646;  Thu, 09 Feb 2017 10:19:22 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.83.17.213 with HTTP; Thu, 9 Feb 2017 10:19:22 -0800 (PST)
In-Reply-To: <19251.1486663121@obiwan.sandelman.ca>
References: <CAG4d1re-o2jBJQhs+C51Xw-T1yV7UmQY86wrq0THikm6WDgQ1A@mail.gmail.com> <19251.1486663121@obiwan.sandelman.ca>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Thu, 9 Feb 2017 13:19:22 -0500
X-Google-Sender-Auth: -hMkLTSibspKLGl0LmP7udjJ1l4
Message-ID: <CAMm+LwhdFkjR3b3YPfnsMKKNdQ4-0wbQAbo_qdz03VrxKtUEaQ@mail.gmail.com>
Subject: Re: tools forum idea for IETF 98
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=94eb2c0763923c632005481d05dd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tirAKoPEhHCUU3Gwg8nhYq5Lm-4>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 18:19:26 -0000

--94eb2c0763923c632005481d05dd
Content-Type: text/plain; charset=UTF-8

Since its on topic, just thought I would mention that I have ported my
documentation and spec building tools to Linux and OSX. I do not yet have a
Linux installer but that will probably happen in a couple of months time.

https://github.com/hallambaker/PHB-Build-Tools

The code is all in C# which has just acquired a fully MIT Licensed open
source implementation. The tools can be used as standalone command line
tools or as integrated Visual Studio components. I use Visual Studio for my
build environment on every platform, Linux and OSX included. There is a
tool that will convert Visual Studio projects to Gnu Makefiles. The only
serious limitation being that I can't run unit tests on platforms other
than Windows at the moment.

OK so what tools?

First, I have my own RFC documentation tool that can take source from
MarkDown, Word, XML2RFC or HTML. It does not yet support the new format but
will in the near future.

Second, I have a protocol compiler that allows a protocol to be defined in
a very high level schema from which the reference sections of the
specification, examples, reference and production code are generated.

My approach is at a higher level of abstraction to YANG. I believe that the
process of designing a standard is to remove choices that don't matter.
There are hundreds of ways that an integer value can be encoded and DNS
uses at least 6 different forms. If you are designing a protocol you should
choose one and stick to it. I don't currently deal in YANG but if I had to,
YANG would be an output from my tools.

The same libraries also include an ASN.1 encoder (and partial decoder),
JSON, RFC822 and DNS serialization/deserialization tools.

The tool building tool is also included.

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

<div dir=3D"ltr"><div class=3D"gmail_default">Since its on topic, just thou=
ght I would mention that I have ported my documentation and spec building t=
ools to Linux and OSX. I do not yet have a Linux installer but that will pr=
obably happen in a couple of months time.</div><div class=3D"gmail_default"=
><br></div><div class=3D"gmail_default"><a href=3D"https://github.com/halla=
mbaker/PHB-Build-Tools">https://github.com/hallambaker/PHB-Build-Tools</a><=
br></div><div class=3D"gmail_default"><br></div><div class=3D"gmail_default=
">The code is all in C# which has just acquired a fully MIT Licensed open s=
ource implementation. The tools can be used as standalone command line tool=
s or as integrated Visual Studio components. I use Visual Studio for my bui=
ld environment on every platform, Linux and OSX included. There is a tool t=
hat will convert Visual Studio projects to Gnu Makefiles. The only serious =
limitation being that I can&#39;t run unit tests on platforms other than Wi=
ndows at the moment.</div><div class=3D"gmail_default"><br></div><div class=
=3D"gmail_default">OK so what tools?</div><div class=3D"gmail_default"><br>=
</div><div class=3D"gmail_default">First, I have my own RFC documentation t=
ool that can take source from MarkDown, Word, XML2RFC or HTML. It does not =
yet support the new format but will in the near future.=C2=A0</div><div cla=
ss=3D"gmail_default"><br></div><div class=3D"gmail_default">Second, I have =
a protocol compiler that allows a protocol to be defined in a very high lev=
el schema from which the reference sections of the specification, examples,=
 reference and production code are generated.</div><div class=3D"gmail_defa=
ult"><br></div><div class=3D"gmail_default">My approach is at a higher leve=
l of abstraction to YANG. I believe that the process of designing a standar=
d is to remove choices that don&#39;t matter. There are hundreds of ways th=
at an integer value can be encoded and DNS uses at least 6 different forms.=
 If you are designing a protocol you should choose one and stick to it. I d=
on&#39;t currently deal in YANG but if I had to, YANG would be an output fr=
om my tools.</div><div class=3D"gmail_default"><br></div><div class=3D"gmai=
l_default">The same libraries also include an ASN.1 encoder (and partial de=
coder), JSON, RFC822 and DNS serialization/deserialization tools.</div><div=
 class=3D"gmail_default"><br></div><div class=3D"gmail_default">The tool bu=
ilding tool is also included.</div></div>

--94eb2c0763923c632005481d05dd--


From nobody Thu Feb  9 13:09:36 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741F5126D74; Thu,  9 Feb 2017 13:09:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.851
X-Spam-Level: 
X-Spam-Status: No, score=-0.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 e3-kY8sjw7ym; Thu,  9 Feb 2017 13:09: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 060471295BF; Thu,  9 Feb 2017 13:09:32 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 05B9B80F4F; Thu,  9 Feb 2017 22:09:24 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, "otroan@employees.org" <otroan@employees.org>, Joe Touch <touch@isi.edu>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com>
Date: Wed, 8 Feb 2017 19:35:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lVwBBKOpXcYkB57DUnM5u19Hgi8>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 21:09:33 -0000

Hi, Fred,

On 02/08/2017 01:35 PM, Templin, Fred L wrote:
>>>
>>> Also not to be lost in this discussion is the potential for spoofed ICMP messages
>>> that would report a size that is either too large or too small.
>>
>> RFC5927 is all about this.
> 
> Right. The point is that these data points would seem to indicate that standard
> PMTUD per rfc1981bis is not reliable nor secure enough for operation on open
> internetworks such as the global public Internet. Maybe the security section
> should say that?

PMTUD as per rfc1981bis is certainly not reliable, since ICMPv6 messages
are not reliable (actually, ICMP itself is obviously unreliable, but the
widespread filtering of ICMPv6 messages results in more deterministic
failures)

"security"-wise, you can improve things to a decent level. e.g., for TCP
based traffic all IPv6 implentations check the TCP sequence number (and
por numbers) in the embedded packet.

Besides, if you look at RFC5927, there a PMTUD-specific mitigation which
essentially means that during the life of a connection, upon receipt of
an ICMP PTB, you save the message, but only honor the message if there's
not progress on the connection. -- somehow mimicking RFC4821.

So I'd say that the issue with PMTUD is mostly reliability than security.

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  9 13:15:26 2017
Return-Path: <denis.ietf@free.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A8A2129484; Thu,  9 Feb 2017 13:15:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.617
X-Spam-Level: 
X-Spam-Status: No, score=-2.617 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 E386ZIYNrCB2; Thu,  9 Feb 2017 13:15:19 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (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 0B109126D74; Thu,  9 Feb 2017 13:15:19 -0800 (PST)
Received: from [192.168.0.13] (unknown [88.182.125.39]) by smtp6-g21.free.fr (Postfix) with ESMTP id 07567780310; Thu,  9 Feb 2017 22:15:14 +0100 (CET)
Subject: Re: [OAUTH-WG] Last Call: <draft-ietf-oauth-jwsreq-11.txt> (The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)) to Proposed Standard
To: Nat Sakimura <sakimura@gmail.com>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
References: <148581788158.29828.4591033587037530374.idtracker@ietfa.amsl.com> <3a6b8cee-ff29-323e-9042-5df6e71a8d81@free.fr> <CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com>
From: Denis <denis.ietf@free.fr>
Message-ID: <81f50f3f-2f04-c74a-d47a-dad8cd9f715a@free.fr>
Date: Thu, 9 Feb 2017 22:15:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------69CBEBA95C3BE4C4C2BE2340"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f_-C8EhwnneXZwzovGBILZmK-Ww>
Cc: draft-ietf-oauth-jwsreq@ietf.org, oauth-chairs@ietf.org, oauth@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 21:15:25 -0000

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

Hi Nat,

My replies to your proposed disposition of comments are embedded in the 
text.

> Thanks Denis. Here is my proposed disposition on your comments.
>
> On Fri, Feb 3, 2017 at 8:11 PM Denis <denis.ietf@free.fr 
> <mailto:denis.ietf@free.fr>> wrote:
>
>     *Comments on I-D Action: draft-ietf-oauth-jwsreq-11.txt*
>
>      Two editorial comments first :
>
>      1. Guidance is a mass noun, not a count noun, plural doesn't make
>     sense.
>     Please change "guidances" into "guidance" twice in Section 11.
>
> Accepted.
> Thanks.
>
>      2. In Section 12 : Please remove my name (Denis Pinkas) from this
>     section.
>
> Accepted.
>
>      Other comments:
>
>     3. Section 1.1 (from boiler plate) states: The key words "MUST",
>     "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
>     "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>     document are to be interpreted as described in RFC 2119 [RFC2119].
>
>     There is not a single other occurrence of the word SHALL within
>     this document. In such case, I wonder how this document can be
>     normative.
>     There are however many (useful) "non-normative examples. A
>     non-normative example does not replace requirements.
>
> Noted.
> There are bunch of MUST. At IETF we usually prefer MUST to SHALL, 
> unlike in ISO.
OK.
>
>      Section 4 states:
>
>     *A Request Object (Section 2.1) is used to provide authorization
>     request parameters for an OAuth 2.0 authorization request.It
>     contains OAuth 2.0 [RFC6749] authorization request parameters
>     including extension parameters**.*
>
>     RFC 6749 contains 75 pages, but does not contain a single
>     occurrence of the wording "authorization request parameter" nor of
>     "extension parameter".
>     There should be either references to one or more specific sections
>     of this document or, even better, a list of the
>     mandatory/recommended/possible
>     authorization request parameters as well as a list of
>     mandatory/recommended/possible extension parameters should be
>     included in this document.
>
>     A clear distinction should be made between the parameters used to
>     authenticate the request and the other ones.
>
>
> Reject.
> There are 4 flows in RFC6749. In each flow, there is a sub-section 
> dedicated to the Authorization request.
> In them, the parameters used in the authorization request are very 
> clearly indicated. For example,
>
>
>         4.1.1 <https://tools.ietf.org/html/rfc6749#section-4.1.1>.
>         Authorization Request
>
>
>
>     The client constructs the request URI by adding the following
>     parameters to the query component of the authorization endpoint URI ...
> It is very difficult to miss.
>
> Then, the possibility for the extension parameters are discussed in 
> 8.2. Needless to say, those extension parameters are going to be 
> discussed in other specifications.
> Thus, it would be misleading just to say the parameters defined in 
> 4.1.1, 4.2.1, etc.
> As an editor, I feel better with the current language because it is at 
> least not wrong nor misleading.

draft-ietf-oauth-jwsreq-11states on page 7.

To sign, JSON Web Signature (JWS) [RFC7515] is used.The result is a

JWS signed JWT [RFC7519].If signed, the Authorization Request

Object SHOULD contain the Claims "iss" (issuer) and "aud" (audience)

as members, with their semantics being the same as defined in the JWT

[RFC7519] specification.

This should be changed into:

To sign, JSON Web Signature (JWS) [RFC7515] is used.The result is a

JWS signed JWT [RFC7519].If signed, the Authorization Request

Object *MUST contain a client_id parameter* and SHOULD contain a
"iss" (issuer) *parameter* and an "aud" (audience) *parameter*, with
their semantics being the same as defined in the JWT RFC7519]
specification.

In section 5.2. Message Signature or MAC Validation, the text states:

When validating a JWS, the following steps are performed.

(...)

See Section 10.6 for security considerations on algorithm

validation.

There is no section 10.6 in this document. It seems to be section 10.3

Anyway, it is not the right place to place requirements in a security 
considerations section and the appropriate text
should be moved in the main body of the document.

RFC 6749 states in clause 4.Obtaining Authorization on page

6.2.JWS Signed Request Object

To perform JWS Signature Validation, the "alg" Header Parameter in

the JOSE Header MUST match the value of the pre-registered algorithm.

The signature MUST be validated against the appropriate key for that

"client_id" and algorithm.

The important point is to provide guidance on how to map the 
client_idparameter with the appropriate key.
There is none at the present time.

Add:

Identifying the appropriate key MUST be done according to section 6
of RFC 7515 and using the Registered Header Parameter Names defined
in section 4.1 of RFC 7515, e.g. using the Header Parameters "jku",
"jwk", "kid", "x5u", "x5c", "x5t", or "x5t#S256".


> 4. The introduction states on page 4:
>
>          (a) (integrity protection) The request can be signed so that
>     the integrity of the request can be checked;
>
>     This should be changed into:
>
>          (a) (integrity protection) The request can be authenticated
>     either using a digital signature or using encryption under a
>     secret key
>               so that the integrity of the request can be checked;
>
>
> Reject.
> This paragraph is talking about the integrity protection and not the 
> source authentication.
> And even for source authentication, saying that encryption under a 
> secret key is not accurate as it was discussed earlier in the WG mail.
>
> I am not sure if "Introduction" needs to state everything that is 
> explained later. The idea of introduction probably is to give main 
> points. The list is not an exhaustive list of the benefit of using JWT 
> as the authorization request format. For example, being able to 
> encrypt the request, which is not listed there, has an advantage of 
> preventing MITB to eavesdrop the request. So I think it is ok as is.
>
Integrity protection cannot be verified without knowing the source of 
the information. Using encryption (which supports at the same time
an integrity service when secret keys are being used) is another way to 
be able to check the integrity of the request.

So I maintain may comment.


> 5. The introduction states on page 4:
>
>     (d) (collection minimization) The request can be *signed* by a
>     third party attesting that the authorization request is compliant
>     tocertain policy.
>
>     The request is not /signed/ by a third party.
>
>     However, later on, there is the following explanation:
>
>     In addition, it allows requests to be prepared by a third party so
>     that a client application cannot request
>        more permissions than previously agreed.
>
>      If it is the intent, the sentence should be rephrased as:
>
>     (d) (collection minimization) The request can be *verified* by a
>     third party attesting that the authorization request is compliant
>     tocertain policy.
>
> Reject
> The third party indeed signs the request on behalf of the client as 
> the result of verification that the permission is the same as 
> previously agreed.

If it were the case, the client_id would indicate the name of the third 
party and the name of the user would be missing (or vice versa).

So I maintain my comment.


>      6. Section 10.1. the text states:
>
>     *When sending the authorization request object through "request"
>     parameter, it MUST either be signed using JWS [RFC7515] or encrypted
>     using JWE [RFC7516] with then considered appropriate algorithm.*
>
>      The wording"with then considered appropriate algorithm"is too
>     vague. This should be changed into:
>
>     *When sending the authorization request object through "request"
>     parameter, it MUST either be signed using JWS [RFC7515] or encrypted
>     using JWE [RFC7516] using a symmetric key algorithm.*
>
>     Reject.
>
> In the above sentence, "*with then considered appropriate algorithm*" 
>  applies both on JWS and JWE.
> The intent of the phrase is that a vulnerable algorithm should not be 
> used.
>
> Also, I do not understand why the algorithm has to be symmetric key 
> algorithm.

Maybe, this explains why you didn't understand the previous comment. 
With public key encryption, it is not possible to authenticate
the source of the request, while it is possible with secret key 
encryption when the encrypted data includes a cryptographic checksum
like a hash value and an error propagation method for the encryption 
algorithm.

So I maintain my comment.


>      7. Section 10.2 states:
>
>     This means that the request object is going to be prepared fresh each
>     time an authorization request is madeand caching cannot be used.
>
>      What are the implications ? Is it required/recommended to use a
>     nonce ? The text should be made clearer.
>
> Reject.
> The implication is given right after the sentence. There is no 
> variable called "nonce" in RFC6749. Since this document is just defining
> another encoding method for OAuth 2.0 authorization request as a 
> framework, it does not mandate these.
> An extension specification should define those requirements.

Note that this section belongs to the security considerations section 
which SHOULD NOT be normative and should only provide guidance.

The sentence right after is the following:

It has a performance disadvantage, but where such disadvantage is

permissible, it should be considered.

It does not provide any guidance.

The key point is that a parameter able to detect replay needs to be 
included in the request. This should be indicated in the normative part.
It is unfortunate that RFC 7515 has not addressed replay protection of 
JWS and only mentions the problem is section 10.10 which is in the
security considerations section. Here it is:

10.10.Replay Protection

While not directly in scope for this specification, note that

applications using JWS (or JWE) objects can thwart replay attacks by

including a unique message identifier as integrity-protected content

in the JWS (or JWE) message and having the recipient verify that the

message has not been previously received or acted upon.

The text on page 7 should be changed into:

To sign, JSON Web Signature (JWS) [RFC7515] is used.The result is a
JWS signed JWT [RFC7519].If signed, the Authorization Request
Object *MUST contain a client_id parameter* *and a "nonce"* *extension
**parameter* *allowing to detect replay attacks *and SHOULD contain an 
"iss"
(issuer) *parameter* and an "aud" (audience) *parameter*, with their
semantics being the same as defined in the JWT specification[RFC7519].

Note that Page 7 uses the "nonce" parameter in the example.


    JSON Web Token Claims are listed at:
    https://www.iana.org/assignments/jwt/jwt.xhtml

"Nonce" is mentioned in OpenID Connect Core 1.0 incorporating errata set 1.

It is described as :

nonce

	

Value used to associate a Client session with an ID Token


This is too restrictive since now a nonce should be included in a JWS token.

The registration is as follows:

  * Parameter name: nonce
  * Parameter usage location: Authorization Request
  * Change controller: OpenID Foundation Artifact Binding Working Group
    - openid-specs-ab@lists.openid.net
  * Specification document(s): Section 3.1.2
    <http://openid.net/specs/openid-connect-core-1_0.html#AuthorizationEndpoint>of
    this document
  * Related information: None


Section 3.1.2 states:


      3.1.2. Authorization Endpoint

The Authorization Endpoint performs Authentication of the End-User. This 
is done by sending the User Agent to the Authorization Server's
Authorization Endpoint for Authentication and Authorization, using 
request parameters defined by OAuth 2.0 and additional parameters
and parameter values defined by OpenID Connect.

Communication with the Authorization Endpoint MUST utilize TLS. See 
Section 16.17 
<http://openid.net/specs/openid-connect-core-1_0.html#TLSRequirements>for 
more information on using TLS

This has nothing to do with the nonce. Hence the nonce registration 
information has been badly defined.

The OpenID specification also states:


"The Client SHOULD check the noncevalue for replay attacks. The precise 
method for detecting replay attacks is Client specific".

This does not allow to interoperate.

Rather than correcting the registration information in the OpenID 
specification, it would be better to suppress it from the OpenID 
specification
and incorporate it within an IETF RFC.

In order to avoid nonces to be kept in a memory for ever, a good 
practice is to split the nonce in two parts:

  * one of them includes a UTC NumericDate using the format defined in
    RFC 7519,and
  * the other one includes a random number.


In this way only recent nonces (e.g. received during the last 5 minutes) 
need to be kept in memory.
Three or fourbytes for the random number will be sufficient.

In order to *allow for interoperability,* a format should be specified.


I propose a NumericDate defining the UTC time concatenated with a random 
number with three bytes.

"Nonce" has not been officially registered by IANA. An IANA 
Considerations section should be added in draft-ietf-oauth-jwsreq-*
*to register the "nonce" parameter.

On page 14, section 6.2., after the previous proposed text which is:

Identifying the appropriate key MUST be done according to section 6
of RFC 7515 and using the Registered Header Parameter Names defined
in section 4.1 of RFC 7515, e.g. using the Header Parameters "jku",
"jwk", "kid", "x5u", "x5c", "x5t", or "x5t#S256".

I proposed to add the following text:

To perform JWS Signature Validation, the "nonce" Header Parameter in

the JOSE Header MUST be present and MUST be checked to verify that
the signed request is not the replay of a previous signed request.

A section defining the nonce parameter should be added.

>      8. Section 10.3 states:
>
>     10.3.Request Source Authentication
>
>     The source of the Authorization Request MUST always be verified.
>
>     There are several ways to do it in this specification.
>
>     (a)Verifying the JWS Signature of the Request Object.
>
>      It seems that the case of using a JWE encrypted using a secret
>     key algorithm has been forgotten here. Please add it.
>
> Accepted with modification.
> You mean, symmetric key algorithm, is that right? I would add "or 
> verifying that the symmetric key for theJWE encryption is a correct one"

Accepted

>      9. Section 10.3 states at its very end:
>
>     An extension specification
>     should be created as a preventive measure to address potential
>     vulnerabilities that have not yet been identified.
>
>
>     Writing a document for vulnerabilities that have not yet been
>     identified is speculative. It would rather be better
>     either to remove this sentence or to explain what is meant by it.
>
> Reject.
> It is referring to the first paragraph of the sub-section. Also, 
> precaution when security is in question is a good thing.

This sentence is simply useless and thus should be deleted. Hence, I 
maintain this comment.



>     10. Section 11.1 states:
>
>     *11.1.Collection limitation*
>
>     *When the Client is being granted access to a protected resource
>     containing personal data, the Client SHOULD limit the collection of
>     personal data to that which is within the bounds of applicable law
>     and strictly necessary for the specified purpose(s).***
>
>      The /presentation/ of personal data should be limited whether or
>     not the protected resource contains personal data.
>
>     It is proposed to change this text into:
>
>     *When the Client requests an access to a protected resource, the
>     Client
>     SHOULD limit the presentation of personal data to that which is within
>     the bounds of applicable law and strictly necessary for the specified
>     purpose(s).*
>
> Reject.
> You are not getting what OAuth does. The party that holds personal 
> data is the authorization server / resource.
> It is not the client. The client is the party who is getting those 
> "resources" which may contain personal data.
> Yes, the client can provide some personal data to the resource 
> depending on what that resource endpoint is, but that is out of scope 
> for OAuth.
> As far as OAuth is concerned, what is being sent from the client to 
> the resource is the access token.

The dispute is whether the protected resource contains or not personal 
data.
The data contained by the protected resource may well be public data 
(or/and personal data).
It does not need to be only "personal data".

Hence, I maintain my comment.



>     **
>
>      11. Section 11.2.1 states:
>
>     11.2.1.Request Disclosure
>
>     This specification allows extension parameters.
>
>      It would be useful to name either all of them or some of them.
>     RFC 6749 is not crystal clear about this.
>
> Noted.
> RFC6749 only defines how to define extension parameters.
> This specification draws from OpenID Connect for some examples of 
> extension parameters such as nonce.
> See section 4 for example.


See my earlier comments where client_id and nonce shall be mandatory.


Denis
>
>      Denis Pinkas (DP Security Consulting SAS)
>
>     ==============================================================
>
>>     The IESG has received a request from the Web Authorization Protocol WG
>>     (oauth) to consider the following document:
>>     - 'The OAuth 2.0 Authorization Framework: JWT Secured Authorization
>>         Request (JAR)'
>>        <draft-ietf-oauth-jwsreq-11.txt> as Proposed Standard
>>
>>     The IESG plans to make a decision in the next few weeks, and solicits
>>     final comments on this action. Please send substantive comments to the
>>     ietf@ietf.org <mailto:ietf@ietf.org>  mailing lists by 2017-02-13. Exceptionally, comments may be
>>     sent toiesg@ietf.org <mailto:iesg@ietf.org>  instead. In either case, please retain the
>>     beginning of the Subject line to allow automated sorting.
>>
>>     Abstract
>>
>>
>>         The authorization request in OAuth 2.0 described in RFC 6749 utilizes
>>         query parameter serialization, which means that Authorization Request
>>         parameters are encoded in the URI of the request and sent through
>>         user agents such as web browsers.  While it is easy to implement, it
>>         means that (a) the communication through the user agents are not
>>         integrity protected and thus the parameters can be tainted, and (b)
>>         the source of the communication is not authenticated.  Because of
>>         these weaknesses, several attacks to the protocol have now been put
>>         forward.
>>
>>         This document introduces the ability to send request parameters in a
>>         JSON Web Token (JWT) instead, which allows the request to be JWS
>>         signed and/or JWE encrypted so that the integrity, source
>>         authentication and confidentiality property of the Authorization
>>         Request is attained.  The request can be sent by value or by
>>         reference.
>>
>>
>>
>>
>>     The file can be obtained via
>>     https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/
>>
>>     IESG discussion can be tracked via
>>     https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/
>>
>>
>>     No IPR declarations have been submitted directly on this I-D.
>>
>>
>>     The document contains these normative downward references.
>>     See RFC 3967 for additional information:
>>          rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (Informational - IETF stream)
>>          rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informational - IETF stream)
>>          rfc6973: Privacy Considerations for Internet Protocols (Informational - IAB stream)
>>     Note that some of these references may already be listed in the acceptable Downref Registry.
>>
>>
>>     _______________________________________________
>>     OAuth mailing list
>>     OAuth@ietf.org <mailto:OAuth@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/oauth
>
>
>     _______________________________________________
>     OAuth mailing list
>     OAuth@ietf.org <mailto:OAuth@ietf.org>
>     https://www.ietf.org/mailman/listinfo/oauth
>
> -- 
>
> Nat Sakimura
>
> Chairman of the Board, OpenID Foundation
>


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Nat,<br>
      <br>
      My replies to your proposed disposition of comments are embedded
      in the text.<br>
      <br>
    </div>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">Thanks Denis. Here is my proposed disposition on
        your comments. <br>
        <br>
        <div class="gmail_quote">
          <div dir="ltr">On Fri, Feb 3, 2017 at 8:11 PM Denis &lt;<a
              moz-do-not-send="true" href="mailto:denis.ietf@free.fr">denis.ietf@free.fr</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"><b class="gmail_msg">Comments on I-D
                      Action: draft-ietf-oauth-jwsreq-11.txt</b></span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> Two editorial comments first :</span></p>
                <p class="MsoNormal gmail_msg"><span class="gmail_msg"
                    lang="EN-US"> 1. </span><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">Guidance is a mass noun, not a count
                    noun, plural doesn't make sense. <br>
                    Please change "guidances" into "guidance" twice in
                    Section 11.</span></p>
              </div>
            </div>
          </blockquote>
          <div>Accepted. </div>
          <div>Thanks. </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"></span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> 2. In Section 12 : Please remove my
                    name (Denis Pinkas) from this section.</span></p>
              </div>
            </div>
          </blockquote>
          <div>Accepted.  </div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> Other comments:</span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    style="font-size:12.0pt;font-family:Arial"
                    class="gmail_msg" lang="EN-US">3. Section 1.1 (from
                    boiler plate) states: </span><span
                    class="gmail_msg" lang="EN-GB">The key words "MUST",
                    "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
                    "SHOULD", <br class="gmail_msg">
                    "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
                    in this document are to be interpreted as described
                    in RFC 2119 [RFC2119].</span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB">There is not a single other occurrence
                    of the word SHALL within this document. In such
                    case, I wonder how this document can be normative. <br
                      class="gmail_msg">
                    There are however many (useful) "</span><span
                    class="gmail_msg" lang="EN-GB">non-normative
                    examples. A non-normative example does not replace
                    requirements.</span></p>
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB"></span></p>
              </div>
            </div>
          </blockquote>
          <div>Noted. </div>
          <div>There are bunch of MUST. At IETF we usually prefer MUST
            to SHALL, unlike in ISO.<br>
          </div>
        </div>
      </div>
    </blockquote>
    OK.<br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB"> Section 4 states:</span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB"> </span><b class="gmail_msg"><span
                      class="gmail_msg" lang="EN-GB"><span
                        class="gmail_msg">   </span>A Request Object
                      (Section 2.1) is used to provide authorization<br>
                      <span class="gmail_msg">   </span>request
                      parameters for an OAuth 2.0 authorization request.<span
                        class="gmail_msg">  </span><span
                        class="gmail_msg">It<br>
                           </span>contains OAuth 2.0 [RFC6749]
                      authorization request parameters<br>
                      <span class="gmail_msg">   </span>including
                      extension parameters</span></b><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB">.<span class="gmail_msg">  </span></span></b></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB">RFC 6749 contains 75 pages, but does
                    not contain a single occurrence of the wording
                    "authorization request parameter" nor of "extension
                    parameter". <br class="gmail_msg">
                    There should be either references to one or more
                    specific sections of this document or, even better,
                    a list of the mandatory/recommended/possible <br
                      class="gmail_msg">
                    authorization request parameters as well as a list
                    of mandatory/recommended/possible extension
                    parameters should be included in this document.</span></p>
                <p class="MsoNormal gmail_msg"><font class="gmail_msg"
                    face="Arial">A clear distinction should be made
                    between the parameters used to authenticate the
                    request and the other ones.</font></p>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Reject. </div>
          <div>There are 4 flows in RFC6749. In each flow, there is a
            sub-section dedicated to the Authorization request. </div>
          <div>In them, the parameters used in the authorization request
            are very clearly indicated. For example, </div>
          <div><br>
          </div>
          <div>
            <pre class="inbox-inbox-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px"><span class="inbox-inbox-h4" style="line-height:0pt;display:inline;font-size:1em;font-weight:bold"><h4 style="line-height:0pt;display:inline;font-size:1em"><a moz-do-not-send="true" class="inbox-inbox-selflink" href="https://tools.ietf.org/html/rfc6749#section-4.1.1" style="color:black;text-decoration:none">4.1.1</a>.  Authorization Request</h4></span>

   The client constructs the request URI by adding the following
   parameters to the query component of the authorization endpoint URI ... </pre>
            <pre class="inbox-inbox-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px">
</pre>
            It is very difficult to miss. </div>
          <div><br>
          </div>
          <div>Then, the possibility for the extension parameters are
            discussed in 8.2. Needless to say, those extension
            parameters are going to be discussed in other
            specifications. </div>
          <div>Thus, it would be misleading just to say the parameters
            defined in 4.1.1, 4.2.1, etc. </div>
          <div>As an editor, I feel better with the current language
            because it is at least not wrong nor misleading. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span style="font-family:&quot;Courier
        New&quot;;
        mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">draft-ietf-oauth-jwsreq-11</span><span
        style="mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><font
          face="Arial">
          states on page 7</font>.<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>To sign, JSON Web
        Signature (JWS) [RFC7515]
        is used.<span style="mso-spacerun: yes">  </span>The result is
        a<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>JWS signed JWT [RFC7519].<span
          style="mso-spacerun: yes">  </span>If signed, the
        Authorization Request<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>Object SHOULD contain the
        Claims
        "iss" (issuer) and "aud" (audience)<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>as members, with their
        semantics being the
        same as defined in the JWT<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>[RFC7519] specification.<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;font-family:Arial;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:
        EN-GB" lang="EN-GB">This should be changed into:<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>To sign, JSON Web
        Signature (JWS) [RFC7515]
        is used.<span style="mso-spacerun: yes">  </span>The result is
        a<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>JWS signed JWT [RFC7519].<span
          style="mso-spacerun: yes">  </span>If signed, the
        Authorization Request<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>Object <b>MUST contain a
          client_id
          parameter</b> and SHOULD contain a<br>
        <span style="mso-spacerun: yes">   </span>"iss" (issuer) <b>parameter</b>
        and an "aud" (audience) <b>parameter</b>, with <br>
        <span style="mso-spacerun: yes">   </span>their semantics being
        the same as
        defined in the JWT RFC7519] <br>
        <span style="mso-spacerun: yes">   </span>specification.<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">In section
          5.2. Message Signature or MAC Validation, the text states:<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">   </span>When validating a JWS,
          the following steps
          are performed.<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">(...)<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">       </span>See Section 10.6
          for security
          considerations on algorithm<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><span
            style="mso-spacerun: yes">       </span>validation.<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">There is no
          section 10.6 in this document. It seems to be section 10.3<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">Anyway, it
          is not the right place to place requirements in a security
          considerations
          section and the appropriate text <br>
          should be moved in the main body of the
          document.<o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><font face="Arial">RFC 6749
          states in clause 4.<span style="mso-spacerun: yes">  </span>Obtaining
          Authorization on page </font><o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">6.2.<span
          style="mso-spacerun: yes">  </span>JWS Signed Request Object<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>To perform JWS Signature
        Validation, the
        "alg" Header Parameter in<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>the JOSE Header <span
          style="background:
          lime;mso-highlight:lime">MUST</span> match the value of the
        pre-registered
        algorithm.<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span><span
          style="background:aqua;mso-highlight:
          aqua">The signature MUST be validated against the appropriate
          key for that<o:p></o:p></span></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;background:aqua;mso-highlight:aqua;
        mso-ansi-language:EN-GB" lang="EN-GB"><span style="mso-spacerun:
          yes">  
        </span>"client_id" and algorithm.</span><span
style="font-size:12.0pt;mso-bidi-font-size:10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;
        mso-ansi-language:EN-GB" lang="EN-GB"><o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">The
          important point is to provide guidance on how to map the </span>client_id<span
          style="mso-fareast-font-family:
          &quot;MS Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">
          parameter with the appropriate key. <br>
          There
          is none at the present time.</span><span
          style="mso-ansi-language:
          EN-GB" lang="EN-GB"><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></font></p>
    <font face="Arial">
    </font>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><font face="Arial">Add:</font><o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>Identifying
        the appropriate
        key MUST be done according to section 6 <br>
        <span style="mso-spacerun: yes">   </span>of RFC 7515 and using
        the Registered
        Header Parameter Names defined <br>
        <span style="mso-spacerun: yes">   </span>in section 4.1 of RFC
        7515, e.g.
        using the Header Parameters "jku", <br>
        <span style="mso-spacerun: yes">   </span>"jwk", "kid",
        "x5u", "x5c", "x5t", or "x5t#S256".<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <meta name="ProgId" content="Word.Document">
    <meta name="Generator" content="Microsoft Word 9">
    <meta name="Originator" content="Microsoft Word 9">
    <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/07/clip_filelist.xml">
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
    <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:3 0 0 0 1 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-alt:"‚l‚r –¾’©";
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h2
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:2;
	font-size:18.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h3
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:3;
	font-size:13.5pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h4
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:4;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
	font-size:10.0pt;
	font-family:"Arial Unicode MS";}
tt
	{mso-ascii-font-family:"Arial Unicode MS";
	mso-fareast-font-family:"Arial Unicode MS";
	mso-hansi-font-family:"Arial Unicode MS";
	mso-bidi-font-family:"Arial Unicode MS";}
p.msonormalgmailmsg, li.msonormalgmailmsg, div.msonormalgmailmsg
	{mso-style-name:"msonormal gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.gmailmsg
	{mso-style-name:gmail_msg;}
p.m5262665161593131067msoplaintextgmailmsg, li.m5262665161593131067msoplaintextgmailmsg, div.m5262665161593131067msoplaintextgmailmsg
	{mso-style-name:"m_5262665161593131067msoplaintext gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.inbox-inbox-h4
	{mso-style-name:inbox-inbox-h4;}
span.m5262665161593131067deletegmailmsg
	{mso-style-name:"m_5262665161593131067delete gmail_msg";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:628128861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1263504596 -40343276 -1933258530 1875814492 1946289654 -395266484 -184810804 -1973797926 1742909670 -568795924;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div> <span style="font-family:Arial" class="gmail_msg"
              lang="EN-GB"></span><span style="font-family:Arial"
              class="gmail_msg" lang="EN-GB">4. The introduction states
              on page 4:</span></div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg" style="margin-top:6.0pt"><span
                    style="font-family:Arial" class="gmail_msg"> </span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">     (a) (integrity protection) The
                    request can be signed so that the integrity of the
                    request can be checked<span
                      class="m_5262665161593131067delete gmail_msg"> </span>;
                  </span><span class="gmail_msg" lang="EN-US"></span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">This should be changed into:</span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US"> </span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">     (a) (integrity protection) The
                    request can be authenticated either using a digital
                    signature or using encryption under a secret key <br
                      class="gmail_msg">
                              so that the integrity of the request can
                    be checked<span class="m_5262665161593131067delete
                      gmail_msg"> </span>;</span></p>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Reject. </div>
          <div>
            <div>This paragraph is talking about the integrity
              protection and not the source authentication. </div>
            <div>And even for source authentication, saying that
              encryption under a secret key is not accurate as it was
              discussed earlier in the WG mail. </div>
          </div>
          <div><br>
          </div>
          <div>I am not sure if "Introduction" needs to state everything
            that is explained later. The idea of introduction probably
            is to give main points. The list is not an exhaustive list
            of the benefit of using JWT as the authorization request
            format. For example, being able to encrypt the request,
            which is not listed there, has an advantage of preventing
            MITB to eavesdrop the request. So I think it is ok as is. </div>
          <div><br>
          </div>
        </div>
      </div>
    </blockquote>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US">Integrity protection cannot be verified
        without knowing the source of
        the information. Using encryption (which supports at the same
        time <br>
        an integrity
        service when secret keys are being used) is another way to be
        able to check the
        integrity of the request. <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US">So I maintain may comment.</span></p>
    <p class="MsoNormal"><br>
      <span style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US"><o:p></o:p></span></p>
    <meta name="ProgId" content="Word.Document">
    <meta name="Generator" content="Microsoft Word 9">
    <meta name="Originator" content="Microsoft Word 9">
    <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/07/clip_filelist.xml">
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
    <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h2
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:2;
	font-size:18.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h3
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:3;
	font-size:13.5pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h4
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:4;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
	font-size:10.0pt;
	font-family:"Arial Unicode MS";}
tt
	{mso-ascii-font-family:"Arial Unicode MS";
	mso-fareast-font-family:"Arial Unicode MS";
	mso-hansi-font-family:"Arial Unicode MS";
	mso-bidi-font-family:"Arial Unicode MS";}
p.msonormalgmailmsg, li.msonormalgmailmsg, div.msonormalgmailmsg
	{mso-style-name:"msonormal gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.gmailmsg
	{mso-style-name:gmail_msg;}
p.m5262665161593131067msoplaintextgmailmsg, li.m5262665161593131067msoplaintextgmailmsg, div.m5262665161593131067msoplaintextgmailmsg
	{mso-style-name:"m_5262665161593131067msoplaintext gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.inbox-inbox-h4
	{mso-style-name:inbox-inbox-h4;}
span.m5262665161593131067deletegmailmsg
	{mso-style-name:"m_5262665161593131067delete gmail_msg";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:628128861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1263504596 -40343276 -1933258530 1875814492 1946289654 -395266484 -184810804 -1973797926 1742909670 -568795924;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <div> <span style="font-family:Arial" class="gmail_msg"
              lang="EN-GB">5. The introduction states on page 4:</span></div>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-GB"> </span></p>
                <p class="MsoNormal gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">(d) (collection minimization) The
                    request can be <b class="gmail_msg">signed</b> by a
                    third party attesting that the authorization request
                    is compliant <span
                      class="m_5262665161593131067delete gmail_msg">to</span></span><span
                    class="gmail_msg" lang="EN-US"> </span><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">certain policy.</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    style="font-size:12.0pt;font-family:Arial"
                    class="gmail_msg" lang="EN-US">The request is not <i
                      class="gmail_msg">signed</i> by a third party. <br
                      class="gmail_msg">
                  </span></p>
              </div>
            </div>
          </blockquote>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US">However, later on,
                    there is the following explanation: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"><span
                      class="gmail_msg">   </span>In addition, it
                    allows requests to be prepared by a third party so
                    that a client application cannot request <br
                      class="gmail_msg">
                       more permissions than <span class="gmail_msg">pr</span>eviously
                    agreed.<span class="gmail_msg">  </span></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Arial;color:#222222"
                    class="gmail_msg" lang="EN-US"> If it is the intent,
                    the sentence should be rephrased as: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    style="font-family:Arial" class="gmail_msg"
                    lang="EN-US">(d) (collection minimization) The
                    request can be <b class="gmail_msg">verified</b> by
                    a third party attesting that the authorization
                    request is compliant <span
                      class="m_5262665161593131067delete gmail_msg">to</span></span><span
                    class="gmail_msg" lang="EN-US"> </span><span
                    style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US">certain policy. <br>
                  </span></p>
              </div>
            </div>
          </blockquote>
          <div>Reject</div>
          <div>The third party indeed signs the request on behalf of the
            client as the result of verification that the permission is
            the same as previously agreed.  <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US">If it were the case, the client_id would
        indicate the name of the third
        party and the name of the user would be missing (or vice versa).<o:p></o:p></span></p>
    <p class="MsoNormal" style="tab-stops:69.3pt"><span
        style="font-family:
        Arial;mso-ansi-language:EN-US" lang="EN-US"><span
          style="mso-tab-count:1">                       </span><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-US" lang="EN-US">So I maintain my comment.</span><br>
    </p>
    <br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"> 6. Section 10.1. the
                    text states: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB"><span class="gmail_msg">   </span>When
                      sending the authorization request object through
                      "request"<br>
                      <span class="gmail_msg">   </span>parameter, it
                      MUST either be signed using JWS [RFC7515] or
                      encrypted<br>
                      <span class="gmail_msg">   </span>using JWE
                      [RFC7516] with then considered appropriate
                      algorithm.</span></b></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Arial;color:#222222"
                    class="gmail_msg" lang="EN-GB"> The wording"</span><span
                    class="gmail_msg" lang="EN-GB"> with then considered
                    appropriate algorithm"</span><span
                    style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> is too vague. This
                    should be changed into:</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB"><span class="gmail_msg">   </span>When
                      sending the authorization request object through
                      "request"<br>
                      <span class="gmail_msg">   </span>parameter, it
                      MUST either be signed using JWS [RFC7515] or
                      encrypted<br>
                      <span class="gmail_msg">   </span>using JWE
                      [RFC7516] <span style="color:blue"
                        class="gmail_msg">using a symmetric key
                        algorithm</span>.</span></b></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> </span>Reject. </p>
              </div>
            </div>
          </blockquote>
          <div>In the above sentence, "<b class="gmail_msg"><span
                class="gmail_msg" lang="EN-GB">with then considered
                appropriate algorithm</span></b>"  applies both on JWS
            and JWE. </div>
          <div>The intent of the phrase is that a vulnerable algorithm
            should not be used. </div>
          <div><br>
          </div>
          <div>Also, I do not understand why the algorithm has to be
            symmetric key algorithm. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">Maybe, this explains why you didn't
        understand the previous comment.
        With public key encryption, it is not possible to authenticate <br>
        the source of
        the request, while it is possible with secret key encryption
        when the encrypted
        data includes a cryptographic checksum <br>
        like a hash value and an error
        propagation method for the encryption algorithm.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">So I maintain my comment.</span><br>
    </p>
    <br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> 7. Section 10.2
                    states: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"><span
                      class="gmail_msg">   </span>This means that the
                    request object is going to be <span
                      class="gmail_msg">prepared fresh each<br>
                         </span>time an authorization request is made</span><span
                    class="gmail_msg" lang="EN-GB"> and caching cannot
                    be used.<span class="gmail_msg">  </span></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> What are the
                    implications ? Is it required/recommended to use a
                    nonce ? The text should be made clearer. </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"></span></p>
              </div>
            </div>
          </blockquote>
          <div>Reject. </div>
          <div>The implication is given right after the sentence. There
            is no variable called "nonce" in RFC6749. Since this
            document is just defining <br>
            another encoding method for OAuth 2.0 authorization request
            as a framework, it does not mandate these. <br>
            An extension specification should define those requirements.
            <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">Note that this section belongs to the
        security considerations section
        which SHOULD NOT be normative and should only provide guidance.
        <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">The sentence right after is the following:<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>It has a performance
        disadvantage, but
        where such disadvantage is<o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>permissible, it should be
        considered.<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">It does not provide any guidance. <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">The key point is that a parameter able to
        detect replay needs to be
        included in the request. This should be indicated in the
        normative part. <br>
        It is
        unfortunate that RFC 7515 has not addressed replay protection of
        JWS and only
        mentions the problem is section 10.10 which is in the <br>
        security considerations
        section. Here it is:<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB">10.10.<span style="mso-spacerun: yes">  </span>Replay
        Protection<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>While
        not directly in scope
        for this specification, note that<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>applications
        using JWS (or
        JWE) objects can thwart replay attacks by<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>including
        a unique message
        identifier as integrity-protected content<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>in
        the JWS (or JWE) message
        and having the recipient verify that the<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>message
        has not been
        previously received or acted upon.<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-bidi-font-family:
        &quot;Times New Roman&quot;;mso-ansi-language:EN-GB"
        lang="EN-GB">The text on page 7 should be changed
        into:<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>To sign, JSON Web
        Signature (JWS) [RFC7515]
        is used.<span style="mso-spacerun: yes">  </span>The result is
        a<br>
        <span style="mso-spacerun: yes">   </span>JWS signed JWT
        [RFC7519].<span style="mso-spacerun: yes">  </span>If signed,
        the Authorization Request<br>
        <span style="mso-spacerun: yes">   </span>Object <b>MUST
          contain a client_id
          parameter</b> <b>and a "nonce"</b> <b>extension <br>
        </b><span style="mso-spacerun: yes">   </span><b>parameter</b>
      </span><b><span
          style="font-size:12.0pt;mso-bidi-font-size:10.0pt;font-family:Courier;
          mso-ansi-language:EN-GB" lang="EN-GB">allowing to detect
          replay attacks </span></b><span
style="font-size:12.0pt;mso-bidi-font-size:10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB">and SHOULD
        contain an "iss" <br>
        <span style="mso-spacerun: yes">   </span>(issuer) <b>parameter</b>
        and an
        "aud" (audience) <b>parameter</b>, with their <br>
        <span style="mso-spacerun: yes">   </span>semantics being the
        same as defined
        in the JWT specification[RFC7519].<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="font-family:&quot;Courier
        New&quot;;
        mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-bidi-font-family:
        &quot;Times New Roman&quot;;mso-ansi-language:EN-GB"
        lang="EN-GB">Note that Page 7 uses the
        "nonce" parameter in the example. <o:p></o:p></span></p>
    <h2><span style="font-size:12.0pt;mso-bidi-font-size:18.0pt;
        font-family:Arial;mso-ansi-language:EN-GB;font-weight:normal"
        lang="EN-GB">JSON Web Token
        Claims are listed at: <span style="color:blue"><a class="moz-txt-link-freetext" href="https://www.iana.org/assignments/jwt/jwt.xhtml">https://www.iana.org/assignments/jwt/jwt.xhtml</a></span><o:p></o:p></span></h2>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">"Nonce" is mentioned in OpenID Connect Core
        1.0 incorporating
        errata set 1. <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">It is described as :<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <table style="mso-cellspacing:1.5pt" border="0" cellpadding="0">
      <tbody>
        <tr>
          <td style="padding:.75pt .75pt .75pt .75pt">
            <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
                lang="EN-GB">nonce</span><span
                style="font-family:&quot;Arial Unicode
                MS&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><o:p></o:p></span></p>
          </td>
          <td style="padding:.75pt .75pt .75pt .75pt">
            <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
                lang="EN-GB">Value used to associate a Client session
                with an ID Token</span><span
                style="font-family:&quot;Arial Unicode
                MS&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><o:p></o:p></span></p>
          </td>
        </tr>
      </tbody>
    </table>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><br>
      </span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">This is too restrictive since now a nonce
        should be included in a JWS
        token.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">The registration is as follows:<o:p></o:p></span></p>
    <ul type="disc">
      <li class="MsoNormal"
        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
        mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB">Parameter
          name: </span><tt><span
            style="mso-ansi-font-size:12.0pt;font-family:Arial;mso-bidi-font-family:
            &quot;Arial Unicode MS&quot;;mso-ansi-language:EN-GB"
            lang="EN-GB">nonce</span></tt><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB"> </span><span
          style="font-family:Arial; mso-fareast-font-family:&quot;Arial
          Unicode MS&quot;;mso-bidi-font-family:&quot;Arial Unicode
          MS&quot;; mso-ansi-language:EN-GB" lang="EN-GB"><o:p></o:p></span></li>
      <li class="MsoNormal"
        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
        mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB">Parameter
          usage location: Authorization Request <o:p></o:p></span></li>
      <li class="MsoNormal"
        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
        mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB">Change
          controller: OpenID Foundation Artifact Binding Working Group -
          <a class="moz-txt-link-abbreviated" href="mailto:openid-specs-ab@lists.openid.net">openid-specs-ab@lists.openid.net</a> <o:p></o:p></span></li>
      <li class="MsoNormal"
        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
        mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB">Specification
          document(s): </span><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;"><a
href="http://openid.net/specs/openid-connect-core-1_0.html#AuthorizationEndpoint"><span
              style="mso-ansi-language:EN-GB" lang="EN-GB">Section 3.1.2</span></a></span><span
          style="font-family:Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;; mso-ansi-language:EN-GB" lang="EN-GB"> of this
          document <o:p></o:p></span></li>
      <li class="MsoNormal"
        style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;
        mso-list:l0 level1 lfo1;tab-stops:list 36.0pt"><span
          style="font-family: Arial;mso-bidi-font-family:&quot;Times New
          Roman&quot;">Related information: None <o:p></o:p></span></li>
    </ul>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><br>
      </span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">Section 3.1.2 states:<o:p></o:p></span></p>
    <h3 style="margin-left:36.0pt"><span style="font-size:12.0pt;
mso-bidi-font-size:13.5pt;font-family:Arial;mso-ansi-language:EN-GB"
        lang="EN-GB">3.1.2. 
        Authorization Endpoint<o:p></o:p></span></h3>
    <p
style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">The Authorization Endpoint performs
        Authentication of the End-User. This
        is done by sending the User Agent to the Authorization Server's
        <br>
        Authorization
        Endpoint for Authentication and Authorization, using request
        parameters defined
        by OAuth 2.0 and additional parameters <br>
        and parameter values defined by OpenID
        Connect. <o:p></o:p></span></p>
    <p
style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p
style="margin-top:0cm;margin-right:0cm;margin-bottom:0cm;margin-left:36.0pt;margin-bottom:.0001pt"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">Communication with the Authorization
        Endpoint MUST utilize TLS. See </span><span
        style="font-family:Arial"><a
href="http://openid.net/specs/openid-connect-core-1_0.html#TLSRequirements"><span
            style="mso-ansi-language:EN-GB" lang="EN-GB">Section 16.17</span></a></span><span
        style="font-family:Arial;mso-ansi-language:EN-GB" lang="EN-GB">
        for more
        information on using TLS<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">This has nothing to do with the nonce. Hence
        the nonce registration
        information has been badly defined. <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">The OpenID specification also states:</span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><br>
      </span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"></span><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"> <o:p></o:p></span></p>
    <p class="MsoNormal" style="margin-left:27.0pt"><font face="Arial"><span
          style="mso-ansi-language:EN-GB" lang="EN-GB">"The Client
          SHOULD check the </span>nonce</font><span
        style="mso-ansi-language:
        EN-GB" lang="EN-GB"><font face="Arial"> value for replay
          attacks. The precise method for detecting replay
          attacks is Client specific".</font><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">This does not allow to interoperate.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">Rather than correcting the registration
        information in the OpenID
        specification, it would be better to suppress it from the OpenID
        specification
        <br>
        and incorporate it within an IETF RFC.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">In order to avoid nonces to be kept in a
        memory for ever, a good
        practice is to split the nonce in two parts: <br>
      </span></p>
    <ul>
      <li><span style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB">one of them
          includes a UTC </span><font face="Arial"><span
            style="mso-ansi-language:EN-GB" lang="EN-GB">NumericDate
            using the format defined in RFC 7519,</span></font><span
          style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB"> and </span></li>
      <li><span style="font-family:
          Arial;mso-ansi-language:EN-GB" lang="EN-GB">the other one
          includes a random number. <br>
        </span></li>
    </ul>
    <p class="MsoNormal"><span style="font-family:
        Arial;mso-ansi-language:EN-GB" lang="EN-GB"><br>
        In
        this way only recent nonces (e.g. received during the last 5
        minutes) need to
        be kept in memory. <br>
        Three or four<span style="mso-spacerun: yes"> </span>bytes
        for the random number will be sufficient.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">In order to <b>allow for interoperability,</b>
        a format should be specified.</span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><br>
      </span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">I
        propose a NumericDate defining the UTC time concatenated with a
        random number
        with three bytes.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">"Nonce" has not been officially registered
        by IANA. An IANA
        Considerations section should be added in </span><span
        class="gmailmsg"><span
          style="font-family:Arial;mso-ansi-language:EN-US" lang="EN-US">draft-ietf-oauth-jwsreq-<b>
            <br>
          </b></span></span><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">to register the "nonce" parameter.<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">On page 14, section 6.2., after the previous
        proposed text which is:<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><span style="mso-spacerun: yes">   </span>Identifying
        the appropriate
        key MUST be done according to section 6 <br>
        <span style="mso-spacerun: yes">   </span>of RFC 7515 and using
        the Registered
        Header Parameter Names defined <br>
        <span style="mso-spacerun: yes">   </span>in section 4.1 of RFC
        7515, e.g.
        using the Header Parameters "jku", <br>
        <span style="mso-spacerun: yes">   </span>"jwk", "kid",
        "x5u", "x5c", "x5t", or "x5t#S256".<o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Courier;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB">I proposed to add the following text: <o:p></o:p></span></p>
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <p class="MsoPlainText"><span
        style="font-size:12.0pt;mso-bidi-font-size:
        10.0pt;mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>To perform JWS Signature
        Validation, the
        "nonce" Header Parameter in<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="font-family:&quot;Courier
        New&quot;;
        mso-fareast-font-family:&quot;MS
        Mincho&quot;;mso-ansi-language:EN-GB" lang="EN-GB"><span
          style="mso-spacerun: yes">   </span>the JOSE Header MUST be
        present and MUST be
        checked to verify that <br>
        <span style="mso-spacerun: yes">   </span>the signed request is
        not the replay
        of a previous signed request.<o:p></o:p></span></p>
    <p class="MsoNormal"><span style="mso-ansi-language:EN-GB"
        lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></p>
    <span
      style="font-size:12.0pt;font-family:Arial;mso-fareast-font-family:
      &quot;Times New
Roman&quot;;mso-ansi-language:EN-GB;mso-fareast-language:FR;mso-bidi-language:AR-SA"
      lang="EN-GB">A section defining the nonce parameter should be
      added.<br>
    </span>
    <meta name="ProgId" content="Word.Document">
    <meta name="Generator" content="Microsoft Word 9">
    <meta name="Originator" content="Microsoft Word 9">
    <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/07/clip_filelist.xml">
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
    <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Courier;
	panose-1:0 0 0 0 0 0 0 0 0 0;
	mso-font-charset:0;
	mso-generic-font-family:modern;
	mso-font-format:other;
	mso-font-pitch:fixed;
	mso-font-signature:3 0 0 0 1 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-alt:"‚l‚r –¾’©";
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:"\@MS Mincho";
	panose-1:2 2 6 9 4 2 5 8 3 4;
	mso-font-charset:128;
	mso-generic-font-family:modern;
	mso-font-pitch:fixed;
	mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h2
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:2;
	font-size:18.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h3
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:3;
	font-size:13.5pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h4
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:4;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
	font-size:10.0pt;
	font-family:"Arial Unicode MS";}
tt
	{mso-ascii-font-family:"Arial Unicode MS";
	mso-fareast-font-family:"Arial Unicode MS";
	mso-hansi-font-family:"Arial Unicode MS";
	mso-bidi-font-family:"Arial Unicode MS";}
p.msonormalgmailmsg, li.msonormalgmailmsg, div.msonormalgmailmsg
	{mso-style-name:"msonormal gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.gmailmsg
	{mso-style-name:gmail_msg;}
p.m5262665161593131067msoplaintextgmailmsg, li.m5262665161593131067msoplaintextgmailmsg, div.m5262665161593131067msoplaintextgmailmsg
	{mso-style-name:"m_5262665161593131067msoplaintext gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.inbox-inbox-h4
	{mso-style-name:inbox-inbox-h4;}
span.m5262665161593131067deletegmailmsg
	{mso-style-name:"m_5262665161593131067delete gmail_msg";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:628128861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1263504596 -40343276 -1933258530 1875814492 1946289654 -395266484 -184810804 -1973797926 1742909670 -568795924;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> 8. Section 10.3
                    states: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB">10.3.<span
                      class="gmail_msg">  </span>Request Source
                    Authentication <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"><span
                      class="gmail_msg">   </span>The source of the
                    Authorization Request MUST always be verified.</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"><span
                      class="gmail_msg">   </span>There are several
                    ways to do it in this specification. <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"><span
                      class="gmail_msg">   </span>(a)<span
                      class="gmail_msg">  </span>Verifying the JWS
                    Signature of the Request Object.</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"> It seems that the
                    case of using a JWE encrypted using a secret key
                    algorithm has been forgotten here. Please add it.</span></p>
              </div>
            </div>
          </blockquote>
          <div>Accepted with modification. </div>
          <div>You mean, symmetric key algorithm, is that right? I would
            add "or verifying that the symmetric key for the<font
              size="+1"> </font><span style="font-size:13.3333px"><font
                size="+1">JWE encryption is a correct one</font>" <br>
            </span></div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <span class="gmailmsg"><span style="font-size:
        12.0pt;font-family:Verdana;mso-fareast-font-family:&quot;Times
        New Roman&quot;;
        mso-bidi-font-family:&quot;Times New
        Roman&quot;;color:#222222;mso-ansi-language:EN-US;
        mso-fareast-language:FR;mso-bidi-language:AR-SA" lang="EN-US">Accepted<br>
      </span></span>
    <meta name="ProgId" content="Word.Document">
    <meta name="Generator" content="Microsoft Word 9">
    <meta name="Originator" content="Microsoft Word 9">
    <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/07/clip_filelist.xml">
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
    <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1593833729 1073750107 16 0 415 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h2
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:2;
	font-size:18.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h3
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:3;
	font-size:13.5pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h4
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:4;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
	font-size:10.0pt;
	font-family:"Arial Unicode MS";}
tt
	{mso-ascii-font-family:"Arial Unicode MS";
	mso-fareast-font-family:"Arial Unicode MS";
	mso-hansi-font-family:"Arial Unicode MS";
	mso-bidi-font-family:"Arial Unicode MS";}
p.msonormalgmailmsg, li.msonormalgmailmsg, div.msonormalgmailmsg
	{mso-style-name:"msonormal gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.gmailmsg
	{mso-style-name:gmail_msg;}
p.m5262665161593131067msoplaintextgmailmsg, li.m5262665161593131067msoplaintextgmailmsg, div.m5262665161593131067msoplaintextgmailmsg
	{mso-style-name:"m_5262665161593131067msoplaintext gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.inbox-inbox-h4
	{mso-style-name:inbox-inbox-h4;}
span.m5262665161593131067deletegmailmsg
	{mso-style-name:"m_5262665161593131067delete gmail_msg";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:628128861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1263504596 -40343276 -1933258530 1875814492 1946289654 -395266484 -184810804 -1973797926 1742909670 -568795924;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style><br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-US"> 9. Section 10.3
                    states at its very end:</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"> <span
                      class="gmail_msg">   </span>An extension
                    specification<br>
                    <span class="gmail_msg">   </span>should be created
                    as a preventive measure to address potential<br>
                    <span class="gmail_msg">   </span>vulnerabilities
                    that have not yet been identified.</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"><br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB">Writing a document
                    for vulnerabilities that have not yet been
                    identified is speculative. It would rather be better
                    <br class="gmail_msg">
                    either to remove this sentence or to explain what is
                    meant by it.</span></p>
              </div>
            </div>
          </blockquote>
          <div>Reject. </div>
          <div>It is referring to the first paragraph of the
            sub-section. Also, precaution when security is in question
            is a good thing. <span
              style="color:rgb(34,34,34);font-family:Verdana;font-size:12pt">
              <br>
            </span></div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span style="font-family:Verdana;color:#222222;
        mso-ansi-language:EN-GB" lang="EN-GB">This sentence is simply
        useless and thus should be
        deleted. Hence, I maintain this comment.</span></p>
    <br>
    <br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB">10. Section 11.1
                    states:</span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> </span><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB">11.1.<span class="gmail_msg">  </span>Collection
                      limitation</span></b></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB"> <span class="gmail_msg">   </span>When
                      the Client is being granted access to a protected
                      resource<br>
                      <span class="gmail_msg">   </span>containing
                      personal data, the Client SHOULD limit the
                      collection of<br>
                      <span class="gmail_msg">   </span>personal data
                      to that which is within the bounds of applicable
                      law<br>
                      <span class="gmail_msg">   </span>and strictly
                      necessary for the specified purpose(s).</span></b><b
                    class="gmail_msg"><span
                      style="font-size:12.0pt;font-family:Verdana;color:#222222"
                      class="gmail_msg" lang="EN-GB"></span></b></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> The <i
                      class="gmail_msg">presentation</i> of personal
                    data should be limited whether or not the protected
                    resource contains personal data.</span> <br>
                </p>
              </div>
            </div>
          </blockquote>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB">It is proposed to
                    change this text into: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><b
                    class="gmail_msg"><span class="gmail_msg"
                      lang="EN-GB"><span class="gmail_msg">   </span>When
                      the Client requests an access to a protected
                      resource, the Client<br>
                      <span class="gmail_msg">   </span>SHOULD limit
                      the presentation of personal data to that which is
                      within<br>
                      <span class="gmail_msg">   </span>the bounds of
                      applicable law and strictly necessary for the
                      specified<br>
                      <span class="gmail_msg">   </span>purpose(s).</span></b></p>
              </div>
            </div>
          </blockquote>
          <div>Reject. </div>
          <div>You are not getting what OAuth does. The party that holds
            personal data is the authorization server / resource. </div>
          <div>It is not the client. The client is the party who is
            getting those "resources" which may contain personal data. </div>
          <div>Yes, the client can provide some personal data to the
            resource depending on what that resource endpoint is, but
            that is out of scope for OAuth. </div>
          <div>As far as OAuth is concerned, what is being sent from the
            client to the resource is the access token. <br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <div style="border:none;border-left:solid #CCCCCC .5pt;padding:0cm
      0cm 0cm 6.0pt">
      <p class="m5262665161593131067msoplaintextgmailmsg"
        style="margin-top:0cm;
margin-right:0cm;margin-bottom:0cm;margin-left:4.8pt;margin-bottom:.0001pt;
        border:none;mso-border-left-alt:solid #CCCCCC
        .5pt;padding:0cm;mso-padding-alt:
        0cm 0cm 0cm 6.0pt"><span
          style="font-family:Arial;mso-ansi-language:
          EN-GB" lang="EN-GB">The dispute is whether the <span
            class="gmailmsg">protected resource
            contains or not personal data. <br>
            The data contained by the protected resource may
            well be public data (or/and personal data). <br>
            It does not need to be only "personal data".<o:p></o:p></span></span></p>
      <p class="m5262665161593131067msoplaintextgmailmsg"
        style="margin-top:0cm;
margin-right:0cm;margin-bottom:0cm;margin-left:4.8pt;margin-bottom:.0001pt;
        border:none;mso-border-left-alt:solid #CCCCCC
        .5pt;padding:0cm;mso-padding-alt:
        0cm 0cm 0cm 6.0pt"><span class="gmailmsg"><span
            style="font-family:
            Arial;mso-ansi-language:EN-GB" lang="EN-GB"><!--[if !supportEmptyParas]--> <!--[endif]--><o:p></o:p></span></span></p>
      <p class="m5262665161593131067msoplaintextgmailmsg"
        style="margin-top:0cm;
margin-right:0cm;margin-bottom:0cm;margin-left:4.8pt;margin-bottom:.0001pt;
        border:none;mso-border-left-alt:solid #CCCCCC
        .5pt;padding:0cm;mso-padding-alt:
        0cm 0cm 0cm 6.0pt"><span class="gmailmsg"><span
            style="font-family:
            Arial;mso-ansi-language:EN-GB" lang="EN-GB">Hence, I
            maintain my comment.</span></span></p>
    </div>
    <br>
    <br>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><b
                    class="gmail_msg"><span
                      style="font-size:12.0pt;font-family:Verdana;color:#222222"
                      class="gmail_msg" lang="EN-GB"></span></b></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> 11. Section 11.2.1
                    states: <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB">11.2.1.<span
                      class="gmail_msg">  </span>Request Disclosure <br>
                  </span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
                    class="gmail_msg" lang="EN-GB"><span
                      class="gmail_msg">   </span>This specification
                    allows extension parameters. </span><span
                    style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> It would be useful
                    to name either all of them or some of them. RFC 6749
                    is not crystal clear about this.</span></p>
              </div>
            </div>
          </blockquote>
          <div>Noted. </div>
          <div>RFC6749 only defines how to define extension parameters. </div>
          <div>This specification draws from OpenID Connect for some
            examples of extension parameters such as nonce. </div>
          <div>See section 4 for example.  <br>
          </div>
        </div>
      </div>
    </blockquote>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <p class="MsoNormal"><span
        style="font-family:Arial;mso-ansi-language:
        EN-GB" lang="EN-GB"><br>
        See my earlier comments where client_id and nonce shall be
        mandatory.<o:p></o:p></span></p>
    <br>
    Denis<br>
    <meta name="ProgId" content="Word.Document">
    <meta name="Generator" content="Microsoft Word 9">
    <meta name="Originator" content="Microsoft Word 9">
    <link rel="File-List"
href="file:///C:/Users/Denis/AppData/Local/Temp/msoclip1/09/clip_filelist.xml">
    <!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:View>Normal</w:View>
  <w:Zoom>0</w:Zoom>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:DoNotOptimizeForBrowser/>
 </w:WordDocument>
</xml><![endif]-->
    <style>
<!--
 /* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;
	mso-font-charset:2;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:0 268435456 0 0 -2147483648 0;}
@font-face
	{font-family:"Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
@font-face
	{font-family:"\@Arial Unicode MS";
	panose-1:2 11 6 4 2 2 2 2 2 4;
	mso-font-charset:128;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-1 -369098753 63 0 4129279 0;}
 /* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
h2
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:2;
	font-size:18.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h3
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:3;
	font-size:13.5pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
h4
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:4;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Courier New";
	mso-fareast-font-family:"Times New Roman";}
p
	{margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
pre
	{margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
	font-size:10.0pt;
	font-family:"Arial Unicode MS";}
tt
	{mso-ascii-font-family:"Arial Unicode MS";
	mso-fareast-font-family:"Arial Unicode MS";
	mso-hansi-font-family:"Arial Unicode MS";
	mso-bidi-font-family:"Arial Unicode MS";}
p.msonormalgmailmsg, li.msonormalgmailmsg, div.msonormalgmailmsg
	{mso-style-name:"msonormal gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.gmailmsg
	{mso-style-name:gmail_msg;}
p.m5262665161593131067msoplaintextgmailmsg, li.m5262665161593131067msoplaintextgmailmsg, div.m5262665161593131067msoplaintextgmailmsg
	{mso-style-name:"m_5262665161593131067msoplaintext gmail_msg";
	margin-right:0cm;
	mso-margin-top-alt:auto;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";}
span.inbox-inbox-h4
	{mso-style-name:inbox-inbox-h4;}
span.m5262665161593131067deletegmailmsg
	{mso-style-name:"m_5262665161593131067delete gmail_msg";}
@page Section1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;
	mso-header-margin:36.0pt;
	mso-footer-margin:36.0pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
@list l0
	{mso-list-id:628128861;
	mso-list-type:hybrid;
	mso-list-template-ids:-1263504596 -40343276 -1933258530 1875814492 1946289654 -395266484 -184810804 -1973797926 1742909670 -568795924;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
    <blockquote
cite="mid:CABzCy2DuPPoBn-3gwjsKpBhR=mqbh08Mn0ST1zBc2vpyMULQPA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_quote">
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <div class="m_5262665161593131067moz-cite-prefix
                gmail_msg">
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"></span></p>
                <p class="m_5262665161593131067MsoPlainText gmail_msg"><span
style="font-size:12.0pt;font-family:Verdana;color:#222222"
                    class="gmail_msg" lang="EN-GB"> Denis Pinkas (DP
                    Security Consulting SAS)</span></p>
                <span
                  style="font-size:12.0pt;font-family:Verdana;color:#222222"
                  class="gmail_msg" lang="EN-GB"> </span><span
                  class="gmail_msg" lang="EN-US">==============================================================
                </span> <br class="gmail_msg">
                <br class="gmail_msg">
              </div>
            </div>
            <div bgcolor="#FFFFFF" text="#000000" class="gmail_msg">
              <blockquote type="cite" class="gmail_msg">
                <pre class="gmail_msg">The IESG has received a request from the Web Authorization Protocol WG
(oauth) to consider the following document:
- 'The OAuth 2.0 Authorization Framework: JWT Secured Authorization
   Request (JAR)'
  &lt;draft-ietf-oauth-jwsreq-11.txt&gt; as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
<a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-abbreviated gmail_msg" href="mailto:ietf@ietf.org" target="_blank">ietf@ietf.org</a> mailing lists by 2017-02-13. Exceptionally, comments may be
sent to <a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-abbreviated gmail_msg" href="mailto:iesg@ietf.org" target="_blank">iesg@ietf.org</a> instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   The authorization request in OAuth 2.0 described in RFC 6749 utilizes
   query parameter serialization, which means that Authorization Request
   parameters are encoded in the URI of the request and sent through
   user agents such as web browsers.  While it is easy to implement, it
   means that (a) the communication through the user agents are not
   integrity protected and thus the parameters can be tainted, and (b)
   the source of the communication is not authenticated.  Because of
   these weaknesses, several attacks to the protocol have now been put
   forward.

   This document introduces the ability to send request parameters in a
   JSON Web Token (JWT) instead, which allows the request to be JWS
   signed and/or JWE encrypted so that the integrity, source
   authentication and confidentiality property of the Authorization
   Request is attained.  The request can be sent by value or by
   reference.




The file can be obtained via
<a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-freetext gmail_msg" href="https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/</a>

IESG discussion can be tracked via
<a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-freetext gmail_msg" href="https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/" target="_blank">https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/ballot/</a>


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


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc6234: US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF) (Informational - IETF stream)
    rfc6819: OAuth 2.0 Threat Model and Security Considerations (Informational - IETF stream)
    rfc6973: Privacy Considerations for Internet Protocols (Informational - IAB stream)
Note that some of these references may already be listed in the acceptable Downref Registry.


_______________________________________________
OAuth mailing list
<a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-abbreviated gmail_msg" href="mailto:OAuth@ietf.org" target="_blank">OAuth@ietf.org</a>
<a moz-do-not-send="true" class="m_5262665161593131067moz-txt-link-freetext gmail_msg" href="https://www.ietf.org/mailman/listinfo/oauth" target="_blank">https://www.ietf.org/mailman/listinfo/oauth</a>
</pre>
              </blockquote>
              <p class="gmail_msg"><br class="gmail_msg">
              </p>
            </div>
            _______________________________________________<br
              class="gmail_msg">
            OAuth mailing list<br class="gmail_msg">
            <a moz-do-not-send="true" href="mailto:OAuth@ietf.org"
              class="gmail_msg" target="_blank">OAuth@ietf.org</a><br
              class="gmail_msg">
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/oauth"
              rel="noreferrer" class="gmail_msg" target="_blank">https://www.ietf.org/mailman/listinfo/oauth</a><br
              class="gmail_msg">
          </blockquote>
        </div>
      </div>
      <div dir="ltr">-- <br>
      </div>
      <div data-smartmail="gmail_signature">
        <p dir="ltr">Nat Sakimura</p>
        <p dir="ltr">Chairman of the Board, OpenID Foundation</p>
      </div>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>

--------------69CBEBA95C3BE4C4C2BE2340--


From nobody Thu Feb  9 13:30:21 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44811129478; Thu,  9 Feb 2017 13:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 BsoC_vkIKA-9; Thu,  9 Feb 2017 13:30:17 -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 DA1F8129455; Thu,  9 Feb 2017 13:30:16 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 146FE80EA4; Thu,  9 Feb 2017 22:30:11 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com>
Date: Thu, 9 Feb 2017 18:30:11 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VWVvD46Up6FL4Vt3ADtaq5nlSps>
Cc: 6man@ietf.org, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, Stefano Previdi <sprevidi@cisco.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 21:30:18 -0000

On 02/09/2017 07:36 AM, otroan@employees.org wrote:
> Fernando,
> 
> Pete asked me to summarize the objections to option 1 - banning header insertion explicitly.
> I responded with the set of objections I've heard for all options, as I couldn't see a straightforward way of only summarising for option 1.
> 
> I don't understand your message.
> Do you disagree with the summary itself? Are there arguments missing?
> Or is your grief that the I have distilled the arguments wrongly or put them in a bad light?
> 
> Or are you just rehashing your position on the issue?

I think that some points are not as clear as they should be:

1) The current state of affairs with respect to IPv6 EH insertion is
that insertion is forbidden. It has always been clear to everyone.

2) However, some folks came up with proposals to insert EH, on the basis
that "RFC2460 does not explicitly ban EH insertion". If there's people
arguing that, we clearly need to make this clear in the spec.

3) There was a consensus call, yes. When the call was made on the
mailing-list, the vast majority of supporters of "let's keep the
ambiguity" were folks from the same company as "2)". I have no idea if
this changes (or not) "consensus"... but this is clearly an important
datapoint.

4) Given "1)" and "2)" above, it should be evident that the spec needs
to be crystal-clear on this topic.

5) Arguing in favor of keeping ambiguity in a spec that has generated
600+ messages in the very group that standardizes the protocol pretty
much reads like "Let's publish a lousy spec!". And I think that would be
very bad. We're talking about something that is at the core of the
protocol, essentially "Is IPv6 an end-to-end protocol?". I would expect
rfc2460bis to answer such a very basic question, and I'm curious how we
could move a spec to (full) Standard without answering such a basic
question.


There's no grief at all. If anything, just a concern that some of these
items might not be clear enough, and, in particular that without the
datapoint in "3)", folks might get a misleading interpretation of the
discussions that happened in th wg. "3" could be read pretty much like
"all folks from the same company that has a proposal to insert EHs what
insertion of EHs to be allowed".

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  9 13:33:49 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141D7129C8B for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 13:33:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_FILL_THIS_FORM_SHORT=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 wcJE_s2IMWWB for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 13:33:46 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D2771295BB for <ietf@ietf.org>; Thu,  9 Feb 2017 13:33:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 7FC6B30041D for <ietf@ietf.org>; Thu,  9 Feb 2017 16:33:45 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id YUl6ejQLbVUj for <ietf@ietf.org>; Thu,  9 Feb 2017 16:33:44 -0500 (EST)
Received: from [192.168.2.100] (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 0A9D530024F for <ietf@ietf.org>; Thu,  9 Feb 2017 16:33:43 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20170209175737.GV28349@mournblade.imrryr.org>
Date: Thu, 9 Feb 2017 16:33:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com>
References: <CAAFsWK1kQUUZrq9Cs47+jYbEJXW+hQN8gzKb+2qjXYdfYhRFzw@mail.gmail.com> <E56ED618-6670-437D-87A9-BD59FC10DBC1@dukhovni.org> <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lkJw0J0SRUKI4YeScccxcAF_rPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 21:33:48 -0000

Viktor:

RFC 5280 says:

   A name constraint for Internet mail addresses MAY specify a
   particular mailbox, all addresses at a particular host, or all
   mailboxes in a domain.  To indicate a particular mailbox, the
   constraint is the complete mail address.  For example,
   "root@example.com" indicates the root mailbox on the host
   "example.com".  To indicate all Internet mail addresses on a
   particular host, the constraint is specified as the host name.  For
   example, the constraint "example.com" is satisfied by any mail
   address at the host "example.com".  To specify any address within a
   domain, the constraint is specified with a leading period (as with
   URIs).  For example, ".example.com" indicates all the Internet mail
   addresses in the domain "example.com", but not Internet mail
   addresses on the host "example.com=E2=80=9D.

I think you are talking about constraints on addresses at a particular =
host and constraints on mailboxes in a domain, but not constraints on a =
particular mailbox.  Please correct me is I got that wrong.

I think you are suggesting that any A-label in the rfc822Name be =
converted to a U-label, and the result is used to constrain the =
SmtpUtf8Name.

If people like your suggestion, then a constraint for a particular =
mailbox will still require a SmtpUtf8Name, so I think the mechanism =
described in the draft is needed.  It would just be used in combination =
with the above.

Russ


On Feb 9, 2017, at 12:57 PM, Viktor Dukhovni <ietf-dane@dukhovni.org> =
wrote:

> [ Sorry about the duplicate post, Somehow the original body got
>  "Content-Disposition: attachment", reposting as "inline". ]
>=20
> On Thu, Feb 09, 2017 at 09:34:27AM -0800, Wei Chuang wrote:
>=20
>>>> The draft says the rfc822Name and SmtpUtf8Name
>>>> name constraints are applied separately, and don't affect other =
results
>>>> (see section 6).
>>>=20
>>> Yes, that's what I'm objecting to.  This is a design error in the
>>> draft.  The namespaces are *not* separate, and orthogonal =
constraints
>>> are not desirable.
>>=20
>> You are stretching the language used above.  They are "applied =
separately".
>=20
> Separate application is not sufficient when the issuer's certificate
> contains only rfc822Name constraints.
>=20
>> I think we're open to changing how name constraints are applied.  But =
its
>> worth spelling out the design concern clearly before going down that =
path.
>> The concern is that as we add a new representation for international =
email
>> address that we are seeing that combinatorial increase in comparisons
>> needed for name constraints.
>=20
> My proposal creates no combinatorial increase of any kind.  When
> the issuer CA has *only* rfc822Name constraints, any SmtpUtf8Name
> subjectAltNames in the certificate, instead of getting a free ride,
> would have to satisfy the rfc822Name constraints.  Each rfc822Name
> constraint becomes (under the identity function) a valid SmtpUtf8
> constraint.
>=20
>> This design chooses to simplify that by keeping rfc822Name name
>> constraint behavior and separately defining a new SmtpUtf8Name name
>> constraint behavior that works only on SmtpUtf8Name names.
>=20
> Yes, buts this evades rfc822Name constraints created SmtpUtf8-agnostic
> parent issuers.  The namespaces are not disjoint.
>=20
>> That simplifies
>> the work of the path verifier and eliminates potential domain (A/U =
label)
>> conversions between the alternate forms.  Work is now shifted to the =
issuer
>> which must explicitly define SmtpUtf8Name name constraint.
>=20
> The simplest thing for the verifier is to do no checks at all.
> Presumably we make things as simple as possible, but no simpler.
> The security requirements should be to correctly process existing
> name constraints.  And I don't believe that *any* conversions are
> required to do this.
>=20
> Specifically, rfc822Name constraints that include a non-empty list
> of permitted subtrees, in the absence of explicit SmtpUtf8Name
> constraints would imply that the CA cannot issue *any* email altnames
> for a non-ASCII domain.   If the domain is all-ASCII, no conversions
> are required.  If the rfc822Name constraints have only excluded
> subtrees, then no non-ASCII domain is excluded.
>=20
>>> The issuer may be SmtpUtf8 aware, but the parent CA that sets the
>>> issuer's constraints (possibly some time ago in the past) may not.
>>> The issuer should not be able to evade name constraints.
>>=20
>> Assuming we keep the current name constraint design, we can add a
>> requirement that name constraints on email addresses has to be =
consistently
>> applied on the certificate issuance path.  In other words, an issuer =
with
>> only rfc822Name name constraints in its path can only issue =
rfc822Name
>> subAltName email addresses.
>=20
> No that's too limiting.  If the issuer is permitted to issue altnames
> for "example.org", it should be able to issue =
"=D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example.org".
>=20
> --=20
> 	Viktor.
>=20


From nobody Thu Feb  9 14:39:57 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E12E51295E8 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 14:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 8BJYFlt7A4gw for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 14:39:53 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56CC21294DA for <ietf@ietf.org>; Thu,  9 Feb 2017 14:39:53 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id 0A8C2284E4C; Thu,  9 Feb 2017 22:39:52 +0000 (UTC)
Date: Thu, 9 Feb 2017 22:39:51 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170209223951.GW28349@mournblade.imrryr.org>
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/We1tksshMsDj3DVVLa-g68hSCAU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 22:39:55 -0000

On Thu, Feb 09, 2017 at 04:33:44PM -0500, Russ Housley wrote:

> RFC 5280 says:
> 
>    A name constraint for Internet mail addresses MAY specify a
>    particular mailbox, all addresses at a particular host, or all
>    mailboxes in a domain.  To indicate a particular mailbox, the
>    constraint is the complete mail address.  For example,
>    "root@example.com" indicates the root mailbox on the host
>    "example.com".  To indicate all Internet mail addresses on a
>    particular host, the constraint is specified as the host name.  For
>    example, the constraint "example.com" is satisfied by any mail
>    address at the host "example.com".  To specify any address within a
>    domain, the constraint is specified with a leading period (as with
>    URIs).  For example, ".example.com" indicates all the Internet mail
>    addresses in the domain "example.com", but not Internet mail
>    addresses on the host "example.com”.
> 
> I think you are talking about constraints on addresses at a particular
> host and constraints on mailboxes in a domain, but not constraints on a
> particular mailbox.  Please correct me is I got that wrong.

Primarily, but not exclusively.  In the case that an issuer CA is
constrainted to a specific rfc822Name, it should not be possible
to evade that constraint by using the same (all-ASCII) address as
an SmtpUtf8Name.

> I think you are suggesting that any A-label in the rfc822Name be converted
> to a U-label, and the result is used to constrain the SmtpUtf8Name.

No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
constraints and no SmptUtf8Name constraints, and the rfc822Name
constraints limit the CA to "example.com", ".example.com", or as
you suggest above, a particular set of explicit rfc822Name addresses,
my suggestion is that it MUST NOT be able to issue SmtpUtf8Name altnames
that violate those constraints.  For example:

    * CA is constrained to permitted subtree rfc822Name: example.com
	- can issue SmtpUtfName: виктор@example.com
	- cannot issue SmtpUtf8Name: виктор@example.net

In the current form of the draft both would be allowed, the second
is a clear violation of the principle of least surprise (and the
policy of the parent CA that created the name constraint).

> If people like your suggestion, then a constraint for a particular mailbox
> will still require a SmtpUtf8Name, so I think the mechanism described in
> the draft is needed.  It would just be used in combination with the above.

As to particular addresses, again:


    * CA is constrained to permitted subtree rfc822Name: viktor@example.com
	- cannot SmtpUtfName: виктор@example.com
	- cannot issue SmtpUtf8Name: виктор@example.net

In the current form of the draft both would be allowed, in clear
violation of the name constraint on the permitted email addresses.

-- 
	Viktor.


From nobody Thu Feb  9 14:51:04 2017
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04C81295F6; Thu,  9 Feb 2017 14:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nj53usJJLTtd; Thu,  9 Feb 2017 14:51:01 -0800 (PST)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 E83ED129607; Thu,  9 Feb 2017 14:51:00 -0800 (PST)
Received: by mail-qk0-x241.google.com with SMTP id i34so2757215qkh.3; Thu, 09 Feb 2017 14:51:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=rXLwJ2xfXUxciBRduZEeXomo3Vuz0sgQ43C3LnPgsJ0=; b=ObwWZDe1LNfD42wRmDMuHMCciCeaXxouE0CC3U/F10/emagcgPPPE9ICsWKT08WDsZ +mgcHHq368+1TQRiuJWOOAbIlXPYSKkyI0uN0OgqkmrFgRFvjr8V9RU8yy6yN5vuxW+J UjFXTpQKN3ZT8FWQxXWt8f3tM5OcDOcofANWyiUZcQHbj01TZu/Tl4pNGI6OVISi6hAP nospjq5s7Gym/tND/EoRcAYMaxKFFZyi6V+mi+s4bvQ74iFNKwP3zJtHBySwySPJZWan gTd3iia8HERnham4JolxqF1hX+4naRVsgVcqq31DMcUv6eSFoq4crDMIt5qif4wmSKAJ fELw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=rXLwJ2xfXUxciBRduZEeXomo3Vuz0sgQ43C3LnPgsJ0=; b=e3oMGhiL/TMkYI29zFiYYZeUo5AZAa4FSmRgiLhgnGG7q+o1DVYBMB+gQfYAxj9Ay5 pqKF9VxvBBruHI+p4i0A1YMKRBQp7ExhsTCIASDrqmxj3tFnJRb7Hd7YBtTlJ8f4oFwa dWV94UxYWv6BaRkzQDNmcbUAUpt7EsYJG3Q4w4H6LenF0Q2Af8UhNYRPjSvJnkhGujdO YppgrRqemjhaSzLy9KmWQm3UhXGnwyTht71r3mcSqUpFGEe84LIz9exbM4Shm60qtsak IvjSAfeW7O/gtUml6ORC64saVN5f6j2JeNrJeP/JRXqtunCg0rn7BxNIUBky7Uy8D/v3 LvhQ==
X-Gm-Message-State: AMke39kX1hc0EF9JR1IjHLMrzAZ0j43sWKsrwdGFb2KZvclhjYRBeZyqcq/KHJWA/CCy1Q==
X-Received: by 10.55.197.28 with SMTP id p28mr5325929qki.255.1486680660017; Thu, 09 Feb 2017 14:51:00 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id f35sm10388332qtb.49.2017.02.09.14.50.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 14:50:59 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <82DA0993-2A86-425A-8314-3AC4831876DE@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_761C8562-AB7D-4A3E-9145-1444E327A716"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
Date: Thu, 9 Feb 2017 14:50:56 -0800
In-Reply-To: <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hRXpfZolBXTx9GwsN28KZ5JQxJs>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org, Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 22:51:02 -0000

--Apple-Mail=_761C8562-AB7D-4A3E-9145-1444E327A716
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Barry,

Thanks, changes look good to me.

Bob

> On Feb 9, 2017, at 9:59 AM, Barry Leiba <barryleiba@computer.org> =
wrote:
>=20
> As a result of the discussion on the -19 version of the draft (where
> "IANA" was replaced with "IANA Services" throughout, and related
> changes were made), the IETF Trust agreed on the alternative of
> putting a paragraph at the beginning (the second paragraph in the
> Introduction in version -20), and then reverting most of the other
> changes in -19.
>=20
> Version -20 now only has the paragraph that explains that we call
> <this stuff> "IANA" in this document, plus a few minor changes that
> came out in IESG Evaluation.
>=20
> We believe the document is now ready to publish, having been through
> Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
> send this version off.
>=20
> Thanks, everyone, for the comments!
>=20
> Barry, document editor
>=20
> On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
>>=20
>> A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
>> has been successfully submitted by Barry Leiba and posted to the
>> IETF repository.
>>=20
>> Name:           draft-leiba-cotton-iana-5226bis
>> Revision:       20
>> Title:          Guidelines for Writing an IANA Considerations Section =
in RFCs
>> Document date:  2017-02-08
>> Group:          Individual Submission
>> Pages:          41
>> URL:            =
https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.tx=
t
>> Status:         =
https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
>> Htmlized:       =
https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
>> Diff:           =
https://www.ietf.org/rfcdiff?url2=3Ddraft-leiba-cotton-iana-5226bis-20
>>=20
>> Abstract:
>>   Many protocols make use of points of extensibility that use =
constants
>>   to identify various protocol parameters.  To ensure that the values
>>   used in these fields do not have conflicting uses, and to promote
>>   interoperability, their allocation is often coordinated by a =
central
>>   record keeper.  For IETF protocols, that role is filled by the
>>   Internet Assigned Numbers Authority (IANA).
>>=20
>>   To make assignments in a given registry prudently, guidance is =
needed
>>   for describing the conditions under which new values should be
>>   assigned, as well as when and how modifications to existing values
>>   can be made.  This document defines a framework for the =
documentation
>>   of these guidelines by specification authors, in order to assure =
that
>>   the provided guidance for the IANA Considerations is clear and
>>   addresses the various issues that are likely in the operation of a
>>   registry.
>>=20
>>   This is the third edition of this document; it obsoletes RFC 5226.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of =
submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> The IETF Secretariat
>>=20
>=20


--Apple-Mail=_761C8562-AB7D-4A3E-9145-1444E327A716
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQEcBAEBCgAGBQJYnPJRAAoJEK7rdBF357uoKrIIAJHGrwuCdH1IsbWKg9sd4fBW
EHmfE9x/jznxMLOS/qOHxDQeE2vKGrCuqCrt3mpie5Okb7Jur/Zt04QQEPw0mqmy
4VluIbV8L78q45WBKbZ5ztfIO5EBDRXMdpZaTdyADIedGBwGPzhXl5Pa5yrKGa0k
flU/iwTTsw4Ecx+RXJKtbYfR+7wIT13yNe+1XsWrKZExBd1aG3kT+NjULsKTB+44
uTNCUurbly4+0Rd9T4ElMVkkdVWnkb4iDLonTpUvWDx3KN6yd1d0gd75xFZDKtRh
c4LTcPeNqD3JlT4YpvyH4ETnT/ptLMg0W96P+LhGN74c7pUIpuPlHlOVrmtseI4=
=bRby
-----END PGP SIGNATURE-----

--Apple-Mail=_761C8562-AB7D-4A3E-9145-1444E327A716--


From nobody Thu Feb  9 14:55:30 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64F7F129409; Thu,  9 Feb 2017 14:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M1zN3aS9Wfbl; Thu,  9 Feb 2017 14:55:23 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 55F3512945F; Thu,  9 Feb 2017 14:55:23 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id e4so1077888pfg.0; Thu, 09 Feb 2017 14:55:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=qdiANBhIoelzfEgV7yU3YVYocdoD72vozdqoP1HAIDA=; b=GZrPYQoYtWgHU9MN8s8sxHBmYuPGUL1gOaQNK42HzEAYokE6CXo8+YH2+O3WeEwyC2 2UlnC2ECboU1QiBbWLBcJOryBDiYDLvJv6fcgRd8+kmnRVBEmE54OffOIpdqpTpVUPTH GEx/QwDcM2x/ruTjnna5/VfCsR2rwyUF4/PgPuKAH1uPKQZ51sHl4m08G9mUfjCJ7wZX 4CBdFVVwo8B8fTqZRjaitUq+iQhcLhesypekQ+WVt39X0HrSi3ne8BtG4zSA704BXi5T TpaJXh0X0rx4nopRVVkbvCxG/oMZw4Y/3g4Y+nO0qYPUqbWjFOrMO2bwFWUir7JdFGsU JPHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=qdiANBhIoelzfEgV7yU3YVYocdoD72vozdqoP1HAIDA=; b=B4QszF2fLGH2Thr0xMvgUbnQs2bS/q1OzfAXaB1Yzxzw/KP4lX3rqEFNiSPxJ/n0W5 B6EJTptcuePt5yu4dNAkr4BsWV+EwdeDcuH0hQeF52WgOrtHS8O8NS76Ow+SVI0qAvvH oH+d563EHxA9TKvJJYACrP5Zr1qF3YQAjhzgzeaQsFix5qrQd0t233drJ3qz+kYIZimw nPAtivF14x1s6nsmPgE5VTyjDwxzV5ow2joA1qB7jSAZ4obsHvunojAAIecjq/c3wBCs 0kQQheVLf/sON4dxHSnhCxrMW3MkKAQqBcByyLClwJukdefLynUqkuWZM5IafPV/QNtG w25w==
X-Gm-Message-State: AMke39n/XF6rQdyPtYa9aeHKeLgPvj+sTuV3tuo9MZtr+CbAD0n4rZNo5YeAjPMOVyKy+w==
X-Received: by 10.84.128.33 with SMTP id 30mr7260769pla.128.1486680922827; Thu, 09 Feb 2017 14:55:22 -0800 (PST)
Received: from ?IPv6:2406:e007:7ac3:1:28cc:dc4c:9703:6781? ([2406:e007:7ac3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 88sm31453517pfr.41.2017.02.09.14.55.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 14:55:22 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>, otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com>
Date: Fri, 10 Feb 2017 11:55:26 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FBDO-6WK9RivfbpR0tt0HsiYADU>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, 6man@ietf.org, IETF Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 22:55:24 -0000

Hi Fernando,

First let me say that I though Ole's summary was fair. One comment below:

On 10/02/2017 10:30, Fernando Gont wrote:
> On 02/09/2017 07:36 AM, otroan@employees.org wrote:
>> Fernando,
>>
>> Pete asked me to summarize the objections to option 1 - banning header insertion explicitly.
>> I responded with the set of objections I've heard for all options, as I couldn't see a straightforward way of only summarising for option 1.
>>
>> I don't understand your message.
>> Do you disagree with the summary itself? Are there arguments missing?
>> Or is your grief that the I have distilled the arguments wrongly or put them in a bad light?
>>
>> Or are you just rehashing your position on the issue?
> 
> I think that some points are not as clear as they should be:
> 
> 1) The current state of affairs with respect to IPv6 EH insertion is
> that insertion is forbidden. It has always been clear to everyone.

I don't think it has. In fact, that's the whole point: some people
have *not* deduced that rule from the RFC2460/RFC1883 wording.

   Brian

> 
> 2) However, some folks came up with proposals to insert EH, on the basis
> that "RFC2460 does not explicitly ban EH insertion". If there's people
> arguing that, we clearly need to make this clear in the spec.
> 
> 3) There was a consensus call, yes. When the call was made on the
> mailing-list, the vast majority of supporters of "let's keep the
> ambiguity" were folks from the same company as "2)". I have no idea if
> this changes (or not) "consensus"... but this is clearly an important
> datapoint.
> 
> 4) Given "1)" and "2)" above, it should be evident that the spec needs
> to be crystal-clear on this topic.
> 
> 5) Arguing in favor of keeping ambiguity in a spec that has generated
> 600+ messages in the very group that standardizes the protocol pretty
> much reads like "Let's publish a lousy spec!". And I think that would be
> very bad. We're talking about something that is at the core of the
> protocol, essentially "Is IPv6 an end-to-end protocol?". I would expect
> rfc2460bis to answer such a very basic question, and I'm curious how we
> could move a spec to (full) Standard without answering such a basic
> question.
> 
> 
> There's no grief at all. If anything, just a concern that some of these
> items might not be clear enough, and, in particular that without the
> datapoint in "3)", folks might get a misleading interpretation of the
> discussions that happened in th wg. "3" could be read pretty much like
> "all folks from the same company that has a proposal to insert EHs what
> insertion of EHs to be allowed".
> 
> Thanks,
> 


From nobody Thu Feb  9 15:17:29 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79B381294EA; Thu,  9 Feb 2017 15:17:23 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 a7VdTVgJOM8q; Thu,  9 Feb 2017 15:17:22 -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 17BE7129BD4; Thu,  9 Feb 2017 15:17:22 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 B6E8A818B3; Fri, 10 Feb 2017 00:17:17 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <753c70f9-5159-8a8b-a364-90e73ec1fc8e@si6networks.com>
Date: Thu, 9 Feb 2017 20:17:05 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CQ2YRu61SK7-Hukcm_ahr82fyKI>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, 6man@ietf.org, IETF Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 23:17:23 -0000

On 02/09/2017 07:55 PM, Brian E Carpenter wrote:
> 
> On 10/02/2017 10:30, Fernando Gont wrote:
>> On 02/09/2017 07:36 AM, otroan@employees.org wrote:
>>> Fernando,
>>>
>>> Pete asked me to summarize the objections to option 1 - banning header insertion explicitly.
>>> I responded with the set of objections I've heard for all options, as I couldn't see a straightforward way of only summarising for option 1.
>>>
>>> I don't understand your message.
>>> Do you disagree with the summary itself? Are there arguments missing?
>>> Or is your grief that the I have distilled the arguments wrongly or put them in a bad light?
>>>
>>> Or are you just rehashing your position on the issue?
>>
>> I think that some points are not as clear as they should be:
>>
>> 1) The current state of affairs with respect to IPv6 EH insertion is
>> that insertion is forbidden. It has always been clear to everyone.
> 
> I don't think it has. In fact, that's the whole point: some people
> have *not* deduced that rule from the RFC2460/RFC1883 wording.

"It has always been clear.... till these proposals on EH insertion arised".

Since some people didn't "deduce" it from the current text, that's a
clear indication that a clarification is warranted.

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  9 15:37:03 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6F02129D26; Thu,  9 Feb 2017 15:37:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeaPztK7uRkq; Thu,  9 Feb 2017 15:37:00 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9571294E5; Thu,  9 Feb 2017 15:37:00 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 09 Feb 2017 23:36:59 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 579D7D788D; Thu,  9 Feb 2017 15:36:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=Te5tmpVtBpEmi7PnKaYIYB6brOA=; b= paQ3Pph3TnyshM+ZubDnjzu4sCjKzANV3ymAHSntSDgSs1Bstev5e6dXrHteo75+ 4laAU0duhPJskig52nrPYiyejtcEZtV6f6P+vkdMxQnPmpO9y1e6Zk5g4xjSoGUj m8q/uP6BWgurH2/yVSgx8AuFO4i6uuFjZrh59iZzB9k=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=lNwT79mbUcBkkibd2ZPzvaI BewSDrSGLR8JPJhxF+SIZzzcns2Hx8/jPLZl0kjDt8n1pKS/H7JTb0BZXEE65saq PE31cDNdQkvk7SFN6eolVlUjsh6CRR71bq4ubWUj74aee1/F1tHbki06IaS8krrr 26K9uDX2ijHhEnqt8pdU=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id D524CD788B; Thu,  9 Feb 2017 15:36:58 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 4D9F288478E0; Fri, 10 Feb 2017 00:36:55 +0100 (CET)
From: otroan@employees.org
Message-Id: <C14D7BF0-6A06-4276-A7F8-9CE9DFE4F793@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7560A77E-A831-406E-AB7E-9FCE5E8D9802"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 10 Feb 2017 00:36:54 +0100
In-Reply-To: <753c70f9-5159-8a8b-a364-90e73ec1fc8e@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com> <753c70f9-5159-8a8b-a364-90e73ec1fc8e@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TGhjWX5Hp5whwv9lLZltiOi-9zM>
Cc: 6man@ietf.org, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 23:37:02 -0000

--Apple-Mail=_7560A77E-A831-406E-AB7E-9FCE5E8D9802
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

>>>> Fernando,
>>>>=20
>>>> Pete asked me to summarize the objections to option 1 - banning =
header insertion explicitly.
>>>> I responded with the set of objections I've heard for all options, =
as I couldn't see a straightforward way of only summarising for option =
1.
>>>>=20
>>>> I don't understand your message.
>>>> Do you disagree with the summary itself? Are there arguments =
missing?
>>>> Or is your grief that the I have distilled the arguments wrongly or =
put them in a bad light?
>>>>=20
>>>> Or are you just rehashing your position on the issue?
>>>=20
>>> I think that some points are not as clear as they should be:
>>>=20
>>> 1) The current state of affairs with respect to IPv6 EH insertion is
>>> that insertion is forbidden. It has always been clear to everyone.
>>=20
>> I don't think it has. In fact, that's the whole point: some people
>> have *not* deduced that rule from the RFC2460/RFC1883 wording.
>=20
> "It has always been clear.... till these proposals on EH insertion =
arised".
>=20
> Since some people didn't "deduce" it from the current text, that's a
> clear indication that a clarification is warranted.

You can now optimize this discussion without having to bother the whole =
IETF list. Just look up the counter arguments in the previously posted =
summary.

E.g. the response to your argument in this email:
1.a.i) Out of scope: Argue the point of header insertion or alternatives =
in the context of those proposals, not in the context of the core IPv6 =
specification. Do not try to make a preemptive strike in the core =
specification.

Only partly tongue in cheek.
O.


--Apple-Mail=_7560A77E-A831-406E-AB7E-9FCE5E8D9802
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYnP0XAAoJEL7aWKiYQt927TgP/04mnqvEK1u4DYplOI0q6Nf+
gCC0uKObzbwywJsXTA3EZCTSggyYZdJJUVNLrYprEatPXOkatOE8Jyf7wz1hlxmy
LX/s4tRBu1OS6J+Mdu/+Rq2DaeCpmsFwMextccQ3LZwgOdaWjJwWRkwT0gvL10kG
BI/AIKNZWtaiBANscO4gyR8zxvvZz2/iBrLKPxK5kKqS4taosDBnqWGaIDnNfI8U
S87S6z3rJBp4bcDbfgLWeSuD4wdToEf/ELz04gDw9Stn26atfjRXoHMtvRLQzDCd
TSztEL6xv9IwiFisY6TjJEUQ4PLmEw1BnpI57KN8pZl4hKCKzv4gpHPXWuXcLdP4
SQWeMixc2ygvwvdgZL+IcMX4WwBfga5fiqOD+wllQEPBPygr7RuQP+pLeQHTFimT
9LrKpIFVZkTu3734h+MYrScuz3XfqqpnsT7/nacirfWGvN7o0WB0Te+mRBapJgig
4WaTXLlPn26M4oqAwpdJIjgFDgX6P4kGn7WtKSETCNCaM3E4wX9bRvbbytpYRpbv
RA2E0iLmlih+MODgEcQDEeRu41twcHOR7vSPjNNozcaNYWQgZr/UbIKlz6oR91ht
UvmQpsu7Kbq4ghzAWqavMxn4VvjD3VxBPsm1apQEJb8bNaHr6WnY2wVCpKYVwFFk
6zTdl3oDvnl7wlx2paQT
=/x3L
-----END PGP SIGNATURE-----

--Apple-Mail=_7560A77E-A831-406E-AB7E-9FCE5E8D9802--


From nobody Thu Feb  9 16:23:46 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21392129D9B for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 16:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LeC6I5gbe18H for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 16:23:43 -0800 (PST)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 C54A3129D9A for <ietf@ietf.org>; Thu,  9 Feb 2017 16:23:43 -0800 (PST)
Received: by mail-pf0-x22a.google.com with SMTP id c73so936147pfb.0 for <ietf@ietf.org>; Thu, 09 Feb 2017 16:23:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=QMVWCQ39x9dRtTIY/u86mPYxYZLRdhfLr/57b/9XJck=; b=kJPln3+pZl6f4Cf3WBFo6a3sB/OCygQthOkxWdKsHLS4bXpnWnqb10pKCp7gW9+fOb Wj4WH6UGrDdK8m/b519nbEsCpNmK8qNqys9Wg/gMDbbLWAfa6EEn7tEL4DPZIhlQZoAh UqvxXngEK4K5Lrz9po7UN0KY03pdZmOgyRYToTdvUmwysLEmF5t0/tKRUKDJJ5s4hPau wiU8+Y6GbBi9MJKo3p6IBX+zIPdeHTmk/Ml3aVNFGPx26rXBAoLicPv/6WpFkRXV9Vly VVmF2GTzhntF1kIXF2mYFJ/toH9QT0KjnQTvVaOAsR7jLOhoDyTY39cnkkcMyHb6EmW0 Y90g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=QMVWCQ39x9dRtTIY/u86mPYxYZLRdhfLr/57b/9XJck=; b=QNwOwaXYFX06n5X1P7ndnpw5mQu521XQjpcyy27Uc6IzMijmar4HdEuoOb26xjgc0s KKl9L6EeftKB5XugN11JI8vMKvAPY5btukeNIzlbsE+SQP5cr5mb/8l2Y3Dt+jNsF58P ofkyIKfIZMqSKoPuFH5IdbbI96+FGOEr9nCRBcvKcTPOt7aS16Bzc8cZvP+5tvR+vhQQ UaNtgi6oOaW/im43L/MHTOFNDWpx4anLgOyVdpVQPNExYr8THtINsTo3vrvenVarQK1k hswCQoaj21GjaRwf5lFErHJAkM31F3pPC1leuUtaadyyX5rA+XVUo9PMiSAQU4i76bkE +ojg==
X-Gm-Message-State: AMke39mD1L7QWpukRME/b8Nm/cETjtXJA4V9luyz2ZsDGictq1947S+0gaWr2DL8NWSMOw==
X-Received: by 10.84.211.137 with SMTP id c9mr7621728pli.8.1486686223367; Thu, 09 Feb 2017 16:23:43 -0800 (PST)
Received: from ?IPv6:2406:e007:7ac3:1:28cc:dc4c:9703:6781? ([2406:e007:7ac3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u14sm31689158pfg.18.2017.02.09.16.23.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 16:23:42 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: otroan@employees.org, Randy Bush <randy@psg.com>
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <a479d81e-42f9-0695-f31a-c494c02de9af@isi.edu> <4118C6CE-7649-436B-9598-78A034AFFE50@employees.org> <209e1aff-aa3a-96a4-650f-44049e04a65d@gmail.com> <m2lgthw9v9.wl-randy@psg.com> <64076704-3fde-39c4-07d0-8aca598e8ad5@gmail.com> <m2fujouw83.wl-randy@psg.com> <61ADC897-E971-48B7-BCB3-BD352B644F98@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <b0612d10-2fc0-d577-1a08-ce48dbd1ac60@gmail.com>
Date: Fri, 10 Feb 2017 13:23:46 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <61ADC897-E971-48B7-BCB3-BD352B644F98@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Fh-_H15lacCs_PTOcVVZJc-KuB4>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 00:23:45 -0000

On 09/02/2017 20:39, otroan@employees.org wrote:
>>>>>> "Many network security devices block all ICMP messages for perceived
>>>>>> security benefits, including the errors that are necessary for the proper
>>>>>> operation of PMTUD. This can result in connections that complete the
>>>>>> TCP three-way handshake correctly, but then hang when data is transferred.
>>>>>> This state is referred to as a black hole connection."
>>>>>
>>>>> Yes. What we are asked to do for Internet Standard is show that a protocol
>>>>> is widely deployed and is interoperable. That's undoubtedly true of RFC1981.
>>>>> The fact that it also has an important failure mode should certainly be
>>>>> documented, but I suspect that every Internet Standard has at least
>>>>> one important failure mode.
>>>>
>>>> the problem is that this particular failure mode is essentially "does
>>>> not work on the real internet."  perhaps documenting that is useful.
>>>> but i guess this is ipv6.
>>>
>>> I fully agree that it should be documented, but the details are already
>>> documented elsewhere. In this document it can be quite short.
>>
>> i have no problem with terse :)
>>
>> "Unfortunately, this protocol does not actually work on the real
>> internet, see \cite{elsewhere}," seems fine to me.
> 
> In the discussion with Joe, we came up with something along the lines of:
> 
> "Many network security devices block all ICMP messages for perceived
> security benefits, including the errors that are necessary for the proper
> operation of PMTUD. This can result in connections that complete the
> TCP three-way handshake correctly, but then hang when data is transferred.
> This state is referred to as a black hole connection. This is one significant
> example of how PMTUD is broken on the Internet."

wfm, subject to Randy's language nit.

    Brian


From nobody Thu Feb  9 16:29:51 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A661295AD; Thu,  9 Feb 2017 16:29:48 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7_zfAVMtim8L; Thu,  9 Feb 2017 16:29: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 D91A6129543; Thu,  9 Feb 2017 16:29:46 -0800 (PST)
Received: from [192.168.3.83] (142-135-17-190.fibertel.com.ar [190.17.135.142]) (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 6764E81A4C; Fri, 10 Feb 2017 01:29:41 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com> <753c70f9-5159-8a8b-a364-90e73ec1fc8e@si6networks.com> <C14D7BF0-6A06-4276-A7F8-9CE9DFE4F793@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <8f5cb517-6a33-792d-a0c4-c3a2bc94264c@si6networks.com>
Date: Thu, 9 Feb 2017 21:29:25 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <C14D7BF0-6A06-4276-A7F8-9CE9DFE4F793@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VC201cxKbdEM3Zany-OCHXj91XM>
Cc: 6man@ietf.org, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 00:29:48 -0000

On 02/09/2017 08:36 PM, otroan@employees.org wrote:
>>> I don't think it has. In fact, that's the whole point: some
>>> people have *not* deduced that rule from the RFC2460/RFC1883
>>> wording.
>> 
>> "It has always been clear.... till these proposals on EH insertion
>> arised".
>> 
>> Since some people didn't "deduce" it from the current text, that's
>> a clear indication that a clarification is warranted.
> 
> You can now optimize this discussion without having to bother the
> whole IETF list. Just look up the counter arguments in the previously
> posted summary.

We're moving RFC2460 to full Standard. You have to make arguments to
*change* the spec, not to clarify what's already in there -- for
instance, ne would expect that part of the benefit of the process is to
clarify the spec where necessary.

If you can make enough of a case to enable EH insertion, then propose
that as what it actually is: a *modification* to the spec.

If we move RFC2460 to full Std without even being able to tell people
whether this is an end-to-end protocol or not, I think that would be a
*very* bad outcome.

Me, I'm done with this discussion. A number of us (Enno Rey, Mark Smith,
and others) have commented on our view on the topic (for IETF folks that
didn't participate in the 6man discussions).

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  9 19:25:47 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2BC129551; Thu,  9 Feb 2017 19:25:42 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ALuGlDn1513o; Thu,  9 Feb 2017 19:25:41 -0800 (PST)
Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 74B04129562; Thu,  9 Feb 2017 19:25:41 -0800 (PST)
Received: by mail-pg0-x244.google.com with SMTP id 204so1932190pge.2; Thu, 09 Feb 2017 19:25:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=89bACYfdmEgrzwwGqzFQd3SxqiJopAme6V1HW2kHR44=; b=mVjv3EyVupQlq20a1Xd9fSLGEhmLmsibWdm1DMZgUEYh5Fefypuwbhp47tbQTIEgFp nqGp0wOgQpmExKymVKnOb+GgNBg3evy1caSzuoIYwPlnVDfLAJmb8/MqZUTVYc03uyUP UGMpm33AqxLHowgLXN0nTaf2JjVvC9oNKKFPqKJjtD6xSoZLhZzxTmOqd9ZHwp6Kvddx Hd7bS5Zl1irpz4101HC1m49T1lCx5fXoagVG3iIgrJuWv4SG0RCo0iJJsqDRLV0ajK78 D41wg1RDuFE9AKPO1jbXcJFsWJLedPLjXunf0sAXrkZFBq9KSdvTIYqMSB40QmN1fONd C0sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=89bACYfdmEgrzwwGqzFQd3SxqiJopAme6V1HW2kHR44=; b=tJhbVzVujApFtelBW3PJjWq4lx8o/wue5gZrHkd/Sr/Ie/AwbttO8M08zl/N8tpCNY 1KzFaohLxB0pHGkPgscja4J7nTD41bEwQTu4FWnm+kS43AyyLLDANaaioLp1fuWogz5z Us4YmuL7rJu1HFIUyT1GEUL1RpL9gmfWCMFductkP+6ZAAFH4Atyoms4kAd/O0lEn1t6 hMkLdv7rWj6Rk4favHAO1u0kEKTFjKTZqQyYrjzujrmzYWPtP5dy9yoz+LdR5qP4KGXk GqlgvpYszNPmCewDYjSlVVS7l1LvXutj0w26+hS93/6hWlJRnxDqefP644x0xeMRjO8t EX6A==
X-Gm-Message-State: AMke39nOPOoODV+f+nFt4zGWesN0NjB7AkFZr/xJH4uRWgUKlG9SOWfrDzqw3ykOAN1xZg==
X-Received: by 10.98.19.145 with SMTP id 17mr7590435pft.26.1486697140821; Thu, 09 Feb 2017 19:25:40 -0800 (PST)
Received: from ?IPv6:2406:e007:7ac3:1:28cc:dc4c:9703:6781? ([2406:e007:7ac3:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k184sm521569pgc.23.2017.02.09.19.25.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Feb 2017 19:25:40 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
Date: Fri, 10 Feb 2017 16:25:44 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fbFK-bB9mYKiIcNH6xJSPW3Tofk>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 03:25:42 -0000

Stewart,

On 10/02/2017 04:19, Stewart Bryant wrote:
...
> I wonder if we would best serve both our future and our heritage
> if we declared RFC1981 as historic, and either left the idea there,
> or declared it as historic and wrote a new text from a clean start?

I don't see that. It's a stable, widely deployed, interoperable
mechanism. That is rather orthogonal to the issue that has been raised,
which is that faulty ICMPv6 filtering blocks it on many, many paths
across the Internet.

...
> It is concerning that the draft does not talk in any detail about
> how modern ECMP works, i.e. using the five tuple, and noting that
> the PMTU may be different depending on the transport layer port
> numbers.

Has this problem been analysed for, say, IPv4? And does the real world
contain ECMP setups with different MTUs on different paths?

> Given that a very large fraction of packets will traverse an MPLS
> network at some point, I am surprised that there is no text talking
> about the importance of providing support for this feature in the 
> MPLS domain. RFC3988 talks to this point, but is only experimental.

I don't understand. How does the fact that there might be some MPLS
segments along the path affect end-to-end PMTUD?

> 
> ======
> 
>    If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>    could use the flow id as the local representation of a path. Packets
>    sent to a particular destination but belonging to different flows may
>    use different paths, with the choice of path depending on the flow
>    id.  This approach will result in the use of optimally sized packets
>    on a per-flow basis, providing finer granularity than PMTU values
>    maintained on a per-destination basis.
> 
> SB> How widely is flow-id supported in networks? I thought that the 
> SB> current position was that it was unreliable as an ECMP indicator
> SB> and thus routers tended to glean information from the packet themselves.

This is future-proofing. Agreed, usage today is limited.

(But it would be better to call it the Flow Label for consistency with other
recent RFCs.)

I think your other comments are all valuable.

Regards
    Brian


From nobody Thu Feb  9 19:27:38 2017
Return-Path: <pwouters@redhat.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BB7129568; Thu,  9 Feb 2017 19:27:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Paul Wouters <pwouters@redhat.com>
To: <secdir@ietf.org>
Subject: Review of draft-ietf-mmusic-sctp-sdp-22
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com>
Date: Thu, 09 Feb 2017 19:27:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hT_0jtbxIUV0nen9Hoz14sunEOk>
Cc: draft-ietf-mmusic-sctp-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 03:27:33 -0000

Reviewer: Paul Wouters
Review result: Has Issues



I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat

these comments just like any other last call comments.


[Note that I am not well versed in SCTP]

This document defines SDP [RFC4566] protocol identifiers (proto
values):
'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.  This specification also
specifies
how to use the new proto values with the SDP Offer/Answer mechanism
[RFC3264] for negotiating SCTP-over-DTLS associations.

As this document only defines a method of signaling to use
UDP/DTLS/SCTP
or UDP/DTLS/SCTP, there are not specific Security Considerations for
this
document, and the Security Considerations correctly points to the
documents
that actually implement the UDP/DTLS/SCTP and TCP/DTLS/SCTP
protocols.

So from a security point of view, this document is Ready.

I do have some generic concerns and questions I would like to see
addressed:

One general issue I have is with the specification of IANA values and
punting
some of its meaning. Let me quote an example:

	NOTE: This specification only defines the usage of the SDP 'max-
	message-size' attribute when associated with an m- line containing
	one of the following proto values: 'UDP/DTLS/SCTP' or 'TCP/DTLS/
	SCTP'.  Usage of the attribute with other proto values needs to be
	defined in a separate specification.

This type of constraint is not clear and easilly displayed in an IANA
registry if
other values are later added to the table. This text is also an
example of how
througout the document, items are explicitely "this use is unspecified
for now
but other documents may change that". It would have been better to
just simply
and clearly state the current specified use, and let future documents
handle
updating this document appropriately. This language use makes a lot of
decisions
for implementers unclear as these decisions are punted forward in time
without
a reference to follow.

Section 4.4.1 states:

	This specification creates an IANA registry for 'association-usage'
values.

I think this should be specified a little more clearly, similar to the
IANA section
specification itself. Something like:

	This specification creates the IANA 'association-usage' registry for
SDP Attributes.

Section 4.4.2:

The table contains an error on the <port> entries (UDP instead of
TCP). I would personally
change the port parameter value to just "port number for <proto>" or
"UDP or TCP port number"

Section 4.5:

I'm unsure if ordering matters, so I am confused by the table ordering
in media, proto, port,
and the m= line example ordering media, port proto.

I'm further confused by the table listing colon's, eg "<proto>:" and
the m= line not
using colons but spaces. And the following a= lines using colons
again. Is this an error,
or this is my lack of familiarity with the used protocols?

Section 5.1:

	Therefore, if the attribute is not present, the associated m- line
MUST be considered invalid.

Is it obvious what one must done when the m- line is considered
invalid?

Section 5.2:

	Leading zeroes MUST NOT be used.

What is the problem with leading zeros? What can go wrong when these
are used? Should
an implementor be warned about something specific?

Section 6.1:

	An SCTP endpoint MUST NOT send a SCTP user message with a message
	size that is larger than the maximum size indicated by the peer, as
	it cannot be assumed that the peer would accept such message.

While this tells an implementer what not to do, it does not tell the
implementer
what to do when this happens on the receiving end. It would be good to
specify
that here as well so that implementors will be reminded to think of
this error
handling case.

	a maximum message size value of zero, it indicates the SCTP endpoint
will handle
	messages of any size, subject to memory capacity etc.

I'm personally not a big fan of 0 meaning infinite, but if this is how
other related
specs are handling these values in this way, I can understand doing it
here as well.
For instance, not specifying a max-message-size seems more indicative
of not having
a max message size. But here that has been defined as meaning 64k. If
this usage
would be a precedent, I would recommend to not do this. If this is how
these things
are done in this world, then I guess stick to what has already been
done in this space.

The table entry in 6.2 lists an email contact for an IANA entry. Why
does an IANA
entry need someone's email address as contact? IANA entries normally
only refer to
the RFC's that define them, and people are expected to contact the
working group
or maybe one of the RFC authors for questions. But putting a name and
email address
entry here seems to convey some kind of "ownership" of the IANA entry
which I think
is the wrong thing to do.

Section 6.3

   As the usage of multiple SCTP associations on top of a single DTLS
   association is outside the scope of this specification, no mux
rules
   are specified for the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto
   values.

Why is this out of scope? If there are good reasons not to do it,
should it not
be defined to MUST NOT? If it is out of scope only for now, then it
seems that
this document should in fact just specify it so people know how to do
it. The
way this is phrased seems to leave the thing hanging in midair, and
implememters
might end up doing different things.


Section 7:

   NOTE: While [I-D.ietf-tsvwg-sctp-dtls-encaps] allows multiple SCTP
   associations on top of a single DTLS association, the procedures
in
   this specification only support the negotiation of a single SCTP
   association on top of any given DTLS association.

And similar here. 

Setion 8:

Similar issues with "the procedures" and with "is out of scope for
this"

Section 9.2:

	This specification does not define semantics for the SDP direction
	attributes [RFC4566].  Unless semantics of these attributes for an
	SCTP association usage have been defined, SDP direction attributes
	MUST be ignored if present.

Why are these attributes not defined in this specification? If there
are good
reasons for it not to have been specified, why not change the language
to
clearly state these attributes here are invalid and MUST be ignored?
If it
is possibly these will be defined in the future (which the current
text
suggest might happen) perhaps that specification really belongs in
this
document.


Nits:

Through the document, there are paragraphs that start with "NOTE:". I
think
those can all be safely removed to increase the readability.

Section 1:

   [I-D.ietf-tsvwg-sctp-dtls-encaps]

This looks but is not a proper reference. (eg there is no link)

   When the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto values, the m-
   line fmt value, identifying the application-layer protocol, MUST
be
   registered by IANA.

This sentence does not parse.


Section 6.1

Line wrapping 'TCP/DTLS/
              SCTP'   is best avoided.


Section 9

	Each can be established and closed without impacting others.

Should that not be "each other" or "the others" (as opposed to
"others" being other things far far away)

Section 10.3

[I-D.ietf-mmusic-dtls-sdp] is not a proper reference with link.

Section 12

I would rephrase "The text in the paragraph above" as these indirect
references make the text harder
to read.



From nobody Thu Feb  9 19:32:45 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50296129656; Thu,  9 Feb 2017 19:32:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.991
X-Spam-Level: 
X-Spam-Status: No, score=-1.991 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, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpVunRpmG5i2; Thu,  9 Feb 2017 19:32:41 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 895E7129578; Thu,  9 Feb 2017 19:32:41 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3vKL9g3zFlz3Dh; Fri, 10 Feb 2017 04:32:39 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1486697559; bh=41ItAJCBPu8Y4GNdSkUe64AugKBIen1ZNJ36Nn8rYY0=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=slCOM8j0RCSCK0AZi/mUHPru6llcQWjcW7MumLmWS30EjA+6TzWxr8JKAXYT8owNm F06QC+162aALKyENVP3Tk99IaZUG1CHbAOd5fkw7sSTvFVKKR08WpvT95AqwVS3Q7/ 0Lazuo+v9qV+Pm5ymisq7Wx4PqdvzloHClqiwdwA=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id NlL_y-MJBiUh; Fri, 10 Feb 2017 04:32:37 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Fri, 10 Feb 2017 04:32:37 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 1C8292DEFE9; Thu,  9 Feb 2017 22:32:35 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 1C8292DEFE9
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 0473940267E6; Thu,  9 Feb 2017 22:32:34 -0500 (EST)
Date: Thu, 9 Feb 2017 22:32:34 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Paul Wouters <pwouters@redhat.com>
Subject: Re: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
In-Reply-To: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com>
Message-ID: <alpine.LRH.2.20.1702092230300.22742@bofh.nohats.ca>
References: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hvGbThT-HBNY_I3KkuYM-j1awFA>
Cc: draft-ietf-mmusic-sctp-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 03:32:44 -0000

On Thu, 9 Feb 2017, Paul Wouters wrote:

> Subject: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
> 
> Reviewer: Paul Wouters
> Review result: Has Issues

ouch. The new secdir review submission using file upload really mangled
the whitespace into something unreadable. I've included the original
review txt file here inline to make the review readable. Perhaps Tero
can investigate what's going on here?

Paul



I have reviewed this document as part of the security directorate's 
ongoing effort to review all IETF documents being processed by the 
IESG.  These comments were written primarily for the benefit of the 
security area directors.  Document editors and WG chairs should treat 
these comments just like any other last call comments.


[Note that I am not well versed in SCTP]

This document defines SDP [RFC4566] protocol identifiers (proto values):
'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.  This specification also specifies
how to use the new proto values with the SDP Offer/Answer mechanism
[RFC3264] for negotiating SCTP-over-DTLS associations.

As this document only defines a method of signaling to use UDP/DTLS/SCTP
or UDP/DTLS/SCTP, there are not specific Security Considerations for this
document, and the Security Considerations correctly points to the documents
that actually implement the UDP/DTLS/SCTP and TCP/DTLS/SCTP protocols.

So from a security point of view, this document is Ready.

I do have some generic concerns and questions I would like to see addressed:

One general issue I have is with the specification of IANA values and punting
some of its meaning. Let me quote an example:

 	NOTE: This specification only defines the usage of the SDP 'max-
 	message-size' attribute when associated with an m- line containing
 	one of the following proto values: 'UDP/DTLS/SCTP' or 'TCP/DTLS/
 	SCTP'.  Usage of the attribute with other proto values needs to be
 	defined in a separate specification.

This type of constraint is not clear and easilly displayed in an IANA registry if
other values are later added to the table. This text is also an example of how
througout the document, items are explicitely "this use is unspecified for now
but other documents may change that". It would have been better to just simply
and clearly state the current specified use, and let future documents handle
updating this document appropriately. This language use makes a lot of decisions
for implementers unclear as these decisions are punted forward in time without
a reference to follow.

Section 4.4.1 states:

 	This specification creates an IANA registry for 'association-usage' values.

I think this should be specified a little more clearly, similar to the IANA section
specification itself. Something like:

 	This specification creates the IANA 'association-usage' registry for SDP Attributes.

Section 4.4.2:

The table contains an error on the <port> entries (UDP instead of TCP). I would personally
change the port parameter value to just "port number for <proto>" or "UDP or TCP port number"

Section 4.5:

I'm unsure if ordering matters, so I am confused by the table ordering in media, proto, port,
and the m= line example ordering media, port proto.

I'm further confused by the table listing colon's, eg "<proto>:" and the m= line not
using colons but spaces. And the following a= lines using colons again. Is this an error,
or this is my lack of familiarity with the used protocols?

Section 5.1:

 	Therefore, if the attribute is not present, the associated m- line MUST be considered invalid.

Is it obvious what one must done when the m- line is considered invalid?

Section 5.2:

 	Leading zeroes MUST NOT be used.

What is the problem with leading zeros? What can go wrong when these are used? Should
an implementor be warned about something specific?

Section 6.1:

 	An SCTP endpoint MUST NOT send a SCTP user message with a message
 	size that is larger than the maximum size indicated by the peer, as
 	it cannot be assumed that the peer would accept such message.

While this tells an implementer what not to do, it does not tell the implementer
what to do when this happens on the receiving end. It would be good to specify
that here as well so that implementors will be reminded to think of this error
handling case.

 	a maximum message size value of zero, it indicates the SCTP endpoint will handle
 	messages of any size, subject to memory capacity etc.

I'm personally not a big fan of 0 meaning infinite, but if this is how other related
specs are handling these values in this way, I can understand doing it here as well.
For instance, not specifying a max-message-size seems more indicative of not having
a max message size. But here that has been defined as meaning 64k. If this usage
would be a precedent, I would recommend to not do this. If this is how these things
are done in this world, then I guess stick to what has already been done in this space.

The table entry in 6.2 lists an email contact for an IANA entry. Why does an IANA
entry need someone's email address as contact? IANA entries normally only refer to
the RFC's that define them, and people are expected to contact the working group
or maybe one of the RFC authors for questions. But putting a name and email address
entry here seems to convey some kind of "ownership" of the IANA entry which I think
is the wrong thing to do.

Section 6.3

    As the usage of multiple SCTP associations on top of a single DTLS
    association is outside the scope of this specification, no mux rules
    are specified for the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto
    values.

Why is this out of scope? If there are good reasons not to do it, should it not
be defined to MUST NOT? If it is out of scope only for now, then it seems that
this document should in fact just specify it so people know how to do it. The
way this is phrased seems to leave the thing hanging in midair, and implememters
might end up doing different things.


Section 7:

    NOTE: While [I-D.ietf-tsvwg-sctp-dtls-encaps] allows multiple SCTP
    associations on top of a single DTLS association, the procedures in
    this specification only support the negotiation of a single SCTP
    association on top of any given DTLS association.

And similar here.

Setion 8:

Similar issues with "the procedures" and with "is out of scope for this"

Section 9.2:

 	This specification does not define semantics for the SDP direction
 	attributes [RFC4566].  Unless semantics of these attributes for an
 	SCTP association usage have been defined, SDP direction attributes
 	MUST be ignored if present.

Why are these attributes not defined in this specification? If there are good
reasons for it not to have been specified, why not change the language to
clearly state these attributes here are invalid and MUST be ignored? If it
is possibly these will be defined in the future (which the current text
suggest might happen) perhaps that specification really belongs in this
document.


Nits:

Through the document, there are paragraphs that start with "NOTE:". I think
those can all be safely removed to increase the readability.

Section 1:

    [I-D.ietf-tsvwg-sctp-dtls-encaps]

This looks but is not a proper reference. (eg there is no link)

    When the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto values, the m-
    line fmt value, identifying the application-layer protocol, MUST be
    registered by IANA.

This sentence does not parse.


Section 6.1

Line wrapping 'TCP/DTLS/
               SCTP'   is best avoided.


Section 9

 	Each can be established and closed without impacting others.

Should that not be "each other" or "the others" (as opposed to "others" being other things far far away)

Section 10.3

[I-D.ietf-mmusic-dtls-sdp] is not a proper reference with link.

Section 12

I would rephrase "The text in the paragraph above" as these indirect references make the text harder
to read.


From nobody Thu Feb  9 20:08:52 2017
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B09129F46; Thu,  9 Feb 2017 20:08:51 -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 autolearn_force=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 LPIrv6bXO0qh; Thu,  9 Feb 2017 20:08:49 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C9EB129F42; Thu,  9 Feb 2017 20:08:49 -0800 (PST)
Received: from [192.168.1.11] (unknown [112.204.169.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id A3C1118013BE; Fri, 10 Feb 2017 05:08:45 +0100 (CET)
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <da7f618d-440a-96b2-ac18-5617b6268c8f@pi.nu>
Date: Fri, 10 Feb 2017 12:08:41 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/90n2EPZMBUVdrjO4Lby5snF2WFg>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 04:08:51 -0000

Barry and Michelle,

The current document says about designated experts:

    The designated expert is responsible for coordinating the appropriate
    review of an assignment request.  The review may be wide or narrow,
    depending on the situation and the judgment of the designated expert.
    This may involve consultation with a set of technology experts,
    discussion on a public mailing list, consultation with a working
    group (or its mailing list if the working group has disbanded), etc.
    Ideally, the designated expert follows specific review criteria as
    documented with the protocol that creates or uses the namespace.  See
    the IANA Considerations sections of [RFC3748] and [RFC3575] for
    specific examples.

And we talk about combinations of allocation policies:

    Such combinations will commonly use one of {Standards Action, IETF
    Review, RFC Required} in combination with one of {Specification
    Required, Expert Review}.  Guidance should be provided about when
    each policy is appropriate, as in the example above.

All this is good, and I support it.

There is one aspect of the work of the designated experts that I have
not seen documented anywhere, maybe not even considered:

We are creating large registries, with quite a bit of inter-
dependencies, in my part of the world the LSP PING registries comes
into mind:
http://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml

That registry have 24 sub-registries, some of the have a "Specification
Required" allocation policy and we have experts appointed.

However, the expert reviews a single allocation at the time, in doing
so I assume that the obvious dependencies are checked. Working groups
allocate code points through Standards Action, there are no explicit
cross review among registries, even though I know that it happens,
individual members of the working sometimes spot issues and propose
improvements. But this is not consistently done across all assignments.

IANA are good at asking when something is not obvious.

As a fail-safe mechanism, and based on what you say above would it be
possible to appoint experts for the ENTIRE registry, no matter what the
allocation policies are. The role of the experts would be extended to
consider the full range of related registries, rather than one registry
at the time.

If this is possible - What would it take?

If it is not possible, can we add text to 5226bis to make it possible?

/Loa




On 2017-02-10 01:59, Barry Leiba wrote:
> As a result of the discussion on the -19 version of the draft (where
> "IANA" was replaced with "IANA Services" throughout, and related
> changes were made), the IETF Trust agreed on the alternative of
> putting a paragraph at the beginning (the second paragraph in the
> Introduction in version -20), and then reverting most of the other
> changes in -19.
>
> Version -20 now only has the paragraph that explains that we call
> <this stuff> "IANA" in this document, plus a few minor changes that
> came out in IESG Evaluation.
>
> We believe the document is now ready to publish, having been through
> Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
> send this version off.
>
> Thanks, everyone, for the comments!
>
> Barry, document editor
>
> On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
>>
>> A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
>> has been successfully submitted by Barry Leiba and posted to the
>> IETF repository.
>>
>> Name:           draft-leiba-cotton-iana-5226bis
>> Revision:       20
>> Title:          Guidelines for Writing an IANA Considerations Section in RFCs
>> Document date:  2017-02-08
>> Group:          Individual Submission
>> Pages:          41
>> URL:            https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.txt
>> Status:         https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
>> Htmlized:       https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
>> Diff:           https://www.ietf.org/rfcdiff?url2=draft-leiba-cotton-iana-5226bis-20
>>
>> Abstract:
>>    Many protocols make use of points of extensibility that use constants
>>    to identify various protocol parameters.  To ensure that the values
>>    used in these fields do not have conflicting uses, and to promote
>>    interoperability, their allocation is often coordinated by a central
>>    record keeper.  For IETF protocols, that role is filled by the
>>    Internet Assigned Numbers Authority (IANA).
>>
>>    To make assignments in a given registry prudently, guidance is needed
>>    for describing the conditions under which new values should be
>>    assigned, as well as when and how modifications to existing values
>>    can be made.  This document defines a framework for the documentation
>>    of these guidelines by specification authors, in order to assure that
>>    the provided guidance for the IANA Considerations is clear and
>>    addresses the various issues that are likely in the operation of a
>>    registry.
>>
>>    This is the third edition of this document; it obsoletes RFC 5226.
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Thu Feb  9 21:02:49 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5656129EE5; Thu,  9 Feb 2017 21:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2vqi7wvi-taG; Thu,  9 Feb 2017 21:02:46 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::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 18779129CD6; Thu,  9 Feb 2017 21:02:46 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id 11so27939442qkl.3; Thu, 09 Feb 2017 21:02:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=e7UudVrnTT8j5sWt7Uz5qKYhvX8ke720f24p9kodXz0=; b=F3+41h3DMNOz4/eCjKTSXtNOJLD27P/7kX9H3a9h7iIik3bKTY94AUu6GTpI5lkPWf W4+hzghtuR5m6+lYeC8+Sa5NYC4jdGsz9TnPixaBBgU4Hqun4+9uJBkcYcoA3n0v/H37 xfBuIZzHJ3DSuLsKcX/3G4StPCF3orkIAGz8fXz29A5a1nsvBnowq76v/KGl8Ox8NiTm S4ydRSlSj2IaNXaYKBoMvCrWg4RIvCJerbLsg2Y3dZTorJK7PXDJYzS3p3RuRbBPRANQ hqbv+1iPh5UM9XmoJMSedQd2p46ch4awHgFyMCBIiODHyyR8Gd9wzpLbXJcDezWDUMo3 1G0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=e7UudVrnTT8j5sWt7Uz5qKYhvX8ke720f24p9kodXz0=; b=Nz8wK7ArZwFd7Cs/1Ukt4UyB8xRt6ZadOfbFWtJsv6sxvOzue4unMHTp3g6WhdwTCk C13v4h8J9SwyEUrF2BaMe455ecPgin3Fseld8R6eq5C/dWOW1WnjziXCzmu9Vi6oS2QR AbsdFRWEhYIJchuWP8ZNhSingwSqTK1paXrRRt3Ok2ZFkShxqYTz5+iQxmy/d+SWaAKN 65FFOlyc9QJy0ILcU2ixBNPusu37y+xKfDLaFpsjwjfnlCWR6t9to5M0r6Kt0iD6KRTi id13hVdt67a0nX0495P9694btVJwQbAUv1m+w1YUCeFfoeUuKwlp/V2ijKZ/40uljin7 Mgag==
X-Gm-Message-State: AMke39mESbbuKO1CO3o97qta780clu/opvfBTOUjGwolEroDd5Q9b8uHlIOoO1IB6V4tjXg7zzRvSijvrRJyuw==
X-Received: by 10.55.146.135 with SMTP id u129mr6482866qkd.219.1486702965022;  Thu, 09 Feb 2017 21:02:45 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.140.19.72 with HTTP; Thu, 9 Feb 2017 21:02:44 -0800 (PST)
In-Reply-To: <da7f618d-440a-96b2-ac18-5617b6268c8f@pi.nu>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com> <da7f618d-440a-96b2-ac18-5617b6268c8f@pi.nu>
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 9 Feb 2017 21:02:44 -0800
X-Google-Sender-Auth: qSOg4XB53vn0VO5ahaZT7AkR2zk
Message-ID: <CALaySJLsGC+UQau9_TyqDXo2a4XA_tagjJt=Pf3uP2waA7VNwA@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
To: Loa Andersson <loa@pi.nu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TqYGmI_52aZaPkPJ74fiyKckObY>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 05:02:48 -0000

Hi, Loa.
I think what you're asking about is already done, and doesn't require
anything specific to be said in BCP 26.  We have quite a few sets of
related registries where the same set of experts is appointed for the
set, and the experts consider what they need to (ideally, what they're
instructed to) with respect to the set of registries.  It's all just a
matter of spelling it out when the registries are created.

We can't put every possible combination of situations and all nuances
in BCP 26.  I think what's there gives enough guidance to allow people
to write policies and guidance for the registries that they need to
create.

Barry

On Thu, Feb 9, 2017 at 8:08 PM, Loa Andersson <loa@pi.nu> wrote:
> Barry and Michelle,
>
> The current document says about designated experts:
>
>    The designated expert is responsible for coordinating the appropriate
>    review of an assignment request.  The review may be wide or narrow,
>    depending on the situation and the judgment of the designated expert.
>    This may involve consultation with a set of technology experts,
>    discussion on a public mailing list, consultation with a working
>    group (or its mailing list if the working group has disbanded), etc.
>    Ideally, the designated expert follows specific review criteria as
>    documented with the protocol that creates or uses the namespace.  See
>    the IANA Considerations sections of [RFC3748] and [RFC3575] for
>    specific examples.
>
> And we talk about combinations of allocation policies:
>
>    Such combinations will commonly use one of {Standards Action, IETF
>    Review, RFC Required} in combination with one of {Specification
>    Required, Expert Review}.  Guidance should be provided about when
>    each policy is appropriate, as in the example above.
>
> All this is good, and I support it.
>
> There is one aspect of the work of the designated experts that I have
> not seen documented anywhere, maybe not even considered:
>
> We are creating large registries, with quite a bit of inter-
> dependencies, in my part of the world the LSP PING registries comes
> into mind:
> http://www.iana.org/assignments/mpls-lsp-ping-parameters/mpls-lsp-ping-parameters.xhtml
>
> That registry have 24 sub-registries, some of the have a "Specification
> Required" allocation policy and we have experts appointed.
>
> However, the expert reviews a single allocation at the time, in doing
> so I assume that the obvious dependencies are checked. Working groups
> allocate code points through Standards Action, there are no explicit
> cross review among registries, even though I know that it happens,
> individual members of the working sometimes spot issues and propose
> improvements. But this is not consistently done across all assignments.
>
> IANA are good at asking when something is not obvious.
>
> As a fail-safe mechanism, and based on what you say above would it be
> possible to appoint experts for the ENTIRE registry, no matter what the
> allocation policies are. The role of the experts would be extended to
> consider the full range of related registries, rather than one registry
> at the time.
>
> If this is possible - What would it take?
>
> If it is not possible, can we add text to 5226bis to make it possible?
>
> /Loa
>
>
>
>
>
> On 2017-02-10 01:59, Barry Leiba wrote:
>>
>> As a result of the discussion on the -19 version of the draft (where
>> "IANA" was replaced with "IANA Services" throughout, and related
>> changes were made), the IETF Trust agreed on the alternative of
>> putting a paragraph at the beginning (the second paragraph in the
>> Introduction in version -20), and then reverting most of the other
>> changes in -19.
>>
>> Version -20 now only has the paragraph that explains that we call
>> <this stuff> "IANA" in this document, plus a few minor changes that
>> came out in IESG Evaluation.
>>
>> We believe the document is now ready to publish, having been through
>> Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
>> send this version off.
>>
>> Thanks, everyone, for the comments!
>>
>> Barry, document editor
>>
>> On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
>>>
>>>
>>> A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
>>> has been successfully submitted by Barry Leiba and posted to the
>>> IETF repository.
>>>
>>> Name:           draft-leiba-cotton-iana-5226bis
>>> Revision:       20
>>> Title:          Guidelines for Writing an IANA Considerations Section in
>>> RFCs
>>> Document date:  2017-02-08
>>> Group:          Individual Submission
>>> Pages:          41
>>> URL:
>>> https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.txt
>>> Status:
>>> https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
>>> Htmlized:
>>> https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
>>> Diff:
>>> https://www.ietf.org/rfcdiff?url2=draft-leiba-cotton-iana-5226bis-20
>>>
>>> Abstract:
>>>    Many protocols make use of points of extensibility that use constants
>>>    to identify various protocol parameters.  To ensure that the values
>>>    used in these fields do not have conflicting uses, and to promote
>>>    interoperability, their allocation is often coordinated by a central
>>>    record keeper.  For IETF protocols, that role is filled by the
>>>    Internet Assigned Numbers Authority (IANA).
>>>
>>>    To make assignments in a given registry prudently, guidance is needed
>>>    for describing the conditions under which new values should be
>>>    assigned, as well as when and how modifications to existing values
>>>    can be made.  This document defines a framework for the documentation
>>>    of these guidelines by specification authors, in order to assure that
>>>    the provided guidance for the IANA Considerations is clear and
>>>    addresses the various issues that are likely in the operation of a
>>>    registry.
>>>
>>>    This is the third edition of this document; it obsoletes RFC 5226.
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Thu Feb  9 21:53:26 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B373129FE6 for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 21:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level: 
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 BzEn8fSUF9DB for <ietf@ietfa.amsl.com>; Thu,  9 Feb 2017 21:53:23 -0800 (PST)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 B6E2E129473 for <ietf@ietf.org>; Thu,  9 Feb 2017 21:53:23 -0800 (PST)
Received: from pps.filterd (m0098420.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1A5nhA5069709 for <ietf@ietf.org>; Fri, 10 Feb 2017 00:53:22 -0500
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by mx0b-001b2d01.pphosted.com with ESMTP id 28h75g132f-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 10 Feb 2017 00:53:22 -0500
Received: from localhost by e32.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 9 Feb 2017 22:53:22 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 9 Feb 2017 22:53:20 -0700
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id C4A7F1FF0023 for <ietf@ietf.org>; Thu,  9 Feb 2017 22:52:57 -0700 (MST)
Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v1A5rKml10813946 for <ietf@ietf.org>; Thu, 9 Feb 2017 22:53:20 -0700
Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DFA43BE03A for <ietf@ietf.org>; Thu,  9 Feb 2017 22:53:19 -0700 (MST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTPS id C44F8BE038 for <ietf@ietf.org>; Thu,  9 Feb 2017 22:53:19 -0700 (MST)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v1A5rIWM018423 for <ietf@ietf.org>; Fri, 10 Feb 2017 00:53:18 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v1A5rIjd018396 for ietf@ietf.org; Fri, 10 Feb 2017 00:53:18 -0500
From: narten@us.ibm.com
Date: Fri, 10 Feb 2017 00:53:18 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 17021005-0004-0000-0000-00001189062C
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006589; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000203; SDB=6.00819761; UDB=6.00400740; IPR=6.00597214;  BA=6.00005130; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014241; XFM=3.00000011; UTC=2017-02-10 05:53:21
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17021005-0005-0000-0000-00007CEF9FB6
Message-Id: <201702100553.v1A5rIjd018396@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-10_02:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702100059
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ee2mQPRD_C4LU8yzU1YM2YoENSU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 05:53:25 -0000

Total of 78 messages in the last 7 days.
 
script run at: Fri Feb 10 00:53:12 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.54% |    9 |  7.78% |    77752 | fgont@si6networks.com
  8.97% |    7 |  6.23% |    62279 | ietf-dane@dukhovni.org
  5.13% |    4 |  9.76% |    97502 | weihaw@google.com
  1.28% |    1 | 13.54% |   135289 | denis.ietf@free.fr
  7.69% |    6 |  6.79% |    67846 | otroan@employees.org
  7.69% |    6 |  5.81% |    58052 | alexey.melnikov@isode.com
  6.41% |    5 |  5.09% |    50911 | brian.e.carpenter@gmail.com
  3.85% |    3 |  4.25% |    42486 | presnick@qti.qualcomm.com
  3.85% |    3 |  1.99% |    19845 | johnl@taugh.com
  2.56% |    2 |  2.20% |    21968 | mellon@fugue.com
  2.56% |    2 |  2.09% |    20850 | phill@hallambaker.com
  2.56% |    2 |  1.95% |    19457 | john-ietf@jck.com
  2.56% |    2 |  1.92% |    19194 | dhc@dcrocker.net
  1.28% |    1 |  3.18% |    31776 | daniele.ceccarelli@ericsson.com
  2.56% |    2 |  1.43% |    14331 | nomcom-chair-2016@ietf.org
  1.28% |    1 |  2.43% |    24274 | ynir.ietf@gmail.com
  1.28% |    1 |  1.50% |    14980 | brford@cisco.com
  1.28% |    1 |  1.50% |    14944 | paul@nohats.ca
  1.28% |    1 |  1.48% |    14809 | stewart@g3ysx.org.uk
  1.28% |    1 |  1.35% |    13528 | akatlas@gmail.com
  1.28% |    1 |  1.33% |    13298 | ted.ietf@gmail.com
  1.28% |    1 |  1.32% |    13194 | lars@netapp.com
  1.28% |    1 |  1.23% |    12249 | pwouters@redhat.com
  1.28% |    1 |  1.19% |    11885 | housley@vigilsec.com
  1.28% |    1 |  1.17% |    11681 | bob.hinden@gmail.com
  1.28% |    1 |  1.16% |    11566 | loa@pi.nu
  1.28% |    1 |  1.01% |    10123 | barryleiba@computer.org
  1.28% |    1 |  0.99% |     9845 | jinmei@wide.ad.jp
  1.28% |    1 |  0.98% |     9756 | spencerdawkins.ietf@gmail.com
  1.28% |    1 |  0.94% |     9405 | heard@pobox.com
  1.28% |    1 |  0.93% |     9265 | ned+ietf@mauve.mrochek.com
  1.28% |    1 |  0.92% |     9172 | fred.l.templin@boeing.com
  1.28% |    1 |  0.90% |     8944 | roland.bless@kit.edu
  1.28% |    1 |  0.88% |     8823 | stewart.bryant@gmail.com
  1.28% |    1 |  0.79% |     7852 | randy@psg.com
  1.28% |    1 |  0.76% |     7610 | mcr+ietf@sandelman.ca
  1.28% |    1 |  0.72% |     7223 | ajs@anvilwalrusden.com
  1.28% |    1 |  0.54% |     5358 | roni.even@mail01.huawei.com
--------+------+--------+----------+------------------------
100.00% |   78 |100.00% |   999322 | Total


From nobody Fri Feb 10 02:20:52 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB87129487; Fri, 10 Feb 2017 02:20:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HaH7n7hUjY3r; Fri, 10 Feb 2017 02:20:41 -0800 (PST)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 BA3E6128E18; Fri, 10 Feb 2017 02:20:40 -0800 (PST)
Received: by mail-wm0-x241.google.com with SMTP id u63so6667232wmu.2; Fri, 10 Feb 2017 02:20:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dBektC9JHSm51JDgOcNkfp/fJv0IMVc5kIf7BSf0igA=; b=K2i3aNiBcyPWxLBpT2wMcFXcJ82i5AeU0a/hjguTWeI+mTasyOJg8I0hzVXgLAmjec gMvlO+H8Fj32dmi8eXGeCzHaox9W355L1AC2ujrcxKNDGreqTVNuyCYQyXqbzPvHBPnu kboriHMn2rJWhb/vKSncm0jSsYoomgHkti7Z9gfyq11IMF1S/RK9gS2MULZSymplcwKf bmCvTtQaBO0YJeMF9Wqdcx/h6hxQXELKasUSJF1fLgsqkd776B6JlU6cM4fepAB42O1e lj8HOBEiuIOgsBxqrBDlNkpdW9Magn4UsGisXwPhrUEZGw2T+7UzRXc0jBarqtSbqPlS 1q1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=dBektC9JHSm51JDgOcNkfp/fJv0IMVc5kIf7BSf0igA=; b=nlaRx13bQZEoIkd0GgNjNQqpOlndtS1BaZKG5OxXyN7+UHvag8jMdsNPQto/vPfTN6 mDnj26Y6SRW/T2wgStfP870m58KhLLyz+nmManioBTCZ06UcL/tjgqJLkdDJD+ZzQQkG 8IXStWz3hMhXkJkHH90IMrqaQ/h9gonO52pG1lRaZsNmezhjxlWkWtvoNg5vI1uV/IMX 4qtJ01fmZXo8KZzvCjj1Ep9nN69MBs/T6sBycNd+qkRu+aHDsy4hgg7zl/Mms1GDFwJ5 cToy9jbEe2SqspHsbsPeM1crIPrEDBJowz7v2/pt2fAq8v8pzvSaSD0Mk+3NzfIzBU93 kq4w==
X-Gm-Message-State: AMke39nCU+NcCxK6IIzKoUx1mEKa7Tdalz1mjRuCMdqS5VnS5oC6mEtYb2jL8hsActNZag==
X-Received: by 10.28.224.213 with SMTP id x204mr6399819wmg.82.1486722038995; Fri, 10 Feb 2017 02:20:38 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id n13sm1976907wrn.40.2017.02.10.02.20.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 02:20:38 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Date: Fri, 10 Feb 2017 10:20:35 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/54dUXgBOR556ucIBIRRdYc3IlZI>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 10:20:42 -0000

On 10/02/2017 03:25, Brian E Carpenter wrote:
> Stewart,
>
> On 10/02/2017 04:19, Stewart Bryant wrote:
> ...
>> I wonder if we would best serve both our future and our heritage
>> if we declared RFC1981 as historic, and either left the idea there,
>> or declared it as historic and wrote a new text from a clean start?
> I don't see that. It's a stable, widely deployed, interoperable
> mechanism. That is rather orthogonal to the issue that has been raised,
> which is that faulty ICMPv6 filtering blocks it on many, many paths
> across the Internet.

I will not debate whether it is faulty or not, but it seems that in 
practice the
Internet breaks the mechanism. However it breaks it is a way that seems
disruptive to some user traffic. The document is really guidance
one how hosts might use  ICMP for optimization, and arguable need
not be a standard at all.

My remark about heritage is that this vintage draft is very much a 
product of
its time, and really needs modernizing, and after modernizing ought to
look quite different, and thus maybe we should employ a procedure
other than a simple replacement.


> ...
>> It is concerning that the draft does not talk in any detail about
>> how modern ECMP works, i.e. using the five tuple, and noting that
>> the PMTU may be different depending on the transport layer port
>> numbers.
> Has this problem been analysed for, say, IPv4? And does the real world
> contain ECMP setups with different MTUs on different paths?

I don't know if anyone has looked. Since the mechanism is 
self-correcting albeit
with some disruption to user traffic it looks to the application and the 
application
user, just like the Internet not working for a few moments.

In a well managed SP network there should not be, but neither should there
be asymmetric path costs, but there are. The less well manage private
networks are less well managed.


>
>> Given that a very large fraction of packets will traverse an MPLS
>> network at some point, I am surprised that there is no text talking
>> about the importance of providing support for this feature in the
>> MPLS domain. RFC3988 talks to this point, but is only experimental.
> I don't understand. How does the fact that there might be some MPLS
> segments along the path affect end-to-end PMTUD?

The point that RFC3988 makes is that MPLS looks like a single hop to IP 
and the
PE has to fragment or has to reply with an ICMP error message to support
PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to 
result
in the right response at the end node.

My point is that the draft is silent on the subject, and perhaps it 
should not be.

However your question make me ask a further question. The draft is also 
silent
on NATs. Is there any advice needed for people designing and configuring 
NATs?

>
>> ======
>>
>>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>     could use the flow id as the local representation of a path. Packets
>>     sent to a particular destination but belonging to different flows may
>>     use different paths, with the choice of path depending on the flow
>>     id.  This approach will result in the use of optimally sized packets
>>     on a per-flow basis, providing finer granularity than PMTU values
>>     maintained on a per-destination basis.
>>
>> SB> How widely is flow-id supported in networks? I thought that the
>> SB> current position was that it was unreliable as an ECMP indicator
>> SB> and thus routers tended to glean information from the packet themselves.
> This is future-proofing. Agreed, usage today is limited.
>
> (But it would be better to call it the Flow Label for consistency with other
> recent RFCs.)

Well the question is whether it is simply limited today, or broken today 
in a manner that
is irrecoverable? I don't know, but I do know that the mainstream ECMP 
approach
is the five-tuple. There is something akin to the flow label being 
deployed in MPLS. However
what distinguishes the MPLS Entropy Label is that it is inserted (and 
removed) by the
service provider and is therefore trusted by the service provider.

>
> I think your other comments are all valuable.
Thank you.

Stewart


From nobody Fri Feb 10 02:29:31 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67E5F1295B2; Fri, 10 Feb 2017 02:29:29 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wSJwDVONDotp; Fri, 10 Feb 2017 02:29:28 -0800 (PST)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 DC3211294F5; Fri, 10 Feb 2017 02:29:27 -0800 (PST)
Received: by mail-wr0-x242.google.com with SMTP id o16so14684296wra.2; Fri, 10 Feb 2017 02:29:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=9QdtTsJ1Fyc2/uzMYpSQv62Aamk/zerXve5ivyTi9+M=; b=NOnvfgu6QIthYXH0+TfEMk4XDR/Y/Gfoq1fQUf4HK9AmQLi7q1M8H7LgRVUl8k438B yz7mQOCtnYRW6Q7zDLiPGqz+8dJ8BtHNzEmRBnt/PTvQVgoiIUZLqALWTfwmN/JCN7v5 HxkqPFxU+NSzJbiJ+85R9C38bcuZJmIEPDnszZdtP7Gl7MFaBJ0A5b8kOPgUJTM6BE8j r0zQJP4Ay5VxYauWKA43OxH1XtM94hl3th8uxLxrSatCyt6iCT014JP6IfN8i4uP8/4/ ABdZb1gFTaRO2EUcS+dSnMxwzE1pG0FLHnslYbOD9s/VQqMVbTfKc5j9pcpEWiZjjcEO LxqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=9QdtTsJ1Fyc2/uzMYpSQv62Aamk/zerXve5ivyTi9+M=; b=cdRAzwnsIzcBNYvinIWZNAi7pjqSGY8YcDMXcL72fN2r/yGGmYH4E/KA6kX721h36i cCuxoWMLOgQW7NvRUN/IQ9gR1doaCk2iqdjgWEir444EnJ/AZ/3cu5leMnhQR/tdgcns mzmeYut4BzpoCqEQVEgUYqlOKp69mihtGX2AmGxgbIiZCN6f6RvNnlOoe7gpZyO7kfWc IyVjawieG+0qMocltjpyqyj2YOvl9K0MN5eAM1BWonzhOvGjwJiJvvxkoNwJe1x6d+Qe flaI8Fkq3yHcC0MLuLQ5P8gipFEn0kigHatF2CbFb/1lEup863fscQbbwIdPBMskG/sr HUdQ==
X-Gm-Message-State: AMke39mx0IWwCjegJjC+i7naqHties7uQ6yjIlB2Y/fFW9GQm3Yuxup6jn6hUpQj3AHp6w==
X-Received: by 10.223.170.221 with SMTP id i29mr8343751wrc.131.1486722566403;  Fri, 10 Feb 2017 02:29:26 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id b87sm926465wmi.0.2017.02.10.02.29.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 02:29:25 -0800 (PST)
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
To: Loa Andersson <loa@pi.nu>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com> <da7f618d-440a-96b2-ac18-5617b6268c8f@pi.nu>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <cb30a738-b5d5-b68a-983c-c95c629a9df4@gmail.com>
Date: Fri, 10 Feb 2017 10:29:23 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <da7f618d-440a-96b2-ac18-5617b6268c8f@pi.nu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/acoK10dkoLnwAQWgFOsMdTtCkuA>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 10:29:29 -0000

Both this document and the early allocation document remain silent
on the reinstatement of expired (dead) early allocations on publication.

If a protocol has taken longer to publish than expected, and the constant
renewal via the IESG has not happened, I think that technically the
result should be a new assignment, when the right thing is often
to support the deployed user base by resurrecting the value and
assigning it to the RFC.

- Stewart


From nobody Fri Feb 10 03:00:14 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35CE41270B4; Fri, 10 Feb 2017 03:00:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level: 
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YiZOgTP69meb; Fri, 10 Feb 2017 03:00:11 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0094.outbound.protection.outlook.com [104.47.0.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9FA611295A6; Fri, 10 Feb 2017 03:00:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=slq/A2ieUhgwWrvnZOd9NPpS0DoJh2G+5BhqnN+XN60=; b=QQ13EPZCvIfEP0pyJ/4BZobX1K9v4fFerNHZbWiNQJqABfArPVBD2WRr7ZRzbSy0oVuMT/XKeq7OfURJX6xxW6n9QnQweFouBHztrQsRPlbiWsxyTXkEOBV6rWoJ+lBzj7Nx+fQRAEFF0hvhRF0zk+0BuWo0IuX3iIbYDI5b7Zo=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.5; Fri, 10 Feb 2017 11:00:05 +0000
Message-ID: <024f01d2838c$7f3670a0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
Date: Fri, 10 Feb 2017 10:57:26 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: HE1PR0701CA0059.eurprd07.prod.outlook.com (10.168.191.27) To VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13)
X-MS-Office365-Filtering-Correlation-Id: 9818fa50-78a3-4ac4-6dad-08d451a3f89d
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:VI1PR07MB1567;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 3:MNv6PF8lsoMimKuf7mJZaiWy9f1H1nQ3XI1x/u7aZP0CX9LZOib9yZsYfNHGIFmOiaId85W2FKkaZ9ekKAk5m3BDX/ve9LWkFAt35QvD8aBGkAsLpgtRxBnNtyWTiWXfhPMk730I5Qa+fkZ3xsqdbqNSnUseqNdv4u8n49lokawCLBYdJsFsE0RwQUsQ1a716ABxkEUDrjGzJMDhwWtR6tjEBuUs9Ib5x8uOiNs/zwZJtog1oYt5TmePOTHYPIZr/EMuDrozEQ6Igr4+yus4IA==; 25:MYpwApclLrjWSYVu05ULvHyGR3n6/sBXdugGBNvu2F6m1HaUOnKWf2cwBfWg8eI/IuYT1v9srxfVcB1ThlhUeNMFR7E58MJvNBoq+Op4grRZfpPH/TVUZxMETUMTFIliynbPfvvevjnJtqBDcaAAzDzpXQdJbHXKAMfBRnHjiKO1wimqQBHSDeS3NmBQWQdttAJ4+GLTwWU4TOhO/KN+ILU6V0kTaJlaM8BrGK7La/7Lzr+rVz2eWze0uaJMtE0Jw1+On/GMGwMyQ1SAiwPwCWJezu6pc1LdxHkdL4tB7X8+fe3s9jkNV+hoxpdSPtIM7ioJi8uaW5OIcZthrjmmvy1EICoYotNpRiUosElEai5lzaKPicdWF0vOJ9M0LTaEyCCF/q3o6Zk68pCDhrElN0Sd6YmqOsaXkPSg6HphzjXkD5/okq6dtBSjhJf+sEiG6E0J1YWLjntd+Fse+dqw4A==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 31:MXv/Ba8SA++DD4KkOX55pU/WNl8BPHzc8LG7YA/vgHaY/h8b8ottw2dbdq0yCp/e5D0LIP7i04mqIT/g/PlZsDGx+ZP/HhUQ/TXZKm8GXagtpSX/dWi2IEXwKNVEs/8a8tAvJFA8zQWgS0i5cZTaeUA/ymNJUZgWheb8esB0ITvt+0P6KPoWBdBEW5SgNbePx/qESqRUIYkSk7Me+yCZN9a01mfVT/qER6qMHhJX8jCAbuQ0nuXq+b2p8gn/muMGG0sLawZALK97OrMBHD/8ug==; 20:EzVj3er4gvQIE2xiKdGdydoTakJ/2o7edfCOOBe/nEkgzmQoIR7VTij7Scsv6xx9JppSfya0NRZtE1O7rTC1P6DNTBaWnPTTfRzdt74P6KZicsc0oVypCBcrM8VuShrfHszO6wnFJUaJabTerQy+U9zjAOBnPQTNeq8LhAxrOAU=
X-Microsoft-Antispam-PRVS: <VI1PR07MB1567CC613671482481D0FDFDC6440@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(120809045254105);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(20161123558025)(6072148); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1567; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 4:2mtzgLUwHO+TUPJR2flRMviF0bDlnlFg3lVphheWHHvAWIeVnZvDATpuar+0rKtcNetaP604SPGBVrjmKtKbtaWkqyPfhQ/H2P6C8rvtDARhLPkZxj6p1N9xzdYbR05QYqF3T4caPz2jhxTgV8o0y/xC1+RxawAsjhV1avccjJ1eTyA7RpsaZuOfj87hqkgdCACyAeP5FHPKhmC1Gln5YbvJkjubAahovGM+oMPZ9LX5QcxOsVZGQKfac9wd85i81HrDerDxX68pEeLiNg7nQXb6RDBieJSPTlpQZ0OAxLK0mbXJVjUS3g6JmrrTR8XmyyVj8Pksn2eT6rO0ClFPZp/btpc/ny840GMp+p52ZOuIYAG32Ggxvc+MMx1zzMzDknvCN8pc6+t0tS3/iTNnjK9vvS9hK1VDUtu+tpej+FZmuzU4mLlsMaX+pB9N/mDXr7xtuH8wo+AO0IaPh3rxeJbUkSopiTCsHwmvWyX1HQeMQAViZwHln55cGyTJfSV/ilKhYLM4eZESZ/CLmB6Ru6ikqU3RkbV6aas2JCh3/E8rSdFXLTVCWdH5/I8Dmmy7gz1iRVeQcCGebvHusbb/iTjaXeFgse7TMihuzf1dcFi78rk9daijlVDl+AFxhUn8+qvdPzIYjfQ2mIyi7bMEQQ==
X-Forefront-PRVS: 0214EB3F68
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(13464003)(377424004)(24454002)(199003)(377454003)(189002)(14496001)(44736005)(53936002)(105586002)(6496005)(6116002)(3846002)(116806002)(106356001)(189998001)(86362001)(15650500001)(33646002)(6486002)(62236002)(230783001)(25786008)(44716002)(4720700003)(50466002)(47776003)(305945005)(230700001)(7736002)(42186005)(92566002)(6666003)(66066001)(1456003)(8676002)(97736004)(81166006)(61296003)(229853002)(81156014)(84392002)(1556002)(101416001)(76176999)(38730400002)(81816999)(50226002)(68736007)(2906002)(4326007)(23676002)(9686003)(6246003)(50986999)(81686999)(6306002)(5660300001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtWSTFQUjA3TUIxNTY3OzIzOmQ3L3k5eXNHZVhqRXhjWkJiYzJQdEFPRkJP?= =?utf-8?B?dG13N01teXRVTkFYdDRaWm1tcS9hUzQvcnZmNGRTRG92U1lJcXBjc3o5eHph?= =?utf-8?B?bVYvYnkrYkV3MmVEMDAvVzk5ZEY4MldZbkJ3NVN2ZklPa0tzQnJRS2sySS9H?= =?utf-8?B?YkI4eEFSL3ZiUGJ6d01LSkJnSG03dzA4Z2RQV2xXNWVWN2ZBRU5jTEtWbUlW?= =?utf-8?B?WlMya0lXQXN0alNLbVpPZ094LzA4cElpYzhnU3ZuZ3djWmw4SDR6cVErdzI3?= =?utf-8?B?ZStYVHJ0SjEwa1BzSDQ5YUhGVFduRkdXamJLdUszQ3MrUmw1aWx0azJWRVI4?= =?utf-8?B?T3dTWGlxWGVVajZGUUxnRmtFMFV5aDJZSWFROGI2VFpHMUxIVlNCOTREQlN5?= =?utf-8?B?dDB0L3lxZzd4eXcweHFSd0Z1d1NPbU1NeVJSdDVkTmp3cllLZkpNOXQyVHJy?= =?utf-8?B?M1AzTytPTXhySHJBZUFEQm83Rzl4ZnlkbWd5Qm43ZHZHTjNJN1lKczcwTmp4?= =?utf-8?B?VG94V1NrY1pPM0UwVjBEUStBNXd5ODdSS0xqWW1LMVh1M3Azc3d6UllxbE1L?= =?utf-8?B?M0ErVmtQYlJXUjRvOEJPa2d2V2Rod29zc284VDl4VUw2TXhpMzNxSlVsTzVj?= =?utf-8?B?ckREWDlQZWhFbmc0REs3Zk1pVHFUT05KY05LSWVZdS9pdFg2S3RPaHdoZVdt?= =?utf-8?B?THZHK1huQm1nc0VPSWt1NEczbXBkNWVpeWNFUlcvYXFDeXkrSloyazM2SVBU?= =?utf-8?B?NWZJclpuOUxkRTJyYWhSdUJhcndKSEJlNnc5TzREY0hHY1pWUGZ0dUhtNnpZ?= =?utf-8?B?R1hIakY5djVVWUtFdXNmM3RtcnVrMmFncDlVOTJ1RmJ6MGEyMEdiTkV3UzBa?= =?utf-8?B?a0k5d3FvTGhuREdyZVRLdnUxeUJHYUlrM0N1TGgxZzRlbjVtMFhJaHBPeGdw?= =?utf-8?B?YXYrZjU5ZksyaGlBYno0czZrRlJsK3RHeE5ZRmJEZTlEWHdNSDZQZ01XSUl5?= =?utf-8?B?QXJwdlUrcE4zNitSQXhMN0tva0l2UFpwQzJOcElXZVhDbFZ3L01NOElQZnRI?= =?utf-8?B?MG80VCtGOTBBZVR0UC9YRm16WGF6SHNXQ2ozK1g0ZjN5Yzh2REN5N0wxdjNa?= =?utf-8?B?SjI4M0ZuWlBhdjJ3c0dVSUpnY3Y5NW5xVFJpWlVXRXpXVE9rK3pzRE9mR0w4?= =?utf-8?B?WjFoVkVhN0lnS3RtS25CZTVOMU00TlFJakQxQmNobnY5UzdnSTZLRkR6MGFi?= =?utf-8?B?WlZpZnYzS3ZWMFl2OUp6SzUzSkpIUzV4MWYveXlJSW5iKytWRk5ybkFnc21r?= =?utf-8?B?YzlycDhySS8zZWlzdnVUREZPOTlCTTlvejhsQzJNT3p2SGVGUEtpRkVKQmx1?= =?utf-8?B?YnFhMmJudEZzSUE4YjlWdGRCblVZNzB2SVh1M2FtTFVVWkZid3MxaG9ENzRZ?= =?utf-8?B?NW41aUxmVHZBbTFMOHkrM2VjSzN1Ny9LczVDa2c1Qm9hWkZ5enM5dGZjdW42?= =?utf-8?B?U0p3M0RlbWVwMWNHcVNGZkxQVC94NjhpWWpNZ3I4U3IzNEk0Y2tEdXd0cWFT?= =?utf-8?B?WnR3OSt3YVJUM1YvUTFjWkhKelhmU1JVTzVIMHFyZzZNektJT3BETzhVeG9l?= =?utf-8?B?QkxXS2tBMTlEQUUzRTBUV3BmRkVXM2JnSlQrcXp4RFkveGxHcGl1UjlDczBr?= =?utf-8?B?L3NXNmdDcllCTUFQbFpqamRQVnlIKzhKTXhPRnlZN25rRWorYWtNWGcvZXNq?= =?utf-8?B?N0pub0x4Ni9VaFhwR0hNODRmZ21jWFUrRVovSmIvMFFOcENKcXpCbWlOVGQ4?= =?utf-8?B?OTdmVmhEdUhlRllUekN1TUV6WFU5RERoOUJKR2Q0akpQbUZGbUUxZUtQTTlH?= =?utf-8?B?YWtiNGxBZUYzdUNDeUZIN0tVaDRkdGtETmxYS2pkdEVSUUdsYTRRNHdHeTdw?= =?utf-8?B?c2ZtUEpDWUYrWFlaYVZzQ3RrUzNKWGV0VjJJRExicTNXK09BNWdnNTIzQmhp?= =?utf-8?B?TUZaa1RxQkR6YUo0Y3pZdmpRZTBtZkNZeTVDdz09?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 6:B5tHB2L+ICzrfO3zz1ON+JsOpoQ3R8j9AaOW6YSb1ppzl/VDlSJULrmwp7xHFUegqhUz+sHoTNv6OKskJOQt5XAnl6GYjrATLUiJx6e5zONpc1qO4Ar4EkycRh2YdCAoRqAwFkGcfljoGojfyW8pBKWPmTUHiHxNh0w8tuirTFkuFthgwDMvbMBHjidR32EiGGm4LW6PEXwGBJ9C7lzGZFKv5jKdP5HgWJObfeFpkQIvVCeP1dutuEJVdYpHLg8WUF2jrS+V/yvyqE56kaaXBY4Q1Z+6SYh2DD3bAGjFLmVwiesC5Gm6XiuWsRoLRcZuM5St13mxB5b/vVtACnW2GQFOY5u7y/uvzvyin7O3RXhAUudG7GSBix1fXzs+fgvnQ8VetACcqAO70WD5i5tJsQ==; 5:cVnyB6YOZyG940rOqatDCuSvj5LBjxy79v/mR8IKnc+114x2kqbiQhTtq5Xjoqc+HUhLXFceE8gawYytKuItnGgYUO3QH4eDh22LeXAk91CK13H4ey95X/fTPqX/M3zwHnF7IPWY9NEN4Vk0X3PvgQ==; 24:Ntnz4VmSpz3AMjikrRIUcHZnNjP41xLvpSYLYdhE0hKbBXn6dd3ob/e2u1CRIz6xLzBg+w5z7sBvixFO4gHf3Y40GCQ5vg2xPBAkRnOpNUM=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 7:Z28rruBp/moYOXktKtBwCL98b6k7iJ5aAI1brqyBX1oSTTON4uOcIzjSv9Oh2SYN8+VGOx5DQLMNlfis53Me/DCAIZZtWHFLRR3BUSUVHsuTReaTre9hwR9FmuWVvgXvgAe9SRv/mGFswAsx1jkxEy4BvAH6Qul5O/O+EttOIedA8RsAvgaGkjSMfAOW034W1edRu7k4WxJ4ranGKS+k4UkLIxun2X+SxEEFkXk8zHFq+m7CmSeDBPjwpyTZ7BdbyXBEaXI/yB7bx42Bj9KDtTV5Y67v9IZYcANjSDQoCVRSaGpYgGHySVi17i5sebLld/0yKMIgi4dCjvKWlcckttdhZg7GJOLPV1QEmucME0uwVNah45fK9s8wNFS+31SJIX7adKqY1ZFphWZZk5pugt2SEOu3QNE/MLLDECW5ECA8EO41E3ZHrCuVoo+5fh42kcv2iC2k7PqpC6QAXITMLw+s4uXUPJUiYmbVof3CQy3/g4DUBjTUOOaR/sEIrZXOND10JgfpkdEZ2sdVIpFJqg==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Feb 2017 11:00:05.1252 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B2mlPbgoOpBKKv_t8Kqo0E_JtH0>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 11:00:13 -0000

Barry

I note that Pete Resnick still  holds a DISCUSS (since 2014) on this
document, according to the datatracker.

What is going to happen to that?

Tom Petch


----- Original Message -----
From: "Barry Leiba" <barryleiba@computer.org>
To: "IETF discussion list" <ietf@ietf.org>
Cc: <draft-leiba-cotton-iana-5226bis.all@ietf.org>
Sent: Thursday, February 09, 2017 5:59 PM


> As a result of the discussion on the -19 version of the draft (where
> "IANA" was replaced with "IANA Services" throughout, and related
> changes were made), the IETF Trust agreed on the alternative of
> putting a paragraph at the beginning (the second paragraph in the
> Introduction in version -20), and then reverting most of the other
> changes in -19.
>
> Version -20 now only has the paragraph that explains that we call
> <this stuff> "IANA" in this document, plus a few minor changes that
> came out in IESG Evaluation.
>
> We believe the document is now ready to publish, having been through
> Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
> send this version off.
>
> Thanks, everyone, for the comments!
>
> Barry, document editor
>
> On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
> >
> > A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
> > has been successfully submitted by Barry Leiba and posted to the
> > IETF repository.
> >
> > Name:           draft-leiba-cotton-iana-5226bis
> > Revision:       20
> > Title:          Guidelines for Writing an IANA Considerations
Section in RFCs
> > Document date:  2017-02-08
> > Group:          Individual Submission
> > Pages:          41
> > URL:
https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.
txt
> > Status:
https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
> > Htmlized:
https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
> > Diff:
https://www.ietf.org/rfcdiff?url2=draft-leiba-cotton-iana-5226bis-20
> >
> > Abstract:
> >    Many protocols make use of points of extensibility that use
constants
> >    to identify various protocol parameters.  To ensure that the
values
> >    used in these fields do not have conflicting uses, and to promote
> >    interoperability, their allocation is often coordinated by a
central
> >    record keeper.  For IETF protocols, that role is filled by the
> >    Internet Assigned Numbers Authority (IANA).
> >
> >    To make assignments in a given registry prudently, guidance is
needed
> >    for describing the conditions under which new values should be
> >    assigned, as well as when and how modifications to existing
values
> >    can be made.  This document defines a framework for the
documentation
> >    of these guidelines by specification authors, in order to assure
that
> >    the provided guidance for the IANA Considerations is clear and
> >    addresses the various issues that are likely in the operation of
a
> >    registry.
> >
> >    This is the third edition of this document; it obsoletes RFC
5226.
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of
submission
> > until the htmlized version and diff are available at tools.ietf.org.
> >
> > The IETF Secretariat
> >
>


From nobody Fri Feb 10 03:29:12 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90152129590; Fri, 10 Feb 2017 03:29:11 -0800 (PST)
X-Quarantine-ID: <ltUzH9tl9eXW>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
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 autolearn_force=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 ltUzH9tl9eXW; Fri, 10 Feb 2017 03:29:10 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 9E186129552; Fri, 10 Feb 2017 03:29:07 -0800 (PST)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cc9Nu-0000CGC; Fri, 10 Feb 2017 12:29:02 +0100
Message-Id: <m1cc9Nu-0000CGC@stereo.hq.phicoh.net>
To: 6man@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard 
From: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <75774ea9-86e8-7353-b4fc-58cad402ffe0@gmail.com> <753c70f9-5159-8a8b-a364-90e73ec1fc8e@si6networks.com> <C14D7BF0-6A06-4276-A7F8-9CE9DFE4F793@employees.org> 
In-reply-to: Your message of "Fri, 10 Feb 2017 00:36:54 +0100 ." <C14D7BF0-6A06-4276-A7F8-9CE9DFE4F793@employees.org> 
Date: Fri, 10 Feb 2017 12:29:00 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CdLxUDoODi-n1ap_fr5bexXahpc>
Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org, IETF Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 11:29:11 -0000

>E.g. the response to your argument in this email:
>1.a.i) Out of scope: Argue the point of header insertion or alternatives 
>in the context of those proposals, not in the context of the core IPv6 
>specification. Do not try to make a preemptive strike in the core 
>specification.

Quoting from this draft (Section 4):
"With one exception, extension headers are not processed by any node
"along a packet's delivery path

"The exception referred to in the preceding paragraph is the Hop-by-
"Hop Options header

I guess somebody has to come up with a creative interpretation of this 
text that allows segment routing headers to be removed along the way.



From nobody Fri Feb 10 06:15:37 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B22C0129965; Fri, 10 Feb 2017 06:15:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 j6RUWTahSP87; Fri, 10 Feb 2017 06:15:29 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 1A3B812988A; Fri, 10 Feb 2017 06:15:28 -0800 (PST)
X-AuditID: c1b4fb2d-2a63298000001743-e6-589dcaff6922
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.183.27]) by  (Symantec Mail Security) with SMTP id E3.7D.05955.FFACD985; Fri, 10 Feb 2017 15:15:27 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 15:15:26 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Wouters <paul@nohats.ca>, Paul Wouters <pwouters@redhat.com>
Subject: Re: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Topic: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Index: AQHSg02fz09JgsaxQEyJwWweq6l2mKFhhUMAgADVvIA=
Date: Fri, 10 Feb 2017 14:15:25 +0000
Message-ID: <D4C388CF.17C73%christer.holmberg@ericsson.com>
References: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com> <alpine.LRH.2.20.1702092230300.22742@bofh.nohats.ca>
In-Reply-To: <alpine.LRH.2.20.1702092230300.22742@bofh.nohats.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <055BCFB29D6093489DCA3E1D4B0D75A4@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsUyM2K7tO7/U3MjDF6+FbXY1L+JxeLZxvks FlOXP2axeH/rEpPFyX33mCw+LHzI4sDmsWTJTyaP7/OYPN7vu8oWwBzFZZOSmpNZllqkb5fA lXFqW1LBRf+KW/dOMzUwvrHrYuTkkBAwkdj47Dk7iC0ksI5R4uhili5GLiB7MaPEh/e3gRIc HGwCFhLd/7RBakQEXCX27r0BVsMssJtR4tmR/WA1wgK2Eqe/KUDU2Ek0z/7ABhIWEbCSaJtp DBJmEVCVaGnqZAGxeQWsJaadf8cMsaqZUWLyheNgYzgFHCW6tuSA1DAKiEl8P7WGCcRmFhCX uPVkPhPEyQISS/acZ4awRSVePv7HCmKLCuhJLH++BiquKPHx1T5GiF4Diffn5jND2NYSa3q3 QtnaEssWvmaGuEdQ4uTMJywTGMVnIVk3C0n7LCTts5C0z0LSvoCRdRWjaHFqcXFuupGxXmpR ZnJxcX6eXl5qySZGYGQe3PJbdwfj6teOhxgFOBiVeHg/NM+JEGJNLCuuzD3EKMHBrCTCO+HQ 3Agh3pTEyqrUovz4otKc1OJDjNIcLErivGYr74cLCaQnlqRmp6YWpBbBZJk4OKUaGJ0u14dN ND6qEuCYlvO5ailXp83By51hKZEtT5a0SHWt4Tx13/1z9c/frH4p387kJ67RX/M84m/Lk4lv mN5IxynNKkva6DbRchL7RomU7jT/6ZdYXnx83qn4pviTuW/Ox6OuytMy/r81fS3a/0uy8ftW ty+/oxsaWdcuS9JaU1z35MGnBRH8DUosxRmJhlrMRcWJAE9Mpl7IAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eAjG2w_oVkg4djomJNRravhl82Y>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 14:15:32 -0000

Hi Paul,

Thanks for your review! Please see inline.

...

>This document defines SDP [RFC4566] protocol identifiers (proto values):
>'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP'.  This specification also specifies
>how to use the new proto values with the SDP Offer/Answer mechanism
>[RFC3264] for negotiating SCTP-over-DTLS associations.
>
>As this document only defines a method of signaling to use UDP/DTLS/SCTP
>or UDP/DTLS/SCTP, there are not specific Security Considerations for this
>document, and the Security Considerations correctly points to the
>documents
>that actually implement the UDP/DTLS/SCTP and TCP/DTLS/SCTP protocols.
>
>So from a security point of view, this document is Ready.

Thanks!

----

>I do have some generic concerns and questions I would like to see
>addressed:
>
>One general issue I have is with the specification of IANA values and
>punting
>some of its meaning. Let me quote an example:
>
> 	NOTE: This specification only defines the usage of the SDP 'max-
> 	message-size' attribute when associated with an m- line containing
> 	one of the following proto values: 'UDP/DTLS/SCTP' or 'TCP/DTLS/
> 	SCTP'.  Usage of the attribute with other proto values needs to be
> 	defined in a separate specification.
>
>This type of constraint is not clear and easilly displayed in an IANA
>registry if
>other values are later added to the table. This text is also an example
>of how
>througout the document, items are explicitely "this use is unspecified
>for now
>but other documents may change that". It would have been better to just
>simply
>and clearly state the current specified use, and let future documents
>handle
>updating this document appropriately. This language use makes a lot of
>decisions
>for implementers unclear as these decisions are punted forward in time
>without
>a reference to follow.

I think the idea is that if someone wants to define the usage for other
proto values he/she does not need to update THIS specification, as it
already allows it.

----

>Section 4.4.1 states:
>
> 	This specification creates an IANA registry for 'association-usage'
>values.
>
>I think this should be specified a little more clearly, similar to the
>IANA section
>specification itself. Something like:
>
> 	This specification creates the IANA 'association-usage' registry for
>SDP Attributes.

We are discussing this with IANA, so the text will be aligned.

----

>Section 4.4.2:
>
>The table contains an error on the <port> entries (UDP instead of TCP).

Correct. That was noted also by the AD.

----

> I would personally change the port parameter value to just "port number
>for <proto>" or "UDP or TCP port number"

People wanted to have the proto values explicitly stated, so I=B9d like to
keep them.

----

>Section 4.5:
>
>I'm unsure if ordering matters, so I am confused by the table ordering in
>media, proto, port,
>and the m=3D line example ordering media, port proto.

I obivously can=B9t change the order in the m=3D line, but I can change the
order of <proto> and <port> in the table, if you think that make things
more clear.

----

>I'm further confused by the table listing colon's, eg "<proto>:" and the
>m=3D line not
>using colons but spaces. And the following a=3D lines using colons again.
>Is this an error,
>or this is my lack of familiarity with the used protocols?

I honestly have no idea why the colones are there (probably a copy/paste
error). I can remove them.

----

>Section 5.1:
>
> 	Therefore, if the attribute is not present, the associated m- line MUST
>be considered invalid.
>
>Is it obvious what one must done when the m- line is considered invalid?

I could add =B3, and MUST NOT be used to establish an SCTP-over-DTLS
association."

----

>Section 5.2:
>
> 	Leading zeroes MUST NOT be used.
>
>What is the problem with leading zeros? What can go wrong when these are
>used? Should
>an implementor be warned about something specific?

I don=B9t know. The same statement exists for a number of SDP attributes,
but I didn=B9t find any justification.

----

>Section 6.1:
>
> 	An SCTP endpoint MUST NOT send a SCTP user message with a message
> 	size that is larger than the maximum size indicated by the peer, as
> 	it cannot be assumed that the peer would accept such message.
>
>While this tells an implementer what not to do, it does not tell the
>implementer
>what to do when this happens on the receiving end. It would be good to
>specify
>that here as well so that implementors will be reminded to think of this
>error
>handling case.

I am not sure whether it=B9s within the scope of this document to say what
SCTP endpoints do if they receive SCTP user messages that are too big for
them to handle.


> 	a maximum message size value of zero, it indicates the SCTP endpoint
>will handle
> 	messages of any size, subject to memory capacity etc.
>
>I'm personally not a big fan of 0 meaning infinite, but if this is how
>other related
>specs are handling these values in this way, I can understand doing it
>here as well.
>For instance, not specifying a max-message-size seems more indicative of
>not having
>a max message size. But here that has been defined as meaning 64k. If
>this usage
>would be a precedent, I would recommend to not do this. If this is how
>these things
>are done in this world, then I guess stick to what has already been done
>in this space.

I don=B9t know how things are normally done, because the only other SDP
attribute I can think of providing similar information is =8Cmax-size=B9 (R=
FC
4975), but it does not define a default value, nor a infinite value.


>The table entry in 6.2 lists an email contact for an IANA entry. Why does
>an IANA
>entry need someone's email address as contact? IANA entries normally only
>refer to
>the RFC's that define them, and people are expected to contact the
>working group
>or maybe one of the RFC authors for questions. But putting a name and
>email address
>entry here seems to convey some kind of "ownership" of the IANA entry
>which I think
>is the wrong thing to do.

You=B9ll have to ask IANA about that :) The e-mail address is within the
template that has to be filled.

Keep in mind, though, that IANA entries are not always defined in RFCs.
For example, a number of registrations have been provided by 3GPP.

----

>Section 6.3
>
>    As the usage of multiple SCTP associations on top of a single DTLS
>    association is outside the scope of this specification, no mux rules
>    are specified for the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto
>    values.
>
>Why is this out of scope? If there are good reasons not to do it, should
>it not
>be defined to MUST NOT? If it is out of scope only for now, then it seems
>that
>this document should in fact just specify it so people know how to do it.
>The
>way this is phrased seems to leave the thing hanging in midair, and
>implememters
>might end up doing different things.

In order to allow multiple SCTP associations, you would have to be able to
provide multiple SCTP ports, and somehow associate those with each
association. We decided not to do that.

But, I don=B9t think we want to forbid people from establishing multiple
SCTP associations - this spec just doesn=B9t support using SDP offer/answer
for negotiating multiple associations.

----

>Section 7:
>
>    NOTE: While [I-D.ietf-tsvwg-sctp-dtls-encaps] allows multiple SCTP
>    associations on top of a single DTLS association, the procedures in
>    this specification only support the negotiation of a single SCTP
>    association on top of any given DTLS association.
>
>And similar here.

See above.

----

>Setion 8:
>
>Similar issues with "the procedures" and with "is out of scope for this"
>
>Section 9.2:
>
> 	This specification does not define semantics for the SDP direction
> 	attributes [RFC4566].  Unless semantics of these attributes for an
> 	SCTP association usage have been defined, SDP direction attributes
> 	MUST be ignored if present.
>
>Why are these attributes not defined in this specification? If there are
>good
>reasons for it not to have been specified, why not change the language to
>clearly state these attributes here are invalid and MUST be ignored? If it
>is possibly these will be defined in the future (which the current text
>suggest might happen) perhaps that specification really belongs in this
>document.

The direction attributes are not used for transports. They are used for
=B3applications=B2, e.g, RTP.

But, as nobody has indicated any interest of defining
RTP-over-SCTP-over-DTLS, there is no idea to define how the direction
attributes would be used.

----


Nits:

>Through the document, there are paragraphs that start with "NOTE:". I
>think
>those can all be safely removed to increase the readability.

Ok, I=B9ll look into that.

----

>Section 1:
>
>    [I-D.ietf-tsvwg-sctp-dtls-encaps]
>
>This looks but is not a proper reference. (eg there is no link)
>
>    When the 'UDP/DTLS/SCTP' and 'TCP/DTLS/SCTP' proto values, the m-
>    line fmt value, identifying the application-layer protocol, MUST be
>    registered by IANA.
>
>This sentence does not parse.
>
>
>Section 6.1
>
>Line wrapping 'TCP/DTLS/
>               SCTP'   is best avoided.

I=B9ll fix that.

----

>Section 9
>
> 	Each can be established and closed without impacting others.
>
>Should that not be "each other" or "the others" (as opposed to "others"
>being other things far far away)

I=B9ll change to =B3the others=B2.

----

>Section 10.3
>
>[I-D.ietf-mmusic-dtls-sdp] is not a proper reference with link.

I=B9ll look into that.

----

>Section 12
>
>I would rephrase "The text in the paragraph above" as these indirect
>references make the text harder
>to read.

I could remove the first sentence, and keep the second:

    "If ICE is not used, the proto value MUST always reflect the transport
protocol used at any given time."



Regards,

Christer



From nobody Fri Feb 10 06:17:40 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2382B129614; Fri, 10 Feb 2017 06:17:30 -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 autolearn_force=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 11cTzIcZstsh; Fri, 10 Feb 2017 06:17:27 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 32BF212998D; Fri, 10 Feb 2017 06:17:18 -0800 (PST)
X-AuditID: c6180641-c3fff70000000a06-dc-589d8518899b
Received: from EUSAAHC005.ericsson.se (Unknown_Domain [147.117.188.87]) by  (Symantec Mail Security) with SMTP id 0C.3B.02566.8158D985; Fri, 10 Feb 2017 10:17:14 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC005.ericsson.se ([147.117.188.87]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 09:17:14 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Charlie Perkins <charles.perkins@earthlink.net>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSe/j/cjYYsQbutUCsVh56ND0V9aFVgPUAgAAQ6gCADSuDgA==
Date: Fri, 10 Feb 2017 14:17:13 +0000
Message-ID: <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
In-Reply-To: <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-originating-ip: [147.117.188.12]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8F92523113235A438CA26F0B60E987E7@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGIsWRmVeSWpSXmKPExsUyuXRPuK5U69wIgwd7jSzu37nGZnH/UY3F /9lb2C2uvvrMYvFs43wWi4N/trFZvDxR5sDuMXn/V2aPKb83snqs+jKB2WPJkp9MASxRXDYp qTmZZalF+nYJXBn3Xk5jK3hxkrHi/IITjA2MF44wdjFycEgImEg8PVvZxcjFISSwnlHi7J49 7BDOckaJhnkdQEWcHGxARRt2fmYCSYgIbGKUuPrlJxuIwywwnVFixc8pbCBVwgIWEjOnXwbr EBGwlJg44yIzhO0kcex6LyuIzSKgKnH++T6wel4Be4meWVuYIdatZpQ40LMa7CZOAUeJ1tX6 IDWMAmIS30+tYQKxmQXEJW49mQ9mSwgISCzZc54ZwhaVePn4H9h8UQE9iY0XprFDxJUk5ry+ xgwykllAU2L9Ln2IMdYSN+4cghqpKDGl+yE7xDmCEidnPmGZwCg+C8m2WQjds5B0z0LSPQtJ 9wJG1lWMHKXFBTm56UaGmxiBsXlMgs1xB+PeXs9DjAIcjEo8vBu850QIsSaWFVfmHmKU4GBW EuGdcGhuhBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXHe6yH3w4UE0hNLUrNTUwtSi2CyTBycUg2M 0Y8uhrRu/LdaKGlVfdTcIOYLZguOSW59m+RnsH2hqFfqZMW4BRMi+l0a3+S+d5cUs1Lsa82/ zyHVLjpj/mP2K0krYtf7T5z3i1tJrPRtQNi8Z2KK7UVHZzFx3foo0r1+s35XugdHwyOBuJem a9Tk5JqXvN5/aHfAPPdwDePdGg87Dx86ZbpViaU4I9FQi7moOBEA0ffDPckCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bYjpgBjJ6RNNIPzysDLSxCLZLYk>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 14:17:30 -0000

SGkgQ2hhcmxpZSwNCiAgSSBoYXZlIG5vdCB5ZXQgc2VlbiBhIHJlc3BvbnNlIHRvIHRoaXMgcmV2
aWV3LiBEbyB5b3UgdGhpbmsgeW91IHdpbGwgYmUgYWJsZSB0byBnZXQgdG8gdGhpcyBpbiB0aGUg
bmV4dCBkYXkgb3IgdHdvPyBUaGUgZG9jdW1lbnQgaXMgb24gdGhlIEZlYnJ1YXJ5IDE2IDIwMTcg
dGVsZWNoYXQgYW5kIEkgd291bGQgbGlrZSB0byBzZWUgcmVzb2x1dGlvbiB0byB0aGVzZSBpc3N1
ZXMgaW4gdGltZSBmb3IgdGhlIG90aGVyIEFEcyB0byBiYWxsb3QuDQoNClRoYW5rcw0KU3VyZXNo
DQoNCk9uIDIvMi8xNywgMToxMCBBTSwgIkNoYXJsaWUgUGVya2lucyIgPGNoYXJsZXMucGVya2lu
c0BlYXJ0aGxpbmsubmV0PiB3cm90ZToNCg0KICAgIEhlbGxvIFNyaSwNCiAgICANCiAgICBUaGUg
cmV2aWV3IHdhcyBpbmRlZWQgc3VwZXIuICBJJ2xsIHJlc3BvbmQgc29tZXRpbWUgaW4gdGhlIG5l
eHQgZmV3IGRheXMuDQogICAgDQogICAgUmVnYXJkcywNCiAgICBDaGFybGllIFAuDQogICAgDQog
ICAgDQogICAgT24gMi8xLzIwMTcgOTowOSBQTSwgU3JpIEd1bmRhdmVsbGkgKHNndW5kYXZlKSB3
cm90ZToNCiAgICA+IFRoYW5rIHlvdSBEYWxlIGZvciBhIGdyZWF0IHJldmlldy4NCiAgICA+DQog
ICAgPg0KICAgID4gQ2hhcmxpZS9BdXRob3JzIC0gQ2FuIHlvdSBwbGVhc2UgcmVzcG9uZCB0byBE
YWxlIGFuZCBhZGRyZXNzIHRoZXNlDQogICAgPiBjb21tZW50cy4NCiAgICA+DQogICAgPg0KICAg
ID4gUmVnYXJkcw0KICAgID4gU3JpDQogICAgPg0KICAgID4NCiAgICA+IE9uIDEvMzEvMTcsIDEx
OjM0IEFNLCAiZG1tIG9uIGJlaGFsZiBvZiBEYWxlIFdvcmxleSIgPGRtbS1ib3VuY2VzQGlldGYu
b3JnDQogICAgPiBvbiBiZWhhbGYgb2Ygd29ybGV5QGFyaWFkbmUuY29tPiB3cm90ZToNCiAgICA+
DQogICAgPj4gUmV2aWV3ZXI6IERhbGUgV29ybGV5DQogICAgPj4gUmV2aWV3IHJlc3VsdDogUmVh
ZHkgd2l0aCBJc3N1ZXMNCiAgICA+Pg0KICAgID4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuICBUaGUgR2VuZXJhbCBBcmVhDQogICAgPj4gUmV2aWV3
IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3Nl
ZA0KICAgID4+IGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0
aGVzZSBjb21tZW50cyBqdXN0DQogICAgPj4gbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1l
bnRzLg0KICAgID4+DQogICAgPj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhl
IEZBUSBhdA0KICAgID4+IDxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90cmFj
L3dpa2kvR2VuQXJ0ZmFxPi4NCiAgICA+Pg0KICAgID4+IERvY3VtZW50OiAgZHJhZnQtaWV0Zi1k
bW0tNDI4M21uaWRzLTA0DQogICAgPj4gUmV2aWV3ZXI6ICBEYWxlIFIuIFdvcmxleQ0KICAgID4+
IFJldmlldyBEYXRlOiAgMzEgSmFuIDIwMTcNCiAgICA+PiBJRVRGIExDIEVuZCBEYXRlOiAgMiBG
ZWIgMjAxNw0KICAgID4+IElFU0cgVGVsZWNoYXQgZGF0ZTogIDE2IEZlYiAyMDE3DQogICAgPj4N
CiAgICA+PiBTdW1tYXJ5Og0KICAgID4+DQogICAgPj4gICAgICAgIFRoaXMgZHJhZnQgaXMgb24g
dGhlIHJpZ2h0IHRyYWNrIGJ1dCBoYXMgb3BlbiBpc3N1ZXMsDQogICAgPj4gZGVzY3JpYmVkDQog
ICAgPj4gICAgICAgIGluIHRoZSByZXZpZXcuDQogICAgPj4NCiAgICA+PiBUZWNobmljYWwgaXNz
dWVzOg0KICAgID4+DQogICAgPj4gMS4gVGhlIEludHJvZHVjdGlvbiBzdGF0ZXMNCiAgICA+Pg0K
ICAgID4+ICAgIE90aGVyIHR5cGVzIG9mIGlkZW50aWZpZXJzIGFyZSBpbg0KICAgID4+ICAgIGNv
bW1vbiB1c2UsIGFuZCBldmVuIHJlZmVyZW5jZWQgaW4gUkZDIDQyODMuDQogICAgPj4NCiAgICA+
PiBGb3IgdGhlIHJlYWRlcidzIHNhbml0eSwgc29tZSBzb3J0IG9mIGFjY291bnRpbmcgbmVlZHMg
dG8gYmUgbWFkZSBvZg0KICAgID4+IHRoZXNlICJvdGhlciB0eXBlcyBvZiBpZGVudGlmaWVycyIs
IGVzcGVjaWFsbHkgYmVjYXVzZSBlYWNoIHR5cGUgb2YNCiAgICA+PiBpZGVudGlmaWVyIG5lZWRz
IGFuIGlkZW50aWZpZXIgdHlwZSBudW1iZXIuICBUaGUgdGV4dCBpbiA0MjgzIGlzDQogICAgPj4N
CiAgICA+PiAgICBTb21lIGV4YW1wbGVzIG9mIGlkZW50aWZpZXJzDQogICAgPj4gICAgaW5jbHVk
ZSBOZXR3b3JrIEFjY2VzcyBJZGVudGlmaWVyIChOQUkpLCBGdWxseSBRdWFsaWZpZWQgRG9tYWlu
DQogICAgPj4gTmFtZQ0KICAgID4+ICAgIChGUUROKSwgSW50ZXJuYXRpb25hbCBNb2JpbGUgU3Rh
dGlvbiBJZGVudGlmaWVyIChJTVNJKSwgYW5kIE1vYmlsZQ0KICAgID4+ICAgIFN1YnNjcmliZXIg
TnVtYmVyIChNU0lTRE4pLg0KICAgID4+DQogICAgPj4gQXJlIHRoZXJlIGFueSBvdGhlciB0eXBl
cyAiaW4gY29tbW9uIHVzZSI/DQogICAgPj4NCiAgICA+PiAtIE5BSSAodHlwZSAxKSBpcyBkZWZp
bmVkIGJ5IDQyODMuDQogICAgPj4gLSBGdWxseSBRdWFsaWZpZWQgRG9tYWluIE5hbWUgKEZRRE4p
IHNlZW1zIG5vdCB0byBiZSBzcGVjaWZpZWQNCiAgICA+PiAtIEludGVybmF0aW9uYWwgTW9iaWxl
IFN0YXRpb24gSWRlbnRpZmllciAoSU1TSSkgKHR5cGUgMykgaXMgZGVmaW5lZA0KICAgID4+IGlu
DQogICAgPj4gICB0aGlzIGRyYWZ0DQogICAgPj4gLSBNb2JpbGUgU3Vic2NyaWJlciBOdW1iZXIg
KE1TSVNETikgc2VlbXMgbm90IHRvIGJlIHNwZWNpZmllZA0KICAgID4+DQogICAgPj4gMi4gSXMg
aXQgaW50ZW5kZWQgdG8gaGF2ZSBhbiBJTUVJIGlkZW50aWZpZXIgdHlwZT8gIFRoZSBpbnRyb2R1
Y3Rpb24NCiAgICA+PiBtZW50aW9ucyBhbiBJTUVJIHR5cGUsIGJ1dCB0aGVyZSBpcyBubyBzcGVj
aWZpY2F0aW9uIGZvciBpdCwgbm9yIGlzDQogICAgPj4gdGhlcmUgYW4gaWRlbnRpZmllciB0eXBl
IG51bWJlciBhc3NpZ25lZCBmb3IgaXQuDQogICAgPj4NCiAgICA+PiAgICAuLi4gdHlwZXMgZm9y
IElNU0kNCiAgICA+PiAgICBbVGhyZWVHUFAtSURTXSwgUC1UTVNJIFtUaHJlZUdQUC1JRFNdLCBJ
TUVJIFtUaHJlZUdQUC1JRFNdLCBhbmQNCiAgICA+PiBHVVRJDQogICAgPj4gICAgW1RocmVlR1BQ
LUlEU10uDQogICAgPj4NCiAgICA+PiBJbml0aWFsbHkgSSBzdXNwZWN0ZWQgaXQgd2FzIGl0IHdh
cyBwcmVzZW50IGluIGFuIGVhcmxpZXIgcmV2aXNpb24NCiAgICA+PiBhbmQNCiAgICA+PiB0aGVu
IGxhdGVyIGRlbGV0ZWQgd2l0aG91dCB0aGlzIHJlZmVyZW5jZSBiZWluZyB1cGRhdGVkLiAgQnV0
IGFsbA0KICAgID4+IHZlcnNpb25zIG9mIGRyYWZ0LWlldGYtZG1tLTQyODNtbmlkcyBhbmQgaXRz
IHByZWRlY2Vzc29yDQogICAgPj4gZHJhZnQtcGVya2lucy1kbW0tNDI4M21uaWRzIG1lbnRpb24g
SU1FSSBpbiB0aGlzIHdheSBhcyBvbmUNCiAgICA+PiBpZGVudGlmaWVyDQogICAgPj4gdHlwZSwg
YnV0IG5vbmUgc3BlY2lmeSBpdCBpbiBhbnkgd2F5LiAgVGhlIG9ubHkgZGlzY3Vzc2lvbiBJIGNh
biBmaW5kDQogICAgPj4gb24gdGhlIERNTSBtYWlsaW5nIGxpc3Qgb2YgSU1FSSBpczoNCiAgICA+
Pg0KICAgID4+ICAgIA0KICAgID4+IGh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9t
c2cvZG1tL3BObXRhcTYtSk9RNFJ1WHlfRDdaYzJKZ3ZZay8/cWlkDQogICAgPj4gPWQyOTU3NWY3
NjdjZTY3YTFlNjdhNzc2NzAwOGVlNmFmDQogICAgPj4NCiAgICA+PiAgICAgRnJvbTogTWFyY28g
TGllYnNjaCA8TWFyY28uTGllYnNjaEBuZWNsYWIuZXU+DQogICAgPj4gICAgIFRvOiBETU0NCiAg
ICA+PiAgICAgRGF0ZTogV2VkLCAxMCBTZXB0ZW1iZXIgMjAxNCAxMzoyOSBVVEMNCiAgICA+PiAg
ICAgUmU6IFtETU1dIHJlZ2FyZGluZyB0aGUgcmUtY2hhcnRlcmluZy4uDQogICAgPj4NCiAgICA+
PiAgICAgSXQgc2VlbXMgdGhlIE1OSUQgaXMgc29tZWhvdyBvdmVybG9hZGVkIHRvIGNhcnJ5IGJv
dGgsDQogICAgPj4gbm9kZS1zcGVjaWZpYw0KICAgID4+ICAgICBJRHMsIGUuZy4gTUFDLCBhcyB3
ZWxsIGFzIHN1YnNjcmliZXIgSURzLCB3aGljaCBpcyB0aGUgSU1TSS4NCiAgICA+PiAgICAgVGhl
cmUgbWF5IGJlIHZhbHVlIGluIGFkZGluZyB0aGUgSU1FSSB0byB0aGUgbGlzdCBvZiBwb3NzaWJs
ZQ0KICAgID4+IHR5cGVzIG9mDQogICAgPj4gICAgIG5vZGUtc3BlY2lmaWMgSURzLg0KICAgID4+
DQogICAgPj4gRWl0aGVyIHRoZSBwcmVzZW5jZSBvZiBJTUVJIGluIHRoaXMgbGlzdCBpcyBhIHNp
bXBsZSBtaXN0YWtlIHRoYXQgaGFzDQogICAgPj4gcGVyc2lzdGVkIGluIGFsbCB2ZXJzaW9ucyBv
ZiB0aGUgZHJhZnQsIG9yIHNwZWNpZnlpbmcgSU1FSSBoYXMgYWx3YXlzDQogICAgPj4gYmVlbiBp
bnRlbmRlZCBidXQgaGFzIGFsd2F5cyBiZWVuIG92ZXJsb29rZWQuDQogICAgPj4NCiAgICA+PiAz
LiBUaGUgZGVmaW5pdGlvbiBvZiBpZGVudGlmaWVyIHR5cGVzIGZvciBib3RoIEVVSS00OCBhbmQg
RVVJLTY0DQogICAgPj4gc3VnZ2VzdHMgdGhhdCBpdCBtaWdodCBiZSBkZXNpcmFibGUgdG8gZGVm
aW5lIGFuIGlkZW50aWZpZXIgdHlwZSBmb3INCiAgICA+PiBhcmJpdHJhcnkgaGFyZHdhcmUgKGxp
bmstbGV2ZWwpIGFkZHJlc3Nlcy4gIEl0IHNlZW1zIHRoYXQgdGhlIG5hdHVyYWwNCiAgICA+PiBk
aWZmZXJlbnRpYXRvciBmb3IgdGhhdCBwdXJwb3NlIGlzIHRoZSAiaGFyZHdhcmUgdHlwZSIgdXNl
ZCBpbiBBUlAsDQogICAgPj4gc28NCiAgICA+PiBhIEVVSS00OCBhZGRyZXNzIHdvdWxkIGJlIHJl
cHJlc2VudGVkIGFzDQogICAgPj4NCiAgICA+PiAgICAgTU4gaWRlbnRpZmllciB0eXBlIChvbmUg
b2N0ZXQpIDUgKHNheSkNCiAgICA+PiAgICAgaGFyZHdhcmUgdHlwZSAodHdvIG9jdGV0cykgMQ0K
ICAgID4+ICAgICBFVUktNDggKHNpeCBvY3RldHMpDQogICAgPj4NCiAgICA+PiBhbmQgYW4gRVVJ
LTY0IHNpbWlsYXJseSwgd2l0aCBoYXJkd2FyZSB0eXBlIDI3Lg0KICAgID4+DQogICAgPj4gQWx0
aG91Z2ggd2l0aCBvbmx5IHR3byBzdWJ0eXBlcyBpbiBjb21tb24gdXNlLCBnZW5lcmFsaXppbmcg
dGhpcw0KICAgID4+IG1pZ2h0DQogICAgPj4gbm90IGJlIHdvcnRoIHRoZSBlZmZvcnQuDQogICAg
Pj4NCiAgICA+PiA0LiBTZXZlcmFsIG9mIHRoZSBpZGVudGlmaWVyIHR5cGVzIGNhbiBiZSByZXBy
ZXNlbnRlZCBhcyBVUk5zOg0KICAgID4+DQogICAgPj4gLSBJTUVJIGNhbiBiZSByZXByZXNlbnRl
ZCBhcyBhIFVSTiBhcyB1cm46Z3NtYTppbWVpOi4uLg0KICAgID4+IC0gYWxsIG9mIHRoZSBSRklE
IHR5cGVzIGhhdmUgYSBVUk4gcmVwcmVzZW50YXRpb24gKGNhbGxlZCB0aGUNCiAgICA+PiAgICJw
dXJlLWlkZW50aXR5IFVSSSIgaW4gdGhlIFJGSUQgc3BlY2lmaWNhdGlvbnMpLCB3aGljaCBzdGFy
dHMNCiAgICA+PiAgIHVybjplcGM6aWQ6Li4uDQogICAgPj4NCiAgICA+PiBTaW5jZSBhbGwgVVJO
IHR5cGVzIGFyZSBlbnN1cmVkIG9mIGJlaW5nIHVuaXF1ZSBhbmQgcGVyc2lzdGVudCwgaXQNCiAg
ICA+PiBzZWVtcyB0aGF0IHdlIGNvdWxkIGRlZmluZSBhIE1OSUQgdHlwZSBmb3IgVVJOcyBnZW5l
cmFsbHksIGFuZCB0aGVuDQogICAgPj4gYW55IFJGSUQgVVJJIG9yIGFuIElNRUkgKGFzIGEgVVJO
KSBjb3VsZCBiZSB1c2VkIGFzIGEgdmFsdWUgb2YgdGhhdA0KICAgID4+IHR5cGUuDQogICAgPj4N
CiAgICA+PiBJZiB0aGlzIGlkZWEgaXMgYWRvcHRlZCwgaXQgc2VlbXMgdGhhdCB0aGUgb3RoZXIg
M0dQUCB0eXBlcyAoSU1TSSwNCiAgICA+PiBQLVRNU0ksIGFuZCBHVVRJKSBzaG91bGQgYmUgZ2l2
ZW4gZGVmaW5lZCBlbmNvZGluZ3MgYXMgVVJOcyBpbiBuZXcNCiAgICA+PiBzdWItbmFtZXNwYWNl
cyBvZiB0aGUgImdzbWEiIFVSTiBuYW1lc3BhY2UsIHRvIHBhcmFsbGVsIHRoZSBlbmNvZGluZw0K
ICAgID4+IG9mIElNRUlzIGRlZmluZWQgaW4gUkZDIDcyNTQuDQogICAgPj4NCiAgICA+PiBUaGlz
IGNvbnNvbGlkYXRpb24gY291bGQgYmUgc2lnbmlmaWNhbnRseSBiZW5lZmljaWFsLiAgSXQgYWxs
b3dzIE1OSUQNCiAgICA+PiB0byB1c2UgYW55IFVSTiBzY2hlbWUgYXMgYW4gaWRlbnRpZmllci4g
IEl0IHJlZHVjZXMgdGhlIHRocmVlDQogICAgPj4gZGlmZmVyZW50IFJGSUQgcmVwcmVzZW50YXRp
b25zIHRvIG9uZS4gIEl0IGluY29ycG9yYXRlcyBhbnkgZnV0dXJlDQogICAgPj4gZXhwYW5zaW9u
IG9mIFJGSUQgc2NoZW1lcyAoYmVjYXVzZSBhbGwgc2NoZW1lcyB3aWxsIGhhdmUgYQ0KICAgID4+
IHB1cmUtaWRlbnRpdHkgVVJOIHJlcHJlc2VudGF0aW9uKS4gIEEgZGlzYWR2YW50YWdlIGlzIHRo
YXQgdGhlIFVSTg0KICAgID4+IGVuY29kaW5ncyBhcmUgbG9uZywgYnV0IHRoZSBzZWN1cml0eSBj
b25zaWRlcmF0aW9ucyBzZWN0aW9uIHN0YXRlcw0KICAgID4+IHRoYXQgTU5JRHMgYXJlIHVzZWQg
b25seSBvbiB0aGUgZmlyc3QgcmVnaXN0cmF0aW9uIGF0IHRoZSBob21lIGFnZW50LA0KICAgID4+
IHNvIHRoZXJlIGlzbid0IG11Y2ggbmVlZCBmb3IgYnJldml0eS4NCiAgICA+Pg0KICAgID4+IFNp
bWlsYXJseSwgdGhpcyBhcHByb2FjaCBpbmNvcnBvcmF0ZXMgYW55IGZ1dHVyZSBleHBhbnNpb24g
b2YgbW9iaWxlDQogICAgPj4gaWRlbnRpZmllcnMgdGhhdCBHU01BIGRlY2lkZXMgdG8gZGVmaW5l
LCBhcyBsb25nIGFzIEdTTUEgcHJvdmlkZXMgYQ0KICAgID4+IFVSTiByZXByZXNlbnRhdGlvbiBm
b3IgaXQuDQogICAgPj4NCiAgICA+PiBUaGUgbW9zdCBzaWduaWZpY2FudCBkaXNhZHZhbnRhZ2Ug
aXMgdGhhdCBzb21lIFVSTiBzY2hlbWVzIGFsbG93DQogICAgPj4gc2V2ZXJhbCBjaGFyYWN0ZXIg
c3RyaW5ncyB0byAibWVhbiIgdGhlIHNhbWUgVVJOLiAgSW4gbW9zdCBVUk4NCiAgICA+PiBzY2hl
bWVzLCB0aGUgYWxsb3dlZCB2YXJpYXRpb24gaXMgbGltaXRlZCB0byB0aGUgY2FzZSBvZiBsZXR0
ZXJzLCBhbmQNCiAgICA+PiB0aGUgY29tbW9uIGNvbnZlbnRpb24gaXMgdG8gYWx3YXlzIHVzZSBs
b3dlci1jYXNlIHdoZW4gdGhlcmUgaXMgYQ0KICAgID4+IGNob2ljZSwgbGVhZGluZyB0byBhIHVu
aXF1ZSBjb252ZW50aW9uYWwgY2Fub25pY2FsIGZvcm0gZm9yIHRoZSBVUk4uDQogICAgPj4NCiAg
ICA+PiA1LiBSZWdhcmRpbmcgdGhlIGVuY29kaW5nIG9mIGEgc3RyaW5nIG9mIGRpZ2l0cyBpbnRv
IG9jdGV0cywgaXQgaXMNCiAgICA+PiBzdGF0ZWQgdGhhdCAiVGhlIGxhc3QgZGlnaXQgTVVTVCBi
ZSB6ZXJvIHBhZGRlZCwgaWYgbmVlZGVkLCBmb3IgZnVsbA0KICAgID4+IG9jdGV0IHNpemUuIiAg
VGhpcyBzZWVtcyB2ZXJ5IHVud2lzZSB1bmxlc3MgdGhlcmUgaXMgYSAzR1BQIGRlY3JlZQ0KICAg
ID4+IHRoYXQgaWYgYSB6ZXJvIGlzIGFwcGVuZGVkIHRvIGEgdmFsaWQgSU1TSSwgdGhlIHJlc3Vs
dGluZyBzdHJpbmcgaXMNCiAgICA+PiBuZXZlciBhIHZhbGlkIElNU0kuICBJbnN0ZWFkLCBJIHdv
dWxkIHNwZWNpZnkgdGhhdCBwYWRkaW5nIGlzIGJ5DQogICAgPj4gZmlsbGluZyB0aGUgbG93LW9y
ZGVyIDQgYml0cyBvZiB0aGUgZmluYWwgb2N0ZXQgd2l0aCAweEYuICBUaGF0DQogICAgPj4gZW5z
dXJlcyB0aGF0IHRoZSBlbmNvZGluZyBjYW4gYmUgdW5pcXVlbHkgZGVjb2RlZCBpbnRvIGFuIElN
U0kuDQogICAgPj4NCiAgICA+PiA2LiBUaGVyZSBhcmUgZm91ciB0eXBlcyBvZiBEVUlEIHNwZWNp
ZmllZCwgZWFjaCB3aXRoIGEgZGlzdGluY3QgTU5JRA0KICAgID4+IHZhbHVlLiAgSG93ZXZlciwg
RFVJRHMgY29udGFpbiBhbiBpbml0aWFsIHR3by1vY3RldCB0eXBlIGZpZWxkIHdoaWNoDQogICAg
Pj4gZGlzdGluZ3Vpc2hlcyB0aGUgdmFyaW91cyB0eXBlcyBvZiBEVUlELCBzbyBwcm92aWRpbmcg
dGhlbSB3aXRoDQogICAgPj4gZGlzdGluY3QgTU5JRCB2YWx1ZXMgaXMgcmVkdW5kYW50Lg0KICAg
ID4+DQogICAgPj4gRGlzdGluZ3Vpc2hpbmcgdGhlIHR5cGVzIGFuZCBhbGxvd2luZyBvbmx5IGZv
dXIgb2YgdGhlbSB0byBiZSB1c2VkIGFzDQogICAgPj4gTU5JRHMgc2VlbXMgdG8gYmUgY29udHJh
cnkgdG8gdGhlIHBoaWxvc29waHkgb2YgRFVJRCBjb25zdHJ1Y3Rpb24NCiAgICA+PiAoUkZDDQog
ICAgPj4gMzMxNSBzZWN0aW9uIDkpOg0KICAgID4+DQogICAgPj4gICAgQ2xpZW50cyBhbmQgc2Vy
dmVycyBNVVNUIHRyZWF0IERVSURzIGFzIG9wYXF1ZSB2YWx1ZXMgYW5kIE1VU1QNCiAgICA+PiBv
bmx5DQogICAgPj4gICAgY29tcGFyZSBEVUlEcyBmb3IgZXF1YWxpdHkuICBDbGllbnRzIGFuZCBz
ZXJ2ZXJzIE1VU1QgTk9UIGluIGFueQ0KICAgID4+ICAgIG90aGVyIHdheSBpbnRlcnByZXQgRFVJ
RHMuICBDbGllbnRzIGFuZCBzZXJ2ZXJzIE1VU1QgTk9UIHJlc3RyaWN0DQogICAgPj4gICAgRFVJ
RHMgdG8gdGhlIHR5cGVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudCwgYXMgYWRkaXRpb25hbCBE
VUlEDQogICAgPj4gdHlwZXMNCiAgICA+PiAgICBtYXkgYmUgZGVmaW5lZCBpbiB0aGUgZnV0dXJl
Lg0KICAgID4+DQogICAgPj4gT2YgY291cnNlLCBNTklEIGlzbid0IGEgREhDUCBvcGVyYXRpb24s
IHNvIGl0IGlzbid0IHN1YmplY3QgdG8gdGhvc2UNCiAgICA+PiByZXF1aXJlbWVudHMsIGJ1dCBJ
IGV4cGVjdCB0aGF0IGRldmljZXMgd2lsbCB1c2UgdGhlIHNhbWUgRFVJRCBmb3INCiAgICA+PiBi
b3RoIG1vYmlsZSBpZGVudGlmaWNhdGlvbiwgYW5kIHdlIGRvbid0IHdhbnQgbW9iaWxlIGlkZW50
aWZpY2F0aW9uDQogICAgPj4gdG8NCiAgICA+PiByZXN0cmljdCBmdXR1cmUgZGV2ZWxvcG1lbnRz
IG9mIERIQ1AuDQogICAgPj4NCiAgICA+PiBJIHRoaW5rIHRoaXMgc3BlY2lmaWNhdGlvbiBtdXN0
IHRyZWF0IERVSURzIGFzIG9wYXF1ZSBhbmQgdXNlIG9ubHkNCiAgICA+PiBvbmUNCiAgICA+PiBN
TklEIHR5cGUgdGhhdCBhbGxvd3MgYWxsIHR5cGVzIG9mIERVSURzIGFzIHZhbHVlcy4NCiAgICA+
Pg0KICAgID4+IEVkaXRvcmlhbCBpc3N1ZXM6DQogICAgPj4NCiAgICA+PiBBYnN0cmFjdA0KICAg
ID4+DQogICAgPj4gICAgQWRkaXRpb25hbCBJZGVudGlmaWVyIFR5cGVzIGFyZSBwcm9wb3NlZCBm
b3IgdXNlIHdpdGggdGhlIE1vYmlsZQ0KICAgID4+IE5vZGUNCiAgICA+PiAgICBJZGVudGlmaWVy
IE9wdGlvbiBmb3IgSVB2NiAoUkZDIDQyODMpLg0KICAgID4+DQogICAgPj4gcy9wcm9wb3NlZC9k
ZWZpbmVkLw0KICAgID4+IFRoaXMgZG9jdW1lbnQgd2lsbCBkZWZpbmUgdGhlIG5ldyB0eXBlcyAo
b25jZSBpdCBpcyBhcHByb3ZlZCkhDQogICAgPj4NCiAgICA+PiAxLiAgSW50cm9kdWN0aW9uDQog
ICAgPj4NCiAgICA+PiAgICAuLi4gdHlwZXMgZm9yIElNU0kNCiAgICA+PiAgICBbVGhyZWVHUFAt
SURTXSwgUC1UTVNJIFtUaHJlZUdQUC1JRFNdLCBJTUVJIFtUaHJlZUdQUC1JRFNdLCBhbmQNCiAg
ICA+PiBHVVRJDQogICAgPj4gICAgW1RocmVlR1BQLUlEU10uDQogICAgPj4NCiAgICA+PiBUaGVy
ZSBpcyBubyBkZXNjcmlwdGlvbiBvZiBQLVRNU0kgaWRlbnRpZmllcnMsIGFsdGhvdWdoIGl0IGlz
DQogICAgPj4gYXNzaWduZWQNCiAgICA+PiBpZGVudGlmaWVyIHR5cGUgNC4NCiAgICA+Pg0KICAg
ID4+IFRoZXJlIGlzIG5vIGRlc2NyaXB0aW9uIG9mIEdVVEkgaWRlbnRpZmllcnMsIGFsdGhvdWdo
IGl0IGlzIGFzc2lnbmVkDQogICAgPj4gaWRlbnRpZmllciB0eXBlIDcuDQogICAgPj4NCiAgICA+
PiAzLiAgTmV3IE1vYmlsZSBOb2RlIElkZW50aWZpZXIgVHlwZXMNCiAgICA+Pg0KICAgID4+ICAg
IFRoZSBmb2xsb3dpbmcgdHlwZXMgb2YgaWRlbnRpZmllcnMgYXJlIGNvbW1vbmx5IHVzZWQgdG8g
aWRlbnRpZnkNCiAgICA+PiAgICBtb2JpbGUgbm9kZXMuICBGb3IgZWFjaCB0eXBlLCByZWZlcmVu
Y2VzIGFyZSBwcm92aWRlZCB3aXRoIGZ1bGwNCiAgICA+PiAgICBkZXRhaWxzIG9uIHRoZSBmb3Jt
YXQgb2YgdGhlIHR5cGUgb2YgaWRlbnRpZmllci4NCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcg
RGF0YSBzdGFuZGFyZCBwcm9tb3RlZCBieSBFbGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAg
ICA+PiAgICAoYWJicmV2aWF0ZWQgRVBDKSBzdXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3Rl
bXMgb3Igc2NoZW1lcw0KICAgID4+ICAgIGluY2x1ZGluZw0KICAgID4+DQogICAgPj4gICAgbyAg
UkZJRC1HSUQgKEdsb2JhbCBJZGVudGlmaWVyKSwNCiAgICA+PiAgICBvICBSRklELVNHVElOIChT
ZXJpYWxpemVkIEdsb2JhbCBUcmFkZSBJdGVtIE51bWJlciksDQogICAgPj4gICAgbyAgUkZJRC1T
U0NDIChTZXJpYWwgU2hpcHBpbmcgQ29udGFpbmVyKSwNCiAgICA+PiAgICBvICBSRklELVNHTE4g
KEdsb2JhbCBMb2NhdGlvbiBOdW1iZXIpLA0KICAgID4+ICAgIG8gIFJGSUQtR1JBSSAoR2xvYmFs
IFJldHVybmFibGUgQXNzZXQgSWRlbnRpZmllciksDQogICAgPj4gICAgbyAgUkZJRC1ET0QgKERl
cGFydG1lbnQgb2YgRGVmZW5zZSBJRCksIGFuZA0KICAgID4+ICAgIG8gIFJGSUQtR0lBSSAoR2xv
YmFsIEluZGl2aWR1YWwgQXNzZXQgSWRlbnRpZmllcikuDQogICAgPj4NCiAgICA+PiAgICBGb3Ig
ZWFjaCBSRklEIHNjaGVtZSBleGNlcHQgR0lELCB0aGVyZSBhcmUgdHdvIHZhcmlhdGlvbnM6IGEN
CiAgICA+PiA2NC1iaXQNCiAgICA+PiAgICBzY2hlbWUgKGZvciBleGFtcGxlLCBTR0xOLTY0KSBh
bmQgYSA5Ni1iaXQgc2NoZW1lIChTR0xOLTk2KS4gIEdJRA0KICAgID4+IGhhcw0KICAgID4+ICAg
IG9ubHkgYSA5Ni1iaXQgc2NoZW1lLiAgV2l0aGluIGVhY2ggc2NoZW1lLCBhbiBFUEMgaWRlbnRp
ZmllciBjYW4NCiAgICA+PiBiZQ0KICAgID4+ICAgIHJlcHJlc2VudGVkIGluIGEgYmluYXJ5IGZv
cm0gb3Igb3RoZXIgZm9ybXMgc3VjaCBhcyBVUkkuDQogICAgPj4NCiAgICA+PiAgICBUaGUgZm9s
bG93aW5nIGxpc3QgaW5jbHVkZXMgdGhlIGFib3ZlIFJGSUQgdHlwZXMgYXMgd2VsbCBhcw0KICAg
ID4+IHZhcmlvdXMNCiAgICA+PiAgICBvdGhlciBjb21tb24gaWRlbnRpZmllcnMgYW5kIHNldmVy
YWwgZGlmZmVyZW50IHR5cGVzIG9mIERVSURzLg0KICAgID4+DQogICAgPj4gVGhlIG9yZ2FuaXph
dGlvbiBvZiB0aGUgdGV4dCBoZXJlIHNlZW1zIHRvIGJlIHBvb3IgLS0gc2VjdGlvbiAzDQogICAg
Pj4gZW51bWVyYXRlcyB0aGUgbmV3IGlkZW50aWZpZXIgdHlwZXMsIGJ1dCBtdWNoIG9mIHRoZSB0
ZXh0IGF0IHRoZQ0KICAgID4+IGJlZ2lubmluZyBvZiB0aGUgc2VjdGlvbiBpcyBhYm91dCB0aGUg
UkZJRC1FUEMgc2V0IG9mIHR5cGVzLiAgSXQNCiAgICA+PiBzZWVtcw0KICAgID4+IGxpa2UgYSBi
ZXR0ZXIgb3JnYW5pemF0aW9uIGlzIHRvIHVzZSBqdXN0IHBhcmFncmFwaCAxIGZvbGxvd2VkIGJ5
DQogICAgPj4gdGFibGUgMSwgYW5kIG1vdmUgcGFyYWdyYXBocyAyLTUgaW50byBzZWN0aW9uIDQu
OS4NCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcgRGF0YSBzdGFuZGFyZCBwcm9tb3RlZCBieSBF
bGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAgICA+PiAgICAoYWJicmV2aWF0ZWQgRVBDKSBz
dXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3RlbXMgb3Igc2NoZW1lcw0KICAgID4+ICAgIGlu
Y2x1ZGluZw0KICAgID4+DQogICAgPj4gVGhlIHRleHQgaXMgdXNpbmcgIlRhZyBEYXRhIiwgIkVQ
QyIsIGFuZCAiUkZJRCIgaW4gYSB3YXkgdGhhdCBpcw0KICAgID4+IGludGVydHdpbmVkIGJ1dCBu
b3QgZXhwbGFpbmVkLiAgSSBjYW4gc2VlIHRoYXQgaXQgbWlnaHQgYmUgdXNlZnVsIHRvDQogICAg
Pj4gdXNlIGFsbCBvZiB0aGUgdGVybXMgaWYgdGhleSBjb21tb25seSB1c2VkIGluIHRoZSBmaWVs
ZCAoZG9uJ3QgZm9yZ2V0DQogICAgPj4gdG8gbWFrZSB0aGVtIGtleXdvcmRzIGZvciB0aGUgUkZD
ISksIGJ1dCB5b3UgbmVlZCB0byBleHBsYWluIHRoZWlyDQogICAgPj4gY29ubmVjdGlvbiBhbmQg
ZGlzdGluY3Rpb24gdG8gdGhlIHJlYWRlciBvciBtYWtlIGl0IGNsZWFyIHRoYXQgdGhlDQogICAg
Pj4gcmVhZGVyIGRvZXMgbm90IG5lZWQgdG8gdW5kZXJzdGFuZCB0aGUgZGlmZmVyZW5jZXMgYW1v
bmcgdGhlIHRlcm1zLg0KICAgID4+IEUuZy4sIHRoaXMgZm9ybXVsYXRpb24gdGllcyBhbGwgdGhy
ZWUgdGVybXMgdG9nZXRoZXINCiAgICA+Pg0KICAgID4+ICAgIFRoZSBUYWcgRGF0YSBzdGFuZGFy
ZCBwcm9tb3RlZCBieSBFbGVjdHJvbmljIFByb2R1Y3QgQ29kZShUTSkNCiAgICA+PiAgICAoYWJi
cmV2aWF0ZWQgRVBDKSBzdXBwb3J0cyBzZXZlcmFsIGVuY29kaW5nIHN5c3RlbXMgb3Igc2NoZW1l
cw0KICAgID4+ICAgIHdoaWNoIGFyZSBjb21tb25seSB1c2VkIGluIFJGSUQgKHJhZGlvLWZyZXF1
ZW5jeSBpZGVudGlmaWNhdGlvbikNCiAgICA+PiAgICBhcHBsaWNhdGlvbnMsIGluY2x1ZGluZw0K
ICAgID4+DQogICAgPj4gLS0NCiAgICA+Pg0KICAgID4+ICAgIEZvciBlYWNoIFJGSUQgc2NoZW1l
IGV4Y2VwdCBHSUQsIHRoZXJlIGFyZSB0d28gdmFyaWF0aW9uczogYQ0KICAgID4+IDY0LWJpdA0K
ICAgID4+ICAgIHNjaGVtZSAoZm9yIGV4YW1wbGUsIFNHTE4tNjQpIGFuZCBhIDk2LWJpdCBzY2hl
bWUgKFNHTE4tOTYpLiAgR0lEDQogICAgPj4gaGFzDQogICAgPj4gICAgb25seSBhIDk2LWJpdCBz
Y2hlbWUuICBXaXRoaW4gZWFjaCBzY2hlbWUsIGFuIEVQQyBpZGVudGlmaWVyIGNhbg0KICAgID4+
IGJlDQogICAgPj4gICAgcmVwcmVzZW50ZWQgaW4gYSBiaW5hcnkgZm9ybSBvciBvdGhlciBmb3Jt
cyBzdWNoIGFzIFVSSS4NCiAgICA+Pg0KICAgID4+IFRoZSB0ZXh0IHVzZXMgInNjaGVtZSIgdG8g
bWVhbiB0aGUgZGlzdGluY3Rpb24gYmV0d2VlbiBlbmNvZGluZw0KICAgID4+IHN5c3RlbXMgKEdJ
RCwgU0dUSU4sIGV0Yy4pIGFuZCBhbmQgYWxzbyB0byBtZWFuIHRoZSBkaXN0aW5jdGlvbg0KICAg
ID4+IGJldHdlZW4gdGhlIDY0LWJpdCBhbmQgOTYtYml0IHZhcmlhdGlvbnMuICBUaGlzIGFtYmln
dWl0eSBpcyB1bndpc2UuDQogICAgPj4gSXQgbWF0dGVycyBoZXJlLCBiZWNhdXNlIHlvdSBzYXkg
IndpdGhpbiBlYWNoIHNjaGVtZSAuLi4gY2FuIGJlDQogICAgPj4gcmVwcmVzZW50ZWQgaW4gYSBi
aW5hcnkgZm9ybSBvciAuLi4gVVJJIi4gIFdoaWNoIG1lYW5pbmcgb2YgInNjaGVtZSINCiAgICA+
PiBhcmUgeW91IHVzaW5nIGhlcmU/ICBJIHRob3VnaHQgeW91IG1lYW50IHRoZSBzZWNvbmQgbWVh
bmluZyB3aGVuIEkNCiAgICA+PiBmaXJzdCByZWFkIHRoZSBwYXJhZ3JhcGgsIGJ1dCBhZnRlciBy
ZWFkaW5nIGV4dGVybmFsIGRvY3VtZW50cyBhYm91dA0KICAgID4+IEVQQywgSSBub3cgdW5kZXJz
dGFuZCB0aGF0IHRoYXQgbGFzdCBzZW50ZW5jZSB1c2VzICJzY2hlbWUiIHRvIGluIHRoZQ0KICAg
ID4+IGZpcnN0IHNlbnNlLg0KICAgID4+DQogICAgPj4gWW91IG5lZWQgdG8gYmUgY2xlYXJlciBo
ZXJlIHRoYXQgdGhlcmUgYXJlIHRocmVlIHJlcHJlc2VudGF0aW9ucw0KICAgID4+IHVzZWQsDQog
ICAgPj4gNjQtYml0IGJpbmFyeSwgOTYtYml0IGJpbmFyeSwgYW5kIFVSSSAoVVJOLCBhY3R1YWxs
eSksIGFuZA0KICAgID4+IHJlcHJlc2VudGF0aW9uIGlzIG9ydGhvZ29uYWwgdG8gdGhlIHNldmVu
IFJGSUQgc2NoZW1lcywgd2l0aCB0aGUNCiAgICA+PiBleGNlcHRpb24gdGhhdCBSRklELUdJRCBk
b2VzIG5vdCBoYXZlIGEgOTYtYml0IGJpbmFyeSByZXByZXNlbnRhdGlvbi4NCiAgICA+Pg0KICAg
ID4+IEknbSBhc3N1bWluZyB0aGF0IHRoZSBUYWcgRGF0YSBzdGFuZGFyZCB1bmFtYmlndW91c2x5
IGRlZmluZXMgdGhlDQogICAgPj4gc2VyaWFsaXphdGlvbiBvZiB0aGUgYmluYXJ5IHJlcHJlc2Vu
dGF0aW9ucyBhcyBhIHNlcXVlbmNlIG9mIG9jdGV0cy4NCiAgICA+PiBJZiBpdCBkb2VzIG5vdCwg
dGhpcyBkb2N1bWVudCBNVVNUIGRvIHRoYXQsIG9yIHlvdSB3aWxsIGhhdmUgYW4NCiAgICA+PiBl
bmRsZXNzIG5pZ2h0bWFyZSBvZiBieXRlLW9yZGVyIHByb2JsZW1zLg0KICAgID4+DQogICAgPj4g
NC4gIERlc2NyaXB0aW9ucyBvZiBNTklEIHR5cGVzDQogICAgPj4NCiAgICA+PiBJZGVudGlmaWVy
IG93bmVyc2hpcCBpcyBhIGdlbmVyYWwgY29uY2VybiAtLSBpdCdzIHdvcnRoIG1lbnRpb25pbmcN
CiAgICA+PiBmb3INCiAgICA+PiBlYWNoIHR5cGUgb2YgaWRlbnRpZmllciB3aGVyZSB0aGUgYXNz
aWduZXIgb2YgdGhlIGlkZW50aWZpZXIgb2J0YWlucw0KICAgID4+IGRlbGVnYXRpb24uICBGb3Ig
YW4gRVVJLCBJIGV4cGVjdCB0aGUgcmVhZGVyIHdpbGwgYXNzdW1lIHRoYXQgaXQncyBhbg0KICAg
ID4+IEVVSSBhc3NpZ25lZCB0byB0aGUgZGV2aWNlIHVuZGVyIElFRUUgcnVsZXMsIGFuZCBzaW1p
bGFybHkgZm9yIFJGSUQNCiAgICA+PiBhbmQgM0dQUCBpZGVudGlmaWVycy4gIEJ1dCBmb3IgRFVJ
RCBpZGVudGlmaWVycywgaXQncyBsZXNzIGNsZWFyLg0KICAgID4+IEknbQ0KICAgID4+IGd1ZXNz
aW5nIHRoYXQgdGhlIERVSUQgaXMgb25lIHRoYXQgaXMsIG9yIGNvdWxkIGJlLCB1c2VkIGJ5IHRo
ZQ0KICAgID4+IGRldmljZQ0KICAgID4+IGZvciBESENQIHB1cnBvc2VzLiAgRm9yIElQdjYgYWRk
cmVzc2VzLCBpdCdzIGV2ZW4gbGVzcyBjbGVhciwgc2luY2UNCiAgICA+PiB0aGUgSVB2NiBhcmNo
aXRlY3R1cmUgZG9lc24ndCBhc3N1bWUgdGhhdCB0aGUgYXNzb2NpYXRpb24gb2YNCiAgICA+PiBh
ZGRyZXNzZXMNCiAgICA+PiB3aXRoIGRldmljZXMgaXMgcGVybWFuZW50Lg0KICAgID4+DQogICAg
Pj4gNC4xLiAgRGVzY3JpcHRpb24gb2YgdGhlIElQdjYgYWRkcmVzcyB0eXBlDQogICAgPj4NCiAg
ICA+PiBJdCB3b3VsZCBiZSBnb29kIGlmIHRoZSBkb2N1bWVudCBkZXNjcmliZWQgd2hhdCB0aGUg
c2VtYW50aWNzIG9mIHRoaXMNCiAgICA+PiBJRCBhcmUuICBZZXMsIGl0J3MgYSB1bmljYXN0IElQ
djYgYWRkcmVzcywgYnV0IHdoYXQgaXMgdGhlIGNvbm5lY3Rpb24NCiAgICA+PiBiZXR3ZWVuIHRo
YXQgYWRkcmVzcyBhbmQgdGhlIGRldmljZT8gIEkgc3VzcGVjdCB0aGUgY29ubmVjdGlvbiBpcw0K
ICAgID4+ICJ0aGUNCiAgICA+PiBkZXZpY2UgaGFzIGJlZW4gY29uZmlndXJlZCB0byBleHBlY3Qg
dGhhdCBpdCB3aWxsIGJlIGFzc2lnbmVkIHRoaXMNCiAgICA+PiBhZGRyZXNzIGFzIGEgbG9uZy10
ZXJtIGludGVyZmFjZSBhZGRyZXNzIiwgYnV0IHRoZXJlIGFyZSBvdGhlcg0KICAgID4+IHBvc3Np
YmlsaXRpZXMuICBFLmcuLCBJIGNhbiBpbWFnaW5lIGEgbW9iaWxlIGNhcnJpZXIgb2J0YWluaW5n
IGEgLzY0DQogICAgPj4gcHJlZml4ICh0aGVyZSBhcmUgcGxlbnR5IG9mIHRoZW0hKSBhbmQgdGhl
biBhc3NpZ25pbmcgYWRkcmVzc2VzIG91dA0KICAgID4+IG9mDQogICAgPj4gaXQgc2ltcGx5IHRv
IGNyZWF0ZSBhIHNlcXVlbmNlIG9mIHVuaXF1ZSBpZGVudGlmaWVycyBmb3IgZGV2aWNlcywgYnV0
DQogICAgPj4gbm90IHVzaW5nIHRob3NlIGFkZHJlc3NlcyBvbiBwYWNrZXRzLg0KICAgID4+DQog
ICAgPj4gVGhlbiBhZ2FpbiwgcGVyaGFwcyB5b3Ugd2FudCB0byBhbGxvdyBmbGV4aWJpbGl0eS4g
IEJ1dCBpbiBhbnkgY2FzZSwNCiAgICA+PiBJDQogICAgPj4gdGhpbmsgeW91IG5lZWQgdG8gc3Bl
Y2lmeSB3aGF0IHRoZSBydWxlcyBhcmUgZm9yIHdoYXQgYWRkcmVzcyBpcw0KICAgID4+IGFzc29j
aWF0ZWQgd2l0aCB3aGF0IGRldmljZS4NCiAgICA+Pg0KICAgID4+IDQuMi4gIERlc2NyaXB0aW9u
IG9mIHRoZSBJTVNJIE1OSUQgdHlwZQ0KICAgID4+DQogICAgPj4gV2hhdCBkb2VzICJpbiBuZXR3
b3JrIG9yZGVyIiBtZWFuIGhlcmU/ICBBcyBmYXIgYXMgSSBrbm93LCB0aGVyZSBpcw0KICAgID4+
IG5vDQogICAgPj4gZGVmaW5lZCAibmV0d29yayBvcmRlciIgZm9yIDQtYml0IHF1YW50aXRpZXMs
IG9ubHkgZm9yIGRpdmlkaW5nDQogICAgPj4gaW50ZWdlcnMgaW50byBvY3RldHMgYW5kIHBsYWNp
bmcgc2VxdWVuY2VzIG9mIGJpdHMgaW50byBvY3RldHMuICBJDQogICAgPj4gYXNzdW1lIHlvdSBt
ZWFuIHRoYXQgaW4gYW55IG9jdGV0LCB0aGUgaGlnaC1vcmRlciA0IGJpdHMgYXJlIHRoZQ0KICAg
ID4+IGZpcnN0DQogICAgPj4gZGlnaXQgYW5kIHRoZSBsb3ctb3JkZXIgNCBiaXRzIGFyZSB0aGUg
c2Vjb25kIGRpZ2l0LCBidXQgSSB0aGluayB5b3UNCiAgICA+PiBuZWVkIHRvIHN0YXRlIHRoYXQg
ZXhwbGljaXRseS4NCiAgICA+Pg0KICAgID4+IDQuMy4gIERlc2NyaXB0aW9uIG9mIHRoZSBFVUkt
NDggYWRkcmVzcyB0eXBlDQogICAgPj4NCiAgICA+PiAgICBUaGUgSUVFRSBFVUktNDggYWRkcmVz
cyBbSUVFRTgwMi1ldWk0OF0gaXMgZW5jb2RlZCBhcyBhIDYgb2N0ZXQNCiAgICA+PiAgICBzdHJp
bmcgY29udGFpbmluZyB0aGUgSUVFRSBFVUktNDggYWRkcmVzcy4NCiAgICA+Pg0KICAgID4+IElz
ICJzdHJpbmciIHRoZSBjb3JyZWN0IHdvcmQsIHRoaXMgbm90IGJlaW5nIGEgc2VxdWVuY2Ugb2YN
CiAgICA+PiBjaGFyYWN0ZXJzPw0KICAgID4+IEkgd291bGQgc2F5ICJzZXF1ZW5jZSBvZiA2IG9j
dGV0cyIgb3Igc2ltcGx5ICJlbmNvZGVkIGFzIDYgb2N0ZXRzIi4NCiAgICA+Pg0KICAgID4+IDQu
OS4gIERlc2NyaXB0aW9uIG9mIHRoZSBSRklEIHR5cGVzDQogICAgPj4NCiAgICA+PiBUaGlzIHNl
Y3Rpb24gbmVlZHMgdG8gYmUgcmV2aXNlZC4gIEl0IHByb3ZpZGVzIGEgbG90IG9mIGRldGFpbCBh
Ym91dA0KICAgID4+IHRoZSBSRklEIHR5cGVzLCBidXQgaXQncyBub3QgZW5vdWdoIGRldGFpbCBm
b3IgYSByZWFkZXIgd2hvIGRvZXNuJ3QNCiAgICA+PiB1bmRlcnN0YW5kIFJGSUQgdG8gbGVhcm4g
aG93IGFueSBwYXJ0aWN1bGFyIFJGSUQgc2NoZW1lIHdvcmtzLiAgRS5nLiwNCiAgICA+PiB0aGUg
Zmlyc3QgcGFyYWdyYXBoIHNheXMgdGhhdCBHSUQgY29udGFpbnMgdGhyZWUgZmllbGRzIGluIHRo
ZSBmaXJzdA0KICAgID4+IHNlbnRlbmNlLCBhbmQgdGhhdCBpdCBjb250YWlucyBmb3VyIGZpZWxk
cyBpbiB0aGUgdGhpcmQgc2VudGVuY2UuDQogICAgPj4gRGVzcGl0ZSB0aGlzLCB0aGUgZGVzY3Jp
cHRpb24gaXNuJ3QgZW5vdWdoIHRvIGFsbG93IHRoZSByZWFkZXIgdG8NCiAgICA+PiBjb25zdHJ1
Y3QgR0lEIGlkZW50aWZpZXJzIG1hbnVhbGx5Lg0KICAgID4+DQogICAgPj4gT24gdGhlIG90aGVy
IGhhbmQsIHJlYWRlcnMgd2hvIGFscmVhZHkgdW5kZXJzdGFuZCB0aGUgUkZJRCBzY2hlbWVzDQog
ICAgPj4gd2lsbCBmaW5kIHRoaXMgdGV4dCByZWR1bmRhbnQuDQogICAgPj4NCiAgICA+PiBJIHRo
aW5rIHRoYXQgYWxtb3N0IGFsbCBvZiB0aGlzIHRleHQgY2FuIGJlIHJlcGxhY2VkIGJ5IHJlZmVy
ZW5jZXMgdG8NCiAgICA+PiB0aGUgRVBDIGRvY3VtZW50cywgc2luY2UgdGhlc2UgaWRlbnRpZmll
cnMgYXJlIG9wYXF1ZSBmcm9tIHRoZSBwb2ludA0KICAgID4+IG9mIHZpZXcgb2YgbW9iaWxlIGlk
ZW50aWZpY2F0aW9uLg0KICAgID4+DQogICAgPj4gNS4gIFNlY3VyaXR5IENvbnNpZGVyYXRpb25z
DQogICAgPj4NCiAgICA+PiBUaGUgYmFzZSBNTklEIHNwZWNpZmljYXRpb24sIFJGQyA0MjgzLCBn
aXZlcyB0aGVzZSBzZWN1cml0eQ0KICAgID4+IGNvbnNpZGVyYXRpb25zIChzZWMgNCksIHdoaWNo
IG91Z2h0IHRvIGJlIHJlZmVyZW5jZWQgYW5kIHByb2JhYmx5DQogICAgPj4gc3VtbWFyaXplZCBp
biB0aGlzIHNlY3Rpb246DQogICAgPj4NCiAgICA+PiAgICBNb3Jlb3ZlciwgTU5JRHMgY29udGFp
bmluZyBzZW5zaXRpdmUgaWRlbnRpZmllcnMgbWlnaHQgb25seSBiZQ0KICAgID4+IHVzZWQNCiAg
ICA+PiAgICBmb3Igc2lnbmFsaW5nIGR1cmluZyBpbml0aWFsIG5ldHdvcmsgZW50cnkuICBTdWJz
ZXF1ZW50IGJpbmRpbmcNCiAgICA+PiAgICB1cGRhdGUgZXhjaGFuZ2VzIG1pZ2h0IHRoZW4gcmVs
eSBvbiBhIHRlbXBvcmFyeSBpZGVudGlmaWVyDQogICAgPj4gYWxsb2NhdGVkDQogICAgPj4gICAg
ZHVyaW5nIHRoZSBpbml0aWFsIG5ldHdvcmsgZW50cnksIHBlcmhhcHMgdXNpbmcgbWVjaGFuaXNt
cyBub3QNCiAgICA+PiAgICBzdGFuZGFyZGl6ZWQgd2l0aGluIHRoZSBJRVRGLiAgTWFuYWdpbmcg
dGhlIGFzc29jaWF0aW9uIGJldHdlZW4NCiAgICA+PiBsb25nLQ0KICAgID4+ICAgIGxpdmVkIGFu
ZCB0ZW1wb3JhcnkgaWRlbnRpZmllcnMgaXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcw0KICAg
ID4+ICAgIGRvY3VtZW50Lg0KICAgID4+DQogICAgPj4gV2hhdCBpcyB0aGUgbWVhbmluZyBvZiB0
aGUgd29yZCAibWlnaHQiIGluIHBhcmFncmFwaCAzPyAgSSBzdXNwZWN0DQogICAgPj4gdGhhdCB0
aGUgcHVycG9zZSBpcyB0byBxdWFsaWZ5IHRoaXMgcGFyYWdyYXBoIHdpdGggIk9uZSB3YXkgdG8N
CiAgICA+PiBhZGRyZXNzDQogICAgPj4gdGhlc2UgdnVsbmVyYWJpbGl0aWVzIGlzIHRvIG9ubHkg
dXNlIE1OSURzIGNvbnRhaW5pbmcgLi4uIi4gIEJ1dCBpZg0KICAgID4+IHRoYXQgaXMgdGhlIG1l
YW5pbmcsIHRoYXQgZXhwYW5kZWQgd29yZGluZyBzaG91bGQgYmUgdXNlZC4gIE90aGVyd2lzZQ0K
ICAgID4+IHRoZSB0ZXh0IHJlYWRzIGFzIGlmIGl0IGlzIGh5cG90aGV0aWNhbC4NCiAgICA+Pg0K
ICAgID4+IFtFTkRdDQogICAgPj4NCiAgICA+Pg0KICAgID4+IF9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fDQogICAgPj4gZG1tIG1haWxpbmcgbGlzdA0KICAg
ID4+IGRtbUBpZXRmLm9yZw0KICAgID4+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vZG1tDQogICAgPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KICAgID4gZG1tIG1haWxpbmcgbGlzdA0KICAgID4gZG1tQGlldGYub3JnDQogICAg
PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2RtbQ0KICAgID4NCiAgICAN
CiAgICANCg0K


From nobody Fri Feb 10 07:30:50 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E769A1293EB; Fri, 10 Feb 2017 07:30:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.588
X-Spam-Level: 
X-Spam-Status: No, score=-4.588 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_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9BLFZ4OUA8K; Fri, 10 Feb 2017 07:30:38 -0800 (PST)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B38111299D4; Fri, 10 Feb 2017 07:30:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486740637; bh=p9ZgACpUrg2s7MwHvTkWa+7J+uZMDVMgyJiL jYlugjU=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=D5ICUNk 1SX3xY2/5Ie5bnRitY3jP2yi6QbTnImgQuldB4JelPtvjRhlHd/Kv/KtrSs8E6vRKpt oimF6fGct7Cn1jiOG2HWkX5HHh88Iu2EJItM4eyr9RWTfdXOu02ZxDQPW/fc0UVmfEU TEygHfFmLCHfRMTu9yIWje7JiwjKpYyRpv0IKzyTi06l6du3Qs443fafZFgU54ue/Em qrKi/St8BqEM9IdEJhldd1YeikvQRH2EQQe+wxWW3XtvLxs7PEe5hab72d7r5JTIxl+ vDJferAZ+Sko/as8XtsK1QVFdcBJU7mxfq77E4Me1Ebss2FY3LvPhwkE3g03NtUUVuw ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=DAiyh7HSTtebU4N3mdop2M8MqUGLKU2O5ZHPIKEH5WxQ7QhNQ/PtiugXjZFMLi76TJKZa8XPhLa8wdFhAf2ixNS9d18ss44oj4Xe2u6U+p/wlKohHaZA561df+OisnyGDYLPXGDIOOpQyuqs+H5DsZ6GOItUh4cNQIS/iAb0vemRRWQjMHRZnrmptzL4Hb6LM4WuYZYCliCsBgySvIkQaNKMc4eC9Nw8xiNFl+4V4rB5SUWw4sL/tur0kekoeLfUGJXABo24Tya7hCPx0E0FTZmJOM+TT69L9JGfLHsrNSzE2/9E/4rvZCnAkNSlmNRtQYoO+cz1Zh4yt0wdlMPeSw==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-curtail.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ccD9A-0001KY-SL; Fri, 10 Feb 2017 10:30:05 -0500
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
To: Suresh Krishnan <suresh.krishnan@ericsson.com>, "Sri Gundavelli (sgundave)" <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net> <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
Date: Fri, 10 Feb 2017 07:30:01 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7b153f6b79f77d65ed61c86f789d10901350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DGG1vBaQ9BYOAoe87tZG9cpglog>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:30:42 -0000

Hello folks,

The last two days have been crammed full with other urgent work 
requirements.  I will respond to these comments today.

Suresh, do you mean to ask if I can submit a revised document before Monday?

Regards,
Charlie P.


On 2/10/2017 6:17 AM, Suresh Krishnan wrote:
> Hi Charlie,
>    I have not yet seen a response to this review. Do you think you will be able to get to this in the next day or two? The document is on the February 16 2017 telechat and I would like to see resolution to these issues in time for the other ADs to ballot.
>
> Thanks
> Suresh
>
> On 2/2/17, 1:10 AM, "Charlie Perkins" <charles.perkins@earthlink.net> wrote:
>
>      Hello Sri,
>      
>      The review was indeed super.  I'll respond sometime in the next few days.
>      
>      Regards,
>      Charlie P.
>      
>      
>      On 2/1/2017 9:09 PM, Sri Gundavelli (sgundave) wrote:
>      > Thank you Dale for a great review.
>      >
>      >
>      > Charlie/Authors - Can you please respond to Dale and address these
>      > comments.
>      >
>      >
>      > Regards
>      > Sri
>      >
>      >
>      > On 1/31/17, 11:34 AM, "dmm on behalf of Dale Worley" <dmm-bounces@ietf.org
>      > on behalf of worley@ariadne.com> wrote:
>      >
>      >> Reviewer: Dale Worley
>      >> Review result: Ready with Issues
>      >>
>      >> I am the assigned Gen-ART reviewer for this draft.  The General Area
>      >> Review Team (Gen-ART) reviews all IETF documents being processed
>      >> by the IESG for the IETF Chair.  Please treat these comments just
>      >> like any other last call comments.
>      >>
>      >> For more information, please see the FAQ at
>      >> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>      >>
>      >> Document:  draft-ietf-dmm-4283mnids-04
>      >> Reviewer:  Dale R. Worley
>      >> Review Date:  31 Jan 2017
>      >> IETF LC End Date:  2 Feb 2017
>      >> IESG Telechat date:  16 Feb 2017
>      >>
>      >> Summary:
>      >>
>      >>        This draft is on the right track but has open issues,
>      >> described
>      >>        in the review.
>      >>
>      >> Technical issues:
>      >>
>      >> 1. The Introduction states
>      >>
>      >>    Other types of identifiers are in
>      >>    common use, and even referenced in RFC 4283.
>      >>
>      >> For the reader's sanity, some sort of accounting needs to be made of
>      >> these "other types of identifiers", especially because each type of
>      >> identifier needs an identifier type number.  The text in 4283 is
>      >>
>      >>    Some examples of identifiers
>      >>    include Network Access Identifier (NAI), Fully Qualified Domain
>      >> Name
>      >>    (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>      >>    Subscriber Number (MSISDN).
>      >>
>      >> Are there any other types "in common use"?
>      >>
>      >> - NAI (type 1) is defined by 4283.
>      >> - Fully Qualified Domain Name (FQDN) seems not to be specified
>      >> - International Mobile Station Identifier (IMSI) (type 3) is defined
>      >> in
>      >>   this draft
>      >> - Mobile Subscriber Number (MSISDN) seems not to be specified
>      >>
>      >> 2. Is it intended to have an IMEI identifier type?  The introduction
>      >> mentions an IMEI type, but there is no specification for it, nor is
>      >> there an identifier type number assigned for it.
>      >>
>      >>    ... types for IMSI
>      >>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>      >> GUTI
>      >>    [ThreeGPP-IDS].
>      >>
>      >> Initially I suspected it was it was present in an earlier revision
>      >> and
>      >> then later deleted without this reference being updated.  But all
>      >> versions of draft-ietf-dmm-4283mnids and its predecessor
>      >> draft-perkins-dmm-4283mnids mention IMEI in this way as one
>      >> identifier
>      >> type, but none specify it in any way.  The only discussion I can find
>      >> on the DMM mailing list of IMEI is:
>      >>
>      >>
>      >> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid
>      >> =d29575f767ce67a1e67a7767008ee6af
>      >>
>      >>     From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>      >>     To: DMM
>      >>     Date: Wed, 10 September 2014 13:29 UTC
>      >>     Re: [DMM] regarding the re-chartering..
>      >>
>      >>     It seems the MNID is somehow overloaded to carry both,
>      >> node-specific
>      >>     IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>      >>     There may be value in adding the IMEI to the list of possible
>      >> types of
>      >>     node-specific IDs.
>      >>
>      >> Either the presence of IMEI in this list is a simple mistake that has
>      >> persisted in all versions of the draft, or specifying IMEI has always
>      >> been intended but has always been overlooked.
>      >>
>      >> 3. The definition of identifier types for both EUI-48 and EUI-64
>      >> suggests that it might be desirable to define an identifier type for
>      >> arbitrary hardware (link-level) addresses.  It seems that the natural
>      >> differentiator for that purpose is the "hardware type" used in ARP,
>      >> so
>      >> a EUI-48 address would be represented as
>      >>
>      >>     MN identifier type (one octet) 5 (say)
>      >>     hardware type (two octets) 1
>      >>     EUI-48 (six octets)
>      >>
>      >> and an EUI-64 similarly, with hardware type 27.
>      >>
>      >> Although with only two subtypes in common use, generalizing this
>      >> might
>      >> not be worth the effort.
>      >>
>      >> 4. Several of the identifier types can be represented as URNs:
>      >>
>      >> - IMEI can be represented as a URN as urn:gsma:imei:...
>      >> - all of the RFID types have a URN representation (called the
>      >>   "pure-identity URI" in the RFID specifications), which starts
>      >>   urn:epc:id:...
>      >>
>      >> Since all URN types are ensured of being unique and persistent, it
>      >> seems that we could define a MNID type for URNs generally, and then
>      >> any RFID URI or an IMEI (as a URN) could be used as a value of that
>      >> type.
>      >>
>      >> If this idea is adopted, it seems that the other 3GPP types (IMSI,
>      >> P-TMSI, and GUTI) should be given defined encodings as URNs in new
>      >> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
>      >> of IMEIs defined in RFC 7254.
>      >>
>      >> This consolidation could be significantly beneficial.  It allows MNID
>      >> to use any URN scheme as an identifier.  It reduces the three
>      >> different RFID representations to one.  It incorporates any future
>      >> expansion of RFID schemes (because all schemes will have a
>      >> pure-identity URN representation).  A disadvantage is that the URN
>      >> encodings are long, but the security considerations section states
>      >> that MNIDs are used only on the first registration at the home agent,
>      >> so there isn't much need for brevity.
>      >>
>      >> Similarly, this approach incorporates any future expansion of mobile
>      >> identifiers that GSMA decides to define, as long as GSMA provides a
>      >> URN representation for it.
>      >>
>      >> The most significant disadvantage is that some URN schemes allow
>      >> several character strings to "mean" the same URN.  In most URN
>      >> schemes, the allowed variation is limited to the case of letters, and
>      >> the common convention is to always use lower-case when there is a
>      >> choice, leading to a unique conventional canonical form for the URN.
>      >>
>      >> 5. Regarding the encoding of a string of digits into octets, it is
>      >> stated that "The last digit MUST be zero padded, if needed, for full
>      >> octet size."  This seems very unwise unless there is a 3GPP decree
>      >> that if a zero is appended to a valid IMSI, the resulting string is
>      >> never a valid IMSI.  Instead, I would specify that padding is by
>      >> filling the low-order 4 bits of the final octet with 0xF.  That
>      >> ensures that the encoding can be uniquely decoded into an IMSI.
>      >>
>      >> 6. There are four types of DUID specified, each with a distinct MNID
>      >> value.  However, DUIDs contain an initial two-octet type field which
>      >> distinguishes the various types of DUID, so providing them with
>      >> distinct MNID values is redundant.
>      >>
>      >> Distinguishing the types and allowing only four of them to be used as
>      >> MNIDs seems to be contrary to the philosophy of DUID construction
>      >> (RFC
>      >> 3315 section 9):
>      >>
>      >>    Clients and servers MUST treat DUIDs as opaque values and MUST
>      >> only
>      >>    compare DUIDs for equality.  Clients and servers MUST NOT in any
>      >>    other way interpret DUIDs.  Clients and servers MUST NOT restrict
>      >>    DUIDs to the types defined in this document, as additional DUID
>      >> types
>      >>    may be defined in the future.
>      >>
>      >> Of course, MNID isn't a DHCP operation, so it isn't subject to those
>      >> requirements, but I expect that devices will use the same DUID for
>      >> both mobile identification, and we don't want mobile identification
>      >> to
>      >> restrict future developments of DHCP.
>      >>
>      >> I think this specification must treat DUIDs as opaque and use only
>      >> one
>      >> MNID type that allows all types of DUIDs as values.
>      >>
>      >> Editorial issues:
>      >>
>      >> Abstract
>      >>
>      >>    Additional Identifier Types are proposed for use with the Mobile
>      >> Node
>      >>    Identifier Option for IPv6 (RFC 4283).
>      >>
>      >> s/proposed/defined/
>      >> This document will define the new types (once it is approved)!
>      >>
>      >> 1.  Introduction
>      >>
>      >>    ... types for IMSI
>      >>    [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
>      >> GUTI
>      >>    [ThreeGPP-IDS].
>      >>
>      >> There is no description of P-TMSI identifiers, although it is
>      >> assigned
>      >> identifier type 4.
>      >>
>      >> There is no description of GUTI identifiers, although it is assigned
>      >> identifier type 7.
>      >>
>      >> 3.  New Mobile Node Identifier Types
>      >>
>      >>    The following types of identifiers are commonly used to identify
>      >>    mobile nodes.  For each type, references are provided with full
>      >>    details on the format of the type of identifier.
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    including
>      >>
>      >>    o  RFID-GID (Global Identifier),
>      >>    o  RFID-SGTIN (Serialized Global Trade Item Number),
>      >>    o  RFID-SSCC (Serial Shipping Container),
>      >>    o  RFID-SGLN (Global Location Number),
>      >>    o  RFID-GRAI (Global Returnable Asset Identifier),
>      >>    o  RFID-DOD (Department of Defense ID), and
>      >>    o  RFID-GIAI (Global Individual Asset Identifier).
>      >>
>      >>    For each RFID scheme except GID, there are two variations: a
>      >> 64-bit
>      >>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>      >> has
>      >>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>      >> be
>      >>    represented in a binary form or other forms such as URI.
>      >>
>      >>    The following list includes the above RFID types as well as
>      >> various
>      >>    other common identifiers and several different types of DUIDs.
>      >>
>      >> The organization of the text here seems to be poor -- section 3
>      >> enumerates the new identifier types, but much of the text at the
>      >> beginning of the section is about the RFID-EPC set of types.  It
>      >> seems
>      >> like a better organization is to use just paragraph 1 followed by
>      >> table 1, and move paragraphs 2-5 into section 4.9.
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    including
>      >>
>      >> The text is using "Tag Data", "EPC", and "RFID" in a way that is
>      >> intertwined but not explained.  I can see that it might be useful to
>      >> use all of the terms if they commonly used in the field (don't forget
>      >> to make them keywords for the RFC!), but you need to explain their
>      >> connection and distinction to the reader or make it clear that the
>      >> reader does not need to understand the differences among the terms.
>      >> E.g., this formulation ties all three terms together
>      >>
>      >>    The Tag Data standard promoted by Electronic Product Code(TM)
>      >>    (abbreviated EPC) supports several encoding systems or schemes
>      >>    which are commonly used in RFID (radio-frequency identification)
>      >>    applications, including
>      >>
>      >> --
>      >>
>      >>    For each RFID scheme except GID, there are two variations: a
>      >> 64-bit
>      >>    scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
>      >> has
>      >>    only a 96-bit scheme.  Within each scheme, an EPC identifier can
>      >> be
>      >>    represented in a binary form or other forms such as URI.
>      >>
>      >> The text uses "scheme" to mean the distinction between encoding
>      >> systems (GID, SGTIN, etc.) and and also to mean the distinction
>      >> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
>      >> It matters here, because you say "within each scheme ... can be
>      >> represented in a binary form or ... URI".  Which meaning of "scheme"
>      >> are you using here?  I thought you meant the second meaning when I
>      >> first read the paragraph, but after reading external documents about
>      >> EPC, I now understand that that last sentence uses "scheme" to in the
>      >> first sense.
>      >>
>      >> You need to be clearer here that there are three representations
>      >> used,
>      >> 64-bit binary, 96-bit binary, and URI (URN, actually), and
>      >> representation is orthogonal to the seven RFID schemes, with the
>      >> exception that RFID-GID does not have a 96-bit binary representation.
>      >>
>      >> I'm assuming that the Tag Data standard unambiguously defines the
>      >> serialization of the binary representations as a sequence of octets.
>      >> If it does not, this document MUST do that, or you will have an
>      >> endless nightmare of byte-order problems.
>      >>
>      >> 4.  Descriptions of MNID types
>      >>
>      >> Identifier ownership is a general concern -- it's worth mentioning
>      >> for
>      >> each type of identifier where the assigner of the identifier obtains
>      >> delegation.  For an EUI, I expect the reader will assume that it's an
>      >> EUI assigned to the device under IEEE rules, and similarly for RFID
>      >> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
>      >> I'm
>      >> guessing that the DUID is one that is, or could be, used by the
>      >> device
>      >> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
>      >> the IPv6 architecture doesn't assume that the association of
>      >> addresses
>      >> with devices is permanent.
>      >>
>      >> 4.1.  Description of the IPv6 address type
>      >>
>      >> It would be good if the document described what the semantics of this
>      >> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
>      >> between that address and the device?  I suspect the connection is
>      >> "the
>      >> device has been configured to expect that it will be assigned this
>      >> address as a long-term interface address", but there are other
>      >> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
>      >> prefix (there are plenty of them!) and then assigning addresses out
>      >> of
>      >> it simply to create a sequence of unique identifiers for devices, but
>      >> not using those addresses on packets.
>      >>
>      >> Then again, perhaps you want to allow flexibility.  But in any case,
>      >> I
>      >> think you need to specify what the rules are for what address is
>      >> associated with what device.
>      >>
>      >> 4.2.  Description of the IMSI MNID type
>      >>
>      >> What does "in network order" mean here?  As far as I know, there is
>      >> no
>      >> defined "network order" for 4-bit quantities, only for dividing
>      >> integers into octets and placing sequences of bits into octets.  I
>      >> assume you mean that in any octet, the high-order 4 bits are the
>      >> first
>      >> digit and the low-order 4 bits are the second digit, but I think you
>      >> need to state that explicitly.
>      >>
>      >> 4.3.  Description of the EUI-48 address type
>      >>
>      >>    The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>      >>    string containing the IEEE EUI-48 address.
>      >>
>      >> Is "string" the correct word, this not being a sequence of
>      >> characters?
>      >> I would say "sequence of 6 octets" or simply "encoded as 6 octets".
>      >>
>      >> 4.9.  Description of the RFID types
>      >>
>      >> This section needs to be revised.  It provides a lot of detail about
>      >> the RFID types, but it's not enough detail for a reader who doesn't
>      >> understand RFID to learn how any particular RFID scheme works.  E.g.,
>      >> the first paragraph says that GID contains three fields in the first
>      >> sentence, and that it contains four fields in the third sentence.
>      >> Despite this, the description isn't enough to allow the reader to
>      >> construct GID identifiers manually.
>      >>
>      >> On the other hand, readers who already understand the RFID schemes
>      >> will find this text redundant.
>      >>
>      >> I think that almost all of this text can be replaced by references to
>      >> the EPC documents, since these identifiers are opaque from the point
>      >> of view of mobile identification.
>      >>
>      >> 5.  Security Considerations
>      >>
>      >> The base MNID specification, RFC 4283, gives these security
>      >> considerations (sec 4), which ought to be referenced and probably
>      >> summarized in this section:
>      >>
>      >>    Moreover, MNIDs containing sensitive identifiers might only be
>      >> used
>      >>    for signaling during initial network entry.  Subsequent binding
>      >>    update exchanges might then rely on a temporary identifier
>      >> allocated
>      >>    during the initial network entry, perhaps using mechanisms not
>      >>    standardized within the IETF.  Managing the association between
>      >> long-
>      >>    lived and temporary identifiers is outside the scope of this
>      >>    document.
>      >>
>      >> What is the meaning of the word "might" in paragraph 3?  I suspect
>      >> that the purpose is to qualify this paragraph with "One way to
>      >> address
>      >> these vulnerabilities is to only use MNIDs containing ...".  But if
>      >> that is the meaning, that expanded wording should be used.  Otherwise
>      >> the text reads as if it is hypothetical.
>      >>
>      >> [END]
>      >>
>      >>
>      >> _______________________________________________
>      >> dmm mailing list
>      >> dmm@ietf.org
>      >> https://www.ietf.org/mailman/listinfo/dmm
>      > _______________________________________________
>      > dmm mailing list
>      > dmm@ietf.org
>      > https://www.ietf.org/mailman/listinfo/dmm
>      >
>      
>      
>
> _______________________________________________
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>


From nobody Fri Feb 10 07:35:13 2017
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EA56D1299F1; Fri, 10 Feb 2017 07:35:11 -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 autolearn_force=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 tJrhxPbwcbF7; Fri, 10 Feb 2017 07:35:10 -0800 (PST)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (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 3599A1299EB; Fri, 10 Feb 2017 07:35:09 -0800 (PST)
X-AuditID: c6180641-c53ff70000000a06-31-589d9756878f
Received: from EUSAAHC007.ericsson.se (Unknown_Domain [147.117.188.93]) by  (Symantec Mail Security) with SMTP id 96.0E.02566.6579D985; Fri, 10 Feb 2017 11:35:06 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC007.ericsson.se ([147.117.188.93]) with mapi id 14.03.0319.002; Fri, 10 Feb 2017 10:35:05 -0500
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Charlie Perkins <charles.perkins@earthlink.net>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSe/j/cjYYsQbutUCsVh56ND0V9aFVgPUAgAAQ6gCADSuDgIAAA5SAgAABaIA=
Date: Fri, 10 Feb 2017 15:35:04 +0000
Message-ID: <54184D70-CFE4-4BCF-A7BA-075D2EC767FE@ericsson.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <D4B7FC35.258902%sgundave@cisco.com> <17671de0-7238-3a3f-c5b6-d6e8bbd3a5e2@earthlink.net> <8E97344D-93A5-4B6F-96F3-735068A4D713@ericsson.com> <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
In-Reply-To: <bbb277e9-c628-02d2-b527-bf43a9e9bbcb@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/signed; boundary="Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrEIsWRmVeSWpSXmKPExsUyuXRPrG7U9LkRBltu8ljcv3ONzeL+oxqL /7O3sFtcffWZxeLZxvksFgf/bGOzeHmizIHdY/L+r8weU35vZPVY9WUCs8eSJT+ZAliiuGxS UnMyy1KL9O0SuDL2/njFWrDEqGLa1YvMDYwf9LsYOTkkBEwkZuxYx9bFyMUhJLCeUWLByzvs EM5yRon5u5ezgVSxAVVt2PmZCcQWETCWaOi9xwxiMwv8Y5TYeNkYxBYWsJCYOf0yI0SNpcTE GReZIWw/ie9/V4DZLAKqEsv6vgPN4eDgFbCXuHTEAGLXDCaJ3a1PwHZxCjhKXOs7BFbPKCAm 8f3UGiaIXeISt57MZ4K4WkTi4cXTbBC2qMTLx/9YIWwliY+/54M9wCwwhVFiyr/TYA28AoIS J2c+YZnAKDILyaxZyOpmIamDKNKWWLbwNfMsoGOZBXQkJi9khAibSrw++hHKtpaY8esgG4St KDGl+yH7AkaOVYwcpcUFObnpRoabGIGxeUyCzXEH495ez0OMAhyMSjy8G7znRAixJpYVV+Ye YlQBan20YfUFRimWvPy8VCUR3sc35kYI8aYkVlalFuXHF5XmpBYfYpTmYFES570ecj9cSCA9 sSQ1OzW1ILUIJsvEwSnVwJj8qYDpgvfRfXZZx6b6zDyy//9jHduVZ6dsucdz6V1ewts/zFf/ L5aPqZ3RXVfS/vbSxUA/y9Wt8oET35c/C1913qtyn6K07IbVl0SLmmy/Wc6Meyig9N5iWpLr Hz9+kx+RsnGBfF+cOgL4Ny5fW8vx4aR01JpJC2Pmvr4SflyvdU2Utm1aZLgSS3FGoqEWc1Fx IgCJjE+E1QIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Wi2cVuEGvwZxVSfFDLz7b1ipqfA>
Cc: "ietf@ietf.org" <ietf@ietf.org>, Gen art <gen-art@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, Sri Gundavelli <sgundave@cisco.com>, Dale Worley <worley@ariadne.com>, "dmm@ietf.org" <dmm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:35:12 -0000

--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Charlie,

> On Feb 10, 2017, at 10:30 AM, Charlie Perkins =
<charles.perkins@earthlink.net> wrote:
>=20
> Hello folks,
>=20
> The last two days have been crammed full with other urgent work =
requirements.  I will respond to these comments today.

Great.

>=20
> Suresh, do you mean to ask if I can submit a revised document before =
Monday?

No. If you can agree on the changes to be applied with Dale by =
Monday/Tuesday I think it would be great. If there are other comments in =
IESG eval, you can address them as well in a new revision.

Thanks
Suresh


--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMszCCBfUw
ggPdoAMCAQICEQDBTwyxD9MsGvfXxnk9EeujMA0GCSqGSIb3DQEBBQUAMDoxETAPBgNVBAoMCEVy
aWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyMB4XDTE0MTIyMjE5
MjAyMloXDTE3MTIyMjE5MjAyMVowbDERMA8GA1UECgwIRXJpY3Nzb24xGDAWBgNVBAMMD1N1cmVz
aCBLcmlzaG5hbjErMCkGCSqGSIb3DQEJARYcc3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbTEQ
MA4GA1UEBRMHbG1jc3VrcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANGcfCXBzd+C
oyGibVfWAz/McYUdmPZ2YiTaQk8v/yLaKsKiFBdOZn9ahr9iu6pXz9OEbxH1h3hrudHg6de44JFg
ZAHfZii/R+Ard+/7dG1BE7jd1+kuSFDzfLzv/BNY2sHEhPlGks4D/VBoCLwGdopsBvkrp8QKOa6+
SzIGsTCwtVS4qnlcp4Qprmj/KCF2VIEERnMc5F93xXhZa+SDV57JI8ep3psnMy8tAdddKvY/0ZBI
MXAD8O1DKhC/SLFLhZQok4JUJBXsjsUGE3+1/D4HG0/johJ8rSGfrMkECgZ8wZZyw0cdM3/cB7+O
nN2V1oY2/Xo0dLL3nPtfRZWFQAECAwEAAaOCAcIwggG+MEgGA1UdHwRBMD8wPaA7oDmGN2h0dHA6
Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2Mi5jcmwwgYIGCCsG
AQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBIBggr
BgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5kaXZp
ZHVhbGNhdjIuY2VyMCcGA1UdEQQgMB6BHHN1cmVzaC5rcmlzaG5hbkBlcmljc3Nvbi5jb20wVQYD
VR0gBE4wTDBKBgwrBgEEAYIPAgMBARIwOjA4BggrBgEFBQcCARYsaHR0cHM6Ly9yZXBvc2l0b3J5
LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMC
MB0GA1UdDgQWBBRTsyLz1xpNDuZ1g4JxlMDczzX4GzAfBgNVHSMEGDAWgBSxDcrURrevhgLDL28G
yg52cX9LNzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAJqZ/LPXQsxfJkyVbggL
B/1m11FTG5OefG+rK3msNbXwEsVBul4MizD6VwCQbLaZK5vt0sm6XhPqBfC2fUICra+YmkuwAhCU
Fzgs9d/qg5ubbe6CgD0wIQJpxP66Y2v5Kr2pFVu3ew18X/XnTgYzLo3sUtr7itLfMoy0SMSDCYvc
4lCP0Zo4qOAuEBnFs0IsNSDVRygRcj0+jjEc3WXpKD3XYEo+qTnCV8yvKNRa1LzIg205zFR2bvsG
H6GDE5qyYAtTEFLiEmvz+FNaTLlXSIM3gBbgxN4BT5UOeU20CJEww2NtIJrlAlBCm6aD5tu8jKUn
78iWA3Mvk3F2HvxY5KIDH7L1MqJflxBrNMgJ1VQ0IL9DdofOeq5PSh4FGPoc4xpIk+aN9px/ZV2r
WyieLB/Pj155yUr3ZtkYXF0VXmeu3S15DCofAHI171Ihsnsm6mamfm8lahLMoGgIMBMz0PS/vqCz
Jd92HYlfhg5W6UC/ZRAhsRJsiF7vEADtzlx9wD+hVfIBzkn5wv3GuCwcDsYroj25K8yfiyXFffPO
NAjVN1b2kiYLy+Z3RD9CxN1UAxBZANJLu1FfjdvsCHtrq5mLk3QFhf1YpoF51hvEN30ymF9UZQkb
Ro9sAC8bULdMRlwNcNeN55Sz2CDW3QNgZNdmLpD2h9Td0FaG0nmODm3uMIIGtjCCBJ6gAwIBAgIR
AKAMy8ybmZjs4jpw9HzBwFkwDQYJKoZIhvcNAQEFBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmEx
HzAdBgNVBAMMFlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTQwNTI3MDc0NjIxWhcNMjQwNTI3
MDc0NjIxWjA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZp
ZHVhbCBDQSB2MjCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIBANq6U+tfSJZTn4k46qN1
3HgaeXXsMmGSWShc6A5IEyFboXMZW3lFHso+/6uO3ZilvB2ipZJhrhU+RL/va+5Chay/PZq9ZZeE
9N03OsHfOzlwk7uwojJ34tHLiX/yQoriI+b5DXxfIYXTFO5zlZLdaIxJwlLEQp0g4/zF6EGtodlp
usaH07FAcLiIEeTMPRgXcn+8GoFOvtuVHNh/WHePlrupUgcI9/P54ITXvmZF6xcNBEjsu8yJm1Vq
qK0GXSgAmInJ4Ga8S6ME2wgSBRDolxAUbmfLQRrMvLC/tyXBvuLO8uChdzpIWt3QPtMYm2R2V1Um
0zANhenIUwYCKNPq5/yHaS48jCsOBAU0TIhBnirnZmlEbC6ALqwzGAcQMaMD8LFf1oLlWLUQxEmI
4YXqBXdP5XnIcMdIEF5BtUBebzBJMMF9dDB2uj8BeoRPSYbpGl7irYUYFpq4TyocQ7qpHdYASC+N
V8VTaTrFnHWqa/CGRdp3GHpkgxfOBvpamOK8udHQYQo2uA3YNd2+j7p4C3jkGG+Z6RrZOskPEwta
IHLxBiA141dhCy5EScOyNajrAXQupsDnvr2ib2ef+4nObPFvedPWIe57lyj0n3e1rTqTGIBIe9wj
NnAA6MqeaTS9HchPtBvOrah/cTWzXzGjwMz0P3UJqTQ2r5EAu12/W5kpAgMBAAGjggG4MIIBtDCB
igYIKwYBBQUHAQEEfjB8MC0GCCsGAQUFBzABhiFodHRwOi8vb2NzcC50cnVzdC50ZWxpYXNvbmVy
YS5jb20wSwYIKwYBBQUHMAKGP2h0dHA6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNv
bS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNlcjASBgNVHRMBAf8ECDAGAQH/AgEAMFUGA1UdIAROMEww
SgYMKwYBBAGCDwIDAQECMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50
ZWxpYXNvbmVyYS5jb20vQ1BTMEsGA1UdHwREMEIwQKA+oDyGOmh0dHA6Ly9jcmwtMy50cnVzdC50
ZWxpYXNvbmVyYS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jcmwwHQYDVR0lBBYwFAYIKwYBBQUH
AwIGCCsGAQUFBwMEMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQUsQ3K1Ea3r4YCwy9vBsoOdnF/
SzcwHwYDVR0jBBgwFoAU8I9ZOACz9Y+algzV6/p7qhfoExIwDQYJKoZIhvcNAQEFBQADggIBAG4H
IGyvrHc9kEKyYZtxJn9cv7S2dUxuUiegmAvUGHc+JGJyB2jyX7py9an8CsHAxg3BI3Ku9j0h7DJp
Xyfrlzmg36XYkNS7Ot0A1UqdjGFrtnIISI+Zj3ywHZudmDF8ktdBihHAjuk47B/Kg/Z8JhUJ37GG
x/KxiIiXg5HMTdOl6mlDbJaTIEGagdRcmH3u57r5snZ+qdVSg5UxWdhgS2+zPru/vDbPd+91zLTj
9GejKXFJ6fEAOLW1j2IjJ0cyDI67d1/OzFTwCK8wYbhopK2wJ9QTKDQuWRuGoyt2d6yzd7WoAS55
JE0BIt+kXDJGbOaK42H2ifO6ERHbJiEr/oh4KzgdAes+GRjwlSaG2Z0va4Ss5lY6zfwVCEZYdZcj
SDpKB0M5tTQYQeO7QyQPOI6Gb4FXA9ko3sHvAPs4+Pq+UtWjp3y8sYr1vLCER9ePEsgLdCG27mUk
9OAijkG6n5oEGOIn+70F+qvKpmm52dZ8b7DELfbuuk0CrY4p0WxH3bBt6FJkPeZJIB6YNXAYHZi7
RcdBjLJh+lawbIYTJFIcoWFHAl0g0/NYsjz3DLhZz4+CrJ6SQSYmp7qDhdJAWPiaq3C+qE/h2DZA
Jwoz9uHrZHB8zsZ5JL8sUZ7zgqYmNMN+9PxzasrycTJn96Y63AIZdDq1kIHIw0vF4PBTVMZtMYIC
mTCCApUCAQEwTzA6MREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5k
aXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa99fGeT0R66MwCQYFKw4DAhoFAKCCAR8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjEwMTUzNTA0WjAjBgkqhkiG9w0B
CQQxFgQUF8FHCP6B39DJNK3w7EZmBO66BG4wXgYJKwYBBAGCNxAEMVEwTzA6MREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MgIRAMFPDLEP0ywa
99fGeT0R66MwYAYLKoZIhvcNAQkQAgsxUaBPMDoxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYyAhEAwU8MsQ/TLBr318Z5PRHrozANBgkqhkiG
9w0BAQEFAASCAQAaxZykHmGn669je599n3IJWdMlQOL9Ged26nK8NP10IwJVkwedvzEKFfaqkpC7
MOvs4hnztmdlpKGOZAQq57iimbJXRXaeypExikciCQtm04r3GnxAIB58Glp2qlhxoAKGZJVDKht5
FhkmwewHbE83Xz5VQ2cXde4tR4HjJrdxWizk+WARERwbL4cZtJbFMZ2uv8byf/Dz60W5djUYnt09
gOzvEY0PCyTMjjGC/lepSC/rEqMUudv1PgmtPOjFDxbDy1Gm8fWhf4sB8BFTKx1GCpjU+L8jxQR7
vT6fyyn4TqRV8npy5VzJkcr4GsEV8jBUzcQpqx3P2kxzdfN2dUoFAAAAAAAA

--Apple-Mail=_5C86FE03-0A3D-4A96-9F4A-316287CDB199--


From nobody Fri Feb 10 07:39:11 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1514E1299F2; Fri, 10 Feb 2017 07:39:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 qb4IaPqc8krZ; Fri, 10 Feb 2017 07:39:04 -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 2D4561299EB; Fri, 10 Feb 2017 07:39:04 -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 v1AFd3wx045561; Fri, 10 Feb 2017 08:39:03 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1AFcw40045152 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Fri, 10 Feb 2017 08:38:58 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Fri, 10 Feb 2017 07:38:57 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Fri, 10 Feb 2017 07:38:57 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXA=
Date: Fri, 10 Feb 2017 15:38:57 +0000
Message-ID: <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
In-Reply-To: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9z86F_ieoI5VnFN-tPcKVDsJxig>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 15:39:06 -0000

Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
converge to the minimum MTU of all paths in the multipath, and so it is
still OK to store the MTU in the network layer where it would be shared
by all flows.

ECMP does present challenges for RFC4821, however. If a first transport
session discovers a large MTU and shares it with a second transport
session, the second session may take a very different path where there
is a smaller MTU and encounter a black hole. IMHO, it might be a good
idea to file an erratum to RFC4821 explaining how ECMP might cause
problems if discovered MTUs are shared between sessions.

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

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
> Sent: Friday, February 10, 2017 2:21 AM
> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stew=
art@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
>=20
>=20
> On 10/02/2017 03:25, Brian E Carpenter wrote:
> > Stewart,
> >
> > On 10/02/2017 04:19, Stewart Bryant wrote:
> > ...
> >> I wonder if we would best serve both our future and our heritage
> >> if we declared RFC1981 as historic, and either left the idea there,
> >> or declared it as historic and wrote a new text from a clean start?
> > I don't see that. It's a stable, widely deployed, interoperable
> > mechanism. That is rather orthogonal to the issue that has been raised,
> > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > across the Internet.
>=20
> I will not debate whether it is faulty or not, but it seems that in
> practice the
> Internet breaks the mechanism. However it breaks it is a way that seems
> disruptive to some user traffic. The document is really guidance
> one how hosts might use  ICMP for optimization, and arguable need
> not be a standard at all.
>=20
> My remark about heritage is that this vintage draft is very much a
> product of
> its time, and really needs modernizing, and after modernizing ought to
> look quite different, and thus maybe we should employ a procedure
> other than a simple replacement.
>=20
>=20
> > ...
> >> It is concerning that the draft does not talk in any detail about
> >> how modern ECMP works, i.e. using the five tuple, and noting that
> >> the PMTU may be different depending on the transport layer port
> >> numbers.
> > Has this problem been analysed for, say, IPv4? And does the real world
> > contain ECMP setups with different MTUs on different paths?
>=20
> I don't know if anyone has looked. Since the mechanism is
> self-correcting albeit
> with some disruption to user traffic it looks to the application and the
> application
> user, just like the Internet not working for a few moments.
>=20
> In a well managed SP network there should not be, but neither should ther=
e
> be asymmetric path costs, but there are. The less well manage private
> networks are less well managed.
>=20
>=20
> >
> >> Given that a very large fraction of packets will traverse an MPLS
> >> network at some point, I am surprised that there is no text talking
> >> about the importance of providing support for this feature in the
> >> MPLS domain. RFC3988 talks to this point, but is only experimental.
> > I don't understand. How does the fact that there might be some MPLS
> > segments along the path affect end-to-end PMTUD?
>=20
> The point that RFC3988 makes is that MPLS looks like a single hop to IP
> and the
> PE has to fragment or has to reply with an ICMP error message to support
> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
> result
> in the right response at the end node.
>=20
> My point is that the draft is silent on the subject, and perhaps it
> should not be.
>=20
> However your question make me ask a further question. The draft is also
> silent
> on NATs. Is there any advice needed for people designing and configuring
> NATs?
>=20
> >
> >> =3D=3D=3D=3D=3D=3D
> >>
> >>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
> >>     could use the flow id as the local representation of a path. Packe=
ts
> >>     sent to a particular destination but belonging to different flows =
may
> >>     use different paths, with the choice of path depending on the flow
> >>     id.  This approach will result in the use of optimally sized packe=
ts
> >>     on a per-flow basis, providing finer granularity than PMTU values
> >>     maintained on a per-destination basis.
> >>
> >> SB> How widely is flow-id supported in networks? I thought that the
> >> SB> current position was that it was unreliable as an ECMP indicator
> >> SB> and thus routers tended to glean information from the packet thems=
elves.
> > This is future-proofing. Agreed, usage today is limited.
> >
> > (But it would be better to call it the Flow Label for consistency with =
other
> > recent RFCs.)
>=20
> Well the question is whether it is simply limited today, or broken today
> in a manner that
> is irrecoverable? I don't know, but I do know that the mainstream ECMP
> approach
> is the five-tuple. There is something akin to the flow label being
> deployed in MPLS. However
> what distinguishes the MPLS Entropy Label is that it is inserted (and
> removed) by the
> service provider and is therefore trusted by the service provider.
>=20
> >
> > I think your other comments are all valuable.
> Thank you.
>=20
> Stewart
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------



From nobody Fri Feb 10 10:23:01 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFADF129A76; Fri, 10 Feb 2017 10:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gWnuxRFcE6G; Fri, 10 Feb 2017 10:22:54 -0800 (PST)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 4E557129A6A; Fri, 10 Feb 2017 10:22:54 -0800 (PST)
Received: by mail-qk0-x241.google.com with SMTP id 11so6145808qkl.0; Fri, 10 Feb 2017 10:22:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=bwJmQqlVuFR/DJ/c5y0tUZGiTrQghZ5QZhNsLYPVTSw=; b=S1xDdUgoRbdBEkLAM9IOAc4nPrrXvRcAGXrGls4qN7/AYCV8fDgj3sYxHfXNjwBSqm o9Ebw91D8b46/qDMCzQ10/5YmVtfDXiQ46Q4W+swPQFdChK9msjpytEzRjMEYycTnKLG vLIhClv8S48ZUXUJIozSzMNZCZJGMJL0Iz0kNP3rDJvA55FI3DUzVS9MYsXEGO5lHfST HDQf1j2N6O+4KmCRZ+lNgAuLybcWc6aL+GQPp9QWUdfITY8glfY+h0/p6qoKauTd8xy7 0mZ3+XNy0DNZFmgsuOpeE11uWuzSjZW46M/a1MQVxWC1xnMN91rvNQ3KIbn0iH67jJg3 Xq9Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=bwJmQqlVuFR/DJ/c5y0tUZGiTrQghZ5QZhNsLYPVTSw=; b=WqKeAFRVIyvZBb+2wRlPU0ffoLfz1OCl/qiGh/M1xE/DiEpKNrGlio1pWYF8nf1KRQ a+uL8+CK+NCoeqWxnfsD4TFJH6oH/gfXltdnzU+11xWiFCKsdnEC1Wu5Dp5/heS5wR/c ApnT5KqHnqtmt1TuWA791aW9eYJgrNTDPWlriolTYFXIAoIuPPb8Q6QOGOLFbZNKfCys Qk0/b1I1ufO5MHaK34Kcn3RJ8nG57HwE11I0dD8HJNEmoU4CN4l2chljC/pzdLPXFaJm ZpdGCH8d13ETZIFUqyzIsqDgtJuIE8DHOvlrn7wSKONW9AY7ceMeJAA65OC0Ks7XOG0i ku5Q==
X-Gm-Message-State: AMke39kxqyIdYpjsu2Fj0arYECLu2lH7aVsBj8MryHnsbWrptcWMwT4FhqaLYqtDSedS3xjNLBXNtdgc53vjhA==
X-Received: by 10.55.146.135 with SMTP id u129mr9561770qkd.219.1486750973229;  Fri, 10 Feb 2017 10:22:53 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.29 with HTTP; Fri, 10 Feb 2017 10:22:52 -0800 (PST)
In-Reply-To: <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Fri, 10 Feb 2017 10:22:52 -0800
X-Google-Sender-Auth: rpOfT7KMBZsFesInnOaCVehElnU
Message-ID: <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j1O11x4ICMUWGJmzlJfCx0y0-c8>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 18:22:56 -0000

At Thu, 9 Feb 2017 18:30:11 -0300,
Fernando Gont <fgont@si6networks.com> wrote:

While I largely agree with Fernando on everything he said, I have to
admit most of the points are just repeated from the 6man discussion,
and won't get us anywhere new by discussing these again at this point.
I guess the only new input for the IETF last call is this:

> 2) However, some folks came up with proposals to insert EH, on the basis
> that "RFC2460 does not explicitly ban EH insertion". If there's people
> arguing that, we clearly need to make this clear in the spec.
>
> 3) There was a consensus call, yes. When the call was made on the
> mailing-list, the vast majority of supporters of "let's keep the
> ambiguity" were folks from the same company as "2)". I have no idea if
> this changes (or not) "consensus"... but this is clearly an important
> datapoint.

Although I don't want to point a finger at particular people or
organizations without an evidence, I guess not a small number of 6man
participants (not only those who explicitly spoke up here) suspected
that the decision process was biased with the influence of a large and
powerful organization and the process and resulting "consensus" was
not really a fair one.  And I'm not an exception to it - in fact, it
was so unbelievable to me that we can't clarify an ambiguity even when
we were also open for future extensions, that I couldn't think of
other reasons than a company agenda.

Of course, it's quite possible that it was just a coincidence that
many people with the same organization genuinely thought we should
leave it ambiguous while many others strongly thought we should
clarify it but few (if not no) people from that organization supported
the clarification.  But I don't think we can prove it either way.

But as Fernando said, I believe this point (and that several, and
arguably more, participants suspected it) should be included in making
the decision at the IESG and at the IETF last call.  And, whatever the
decision, it would be more productive to move on after that and use
our time for some other things.

I'll shut up here on this so I won't be a cause of another 600+ email
thread.

--
JINMEI, Tatuya


From nobody Fri Feb 10 11:45:45 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE3B1295A2; Fri, 10 Feb 2017 11:45:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MOxZ3dYvUwbD; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (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 1E7E5129540; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
Received: by mail-pf0-x241.google.com with SMTP id 19so3069934pfo.3; Fri, 10 Feb 2017 11:45:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=swUDx54phvfF0lOJ8hCltKAaJz4Je2hRCpTLONbFpxE=; b=lZ9rxZpcxBgBycFYjYudiE8smtLoEKuo6uJhdWncUj/jY9FvtZw6xMUyYHVkBFB5wN WmITLo/bmNhptJKVrNYYpyse9pHvJo3/hfXRY/3FnnOa14cRHYqb6B7fAftGxEvb81t3 jm92G8ndxKQmjm7yXa3F7hNw4xiAjqw5iQomRGcjGm5WkzloTZiY3eGMSdVVM0Z4pMUx j3Cu6vUGU4ttPIbmrnIcYg+9yKqJpXCOwfoSSsVlV4O8BEVrVQpJFVBn4zeEQ7CNbhMs ObPnlEloaM10GI8y0ERq/7m4lw+IOIcADRscnbA8oSJ71Dr/wQrkPweoQIA7ubMSpVFM qibg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=swUDx54phvfF0lOJ8hCltKAaJz4Je2hRCpTLONbFpxE=; b=Rdm/4tHvDHgDGlet7UAb8LXOK728NTmvWqdLXMgoCFWi2fI0dbkVu2/vzJiX+W5uHU e84Gfpl5ebz2862DZoH9LPEV5YelHCZSgc/0m9E8G8pBOf1fNVx8J3eTUWHMYqaUZwPM vhdYqir2Bvh1OmzwGVc/oodKRNUkiHgRCmvo1sDPgkxkmbq/k5Ic+qOEaxbpOTjIdWod sQt72/GTL+tl+tMZ9Nj9JLXoFloIgOuHt3vupm0XFT51C/d8j1K0TroY21PzbUUA2/cb qyILRpBQwb3+TcE/T6Szv0aVbSQR3XHnt2JxZITs9Drmy+fA2NVlG51HUMkA/qtrfFeu 5cmQ==
X-Gm-Message-State: AMke39nbKoqJl/w80yPTzdf2nru48VoswBBke/MHKhfCEsZhsKIh+9ozCvU8xEgxgyX63w==
X-Received: by 10.99.109.143 with SMTP id i137mr12712107pgc.11.1486755936371;  Fri, 10 Feb 2017 11:45:36 -0800 (PST)
Received: from ?IPv6:2406:e007:769c:1:28cc:dc4c:9703:6781? ([2406:e007:769c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id g70sm7160051pfb.50.2017.02.10.11.45.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 11:45:35 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
Date: Sat, 11 Feb 2017 08:45:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DnN_VheH0_NVD9hmCAJ_mnaEB_s>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 19:45:38 -0000

On 10/02/2017 23:20, Stewart Bryant wrote:
> 
> 
> On 10/02/2017 03:25, Brian E Carpenter wrote:
>> Stewart,
>>
>> On 10/02/2017 04:19, Stewart Bryant wrote:
>> ...
>>> I wonder if we would best serve both our future and our heritage
>>> if we declared RFC1981 as historic, and either left the idea there,
>>> or declared it as historic and wrote a new text from a clean start?
>> I don't see that. It's a stable, widely deployed, interoperable
>> mechanism. That is rather orthogonal to the issue that has been raised,
>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>> across the Internet.
> 
> I will not debate whether it is faulty or not, but it seems that in 

It's faulty by the standard of RFC4890 (which is Informational).

> practice the
> Internet breaks the mechanism. However it breaks it is a way that seems
> disruptive to some user traffic. The document is really guidance
> one how hosts might use  ICMP for optimization, and arguable need
> not be a standard at all.

I think that's a mischaracterisation of the mechanism (and the draft).
PMTUD is not an optimisation. Without it, you get black holes.

> 
> My remark about heritage is that this vintage draft is very much a 
> product of
> its time, and really needs modernizing, and after modernizing ought to
> look quite different, and thus maybe we should employ a procedure
> other than a simple replacement.

It's proposed for Internet Standard. That means it must replace the
PS document and must specify the same thing, plus corrections, minus
unused features.

>> ...
>>> It is concerning that the draft does not talk in any detail about
>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>> the PMTU may be different depending on the transport layer port
>>> numbers.
>> Has this problem been analysed for, say, IPv4? And does the real world
>> contain ECMP setups with different MTUs on different paths?
> 
> I don't know if anyone has looked. Since the mechanism is 
> self-correcting albeit
> with some disruption to user traffic it looks to the application and the 
> application
> user, just like the Internet not working for a few moments.
> 
> In a well managed SP network there should not be, but neither should there
> be asymmetric path costs, but there are. The less well manage private
> networks are less well managed.
> 
> 
>>
>>> Given that a very large fraction of packets will traverse an MPLS
>>> network at some point, I am surprised that there is no text talking
>>> about the importance of providing support for this feature in the
>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>> I don't understand. How does the fact that there might be some MPLS
>> segments along the path affect end-to-end PMTUD?
> 
> The point that RFC3988 makes is that MPLS looks like a single hop to IP 
> and the
> PE has to fragment or has to reply with an ICMP error message to support
> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to 
> result
> in the right response at the end node.
> 
> My point is that the draft is silent on the subject, and perhaps it 
> should not be.

Well, in general it's silent on tunnels. They have to emulate links,
as stated in section 2. I still don't see why an MPLS tunnel is a special case.

> 
> However your question make me ask a further question. The draft is also 
> silent
> on NATs. Is there any advice needed for people designing and configuring 
> NATs?

Yes, for NAT64/NAT46 - in RFC6145. For NAT66, the advice is "don't".

>>
>>> ======
>>>
>>>     If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>     could use the flow id as the local representation of a path. Packets
>>>     sent to a particular destination but belonging to different flows may
>>>     use different paths, with the choice of path depending on the flow
>>>     id.  This approach will result in the use of optimally sized packets
>>>     on a per-flow basis, providing finer granularity than PMTU values
>>>     maintained on a per-destination basis.
>>>
>>> SB> How widely is flow-id supported in networks? I thought that the
>>> SB> current position was that it was unreliable as an ECMP indicator
>>> SB> and thus routers tended to glean information from the packet themselves.
>> This is future-proofing. Agreed, usage today is limited.
>>
>> (But it would be better to call it the Flow Label for consistency with other
>> recent RFCs.)
> 
> Well the question is whether it is simply limited today, or broken today 
> in a manner that
> is irrecoverable? 

Nothing's broken. It's just underused.

> I don't know, but I do know that the mainstream ECMP
> approach is the five-tuple.

Sure, but see RFC6438 for some of the difficulties that
causes with IPv6.

> There is something akin to the flow label being
> deployed in MPLS. However
> what distinguishes the MPLS Entropy Label is that it is inserted (and 
> removed) by the
> service provider and is therefore trusted by the service provider.

Exactly the same for ECMP tunnels, in RFC6438. Guess what, my co-author
was from a provider.

   Brian

>>
>> I think your other comments are all valuable.
> Thank you.
> 
> Stewart
> .
> 


From nobody Fri Feb 10 12:48:52 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6417E129BD9; Fri, 10 Feb 2017 12:48:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X8FfURrp894n; Fri, 10 Feb 2017 12:48:50 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D3CB12954B; Fri, 10 Feb 2017 12:48:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1486759730; x=1518295730; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=koT6Rww2eHBCOjyqKkgLKHkWJyT+BNzq2L86eQkufIU=; b=BAzaT2NmLYK04fXCZkEVcKEGqSmMGFZMZJmNv05g2aZWzXIdyKADHQ+C HGPl6rVwxGIaPVADHANdnJVnXck6A6HXoDzQC7ZrOTiA5KXrbZghInYGQ /ZEAI8J+X1QNu20433ZasEN505UfQd+5WXNtgcDj9Ft4e1aH4gB2W0PWc U=;
X-IronPort-AV: E=Sophos;i="5.35,142,1484035200"; d="scan'208";a="357302233"
Received: from unknown (HELO Ironmsg03-R.qualcomm.com) ([10.53.140.107]) by wolverine02.qualcomm.com with ESMTP; 10 Feb 2017 12:47:53 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8435"; a="1307178730"
Received: from unknown (HELO [10.64.126.193]) ([10.64.126.193]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 10 Feb 2017 12:47:52 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "tom p." <daedulus@btconnect.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
Date: Fri, 10 Feb 2017 14:47:09 -0600
Message-ID: <84D3DD56-7CD5-4DBE-A600-D484168E5C3F@qti.qualcomm.com>
In-Reply-To: <024f01d2838c$7f3670a0$4001a8c0@gateway.2wire.net>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com> <024f01d2838c$7f3670a0$4001a8c0@gateway.2wire.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7l_DJSqtDPNssvR3-zkkJMHmDI4>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 20:48:51 -0000

[Apologies for sending this earlier from the wrong address. Resending.]

My old DISCUSS has no formal effect since I'm no longer on the IESG.

Hopefully someone will check to see that my DISCUSS points are 
addressed. If I get some cycles, I will do so myself.

pr

On 10 Feb 2017, at 4:57, tom p. wrote:

> Barry
>
> I note that Pete Resnick still  holds a DISCUSS (since 2014) on this
> document, according to the datatracker.
>
> What is going to happen to that?
>
> Tom Petch
>
>
> ----- Original Message -----
> From: "Barry Leiba" <barryleiba@computer.org>
> To: "IETF discussion list" <ietf@ietf.org>
> Cc: <draft-leiba-cotton-iana-5226bis.all@ietf.org>
> Sent: Thursday, February 09, 2017 5:59 PM
>
>
>> As a result of the discussion on the -19 version of the draft (where
>> "IANA" was replaced with "IANA Services" throughout, and related
>> changes were made), the IETF Trust agreed on the alternative of
>> putting a paragraph at the beginning (the second paragraph in the
>> Introduction in version -20), and then reverting most of the other
>> changes in -19.
>>
>> Version -20 now only has the paragraph that explains that we call
>> <this stuff> "IANA" in this document, plus a few minor changes that
>> came out in IESG Evaluation.
>>
>> We believe the document is now ready to publish, having been through
>> Last Call and IESG Evaluation, and ask Terry, as responsible AD, to
>> send this version off.
>>
>> Thanks, everyone, for the comments!
>>
>> Barry, document editor
>>
>> On Thu, Feb 9, 2017 at 9:52 AM,  <internet-drafts@ietf.org> wrote:
>>>
>>> A new version of I-D, draft-leiba-cotton-iana-5226bis-20.txt
>>> has been successfully submitted by Barry Leiba and posted to the
>>> IETF repository.
>>>
>>> Name:           draft-leiba-cotton-iana-5226bis
>>> Revision:       20
>>> Title:          Guidelines for Writing an IANA Considerations
> Section in RFCs
>>> Document date:  2017-02-08
>>> Group:          Individual Submission
>>> Pages:          41
>>> URL:
> https://www.ietf.org/internet-drafts/draft-leiba-cotton-iana-5226bis-20.
> txt
>>> Status:
> https://datatracker.ietf.org/doc/draft-leiba-cotton-iana-5226bis/
>>> Htmlized:
> https://tools.ietf.org/html/draft-leiba-cotton-iana-5226bis-20
>>> Diff:
> https://www.ietf.org/rfcdiff?url2=draft-leiba-cotton-iana-5226bis-20
>>>
>>> Abstract:
>>>    Many protocols make use of points of extensibility that use
> constants
>>>    to identify various protocol parameters.  To ensure that the
> values
>>>    used in these fields do not have conflicting uses, and to promote
>>>    interoperability, their allocation is often coordinated by a
> central
>>>    record keeper.  For IETF protocols, that role is filled by the
>>>    Internet Assigned Numbers Authority (IANA).
>>>
>>>    To make assignments in a given registry prudently, guidance is
> needed
>>>    for describing the conditions under which new values should be
>>>    assigned, as well as when and how modifications to existing
> values
>>>    can be made.  This document defines a framework for the
> documentation
>>>    of these guidelines by specification authors, in order to assure
> that
>>>    the provided guidance for the IANA Considerations is clear and
>>>    addresses the various issues that are likely in the operation of
> a
>>>    registry.
>>>
>>>    This is the third edition of this document; it obsoletes RFC
> 5226.
>>>
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
> submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>
>>> The IETF Secretariat
>>>
>>


-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Fri Feb 10 12:50:12 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6056712946E; Fri, 10 Feb 2017 12:50:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uAt-3zr8rG7O; Fri, 10 Feb 2017 12:50:09 -0800 (PST)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::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 5542D12943A; Fri, 10 Feb 2017 12:50:09 -0800 (PST)
Received: by mail-it0-x230.google.com with SMTP id c7so150058220itd.1; Fri, 10 Feb 2017 12:50:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Ds85TY7cSf+umA3OSOTvnNiEZdYYuH1Kaotul0DmcJg=; b=qTqSYo8n0PEoHOZ4c/K29u2+iH5TBPCDvsoifwa+mab41pZFmcj0mEuTm+WUomvwhQ eFxf55tIRf+XdehRnj23+V+lRiPSe8kVP/pHuyOH1FGNa0L0BEe7BtJw+Qs7vekhKL4S bxG+2k2szPujdVWzj09G7C9sgaO/vJChHYSBlhsSN4Ac284WKPdQRQOJFZbaLo0gdsag JmJoC4GoFLTXBm1Mca2+IuMqz+YYKUVXikiyM1t8KAGA9dIOvnL/W8Wyf+oH1Y8mINua DCsWCZ6RTM2hPepEFDcf29GnvUWoF9WYWDeswWgtpuM5YUCgFDh0D0ivRscP3OvqGvM+ DepQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Ds85TY7cSf+umA3OSOTvnNiEZdYYuH1Kaotul0DmcJg=; b=GR6j8hvQC5ufu/adj3QZodmbE+VrngK2IJDI1jC9fQYxHwHGnBLSIsEjZ9QwOXYtS8 h9tZaMLkO6NEGeaZy6q8G5rFNI43oapzHLsTh+kcPIbCQAiP4h8Bcr7V/PfsdtLdq14g I55iBGPVDiaEWCJ+vfCssSHIOSxpWMqUtELUd1M9Nb9N8+q/y4rkFRCuLcABDs0RjNBq LK3WqpNt7KAwNMIKpMAw4qVV2rS+O/GLKgPKGn17fDUNOa0o0IF0A7JfrLw0JWLB5gxY ABVLePxjHmHsjXbrNzEUDSu5YAkGrOgH1J93JOzEkHwyIi+UkhrZKgH7MxrUO0cEJNu2 E5mw==
X-Gm-Message-State: AIkVDXJfcaex5h6ryJyVrRNqJYxn2lli2B3DmgJ/cFgChbZhcXrYMkSDzTZZECRgTP1wPrjna4lcM8GWpgPF8g==
X-Received: by 10.36.69.30 with SMTP id y30mr28570924ita.119.1486759808721; Fri, 10 Feb 2017 12:50:08 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Fri, 10 Feb 2017 12:50:08 -0800 (PST)
In-Reply-To: <42526EE6-D1E2-4988-A724-A37EB8FF1BB5@uc2b.net>
References: <148666276925.548.6888411648092656848.idtracker@ietfa.amsl.com> <CALaySJKxyF_o8rgoOZNKNFMBiydgvQ0eGTkoZ4bMasLaos5RWw@mail.gmail.com> <024f01d2838c$7f3670a0$4001a8c0@gateway.2wire.net> <42526EE6-D1E2-4988-A724-A37EB8FF1BB5@uc2b.net>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 10 Feb 2017 12:50:08 -0800
X-Google-Sender-Auth: JUHuedRq0710_DE0mZHWxZvgTlc
Message-ID: <CALaySJLBMAQyT=FncQ0quUJToNpxzB2QFvjHmr1Z+PrKENmURg@mail.gmail.com>
Subject: Re: New Version Notification for draft-leiba-cotton-iana-5226bis-20.txt
To: Pete Resnick <resnick@uc2b.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0MQPCjJR5cuWQqHMpNBryjKRHTc>
Cc: draft-leiba-cotton-iana-5226bis.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 20:50:10 -0000

> Hopefully someone will check to see that my DISCUSS points are addressed. If
> I get some cycles, I will do so myself.

You already did, some while ago.  We chatted about one point at
length, and came up with text.

Barry


From nobody Fri Feb 10 13:03:22 2017
Return-Path: <mls.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E80F2129BDD; Fri, 10 Feb 2017 13:03:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Stiemerling <mls.ietf@gmail.com>
To: <tsv-art@ietf.org>
Subject: Review of draft-ietf-mmusic-sctp-sdp-23
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148676059794.29305.2115176925259048270.idtracker@ietfa.amsl.com>
Date: Fri, 10 Feb 2017 13:03:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Bj_6X9nQfEbEm75OE0hL3ayaP7g>
Cc: draft-ietf-mmusic-sctp-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 21:03:18 -0000

Reviewer: Martin Stiemerling
Review result: Ready

Hi there, 

I have reviewed draft-ietf-mmusic-sctp-sdp-23 as part of the TSV Area
Review. 

Short summary: This draft is ready. 

Thank you for the clearly written draft. 

 Martin


From nobody Fri Feb 10 13:34:53 2017
Return-Path: <ben@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A2B12946B; Fri, 10 Feb 2017 13:34:41 -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=unavailable autolearn_force=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 ywz9Lz0wpR2r; Fri, 10 Feb 2017 13:34:41 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 6DDF1126BF6; Fri, 10 Feb 2017 13:26:37 -0800 (PST)
Received: from [10.0.1.39] (cpe-66-25-7-22.tx.res.rr.com [66.25.7.22]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1ALQY1U053101 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 10 Feb 2017 15:26:36 -0600 (CST) (envelope-from ben@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host cpe-66-25-7-22.tx.res.rr.com [66.25.7.22] claimed to be [10.0.1.39]
From: "Ben Campbell" <ben@nostrum.com>
To: "Martin Stiemerling" <mls.ietf@gmail.com>
Subject: Re: Review of draft-ietf-mmusic-sctp-sdp-23
Date: Fri, 10 Feb 2017 15:26:33 -0600
Message-ID: <5D2D3F1D-9D7A-4C20-B8D5-E5F118F07DEE@nostrum.com>
In-Reply-To: <148676059794.29305.2115176925259048270.idtracker@ietfa.amsl.com>
References: <148676059794.29305.2115176925259048270.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O9TCwl10qbnoYigJJPOPg86zY0s>
Cc: tsv-art@ietf.org, draft-ietf-mmusic-sctp-sdp.all@ietf.org, ietf@ietf.org, mmusic@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 21:34:42 -0000

Thanks, Martin!

Ben.

On 10 Feb 2017, at 15:03, Martin Stiemerling wrote:

> Reviewer: Martin Stiemerling
> Review result: Ready
>
> Hi there,
>
> I have reviewed draft-ietf-mmusic-sctp-sdp-23 as part of the TSV Area
> Review.
>
> Short summary: This draft is ready.
>
> Thank you for the clearly written draft.
>
>  Martin


From nobody Fri Feb 10 14:29:34 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0144129E75; Fri, 10 Feb 2017 14:29:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h7TRqykg-poB; Fri, 10 Feb 2017 14:29:21 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93A3E129DC6; Fri, 10 Feb 2017 14:29:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1486765760; bh=NBBNkzcneukveGKcrKonaU2IS7LMOzfY0+d3 FZQv7d0=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace: X-Originating-IP; b=IjEREYXu4O7MDECgGGbRE9OHLV6ZqnpaZNXxRE5HIOH1D4 x/2LeAt0ZCjA7yTVE0pD2IR4LrYEA5uNMbJC1BFzs9/uc+tU6e8tgvTEeNtwuXZHsQK zgVwJYwAfAtBaVx5lqvGNkVT/mrk82qxh6Cc2NZvvK+G8zC2YDOEtZ7OrjIbB0oRfHV B3ZYCXaokGnrjkd9WLZb38dWQyicHxO6EGehXO4xSgkiUX92LAJ216OWXhdaZuVojKP 4mxhCWsRzbtH5778gR5vg8/igY8nmbnpVA9NQashz0eSVH0U64OCycs3bbNpvn/2m1I rmVvaAp9PE7uKevtvV+sp4mcYfAA==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=N97Z4iuHYnUdyuL3brNQuX2cJmdnw8+Vdl4mWLdxftcXqOlPeJsTSEPifxh5v6JK1rkMQN13Naj1apqf7u+IfE96JFH6ReH/HrfRhKz4kAbgOMaOIechYkVoo9omkrMKoLavxkhHPN5jhj6n4E1xpV/3lj0z60d6X6VHRpf5YXNbP3K9z7CRJAoN0rAYEbQ7TtfWf6BGgP/o4lt0hgEaG9/2FZt9eSuSGkXy776hzogY1IR7+oodeaSCI9UKMf0U+CXmbFKY+L88uWTJTPVwOJHwd4dxtEg7Ypzlk9lbC04dbewhRFYH7JSmdmvQeRShNEe4k0gUWCmUzldFRqlWag==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ccJgP-0006un-JW; Fri, 10 Feb 2017 17:28:49 -0500
Subject: Re: Review of draft-ietf-dmm-4283mnids-04
To: Dale Worley <worley@ariadne.com>, gen-art@ietf.org
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
Date: Fri, 10 Feb 2017 14:28:45 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------34D9108758E61C1C73F50279"
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac788c72805e4d8e22a6c46c4a40f98dc8c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e29Mj3IwseCyrLvDmFAGJMkA3IY>
Cc: draft-ietf-dmm-4283mnids.all@ietf.org, ietf@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Feb 2017 22:29:26 -0000

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

Hello Dale,

Thanks for the thorough review.  My follow-up comments are inline below.


On 1/31/2017 11:34 AM, Dale Worley wrote:
> 1. The Introduction states
>
>     Other types of identifiers are in
>     common use, and even referenced in RFC 4283.
>
> For the reader's sanity, some sort of accounting needs to be made of
> these "other types of identifiers", especially because each type of
> identifier needs an identifier type number.  The text in 4283 is
>
>     Some examples of identifiers
>     include Network Access Identifier (NAI), Fully Qualified Domain
> Name
>     (FQDN), International Mobile Station Identifier (IMSI), and Mobile
>     Subscriber Number (MSISDN).
>
> Are there any other types "in common use"?

I will add some text according to your suggestion.  My criterion for 
whether the identifier type was included in the document was whether or 
not anyone had asked for it to be included.

>
> - NAI (type 1) is defined by 4283.
> - Fully Qualified Domain Name (FQDN) seems not to be specified
> - International Mobile Station Identifier (IMSI) (type 3) is defined
> in
>    this draft
> - Mobile Subscriber Number (MSISDN) seems not to be specified

It is not the jurisdiction of the MNIDs document to specify these 
identifiers, but citations for the specifications are located elsewhere 
in the document.  I will also include those citations here.

>
> 2. Is it intended to have an IMEI identifier type?  The introduction
> mentions an IMEI type, but there is no specification for it, nor is
> there an identifier type number assigned for it.
>
>     ... types for IMSI
>     [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
> GUTI
>     [ThreeGPP-IDS].
>
> Initially I suspected it was it was present in an earlier revision
> and
> then later deleted without this reference being updated.  But all
> versions of draft-ietf-dmm-4283mnids and its predecessor
> draft-perkins-dmm-4283mnids mention IMEI in this way as one
> identifier
> type, but none specify it in any way.  The only discussion I can find
> on the DMM mailing list of IMEI is:
>
>     
> https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af
>
>      From: Marco Liebsch <Marco.Liebsch@neclab.eu>
>      To: DMM
>      Date: Wed, 10 September 2014 13:29 UTC
>      Re: [DMM] regarding the re-chartering..
>
>      It seems the MNID is somehow overloaded to carry both,
> node-specific
>      IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
>      There may be value in adding the IMEI to the list of possible
> types of
>      node-specific IDs.
>
> Either the presence of IMEI in this list is a simple mistake that has
> persisted in all versions of the draft, or specifying IMEI has always
> been intended but has always been overlooked.

I don't know why this happened, but I am happy to include an identifier 
type for IMEI as well as a citation for it.  Thanks for catching this 
and looking through the archives!

>
> 3. The definition of identifier types for both EUI-48 and EUI-64
> suggests that it might be desirable to define an identifier type for
> arbitrary hardware (link-level) addresses.  It seems that the natural
> differentiator for that purpose is the "hardware type" used in ARP,
> so
> a EUI-48 address would be represented as
>
>      MN identifier type (one octet) 5 (say)
>      hardware type (two octets) 1
>      EUI-48 (six octets)
>
> and an EUI-64 similarly, with hardware type 27.
>
> Although with only two subtypes in common use, generalizing this
> might
> not be worth the effort.

Actually, I am O.K. either way on this matter.  However, at this point 
in time it does not seem that we are likely to see any other link 
hardware address types to be used as MNIDs.

>
> 4. Several of the identifier types can be represented as URNs:
>
> - IMEI can be represented as a URN as urn:gsma:imei:...
> - all of the RFID types have a URN representation (called the
>    "pure-identity URI" in the RFID specifications), which starts
>    urn:epc:id:...
>
> Since all URN types are ensured of being unique and persistent, it
> seems that we could define a MNID type for URNs generally, and then
> any RFID URI or an IMEI (as a URN) could be used as a value of that
> type.
>
> If this idea is adopted, it seems that the other 3GPP types (IMSI,
> P-TMSI, and GUTI) should be given defined encodings as URNs in new
> sub-namespaces of the "gsma" URN namespace, to parallel the encoding
> of IMEIs defined in RFC 7254.
>
> This consolidation could be significantly beneficial.  It allows MNID
> to use any URN scheme as an identifier.  It reduces the three
> different RFID representations to one.  It incorporates any future
> expansion of RFID schemes (because all schemes will have a
> pure-identity URN representation).  A disadvantage is that the URN
> encodings are long, but the security considerations section states
> that MNIDs are used only on the first registration at the home agent,
> so there isn't much need for brevity.
>
> Similarly, this approach incorporates any future expansion of mobile
> identifiers that GSMA decides to define, as long as GSMA provides a
> URN representation for it.
>
> The most significant disadvantage is that some URN schemes allow
> several character strings to "mean" the same URN.  In most URN
> schemes, the allowed variation is limited to the case of letters, and
> the common convention is to always use lower-case when there is a
> choice, leading to a unique conventional canonical form for the URN.

There is a sort of "hidden" disadvantage to long names, especially for 
tiny devices using constrained link layers.  Namely, a longer name makes 
it more likely to require lower-layer fragmentation.  I'm not sure that 
it should be the job of a layer-3 mobility entity to parse URNs and 
determine if two different flavors are supposed to be equivalent.

Other than that, I don't have any real objection to reorganizing the 
namespace, but I'd like some additional confirmation that it's a good idea.

>
> 5. Regarding the encoding of a string of digits into octets, it is
> stated that "The last digit MUST be zero padded, if needed, for full
> octet size."  This seems very unwise unless there is a 3GPP decree
> that if a zero is appended to a valid IMSI, the resulting string is
> never a valid IMSI.  Instead, I would specify that padding is by
> filling the low-order 4 bits of the final octet with 0xF.  That
> ensures that the encoding can be uniquely decoded into an IMSI.

I am O.K. with this.  I need to go find out where I got that language 
from, because I don't think I was the person who crafted it.

>
> 6. There are four types of DUID specified, each with a distinct MNID
> value.  However, DUIDs contain an initial two-octet type field which
> distinguishes the various types of DUID, so providing them with
> distinct MNID values is redundant.
>
> Distinguishing the types and allowing only four of them to be used as
> MNIDs seems to be contrary to the philosophy of DUID construction
> (RFC
> 3315 section 9):
>
>     Clients and servers MUST treat DUIDs as opaque values and MUST
> only
>     compare DUIDs for equality.  Clients and servers MUST NOT in any
>     other way interpret DUIDs.  Clients and servers MUST NOT restrict
>     DUIDs to the types defined in this document, as additional DUID
> types
>     may be defined in the future.
>
> Of course, MNID isn't a DHCP operation, so it isn't subject to those
> requirements, but I expect that devices will use the same DUID for
> both mobile identification, and we don't want mobile identification
> to
> restrict future developments of DHCP.
>
> I think this specification must treat DUIDs as opaque and use only
> one
> MNID type that allows all types of DUIDs as values.

Thanks for this observation.  I will make the corresponding revisions to 
the text.

>
> Editorial issues:
>
> Abstract
>
>     Additional Identifier Types are proposed for use with the Mobile
> Node
>     Identifier Option for IPv6 (RFC 4283).
>
> s/proposed/defined/
> This document will define the new types (once it is approved)!

O.K. with your modification.  The document just defines numbers for the 
types, not the types.

>
> 1.  Introduction
>
>     ... types for IMSI
>     [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
> GUTI
>     [ThreeGPP-IDS].
>
> There is no description of P-TMSI identifiers, although it is
> assigned
> identifier type 4.
>
> There is no description of GUTI identifiers, although it is assigned
> identifier type 7.

I will insert text from the relevant 3GPP documents to describe these 
identifiers.

>
> 3.  New Mobile Node Identifier Types
>
>     The following types of identifiers are commonly used to identify
>     mobile nodes.  For each type, references are provided with full
>     details on the format of the type of identifier.
>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     including
>
>     o  RFID-GID (Global Identifier),
>     o  RFID-SGTIN (Serialized Global Trade Item Number),
>     o  RFID-SSCC (Serial Shipping Container),
>     o  RFID-SGLN (Global Location Number),
>     o  RFID-GRAI (Global Returnable Asset Identifier),
>     o  RFID-DOD (Department of Defense ID), and
>     o  RFID-GIAI (Global Individual Asset Identifier).
>
>     For each RFID scheme except GID, there are two variations: a
> 64-bit
>     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
> has
>     only a 96-bit scheme.  Within each scheme, an EPC identifier can
> be
>     represented in a binary form or other forms such as URI.
>
>     The following list includes the above RFID types as well as
> various
>     other common identifiers and several different types of DUIDs.
>
> The organization of the text here seems to be poor -- section 3
> enumerates the new identifier types, but much of the text at the
> beginning of the section is about the RFID-EPC set of types.  It
> seems
> like a better organization is to use just paragraph 1 followed by
> table 1, and move paragraphs 2-5 into section 4.9.

O.K.  Thanks for the suggestion.

>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     including
>
> The text is using "Tag Data", "EPC", and "RFID" in a way that is
> intertwined but not explained.  I can see that it might be useful to
> use all of the terms if they commonly used in the field (don't forget
> to make them keywords for the RFC!), but you need to explain their
> connection and distinction to the reader or make it clear that the
> reader does not need to understand the differences among the terms.
> E.g., this formulation ties all three terms together
>
>     The Tag Data standard promoted by Electronic Product Code(TM)
>     (abbreviated EPC) supports several encoding systems or schemes
>     which are commonly used in RFID (radio-frequency identification)
>     applications, including

Thanks for the text.  I will use it.

> --
>
>     For each RFID scheme except GID, there are two variations: a
> 64-bit
>     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
> has
>     only a 96-bit scheme.  Within each scheme, an EPC identifier can
> be
>     represented in a binary form or other forms such as URI.
>
> The text uses "scheme" to mean the distinction between encoding
> systems (GID, SGTIN, etc.) and and also to mean the distinction
> between the 64-bit and 96-bit variations.  This ambiguity is unwise.
> It matters here, because you say "within each scheme ... can be
> represented in a binary form or ... URI".  Which meaning of "scheme"
> are you using here?  I thought you meant the second meaning when I
> first read the paragraph, but after reading external documents about
> EPC, I now understand that that last sentence uses "scheme" to in the
> first sense.
>
> You need to be clearer here that there are three representations
> used,
> 64-bit binary, 96-bit binary, and URI (URN, actually), and
> representation is orthogonal to the seven RFID schemes, with the
> exception that RFID-GID does not have a 96-bit binary representation.

This is a good idea.  How about the following:

>    For each RFID scheme except GID, there are three representations:
>     - a 64-bit binary representation (for example, SGLN-64)
>     - a 96-bit binary representation (SGLN-96).
>     - a representation as a URI

I didn't originate the use of URI for the non-binary representation. The 
EPC document has the following language:

> All categories of URIs are represented as Uniform Reference Names 
> (URNs) as defined by [RFC2141], where the URN Namespace is epc.
>

If I were to change it to URN, then I would have to go into some detail 
about why this document somehow disagrees with the EPC-Tag-Data 
document.  Do you think that is necessary?

>
> I'm assuming that the Tag Data standard unambiguously defines the
> serialization of the binary representations as a sequence of octets.
> If it does not, this document MUST do that, or you will have an
> endless nightmare of byte-order problems.

I read through some relevant text in the EPC-Tag-Data document and it 
seems O.K. to me, but nontrivial and it relies on digging through other 
even more arcane documents to be absolutely sure.  I am pretty sure that 
the IETF document should not get into the business of augmenting the 
standards already in place from the external SDOs.

>
> 4.  Descriptions of MNID types
>
> Identifier ownership is a general concern -- it's worth mentioning
> for
> each type of identifier where the assigner of the identifier obtains
> delegation.  For an EUI, I expect the reader will assume that it's an
> EUI assigned to the device under IEEE rules, and similarly for RFID
> and 3GPP identifiers.  But for DUID identifiers, it's less clear.
> I'm
> guessing that the DUID is one that is, or could be, used by the
> device
> for DHCP purposes.  For IPv6 addresses, it's even less clear, since
> the IPv6 architecture doesn't assume that the association of
> addresses
> with devices is permanent.

I hope that this document does not have to specify allocation procedures 
for the MNIDs.  It seems to me that if a system designer wants to use 
one of the MNID types, that person will already know about how to 
request the allocation and would not need to rely on the MNIDs document 
for that information.  Plus it's really out of scope.  This document was 
always intended to be a simple tabulation of types already in use 
elsewhere and enabling IETF mobility management protocols to use the 
most natural identifier available for a mobile node.  I hope that citing 
the defining documents for the identifier types will be enough to 
satisfy that.

>
> 4.1.  Description of the IPv6 address type
>
> It would be good if the document described what the semantics of this
> ID are.  Yes, it's a unicast IPv6 address, but what is the connection
> between that address and the device?  I suspect the connection is
> "the
> device has been configured to expect that it will be assigned this
> address as a long-term interface address", but there are other
> possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
> prefix (there are plenty of them!) and then assigning addresses out
> of
> it simply to create a sequence of unique identifiers for devices, but
> not using those addresses on packets.
>
> Then again, perhaps you want to allow flexibility.  But in any case,
> I
> think you need to specify what the rules are for what address is
> associated with what device.

As far as I have understood, the unicast IPv6 address in use as a MNID 
is already assigned to the device.  I have not heard anyone asking for 
this to be an address for future assignment.  I'll try to make that 
clear in the text.

>
> 4.2.  Description of the IMSI MNID type
>
> What does "in network order" mean here?  As far as I know, there is
> no
> defined "network order" for 4-bit quantities, only for dividing
> integers into octets and placing sequences of bits into octets.  I
> assume you mean that in any octet, the high-order 4 bits are the
> first
> digit and the low-order 4 bits are the second digit, but I think you
> need to state that explicitly.

I probably lifted that language directly from the IMSI spec, but I can 
make further clarification according to your suggestion.

>
> 4.3.  Description of the EUI-48 address type
>
>     The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
>     string containing the IEEE EUI-48 address.
>
> Is "string" the correct word, this not being a sequence of
> characters?
> I would say "sequence of 6 octets" or simply "encoded as 6 octets".

O.K.  I also lifted that language from elsewhere.
>
> 4.9.  Description of the RFID types
>
> This section needs to be revised.  It provides a lot of detail about
> the RFID types, but it's not enough detail for a reader who doesn't
> understand RFID to learn how any particular RFID scheme works.  E.g.,
> the first paragraph says that GID contains three fields in the first
> sentence, and that it contains four fields in the third sentence.
> Despite this, the description isn't enough to allow the reader to
> construct GID identifiers manually.
>
> On the other hand, readers who already understand the RFID schemes
> will find this text redundant.
>
> I think that almost all of this text can be replaced by references to
> the EPC documents, since these identifiers are opaque from the point
> of view of mobile identification.

Here I am at a loss, because I was specifically requested to insert some 
descriptive but not normative text.  I will ask the person who made the 
request to provide their feedback on the mailing list.  For myself, I am 
more than happy to delete the text.

>
> 5.  Security Considerations
>
> The base MNID specification, RFC 4283, gives these security
> considerations (sec 4), which ought to be referenced and probably
> summarized in this section:
>
>     Moreover, MNIDs containing sensitive identifiers might only be
> used
>     for signaling during initial network entry.  Subsequent binding
>     update exchanges might then rely on a temporary identifier
> allocated
>     during the initial network entry, perhaps using mechanisms not
>     standardized within the IETF.  Managing the association between
> long-
>     lived and temporary identifiers is outside the scope of this
>     document.
>
> What is the meaning of the word "might" in paragraph 3?  I suspect
> that the purpose is to qualify this paragraph with "One way to
> address
> these vulnerabilities is to only use MNIDs containing ...".  But if
> that is the meaning, that expanded wording should be used.  Otherwise
> the text reads as if it is hypothetical.

This text was meant to be generally descriptive, so that people wanting 
to include the Mobile Node Identifier Option with the relevant MNIDs 
could understand how the identifiers are actually used in various 
circumstances.  I could replace constructions using "might" with "in 
some specifications" or "in some situations" if needed.  Is it also 
necessary to include citations to the relevant documents of the external 
SDO?


Regards,
Charlie P.


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hello Dale,</p>
    <p>Thanks for the thorough review.  My follow-up comments are inline
      below.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 1/31/2017 11:34 AM, Dale Worley
      wrote:<br>
    </div>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">
1. The Introduction states

   Other types of identifiers are in
   common use, and even referenced in RFC 4283.

For the reader's sanity, some sort of accounting needs to be made of
these "other types of identifiers", especially because each type of
identifier needs an identifier type number.  The text in 4283 is

   Some examples of identifiers
   include Network Access Identifier (NAI), Fully Qualified Domain
Name
   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
   Subscriber Number (MSISDN).

Are there any other types "in common use"?</pre>
    </blockquote>
    <br>
    I will add some text according to your suggestion.  My criterion for
    whether the identifier type was included in the document was whether
    or not anyone had asked for it to be included.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

- NAI (type 1) is defined by 4283.
- Fully Qualified Domain Name (FQDN) seems not to be specified
- International Mobile Station Identifier (IMSI) (type 3) is defined
in
  this draft
- Mobile Subscriber Number (MSISDN) seems not to be specified</pre>
    </blockquote>
    <br>
    It is not the jurisdiction of the MNIDs document to specify these
    identifiers, but citations for the specifications are located
    elsewhere in the document.  I will also include those citations
    here.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

2. Is it intended to have an IMEI identifier type?  The introduction
mentions an IMEI type, but there is no specification for it, nor is
there an identifier type number assigned for it.

   ... types for IMSI
   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
GUTI
   [ThreeGPP-IDS].

Initially I suspected it was it was present in an earlier revision
and
then later deleted without this reference being updated.  But all
versions of draft-ietf-dmm-4283mnids and its predecessor
draft-perkins-dmm-4283mnids mention IMEI in this way as one
identifier
type, but none specify it in any way.  The only discussion I can find
on the DMM mailing list of IMEI is:

   
<a class="moz-txt-link-freetext" href="https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af">https://mailarchive.ietf.org/arch/msg/dmm/pNmtaq6-JOQ4RuXy_D7Zc2JgvYk/?qid=d29575f767ce67a1e67a7767008ee6af</a>

    From: Marco Liebsch <a class="moz-txt-link-rfc2396E" href="mailto:Marco.Liebsch@neclab.eu">&lt;Marco.Liebsch@neclab.eu&gt;</a>
    To: DMM
    Date: Wed, 10 September 2014 13:29 UTC
    Re: [DMM] regarding the re-chartering..

    It seems the MNID is somehow overloaded to carry both,
node-specific
    IDs, e.g. MAC, as well as subscriber IDs, which is the IMSI.
    There may be value in adding the IMEI to the list of possible
types of
    node-specific IDs. 

Either the presence of IMEI in this list is a simple mistake that has
persisted in all versions of the draft, or specifying IMEI has always
been intended but has always been overlooked.</pre>
    </blockquote>
    <br>
    I don't know why this happened, but I am happy to include an
    identifier type for IMEI as well as a citation for it.  Thanks for
    catching this and looking through the archives!<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

3. The definition of identifier types for both EUI-48 and EUI-64
suggests that it might be desirable to define an identifier type for
arbitrary hardware (link-level) addresses.  It seems that the natural
differentiator for that purpose is the "hardware type" used in ARP,
so
a EUI-48 address would be represented as

    MN identifier type (one octet) 5 (say)
    hardware type (two octets) 1
    EUI-48 (six octets)

and an EUI-64 similarly, with hardware type 27.

Although with only two subtypes in common use, generalizing this
might
not be worth the effort.</pre>
    </blockquote>
    <br>
    Actually, I am O.K. either way on this matter.  However, at this
    point in time it does not seem that we are likely to see any other
    link hardware address types to be used as MNIDs.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4. Several of the identifier types can be represented as URNs:

- IMEI can be represented as a URN as urn:gsma:imei:...
- all of the RFID types have a URN representation (called the
  "pure-identity URI" in the RFID specifications), which starts
  urn:epc:id:...

Since all URN types are ensured of being unique and persistent, it
seems that we could define a MNID type for URNs generally, and then
any RFID URI or an IMEI (as a URN) could be used as a value of that
type.

If this idea is adopted, it seems that the other 3GPP types (IMSI,
P-TMSI, and GUTI) should be given defined encodings as URNs in new
sub-namespaces of the "gsma" URN namespace, to parallel the encoding
of IMEIs defined in RFC 7254.

This consolidation could be significantly beneficial.  It allows MNID
to use any URN scheme as an identifier.  It reduces the three
different RFID representations to one.  It incorporates any future
expansion of RFID schemes (because all schemes will have a
pure-identity URN representation).  A disadvantage is that the URN
encodings are long, but the security considerations section states
that MNIDs are used only on the first registration at the home agent,
so there isn't much need for brevity.

Similarly, this approach incorporates any future expansion of mobile
identifiers that GSMA decides to define, as long as GSMA provides a
URN representation for it.

The most significant disadvantage is that some URN schemes allow
several character strings to "mean" the same URN.  In most URN
schemes, the allowed variation is limited to the case of letters, and
the common convention is to always use lower-case when there is a
choice, leading to a unique conventional canonical form for the URN.</pre>
    </blockquote>
    <br>
    There is a sort of "hidden" disadvantage to long names, especially
    for tiny devices using constrained link layers.  Namely, a longer
    name makes it more likely to require lower-layer fragmentation.  I'm
    not sure that it should be the job of a layer-3 mobility entity to
    parse URNs and determine if two different flavors are supposed to be
    equivalent.<br>
    <br>
    Other than that, I don't have any real objection to reorganizing the
    namespace, but I'd like some additional confirmation that it's a
    good idea.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

5. Regarding the encoding of a string of digits into octets, it is
stated that "The last digit MUST be zero padded, if needed, for full
octet size."  This seems very unwise unless there is a 3GPP decree
that if a zero is appended to a valid IMSI, the resulting string is
never a valid IMSI.  Instead, I would specify that padding is by
filling the low-order 4 bits of the final octet with 0xF.  That
ensures that the encoding can be uniquely decoded into an IMSI.</pre>
    </blockquote>
    <br>
    I am O.K. with this.  I need to go find out where I got that
    language from, because I don't think I was the person who crafted
    it.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

6. There are four types of DUID specified, each with a distinct MNID
value.  However, DUIDs contain an initial two-octet type field which
distinguishes the various types of DUID, so providing them with
distinct MNID values is redundant.

Distinguishing the types and allowing only four of them to be used as
MNIDs seems to be contrary to the philosophy of DUID construction
(RFC
3315 section 9):

   Clients and servers MUST treat DUIDs as opaque values and MUST
only
   compare DUIDs for equality.  Clients and servers MUST NOT in any
   other way interpret DUIDs.  Clients and servers MUST NOT restrict
   DUIDs to the types defined in this document, as additional DUID
types
   may be defined in the future.

Of course, MNID isn't a DHCP operation, so it isn't subject to those
requirements, but I expect that devices will use the same DUID for
both mobile identification, and we don't want mobile identification
to
restrict future developments of DHCP.

I think this specification must treat DUIDs as opaque and use only
one
MNID type that allows all types of DUIDs as values.</pre>
    </blockquote>
    <br>
    Thanks for this observation.  I will make the corresponding
    revisions to the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

Editorial issues:

Abstract

   Additional Identifier Types are proposed for use with the Mobile
Node
   Identifier Option for IPv6 (RFC 4283).

s/proposed/defined/
This document will define the new types (once it is approved)!</pre>
    </blockquote>
    <br>
    O.K. with your modification.  The document just defines numbers for
    the types, not the types.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

1.  Introduction

   ... types for IMSI
   [ThreeGPP-IDS], P-TMSI [ThreeGPP-IDS], IMEI [ThreeGPP-IDS], and
GUTI
   [ThreeGPP-IDS].

There is no description of P-TMSI identifiers, although it is
assigned
identifier type 4.

There is no description of GUTI identifiers, although it is assigned
identifier type 7.</pre>
    </blockquote>
    <br>
    I will insert text from the relevant 3GPP documents to describe
    these identifiers.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

3.  New Mobile Node Identifier Types

   The following types of identifiers are commonly used to identify
   mobile nodes.  For each type, references are provided with full
   details on the format of the type of identifier.

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   including

   o  RFID-GID (Global Identifier),
   o  RFID-SGTIN (Serialized Global Trade Item Number),
   o  RFID-SSCC (Serial Shipping Container),
   o  RFID-SGLN (Global Location Number),
   o  RFID-GRAI (Global Returnable Asset Identifier),
   o  RFID-DOD (Department of Defense ID), and
   o  RFID-GIAI (Global Individual Asset Identifier).

   For each RFID scheme except GID, there are two variations: a
64-bit
   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
has
   only a 96-bit scheme.  Within each scheme, an EPC identifier can
be
   represented in a binary form or other forms such as URI.

   The following list includes the above RFID types as well as
various
   other common identifiers and several different types of DUIDs.

The organization of the text here seems to be poor -- section 3
enumerates the new identifier types, but much of the text at the
beginning of the section is about the RFID-EPC set of types.  It
seems
like a better organization is to use just paragraph 1 followed by
table 1, and move paragraphs 2-5 into section 4.9.</pre>
    </blockquote>
    <br>
    O.K.  Thanks for the suggestion.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   including

The text is using "Tag Data", "EPC", and "RFID" in a way that is
intertwined but not explained.  I can see that it might be useful to
use all of the terms if they commonly used in the field (don't forget
to make them keywords for the RFC!), but you need to explain their
connection and distinction to the reader or make it clear that the
reader does not need to understand the differences among the terms.
E.g., this formulation ties all three terms together

   The Tag Data standard promoted by Electronic Product Code(TM)
   (abbreviated EPC) supports several encoding systems or schemes
   which are commonly used in RFID (radio-frequency identification)
   applications, including</pre>
    </blockquote>
    <br>
    Thanks for the text.  I will use it.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">--

   For each RFID scheme except GID, there are two variations: a
64-bit
   scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID
has
   only a 96-bit scheme.  Within each scheme, an EPC identifier can
be
   represented in a binary form or other forms such as URI.

The text uses "scheme" to mean the distinction between encoding
systems (GID, SGTIN, etc.) and and also to mean the distinction
between the 64-bit and 96-bit variations.  This ambiguity is unwise.
It matters here, because you say "within each scheme ... can be
represented in a binary form or ... URI".  Which meaning of "scheme"
are you using here?  I thought you meant the second meaning when I
first read the paragraph, but after reading external documents about
EPC, I now understand that that last sentence uses "scheme" to in the
first sense.

You need to be clearer here that there are three representations
used,
64-bit binary, 96-bit binary, and URI (URN, actually), and
representation is orthogonal to the seven RFID schemes, with the
exception that RFID-GID does not have a 96-bit binary representation.</pre>
    </blockquote>
    <br>
    This is a good idea.  How about the following:<br>
    <br>
    <blockquote type="cite">   For each RFID scheme except GID, there
      are three representations:<br>
          - a 64-bit binary representation (for example, SGLN-64)<br>
          - a 96-bit binary representation (SGLN-96).<br>
          - a representation as a URI</blockquote>
    <br>
    I didn't originate the use of URI for the non-binary representation.
    The EPC document has the following language:<br>
    <br>
    <blockquote type="cite">
      <div style="left: 520.439px; top: 898.022px; font-size: 18.6471px;
        font-family: serif; transform: scaleX(0.99895);">
        <p>All categories of URIs are represented as Uniform Reference
          Names (<span class="highlight selected">URN</span>s) as
          defined by [RFC2141], where the URN Namespace is   <tt>epc</tt>.
        </p>
      </div>
    </blockquote>
    <br>
    If I were to change it to URN, then I would have to go into some
    detail about why this document somehow disagrees with the
    EPC-Tag-Data document.  Do you think that is necessary? <br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

I'm assuming that the Tag Data standard unambiguously defines the
serialization of the binary representations as a sequence of octets.
If it does not, this document MUST do that, or you will have an
endless nightmare of byte-order problems.</pre>
    </blockquote>
    <br>
    I read through some relevant text in the EPC-Tag-Data document and
    it seems O.K. to me, but nontrivial and it relies on digging through
    other even more arcane documents to be absolutely sure.  I am pretty
    sure that the IETF document should not get into the business of
    augmenting the standards already in place from the external SDOs.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.  Descriptions of MNID types

Identifier ownership is a general concern -- it's worth mentioning
for
each type of identifier where the assigner of the identifier obtains
delegation.  For an EUI, I expect the reader will assume that it's an
EUI assigned to the device under IEEE rules, and similarly for RFID
and 3GPP identifiers.  But for DUID identifiers, it's less clear. 
I'm
guessing that the DUID is one that is, or could be, used by the
device
for DHCP purposes.  For IPv6 addresses, it's even less clear, since
the IPv6 architecture doesn't assume that the association of
addresses
with devices is permanent.</pre>
    </blockquote>
    <br>
    I hope that this document does not have to specify allocation
    procedures for the MNIDs.  It seems to me that if a system designer
    wants to use one of the MNID types, that person will already know
    about how to request the allocation and would not need to rely on
    the MNIDs document for that information.  Plus it's really out of
    scope.  This document was always intended to be a simple tabulation
    of types already in use elsewhere and enabling IETF mobility
    management protocols to use the most natural identifier available
    for a mobile node.  I hope that citing the defining documents for
    the identifier types will be enough to satisfy that.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.1.  Description of the IPv6 address type

It would be good if the document described what the semantics of this
ID are.  Yes, it's a unicast IPv6 address, but what is the connection
between that address and the device?  I suspect the connection is
"the
device has been configured to expect that it will be assigned this
address as a long-term interface address", but there are other
possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
prefix (there are plenty of them!) and then assigning addresses out
of
it simply to create a sequence of unique identifiers for devices, but
not using those addresses on packets.

Then again, perhaps you want to allow flexibility.  But in any case,
I
think you need to specify what the rules are for what address is
associated with what device.</pre>
    </blockquote>
    <br>
    As far as I have understood, the unicast IPv6 address in use as a
    MNID is already assigned to the device.  I have not heard anyone
    asking for this to be an address for future assignment.  I'll try to
    make that clear in the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.2.  Description of the IMSI MNID type

What does "in network order" mean here?  As far as I know, there is
no
defined "network order" for 4-bit quantities, only for dividing
integers into octets and placing sequences of bits into octets.  I
assume you mean that in any octet, the high-order 4 bits are the
first
digit and the low-order 4 bits are the second digit, but I think you
need to state that explicitly.</pre>
    </blockquote>
    <br>
    I probably lifted that language directly from the IMSI spec, but I
    can make further clarification according to your suggestion.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.3.  Description of the EUI-48 address type

   The IEEE EUI-48 address [IEEE802-eui48] is encoded as a 6 octet
   string containing the IEEE EUI-48 address.

Is "string" the correct word, this not being a sequence of
characters?
I would say "sequence of 6 octets" or simply "encoded as 6 octets".</pre>
    </blockquote>
    <br>
    O.K.  I also lifted that language from elsewhere.<br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.</pre>
    </blockquote>
    <br>
    Here I am at a loss, because I was specifically requested to insert
    some descriptive but not normative text.  I will ask the person who
    made the request to provide their feedback on the mailing list.  For
    myself, I am more than happy to delete the text.<br>
    <br>
    <blockquote
cite="mid:148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com"
      type="cite">
      <pre wrap="">

5.  Security Considerations

The base MNID specification, RFC 4283, gives these security
considerations (sec 4), which ought to be referenced and probably
summarized in this section:

   Moreover, MNIDs containing sensitive identifiers might only be
used
   for signaling during initial network entry.  Subsequent binding
   update exchanges might then rely on a temporary identifier
allocated
   during the initial network entry, perhaps using mechanisms not
   standardized within the IETF.  Managing the association between
long-
   lived and temporary identifiers is outside the scope of this
   document.

What is the meaning of the word "might" in paragraph 3?  I suspect
that the purpose is to qualify this paragraph with "One way to
address
these vulnerabilities is to only use MNIDs containing ...".  But if
that is the meaning, that expanded wording should be used.  Otherwise
the text reads as if it is hypothetical.</pre>
    </blockquote>
    <br>
    This text was meant to be generally descriptive, so that people
    wanting to include the Mobile Node Identifier Option with the
    relevant MNIDs could understand how the identifiers are actually
    used in various circumstances.  I could replace constructions using
    "might" with "in some specifications" or "in some situations" if
    needed.  Is it also necessary to include citations to the relevant
    documents of the external SDO?<br>
    <br>
    <br>
    Regards,<br>
    Charlie P.<br>
    <br>
  </body>
</html>

--------------34D9108758E61C1C73F50279--


From nobody Fri Feb 10 17:02:46 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89A73129596; Fri, 10 Feb 2017 17:02:44 -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 autolearn_force=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 iDOjZjm3Bs6B; Fri, 10 Feb 2017 17:02:43 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 9C4EE1295C7; Fri, 10 Feb 2017 17:02:43 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ccM5B-0006J8-He; Sat, 11 Feb 2017 01:02:33 +0000
Date: Sat, 11 Feb 2017 10:02:30 +0900
Message-ID: <m2y3xdpmjd.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
In-Reply-To: <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4EjCOpbrlqDXROZBflViP8kpvtg>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 01:02:44 -0000

> While I largely agree with Fernando on everything he said, I have to
> admit most of the points are just repeated from the 6man discussion,
> and won't get us anywhere new by discussing these again at this point.

excuse?  this is why we have ietf last call.

randy


From nobody Fri Feb 10 17:12:35 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A888129511 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 17:12:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqMdLP2xs4A7 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 17:12:32 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 A252A1293F3 for <ietf@ietf.org>; Fri, 10 Feb 2017 17:12:32 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id v23so50735331qtb.0 for <ietf@ietf.org>; Fri, 10 Feb 2017 17:12:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yJa5fhjIf0Xc670ETq61hDSCENbVGGwMCg55ufZCWhw=; b=a8oA8VoADx1+5YsdTh6DKKtkaYCubf2e9JPxJ0tdRs96OsTXCCTGE+R6dJha06Rm3j cfe5EanomYL6+Pk8VOUJPnBZ+mgJzeKZytJAcgG5GSt6rOK2wiTTrPXZwoxLW/kFwGzh dL2eE4Mfj2QDsXEwAziSiuMIvKcfESQqiku4C7ehZKO+7etFmVQ0XY0k7aAuidTJnQ8A ezxnbD3lYZGuoHdyyX6mR4cQTUDUX3xDvnI8j10uzi0n/wUDPtJOFrEeRglzq7KTi/3L C7VKcPtZ24NsTmjuKm2FG6AqeKgPPS7UotIjLOARnHnL6EWWGSmX9XAGBjd6pDJybhK5 uOoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yJa5fhjIf0Xc670ETq61hDSCENbVGGwMCg55ufZCWhw=; b=JfaQOFyT8CrBXqb6+CPdb5HLuko3bGPXKx50FG0gJS3ZEZgObb/1zTywq6qDsGzDTT Co0H7h7YYosJ8XjxEQBK0dXnPneNmi9qGWJcqtjMXzYV5mgypWu98ftjhWgzYkzI58Ds +fShUfnjzsuoQAY8lox9FzmRLWtYaLpWPlG268WHWVVSVIcEKB8vzUMc/7XdAVSDiDTs Kz9vUFSEzFGv8EGhUwGAEQ+jGMfHe5zISMoqMlwCpLBKEogBZUXy72qQ2KOiv/n4cqNh 9RiGQivRZjL+7c1IhuSYX3Mo1aiZXUprK5zZ+5JLXxCs99HSSAn0VzesjKLhyUSShvVk wNog==
X-Gm-Message-State: AMke39lhKEOUjidhPsgx5NVzKrM2M/QM82madrW5x1wRTupudv7OAQQK6Y4KiJDAVRiHow==
X-Received: by 10.200.57.75 with SMTP id t11mr11571694qtb.274.1486775551863; Fri, 10 Feb 2017 17:12:31 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f128sm1041975qkd.62.2017.02.10.17.12.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 17:12:30 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B3E2C1E0-EC17-4CC6-BF26-39427CF40AB2"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 10 Feb 2017 20:12:28 -0500
In-Reply-To: <m2y3xdpmjd.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y9rwmfa6XGXNEwHu4BtMgvH2orI>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 01:12:34 -0000

--Apple-Mail=_B3E2C1E0-EC17-4CC6-BF26-39427CF40AB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 10, 2017, at 8:02 PM, Randy Bush <randy@psg.com> wrote:
> excuse?  this is why we have ietf last call.

No, we do not have IETF last call so that people who participated in the =
working group discussion can re-litigate the points they lost on in the =
working group discussion.


--Apple-Mail=_B3E2C1E0-EC17-4CC6-BF26-39427CF40AB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 10, 2017, at 8:02 PM, Randy Bush &lt;<a =
href=3D"mailto:randy@psg.com" class=3D"">randy@psg.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">excuse? &nbsp;this is why we have ietf last =
call.</span><br style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote></div><br class=3D""><div class=3D"">No, =
we do not have IETF last call so that people who participated in the =
working group discussion can re-litigate the points they lost on in the =
working group discussion.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_B3E2C1E0-EC17-4CC6-BF26-39427CF40AB2--


From nobody Fri Feb 10 17:18:04 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAA71294FD; Fri, 10 Feb 2017 17:17:59 -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 autolearn_force=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 7H1r0ksxtfkP; Fri, 10 Feb 2017 17:17:57 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 885AD1293F3; Fri, 10 Feb 2017 17:17:57 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ccMK0-0006U5-C6; Sat, 11 Feb 2017 01:17:52 +0000
Date: Sat, 11 Feb 2017 10:17:49 +0900
Message-ID: <m2wpcxpltu.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
In-Reply-To: <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y3Bx1x2X-UZDBs1Bi-mch9sgtCI>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@wide.ad.jp>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 01:17:59 -0000

>> excuse?  this is why we have ietf last call.
> 
> No, we do not have IETF last call so that people who participated in
> the working group discussion can re-litigate the points they lost on
> in the working group discussion.

cite?

and those of us who gave up on 6stonewall years ago appreciate a more
open discussion on the ietf list, tyvm.

randy


From nobody Fri Feb 10 17:32:38 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903F21295CF for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 17:32:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K1zqNtA3Jpoj for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 17:32:35 -0800 (PST)
Received: from mail-pg0-x236.google.com (mail-pg0-x236.google.com [IPv6:2607:f8b0:400e: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 0421E129492 for <ietf@ietf.org>; Fri, 10 Feb 2017 17:32:35 -0800 (PST)
Received: by mail-pg0-x236.google.com with SMTP id 194so15040195pgd.2 for <ietf@ietf.org>; Fri, 10 Feb 2017 17:32:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=LkKS9jHg3vEFini4kBGlsC8B4KkCYKfYyNkwxaErQ00=; b=iCl/4vxJA0+XMOrqtVg9pngPqATm/k4XV0NwRe7rP+RBnrpEdn+DExKAubUITcYhKW R3Wxs9BsHTzfFhVJiTtmxcgpXiArGuzPlMQeft2L4XWKeEe4vrRlM4SQfQK98nqQ1Yap Dc++bz1jeGxfppXwnFmnt86NvYUu4BQKkPtPrMVTaom8yUDQZh/U7Z+X+0PvB5PJM63V sq7HT7MdZlLHWCEnXP/RKiN80rn0ZnpF025sbyJkoqXR5n52qdK+wa6YkNMMvI/RCEFE 6gVvsS1+V+E5UhNOAquzS+y4ewRBELLVkgJx32HUUKQbJZN4O5xZrscTAPcuIqkJx2hI t3Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=LkKS9jHg3vEFini4kBGlsC8B4KkCYKfYyNkwxaErQ00=; b=ftRTrAwS5JHjp4MI1uHrMh7Re+BXo99vAyAG7phH7u6fsFE4V62KFdOEqnIegG+O9y EhSZH9S60hA+tOoNXnME0RnULjmh7NX1dV/oEFy6HAodBQtA3kCFezay2gLxnuoLBRqO 6UzZTTHfkvIP7/u+YPSh+nE2gbfFK7aoqd0zulnPE2J2TJ2RXXmCiiaePqblaKM8/056 dD19EKkdZv9EeCEaXKZy973ZB0ANb3dBhVaa3nbS7G1x2AuegiFtyg5/IctGOafZpZ9l hT+bbDRTE74mJpNlBD8IeCR+NNDT/OvFWtknKvVEo9PxGfaYporI3pBxvZlHz2FHv9ZK YEBw==
X-Gm-Message-State: AMke39kKLH8auIphM+aNWD3MjiiCsLnYM5TvGP65zyfE4tMrnC0PEYUnc7/Ix9dVlSG8wA==
X-Received: by 10.84.148.134 with SMTP id k6mr15377129pla.142.1486776754358; Fri, 10 Feb 2017 17:32:34 -0800 (PST)
Received: from ?IPv6:2406:e007:769c:1:28cc:dc4c:9703:6781? ([2406:e007:769c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k78sm7727514pfb.93.2017.02.10.17.32.32 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 17:32:33 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com>
Date: Sat, 11 Feb 2017 14:32:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fWeBRkE1Eb5E4GWnvQKNYcdyTdM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 01:32:36 -0000

On 11/02/2017 14:12, Ted Lemon wrote:
> On Feb 10, 2017, at 8:02 PM, Randy Bush <randy@psg.com> wrote:
>> excuse?  this is why we have ietf last call.
> 
> No, we do not have IETF last call so that people who participated in the working group discussion can re-litigate the points they lost on in the working group discussion.

I was fairly specific when I raised the issue at
https://mailarchive.ietf.org/arch/msg/ietf/myyPO9b4dYfYeGQrdPjTNzIHArY

>> I do not dispute that this sentence reached WG consensus. However, I want
>> to ask if it has IETF consensus.

If people who were not involved in the 6man debate have opinions, it would
be useful to hear from them. I agree that there is no point in the same
people repeating the same arguments.

     Brian


From nobody Fri Feb 10 18:03:06 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB931295E8; Fri, 10 Feb 2017 18:03:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 voh7ETHOUTfq; Fri, 10 Feb 2017 18:03:03 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (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 39852129522; Fri, 10 Feb 2017 18:03:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id B3EDA3A1F335; Fri, 10 Feb 2017 21:03:00 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAiCKdqRhTPD; Fri, 10 Feb 2017 21:03:00 -0500 (EST)
Received: from [10.101.3.168] (ec2-52-55-200-77.compute-1.amazonaws.com [52.55.200.77]) by sobco.sobco.com (Postfix) with ESMTPSA id 934B93A1F322; Fri, 10 Feb 2017 21:02:58 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
From: Scott Bradner <sob@sobco.com>
In-Reply-To: <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
Date: Fri, 10 Feb 2017 21:02:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9937846C-5057-427B-AA69-A2F2754DA6EE@sobco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LXH0N3XpyOpWn9I6QQv1gmSaGkQ>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 02:03:04 -0000

kinda a cynical view

Scott

> On Feb 10, 2017, at 8:12 PM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> On Feb 10, 2017, at 8:02 PM, Randy Bush <randy@psg.com> wrote:
>> excuse?  this is why we have ietf last call.
>=20
> No, we do not have IETF last call so that people who participated in =
the working group discussion can re-litigate the points they lost on in =
the working group discussion.
>=20


From nobody Fri Feb 10 18:29:43 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34543129529 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 18:29:42 -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=unavailable autolearn_force=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 mubsUezS0hSz for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 18:29:41 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 54DAE129464 for <ietf@ietf.org>; Fri, 10 Feb 2017 18:23:36 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ccNLZ-0007Fb-VE; Sat, 11 Feb 2017 02:23:34 +0000
Date: Sat, 11 Feb 2017 11:23:31 +0900
Message-ID: <m2poippisc.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
In-Reply-To: <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6b7-dhVEguSx-YMgfnaM26-TzOM>
Cc: IETF Rinse Repeat <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 02:29:42 -0000

> If people who were not involved in the 6man debate have opinions, it
> would be useful to hear from them. I agree that there is no point in
> the same people repeating the same arguments.

in the absence of a (somewhat unbiased) summary of the critical
issues(s), what do you suggest?

randy


From nobody Fri Feb 10 19:10:46 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBB29129489 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 19:10:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1YBDDwMB-9d for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 19:10:43 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::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 77823129415 for <ietf@ietf.org>; Fri, 10 Feb 2017 19:10:43 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id 202so10557179pfx.2 for <ietf@ietf.org>; Fri, 10 Feb 2017 19:10:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=rTw/MT2IPSLnA79xsD2SyuGxQqe3YfopuyQmF6tojiU=; b=PFDqAaot/P5OsCKtSXnsCCzMuDG7EisTmUtIJAu4XOERl93vjAxI6KALSPSk4G+Yyg Ug39qduXweBX83EhvyRkbH1qc2Ndy7SuO0Nx5W9LJo+Z5bbNoXkOoB9x38//Zp4fJE4B VcrsWKJh0oBmViw0Jy3VzWuwxDyYnDjv144ihLnRaRrkYYkC2ytoTh7CWABTBXZ3B3zG YUuCvlR+AgmxGAqvNGuzFEe6z1V0bBkYN5q48LU4BU/BOsrTQz7bLGD/5f7M9SJDCQg6 UtidH7AwGVs0v+so8KV2KUMbZhT3tfb6hoK5zXsaqjN/YTzk26FE0lyS9CmIPfNOHQz5 emJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=rTw/MT2IPSLnA79xsD2SyuGxQqe3YfopuyQmF6tojiU=; b=EWbt7cRtLIs7qI2W13Z0hjwKUyQRbKoiNFOw7ARt6h/HRo0l+ZscIKu7iPmCU1ve8E HKuxEGHaQRM5JBi4ZD/euEhrbZRclvhdlAmocM0OP2ipOYcO1gBk7mzi3YIxfKETYOmA nyip2McdlN58PSIkzWQOeiNKFvBHnc9tKT5NpESlVYfUzpyyyccLrehmIoRWjtE/0+9X F5gVBJT/yEpvhCD6/evBraZa57niYzz2laQIowhfcLNY4R1QarJ+6MdtQgdBOa40d/b9 d+ci1gEGiKbmFYvcAMT0RkjSWZf+Cz5gU6z9ZllMjTKpHECpSL3ymp4FMrTAWw/d+kP7 lRDw==
X-Gm-Message-State: AMke39m9bFznuzsr35fmUMxKdaDGeJonWN2x3RnP8btXjgbJxuxdVhxJx6EzHs0tDdxSuw==
X-Received: by 10.99.136.198 with SMTP id l189mr14500535pgd.45.1486782642858;  Fri, 10 Feb 2017 19:10:42 -0800 (PST)
Received: from ?IPv6:2406:e007:769c:1:28cc:dc4c:9703:6781? ([2406:e007:769c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id z70sm7977889pff.26.2017.02.10.19.10.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 19:10:41 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Randy Bush <randy@psg.com>, IETF discussion list <ietf@ietf.org>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com>
Date: Sat, 11 Feb 2017 16:10:49 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <m2poippisc.wl-randy@psg.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ihxp07dzsCaaYAbV4xMsaMbkqhM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 03:10:45 -0000

On 11/02/2017 15:23, Randy Bush wrote:
>> If people who were not involved in the 6man debate have opinions, it
>> would be useful to hear from them. I agree that there is no point in
>> the same people repeating the same arguments.
> 
> in the absence of a (somewhat unbiased) summary of the critical
> issues(s), what do you suggest?

I was going to say this off list, but what the heck?

To be honest I'm trying to stay quiet. I think I've made my opinion
plain, and although I am of course the only human being alive who doesn't
suffer from confirmation bias, I'd *really* like to hear what people
think whose opinion I haven't already heard 20 times.

I try not to be a purist. If the right answer is to allow packet
modifications that break PMTUD and IPsec/AH, let's do it, but let's
also say we're doing it. (I happen to think it's the wrong answer,
but that's my problem.) Leaving the text open to interpretation
would make a mockery of promoting it to Standard.

Regards
   Brian


From nobody Fri Feb 10 19:23:17 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC873129650 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 19:23:15 -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 autolearn_force=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 qWU4FmFi-y2m for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 19:23:15 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 CFAE812963A for <ietf@ietf.org>; Fri, 10 Feb 2017 19:23:14 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ccOHI-0007xQ-NN; Sat, 11 Feb 2017 03:23:13 +0000
Date: Sat, 11 Feb 2017 12:23:10 +0900
Message-ID: <m2o9y9pg0x.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
In-Reply-To: <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vTwygu8JgJwOU9pUxKZMYwc1y5A>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 03:23:16 -0000

just to get down a level from meta-

> If the right answer is to allow packet modifications that break PMTUD
> and IPsec/AH, let's do it, but let's also say we're doing it.

obvious imiho

> I happen to think it's the wrong answer, but that's my problem.

i share it, but this is at the border of my expertise.  i have this
fantasy of pmtu actually working before i retire.  i realize it is
unrealistic.

> Leaving the text open to interpretation would make a mockery of
> promoting it to Standard.

agree.  but v6 specs seem to like wussing out and leaving the
opportunity to do wrong things.  i'll bet you a reuben at the corned
beef factory in chicago that the next try at the addressing architecture
still does not *unambiguously* state cidr except for slaac.

randy


From nobody Fri Feb 10 20:29:32 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07C631296C7; Fri, 10 Feb 2017 20:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E5Qaokb2pXGX; Fri, 10 Feb 2017 20:29:17 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A79771296C5; Fri, 10 Feb 2017 20:29:17 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 0EA2568668; Fri, 10 Feb 2017 23:29:16 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=J7x pklY1odrNjGqVtYjz9B4uWZY=; b=yXaBLrCPnxLafx7D0qum3k4NbB8+xyx7iEz 00imc1/3MTaNr3bcUq02dfnDzEMOdyxbjLuWZiGp4yb3b4fEtmXVNUikXp59fIV0 vUPAYFrx6q8UJYHIUc34hr9PNn6SEZGLbcN1P2Mp14BWtR558buoJY7tKuDDQsfk Ib5UGjoY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= smNhL4F9gBpktzecOhqVX2/Y/pcw8ZnrULbK3OzIXeZHwMIv5jNzwV9JbH7WPbpF gw3wimCUVKgp4KhiA/bAN+PN+TKoI56z7iZnLsCdQEprXP/FaPOe57K398AG4hVF BrjS0x+IeYwf4FwJT/gRD6T8FkIvXGtT/uCnmLcZmeY=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 047F168667; Fri, 10 Feb 2017 23:29:16 -0500 (EST)
Received: from mail-qk0-f169.google.com (unknown [209.85.220.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 6C89868664; Fri, 10 Feb 2017 23:29:15 -0500 (EST)
Received: by mail-qk0-f169.google.com with SMTP id 11so58490805qkl.3; Fri, 10 Feb 2017 20:29:15 -0800 (PST)
X-Gm-Message-State: AMke39lwbW0OzJwPBXJ578D/czmoj6CgBusemGyn2JSypeqMnxPbF/2P4Vy6/W3vgl9MqZsHq+UyKUG6dqBVGg==
X-Received: by 10.55.119.1 with SMTP id s1mr12786187qkc.81.1486787354703; Fri, 10 Feb 2017 20:29:14 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Fri, 10 Feb 2017 20:28:54 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Fri, 10 Feb 2017 20:28:54 -0800
X-Gmail-Original-Message-ID: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
Message-ID: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: A54B2766-F012-11E6-98C3-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fyqCsGNlkp3R915NvQvmWL6I_Ko>
Cc: Stewart Bryant <stewart@g3ysx.org.uk>, Gen-ART <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 04:29:19 -0000

On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> On 10/02/2017 23:20, Stewart Bryant wrote:
> > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > I wonder if we would best serve both our future and our heritage
> > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > or declared it as historic and wrote a new text from a clean start?
> > >
> > > I don't see that. It's a stable, widely deployed, interoperable
> > > mechanism. That is rather orthogonal to the issue that has been raised,
> > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > across the Internet.
> >
> > I will not debate whether it is faulty or not,
>
> It's faulty by the standard of RFC4890 (which is Informational).
>
> > but it seems that in practice the Internet breaks the mechanism.
> > However it breaks it is a way that seems disruptive to some user
> > traffic. The document is really guidance one how hosts might use
> > ICMP for optimization, and arguabl[y] need not be a standard at all.
>
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes.

Actually, no. You do not have to use PMTUD to avoid black holes.
Other options include:

- Send packets no larger than 1280 bytes (this is always an option)
- Use PLPMTUD (for transports that do their own packetization and
  that can detect packet loss)

> > My remark about heritage is that this vintage draft is very much a
> > product of its time, and really needs modernizing, and after
> > modernizing ought to look quite different, and thus maybe we
> > should employ a procedure other than a simple replacement.

I am afraid that I have to agree with this. Classic PMTUD by itself
is today not enough, but it can be a very useful optimization to
augment other techniques.

> It's proposed for Internet Standard. That means it must replace the
> PS document and must specify the same thing, plus corrections,
> minus unused features.

All true, and my conclusion is that is it should not be promoted to IS.
I would have no problem with republishing at PS to correct the errata
and aid the eventual advance of RFC 4821 (PLPMTUD).

If this document does go forward, the words in Appendix B (Changes
Since RFC 1981) relating to RFC 4821 should be removed, since
there was no mention of RFC 4821 in RFC 1981.

Mike Heard


From nobody Fri Feb 10 22:11:16 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F35712946F; Fri, 10 Feb 2017 22:11:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h3gDHAB80b8J; Fri, 10 Feb 2017 22:11:09 -0800 (PST)
Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (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 BC28612944C; Fri, 10 Feb 2017 22:11:09 -0800 (PST)
Received: by mail-vk0-x243.google.com with SMTP id n125so4154262vke.3; Fri, 10 Feb 2017 22:11:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8KzNrGWVx/RP5HFg/oFwWhAt/41VhhYaKedxm5zados=; b=uGl6V5ZX2mJ1Po9G0Y4aEmcbYWpaUQsE27eoQ8LFZCY7iM5n0dwkyeRl8o2UTRFNgw 4lfBFCnPVBzYP+AA+bCwrVftewjUyxWPWvV0iGrU+259WR2coADp6O1qC64pHJ3eIyYk HMagyBnVPb8hWRLN1eDA7RJPSSdNNI9vXCOTUcTYqAMTV292Hq01pBbUBKhx/nLxvwhH yO8Fk0qdqxADEcZAuKVGMCxqV3DzyaKeFWJe6bi0sehFKqRJ3TMOBPO12ylaQQiyUQti LyL+yz+YHLf6fspnyy51HwuM1Phv6rUTGBoZMirFViOn5YNVwpd1bYyFYx7ycybV7Fr9 D/lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=8KzNrGWVx/RP5HFg/oFwWhAt/41VhhYaKedxm5zados=; b=PTxFvmMXyz5dU3rDemxD03Y3gon1qmR0REQ8bv6OceBCwgiZrFYWnoY46S84NV3t5R kTvNa94pi7cWaSnCaCbSZdXBLSOATF4uv3sx3yRK6g0TeuhUe9NkdbFEA1+fMI5UWmbu wCH87xksuY2m6C9FomG5jCMzFZAm85kyMTdv/q5zB0RmLUOYFpp2NFKaSGh6mYY7iZ5+ 4MYMF5N7D/KLsliXFvMTuHLRpAN5IuElcDtKUumgEp3BpkUt6Mr7mrG4y8v9d+szV8Fn 7DzxCBMvA47VAK72g9BQ6zwlEi4j4ehiEoYS+EFXmzwadN2eJuXSyvebv5V/OZG1ZB/4 +eUg==
X-Gm-Message-State: AMke39n0qHIQuMe+Aru/YUCWUhrjWd+K74G370C/ay/eKucCgq8TMVWyVET+drF97o3XTRQFU9YJpECb7mX2Ww==
X-Received: by 10.31.149.15 with SMTP id x15mr5476181vkd.130.1486793468754; Fri, 10 Feb 2017 22:11:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:11:07 -0800 (PST)
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:11:07 -0800 (PST)
In-Reply-To: <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Sat, 11 Feb 2017 01:11:07 -0500
Message-ID: <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=001a114264d68f42b205483b14a9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EegdIivu2uKy_g-PrzFE32UtHxU>
Cc: 6man@ietf.org, IETF Discussion list <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, draft-ietf-6man-rfc2460bis@tools.ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 06:11:11 -0000

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

Hi Jinmei,

On Feb 10, 2017 1:23 PM, "=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89" <jinmei@wid=
e.ad.jp> wrote:

At Thu, 9 Feb 2017 18:30:11 -0300,
Fernando Gont <fgont@si6networks.com> wrote:

While I largely agree with Fernando on everything he said, I have to
admit most of the points are just repeated from the 6man discussion,
and won't get us anywhere new by discussing these again at this point.
I guess the only new input for the IETF last call is this:

> 2) However, some folks came up with proposals to insert EH, on the basis
> that "RFC2460 does not explicitly ban EH insertion". If there's people
> arguing that, we clearly need to make this clear in the spec.
>
> 3) There was a consensus call, yes. When the call was made on the
> mailing-list, the vast majority of supporters of "let's keep the
> ambiguity" were folks from the same company as "2)". I have no idea if
> this changes (or not) "consensus"... but this is clearly an important
> datapoint.

Although I don't want to point a finger at particular people or
organizations without an evidence, I guess not a small number of 6man
participants (not only those who explicitly spoke up here) suspected
that the decision process was biased with the influence of a large and
powerful organization and the process and resulting "consensus" was
not really a fair one.  And I'm not an exception to it - in fact, it
was so unbelievable to me that we can't clarify an ambiguity even when
we were also open for future extensions, that I couldn't think of
other reasons than a company agenda.

Of course, it's quite possible that it was just a coincidence that
many people with the same organization genuinely thought we should
leave it ambiguous while many others strongly thought we should
clarify it but few (if not no) people from that organization supported
the clarification.  But I don't think we can prove it either way.

But as Fernando said, I believe this point (and that several, and
arguably more, participants suspected it) should be included in making
the decision at the IESG and at the IETF last call.  And, whatever the
decision, it would be more productive to move on after that and use
our time for some other things.


I am guessing that the people who spoke up during the WG process to not put
in an outright prohibition would make their case along with their arguments
here as well. We are only a week into a four week long last call.

Thanks
Suresh

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

<div dir=3D"auto"><div>Hi Jinmei,=C2=A0<br><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">On Feb 10, 2017 1:23 PM, &quot;=E7=A5=9E=E6=98=8E=
=E9=81=94=E5=93=89&quot; &lt;<a href=3D"mailto:jinmei@wide.ad.jp">jinmei@wi=
de.ad.jp</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">At=
 Thu, 9 Feb 2017 18:30:11 -0300,<br>
Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com">fgont@si6network=
s.com</a>&gt; wrote:<br>
<br>
While I largely agree with Fernando on everything he said, I have to<br>
admit most of the points are just repeated from the 6man discussion,<br>
and won&#39;t get us anywhere new by discussing these again at this point.<=
br>
I guess the only new input for the IETF last call is this:<br>
<div class=3D"quoted-text"><br>
&gt; 2) However, some folks came up with proposals to insert EH, on the bas=
is<br>
&gt; that &quot;RFC2460 does not explicitly ban EH insertion&quot;. If ther=
e&#39;s people<br>
&gt; arguing that, we clearly need to make this clear in the spec.<br>
&gt;<br>
&gt; 3) There was a consensus call, yes. When the call was made on the<br>
&gt; mailing-list, the vast majority of supporters of &quot;let&#39;s keep =
the<br>
&gt; ambiguity&quot; were folks from the same company as &quot;2)&quot;. I =
have no idea if<br>
&gt; this changes (or not) &quot;consensus&quot;... but this is clearly an =
important<br>
&gt; datapoint.<br>
<br>
</div>Although I don&#39;t want to point a finger at particular people or<b=
r>
organizations without an evidence, I guess not a small number of 6man<br>
participants (not only those who explicitly spoke up here) suspected<br>
that the decision process was biased with the influence of a large and<br>
powerful organization and the process and resulting &quot;consensus&quot; w=
as<br>
not really a fair one.=C2=A0 And I&#39;m not an exception to it - in fact, =
it<br>
was so unbelievable to me that we can&#39;t clarify an ambiguity even when<=
br>
we were also open for future extensions, that I couldn&#39;t think of<br>
other reasons than a company agenda.<br>
<br>
Of course, it&#39;s quite possible that it was just a coincidence that<br>
many people with the same organization genuinely thought we should<br>
leave it ambiguous while many others strongly thought we should<br>
clarify it but few (if not no) people from that organization supported<br>
the clarification.=C2=A0 But I don&#39;t think we can prove it either way.<=
br>
<br>
But as Fernando said, I believe this point (and that several, and<br>
arguably more, participants suspected it) should be included in making<br>
the decision at the IESG and at the IETF last call.=C2=A0 And, whatever the=
<br>
decision, it would be more productive to move on after that and use<br>
our time for some other things.<br></blockquote></div></div></div><div dir=
=3D"auto"><br></div><div dir=3D"auto">I am guessing that the people who spo=
ke up during the WG process to not put in an outright prohibition would mak=
e their case along with their arguments here as well. We are only a week in=
to a four week long last call.</div><div dir=3D"auto"><br></div><div dir=3D=
"auto">Thanks=C2=A0</div><div dir=3D"auto">Suresh</div></div>

--001a114264d68f42b205483b14a9--


From nobody Fri Feb 10 22:15:36 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98CAD12956F for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 22:15:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vDAIyVCy68rI for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 22:15:31 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 6F46912944C for <ietf@ietf.org>; Fri, 10 Feb 2017 22:15:31 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id i68so42432177uad.0 for <ietf@ietf.org>; Fri, 10 Feb 2017 22:15:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VLUR+Dorq2xCsVfPXBm9o8n0fx90bak6ixm7ooVmXko=; b=JHIhAcEahrKvNsU7YBqRWiIvDkdfXHv18/d4yXIOUgGImILsehHBcJvrZ2pSqgYUrA xNhvquyv2vghWXyUdMXMvb/GFa6TyvrRnMrMvi3KZPKFoDVLJBDmSGPhwg/UaQACqGOu 8/Agh2FHQF4+1KYxFHTC7ULQ+lhqwskhl1zCuw7FuH3Yvfsmqh5k4SnZMGWVV3+UvCZB 7TSk4V/7ZQIOaDZqDAViOltdkNidBbbbybKureu5tpwe4cCCk2bdPB6/QDRALWR3eHvn qttWeT0T40tTr/Pt5ETjEt3DX8H9TSmlkkFy4Fkv/Ap3r28uUdElq7x6iTBvCGXGsSkt FemA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VLUR+Dorq2xCsVfPXBm9o8n0fx90bak6ixm7ooVmXko=; b=PgD5O4EyLUzKW/hMWsUlOn/NNyXb/b/3bpUM7dFUiwJ1Yy1vxz3wI0Y/zcobubRkPm XuA9vIHjrPVvJQE8V5W1bx3fTpfAdS9XL5cy6yuDMJnDRLB19NVUDn8xF9rJ5oabCZ/1 kZIAaJoWhWa/01T9+SYMjfC3v+BI0Yo6iFYGGHfXkY9KRZLEE4G6WzUuSFnH0wC7T4TX ykRXq8hd0cCfkiTBQlf/UIN0AdBmUnFTXE+aVNkPRddCs+NGRDPXqj2mlVaYDGFgey+G hqf4A7ywECaiLwEBfvYEIrsb7Ym7Gmq+85yptBaeaGnFZcqiqlT80U7heG+xdEcALEYy cxlw==
X-Gm-Message-State: AMke39noapgSyA6plfaKhfFaWLw4GB/oaR3x5Y4kFXDhmrxh+PVdUFvgzE9RJNQXRgywJpAgH1WwI26REFu6hg==
X-Received: by 10.176.85.24 with SMTP id t24mr6708094uaa.75.1486793730507; Fri, 10 Feb 2017 22:15:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:15:29 -0800 (PST)
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:15:29 -0800 (PST)
In-Reply-To: <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Sat, 11 Feb 2017 01:15:29 -0500
Message-ID: <CA+MHpBoVEqvfcAXURj9FuqQR7JxWbbeL0P8r5E5dwcXOnB13wQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=f403045dd960294b7c05483b2496
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wQC-iKE-iRoH9qM2flNZNJeTarY>
Cc: IETF Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 06:15:35 -0000

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

Hi Brian,

On Feb 10, 2017 8:32 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

On 11/02/2017 14:12, Ted Lemon wrote:
> On Feb 10, 2017, at 8:02 PM, Randy Bush <randy@psg.com> wrote:
>> excuse?  this is why we have ietf last call.
>
> No, we do not have IETF last call so that people who participated in the
working group discussion can re-litigate the points they lost on in the
working group discussion.

I was fairly specific when I raised the issue at
https://mailarchive.ietf.org/arch/msg/ietf/myyPO9b4dYfYeGQrdPjTNzIHArY

>> I do not dispute that this sentence reached WG consensus. However, I want
>> to ask if it has IETF consensus.

If people who were not involved in the 6man debate have opinions, it would
be useful to hear from them. I agree that there is no point in the same
people repeating the same arguments.


Thanks for putting it so succinctly. Getting the input from the broader
community will be extremely helpful.

Regards
Suresh

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

<div dir=3D"auto"><div>Hi Brian,=C2=A0<br><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Feb 10, 2017 8:32 PM, &quot;Brian E Carpenter&q=
uot; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@g=
mail.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv class=3D"elided-text">On 11/02/2017 14:12, Ted Lemon wrote:<br>
&gt; On Feb 10, 2017, at 8:02 PM, Randy Bush &lt;<a href=3D"mailto:randy@ps=
g.com">randy@psg.com</a>&gt; wrote:<br>
&gt;&gt; excuse?=C2=A0 this is why we have ietf last call.<br>
&gt;<br>
&gt; No, we do not have IETF last call so that people who participated in t=
he working group discussion can re-litigate the points they lost on in the =
working group discussion.<br>
<br>
</div>I was fairly specific when I raised the issue at<br>
<a href=3D"https://mailarchive.ietf.org/arch/msg/ietf/myyPO9b4dYfYeGQrdPjTN=
zIHArY" rel=3D"noreferrer" target=3D"_blank">https://mailarchive.ietf.org/<=
wbr>arch/msg/ietf/<wbr>myyPO9b4dYfYeGQrdPjTNzIHArY</a><br>
<div class=3D"quoted-text"><br>
&gt;&gt; I do not dispute that this sentence reached WG consensus. However,=
 I want<br>
&gt;&gt; to ask if it has IETF consensus.<br>
<br>
</div>If people who were not involved in the 6man debate have opinions, it =
would<br>
be useful to hear from them. I agree that there is no point in the same<br>
people repeating the same arguments.<br>
<font color=3D"#888888"></font></blockquote></div></div></div><div dir=3D"a=
uto"><br></div><div dir=3D"auto">Thanks for putting it so succinctly. Getti=
ng the input from the broader community will be extremely helpful.=C2=A0<br=
></div><div dir=3D"auto"><br></div><div dir=3D"auto">Regards</div><div dir=
=3D"auto">Suresh</div><div dir=3D"auto"><div class=3D"gmail_extra"><br></di=
v></div></div>

--f403045dd960294b7c05483b2496--


From nobody Fri Feb 10 22:26:56 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D071293F9 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 22:26:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ucm49_Wv-vO5 for <ietf@ietfa.amsl.com>; Fri, 10 Feb 2017 22:26:51 -0800 (PST)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::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 966FE127735 for <ietf@ietf.org>; Fri, 10 Feb 2017 22:26:51 -0800 (PST)
Received: by mail-ua0-x232.google.com with SMTP id 96so42446295uaq.3 for <ietf@ietf.org>; Fri, 10 Feb 2017 22:26:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MNvM1RAwHw+YnBzDJdQ8hXGnJik2CbsIhjIuxOy6cw8=; b=JSkeor5Zleaw9prie4JxBU1aBBINXjjLQwmBzwb+49t2f/NPfrgKWAwBoB8/4fstYB Kb6F2IFbBf1ncKZQV7vkiRH2ul3l5clSQV9MnkTQHKlTUhQA2KJMk1WDTBYJPUloauro ufuzOs/FFyydvQwBEePYnJNIwNsSHR0sLjm60ipCAKubux83pfC0zID8OLfyc+vDAFnq iXhB1CL+6XZ6EO+oQu+QDfEe96axQyxDHWhU5d3wiZT7Eb6qkgJLL+VOGZ2GvGpVgUEf cSskxg3DdLbcJ18CzwSgSizKPbsA+j5oAieo9fauOAgEqKKm0q6U0Yk2IzGz+tMJRCwD UdUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MNvM1RAwHw+YnBzDJdQ8hXGnJik2CbsIhjIuxOy6cw8=; b=UfQbbU3rgZ7/TsOVvGn52hdl93GTh4gLa/ImCRCmI6HaCLmEQnHmaGCs18VItTqsdk uQISsx73gt3CNvfXalPuIdCbRt2CK0ck/E9uQUKiozNAX2X0LLyE5lF1bixdf+zLs2ei Vj8Ye4tUl2VXJmiFOwNeQPJB8gQ24WMTer9PKk5xMOSSSgUXdcYkYFPynLz2M1aXQJGc 5ueXpH4rvAYfN7JZgvQSpNGNwPbgLaZBZmRytHbtxQ4M3DKDb32PSf/p2AgB4x3gJb9S pyXbQXNj4bVF1BLH/97umZ4DOQO4RZz8fUvBKmVkGf0++t/S18Q7oJy6bzUrjaMi/35N Vzrw==
X-Gm-Message-State: AMke39lmwyhBns4UyMrpJ/WSt7v6iobYzR6jJYXSr2ixfKDy1z0rdQDiF0uekm+vQ3JsMVE23kNt248qBKKrpw==
X-Received: by 10.176.6.3 with SMTP id f3mr5584550uaf.37.1486794410554; Fri, 10 Feb 2017 22:26:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:26:49 -0800 (PST)
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:26:49 -0800 (PST)
In-Reply-To: <m2o9y9pg0x.wl-randy@psg.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <m2o9y9pg0x.wl-randy@psg.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Sat, 11 Feb 2017 01:26:49 -0500
Message-ID: <CA+MHpBo1kUeXHv9A_0x_vkpbRQTef+AqaBPpUSDLWne1S1eeLw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=94eb2c048440b1fce205483b4ca7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Fu9Rwaq22mPeLIv_Cy0GcOV6qs8>
Cc: IETF Discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 06:26:53 -0000

--94eb2c048440b1fce205483b4ca7
Content-Type: text/plain; charset=UTF-8

Hi Randy,

On Feb 10, 2017 10:23 PM, "Randy Bush" <randy@psg.com> wrote:

just to get down a level from meta-

> If the right answer is to allow packet modifications that break PMTUD
> and IPsec/AH, let's do it, but let's also say we're doing it.

obvious imiho

> I happen to think it's the wrong answer, but that's my problem.

i share it, but this is at the border of my expertise.  i have this
fantasy of pmtu actually working before i retire.  i realize it is
unrealistic.

> Leaving the text open to interpretation would make a mockery of
> promoting it to Standard.

agree.  but v6 specs seem to like wussing out and leaving the
opportunity to do wrong things.  i'll bet you a reuben at the corned
beef factory in chicago that the next try at the addressing architecture
still does not *unambiguously* state cidr except for slaac.


Do you mean the affinity for a 64 bit IID for addresses? If so, this has
been widely explored and documented in RFC7421. I agree with you that this
is hard to get out of given the state of implementations. I am not sure how
this draft (rfc2460bis) is related to that though.

Thanks
Suresh

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

<div dir=3D"auto"><div>Hi Randy,=C2=A0<br><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Feb 10, 2017 10:23 PM, &quot;Randy Bush&quot; &=
lt;<a href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote:<br type=3D=
"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">just to get down a level from meta-<=
br>
<div class=3D"quoted-text"><br>
&gt; If the right answer is to allow packet modifications that break PMTUD<=
br>
&gt; and IPsec/AH, let&#39;s do it, but let&#39;s also say we&#39;re doing =
it.<br>
<br>
</div>obvious imiho<br>
<div class=3D"quoted-text"><br>
&gt; I happen to think it&#39;s the wrong answer, but that&#39;s my problem=
.<br>
<br>
</div>i share it, but this is at the border of my expertise.=C2=A0 i have t=
his<br>
fantasy of pmtu actually working before i retire.=C2=A0 i realize it is<br>
unrealistic.<br>
<div class=3D"quoted-text"><br>
&gt; Leaving the text open to interpretation would make a mockery of<br>
&gt; promoting it to Standard.<br>
<br>
</div>agree.=C2=A0 but v6 specs seem to like wussing out and leaving the<br=
>
opportunity to do wrong things.=C2=A0 i&#39;ll bet you a reuben at the corn=
ed<br>
beef factory in chicago that the next try at the addressing architecture<br=
>
still does not *unambiguously* state cidr except for slaac.<br></blockquote=
></div></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Do you mea=
n the affinity for a 64 bit IID for addresses? If so, this has been widely =
explored and documented in RFC7421. I agree with you that this is hard to g=
et out of given the state of implementations. I am not sure how this draft =
(rfc2460bis) is related to that though. =C2=A0</div><div dir=3D"auto"><br><=
/div><div dir=3D"auto">Thanks=C2=A0</div><div dir=3D"auto">Suresh=C2=A0</di=
v><div dir=3D"auto"><div class=3D"gmail_extra"><br></div></div></div>

--94eb2c048440b1fce205483b4ca7--


From nobody Fri Feb 10 22:42:58 2017
Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B77681294AD; Fri, 10 Feb 2017 22:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i7RJZAQS5Ouw; Fri, 10 Feb 2017 22:42:46 -0800 (PST)
Received: from mail-vk0-x229.google.com (mail-vk0-x229.google.com [IPv6:2607:f8b0:400c:c05::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 0E20E127601; Fri, 10 Feb 2017 22:42:45 -0800 (PST)
Received: by mail-vk0-x229.google.com with SMTP id k127so39066542vke.0; Fri, 10 Feb 2017 22:42:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OVjo0u3qVPxNT/T53/VeGKf8JIGySnqBdG62iqs+J74=; b=Eu7grB2SCiiDM0Ed+x2HDbGy7avzpb5sMeFvDgvWkT7dO+CkqWqsDkXUOFYErb1NBN q753ZqU3R86ypQ03vXnGU1NTtmupD4hhQwQ8Zo1ct/KO+2nE4DkxjHoEp3TmdLNPstP+ 6t6FLLvwDT5BaCVrSpRi/QDtYv0J7wEGOLXNUw0IIlJ1ddcT+EHII2SwuzT4M0qAbm5V vxyJ2IrI5bqRlIi41BHmuJufgbXTGGKkCjQylKcMRyT4jj+LM6pqE/OxI3miwLh1Yy4J 79YVnnPi5kFnJaplOqhASVjsS22TVpObeisQGR0W8IYHvoOKTX5bSWuxpMcz1e3hLHxs HqZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OVjo0u3qVPxNT/T53/VeGKf8JIGySnqBdG62iqs+J74=; b=UPJWFI48C/3RdRSF2ZvxlzMaTcsBQ5Z/9FbCpMlOCk25DLK9hNCMgSBXtLWPhkNPhH l7H1kUjPFqPkQjWITlbbHW42Ffn6HuOr8eJGSIJCXvBDV28klKKhSbOUUCSYHo2VrLfv jzYci1hG6uXiMLOoKKzZf8aDcIsOx75ki62GeVFXKxDy1zTr/SyXiO3iHqRXk0/bu2FT XnRMI7AmdLoFDAgREGhe6AYoyefvKYQex73+cu8hYoau/t1go27IsBmJCarodB0Xrosp FzlSCvMSNpT6Dn3COrgAFaAQnJWz7bc9WymyY7dsbmH7Xd6F/KRZBneuOFCbUDPsR5uG uN1w==
X-Gm-Message-State: AMke39kZxCu3ENJxge8ivqEuG8TaNFeOCRR7LtRRYh5v5bCPmf1uPshcxP5UIEu8S+Ey1Wigy36gn3GF8havcQ==
X-Received: by 10.31.128.78 with SMTP id b75mr6185594vkd.174.1486795364824; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
Received: by 10.103.49.14 with HTTP; Fri, 10 Feb 2017 22:42:44 -0800 (PST)
In-Reply-To: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
References: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Sat, 11 Feb 2017 01:42:44 -0500
Message-ID: <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: "C. M. Heard" <heard@pobox.com>
Content-Type: multipart/alternative; boundary=001a1142a40492fece05483b8561
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oGajeQEn6Ey7zGvcn9c2wtacAVw>
Cc: 6man WG <ipv6@ietf.org>, gen-art@ietf.org, Stewart Bryant <stewart@g3ysx.org.uk>, IETF <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 06:42:48 -0000

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

Hi Mike,

On Feb 10, 2017 11:30 PM, "C. M. Heard" <heard@pobox.com> wrote:

On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> On 10/02/2017 23:20, Stewart Bryant wrote:
> > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > I wonder if we would best serve both our future and our heritage
> > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > or declared it as historic and wrote a new text from a clean start?
> > >
> > > I don't see that. It's a stable, widely deployed, interoperable
> > > mechanism. That is rather orthogonal to the issue that has been
raised,
> > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > across the Internet.
> >
> > I will not debate whether it is faulty or not,
>
> It's faulty by the standard of RFC4890 (which is Informational).
>
> > but it seems that in practice the Internet breaks the mechanism.
> > However it breaks it is a way that seems disruptive to some user
> > traffic. The document is really guidance one how hosts might use
> > ICMP for optimization, and arguabl[y] need not be a standard at all.
>
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes.

Actually, no. You do not have to use PMTUD to avoid black holes.
Other options include:

- Send packets no larger than 1280 bytes (this is always an option)
- Use PLPMTUD (for transports that do their own packetization and
  that can detect packet loss)


How does this work for UDP?


> > My remark about heritage is that this vintage draft is very much a
> > product of its time, and really needs modernizing, and after
> > modernizing ought to look quite different, and thus maybe we
> > should employ a procedure other than a simple replacement.

I am afraid that I have to agree with this. Classic PMTUD by itself
is today not enough, but it can be a very useful optimization to
augment other techniques.


OK.


> It's proposed for Internet Standard. That means it must replace the
> PS document and must specify the same thing, plus corrections,
> minus unused features.

All true, and my conclusion is that is it should not be promoted to IS.


What criteria for advancement to IS do you think are not met by this
document?

I would have no problem with republishing at PS to correct the errata
and aid the eventual advance of RFC 4821 (PLPMTUD).

If this document does go forward, the words in Appendix B (Changes
Since RFC 1981) relating to RFC 4821 should be removed, since
there was no mention of RFC 4821 in RFC 1981.


Not sure I understand your concern. This is a change log since RFC1981. And
it is a fact that the reference to RFC4821 was added into this draft. Can
you clarify?

Thanks
Suresh

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

<div dir=3D"auto"><div>Hi Mike,=C2=A0<br><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Feb 10, 2017 11:30 PM, &quot;C. M. Heard&quot; &=
lt;<a href=3D"mailto:heard@pobox.com">heard@pobox.com</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">On Fr=
i, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:<br>
&gt; On 10/02/2017 23:20, Stewart Bryant wrote:<br>
&gt; &gt; On 10/02/2017 03:25, Brian E Carpenter wrote:<br>
</div><div class=3D"quoted-text">&gt; &gt; &gt; On 10/02/2017 04:19, Stewar=
t Bryant wrote:<br>
</div><div class=3D"quoted-text">&gt; &gt; &gt; &gt; I wonder if we would b=
est serve both our future and our heritage<br>
&gt; &gt; &gt; &gt; if we declared RFC1981 as historic, and either left the=
 idea there,<br>
&gt; &gt; &gt; &gt; or declared it as historic and wrote a new text from a =
clean start?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don&#39;t see that. It&#39;s a stable, widely deployed, in=
teroperable<br>
&gt; &gt; &gt; mechanism. That is rather orthogonal to the issue that has b=
een raised,<br>
&gt; &gt; &gt; which is that faulty ICMPv6 filtering blocks it on many, man=
y paths<br>
&gt; &gt; &gt; across the Internet.<br>
&gt; &gt;<br>
&gt; &gt; I will not debate whether it is faulty or not,<br>
&gt;<br>
</div><div class=3D"quoted-text">&gt; It&#39;s faulty by the standard of RF=
C4890 (which is Informational).<br>
&gt;<br>
</div>&gt; &gt; but it seems that in practice the Internet breaks the mecha=
nism.<br>
<div class=3D"quoted-text">&gt; &gt; However it breaks it is a way that see=
ms disruptive to some user<br>
&gt; &gt; traffic. The document is really guidance one how hosts might use<=
br>
</div>&gt; &gt; ICMP for optimization, and arguabl[y] need not be a standar=
d at all.<br>
<div class=3D"quoted-text">&gt;<br>
&gt; I think that&#39;s a mischaracterisation of the mechanism (and the dra=
ft).<br>
&gt; PMTUD is not an optimisation. Without it, you get black holes.<br>
<br>
</div>Actually, no. You do not have to use PMTUD to avoid black holes.<br>
Other options include:<br>
<br>
- Send packets no larger than 1280 bytes (this is always an option)<br>
- Use PLPMTUD (for transports that do their own packetization and<br>
=C2=A0 that can detect packet loss)<br></blockquote></div></div></div><div =
dir=3D"auto"><br></div><div dir=3D"auto">How does this work for UDP?=C2=A0<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class=3D"quoted-text"><br>
&gt; &gt; My remark about heritage is that this vintage draft is very much =
a<br>
&gt; &gt; product of its time, and really needs modernizing, and after<br>
&gt; &gt; modernizing ought to look quite different, and thus maybe we<br>
&gt; &gt; should employ a procedure other than a simple replacement.<br>
<br>
</div>I am afraid that I have to agree with this. Classic PMTUD by itself<b=
r>
is today not enough, but it can be a very useful optimization to<br>
augment other techniques.<br></blockquote></div></div></div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">OK.=C2=A0</div><div dir=3D"auto"><br></div><=
div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
<div class=3D"quoted-text"><br>
&gt; It&#39;s proposed for Internet Standard. That means it must replace th=
e<br>
&gt; PS document and must specify the same thing, plus corrections,<br>
&gt; minus unused features.<br>
<br>
</div>All true, and my conclusion is that is it should not be promoted to I=
S.<br></blockquote></div></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">What criteria for advancement to IS do you think are not met by t=
his document?=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I would have no problem with republishing at PS to correct the errata<br>
and aid the eventual advance of RFC 4821 (PLPMTUD).<br>
<br>
If this document does go forward, the words in Appendix B (Changes<br>
Since RFC 1981) relating to RFC 4821 should be removed, since<br>
there was no mention of RFC 4821 in RFC 1981.<br></blockquote></div></div><=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">Not sure I understand yo=
ur concern. This is a change log since RFC1981. And it is a fact that the r=
eference to RFC4821 was added into this draft. Can you clarify?=C2=A0</div>=
<div dir=3D"auto"><br></div><div dir=3D"auto">Thanks=C2=A0</div><div dir=3D=
"auto">Suresh</div><div dir=3D"auto"><div class=3D"gmail_extra"><br></div><=
/div></div>

--001a1142a40492fece05483b8561--


From nobody Sat Feb 11 04:36:55 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36665129618 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 04:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rzndr46a0zcd for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 04:36:52 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id B4E391294E0 for <ietf@ietf.org>; Sat, 11 Feb 2017 04:36:52 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 11 Feb 2017 12:36:52 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 96C0DD788D; Sat, 11 Feb 2017 04:36:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=7cxyugcVhloFCgiv/9RD4/pYyy4=; b= YoUzA7aI9QpqXcJ9kq8wvBAEek8kV5JdyYXmvkthYxeGSDBaIwzA+GMcvLIH5DfH c7zo4hw/VxPQlQlHIPH5NhHDlqIShWc1VMWhItQcX0d+TWJqiiI4hQoIldROZXZi MiiAZ+8lSimcL5n6YliO7VIFMmTLgihRf5bEX5oHHUk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=cP1OHir7G8ibR7+pJCBN4yo frgrmnJbMwggBOwMOEtg5b8411SwFF+ReYlqOm7cF9KoUdzlniuW+OCMQ4fgF1CK pz25wmyPzBaD1LJht76pGUihVworO0UoTW7OfQlkiQYYCQSSBB2BETwQVuhfONkU KuIfpOY8pkSMtPohHxPA=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 1DBA9D788B; Sat, 11 Feb 2017 04:36:51 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 3290A894A95E; Sat, 11 Feb 2017 13:36:52 +0100 (CET)
From: otroan@employees.org
Message-Id: <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_DB283C45-6594-4ED1-96F7-C700C8A55840"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Sat, 11 Feb 2017 13:36:51 +0100
In-Reply-To: <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YqxeNyu2NJm53fmIeCwbbM7aieg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 12:36:54 -0000

--Apple-Mail=_DB283C45-6594-4ED1-96F7-C700C8A55840
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

>>> If people who were not involved in the 6man debate have opinions, it
>>> would be useful to hear from them. I agree that there is no point in
>>> the same people repeating the same arguments.
>>=20
>> in the absence of a (somewhat unbiased) summary of the critical
>> issues(s), what do you suggest?
>=20
> I was going to say this off list, but what the heck?
>=20
> To be honest I'm trying to stay quiet. I think I've made my opinion
> plain, and although I am of course the only human being alive who =
doesn't
> suffer from confirmation bias, I'd *really* like to hear what people
> think whose opinion I haven't already heard 20 times.
>=20
> I try not to be a purist. If the right answer is to allow packet
> modifications that break PMTUD and IPsec/AH, let's do it, but let's
> also say we're doing it. (I happen to think it's the wrong answer,
> but that's my problem.) Leaving the text open to interpretation
> would make a mockery of promoting it to Standard.

This is really not the discussion we ought to be having.
"Allowing" or in any way specifying how header insertion could possibly =
be made to work is far outside of the scope of advancing 2460 to =
Internet standard.

Best regards,
Ole

--Apple-Mail=_DB283C45-6594-4ED1-96F7-C700C8A55840
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYnwVjAAoJEL7aWKiYQt92rMgQAL7pdXvFk+fObhgzPZlbyZF0
Z/fLwI9GzP8mihbe5qhZWgNcjyk5QgBoDxqPWTqdHAH2BZJtuCRWyjZ4BkU6elOn
e463Hs4wXlAZjP+OOgg2eFwaVKQZ4oAjvp+oxG46xOUXoVXW+VxBPnor4XOT53lc
5bfkfM5F6tDZbBA8jTFYeUE1gzDRO1XMq2D3fy7XOUQVIEQmTZa1opDzhkndpuuG
3RqadfNQa+V31tUzZeJDNyOkY4ydbWH8E8arz11EhB5ueJer5vkvY3TXryHDc25x
24tjOR1bLgGxJDqlDukCisZL6u0uWpcHpaRLyJLblOBokkgrU+X06fmishuI4jMy
RHF5Pp1JDaYZV71yLKmm+OM8C1yV/Sf6axjZM3HQaIdaD1Bkc8CAvlwdG19CPNqX
Vi2L5aEyOV059MZ5Gs6Z8jBBmyt5G7V32mvWeKqfXQFk0Umr49u9XByeNQD/6u+c
tinC7/EesL4xz558wZ5iqeQCTgitC3Gchx6qutkcOFV8ms5sT5J6dT14mNDTusgh
4wy6pUlaZvfTRwLAjC9TsThJqE7aWF10umu7KOQnmq1LpExz7RjFJeHQttOodm15
PlE5/OcGmvGdGt6I7EYONo20s6siNygyEgGLCm5OvNnaXOlpLGWhUUBsqCy4bOyr
6WEDPvSVq/NNfimIySAA
=9mzO
-----END PGP SIGNATURE-----

--Apple-Mail=_DB283C45-6594-4ED1-96F7-C700C8A55840--


From nobody Sat Feb 11 04:48:45 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D99129552 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 04:48:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHFZ4XtOcUzl for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 04:48:42 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 36B89126579 for <ietf@ietf.org>; Sat, 11 Feb 2017 04:48:42 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 11 Feb 2017 12:48:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id DD010D788A; Sat, 11 Feb 2017 04:48:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=L1soXuiNYEzhBBJfN/Tvrb9fdMM=; b= WwPw7wYWt2EItcojaKsvWvifqUcDPi0D861t8kA/+qjVtBqjU46++CUIE2k1toZh 7D9oc5S94o/p5XAb7ElZMdo8+H+tt0CXpdIlUMD2xDzm1pM0JZWPO9rTCHFibQTE WRc4Zq8/PamWcDZ8YD9CB+X8Pi56PjRk4gcAnkOQLzg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=Gk0+641++e91ZUn6qGShryj fTpJscV7oM6Ce+/hEyZ99huwFKuzAITd9Vl5jTveBQY+RU2fwSSaf/GrZgFutAGX 0pQZ4fLNclrCI+/mFmmTblHPAS8UN6VomVqi9XgFcaAjP+2cegVD8blEoel+PF/8 Q4p6BJimghIGv2X2nuQ8=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id A27A0D788E; Sat, 11 Feb 2017 04:48:41 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 777D1894DE74; Sat, 11 Feb 2017 13:48:41 +0100 (CET)
From: otroan@employees.org
Message-Id: <D76BD8B5-7CFE-4EAB-A79A-A9318052C22A@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_29024FD8-2911-4C8C-82F1-F147F4C095AF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
Date: Sat, 11 Feb 2017 13:48:40 +0100
In-Reply-To: <m2o9y9pg0x.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <m2o9y9pg0x.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/axa7rKItH3-e5YINPToNHZDgoWg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 12:48:43 -0000

--Apple-Mail=_29024FD8-2911-4C8C-82F1-F147F4C095AF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> Leaving the text open to interpretation would make a mockery of
>> promoting it to Standard.
>=20
> agree.  but v6 specs seem to like wussing out and leaving the
> opportunity to do wrong things.  i'll bet you a reuben at the corned
> beef factory in chicago that the next try at the addressing =
architecture
> still does not *unambiguously* state cidr except for slaac.

we're striving to write specifications that ensure interoperability.

is rewriting addresses permitted by the IPv6 architecture?
the intent of the authors were certainly clear, but we still have IPv6 =
NAT and NPT66.

does 2460 permit 5-tuple based ECMP? clearly not, but we also have to =
accept reality sometimes.

if you aren't happy with my biases please provide your own.

Best regards,
Ole

--Apple-Mail=_29024FD8-2911-4C8C-82F1-F147F4C095AF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYnwgpAAoJEL7aWKiYQt925d8QAJQhGLv/HK1ZPTUyTS6vTEpe
sdR51k+2o3WSQMvKrqCeLzZSgAqLsqPs/fnAohW5oZ1oCsYSUc/QR+rBz/Bbhj1z
xCkGnE7DVcMbW5RVrA5yTzBtw6B62efF5ooFr/DvjriuvpMGUVivb6jLNXwhfXGs
bpFzQKn0+wGiQb9d9pZ/8SdMolG7e1r+UKNZVjhbBkv2wmrZr2RY80c0HGDkk9mY
aA3nkj1fUCxR+BaUMJtWyQJ6hZGy0Oo5Kb/KqoVueYF71pMH6qJgreeiKRIqZ3dA
0g7tbR+D3nCiNomGvjOoUX/T+oTtniuEIS2HcOUw6IW17jrpK2csCGvdUtlyLDyo
aaXN6lhJohwx8rnVtTp3mISwhem3HWrWnoPwn7y7gGoK6dGFlcy+5jA22b5HDcj6
XUc9nKsVILd2I+dzcokrDo0q3cZ8Zvj9Tgm9Z6y/JDPi4Gg+Pk1V4sxRMrmOBytS
Jah7ArvZsjVrRXZVNoiblwgR/EcGzWXrE9x00iRTnaYF9hLhRktPKjhZcvmzwWuP
ixQ54rFoNl9kac/cfKaqvDmlhSzaTp38SagujoOQ5X1pQufH4VMBttDj1vIaFDQJ
hwEtB2wJZspo3Fiwss511WObgQKpOKxEemXcOfld8Lvc5ru10kTUoOmQXl/QKrBD
C5KYDGpzYYsVITDzN30k
=RLnp
-----END PGP SIGNATURE-----

--Apple-Mail=_29024FD8-2911-4C8C-82F1-F147F4C095AF--


From nobody Sat Feb 11 10:05:47 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE353129A34; Sat, 11 Feb 2017 10:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XEuPaTY-epPa; Sat, 11 Feb 2017 10:05:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 383B4129A33; Sat, 11 Feb 2017 10:05:37 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id C40E4652D2; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=rZC bRNP8cBp3UQQ+laGRw8A/XzE=; b=svUktSM/bJn9xAk+5ZSosysCHDFJYPwYJgg KTyObZD/ePdjZ+0PxZtJimIDoFSu7nEtHvC0WYnokROm/oMhNLFJhYCQ7+O0zgiC mQSzudNRLb2wFlYRImo8mDuj+b6imhIAea8Y7FOk7nM4b5RGdlIkj37GdTpQcDbp TLGPfuIA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= SOt6WAPXlhqWXSrOBL6C2HoJdQvhStfHFDmZq+LedWVcpClXJpiK+3joIvL5a9wN Lqql7A7hhlU1BMm1kq4FQ03U5ppJhWJ1hALgigcwPvSk8a/Z0wccIJ62fL2nIMeu XZHs6boEPRiCgd0Lu4LDq6z/jsAWTHRhNbQqLrtiBn8=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id AE6A8652D1; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
Received: from mail-qk0-f171.google.com (unknown [209.85.220.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 0E0E4652CC; Sat, 11 Feb 2017 13:05:36 -0500 (EST)
Received: by mail-qk0-f171.google.com with SMTP id s140so66616179qke.0; Sat, 11 Feb 2017 10:05:35 -0800 (PST)
X-Gm-Message-State: AMke39mvdb4S9RGGlNJ9NIW/yryN3p/e5YTatqfesPFjmSqVIvwu5/5MObTB7PrfeUSKVCAS1+l/sJnT8B9EWA==
X-Received: by 10.55.170.17 with SMTP id t17mr13933696qke.15.1486836334971; Sat, 11 Feb 2017 10:05:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sat, 11 Feb 2017 10:05:14 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Sat, 11 Feb 2017 10:05:14 -0800
X-Gmail-Original-Message-ID: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
Message-ID: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Content-Type: multipart/alternative; boundary=001a114d519895d98b0548450f27
X-Pobox-Relay-ID: B00396D0-F084-11E6-A0BE-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6OoIjAhpcCUni2a8MPhWrskjehc>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, Gen-ART <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:05:39 -0000

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

On Fri, Feb 10, 2017 at 10:42 PM, Suresh Krishnan <suresh.krishnan@gmail.com
> wrote:

> On Feb 10, 2017 11:30 PM, "C. M. Heard" <heard@pobox.com> wrote:
>
> On Fri, 10 Feb 2017 11:45 -0800 , Brian E Carpenter wrote:
> > On 10/02/2017 23:20, Stewart Bryant wrote:
> > > On 10/02/2017 03:25, Brian E Carpenter wrote:
> > > > On 10/02/2017 04:19, Stewart Bryant wrote:
> > > > > I wonder if we would best serve both our future and our heritage
> > > > > if we declared RFC1981 as historic, and either left the idea there,
> > > > > or declared it as historic and wrote a new text from a clean start?
> > > >
> > > > I don't see that. It's a stable, widely deployed, interoperable
> > > > mechanism. That is rather orthogonal to the issue that has been
> raised,
> > > > which is that faulty ICMPv6 filtering blocks it on many, many paths
> > > > across the Internet.
> > >
> > > I will not debate whether it is faulty or not,
> >
> > It's faulty by the standard of RFC4890 (which is Informational).
> >
> > > but it seems that in practice the Internet breaks the mechanism.
> > > However it breaks it is a way that seems disruptive to some user
> > > traffic. The document is really guidance one how hosts might use
> > > ICMP for optimization, and arguabl[y] need not be a standard at all.
> >
> > I think that's a mischaracterisation of the mechanism (and the draft).
> > PMTUD is not an optimisation. Without it, you get black holes.
>
> Actually, no. You do not have to use PMTUD to avoid black holes.
> Other options include:
>
> - Send packets no larger than 1280 bytes (this is always an option)
> - Use PLPMTUD (for transports that do their own packetization and
>   that can detect packet loss)
>
>
> How does this work for UDP?
>

Sending packets no larger than 1280 bytes is always an option, and in
the case of UDP-based request-response protocols such as DNS that do
not have connection state, it may be the only feasible option.

Anyway, the point I was trying to make was not to argue about better
or worse methods but rather to dispute the statement that PMTUD is
essential for avoiding black holes. I don't believe that it is. The
draft itself explicitly says that "IPv6 nodes are not required to
implement Path MTU Discovery."

> > My remark about heritage is that this vintage draft is very much a
> > > product of its time, and really needs modernizing, and after
> > > modernizing ought to look quite different, and thus maybe we
> > > should employ a procedure other than a simple replacement.
>
> I am afraid that I have to agree with this. Classic PMTUD by itself
> is today not enough, but it can be a very useful optimization to
> augment other techniques.
>
>
> OK.
>
>
> > It's proposed for Internet Standard. That means it must replace the
> > PS document and must specify the same thing, plus corrections,
> > minus unused features.
>
> All true, and my conclusion is that is it should not be promoted to IS.
>
>
> What criteria for advancement to IS do you think are not met by this
> document?
>

I do not dispute that the document has met the formal criteria for IS in
Section
2.2 of RFC 6410. I would argue, however, that its failure to provide a
complete
solution for environments where delivery of ICMP messages is not assured
constitutes a significant technical omission for today's Internet, and I
note
that per RFC 2026 Section 4.1.1, even a PS "should have no known technical
omissions." What I am asking the community, and the IESG, is whether it is
wise to advance a document with known technical omissions; it seems to me
that the Gen-ART reviewer has raised much the same question.

I would have no problem with republishing at PS to correct the errata
> and aid the eventual advance of RFC 4821 (PLPMTUD).
>
> If this document does go forward, the words in Appendix B (Changes
> Since RFC 1981) relating to RFC 4821 should be removed, since
> there was no mention of RFC 4821 in RFC 1981.
>
>
> Not sure I understand your concern. This is a change log since RFC1981.
>
And it is a fact that the reference to RFC4821 was added into this draft.
>
Can you clarify?
>

My apologies, I wrote that too hastily, before reading the complete change
log, which contains a description of what changed in each draft as the
document proceeded through the WG process. The comment that I should
have made is that many of those details are not useful to readers of an
archival document. Looking at a diff between RFC 1981 and this draft,
the substantive changes pretty much boil down to these:

      - In Section 1, added a reference to RFC4821 along with a short
        summary of what it does.

      - In Section 4, added text to discard an ICMP Packet Too Big message
        containing an MTU less than the IPv6 minimum link MTU and removed
        the corresponding note specifying actions that were removed from
        [I-D.ietf-6man-rfc2460bis].

      - In Section 5.2, removed text regarding RH0 (since it was deprecated
        by RFC5095) and removed text about obsolete security
classifications.

      - In Section 5.2, clarified that the tentative PMTU must not be made
        smaller that the IPv6 minimum link MTU.

Regarding that last change, I got confused when I was reading the current
text
in the draft:

   The node then uses the value in the MTU field in the Packet Too Big
   message as a tentative PMTU value or the minimum IPv6 next hope MTU
   if that is larger, and compares the tentative PMTU to the existing
   PMTU.  If the tentative PMTU is less than the existing PMTU estimate,
   the tentative PMTU replaces the existing PMTU as the PMTU value for
   the path.

I initially took the words "minimum IPv6 next hope [sic] MTU" to mean the
next
hop MTU of any link on the node, which of course is not what it meant. Maybe
I'm being dense, but it wasn't until I looked at Donald Eastlake's INT-DIR
review (https://www.ietf.org/mail-archive/web/int-dir/current/msg00339.html)
that the correct meaning finally dawned on me. May I suggest saying
 instead:

   The node then uses the value in the MTU field in the Packet Too Big
   message as a tentative PMTU value or the IPv6 minimum link MTU if
   that is larger, and compares the tentative PMTU to the existing
   PMTU.  If the tentative PMTU is less than the existing PMTU estimate,
   the tentative PMTU replaces the existing PMTU as the PMTU value for
   the path.

In other words, s/minimum IPv6 next hope MTU/IPv6 minimum link MTU/.
That makes the terminology consistent with the rest of the document.

Thanks and regards,

Mike Heard

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 10, 2017 at 10:42 PM, Suresh Krishnan <span dir=3D"ltr">&lt;<a href=
=3D"mailto:suresh.krishnan@gmail.com" target=3D"_blank">suresh.krishnan@gma=
il.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex"><div dir=3D"auto"><div><di=
v><div class=3D"gmail-h5"><div class=3D"gmail_extra"><div class=3D"gmail_qu=
ote">On Feb 10, 2017 11:30 PM, &quot;C. M. Heard&quot; &lt;<a href=3D"mailt=
o:heard@pobox.com" target=3D"_blank">heard@pobox.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"gmail-m_-4490337820322616361quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex"><div class=3D"gmail=
-m_-4490337820322616361quoted-text">On Fri, 10 Feb 2017 11:45 -0800 , Brian=
 E Carpenter wrote:<br>
&gt; On 10/02/2017 23:20, Stewart Bryant wrote:<br>
&gt; &gt; On 10/02/2017 03:25, Brian E Carpenter wrote:<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; &gt;=
 On 10/02/2017 04:19, Stewart Bryant wrote:<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; &gt;=
 &gt; I wonder if we would best serve both our future and our heritage<br>
&gt; &gt; &gt; &gt; if we declared RFC1981 as historic, and either left the=
 idea there,<br>
&gt; &gt; &gt; &gt; or declared it as historic and wrote a new text from a =
clean start?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I don&#39;t see that. It&#39;s a stable, widely deployed, in=
teroperable<br>
&gt; &gt; &gt; mechanism. That is rather orthogonal to the issue that has b=
een raised,<br>
&gt; &gt; &gt; which is that faulty ICMPv6 filtering blocks it on many, man=
y paths<br>
&gt; &gt; &gt; across the Internet.<br>
&gt; &gt;<br>
&gt; &gt; I will not debate whether it is faulty or not,<br>
&gt;<br>
</div><div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; It&#39;s =
faulty by the standard of RFC4890 (which is Informational).<br>
&gt;<br>
</div>&gt; &gt; but it seems that in practice the Internet breaks the mecha=
nism.<br>
<div class=3D"gmail-m_-4490337820322616361quoted-text">&gt; &gt; However it=
 breaks it is a way that seems disruptive to some user<br>
&gt; &gt; traffic. The document is really guidance one how hosts might use<=
br>
</div>&gt; &gt; ICMP for optimization, and arguabl[y] need not be a standar=
d at all.<br>
<div class=3D"gmail-m_-4490337820322616361quoted-text">&gt;<br>
&gt; I think that&#39;s a mischaracterisation of the mechanism (and the dra=
ft).<br>
&gt; PMTUD is not an optimisation. Without it, you get black holes.<br>
<br>
</div>Actually, no. You do not have to use PMTUD to avoid black holes.<br>
Other options include:<br>
<br>
- Send packets no larger than 1280 bytes (this is always an option)<br>
- Use PLPMTUD (for transports that do their own packetization and<br>
=C2=A0 that can detect packet loss)<br></blockquote></div></div></div></div=
></div><div dir=3D"auto"><br></div><div dir=3D"auto">How does this work for=
 UDP?</div></div></blockquote><div><br></div><div><div>Sending packets no l=
arger than 1280 bytes is always an option, and in</div><div>the case of UDP=
-based request-response protocols such as DNS that do</div><div>not have co=
nnection state, it may be the only feasible option.</div><div><br></div><di=
v>Anyway, the point I was trying to make was not to argue about better</div=
><div>or worse methods but rather to dispute the statement that PMTUD is</d=
iv><div>essential for avoiding black holes. I don&#39;t believe that it is.=
 The</div><div>draft itself explicitly says that &quot;IPv6 nodes are not r=
equired to</div><div>implement Path MTU Discovery.&quot;</div></div><div><b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style=
:solid;padding-left:1ex"><div dir=3D"auto"><span class=3D"gmail-"><div dir=
=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail-m_-4490337820322616361quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-st=
yle:solid;padding-left:1ex"><div class=3D"gmail-m_-4490337820322616361quote=
d-text">
&gt; &gt; My remark about heritage is that this vintage draft is very much =
a<br>
&gt; &gt; product of its time, and really needs modernizing, and after<br>
&gt; &gt; modernizing ought to look quite different, and thus maybe we<br>
&gt; &gt; should employ a procedure other than a simple replacement.<br>
<br>
</div>I am afraid that I have to agree with this. Classic PMTUD by itself<b=
r>
is today not enough, but it can be a very useful optimization to<br>
augment other techniques.<br></blockquote></div></div></div><div dir=3D"aut=
o"><br></div></span><div dir=3D"auto">OK.=C2=A0</div><span class=3D"gmail-"=
><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extra"><=
div class=3D"gmail_quote"><blockquote class=3D"gmail-m_-4490337820322616361=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=3D"gmail-m_-4490337820322616361quoted-text"><br>
&gt; It&#39;s proposed for Internet Standard. That means it must replace th=
e<br>
&gt; PS document and must specify the same thing, plus corrections,<br>
&gt; minus unused features.<br>
<br>
</div>All true, and my conclusion is that is it should not be promoted to I=
S.<br></blockquote></div></div></div><div dir=3D"auto"><br></div></span><di=
v dir=3D"auto">What criteria for advancement to IS do you think are not met=
 by this document?</div></div></blockquote><div><br></div><div><div>I do no=
t dispute that the document has met the formal criteria for IS in Section</=
div><div>2.2 of RFC 6410. I would argue, however, that its failure to provi=
de a complete</div><div>solution for environments where delivery of ICMP me=
ssages is not assured</div><div>constitutes a significant technical omissio=
n for today&#39;s Internet, and I note</div><div>that per RFC 2026 Section =
4.1.1, even a PS &quot;should have no known technical</div><div>omissions.&=
quot; What I am asking the community, and the IESG, is whether it is</div><=
div>wise to advance a document with known technical omissions; it seems to =
me</div><div>that the Gen-ART reviewer has raised much the same question.</=
div></div><div><div><br></div></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"auto"><spa=
n class=3D"gmail-"><div dir=3D"auto"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail-m_-4490337820322616361quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb=
(204,204,204);border-left-style:solid;padding-left:1ex">I would have no pro=
blem with republishing at PS to correct the errata<br>
and aid the eventual advance of RFC 4821 (PLPMTUD).<br>
<br>
If this document does go forward, the words in Appendix B (Changes<br>
Since RFC 1981) relating to RFC 4821 should be removed, since<br>
there was no mention of RFC 4821 in RFC 1981.<br></blockquote></div></div><=
/div><div dir=3D"auto"><br></div></span><div dir=3D"auto">Not sure I unders=
tand your concern. This is a change log since RFC1981.=C2=A0</div></div></b=
lockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-sty=
le:solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto">And it is a =
fact that the reference to RFC4821 was added into this draft.=C2=A0</div></=
div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto">Can y=
ou clarify?=C2=A0</div></div></blockquote><div><br></div><div>My apologies,=
 I wrote that too hastily, before reading the complete change</div><div>log=
, which contains a description of what changed in each draft as the</div><d=
iv>document proceeded through the WG process. The comment that I should</di=
v><div>have made is that many of those details are not useful to readers of=
 an</div><div>archival document. Looking at a diff between RFC 1981 and thi=
s draft,</div><div>the substantive changes pretty much boil down to these:<=
/div><div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 1, added a =
reference to RFC4821 along with a short</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 summary of what it does.</div></div><div><br></div><div><div>=C2=A0 =C2=
=A0 =C2=A0 - In Section 4, added text to discard an ICMP Packet Too Big mes=
sage</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 containing an MTU less than the =
IPv6 minimum link MTU and removed</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 the=
 corresponding note specifying actions that were removed from</div><div>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 [I-D.ietf-6man-rfc2460bis].</div></div><div><br></=
div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 5.2, removed text regarding=
 RH0 (since it was deprecated</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 by RFC5=
095) and removed text about obsolete security classifications.</div></div><=
div><br></div><div><div>=C2=A0 =C2=A0 =C2=A0 - In Section 5.2, clarified th=
at the tentative PMTU must not be made</div></div><div>=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 smaller that the IPv6 minimum link MTU.</div><div><br></div><div><d=
iv><div>Regarding that last change, I got confused when I was reading the c=
urrent text=C2=A0</div><div>in the draft:</div><div><br></div><div>=C2=A0 =
=C2=A0The node then uses the value in the MTU field in the Packet Too Big</=
div><div>=C2=A0 =C2=A0message as a tentative PMTU value or the minimum IPv6=
 next hope MTU</div><div>=C2=A0 =C2=A0if that is larger, and compares the t=
entative PMTU to the existing</div><div>=C2=A0 =C2=A0PMTU.=C2=A0 If the ten=
tative PMTU is less than the existing PMTU estimate,</div><div>=C2=A0 =C2=
=A0the tentative PMTU replaces the existing PMTU as the PMTU value for</div=
><div>=C2=A0 =C2=A0the path.</div><div><br></div><div>I initially took the =
words &quot;minimum IPv6 next hope [sic] MTU&quot; to mean the next</div><d=
iv>hop MTU of any link on the node, which of course is not what it meant. M=
aybe</div><div>I&#39;m being dense, but it wasn&#39;t until I looked at Don=
ald Eastlake&#39;s INT-DIR</div><div>review (<a href=3D"https://www.ietf.or=
g/mail-archive/web/int-dir/current/msg00339.html">https://www.ietf.org/mail=
-archive/web/int-dir/current/msg00339.html</a>)</div><div>that the correct =
meaning finally dawned on me. May I suggest saying =C2=A0instead:</div><div=
><br></div><div>=C2=A0 =C2=A0The node then uses the value in the MTU field =
in the Packet Too Big</div><div>=C2=A0 =C2=A0message as a tentative PMTU va=
lue or the IPv6 minimum link MTU if</div><div>=C2=A0 =C2=A0that is larger, =
and compares the tentative PMTU to the existing</div><div>=C2=A0 =C2=A0PMTU=
.=C2=A0 If the tentative PMTU is less than the existing PMTU estimate,</div=
><div>=C2=A0 =C2=A0the tentative PMTU replaces the existing PMTU as the PMT=
U value for</div><div>=C2=A0 =C2=A0the path.</div><div><br></div><div>In ot=
her words, s/minimum IPv6 next hope MTU/IPv6 minimum link MTU/.</div></div>=
</div><div>That makes the terminology consistent with the rest of the docum=
ent.</div><div><br></div><div>Thanks and regards,</div><div><br></div><div>=
Mike Heard<br></div></div></div></div>

--001a114d519895d98b0548450f27--


From nobody Sat Feb 11 10:42:09 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 470CB129888 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 99cvIr8aI3n8 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:42:05 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B515C129526 for <ietf@ietf.org>; Sat, 11 Feb 2017 10:42:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0023A3002C7 for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:04 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id DcF8xWwgV_rM for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:03 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id AC1D230009D for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:03 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Sat, 11 Feb 2017 13:42:02 -0500
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Message-Id: <B10DA49E-9562-42FF-A2B6-352EA7527167@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6FOmEbEf9taZoZWLbBB4-ApyHI8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:42:07 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Sat Feb 11 10:42:14 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8ACBB129526 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 9iFlqeHDGRTL for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:42:07 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DBA212953F for <ietf@ietf.org>; Sat, 11 Feb 2017 10:42:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 9076130040A for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:06 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id LyC9GyLsbIzu for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:05 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 6A50530009D for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:05 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Sat, 11 Feb 2017 13:42:05 -0500
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Message-Id: <4855E9DE-DF23-4E78-AD7F-0CD542BA3A9F@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vVJev5yDLhFE7e3-4qkn0wsgtfU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:42:08 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Sat Feb 11 10:49:00 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0D2F12941A for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:48:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 rLG6b6OJQrtB for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:48:58 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0396D129888 for <ietf@ietf.org>; Sat, 11 Feb 2017 10:48:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0FFD7300425 for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ds3Hl0hkMTSs for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:15 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id C870F30009D for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:15 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Sat, 11 Feb 2017 13:42:15 -0500
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Message-Id: <2B16B736-AA1A-4C50-AF5C-65C87A93099F@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o3OKArsEfIx-XQm61uAolzgXp-Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:48:59 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Sat Feb 11 10:49:10 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A559512997E for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:49:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-KCyU0Ujf64 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:48:58 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00AD9129526 for <ietf@ietf.org>; Sat, 11 Feb 2017 10:48:58 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id ECDAC300424 for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 2-xEYP3vul7D for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:16 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id A754B3003CF for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:16 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Sat, 11 Feb 2017 13:42:16 -0500
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Message-Id: <C94E592C-ADB7-4B2D-A40E-80B6E6C1EFE9@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wc7Q9KTUybe9O3d9x6yWZoK3I94>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:49:01 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Sat Feb 11 10:59:00 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08B09129485 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:58:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 7DZNvSL48K8Q for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 10:58:57 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BED7612941A for <ietf@ietf.org>; Sat, 11 Feb 2017 10:58:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D33E130040A for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:07 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 69LUB5MThydd for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:06 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id BF5AF30009D for <ietf@ietf.org>; Sat, 11 Feb 2017 13:42:06 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Sat, 11 Feb 2017 13:42:06 -0500
References: <CAAFsWK2QjdkovXTgJR-6Hpj=u=MD5Mjk0srYVpoqNnK_d7_Y9Q@mail.gmail.com> <78EFB6CA-BB21-4B6F-964C-9A0BBAA68023@dukhovni.org> <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org>
To: IETF <ietf@ietf.org>
In-Reply-To: <20170209223951.GW28349@mournblade.imrryr.org>
Message-Id: <65117389-C8DC-407A-99DC-7ED9C14CAB91@vigilsec.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9LoVcseVNI3C7xoQkP_STlzVUyM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 18:58:59 -0000

Viktor:

[bottom posting]

>=20
>> RFC 5280 says:
>>=20
>> A name constraint for Internet mail addresses MAY specify a
>> particular mailbox, all addresses at a particular host, or all
>> mailboxes in a domain.  To indicate a particular mailbox, the
>> constraint is the complete mail address.  For example,
>> "root@example.com" indicates the root mailbox on the host
>> "example.com".  To indicate all Internet mail addresses on a
>> particular host, the constraint is specified as the host name.  For
>> example, the constraint "example.com" is satisfied by any mail
>> address at the host "example.com".  To specify any address within a
>> domain, the constraint is specified with a leading period (as with
>> URIs).  For example, ".example.com" indicates all the Internet mail
>> addresses in the domain "example.com", but not Internet mail
>> addresses on the host "example.com=E2=80=9D.
>>=20
>> I think you are talking about constraints on addresses at a =
particular
>> host and constraints on mailboxes in a domain, but not constraints on =
a
>> particular mailbox.  Please correct me is I got that wrong.
>=20
> Primarily, but not exclusively.  In the case that an issuer CA is
> constrainted to a specific rfc822Name, it should not be possible
> to evade that constraint by using the same (all-ASCII) address as
> an SmtpUtf8Name.
>=20
>> I think you are suggesting that any A-label in the rfc822Name be =
converted
>> to a U-label, and the result is used to constrain the SmtpUtf8Name.
>=20
> No.  I am *not* suggesting *any* conversions.  If a CA has rfc822Name
> constraints and no SmptUtf8Name constraints, and the rfc822Name
> constraints limit the CA to "example.com", ".example.com", or as
> you suggest above, a particular set of explicit rfc822Name addresses,
> my suggestion is that it MUST NOT be able to issue SmtpUtf8Name =
altnames
> that violate those constraints.  For example:
>=20
> * CA is constrained to permitted subtree rfc822Name: example.com
> 	- can issue SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@exam=
ple.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, the second
> is a clear violation of the principle of least surprise (and the
> policy of the parent CA that created the name constraint).
>=20
>> If people like your suggestion, then a constraint for a particular =
mailbox
>> will still require a SmtpUtf8Name, so I think the mechanism described =
in
>> the draft is needed.  It would just be used in combination with the =
above.
>=20
> As to particular addresses, again:
>=20
>=20
> * CA is constrained to permitted subtree rfc822Name: =
viktor@example.com
> 	- cannot SmtpUtfName: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@example=
.com
> 	- cannot issue SmtpUtf8Name: =D0=B2=D0=B8=D0=BA=D1=82=D0=BE=D1=80@=
example.net
>=20
> In the current form of the draft both would be allowed, in clear
> violation of the name constraint on the permitted email addresses.


Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be =
completely separate.

You are arguing for some crossover, but I do not understand how A-labels =
in the rfc822Name are handled in your proposal.

If rfc822Name permits 'xn--fa-hia.de=E2=80=99 then it would need to be =
translated to 'fa=C3=9F.de=E2=80=99 for comparison in SmtpUtf8Name.

Russ


From nobody Sat Feb 11 11:24:25 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E9E2129457 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 11:24:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J2D95HzaT6Hu for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 11:24:23 -0800 (PST)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 121B11293EC for <ietf@ietf.org>; Sat, 11 Feb 2017 11:24:23 -0800 (PST)
Received: by mail-pf0-x243.google.com with SMTP id e4so4262011pfg.0 for <ietf@ietf.org>; Sat, 11 Feb 2017 11:24:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=o3lrDmvx52h2cpBOkqMk6R9Mw5mowHqrlIgXkcXxWiQ=; b=c8uUB3YwigupX8nLJPWl4eo5evaiR3GbSbANPrmoJLcPiBeYNrgZJm/alGte5M7Kiy Oeby9pohZZyDhafjWLC18AJcHjzY/6OMQnHDOhS/5h/J1gioc9GJnzlBP0qU+t72NMHT pWmCjt3hKPGPUom/dbVADhdxoIgZ1zoIP09JFKZnXFlupXjSJ7jyzhZ0mXA5oU39mdMD yLbKTKYULKwiUqV0u5c0QXo00CTiXJ/cNEmkyyLPSxHq0LOIKzIKHpmqfwUNJTO6fIyF yX9fT6A8Z2YoOdGWtympGrWA4blMxDILbeytvoHQ9M6XvNgIcZ5jH8SdwR5JaiFVHITK WUSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=o3lrDmvx52h2cpBOkqMk6R9Mw5mowHqrlIgXkcXxWiQ=; b=BTNBdBV8d1n3sLSRq7UAKGWOydWYXEOvLG/lZpcQyQYnYy12N5pXQiYnfQrco+VaEz 5SzDmX3e/+zmGsyhrP90R4er6g47LE7OXiT1825VgnukD3laZBWYVN/oGNTinKgh5nYB GlUtEp1jKTT5bewZcDC7wh6ceAPHph6zYuQe9eMhLzeAdbQyr/M7AJQed+2rOYbtmsLr DQ0CrxkhO0XRMWvwodcq3MnCcs9EVbrs1eapnAkM8DtmoPkiWxxC6sP0Uk8f4uJ0wTnD ssqZ5b4ADaTxslkg7RJ25HK/xHWibVwy8qAkPa25bR+ie+GAvL7RrY5xwBV3fLIMY2Z2 2aGA==
X-Gm-Message-State: AMke39mfgGUXAMZffqyCeCJ/RY6Qc1OIBdbCTD5jTutns/d4l+6E15hPULxtM8G2lQtabw==
X-Received: by 10.84.248.11 with SMTP id p11mr19471049pll.72.1486841062600; Sat, 11 Feb 2017 11:24:22 -0800 (PST)
Received: from [192.168.178.21] ([118.149.99.98]) by smtp.gmail.com with ESMTPSA id s65sm6095293pgb.64.2017.02.11.11.24.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Feb 2017 11:24:21 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com>
Date: Sun, 12 Feb 2017 08:24:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R4Ge5sk_dVleavCEDIJDGQnzeGo>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 19:24:24 -0000

On 12/02/2017 01:36, otroan@employees.org wrote:
> Brian,
> 
>>>> If people who were not involved in the 6man debate have opinions, it
>>>> would be useful to hear from them. I agree that there is no point in
>>>> the same people repeating the same arguments.
>>>
>>> in the absence of a (somewhat unbiased) summary of the critical
>>> issues(s), what do you suggest?
>>
>> I was going to say this off list, but what the heck?
>>
>> To be honest I'm trying to stay quiet. I think I've made my opinion
>> plain, and although I am of course the only human being alive who doesn't
>> suffer from confirmation bias, I'd *really* like to hear what people
>> think whose opinion I haven't already heard 20 times.
>>
>> I try not to be a purist. If the right answer is to allow packet
>> modifications that break PMTUD and IPsec/AH, let's do it, but let's
>> also say we're doing it. (I happen to think it's the wrong answer,
>> but that's my problem.) Leaving the text open to interpretation
>> would make a mockery of promoting it to Standard.
> 
> This is really not the discussion we ought to be having.
> "Allowing" or in any way specifying how header insertion could possibly be made to work is far outside of the scope of advancing 2460 to Internet standard.

If so, how can it be OK to leave the text ambiguous?

    Brian


From nobody Sat Feb 11 11:56:14 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E8C12944F for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 11:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 2NOaLdL-ccXc for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 11:56:11 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A35812943C for <ietf@ietf.org>; Sat, 11 Feb 2017 11:56:11 -0800 (PST)
Received: by mournblade.imrryr.org (Postfix, from userid 1034) id ECEE9284E4C; Sat, 11 Feb 2017 19:56:09 +0000 (UTC)
Date: Sat, 11 Feb 2017 19:56:09 +0000
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <20170211195609.GH28349@mournblade.imrryr.org>
References: <CAAFsWK0p5Zjj73Av3Z=TpjRmpJwFekfj9N+4zdcE_fFDcw65dA@mail.gmail.com> <20170206182023.GN28349@mournblade.imrryr.org> <20170208051311.GP28349@mournblade.imrryr.org> <CAAFsWK3xY35+yD5drtmUJUNMaAA8pRUwM3h22rvm+k7g5W8uKg@mail.gmail.com> <20170208151943.GQ28349@mournblade.imrryr.org> <CAAFsWK20Sf51W+cRUBET8-U5XXO+Z1ixOt3dgu70ad99FPsrWg@mail.gmail.com> <20170209175737.GV28349@mournblade.imrryr.org> <EB04BFE1-6A74-4697-9D4F-67A356B107DE@vigilsec.com> <20170209223951.GW28349@mournblade.imrryr.org> <B10DA49E-9562-42FF-A2B6-352EA7527167@vigilsec.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <B10DA49E-9562-42FF-A2B6-352EA7527167@vigilsec.com>
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7z8GwgAAttR0Lh_9i0hFCz-0nQQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 19:56:13 -0000

On Sat, Feb 11, 2017 at 01:42:02PM -0500, Russ Housley wrote:

> Wei is arguing that the two (ffc822Name and SmtpMUtf8Name) should be
> completely separate.

This introduces a means to evade name constraints placed on existing
(intermediate) CAs whose issuer (parent CA) was/is not SmtpUtf8 aware.
Software that introduces such bypass mechanisms would rate a CVE.
OpenSSL will not implement the proposal in its current form.

Once again, a CA with *ONLY* rfc822Name constraints should not be
able to able issue EE certificates with SmtpUtf8Name altNames that
conflict with its rfc822Name constraints.

Once again, I am not concerned about A-labels, U-labels, etc.,
rather, if a CA is constrained to example.com (an ordinary LDH
domain) email addresses via rfc822Name, and no SmtpUtf8Name
constraints are present, then the CA in question MUST NOT be able
to bypass that constraint via SmtpUtf8Name altnames with a domain
part of "example.com".

> You are arguing for some crossover, but I do not understand how A-labels
> in the rfc822Name are handled in your proposal.

So far, I've said nothing about about A-labels in rfc822Name
constraints.  Now that you ask, my view is that in the absence of
SmtpUtf8 constraints, an rfc822Name constraint that restricts a CA
to issue EE altnames with a domain part of xn--b1adqpd3ao5c.org
means that the CA should only be only issue rfc822Name altnames with
that verbatim A-label form only.  Thus, that same hypotheical CA would
not be able to issue SmtpUtf8Names with a domain part of духовный.org,
because that UTF-8 name does not match the literal rfc822Name constraint.

> If rfc822Name permits 'xn--fa-hia.de’ then it would need to be translated
> to 'faß.de’ for comparison in SmtpUtf8Name.

I did not want to conflate the rfc822Name constraint bypass issue
with the issue of A-label/U-label conversions.  My take is still
that conversions are not a good idea, and that a reference identifier
should be found verbatim in the certificate as a matching presented
identifier with no conversions.  With that a 'faß.de' SmtpUtf8Name
altname would not be allowed for a CA constrained to just
'xn--fa-hia.de'.

A CA that wants to start issuing 'faß.de' altnames can use a
suitable new intermediate certificate with appropriate additional
SmtpUtf8 constraints.

Requiring conversions from rfc822Name constraints that are A-labels
to correspoding U-label constraints would IMHO be a mistake, and
would require the introduction into OpenSSL and other X.509 stacks
of code that converts from A-labels to U-labels.  I think such
complexity is unwarranted, and I'd very much like to avoid the
need for any such conversions.

-- 
	Viktor.


From nobody Sat Feb 11 13:06:54 2017
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E08981293D8 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 13:06:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LSNBdeOKurVh for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 13:06:51 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAE17127076 for <ietf@ietf.org>; Sat, 11 Feb 2017 13:06:51 -0800 (PST)
Received: (qmail 1797 invoked from network); 11 Feb 2017 21:06:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent; s=703.589f7cea.k1702; bh=f90RDY9FpJXCWbvGHC1gf95+av3re4dhhitpNdP/92o=; b=jGHCShsHBcEdRHsqEUO42XOBmEHFwDDYMky9ieuB84+EmtaIeLXIukfFKCck1WdQAKexLBZ+ugjpdNiuesvW3/1iBJT9NXTrpkYfo7N/Zj3idI/JYPm5nzjkkScuxKFXZjmmpyqpMhh9LzsFPfGQ2FmOsy1FsMJDIrz2vo9qq+h3M/1IL70vQbJRJ/CUFmNdfnu31n6yoOyZtsTXL0icIRauMyf9cZrLEyFjbu6xGYcgFGUXJa1UfTrg3wJLoBah
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 11 Feb 2017 21:06:50 -0000
Date: 11 Feb 2017 16:06:49 -0500
Message-ID: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: "IETF general list" <ietf@ietf.org>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 21:06:53 -0000

>Once again, a CA with *ONLY* rfc822Name constraints should not be
>able to able issue EE certificates with SmtpUtf8Name altNames that
>conflict with its rfc822Name constraints.

How about if a CA with only rfc822Name constraints can't issue certs
with SmtpUTF8Names at all, and of course vice versa.  If you want both
kinds of names, the CA has to constrain both.

R's,
John


From nobody Sat Feb 11 13:13:05 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360FD127076 for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 13:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 6DXAKOfYVFgl for <ietf@ietfa.amsl.com>; Sat, 11 Feb 2017 13:13:02 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC5C012945A for <ietf@ietf.org>; Sat, 11 Feb 2017 13:13:02 -0800 (PST)
Received: from [IPv6:2604:2000:1382:81a2:151a:69a9:77ba:33a5] (unknown [IPv6:2604:2000:1382:81a2:151a:69a9:77ba:33a5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 4B094284E4B for <ietf@ietf.org>; Sat, 11 Feb 2017 21:13:01 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
Date: Sat, 11 Feb 2017 16:12:59 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <02630AD1-7F23-4597-B91B-AF64591EB6DF@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/08WXhnZgVEZ6xP6vHIx-xXlH294>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 21:13:04 -0000

> On Feb 11, 2017, at 4:06 PM, John R. Levine <johnl@iecc.com> wrote:
> 
> How about if a CA with only rfc822Name constraints can't issue certs
> with SmtpUTF8Names at all, and of course vice versa.  If you want both
> kinds of names, the CA has to constrain both.

This seems to me to be more restrictive than necessary, but I can live
with this as a rough consensus position if others prefer this option.

-- 
	Viktor.


From nobody Sat Feb 11 14:59:38 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58722129593; Sat, 11 Feb 2017 14:59:29 -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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dVmqmwQla--v; Sat, 11 Feb 2017 14:59:27 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id AE01212958D; Sat, 11 Feb 2017 14:59:27 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 11 Feb 2017 22:59:27 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 7599AD788D; Sat, 11 Feb 2017 14:59:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=ty5fPjcZy3Nqg4Wh6SbLO0l06G4=; b= c6ke+e30wx7UHQTss69syLtR7aoTuYqWAULKxvGY2I6d4le/C4EwfRIf3o3I+JP1 tHGssg2v8UezsgBKcm59nXVPSB1tUAKrnNB7NnUbw2n4I3GZiyCGmKvfWL12F7wP M6eAhNEZlZVa+nm5LpG7zDTFXujQPzR/gJ0I0pivk3Y=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=HM/MU5WH+IaRS1pyphKk8Bo 0jSy80P2hXL7B/gGR9S/4TmJvBAzgz9GDRuSYeGvuAzReLhulq8E3OmofIK2uDWU mWHp3LdzcFKU9diLHGiqLEh5V+MPRFa3DyT20UTneWFacMmJla0h5Nx88kzZknGb 9etswSQloDgOxZSl1piI=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id F3440D788A; Sat, 11 Feb 2017 14:59:25 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id C207089992FC; Sat, 11 Feb 2017 23:59:21 +0100 (CET)
From: otroan@employees.org
Message-Id: <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Date: Sat, 11 Feb 2017 23:59:20 +0100
In-Reply-To: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
To: "C. M. Heard" <heard@pobox.com>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y8eZcQsje155cKzV_6RWJwYoPy0>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Gen-ART <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2017 22:59:29 -0000

--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> How does this work for UDP?
>=20
> Sending packets no larger than 1280 bytes is always an option, and in
> the case of UDP-based request-response protocols such as DNS that do
> not have connection state, it may be the only feasible option.

Yes, but DNS tend to use IP fragmentation that suffers an order of =
magnitude worse fate than ICMP messages. ;-)

> Anyway, the point I was trying to make was not to argue about better
> or worse methods but rather to dispute the statement that PMTUD is
> essential for avoiding black holes. I don't believe that it is. The
> draft itself explicitly says that "IPv6 nodes are not required to
> implement Path MTU Discovery."

That's correct. But it then must restrict itself to sending packets at =
the minimum MTU size.
You cannot implement RFC2473 (IP in IP) without PMTUD for example.

[...]

> What criteria for advancement to IS do you think are not met by this =
document?
>=20
> I do not dispute that the document has met the formal criteria for IS =
in Section
> 2.2 of RFC 6410. I would argue, however, that its failure to provide a =
complete
> solution for environments where delivery of ICMP messages is not =
assured
> constitutes a significant technical omission for today's Internet, and =
I note
> that per RFC 2026 Section 4.1.1, even a PS "should have no known =
technical
> omissions." What I am asking the community, and the IESG, is whether =
it is
> wise to advance a document with known technical omissions; it seems to =
me
> that the Gen-ART reviewer has raised much the same question.

For IPv6, because of the removal of fragmentation by intermediate nodes, =
failure to provide a path where ICMP message delivery is assured is a =
considered a configuration error.

=46rom =
http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis=
.pdf:

"We observed that for IPV4 between 4% and 6% of the paths between the =
vantage points and our experimental setup filter ICMP PTB packets. For =
IPV6 this was between 0.77% and 1.07%. Furthermore, we found that when =
IPV4 Domain Name System (DNS) servers do not act on the receipt of ICMP =
PTB packets, between 11% and 14% of the answers from these DNS servers =
are lost. For IPV6 DNS servers this was between 40% and 42%. Lastly, we =
found that for IPV4 approximately 6% of the paths between the vantage =
points and our experimental setup filter IP fragments. For IPV6 this was =
approximately 10%."

=46rom that data it looks like we have been quite successful. ICMPv6 =
PMTUD is treated a lot better (about a 1% loss) than its IPv4 =
counterpart.
Unless better data exists I tend to conclude that the claim that the =
Internet breaks PTUMD for IPv6 is a myth.

Fragmentation on the other hand...
And please don't get me wrong, I think we have a big job to do on MTU =
issues. I just don't see data showing that PMTUD isn't doing what it was =
designed to do.

Best regards,
Ole




--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYn5dJAAoJEL7aWKiYQt926xAP/1sMZnrIKXS2y/MeUP1xHuPW
t5fvtAwaYLk1eDlpqkmQNagnn9RZOvoBgBZEN9xEL3pm2b+SD2PeP7cNbrCuY+K6
2LZ29tV12/Tu/mPq1JIyHjvRLN5RhmPOMXdxQyGAHvihJ+hjwJJEcsPqJkYaTzj0
rcZsVPXF38ueWUsM6TtbbXRSSCw2wOh4fhRbKCVaRBrerXkWu9EuRbS5IEwkA9/P
mJNm10RYXLvJcpR1xQMFHK3fsIrO+yEobiNtl6b3Uwh1z0l4OyoG65I8L295j/GW
SXKQIF8zmT59zcAFooajV+ZiCtSDBb+1XnPfzMxGX/Wo3a/uHqEhKrpOCHZmliDW
tJtsk1a+iopJnYP/4pKJ2SH9ccRQOU7K4zajTb7/0nvb4suAc5JrvqGIGZPmiVqf
12Zwz6w3j2g7Mt76uWcofXtcBuEBTmYiyGWYUb24YNUkZlSIwCC0/Qnmy+9JHQTo
x12EAh85S/utghlAyLmqmqRVPTw+j0sosIRxJxUlB/2tmSPuSvPw5BCOoJmtlcVf
pRE1pDEsW9w3/zL50w40t5hlouIh7UoC9cEsOJcPqI1sPXRy5DSmeW+4KEbxqF/H
6Wjr8HMNfpUpbPxsOmHj/8hAd07ibSCiEgk5/+iGCQ4GDU8mTJs8LaKcxz3h7UEs
jfFqsL+lt/obn+RsMm2k
=qWf4
-----END PGP SIGNATURE-----

--Apple-Mail=_6588FB4B-F8B2-4090-85F1-F52B0F22C020--


From nobody Sun Feb 12 02:50:12 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D498C127A90; Sun, 12 Feb 2017 02:50:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 AxF-T-mrUSU1; Sun, 12 Feb 2017 02:50:02 -0800 (PST)
Received: from sessmg23.ericsson.net (sessmg23.ericsson.net [193.180.251.45]) (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 9C246129443; Sun, 12 Feb 2017 02:50:01 -0800 (PST)
X-AuditID: c1b4fb2d-ec7ff70000001743-2f-58a03dd78d06
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id D8.07.05955.7DD30A85; Sun, 12 Feb 2017 11:49:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Sun, 12 Feb 2017 11:49:58 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Ben Campbell <ben@nostrum.com>, Martin Stiemerling <mls.ietf@gmail.com>
Subject: RE: Review of draft-ietf-mmusic-sctp-sdp-23
Thread-Topic: Review of draft-ietf-mmusic-sctp-sdp-23
Thread-Index: AQHSg+EbAwpJPT4tJUqGBSz5Ce2Q06FisC2AgAKDhPA=
Date: Sun, 12 Feb 2017 10:49:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4BFF8030@ESESSMB209.ericsson.se>
References: <148676059794.29305.2115176925259048270.idtracker@ietfa.amsl.com> <5D2D3F1D-9D7A-4C20-B8D5-E5F118F07DEE@nostrum.com>
In-Reply-To: <5D2D3F1D-9D7A-4C20-B8D5-E5F118F07DEE@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2J7oO512wURBj3nNSzmd55mt9jUv4nF 4tnG+SwWk55OY7KYuvwxi8WsPYtYHNg8ds66y+6xZMlPJo9ZO5+wBDBHcdmkpOZklqUW6dsl cGV8PveSpWAva8XZo39YGhh3s3QxcnJICJhIPHxyibmLkYtDSGAdo8S0N3tZIJzFjBLPdjxm 62Lk4GATsJDo/qcN0iAi4C0xo2kxWA2zwClGiW8zD7GBJISBJu3s2sgEUWQqsaV/HjuEbSXR O286mM0ioCpxfOZOsHpeAV+J1sdbGCGWNTFK/P28ixkkwSlgL7HpwW2wIkYBMYnvp9aADWUW EJe49WQ+E8TZAhJL9pxnhrBFJV4+/scKYStJNC55wgpRryOxYPcnNghbW2LZwtfMEIsFJU7O fMIygVF0FpKxs5C0zELSMgtJywJGllWMosWpxcW56UbGeqlFmcnFxfl5enmpJZsYgdF1cMtv 3R2Mq187HmIU4GBU4uE1iJ8fIcSaWFZcmXuIUYKDWUmElx0Ym0K8KYmVValF+fFFpTmpxYcY pTlYlMR5zVbeDxcSSE8sSc1OTS1ILYLJMnFwSjUwWm1t27JBbr2XuXCL1p2Pi66UGgWoOPrm aH4X7Z+1IbnF2OXQcpEV15N0o3fdPaB2UEJL6tBrdRH29Pmv77QxrTxy0bX95ofQhU87OQ8u e8ljMZfrmscBuROVrbuOnToWVcaw+JxHvU/c+y8OdxgXxH3LizvFrHamdEZh3dYH5sLPmzNm KnM+VWIpzkg01GIuKk4EABE5CcWqAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cQVRQ8MejSjMe_hnecqEwU1DTCQ>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 10:50:04 -0000

Thank You, Martin!=20

Regards,

Christer

-----Original Message-----
From: Ben Campbell [mailto:ben@nostrum.com]=20
Sent: 10 February 2017 23:27
To: Martin Stiemerling <mls.ietf@gmail.com>
Cc: tsv-art@ietf.org; draft-ietf-mmusic-sctp-sdp.all@ietf.org; ietf@ietf.or=
g; mmusic@ietf.org
Subject: Re: Review of draft-ietf-mmusic-sctp-sdp-23

Thanks, Martin!

Ben.

On 10 Feb 2017, at 15:03, Martin Stiemerling wrote:

> Reviewer: Martin Stiemerling
> Review result: Ready
>
> Hi there,
>
> I have reviewed draft-ietf-mmusic-sctp-sdp-23 as part of the TSV Area=20
> Review.
>
> Short summary: This draft is ready.
>
> Thank you for the clearly written draft.
>
>  Martin


From nobody Sun Feb 12 12:15:48 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB988129A38 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2017 12:15:46 -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 autolearn_force=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 HuARI8kRvrff for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2017 12:15:45 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F4088129A2E for <ietf@ietf.org>; Sun, 12 Feb 2017 12:15:44 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cd0Yc-000Awa-Fe; Sun, 12 Feb 2017 15:15:38 -0500
Date: Sun, 12 Feb 2017 15:15:31 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ned Freed <ned.freed@mrochek.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <1162BF5A37921B1555FF29F9@PSB>
In-Reply-To: <01QANBYPRC140005AQ@mauve.mrochek.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7ZR4b0DyNEPXbnD12OnkV9ASkvY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 20:15:47 -0000

--On Wednesday, February 8, 2017 12:39 -0800 Ned Freed
<ned.freed@mrochek.com> wrote:

>> 1). JMAP is just a a proxy and uses IMAP on the backend.
>> Configuring JMAP server is the same as configuring a MUA.
> 
> This is a key point. A lot of people have criticized this
> proposal based on the assumption that new clients will have to
> support both IMAP/SUBMIT and JMAP.

To be clear about what I'm concerned about, it isn't that.  My
assumption is that, although there might be exceptions, any
given client will support either one or the other, not both.  I
am concerned about what the servers and message stores need to
support and I think that would likely be "both" for a long time
or those who depend on IMAP clients would suffer gradual but
significant degradation of service.   See below for the latter.
Even if every client created after today supports JMAP only, I
would predict a long transition period.   That isn't really an
objection to the WG, just a request that the charter explicitly
requiring addressing the issue.

Parts of that are irrelevant if the message store supports pure
5322 objects with no metadata, but IMAP requires a certain
amount of metadata, so that, AFAICT, either makes the above
relevant or requires that JMAP support a strict superset on
those metadata in compatible formats.

> I think this is very unlikely to be the case. Once JMAP is out
> there I suspect there will be a significant number of clients
> - perhaps the majority - that will only support JMAP.

Yes.  See above.  But note that "JMAP replaces IMAP" requires
that it support identical functionality, be a superset of IMAP
function, or drop only the functions that no one is using or
cares about.  Note that I'm talking about functionality, not
syntax -- there are clearly a number of clumsy constructions in
IMAP that work that way only for historical compatibility
reasons and some cases of multiple ways to do the same thing.
If a new syntax and protocol model were adopted, no one sensible
would continue to defend those IMAP characteristics.

> These clients will depend on a combination of (1) Large MSPs
> quickly moving to deploy JMAP in addition to IMAP, (2) The
> availability of JMAP->IMAP/SUBMIT proxies, and (3) The
> addition of JMAP support to at least some of the open source
> message store implemenations.
> 
> (2) in particular creates additional requirements that need to
> be explicitly called out in the charter. In particular, it's
> imperative that (a) It be reasonable to implement
> JMAP->IMAP/SUBMIT proxies, even if that constrains JMAP in
> ways some folks do not like, (b) The list of IMAP extensions
> needed to properly implement JMAP be called out, and (c) The
> security considerations involved in operating such a proxy
> need to be described in detail.

Exactly.  If one expects JMAP to be wildly successful, and
unless there is either a plausible plan to make all of those
IMAP clients go away (even if there are no new ones), I think
that list should include either its being reasonable to
implement and support IMAP/SUBMIT-> JMAP proxies or other
overlays or a charter requirement to discuss residual use cases
for IMAP.    I'm particularly concerned about supporting
IMAP-native clients with a JMAP-native mailstore.

>> 2). Both are supported by the same software (i.e. Cyrus and
>> Dovecot use case). I doubt that incremental cost of
>> configuring both is much higher than just configuring one of
>> them.
> 
>> In either case configuring JMAP clients is a simple(r)
>> proposition: just distribute HTTP URI for a JMAP instance.
> 
>> > and to support, also for a long time, the ability to convert
>> > between the two formats.
> 
>> There are no 2 formats, both IMAP and JMAP operate on RFC
>> 5322 objects, so the rest of your argument is invalid.
> 
> Agreed. I have to say I really don't understand the confusion
> surrounding this point. IMAP has bodystructure plus a couple
> of other formats for returning message data, and a means of
> creating new messages from pieces of other messages, none of
> which look remotely like MIME/RFC 5322, and nobody cares.
> 
> This is effectively the same thing; why should anyone care
> here?

I can't speak for anyone else, but I'm concerned about what it
takes to create and maintain servers and mailstores that are
compatible with both IMAP and JMAP.  If that means proxies, we
either need to address the question of IMAP proxies over JMAP
and JMAP mailstores as well as the JMAP over IMAP-compatible
ones or I'd like the charter is require a good explanation of
why that isn't necessary.  That might be "IMAP-based systems
with JMAP overlays forever", but, the more people argue that
JMAP will take over (rapidly or otherwise), the less plausible
that position feels.

best,
    john


From nobody Sun Feb 12 12:56:50 2017
Return-Path: <evyncke@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDC8012943C; Sun, 12 Feb 2017 12:56:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nPb7_iy7X29x; Sun, 12 Feb 2017 12:56:42 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67C9C129A2E; Sun, 12 Feb 2017 12:56:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15100; q=dns/txt; s=iport; t=1486933002; x=1488142602; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=GSdSXhBUZZ9e4ZeNfXzg3CDrfdn7ZnhwjXl0jqCPavo=; b=K2zomYUb7gziVbJyXUrneEIAdTizyXuTh/eDqXe2fPFww/8cAF0cinDb aoBcGkTkvi//ek8TKdpQvQjtUNp0IRSX80Kn/4Z+Azknsci5/Ie/iotma 7vFMmSUeKYSi4iLlUUxqWAYDR+ZVH++4EPXHtysSgWG4khWBEMvt4i5Cu Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DqAQBOy6BY/5xdJa1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm86KWGBCQeDUooIkguIDId+hSyCDIYiAhqCYT8YAQIBAQEBAQE?= =?us-ascii?q?BYiiEaQEBAQMBI0sLBQsCAQYCEQMBAiQEAwICAh8RFAkIAgQBDQWJUgMNCJEqn?= =?us-ascii?q?U6CJSuGeQ2EEAEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTIIFgmqCUYIaCRaCUC6?= =?us-ascii?q?CMQWbODoBjXqEGZEFijWIXwEfOIEAURU9EQGEMx0ZgUh1iTOBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,154,1484006400";  d="scan'208,217";a="382769216"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Feb 2017 20:56:41 +0000
Received: from XCH-ALN-012.cisco.com (xch-aln-012.cisco.com [173.36.7.22]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v1CKufPg013975 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 12 Feb 2017 20:56:41 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-ALN-012.cisco.com (173.36.7.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 12 Feb 2017 14:56:40 -0600
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1210.000; Sun, 12 Feb 2017 14:56:40 -0600
From: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AQHSfOX4BXu17vCOlEW5Zvc01+W9PaFVw50AgAEB4YCAAInqAIAH3A5rgABc74CAAVJ4AIAAtouAgAFd/wCAANalgIACmaqA
Date: Sun, 12 Feb 2017 20:56:40 +0000
Message-ID: <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com>
In-Reply-To: <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.104.91]
Content-Type: multipart/alternative; boundary="_000_5CE4B4BF75A94DC980AE220281B046E9ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/255ZkMMhx0n5TWaTClVI2ZvwCPw>
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 20:56:45 -0000

--_000_5CE4B4BF75A94DC980AE220281B046E9ciscocom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

U3VyZXNoLCBKaW5tZWkgYW5kIEZlcm5hbmRvLA0KDQpJIGZ1bGx5IGFncmVlIHdpdGggeW91IFN1
cmVzaCwgdGhlIGdvYWwgb2YgYW4gSUVURiBsYXN0IGNhbGwgaXMgdG8gZ2V0IE5FVyBkaXNjdXNz
aW9uIGFuZCB0byByZS1kbyB0aGUgbGVuZ3RoeSBkaXNjdXNzaW9ucyB3ZSBoYWQgb24gNk1BTiBX
Ry4NCg0KLcOpcmljDQoNCkZyb206IGlwdjYgPGlwdjYtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVo
YWxmIG9mIFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNoLmtyaXNobmFuQGdtYWlsLmNvbT4NCkRhdGU6
IFNhdHVyZGF5IDExIEZlYnJ1YXJ5IDIwMTcgYXQgMDc6MTENClRvOiDnpZ7mmI7pgZTlk4kgPGpp
bm1laUB3aWRlLmFkLmpwPg0KQ2M6ICI2bWFuQGlldGYub3JnIiA8Nm1hbkBpZXRmLm9yZz4sIElF
VEYgRGlzY3Vzc2lvbiBsaXN0IDxpZXRmQGlldGYub3JnPiwgUGV0ZSBSZXNuaWNrIDxwcmVzbmlj
a0BxdGkucXVhbGNvbW0uY29tPiwgRmVybmFuZG8gR29udCA8ZmdvbnRAc2k2bmV0d29ya3MuY29t
PiwgImRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYub3JnIiA8ZHJhZnQtaWV0
Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmc+LCAiNm1hbi1jaGFpcnNAaWV0Zi5vcmci
IDw2bWFuLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1p
ZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQ+IChJbnRlcm5ldCBQcm90b2NvbCwgVmVyc2lvbiA2
IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJbnRlcm5ldCBTdGFuZGFyZA0KDQpIaSBKaW5tZWks
DQoNCk9uIEZlYiAxMCwgMjAxNyAxOjIzIFBNLCAi56We5piO6YGU5ZOJIiA8amlubWVpQHdpZGUu
YWQuanA8bWFpbHRvOmppbm1laUB3aWRlLmFkLmpwPj4gd3JvdGU6DQpBdCBUaHUsIDkgRmViIDIw
MTcgMTg6MzA6MTEgLTAzMDAsDQpGZXJuYW5kbyBHb250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb208
bWFpbHRvOmZnb250QHNpNm5ldHdvcmtzLmNvbT4+IHdyb3RlOg0KDQpXaGlsZSBJIGxhcmdlbHkg
YWdyZWUgd2l0aCBGZXJuYW5kbyBvbiBldmVyeXRoaW5nIGhlIHNhaWQsIEkgaGF2ZSB0bw0KYWRt
aXQgbW9zdCBvZiB0aGUgcG9pbnRzIGFyZSBqdXN0IHJlcGVhdGVkIGZyb20gdGhlIDZtYW4gZGlz
Y3Vzc2lvbiwNCmFuZCB3b24ndCBnZXQgdXMgYW55d2hlcmUgbmV3IGJ5IGRpc2N1c3NpbmcgdGhl
c2UgYWdhaW4gYXQgdGhpcyBwb2ludC4NCkkgZ3Vlc3MgdGhlIG9ubHkgbmV3IGlucHV0IGZvciB0
aGUgSUVURiBsYXN0IGNhbGwgaXMgdGhpczoNCg0KPiAyKSBIb3dldmVyLCBzb21lIGZvbGtzIGNh
bWUgdXAgd2l0aCBwcm9wb3NhbHMgdG8gaW5zZXJ0IEVILCBvbiB0aGUgYmFzaXMNCj4gdGhhdCAi
UkZDMjQ2MCBkb2VzIG5vdCBleHBsaWNpdGx5IGJhbiBFSCBpbnNlcnRpb24iLiBJZiB0aGVyZSdz
IHBlb3BsZQ0KPiBhcmd1aW5nIHRoYXQsIHdlIGNsZWFybHkgbmVlZCB0byBtYWtlIHRoaXMgY2xl
YXIgaW4gdGhlIHNwZWMuDQo+DQo+IDMpIFRoZXJlIHdhcyBhIGNvbnNlbnN1cyBjYWxsLCB5ZXMu
IFdoZW4gdGhlIGNhbGwgd2FzIG1hZGUgb24gdGhlDQo+IG1haWxpbmctbGlzdCwgdGhlIHZhc3Qg
bWFqb3JpdHkgb2Ygc3VwcG9ydGVycyBvZiAibGV0J3Mga2VlcCB0aGUNCj4gYW1iaWd1aXR5IiB3
ZXJlIGZvbGtzIGZyb20gdGhlIHNhbWUgY29tcGFueSBhcyAiMikiLiBJIGhhdmUgbm8gaWRlYSBp
Zg0KPiB0aGlzIGNoYW5nZXMgKG9yIG5vdCkgImNvbnNlbnN1cyIuLi4gYnV0IHRoaXMgaXMgY2xl
YXJseSBhbiBpbXBvcnRhbnQNCj4gZGF0YXBvaW50Lg0KQWx0aG91Z2ggSSBkb24ndCB3YW50IHRv
IHBvaW50IGEgZmluZ2VyIGF0IHBhcnRpY3VsYXIgcGVvcGxlIG9yDQpvcmdhbml6YXRpb25zIHdp
dGhvdXQgYW4gZXZpZGVuY2UsIEkgZ3Vlc3Mgbm90IGEgc21hbGwgbnVtYmVyIG9mIDZtYW4NCnBh
cnRpY2lwYW50cyAobm90IG9ubHkgdGhvc2Ugd2hvIGV4cGxpY2l0bHkgc3Bva2UgdXAgaGVyZSkg
c3VzcGVjdGVkDQp0aGF0IHRoZSBkZWNpc2lvbiBwcm9jZXNzIHdhcyBiaWFzZWQgd2l0aCB0aGUg
aW5mbHVlbmNlIG9mIGEgbGFyZ2UgYW5kDQpwb3dlcmZ1bCBvcmdhbml6YXRpb24gYW5kIHRoZSBw
cm9jZXNzIGFuZCByZXN1bHRpbmcgImNvbnNlbnN1cyIgd2FzDQpub3QgcmVhbGx5IGEgZmFpciBv
bmUuICBBbmQgSSdtIG5vdCBhbiBleGNlcHRpb24gdG8gaXQgLSBpbiBmYWN0LCBpdA0Kd2FzIHNv
IHVuYmVsaWV2YWJsZSB0byBtZSB0aGF0IHdlIGNhbid0IGNsYXJpZnkgYW4gYW1iaWd1aXR5IGV2
ZW4gd2hlbg0Kd2Ugd2VyZSBhbHNvIG9wZW4gZm9yIGZ1dHVyZSBleHRlbnNpb25zLCB0aGF0IEkg
Y291bGRuJ3QgdGhpbmsgb2YNCm90aGVyIHJlYXNvbnMgdGhhbiBhIGNvbXBhbnkgYWdlbmRhLg0K
DQpPZiBjb3Vyc2UsIGl0J3MgcXVpdGUgcG9zc2libGUgdGhhdCBpdCB3YXMganVzdCBhIGNvaW5j
aWRlbmNlIHRoYXQNCm1hbnkgcGVvcGxlIHdpdGggdGhlIHNhbWUgb3JnYW5pemF0aW9uIGdlbnVp
bmVseSB0aG91Z2h0IHdlIHNob3VsZA0KbGVhdmUgaXQgYW1iaWd1b3VzIHdoaWxlIG1hbnkgb3Ro
ZXJzIHN0cm9uZ2x5IHRob3VnaHQgd2Ugc2hvdWxkDQpjbGFyaWZ5IGl0IGJ1dCBmZXcgKGlmIG5v
dCBubykgcGVvcGxlIGZyb20gdGhhdCBvcmdhbml6YXRpb24gc3VwcG9ydGVkDQp0aGUgY2xhcmlm
aWNhdGlvbi4gIEJ1dCBJIGRvbid0IHRoaW5rIHdlIGNhbiBwcm92ZSBpdCBlaXRoZXIgd2F5Lg0K
DQpCdXQgYXMgRmVybmFuZG8gc2FpZCwgSSBiZWxpZXZlIHRoaXMgcG9pbnQgKGFuZCB0aGF0IHNl
dmVyYWwsIGFuZA0KYXJndWFibHkgbW9yZSwgcGFydGljaXBhbnRzIHN1c3BlY3RlZCBpdCkgc2hv
dWxkIGJlIGluY2x1ZGVkIGluIG1ha2luZw0KdGhlIGRlY2lzaW9uIGF0IHRoZSBJRVNHIGFuZCBh
dCB0aGUgSUVURiBsYXN0IGNhbGwuICBBbmQsIHdoYXRldmVyIHRoZQ0KZGVjaXNpb24sIGl0IHdv
dWxkIGJlIG1vcmUgcHJvZHVjdGl2ZSB0byBtb3ZlIG9uIGFmdGVyIHRoYXQgYW5kIHVzZQ0Kb3Vy
IHRpbWUgZm9yIHNvbWUgb3RoZXIgdGhpbmdzLg0KDQpJIGFtIGd1ZXNzaW5nIHRoYXQgdGhlIHBl
b3BsZSB3aG8gc3Bva2UgdXAgZHVyaW5nIHRoZSBXRyBwcm9jZXNzIHRvIG5vdCBwdXQgaW4gYW4g
b3V0cmlnaHQgcHJvaGliaXRpb24gd291bGQgbWFrZSB0aGVpciBjYXNlIGFsb25nIHdpdGggdGhl
aXIgYXJndW1lbnRzIGhlcmUgYXMgd2VsbC4gV2UgYXJlIG9ubHkgYSB3ZWVrIGludG8gYSBmb3Vy
IHdlZWsgbG9uZyBsYXN0IGNhbGwuDQoNClRoYW5rcw0KU3VyZXNoDQo=

--_000_5CE4B4BF75A94DC980AE220281B046E9ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <12D7C297E86B9740A4AA486D370B0D7B@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpQTWluZ0xpVTsNCglwYW5vc2UtMToyIDIgNSAwIDAgMCAwIDAgMCAwO30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Ik1TIE1pbmNobyI7DQoJcGFub3NlLTE6MiAyIDYgOSA0IDIgNSA4IDMg
NDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJs
dWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlw
ZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6
d2luZG93dGV4dDt9DQpzcGFuLm1zb0lucw0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsN
Cgltc28tc3R5bGUtbmFtZToiIjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lOw0KCWNvbG9y
OnRlYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5
Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29yZFNl
Y3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9k
eSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPlN1cmVzaCwgSmlu
bWVpIGFuZCBGZXJuYW5kbyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj5JIGZ1bGx5IGFncmVl
IHdpdGggeW91IFN1cmVzaCwgdGhlIGdvYWwgb2YgYW4gSUVURiBsYXN0IGNhbGwgaXMgdG8gZ2V0
IE5FVyBkaXNjdXNzaW9uIGFuZCB0byByZS1kbyB0aGUgbGVuZ3RoeSBkaXNjdXNzaW9ucyB3ZSBo
YWQgb24gNk1BTiBXRy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj4tw6lyaWM8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0I1QzRE
RiA0LjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0O21hcmdpbi1sZWZ0OjMuNzVwdDttYXJn
aW4tcmlnaHQ6MGNtIj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQg
I0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpO2NvbG9yOmJsYWNrIj5G
cm9tOiA8L3NwYW4+DQo8L2I+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7Y29sb3I6
YmxhY2siPmlwdjYgJmx0O2lwdjYtYm91bmNlc0BpZXRmLm9yZyZndDsgb24gYmVoYWxmIG9mIFN1
cmVzaCBLcmlzaG5hbiAmbHQ7c3VyZXNoLmtyaXNobmFuQGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5E
YXRlOiA8L2I+U2F0dXJkYXkgMTEgRmVicnVhcnkgMjAxNyBhdCAwNzoxMTxicj4NCjxiPlRvOiA8
L2I+PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNUyBNaW5jaG8mcXVvdDs7
Y29sb3I6YmxhY2siPuelnuaYjumBlOWTiTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
Q2FsaWJyaTtjb2xvcjpibGFjayI+ICZsdDtqaW5tZWlAd2lkZS5hZC5qcCZndDs8L3NwYW4+PHNw
YW4gc3R5bGU9ImZvbnQtZmFtaWx5OlBNaW5nTGlVO2NvbG9yOmJsYWNrIj48YnI+DQo8L3NwYW4+
PGI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7Y29sb3I6YmxhY2siPkNjOiA8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpO2NvbG9yOmJsYWNrIj4mcXVv
dDs2bWFuQGlldGYub3JnJnF1b3Q7ICZsdDs2bWFuQGlldGYub3JnJmd0OywgSUVURiBEaXNjdXNz
aW9uIGxpc3QgJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7LCBQZXRlIFJlc25pY2sgJmx0O3ByZXNuaWNr
QHF0aS5xdWFsY29tbS5jb20mZ3Q7LCBGZXJuYW5kbyBHb250ICZsdDtmZ29udEBzaTZuZXR3b3Jr
cy5jb20mZ3Q7LA0KICZxdW90O2RyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYu
b3JnJnF1b3Q7ICZsdDtkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZyZn
dDssICZxdW90OzZtYW4tY2hhaXJzQGlldGYub3JnJnF1b3Q7ICZsdDs2bWFuLWNoYWlyc0BpZXRm
Lm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IExhc3QgQ2FsbDogJmx0O2RyYWZ0LWll
dGYtNm1hbi1yZmMyNDYwYmlzLTA4LnR4dCZndDsgKEludGVybmV0IFByb3RvY29sLCBWZXJzaW9u
IDYgKElQdjYpIFNwZWNpZmljYXRpb24pIHRvIEludGVybmV0IFN0YW5kYXJkPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SGkgSmlubWVpLCZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9u
IEZlYiAxMCwgMjAxNyAxOjIzIFBNLCAmcXVvdDs8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1
b3Q7TVMgTWluY2hvJnF1b3Q7Ij7npZ7mmI7pgZTlk4k8L3NwYW4+JnF1b3Q7ICZsdDs8YSBocmVm
PSJtYWlsdG86amlubWVpQHdpZGUuYWQuanAiPmppbm1laUB3aWRlLmFkLmpwPC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QXQg
VGh1LCA5IEZlYiAyMDE3IDE4OjMwOjExIC0wMzAwLDxicj4NCkZlcm5hbmRvIEdvbnQgJmx0Ozxh
IGhyZWY9Im1haWx0bzpmZ29udEBzaTZuZXR3b3Jrcy5jb20iPmZnb250QHNpNm5ldHdvcmtzLmNv
bTwvYT4mZ3Q7IHdyb3RlOjxicj4NCjxicj4NCldoaWxlIEkgbGFyZ2VseSBhZ3JlZSB3aXRoIEZl
cm5hbmRvIG9uIGV2ZXJ5dGhpbmcgaGUgc2FpZCwgSSBoYXZlIHRvPGJyPg0KYWRtaXQgbW9zdCBv
ZiB0aGUgcG9pbnRzIGFyZSBqdXN0IHJlcGVhdGVkIGZyb20gdGhlIDZtYW4gZGlzY3Vzc2lvbiw8
YnI+DQphbmQgd29uJ3QgZ2V0IHVzIGFueXdoZXJlIG5ldyBieSBkaXNjdXNzaW5nIHRoZXNlIGFn
YWluIGF0IHRoaXMgcG9pbnQuPGJyPg0KSSBndWVzcyB0aGUgb25seSBuZXcgaW5wdXQgZm9yIHRo
ZSBJRVRGIGxhc3QgY2FsbCBpcyB0aGlzOjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KJmd0OyAyKSBI
b3dldmVyLCBzb21lIGZvbGtzIGNhbWUgdXAgd2l0aCBwcm9wb3NhbHMgdG8gaW5zZXJ0IEVILCBv
biB0aGUgYmFzaXM8YnI+DQomZ3Q7IHRoYXQgJnF1b3Q7UkZDMjQ2MCBkb2VzIG5vdCBleHBsaWNp
dGx5IGJhbiBFSCBpbnNlcnRpb24mcXVvdDsuIElmIHRoZXJlJ3MgcGVvcGxlPGJyPg0KJmd0OyBh
cmd1aW5nIHRoYXQsIHdlIGNsZWFybHkgbmVlZCB0byBtYWtlIHRoaXMgY2xlYXIgaW4gdGhlIHNw
ZWMuPGJyPg0KJmd0Ozxicj4NCiZndDsgMykgVGhlcmUgd2FzIGEgY29uc2Vuc3VzIGNhbGwsIHll
cy4gV2hlbiB0aGUgY2FsbCB3YXMgbWFkZSBvbiB0aGU8YnI+DQomZ3Q7IG1haWxpbmctbGlzdCwg
dGhlIHZhc3QgbWFqb3JpdHkgb2Ygc3VwcG9ydGVycyBvZiAmcXVvdDtsZXQncyBrZWVwIHRoZTxi
cj4NCiZndDsgYW1iaWd1aXR5JnF1b3Q7IHdlcmUgZm9sa3MgZnJvbSB0aGUgc2FtZSBjb21wYW55
IGFzICZxdW90OzIpJnF1b3Q7LiBJIGhhdmUgbm8gaWRlYSBpZjxicj4NCiZndDsgdGhpcyBjaGFu
Z2VzIChvciBub3QpICZxdW90O2NvbnNlbnN1cyZxdW90Oy4uLiBidXQgdGhpcyBpcyBjbGVhcmx5
IGFuIGltcG9ydGFudDxicj4NCiZndDsgZGF0YXBvaW50LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbHRob3VnaCBJIGRvbid0IHdhbnQgdG8gcG9pbnQgYSBm
aW5nZXIgYXQgcGFydGljdWxhciBwZW9wbGUgb3I8YnI+DQpvcmdhbml6YXRpb25zIHdpdGhvdXQg
YW4gZXZpZGVuY2UsIEkgZ3Vlc3Mgbm90IGEgc21hbGwgbnVtYmVyIG9mIDZtYW48YnI+DQpwYXJ0
aWNpcGFudHMgKG5vdCBvbmx5IHRob3NlIHdobyBleHBsaWNpdGx5IHNwb2tlIHVwIGhlcmUpIHN1
c3BlY3RlZDxicj4NCnRoYXQgdGhlIGRlY2lzaW9uIHByb2Nlc3Mgd2FzIGJpYXNlZCB3aXRoIHRo
ZSBpbmZsdWVuY2Ugb2YgYSBsYXJnZSBhbmQ8YnI+DQpwb3dlcmZ1bCBvcmdhbml6YXRpb24gYW5k
IHRoZSBwcm9jZXNzIGFuZCByZXN1bHRpbmcgJnF1b3Q7Y29uc2Vuc3VzJnF1b3Q7IHdhczxicj4N
Cm5vdCByZWFsbHkgYSBmYWlyIG9uZS4mbmJzcDsgQW5kIEknbSBub3QgYW4gZXhjZXB0aW9uIHRv
IGl0IC0gaW4gZmFjdCwgaXQ8YnI+DQp3YXMgc28gdW5iZWxpZXZhYmxlIHRvIG1lIHRoYXQgd2Ug
Y2FuJ3QgY2xhcmlmeSBhbiBhbWJpZ3VpdHkgZXZlbiB3aGVuPGJyPg0Kd2Ugd2VyZSBhbHNvIG9w
ZW4gZm9yIGZ1dHVyZSBleHRlbnNpb25zLCB0aGF0IEkgY291bGRuJ3QgdGhpbmsgb2Y8YnI+DQpv
dGhlciByZWFzb25zIHRoYW4gYSBjb21wYW55IGFnZW5kYS48YnI+DQo8YnI+DQpPZiBjb3Vyc2Us
IGl0J3MgcXVpdGUgcG9zc2libGUgdGhhdCBpdCB3YXMganVzdCBhIGNvaW5jaWRlbmNlIHRoYXQ8
YnI+DQptYW55IHBlb3BsZSB3aXRoIHRoZSBzYW1lIG9yZ2FuaXphdGlvbiBnZW51aW5lbHkgdGhv
dWdodCB3ZSBzaG91bGQ8YnI+DQpsZWF2ZSBpdCBhbWJpZ3VvdXMgd2hpbGUgbWFueSBvdGhlcnMg
c3Ryb25nbHkgdGhvdWdodCB3ZSBzaG91bGQ8YnI+DQpjbGFyaWZ5IGl0IGJ1dCBmZXcgKGlmIG5v
dCBubykgcGVvcGxlIGZyb20gdGhhdCBvcmdhbml6YXRpb24gc3VwcG9ydGVkPGJyPg0KdGhlIGNs
YXJpZmljYXRpb24uJm5ic3A7IEJ1dCBJIGRvbid0IHRoaW5rIHdlIGNhbiBwcm92ZSBpdCBlaXRo
ZXIgd2F5Ljxicj4NCjxicj4NCkJ1dCBhcyBGZXJuYW5kbyBzYWlkLCBJIGJlbGlldmUgdGhpcyBw
b2ludCAoYW5kIHRoYXQgc2V2ZXJhbCwgYW5kPGJyPg0KYXJndWFibHkgbW9yZSwgcGFydGljaXBh
bnRzIHN1c3BlY3RlZCBpdCkgc2hvdWxkIGJlIGluY2x1ZGVkIGluIG1ha2luZzxicj4NCnRoZSBk
ZWNpc2lvbiBhdCB0aGUgSUVTRyBhbmQgYXQgdGhlIElFVEYgbGFzdCBjYWxsLiZuYnNwOyBBbmQs
IHdoYXRldmVyIHRoZTxicj4NCmRlY2lzaW9uLCBpdCB3b3VsZCBiZSBtb3JlIHByb2R1Y3RpdmUg
dG8gbW92ZSBvbiBhZnRlciB0aGF0IGFuZCB1c2U8YnI+DQpvdXIgdGltZSBmb3Igc29tZSBvdGhl
ciB0aGluZ3MuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFtIGd1ZXNzaW5nIHRoYXQg
dGhlIHBlb3BsZSB3aG8gc3Bva2UgdXAgZHVyaW5nIHRoZSBXRyBwcm9jZXNzIHRvIG5vdCBwdXQg
aW4gYW4gb3V0cmlnaHQgcHJvaGliaXRpb24gd291bGQgbWFrZSB0aGVpciBjYXNlIGFsb25nIHdp
dGggdGhlaXIgYXJndW1lbnRzIGhlcmUgYXMgd2VsbC4gV2UgYXJlIG9ubHkgYSB3ZWVrIGludG8g
YSBmb3VyIHdlZWsgbG9uZyBsYXN0IGNhbGwuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3VyZXNoPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_5CE4B4BF75A94DC980AE220281B046E9ciscocom_--


From nobody Sun Feb 12 15:05:59 2017
Return-Path: <John_Leddy@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A83612945D; Sun, 12 Feb 2017 15:05: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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 4HgiFchWh_3B; Sun, 12 Feb 2017 15:05:54 -0800 (PST)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (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 F1697126D74; Sun, 12 Feb 2017 15:05:53 -0800 (PST)
X-AuditID: 60721c4c-61fff70000007eaf-74-58a0ea4efafd
Received: from VAADCEX47.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by  (SMTP Gateway) with SMTP id F4.BE.32431.E4AE0A85; Sun, 12 Feb 2017 18:05:52 -0500 (EST)
Received: from VAADCEX41.cable.comcast.com (147.191.103.218) by VAADCEX47.cable.comcast.com (147.191.103.224) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Sun, 12 Feb 2017 18:05:49 -0500
Received: from VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268]) by VAADCEX41.cable.comcast.com ([fe80::3aea:a7ff:fe12:e268%19]) with mapi id 15.00.1263.000; Sun, 12 Feb 2017 18:05:49 -0500
From: "Leddy, John" <John_Leddy@comcast.com>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, =?utf-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AQHSfOX4BXu17vCOlEW5Zvc01+W9PaFVw50AgAEB4YCAAInqAIAH3A5rgABc74CAAVJ4AIAAtouAgAFd/wCAANalgIACmaqA//+vlgA=
Date: Sun, 12 Feb 2017 23:05:49 +0000
Message-ID: <A823FD1C-4ED8-4788-81F0-0F672F1FA364@cable.comcast.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com> <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com>
In-Reply-To: <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1e.0.170107
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [68.87.29.11]
Content-Type: multipart/alternative; boundary="_000_A823FD1C4ED8478881F00F672F1FA364cablecomcastcom_"
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDKsWRmVeSWpSXmKPExsWSUOxpoRvwakGEwaadFha7p0xjs1i54i6T xe5FPawWX/YvYLR4tnE+i8Wi3QfYLK5cbWG2OLLhLKsDh8eU3xtZPXbOusvusWTJTyaPRVOf MXp8ufyZzWPv02NsAWxRXDYpqTmZZalF+nYJXBktT1ezFPyZx1hxu6+DrYHx9izGLkZODgkB E4kT7ROZuhi5OIQEZjJJXOhexAzhHGKU2HT0CAuEc5JR4vyEL2AtbAI6EjOmXWMFSYgITGCU uL7hA1g/s0Azk8TU76fZQRxhgTZGiakXnjJClLUzSqxr+cEK0i8iUCbx7doEJhCbRUBV4nDn djCbV8BF4t+UXWwQC5eyS1yY/YsFJMEpYCsxp7cTrIhRQEzi+6k1YDazgLjErSfzmSD+EJBY suc8M4QtKvHy8T+wZaICehIbL0xjh4jrSJy9/gTqbwOJrUv3Ac3nALLlJT7OZQIxmQXSJZ6u cIM4R1Di5MwnLBDV4hKHj+xgncAoOQvJ4lkIHbOQdECENSXW79KHqFaUmNL9kB3C1pBonTMX ynaQuNvUx4isZgEjxypGubLExJTk3Iz80hIDI73kxKScVL3k/NzkxOISEL2JEZRmimR8djB+ muZxiFGAg1GJhzfr5oIIIdbEsuLKXGDEcTArifAufAgU4k1JrKxKLcqPLyrNSS0+xCjNwaIk zpt0aEaEkEB6YklqdmpqQWoRTJaJg1OqgdGe6Ui03f9b9y8I50hd+7w+wKLz8PMr7y7rPF/4 dmYK71OnfTrPpR5npnfNTDpqtsbgxreQC29UHSbd3mjtWJFvmpBn7Dm7aMph/l1NC3XXv35x k5tlucm5x3MPm+dqerW9mibwvUu57LRf0YoUBsXXldK39bYsSBJm2mkZu2Xer4N+HgoLCiSV WIozEg21mIuKEwFnM2eSLwMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/byGahLnejDIqovzxyMDbAMS6J64>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Feb 2017 23:05:56 -0000

--_000_A823FD1C4ED8478881F00F672F1FA364cablecomcastcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gdHJ5aW5nIHRvIHVuZGVyc3RhbmQgaG93IGEgYmFuIG9mIHRoaXMgZnVuY3Rpb25hbGl0
eSB3b3VsZCB3b3JrLiAgSXMgaXQgdGFyZ2V0ZWQgYXQgdmVuZG9yIHByb2R1Y3RzLCBwcmVjbHVk
aW5nIHRoZW0gZnJvbSBpbXBsZW1lbnRpbmcgdGhlIGZ1bmN0aW9uYWxpdHk/DQoNCklmIHRoZXJl
IGlzIGEgdGVjaG5pY2FsIHByb2JsZW0gdGhhdCBjYW4gYmUgc29sdmVkIGJ5IHVzaW5nIEVIIGlu
c2VydGlvbiB3aXRoaW4gYSBkb21haW4gd2hlcmUgdGhlcmUgYXJlIG5vIGhhcm1mdWwgc2lkZSBl
ZmZlY3RzLCBpdCBzaG91bGQgYmUgYWJsZSB0byBiZSB1c2VkLg0KSW4gYSBzb2Z0d2FyZSBuZXR3
b3JraW5nIHdvcmxkIHdoZXJlIGZ1bmN0aW9uYWxpdHkgaXMgYmVpbmcgZGVwbG95ZWQgdGhhdCBp
cyBub3QgZnJvbSB0cmFkaXRpb25hbCBuZXR3b3JrIHZlbmRvcnM7IHNvbHV0aW9ucyB0aGF0IHNv
bHZlIHByb2JsZW1zIGVmZmljaWVudGx5IHdpbGwgZ2V0IGRlcGxveWVkLg0KDQpKb2huIExlZGR5
DQoNCkZyb206IGlldGYgPGlldGYtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVoYWxmIG9mICJFcmlj
IFZ5bmNrZSAoZXZ5bmNrZSkiIDxldnluY2tlQGNpc2NvLmNvbT4NCkRhdGU6IFN1bmRheSwgRmVi
cnVhcnkgMTIsIDIwMTcgYXQgMzo1NiBQTQ0KVG86IFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNoLmty
aXNobmFuQGdtYWlsLmNvbT4sIOelnuaYjumBlOWTiSA8amlubWVpQHdpZGUuYWQuanA+DQpDYzog
IjZtYW5AaWV0Zi5vcmciIDw2bWFuQGlldGYub3JnPiwgSUVURiBEaXNjdXNzaW9uIGxpc3QgPGll
dGZAaWV0Zi5vcmc+LCBQZXRlIFJlc25pY2sgPHByZXNuaWNrQHF0aS5xdWFsY29tbS5jb20+LCAi
ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmciIDxkcmFmdC1pZXRmLTZt
YW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZz4sICI2bWFuLWNoYWlyc0BpZXRmLm9yZyIgPDZt
YW4tY2hhaXJzQGlldGYub3JnPg0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWlldGYt
Nm1hbi1yZmMyNDYwYmlzLTA4LnR4dD4gKEludGVybmV0IFByb3RvY29sLCBWZXJzaW9uIDYgKElQ
djYpIFNwZWNpZmljYXRpb24pIHRvIEludGVybmV0IFN0YW5kYXJkDQoNClN1cmVzaCwgSmlubWVp
IGFuZCBGZXJuYW5kbywNCg0KSSBmdWxseSBhZ3JlZSB3aXRoIHlvdSBTdXJlc2gsIHRoZSBnb2Fs
IG9mIGFuIElFVEYgbGFzdCBjYWxsIGlzIHRvIGdldCBORVcgZGlzY3Vzc2lvbiBhbmQgdG8gcmUt
ZG8gdGhlIGxlbmd0aHkgZGlzY3Vzc2lvbnMgd2UgaGFkIG9uIDZNQU4gV0cuDQoNCi3DqXJpYw0K
DQpGcm9tOiBpcHY2IDxpcHY2LWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBTdXJlc2gg
S3Jpc2huYW4gPHN1cmVzaC5rcmlzaG5hbkBnbWFpbC5jb20+DQpEYXRlOiBTYXR1cmRheSAxMSBG
ZWJydWFyeSAyMDE3IGF0IDA3OjExDQpUbzog56We5piO6YGU5ZOJIDxqaW5tZWlAd2lkZS5hZC5q
cD4NCkNjOiAiNm1hbkBpZXRmLm9yZyIgPDZtYW5AaWV0Zi5vcmc+LCBJRVRGIERpc2N1c3Npb24g
bGlzdCA8aWV0ZkBpZXRmLm9yZz4sIFBldGUgUmVzbmljayA8cHJlc25pY2tAcXRpLnF1YWxjb21t
LmNvbT4sIEZlcm5hbmRvIEdvbnQgPGZnb250QHNpNm5ldHdvcmtzLmNvbT4sICJkcmFmdC1pZXRm
LTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZyIgPGRyYWZ0LWlldGYtNm1hbi1yZmMyNDYw
YmlzQHRvb2xzLmlldGYub3JnPiwgIjZtYW4tY2hhaXJzQGlldGYub3JnIiA8Nm1hbi1jaGFpcnNA
aWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQtaWV0Zi02bWFuLXJmYzI0
NjBiaXMtMDgudHh0PiAoSW50ZXJuZXQgUHJvdG9jb2wsIFZlcnNpb24gNiAoSVB2NikgU3BlY2lm
aWNhdGlvbikgdG8gSW50ZXJuZXQgU3RhbmRhcmQNCg0KSGkgSmlubWVpLA0KDQpPbiBGZWIgMTAs
IDIwMTcgMToyMyBQTSwgIuelnuaYjumBlOWTiSIgPGppbm1laUB3aWRlLmFkLmpwPG1haWx0bzpq
aW5tZWlAd2lkZS5hZC5qcD4+IHdyb3RlOg0KQXQgVGh1LCA5IEZlYiAyMDE3IDE4OjMwOjExIC0w
MzAwLA0KRmVybmFuZG8gR29udCA8ZmdvbnRAc2k2bmV0d29ya3MuY29tPG1haWx0bzpmZ29udEBz
aTZuZXR3b3Jrcy5jb20+PiB3cm90ZToNCg0KV2hpbGUgSSBsYXJnZWx5IGFncmVlIHdpdGggRmVy
bmFuZG8gb24gZXZlcnl0aGluZyBoZSBzYWlkLCBJIGhhdmUgdG8NCmFkbWl0IG1vc3Qgb2YgdGhl
IHBvaW50cyBhcmUganVzdCByZXBlYXRlZCBmcm9tIHRoZSA2bWFuIGRpc2N1c3Npb24sDQphbmQg
d29uJ3QgZ2V0IHVzIGFueXdoZXJlIG5ldyBieSBkaXNjdXNzaW5nIHRoZXNlIGFnYWluIGF0IHRo
aXMgcG9pbnQuDQpJIGd1ZXNzIHRoZSBvbmx5IG5ldyBpbnB1dCBmb3IgdGhlIElFVEYgbGFzdCBj
YWxsIGlzIHRoaXM6DQoNCj4gMikgSG93ZXZlciwgc29tZSBmb2xrcyBjYW1lIHVwIHdpdGggcHJv
cG9zYWxzIHRvIGluc2VydCBFSCwgb24gdGhlIGJhc2lzDQo+IHRoYXQgIlJGQzI0NjAgZG9lcyBu
b3QgZXhwbGljaXRseSBiYW4gRUggaW5zZXJ0aW9uIi4gSWYgdGhlcmUncyBwZW9wbGUNCj4gYXJn
dWluZyB0aGF0LCB3ZSBjbGVhcmx5IG5lZWQgdG8gbWFrZSB0aGlzIGNsZWFyIGluIHRoZSBzcGVj
Lg0KPg0KPiAzKSBUaGVyZSB3YXMgYSBjb25zZW5zdXMgY2FsbCwgeWVzLiBXaGVuIHRoZSBjYWxs
IHdhcyBtYWRlIG9uIHRoZQ0KPiBtYWlsaW5nLWxpc3QsIHRoZSB2YXN0IG1ham9yaXR5IG9mIHN1
cHBvcnRlcnMgb2YgImxldCdzIGtlZXAgdGhlDQo+IGFtYmlndWl0eSIgd2VyZSBmb2xrcyBmcm9t
IHRoZSBzYW1lIGNvbXBhbnkgYXMgIjIpIi4gSSBoYXZlIG5vIGlkZWEgaWYNCj4gdGhpcyBjaGFu
Z2VzIChvciBub3QpICJjb25zZW5zdXMiLi4uIGJ1dCB0aGlzIGlzIGNsZWFybHkgYW4gaW1wb3J0
YW50DQo+IGRhdGFwb2ludC4NCkFsdGhvdWdoIEkgZG9uJ3Qgd2FudCB0byBwb2ludCBhIGZpbmdl
ciBhdCBwYXJ0aWN1bGFyIHBlb3BsZSBvcg0Kb3JnYW5pemF0aW9ucyB3aXRob3V0IGFuIGV2aWRl
bmNlLCBJIGd1ZXNzIG5vdCBhIHNtYWxsIG51bWJlciBvZiA2bWFuDQpwYXJ0aWNpcGFudHMgKG5v
dCBvbmx5IHRob3NlIHdobyBleHBsaWNpdGx5IHNwb2tlIHVwIGhlcmUpIHN1c3BlY3RlZA0KdGhh
dCB0aGUgZGVjaXNpb24gcHJvY2VzcyB3YXMgYmlhc2VkIHdpdGggdGhlIGluZmx1ZW5jZSBvZiBh
IGxhcmdlIGFuZA0KcG93ZXJmdWwgb3JnYW5pemF0aW9uIGFuZCB0aGUgcHJvY2VzcyBhbmQgcmVz
dWx0aW5nICJjb25zZW5zdXMiIHdhcw0Kbm90IHJlYWxseSBhIGZhaXIgb25lLiAgQW5kIEknbSBu
b3QgYW4gZXhjZXB0aW9uIHRvIGl0IC0gaW4gZmFjdCwgaXQNCndhcyBzbyB1bmJlbGlldmFibGUg
dG8gbWUgdGhhdCB3ZSBjYW4ndCBjbGFyaWZ5IGFuIGFtYmlndWl0eSBldmVuIHdoZW4NCndlIHdl
cmUgYWxzbyBvcGVuIGZvciBmdXR1cmUgZXh0ZW5zaW9ucywgdGhhdCBJIGNvdWxkbid0IHRoaW5r
IG9mDQpvdGhlciByZWFzb25zIHRoYW4gYSBjb21wYW55IGFnZW5kYS4NCg0KT2YgY291cnNlLCBp
dCdzIHF1aXRlIHBvc3NpYmxlIHRoYXQgaXQgd2FzIGp1c3QgYSBjb2luY2lkZW5jZSB0aGF0DQpt
YW55IHBlb3BsZSB3aXRoIHRoZSBzYW1lIG9yZ2FuaXphdGlvbiBnZW51aW5lbHkgdGhvdWdodCB3
ZSBzaG91bGQNCmxlYXZlIGl0IGFtYmlndW91cyB3aGlsZSBtYW55IG90aGVycyBzdHJvbmdseSB0
aG91Z2h0IHdlIHNob3VsZA0KY2xhcmlmeSBpdCBidXQgZmV3IChpZiBub3Qgbm8pIHBlb3BsZSBm
cm9tIHRoYXQgb3JnYW5pemF0aW9uIHN1cHBvcnRlZA0KdGhlIGNsYXJpZmljYXRpb24uICBCdXQg
SSBkb24ndCB0aGluayB3ZSBjYW4gcHJvdmUgaXQgZWl0aGVyIHdheS4NCg0KQnV0IGFzIEZlcm5h
bmRvIHNhaWQsIEkgYmVsaWV2ZSB0aGlzIHBvaW50IChhbmQgdGhhdCBzZXZlcmFsLCBhbmQNCmFy
Z3VhYmx5IG1vcmUsIHBhcnRpY2lwYW50cyBzdXNwZWN0ZWQgaXQpIHNob3VsZCBiZSBpbmNsdWRl
ZCBpbiBtYWtpbmcNCnRoZSBkZWNpc2lvbiBhdCB0aGUgSUVTRyBhbmQgYXQgdGhlIElFVEYgbGFz
dCBjYWxsLiAgQW5kLCB3aGF0ZXZlciB0aGUNCmRlY2lzaW9uLCBpdCB3b3VsZCBiZSBtb3JlIHBy
b2R1Y3RpdmUgdG8gbW92ZSBvbiBhZnRlciB0aGF0IGFuZCB1c2UNCm91ciB0aW1lIGZvciBzb21l
IG90aGVyIHRoaW5ncy4NCg0KSSBhbSBndWVzc2luZyB0aGF0IHRoZSBwZW9wbGUgd2hvIHNwb2tl
IHVwIGR1cmluZyB0aGUgV0cgcHJvY2VzcyB0byBub3QgcHV0IGluIGFuIG91dHJpZ2h0IHByb2hp
Yml0aW9uIHdvdWxkIG1ha2UgdGhlaXIgY2FzZSBhbG9uZyB3aXRoIHRoZWlyIGFyZ3VtZW50cyBo
ZXJlIGFzIHdlbGwuIFdlIGFyZSBvbmx5IGEgd2VlayBpbnRvIGEgZm91ciB3ZWVrIGxvbmcgbGFz
dCBjYWxsLg0KDQpUaGFua3MNClN1cmVzaA0K

--_000_A823FD1C4ED8478881F00F672F1FA364cablecomcastcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FEB4E4517DF6904884793E011C3DEB55@cable.comcast.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWls
eTpQTWluZ0xpVTsNCglwYW5vc2UtMToyIDIgNSAwIDAgMCAwIDAgMCAwO30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Ik1TIE1pbmNobyI7DQoJcGFub3NlLTE6MiAyIDYgOSA0IDIgNSA4IDMg
NDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwg
ZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglm
b250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCmE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJs
dWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlw
ZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93
dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBs
eTsNCglmb250LWZhbWlseTpDYWxpYnJpOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5tc29J
bnMNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJbXNvLXN0eWxlLW5hbWU6IiI7DQoJ
dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTsNCgljb2xvcjp0ZWFsO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0iRU4tVVMi
IGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OkNhbGlicmkiPknigJltIHRyeWluZyB0byB1bmRlcnN0YW5kIGhvdyBhIGJhbiBvZiB0
aGlzIGZ1bmN0aW9uYWxpdHkgd291bGQgd29yay4mbmJzcDsgSXMgaXQgdGFyZ2V0ZWQgYXQgdmVu
ZG9yIHByb2R1Y3RzLCBwcmVjbHVkaW5nIHRoZW0gZnJvbSBpbXBsZW1lbnRpbmcgdGhlIGZ1bmN0
aW9uYWxpdHk/PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SWYgdGhlcmUgaXMgYSB0ZWNobmlj
YWwgcHJvYmxlbSB0aGF0IGNhbiBiZSBzb2x2ZWQgYnkgdXNpbmcgRUggaW5zZXJ0aW9uIHdpdGhp
biBhIGRvbWFpbiB3aGVyZSB0aGVyZSBhcmUgbm8gaGFybWZ1bCBzaWRlIGVmZmVjdHMsIGl0IHNo
b3VsZCBiZSBhYmxlIHRvIGJlIHVzZWQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2Fs
aWJyaSI+SW4gYSBzb2Z0d2FyZSBuZXR3b3JraW5nIHdvcmxkIHdoZXJlIGZ1bmN0aW9uYWxpdHkg
aXMgYmVpbmcgZGVwbG95ZWQgdGhhdCBpcyBub3QgZnJvbSB0cmFkaXRpb25hbCBuZXR3b3JrIHZl
bmRvcnM7IHNvbHV0aW9ucyB0aGF0IHNvbHZlIHByb2JsZW1zIGVmZmljaWVudGx5IHdpbGwgZ2V0
IGRlcGxveWVkLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OkNhbGlicmkiPkpvaG4gTGVkZHk8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7
cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFuPg0K
PC9iPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpO2NvbG9yOmJsYWNrIj5pZXRmICZs
dDtpZXRmLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiAmcXVvdDtFcmljIFZ5bmNr
ZSAoZXZ5bmNrZSkmcXVvdDsgJmx0O2V2eW5ja2VAY2lzY28uY29tJmd0Ozxicj4NCjxiPkRhdGU6
IDwvYj5TdW5kYXksIEZlYnJ1YXJ5IDEyLCAyMDE3IGF0IDM6NTYgUE08YnI+DQo8Yj5UbzogPC9i
PlN1cmVzaCBLcmlzaG5hbiAmbHQ7c3VyZXNoLmtyaXNobmFuQGdtYWlsLmNvbSZndDssIDwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TVMgTWluY2hvJnF1b3Q7O2NvbG9yOmJs
YWNrIj7npZ7mmI7pgZTlk4k8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmk7
Y29sb3I6YmxhY2siPiAmbHQ7amlubWVpQHdpZGUuYWQuanAmZ3Q7PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTpQTWluZ0xpVTtjb2xvcjpibGFjayI+PGJyPg0KPC9zcGFuPjxiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpO2NvbG9yOmJsYWNrIj5DYzogPC9zcGFuPjwvYj48
c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTtjb2xvcjpibGFjayI+JnF1b3Q7Nm1hbkBp
ZXRmLm9yZyZxdW90OyAmbHQ7Nm1hbkBpZXRmLm9yZyZndDssIElFVEYgRGlzY3Vzc2lvbiBsaXN0
ICZsdDtpZXRmQGlldGYub3JnJmd0OywgUGV0ZSBSZXNuaWNrICZsdDtwcmVzbmlja0BxdGkucXVh
bGNvbW0uY29tJmd0OywgJnF1b3Q7ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0
Zi5vcmcmcXVvdDsNCiAmbHQ7ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5v
cmcmZ3Q7LCAmcXVvdDs2bWFuLWNoYWlyc0BpZXRmLm9yZyZxdW90OyAmbHQ7Nm1hbi1jaGFpcnNA
aWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBMYXN0IENhbGw6ICZsdDtkcmFm
dC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQmZ3Q7IChJbnRlcm5ldCBQcm90b2NvbCwgVmVy
c2lvbiA2IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJbnRlcm5ldCBTdGFuZGFyZDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTpDYWxpYnJpIj5TdXJlc2gsIEppbm1laSBh
bmQgRmVybmFuZG8sPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+SSBmdWxseSBhZ3JlZSB3aXRo
IHlvdSBTdXJlc2gsIHRoZSBnb2FsIG9mIGFuIElFVEYgbGFzdCBjYWxsIGlzIHRvIGdldCBORVcg
ZGlzY3Vzc2lvbiBhbmQgdG8gcmUtZG8gdGhlIGxlbmd0aHkgZGlzY3Vzc2lvbnMgd2UgaGFkIG9u
IDZNQU4gV0cuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+Jm5ic3A7PC9z
cGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+LcOpcmljPC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6Q2FsaWJyaSI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNCNUM0REYgNC41
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA0LjBwdDttYXJnaW4tbGVmdDozLjc1cHQ7bWFyZ2luLXRv
cDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdiBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4w
cHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OkNhbGlicmk7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj4NCjwvYj48c3BhbiBz
dHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaTtjb2xvcjpibGFjayI+aXB2NiAmbHQ7aXB2Ni1ib3Vu
Y2VzQGlldGYub3JnJmd0OyBvbiBiZWhhbGYgb2YgU3VyZXNoIEtyaXNobmFuICZsdDtzdXJlc2gu
a3Jpc2huYW5AZ21haWwuY29tJmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5TYXR1cmRheSAxMSBGZWJy
dWFyeSAyMDE3IGF0IDA3OjExPGJyPg0KPGI+VG86IDwvYj48L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O01TIE1pbmNobyZxdW90Oztjb2xvcjpibGFjayI+56We5piO6YGU5ZOJ
PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTpDYWxpYnJpO2NvbG9yOmJsYWNrIj4gJmx0
O2ppbm1laUB3aWRlLmFkLmpwJmd0Ozwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6UE1p
bmdMaVU7Y29sb3I6YmxhY2siPjxicj4NCjwvc3Bhbj48Yj48c3BhbiBzdHlsZT0iZm9udC1mYW1p
bHk6Q2FsaWJyaTtjb2xvcjpibGFjayI+Q2M6IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OkNhbGlicmk7Y29sb3I6YmxhY2siPiZxdW90OzZtYW5AaWV0Zi5vcmcmcXVvdDsgJmx0
OzZtYW5AaWV0Zi5vcmcmZ3Q7LCBJRVRGIERpc2N1c3Npb24gbGlzdCAmbHQ7aWV0ZkBpZXRmLm9y
ZyZndDssIFBldGUgUmVzbmljayAmbHQ7cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbSZndDssIEZl
cm5hbmRvIEdvbnQgJmx0O2Znb250QHNpNm5ldHdvcmtzLmNvbSZndDssDQogJnF1b3Q7ZHJhZnQt
aWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmcmcXVvdDsgJmx0O2RyYWZ0LWlldGYt
Nm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYub3JnJmd0OywgJnF1b3Q7Nm1hbi1jaGFpcnNAaWV0
Zi5vcmcmcXVvdDsgJmx0OzZtYW4tY2hhaXJzQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6
IDwvYj5SZTogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXMtMDgudHh0
Jmd0OyAoSW50ZXJuZXQgUHJvdG9jb2wsIFZlcnNpb24gNiAoSVB2NikgU3BlY2lmaWNhdGlvbikg
dG8gSW50ZXJuZXQgU3RhbmRhcmQ8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBKaW5tZWksJm5ic3A7PG86cD48L286
cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gRmViIDEwLCAyMDE3IDE6MjMgUE0sICZx
dW90OzxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNUyBNaW5jaG8mcXVvdDsiPuelnuaY
jumBlOWTiTwvc3Bhbj4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpqaW5tZWlAd2lkZS5hZC5q
cCI+amlubWVpQHdpZGUuYWQuanA8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxibG9j
a3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0
O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1
LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+QXQgVGh1LCA5IEZlYiAyMDE3IDE4OjMwOjExIC0wMzAwLDxicj4NCkZlcm5hbmRv
IEdvbnQgJmx0OzxhIGhyZWY9Im1haWx0bzpmZ29udEBzaTZuZXR3b3Jrcy5jb20iPmZnb250QHNp
Nm5ldHdvcmtzLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCjxicj4NCldoaWxlIEkgbGFyZ2VseSBh
Z3JlZSB3aXRoIEZlcm5hbmRvIG9uIGV2ZXJ5dGhpbmcgaGUgc2FpZCwgSSBoYXZlIHRvPGJyPg0K
YWRtaXQgbW9zdCBvZiB0aGUgcG9pbnRzIGFyZSBqdXN0IHJlcGVhdGVkIGZyb20gdGhlIDZtYW4g
ZGlzY3Vzc2lvbiw8YnI+DQphbmQgd29uJ3QgZ2V0IHVzIGFueXdoZXJlIG5ldyBieSBkaXNjdXNz
aW5nIHRoZXNlIGFnYWluIGF0IHRoaXMgcG9pbnQuPGJyPg0KSSBndWVzcyB0aGUgb25seSBuZXcg
aW5wdXQgZm9yIHRoZSBJRVRGIGxhc3QgY2FsbCBpcyB0aGlzOjxvOnA+PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJy
Pg0KJmd0OyAyKSBIb3dldmVyLCBzb21lIGZvbGtzIGNhbWUgdXAgd2l0aCBwcm9wb3NhbHMgdG8g
aW5zZXJ0IEVILCBvbiB0aGUgYmFzaXM8YnI+DQomZ3Q7IHRoYXQgJnF1b3Q7UkZDMjQ2MCBkb2Vz
IG5vdCBleHBsaWNpdGx5IGJhbiBFSCBpbnNlcnRpb24mcXVvdDsuIElmIHRoZXJlJ3MgcGVvcGxl
PGJyPg0KJmd0OyBhcmd1aW5nIHRoYXQsIHdlIGNsZWFybHkgbmVlZCB0byBtYWtlIHRoaXMgY2xl
YXIgaW4gdGhlIHNwZWMuPGJyPg0KJmd0Ozxicj4NCiZndDsgMykgVGhlcmUgd2FzIGEgY29uc2Vu
c3VzIGNhbGwsIHllcy4gV2hlbiB0aGUgY2FsbCB3YXMgbWFkZSBvbiB0aGU8YnI+DQomZ3Q7IG1h
aWxpbmctbGlzdCwgdGhlIHZhc3QgbWFqb3JpdHkgb2Ygc3VwcG9ydGVycyBvZiAmcXVvdDtsZXQn
cyBrZWVwIHRoZTxicj4NCiZndDsgYW1iaWd1aXR5JnF1b3Q7IHdlcmUgZm9sa3MgZnJvbSB0aGUg
c2FtZSBjb21wYW55IGFzICZxdW90OzIpJnF1b3Q7LiBJIGhhdmUgbm8gaWRlYSBpZjxicj4NCiZn
dDsgdGhpcyBjaGFuZ2VzIChvciBub3QpICZxdW90O2NvbnNlbnN1cyZxdW90Oy4uLiBidXQgdGhp
cyBpcyBjbGVhcmx5IGFuIGltcG9ydGFudDxicj4NCiZndDsgZGF0YXBvaW50LjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbHRob3VnaCBJIGRvbid0IHdhbnQg
dG8gcG9pbnQgYSBmaW5nZXIgYXQgcGFydGljdWxhciBwZW9wbGUgb3I8YnI+DQpvcmdhbml6YXRp
b25zIHdpdGhvdXQgYW4gZXZpZGVuY2UsIEkgZ3Vlc3Mgbm90IGEgc21hbGwgbnVtYmVyIG9mIDZt
YW48YnI+DQpwYXJ0aWNpcGFudHMgKG5vdCBvbmx5IHRob3NlIHdobyBleHBsaWNpdGx5IHNwb2tl
IHVwIGhlcmUpIHN1c3BlY3RlZDxicj4NCnRoYXQgdGhlIGRlY2lzaW9uIHByb2Nlc3Mgd2FzIGJp
YXNlZCB3aXRoIHRoZSBpbmZsdWVuY2Ugb2YgYSBsYXJnZSBhbmQ8YnI+DQpwb3dlcmZ1bCBvcmdh
bml6YXRpb24gYW5kIHRoZSBwcm9jZXNzIGFuZCByZXN1bHRpbmcgJnF1b3Q7Y29uc2Vuc3VzJnF1
b3Q7IHdhczxicj4NCm5vdCByZWFsbHkgYSBmYWlyIG9uZS4mbmJzcDsgQW5kIEknbSBub3QgYW4g
ZXhjZXB0aW9uIHRvIGl0IC0gaW4gZmFjdCwgaXQ8YnI+DQp3YXMgc28gdW5iZWxpZXZhYmxlIHRv
IG1lIHRoYXQgd2UgY2FuJ3QgY2xhcmlmeSBhbiBhbWJpZ3VpdHkgZXZlbiB3aGVuPGJyPg0Kd2Ug
d2VyZSBhbHNvIG9wZW4gZm9yIGZ1dHVyZSBleHRlbnNpb25zLCB0aGF0IEkgY291bGRuJ3QgdGhp
bmsgb2Y8YnI+DQpvdGhlciByZWFzb25zIHRoYW4gYSBjb21wYW55IGFnZW5kYS48YnI+DQo8YnI+
DQpPZiBjb3Vyc2UsIGl0J3MgcXVpdGUgcG9zc2libGUgdGhhdCBpdCB3YXMganVzdCBhIGNvaW5j
aWRlbmNlIHRoYXQ8YnI+DQptYW55IHBlb3BsZSB3aXRoIHRoZSBzYW1lIG9yZ2FuaXphdGlvbiBn
ZW51aW5lbHkgdGhvdWdodCB3ZSBzaG91bGQ8YnI+DQpsZWF2ZSBpdCBhbWJpZ3VvdXMgd2hpbGUg
bWFueSBvdGhlcnMgc3Ryb25nbHkgdGhvdWdodCB3ZSBzaG91bGQ8YnI+DQpjbGFyaWZ5IGl0IGJ1
dCBmZXcgKGlmIG5vdCBubykgcGVvcGxlIGZyb20gdGhhdCBvcmdhbml6YXRpb24gc3VwcG9ydGVk
PGJyPg0KdGhlIGNsYXJpZmljYXRpb24uJm5ic3A7IEJ1dCBJIGRvbid0IHRoaW5rIHdlIGNhbiBw
cm92ZSBpdCBlaXRoZXIgd2F5Ljxicj4NCjxicj4NCkJ1dCBhcyBGZXJuYW5kbyBzYWlkLCBJIGJl
bGlldmUgdGhpcyBwb2ludCAoYW5kIHRoYXQgc2V2ZXJhbCwgYW5kPGJyPg0KYXJndWFibHkgbW9y
ZSwgcGFydGljaXBhbnRzIHN1c3BlY3RlZCBpdCkgc2hvdWxkIGJlIGluY2x1ZGVkIGluIG1ha2lu
Zzxicj4NCnRoZSBkZWNpc2lvbiBhdCB0aGUgSUVTRyBhbmQgYXQgdGhlIElFVEYgbGFzdCBjYWxs
LiZuYnNwOyBBbmQsIHdoYXRldmVyIHRoZTxicj4NCmRlY2lzaW9uLCBpdCB3b3VsZCBiZSBtb3Jl
IHByb2R1Y3RpdmUgdG8gbW92ZSBvbiBhZnRlciB0aGF0IGFuZCB1c2U8YnI+DQpvdXIgdGltZSBm
b3Igc29tZSBvdGhlciB0aGluZ3MuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFtIGd1
ZXNzaW5nIHRoYXQgdGhlIHBlb3BsZSB3aG8gc3Bva2UgdXAgZHVyaW5nIHRoZSBXRyBwcm9jZXNz
IHRvIG5vdCBwdXQgaW4gYW4gb3V0cmlnaHQgcHJvaGliaXRpb24gd291bGQgbWFrZSB0aGVpciBj
YXNlIGFsb25nIHdpdGggdGhlaXIgYXJndW1lbnRzIGhlcmUgYXMgd2VsbC4gV2UgYXJlIG9ubHkg
YSB3ZWVrIGludG8gYSBmb3VyIHdlZWsgbG9uZyBsYXN0IGNhbGwuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3VyZXNoPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_A823FD1C4ED8478881F00F672F1FA364cablecomcastcom_--


From nobody Sun Feb 12 16:40:15 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58183127058; Sun, 12 Feb 2017 16:40:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyMBW16AyXyB; Sun, 12 Feb 2017 16:40:12 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 28BF41294E1; Sun, 12 Feb 2017 16:40:12 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id o64so5281073pfb.1; Sun, 12 Feb 2017 16:40:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=hApkLpY3/DPAaZGAiEKt2nmkpVh72MkkfVJ52b1bUjw=; b=ppVkN2f4zsTJf1Do91cARSAWxmkTICS+sixyyUAN1hnwB4LnJlcm2Gfryz6y40DY0H tIifM81LYweJaRibtSR8bhAkV7IOg162uovfrMuseMIepFG0qENQSIhLfJkep2z+5qe9 l6HzJm5eGRlu/w6dB9H8FOUxfbDpa+pQPst/evoyT00y/QKcWh6nS5UZmfFTjvJ0kcQ4 Fr88nCILpnE+OP+cCKcta5KWxYI8B/o7oXvNj1bAUObXldtIgLCKkF5DHOZ4DhouExxG pB2R9zb81q5sdBEIFHrbR+GHx7wqHjToaeP5ADgg61psCU4hHyDKVFnO1/AfHP0EQft6 /Xhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=hApkLpY3/DPAaZGAiEKt2nmkpVh72MkkfVJ52b1bUjw=; b=qn7HKfF2YREkoQJEO8m4vq3CBFqsJB2waWwZhvRWOZv5B/xwPV3VvnUkCSUS4LaDEm zd2r0C3PoLySv+PSZ9z7NpXEafsmrzjvp72pkQogYtlrFEi7lyCVeUCuNJOzZck6JZYq 5HSMaWstUpulR05pJgIDgCMhVP1/OtTDSpvqd6uLPSF6k36iZ7+BLV5Puqi5WgJWUL5Y RprTb6j/UKe+cY4Wy/AwF1THDu80/a0USiKHbHqVfS7LBqQsx2Bxfm6H1AioXnZ7x2sh YWtj8NWuE5GfFzZs3TApSlfMZNWlGW9m4vy/irjRMlEmd0yh69mXJR6Y6Q289O8vYeYQ auTA==
X-Gm-Message-State: AMke39nagcROjcKsnhQiL4+E9pQeSTo/0K3e0ZdJlX2y/+DnZLN/In5ttWmxMvUJQY+h0w==
X-Received: by 10.99.105.66 with SMTP id e63mr23812563pgc.104.1486946411640; Sun, 12 Feb 2017 16:40:11 -0800 (PST)
Received: from ?IPv6:2406:e007:6e60:1:28cc:dc4c:9703:6781? ([2406:e007:6e60:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id b83sm16903658pfe.12.2017.02.12.16.40.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Feb 2017 16:40:10 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: "Leddy, John" <John_Leddy@comcast.com>, "Eric Vyncke (evyncke)" <evyncke@cisco.com>, Suresh Krishnan <suresh.krishnan@gmail.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com> <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com> <A823FD1C-4ED8-4788-81F0-0F672F1FA364@cable.comcast.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <cd1ef13e-7d3c-0dbf-a4d9-61442f663d3e@gmail.com>
Date: Mon, 13 Feb 2017 13:40:04 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <A823FD1C-4ED8-4788-81F0-0F672F1FA364@cable.comcast.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E4LgECz4IAxLS5txPVUIGLUO8uA>
Cc: "6man@ietf.org" <6man@ietf.org>, Pete Resnick <presnick@qti.qualcomm.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 00:40:14 -0000

John,

On 13/02/2017 12:05, Leddy, John wrote:
> I=E2=80=99m trying to understand how a ban of this functionality would =
work.  Is it targeted at vendor products, precluding them from implementi=
ng the functionality?

It's targetted at interoperability across the Internet. We can never stop=

people doing whatever they please inside a private domain, obviously.
As always, there are no protocol police.

> If there is a technical problem that can be solved by using EH insertio=
n within a domain where there are no harmful side effects, it should be a=
ble to be used.
> In a software networking world where functionality is being deployed th=
at is not from traditional network vendors; solutions that solve problems=
 efficiently will get deployed.

We had a lot of this conversation in a slightly different form prior to
RFC 6437. It proved impossible to specify "local domain" rules that could=

reach consensus. I think we'd have the same problem trying to write rules=

for header insertion/deletion within a domain. But in any case, that isn'=
t
the target for RFC2460bis: the target is the Internet.

    Brian

>=20
> John Leddy
>=20
> From: ietf <ietf-bounces@ietf.org> on behalf of "Eric Vyncke (evyncke)"=
 <evyncke@cisco.com>
> Date: Sunday, February 12, 2017 at 3:56 PM
> To: Suresh Krishnan <suresh.krishnan@gmail.com>, =E7=A5=9E=E6=98=8E=E9=81=
=94=E5=93=89 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.or=
g>, Pete Resnick <presnick@qti.qualcomm.com>, "draft-ietf-6man-rfc2460bis=
@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chair=
s@ietf.org" <6man-chairs@ietf.org>
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet P=
rotocol, Version 6 (IPv6) Specification) to Internet Standard
>=20
> Suresh, Jinmei and Fernando,
>=20
> I fully agree with you Suresh, the goal of an IETF last call is to get =
NEW discussion and to re-do the lengthy discussions we had on 6MAN WG.
>=20
> -=C3=A9ric
>=20
> From: ipv6 <ipv6-bounces@ietf.org> on behalf of Suresh Krishnan <suresh=
=2Ekrishnan@gmail.com>
> Date: Saturday 11 February 2017 at 07:11
> To: =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.or=
g>, Pete Resnick <presnick@qti.qualcomm.com>, Fernando Gont <fgont@si6net=
works.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-=
rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>=

> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet P=
rotocol, Version 6 (IPv6) Specification) to Internet Standard
>=20
> Hi Jinmei,
>=20
> On Feb 10, 2017 1:23 PM, "=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89" <jinmei=
@wide.ad.jp<mailto:jinmei@wide.ad.jp>> wrote:
> At Thu, 9 Feb 2017 18:30:11 -0300,
> Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>> wro=
te:
>=20
> While I largely agree with Fernando on everything he said, I have to
> admit most of the points are just repeated from the 6man discussion,
> and won't get us anywhere new by discussing these again at this point.
> I guess the only new input for the IETF last call is this:
>=20
>> 2) However, some folks came up with proposals to insert EH, on the bas=
is
>> that "RFC2460 does not explicitly ban EH insertion". If there's people=

>> arguing that, we clearly need to make this clear in the spec.
>>
>> 3) There was a consensus call, yes. When the call was made on the
>> mailing-list, the vast majority of supporters of "let's keep the
>> ambiguity" were folks from the same company as "2)". I have no idea if=

>> this changes (or not) "consensus"... but this is clearly an important
>> datapoint.
> Although I don't want to point a finger at particular people or
> organizations without an evidence, I guess not a small number of 6man
> participants (not only those who explicitly spoke up here) suspected
> that the decision process was biased with the influence of a large and
> powerful organization and the process and resulting "consensus" was
> not really a fair one.  And I'm not an exception to it - in fact, it
> was so unbelievable to me that we can't clarify an ambiguity even when
> we were also open for future extensions, that I couldn't think of
> other reasons than a company agenda.
>=20
> Of course, it's quite possible that it was just a coincidence that
> many people with the same organization genuinely thought we should
> leave it ambiguous while many others strongly thought we should
> clarify it but few (if not no) people from that organization supported
> the clarification.  But I don't think we can prove it either way.
>=20
> But as Fernando said, I believe this point (and that several, and
> arguably more, participants suspected it) should be included in making
> the decision at the IESG and at the IETF last call.  And, whatever the
> decision, it would be more productive to move on after that and use
> our time for some other things.
>=20
> I am guessing that the people who spoke up during the WG process to not=
 put in an outright prohibition would make their case along with their ar=
guments here as well. We are only a week into a four week long last call.=

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


From nobody Sun Feb 12 16:52:49 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48401129521; Sun, 12 Feb 2017 16:52:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level: 
X-Spam-Status: No, score=-14.521 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36iWBtMFHc88; Sun, 12 Feb 2017 16:52:45 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D46021294E9; Sun, 12 Feb 2017 16:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10991; q=dns/txt; s=iport; t=1486947164; x=1488156764; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=BYQ9fDmK7GmTXhib7cVNaX+eYAAwaYK3/ly0Rpk4VuM=; b=MIqphDEtN6X+wfYrJoBXZYXUcT4kg6+rilfy9Biugc4qDSHksxeOiwXc AyJFS/cznrn5nkd9a9S2X4olZTr9m3gJqWzE9oHoE0eOnc+6hfXcHgrFl r/OAMLIeEOPxdbaB+5ciSzKIRnAduJcdO8ol5GLiGYf+VxurkfvKLxyA8 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AaAQBZAqFY/4gNJK1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm9jgWoHjVqSCpAKhSyCDIYiAoJ7PxgBAgEBAQEBAQFiKIRpAQE?= =?us-ascii?q?BAwFuCwULAgEIDgMDAQIoBzIUCQgCBAENBYlSAw0IsQcrixYBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEdhkyEb4JRgVURATwWhS8FkAOFUYYeAZITgXuFF4lzkxQBHzh?= =?us-ascii?q?4CFEVPYRFHYFhdYgSgSGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,155,1484006400";  d="scan'208,217";a="383183107"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 13 Feb 2017 00:52:43 +0000
Received: from XCH-RCD-009.cisco.com (xch-rcd-009.cisco.com [173.37.102.19]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1D0qh1E004281 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 13 Feb 2017 00:52:43 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-009.cisco.com (173.37.102.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 12 Feb 2017 18:52:42 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Sun, 12 Feb 2017 18:52:42 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: Charlie Perkins <charles.perkins@earthlink.net>, Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHShZN7GUjlGCaTJE+d8OzNd5SzNQ==
Date: Mon, 13 Feb 2017 00:52:42 +0000
Message-ID: <D4C63E24.2598D8%sgundave@cisco.com>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com> <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
In-Reply-To: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: multipart/alternative; boundary="_000_D4C63E242598D8sgundaveciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cKxjEpjlk9sZpdJp706MazsWk8k>
Cc: "dmm@ietf.org" <dmm@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 00:52:47 -0000

--_000_D4C63E242598D8sgundaveciscocom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Charlie,

Please see inline.


From: dmm <dmm-bounces@ietf.org<mailto:dmm-bounces@ietf.org>> on behalf of =
Charlie Perkins <charles.perkins@earthlink.net<mailto:charles.perkins@earth=
link.net>>
Date: Friday, February 10, 2017 at 2:28 PM
To: Dale Worley <worley@ariadne.com<mailto:worley@ariadne.com>>, "gen-art@i=
etf.org<mailto:gen-art@ietf.org>" <gen-art@ietf.org<mailto:gen-art@ietf.org=
>>
Cc: "draft-ietf-dmm-4283mnids.all@ietf.org<mailto:draft-ietf-dmm-4283mnids.=
all@ietf.org>" <draft-ietf-dmm-4283mnids.all@ietf.org<mailto:draft-ietf-dmm=
-4283mnids.all@ietf.org>>, "ietf@ietf.org<mailto:ietf@ietf.org>" <ietf@ietf=
.org<mailto:ietf@ietf.org>>, "dmm@ietf.org<mailto:dmm@ietf.org>" <dmm@ietf.=
org<mailto:dmm@ietf.org>>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04


4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.

> Here I am at a loss, because I was specifically requested to insert some =
descriptive but not normative text.  I will ask the person who made the req=
uest to provide their feedback on the mailing list.  For myself, I am more =
than happy to delete the text.

When we discussed this issue in the past, the general feedback from the WG =
was that the draft should provide some minimal amount of details on the new=
 identifier types, what the identifier is, how the identifier is constructe=
d, what is the access technology and a reference to the specification that =
provides that definition. The idea is NOT TO provide extensive details on t=
he spec, but to enable a reader with some high level details and a pointer =
to the specification. I tend to think the text in the current specification=
 just does that. If the text is seen as redundant text, we can certainly ad=
d a statement saying that the definition for the identifier is provided in =
spec-XYZ and is repeated here for convenience. May be other folks in the WG=
 have some views on this.


Comments from 10/11/2015 email:

"Some text on the motivation for defining new Types may be helpful. Documen=
t is not just standardizing the currently in-use/popular identifier types, =
its also introducing new types are not in use. The reasons/interest for def=
ining identifiers that are tied to the physical elements of the device (RFI=
D, MAC address ..etc) and how it helps in deployment of the technology may =
be useful. Few lines of text will really help."

"I was hoping to see a sub-section for each of the types. We cannot standar=
dize a identifier type without providing any explanation on the identifier =
type or the references to the base definitions. This can be painful, but I'=
d have a small section for each of the types. It can be 3 line text on the =
a.) Definition b.) Format c.) Example format d.) Reference to the base spec=
 that defines those identifiers."



--_000_D4C63E242598D8sgundaveciscocom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <F2960967A78F294BB9C9AEF31440D9F7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Hi Charlie,</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Please see inline.</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION" style=3D"font-family: Calibri, sans-serif=
; font-size: 14px; color: rgb(0, 0, 0);">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>dmm &lt;<a href=3D"mailto:dmm=
-bounces@ietf.org">dmm-bounces@ietf.org</a>&gt; on behalf of Charlie Perkin=
s &lt;<a href=3D"mailto:charles.perkins@earthlink.net">charles.perkins@eart=
hlink.net</a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Friday, February 10, 2017 at =
2:28 PM<br>
<span style=3D"font-weight:bold">To: </span>Dale Worley &lt;<a href=3D"mail=
to:worley@ariadne.com">worley@ariadne.com</a>&gt;, &quot;<a href=3D"mailto:=
gen-art@ietf.org">gen-art@ietf.org</a>&quot; &lt;<a href=3D"mailto:gen-art@=
ietf.org">gen-art@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:draft-i=
etf-dmm-4283mnids.all@ietf.org">draft-ietf-dmm-4283mnids.all@ietf.org</a>&q=
uot; &lt;<a href=3D"mailto:draft-ietf-dmm-4283mnids.all@ietf.org">draft-iet=
f-dmm-4283mnids.all@ietf.org</a>&gt;, &quot;<a href=3D"mailto:ietf@ietf.org=
">ietf@ietf.org</a>&quot;
 &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, &quot;<a href=
=3D"mailto:dmm@ietf.org">dmm@ietf.org</a>&quot; &lt;<a href=3D"mailto:dmm@i=
etf.org">dmm@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>Re: [DMM] Review of draft-=
ietf-dmm-4283mnids-04<br>
</div>
<div><br>
</div>
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<blockquote cite=3D"mid:148589124578.6067.10086408452323670298.idtracker@ie=
tfa.amsl.com" type=3D"cite">
<pre wrap=3D"">4.9.  Description of the RFID types

This section needs to be revised.  It provides a lot of detail about
the RFID types, but it's not enough detail for a reader who doesn't
understand RFID to learn how any particular RFID scheme works.  E.g.,
the first paragraph says that GID contains three fields in the first
sentence, and that it contains four fields in the third sentence.
Despite this, the description isn't enough to allow the reader to
construct GID identifiers manually.

On the other hand, readers who already understand the RFID schemes
will find this text redundant.

I think that almost all of this text can be replaced by references to
the EPC documents, since these identifiers are opaque from the point
of view of mobile identification.</pre>
</blockquote>
<br>
&gt; Here I am at a loss, because I was specifically requested to insert so=
me descriptive but not normative text.&nbsp; I will ask the person who made=
 the request to provide their feedback on the mailing list.&nbsp; For mysel=
f, I am more than happy to delete the text.<br>
<br>
When we discussed this issue in the past, the general feedback from the WG =
was that the draft should provide some minimal amount of details on the new=
 identifier types, what the identifier is, how the identifier is constructe=
d, what is the access technology
 and a reference to the specification that provides that definition. The id=
ea is NOT TO provide extensive details on the spec, but to enable a reader =
with some high level details and a pointer to the specification. I tend to =
think the text in the current specification
 just does that. If the text is seen as redundant text, we can certainly ad=
d a statement saying that the definition for the identifier is provided in =
spec-XYZ and is repeated here for convenience. May be other folks in the WG=
 have some views on this.</div>
</div>
</span>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
<br>
</div>
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px; color: rgb=
(0, 0, 0);">
Comments from 10/11/2015 email:</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div>
<pre style=3D"word-wrap: break-word;"><pre style=3D"word-wrap: break-word;"=
><pre style=3D"word-wrap: break-word;"><pre style=3D"word-wrap: break-word;=
"><font color=3D"#ff0000" style=3D"font-family: Calibri, sans-serif; font-s=
ize: 14px;"><b><font face=3D"Calibri,sans-serif"><span style=3D"white-space=
: pre-wrap;">&quot;Some text on the motivation for defining new Types may b=
e helpful. Document is not just </span></font><span style=3D"white-space: p=
re-wrap;">standardizing the currently in-use/popular identifier types, its =
also introducing new types are not in use. The reasons/interest for definin=
g identifiers that are tied to the physical elements of the device (RFID, M=
AC address ..etc) and how it helps in deployment of the technology may be u=
seful. Few lines of text will really help.</span></b></font><font color=3D"=
#ff0000"><span style=3D"font-size: 14px; white-space: pre-wrap;"><b>&#8221;=
</b></span></font></pre></pre></pre></pre>
</div>
</span>
<div>&quot;<b style=3D"font-family: Calibri, sans-serif; font-size: 14px; c=
olor: rgb(255, 0, 0);"><span style=3D"white-space: pre-wrap;">I</span><span=
 style=3D"white-space: pre-wrap;"> was hoping to see a sub-section for each=
 of the types. We cannot standardize a identifier
 type without providing any explanation on the identifier type or the refer=
ences to the base definitions. This can be painful, but I'd have a small se=
ction for each of the types. It can be 3 line text on the a.) Definition b.=
) Format c.) Example format d.)
 Reference to the base spec that defines those identifiers.</span></b><font=
 color=3D"#ff0000" face=3D"Calibri,sans-serif"><span style=3D"white-space: =
pre-wrap;"><b>&#8221;</b></span></font></div>
<div><font color=3D"#ff0000" face=3D"Calibri,sans-serif"><span style=3D"whi=
te-space: pre-wrap;"><b><br>
</b></span></font></div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family: Calibri, sans-serif; font-size: 14px;"><b style=
=3D"color: rgb(255, 0, 0);"><span style=3D"white-space: pre-wrap;"><br>
</span></b></div>
</span>
</body>
</html>

--_000_D4C63E242598D8sgundaveciscocom_--


From nobody Sun Feb 12 19:13:24 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18A5B1295D8 for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2017 19:13:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 LgvAmn03cQ5N for <ietf@ietfa.amsl.com>; Sun, 12 Feb 2017 19:13:21 -0800 (PST)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (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 558651295CA for <ietf@ietf.org>; Sun, 12 Feb 2017 19:13:21 -0800 (PST)
Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-06v.sys.comcast.net with SMTP id d73fcOwYMLSLVd74qcRrK4; Mon, 13 Feb 2017 03:13:20 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-03v.sys.comcast.net with SMTP id d74ncX3wGAjV2d74ocTEdC; Mon, 13 Feb 2017 03:13:19 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1D3DHXd028897; Sun, 12 Feb 2017 22:13:17 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1D3DG6o028894; Sun, 12 Feb 2017 22:13:16 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Charlie Perkins <charles.perkins@earthlink.net>
Subject: Re: Review of draft-ietf-dmm-4283mnids-04
In-Reply-To: <400befde-9457-74b0-274f-87c739d2af86@earthlink.net> (charles.perkins@earthlink.net)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 12 Feb 2017 22:13:16 -0500
Message-ID: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfBTClhHcg8kU70LEEhc9rVMAWPpsRcs1E/x+FAUazwjqoreRWMCkvgfT1wS+L9lve2zQsI6Ba4OQbdCytoLFFiwUPVsxYh/J1gMb28E/aqkTcsac86s0 vqmK/MMN4by2jBEoAejfVmfw/PApFXPVe/ThpB+2Kh0xFNZ+LoaTMSs96oPn/W/hB2UPknUDXn+PU8A/0nmXA+avnTSNoHvc1ABuVt3PDacUQgNPyvVx/SWv 9GM3V3S3gdkGDN5/AHBUFaReexK/KlD9SYFdKrTwC0ftNJ74axLNkNTZ0tdFZMqt
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oC4DrBU8pSn9BSDpvcj4coTw3F8>
Cc: draft-ietf-dmm-4283mnids.all@ietf.org, gen-art@ietf.org, ietf@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 03:13:23 -0000

Charlie Perkins <charles.perkins@earthlink.net> writes:
> > Are there any other types "in common use"?
> 
> I will add some text according to your suggestion.  My criterion for 
> whether the identifier type was included in the document was whether or 
> not anyone had asked for it to be included.

A good criterion -- if it's commonly used, likely someone would have
asked.

> > - NAI (type 1) is defined by 4283.
> > - Fully Qualified Domain Name (FQDN) seems not to be specified
> > - International Mobile Station Identifier (IMSI) (type 3) is defined
> >   in this draft
> > - Mobile Subscriber Number (MSISDN) seems not to be specified
> 
> It is not the jurisdiction of the MNIDs document to specify these 
> identifiers, but citations for the specifications are located elsewhere 
> in the document.  I will also include those citations here.

What I was noting was that 4283 says:

   Mobile IPv6
   nodes need the capability to identify themselves using an identity
   other than the default home IP address.  Some examples of identifiers
   include Network Access Identifier (NAI), Fully Qualified Domain Name
   (FQDN), International Mobile Station Identifier (IMSI), and Mobile
   Subscriber Number (MSISDN).

but that taking 4283 and this document together, there is no way to
specify FQDN or MSISDN as MN identifiers.  If in practice, people don't
use either of those, then the situation is OK, though 4283 is
inaccurate.  But if people do use FQDNs or MSISDNs as MN identifiers,
should those be added to this document?  (I can't find them specified
elsewhere.)

> > 2. Is it intended to have an IMEI identifier type?  The introduction
> > mentions an IMEI type, but there is no specification for it, nor is
> > there an identifier type number assigned for it.

> I don't know why this happened, but I am happy to include an identifier 
> type for IMEI as well as a citation for it.  Thanks for catching this 
> and looking through the archives!

I'm not saying, "Add it because I think it's a good idea to use IMEIs.",
I'm saying, "Your introduction says that you define an MNID type for
IMEIs, but you don't."  Perhaps there is no need for IMEIs, but in that
case, the introduction needs to be edited.

> > 3. The definition of identifier types for both EUI-48 and EUI-64
> > suggests that it might be desirable to define an identifier type for
> > arbitrary hardware (link-level) addresses.  It seems that the natural
> > differentiator for that purpose is the "hardware type" used in ARP,
> > so
> > a EUI-48 address would be represented as

> Actually, I am O.K. either way on this matter.  However, at this point 
> in time it does not seem that we are likely to see any other link 
> hardware address types to be used as MNIDs.

I agree with you there, although I wouldn't be entirely surprised if a
new mobile network introduced a new link-layer address.  But there
doesn't seem to be much value in making the change I suggested, other
than for generality.

> There is a sort of "hidden" disadvantage to long names, especially for 
> tiny devices using constrained link layers.  Namely, a longer name makes 
> it more likely to require lower-layer fragmentation.  I'm not sure that 
> it should be the job of a layer-3 mobility entity to parse URNs and 
> determine if two different flavors are supposed to be equivalent.
> 
> Other than that, I don't have any real objection to reorganizing the 
> namespace, but I'd like some additional confirmation that it's a good idea.

There are a couple of reasons I like this idea.

One is that EPC seems to have a policy of providing a URN form for all
of the identifier classes it defines.  Making a single URN MNID type
means that you've incorporated all future classes of identifier that EPC
defines.

A single URN MNID type would incorporate any of the defined URN
namespaces that turn out to be useful for anybody.  This isn't so
interesting for really large deployments, since they could ask for a new
MNID type, but experimental or small-scale deployments may want to
define their own identifiers, and URNs provide several convenient ways
to do that.

It removes a certain amount of redundancy, in that each RFID class now
has three representations, for a total of 20 MNID types, whereas they
could all be collapsed into one MNID type.

The negatives I see are:

Some URN schemes do not have a unique representation as a character
string.  In practice, this is combated by either (1) Code that handles
URNs of arbitrary namespace copies and compares them as character
strings.  Users of such systems know to write URNs that have multiple
representations in a canonical form.  Or, (2) Code that handles one or a
small fixed set of URN namespaces knows the canonicalization/comparison
rules for those namespaces.  Generally, using these processes doesn't
cause problems in practice.  I expect that whatever receives the MNID
and looks it up in appropriate databases would not be a constrained
device, so it could process URNs carefully.

If the link layer is constrained, longer identifiers may require
fragmentation.  Changing a 96-bit binary representation into a URN seems
to add something like 40 octets, given the examples I've found online.
OTOH, it seems that the MNID is only transmitted when attaching to a
network, and so having that one packet require extra work doesn't seem
to be much of a penalty.

The all-URN ides envisions embedding IMSI and possibly MSISDN into the
gsma URN namespace.  (IMEI is already embedded as urn:gsma:imei:...)
That would take additional specification, although I don't see that
being controversial.  (Andrew Allen <aallen@blackberry.com> would be a
good contact for doing this.)

> > 5. Regarding the encoding of a string of digits into octets, it is
> > stated that "The last digit MUST be zero padded, if needed, for full
> > octet size."  This seems very unwise unless there is a 3GPP decree
> > that if a zero is appended to a valid IMSI, the resulting string is
> > never a valid IMSI.  Instead, I would specify that padding is by
> > filling the low-order 4 bits of the final octet with 0xF.  That
> > ensures that the encoding can be uniquely decoded into an IMSI.
> 
> I am O.K. with this.  I need to go find out where I got that language 
> from, because I don't think I was the person who crafted it.

I suspect this is really an editorial mistake, but I had to treat it as
technical because I couldn't rule out that it was a design question.

> > 6. There are four types of DUID specified, each with a distinct MNID
> > value.  However, DUIDs contain an initial two-octet type field which
> > distinguishes the various types of DUID, so providing them with
> > distinct MNID values is redundant.
> >
> > Distinguishing the types and allowing only four of them to be used as
> > MNIDs seems to be contrary to the philosophy of DUID construction (RFC
> > 3315 section 9):
> >
> >     Clients and servers MUST treat DUIDs as opaque values and MUST only
> >     compare DUIDs for equality.  Clients and servers MUST NOT in any
> >     other way interpret DUIDs.  Clients and servers MUST NOT restrict
> >     DUIDs to the types defined in this document, as additional DUID types
> >     may be defined in the future.
> >
> > Of course, MNID isn't a DHCP operation, so it isn't subject to those
> > requirements, but I expect that devices will use the same DUID for
> > both mobile identification, and we don't want mobile identification to
> > restrict future developments of DHCP.
> >
> > I think this specification must treat DUIDs as opaque and use only
> > one
> > MNID type that allows all types of DUIDs as values.
> 
> Thanks for this observation.  I will make the corresponding revisions to 
> the text.

Give that there has been only 4 types of DUID defined in 13 years, I
don't expect much need for extensibility, but it seems to me that if
devices take their MNID from their platform's DHCP implementation,
there is a risk that the protocol will fail if someone uses a
proprietary/experimental DUID type.

> > Editorial issues:

Trimming everything I have no further comment on:

> > Abstract
> >
> >     Additional Identifier Types are proposed for use with the Mobile
> > Node
> >     Identifier Option for IPv6 (RFC 4283).
> >
> > s/proposed/defined/
> > This document will define the new types (once it is approved)!
> 
> O.K. with your modification.  The document just defines numbers for the 
> types, not the types.

True...  So really "Additional Identifier Type Numbers are defined for
use ..."

> > --
> >
> >     For each RFID scheme except GID, there are two variations: a 64-bit
> >     scheme (for example, SGLN-64) and a 96-bit scheme (SGLN-96).  GID has
> >     only a 96-bit scheme.  Within each scheme, an EPC identifier can be
> >     represented in a binary form or other forms such as URI.
> >
> > The text uses "scheme" to mean the distinction between encoding
> > systems (GID, SGTIN, etc.) and and also to mean the distinction
> > between the 64-bit and 96-bit variations.  This ambiguity is unwise.
> > It matters here, because you say "within each scheme ... can be
> > represented in a binary form or ... URI".  Which meaning of "scheme"
> > are you using here?  I thought you meant the second meaning when I
> > first read the paragraph, but after reading external documents about
> > EPC, I now understand that that last sentence uses "scheme" to in the
> > first sense.
> >
> > You need to be clearer here that there are three representations
> > used,
> > 64-bit binary, 96-bit binary, and URI (URN, actually), and
> > representation is orthogonal to the seven RFID schemes, with the
> > exception that RFID-GID does not have a 96-bit binary representation.
> 
> This is a good idea.  How about the following:
> 
> >    For each RFID scheme except GID, there are three representations:
> >     - a 64-bit binary representation (for example, SGLN-64)
> >     - a 96-bit binary representation (SGLN-96).
> >     - a representation as a URI

That's close, but it doesn't assert the representations for GID.
Better:

    For each RFID there are three representations:
     - a 64-bit binary representation (for example, SGLN-64)
       (except for GID)
     - a 96-bit binary representation (SGLN-96).
     - a representation as a URI (a URN, actually)

(Though all of this discussion can be removed of the binary
representations are removed in favor of the URN representation.)

> I didn't originate the use of URI for the non-binary representation. The 
> EPC document has the following language:
> 
> > All categories of URIs are represented as Uniform Reference Names 
> > (URNs) as defined by [RFC2141], where the URN Namespace is epc.
> 
> If I were to change it to URN, then I would have to go into some detail 
> about why this document somehow disagrees with the EPC-Tag-Data 
> document.  Do you think that is necessary?

We do want to stay aligned with EPC, otherwise there would be chaos.
And technically, all URNs are URIs.  But approaching the subject from
the IETF, it makes a lot more sense that RFID schemes are represented as
URNs rather than general URIs.  It seems to me to be quite sufficient to
notify the reader in some appropriate place that these URIs are URNs.
See the last line of the text I suggested above for one way to do it.

> > I'm assuming that the Tag Data standard unambiguously defines the
> > serialization of the binary representations as a sequence of octets.
> > If it does not, this document MUST do that, or you will have an
> > endless nightmare of byte-order problems.
> 
> I read through some relevant text in the EPC-Tag-Data document and it 
> seems O.K. to me, but nontrivial and it relies on digging through other 
> even more arcane documents to be absolutely sure.  I am pretty sure that 
> the IETF document should not get into the business of augmenting the 
> standards already in place from the external SDOs.

Oh, yes, we don't want to duplicate EPC's work.  I just wanted to know
that you've checked that EPC does define a sequence of octets, rather
than only a sequence of *bits*, which would leave the ordering of the
bits within the octets unspecified.

> > 4.  Descriptions of MNID types
> >
> > Identifier ownership is a general concern -- it's worth mentioning
> > for
> > each type of identifier where the assigner of the identifier obtains
> > delegation.  For an EUI, I expect the reader will assume that it's an
> > EUI assigned to the device under IEEE rules, and similarly for RFID
> > and 3GPP identifiers.  But for DUID identifiers, it's less clear.
> > I'm
> > guessing that the DUID is one that is, or could be, used by the
> > device
> > for DHCP purposes.  For IPv6 addresses, it's even less clear, since
> > the IPv6 architecture doesn't assume that the association of
> > addresses
> > with devices is permanent.
> 
> I hope that this document does not have to specify allocation procedures 
> for the MNIDs.  It seems to me that if a system designer wants to use 
> one of the MNID types, that person will already know about how to 
> request the allocation and would not need to rely on the MNIDs document 
> for that information.  Plus it's really out of scope.  This document was 
> always intended to be a simple tabulation of types already in use 
> elsewhere and enabling IETF mobility management protocols to use the 
> most natural identifier available for a mobile node.  I hope that citing 
> the defining documents for the identifier types will be enough to 
> satisfy that.

OK, I can agree with you there.  The only identifier which doesn't seem
to have a "natural" ownership scheme is IPv6 addresses; I think of IPv6
addressed as being assigned to a device every time it is initialized,
rather than being a way to identify the device.  But you address that in
the item below.

> > 4.1.  Description of the IPv6 address type
> >
> > It would be good if the document described what the semantics of this
> > ID are.  Yes, it's a unicast IPv6 address, but what is the connection
> > between that address and the device?  I suspect the connection is
> > "the
> > device has been configured to expect that it will be assigned this
> > address as a long-term interface address", but there are other
> > possibilities.  E.g., I can imagine a mobile carrier obtaining a /64
> > prefix (there are plenty of them!) and then assigning addresses out
> > of
> > it simply to create a sequence of unique identifiers for devices, but
> > not using those addresses on packets.
> >
> > Then again, perhaps you want to allow flexibility.  But in any case,
> > I
> > think you need to specify what the rules are for what address is
> > associated with what device.
> 
> As far as I have understood, the unicast IPv6 address in use as a MNID 
> is already assigned to the device.  I have not heard anyone asking for 
> this to be an address for future assignment.  I'll try to make that 
> clear in the text.

OK, if that's the case, then the usage is clear, as is how the device
obtains ownership of an address.

> > 4.2.  Description of the IMSI MNID type
> >
> > What does "in network order" mean here?  As far as I know, there is
> > no
> > defined "network order" for 4-bit quantities, only for dividing
> > integers into octets and placing sequences of bits into octets.  I
> > assume you mean that in any octet, the high-order 4 bits are the
> > first
> > digit and the low-order 4 bits are the second digit, but I think you
> > need to state that explicitly.
> 
> I probably lifted that language directly from the IMSI spec, but I can 
> make further clarification according to your suggestion.

It's likely that in the context of the IMSI spec that "network order"
means high-to-low for all sizes quantities, but I've not seen that used
in IETF context, so it's probably worth clarifying just to be thorough.

> > 4.9.  Description of the RFID types
> >
> > This section needs to be revised.  It provides a lot of detail about
> > the RFID types, but it's not enough detail for a reader who doesn't
> > understand RFID to learn how any particular RFID scheme works.  E.g.,
> > the first paragraph says that GID contains three fields in the first
> > sentence, and that it contains four fields in the third sentence.
> > Despite this, the description isn't enough to allow the reader to
> > construct GID identifiers manually.
> >
> > On the other hand, readers who already understand the RFID schemes
> > will find this text redundant.
> >
> > I think that almost all of this text can be replaced by references to
> > the EPC documents, since these identifiers are opaque from the point
> > of view of mobile identification.
> 
> Here I am at a loss, because I was specifically requested to insert some 
> descriptive but not normative text.  I will ask the person who made the 
> request to provide their feedback on the mailing list.  For myself, I am 
> more than happy to delete the text.

OK, if people have asked for descriptions, I can see the value in that.
But you might want to check that your phrasing makes sense to someone
who isn't already familiar with the EPC schemes.

> > 5.  Security Considerations
> >
> > The base MNID specification, RFC 4283, gives these security
> > considerations (sec 4), which ought to be referenced and probably
> > summarized in this section:
> >
> >     Moreover, MNIDs containing sensitive identifiers might only be used
> >     for signaling during initial network entry.  Subsequent binding
> >     update exchanges might then rely on a temporary identifier allocated
> >     during the initial network entry, perhaps using mechanisms not
> >     standardized within the IETF.  Managing the association between long-
> >     lived and temporary identifiers is outside the scope of this
> >     document.
> >
> > What is the meaning of the word "might" in paragraph 3?  I suspect
> > that the purpose is to qualify this paragraph with "One way to
> > address
> > these vulnerabilities is to only use MNIDs containing ...".  But if
> > that is the meaning, that expanded wording should be used.  Otherwise
> > the text reads as if it is hypothetical.
> 
> This text was meant to be generally descriptive, so that people wanting 
> to include the Mobile Node Identifier Option with the relevant MNIDs 
> could understand how the identifiers are actually used in various 
> circumstances.  I could replace constructions using "might" with "in 
> some specifications" or "in some situations" if needed.  Is it also 
> necessary to include citations to the relevant documents of the external 
> SDO?

I'd definitely prefer some other term than "might".  I'm not sure why,
but I think that it's because "might" isn't used much in specifications

If the external documents show how MNIDs will be used, and if that
context shows why the security problems are small, then I'd definitely
reference them.

One point that is not clear to me.  The above quoted paragraph suggests
that MNIDs are only transmitted during initial network entry.  But
reading it again, I'm led to guess that they are currently also used for
"binding update exchanges".  And you are suggesting that their use in
binding update exchanges could be eliminated by using temporary
identifiers?

If the first case is true, you can make the statement more definitive
as simply:

     Currently, MNIDs are only be used for signaling during initial
     network entry. [external reference]

If the second case is true, you want to make it clearer that the current
risks are (slightly) higher:

     Currently, MNIDs are only be used for signaling during initial
     network entry and binding update exchanges. [external reference]
     Future work could ensure that MNIDs are only be used for signaling
     during initial network entry by having subsequent binding update
     exchanges rely on a temporary identifier allocated during the
     initial network entry, perhaps using mechanisms not standardized
     within the IETF.  [perhaps delete that last phrase as not really
     adding anything?]  Managing the association between long-lived and
     temporary identifiers is outside the scope of this document.

Dale


From nobody Sun Feb 12 21:30:33 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BB09129480; Sun, 12 Feb 2017 21:30:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VQK6uAo1HHLB; Sun, 12 Feb 2017 21:30:30 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 196FE12948C; Sun, 12 Feb 2017 21:30:29 -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)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id D8E5324AE0B; Mon, 13 Feb 2017 05:30:25 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 74979160043; Mon, 13 Feb 2017 05:30:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 4B473160067; Mon, 13 Feb 2017 05:30:24 +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 vsXD7j-Owyzc; Mon, 13 Feb 2017 05:30:24 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 640D1160043; Mon, 13 Feb 2017 05:30:23 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BE00D6390011; Mon, 13 Feb 2017 16:30:18 +1100 (EST)
To: otroan@employees.org
From: Mark Andrews <marka@isc.org>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com> <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
In-reply-to: Your message of "Sat, 11 Feb 2017 23:59:20 +0100." <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Date: Mon, 13 Feb 2017 16:30:18 +1100
Message-Id: <20170213053018.BE00D6390011@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IE1sRHTc7BCbq9nLL-PJYNtd7I0>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, Gen-ART <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 05:30:32 -0000

In message <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>, otroan@employees.org writes:
> > How does this work for UDP?
> >
> > Sending packets no larger than 1280 bytes is always an option, and in
> > the case of UDP-based request-response protocols such as DNS that do
> > not have connection state, it may be the only feasible option.
>
> Yes, but DNS tend to use IP fragmentation that suffers an order of
> magnitude worse fate than ICMP messages. ;-)

Yep.  Idiots with firewalls break otherwise working protocols.
 
> > Anyway, the point I was trying to make was not to argue about better
> > or worse methods but rather to dispute the statement that PMTUD is
> > essential for avoiding black holes. I don't believe that it is. The
> > draft itself explicitly says that "IPv6 nodes are not required to
> > implement Path MTU Discovery."
>
> That's correct. But it then must restrict itself to sending packets at
> the minimum MTU size.
> You cannot implement RFC2473 (IP in IP) without PMTUD for example.
>
> [...]
>
> > What criteria for advancement to IS do you think are not met by this
> document?
> >
> > I do not dispute that the document has met the formal criteria for IS
> in Section
> > 2.2 of RFC 6410. I would argue, however, that its failure to provide a
> complete
> > solution for environments where delivery of ICMP messages is not assured
> > constitutes a significant technical omission for today's Internet, and
> I note
> > that per RFC 2026 Section 4.1.1, even a PS "should have no known
> technical
> > omissions." What I am asking the community, and the IESG, is whether it
> is
> > wise to advance a document with known technical omissions; it seems to
> me
> > that the Gen-ART reviewer has raised much the same question.
>
> For IPv6, because of the removal of fragmentation by intermediate nodes,
> failure to provide a path where ICMP message delivery is assured is a
> considered a configuration error.
>
> From
> http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-thesis
> .pdf:
>
> "We observed that for IPV4 between 4% and 6% of the paths between the
> vantage points and our experimental setup filter ICMP PTB packets. For
> IPV6 this was between 0.77% and 1.07%. Furthermore, we found that when
> IPV4 Domain Name System (DNS) servers do not act on the receipt of ICMP
> PTB packets, between 11% and 14% of the answers from these DNS servers
> are lost. For IPV6 DNS servers this was between 40% and 42%. Lastly, we
> found that for IPV4 approximately 6% of the paths between the vantage
> points and our experimental setup filter IP fragments. For IPV6 this was
> approximately 10%."

There isn't a lot a DNS server can do unless the host OS records
the path MTU for that destination.  I suppose theoretically it could
listen for PTB then set IPV6_USE_MIN_MTU for destinations that it
has received a PTB for but that is not optimal.  Unfortunately the
OPT/TSIG/SIG records are towards the end of the packet so it generally
isn't possible to resend the response that triggered the PTB.

> From that data it looks like we have been quite successful. ICMPv6 PMTUD
> is treated a lot better (about a 1% loss) than its IPv4 counterpart.
> Unless better data exists I tend to conclude that the claim that the
> Internet breaks PTUMD for IPv6 is a myth.
>
> Fragmentation on the other hand...

Fragmentation failing is basically gun, foot, shoot by blocking all
fragments at the firewall.  Nameservers don't need to support
fragmentation for request traffic which is what at least one of the
fragmentation is broken tested.  Firewall could reassemble or be
more selective about the fragments they drop.

It doesn't help that there is this myth that IPv6 packets will never
be fragmented.

Mark

> And please don't get me wrong, I think we have a big job to do on MTU
> issues. I just don't see data showing that PMTUD isn't doing what it was
> designed to do.
>
> 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 Mon Feb 13 00:41:43 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8406D129558; Mon, 13 Feb 2017 00:41:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level: 
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a3bSbK8zGsBz; Mon, 13 Feb 2017 00:41:36 -0800 (PST)
Received: from mx143.netapp.com (mx143.netapp.com [216.240.21.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5ECA129551; Mon, 13 Feb 2017 00:41:35 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,155,1484035200";  d="asc'?scan'208";a="175583806"
Received: from vmwexchts01-prd.hq.netapp.com ([10.122.105.12]) by mx143-out.netapp.com with ESMTP; 13 Feb 2017 00:28:49 -0800
Received: from VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) by VMWEXCHTS01-PRD.hq.netapp.com (10.122.105.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 00:36:34 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Mon, 13 Feb 2017 00:36:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=g/4R4Dzx3VmQfnmcvEhSkC1KORKM2cWxckqac24/How=; b=OCybobcpKhrgaOXSyNz45cPN8ZUP+utpBy7uHKV/fWq6Xb5VDP+BkUtvpuIO1r71ENm7lyoEDu7sNxIYwBndGScIvsD/rCulR7Be1Aap/vBzXcjQq4vN5SBHZrCVPySsEFKyWx/OUq0Lngn95h0p8+Y+UzaRp+EOjMHHkgPKFuA=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1154.namprd06.prod.outlook.com (10.160.157.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Mon, 13 Feb 2017 08:36:33 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0888.030; Mon, 13 Feb 2017 08:36:33 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Suresh Krishnan <suresh.krishnan@gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHShB9acsjWwaSyJ0WIyoGy+ZdFEqFjW9oAgANEb4A=
Date: Mon, 13 Feb 2017 08:36:33 +0000
Message-ID: <8C4F2A09-AD95-4B0E-9899-AF739E2BE7D8@netapp.com>
References: <CACL_3VEyOriSb6fjvGbYvG5a3gKOYPEe89-w7B9C_A5y_A9O9Q@mail.gmail.com> <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
In-Reply-To: <CA+MHpBougeQHCeajjpuGWj2N7RSsum80X6yy7nxzJzXfiDn+3Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: a8cc0b55-e175-4707-d41a-08d453eb6a6f
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1154; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1154; 7:ACULdsGakaEo4oMqoKzIrHCJPJO/RTlz+I/RJJ7YtIy1By9u+3aDYgPJZZbtm4MqXImHczLh1t+tp2nZT/pG4Ukm9SkmaR2kLTCp7eGgQNDFctAYdEJ8W0bMVKxmDstscKMZatgqGAMfLSW4me17CUaGEfmMB1YtiVaVj5nBgpxTWcnyWKiTuIEfzb3O4bGcrToOY6WlKpK84Y17JGqU4++MeiTeyLV+7tGHHtVNfafF8P3l099FPylOZtFCYolKNw22RIW1a1KrWXuaozUbyNB9iJDyjRV/5OKiTiS70VvKYb4x49Jt/ZVQ8JLDLjCcqzb9GP5lemgsAMg5/X1e47LBEYpxfjaESqwzv2u5CSkdF4YD04lot0TCazNsfBZDeHANJMkD2BV0awY1p7621ptvdhuSdqERPbBZV0i/tsNwtliDvYUbJ+E8COc5ZtTAZLovI8WYbnrShcPbpUZfNG3PrDX4QBePJ/ADxLGbUVb6EXXbgUVIaJCQGMvCOtGOignvwriGhfpJxmKP587qJA==
x-microsoft-antispam-prvs: <BN3PR0601MB11542BF7CA678AEA8EE23AD1A7590@BN3PR0601MB1154.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123564025)(20161123555025)(20161123558025)(20161123560025)(20161123562025)(6072148); SRVR:BN3PR0601MB1154; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1154; 
x-forefront-prvs: 02176E2458
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(199003)(24454002)(377424004)(189002)(36756003)(53936002)(38730400002)(110136004)(101416001)(77096006)(6116002)(82746002)(6436002)(53546003)(6246003)(102836003)(2900100001)(3846002)(122556002)(2950100002)(189998001)(230783001)(97736004)(6916009)(83716003)(66066001)(4001150100001)(50226002)(25786008)(8656002)(5660300001)(6486002)(68736007)(76176999)(8936002)(86362001)(3660700001)(99286003)(50986999)(3280700002)(57306001)(54906002)(81156014)(8676002)(81166006)(99936001)(6506006)(229853002)(2906002)(105586002)(106116001)(33656002)(7736002)(39060400001)(305945005)(4326007)(106356001)(558084003)(6512007)(92566002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1154; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Feb 2017 08:36:33.1874 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1154
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nwEm26rU9C9w1v7BY2bwR_WLVxU>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "C. M. Heard" <heard@pobox.com>, "gen-art@ietf.org" <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 08:41:37 -0000

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2017-2-11, at 7:42, Suresh Krishnan <suresh.krishnan@gmail.com> =
wrote:
> How does this work for UDP?

See draft-ietf-tsvwg-rfc5405bis (which is in AUTH48), Section 3.2 =
"Message Size Guidelines".

Lars

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYoXALAAoJEFS1wwm/cMFXxNkQALiBKBPolhYj/Q/4++kLc/ed
eAwp9gcI+0CVMzaRxhsbb8jMTkZWsU4+coQ7LXwGA302L8tqAmcYO9o6HPx0T3bO
eLYbMsombhLRmbyBj9nZiVbvsLWydjBTSaHiWNY6UAwqSA3VYhBev0WWqC4+EKYR
Y0eSUmldufGE1XvSOFSgtj32RAFy/iXXmjIRpwKG0ynao0bI/LwpQStlRbkfMBs1
HnCZdyxbt7H1RD3qsi3lJDE8coTC8YZ9pZh7549NrhHRv4/XWsMQuVll37OIYhIV
7cubHZjNOEP9ZUCgSFhlMLBK1FkukR60KibBGlVl4SEwe4cGRM9f1mu6wSsoAsN1
4nqDKfnpGqZJUZJQMza2v9SCUz2JGldbGMHSHMF4STURnn4TQBy0zbiJeGr4MpEY
Y2mE/JkCFkOAP0BSotO2RPL/6zqjqKr2a3IM4Fz4LKnR55Yvdq0zsb6fBB5+wv39
IpPw+Km7d6IFzopljQq+PafIo0n+KaAohYnDxmeelgDMie60wF33MuvPFlgeXjYc
Un4rfMSfP1s4nDEtJxZTELVrJfHLEX0kMlhi3UxsCkU9NLGKJkbN9DYV4cs402o8
Djf7e8HTRGSRfImOi3JLNyAqGd3oQaql8YgFkhK7DbDft9waonrbeyRdFawpR5w0
qgnps6+pH1SftjWGKsYd
=zv15
-----END PGP SIGNATURE-----

--Apple-Mail=_EE74725D-B983-4B1C-B183-D1F528063CF1--


From nobody Mon Feb 13 02:35:07 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 136691295CC for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 02:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 pajQN6gnIfDk for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 02:35:00 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 24FFB1293DF for <ietf@ietf.org>; Mon, 13 Feb 2017 02:34:59 -0800 (PST)
X-Halon-ID: 09cc9353-f1d8-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Mon, 13 Feb 2017 11:34:45 +0100 (CET)
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Subject: Re: Last Call: <draft-ietf-slim-negotiating-human-language-06.txt> (Negotiating Human Language in Real-Time Communications) to Proposed Standard
References: <148639487217.18865.13611191877947090796.idtracker@ietfa.amsl.com>
To: "slim@ietf.org" <slim@ietf.org>, ietf@ietf.org
Message-ID: <21d6ddb3-ebbd-833e-f5ff-800bdf144d2d@omnitor.se>
Date: Mon, 13 Feb 2017 11:34:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148639487217.18865.13611191877947090796.idtracker@ietfa.amsl.com>
Content-Type: multipart/mixed; boundary="------------14511186B3059DA30155E67B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9omqK5exPd7zet05KUYtUB-SoZg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 10:35:06 -0000

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

I have reviewed draft-ietf-slim-negotiating-human-language-06.txt and 
have composed a proposed edited version adjusted for my comments below, 
and additionally for some minor editorial issues.

The attached version is a rough edit of the txt file version. Accepted 
edits need to be re-done in the XML version.

Please use a diff to find all edit proposals. The main ones are listed 
below with reference to sections in the files.

-------------------------------------------------------------------------------------------------

1. Inexact wording about the syntax of the new attributes.

Sections 5 and 5.2,  .

The text sometimes indicate that the value of the attributes is a 
language tag, and sometimes a language tag with an optionally appended 
asterisk. The syntax shown in section 5.2 is also not in alignment with 
the syntax shown in section 6. In 5.2 it is shown without the optional 
asterisk, and in 6 with the optional asterisk.

Proposed action:  Make the attribute syntax equal in sections 5.2 and 6. 
Make sure that when "Language-Tag" is mentioned, it is only about the 
language tag part of the attribute value, and when the attribute value 
is mentioned, it is about the complete value, including the optional 
modifier.

Changes:

Last line in 5.  Change "be" to "contain"

Add [ asterisk ] last in both syntax lines in 5.2.

Multiple small changes in section 5.2. to adjust wording to be more 
exact. - See attached draft.

--------------------------------------------------------------------------------------------------------------------------------

2. Reminiscense of earlier syntax.

In a couple of places, there is wording left over from a recently 
abandoned syntax for the attributes. In an earlier version, each 
attribute value could contain multiple language-tags. Now, there is just 
one language-tag in each attribute value.

Changes:
At end of page 6:
Old:  "The values constitute a list of languages in preference order"

New: "The values from multiple attributes constitute a list of languages 
in preference order per direction"

At end of Section 5.3, the comparison with Accept-Language syntax is not 
valid anymore.

Delete: "(similar to SIP Accept-Language syntax)"

----------------------------------------------------------------------------------------------------------------------------------

3. Inexact wording about O/A procedure in section 5.2

The answers are called "accepted language", but within paranthesis it is 
mentioned that it is only in most cases that it is selected from the 
offer. More suitable is then to just call it just "language":

Old:
" In an answer, 'humintlang-send' is the accepted language the answerer
will send (which in most cases is one of the languages in the offer's
'humintlang-recv'), and 'humintlang-recv' is the accepted language
the answerer expects to receive (which in most cases is one of the
languages in the offer's 'humintlang-send')."

New:

"In an answer, 'humintlang-send' indicates the language the answerer
will send (which in most cases is one of the languages in the offer's
'humintlang-recv'), and 'humintlang-recv' indicates the language
the answerer expects to receive (which in most cases is one of the
languages in the offer's 'humintlang-send')."

-----------------------------------------------------------------------------------------------

4. Inexact note at end of section 5.2.

The note at end of 5.2 has a short discussion about accepted media as if 
it should possibly be influenced by the matching languages. This 
discussion is not really valid. A media section is a request to set up a 
media stream, unrelated to the language indications. The devices should 
deny media because they are not needed for language communication. This 
is made more clear in an extended note.

Old:

     "Note that media and language negotiation might result in more media
     streams being accepted than are needed by the users (e.g., if more
     preferred and less preferred combinations of media and language are
     all accepted)."

New:

"Note that media and language negotiation might result in more media
streams being accepted than are needed by the users for language
exchange (e.g., if more preferred and less preferred combinations
of media and language are all accepted). This is normal and accepted,
because the humintlang attribute is not intended to restrict media
streams to be used only for language exchange."

---------------------------------------------------------------------------------

5. Make use of the asterisk modifier on media level with session scope 
also for media level purposes

The asterisk modifier optionally appended on attribute values has in the 
original -06 draft only a session effect. It is specified to indicate if 
the call should be rejected or not if languages do not match. It can be 
appended to any humintlang attribute in the whole SDP without any change 
in effect. This independancy of placement indicates that it is wrongly 
placed. With the current definition, it should be a single separate 
session level attribute. Instead of specifying a separate session level 
attribute, it is proposed that the asterisk gets an expanded definition, 
so that its placement conveys meaning of value for the successful 
language negotiation.

It has been discussed in the SLIM WG that the specification lacks two 
functions, required by the specifications by other bodies who are 
waiting for the results of SLIM real-time work. (e.g. 3GPP TS 22.228 and 
ETSI TR 103 201). 3GPP TS 22.228 requires "The system should be able to 
negotiate the user's desired language(s) and modalities, per media 
stream and/or session, in order of preference." Thus negotiation
with preference indication within the session is required, not only 
within each media.
ETSI TR 103 201 says "the Total Conversation user should be able to 
indicate the preferred method of communication for each direction of the 
session, so that the call-taker can be selected appropriately or an 
appropriate assisting service be invoked. " Saying "preferred" means
that it should also be possible to indicate less preferred alternatives.

The most urgent of these functions can be fulfilled in a simple but 
sufficient way by extending the meaning of the asterisk. That is the 
possibility to indicate a difference in preference between languages in 
different modalities. There is an apparent risk that many calls will 
start and continue in an inconvenient modaity if this differentiation is 
not introduced. See the proposed replaced section 5.3 and extended 
examples in section 5.5.

Earlier discussions on this topic has not resulted in a sufficiently 
simple mechanism. The extended use of the asterisk proposed here is 
intended to introduce the required simplification, and yet meet the most 
urgent needs.


Changes:

In 5.2

Old:

"In an offer, each language tag value MAY have an asterisk appended as
the last character (after the language tag).  The asterisk indicates
a request by the caller to not fail the call if there is no language
in common."

New:

"In an offer or answer, each attribute value MAY have a modifier 
appended as the last character (after the Language-Tag). This 
specification defines one value for the modifier; an asterisk ("*"). The 
asterisk included in a humintlang attribute value in the SDP indicates a 
lower preference for the indicated language and a request by the caller 
to not reject the call if there is no language in common."

In 5.3. The whole section replaced by:

"
5.3.  Preferences within the session

It is of high importance for a smooth start of a call that the
answering party is answering the call using the best matching
language(s) and modality(ies) suitable for the continuation of the call.
Switching language and modality during the call by agreement between
the participants is often time consuming. Without support of detailed
language and modality negotiation the particiants may have a tendency
to continue the call in the initial language and modality even if a
more convenient common language and modality combination is available.
In order to support the decision on which of the available language(s)
and modality(ies) to use initially in the call, a simple two-level
preference indicator is specified here for inclusion as a modifier
in the humintlang attribute values. The preference indicator is also
used as an indicator that the call SHOULD be established even if no
language match is found.

The asterisk ("*") is used as a preference indicator within the session.
Low relative preference for a language and modality to be used in the
session SHOULD be indicated by appending an asterisk after the language
tag in the attribute value. This indication from the offering party
SHOULD be interpreted by the answering party as a request to use a
higher preferred language and modality when answering the call if
available, but otherwise accept a lower preferred language and
modality combination if that is available. When satisfying languages
and modalities in the offer is regarded to be so important that the
whole call SHOULD be rejected if no match can be provided in the
session in one or both directions, then the asterisk shall not be
appended on any indicated language in the whole session description.
For the case when no specific preference is desired, but the offering
party does not want the call to be rejected, all indicated languages
and modalities SHOULD have an asterisk appended.

In an answer, the language(s) and modality(ies) that the answering
party will use initially in the answer SHOULD be indicated without
an appended asterisk. Any language and modality available for later
use in the session MAY be indicated by a language tag with an
appended asterisk.

In the case when more than two parties participate in the call,
the language and modality indications provided to each party
SHOULD be the sum of the indications from the other parties.

The use of the preference indicator as specified above does
not provide for distinguishing between the case when two or
more language/modality combinations in the same direction
are desired for use simultaneously versus the case when two
or more language/modality combinations for the same directions
are provided as selectable alternatives without specific
preference differentiation. The context or other specifications
may introduce the possibility to distinguish between these cases.
When a party in a call has no indications that two or more
language/modality combinations for each direction are desired
simultaeously in the call, the party SHOULD assume that
satisfying one is sufficient.

Other specifications may add other attribute value modifiers than
the asterisk. If an unknown modifier is detected, the modifier
SHALL be ignored."

In section 6.

Reference to semantics in the attribute registrations are expanded from 
5.2 to 5.2-5.3.

---------------------------------------------------------------------------------------------------

6. The cases in the "Silly states" section 5.4 are not all silly.

Section 5.4 contains some proposed interpretations of unusual language 
indications.

They are not silly, but just unusual. Therefore change the name of the 
section to

"5.4 Unusual indications"

The section contains too weak specification about what to do with the 
unusual indications. That may cause a risk that a user who gets 
accustomed to one behavior in contact with certain UAs, suddeenly gets 
another behavior in contact with another UA.

Change:
Old:

"An offer MUST NOT be created where the language does not make sense
for the media type.  If such an offer is received, the receiver MAY
reject the media, ignore the language specified, or attempt to
interpret the intent (e.g., if American Sign Language is specified
for an audio media stream, this might be interpreted as a desire to
use spoken English)."

To:

"An offer MUST NOT be created where the language does not make sense
for the media type.  If such an offer is received, the receiver SHOULD
ignore the language specified."


Also add the following at the end of 5.4 to explain the choice of 
interpretation of a spoken/written language tag in a video medium to be 
a request to see the speaker rather than having text captions overlayed 
on video.

"There is no difference between language tags for spoken and written
languages. The spoken or written language tag indicated for a video
stream could therefore be interpreted as a capability or request to
use text captions overlayed on the video stream. The interpretation
according to this specification SHALL however be to have a view of
the speaker."

-----------------------------------------------------------------------------------------------------------

7. Examples section 5.5 requires expansion

Section 5.5 Examples has very little explanations and show just a few 
cases. The section is proposed to be expanded, with O/A examples with 
descriptions and alternative outcomes in order to more thoroughly 
describe the intended use.

See 5.5 in the the attached file for the proposed expansion.

------------------------------------------------------------------------------------------------------------

8. Include more fields for attribute registration from 4566bis

Section 6 has the form for attribute registration by IANA. There are a 
couple of fields missing that will be important for use of the 
specification in the WebRTC environment.  Include these fields if that 
is allowable according to current IANA procedures and if that does not 
delay the publication of this draft. These fields are needed for use of 
text media in WebRTC.

Change:

In two locations from:
     "Usage Level:  media"

to:

     "Usage Level:  media, dcsa(subprotocol)"

Insert in two locations in the registration forms:
"Mux Category: NORMAL"

---------------------------------------------------------------------------------------------------------------


With these proposed modifications accepted I am convinced that the 
result will be useful for its purpose.

Regards

Gunnar Hellstrom

-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288




Den 2017-02-06 kl. 16:27, skrev The IESG:
> The IESG has received a request from the Selection of Language for
> Internet Media WG (slim) to consider the following document:
> - 'Negotiating Human Language in Real-Time Communications'
>    <draft-ietf-slim-negotiating-human-language-06.txt> as Proposed
> Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-02-20. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     Users have various human (natural) language needs, abilities, and
>     preferences regarding spoken, written, and signed languages.  When
>     establishing interactive communication ("calls") there needs to be a
>     way to negotiate (communicate and match) the caller's language and
>     media needs with the capabilities of the called party.  This is
>     especially important with emergency calls, where a call can be
>     handled by a call taker capable of communicating with the user, or a
>     translator or relay operator can be bridged into the call during
>     setup, but this applies to non-emergency calls as well (as an
>     example, when calling a company call center).
>
>     This document describes the need and a solution using new SDP stream
>     attributes.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-slim-negotiating-human-language/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-slim-negotiating-human-language/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>      draft-saintandre-sip-xmpp-chat: Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat (None - )
> Note that some of these references may already be listed in the acceptable Downref Registry.
>
>

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288



--------------14511186B3059DA30155E67B
Content-Type: text/plain; charset=UTF-8;
 name="draft-ietf-slim-negotiating-human-language-06g.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="draft-ietf-slim-negotiating-human-language-06g.txt"

CgoKCk5ldHdvcmsgV29ya2luZyBHcm91cCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgUi4gR2VsbGVucwpJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgQ29yZSBUZWNobm9sb2d5IENvbnN1bHRpbmcKSW50ZW5kZWQgc3Rh
dHVzOiBTdGFuZGFyZHMgVHJhY2sgICAgICAgICAgICAgICAgICAgICAgIEZlYnJ1YXJ5IDEy
LCAyMDE3CkV4cGlyZXM6IEF1Z3VzdCA2LCAyMDE3CgoKICAgICAgICAgTmVnb3RpYXRpbmcg
SHVtYW4gTGFuZ3VhZ2UgaW4gUmVhbC1UaW1lIENvbW11bmljYXRpb25zCiAgICAgICAgICAg
ICBkcmFmdC1pZXRmLXNsaW0tbmVnb3RpYXRpbmctaHVtYW4tbGFuZ3VhZ2UtMDZnaAoKQWJz
dHJhY3QKCiAgIFVzZXJzIGhhdmUgdmFyaW91cyBodW1hbiAobmF0dXJhbCkgbGFuZ3VhZ2Ug
bmVlZHMsIGFiaWxpdGllcywgYW5kCiAgIHByZWZlcmVuY2VzIHJlZ2FyZGluZyBzcG9rZW4s
IHdyaXR0ZW4sIGFuZCBzaWduZWQgbGFuZ3VhZ2VzLiAgV2hlbgogICBlc3RhYmxpc2hpbmcg
aW50ZXJhY3RpdmUgY29tbXVuaWNhdGlvbiAoImNhbGxzIikgdGhlcmUgbmVlZHMgdG8gYmUg
YQogICB3YXkgdG8gbmVnb3RpYXRlIChjb21tdW5pY2F0ZSBhbmQgbWF0Y2gpIHRoZSBjYWxs
ZXIncyBsYW5ndWFnZSBhbmQKICAgbWVkaWEgbmVlZHMgd2l0aCB0aGUgY2FwYWJpbGl0aWVz
IG9mIHRoZSBjYWxsZWQgcGFydHkuICBUaGlzIGlzCiAgIGVzcGVjaWFsbHkgaW1wb3J0YW50
IHdpdGggZW1lcmdlbmN5IGNhbGxzLCB3aGVyZSBhIGNhbGwgY2FuIGJlCiAgIGhhbmRsZWQg
YnkgYSBjYWxsIHRha2VyIGNhcGFibGUgb2YgY29tbXVuaWNhdGluZyB3aXRoIHRoZSB1c2Vy
LCBvciBhCiAgIHRyYW5zbGF0b3Igb3IgcmVsYXkgb3BlcmF0b3IgY2FuIGJlIGJyaWRnZWQg
aW50byB0aGUgY2FsbCBkdXJpbmcKICAgc2V0dXAsIGJ1dCB0aGlzIGFwcGxpZXMgdG8gbm9u
LWVtZXJnZW5jeSBjYWxscyBhcyB3ZWxsIChhcyBhbgogICBleGFtcGxlLCB3aGVuIGNhbGxp
bmcgYSBjb21wYW55IGNhbGwgY2VudGVyKS4KCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVz
IHRoZSBuZWVkIGFuZCBhIHNvbHV0aW9uIHVzaW5nIG5ldyBTRFAgc3RyZWFtCiAgIGF0dHJp
YnV0ZXMuCgpTdGF0dXMgb2YgVGhpcyBNZW1vCgogICBUaGlzIEludGVybmV0LURyYWZ0IGlz
IHN1Ym1pdHRlZCBpbiBmdWxsIGNvbmZvcm1hbmNlIHdpdGggdGhlCiAgIHByb3Zpc2lvbnMg
b2YgQkNQIDc4IGFuZCBCQ1AgNzkuCgogICBJbnRlcm5ldC1EcmFmdHMgYXJlIHdvcmtpbmcg
ZG9jdW1lbnRzIG9mIHRoZSBJbnRlcm5ldCBFbmdpbmVlcmluZwogICBUYXNrIEZvcmNlIChJ
RVRGKS4gIE5vdGUgdGhhdCBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZQogICB3
b3JraW5nIGRvY3VtZW50cyBhcyBJbnRlcm5ldC1EcmFmdHMuICBUaGUgbGlzdCBvZiBjdXJy
ZW50IEludGVybmV0LQogICBEcmFmdHMgaXMgYXQgaHR0cDovL2RhdGF0cmFja2VyLmlldGYu
b3JnL2RyYWZ0cy9jdXJyZW50Ly4KCiAgIEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9j
dW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0gb2Ygc2l4IG1vbnRocwogICBhbmQgbWF5IGJl
IHVwZGF0ZWQsIHJlcGxhY2VkLCBvciBvYnNvbGV0ZWQgYnkgb3RoZXIgZG9jdW1lbnRzIGF0
IGFueQogICB0aW1lLiAgSXQgaXMgaW5hcHByb3ByaWF0ZSB0byB1c2UgSW50ZXJuZXQtRHJh
ZnRzIGFzIHJlZmVyZW5jZQogICBtYXRlcmlhbCBvciB0byBjaXRlIHRoZW0gb3RoZXIgdGhh
biBhcyAid29yayBpbiBwcm9ncmVzcy4iCgogICBUaGlzIEludGVybmV0LURyYWZ0IHdpbGwg
ZXhwaXJlIG9uIEF1Z3VzdCA2LCAyMDE3LgoKQ29weXJpZ2h0IE5vdGljZQoKICAgQ29weXJp
Z2h0IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25zIGlkZW50aWZpZWQgYXMg
dGhlCiAgIGRvY3VtZW50IGF1dGhvcnMuICBBbGwgcmlnaHRzIHJlc2VydmVkLgoKCgoKCkdl
bGxlbnMgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAgICAgICAg
ICAgICAgICBbUGFnZSAxXQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3RpYXRpbmcg
SHVtYW4gTGFuZ3VhZ2UgICAgICAgICAgRmVicnVhcnkgMjAxNwoKCiAgIFRoaXMgZG9jdW1l
bnQgaXMgc3ViamVjdCB0byBCQ1AgNzggYW5kIHRoZSBJRVRGIFRydXN0J3MgTGVnYWwKICAg
UHJvdmlzaW9ucyBSZWxhdGluZyB0byBJRVRGIERvY3VtZW50cwogICAoaHR0cDovL3RydXN0
ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUgb2YKICAg
cHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIFBsZWFzZSByZXZpZXcgdGhlc2UgZG9j
dW1lbnRzCiAgIGNhcmVmdWxseSwgYXMgdGhleSBkZXNjcmliZSB5b3VyIHJpZ2h0cyBhbmQg
cmVzdHJpY3Rpb25zIHdpdGggcmVzcGVjdAogICB0byB0aGlzIGRvY3VtZW50LiAgQ29kZSBD
b21wb25lbnRzIGV4dHJhY3RlZCBmcm9tIHRoaXMgZG9jdW1lbnQgbXVzdAogICBpbmNsdWRl
IFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UgdGV4dCBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA0
LmUgb2YKICAgdGhlIFRydXN0IExlZ2FsIFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3
aXRob3V0IHdhcnJhbnR5IGFzCiAgIGRlc2NyaWJlZCBpbiB0aGUgU2ltcGxpZmllZCBCU0Qg
TGljZW5zZS4KClRhYmxlIG9mIENvbnRlbnRzCgogICAxLiAgSW50cm9kdWN0aW9uICAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDMKICAgMi4g
IFRlcm1pbm9sb2d5IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gICA1CiAgIDMuICBEZXNpcmVkIFNlbWFudGljcyAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNQogICA0LiAgVGhlIGV4aXN0aW5nICds
YW5nJyBhdHRyaWJ1dGUgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgIDUKICAg
NS4gIFByb3Bvc2VkIFNvbHV0aW9uIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gICA2CiAgICAgNS4xLiAgUmF0aW9uYWxlIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgNgogICAgIDUuMi4gIFRoZSAnaHVt
aW50bGFuZy1zZW5kJyBhbmQgJ2h1bWludGxhbmctcmVjdicgYXR0cmlidXRlcyAgLiAgIDYK
ICAgICA1LjMuICBQcmVmZXJlbmNlcyB3aXRoaW4gdGhlIHNlc3Npb24gIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gICA4CiAgICAgNS40LiAgVW51c3VhbCBpbmRpY2F0aW9ucyAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAgOAogICAgIDUuNS4gIEV4YW1w
bGVzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
IDkKICAgNi4gIElBTkEgQ29uc2lkZXJhdGlvbnMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gICA5CiAgIDcuICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucyAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMAogICA4LiAgUHJpdmFj
eSBDb25zaWRlcmF0aW9ucyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAgMTAKICAgOS4gIENoYW5nZXMgZnJvbSBQcmV2aW91cyBWZXJzaW9ucyAgLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwCiAgICAgOS4xLiAgQ2hhbmdlcyBmcm9tIGRyYWZ0
LWlldGYtc2xpbS0uLi4tMDQgdG8gZHJhZnQtaWV0Zi0KICAgICAgICAgICBzbGltLS4uLi0w
NiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEwCiAg
ICAgOS4yLiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWlldGYtc2xpbS0uLi4tMDIgdG8gZHJhZnQt
aWV0Zi0KICAgICAgICAgICBzbGltLS4uLi0wMyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExCiAgICAgOS4zLiAgQ2hhbmdlcyBmcm9tIGRyYWZ0
LWlldGYtc2xpbS0uLi4tMDEgdG8gZHJhZnQtaWV0Zi0KICAgICAgICAgICBzbGltLS4uLi0w
MiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExCiAg
ICAgOS40LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWlldGYtc2xpbS0uLi4tMDAgdG8gZHJhZnQt
aWV0Zi0KICAgICAgICAgICBzbGltLS4uLi0wMSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExCiAgICAgOS41LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0
LWdlbGxlbnMtc2xpbS0uLi4tMDMgdG8gZHJhZnQtaWV0Zi0KICAgICAgICAgICBzbGltLS4u
Li0wMCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEx
CiAgICAgOS42LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWdlbGxlbnMtc2xpbS0uLi4tMDIgdG8g
ZHJhZnQtZ2VsbGVucy0KICAgICAgICAgICBzbGltLS4uLi0wMyAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExCiAgICAgOS43LiAgQ2hhbmdlcyBm
cm9tIGRyYWZ0LWdlbGxlbnMtc2xpbS0uLi4tMDEgdG8gZHJhZnQtZ2VsbGVucy0KICAgICAg
ICAgICBzbGltLS4uLi0wMiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gIDExCiAgICAgOS44LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWdlbGxlbnMtc2xp
bS0uLi4tMDAgdG8gZHJhZnQtZ2VsbGVucy0KICAgICAgICAgICBzbGltLS4uLi0wMSAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDExCiAgICAgOS45
LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWdlbGxlbnMtbW11c2ljLS4uLi0wMiB0byBkcmFmdC0K
ICAgICAgICAgICBnZWxsZW5zLXNsaW0tLi4uLTAwIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDExCiAgICAgOS4xMC4gQ2hhbmdlcyBmcm9tIGRyYWZ0LWdlbGxl
bnMtbW11c2ljLS4uLi0wMSB0byAtMDIgLiAuIC4gLiAuICAxMgogICAgIDkuMTEuIENoYW5n
ZXMgZnJvbSBkcmFmdC1nZWxsZW5zLW1tdXNpYy0uLi4tMDAgdG8gLTAxIC4gLiAuIC4gLiAg
MTIKICAgICA5LjEyLiBDaGFuZ2VzIGZyb20gZHJhZnQtZ2VsbGVucy0uLi4tMDIgdG8gZHJh
ZnQtZ2VsbGVucy0KICAgICAgICAgICBtbXVzaWMtLi4uLTAwIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEyCgoKCkdlbGxlbnMgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAgICAgICAgICAgICAgICBbUGFnZSAyXQoM
CkludGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAg
ICAgICAgRmVicnVhcnkgMjAxNwoKCiAgICAgOS4xMy4gQ2hhbmdlcyBmcm9tIGRyYWZ0LWdl
bGxlbnMtLi4uLTAxIHRvIC0wMiAgLiAuIC4gLiAuIC4gLiAuICAxMwogICAgIDkuMTQuIENo
YW5nZXMgZnJvbSBkcmFmdC1nZWxsZW5zLS4uLi0wMCB0byAtMDEgIC4gLiAuIC4gLiAuIC4g
LiAgMTMKICAgMTAuIENvbnRyaWJ1dG9ycyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gIDEzCiAgIDExLiBBY2tub3dsZWRnbWVudHMgLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxMwogICAxMi4gUmVm
ZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAgMTQKICAgICAxMi4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDE0CiAgICAgMTIuMi4gIEluZm9ybWF0aW9uYWwg
UmVmZXJlbmNlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxNAogICBBcHBl
bmRpeCBBLiAgSGlzdG9yaWMgQWx0ZXJuYXRpdmUgUHJvcG9zYWw6IENhbGxlci1wcmVmcyAg
LiAuIC4gLiAgMTQKICAgICBBLjEuICBVc2Ugb2YgQ2FsbGVyIFByZWZlcmVuY2VzIFdpdGhv
dXQgQWRkaXRpb25zIC4gLiAuIC4gLiAuIC4gIDE1CiAgICAgQS4yLiAgQWRkaXRpb25hbCBD
YWxsZXIgUHJlZmVyZW5jZXMgZm9yIEFzeW1tZXRyaWMgTmVlZHMgIC4gLiAuICAxNwogICAg
ICAgQS4yLjEuICBDYWxsZXIgUHJlZmVyZW5jZXMgZm9yIEFzeW1tZXRyaWMgTW9kYWxpdHkg
TmVlZHMgIC4gLiAgMTcKICAgICAgIEEuMi4yLiAgQ2FsbGVyIFByZWZlcmVuY2VzIGZvciBB
c3ltbWV0cmljIExhbmd1YWdlIFRhZ3MgLiAuIC4gIDE4CiAgIEF1dGhvcidzIEFkZHJlc3Mg
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAxOQoK
MS4gIEludHJvZHVjdGlvbgoKICAgQSBtdXR1YWxseSBjb21wcmVoZW5zaWJsZSBsYW5ndWFn
ZSBpcyBoZWxwZnVsIGZvciBodW1hbgogICBjb21tdW5pY2F0aW9uLiAgVGhpcyBkb2N1bWVu
dCBhZGRyZXNzZXMgdGhlIHJlYWwtdGltZSwgaW50ZXJhY3RpdmUKICAgc2lkZSBvZiB0aGUg
aXNzdWUuICBBIGNvbXBhbmlvbiBkb2N1bWVudCBvbiBsYW5ndWFnZSBzZWxlY3Rpb24gaW4K
ICAgZW1haWwgW0ktRC5pZXRmLXNsaW0tbXVsdGlsYW5nY29udGVudF0gYWRkcmVzc2VzIHRo
ZSBub24tcmVhbC10aW1lCiAgIHNpZGUuCgogICBXaGVuIHNldHRpbmcgdXAgaW50ZXJhY3Rp
dmUgY29tbXVuaWNhdGlvbiBzZXNzaW9ucyAodXNpbmcgU0lQIG9yCiAgIG90aGVyIHByb3Rv
Y29scyksIGh1bWFuIChuYXR1cmFsKSBsYW5ndWFnZSBhbmQgbWVkaWEgbW9kYWxpdHkKICAg
KHNwb2tlbiwgc2lnbmVkLCB3cml0dGVuKSBuZWdvdGlhdGlvbiBtYXkgYmUgbmVlZGVkLiAg
VW5sZXNzIHRoZQogICBjYWxsZXIgYW5kIGNhbGxlZSBrbm93IGVhY2ggb3RoZXIgb3IgdGhl
cmUgaXMgY29udGV4dHVhbCBvciBvdXQgb2YKICAgYmFuZCBpbmZvcm1hdGlvbiBmcm9tIHdo
aWNoIHRoZSBsYW5ndWFnZShzKSBhbmQgbWVkaWEgbW9kYWxpdGllcyBjYW4KICAgYmUgZGV0
ZXJtaW5lZCwgdGhlcmUgaXMgYSBuZWVkIGZvciBzcG9rZW4sIHNpZ25lZCwgb3Igd3JpdHRl
bgogICBsYW5ndWFnZXMgdG8gYmUgbmVnb3RpYXRlZCBiYXNlZCBvbiB0aGUgY2FsbGVyJ3Mg
bmVlZHMgYW5kIHRoZQogICBjYWxsZWUncyBjYXBhYmlsaXRpZXMuICBUaGlzIG5lZWQgYXBw
bGllcyB0byBib3RoIGVtZXJnZW5jeSBhbmQgbm9uLQogICBlbWVyZ2VuY3kgY2FsbHMuICBG
b3IgdmFyaW91cyByZWFzb25zLCBpbmNsdWRpbmcgdGhlIGFiaWxpdHkgdG8KICAgZXN0YWJs
aXNoIG11bHRpcGxlIHN0cmVhbXMgdXNpbmcgZGlmZmVyZW50IG1lZGlhIChlLmcuLCB2b2lj
ZSwgdGV4dCwKICAgdmlkZW8pLCBpdCBtYWtlcyBzZW5zZSB0byB1c2UgYSBwZXItc3RyZWFt
IG5lZ290aWF0aW9uIG1lY2hhbmlzbSwgaW4KICAgdGhpcyBjYXNlLCBTRFAuCgogICBUaGlz
IGFwcHJvYWNoIGhhcyBhIG51bWJlciBvZiBiZW5lZml0cywgaW5jbHVkaW5nIHRoYXQgaXQg
aXMgZ2VuZXJpYwogICAoYXBwbGllcyB0byBhbGwgaW50ZXJhY3RpdmUgY29tbXVuaWNhdGlv
bnMgbmVnb3RpYXRlZCB1c2luZyBTRFApIGFuZAogICBub3QgbGltaXRlZCB0byBlbWVyZ2Vu
Y3kgY2FsbHMuICBJbiBzb21lIGNhc2VzIHN1Y2ggYSBmYWNpbGl0eSBpc24ndAogICBuZWVk
ZWQsIGJlY2F1c2UgdGhlIGxhbmd1YWdlIGlzIGtub3duIGZyb20gdGhlIGNvbnRleHQgKHN1
Y2ggYXMgd2hlbgogICBhIGNhbGxlciBwbGFjZXMgYSBjYWxsIHRvIGEgc2lnbiBsYW5ndWFn
ZSByZWxheSBjZW50ZXIsIHRvIGEgZnJpZW5kLAogICBvciBjb2xsZWFndWUpLiAgQnV0IGl0
IGlzIGNsZWFybHkgdXNlZnVsIGluIG1hbnkgb3RoZXIgY2FzZXMuICBGb3IKICAgZXhhbXBs
ZSwgc29tZW9uZSBjYWxsaW5nIGEgY29tcGFueSBjYWxsIGNlbnRlciBvciBhIFB1YmxpYyBT
YWZldHkKICAgQW5zd2VyaW5nIFBvaW50IChQU0FQKSBzaG91bGQgYmUgYWJsZSB0byBpbmRp
Y2F0ZSBpZiBvbmUgb3IgbW9yZQogICBzcGVjaWZpYyBzaWduZWQsIHdyaXR0ZW4sIGFuZC9v
ciBzcG9rZW4gbGFuZ3VhZ2VzIGFyZSBwcmVmZXJyZWQsIHRoZQogICBjYWxsZWUgc2hvdWxk
IGJlIGFibGUgdG8gaW5kaWNhdGUgaXRzIGNhcGFiaWxpdGllcyBpbiB0aGlzIGFyZWEsIGFu
ZAogICB0aGUgY2FsbCBwcm9jZWVkIHVzaW5nIGluLWNvbW1vbiBsYW5ndWFnZShzKSBhbmQg
bWVkaWEgZm9ybXMuCgoKCgoKR2VsbGVucyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXVn
dXN0IDYsIDIwMTcgICAgICAgICAgICAgICAgIFtQYWdlIDNdCgwKSW50ZXJuZXQtRHJhZnQg
ICAgICAgICBOZWdvdGlhdGluZyBIdW1hbiBMYW5ndWFnZSAgICAgICAgICBGZWJydWFyeSAy
MDE3CgoKICAgU2luY2UgdGhpcyBpcyBhIHByb3RvY29sIG1lY2hhbmlzbSwgdGhlIHVzZXIg
ZXF1aXBtZW50IChVRSBjbGllbnQpCiAgIG5lZWRzIHRvIGtub3cgdGhlIHVzZXIncyBwcmVm
ZXJyZWQgbGFuZ3VhZ2VzOyBhIHJlYXNvbmFibGUgdGVjaG5pcXVlCiAgIGNvdWxkIGluY2x1
ZGUgYSBjb25maWd1cmF0aW9uIG1lY2hhbmlzbSB3aXRoIGEgZGVmYXVsdCBvZiB0aGUKICAg
bGFuZ3VhZ2Ugb2YgdGhlIHVzZXIgaW50ZXJmYWNlLiAgSW4gc29tZSBjYXNlcywgYSBVRSBj
b3VsZCB0aWUKICAgbGFuZ3VhZ2UgYW5kIG1lZGlhIHByZWZlcmVuY2VzLCBzdWNoIGFzIGEg
cHJlZmVyZW5jZSBmb3IgYSB2aWRlbwogICBzdHJlYW0gdXNpbmcgYSBzaWduZWQgbGFuZ3Vh
Z2UgYW5kL29yIGEgdGV4dCBvciBhdWRpbyBzdHJlYW0gdXNpbmcgYQogICB3cml0dGVuL3Nw
b2tlbiBsYW5ndWFnZS4KCiAgIEluY2x1ZGluZyB0aGUgdXNlcidzIGh1bWFuIChuYXR1cmFs
KSBsYW5ndWFnZSBwcmVmZXJlbmNlcyBpbiB0aGUKICAgc2Vzc2lvbiBlc3RhYmxpc2htZW50
IG5lZ290aWF0aW9uIGlzIGluZGVwZW5kZW50IG9mIHRoZSB1c2Ugb2YgYQogICByZWxheSBz
ZXJ2aWNlIGFuZCBpcyB0cmFuc3BhcmVudCB0byBhIHZvaWNlIHNlcnZpY2UgcHJvdmlkZXIu
ICBGb3IKICAgZXhhbXBsZSwgYXNzdW1lIGEgdXNlciB3aXRoaW4gdGhlIFVuaXRlZCBTdGF0
ZXMgd2hvIHNwZWFrcyBTcGFuaXNoCiAgIGJ1dCBub3QgRW5nbGlzaCBwbGFjZXMgYSB2b2lj
ZSBjYWxsLiAgVGhlIGNhbGwgY291bGQgYmUgYW4gZW1lcmdlbmN5CiAgIGNhbGwgb3IgcGVy
aGFwcyB0byBhbiBhaXJsaW5lIHJlc2VydmF0aW9uIGRlc2suICBUaGUgbGFuZ3VhZ2UKICAg
aW5mb3JtYXRpb24gaXMgdHJhbnNwYXJlbnQgdG8gdGhlIHZvaWNlIHNlcnZpY2UgcHJvdmlk
ZXIsIGJ1dCBpcyBwYXJ0CiAgIG9mIHRoZSBzZXNzaW9uIG5lZ290aWF0aW9uIGJldHdlZW4g
dGhlIFVFIGFuZCB0aGUgdGVybWluYXRpbmcgZW50aXR5LgogICBJbiB0aGUgY2FzZSBvZiBh
IGNhbGwgdG8gZS5nLiwgYW4gYWlybGluZSwgdGhlIGNhbGwgY291bGQgYmUKICAgYXV0b21h
dGljYWxseSBoYW5kbGVkIGJ5IGEgU3BhbmlzaC1zcGVha2luZyBhZ2VudC4gIEluIHRoZSBj
YXNlIG9mIGFuCiAgIGVtZXJnZW5jeSBjYWxsLCB0aGUgRW1lcmdlbmN5IFNlcnZpY2VzIElQ
IG5ldHdvcmsgKEVTSW5ldCkgYW5kIHRoZQogICBQU0FQIG1heSBjaG9vc2UgdG8gdGFrZSB0
aGUgbGFuZ3VhZ2UgYW5kIG1lZGlhIHByZWZlcmVuY2VzIGludG8KICAgYWNjb3VudCB3aGVu
IGRldGVybWluaW5nIGhvdyB0byBwcm9jZXNzIHRoZSBjYWxsLgoKICAgQnkgdHJlYXRpbmcg
bGFuZ3VhZ2UgYXMgYW5vdGhlciBhdHRyaWJ1dGUgdGhhdCBpcyBuZWdvdGlhdGVkIGFsb25n
CiAgIHdpdGggb3RoZXIgYXNwZWN0cyBvZiBhIG1lZGlhIHN0cmVhbSwgaXQgYmVjb21lcyBw
b3NzaWJsZSB0bwogICBhY2NvbW1vZGF0ZSBhIHJhbmdlIG9mIHVzZXJzJyBuZWVkcyBhbmQg
Y2FsbGVkIHBhcnR5IGZhY2lsaXRpZXMuICBGb3IKICAgZXhhbXBsZSwgc29tZSB1c2VycyBt
YXkgYmUgYWJsZSB0byBzcGVhayBzZXZlcmFsIGxhbmd1YWdlcywgYnV0IGhhdmUKICAgYSBw
cmVmZXJlbmNlLiAgU29tZSBjYWxsZWQgcGFydGllcyBtYXkgc3VwcG9ydCBzb21lIG9mIHRo
b3NlCiAgIGxhbmd1YWdlcyBpbnRlcm5hbGx5IGJ1dCByZXF1aXJlIHRoZSB1c2Ugb2YgYSB0
cmFuc2xhdGlvbiBzZXJ2aWNlIGZvcgogICBvdGhlcnMsIG9yIG1heSBoYXZlIGEgbGltaXRl
ZCBudW1iZXIgb2YgY2FsbCB0YWtlcnMgYWJsZSB0byB1c2UKICAgY2VydGFpbiBsYW5ndWFn
ZXMuICBBbm90aGVyIGV4YW1wbGUgd291bGQgYmUgYSB1c2VyIHdobyBpcyBhYmxlIHRvCiAg
IHNwZWFrIGJ1dCBpcyBkZWFmIG9yIGhhcmQtb2YtaGVhcmluZyBhbmQgcmVxdWlyZXMgYSB2
b2ljZSBzdHJlYW0gcGx1cwogICBhIHRleHQgc3RyZWFtLiAgTWFraW5nIGxhbmd1YWdlIGEg
bWVkaWEgYXR0cmlidXRlIGFsbG93cyB0aGUgc3RhbmRhcmQKICAgc2Vzc2lvbiBuZWdvdGlh
dGlvbiBtZWNoYW5pc20gdG8gaGFuZGxlIHRoaXMgYnkgcHJvdmlkaW5nIHRoZQogICBpbmZv
cm1hdGlvbiBhbmQgbWVjaGFuaXNtIGZvciB0aGUgZW5kcG9pbnRzIHRvIG1ha2UgYXBwcm9w
cmlhdGUKICAgZGVjaXNpb25zLgoKICAgUmVnYXJkaW5nIHJlbGF5IHNlcnZpY2VzLCBpbiB0
aGUgY2FzZSBvZiBhbiBlbWVyZ2VuY3kgY2FsbCByZXF1aXJpbmcKICAgc2lnbiBsYW5ndWFn
ZSBzdWNoIGFzIEFTTCwgdGhlcmUgYXJlIGN1cnJlbnRseSB0d28gY29tbW9uIGFwcHJvYWNo
ZXM6CiAgIHRoZSBjYWxsZXIgaW5pdGlhdGVzIHRoZSBjYWxsIHRvIGEgcmVsYXkgY2VudGVy
LCBvciB0aGUgY2FsbGVyIHBsYWNlcwogICB0aGUgY2FsbCB0byBlbWVyZ2VuY3kgc2Vydmlj
ZXMgKGUuZy4sIDkxMSBpbiB0aGUgVS5TLiBvciAxMTIgaW4KICAgRXVyb3BlKS4gIChJbiBh
IHZhcmlhbnQgb2YgdGhlIHNlY29uZCBjYXNlLCB0aGUgdm9pY2Ugc2VydmljZQogICBwcm92
aWRlciBpbnZva2VzIGEgcmVsYXkgc2VydmljZSBhcyB3ZWxsIGFzIGVtZXJnZW5jeSBzZXJ2
aWNlcy4pICBJbgogICB0aGUgZm9ybWVyIGNhc2UsIHRoZSBsYW5ndWFnZSBuZWVkIGlzIGFu
Y2lsbGFyeSBhbmQgc3VwcGxlbWVudGFsLiAgSW4KICAgdGhlIG5vbi12YXJpYW50IHNlY29u
ZCBjYXNlLCB0aGUgRVNJbmV0IGFuZC9vciBQU0FQIG1heSB0YWtlIHRoZSBuZWVkCiAgIGZv
ciBzaWduIGxhbmd1YWdlIGludG8gYWNjb3VudCBhbmQgYnJpZGdlIGluIGEgcmVsYXkgY2Vu
dGVyLiAgSW4gdGhpcwogICBjYXNlLCB0aGUgRVNJbmV0IGFuZCBQU0FQIGhhdmUgYWxsIHRo
ZSBzdGFuZGFyZCBpbmZvcm1hdGlvbiBhdmFpbGFibGUKICAgKHN1Y2ggYXMgbG9jYXRpb24p
IGJ1dCBhcmUgYWJsZSB0byBicmlkZ2UgdGhlIHJlbGF5IHNvb25lciBpbiB0aGUKICAgY2Fs
bCBwcm9jZXNzaW5nLgoKCgpHZWxsZW5zICAgICAgICAgICAgICAgICAgRXhwaXJlcyBBdWd1
c3QgNiwgMjAxNyAgICAgICAgICAgICAgICAgW1BhZ2UgNF0KDApJbnRlcm5ldC1EcmFmdCAg
ICAgICAgIE5lZ290aWF0aW5nIEh1bWFuIExhbmd1YWdlICAgICAgICAgIEZlYnJ1YXJ5IDIw
MTcKCgogICBCeSBtYWtpbmcgdGhpcyBmYWNpbGl0eSBwYXJ0IG9mIHRoZSBlbmQtdG8tZW5k
IG5lZ290aWF0aW9uLCB0aGUKICAgcXVlc3Rpb24gb2Ygd2hpY2ggZW50aXR5IHByb3ZpZGVz
IG9yIGVuZ2FnZXMgdGhlIHJlbGF5IHNlcnZpY2UKICAgYmVjb21lcyBzZXBhcmF0ZSBmcm9t
IHRoZSBjYWxsIHByb2Nlc3NpbmcgbWVjaGFuaWNzOyBpZiB0aGUgY2FsbGVyCiAgIGRpcmVj
dHMgdGhlIGNhbGwgdG8gYSByZWxheSBzZXJ2aWNlIHRoZW4gdGhlIGh1bWFuIGxhbmd1YWdl
CiAgIG5lZ290aWF0aW9uIGZhY2lsaXR5IHByb3ZpZGVzIGV4dHJhIGluZm9ybWF0aW9uIHRv
IHRoZSByZWxheSBzZXJ2aWNlCiAgIGJ1dCBjYWxscyB3aWxsIHN0aWxsIGZ1bmN0aW9uIHdp
dGhvdXQgaXQ7IGlmIHRoZSBjYWxsZXIgZGlyZWN0cyB0aGUKICAgY2FsbCB0byBlbWVyZ2Vu
Y3kgc2VydmljZXMsIHRoZW4gdGhlIEVTSW5ldC9QU0FQIGFyZSBhYmxlIHRvIHRha2UgdGhl
CiAgIHVzZXIncyBodW1hbiBsYW5ndWFnZSBuZWVkcyBpbnRvIGFjY291bnQsIGUuZy4sIGJ5
IGFzc2lnbmluZyB0byBhCiAgIHNwZWNpZmljIHF1ZXVlIG9yIGNhbGwgdGFrZXIgb3IgYnJp
ZGdpbmcgaW4gYSByZWxheSBzZXJ2aWNlIG9yCiAgIHRyYW5zbGF0b3IuCgogICBUaGUgdGVy
bSAibmVnb3RpYXRpb24iIGlzIHVzZWQgaGVyZSByYXRoZXIgdGhhbiAiaW5kaWNhdGlvbiIg
YmVjYXVzZQogICBodW1hbiBsYW5ndWFnZSAoc3Bva2VuL3dyaXR0ZW4vc2lnbmVkKSBpcyBz
b21ldGhpbmcgdGhhdCBjYW4gYmUKICAgbmVnb3RpYXRlZCBpbiB0aGUgc2FtZSB3YXkgYXMg
d2hpY2ggZm9ybXMgb2YgbWVkaWEgKGF1ZGlvL3RleHQvdmlkZW8pCiAgIG9yIHdoaWNoIGNv
ZGVjcy4gIEZvciBleGFtcGxlLCBpZiB3ZSB0aGluayBvZiBub24tZW1lcmdlbmN5IGNhbGxz
LAogICBzdWNoIGFzIGEgdXNlciBjYWxsaW5nIGFuIGFpcmxpbmUgcmVzZXJ2YXRpb24gY2Vu
dGVyLCB0aGUgdXNlciBtYXkKICAgaGF2ZSBhIHNldCBvZiBsYW5ndWFnZXMgaGUgb3Igc2hl
IHNwZWFrcywgd2l0aCBwZXJoYXBzIHByZWZlcmVuY2VzCiAgIGZvciBvbmUgb3IgYSBmZXcs
IHdoaWxlIHRoZSBhaXJsaW5lIHJlc2VydmF0aW9uIGNlbnRlciB3aWxsIHN1cHBvcnQgYQog
ICBmaXhlZCBzZXQgb2YgbGFuZ3VhZ2VzLiAgTmVnb3RpYXRpb24gU0hPVUxEIHNlbGVjdCB0
aGUgdXNlcidzIG1vc3QKICAgcHJlZmVycmVkIGxhbmd1YWdlIHRoYXQgaXMgc3VwcG9ydGVk
IGJ5IHRoZSBjYWxsIGNlbnRlci4gIEJvdGggc2lkZXMKICAgc2hvdWxkIGJlIGF3YXJlIG9m
IHdoaWNoIGxhbmd1YWdlIHdhcyBuZWdvdGlhdGVkLiAgVGhpcyBpcwogICBjb25jZXB0dWFs
bHkgc2ltaWxhciB0byB0aGUgd2F5IG90aGVyIGFzcGVjdHMgb2YgZWFjaCBtZWRpYSBzdHJl
YW0KICAgYXJlIG5lZ290aWF0ZWQgdXNpbmcgU0RQIChlLmcuLCBtZWRpYSB0eXBlIGFuZCBj
b2RlY3MpLgoKMi4gIFRlcm1pbm9sb2d5CgogICBUaGUga2V5IHdvcmRzICJNVVNUIiwgIk1V
U1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5PVCIsCiAgICJTSE9VTEQi
LCAiU0hPVUxEIE5PVCIsICJSRUNPTU1FTkRFRCIsICJNQVkiLCBhbmQgIk9QVElPTkFMIiBp
biB0aGlzCiAgIGRvY3VtZW50IGFyZSB0byBiZSBpbnRlcnByZXRlZCBhcyBkZXNjcmliZWQg
aW4gUkZDIDIxMTkgW1JGQzIxMTldLgoKMy4gIERlc2lyZWQgU2VtYW50aWNzCgogICBUaGUg
ZGVzaXJlZCBzb2x1dGlvbiBpcyBhIG1lZGlhIGF0dHJpYnV0ZSAocHJlZmVyYWJseSBwZXIg
ZGlyZWN0aW9uKQogICB0aGF0IE1BWSBiZSB1c2VkIHdpdGhpbiBhbiBvZmZlciB0byBpbmRp
Y2F0ZSB0aGUgcHJlZmVycmVkIGxhbmd1YWdlCiAgIG9mIGVhY2ggKGRpcmVjdGlvbiBvZiBh
KSBtZWRpYSBzdHJlYW0sIGFuZCB3aXRoaW4gYW4gYW5zd2VyIHRvCiAgIGluZGljYXRlIHRo
ZSBhY2NlcHRlZCBsYW5ndWFnZS4gIFRoZSBzZW1hbnRpY3Mgb2YgaW5jbHVkaW5nIG11bHRp
cGxlCiAgIHZhbHVlcyBmb3IgYSBtZWRpYSBzdHJlYW0gd2l0aGluIGFuIG9mZmVyIGlzIHRo
YXQgdGhlIGxhbmd1YWdlcyBhcmUKICAgbGlzdGVkIGluIG9yZGVyIG9mIHByZWZlcmVuY2Uu
CgogICAoTmVnb3RpYXRpbmcgbXVsdGlwbGUgc2ltdWx0YW5lb3VzIGxhbmd1YWdlcyB3aXRo
aW4gYSBtZWRpYSBzdHJlYW0gaXMKICAgb3V0IG9mIHNjb3BlLCBhcyB0aGUgY29tcGxleGl0
eSBvZiBkb2luZyBzbyBvdXR3ZWlnaHMgdGhlCiAgIHVzZWZ1bG5lc3MuKQoKNC4gIFRoZSBl
eGlzdGluZyAnbGFuZycgYXR0cmlidXRlCgogICBSRkMgNDU2NiBbUkZDNDU2Nl0gc3BlY2lm
aWVzIGFuIGF0dHJpYnV0ZSAnbGFuZycgd2hpY2ggYXBwZWFycwogICBzaW1pbGFyIHRvIHdo
YXQgaXMgbmVlZGVkIGhlcmUsIGJ1dCBpcyBub3Qgc3VmZmljaWVudGx5IGRldGFpbGVkIGZv
cgogICB1c2UgaGVyZS4gIEluIGFkZGl0aW9uLCBpdCBpcyBub3QgbWVudGlvbmVkIGluIFtS
RkMzMjY0XSBhbmQgdGhlcmUKCgoKR2VsbGVucyAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
QXVndXN0IDYsIDIwMTcgICAgICAgICAgICAgICAgIFtQYWdlIDVdCgwKSW50ZXJuZXQtRHJh
ZnQgICAgICAgICBOZWdvdGlhdGluZyBIdW1hbiBMYW5ndWFnZSAgICAgICAgICBGZWJydWFy
eSAyMDE3CgoKICAgYXJlIG5vIGtub3duIGltcGxlbWVudGF0aW9ucyBpbiBTSVAuICBGdXJ0
aGVyLCB0aGVyZSBpcyB2YWx1ZSBpbgogICBiZWluZyBhYmxlIHRvIHNwZWNpZnkgbGFuZ3Vh
Z2UgcGVyIGRpcmVjdGlvbiAoc2VuZGluZyBhbmQgcmVjZWl2aW5nKS4KICAgVGhpcyBkb2N1
bWVudCB0aGVyZWZvcmUgZGVmaW5lcyB0d28gbmV3IGF0dHJpYnV0ZXMuCgo1LiAgUHJvcG9z
ZWQgU29sdXRpb24KCiAgIEFuIFNEUCBhdHRyaWJ1dGUgKHBlciBkaXJlY3Rpb24pIHNlZW1z
IHRoZSBuYXR1cmFsIGNob2ljZSB0bwogICBuZWdvdGlhdGUgaHVtYW4gKG5hdHVyYWwpIGxh
bmd1YWdlIG9mIGFuIGludGVyYWN0aXZlIG1lZGlhIHN0cmVhbS4KICAgVGhlIGF0dHJpYnV0
ZSB2YWx1ZSBTSE9VTEQgY29udGFpbiBhIGxhbmd1YWdlIHRhZyBwZXIgQkNQIDQ3IFtSRkM1
NjQ2XQoKNS4xLiAgUmF0aW9uYWxlCgogICBUaGUgZGVjaXNpb24gdG8gYmFzZSB0aGUgcHJv
cG9zYWwgYXQgdGhlIG1lZGlhIG5lZ290aWF0aW9uIGxldmVsLCBhbmQKICAgc3BlY2lmaWNh
bGx5IHRvIHVzZSBTRFAsIGNhbWUgYWZ0ZXIgc2lnbmlmaWNhbnQgZGViYXRlIGFuZAogICBk
aXNjdXNzaW9uLiAgRnJvbSBhbiBlbmdpbmVlcmluZyBzdGFuZHBvaW50LCBpdCBpcyBwb3Nz
aWJsZSB0byBtZWV0CiAgIHRoZSBvYmplY3RpdmVzIHVzaW5nIGEgdmFyaWV0eSBvZiBtZWNo
YW5pc21zLCBidXQgbm9uZSBhcmUgcGVyZmVjdC4KICAgTm9uZSBvZiB0aGUgcHJvcG9zZWQg
YWx0ZXJuYXRpdmVzIHdhcyBjbGVhcmx5IGJldHRlciB0ZWNobmljYWxseSBpbgogICBlbm91
Z2ggd2F5cyB0byB3aW4gb3ZlciBwcm9wb25lbnRzIG9mIHRoZSBvdGhlcnMsIGFuZCBub25l
IHdlcmUKICAgY2xlYXJseSBzbyBiYWQgdGVjaG5pY2FsbHkgYXMgdG8gYmUgZWFzaWx5IHJl
amVjdGVkLiAgQXMgaXMgb2Z0ZW4gdGhlCiAgIGNhc2UgaW4gZW5naW5lZXJpbmcsIGNob29z
aW5nIHRoZSBzb2x1dGlvbiBpcyBhIG1hdHRlciBvZiBiYWxhbmNpbmcKICAgdHJhZGUtb2Zm
cywgYW5kIHVsdGltYXRlbHkgbW9yZSBhIG1hdHRlciBvZiB0YXN0ZSB0aGFuIHRlY2huaWNh
bAogICBtZXJpdC4gIFRoZSB0d28gbWFpbiBwcm9wb3NhbHMgd2VyZSB0byB1c2UgU0RQIGFu
ZCBTSVAuICBTRFAgaGFzIHRoZQogICBhZHZhbnRhZ2UgdGhhdCB0aGUgbGFuZ3VhZ2UgaXMg
bmVnb3RpYXRlZCB3aXRoIHRoZSBtZWRpYSB0byB3aGljaCBpdAogICBhcHBsaWVzLCB3aGls
ZSBTSVAgaGFzIHRoZSBpc3N1ZSB0aGF0IHRoZSBsYW5ndWFnZXMgZXhwcmVzc2VkIG1heSBu
b3QKICAgbWF0Y2ggdGhlIFNEUCBtZWRpYSBuZWdvdGlhdGVkIChmb3IgZXhhbXBsZSwgYSBz
ZXNzaW9uIGNvdWxkCiAgIG5lZ290aWF0ZSB2aWRlbyBhdCB0aGUgU0lQIGxldmVsIGJ1dCBm
YWlsIHRvIG5lZ290aWF0ZSBhbnkgdmlkZW8KICAgbWVkaWEgc3RyZWFtIGF0IHRoZSBTRFAg
bGF5ZXIpLgoKICAgVGhlIG1lY2hhbmlzbSBkZXNjcmliZWQgaGVyZSBmb3IgU0RQIGNhbiBi
ZSBhZGFwdGVkIHRvIG1lZGlhCiAgIG5lZ290aWF0aW9uIHByb3RvY29scyBvdGhlciB0aGFu
IFNEUC4KCjUuMi4gIFRoZSAnaHVtaW50bGFuZy1zZW5kJyBhbmQgJ2h1bWludGxhbmctcmVj
dicgYXR0cmlidXRlcwoKICAgVGhpcyBkb2N1bWVudCBkZWZpbmVzIHR3byBtZWRpYS1sZXZl
bCBhdHRyaWJ1dGVzIHN0YXJ0aW5nIHdpdGgKICAgJ2h1bWludGxhbmcnIChzaG9ydCBmb3Ig
Imh1bWFuIGludGVyYWN0aXZlIGxhbmd1YWdlIikgdG8gbmVnb3RpYXRlCiAgIHdoaWNoIGh1
bWFuIGxhbmd1YWdlIGlzIHVzZWQgaW4gZWFjaCBpbnRlcmFjdGl2ZSBtZWRpYSBzdHJlYW0u
ICBUaGVyZQogICBhcmUgdHdvIGF0dHJpYnV0ZXMsIG9uZSBlbmRpbmcgaW4gIi1zZW5kIiBh
bmQgdGhlIG90aGVyIGluICItcmVjdiIsCiAgIHJlZ2lzdGVyZWQgaW4gU2VjdGlvbiA2IGFu
ZCBkZXNjcmliZWQgaGVyZToKCiAgICAgIGE9aHVtaW50bGFuZy1zZW5kOjxMYW5ndWFnZS1U
YWc+W2FzdGVyaXNrXQogICAgICBhPWh1bWludGxhbmctcmVjdjo8TGFuZ3VhZ2UtVGFnPlth
c3Rlcmlza10KCiAgIEVhY2ggY2FuIGFwcGVhciBtdWx0aXBsZSB0aW1lcyBpbiBhbiBvZmZl
ciBmb3IgYSBtZWRpYSBzdHJlYW0uCgogICBJbiBhbiBvZmZlciwgZWFjaCAnaHVtaW50bGFu
Zy1zZW5kJyBhdHRyaWJ1dGUgaW5kaWNhdGVzIGEgbGFuZ3VhZ2UgdGhlCiAgIG9mZmVyZXIg
aXMgd2lsbGluZyB0byB1c2Ugd2hlbiBzZW5kaW5nIHVzaW5nIHRoZSBtZWRpYSwgYW5kCiAg
ICdodW1pbnRsYW5nLXJlY3YnIGluZGljYXRlcyBhIGxhbmd1YWdlIHRoZSBvZmZlcmVyIGlz
IHdpbGxpbmcgdG8gdXNlIHdoZW4KICAgcmVjZWl2aW5nIHVzaW5nIHRoZSBtZWRpYS4gIFRo
ZSBMYW5ndWFnZS1UYWcgdmFsdWVzIGZyb20gbXVsdGlwbGUgCiAgIGF0dHJpYnV0ZXMgY29u
c3RpdHV0ZSBhIGxpc3Qgb2YgbGFuZ3VhZ2VzIGluIHByZWZlcmVuY2Ugb3JkZXIgcGVyIGRp
cmVjdGlvbiAKICAgKGZpcnN0IGlzIG1vc3QgcHJlZmVycmVkKS4KCgoKR2VsbGVucyAgICAg
ICAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDYsIDIwMTcgICAgICAgICAgICAgICAgIFtQ
YWdlIDZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICBOZWdvdGlhdGluZyBIdW1hbiBMYW5n
dWFnZSAgICAgICAgICBGZWJydWFyeSAyMDE3CgoKICAgIAoJCglXaGVuIGEgbWVkaWEgaXMg
aW50ZW5kZWQgZm9yIGxhbmd1YWdlIHVzZSBpbiBvbmUgZGlyZWN0aW9uIG9ubHkgKHN1Y2gg
CglhcyBhIHVzZXIgd2l0aCBzcGVlY2gtaW1wYWlybWVudCBpcyBzZW5kaW5nIHVzaW5nIHRl
eHQgYW5kIHJlY2VpdmluZyAKCXVzaW5nIGF1ZGlvKSwgZWl0aGVyIGh1bWludGxhbmctc2Vu
ZCBvciBodW1pbnRsYW5nLXJlY3YgTUFZIGJlIG9taXR0ZWQuCglXaGVuIGEgbWVkaWEgaXMg
bm90IHByaW1hcmlseSBpbnRlbmRlZCBmb3IgbGFuZ3VhZ2UgKGZvciBleGFtcGxlLCBhIAoJ
dmlkZW8gb3IgYXVkaW8gc3RyZWFtIGludGVuZGVkIGZvciBiYWNrZ3JvdW5kIG9ubHkpIGJv
dGggU0hPVUxEIGJlIG9taXR0ZWQuCiAgIE90aGVyd2lzZSwgYm90aCBTSE9VTEQgaGF2ZSB0
aGUgc2FtZSB2YWx1ZXMgaW4gdGhlIHNhbWUgb3JkZXIuIFRoZQogICB0d28gU0hPVUxEIE5P
VCBiZSBzZXQgdG8gbGFuZ3VhZ2VzIHdoaWNoIGFyZSBkaWZmaWN1bHQgdG8gbWF0Y2gKICAg
dG9nZXRoZXIgKGUuZy4sIHNwZWNpZnlpbmcgYSBkZXNpcmUgdG8gc2VuZCBhdWRpbyBpbiBI
dW5nYXJpYW4gYW5kCiAgIHJlY2VpdmUgYXVkaW8gaW4gUG9ydHVndWVzZSB3aWxsIG1ha2Ug
aXQgZGlmZmljdWx0IHRvIHN1Y2Nlc3NmdWxseQogICBjb21wbGV0ZSB0aGUgY2FsbCkuCgog
ICBJbiBhbiBhbnN3ZXIsICdodW1pbnRsYW5nLXNlbmQnIGluZGljYXRlcyB0aGUgbGFuZ3Vh
Z2UgdGhlIGFuc3dlcmVyCiAgIHdpbGwgc2VuZCAod2hpY2ggaW4gbW9zdCBjYXNlcyBpcyBv
bmUgb2YgdGhlIGxhbmd1YWdlcyBpbiB0aGUgb2ZmZXIncwogICAnaHVtaW50bGFuZy1yZWN2
JyksIGFuZCAnaHVtaW50bGFuZy1yZWN2JyBpbmRpY2F0ZXMgdGhlIGxhbmd1YWdlCiAgIHRo
ZSBhbnN3ZXJlciBleHBlY3RzIHRvIHJlY2VpdmUgKHdoaWNoIGluIG1vc3QgY2FzZXMgaXMg
b25lIG9mIHRoZQogICBsYW5ndWFnZXMgaW4gdGhlIG9mZmVyJ3MgJ2h1bWludGxhbmctc2Vu
ZCcpLgoKICAgRWFjaCBMYW5ndWFnZS1UYWcgdmFsdWUgTVVTVCBiZSBhIGxhbmd1YWdlIHRh
ZyBwZXIgQkNQIDQ3IFtSRkM1NjQ2XS4gIAogICBCQ1AgNDcgZGVzY3JpYmVzIG1lY2hhbmlz
bXMgZm9yIG1hdGNoaW5nIGxhbmd1YWdlIHRhZ3MuICBOb3RlIHRoYXQgCiAgIFtSRkM1NjQ2
XSBTZWN0aW9uIDQuMSBhZHZpc2VzIHRvICJ0YWcgY29udGVudCB3aXNlbHkiIGFuZCBub3Qg
aW5jbHVkZQogICB1bm5lY2Vzc2FyeSBzdWJ0YWdzLgoKICAgSW4gYW4gb2ZmZXIgb3IgYW5z
d2VyLCBlYWNoIGF0dHJpYnV0ZSB2YWx1ZSBNQVkgaGF2ZSBhIG1vZGlmaWVyIGFwcGVuZGVk
IGFzCiAgIHRoZSBsYXN0IGNoYXJhY3RlciAoYWZ0ZXIgdGhlIExhbmd1YWdlLVRhZykuIFRo
aXMgc3BlY2lmaWNhdGlvbiBkZWZpbmVzIG9uZSAKICAgdmFsdWUgZm9yIHRoZSBtb2RpZmll
cjsgYW4gYXN0ZXJpc2sgKCIqIikuIFRoZSBhc3RlcmlzayBpbmNsdWRlZCBpbiBhIGh1bWlu
dGxhbmcgCiAgIGF0dHJpYnV0ZSB2YWx1ZSBpbiB0aGUgU0RQIGluZGljYXRlcyBhIGxvd2Vy
IHByZWZlcmVuY2UgZm9yIHRoZSBpbmRpY2F0ZWQgCiAgIGxhbmd1YWdlIGFuZCBhIHJlcXVl
c3QgYnkgdGhlIGNhbGxlciB0byBub3QgcmVqZWN0IHRoZSBjYWxsIGlmIHRoZXJlIAogICBp
cyBubyBsYW5ndWFnZSBpbiBjb21tb24uICAKICAgU2VlIFNlY3Rpb24gNS4zIGZvciBtb3Jl
IGluZm9ybWF0aW9uIGFuZCBkaXNjdXNzaW9uLgoKICAgV2hlbiBwbGFjaW5nIGFuIGVtZXJn
ZW5jeSBjYWxsLCBhbmQgaW4gYW55IG90aGVyIGNhc2Ugd2hlcmUgdGhlCiAgIGxhbmd1YWdl
IGNhbm5vdCBiZSBhc3N1bWVkIGZyb20gY29udGV4dCwgZWFjaCBtZWRpYSBzdHJlYW0gaW4g
YW4KICAgb2ZmZXIgcHJpbWFyaWx5IGludGVuZGVkIGZvciBodW1hbiBsYW5ndWFnZSBjb21t
dW5pY2F0aW9uIFNIT1VMRAogICBzcGVjaWZ5IGJvdGggKG9yIGluIHNvbWUgY2FzZXMgYXMg
ZGVzY3JpYmVkIGFib3ZlLCBvbmUgb2YpIHRoZSAKICAgJ2h1bWludGxhbmctc2VuZCcgYW5k
ICdodW1pbnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXMuCgogICBOb3RlIHRoYXQgd2hpbGUgc2ln
bmVkIGxhbmd1YWdlIHRhZ3MgYXJlIHVzZWQgd2l0aCBhIHZpZGVvIHN0cmVhbSB0bwogICBp
bmRpY2F0ZSBzaWduIGxhbmd1YWdlLCBhIHNwb2tlbiBsYW5ndWFnZSB0YWcgZm9yIGEgdmlk
ZW8gc3RyZWFtIGluCiAgIHBhcmFsbGVsIHdpdGggYW4gYXVkaW8gc3RyZWFtIHdpdGggdGhl
IHNhbWUgc3Bva2VuIGxhbmd1YWdlIHRhZwogICBpbmRpY2F0ZXMgYSByZXF1ZXN0IGZvciBh
IHN1cHBsZW1lbnRhbCB2aWRlbyBzdHJlYW0gdG8gc2VlIHRoZQogICBzcGVha2VyLgoKICAg
Q2xpZW50cyBhY3Rpbmcgb24gYmVoYWxmIG9mIGVuZCB1c2VycyBhcmUgZXhwZWN0ZWQgdG8g
c2V0IG9uZSBvciBib3RoCiAgICdodW1pbnRsYW5nLXNlbmQnIGFuZCAnaHVtaW50bGFuZy1y
ZWN2JyBhdHRyaWJ1dGVzIG9uIGVhY2ggbWVkaWEKICAgc3RyZWFtIHByaW1hcmlseSBpbnRl
bmRlZCBmb3IgaHVtYW4gY29tbXVuaWNhdGlvbiBpbiBhbiBvZmZlciB3aGVuCiAgIHBsYWNp
bmcgYW4gb3V0Z29pbmcgc2Vzc2lvbiwgYW5kIGVpdGhlciBpZ25vcmUgb3IgdGFrZSBpbnRv
CiAgIGNvbnNpZGVyYXRpb24gdGhlIGF0dHJpYnV0ZXMgd2hlbiByZWNlaXZpbmcgaW5jb21p
bmcgY2FsbHMsIGJhc2VkIG9uCiAgIGxvY2FsIGNvbmZpZ3VyYXRpb24gYW5kIGNhcGFiaWxp
dGllcy4gIFN5c3RlbXMgYWN0aW5nIG9uIGJlaGFsZiBvZgogICBjYWxsIGNlbnRlcnMgYW5k
IFBTQVBzIGFyZSBleHBlY3RlZCB0byB0YWtlIGludG8gYWNjb3VudCB0aGUgdmFsdWVzCiAg
IHdoZW4gcHJvY2Vzc2luZyBpbmJvdW5kIGNhbGxzLgoKCgpHZWxsZW5zICAgICAgICAgICAg
ICAgICAgRXhwaXJlcyBBdWd1c3QgNiwgMjAxNyAgICAgICAgICAgICAgICAgW1BhZ2UgN10K
DApJbnRlcm5ldC1EcmFmdCAgICAgICAgIE5lZ290aWF0aW5nIEh1bWFuIExhbmd1YWdlICAg
ICAgICAgIEZlYnJ1YXJ5IDIwMTcKCgogICBOb3RlIHRoYXQgbWVkaWEgYW5kIGxhbmd1YWdl
IG5lZ290aWF0aW9uIG1pZ2h0IHJlc3VsdCBpbiBtb3JlIG1lZGlhCiAgIHN0cmVhbXMgYmVp
bmcgYWNjZXB0ZWQgdGhhbiBhcmUgbmVlZGVkIGJ5IHRoZSB1c2VycyBmb3IgbGFuZ3VhZ2Ug
CiAgIGV4Y2hhbmdlIChlLmcuLCBpZiBtb3JlIHByZWZlcnJlZCBhbmQgbGVzcyBwcmVmZXJy
ZWQgY29tYmluYXRpb25zIAogICBvZiBtZWRpYSBhbmQgbGFuZ3VhZ2UgYXJlIGFsbCBhY2Nl
cHRlZCkuIFRoaXMgaXMgbm9ybWFsIGFuZCBhY2NlcHRlZCwKICAgYmVjYXVzZSB0aGUgaHVt
aW50bGFuZyBhdHRyaWJ1dGUgaXMgbm90IGludGVuZGVkIHRvIHJlc3RyaWN0IG1lZGlhCiAg
IHN0cmVhbXMgdG8gYmUgdXNlZCBvbmx5IGZvciBsYW5ndWFnZSBleGNoYW5nZS4KCjUuMy4g
IFByZWZlcmVuY2VzIHdpdGhpbiB0aGUgc2Vzc2lvbgoKICAgSXQgaXMgb2YgaGlnaCBpbXBv
cnRhbmNlIGZvciBhIHNtb290aCBzdGFydCBvZiBhIGNhbGwgdGhhdCB0aGUgCiAgIGFuc3dl
cmluZyBwYXJ0eSBpcyBhbnN3ZXJpbmcgdGhlIGNhbGwgdXNpbmcgdGhlIGJlc3QgbWF0Y2hp
bmcgCiAgIGxhbmd1YWdlKHMpIGFuZCBtb2RhbGl0eShpZXMpIHN1aXRhYmxlIGZvciB0aGUg
Y29udGludWF0aW9uIG9mIHRoZSBjYWxsLiAKICAgU3dpdGNoaW5nIGxhbmd1YWdlIGFuZCBt
b2RhbGl0eSBkdXJpbmcgdGhlIGNhbGwgYnkgYWdyZWVtZW50IGJldHdlZW4gCiAgIHRoZSBw
YXJ0aWNpcGFudHMgaXMgb2Z0ZW4gdGltZSBjb25zdW1pbmcuIFdpdGhvdXQgc3VwcG9ydCBv
ZiBkZXRhaWxlZCAKICAgbGFuZ3VhZ2UgYW5kIG1vZGFsaXR5IG5lZ290aWF0aW9uIHRoZSBw
YXJ0aWNpYW50cyBtYXkgaGF2ZSBhIHRlbmRlbmN5IAogICB0byBjb250aW51ZSB0aGUgY2Fs
bCBpbiB0aGUgaW5pdGlhbCBsYW5ndWFnZSBhbmQgbW9kYWxpdHkgZXZlbiBpZiBhIAogICBt
b3JlIGNvbnZlbmllbnQgY29tbW9uIGxhbmd1YWdlIGFuZCBtb2RhbGl0eSBjb21iaW5hdGlv
biBpcyBhdmFpbGFibGUuIAogICBJbiBvcmRlciB0byBzdXBwb3J0IHRoZSBkZWNpc2lvbiBv
biB3aGljaCBvZiB0aGUgYXZhaWxhYmxlIGxhbmd1YWdlKHMpCiAgIGFuZCBtb2RhbGl0eShp
ZXMpIHRvIHVzZSBpbml0aWFsbHkgaW4gdGhlIGNhbGwsIGEgc2ltcGxlIHR3by1sZXZlbCAK
ICAgcHJlZmVyZW5jZSBpbmRpY2F0b3IgaXMgc3BlY2lmaWVkIGhlcmUgZm9yIGluY2x1c2lv
biBhcyBhIG1vZGlmaWVyIAogICBpbiB0aGUgaHVtaW50bGFuZyBhdHRyaWJ1dGUgdmFsdWVz
LiBUaGUgcHJlZmVyZW5jZSBpbmRpY2F0b3IgaXMgYWxzbwogICB1c2VkIGFzIGFuIGluZGlj
YXRvciB0aGF0IHRoZSBjYWxsIFNIT1VMRCBiZSBlc3RhYmxpc2hlZCBldmVuIGlmIG5vIAog
ICBsYW5ndWFnZSBtYXRjaCBpcyBmb3VuZC4gCgogICBUaGUgYXN0ZXJpc2sgKCIqIikgaXMg
dXNlZCBhcyBhIHByZWZlcmVuY2UgaW5kaWNhdG9yIHdpdGhpbiB0aGUgc2Vzc2lvbi4gCiAg
IExvdyByZWxhdGl2ZSBwcmVmZXJlbmNlIGZvciBhIGxhbmd1YWdlIGFuZCBtb2RhbGl0eSB0
byBiZSB1c2VkIGluIHRoZQogICBzZXNzaW9uIFNIT1VMRCBiZSBpbmRpY2F0ZWQgYnkgYXBw
ZW5kaW5nIGFuIGFzdGVyaXNrIGFmdGVyIHRoZSBsYW5ndWFnZQogICB0YWcgaW4gdGhlIGF0
dHJpYnV0ZSB2YWx1ZS4gVGhpcyBpbmRpY2F0aW9uIGZyb20gdGhlIG9mZmVyaW5nIHBhcnR5
IAogICBTSE9VTEQgYmUgaW50ZXJwcmV0ZWQgYnkgdGhlIGFuc3dlcmluZyBwYXJ0eSBhcyBh
IHJlcXVlc3QgdG8gdXNlIGEKICAgaGlnaGVyIHByZWZlcnJlZCBsYW5ndWFnZSBhbmQgbW9k
YWxpdHkgd2hlbiBhbnN3ZXJpbmcgdGhlIGNhbGwgaWYgCiAgIGF2YWlsYWJsZSwgYnV0IG90
aGVyd2lzZSBhY2NlcHQgYSBsb3dlciBwcmVmZXJyZWQgbGFuZ3VhZ2UgYW5kIAogICBtb2Rh
bGl0eSBjb21iaW5hdGlvbiBpZiB0aGF0IGlzIGF2YWlsYWJsZS4gV2hlbiBzYXRpc2Z5aW5n
IGxhbmd1YWdlcwogICBhbmQgbW9kYWxpdGllcyBpbiB0aGUgb2ZmZXIgaXMgcmVnYXJkZWQg
dG8gYmUgc28gaW1wb3J0YW50IHRoYXQgdGhlIAogICB3aG9sZSBjYWxsIFNIT1VMRCBiZSBy
ZWplY3RlZCBpZiBubyBtYXRjaCBjYW4gYmUgcHJvdmlkZWQgaW4gdGhlIAogICBzZXNzaW9u
IGluIG9uZSBvciBib3RoIGRpcmVjdGlvbnMsIHRoZW4gdGhlIGFzdGVyaXNrIHNoYWxsIG5v
dCBiZSAKICAgYXBwZW5kZWQgb24gYW55IGluZGljYXRlZCBsYW5ndWFnZSBpbiB0aGUgd2hv
bGUgc2Vzc2lvbiBkZXNjcmlwdGlvbi4KICAgRm9yIHRoZSBjYXNlIHdoZW4gbm8gc3BlY2lm
aWMgcHJlZmVyZW5jZSBpcyBkZXNpcmVkLCBidXQgdGhlIG9mZmVyaW5nCiAgIHBhcnR5IGRv
ZXMgbm90IHdhbnQgdGhlIGNhbGwgdG8gYmUgcmVqZWN0ZWQsIGFsbCBpbmRpY2F0ZWQgbGFu
Z3VhZ2VzIAogICBhbmQgbW9kYWxpdGllcyBTSE9VTEQgaGF2ZSBhbiBhc3RlcmlzayBhcHBl
bmRlZC4KCiAgIEluIGFuIGFuc3dlciwgdGhlIGxhbmd1YWdlKHMpIGFuZCBtb2RhbGl0eShp
ZXMpIHRoYXQgdGhlIGFuc3dlcmluZyAKICAgcGFydHkgd2lsbCB1c2UgaW5pdGlhbGx5IGlu
IHRoZSBhbnN3ZXIgU0hPVUxEIGJlIGluZGljYXRlZCB3aXRob3V0IAogICBhbiBhcHBlbmRl
ZCBhc3Rlcmlzay4gQW55IGxhbmd1YWdlIGFuZCBtb2RhbGl0eSBhdmFpbGFibGUgZm9yIGxh
dGVyIAogICB1c2UgaW4gdGhlIHNlc3Npb24gTUFZIGJlIGluZGljYXRlZCBieSBhIGxhbmd1
YWdlIHRhZyB3aXRoIGFuIAogICBhcHBlbmRlZCBhc3Rlcmlzay4KICAgCiAgIEluIHRoZSBj
YXNlIHdoZW4gbW9yZSB0aGFuIHR3byBwYXJ0aWVzIHBhcnRpY2lwYXRlIGluIHRoZSBjYWxs
LCAKICAgdGhlIGxhbmd1YWdlIGFuZCBtb2RhbGl0eSBpbmRpY2F0aW9ucyBwcm92aWRlZCB0
byBlYWNoIHBhcnR5IAogICBTSE9VTEQgYmUgdGhlIHN1bSBvZiB0aGUgaW5kaWNhdGlvbnMg
ZnJvbSB0aGUgb3RoZXIgcGFydGllcy4KICAgCiAgIFRoZSB1c2Ugb2YgdGhlIHByZWZlcmVu
Y2UgaW5kaWNhdG9yIGFzIHNwZWNpZmllZCBhYm92ZSBkb2VzIAogICBub3QgcHJvdmlkZSBm
b3IgZGlzdGluZ3Vpc2hpbmcgYmV0d2VlbiB0aGUgY2FzZSB3aGVuIHR3byBvciAKICAgbW9y
ZSBsYW5ndWFnZS9tb2RhbGl0eSBjb21iaW5hdGlvbnMgaW4gdGhlIHNhbWUgZGlyZWN0aW9u
IAogICBhcmUgZGVzaXJlZCBmb3IgdXNlIHNpbXVsdGFuZW91c2x5IHZlcnN1cyB0aGUgY2Fz
ZSB3aGVuIHR3bwogICBvciBtb3JlIGxhbmd1YWdlL21vZGFsaXR5IGNvbWJpbmF0aW9ucyBm
b3IgdGhlIHNhbWUgZGlyZWN0aW9ucyAKICAgYXJlIHByb3ZpZGVkIGFzIHNlbGVjdGFibGUg
YWx0ZXJuYXRpdmVzIHdpdGhvdXQgc3BlY2lmaWMgCiAgIHByZWZlcmVuY2UgZGlmZmVyZW50
aWF0aW9uLiBUaGUgY29udGV4dCBvciBvdGhlciBzcGVjaWZpY2F0aW9ucyAKICAgbWF5IGlu
dHJvZHVjZSB0aGUgcG9zc2liaWxpdHkgdG8gZGlzdGluZ3Vpc2ggYmV0d2VlbiB0aGVzZSBj
YXNlcy4gCiAgIFdoZW4gYSBwYXJ0eSBpbiBhIGNhbGwgaGFzIG5vIGluZGljYXRpb25zIHRo
YXQgdHdvIG9yIG1vcmUgCiAgIGxhbmd1YWdlL21vZGFsaXR5IGNvbWJpbmF0aW9ucyBmb3Ig
ZWFjaCBkaXJlY3Rpb24gYXJlIGRlc2lyZWQgCiAgIHNpbXVsdGFlb3VzbHkgaW4gdGhlIGNh
bGwsIHRoZSBwYXJ0eSBTSE9VTEQgYXNzdW1lIHRoYXQgCiAgIHNhdGlzZnlpbmcgb25lIGlz
IHN1ZmZpY2llbnQuCiAgIAogICBPdGhlciBzcGVjaWZpY2F0aW9ucyBtYXkgYWRkIG90aGVy
IGF0dHJpYnV0ZSB2YWx1ZSBtb2RpZmllcnMgdGhhbgogICB0aGUgYXN0ZXJpc2suIElmIGFu
IHVua25vd24gbW9kaWZpZXIgaXMgZGV0ZWN0ZWQsIHRoZSBtb2RpZmllcgogICBTSEFMTCBi
ZSBpZ25vcmVkLgogICAKNS40LiAgVW51c3VhbCBpbmRpY2F0aW9ucwoKCiAgIEl0IGlzIHBv
c3NpYmxlIHRvIHNwZWNpZnkgYW4gdW51c3VhbCBpbmRpY2F0aW9ubiB3aGVyZSB0aGUgbGFu
Z3VhZ2UKICAgc3BlY2lmaWVkIGRvZXMgbm90IG1ha2Ugc2Vuc2UgZm9yIHRoZSBtZWRpYSB0
eXBlLCBzdWNoIGFzIHNwZWNpZnlpbmcKICAgYSBzaWduZWQgbGFuZ3VhZ2UgZm9yIGFuIGF1
ZGlvIG1lZGlhIHN0cmVhbS4KCiAgIEFuIG9mZmVyIE1VU1QgTk9UIGJlIGNyZWF0ZWQgd2hl
cmUgdGhlIGxhbmd1YWdlIGRvZXMgbm90IG1ha2Ugc2Vuc2UKICAgZm9yIHRoZSBtZWRpYSB0
eXBlLiAgSWYgc3VjaCBhbiBvZmZlciBpcyByZWNlaXZlZCwgdGhlIHJlY2VpdmVyIFNIT1VM
RCAKICAgaWdub3JlIHRoZSBsYW5ndWFnZSBzcGVjaWZpZWQuCgogICBIb3dldmVyLCB0aGVy
ZSBhcmUgaW5kaWNhdGlvbnMgd2hpY2ggbG9vayBpbGxvZ2ljYWwsIGJ1dCBjYW4gYmUKICAg
YXNzaWduZWQgdmFsaWQgaW50ZXJwcmV0YXRpb25zLgogICAKICAgQSBzcG9rZW4gbGFuZ3Vh
Z2UgdGFnIGZvciBhIHZpZGVvIHN0cmVhbSBpbiBjb25qdW5jdGlvbiB3aXRoIGFuIGF1ZGlv
CiAgIHN0cmVhbSB3aXRoIHRoZSBzYW1lIGxhbmd1YWdlIGluZGljYXRlcyBhIHJlcXVlc3Qg
Zm9yCiAgIHN1cHBsZW1lbnRhbCB2aWRlbyB0byBzZWUgdGhlIHNwZWFrZXIuCiAgIAogICBU
aGVyZSBpcyBubyBkaWZmZXJlbmNlIGJldHdlZW4gbGFuZ3VhZ2UgdGFncyBmb3Igc3Bva2Vu
IGFuZCB3cml0dGVuIAogICBsYW5ndWFnZXMuIFRoZSBzcG9rZW4gb3Igd3JpdHRlbiBsYW5n
dWFnZSB0YWcgaW5kaWNhdGVkIGZvciBhIHZpZGVvCiAgIHN0cmVhbSBjb3VsZCB0aGVyZWZv
cmUgYmUgaW50ZXJwcmV0ZWQgYXMgYSBjYXBhYmlsaXR5IG9yIHJlcXVlc3QgdG8KICAgdXNl
IHRleHQgY2FwdGlvbnMgb3ZlcmxheWVkIG9uIHRoZSB2aWRlbyBzdHJlYW0uIFRoZSBpbnRl
cnByZXRhdGlvbiAKICAgYWNjb3JkaW5nIHRvIHRoaXMgc3BlY2lmaWNhdGlvbiBTSEFMTCBo
b3dldmVyIGJlIHRvIGhhdmUgYSB2aWV3IG9mIAogICB0aGUgc3BlYWtlci4gCiAgIAoKCgoK
CgoKCkdlbGxlbnMgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAg
ICAgICAgICAgICAgICBbUGFnZSA4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3Rp
YXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAgICAgICAgRmVicnVhcnkgMjAxNwoKCjUuNS4gIEV4
YW1wbGVzCgogICBTb21lIGluZm9ybWF0aXZlIGV4YW1wbGVzIGFyZSBzaG93biBiZWxvdy4g
IE9ubHkgdGhlIG1vc3QgZGlyZWN0bHkgCiAgIHJlbGV2YW50IHBvcnRpb25zIG9mIHRoZSBT
RFAgYmxvY2sgYXJlIHNob3duLCBmb3IgY2xhcml0eS4KCjUuNS4xIFByZWZlcmVuY2UgZm9y
IGEgc3Bva2VuIGxhbmd1YWdlIGFuZCBkZXNpcmUgdG8gZmFpbCB0aGUgY2FsbCBpZiBub3Qg
bWV0CgogICBBIGNhbGxpbmcgdXNlciBkb2VzIG9ubHkgd2FudCB0byB1c2Ugc3Bva2VuIFJ1
c3NpYW4gYW5kIHdhbnQgdGhlIGNhbGwgdG8KICAgYmUgcmVqZWN0ZWQgaWYgdGhpcyBwcmVm
ZXJlbmNlIGlzIG5vdCBtZXQuIFZpZGVvIGlzIGFsc28gaW5jbHVkZWQgaW4gCiAgIHRoZSBv
ZmZlciBidXQgbm90IGZvciBsYW5ndWFnZSBjb21tdW5pY2F0aW9uIHB1cnBvc2UuCgogICAg
ICBtPWF1ZGlvIDQ5MTcwIFJUUC9BVlAgMAogICAgICBhPWh1bWludGxhbmctc2VuZDpydQog
ICAgICBhPWh1bWludGxhbmctcmVjdjpydQoKICAgICAgbT12aWRlbyA1MTM3MiBSVFAvQVZQ
IDM0CgogICBUaGUgZGVzaXJlIHRvIGdldCB0aGUgY2FsbCByZWplY3RlZCBpZiB0aGUgbGFu
Z3VhZ2UgcHJlZmVyZW5jZXMgYXJlIAogICBub3QgbWV0IGlzIGluZGljYXRlZCBieSBub3Qg
YXBwZW5kaW5nIGFueSBhc3RlcmlzayBvbiBhbnkgb2YgdGhlIAogICBodW1pbnRsYW5nIGF0
dHJpYnV0ZXMuIFRoZSBhbnN3ZXJpbmcgcGFydHkgaGFzIGNhcGFiaWxpdHkgaW4gc3Bva2Vu
IAogICBSdXNzaWFuLCBidXQgbm8gdmlkZW8gY2FwYWJpbGl0eSBpbiB0aGUgVUUsIHNvIHRo
ZSBhbnN3ZXIgCiAgIHdpbGwgY29udGFpbiB0aGUgZm9sbG93aW5nOgoKICAgICAgbT1hdWRp
byA1NDAwMCBSVFAvQVZQIDAKICAgICAgYT1odW1pbnRsYW5nLXNlbmQ6cnUKICAgICAgYT1o
dW1pbnRsYW5nLXJlY3Y6cnUKCiAgICAgIG09dmlkZW8gMCBSVFAvQVZQIDM0CgkgIAogICAK
CjUuNS4yIFByZWZlcmVuY2UgZm9yIHNwb2tlbiBsYW5ndWFnZSBhbmQgY2FwYWJpbGl0eSBp
biBzaWduIGxhbmd1YWdlCgogICBUaGlzIFNEUCBzaG93cyBwcmVmZXJlbmNlIGZvciBzcG9r
ZW4gRW5nbGlzaCBib3RoIHdheXMuIFRoZSB1c2VyIAogICBhbHNvIGhhcyBrbm93bGVkZ2Ug
aW4gQW1lcmljYW4gc2lnbiBsYW5ndWFnZSBidXQgYnkgaW5kaWNhdGlvbiBvZiAKICAgdGhl
IGFzdGVyaXNrcyBvbiB0aGVzZSBhdHRyaWJ1dGUgdmFsdWVzLCB0aGUgdXNlciBkb2VzIG5v
dCBwcmVmZXIgCiAgIHRoYXQgbW9kYWxpdHkuIFRleHQgaXMgaW5jbHVkZWQgaW4gdGhlIG9m
ZmVyIGJ1dCB3aXRoIG5vIGluZGljYXRpb24KICAgdG8gYmUgdXNlZCBwcmltYXJpbHkgZm9y
IGluaXRpYWwgbGFuZ3VhZ2UgZXhjaGFuZ2UuIAogICBUaGUgY2FsbCBpcyBhbHNvIHJlcXVl
c3RlZCB0byBub3QgYmUgcmVqZWN0ZWQgZXZlbiBpZiBub25lIG9mIHRoZSAKICAgaW5kaWNh
dGVkIGxhbmd1YWdlcyBjYW4gYmUgcHJvdmlkZWQuCgoKCiAgICAgIG09YXVkaW8gNDkxNzAg
UlRQL0FWUCAwCiAgICAgIGE9aHVtaW50bGFuZy1zZW5kOmVuCiAgICAgIGE9aHVtaW50bGFu
Zy1yZWN2OmVuCgogICAgICBtPXZpZGVvIDUxMzcyIFJUUC9BVlAgMzEgMzIKICAgICAgYT1o
dW1pbnRsYW5nLXNlbmQ6YXNlKgogICAgICBhPWh1bWludGxhbmctcmVjdjphc2UqCgoJICBt
PXRleHQgNDU2NzAgUlRQL0FWUCAxMDAgMTAyCgo1LjUuMyBQcmVmZXJlbmNlIGZvciBzcG9r
ZW4gYW5kIGNhcGFiaWxpdHkgZm9yIHdyaXR0ZW4gbGFuZ3VhZ2VzCSAgCgogICBUaGlzIG9m
ZmVyIHNob3dzIHByZWZlcmVuY2UgZm9yIHNwb2tlbiBTcGFuaXNoIGFuZCBCYXNxdWUgaW4g
dGhpcyAKICAgb3JkZXIsIGFuZCBhdCBsb3dlciBwcmVmZXJlbmNlIGEgY2FwYWJpbGl0eSBm
b3Igd3JpdHRlbiBTcGFuaXNoLCAKICAgQmFzcXVlIGFuZCBhbHNvIEVuZ2xpc2guIFZpZGVv
IGlzIGluY2x1ZGUgd2l0aG91dCBhbnkgaW5kaWNhdGlvbiAKICAgb2YgdXNlIGZvciBsYW5n
dWFnZSBjb21tdW5pY2F0aW9uIHB1cnBvc2VzLgogICBUaGUgY2FsbCBpcyBhbHNvIHJlcXVl
c3RlZCB0byBub3QgYmUgcmVqZWN0ZWQgZXZlbiBpZiBub25lIG9mIAogICB0aGVzZSBsYW5n
dWFnZXMgY2FuIGJlIHByb3ZpZGVkLgoJICAKICAgICAgbT1hdWRpbyA0OTI1MCBSVFAvQVZQ
IDIwCiAgICAgIGE9aHVtaW50bGFuZy1zZW5kOmVzCiAgICAgIGE9aHVtaW50bGFuZy1yZWN2
OmVzCiAgICAgIGE9aHVtaW50bGFuZy1zZW5kOmV1CiAgICAgIGE9aHVtaW50bGFuZy1yZWN2
OmV1CgogICAgICBtPXRleHQgNDUwMjAgUlRQL0FWUCAxMDMgMTA0CiAgICAgIGE9aHVtaW50
bGFuZy1zZW5kOmVzKgogICAgICBhPWh1bWludGxhbmctcmVjdjplcyoKICAgICAgYT1odW1p
bnRsYW5nLXNlbmQ6ZXUqCiAgICAgIGE9aHVtaW50bGFuZy1yZWN2OmV1KgogICAgICBhPWh1
bWludGxhbmctc2VuZDplbioKICAgICAgYT1odW1pbnRsYW5nLXJlY3Y6ZW4qCgkgIAoJICBt
PXZpZGVvIDU0MzMyIFJUUC9BVlAgMzIgOTYKCSAgCiAgIEEgY29ycmVzcG9uZGluZyBhbnN3
ZXIgY2FuIGluZGljYXRlIHRoYXQgdGhlIGFuc3dlcmluZyBwYXJ0eSAKICAgaXMgb25seSBj
YXBhYmxlIHRvIG1ha2UgdGhlIGNhbGwgaW4gd3JpdHRlbiBFbmdsaXNoLgogICBUaGUgb3Ro
ZXIgbWVkaWEgYXJlIGFjY2VwdGVkIGJ1dCBub3QgaW50ZW5kZWQgdG8gYmUgdXNlZCBmb3Ig
CiAgIGFueSBkb21pbmF0aW5nIGxhbmd1YWdlIGNvbW11bmljYXRpb24uCgoJICBtPWF1ZGlv
IDYwMDAwIFJUUC9BVlAgMjAJCgkgIAogICAgICBtPXRleHQgNDUwNDAgUlRQL0FWUCAxMDMg
MTA0CiAgICAgIGE9aHVtaW50bGFuZy1yZWN2OmVuCiAgICAgIGE9aHVtaW50bGFuZy1zZW5k
OmVuCSAKCgkgIG09dmlkZW8gNTYwMDAgUlRQL0FWUCAgOTYJICAKCgkgIAo1LjUuNCBQcmVm
ZXJlbmNlIGZvciBzcGVha2luZyBhbmQgcmVjZWl2aW5nIHRleHQKCiAgIEluIHRoaXMgZXhh
bXBsZSBhIEZyZW5jaCB1c2VyIHdpdGggaGVhcmluZyBsb3NzIHByZWZlcnMgdG8gc3BlYWsg
CiAgIGFuZCBwcmVmZXJzIHRvIHJlY2VpdmUgcmVhbC10aW1lIHRleHQuIFRoZSB1c2VyIGFs
c28gYmVuZWZpdHMgCiAgIGZyb20gcmVjZWl2aW5nIHNwb2tlbiBGcmVuY2gsIGJ1dCBkb2Vz
IG5vdCBoYW5kbGUgYSBjb252ZXJzYXRpb24KICAgaW4ganVzdCBzcG9rZW4gRnJlbmNoIHdl
bGwuIFRoZSB1c2VyIGFsc28gZG9lcyBub3QgZmVlbCByYXBpZCAKICAgZW5vdWdoIG9uIHRo
ZSBrZXlib2FyZCwgc28gc2VuZGluZyB0ZXh0IGlzIG5vdCBhbiBhbHRlcm5hdGl2ZS4KICAg
CiAgIFRoZSBjYWxsaW5nIHVzZXIgd291bGQgbGlrZSB0byBpbmRpY2F0ZSB0aGF0IHRoZXJl
IGlzIHZhbHVlIHRvIAogICByZWNlaXZlIHNwb2tlbiBGcmVuY2ggdG9nZXRoZXIgd2l0aCB0
aGUgcmVjaWV2ZWQgdGV4dC4gVGhlIAogICBjdXJyZW50IHNwZWNpZmljYXRpb24gaGFzIG5v
IHdheSB0byBpbmRpY2F0ZSB0aGF0IHByZWZlcmVuY2UsIAogICBzbyBvbmx5IHRoZSBsb3dl
ciBwcmVmZXJlbmNlIGZvciByZWNlaXZlZCBzcG9rZW4gRnJlbmNoIGFzIGFuIAogICBhbHRl
cm5hdGl2ZSBpcyBpbmRpY2F0ZWQuIAogICBUaGUgY2FsbGluZyB1c2VyIHdhbnQgdGhlIGNh
bGwgdG8gZ28gdGhyb3VnaCBldmVuIGlmIHRoZSAKICAgbGFuZ3VhZ2VzIGRvIG5vdCBtYXRj
aC4gVGhpcyBpcyBpbmRpY2F0ZWQgYnkgdGhlIGFzdGVyaXNrIAogICBhcHBlbmRlZCBvbiB0
aGUgbG93ZXIgcHJlZmVyZW5jZSBhdHRyaWJ1dGUgZm9yIHJlY2VpdmVkIEZyZW5jaC4gCgog
ICBXaGVuIGNhbGxpbmcsIHRoZSBvZmZlciBtYXkgYmU6CgogICAgICBtPWF1ZGlvIDQ5MjUw
IFJUUC9BVlAgMjAKICAgICAgYT1odW1pbnRsYW5nLXNlbmQ6ZnIKICAgICAgYT1odW1pbnRs
YW5nLXJlY3Y6ZnIqCgogICAgICBtPXRleHQgNDUwMjAgUlRQL0FWUCAxMDMgMTA0CiAgICAg
IGE9aHVtaW50bGFuZy1yZWN2OmZyCgogCiAgIFRoZSBhbnN3ZXJpbmcgcGFydHkgZGV0ZWN0
cyB0aGUgdHdvIHByZWZlcnJlZCBhdHRyaWJ1dGVzIHdpdGhvdXQKICAgYW4gYXN0ZXJpc2sg
dG8gYmUgdGhlIG1haW4gcHJlZmVycmVkIGxhbmd1YWdlcyBmb3IgdGhlIGNvbnZlcnNhdGlv
biwKICAgYW5kIGhhcyBjYXBhYmlsaXR5IGZvciB0aGlzIGNvbWJpbmF0aW9uLiBUaGUgYW5z
d2VyIHdpbGwgYmU6CgogICAgICBtPWF1ZGlvIDQ5MzAwIFJUUC9BVlAgMjAKICAgICAgYT1o
dW1pbnRsYW5nLXJlY3Y6ZnIKCiAgICAgIG09dGV4dCA0NTYwMCBSVFAvQVZQIDEwMyAxMDQK
ICAgICAgYT1odW1pbnRsYW5nLXNlbmQ6ZnIJICAKCgogICBUaGUgc2FtZSB1c2VyIGlzIGN1
c3RvbWVyIG9mIGEgcmVsYXkgc2VydmljZSB0aGF0IGNhbiBiZSBpbnZva2VkIGlmIAogICB0
aGUgYW5zd2VyIGRvZXMgbm90IHNhdGlzZnkgdGhlIGhpZ2hlc3QgcHJlZmVyZW5jZSBvZiB0
aGUgY2FsbGluZyB1c2VyLiAKICAgSW4gYW5vdGhlciBjYWxsIHN0YXJ0aW5nIHdpdGggdGhl
IHNhbWUgb2ZmZXIsIHRoZSBpbml0aWFsIGFuc3dlciBtYXkgCiAgIGJlIGZyb20gYSB1c2Vy
IHdobyBoYXMgbm8gdGV4dCBjYXBhYmlsaXRpZXMuIEluc3RlYWQgdGhlIGFuc3dlcmluZyAK
ICAgcGFydHkgZGV0ZWN0cyB0aGF0IGFuc3dlcmluZyB3aXRoIHNwb2tlbiBGcmVuY2ggaXMg
YW4gb3B0aW9uIGV2ZW4gCiAgIGlmIGl0IGlzIGxlc3MgcHJlZmVycmVkLiBUaGUgYW5zd2Vy
IGluIHRoaXMgY2FzZSBpbmRpY2F0ZXMgc3Bva2VuIAogICBGcmVuY2ggaW4gYm90aCBkaXJl
Y3Rpb25zLgoKICAgICAgbT1hdWRpbyA0OTMwMCBSVFAvQVZQIDIwCiAgICAgIGE9aHVtaW50
bGFuZy1yZWN2OmZyCgkgIGE9aHVtaW50bGFuZy1zZW5kOmZyCgogICAgICBtPXRleHQgMCBS
VFAvQVZQIDEwMyAxMDQKCiAgIFRoZSBhbnN3ZXIgaXMgYW5hbHl6ZWQgYnkgdGhlIGNhbGxp
bmcgdXNlcidzIFVFIGFuZCB0aGUgbGFjayAKICAgb2YgdGhlIHByZWZlcnJlZCByZWNlaXZl
ZCBGcmVuY2ggdGV4dCBpcyBkZXRlY3RlZC4gVGhlIFVFIAogICBpbnZva2VzIHRoZSByZWxh
eSBzZXJ2aWNlIGFzIGEgdGhpcmQgcGFydHkgaW4gdGhlIGNhbGwsIGluIG9yZGVyIAogICB0
byBnZXQgdGhlIHNwb2tlbiBGcmVuY2ggZnJvbSB0aGUgY2FsbGVkIHVzZXIgdG8gYmUgdHJh
bnNsYXRlZCB0byAKICAgRnJlbmNoIHRleHQuIFRoZSBzcG9rZW4gRnJlbmNoIGZyb20gdGhl
IGFuc3dlcmluZyBwYXJ0eSB3aWxsIGJlIAogICBkZWxpdmVyZWQgdG8gYm90aCB0aGUgY2Fs
bGluZyB1c2VyIGFuZCB0aGUgcmVsYXkgc2VydmljZS4gVGhlIAogICBpbnZvY2F0aW9uIG9m
IHRoZSByZWxheSBzZXJ2aWNlIGlzIGEgc2VwYXJhdGUgYXBwbGljYXRpb24gYWN0aW9uIAog
ICBhbmQgdGhlIHNpZ25hbGluZyBub3QgaW5jbHVkZWQgaGVyZS4gCgkgIAoJCgo2LiAgSUFO
QSBDb25zaWRlcmF0aW9ucwoKICAgSUFOQSBpcyBraW5kbHkgcmVxdWVzdGVkIHRvIGFkZCB0
d28gZW50cmllcyB0byB0aGUgJ2F0dC1maWVsZCAobWVkaWEKICAgbGV2ZWwgb25seSknIHRh
YmxlIG9mIHRoZSBTRFAgcGFyYW1ldGVycyByZWdpc3RyeToKCiAgIENvbnRhY3QgTmFtZTog
IFJhbmRhbGwgR2VsbGVucwogICBDb250YWN0IEVtYWlsIEFkZHJlc3M6ICByZytpZXRmQHJh
bmR5LnBlbnNpdmUub3JnCiAgIEF0dHJpYnV0ZSBOYW1lOiAgaHVtaW50bGFuZy1yZWN2CiAg
IEF0dHJpYnV0ZSBTeW50YXg6CgogICAgICBodW1pbnRsYW5nLXZhbHVlID0gIExhbmd1YWdl
LVRhZyBbIGFzdGVyaXNrIF0KICAgICAgICAgICAgICAgICAgICAgICAgICA7IExhbmd1YWdl
LVRhZyBkZWZpbmVkIGluIFJGQyA1NjQ2CgkgIGFzdGVyaXNrICAgICAgICAgPSAgIioiCgog
ICBBdHRyaWJ1dGUgU2VtYW50aWNzOiAgRGVzY3JpYmVkIGluIFNlY3Rpb24gNS4yLTUuMyBv
ZiBUQkQ6IFRISVMgRE9DVU1FTlQKICAgVXNhZ2UgTGV2ZWw6ICBtZWRpYSwgZGNzYShzdWJw
cm90b2NvbCkKICAgQ2hhcnNldCBEZXBlbmRlbnQ6ICBObwogICBQdXJwb3NlOiAgU2VlIFNl
Y3Rpb24gNS4yLTUuMyBvZiBUQkQ6IFRISVMgRE9DVU1FTlQKICAgTXV4IENhdGVnb3J5OiBO
T1JNQUwKICAgTy9BIFByb2NlZHVyZXM6ICBTZWUgU2VjdGlvbiA1LjItNS4zIG9mIFRCRDog
VEhJUyBET0NVTUVOVAogICBSZWZlcmVuY2U6ICBUQkQ6IFRISVMgRE9DVU1FTlQKCiAgIENv
bnRhY3QgTmFtZTogIFJhbmRhbGwgR2VsbGVucwogICBDb250YWN0IEVtYWlsIEFkZHJlc3M6
ICByZytpZXRmQHJhbmR5LnBlbnNpdmUub3JnCgoKCkdlbGxlbnMgICAgICAgICAgICAgICAg
ICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAgICAgICAgICAgICAgICBbUGFnZSA5XQoMCklu
dGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAgICAg
ICAgRmVicnVhcnkgMjAxNwoKCiAgIEF0dHJpYnV0ZSBOYW1lOiAgaHVtaW50bGFuZy1zZW5k
CiAgIEF0dHJpYnV0ZSBTeW50YXg6CgogICAgICBodW1pbnRsYW5nLXZhbHVlID0gIExhbmd1
YWdlLVRhZyBbIGFzdGVyaXNrIF0KICAgICAgICAgICAgICAgICAgICAgICAgICA7IExhbmd1
YWdlLVRhZyBkZWZpbmVkIGluIFJGQyA1NjQ2CgkgIGFzdGVyaXNrICAgICAgICAgPSAgIioi
CgogICBBdHRyaWJ1dGUgU2VtYW50aWNzOiAgRGVzY3JpYmVkIGluIFNlY3Rpb24gNS4yLTUu
MyBvZiBUQkQ6IFRISVMgRE9DVU1FTlQKICAgVXNhZ2UgTGV2ZWw6ICBtZWRpYSwgZGNzYShz
dWJwcm90b2NvbCkKICAgQ2hhcnNldCBEZXBlbmRlbnQ6ICBObwogICBQdXJwb3NlOiAgU2Vl
IFNlY3Rpb24gNS4yLTUuMyBvZiBUQkQ6IFRISVMgRE9DVU1FTlQKICAgTXV4IENhdGVnb3J5
OiBOT1JNQUwKICAgTy9BIFByb2NlZHVyZXM6ICBTZWUgU2VjdGlvbiA1LjItNS4zIG9mIFRC
RDogVEhJUyBET0NVTUVOVAogICBSZWZlcmVuY2U6ICBUQkQ6IFRISVMgRE9DVU1FTlQKCjcu
ICBTZWN1cml0eSBDb25zaWRlcmF0aW9ucwoKICAgVGhlIFNlY3VyaXR5IENvbnNpZGVyYXRp
b25zIG9mIEJDUCA0NyBbUkZDNTY0Nl0gYXBwbHkgaGVyZS4gIEluCiAgIGFkZGl0aW9uLCBp
ZiB0aGUgJ2h1bWludGxhbmctc2VuZCcgb3IgJ2h1bWludGxhbmctcmVjdicgdmFsdWVzIGFy
ZQogICBhbHRlcmVkIG9yIGRlbGV0ZWQgZW4gcm91dGUsIHRoZSBzZXNzaW9uIGNvdWxkIGZh
aWwgb3IgbGFuZ3VhZ2VzCiAgIGluY29tcHJlaGVuc2libGUgdG8gdGhlIGNhbGxlciBjb3Vs
ZCBiZSBzZWxlY3RlZDsgaG93ZXZlciwgdGhpcyBpcwogICBhbHNvIGEgcmlzayBpZiBhbnkg
U0RQIHBhcmFtZXRlcnMgYXJlIG1vZGlmaWVkIGVuIHJvdXRlLgoKOC4gIFByaXZhY3kgQ29u
c2lkZXJhdGlvbnMKCiAgIExhbmd1YWdlIGFuZCBtZWRpYSBpbmZvcm1hdGlvbiBjYW4gc3Vn
Z2VzdCBhIHVzZXIncyBuYXRpb25hbGl0eSwKICAgYmFja2dyb3VuZCwgYWJpbGl0aWVzLCBk
aXNhYmlsaXRpZXMsIGV0Yy4KCjkuICBDaGFuZ2VzIGZyb20gUHJldmlvdXMgVmVyc2lvbnMK
CiAgIFJGQyBFRElUT1I6IFBsZWFzZSByZW1vdmUgdGhpcyBzZWN0aW9uIHByaW9yIHRvIHB1
YmxpY2F0aW9uLgoKOS4xLiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWlldGYtc2xpbS0uLi4tMDQg
dG8gZHJhZnQtaWV0Zi1zbGltLS4uLi0wNgoKICAgbyAgRGVsZXRlZCBTZWN0aW9uIDMgKCJF
eHBlY3RlZCBVc2UiKQogICBvICBSZXdvcmRlZCBtb2RhbGl0aWVzIGluIEludHJvZHVjdGlv
biBmcm9tICJ2b2ljZSwgdmlkZW8sIHRleHQiIHRvCiAgICAgICJzcG9rZW4sIHNpZ25lZCwg
d3JpdHRlbiIKICAgbyAgUmV3b3JkZWQgdGV4dCBhYm91dCAiaW5jcmVhc2luZ2x5IGZpbmUt
Z3JhaW5lZCBkaXN0aW5jdGlvbnMiIHRvCiAgICAgIGluc3RlYWQgbWVyZWx5IHBvaW50IHRv
IEJDUCA0NyBTZWN0aW9uIDQuMSdzIGFkdmljZSB0byAidGFnCiAgICAgIGNvbnRlbnQgd2lz
ZWx5IiBhbmQgbm90IGluY2x1ZGUgdW5uZWNlc3Nhcnkgc3VidGFncwogICBvICBDaGFuZ2Vk
IElBTkEgcmVnaXN0cmF0aW9uIG9mIG5ldyBTRFAgYXR0cmlidXRlcyB0byBmb2xsb3cgUkZD
IDQ1NjYKICAgICAgdGVtcGxhdGUgd2l0aCBleHRyYSBmaWVsZHMgc3VnZ2VzdGVkIGluIDQ1
NjYtYmlzIChleHBpcmVkIGRyYWZ0KQogICBvICBEZWxldGVkICIoa25vd24gYXMgdm9pY2Ug
Y2Fycnkgb3ZlcikiCiAgIG8gIENoYW5nZWQgdGV4dHVhbCBpbnN0YW5jZWQgb2YgUkZDIDU2
NDYgdG8gQkNQIDQ3LCBhbHRob3VnaCBhY3R1YWwKICAgICAgcmVmZXJlbmNlIHJlbWFpbnMg
UkZDIGR1ZSB0byB4bWwycmZjIGxpbWl0YXRpb25zCgoKCgoKCgpHZWxsZW5zICAgICAgICAg
ICAgICAgICAgRXhwaXJlcyBBdWd1c3QgNiwgMjAxNyAgICAgICAgICAgICAgICBbUGFnZSAx
MF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgIE5lZ290aWF0aW5nIEh1bWFuIExhbmd1YWdl
ICAgICAgICAgIEZlYnJ1YXJ5IDIwMTcKCgo5LjIuICBDaGFuZ2VzIGZyb20gZHJhZnQtaWV0
Zi1zbGltLS4uLi0wMiB0byBkcmFmdC1pZXRmLXNsaW0tLi4uLTAzCgogICBvICBBZGRlZCBF
eGFtcGxlcwogICBvICBBZGRlZCBQcml2YWN5IENvbnNpZGVyYXRpb25zIHNlY3Rpb24KICAg
byAgT3RoZXIgZWRpdG9yaWFsIGNoYW5nZXMgZm9yIGNsYXJpdHkKCjkuMy4gIENoYW5nZXMg
ZnJvbSBkcmFmdC1pZXRmLXNsaW0tLi4uLTAxIHRvIGRyYWZ0LWlldGYtc2xpbS0uLi4tMDIK
CiAgIG8gIERlbGV0ZWQgbW9zdCBvZiBTZWN0aW9uIDQgYW5kIHJlcGxhY2VkIHdpdGggYSB2
ZXJ5IHNob3J0IHN1bW1hcnkKICAgbyAgUmVwbGFjZWQgIndpc2hlcyB0byIgd2l0aCAiaXMg
d2lsbGluZyB0byIgaW4gU2VjdGlvbiA1LjIKICAgbyAgUmV3b3JkZWQgZGVzY3JpcHRpb24g
b2YgYXR0cmlidXRlIHVzYWdlIHRvIGNsYXJpZnkgd2hlbiB0byBzZXQKICAgICAgYm90aCwg
b25seSBvbmUsIG9yIG5laXRoZXIKICAgbyAgRGVsZXRlZCBhbGwgdXNlcyBvZiAiSU1TIgog
ICBvICBPdGhlciBlZGl0b3JpYWwgY2hhbmdlcyBmb3IgY2xhcml0eQoKOS40LiAgQ2hhbmdl
cyBmcm9tIGRyYWZ0LWlldGYtc2xpbS0uLi4tMDAgdG8gZHJhZnQtaWV0Zi1zbGltLS4uLi0w
MQoKICAgbyAgRWRpdG9yaWFsIGNoYW5nZXMgdG8gd29yZGluZyBpbiBTZWN0aW9uIDUuCgo5
LjUuICBDaGFuZ2VzIGZyb20gZHJhZnQtZ2VsbGVucy1zbGltLS4uLi0wMyB0byBkcmFmdC1p
ZXRmLXNsaW0tLi4uLTAwCgogICBvICBVcGRhdGVkIHRpdGxlIHRvIHJlZmxlY3QgV0cgYWRv
cHRpb24KCjkuNi4gIENoYW5nZXMgZnJvbSBkcmFmdC1nZWxsZW5zLXNsaW0tLi4uLTAyIHRv
IGRyYWZ0LWdlbGxlbnMtCiAgICAgIHNsaW0tLi4uLTAzCgogICBvICBSZW1vdmVkIFVzZSBD
YXNlcyBzZWN0aW9uLCBwZXIgZmFjZS10by1mYWNlIGRpc2N1c3Npb24gYXQgSUVURiA5Mwog
ICBvICBSZW1vdmVkIGRpc2N1c3Npb24gb2Ygcm91dGluZywgcGVyIGZhY2UtdG8tZmFjZSBk
aXNjdXNzaW9uIGF0IElFVEYKICAgICAgOTMKCjkuNy4gIENoYW5nZXMgZnJvbSBkcmFmdC1n
ZWxsZW5zLXNsaW0tLi4uLTAxIHRvIGRyYWZ0LWdlbGxlbnMtCiAgICAgIHNsaW0tLi4uLTAy
CgogICBvICBVcGRhdGVkIE5FTkEgdXNhZ2UgbWVudGlvbgogICBvICBSZW1vdmVkIGJhY2tn
cm91bmQgdGV4dCByZWZlcmVuY2UgdG8gZHJhZnQtc2FpbnRhbmRyZS1zaXAteG1wcC0KICAg
ICAgY2hhdC0wNCBzaW5jZSB0aGF0IGRyYWZ0IGV4cGlyZWQKCjkuOC4gIENoYW5nZXMgZnJv
bSBkcmFmdC1nZWxsZW5zLXNsaW0tLi4uLTAwIHRvIGRyYWZ0LWdlbGxlbnMtCiAgICAgIHNs
aW0tLi4uLTAxCgogICBvICBSZXZpc2lvbiB0byBrZWVwIGRyYWZ0IGZyb20gZXhwaXJpbmcK
CjkuOS4gIENoYW5nZXMgZnJvbSBkcmFmdC1nZWxsZW5zLW1tdXNpYy0uLi4tMDIgdG8gZHJh
ZnQtZ2VsbGVucy0KICAgICAgc2xpbS0uLi4tMDAKCiAgIG8gIENoYW5nZWQgbmFtZSBmcm9t
IC1tbXVzaWMtIHRvIC1zbGltLSB0byByZWZsZWN0IHByb3Bvc2VkIFdHIG5hbWUKICAgbyAg
QXMgYSByZXN1bHQgb2YgdGhlIGZhY2UtdG8tZmFjZSBkaXNjdXNzaW9uIGluIFRvcm9udG8s
IHRoZSBTRFAgdnMKICAgICAgU0lQIGlzc3VlIHdhcyByZXNvbHZlZCBieSBnb2luZyBiYWNr
IHRvIFNEUCwgdGFraW5nIG91dCB0aGUgU0lQCgoKCkdlbGxlbnMgICAgICAgICAgICAgICAg
ICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAgICAgICAgICAgICAgIFtQYWdlIDExXQoMCklu
dGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAgICAg
ICAgRmVicnVhcnkgMjAxNwoKCiAgICAgIGhpbnQsIGFuZCBjb252ZXJ0aW5nIHdoYXQgaGFk
IGJlZW4gYSBzZXQgb2YgYWx0ZXJuYXRlIHByb3Bvc2FscwogICAgICBmb3IgdmFyaW91cyB3
YXlzIG9mIGRvaW5nIGl0IHdpdGhpbiBTSVAgaW50byBhbiBpbmZvcm1hdGl2ZSBhbm5leAog
ICAgICBzZWN0aW9uIHdoaWNoIGluY2x1ZGVzIGJhY2tncm91bmQgb24gd2h5IFNEUCBpcyB0
aGUgcHJvcG9zYWwKICAgbyAgQWRkZWQgbWVudGlvbiB0aGF0IGVuYWJsaW5nIGEgbXV0dWFs
bHkgY29tcHJlaGVuc2libGUgbGFuZ3VhZ2UgaXMKICAgICAgYSBnZW5lcmFsIHByb2JsZW0g
b2Ygd2hpY2ggdGhpcyBkb2N1bWVudCBhZGRyZXNzZXMgdGhlIHJlYWwtdGltZQogICAgICBz
aWRlLCB3aXRoIHJlZmVyZW5jZSB0byBbSS1ELmlldGYtc2xpbS1tdWx0aWxhbmdjb250ZW50
XSB3aGljaAogICAgICBhZGRyZXNzZXMgdGhlIG5vbi1yZWFsLXRpbWUgc2lkZS4KCjkuMTAu
ICBDaGFuZ2VzIGZyb20gZHJhZnQtZ2VsbGVucy1tbXVzaWMtLi4uLTAxIHRvIC0wMgoKICAg
byAgQWRkZWQgY2xhcmlmeWluZyB0ZXh0IG9uIGxlYXZpbmcgYXR0cmlidXRlcyB1bnNldCBm
b3IgbWVkaWEgbm90CiAgICAgIHByaW1hcmlseSBpbnRlbmRlZCBmb3IgaHVtYW4gbGFuZ3Vh
Z2UgY29tbXVuaWNhdGlvbiAoZS5nLiwKICAgICAgYmFja2dyb3VuZCBhdWRpbyBvciB2aWRl
bykuCiAgIG8gIEFkZGVkIG5ldyBzZWN0aW9uIEFwcGVuZGl4IEEgKCJBbHRlcm5hdGl2ZSBQ
cm9wb3NhbDogQ2FsbGVyLQogICAgICBwcmVmcyIpIGRpc2N1c3NpbmcgdXNlIG9mIFNJUC1s
ZXZlbCBDYWxsZXItcHJlZnMgaW5zdGVhZCBvZiBTRFAtCiAgICAgIGxldmVsLgoKOS4xMS4g
IENoYW5nZXMgZnJvbSBkcmFmdC1nZWxsZW5zLW1tdXNpYy0uLi4tMDAgdG8gLTAxCgogICBv
ICBSZWxheGVkIGxhbmd1YWdlIG9uIHNldHRpbmcgLXNlbmQgYW5kIC1yZWNlaXZlIHRvIHNh
bWUgdmFsdWVzOwogICAgICBhZGRlZCB0ZXh0IG9uIGxlYXZpbmcgb24gZW1wdHkgdG8gaW5k
aWNhdGUgYXN5bW1ldHJpYyB1c2FnZS4KICAgbyAgQWRkZWQgdGV4dCB0aGF0IGNsaWVudHMg
b24gYmVoYWxmIG9mIGVuZCB1c2VycyBhcmUgZXhwZWN0ZWQgdG8gc2V0CiAgICAgIHRoZSBh
dHRyaWJ1dGVzIG9uIG91dGdvaW5nIGNhbGxzIGFuZCBpZ25vcmUgb24gaW5jb21pbmcgY2Fs
bHMKICAgICAgd2hpbGUgc3lzdGVtcyBvbiBiZWhhbGYgb2YgY2FsbCBjZW50ZXJzIGFuZCBQ
U0FQcyBhcmUgZXhwZWN0ZWQgdG8KICAgICAgdGFrZSB0aGUgYXR0cmlidXRlcyBpbnRvIGFj
Y291bnQgd2hlbiBwcm9jZXNzaW5nIGluY29taW5nIGNhbGxzLgoKOS4xMi4gIENoYW5nZXMg
ZnJvbSBkcmFmdC1nZWxsZW5zLS4uLi0wMiB0byBkcmFmdC1nZWxsZW5zLW1tdXNpYy0uLi4t
MDAKCiAgIG8gIFVwZGF0ZWQgdGV4dCB0byByZWZlciB0byBSRkMgNTY0NiByYXRoZXIgdGhh
biB0aGUgSUFOQSBsYW5ndWFnZQogICAgICBzdWJ0YWdzIHJlZ2lzdHJ5IGRpcmVjdGx5Lgog
ICBvICBNb3ZlZCBkaXNjdXNzaW9uIG9mIGV4aXN0aW5nICdsYW5nJyBhdHRyaWJ1dGUgb3V0
IG9mICJQcm9wb3NlZAogICAgICBTb2x1dGlvbiIgc2VjdGlvbiBhbmQgaW50byBvd24gc2Vj
dGlvbiBub3cgdGhhdCBpdCBpcyBub3QgcGFydCBvZgogICAgICBwcm9wb3NhbC4KICAgbyAg
VXBkYXRlZCB0ZXh0IGFib3V0IGV4aXN0aW5nICdsYW5nJyBhdHRyaWJ1dGUuCiAgIG8gIEFk
ZGVkIGV4YW1wbGUgdXNlIGNhc2VzLgogICBvICBSZXBsYWNlZCBwcm9wb3NlZCBzaW5nbGUg
J2h1bWludGxhbmcnIGF0dHJpYnV0ZSB3aXRoICdodW1pbnRsYW5nLQogICAgICBzZW5kJyBh
bmQgJ2h1bWludGxhbmctcmVjdicgcGVyIEhhcmFsZCdzIHJlcXVlc3QvaW5mb3JtYXRpb24g
dGhhdAogICAgICBpdCB3YXMgYSBtaXN1c2Ugb2YgU0RQIHRvIHVzZSB0aGUgc2FtZSBhdHRy
aWJ1dGUgZm9yIHNlbmRpbmcgYW5kCiAgICAgIHJlY2VpdmluZy4KICAgbyAgQWRkZWQgc2Vj
dGlvbiBkZXNjcmliaW5nIHVzYWdlIGJlaW5nIGFkdmlzb3J5IHZzIHJlcXVpcmVkIGFuZCB0
ZXh0CiAgICAgIGluIGF0dHJpYnV0ZSBzZWN0aW9uLgogICBvICBBZGRlZCBzZWN0aW9uIG9u
IFNJUCAiaGludCIgaGVhZGVyIChub3QgeWV0IG5haWxlZCBkb3duIGJldHdlZW4KICAgICAg
bmV3IGFuZCBleGlzdGluZyBoZWFkZXIpLgogICBvICBBZGRlZCB0ZXh0IGRpc2N1c3Npbmcg
dXNhZ2UgaW4gcG9saWN5LWJhc2VkIHJvdXRpbmcgZnVuY3Rpb24gb3IKICAgICAgdXNlIG9m
IFNJUCBoZWFkZXIgImhpbnQiIGlmIHVuYWJsZSB0byBkbyBzby4KICAgbyAgQWRkZWQgU0hP
VUxEIHRoYXQgdGhlIHZhbHVlIG9mIHRoZSBwYXJhbWV0ZXJzIHN0aWNrIHRvIHRoZSBsYXJn
ZXN0CiAgICAgIGdyYW51bGFyaXR5IG9mIGxhbmd1YWdlIHRhZ3MuCgoKCgpHZWxsZW5zICAg
ICAgICAgICAgICAgICAgRXhwaXJlcyBBdWd1c3QgNiwgMjAxNyAgICAgICAgICAgICAgICBb
UGFnZSAxMl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgIE5lZ290aWF0aW5nIEh1bWFuIExh
bmd1YWdlICAgICAgICAgIEZlYnJ1YXJ5IDIwMTcKCgogICBvICBBZGRlZCB0ZXh0IHRvIElu
dHJvZHVjdGlvbiB0byBiZSB0cnkgYW5kIGJlIG1vcmUgY2xlYXIgYWJvdXQKICAgICAgcHVy
cG9zZSBvZiBkb2N1bWVudCBhbmQgcHJvYmxlbSBiZWluZyBzb2x2ZWQuCiAgIG8gIE1hbnkg
d29yZGluZyBpbXByb3ZlbWVudHMgYW5kIGNsYXJpZmljYXRpb25zIHRocm91Z2hvdXQgdGhl
CiAgICAgIGRvY3VtZW50LgogICBvICBGaWxsZWQgaW4gU2VjdXJpdHkgQ29uc2lkZXJhdGlv
bnMuCiAgIG8gIEZpbGxlZCBpbiBJQU5BIENvbnNpZGVyYXRpb25zLgogICBvICBBZGRlZCB0
byBBY2tub3dsZWRnbWVudHMgdGhvc2Ugd2hvIHBhcnRpY2lwYXRlZCBpbiB0aGUgT3JsYW5k
byBhZC0KICAgICAgaG9jIGRpc2N1c3Npb24gYXMgd2VsbCBhcyB0aG9zZSB3aG8gcGFydGlj
aXBhdGVkIGluIGVtYWlsCiAgICAgIGRpc2N1c3Npb24gYW5kIHNpZGUgb25lLW9uLW9uZSBk
aXNjdXNzaW9ucy4KCjkuMTMuICBDaGFuZ2VzIGZyb20gZHJhZnQtZ2VsbGVucy0uLi4tMDEg
dG8gLTAyCgogICBvICBVcGRhdGVkIHRleHQgZm9yIChwb3NzaWJsZSkgbmV3IGF0dHJpYnV0
ZSAiaHVtaW50bGFuZyIgdG8KICAgICAgcmVmZXJlbmNlIFJGQyA1NjQ2CiAgIG8gIEFkZGVk
IGNsYXJpZnlpbmcgdGV4dCBmb3IgKHBvc3NpYmxlKSByZS11c2Ugb2YgZXhpc3RpbmcgJ2xh
bmcnCiAgICAgIGF0dHJpYnV0ZSBzYXlpbmcgdGhhdCB0aGUgcmVnaXN0cmF0aW9uIHdvdWxk
IGJlIHVwZGF0ZWQgdG8gcmVmbGVjdAogICAgICBkaWZmZXJlbnQgc2VtYW50aWNzIGZvciBt
dWx0aXBsZSB2YWx1ZXMgZm9yIGludGVyYWN0aXZlIHZlcnN1cwogICAgICBub24taW50ZXJh
Y3RpdmUgbWVkaWEuCiAgIG8gIEFkZGVkIGNsYXJpZnlpbmcgdGV4dCBmb3IgKHBvc3NpYmxl
KSBuZXcgYXR0cmlidXRlICJodW1pbnRsYW5nIiB0bwogICAgICBhdHRlbXB0IHRvIGJldHRl
ciBkZXNjcmliZSB0aGUgcm9sZSBvZiBsYW5ndWFnZSB0YWdzIGluIG1lZGlhIGluCiAgICAg
IGFuIG9mZmVyIGFuZCBhbiBhbnN3ZXIuCgo5LjE0LiAgQ2hhbmdlcyBmcm9tIGRyYWZ0LWdl
bGxlbnMtLi4uLTAwIHRvIC0wMQoKICAgbyAgQ2hhbmdlZCBuYW1lIG9mIChwb3NzaWJsZSkg
bmV3IGF0dHJpYnV0ZSBmcm9tICdodW1sYW5nIiB0bwogICAgICAiaHVtaW50bGFuZyIKICAg
byAgQWRkZWQgZGlzY3Vzc2lvbiBvZiBzaWxseSBzdGF0ZSAobGFuZ3VhZ2Ugbm90IGFwcHJv
cHJpYXRlIGZvcgogICAgICBtZWRpYSB0eXBlKQogICBvICBBZGRlZCBWb2ljZSBDYXJyeSBP
dmVyIGV4YW1wbGUKICAgbyAgQWRkZWQgbWVudGlvbiBvZiBtdWx0aWxpbmd1YWwgcGVvcGxl
IGFuZCBtdWx0aXBsZSBsYW5ndWFnZXMKICAgbyAgTWlub3IgdGV4dCBjbGFyaWZpY2F0aW9u
cwoKMTAuICBDb250cmlidXRvcnMKCiAgIEd1bm5hciBIZWxsc3Ryb20gZGVzZXJ2ZXMgc3Bl
Y2lhbCBtZW50aW9uIGZvciBoaXMgcmV2aWV3cywKICAgYXNzaXN0YW5jZSwgYW5kIGVzcGVj
aWFsbHkgZm9yIGNvbnRyaWJ1dGluZyB0aGUgY29yZSB0ZXh0IGluCiAgIEFwcGVuZGl4IEEu
CgoxMS4gIEFja25vd2xlZGdtZW50cwoKICAgTWFueSB0aGFua3MgdG8gQmVybmFyZCBBYm9i
YSwgSGFyYWxkIEFsdmVzdHJhbmQsIEZsZW1taW5nIEFuZHJlYXNlbiwKICAgRnJhbmNvaXMg
QXVkZXQsIEVyaWMgQnVyZ2VyLCBLZWl0aCBEcmFnZSwgRG91ZyBFd2VsbCwgQ2hyaXN0aWFu
CiAgIEdyb3ZlcywgQW5kcmV3IEh1dHRvbiwgSGFkcmllbCBLYXBsYW4sIEFyaSBLZXJhbmVu
LCBKb2huIEtsZW5zaW4sCiAgIFBhdWwgS3l6aXZhdCwgSm9obiBMZXZpbmUsIEFsZXhleSBN
ZWxuaWtvdiwgSmFtZXMgUG9saywgUGV0ZSBSZXNuaWNrLAogICBQZXRlciBTYWludC1BbmRy
ZSwgYW5kIERhbGUgV29ybGV5IGZvciByZXZpZXdzLCBjb3JyZWN0aW9ucywKICAgc3VnZ2Vz
dGlvbnMsIGFuZCBwYXJ0aWNpcGF0aW5nIGluIGluLXBlcnNvbiBhbmQgZW1haWwgZGlzY3Vz
c2lvbnMuCgoKCgoKR2VsbGVucyAgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDYs
IDIwMTcgICAgICAgICAgICAgICAgW1BhZ2UgMTNdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAg
ICBOZWdvdGlhdGluZyBIdW1hbiBMYW5ndWFnZSAgICAgICAgICBGZWJydWFyeSAyMDE3CgoK
MTIuICBSZWZlcmVuY2VzCgoxMi4xLiAgTm9ybWF0aXZlIFJlZmVyZW5jZXMKCiAgIFtSRkMy
MTE5XSAgQnJhZG5lciwgUy4sICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRvIEluZGlj
YXRlCiAgICAgICAgICAgICAgUmVxdWlyZW1lbnQgTGV2ZWxzIiwgQkNQIDE0LCBSRkMgMjEx
OSwKICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDMjExOSwgTWFyY2ggMTk5NywKICAg
ICAgICAgICAgICA8aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzIxMTk+LgoK
ICAgW1JGQzQ1NjZdICBIYW5kbGV5LCBNLiwgSmFjb2Jzb24sIFYuLCBhbmQgQy4gUGVya2lu
cywgIlNEUDogU2Vzc2lvbgogICAgICAgICAgICAgIERlc2NyaXB0aW9uIFByb3RvY29sIiwg
UkZDIDQ1NjYsIERPSSAxMC4xNzQ4Ny9SRkM0NTY2LAogICAgICAgICAgICAgIEp1bHkgMjAw
NiwgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmM0NTY2Pi4KCiAgIFtSRkM1
NjQ2XSAgUGhpbGxpcHMsIEEuLCBFZC4gYW5kIE0uIERhdmlzLCBFZC4sICJUYWdzIGZvciBJ
ZGVudGlmeWluZwogICAgICAgICAgICAgIExhbmd1YWdlcyIsIEJDUCA0NywgUkZDIDU2NDYs
IERPSSAxMC4xNzQ4Ny9SRkM1NjQ2LAogICAgICAgICAgICAgIFNlcHRlbWJlciAyMDA5LCA8
aHR0cDovL3d3dy5yZmMtZWRpdG9yLm9yZy9pbmZvL3JmYzU2NDY+LgoKMTIuMi4gIEluZm9y
bWF0aW9uYWwgUmVmZXJlbmNlcwoKICAgW0ktRC5pZXRmLXNsaW0tbXVsdGlsYW5nY29udGVu
dF0KICAgICAgICAgICAgICBUb21raW5zb24sIE4uIGFuZCBOLiBCb3JlbnN0ZWluLCAiTXVs
dGlwbGUgTGFuZ3VhZ2UKICAgICAgICAgICAgICBDb250ZW50IFR5cGUiLCBkcmFmdC1pZXRm
LXNsaW0tbXVsdGlsYW5nY29udGVudC0wNiAod29yawogICAgICAgICAgICAgIGluIHByb2dy
ZXNzKSwgT2N0b2JlciAyMDE2LgoKICAgW1JGQzMyNjRdICBSb3NlbmJlcmcsIEouIGFuZCBI
LiBTY2h1bHpyaW5uZSwgIkFuIE9mZmVyL0Fuc3dlciBNb2RlbAogICAgICAgICAgICAgIHdp
dGggU2Vzc2lvbiBEZXNjcmlwdGlvbiBQcm90b2NvbCAoU0RQKSIsIFJGQyAzMjY0LAogICAg
ICAgICAgICAgIERPSSAxMC4xNzQ4Ny9SRkMzMjY0LCBKdW5lIDIwMDIsCiAgICAgICAgICAg
ICAgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmMzMjY0Pi4KCiAgIFtSRkMz
ODQwXSAgUm9zZW5iZXJnLCBKLiwgU2NodWx6cmlubmUsIEguLCBhbmQgUC4gS3l6aXZhdCwK
ICAgICAgICAgICAgICAiSW5kaWNhdGluZyBVc2VyIEFnZW50IENhcGFiaWxpdGllcyBpbiB0
aGUgU2Vzc2lvbgogICAgICAgICAgICAgIEluaXRpYXRpb24gUHJvdG9jb2wgKFNJUCkiLCBS
RkMgMzg0MCwKICAgICAgICAgICAgICBET0kgMTAuMTc0ODcvUkZDMzg0MCwgQXVndXN0IDIw
MDQsCiAgICAgICAgICAgICAgPGh0dHA6Ly93d3cucmZjLWVkaXRvci5vcmcvaW5mby9yZmMz
ODQwPi4KCiAgIFtSRkMzODQxXSAgUm9zZW5iZXJnLCBKLiwgU2NodWx6cmlubmUsIEguLCBh
bmQgUC4gS3l6aXZhdCwgIkNhbGxlcgogICAgICAgICAgICAgIFByZWZlcmVuY2VzIGZvciB0
aGUgU2Vzc2lvbiBJbml0aWF0aW9uIFByb3RvY29sIChTSVApIiwKICAgICAgICAgICAgICBS
RkMgMzg0MSwgRE9JIDEwLjE3NDg3L1JGQzM4NDEsIEF1Z3VzdCAyMDA0LAogICAgICAgICAg
ICAgIDxodHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2luZm8vcmZjMzg0MT4uCgpBcHBlbmRp
eCBBLiAgSGlzdG9yaWMgQWx0ZXJuYXRpdmUgUHJvcG9zYWw6IENhbGxlci1wcmVmcwoKICAg
VGhlIGRlY2lzaW9uIHRvIGJhc2UgdGhlIHByb3Bvc2FsIGF0IHRoZSBtZWRpYSBuZWdvdGlh
dGlvbiBsZXZlbCwgYW5kCiAgIHNwZWNpZmljYWxseSB0byB1c2UgU0RQLCBjYW1lIGFmdGVy
IHNpZ25pZmljYW50IGRlYmF0ZSBhbmQKICAgZGlzY3Vzc2lvbi4gIEl0IGlzIHBvc3NpYmxl
IHRvIG1lZXQgdGhlIG9iamVjdGl2ZXMgdXNpbmcgYSB2YXJpZXR5IG9mCiAgIG1lY2hhbmlz
bXMsIGJ1dCBub25lIGFyZSBwZXJmZWN0LiAgVXNpbmcgU0RQIG1lYW5zIGRlYWxpbmcgd2l0
aCB0aGUKICAgY29tcGxleGl0eSBvZiBTRFAsIGFuZCBsZWF2ZXMgb3V0IHJlYWwtdGltZSBz
ZXNzaW9uIHByb3RvY29scyB0aGF0IGRvCiAgIG5vdCB1c2UgU0RQLiAgVGhlIG1ham9yIGFs
dGVybmF0aXZlIHByb3Bvc2FsIHdhcyB0byB1c2UgU0lQLiAgVXNpbmcKCgoKR2VsbGVucyAg
ICAgICAgICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDYsIDIwMTcgICAgICAgICAgICAgICAg
W1BhZ2UgMTRdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICBOZWdvdGlhdGluZyBIdW1hbiBM
YW5ndWFnZSAgICAgICAgICBGZWJydWFyeSAyMDE3CgoKICAgU0lQIGxlYXZlcyBvdXQgbm9u
LVNJUCBzZXNzaW9uIHByb3RvY29scywgYnV0IG1vcmUgZnVuZGFtZW50YWxseSwKICAgd291
bGQgb2NjdXIgYXQgYSBkaWZmZXJlbnQgbGF5ZXIgdGhhbiB0aGUgbWVkaWEgbmVnb3RpYXRp
b24uICBUaGlzCiAgIHJlc3VsdHMgaW4gYSBtb3JlIGZyYWdpbGUgc29sdXRpb24gc2luY2Ug
dGhlIG1lZGlhIG1vZGFsaXR5IGFuZAogICBsYW5ndWFnZSB3b3VsZCBiZSBuZWdvdGlhdGVk
IHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNpZmljIG1lZGlhCiAgIGZvcm1hdHMgKHdo
aWNoIGluaGVyZW50bHkgaW5jbHVkZSB0aGUgbW9kYWxpdHkpIHdvdWxkIGJlIG5lZ290aWF0
ZWQKICAgYXQgYSBkaWZmZXJlbnQgbGV2ZWwgKHR5cGljYWxseSBTRFAsIGVzcGVjaWFsbHkg
aW4gdGhlIGVtZXJnZW5jeQogICBjYWxsaW5nIGNhc2VzKSwgbWFraW5nIGl0IGVhc2llciB0
byBoYXZlIG1pc21hdGNoZXMgKHN1Y2ggYXMgd2hlcmUKICAgdGhlIG1lZGlhIG1vZGFsaXR5
IG5lZ290aWF0ZWQgaW4gU0lQIGRvbid0IG1hdGNoIHdoYXQgd2FzIG5lZ290aWF0ZWQKICAg
dXNpbmcgU0RQKS4KCiAgIEFuIGFsdGVybmF0aXZlIHByb3Bvc2FsIHdhcyB0byB1c2UgdGhl
IFNJUC1sZXZlbCBDYWxsZXIgUHJlZmVyZW5jZXMKICAgbWVjaGFuaXNtIGZyb20gUkZDIDM4
NDAgW1JGQzM4NDBdIGFuZCBSRkMgMzg0MSBbUkZDMzg0MV0uCgogICBUaGUgQ2FsbGVyLXBy
ZWZzIG1lY2hhbmlzbSBpbmNsdWRlcyBhIHByaW9yaXR5IHN5c3RlbTsgdGhpcyB3b3VsZAog
ICBhbGxvdyBkaWZmZXJlbnQgY29tYmluYXRpb25zIG9mIG1lZGlhIGFuZCBsYW5ndWFnZXMg
dG8gYmUgYXNzaWduZWQKICAgZGlmZmVyZW50IHByaW9yaXRpZXMuICBUaGUgZXZhbHVhdGlv
biBhbmQgZGVjaXNpb25zIG9uIHdoYXQgdG8gZG8KICAgd2l0aCB0aGUgY2FsbCBjYW4gYmUg
ZG9uZSBlaXRoZXIgYnkgcHJveGllcyBhbG9uZyB0aGUgY2FsbCBwYXRoLCBvcgogICBieSB0
aGUgYWRkcmVzc2VkIFVBLiAgRXZhbHVhdGlvbiBvZiBhbHRlcm5hdGl2ZXMgZm9yIHJvdXRp
bmcgaXMKICAgZGVzY3JpYmVkIGluIFJGQyAzODQxIFtSRkMzODQxXS4KCkEuMS4gIFVzZSBv
ZiBDYWxsZXIgUHJlZmVyZW5jZXMgV2l0aG91dCBBZGRpdGlvbnMKCiAgIFRoZSBmb2xsb3dp
bmcgd291bGQgYmUgcG9zc2libGUgd2l0aG91dCBhZGRpbmcgYW55IG5ldyByZWdpc3RlcmVk
CiAgIHRhZ3M6CgogICBQb3RlbnRpYWwgY2FsbGVycyBhbmQgcmVjaXBpZW50cyBNQVkgaW5j
bHVkZSBpbiB0aGUgQ29udGFjdCBmaWVsZCBpbgogICB0aGVpciBTSVAgcmVnaXN0cmF0aW9u
cyBtZWRpYSBhbmQgbGFuZ3VhZ2UgdGFncyBhY2NvcmRpbmcgdG8gdGhlCiAgIGpvaW50IGNh
cGFiaWxpdGllcyBvZiB0aGUgVUEgYW5kIHRoZSBodW1hbiB1c2VyIGFjY29yZGluZyB0byBS
RkMgMzg0MAogICBbUkZDMzg0MF0uCgogICBUaGUgbW9zdCByZWxldmFudCBtZWRpYSBjYXBh
YmlsaXR5IHRhZ3MgYXJlICJ2aWRlbyIsICJ0ZXh0IiBhbmQKICAgImF1ZGlvIi4gIEVhY2gg
dGFnIHJlcHJlc2VudHMgYSBjYXBhYmlsaXR5IHRvIHVzZSB0aGUgbWVkaWEgaW4gdHdvLQog
ICB3YXkgY29tbXVuaWNhdGlvbi4KCiAgIExhbmd1YWdlIGNhcGFiaWxpdGllcyBhcmUgZGVj
bGFyZWQgd2l0aCBhIGNvbW1hLXNlcGFyYXRlZCBsaXN0IG9mCiAgIGxhbmd1YWdlcyB0aGF0
IGNhbiBiZSB1c2VkIGluIHRoZSBjYWxsIGFzIHBhcmFtZXRlcnMgdG8gdGhlIHRhZwogICAi
bGFuZ3VhZ2U9Ii4KCiAgIFRoaXMgaXMgYW4gZXhhbXBsZSBvZiBob3cgaXQgaXMgdXNlZCBp
biBhIFNJUCBSRUdJU1RFUjoKCgoKICAgICAgUkVHSVNURVIgICAgdXNlckBleGFtcGxlLm5l
dAogICAgICBDb250YWN0OiAgICA8c2lwOnVzZXIxQGV4YW1wbGUubmV0PiBhdWRpbzsgdmlk
ZW87IHRleHQ7CiAgICAgICAgICAgICAgICAgIGxhbmd1YWdlPSJlbixlcyxhc2UiCgogICBJ
bmNsdWRpbmcgdGhpcyBpbmZvcm1hdGlvbiBpbiBTSVAgUkVHSVNURVIgYWxsb3dzIHByb3hp
ZXMgdG8gYWN0IG9uCiAgIHRoZSBpbmZvcm1hdGlvbi4gIEZvciB0aGUgcHJvYmxlbSBzZXQg
YWRkcmVzc2VkIGJ5IHRoaXMgZG9jdW1lbnQsIGl0CgoKCkdlbGxlbnMgICAgICAgICAgICAg
ICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3ICAgICAgICAgICAgICAgIFtQYWdlIDE1XQoM
CkludGVybmV0LURyYWZ0ICAgICAgICAgTmVnb3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAg
ICAgICAgRmVicnVhcnkgMjAxNwoKCiAgIGlzIG5vdCBhbnRpY2lwYXRlZCB0aGF0IHByb3hp
ZXMgd2lsbCBkbyBzbyB1c2luZyByZWdpc3RyYXRpb24gZGF0YS4KICAgRnVydGhlciwgdGhl
cmUgYXJlIGNsYXNzZXMgb2YgZGV2aWNlcyAoc3VjaCBhcyBjZWxsdWxhciBtb2JpbGUKICAg
cGhvbmVzKSB0aGF0IGFyZSBub3QgYW50aWNpcGF0ZWQgdG8gaW5jbHVkZSB0aGlzIGluZm9y
bWF0aW9uIGluIHRoZWlyCiAgIHJlZ2lzdHJhdGlvbnMuICBIZW5jZSwgdXNlIGluIHJlZ2lz
dHJhdGlvbiBpcyBPUFRJT05BTC4KCiAgIEluIGEgY2FsbCwgYSBsaXN0IG9mIGFjY2VwdGFi
bGUgbWVkaWEgYW5kIGxhbmd1YWdlIGNvbWJpbmF0aW9ucyBpcwogICBkZWNsYXJlZCwgYW5k
IGEgcHJpb3JpdHkgYXNzaWduZWQgdG8gZWFjaCBjb21iaW5hdGlvbi4KCiAgIFRoaXMgaXMg
ZG9uZSBieSB0aGUgQWNjZXB0LUNvbnRhY3QgaGVhZGVyIGZpZWxkLCB3aGljaCBkZWZpbmVz
CiAgIGRpZmZlcmVudCBjb21iaW5hdGlvbnMgb2YgbWVkaWEgYW5kIGxhbmd1YWdlcyBhbmQg
YXNzaWducyBwcmlvcml0aWVzCiAgIGZvciBjb21wbGV0aW5nIHRoZSBjYWxsIHdpdGggdGhl
IFNJUCBVUkkgcmVwcmVzZW50ZWQgYnkgdGhhdCBDb250YWN0LgogICBBIHByaW9yaXR5IGlz
IGFzc2lnbmVkIHRvIGVhY2ggc2V0IGFzIGEgc28tY2FsbGVkICJxLXZhbHVlIiB3aGljaAog
ICByYW5nZXMgZnJvbSAxIChtb3N0IHByZWZlcnJlZCkgdG8gMCAobGVhc3QgcHJlZmVycmVk
KS4KCiAgIFVzaW5nIHRoZSBBY2NlcHQtQ29udGFjdCBoZWFkZXIgZmllbGQgaW4gSU5WSVRF
IHJlcXVlc3RzIGFuZAogICByZXNwb25zZXMgYWxsb3dzIHRoZXNlIGNhcGFiaWxpdGllcyB0
byBiZSBleHByZXNzZWQgYW5kIHVzZWQgZHVyaW5nCiAgIGNhbGwgc2V0LXVwLiAgQ2xpZW50
cyBTSE9VTEQgaW5jbHVkZSB0aGlzIGluZm9ybWF0aW9uIGluIElOVklURQogICByZXF1ZXN0
cyBhbmQgcmVzcG9uc2VzLgoKICAgRXhhbXBsZToKCgoKICAgICAgQWNjZXB0LUNvbnRhY3Q6
ICAgICo7IHRleHQ7IGxhbmd1YWdlPSJlbiI7IHE9MC4yCiAgICAgIEFjY2VwdC1Db250YWN0
OiAgICAqOyB2aWRlbzsgbGFuZ3VhZ2U9ImFzZSI7IHE9MC44CgogICBUaGlzIGV4YW1wbGUg
c2hvd3MgdGhlIGhpZ2hlc3QgcHJlZmVyZW5jZSBleHByZXNzZWQgYnkgdGhlIGNhbGxlciBp
cwogICB0byB1c2UgdmlkZW8gd2l0aCBBbWVyaWNhbiBTaWduIExhbmd1YWdlIChsYW5ndWFn
ZSBjb2RlICJhc2UiKS4gIEFzIGEKICAgZmFsbGJhY2ssIGl0IGlzIGFjY2VwdGFibGUgdG8g
Z2V0IHRoZSBjYWxsIGNvbm5lY3RlZCB3aXRoIG9ubHkKICAgRW5nbGlzaCB0ZXh0IHVzZWQg
Zm9yIGh1bWFuIGNvbW11bmljYXRpb24uICBPdGhlciBtZWRpYSBtYXkgb2YgY291cnNlCiAg
IGJlIGNvbm5lY3RlZCBhcyB3ZWxsLCB3aXRob3V0IGV4cGVjdGF0aW9uIHRoYXQgaXQgd2ls
bCBiZSB1c2FibGUgYnkKICAgdGhlIGNhbGxlciBmb3IgaW50ZXJhY3RpdmUgY29tbXVuaWNh
dGlvbnMgKGJ1dCBtYXkgc3RpbGwgYmUgaGVscGZ1bAogICB0byB0aGUgY2FsbGVyKS4KCiAg
IFRoaXMgc3lzdGVtIHNhdGlzZmllcyBhbGwgdGhlIG5lZWRzIGRlc2NyaWJlZCBpbiB0aGUg
cHJldmlvdXMKICAgY2hhcHRlcnMsIGV4Y2VwdCB0aGF0IGxhbmd1YWdlIHNwZWNpZmljYXRp
b25zIGRvIG5vdCBtYWtlIGFueQogICBkaXN0aW5jdGlvbiBiZXR3ZWVuIHNwb2tlbiBhbmQg
d3JpdHRlbiBsYW5ndWFnZSwgYW5kIHRoYXQgdGhlIG5lZWQKICAgZm9yIGRpcmVjdGlvbmFs
aXR5IGluIHRoZSBzcGVjaWZpY2F0aW9uIGNhbm5vdCBiZSBmdWxmaWxsZWQuCgogICBUbyBz
b21lIGRlZ3JlZSB0aGUgbGFjayBvZiBtZWRpYSBzcGVjaWZpY2F0aW9uIGJldHdlZW4gc3Bl
ZWNoIGFuZAogICB0ZXh0IGluIGxhbmd1YWdlIHRhZ3MgY2FuIGJlIGNvbXBlbnNhdGVkIGJ5
IG9ubHkgc3BlY2lmeWluZyB0aGUKICAgaW1wb3J0YW50IG1lZGl1bSBpbiB0aGUgQWNjZXB0
LUNvbnRhY3QgZmllbGQuCgogICBUaHVzLCBhIHVzZXIgd2hvIHdhbnRzIHRvIHVzZSBFbmds
aXNoIG1haW5seSBmb3IgdGV4dCB3b3VsZCBzcGVjaWZ5OgoKCgogICAgICBBY2NlcHQtQ29u
dGFjdDogICAgKjt0ZXh0O2xhbmd1YWdlPSJlbiI7cT0xLjAKCgoKR2VsbGVucyAgICAgICAg
ICAgICAgICAgIEV4cGlyZXMgQXVndXN0IDYsIDIwMTcgICAgICAgICAgICAgICAgW1BhZ2Ug
MTZdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICBOZWdvdGlhdGluZyBIdW1hbiBMYW5ndWFn
ZSAgICAgICAgICBGZWJydWFyeSAyMDE3CgoKICAgV2hpbGUgYSB1c2VyIHdobyB3YW50cyB0
byB1c2UgRW5nbGlzaCBtYWlubHkgZm9yIHNwZWVjaCBidXQgYWNjZXB0IGl0CiAgIGZvciB0
ZXh0IHdvdWxkIHNwZWNpZnk6CgoKCiAgICAgIEFjY2VwdC1Db250YWN0OiAgICAqO2F1ZGlv
O2xhbmd1YWdlPSJlbiI7cT0wLjgKICAgICAgQWNjZXB0LUNvbnRhY3Q6ICAgICo7dGV4dDts
YW5ndWFnZT0iZW4iO3E9MC4yCgogICBIb3dldmVyLCBhIHVzZXIgd2hvIHdvdWxkIGxpa2Ug
dG8gdGFsaywgYnV0IHJlY2VpdmUgdGV4dCBiYWNrIGhhcyBubwogICB3YXkgdG8gZG8gaXQg
d2l0aCB0aGUgZXhpc3Rpbmcgc3BlY2lmaWNhdGlvbi4KCkEuMi4gIEFkZGl0aW9uYWwgQ2Fs
bGVyIFByZWZlcmVuY2VzIGZvciBBc3ltbWV0cmljIE5lZWRzCgogICBJbiBvcmRlciB0byBi
ZSBhYmxlIHRvIHNwZWNpZnkgYXN5bW1ldHJpYyBwcmVmZXJlbmNlcywgdGhlcmUgYXJlIHR3
bwogICBwb3NzaWJpbGl0aWVzLiAgRWl0aGVyIG5ldyBsYW5ndWFnZSB0YWdzIGluIHRoZSBz
dHlsZSBvZiB0aGUKICAgaHVtaW50bGFuZyBwYXJhbWV0ZXJzIGRlc2NyaWJlZCBhYm92ZSBm
b3IgU0RQIGNvdWxkIGJlIHJlZ2lzdGVyZWQsIG9yCiAgIGFkZGl0aW9uYWwgbWVkaWEgdGFn
cyBkZXNjcmliaW5nIHRoZSBhc3ltbWV0cnkgY291bGQgYmUgcmVnaXN0ZXJlZC4KCkEuMi4x
LiAgQ2FsbGVyIFByZWZlcmVuY2VzIGZvciBBc3ltbWV0cmljIE1vZGFsaXR5IE5lZWRzCgog
ICBUaGUgZm9sbG93aW5nIG5ldyBtZWRpYSB0YWdzIHNob3VsZCBiZSBkZWZpbmVkOgoKICAg
ICAgc3BlZWNoLXJlY2VpdmUKICAgICAgc3BlZWNoLXNlbmQKICAgICAgdGV4dC1yZWNlaXZl
CiAgICAgIHRleHQtc2VuZAogICAgICBzaWduLXNlbmQKICAgICAgc2lnbi1yZWNlaXZlCgog
ICBBIHVzZXIgd2hvIHByZWZlcnMgdG8gdGFsayBhbmQgZ2V0IHRleHQgaW4gcmV0dXJuIGlu
IEVuZ2xpc2ggd291bGQKICAgcmVnaXN0ZXIgdGhlIGZvbGxvd2luZyAoaWYgaW5jbHVkaW5n
IHRoaXMgaW5mb3JtYXRpb24gaW4gcmVnaXN0cmF0aW9uCiAgIGRhdGEpOgoKCgogICAgICBS
RUdJU1RFUiAgICB1c2VyQGV4YW1wbGUubmV0CiAgICAgIENvbnRhY3Q6ICAgIDxzaXA6dXNl
cjFAZXhhbXBsZS5uZXQ+IGF1ZGlvO3RleHQ7c3BlZWNoLXNlbmQ7dGV4dC0KICAgICAgICAg
ICAgICAgICAgcmVjZWl2ZTtsYW5ndWFnZT0iZW4iCgogICBBdCBjYWxsIHRpbWUsIGEgdXNl
ciB3aG8gcHJlZmVycyB0byB0YWxrIGFuZCBnZXQgdGV4dCBpbiByZXR1cm4gaW4KICAgRW5n
bGlzaCB3b3VsZCBzZXQgdGhlIEFjY2VwdC1Db250YWN0IGhlYWRlciBmaWVsZCB0bzoKCgoK
ICAgICAgQWNjZXB0LUNvbnRhY3Q6ICAgICo7IGF1ZGlvOyB0ZXh0OyBzcGVlY2gtcmVjZWl2
ZTsgdGV4dC1zZW5kOwogICAgICAgICAgICAgICAgICAgICAgICAgbGFuZ3VhZ2U9ImVuIjtx
PTAuOAogICAgICBBY2NlcHQtQ29udGFjdDogICAgKjsgdGV4dDsgbGFuZ3VhZ2U9ImVuIjsg
cT0wLjIKCgoKCkdlbGxlbnMgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAy
MDE3ICAgICAgICAgICAgICAgIFtQYWdlIDE3XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAg
TmVnb3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAgICAgICAgRmVicnVhcnkgMjAxNwoKCiAg
IE5vdGUgdGhhdCB0aGUgZGlyZWN0aW9ucyBzcGVjaWZpZWQgaGVyZSBhcmUgYXMgdmlld2Vk
IGZyb20gdGhlIGNhbGxlZQogICBzaWRlIHRvIG1hdGNoIHdoYXQgdGhlIGNhbGxlZSBoYXMg
cmVnaXN0ZXJlZC4KCiAgIEEgYnJpZGdlIGFycmFuZ2VkIGZvciBpbnZva2luZyBhIHJlbGF5
IHNlcnZpY2Ugc3BlY2lmaWNhbGx5IGFycmFuZ2VkCiAgIGZvciBjYXB0aW9uZWQgdGVsZXBo
b255IHdvdWxkIHJlZ2lzdGVyIHRoZSBmb2xsb3dpbmcgZm9yIHN1cHBvcnRpbmcKICAgY2Fs
bGluZyB1c2VyczoKCgoKICAgICAgUkVHSVNURVIgICAgY3RAY3RyZWxheS5uZXQKICAgICAg
Q29udGFjdDogICAgPHNpcDpjdDFAY3RyZWxleS5uZXQ+IGF1ZGlvOyB0ZXh0OyBzcGVlY2gt
cmVjZWl2ZTsKICAgICAgICAgICAgICAgICAgdGV4dC1zZW5kOyBsYW5ndWFnZT0iZW4iCgog
ICBBIGJyaWRnZSBhcnJhbmdlZCBmb3IgaW52b2tpbmcgYSByZWxheSBzZXJ2aWNlIHNwZWNp
ZmljYWxseSBhcnJhbmdlZAogICBmb3IgY2FwdGlvbmVkIHRlbGVwaG9ueSB3b3VsZCByZWdp
c3RlciB0aGUgZm9sbG93aW5nIGZvciBzdXBwb3J0aW5nCiAgIGNhbGxlZCB1c2VyczoKCgoK
ICAgICAgUkVHSVNURVIgICAgY3RAY3RyZWxheS5uZXQKICAgICAgQ29udGFjdDogICAgPHNp
cDpjdDJAY3RyZWxleS5uZXQ+IGF1ZGlvOyB0ZXh0OyBzcGVlY2gtc2VuZDsgdGV4dC0KICAg
ICAgICAgICAgICAgICAgcmVjZWl2ZTsgbGFuZ3VhZ2U9ImVuIgoKICAgQXQgY2FsbCB0aW1l
LCB0aGVzZSBhbHRlcm5hdGl2ZXMgYXJlIGluY2x1ZGVkIGluIHRoZSBsaXN0IG9mIHBvc3Np
YmxlCiAgIG91dGNvbWUgb2YgdGhlIGNhbGwgcm91dGluZyBieSB0aGUgU0lQIHByb3hpZXMg
YW5kIHRoZSBwcm9wZXIgcmVsYXkKICAgc2VydmljZSBpcyBpbnZva2VkLgoKQS4yLjIuICBD
YWxsZXIgUHJlZmVyZW5jZXMgZm9yIEFzeW1tZXRyaWMgTGFuZ3VhZ2UgVGFncwoKICAgQW4g
YWx0ZXJuYXRpdmUgaXMgdG8gcmVnaXN0ZXIgbmV3IGxhbmd1YWdlIHRhZ3MgZm9yIHRoZSBw
dXJwb3NlIG9mCiAgIGFzeW1tZXRyaWMgbGFuZ3VhZ2UgdXNhZ2UuCgogICBJbnN0ZWFkIG9m
IHVzaW5nICJsYW5ndWFnZT0iLCBzaXggbmV3IGxhbmd1YWdlIHRhZ3Mgd291bGQgYmUKICAg
cmVnaXN0ZXJlZDoKCiAgICAgIGh1bWludGxhbmctdGV4dC1yZWN2CiAgICAgIGh1bWludGxh
bmctdGV4dC1zZW5kCiAgICAgIGh1bWludGxhbmctc3BlZWNoLXJlY3YKICAgICAgaHVtaW50
bGFuZy1zcGVlY2gtc2VuZAogICAgICBodW1pbnRsYW5nLXNpZ24tcmVjdgogICAgICBodW1p
bnRsYW5nLXNpZ24tc2VuZAoKICAgVGhlc2UgbGFuZ3VhZ2UgdGFncyB3b3VsZCBiZSB1c2Vk
IGluc3RlYWQgb2YgdGhlIHJlZ3VsYXIKICAgYmlkaXJlY3Rpb25hbCBsYW5ndWFnZSB0YWdz
LCBhbmQgdXNlcnMgd2l0aCBiaWRpcmVjdGlvbmFsCiAgIGNhcGFiaWxpdGllcyBTSE9VTEQg
c3BlY2lmeSB2YWx1ZXMgZm9yIGJvdGggZGlyZWN0aW9ucy4gIFNlcnZpY2VzCiAgIHNwZWNp
ZmljYWxseSBhcnJhbmdlZCBmb3Igc3VwcG9ydGluZyB1c2VycyB3aXRoIGFzeW1tZXRyaWMg
bmVlZHMKICAgU0hPVUxEIHNwZWNpZnkgb25seSB0aGUgYXN5bW1ldHJ5IHRoZXkgc3VwcG9y
dC4KCgoKCkdlbGxlbnMgICAgICAgICAgICAgICAgICBFeHBpcmVzIEF1Z3VzdCA2LCAyMDE3
ICAgICAgICAgICAgICAgIFtQYWdlIDE4XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgTmVn
b3RpYXRpbmcgSHVtYW4gTGFuZ3VhZ2UgICAgICAgICAgRmVicnVhcnkgMjAxNwoKCkF1dGhv
cidzIEFkZHJlc3MKCiAgIFJhbmRhbGwgR2VsbGVucwogICBDb3JlIFRlY2hub2xvZ3kgQ29u
c3VsdGluZwoKICAgRW1haWw6IHJnK2lldGZAcmFuZHkucGVuc2l2ZS5vcmcKCgoKCgoKCgoK
CgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKR2VsbGVucyAgICAgICAgICAg
ICAgICAgIEV4cGlyZXMgQXVndXN0IDYsIDIwMTcgICAgICAgICAgICAgICAgW1BhZ2UgMTld
Cg==
--------------14511186B3059DA30155E67B--


From nobody Mon Feb 13 05:17:21 2017
Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73539129667; Mon, 13 Feb 2017 05:17:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 1t0M00N8YflB; Mon, 13 Feb 2017 05:17:18 -0800 (PST)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 B7969129666; Mon, 13 Feb 2017 05:17:17 -0800 (PST)
X-AuditID: c1b4fb3a-bb7cb98000005e23-4a-58a1b1db6ad5
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.183.81]) by  (Symantec Mail Security) with SMTP id 08.20.24099.BD1B1A85; Mon, 13 Feb 2017 14:17:15 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.76]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.03.0319.002; Mon, 13 Feb 2017 14:16:29 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Paul Wouters <paul@nohats.ca>, Paul Wouters <pwouters@redhat.com>
Subject: Re: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Topic: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
Thread-Index: AQHSg02fz09JgsaxQEyJwWweq6l2mKFhhUMAgADVvICABKaOgA==
Date: Mon, 13 Feb 2017 13:16:28 +0000
Message-ID: <D4C77E98.17E98%christer.holmberg@ericsson.com>
References: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com> <alpine.LRH.2.20.1702092230300.22742@bofh.nohats.ca> <D4C388CF.17C73%christer.holmberg@ericsson.com>
In-Reply-To: <D4C388CF.17C73%christer.holmberg@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.1.161129
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <7C93A738973FC344BE5F5B64AC34F280@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOIsWRmVeSWpSXmKPExsUyM2J7oO7tjQsjDDY1mFts6t/EYvFs43wW i6nLH7NYvL91icni5L57TBYfFj5kcWDzWLLkJ5PH93lMHu/3XWULYI7isklJzcksSy3St0vg ypi2+SxTwQ6mipmPNzA3MG5g6mLk5JAQMJHo/97C3MXIxSEksI5R4saxKSwgCSGBxYwSvxZY dTFycLAJWEh0/9MGCYsIVEu8bu1kAqlnFtjNKPHsyH52kBphAVuJ098UIGrsJJpnf2CDsJ0k Jn5dwQxiswioSnQ3bWEFsXkFrCW+dl+B2ruVUeL88p9gB3EK2EhcWX8E7AZGATGJ76fWgMWZ BcQlbj2ZD3W0gMSSPeeZIWxRiZeP/4ENFRXQk1j+fA0zyD0SAkoS07amQbRqSXz5sY8NwraW ePD4PTOErSgxpfshO8Q9ghInZz5hmcAoPgvJtllI2mchaZ+FpH0WkvYFjKyrGEWLU4uLc9ON jPRSizKTi4vz8/TyUks2MQKj8+CW31Y7GA8+dzzEKMDBqMTDu2HDgggh1sSy4srcQ4wSHMxK IrzlGxZGCPGmJFZWpRblxxeV5qQWH2KU5mBREuc1W3k/XEggPbEkNTs1tSC1CCbLxMEp1cBY +GgKB+/cdmf1Db9+ndjedO+k6ZWMN/dvZd+wCzz98NYklaONp76eu/ExT1Rc7zTD7rio+H2M p17VT65etuyu8UaBSjsbBm71+Lllk2bx6H5vauD73HVuZ+HJU2LaDQJGSrVX7rs5/us7w8z5 dq6pptrrbSpe689pFVla8vU+WNls1debP/GlEktxRqKhFnNRcSIAqy7p5MoCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2TFHujsU4a-HEVGb6TIl3ZkLuTo>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 13:17:19 -0000

SGkgUGF1bCwNCg0KLi4uDQoNCj4+U2VjdGlvbiAxMC4zDQo+Pg0KPj5bSS1ELmlldGYtbW11c2lj
LWR0bHMtc2RwXSBpcyBub3QgYSBwcm9wZXIgcmVmZXJlbmNlIHdpdGggbGluay4NCj4NCj5JqfZs
bCBsb29rIGludG8gdGhhdC4NCg0KSSBoYWQgYSBsb29rIGEgdGhpcywgYnV0IEkgYW0gbm90IHN1
cmUgSSB1bmRlcnN0YW5kIHlvdXIgaXNzdWUuDQoNClJlZ2FyZHMsDQoNCkNocmlzdGVyDQoNCg==


From nobody Mon Feb 13 05:43:57 2017
Return-Path: <talmi@marvell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488EB129588; Mon, 13 Feb 2017 05:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 iwBFVpYO1UaP; Mon, 13 Feb 2017 05:43:53 -0800 (PST)
Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) (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 C12DB1295A1; Mon, 13 Feb 2017 05:43:53 -0800 (PST)
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1DDeAgM028006; Mon, 13 Feb 2017 05:43:53 -0800
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0a-0016f401.pphosted.com with ESMTP id 28j0ura9s4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 05:43:52 -0800
Received: from IL-EXCH01.marvell.com (10.4.102.220) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 13 Feb 2017 15:43:48 +0200
Received: from IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36]) by IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36%20]) with mapi id 15.00.1210.000; Mon, 13 Feb 2017 15:43:48 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AdKF/X9u+WIK+SvpTdCAbZfIxgfsEg==
Date: Mon, 13 Feb 2017 13:43:47 +0000
Message-ID: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.4.102.210]
Content-Type: multipart/alternative; boundary="_000_67ab3d39d55840c8a207e2104e6020cdILEXCH01marvellcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-13_08:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702130134
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x6xk8a45uG1QTdJdjEtVr586xN4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 13:43:56 -0000

--_000_67ab3d39d55840c8a207e2104e6020cdILEXCH01marvellcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGksDQoNCkdvb2QgZGlzY3Vzc2lvbiByZWdhcmRpbmcgdGhlIHRleHQgYWJvdXQgdGhlIGhvcC1i
eS1ob3AgZXh0ZW5zaW9uLg0KDQpJbiBteSBvcGluaW9uIHRoZXJlIGlzIGEgdmFsaWQgdXNlIGNh
c2UgZm9yIGludGVybWVkaWF0ZSBub2RlcyB0aGF0IGluc2VydC9yZW1vdmUvbW9kaWZ5L3Byb2Nl
c3MgaG9wLWJ5LWhvcCBleHRlbnNpb25zLiBFeGFtcGxlczogSU9BTSwgSU5ULg0KU2luY2UgdGhl
cmUgaXMgYSB1c2UgY2FzZSwgSSBiZWxpZXZlIHdlIG5lZWQgZXhwbGljaXQgdGV4dCBhYm91dCBp
bnRlcm1lZGlhdGUgaGFuZGxpbmcgb2YgaG9wLWJ5LWhvcCBleHRlbnNpb25zLg0KDQpUaGlzIFtz
b21ld2hhdF0gcmVtaW5kcyBtZSBvZiB0aGUgZGlzY3Vzc2lvbiBhIGZldyB5ZWFycyBhZ28gYWJv
dXQgdGhlIElQdjYvVURQIHplcm8gY2hlY2tzdW0uIFRoZSBXRyBlbmRlZCB1cCBkZWZpbmluZyB0
aGF0IOKAnFplcm8gY2hlY2tzdW0gaXMgcGVybWl0dGVkIGluIElQdjYvVURQICppZiogW+KApuKA
pi4uXSBhbmQgdGhlIHBvc3NpYmxlIGNvbnNlcXVlbmNlcyBhcmUgW+KApuKApi4uXeKAnS4NCg0K
SSB3b3VsZCBhcmd1ZSB0aGF0IHJlZ2FyZGluZyBob3AtYnktaG9wIGV4dGVuc2lvbiBoYW5kbGlu
ZyB3ZSBhbHNvIG5lZWQgdG8gZGVmaW5lIHRoYXQg4oCcSG9wLWJ5LWhvcCBleHRlbnNpb25zIGNh
biBiZSBpbnNlcnRlZC9yZW1vdmVkL21vZGlmaWVkL3Byb2Nlc3NlZCBieSBpbnRlcm1lZGlhdGUg
bm9kZXMgKmlmKiBb4oCm4oCmLi5dIGFuZCB0aGUgcG9zc2libGUgY29uc2VxdWVuY2VzIGFyZSBb
4oCm4oCmLi5d4oCdLg0KDQpDaGVlcnMsDQpUYWwuDQoNCg0KRnJvbTogaXB2NiBbbWFpbHRvOmlw
djYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1hcmsgU21pdGgNClNlbnQ6IE1vbmRh
eSwgRmVicnVhcnkgMTMsIDIwMTcgMzo1MiBBTQ0KVG86IEJyaWFuIEUgQ2FycGVudGVyDQpDYzog
Nm1hbkBpZXRmLm9yZzsgSUVURiBEaXNjdXNzaW9uIGxpc3Q7IExlZGR5LCBKb2huOyBQZXRlIFJl
c25pY2s7IOelnuaYjumBlOWTiTsgU3VyZXNoIEtyaXNobmFuOyBkcmFmdC1pZXRmLTZtYW4tcmZj
MjQ2MGJpc0B0b29scy5pZXRmLm9yZzsgNm1hbi1jaGFpcnNAaWV0Zi5vcmcNClN1YmplY3Q6IFtF
WFRdIFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQ+IChJ
bnRlcm5ldCBQcm90b2NvbCwgVmVyc2lvbiA2IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJbnRl
cm5ldCBTdGFuZGFyZA0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KDQoNCk9u
IDEzIEZlYi4gMjAxNyAxMTo0MCBhbSwgIkJyaWFuIEUgQ2FycGVudGVyIiA8YnJpYW4uZS5jYXJw
ZW50ZXJAZ21haWwuY29tPG1haWx0bzpicmlhbi5lLmNhcnBlbnRlckBnbWFpbC5jb20+PiB3cm90
ZToNCkpvaG4sDQoNCk9uIDEzLzAyLzIwMTcgMTI6MDUsIExlZGR5LCBKb2huIHdyb3RlOg0KPiBJ
4oCZbSB0cnlpbmcgdG8gdW5kZXJzdGFuZCBob3cgYSBiYW4gb2YgdGhpcyBmdW5jdGlvbmFsaXR5
IHdvdWxkIHdvcmsuICBJcyBpdCB0YXJnZXRlZCBhdCB2ZW5kb3IgcHJvZHVjdHMsIHByZWNsdWRp
bmcgdGhlbSBmcm9tIGltcGxlbWVudGluZyB0aGUgZnVuY3Rpb25hbGl0eT8NCkl0J3MgdGFyZ2V0
dGVkIGF0IGludGVyb3BlcmFiaWxpdHkgYWNyb3NzIHRoZSBJbnRlcm5ldC4gV2UgY2FuIG5ldmVy
IHN0b3ANCnBlb3BsZSBkb2luZyB3aGF0ZXZlciB0aGV5IHBsZWFzZSBpbnNpZGUgYSBwcml2YXRl
IGRvbWFpbiwgb2J2aW91c2x5Lg0KQXMgYWx3YXlzLCB0aGVyZSBhcmUgbm8gcHJvdG9jb2wgcG9s
aWNlLg0KDQo+IElmIHRoZXJlIGlzIGEgdGVjaG5pY2FsIHByb2JsZW0gdGhhdCBjYW4gYmUgc29s
dmVkIGJ5IHVzaW5nIEVIIGluc2VydGlvbiB3aXRoaW4gYSBkb21haW4gd2hlcmUgdGhlcmUgYXJl
IG5vIGhhcm1mdWwgc2lkZSBlZmZlY3RzLCBpdCBzaG91bGQgYmUgYWJsZSB0byBiZSB1c2VkLg0K
PiBJbiBhIHNvZnR3YXJlIG5ldHdvcmtpbmcgd29ybGQgd2hlcmUgZnVuY3Rpb25hbGl0eSBpcyBi
ZWluZyBkZXBsb3llZCB0aGF0IGlzIG5vdCBmcm9tIHRyYWRpdGlvbmFsIG5ldHdvcmsgdmVuZG9y
czsgc29sdXRpb25zIHRoYXQgc29sdmUgcHJvYmxlbXMgZWZmaWNpZW50bHkgd2lsbCBnZXQgZGVw
bG95ZWQuDQpXZSBoYWQgYSBsb3Qgb2YgdGhpcyBjb252ZXJzYXRpb24gaW4gYSBzbGlnaHRseSBk
aWZmZXJlbnQgZm9ybSBwcmlvciB0bw0KUkZDIDY0MzcuIEl0IHByb3ZlZCBpbXBvc3NpYmxlIHRv
IHNwZWNpZnkgImxvY2FsIGRvbWFpbiIgcnVsZXMgdGhhdCBjb3VsZA0KcmVhY2ggY29uc2Vuc3Vz
LiBJIHRoaW5rIHdlJ2QgaGF2ZSB0aGUgc2FtZSBwcm9ibGVtIHRyeWluZyB0byB3cml0ZSBydWxl
cw0KZm9yIGhlYWRlciBpbnNlcnRpb24vZGVsZXRpb24gd2l0aGluIGEgZG9tYWluLiBCdXQgaW4g
YW55IGNhc2UsIHRoYXQgaXNuJ3QNCnRoZSB0YXJnZXQgZm9yIFJGQzI0NjBiaXM6IHRoZSB0YXJn
ZXQgaXMgdGhlIEludGVybmV0Lg0KDQpXZSBhbHNvIGtub3cgdGhhdCB0aGlzIHN0YXRlbWVudCBm
cm9tIFJGQzE5MTggaGFzbid0IGJlZW4gMTAwJSBlZmZlY3RpdmU6DQoNCg0KDQogICBCZWNhdXNl
IHByaXZhdGUgYWRkcmVzc2VzIGhhdmUgbm8gZ2xvYmFsIG1lYW5pbmcsIHJvdXRpbmcgaW5mb3Jt
YXRpb24NCg0KICAgYWJvdXQgcHJpdmF0ZSBuZXR3b3JrcyBzaGFsbCBub3QgYmUgcHJvcGFnYXRl
ZCBvbiBpbnRlci1lbnRlcnByaXNlDQoNCiAgIGxpbmtzLCBhbmQgcGFja2V0cyB3aXRoIHByaXZh
dGUgc291cmNlIG9yIGRlc3RpbmF0aW9uIGFkZHJlc3Nlcw0KDQogICBzaG91bGQgbm90IGJlIGZv
cndhcmRlZCBhY3Jvc3Mgc3VjaCBsaW5rcy4NCg0KYW5kIHdlIHN0aWxsIGRvbid0IGhhdmUgZW5v
dWdoIGRlcGxveW1lbnQgb2YgQkNQMzggd2hpY2ggd291bGQgYWxzbyBoZWxwIGVuZm9yY2UgdGhh
dC4NCg0KSWYgaXQgaXMgcG9zc2libGUgdG8gcGx1ZyBhIGRldmljZSBpbnRvIHRoZSBJbnRlcm5l
dCBJIHRoaW5rIGl0IGlzIGJldHRlciB0byBhc3N1bWUgc29tZWJvZHkgcHJvYmFibHkgd2lsbCAo
YW5kIHlvdSB3b24ndCBiZSB0aGVyZSB0byBzdG9wIHRoZW0pIGFuZCBkZXNpZ24gdG8gdGhhdCBh
c3N1bXB0aW9uLg0KDQooQWxsIHRoZSByZWNlbnQgIklvVCIgYm90bmV0cyBhbmQgY29ycmVzcG9u
ZGluZyBhdHRhY2tzIGFyZSBhIHJlc3VsdCBvZiBhc3N1bWluZyB0aG9zZSBkZXZpY2VzIHdpbGwg
b25seSBiZSBjb25uZWN0ZWQgdG8gUHJpdmF0ZSBJbnRlcm5ldHMsIGFuZCB0aGVyZWZvcmUgdGhl
eSBkb24ndCBoYXZlIHRvIGJlIGluZGl2aWR1YWxseSAiSW50ZXJuZXQgcHJvb2YiIChjb25jZXB0
dWFsbHkgc2ltaWxhciB0byBhICJ3YXRlciBwcm9vZiIgd2F0Y2gpLikNCg0KUmVnYXJkcywNCk1h
cmsuDQoNCg0KDQogICAgQnJpYW4NCg0KPg0KPiBKb2huIExlZGR5DQo+DQo+IEZyb206IGlldGYg
PGlldGYtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86aWV0Zi1ib3VuY2VzQGlldGYub3JnPj4gb24g
YmVoYWxmIG9mICJFcmljIFZ5bmNrZSAoZXZ5bmNrZSkiIDxldnluY2tlQGNpc2NvLmNvbTxtYWls
dG86ZXZ5bmNrZUBjaXNjby5jb20+Pg0KPiBEYXRlOiBTdW5kYXksIEZlYnJ1YXJ5IDEyLCAyMDE3
IGF0IDM6NTYgUE0NCj4gVG86IFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNoLmtyaXNobmFuQGdtYWls
LmNvbTxtYWlsdG86c3VyZXNoLmtyaXNobmFuQGdtYWlsLmNvbT4+LCDnpZ7mmI7pgZTlk4kgPGpp
bm1laUB3aWRlLmFkLmpwPG1haWx0bzpqaW5tZWlAd2lkZS5hZC5qcD4+DQo+IENjOiAiNm1hbkBp
ZXRmLm9yZzxtYWlsdG86Nm1hbkBpZXRmLm9yZz4iIDw2bWFuQGlldGYub3JnPG1haWx0bzo2bWFu
QGlldGYub3JnPj4sIElFVEYgRGlzY3Vzc2lvbiBsaXN0IDxpZXRmQGlldGYub3JnPG1haWx0bzpp
ZXRmQGlldGYub3JnPj4sIFBldGUgUmVzbmljayA8cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbTxt
YWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbT4+LCAiZHJhZnQtaWV0Zi02bWFuLXJmYzI0
NjBiaXNAdG9vbHMuaWV0Zi5vcmc8bWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRv
b2xzLmlldGYub3JnPiIgPGRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYub3Jn
PG1haWx0bzpkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZz4+LCAiNm1h
bi1jaGFpcnNAaWV0Zi5vcmc8bWFpbHRvOjZtYW4tY2hhaXJzQGlldGYub3JnPiIgPDZtYW4tY2hh
aXJzQGlldGYub3JnPG1haWx0bzo2bWFuLWNoYWlyc0BpZXRmLm9yZz4+DQo+IFN1YmplY3Q6IFJl
OiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQ+IChJbnRlcm5l
dCBQcm90b2NvbCwgVmVyc2lvbiA2IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJbnRlcm5ldCBT
dGFuZGFyZA0KPg0KPiBTdXJlc2gsIEppbm1laSBhbmQgRmVybmFuZG8sDQo+DQo+IEkgZnVsbHkg
YWdyZWUgd2l0aCB5b3UgU3VyZXNoLCB0aGUgZ29hbCBvZiBhbiBJRVRGIGxhc3QgY2FsbCBpcyB0
byBnZXQgTkVXIGRpc2N1c3Npb24gYW5kIHRvIHJlLWRvIHRoZSBsZW5ndGh5IGRpc2N1c3Npb25z
IHdlIGhhZCBvbiA2TUFOIFdHLg0KPg0KPiAtw6lyaWMNCj4NCj4gRnJvbTogaXB2NiA8aXB2Ni1i
b3VuY2VzQGlldGYub3JnPG1haWx0bzppcHY2LWJvdW5jZXNAaWV0Zi5vcmc+PiBvbiBiZWhhbGYg
b2YgU3VyZXNoIEtyaXNobmFuIDxzdXJlc2gua3Jpc2huYW5AZ21haWwuY29tPG1haWx0bzpzdXJl
c2gua3Jpc2huYW5AZ21haWwuY29tPj4NCj4gRGF0ZTogU2F0dXJkYXkgMTEgRmVicnVhcnkgMjAx
NyBhdCAwNzoxMQ0KPiBUbzog56We5piO6YGU5ZOJIDxqaW5tZWlAd2lkZS5hZC5qcDxtYWlsdG86
amlubWVpQHdpZGUuYWQuanA+Pg0KPiBDYzogIjZtYW5AaWV0Zi5vcmc8bWFpbHRvOjZtYW5AaWV0
Zi5vcmc+IiA8Nm1hbkBpZXRmLm9yZzxtYWlsdG86Nm1hbkBpZXRmLm9yZz4+LCBJRVRGIERpc2N1
c3Npb24gbGlzdCA8aWV0ZkBpZXRmLm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4+LCBQZXRlIFJl
c25pY2sgPHByZXNuaWNrQHF0aS5xdWFsY29tbS5jb208bWFpbHRvOnByZXNuaWNrQHF0aS5xdWFs
Y29tbS5jb20+PiwgRmVybmFuZG8gR29udCA8ZmdvbnRAc2k2bmV0d29ya3MuY29tPG1haWx0bzpm
Z29udEBzaTZuZXR3b3Jrcy5jb20+PiwgImRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xz
LmlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9y
Zz4iIDxkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZzxtYWlsdG86ZHJh
ZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmc+PiwgIjZtYW4tY2hhaXJzQGll
dGYub3JnPG1haWx0bzo2bWFuLWNoYWlyc0BpZXRmLm9yZz4iIDw2bWFuLWNoYWlyc0BpZXRmLm9y
ZzxtYWlsdG86Nm1hbi1jaGFpcnNAaWV0Zi5vcmc+Pg0KPiBTdWJqZWN0OiBSZTogTGFzdCBDYWxs
OiA8ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXMtMDgudHh0PiAoSW50ZXJuZXQgUHJvdG9jb2ws
IFZlcnNpb24gNiAoSVB2NikgU3BlY2lmaWNhdGlvbikgdG8gSW50ZXJuZXQgU3RhbmRhcmQNCj4N
Cj4gSGkgSmlubWVpLA0KPg0KPiBPbiBGZWIgMTAsIDIwMTcgMToyMyBQTSwgIuelnuaYjumBlOWT
iSIgPGppbm1laUB3aWRlLmFkLmpwPG1haWx0bzpqaW5tZWlAd2lkZS5hZC5qcD48bWFpbHRvOmpp
bm1laUB3aWRlLmFkLmpwPG1haWx0bzpqaW5tZWlAd2lkZS5hZC5qcD4+PiB3cm90ZToNCj4gQXQg
VGh1LCA5IEZlYiAyMDE3IDE4OjMwOjExIC0wMzAwLA0KPiBGZXJuYW5kbyBHb250IDxmZ29udEBz
aTZuZXR3b3Jrcy5jb208bWFpbHRvOmZnb250QHNpNm5ldHdvcmtzLmNvbT48bWFpbHRvOmZnb250
QHNpNm5ldHdvcmtzLmNvbTxtYWlsdG86ZmdvbnRAc2k2bmV0d29ya3MuY29tPj4+IHdyb3RlOg0K
Pg0KPiBXaGlsZSBJIGxhcmdlbHkgYWdyZWUgd2l0aCBGZXJuYW5kbyBvbiBldmVyeXRoaW5nIGhl
IHNhaWQsIEkgaGF2ZSB0bw0KPiBhZG1pdCBtb3N0IG9mIHRoZSBwb2ludHMgYXJlIGp1c3QgcmVw
ZWF0ZWQgZnJvbSB0aGUgNm1hbiBkaXNjdXNzaW9uLA0KPiBhbmQgd29uJ3QgZ2V0IHVzIGFueXdo
ZXJlIG5ldyBieSBkaXNjdXNzaW5nIHRoZXNlIGFnYWluIGF0IHRoaXMgcG9pbnQuDQo+IEkgZ3Vl
c3MgdGhlIG9ubHkgbmV3IGlucHV0IGZvciB0aGUgSUVURiBsYXN0IGNhbGwgaXMgdGhpczoNCj4N
Cj4+IDIpIEhvd2V2ZXIsIHNvbWUgZm9sa3MgY2FtZSB1cCB3aXRoIHByb3Bvc2FscyB0byBpbnNl
cnQgRUgsIG9uIHRoZSBiYXNpcw0KPj4gdGhhdCAiUkZDMjQ2MCBkb2VzIG5vdCBleHBsaWNpdGx5
IGJhbiBFSCBpbnNlcnRpb24iLiBJZiB0aGVyZSdzIHBlb3BsZQ0KPj4gYXJndWluZyB0aGF0LCB3
ZSBjbGVhcmx5IG5lZWQgdG8gbWFrZSB0aGlzIGNsZWFyIGluIHRoZSBzcGVjLg0KPj4NCj4+IDMp
IFRoZXJlIHdhcyBhIGNvbnNlbnN1cyBjYWxsLCB5ZXMuIFdoZW4gdGhlIGNhbGwgd2FzIG1hZGUg
b24gdGhlDQo+PiBtYWlsaW5nLWxpc3QsIHRoZSB2YXN0IG1ham9yaXR5IG9mIHN1cHBvcnRlcnMg
b2YgImxldCdzIGtlZXAgdGhlDQo+PiBhbWJpZ3VpdHkiIHdlcmUgZm9sa3MgZnJvbSB0aGUgc2Ft
ZSBjb21wYW55IGFzICIyKSIuIEkgaGF2ZSBubyBpZGVhIGlmDQo+PiB0aGlzIGNoYW5nZXMgKG9y
IG5vdCkgImNvbnNlbnN1cyIuLi4gYnV0IHRoaXMgaXMgY2xlYXJseSBhbiBpbXBvcnRhbnQNCj4+
IGRhdGFwb2ludC4NCj4gQWx0aG91Z2ggSSBkb24ndCB3YW50IHRvIHBvaW50IGEgZmluZ2VyIGF0
IHBhcnRpY3VsYXIgcGVvcGxlIG9yDQo+IG9yZ2FuaXphdGlvbnMgd2l0aG91dCBhbiBldmlkZW5j
ZSwgSSBndWVzcyBub3QgYSBzbWFsbCBudW1iZXIgb2YgNm1hbg0KPiBwYXJ0aWNpcGFudHMgKG5v
dCBvbmx5IHRob3NlIHdobyBleHBsaWNpdGx5IHNwb2tlIHVwIGhlcmUpIHN1c3BlY3RlZA0KPiB0
aGF0IHRoZSBkZWNpc2lvbiBwcm9jZXNzIHdhcyBiaWFzZWQgd2l0aCB0aGUgaW5mbHVlbmNlIG9m
IGEgbGFyZ2UgYW5kDQo+IHBvd2VyZnVsIG9yZ2FuaXphdGlvbiBhbmQgdGhlIHByb2Nlc3MgYW5k
IHJlc3VsdGluZyAiY29uc2Vuc3VzIiB3YXMNCj4gbm90IHJlYWxseSBhIGZhaXIgb25lLiAgQW5k
IEknbSBub3QgYW4gZXhjZXB0aW9uIHRvIGl0IC0gaW4gZmFjdCwgaXQNCj4gd2FzIHNvIHVuYmVs
aWV2YWJsZSB0byBtZSB0aGF0IHdlIGNhbid0IGNsYXJpZnkgYW4gYW1iaWd1aXR5IGV2ZW4gd2hl
bg0KPiB3ZSB3ZXJlIGFsc28gb3BlbiBmb3IgZnV0dXJlIGV4dGVuc2lvbnMsIHRoYXQgSSBjb3Vs
ZG4ndCB0aGluayBvZg0KPiBvdGhlciByZWFzb25zIHRoYW4gYSBjb21wYW55IGFnZW5kYS4NCj4N
Cj4gT2YgY291cnNlLCBpdCdzIHF1aXRlIHBvc3NpYmxlIHRoYXQgaXQgd2FzIGp1c3QgYSBjb2lu
Y2lkZW5jZSB0aGF0DQo+IG1hbnkgcGVvcGxlIHdpdGggdGhlIHNhbWUgb3JnYW5pemF0aW9uIGdl
bnVpbmVseSB0aG91Z2h0IHdlIHNob3VsZA0KPiBsZWF2ZSBpdCBhbWJpZ3VvdXMgd2hpbGUgbWFu
eSBvdGhlcnMgc3Ryb25nbHkgdGhvdWdodCB3ZSBzaG91bGQNCj4gY2xhcmlmeSBpdCBidXQgZmV3
IChpZiBub3Qgbm8pIHBlb3BsZSBmcm9tIHRoYXQgb3JnYW5pemF0aW9uIHN1cHBvcnRlZA0KPiB0
aGUgY2xhcmlmaWNhdGlvbi4gIEJ1dCBJIGRvbid0IHRoaW5rIHdlIGNhbiBwcm92ZSBpdCBlaXRo
ZXIgd2F5Lg0KPg0KPiBCdXQgYXMgRmVybmFuZG8gc2FpZCwgSSBiZWxpZXZlIHRoaXMgcG9pbnQg
KGFuZCB0aGF0IHNldmVyYWwsIGFuZA0KPiBhcmd1YWJseSBtb3JlLCBwYXJ0aWNpcGFudHMgc3Vz
cGVjdGVkIGl0KSBzaG91bGQgYmUgaW5jbHVkZWQgaW4gbWFraW5nDQo+IHRoZSBkZWNpc2lvbiBh
dCB0aGUgSUVTRyBhbmQgYXQgdGhlIElFVEYgbGFzdCBjYWxsLiAgQW5kLCB3aGF0ZXZlciB0aGUN
Cj4gZGVjaXNpb24sIGl0IHdvdWxkIGJlIG1vcmUgcHJvZHVjdGl2ZSB0byBtb3ZlIG9uIGFmdGVy
IHRoYXQgYW5kIHVzZQ0KPiBvdXIgdGltZSBmb3Igc29tZSBvdGhlciB0aGluZ3MuDQo+DQo+IEkg
YW0gZ3Vlc3NpbmcgdGhhdCB0aGUgcGVvcGxlIHdobyBzcG9rZSB1cCBkdXJpbmcgdGhlIFdHIHBy
b2Nlc3MgdG8gbm90IHB1dCBpbiBhbiBvdXRyaWdodCBwcm9oaWJpdGlvbiB3b3VsZCBtYWtlIHRo
ZWlyIGNhc2UgYWxvbmcgd2l0aCB0aGVpciBhcmd1bWVudHMgaGVyZSBhcyB3ZWxsLiBXZSBhcmUg
b25seSBhIHdlZWsgaW50byBhIGZvdXIgd2VlayBsb25nIGxhc3QgY2FsbC4NCj4NCj4gVGhhbmtz
DQo+IFN1cmVzaA0KPg0KPg0KPg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPiBJRVRGIElQdjYgd29ya2luZyBn
cm91cCBtYWlsaW5nIGxpc3QNCj4gaXB2NkBpZXRmLm9yZzxtYWlsdG86aXB2NkBpZXRmLm9yZz4N
Cj4gQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vaXB2Ng0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KSUVURiBJUHY2
IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQppcHY2QGlldGYub3JnPG1haWx0bzppcHY2QGll
dGYub3JnPg0KQWRtaW5pc3RyYXRpdmUgUmVxdWVzdHM6IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaXB2Ng0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0K

--_000_67ab3d39d55840c8a207e2104e6020cdILEXCH01marvellcom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJNUyBHb3RoaWMiOw0KCXBhbm9zZS0xOjIgMTEgNiA5IDcgMiA1IDgg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ik1TIEdvdGhpYyI7DQoJcGFub3NlLTE6
MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJp
Ow0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1m
YW1pbHk6VGFob21hOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCkBmb250LWZh
Y2UNCgl7Zm9udC1mYW1pbHk6Q29uc29sYXM7DQoJcGFub3NlLTE6MiAxMSA2IDkgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiXEBNUyBHb3RoaWMiOw0KCXBhbm9zZS0x
OjIgMTEgNiA5IDcgMiA1IDggMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Ik1TIFVJ
IEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDAgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiXEBNUyBVSSBHb3RoaWMiOw0KCXBhbm9zZS0xOjIgMTEgNiAwIDcgMiA1
IDggMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9y
bWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0
Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsInNl
cmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVk
LCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwcmUNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCBDaGFy
IjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTAu
MHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0Kc3Bhbi5IVE1MUHJlZm9ybWF0dGVk
Q2hhcg0KCXttc28tc3R5bGUtbmFtZToiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7DQoJbXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJIVE1MIFByZWZvcm1hdHRlZCI7DQoJ
Zm9udC1mYW1pbHk6Q29uc29sYXM7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsN
Cgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9y
dC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0
IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9
DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2
OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAg
djpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZd
LS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+R29v
ZCBkaXNjdXNzaW9uIHJlZ2FyZGluZyB0aGUgdGV4dCBhYm91dCB0aGUgaG9wLWJ5LWhvcCBleHRl
bnNpb24uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5JbiBteSBvcGluaW9uIHRoZXJlIGlzIGEgdmFsaWQgdXNlIGNhc2Ug
Zm9yIGludGVybWVkaWF0ZSBub2RlcyB0aGF0IGluc2VydC9yZW1vdmUvbW9kaWZ5L3Byb2Nlc3Mg
aG9wLWJ5LWhvcCBleHRlbnNpb25zLiBFeGFtcGxlczogSU9BTSwgSU5ULjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojMUY0OTdEIj5TaW5jZSB0aGVyZSBpcyBhIHVzZSBjYXNlLCBJIGJlbGlldmUgd2Ug
bmVlZCBleHBsaWNpdCB0ZXh0IGFib3V0IGludGVybWVkaWF0ZSBoYW5kbGluZyBvZiBob3AtYnkt
aG9wIGV4dGVuc2lvbnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1z
ZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5UaGlzIFtzb21ld2hhdF0gcmVtaW5kcyBtZSBvZiB0
aGUgZGlzY3Vzc2lvbiBhIGZldyB5ZWFycyBhZ28gYWJvdXQgdGhlIElQdjYvVURQIHplcm8gY2hl
Y2tzdW0uIFRoZSBXRyBlbmRlZCB1cCBkZWZpbmluZyB0aGF0IOKAnFplcm8gY2hlY2tzdW0gaXMg
cGVybWl0dGVkIGluDQogSVB2Ni9VRFAgKjxiPmlmPC9iPiogW+KApuKApi4uXSBhbmQgdGhlIHBv
c3NpYmxlIGNvbnNlcXVlbmNlcyBhcmUgW+KApuKApi4uXeKAnS48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgd291bGQg
YXJndWUgdGhhdCByZWdhcmRpbmcgaG9wLWJ5LWhvcCBleHRlbnNpb24gaGFuZGxpbmcgd2UgYWxz
byBuZWVkIHRvIGRlZmluZSB0aGF0IOKAnEhvcC1ieS1ob3AgZXh0ZW5zaW9ucyBjYW4gYmUgaW5z
ZXJ0ZWQvcmVtb3ZlZC9tb2RpZmllZC9wcm9jZXNzZWQgYnkNCiBpbnRlcm1lZGlhdGUgbm9kZXMg
KjxiPmlmPC9iPiogW+KApuKApi4uXSBhbmQgdGhlIHBvc3NpYmxlIGNvbnNlcXVlbmNlcyBhcmUg
W+KApuKApi4uXeKAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZh
bWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFG
NDk3RCI+VGFsLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBj
bSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1Rh
aG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gaXB2NiBbbWFpbHRvOmlwdjYtYm91
bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+TWFyayBTbWl0aDxicj4NCjxiPlNl
bnQ6PC9iPiBNb25kYXksIEZlYnJ1YXJ5IDEzLCAyMDE3IDM6NTIgQU08YnI+DQo8Yj5Ubzo8L2I+
IEJyaWFuIEUgQ2FycGVudGVyPGJyPg0KPGI+Q2M6PC9iPiA2bWFuQGlldGYub3JnOyBJRVRGIERp
c2N1c3Npb24gbGlzdDsgTGVkZHksIEpvaG47IFBldGUgUmVzbmljazsgPC9zcGFuPg0KPHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7TVMgVUkgR290aGljJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPuelnuaYjumBlOWTiTwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+OyBTdXJlc2ggS3Jpc2huYW47IGRyYWZ0LWlldGYtNm1hbi1yZmMy
NDYwYmlzQHRvb2xzLmlldGYub3JnOyA2bWFuLWNoYWlyc0BpZXRmLm9yZzxicj4NCjxiPlN1Ympl
Y3Q6PC9iPiBbRVhUXSBSZTogTGFzdCBDYWxsOiAmbHQ7ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBi
aXMtMDgudHh0Jmd0OyAoSW50ZXJuZXQgUHJvdG9jb2wsIFZlcnNpb24gNiAoSVB2NikgU3BlY2lm
aWNhdGlvbikgdG8gSW50ZXJuZXQgU3RhbmRhcmQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
ZGl2IGNsYXNzPSJNc29Ob3JtYWwiIGFsaWduPSJjZW50ZXIiIHN0eWxlPSJ0ZXh0LWFsaWduOmNl
bnRlciI+DQo8aHIgc2l6ZT0iMiIgd2lkdGg9IjEwMCUiIGFsaWduPSJjZW50ZXIiPg0KPC9kaXY+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIDEzIEZlYi4gMjAxNyAxMTo0MCBhbSwgJnF1b3Q7
QnJpYW4gRSBDYXJwZW50ZXImcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpicmlhbi5lLmNhcnBl
bnRlckBnbWFpbC5jb20iPmJyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Sm9obiw8bzpwPjwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4w
cHQiPjxicj4NCk9uIDEzLzAyLzIwMTcgMTI6MDUsIExlZGR5LCBKb2huIHdyb3RlOjxicj4NCiZn
dDsgSeKAmW0gdHJ5aW5nIHRvIHVuZGVyc3RhbmQgaG93IGEgYmFuIG9mIHRoaXMgZnVuY3Rpb25h
bGl0eSB3b3VsZCB3b3JrLiZuYnNwOyBJcyBpdCB0YXJnZXRlZCBhdCB2ZW5kb3IgcHJvZHVjdHMs
IHByZWNsdWRpbmcgdGhlbSBmcm9tIGltcGxlbWVudGluZyB0aGUgZnVuY3Rpb25hbGl0eT88bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SXQncyB0YXJnZXR0ZWQg
YXQgaW50ZXJvcGVyYWJpbGl0eSBhY3Jvc3MgdGhlIEludGVybmV0LiBXZSBjYW4gbmV2ZXIgc3Rv
cDxicj4NCnBlb3BsZSBkb2luZyB3aGF0ZXZlciB0aGV5IHBsZWFzZSBpbnNpZGUgYSBwcml2YXRl
IGRvbWFpbiwgb2J2aW91c2x5Ljxicj4NCkFzIGFsd2F5cywgdGhlcmUgYXJlIG5vIHByb3RvY29s
IHBvbGljZS48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCiZndDsgSWYgdGhlcmUgaXMgYSB0ZWNobmlj
YWwgcHJvYmxlbSB0aGF0IGNhbiBiZSBzb2x2ZWQgYnkgdXNpbmcgRUggaW5zZXJ0aW9uIHdpdGhp
biBhIGRvbWFpbiB3aGVyZSB0aGVyZSBhcmUgbm8gaGFybWZ1bCBzaWRlIGVmZmVjdHMsIGl0IHNo
b3VsZCBiZSBhYmxlIHRvIGJlIHVzZWQuPGJyPg0KJmd0OyBJbiBhIHNvZnR3YXJlIG5ldHdvcmtp
bmcgd29ybGQgd2hlcmUgZnVuY3Rpb25hbGl0eSBpcyBiZWluZyBkZXBsb3llZCB0aGF0IGlzIG5v
dCBmcm9tIHRyYWRpdGlvbmFsIG5ldHdvcmsgdmVuZG9yczsgc29sdXRpb25zIHRoYXQgc29sdmUg
cHJvYmxlbXMgZWZmaWNpZW50bHkgd2lsbCBnZXQgZGVwbG95ZWQuPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldlIGhhZCBhIGxvdCBvZiB0aGlzIGNvbnZlcnNh
dGlvbiBpbiBhIHNsaWdodGx5IGRpZmZlcmVudCBmb3JtIHByaW9yIHRvPGJyPg0KUkZDIDY0Mzcu
IEl0IHByb3ZlZCBpbXBvc3NpYmxlIHRvIHNwZWNpZnkgJnF1b3Q7bG9jYWwgZG9tYWluJnF1b3Q7
IHJ1bGVzIHRoYXQgY291bGQ8YnI+DQpyZWFjaCBjb25zZW5zdXMuIEkgdGhpbmsgd2UnZCBoYXZl
IHRoZSBzYW1lIHByb2JsZW0gdHJ5aW5nIHRvIHdyaXRlIHJ1bGVzPGJyPg0KZm9yIGhlYWRlciBp
bnNlcnRpb24vZGVsZXRpb24gd2l0aGluIGEgZG9tYWluLiBCdXQgaW4gYW55IGNhc2UsIHRoYXQg
aXNuJ3Q8YnI+DQp0aGUgdGFyZ2V0IGZvciBSRkMyNDYwYmlzOiB0aGUgdGFyZ2V0IGlzIHRoZSBJ
bnRlcm5ldC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPldlIGFsc28ga25vdyB0aGF0IHRoaXMgc3RhdGVtZW50IGZy
b20gUkZDMTkxOCBoYXNuJ3QgYmVlbiAxMDAlIGVmZmVjdGl2ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdCI+PGJyPjxicj48
bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVw
dCI+Jm5ic3A7Jm5ic3A7IEJlY2F1c2UgcHJpdmF0ZSBhZGRyZXNzZXMgaGF2ZSBubyBnbG9iYWwg
bWVhbmluZywgcm91dGluZyBpbmZvcm1hdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPHBy
ZT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0Ij4mbmJzcDsmbmJzcDsgYWJvdXQgcHJpdmF0
ZSBuZXR3b3JrcyBzaGFsbCBub3QgYmUgcHJvcGFnYXRlZCBvbiBpbnRlci1lbnRlcnByaXNlPG86
cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQi
PiZuYnNwOyZuYnNwOyBsaW5rcywgYW5kIHBhY2tldHMgd2l0aCBwcml2YXRlIHNvdXJjZSBvciBk
ZXN0aW5hdGlvbiBhZGRyZXNzZXM8bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxwcmU+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTo5LjVwdCI+Jm5ic3A7Jm5ic3A7IHNob3VsZCBub3QgYmUgZm9yd2Fy
ZGVkIGFjcm9zcyBzdWNoIGxpbmtzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcHJlPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5hbmQgd2Ugc3RpbGwgZG9uJ3QgaGF2ZSBlbm91
Z2ggZGVwbG95bWVudCBvZiBCQ1AzOCB3aGljaCB3b3VsZCBhbHNvIGhlbHAgZW5mb3JjZSB0aGF0
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
ZiBpdCBpcyBwb3NzaWJsZSB0byBwbHVnIGEgZGV2aWNlIGludG8gdGhlIEludGVybmV0IEkgdGhp
bmsgaXQgaXMgYmV0dGVyIHRvIGFzc3VtZSBzb21lYm9keSBwcm9iYWJseSB3aWxsIChhbmQgeW91
IHdvbid0IGJlIHRoZXJlIHRvIHN0b3AgdGhlbSkgYW5kIGRlc2lnbiB0byB0aGF0IGFzc3VtcHRp
b24uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PihBbGwgdGhlIHJlY2VudCAmcXVvdDtJb1QmcXVvdDsgYm90bmV0cyBhbmQgY29ycmVzcG9uZGlu
ZyBhdHRhY2tzIGFyZSBhIHJlc3VsdCBvZiBhc3N1bWluZyB0aG9zZSBkZXZpY2VzIHdpbGwgb25s
eSBiZSBjb25uZWN0ZWQgdG8gUHJpdmF0ZSBJbnRlcm5ldHMsIGFuZCB0aGVyZWZvcmUgdGhleSBk
b24ndCBoYXZlIHRvIGJlIGluZGl2aWR1YWxseSAmcXVvdDtJbnRlcm5ldCBwcm9vZiZxdW90OyAo
Y29uY2VwdHVhbGx5IHNpbWlsYXIgdG8gYSAmcXVvdDt3YXRlcg0KIHByb29mJnF1b3Q7IHdhdGNo
KS4pPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PlJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5NYXJrLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tcmlnaHQ6MGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjoj
ODg4ODg4Ij48YnI+DQombmJzcDsgJm5ic3A7IEJyaWFuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxicj4NCiZndDs8YnI+DQomZ3Q7IEpvaG4gTGVk
ZHk8YnI+DQomZ3Q7PGJyPg0KJmd0OyBGcm9tOiBpZXRmICZsdDs8YSBocmVmPSJtYWlsdG86aWV0
Zi1ib3VuY2VzQGlldGYub3JnIj5pZXRmLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBvbiBiZWhh
bGYgb2YgJnF1b3Q7RXJpYyBWeW5ja2UgKGV2eW5ja2UpJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWls
dG86ZXZ5bmNrZUBjaXNjby5jb20iPmV2eW5ja2VAY2lzY28uY29tPC9hPiZndDs8YnI+DQomZ3Q7
IERhdGU6IFN1bmRheSwgRmVicnVhcnkgMTIsIDIwMTcgYXQgMzo1NiBQTTxicj4NCiZndDsgVG86
IFN1cmVzaCBLcmlzaG5hbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnN1cmVzaC5rcmlzaG5hbkBnbWFp
bC5jb20iPnN1cmVzaC5rcmlzaG5hbkBnbWFpbC5jb208L2E+Jmd0OywNCjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtNUyBHb3RoaWMmcXVvdDsiPuelnuaYjumBlOWTiTwvc3Bhbj4gJmx0
OzxhIGhyZWY9Im1haWx0bzpqaW5tZWlAd2lkZS5hZC5qcCI+amlubWVpQHdpZGUuYWQuanA8L2E+
Jmd0Ozxicj4NCiZndDsgQ2M6ICZxdW90OzxhIGhyZWY9Im1haWx0bzo2bWFuQGlldGYub3JnIj42
bWFuQGlldGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOjZtYW5AaWV0Zi5vcmci
PjZtYW5AaWV0Zi5vcmc8L2E+Jmd0OywgSUVURiBEaXNjdXNzaW9uIGxpc3QgJmx0OzxhIGhyZWY9
Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3JnPC9hPiZndDssIFBldGUgUmVzbmlj
ayAmbHQ7PGEgaHJlZj0ibWFpbHRvOnByZXNuaWNrQHF0aS5xdWFsY29tbS5jb20iPnByZXNuaWNr
QHF0aS5xdWFsY29tbS5jb208L2E+Jmd0OywNCiAmcXVvdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQt
aWV0Zi02bWFuLXJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWlldGYtNm1hbi1yZmMy
NDYwYmlzQHRvb2xzLmlldGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0
LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLTZtYW4tcmZj
MjQ2MGJpc0B0b29scy5pZXRmLm9yZzwvYT4mZ3Q7LCAmcXVvdDs8YSBocmVmPSJtYWlsdG86Nm1h
bi1jaGFpcnNAaWV0Zi5vcmciPjZtYW4tY2hhaXJzQGlldGYub3JnPC9hPiZxdW90Ow0KICZsdDs8
YSBocmVmPSJtYWlsdG86Nm1hbi1jaGFpcnNAaWV0Zi5vcmciPjZtYW4tY2hhaXJzQGlldGYub3Jn
PC9hPiZndDs8YnI+DQomZ3Q7IFN1YmplY3Q6IFJlOiBMYXN0IENhbGw6ICZsdDtkcmFmdC1pZXRm
LTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQmZ3Q7IChJbnRlcm5ldCBQcm90b2NvbCwgVmVyc2lvbiA2
IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJbnRlcm5ldCBTdGFuZGFyZDxicj4NCiZndDs8YnI+
DQomZ3Q7IFN1cmVzaCwgSmlubWVpIGFuZCBGZXJuYW5kbyw8YnI+DQomZ3Q7PGJyPg0KJmd0OyBJ
IGZ1bGx5IGFncmVlIHdpdGggeW91IFN1cmVzaCwgdGhlIGdvYWwgb2YgYW4gSUVURiBsYXN0IGNh
bGwgaXMgdG8gZ2V0IE5FVyBkaXNjdXNzaW9uIGFuZCB0byByZS1kbyB0aGUgbGVuZ3RoeSBkaXNj
dXNzaW9ucyB3ZSBoYWQgb24gNk1BTiBXRy48YnI+DQomZ3Q7PGJyPg0KJmd0OyAtw6lyaWM8YnI+
DQomZ3Q7PGJyPg0KJmd0OyBGcm9tOiBpcHY2ICZsdDs8YSBocmVmPSJtYWlsdG86aXB2Ni1ib3Vu
Y2VzQGlldGYub3JnIj5pcHY2LWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyBvbiBiZWhhbGYgb2Yg
U3VyZXNoIEtyaXNobmFuICZsdDs8YSBocmVmPSJtYWlsdG86c3VyZXNoLmtyaXNobmFuQGdtYWls
LmNvbSI+c3VyZXNoLmtyaXNobmFuQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KJmd0OyBEYXRlOiBT
YXR1cmRheSAxMSBGZWJydWFyeSAyMDE3IGF0IDA3OjExPGJyPg0KJmd0OyBUbzogPHNwYW4gc3R5
bGU9ImZvbnQtZmFtaWx5OiZxdW90O01TIEdvdGhpYyZxdW90OyI+56We5piO6YGU5ZOJPC9zcGFu
PiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmppbm1laUB3aWRlLmFkLmpwIj5qaW5tZWlAd2lkZS5hZC5q
cDwvYT4mZ3Q7PGJyPg0KJmd0OyBDYzogJnF1b3Q7PGEgaHJlZj0ibWFpbHRvOjZtYW5AaWV0Zi5v
cmciPjZtYW5AaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86Nm1hbkBpZXRm
Lm9yZyI+Nm1hbkBpZXRmLm9yZzwvYT4mZ3Q7LCBJRVRGIERpc2N1c3Npb24gbGlzdCAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+Jmd0OywgUGV0ZSBS
ZXNuaWNrICZsdDs8YSBocmVmPSJtYWlsdG86cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbSI+cHJl
c25pY2tAcXRpLnF1YWxjb21tLmNvbTwvYT4mZ3Q7LA0KIEZlcm5hbmRvIEdvbnQgJmx0OzxhIGhy
ZWY9Im1haWx0bzpmZ29udEBzaTZuZXR3b3Jrcy5jb20iPmZnb250QHNpNm5ldHdvcmtzLmNvbTwv
YT4mZ3Q7LCAmcXVvdDs8YSBocmVmPSJtYWlsdG86ZHJhZnQtaWV0Zi02bWFuLXJmYzI0NjBiaXNA
dG9vbHMuaWV0Zi5vcmciPmRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlzQHRvb2xzLmlldGYub3Jn
PC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlz
QHRvb2xzLmlldGYub3JnIj5kcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpc0B0b29scy5pZXRmLm9y
ZzwvYT4mZ3Q7LA0KICZxdW90OzxhIGhyZWY9Im1haWx0bzo2bWFuLWNoYWlyc0BpZXRmLm9yZyI+
Nm1hbi1jaGFpcnNAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86Nm1hbi1j
aGFpcnNAaWV0Zi5vcmciPjZtYW4tY2hhaXJzQGlldGYub3JnPC9hPiZndDs8YnI+DQomZ3Q7IFN1
YmplY3Q6IFJlOiBMYXN0IENhbGw6ICZsdDtkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50
eHQmZ3Q7IChJbnRlcm5ldCBQcm90b2NvbCwgVmVyc2lvbiA2IChJUHY2KSBTcGVjaWZpY2F0aW9u
KSB0byBJbnRlcm5ldCBTdGFuZGFyZDxicj4NCiZndDs8YnI+DQomZ3Q7IEhpIEppbm1laSw8YnI+
DQomZ3Q7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4mZ3Q7IE9uIEZlYiAxMCwgMjAxNyAxOjIzIFBNLCAmcXVvdDs8c3BhbiBzdHlsZT0iZm9udC1m
YW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7Ij7npZ7mmI7pgZTlk4k8L3NwYW4+JnF1b3Q7ICZs
dDs8YSBocmVmPSJtYWlsdG86amlubWVpQHdpZGUuYWQuanAiPmppbm1laUB3aWRlLmFkLmpwPC9h
PiZsdDttYWlsdG86PGEgaHJlZj0ibWFpbHRvOmppbm1laUB3aWRlLmFkLmpwIj5qaW5tZWlAd2lk
ZS5hZC5qcDwvYT4mZ3Q7Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7IEF0IFRodSwgOSBGZWIgMjAxNyAx
ODozMDoxMSAtMDMwMCw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZndDsgRmVybmFuZG8gR29udCAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZnb250QHNp
Nm5ldHdvcmtzLmNvbSI+ZmdvbnRAc2k2bmV0d29ya3MuY29tPC9hPiZsdDttYWlsdG86PGEgaHJl
Zj0ibWFpbHRvOmZnb250QHNpNm5ldHdvcmtzLmNvbSI+ZmdvbnRAc2k2bmV0d29ya3MuY29tPC9h
PiZndDsmZ3Q7IHdyb3RlOjxicj4NCiZndDs8YnI+DQomZ3Q7IFdoaWxlIEkgbGFyZ2VseSBhZ3Jl
ZSB3aXRoIEZlcm5hbmRvIG9uIGV2ZXJ5dGhpbmcgaGUgc2FpZCwgSSBoYXZlIHRvPGJyPg0KJmd0
OyBhZG1pdCBtb3N0IG9mIHRoZSBwb2ludHMgYXJlIGp1c3QgcmVwZWF0ZWQgZnJvbSB0aGUgNm1h
biBkaXNjdXNzaW9uLDxicj4NCiZndDsgYW5kIHdvbid0IGdldCB1cyBhbnl3aGVyZSBuZXcgYnkg
ZGlzY3Vzc2luZyB0aGVzZSBhZ2FpbiBhdCB0aGlzIHBvaW50Ljxicj4NCiZndDsgSSBndWVzcyB0
aGUgb25seSBuZXcgaW5wdXQgZm9yIHRoZSBJRVRGIGxhc3QgY2FsbCBpcyB0aGlzOjxicj4NCiZn
dDs8YnI+DQomZ3Q7Jmd0OyAyKSBIb3dldmVyLCBzb21lIGZvbGtzIGNhbWUgdXAgd2l0aCBwcm9w
b3NhbHMgdG8gaW5zZXJ0IEVILCBvbiB0aGUgYmFzaXM8YnI+DQomZ3Q7Jmd0OyB0aGF0ICZxdW90
O1JGQzI0NjAgZG9lcyBub3QgZXhwbGljaXRseSBiYW4gRUggaW5zZXJ0aW9uJnF1b3Q7LiBJZiB0
aGVyZSdzIHBlb3BsZTxicj4NCiZndDsmZ3Q7IGFyZ3VpbmcgdGhhdCwgd2UgY2xlYXJseSBuZWVk
IHRvIG1ha2UgdGhpcyBjbGVhciBpbiB0aGUgc3BlYy48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsm
Z3Q7IDMpIFRoZXJlIHdhcyBhIGNvbnNlbnN1cyBjYWxsLCB5ZXMuIFdoZW4gdGhlIGNhbGwgd2Fz
IG1hZGUgb24gdGhlPGJyPg0KJmd0OyZndDsgbWFpbGluZy1saXN0LCB0aGUgdmFzdCBtYWpvcml0
eSBvZiBzdXBwb3J0ZXJzIG9mICZxdW90O2xldCdzIGtlZXAgdGhlPGJyPg0KJmd0OyZndDsgYW1i
aWd1aXR5JnF1b3Q7IHdlcmUgZm9sa3MgZnJvbSB0aGUgc2FtZSBjb21wYW55IGFzICZxdW90OzIp
JnF1b3Q7LiBJIGhhdmUgbm8gaWRlYSBpZjxicj4NCiZndDsmZ3Q7IHRoaXMgY2hhbmdlcyAob3Ig
bm90KSAmcXVvdDtjb25zZW5zdXMmcXVvdDsuLi4gYnV0IHRoaXMgaXMgY2xlYXJseSBhbiBpbXBv
cnRhbnQ8YnI+DQomZ3Q7Jmd0OyBkYXRhcG9pbnQuPGJyPg0KJmd0OyBBbHRob3VnaCBJIGRvbid0
IHdhbnQgdG8gcG9pbnQgYSBmaW5nZXIgYXQgcGFydGljdWxhciBwZW9wbGUgb3I8YnI+DQomZ3Q7
IG9yZ2FuaXphdGlvbnMgd2l0aG91dCBhbiBldmlkZW5jZSwgSSBndWVzcyBub3QgYSBzbWFsbCBu
dW1iZXIgb2YgNm1hbjxicj4NCiZndDsgcGFydGljaXBhbnRzIChub3Qgb25seSB0aG9zZSB3aG8g
ZXhwbGljaXRseSBzcG9rZSB1cCBoZXJlKSBzdXNwZWN0ZWQ8YnI+DQomZ3Q7IHRoYXQgdGhlIGRl
Y2lzaW9uIHByb2Nlc3Mgd2FzIGJpYXNlZCB3aXRoIHRoZSBpbmZsdWVuY2Ugb2YgYSBsYXJnZSBh
bmQ8YnI+DQomZ3Q7IHBvd2VyZnVsIG9yZ2FuaXphdGlvbiBhbmQgdGhlIHByb2Nlc3MgYW5kIHJl
c3VsdGluZyAmcXVvdDtjb25zZW5zdXMmcXVvdDsgd2FzPGJyPg0KJmd0OyBub3QgcmVhbGx5IGEg
ZmFpciBvbmUuJm5ic3A7IEFuZCBJJ20gbm90IGFuIGV4Y2VwdGlvbiB0byBpdCAtIGluIGZhY3Qs
IGl0PGJyPg0KJmd0OyB3YXMgc28gdW5iZWxpZXZhYmxlIHRvIG1lIHRoYXQgd2UgY2FuJ3QgY2xh
cmlmeSBhbiBhbWJpZ3VpdHkgZXZlbiB3aGVuPGJyPg0KJmd0OyB3ZSB3ZXJlIGFsc28gb3BlbiBm
b3IgZnV0dXJlIGV4dGVuc2lvbnMsIHRoYXQgSSBjb3VsZG4ndCB0aGluayBvZjxicj4NCiZndDsg
b3RoZXIgcmVhc29ucyB0aGFuIGEgY29tcGFueSBhZ2VuZGEuPGJyPg0KJmd0Ozxicj4NCiZndDsg
T2YgY291cnNlLCBpdCdzIHF1aXRlIHBvc3NpYmxlIHRoYXQgaXQgd2FzIGp1c3QgYSBjb2luY2lk
ZW5jZSB0aGF0PGJyPg0KJmd0OyBtYW55IHBlb3BsZSB3aXRoIHRoZSBzYW1lIG9yZ2FuaXphdGlv
biBnZW51aW5lbHkgdGhvdWdodCB3ZSBzaG91bGQ8YnI+DQomZ3Q7IGxlYXZlIGl0IGFtYmlndW91
cyB3aGlsZSBtYW55IG90aGVycyBzdHJvbmdseSB0aG91Z2h0IHdlIHNob3VsZDxicj4NCiZndDsg
Y2xhcmlmeSBpdCBidXQgZmV3IChpZiBub3Qgbm8pIHBlb3BsZSBmcm9tIHRoYXQgb3JnYW5pemF0
aW9uIHN1cHBvcnRlZDxicj4NCiZndDsgdGhlIGNsYXJpZmljYXRpb24uJm5ic3A7IEJ1dCBJIGRv
bid0IHRoaW5rIHdlIGNhbiBwcm92ZSBpdCBlaXRoZXIgd2F5Ljxicj4NCiZndDs8YnI+DQomZ3Q7
IEJ1dCBhcyBGZXJuYW5kbyBzYWlkLCBJIGJlbGlldmUgdGhpcyBwb2ludCAoYW5kIHRoYXQgc2V2
ZXJhbCwgYW5kPGJyPg0KJmd0OyBhcmd1YWJseSBtb3JlLCBwYXJ0aWNpcGFudHMgc3VzcGVjdGVk
IGl0KSBzaG91bGQgYmUgaW5jbHVkZWQgaW4gbWFraW5nPGJyPg0KJmd0OyB0aGUgZGVjaXNpb24g
YXQgdGhlIElFU0cgYW5kIGF0IHRoZSBJRVRGIGxhc3QgY2FsbC4mbmJzcDsgQW5kLCB3aGF0ZXZl
ciB0aGU8YnI+DQomZ3Q7IGRlY2lzaW9uLCBpdCB3b3VsZCBiZSBtb3JlIHByb2R1Y3RpdmUgdG8g
bW92ZSBvbiBhZnRlciB0aGF0IGFuZCB1c2U8YnI+DQomZ3Q7IG91ciB0aW1lIGZvciBzb21lIG90
aGVyIHRoaW5ncy48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJIGFtIGd1ZXNzaW5nIHRoYXQgdGhlIHBl
b3BsZSB3aG8gc3Bva2UgdXAgZHVyaW5nIHRoZSBXRyBwcm9jZXNzIHRvIG5vdCBwdXQgaW4gYW4g
b3V0cmlnaHQgcHJvaGliaXRpb24gd291bGQgbWFrZSB0aGVpciBjYXNlIGFsb25nIHdpdGggdGhl
aXIgYXJndW1lbnRzIGhlcmUgYXMgd2VsbC4gV2UgYXJlIG9ubHkgYSB3ZWVrIGludG8gYSBmb3Vy
IHdlZWsgbG9uZyBsYXN0IGNhbGwuPGJyPg0KJmd0Ozxicj4NCiZndDsgVGhhbmtzPGJyPg0KJmd0
OyBTdXJlc2g8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDsgLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08YnI+DQom
Z3Q7IElFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxpbmcgbGlzdDxicj4NCiZndDsgPGEgaHJl
Zj0ibWFpbHRvOmlwdjZAaWV0Zi5vcmciPmlwdjZAaWV0Zi5vcmc8L2E+PGJyPg0KJmd0OyBBZG1p
bmlzdHJhdGl2ZSBSZXF1ZXN0czogPGEgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1h
bi9saXN0aW5mby9pcHY2IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2lwdjY8L2E+PGJyPg0KJmd0OyAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCiZndDs8
YnI+DQo8YnI+DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxicj4NCklFVEYgSVB2NiB3b3JraW5nIGdyb3VwIG1haWxp
bmcgbGlzdDxicj4NCjxhIGhyZWY9Im1haWx0bzppcHY2QGlldGYub3JnIj5pcHY2QGlldGYub3Jn
PC9hPjxicj4NCkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiA8YSBocmVmPSJodHRwczovL3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8v
d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaXB2NjwvYT48YnI+DQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_67ab3d39d55840c8a207e2104e6020cdILEXCH01marvellcom_--


From nobody Mon Feb 13 06:08:43 2017
Return-Path: <vijay.gurbani@alcatel-lucent.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7622B129582; Mon, 13 Feb 2017 06:08:33 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Vijay Gurbani <vijay.gurbani@alcatel-lucent.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-grow-mrt-add-paths-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148699491344.24997.6536739002535110358.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 06:08:33 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NaBVOG0h8AOO0a_d1qVr2MjGYk0>
Cc: draft-ietf-grow-mrt-add-paths.all@ietf.org, grow@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 14:08:33 -0000

Reviewer: Vijay Gurbani
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-grow-mrt-add-paths-??
Reviewer: Vijay Gurbani
Review Date: 2017-02-13
IETF LC End Date: 2017-02-15
IESG Telechat date: Not scheduled for a telechat

Summary: Document is ready as a PS.

Major issues: None.

Minor issues: None.

Nits/editorial comments:  None.



From nobody Mon Feb 13 07:31:24 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BA512965A; Mon, 13 Feb 2017 07:31:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 1-ILDBiEBV84; Mon, 13 Feb 2017 07:31:20 -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 54B3912961D; Mon, 13 Feb 2017 07:31:20 -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 v1DFVJTp041098; Mon, 13 Feb 2017 08:31:19 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1DFVDo5041017 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Mon, 13 Feb 2017 08:31:14 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Mon, 13 Feb 2017 07:31:13 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Mon, 13 Feb 2017 07:31:13 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, "C. M. Heard" <heard@pobox.com>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHShJFkd1t1l5P4r0CAXezaoK6tiaFk8e4AgAIhCtA=
Date: Mon, 13 Feb 2017 15:31:12 +0000
Message-ID: <f8ce237bd57d4262af37cee5889c1830@XCH15-06-08.nw.nos.boeing.com>
References: <CACL_3VEm=M9cYG1HEe7wu2RHo23P9hqH4e7qX-GGWds1CLSL=w@mail.gmail.com> <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
In-Reply-To: <A33FF8C9-E244-4404-9596-503D82F20B47@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GrUb18gigGVnfDegCdV-kQaJoF8>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Gen-ART <gen-art@ietf.org>, Stewart Bryant <stewart@g3ysx.org.uk>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 15:31:22 -0000

Hi Ole,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.o=
rg
> Sent: Saturday, February 11, 2017 2:59 PM
> To: C. M. Heard <heard@pobox.com>
> Cc: 6man WG <ipv6@ietf.org>; IETF <ietf@ietf.org>; Gen-ART <gen-art@ietf.=
org>; Suresh Krishnan <suresh.krishnan@gmail.com>;
> Stewart Bryant <stewart@g3ysx.org.uk>; draft-ietf-6man-rfc1981bis.all@iet=
f.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> > How does this work for UDP?
> >
> > Sending packets no larger than 1280 bytes is always an option, and in
> > the case of UDP-based request-response protocols such as DNS that do
> > not have connection state, it may be the only feasible option.
>=20
> Yes, but DNS tend to use IP fragmentation that suffers an order of magnit=
ude worse fate than ICMP messages. ;-)
>=20
> > Anyway, the point I was trying to make was not to argue about better
> > or worse methods but rather to dispute the statement that PMTUD is
> > essential for avoiding black holes. I don't believe that it is. The
> > draft itself explicitly says that "IPv6 nodes are not required to
> > implement Path MTU Discovery."
>=20
> That's correct. But it then must restrict itself to sending packets at th=
e minimum MTU size.
> You cannot implement RFC2473 (IP in IP) without PMTUD for example.

Right, but RFC2473 also has other problems, e.g., integrity.

Thanks - Fred

> [...]
>=20
> > What criteria for advancement to IS do you think are not met by this do=
cument?
> >
> > I do not dispute that the document has met the formal criteria for IS i=
n Section
> > 2.2 of RFC 6410. I would argue, however, that its failure to provide a =
complete
> > solution for environments where delivery of ICMP messages is not assure=
d
> > constitutes a significant technical omission for today's Internet, and =
I note
> > that per RFC 2026 Section 4.1.1, even a PS "should have no known techni=
cal
> > omissions." What I am asking the community, and the IESG, is whether it=
 is
> > wise to advance a document with known technical omissions; it seems to =
me
> > that the Gen-ART reviewer has raised much the same question.
>=20
> For IPv6, because of the removal of fragmentation by intermediate nodes, =
failure to provide a path where ICMP message delivery is
> assured is a considered a configuration error.
>=20
> From http://www.nlnetlabs.nl/downloads/publications/pmtu-black-holes-msc-=
thesis.pdf:
>=20
> "We observed that for IPV4 between 4% and 6% of the paths between the van=
tage points and our experimental setup filter ICMP PTB
> packets. For IPV6 this was between 0.77% and 1.07%. Furthermore, we found=
 that when IPV4 Domain Name System (DNS) servers do
> not act on the receipt of ICMP PTB packets, between 11% and 14% of the an=
swers from these DNS servers are lost. For IPV6 DNS
> servers this was between 40% and 42%. Lastly, we found that for IPV4 appr=
oximately 6% of the paths between the vantage points and
> our experimental setup filter IP fragments. For IPV6 this was approximate=
ly 10%."
>=20
> From that data it looks like we have been quite successful. ICMPv6 PMTUD =
is treated a lot better (about a 1% loss) than its IPv4
> counterpart.
> Unless better data exists I tend to conclude that the claim that the Inte=
rnet breaks PTUMD for IPv6 is a myth.
>=20
> Fragmentation on the other hand...
> And please don't get me wrong, I think we have a big job to do on MTU iss=
ues. I just don't see data showing that PMTUD isn't doing
> what it was designed to do.
>=20
> Best regards,
> Ole
>=20
>=20



From nobody Mon Feb 13 07:41:33 2017
Return-Path: <paul@nohats.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564931296CA; Mon, 13 Feb 2017 07:41:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 05R1TK_WSdyr; Mon, 13 Feb 2017 07:41:31 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 C6C38129406; Mon, 13 Feb 2017 07:41:30 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3vMVBb4lTmzd3; Mon, 13 Feb 2017 16:40:55 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1487000456; bh=nu5I0bqJq9L+xfMF+e5anV7CyisU334gGcoBDcUyBIU=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Hj4kT1oBeEzoONM2kDVZubv0bMeV+p6n1ywJgoQCSAsgxWHUgmhlpYOUnjvUBZH+O tVCVlAy6Uk+5Q7fU0Elcj3CJT3NuPTxtGtLQMqakvfTn8AEmLIkgbyUN3RE6b+eBG5 t6zEvC6IPn0gzpc2z3oyIH5qgcVBzQ2FrYEX6UDw=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id qzZk10l4PELa; Mon, 13 Feb 2017 16:40:53 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 13 Feb 2017 16:40:53 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id A42E02DEFF6; Mon, 13 Feb 2017 10:40:52 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca A42E02DEFF6
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 8D6AC41DA420; Mon, 13 Feb 2017 10:40:52 -0500 (EST)
Date: Mon, 13 Feb 2017 10:40:52 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [secdir] Review of draft-ietf-mmusic-sctp-sdp-22
In-Reply-To: <D4C77E98.17E98%christer.holmberg@ericsson.com>
Message-ID: <alpine.LRH.2.20.1702131039400.1198@bofh.nohats.ca>
References: <148669725288.8138.2095744202497272272.idtracker@ietfa.amsl.com> <alpine.LRH.2.20.1702092230300.22742@bofh.nohats.ca> <D4C388CF.17C73%christer.holmberg@ericsson.com> <D4C77E98.17E98%christer.holmberg@ericsson.com>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=euc-kr; format=flowed
Content-Transfer-Encoding: 8BIT
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3EWZr7oqVOgfbB3MVFUrjmYldZE>
Cc: "draft-ietf-mmusic-sctp-sdp.all@ietf.org" <draft-ietf-mmusic-sctp-sdp.all@ietf.org>, Paul Wouters <pwouters@redhat.com>, "ietf@ietf.org" <ietf@ietf.org>, "mmusic@ietf.org" <mmusic@ietf.org>, secdir <secdir@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 15:41:32 -0000

On Mon, 13 Feb 2017, Christer Holmberg wrote:

>>> Section 10.3
>>>
>>> [I-D.ietf-mmusic-dtls-sdp] is not a proper reference with link.
>>
>> I©öll look into that.
>
> I had a look a this, but I am not sure I understand your issue.

It has the ascii test "[I-D.ietf-mmusic-dtls-sdp]" instead of the
markup text: <xref target="I-D.ietf-mmusic-dtls-sdp"/>

Paul


From nobody Mon Feb 13 08:07:33 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACCB21296D3; Mon, 13 Feb 2017 08:07:27 -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, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aEy8DDhYRHFX; Mon, 13 Feb 2017 08:07:27 -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 C335812951B; Mon, 13 Feb 2017 08:07:26 -0800 (PST)
Received: by mail-vk0-x22f.google.com with SMTP id k127so63415171vke.0; Mon, 13 Feb 2017 08:07:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=UFEs9j4O78SFDwCZ7bMHoMdtvnO6WDPC0ntQjkfN7mE=; b=fQtsXWvl8oBKwbbdgGTS3OpQSepj4CJU/H8TvoqZvkcnIWcfgO7tYek7npZ2gOKmOY pirIAD0fFaIMNk+2rFK9RWrgAhb4Nj04VNOeJhKT7pZxV2o5NvDh0PceaOQFqFevfVj5 +6hrayBD6Tb75xYL9rtpIzgy8YyV8VdKfVJGmtRkjCFupAVRCef14MNTijUdup1Z1KgK IbdUB0daF1RFJLJ7Jthu3tsvqW3+sdFNN2kAkYTz6Ete5DxEVpvSkio4mvKsS4zZSnK2 Mj+bVkN2bskmkteek83IuWbphQOjjvWo9AF3bRV4QSe/0CaRkGwNu6H+XFpProHiCt6t RLOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=UFEs9j4O78SFDwCZ7bMHoMdtvnO6WDPC0ntQjkfN7mE=; b=W/ljcdOC8VFcImHJDHoJFPBJKZc9oTkSudWe02x6cn/jSmVCtD2jxLlkMU2qaT6SUd 9zFWLa0iEJAnyhS4TUkdJj4SA7GYZpvNiPoDoDKwEHzFdPH4g1/4RgN4MAu0/5sbJD4K Bu6RMtIwRc4OnLNmat7HsaZQwVB/AAmEYhKihawtwbVvaZZ+9WsDCROh/DdNxgnWzUgK lIVBWg0Zl3N4JFnZqHPlwYJ7MndqoFzCaH2dO5BfIsxrR4YsP9GLNut74hGIbBIvDcnL Je5Szi1qzIaNdhOBVQZYbDEBq145IMxe3+x9iywmTqAh0YJZAr3tAij7jZkyc0C9cbR3 jv+g==
X-Gm-Message-State: AMke39mhFy8YXYSj0Prne3lQzCAX4flvrDDrVfnp9lAYP5+Dqd0XnYGxnA68LjtIBQ0x7k7eLVe7nFGmhxbrDQ==
X-Received: by 10.31.54.85 with SMTP id d82mr9524686vka.25.1487002045827; Mon, 13 Feb 2017 08:07:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.33.173 with HTTP; Mon, 13 Feb 2017 08:06:55 -0800 (PST)
In-Reply-To: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com>
References: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Tue, 14 Feb 2017 03:06:55 +1100
Message-ID: <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pyTZXyKKKoW6ywCzqr0XMIuEdWk>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 16:07:28 -0000

Hi,



On 14 February 2017 at 00:43, Tal Mizrahi <talmi@marvell.com> wrote:
> Hi,
>
>
>
> Good discussion regarding the text about the hop-by-hop extension.
>
>
>
> In my opinion there is a valid use case for intermediate nodes that
> insert/remove/modify/process hop-by-hop extensions. Examples: IOAM, INT.
>
> Since there is a use case, I believe we need explicit text about
> intermediate handling of hop-by-hop extensions.
>


Imagine you sent a letter through the postal system, and the postal
system wanted to add information to that letter, that is then to be
removed before the letter arrives at its final destination.

The postal system have at least two choices as to how to add that
information. They could:

(a) unstick your envelope's seal, insert the information, reseal the
envelope so well you can't tell and send it on its way, some how
flagging to a destination device within the postal system that this
specific envelop needs to be openned, a specific page removed, and
then resealed.

(b) take a new envelope with new internal postal system source and
destination address information, insert your letter without touching
it in addition to the new information, and then sending it on its way.

Imagine that the information to be added by the postal system is
printed on the same type of paper and is written in the same font as
you've chosen to use to write your letter.

Have a think about these two methods, what could fail with each of
them, and what the consequences may be if any of those failures occur.
Have a think of the benefits of each method, and whether they're worth
it compared to the failure mode costs and consequences for the method.

>
>
> This [somewhat] reminds me of the discussion a few years ago about the
> IPv6/UDP zero checksum. The WG ended up defining that =E2=80=9CZero check=
sum is
> permitted in IPv6/UDP *if* [=E2=80=A6=E2=80=A6..] and the possible conseq=
uences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>
>

That is a far more trivial change to the packet - it is allowing a
value in an existing field that was formerly prohibited, and nodes
that did not understand that value would drop the packet because that
is what they had been specified to do if they received this prohibited
value. In other words, existing implementations ' behaviour when this
formerly unexpected value was encountered had already been specified
and deployed.


>
> I would argue that regarding hop-by-hop extension handling we also need t=
o
> define that =E2=80=9CHop-by-hop extensions can be
> inserted/removed/modified/processed by intermediate nodes *if* [=E2=80=A6=
=E2=80=A6..] and
> the possible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>

Some things that are possible to do in theory shouldn't be done in
practice, because the consequences when their implementations fail can
be severe and outweigh the benefits.

In theory, inserted EHs will be removed 100% of the time. In practice
they won't be, because implementations can have bugs and they can also
fail in unexpected ways e.g., hardware faults.

Regards,
Mark.


From nobody Mon Feb 13 08:29:09 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2656912953E; Mon, 13 Feb 2017 08:29:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <rtg-dir@ietf.org>
Subject: Review of draft-leiba-rfc2119-update-01
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148700334813.25059.6320598686717139053.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 08:29:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SSFDRu2RZHLRJcNsJwONzgpMayA>
Cc: draft-leiba-rfc2119-update.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 16:29:08 -0000

Reviewer: Joel Halpern
Review result: Ready

I have reviewed this document on behalf of the Routing Area
Directors.

This document is ready for publication as a Best Current Practice.

I do not see any issues with the document.


From nobody Mon Feb 13 08:56:00 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0AB7129565 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 08:55:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 zdfwQ2CTBn4z for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 08:55:53 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 A7860129441 for <ietf@ietf.org>; Mon, 13 Feb 2017 08:55:53 -0800 (PST)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-08v.sys.comcast.net with SMTP id dJu6cFCdmy4bMdJurcU211; Mon, 13 Feb 2017 16:55:53 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-01v.sys.comcast.net with SMTP id dJuocoNOPgcVOdJuqcaYLc; Mon, 13 Feb 2017 16:55:52 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1DGtnOd013897; Mon, 13 Feb 2017 11:55:49 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1DGtmKN013894; Mon, 13 Feb 2017 11:55:48 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Sri Gundavelli \(sgundave\)" <sgundave@cisco.com>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
In-Reply-To: <D4C63E24.2598D8%sgundave@cisco.com>
Sender: worley@ariadne.com (Dale R. Worley)
Date: Mon, 13 Feb 2017 11:55:48 -0500
Message-ID: <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfLBYsvvQpSgsytl+ZkBaSpG8sIpIb+R578s7f49lUIVmj/oCsOqEvGTJnwlhOQ7/rbp+jcGowToziBn3MMJfUMpswQKdPcOUus/aKYzpN7zDiMLm9pYR rQAO2NvrotFI8CEdjXoc3EV/ZF/eXZmRM1AXDu7T5nU80+NV+axvqoGNfiXYefgsRRa2rVGUJJgKk7AgkSHZu8skex9p14dwd7YWgCaJWZ29hZvWqrhE941L bEEkARtbsy3aIpkv6oUiIOiW/TYKS3WPAU8WDmKJNQHlH8Y3p+VQB9NyeKaMR4a6VnjB+5hpwvSJIs01Kd/bCj77Gnlw/djxk9KTN8zTXog=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/14S3qZ7sqAkKkCfSvKVl1HQ1HCc>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 16:55:55 -0000

"Sri Gundavelli (sgundave)" <sgundave@cisco.com> writes:
> When we discussed this issue in the past, the general feedback from
> the WG was that the draft should provide some minimal amount of
> details on the new identifier types, what the identifier is, how the
> identifier is constructed, what is the access technology and a
> reference to the specification that provides that definition. The idea
> is NOT TO provide extensive details on the spec, but to enable a
> reader with some high level details and a pointer to the
> specification. I tend to think the text in the current specification
> just does that. If the text is seen as redundant text, we can
> certainly add a statement saying that the definition for the
> identifier is provided in spec-XYZ and is repeated here for
> convenience. May be other folks in the WG have some views on this.

I take it that the following are typical comments from the WG:

> Comments from 10/11/2015 email:
>
> "Some text on the motivation for defining new Types may be
> helpful. Document is not just standardizing the currently
> in-use/popular identifier types, its also introducing new types are
> not in use. The reasons/interest for defining identifiers that are
> tied to the physical elements of the device (RFID, MAC address ..etc)
> and how it helps in deployment of the technology may be useful. Few
> lines of text will really help."
>
> "I was hoping to see a sub-section for each of the types. We cannot
> standardize a identifier type without providing any explanation on the
> identifier type or the references to the base definitions. This can be
> painful, but I'd have a small section for each of the types. It can be
> 3 line text on the a.) Definition b.) Format c.) Example format d.)
> Reference to the base spec that defines those identifiers."

I can understand these desires, and I agree with following them.

In regard to the first message, it seems to request "The
reasons/interest for defining identifiers that are tied to the physical
elements of the device (RFID, MAC address ..etc) and how it helps in
deployment of the technology may be useful."  As far as I can tell, this
isn't handled in section 4.9 (which is the part I was complaining
about).  And I don't recall if the earlier parts of the draft are
specific about "the reasons/interest" for any of the new types.  I
believe from this discussion that the reason an identifier was included
is that somebody told the authors that they wanted to use the identifier
in question -- and that is quite legitimate.  Perhaps saying it
explicitly in the early parts of the draft would help.

In regard to the second message, it seems to request

    a small section for each of the types. It can be
    3 line text on the
	a.) Definition
	b.) Format
	c.) Example format
	d.) Reference to the base spec that defines those identifiers.

Of course, (d) "reference to base spec" is necessary, and the
sub-sections of 4.9 do that for each format, as does Table 1.

For (a) "definition", the texts in 4.9 proper seem to be fairly good.
E.g.,

   The EPC encoding scheme for SGTIN permits the direct embedding of
   EAN.UCC System standard GTIN and Serial Number codes on EPC tags.  In
   all cases, the check digit is not encoded.  Two encoding schemes are
   specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits).

Based on that alone, I couldn't possibly construct a SGTIN-64 myself,
but I have some idea of the information it contains and the technical
terms to look up to find the real definition of the data items.

However (b) "format" seems to be missing (except in the most abstract
sense) and (c) "example format" seem to be missing entirely.  OTOH, I'm
not sure that the space needed to specify those would be worth the
effort.

Summary:  After thinking about it more, I think it's not worth the
effort to revise 4.9 heavily.  Most of that information is for the use
of people who are familiar with the RFID identifiers and their formats,
and if they are happy with it, there's no reason to change it.

Dale


From nobody Mon Feb 13 09:17:29 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885151295EA for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:17:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qu9kIxQbZ2KB for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:17:21 -0800 (PST)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::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 74C8F1296FB for <ietf@ietf.org>; Mon, 13 Feb 2017 09:17:19 -0800 (PST)
Received: by mail-wm0-x234.google.com with SMTP id v77so99095331wmv.0 for <ietf@ietf.org>; Mon, 13 Feb 2017 09:17:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=C/zy10gXStTpI9Cni5mk5fkDZBayW3koRjGSboyU/A0=; b=d45D01hPZJQor9TI0WusfTz8tW7TKzYarQyLAb7IRvSek1JnW9RQjAxfCf436b7l9t W7SI6nSi3/oCiSOSz+RbNNGueAn4qAu7SxNAPjHRCG1mTfqo2IwyuqxkgwuCDifL+xIn Xo+kv9YtExoAwrJ86x8ePv6ncXspV4Jassp18=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=C/zy10gXStTpI9Cni5mk5fkDZBayW3koRjGSboyU/A0=; b=DkoMlPxqyaQv7DVkeF1r9vf/6B4VDcRuTJjIJ8w5OY6AN3jXXZxm4Okzl1FBRfM7iD sAZY3k7cCLmK+B9vDj5n7gtJ4oivuPK38zAJZmkPfK0U9mrk9s+Edb9xEuCbzqUJ8GyX B4nxS+y1toNWhqTOZ3rQN1l70vj8EafeHGslnmDv7+LdWcB8FFjYU9gF3QkpCFGLDd1f czzJEWZcHfQ5jrI6czOfUhmLHM+ebzaWKOySRha3FpnGIIKZ1AXa2AnmVQvZg/c72we+ egUeLYlcoH0tJPSXtLRPJ2xB/Q0ZiHvNQRdK3WUJTk6HGOX5OP2XeYMI6lYyMeAAavoZ UnTw==
X-Gm-Message-State: AMke39ly1izq1VR7b0dbPCMvYlrYXUlwKVmWSJyEPf7bhfM6h30ohRSYvXzP2fuFJ1iUT/S7S+y6iiB3i/xbCOa2
X-Received: by 10.28.99.69 with SMTP id x66mr38270098wmb.91.1487006237736; Mon, 13 Feb 2017 09:17:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.136.199 with HTTP; Mon, 13 Feb 2017 09:17:17 -0800 (PST)
In-Reply-To: <1162BF5A37921B1555FF29F9@PSB>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB>
From: Dave Cridland <dave@cridland.net>
Date: Mon, 13 Feb 2017 17:17:17 +0000
Message-ID: <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tTNFdQdHUAfBzAihwxQXr9b57Xw>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 17:17:27 -0000

On 12 February 2017 at 20:15, John C Klensin <john-ietf@jck.com> wrote:
> Yes.  See above.  But note that "JMAP replaces IMAP" requires
> that it support identical functionality, be a superset of IMAP
> function, or drop only the functions that no one is using or
> cares about.  Note that I'm talking about functionality, not
> syntax

I don't think this is true.

If JMAP is to supplant IMAP - and I think that's a worthy goal even if
its likelihood remains a matter for debate - then JMAP has to support
the same model.

The model of IMAP is that:

* Each message resides in a single mailbox,
* Each message has a set of independent flags,
* Each message is immutable.

(One could argue that other metadata exists, given ANNOTATE, but
nobody [to a reasonable approximation] uses ANNOTATE).

Gmail is an example of a case where the model of IMAP doesn't fit the
underlying data model - this is a shame, as IMAP's original design
took considerable effort to fit the wide, existing models of the time.
JMAP, on the other hand, can cope with both gmail style labels and
IMAP-style mailboxes, by stated design.

So I'm confident that, while your statement seems incorrect to me, the
corrected statement would be satisfied.

Dave.


From nobody Mon Feb 13 09:30:22 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6511296DA for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:30:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0aIWc5pK5ILT for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:30:19 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 61C6C1296D1 for <ietf@ietf.org>; Mon, 13 Feb 2017 09:30:19 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1DHVx3I011227 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 09:32:00 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1487007120; bh=qSggWoCKBzE+kMoZBpV8kzrkBm1gebgU9sD6bRmy7yQ=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=Jjrq/lTfqoKRp00poHs73NX15ffrGAVVY0XEYFPareATeGcLtJmzKoHAuhFvwbb3J LIJ4J3ckCRY4lcJ9H81URqqR5tgzp10y1TO+yY9YnSYme3YUCoQpx1FqPw9fHOIjro XghGrwr0LT/OOt1fuaK0jIW599y44ZhlLt/eYLqQ=
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Dave Cridland <dave@cridland.net>, John C Klensin <john-ietf@jck.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net>
Date: Mon, 13 Feb 2017 09:30:09 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FTVFTbGbl3AZavc75zSbGU9d2SA>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 17:30:20 -0000

On 2/13/2017 9:17 AM, Dave Cridland wrote:
> I don't think this is true.
...
> JMAP, on the other hand, can cope with both gmail style labels and
> IMAP-style mailboxes, by stated design.


The constraints/flexibility of an effort depend on the goals it asserts 
and the support for those goals.  I think it's dandy to target an access 
protocol that is substantially different from the 
features/style/whatever of IMAP.  The requirements are to be very clear 
about the features/style/whatever of the new effort, very clear about 
the expected benefits, and very clear about the support for that.

Given the long history of IMAP, the proposed JMAP effort should offer 
clear assertions of the relative differences and benefits of the new 
effort, to aid in assessing likely appeal of the effort.

So, for example, the above comment about JMAP's handling of different 
reference models is substantive and appealing.  However the various 
notes that have been posted about JMAP leave me thinking that there is 
less clarity about the effort than one would like, among JMAP's supporters.

The embodiment of the clarity needs to be the charter text and I don't 
think it's made its case well enough.  For example, I don't see a 
reference to the ability to support different referencing models.

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Mon Feb 13 09:51:43 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 588D1129583; Sun, 12 Feb 2017 17:51:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level: 
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6BXGgOd4gYvk; Sun, 12 Feb 2017 17:51:35 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 C1258129587; Sun, 12 Feb 2017 17:51:34 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id 96so57547011uaq.3; Sun, 12 Feb 2017 17:51:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1kEThVIEMXC3EOZfk6+Inq3u+C5Sqx9zcGmtEhtCJ4o=; b=pksOgDFuKmVCCuENTNZxXn4CGsDQBl+VkiU4ZRqtuzhhhqiSO5k8AOHzOsqpV7hxb/ g28BBZJBhLjuQud/c5DkCAP4JuAhMIfmA5lupwwSf3rJ8GUUcTblZcuWaoysy1s2gfxX RSL3JofzRForx368CNL4yjfaNCSpzJnHTAdwRXO8BEdu9qTkoCkQa+aICD3qEqs7Qg2Q WY4aAh/CJTE8NbXsYtRHs3Gy9v+CqAr0U5hDrERD0kaNFjcPSQmHMwpMODeAeWUHM7Cq 7KccwHExkjiCYMwRAxEZO5iONpQ130oL+gCVjlohUPMbU6OoI5tx7cD6R5TOE0+2jrib dA8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1kEThVIEMXC3EOZfk6+Inq3u+C5Sqx9zcGmtEhtCJ4o=; b=SoZKZfJbY4oDy6Lkfduajv+4QEmMqdZU93SXYeNRzrHXVUmJUq1ihoH8PX1P1UdBXX 3q4dlvZpowcIGhvc+TEpSyhkyzdXfLsqya8wRU1qFe6eZNzJWg6O+DkodpXJz+drkwv1 zbeOfzD2WJeL2OkJkk0p9Pnr6e3H9NpKSQ7Y9V/woCECYI02er4K8WLpFNry5X0Z8rR7 3XadH5etEf1vJ+lw4hCY0p+eXb9bhLbhO2UiUlKUNQvHvo+qCGLiQ9dMk8PMFjfkCW5u zTBF/82CabwWcQxJX5l1riU7niUHpVFBgIT4iKrFxhFnEVjqAo9qt/3hR4HtlL7PBPPC MH/g==
X-Gm-Message-State: AMke39kFr+kgXFhmRmsaoI6oSrCu9vSf6Nf5pVzwc/T+U9ijP/Rul8byzByEDYEDfqJS+jXo1jyrISjh+Xs/rw==
X-Received: by 10.159.40.201 with SMTP id d67mr10552812uad.98.1486950693836; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.33.173 with HTTP; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
Received: by 10.159.33.173 with HTTP; Sun, 12 Feb 2017 17:51:33 -0800 (PST)
In-Reply-To: <cd1ef13e-7d3c-0dbf-a4d9-61442f663d3e@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30725d25-9829-bf50-23c6-9e1b757e5cba@si6networks.com> <7ee506c2-4213-9396-186a-2b742c32f93b@gmail.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <CA+MHpBrPGLebKj1XcSbuv8DyVTLWE_DpjHeZLzPpDBLg0sEpGA@mail.gmail.com> <5CE4B4BF-75A9-4DC9-80AE-220281B046E9@cisco.com> <A823FD1C-4ED8-4788-81F0-0F672F1FA364@cable.comcast.com> <cd1ef13e-7d3c-0dbf-a4d9-61442f663d3e@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Mon, 13 Feb 2017 12:51:33 +1100
Message-ID: <CAO42Z2zbnAZ5KUWmWouB4T0Cpg9WEk4aEKNi50X+Xow8L22LTg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c123f16e79e3505485faf79
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SvsOwQaCTMTM4XJ5IwCIBLcCnRE>
X-Mailman-Approved-At: Mon, 13 Feb 2017 09:51:42 -0800
Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "Leddy, John" <John_Leddy@comcast.com>, Pete Resnick <presnick@qti.qualcomm.com>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, "Eric Vyncke \(evyncke\)" <evyncke@cisco.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 01:51:40 -0000

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

On 13 Feb. 2017 11:40 am, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

John,

On 13/02/2017 12:05, Leddy, John wrote:
> I=E2=80=99m trying to understand how a ban of this functionality would wo=
rk.  Is
it targeted at vendor products, precluding them from implementing the
functionality?

It's targetted at interoperability across the Internet. We can never stop
people doing whatever they please inside a private domain, obviously.
As always, there are no protocol police.

> If there is a technical problem that can be solved by using EH insertion
within a domain where there are no harmful side effects, it should be able
to be used.
> In a software networking world where functionality is being deployed that
is not from traditional network vendors; solutions that solve problems
efficiently will get deployed.

We had a lot of this conversation in a slightly different form prior to
RFC 6437. It proved impossible to specify "local domain" rules that could
reach consensus. I think we'd have the same problem trying to write rules
for header insertion/deletion within a domain. But in any case, that isn't
the target for RFC2460bis: the target is the Internet.


We also know that this statement from RFC1918 hasn't been 100% effective:



   Because private addresses have no global meaning, routing information
   about private networks shall not be propagated on inter-enterprise
   links, and packets with private source or destination addresses
   should not be forwarded across such links.


and we still don't have enough deployment of BCP38 which would also help
enforce that.

If it is possible to plug a device into the Internet I think it is better
to assume somebody probably will (and you won't be there to stop them) and
design to that assumption.

(All the recent "IoT" botnets and corresponding attacks are a result of
assuming those devices will only be connected to Private Internets, and
therefore they don't have to be individually "Internet proof" (conceptually
similar to a "water proof" watch).)

Regards,
Mark.



    Brian

>
> John Leddy
>
> From: ietf <ietf-bounces@ietf.org> on behalf of "Eric Vyncke (evyncke)" <
evyncke@cisco.com>
> Date: Sunday, February 12, 2017 at 3:56 PM
> To: Suresh Krishnan <suresh.krishnan@gmail.com>, =E7=A5=9E=E6=98=8E=E9=81=
=94=E5=93=89 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>=
,
Pete Resnick <presnick@qti.qualcomm.com>, "draft-ietf-6man-rfc2460bis@
tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "
6man-chairs@ietf.org" <6man-chairs@ietf.org>
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
> Suresh, Jinmei and Fernando,
>
> I fully agree with you Suresh, the goal of an IETF last call is to get
NEW discussion and to re-do the lengthy discussions we had on 6MAN WG.
>
> -=C3=A9ric
>
> From: ipv6 <ipv6-bounces@ietf.org> on behalf of Suresh Krishnan <
suresh.krishnan@gmail.com>
> Date: Saturday 11 February 2017 at 07:11
> To: =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinmei@wide.ad.jp>
> Cc: "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>=
,
Pete Resnick <presnick@qti.qualcomm.com>, Fernando Gont <
fgont@si6networks.com>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <
draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man-chairs@ietf.org" <
6man-chairs@ietf.org>
> Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet
Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
> Hi Jinmei,
>
> On Feb 10, 2017 1:23 PM, "=E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89" <jinmei@w=
ide.ad.jp<mailto:jinm
ei@wide.ad.jp>> wrote:
> At Thu, 9 Feb 2017 18:30:11 -0300,
> Fernando Gont <fgont@si6networks.com<mailto:fgont@si6networks.com>> wrote=
:
>
> While I largely agree with Fernando on everything he said, I have to
> admit most of the points are just repeated from the 6man discussion,
> and won't get us anywhere new by discussing these again at this point.
> I guess the only new input for the IETF last call is this:
>
>> 2) However, some folks came up with proposals to insert EH, on the basis
>> that "RFC2460 does not explicitly ban EH insertion". If there's people
>> arguing that, we clearly need to make this clear in the spec.
>>
>> 3) There was a consensus call, yes. When the call was made on the
>> mailing-list, the vast majority of supporters of "let's keep the
>> ambiguity" were folks from the same company as "2)". I have no idea if
>> this changes (or not) "consensus"... but this is clearly an important
>> datapoint.
> Although I don't want to point a finger at particular people or
> organizations without an evidence, I guess not a small number of 6man
> participants (not only those who explicitly spoke up here) suspected
> that the decision process was biased with the influence of a large and
> powerful organization and the process and resulting "consensus" was
> not really a fair one.  And I'm not an exception to it - in fact, it
> was so unbelievable to me that we can't clarify an ambiguity even when
> we were also open for future extensions, that I couldn't think of
> other reasons than a company agenda.
>
> Of course, it's quite possible that it was just a coincidence that
> many people with the same organization genuinely thought we should
> leave it ambiguous while many others strongly thought we should
> clarify it but few (if not no) people from that organization supported
> the clarification.  But I don't think we can prove it either way.
>
> But as Fernando said, I believe this point (and that several, and
> arguably more, participants suspected it) should be included in making
> the decision at the IESG and at the IETF last call.  And, whatever the
> decision, it would be more productive to move on after that and use
> our time for some other things.
>
> I am guessing that the people who spoke up during the WG process to not
put in an outright prohibition would make their case along with their
arguments here as well. We are only a week into a four week long last call.
>
> Thanks
> Suresh
>
>
>
> --------------------------------------------------------------------
> 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
--------------------------------------------------------------------

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 13 Feb. 2017 11:40 am, &quot;Brian E Carpenter&quot; &lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&g=
t; wrote:<br type=3D"attribution"><blockquote class=3D"quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">John,<br>
<div class=3D"quoted-text"><br>
On 13/02/2017 12:05, Leddy, John wrote:<br>
&gt; I=E2=80=99m trying to understand how a ban of this functionality would=
 work.=C2=A0 Is it targeted at vendor products, precluding them from implem=
enting the functionality?<br>
<br>
</div>It&#39;s targetted at interoperability across the Internet. We can ne=
ver stop<br>
people doing whatever they please inside a private domain, obviously.<br>
As always, there are no protocol police.<br>
<div class=3D"quoted-text"><br>
&gt; If there is a technical problem that can be solved by using EH inserti=
on within a domain where there are no harmful side effects, it should be ab=
le to be used.<br>
&gt; In a software networking world where functionality is being deployed t=
hat is not from traditional network vendors; solutions that solve problems =
efficiently will get deployed.<br>
<br>
</div>We had a lot of this conversation in a slightly different form prior =
to<br>
RFC 6437. It proved impossible to specify &quot;local domain&quot; rules th=
at could<br>
reach consensus. I think we&#39;d have the same problem trying to write rul=
es<br>
for header insertion/deletion within a domain. But in any case, that isn&#3=
9;t<br>
the target for RFC2460bis: the target is the Internet.<br></blockquote></di=
v></div></div><div dir=3D"auto"><br></div><div dir=3D"auto">We also know th=
at this statement from RFC1918 hasn&#39;t been 100% effective:</div><div di=
r=3D"auto"><pre style=3D"font-size:12.6667px;margin-top:0px;margin-bottom:0=
px"><br>
   Because private addresses have no global meaning, routing information
   about private networks shall not be propagated on inter-enterprise
   links, and packets with private source or destination addresses
   should not be forwarded across such links.</pre></div><div dir=3D"auto">=
<br></div><div dir=3D"auto">and we still don&#39;t have enough deployment o=
f BCP38 which would also help enforce that.</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto">If it is possible to plug a device into the Internet I =
think it is better to assume somebody probably will (and you won&#39;t be t=
here to stop them) and design to that assumption.</div><div dir=3D"auto"><b=
r></div><div dir=3D"auto">(All the recent &quot;IoT&quot; botnets and corre=
sponding attacks are a result of assuming those devices will only be connec=
ted to Private Internets, and therefore they don&#39;t have to be individua=
lly &quot;Internet proof&quot; (conceptually similar to a &quot;water proof=
&quot; watch).)</div><div dir=3D"auto"><br></div><div dir=3D"auto">Regards,=
</div><div dir=3D"auto">Mark.</div><div dir=3D"auto"><br></div><div dir=3D"=
auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
<font color=3D"#888888"><br>
=C2=A0 =C2=A0 Brian<br>
</font><div class=3D"quoted-text"><br>
&gt;<br>
&gt; John Leddy<br>
&gt;<br>
&gt; From: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@i=
etf.org</a>&gt; on behalf of &quot;Eric Vyncke (evyncke)&quot; &lt;<a href=
=3D"mailto:evyncke@cisco.com">evyncke@cisco.com</a>&gt;<br>
&gt; Date: Sunday, February 12, 2017 at 3:56 PM<br>
&gt; To: Suresh Krishnan &lt;<a href=3D"mailto:suresh.krishnan@gmail.com">s=
uresh.krishnan@gmail.com</a>&gt;, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 &lt;=
<a href=3D"mailto:jinmei@wide.ad.jp">jinmei@wide.ad.jp</a>&gt;<br>
&gt; Cc: &quot;<a href=3D"mailto:6man@ietf.org">6man@ietf.org</a>&quot; &lt=
;<a href=3D"mailto:6man@ietf.org">6man@ietf.org</a>&gt;, IETF Discussion li=
st &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, Pete Resnick=
 &lt;<a href=3D"mailto:presnick@qti.qualcomm.com">presnick@qti.qualcomm.com=
</a>&gt;, &quot;<a href=3D"mailto:draft-ietf-6man-rfc2460bis@tools.ietf.org=
">draft-ietf-6man-rfc2460bis@<wbr>tools.ietf.org</a>&quot; &lt;<a href=3D"m=
ailto:draft-ietf-6man-rfc2460bis@tools.ietf.org">draft-ietf-6man-rfc2460bis=
@<wbr>tools.ietf.org</a>&gt;, &quot;<a href=3D"mailto:6man-chairs@ietf.org"=
>6man-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:6man-chairs@ietf.org"=
>6man-chairs@ietf.org</a>&gt;<br>
&gt; Subject: Re: Last Call: &lt;draft-ietf-6man-rfc2460bis-<wbr>08.txt&gt;=
 (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard<b=
r>
&gt;<br>
&gt; Suresh, Jinmei and Fernando,<br>
&gt;<br>
&gt; I fully agree with you Suresh, the goal of an IETF last call is to get=
 NEW discussion and to re-do the lengthy discussions we had on 6MAN WG.<br>
&gt;<br>
&gt; -=C3=A9ric<br>
&gt;<br>
&gt; From: ipv6 &lt;<a href=3D"mailto:ipv6-bounces@ietf.org">ipv6-bounces@i=
etf.org</a>&gt; on behalf of Suresh Krishnan &lt;<a href=3D"mailto:suresh.k=
rishnan@gmail.com">suresh.krishnan@gmail.com</a>&gt;<br>
&gt; Date: Saturday 11 February 2017 at 07:11<br>
&gt; To: =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 &lt;<a href=3D"mailto:jinmei@=
wide.ad.jp">jinmei@wide.ad.jp</a>&gt;<br>
&gt; Cc: &quot;<a href=3D"mailto:6man@ietf.org">6man@ietf.org</a>&quot; &lt=
;<a href=3D"mailto:6man@ietf.org">6man@ietf.org</a>&gt;, IETF Discussion li=
st &lt;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;, Pete Resnick=
 &lt;<a href=3D"mailto:presnick@qti.qualcomm.com">presnick@qti.qualcomm.com=
</a>&gt;, Fernando Gont &lt;<a href=3D"mailto:fgont@si6networks.com">fgont@=
si6networks.com</a>&gt;, &quot;<a href=3D"mailto:draft-ietf-6man-rfc2460bis=
@tools.ietf.org">draft-ietf-6man-rfc2460bis@<wbr>tools.ietf.org</a>&quot; &=
lt;<a href=3D"mailto:draft-ietf-6man-rfc2460bis@tools.ietf.org">draft-ietf-=
6man-rfc2460bis@<wbr>tools.ietf.org</a>&gt;, &quot;<a href=3D"mailto:6man-c=
hairs@ietf.org">6man-chairs@ietf.org</a>&quot; &lt;<a href=3D"mailto:6man-c=
hairs@ietf.org">6man-chairs@ietf.org</a>&gt;<br>
&gt; Subject: Re: Last Call: &lt;draft-ietf-6man-rfc2460bis-<wbr>08.txt&gt;=
 (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard<b=
r>
&gt;<br>
&gt; Hi Jinmei,<br>
&gt;<br>
</div><div class=3D"quoted-text">&gt; On Feb 10, 2017 1:23 PM, &quot;=E7=A5=
=9E=E6=98=8E=E9=81=94=E5=93=89&quot; &lt;<a href=3D"mailto:jinmei@wide.ad.j=
p">jinmei@wide.ad.jp</a>&lt;mailto:<a href=3D"mailto:jinmei@wide.ad.jp">jin=
m<wbr>ei@wide.ad.jp</a>&gt;&gt; wrote:<br>
&gt; At Thu, 9 Feb 2017 18:30:11 -0300,<br>
</div><div class=3D"elided-text">&gt; Fernando Gont &lt;<a href=3D"mailto:f=
gont@si6networks.com">fgont@si6networks.com</a>&lt;mailto:<a href=3D"mailto=
:fgont@si6networks.com"><wbr>fgont@si6networks.com</a>&gt;&gt; wrote:<br>
&gt;<br>
&gt; While I largely agree with Fernando on everything he said, I have to<b=
r>
&gt; admit most of the points are just repeated from the 6man discussion,<b=
r>
&gt; and won&#39;t get us anywhere new by discussing these again at this po=
int.<br>
&gt; I guess the only new input for the IETF last call is this:<br>
&gt;<br>
&gt;&gt; 2) However, some folks came up with proposals to insert EH, on the=
 basis<br>
&gt;&gt; that &quot;RFC2460 does not explicitly ban EH insertion&quot;. If =
there&#39;s people<br>
&gt;&gt; arguing that, we clearly need to make this clear in the spec.<br>
&gt;&gt;<br>
&gt;&gt; 3) There was a consensus call, yes. When the call was made on the<=
br>
&gt;&gt; mailing-list, the vast majority of supporters of &quot;let&#39;s k=
eep the<br>
&gt;&gt; ambiguity&quot; were folks from the same company as &quot;2)&quot;=
. I have no idea if<br>
&gt;&gt; this changes (or not) &quot;consensus&quot;... but this is clearly=
 an important<br>
&gt;&gt; datapoint.<br>
&gt; Although I don&#39;t want to point a finger at particular people or<br=
>
&gt; organizations without an evidence, I guess not a small number of 6man<=
br>
&gt; participants (not only those who explicitly spoke up here) suspected<b=
r>
&gt; that the decision process was biased with the influence of a large and=
<br>
&gt; powerful organization and the process and resulting &quot;consensus&qu=
ot; was<br>
&gt; not really a fair one.=C2=A0 And I&#39;m not an exception to it - in f=
act, it<br>
&gt; was so unbelievable to me that we can&#39;t clarify an ambiguity even =
when<br>
&gt; we were also open for future extensions, that I couldn&#39;t think of<=
br>
&gt; other reasons than a company agenda.<br>
&gt;<br>
&gt; Of course, it&#39;s quite possible that it was just a coincidence that=
<br>
&gt; many people with the same organization genuinely thought we should<br>
&gt; leave it ambiguous while many others strongly thought we should<br>
&gt; clarify it but few (if not no) people from that organization supported=
<br>
&gt; the clarification.=C2=A0 But I don&#39;t think we can prove it either =
way.<br>
&gt;<br>
&gt; But as Fernando said, I believe this point (and that several, and<br>
&gt; arguably more, participants suspected it) should be included in making=
<br>
&gt; the decision at the IESG and at the IETF last call.=C2=A0 And, whateve=
r the<br>
&gt; decision, it would be more productive to move on after that and use<br=
>
&gt; our time for some other things.<br>
&gt;<br>
&gt; I am guessing that the people who spoke up during the WG process to no=
t put in an outright prohibition would make their case along with their arg=
uments here as well. We are only a week into a four week long last call.<br=
>
&gt;<br>
&gt; Thanks<br>
&gt; Suresh<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div><div class=3D"elided-text">&gt; ------------------------------<wbr>--=
----------------------------<wbr>--------<br>
&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" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt;<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
---<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/<wbr=
>listinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</div></blockquote></div><br></div></div></div>

--94eb2c123f16e79e3505485faf79--


From nobody Mon Feb 13 09:54:12 2017
Return-Path: <doug@ewellic.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7095C1296F7 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 R-U8rUPnpCsx for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 09:54:02 -0800 (PST)
Received: from p3plwbeout03-03.prod.phx3.secureserver.net (p3plsmtp03-03-2.prod.phx3.secureserver.net [72.167.218.215]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7191129547 for <ietf@ietf.org>; Mon, 13 Feb 2017 09:54:01 -0800 (PST)
Received: from localhost ([72.167.218.132]) by p3plwbeout03-03.prod.phx3.secureserver.net with bizsmtp id kHtx1u0032rz53401HtxCC; Mon, 13 Feb 2017 10:53:57 -0700
X-SID: kHtx1u0032rz53401
Received: (qmail 16049 invoked by uid 99); 13 Feb 2017 17:53:57 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.189
User-Agent: Workspace Webmail 6.6.2
Message-Id: <20170213105355.665a7a7059d7ee80bb4d670165c8327d.1c694c05b8.wbe@email03.godaddy.com>
From: "Doug Ewell" <doug@ewellic.org>
To: slim@ietf.org, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-slim-negotiating-human-language-06.txt> (Negotiating Human Language in Real-Time Communications) to Proposed Standard
Date: Mon, 13 Feb 2017 10:53:55 -0700
Mime-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UNINPkb81VK29d5kPzqVH7dF77A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 17:54:03 -0000

Gunnar Hellstr=C3=B6m wrote:=0A=0A> 5. Make use of the asterisk modifier on=
 media level with session scope=0A> also for media level purposes =0A>=0A> =
The asterisk modifier optionally appended on attribute values has in=0A> th=
e original -06 draft only a session effect. It is specified to=0A> indicate=
 if the call should be rejected or not if languages do not=0A> match. It ca=
n be appended to any humintlang attribute in the whole SDP=0A> without any =
change in effect. This independancy of placement indicates=0A> that it is w=
rongly placed. With the current definition, it should be a=0A> single separ=
ate session level attribute. Instead of specifying a=0A> separate session l=
evel attribute, it is proposed that the asterisk=0A> gets an expanded defin=
ition, so that its placement conveys meaning of=0A> value for the successfu=
l language negotiation. =0A>=0A> It has been discussed in the SLIM WG that =
the specification lacks two=0A> functions, required by the specifications b=
y other bodies who are=0A> waiting for the results of SLIM real-time work. =
(e.g. 3GPP TS 22.228=0A> and ETSI TR 103 201). 3GPP TS 22.228 requires "The=
 system should be=0A> able to negotiate the user's desired language(s) and =
modalities, per=0A> media stream and/or session, in order of preference." T=
hus negotiation=0A> with preference indication within the session is requir=
ed, not only=0A> within each media. ETSI TR 103 201 says "the Total Convers=
ation user=0A> should be able to indicate the preferred method of communica=
tion for=0A> each direction of the session, so that the call-taker can be s=
elected=0A> appropriately or an appropriate assisting service be invoked. "=
 Saying=0A> "preferred" means that it should also be possible to indicate l=
ess=0A> preferred alternatives.=0A=0AGunnar, who participated extensively i=
n the SLIM WG, appears to be=0Aattempting to re-introduce a mechanism to in=
dicate preference of=0Amodality which was considered and rejected multiple =
times by the WG.=0A=0AWG rejection of Gunnar's previous proposals to do thi=
s was based on=0Areluctance to try to solve this particular problem in the =
first version=0Aof the spec, not on any of the specific mechanisms proposed=
 to solve the=0Aproblem. Proposing a new or modified mechanism during IETF =
LC appears to=0Abe an attempt to rehash an argument made, but not won, in t=
he WG.=0A=0AIf this concerns a different issue, not merely a different way =
of=0Aapproaching it, please accept my apology and explain more clearly how =
it=0Ais different.=0A=0A =0A--=0ADoug Ewell | Thornton, CO, US | ewellic.or=
g


From nobody Mon Feb 13 10:30:10 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B37D91294A0; Mon, 13 Feb 2017 10:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 63gqeWrcP0ji; Mon, 13 Feb 2017 10:30:02 -0800 (PST)
Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 7D501129441; Mon, 13 Feb 2017 10:30:02 -0800 (PST)
Received: by mail-it0-x229.google.com with SMTP id c7so15903404itd.1; Mon, 13 Feb 2017 10:30:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ao7kQEsBm/0jl3gDgBALhJRkDP/Wk2/m2o8VpY/y09k=; b=R5UGTAaeE+NzS/SOabmNta7fsHCm7Z3sqzbT05s/RWJvZfmnr16PdKamuah1Ze/Aet eU9YdfdzVTzuhwmPYYrQZa8r51sLPzz+OHugxyvu1syabHE2jGBUgWVZv1ylfdj8JT9u ONudsTnsnbcXMAn2fbG5wAcwpRxea86tOqomjTZ2StjHIOLkczTcWCPe1BaU2mQX32zM 5LHYUb39nIVyEst9G+gFy0WfU035cV606uDT+JYT/drlmruOfag0dCj4SNdI032mD5Gv wTue96deR9qYCgGOXxpR8w8vPxTRFqQOXLdFrPwuKGksRLhiyuqZs/zvM8ZG6f4HJi15 tG1A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ao7kQEsBm/0jl3gDgBALhJRkDP/Wk2/m2o8VpY/y09k=; b=EaTvm4/SiUPUQForSIdfOWvxwjHB1nRuWPeBDVbX/V0VrWmi1hZaUuNxQeK5DLn5ZB UEKtbyOz1LUlrN1nSZv1DFaYOr7UaHZA0uPQjgTwAbuXeASOwPk9oKDzX9ahdch1quck EIVr1ER6EPboYvV1ak4W5fbzxPUN651YxNbZg9TDmCJkff0sBTf7F9TbdCIkRBhKw4MN XpFDy6flY6+VTIFeAiVpFTcNpZ3LJCjBqXcH1+tSCcu2Hu/1OdjkYsf7PzhTksQtSkLc YZtqMx4OqotYr/hUoDBURNdEeOEwyn3V+VZ7H3BsVqXILgwHf8/HL7OabGxL/j8QsRsz q93w==
X-Gm-Message-State: AIkVDXJByFPqYRQ6AwFKYaYqRvLRpedXdYG7uG6rvaOA9rbQTkmvN+Fm14qFCMUA90hd5OHKdXg7dfJJzTY9ZA==
X-Received: by 10.36.69.30 with SMTP id y30mr40150006ita.119.1487010114042; Mon, 13 Feb 2017 10:21:54 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Mon, 13 Feb 2017 10:21:53 -0800 (PST)
In-Reply-To: <148700334813.25059.6320598686717139053.idtracker@ietfa.amsl.com>
References: <148700334813.25059.6320598686717139053.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 13 Feb 2017 13:21:53 -0500
X-Google-Sender-Auth: 8kNwc2TiFBWzxQAQK9YblLGVrqU
Message-ID: <CALaySJ+ULSpfESJb7CoqtzAeN4udUaHdVxtFzeWcfcsXtWuzwQ@mail.gmail.com>
Subject: Re: Review of draft-leiba-rfc2119-update-01
To: Joel Halpern <jmh@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ajPgmqweEgPyAkbIn0Qdg1B-wKA>
Cc: rtg-dir@ietf.org, draft-leiba-rfc2119-update.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 18:30:05 -0000

Thanks for doing the review, Joel.

Barry

On Mon, Feb 13, 2017 at 11:29 AM, Joel Halpern <jmh@joelhalpern.com> wrote:
> Reviewer: Joel Halpern
> Review result: Ready
>
> I have reviewed this document on behalf of the Routing Area
> Directors.
>
> This document is ready for publication as a Best Current Practice.
>
> I do not see any issues with the document.
>


From nobody Mon Feb 13 10:48:43 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C4C1297A8 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 10:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nWSZ0rLaMpU9 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 10:48:41 -0800 (PST)
Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::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 328D61296F0 for <ietf@ietf.org>; Mon, 13 Feb 2017 10:48:41 -0800 (PST)
Received: by mail-qt0-x233.google.com with SMTP id v23so91596392qtb.0 for <ietf@ietf.org>; Mon, 13 Feb 2017 10:48:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=LhuYfRWQygJwPKkT2T3zEEeThDdR6tgl3iObhs72uUo=; b=y1X1yIHFO7JQXf7M11rxL4mApWLfBVFK6Eiy7R4VD8KNR+0t/pqOgJcco0/W+9HJfr PseG31B0qqvjQUBRkndGh+YAKrySNdQ/s+PLEOz/FZzcmLy+Q0hLf23XbnV90WX0rZLL G1ZjGrMEMQNdu4tSRhttIUXvlM9cFHzA6UR/j3vwax3fStqbDGARew9G1v/sP6g6TO0z D2kgI4LF1NY0XDi02FbyxCws5CDExGZ39OegRdtKDhOGv2D/xJ2N+vZoFdXh/IBS/fZH T+YNHDknyOg7TUKgQOk1hjTBPvkMchA6A76HjPSHZaxpJcfci2d3fbIThPu0I0qdipf3 c3eQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=LhuYfRWQygJwPKkT2T3zEEeThDdR6tgl3iObhs72uUo=; b=Y4JqSrjLpN8bQptqPyIFRDP7IorLO8WWNJac4ccCXWcmntoM3A8HtLSoXY5TXJ4KCk c/AUFbSQb1Epit0Q4GklTk1hlLrs5tM1HQ39mXbrIKbbWpTyitcBCNnJ16ZL77u0Zumm /RzsPfNS0ILJhnjAm6QwhCreuh5yVEoWUS+MqrgPknJYDFaXLoOZMLXV6Vit0RppmQBi +k6ve9l3ImxSj/L8V+2+YWpXYJJ2sZG1YVZSdXqZS1gu8rE4q/gKBl2Aw8EvltbeFCT9 ATSKeMJm+nnx4p8WMmHly8ZMrm5A0rMXJLtpgk5HcSBTbhrDfYQhXZ5e5VHyMjCcjPzt /RdA==
X-Gm-Message-State: AMke39lcJi9fKUWhPQ4buUHkEWFGYkxcxR4sqEGqwjjqUNCr8ifzftfTCMlyH1VMElpdEA==
X-Received: by 10.200.39.35 with SMTP id g32mr25305543qtg.265.1487011720277; Mon, 13 Feb 2017 10:48:40 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 37sm8032293qto.43.2017.02.13.10.48.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 10:48:39 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_56DFF2D5-B391-42B7-A5C3-963D8B4FA150"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Mon, 13 Feb 2017 13:48:37 -0500
In-Reply-To: <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-eiWLUi9TBOzontSfZEmgpuNQTk>
Cc: John C Klensin <john-ietf@jck.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 18:48:43 -0000

--Apple-Mail=_56DFF2D5-B391-42B7-A5C3-963D8B4FA150
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 13, 2017, at 12:17 PM, Dave Cridland <dave@cridland.net> wrote:
> If JMAP is to supplant IMAP - and I think that's a worthy goal even if
> its likelihood remains a matter for debate - then JMAP has to support
> the same model.
>=20
> The model of IMAP is that:
>=20
> * Each message resides in a single mailbox,
> * Each message has a set of independent flags,
> * Each message is immutable.

This would be unfortunate.  The "mailbox" paradigm really doesn't work =
well=E2=80=94as someone mentioned earlier in this thread, it makes =
synchronization needlessly slow and painful, and it also restricts the =
end user's ability to tag messages with more than one meaning.


--Apple-Mail=_56DFF2D5-B391-42B7-A5C3-963D8B4FA150
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"">On Feb 13, 2017, at 12:17 PM, Dave Cridland &lt;<a =
href=3D"mailto:dave@cridland.net" class=3D"">dave@cridland.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">If JMAP is to supplant IMAP - and I think that's =
a worthy goal even if</span><br style=3D"font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">its likelihood remains a matter for =
debate - then JMAP has to support</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">the same model.</span><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family:=
 Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">The model of IMAP is =
that:</span><br style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">* Each message resides in a single =
mailbox,</span><br style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">* Each message has a set of independent =
flags,</span><br style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">* Each message is =
immutable.</span></div></blockquote></div><br class=3D""><div =
class=3D"">This would be unfortunate. &nbsp;The "mailbox" paradigm =
really doesn't work well=E2=80=94as someone mentioned earlier in this =
thread, it makes synchronization needlessly slow and painful, and it =
also restricts the end user's ability to tag messages with more than one =
meaning.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_56DFF2D5-B391-42B7-A5C3-963D8B4FA150--


From nobody Mon Feb 13 11:04:49 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9891297CE for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:04:47 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 vrmGAukRXXTo for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:04:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC4F31296EE for <ietf@ietf.org>; Mon, 13 Feb 2017 11:04:45 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdLvQ-000ERf-C0; Mon, 13 Feb 2017 14:04:36 -0500
Date: Mon, 13 Feb 2017 14:04:29 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, Dave Cridland <dave@cridland.net>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <3974108D855D9B53126DFEA7@PSB>
In-Reply-To: <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pMvWAi8fshKG6p0Welr63f02AWo>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:04:48 -0000

(Top Post)
Exactly.  Could not have said it better myself.

There is one additional issue here.  JMAP (or some hypothetical
xMAP) can either aspire to be a cleaner, more modern, less
LISP-like interface to (more or less, see below) the same
functionality as IMAP _or_ it can aspire to be a better idea,
with a different underlying architecture and/or reference model,
functionality, etc.  

Can't have it both ways, at least without moving from
discussions about proxies and overlays and into discussions
about translators that are a lot more like gateways, gateways
that, like most of their predecessors, mostly work and mostly
preserve functionality and semantics.

My confusion about this effort -- and it has been considerable--
is that I've heard different statements claiming goals in both
categories.  That isn't acceptable, if one because a WG proposal
for one approach should be evaluated differently from one
proposing the there one.   The choice really must be made now
and, whatever it is, should be absolutely crystal-clear in the
charter... in addition to the things Dave describes below, which
should also be spelled out.

    john
  

--On Monday, February 13, 2017 09:30 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 2/13/2017 9:17 AM, Dave Cridland wrote:
>> I don't think this is true.
> ...
>> JMAP, on the other hand, can cope with both gmail style
>> labels and IMAP-style mailboxes, by stated design.
> 
> 
> The constraints/flexibility of an effort depend on the goals
> it asserts and the support for those goals.  I think it's
> dandy to target an access protocol that is substantially
> different from the features/style/whatever of IMAP.  The
> requirements are to be very clear about the
> features/style/whatever of the new effort, very clear about
> the expected benefits, and very clear about the support for
> that.
> 
> Given the long history of IMAP, the proposed JMAP effort
> should offer clear assertions of the relative differences and
> benefits of the new effort, to aid in assessing likely appeal
> of the effort.
> 
> So, for example, the above comment about JMAP's handling of
> different reference models is substantive and appealing.
> However the various notes that have been posted about JMAP
> leave me thinking that there is less clarity about the effort
> than one would like, among JMAP's supporters.
> 
> The embodiment of the clarity needs to be the charter text and
> I don't think it's made its case well enough.  For example, I
> don't see a reference to the ability to support different
> referencing models.
> 
> d/





From nobody Mon Feb 13 11:07:28 2017
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B7C71296EE; Mon, 13 Feb 2017 11:07:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lD0fWYeyPSNu; Mon, 13 Feb 2017 11:07:21 -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 055881297F0; Mon, 13 Feb 2017 11:07:19 -0800 (PST)
Received: by mail-vk0-x231.google.com with SMTP id r136so66896567vke.1; Mon, 13 Feb 2017 11:07:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=NDew0FUK8ElkqHlOhFFJAoOgzkDKBO5BiBkfzY1cYYU=; b=QwyqV12/Om7EB+mBGX0WgX78zxA9vPhc901aewOeBrCiW8lOYYkzXzQMRvBDQuNbvN pBAqzJ4FyOxtFSt7H39+mclF177fA/qeh4jkYL52tykux03EREbJMu3aSk76Uc2hBq2d DVyJm45wYey6YzMcrmDlSboXScS5R091/TRwz5mq1B2nbwKlHO0bKzvfu+FyB4k/g5O3 +/usNpFGqS1EHH5VA1rKtjoArWphmh8QW49ztM53xsHr4kYdUz9yg+vGQ0exuZTv9fiL VHvNMqoRNVmOhvkREtktBu+uknuBgY7XB9RnYBXanKFKRWVkmyzJH3jhGGPp0tNcRa/W YqMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NDew0FUK8ElkqHlOhFFJAoOgzkDKBO5BiBkfzY1cYYU=; b=n14XZLifLmaj43fg5OzZuv5vQ/Jy7/9ej5RZ+N2ly2hMehNJhjHscwee5ekak4vbnc pr6uQc5/bt44NlR6KLzPIRBk4ycdUfMVYi1J3tTEDFDZPMvOPQBFD6vr6gCm7Xw5LiN9 SxZvpZlouFTQhPX7WIzTHxb4oKJDu0PiUIJql8min+8AHWX/tLUxcP88Z4fLyMteuO3Q uSK6L4dnoKfNlXXNTLhzVnyoe1BSsIi1yOEJq3CBJkA3J/uujg2rFE8ubf+tMgWUGzKg mmXyNO9FSDV4jSoAwQvN7qQXnscY99rdUlnZCSFD/JF1hf7FSNoSJA4BMPJ51LyAdWUs CWSA==
X-Gm-Message-State: AMke39kk6wnT5cZ2fmD3xTJfruyj362JL7zHgPuAHR1Q6mPfQNPDGj6gjbSkQNkap5EaP5QB9SRYuO5+OPO+eA==
X-Received: by 10.31.191.71 with SMTP id p68mr9926607vkf.50.1487012837822; Mon, 13 Feb 2017 11:07:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.88.90 with HTTP; Mon, 13 Feb 2017 11:06:57 -0800 (PST)
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 13 Feb 2017 11:06:57 -0800
Message-ID: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com>
Subject: Re: IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: slim@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a114ddaf8f9996105486e27b7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XgN1GbiDzPLTApg4ZDC1CRkKQyA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:07:23 -0000

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

Looking over Section 5.4, it seems to me that the title "Silly States" may
not be appropriate, because it mixes discussion of combinations of media
and language that have an "undefined" meaning with combinations for which
normative guidance can be provided  So rather than having a single "Silly
States" section, perhaps we can have a section on "Undefined States" (for
those combinations which have an undefined meaning) provide normative
guidance on defined combinations elsewhere.

5.4 <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4>.
Silly States

   It is possible to specify a "silly state" where the language
   specified does not make sense for the media type, such as specifying
   a signed language for an audio media stream.

   An offer MUST NOT be created where the language does not make sense
   for the media type.  If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent (e.g., if American Sign Language is specified
   for an audio media stream, this might be interpreted as a desire to
   use spoken English).

   A spoken language tag for a video stream in conjunction with an audio
   stream with the same language might indicate a request for
   supplemental video to see the speaker.


[BA] Rather than using terms like "might" for combinations that could have a

defined meaning, I would like to see the specification provide normative

language on these use cases. In particular, I would like the
specification to describe:


a. What it means when a spoken language tag is included for a video stream.

Is this to be interpreted as a request for captioning?

b. What it means when a signed language tag is included for an audio stream.

Is the meaning of this "undefined" and if so, should it be ignored?

c. What it means when a signed language tag is included for a text stream.


If some of these scenarios are not defined, the specification can say

"this combination does not have a defined meaning" or something like that.

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

<div dir=3D"ltr"><span class=3D"gmail-im" style=3D"font-size:12.8px"><div>L=
ooking over Section 5.4, it seems to me that the title &quot;Silly States&q=
uot; may not be appropriate, because it mixes discussion of combinations<sp=
an style=3D"font-size:12.8px">=C2=A0of media and language that have an &quo=
t;undefined&quot; meaning with combinations=C2=A0</span><span style=3D"font=
-size:12.8px">for which normative guidance can be provided =C2=A0So rather =
than having a single &quot;Silly States&quot; section, perhaps we can have =
a section on &quot;Undefined States&quot; (for those combinations which hav=
e an undefined meaning) provide normative guidance on defined combinations =
elsewhere.</span></div><div><br></div><div><pre class=3D"gmail-newpage" sty=
le=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)=
"><span class=3D"gmail-h3" style=3D"line-height:0pt;display:inline;font-siz=
e:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:inline;font-si=
ze:1em"><a class=3D"gmail-selflink" name=3D"section-5.4" href=3D"https://to=
ols.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4=
" style=3D"color:black;text-decoration:none">5.4</a>.  Silly States</h3></s=
pan>

   It is possible to specify a &quot;silly state&quot; where the language
   specified does not make sense for the media type, such as specifying
   a signed language for an audio media stream.</pre><pre class=3D"gmail-ne=
wpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:=
rgb(0,0,0)">   An offer MUST NOT be created where the language does not mak=
e sense
   for the media type.  If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent (e.g., if American Sign Language is specified
   for an audio media stream, this might be interpreted as a desire to
   use spoken English).

   A spoken language tag for a video stream in conjunction with an audio
   stream with the same language might indicate a request for
   supplemental video to see the speaker.</pre><pre class=3D"gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,=
0,0)"><br></pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;m=
argin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">[BA] Rather than using te=
rms like &quot;might&quot; for combinations that could have a</pre><pre cla=
ss=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bot=
tom:0px;color:rgb(0,0,0)">defined meaning, I would like to see the specific=
ation provide normative </pre><pre class=3D"gmail-newpage" style=3D"font-si=
ze:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">language on=
 these use cases. In particular, I would like the specification to describe=
: </pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-to=
p:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-new=
page" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:r=
gb(0,0,0)">a. What it means when a spoken language tag is included for a vi=
deo stream. </pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px=
;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is this to be interpret=
ed as a request for captioning?</pre><pre class=3D"gmail-newpage" style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">b. W=
hat it means when a signed language tag is included for an audio stream.</p=
re><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px=
;margin-bottom:0px;color:rgb(0,0,0)">Is the meaning of this &quot;undefined=
&quot; and if so, should it be ignored?</pre><pre class=3D"gmail-newpage" s=
tyle=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,=
0)">c. What it means when a signed language tag is included for a text stre=
am.</pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-ne=
wpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:=
rgb(0,0,0)">If some of these scenarios are not defined, the specification c=
an say</pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margi=
n-top:0px;margin-bottom:0px;color:rgb(0,0,0)">&quot;this combination does n=
ot have a defined meaning&quot; or something like that.</pre></div></span><=
/div>

--001a114ddaf8f9996105486e27b7--


From nobody Mon Feb 13 11:20:49 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77849129868 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:20:47 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Ua9zHF2p0LKV for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:20:46 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D66A129862 for <ietf@ietf.org>; Mon, 13 Feb 2017 11:20:46 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdMB0-000EUA-F1; Mon, 13 Feb 2017 14:20:42 -0500
Date: Mon, 13 Feb 2017 14:20:36 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <mellon@fugue.com>, Dave Cridland <dave@cridland.net>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <8FE91176833F1697D9844B25@PSB>
In-Reply-To: <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tL9otgJvdZ8V3QsyKBvEjbVIPl4>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:20:47 -0000

--On Monday, February 13, 2017 13:48 -0500 Ted Lemon
<mellon@fugue.com> wrote:

>> The model of IMAP is that:
>>=20
>> * Each message resides in a single mailbox,
>> * Each message has a set of independent flags,
>> * Each message is immutable.
>=20
> This would be unfortunate.  The "mailbox" paradigm really
> doesn't work well=E2=80=94as someone mentioned earlier in this
> thread, it makes synchronization needlessly slow and painful,
> and it also restricts the end user's ability to tag messages
> with more than one meaning.

Just a clarification in the hope of understanding where we
disagree...

I would have described the IMAP model as assuming that each
message is associated with a single mailbox.  Most of the issues
you mention are associated with "resides".  Up to a point, it is
possible to use a Google-like arrangement to support all of the
IMAP functionality I can think of simply by attaching a label or
attribute with the mailbox name and constraining retrievals,
searches, and displays accordingly.   That is exactly what at
least some of the systems that use a Relational DBMS as a
mailstore do, whether they then have "relation per user" or
treat the UserID as yet another attribute.

That may not be the best thing to do and may or may not provide
equivalent functionality and efficiency for various operations.
In particular, it still implies some advantages for having all
of the messages associated with a given mailbox on the same host
or closely-related set of hosts and I have no idea whether gmail
does that or not.    But, if one goes much past that, my earlier
comments about a switch in reference models and fundamental
architecture apply.

   john


From nobody Mon Feb 13 11:25:30 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 296601297B8 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h4ZmtLn6hKuL for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:25:26 -0800 (PST)
Received: from mail-qk0-x236.google.com (mail-qk0-x236.google.com [IPv6:2607:f8b0:400d:c09::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 4E6F9129618 for <ietf@ietf.org>; Mon, 13 Feb 2017 11:25:26 -0800 (PST)
Received: by mail-qk0-x236.google.com with SMTP id s186so103784628qkb.1 for <ietf@ietf.org>; Mon, 13 Feb 2017 11:25:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nOVnHDkOpIuPyVbnJKVp8bLTyh8XubDxqNRhJ/RR4R0=; b=1FMzUd0h62dbB5iYGQICzBoCqYALm5NhknpdfXICxjkGc5fZ0Sn4xu0Yrf/bAbsNFz fdQ01J5bETW2ts/WddgNSEjVluewvSEFE1K6FDi3Groes3/CZXRKQgYv/x9SWaC2KWXt YMeg+WZOPGra+EF/a00GbspjrpZfnw91r2xOboPLUfNjN0HtJ0k+PbC8nLm3Ka4Xe9z2 GHxBhM85gptOyjGa/Zz7k1VBmAp7cTPR6ht8dLxCDPnabtpAiNWO9AvWIcxr+rRGTSST +gl0XkCZy1EZMq8Ci9kVLNgrVYEOeNsxezpHiIWSo7IE0n4BCM/OUDB5/+tC4gizpENK WlNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nOVnHDkOpIuPyVbnJKVp8bLTyh8XubDxqNRhJ/RR4R0=; b=mLp9My9No9C07ACYu2e7h1pUjp2f0aqcgxBGn3BKqCdaLTNgvL5Q6K/UaFFYjH5HJR VBfSySLTi0WCwVvkRbu01nWw5qguFuTzHRuTlS0GbzibyGjislbbHD+zDWPclfOsq/2Z Qp8Udv/VMUw6E7/xQLyJOxZPH35Xkn9FPDvmqtvQLeLgQc8P+ZXnb6NGa4A8KO3MB/bi 2iBe7t7v4aclmY/ynbcd6OYrHoFjoFONwG90zugtX5n5Suwj0MHvTDk8PptnPHdqLpqJ qRt/BIBn7+9F7zk+h2q6z4IS6EDmzPW1xb8nE3hzSsMI5ESzgBd7vQ7ljZtfytmrfVnj saXQ==
X-Gm-Message-State: AMke39nltdojHsEsEUlOUyePZ6bPwo+UxsRvm47nbXRLsl7LZ1a88w6jfLe/lFZK2i4/zw==
X-Received: by 10.55.71.13 with SMTP id u13mr21750125qka.300.1487013925488; Mon, 13 Feb 2017 11:25:25 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id d191sm8110240qke.15.2017.02.13.11.25.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 11:25:24 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B2B0ED0F-62ED-4F7D-A977-0E82D6623BC4@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4552FF5B-9ED5-468A-BABB-65C7A0BDF198"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Mon, 13 Feb 2017 14:25:23 -0500
In-Reply-To: <8FE91176833F1697D9844B25@PSB>
To: John C Klensin <john-ietf@jck.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com> <8FE91176833F1697D9844B25@PSB>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QMU1RvSJZquc_dzRKJeZHQeycBI>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:25:28 -0000

--Apple-Mail=_4552FF5B-9ED5-468A-BABB-65C7A0BDF198
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 13, 2017, at 2:20 PM, John C Klensin <john-ietf@jck.com> wrote:
> I would have described the IMAP model as assuming that each
> message is associated with a single mailbox.  Most of the issues
> you mention are associated with "resides".  Up to a point, it is
> possible to use a Google-like arrangement to support all of the
> IMAP functionality I can think of simply by attaching a label or
> attribute with the mailbox name and constraining retrievals,
> searches, and displays accordingly.   That is exactly what at
> least some of the systems that use a Relational DBMS as a
> mailstore do, whether they then have "relation per user" or
> treat the UserID as yet another attribute.

Indeed, but then what you are saying is that replicating the IMAP data =
model is _not_ necessary, which is my point.   If you think of the data =
store of email messages as a single relation, with something like a =
message ID as the key, then it's easy to synchronize with the server: =
you just make sure that your copy of the relation has the intended =
subset of all messages in the relation, and it's very easy to compare to =
see whether this is the case.   If, on the other hand, you have N =
relations, each of which is a mailbox, then synchronizing becomes a =
process of iterating across the set of all relations, synchronizing each =
one.

When you describe it using the relational model, I think it's pretty =
obvious why you want the single-relation model, and not the =
multiple-relation model.


--Apple-Mail=_4552FF5B-9ED5-468A-BABB-65C7A0BDF198
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 13, 2017, at 2:20 PM, John C Klensin &lt;<a =
href=3D"mailto:john-ietf@jck.com" class=3D"">john-ietf@jck.com</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">I would have described the IMAP model as =
assuming that each</span><br style=3D"font-family: Menlo-Regular; =
font-size: 14px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">message is associated with a single =
mailbox. &nbsp;Most of the issues</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">you mention are associated with =
"resides". &nbsp;Up to a point, it is</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">possible to use a Google-like =
arrangement to support all of the</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">IMAP functionality I can think =
of simply by attaching a label or</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">attribute with the mailbox name =
and constraining retrievals,</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">searches, and displays =
accordingly. &nbsp;&nbsp;That is exactly what at</span><br =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">least some of the systems that use a Relational =
DBMS as a</span><br style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span=
 style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">mailstore do, whether they then have "relation =
per user" or</span><br style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span=
 style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">treat the UserID as yet another =
attribute.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Indeed, but then what you are saying is that replicating the =
IMAP data model is _not_ necessary, which is my point. &nbsp; If you =
think of the data store of email messages as a single relation, with =
something like a message ID as the key, then it's easy to synchronize =
with the server: you just make sure that your copy of the relation has =
the intended subset of all messages in the relation, and it's very easy =
to compare to see whether this is the case. &nbsp; If, on the other =
hand, you have N relations, each of which is a mailbox, then =
synchronizing becomes a process of iterating across the set of all =
relations, synchronizing each one.</div><div class=3D""><br =
class=3D""></div><div class=3D"">When you describe it using the =
relational model, I think it's pretty obvious why you want the =
single-relation model, and not the multiple-relation model.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_4552FF5B-9ED5-468A-BABB-65C7A0BDF198--


From nobody Mon Feb 13 11:52:26 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5016812989C for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:52:25 -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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5YJzJdgp_zo for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:52:23 -0800 (PST)
Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::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 0D58912986D for <ietf@ietf.org>; Mon, 13 Feb 2017 11:52:22 -0800 (PST)
Received: by mail-wr0-x233.google.com with SMTP id 89so157991821wrr.2 for <ietf@ietf.org>; Mon, 13 Feb 2017 11:52:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=cv+T+WNVovI/7qmnobA/lN7r+fnLKnmaaJNkuJ/zmTs=; b=jb3UbsrL2DqXHxDIXkc8pQ05k0v9SJOk1QRmfOWIaSuQCf6Yl0WrD1To4dWEuFkMCx VlcIWHDcLI9OBEGmuxRgnKN1BJXgJmPnJWsHhlZ/1gpvy10u178oEYiwWDtlE4lD4hxS oKAuki/ZqgEkTgm+igjmWoXWC9DL0NcW8UX3g=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=cv+T+WNVovI/7qmnobA/lN7r+fnLKnmaaJNkuJ/zmTs=; b=qieX0pJTiQsuYxIe9LEZm68j+CFx2xzkpttkyOvK/oVy8iqoHHxZsEwcyMHGQxvyZq X3GKjzNoSuKWDYZMu83UhdwjBn4PvAfGCq8gyJHaQkf3ayKdKLPgWs5tPxKrg7N2R+5Z abqPh3ZbBBbJThmqnKdE6Jacq9FHkCYVgSPusgt9U/ZyuHLBHOwYCplpaCMi+Vqd6JNg yicSWi010tO7a3MttzPTPu9SdkMexd5+Vb6usd5gMURLsIb5SqHEK3j96pStlZOB2CtV AySxnwfTALJzeLnaNYXlxAPiQq7X3gyQbRl9DRaodH54IFUPC72Pfbyg/gpcoIsU1eNG nQZQ==
X-Gm-Message-State: AMke39ljKmB32gS54orlUUwPEfvnpI3Y5lRmJE4FvwumM95tyCCsfGLvvXOHuynBrM8Z7eSls+Eze8wdrnb2W022
X-Received: by 10.223.152.2 with SMTP id v2mr21418025wrb.109.1487015540436; Mon, 13 Feb 2017 11:52:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.136.199 with HTTP; Mon, 13 Feb 2017 11:52:19 -0800 (PST)
In-Reply-To: <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com>
From: Dave Cridland <dave@cridland.net>
Date: Mon, 13 Feb 2017 19:52:19 +0000
Message-ID: <CAKHUCzzToOM4YAeeJTdiqx4av2JMuFP1Vgo1-XLVQJBs11vuiA@mail.gmail.com>
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L-EMRbNEvaVTa087iM7EGwdJf2M>
Cc: John C Klensin <john-ietf@jck.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:52:25 -0000

On 13 February 2017 at 18:48, Ted Lemon <mellon@fugue.com> wrote:
> On Feb 13, 2017, at 12:17 PM, Dave Cridland <dave@cridland.net> wrote:
>
> If JMAP is to supplant IMAP - and I think that's a worthy goal even if
> its likelihood remains a matter for debate - then JMAP has to support
> the same model.
>
> The model of IMAP is that:
>
> * Each message resides in a single mailbox,
> * Each message has a set of independent flags,
> * Each message is immutable.
>
>
> This would be unfortunate.  The "mailbox" paradigm really doesn't work
> well=E2=80=94as someone mentioned earlier in this thread, it makes synchr=
onization
> needlessly slow and painful, and it also restricts the end user's ability=
 to
> tag messages with more than one meaning.
>

I'm not claiming it's a good model, or even (see John's messages) that
this precludes any other model being made to fit. But I *am* asserting
this is the model around which IMAP was designed. In fact, I could go
further and suggest that at least some portions of the IMAP design
assume that a mailbox is embodied by a single file, but workarounds
for that issue have been long-implemented in the community. And other
models are possible to expose with greater or lesser degrees of
fidelity.

When gmail, for example, exposes its mailstore over IMAP, it does so
by playing fast and loose (and often loose) with the IMAP model. So
messages are visible in multiple mailboxes, but there's no method
exposed within IMAP that allows a client to understand that - to the
client, they're distinct messages with the same content. Flags (or
labels, which are exposed as mailbox names) change on all the copies
in step, but the copies remain copies, from an IMAP perspective.

Within JMAP, the semantics available are a proper superset of IMAP, so
while the IMAP model can be exposed, so can a more gmail-like concept
wherein the same message can appear in multiple mailboxes, for
example. This means, as a casual observation, that the JMAP model (and
therefore protocol) can be used to expose nearly every mailstore
available. Curiously, this was the driver behind some of IMAP's design
choices at the time.

I'd recommend, if you're interested in the differences between the
JMAP and IMAP models, to go look at the https://jmap.io site, which
explains them very thoroughly.

I'd note in passing that I was deeply skeptical of JMAP initially, and
I've been persuaded by solid technical argument as well as market
pressures. I'd be curious about concrete issues rather than
hypothetical issues.

Dave.


From nobody Mon Feb 13 11:58:49 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E398012986D for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:58:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p-ekyvv0QckE for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 11:58:45 -0800 (PST)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::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 9D15612988F for <ietf@ietf.org>; Mon, 13 Feb 2017 11:58:45 -0800 (PST)
Received: by mail-wm0-x22d.google.com with SMTP id v77so551895wmv.0 for <ietf@ietf.org>; Mon, 13 Feb 2017 11:58:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uZgZiLPOi76L1+ywJmI6/CVP2PqkNiv4QIUxfMU30vc=; b=iXQTRa5cV+2KmAxiIokDMj/f3QKynAe3pYomA0VVgC293MPWfDRXpXVfylfMAhJLOz IVgrm/yTIbRtJb3XAQG4UiFIWkSt0SsD8+Qc1Q3xZb5p7Fam6M4TP3Ssl+ZpD81ZPKBp WCGSQ3DKEWHybaebUmgVYAW1Jzc04mcMld5jU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uZgZiLPOi76L1+ywJmI6/CVP2PqkNiv4QIUxfMU30vc=; b=gHbk5+AVWbmsaxo0i/WWKS9NstHnfRx1yzz/KLQpmzPLg/NiQWNscDWvTQNXUWwvFg vipK0V9SHTLQXNBlP6UEuvNbb5RFnPUspyzIt1BONFOOnCh6JFs4RzYGchzpBQg2wiyy d/x378teDNUzpFPCnquWRUK0fBZFjlpl9bFgH3KU0okY0bgovujNZ9tdUG+qjkfleyV0 5fXU/rL7cYK602mHOSHC12b5rC2nlWHhG4dQ34ZDgpKIVaVXrGrgwSAhs7kITNXyoj2V fQKFV+UCGr4nRhfczqpmWS9QN5t2PSAcocNCC0zWmtmIpHIg2sGoI+ZiWsyR611a7yRL 2Sbw==
X-Gm-Message-State: AMke39maltUaacvZpZUmNPw5L4eKysPMXE1ThRX4tz/CG6l+HvIh+DO57NZ+dqWSg8xg9syAocyk6GoMm14lkI88
X-Received: by 10.28.128.205 with SMTP id b196mr53961wmd.21.1487015924052; Mon, 13 Feb 2017 11:58:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.136.199 with HTTP; Mon, 13 Feb 2017 11:58:43 -0800 (PST)
In-Reply-To: <3974108D855D9B53126DFEA7@PSB>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <23132594-9f68-d7dc-fe92-6487182d4e59@dcrocker.net> <3974108D855D9B53126DFEA7@PSB>
From: Dave Cridland <dave@cridland.net>
Date: Mon, 13 Feb 2017 19:58:43 +0000
Message-ID: <CAKHUCzxgLSdOcGCMcK3qtdCzACsnSUSD8Qec+xc1_ksV=B18Fw@mail.gmail.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iFOsy1eFG0MntCa4eDNQUVKwhnA>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 19:58:47 -0000

On 13 February 2017 at 19:04, John C Klensin <john-ietf@jck.com> wrote:
> There is one additional issue here.  JMAP (or some hypothetical
> xMAP) can either aspire to be a cleaner, more modern, less
> LISP-like interface to (more or less, see below) the same
> functionality as IMAP _or_ it can aspire to be a better idea,
> with a different underlying architecture and/or reference model,
> functionality, etc.
>
> Can't have it both ways

I feel sure I'm misunderstanding something here, because clearly you can.

If the underlying model of JMAP is a proper superset of that of IMAP,
then it can both provide the option of different underlying
architectures and/or reference models, and yet also provide a cleaner
interface to the existing IMAP model.

It means that some mailservices, which wish to remain perfectly
compatible with IMAP, can be equally exposed over JMAP (for example,
Cyrus) or exposed via a JMAP/IMAP gateway services. Yet others with a
model that is different to some degree (gmail) will be exposed with
higher fidelity and less awful hacks.

How is this not achieving both goals here?

I understand that these goals *could* be in conflict, but I think it
is a false dichotomy, and one in this case that does not exist.

Dave.


From nobody Mon Feb 13 12:04:12 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 917C112986C for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 12:04:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bX404i-24DJQ for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 12:04:07 -0800 (PST)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::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 E33CB1296D1 for <ietf@ietf.org>; Mon, 13 Feb 2017 12:04:05 -0800 (PST)
Received: by mail-qk0-x22c.google.com with SMTP id p22so12610245qka.0 for <ietf@ietf.org>; Mon, 13 Feb 2017 12:04:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=WooIJIX4TZ1jMmc/xZzy4ANdsFFS3Npe6Hz+QVHn/Ac=; b=KNzRad12qP4e7U/luNnndrkYEdUbrBRxfkvh9WkbB8WE2h/W3fwMBmB5Zs+Q6Zt9dd iSqDhmc+etaQCFk35xkvhivKXMD8N83TV1fn+fEsha6UGvsnE8Km3zc7QnktbGqktDah xWu2AYjs3rF99wB4V0Rl6KmHsdnDjxOM9VXqOu/2NfQ8HeDxpKJ+30rzQmWZ1EguyvLm OtJEnURkz6fb58CT0LDZYxo8LybYu5FwQ/mwapwrPfh4476z42lR2CdB36iAdn5RSV1Q +jiYxJ3vc4aLYNWsskng/5sqZupMcIMmHmRuwUNthhIs+SlToWAGmXVJzNLe7HkHLxNE uWdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=WooIJIX4TZ1jMmc/xZzy4ANdsFFS3Npe6Hz+QVHn/Ac=; b=ijEbAQuXHOs4G6+XYu79/wOGvpBuRnqeZtJzQDWzBXwnIz0tgMk0yi7OfTx4WKqgeC ilQObdOaFrerGzZi1YoSSEyP/FJ35OHRJGb+PLmO6BQtc8EfaUoo3q52OwQnIc8kVoBN /T1KbL2lf+9oweZ87f17JO+OrmwF85CIql3e298VwF9gssojLoe2Tzt5AtL93j/xMOWP l0TWLgQshy9o+SOPf6bBWJ69kJsytmvRCGurNz4RyJ0GS9GKYifQ7FfMuM5xsZHJbMdM f5ukdjL1Br8EUiMgxqRucoHvpbD+6soMOUPivNLzLSHUzLRkUicshnPqS9vSTK3uhUgH Awug==
X-Gm-Message-State: AMke39k+rNzeZ7pVrI+HOmfgfux+JjG1WxGzDCwMb2CboImsnZKBY5gitpWc+kigC6T3yw==
X-Received: by 10.55.79.8 with SMTP id d8mr22056995qkb.50.1487016244969; Mon, 13 Feb 2017 12:04:04 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id f126sm8121762qkc.47.2017.02.13.12.04.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 12:04:03 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <90F085DD-499D-4AF3-AFAC-69CA88214B86@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E3E943B5-A5A1-4AB9-A3F0-AD288AEC972D"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Jmap] WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Date: Mon, 13 Feb 2017 15:04:02 -0500
In-Reply-To: <CAKHUCzzToOM4YAeeJTdiqx4av2JMuFP1Vgo1-XLVQJBs11vuiA@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <CAKHUCzyQSTiLXg9W+ePwwm=B01TNgCN+L729pzP1iZvqG3Kweg@mail.gmail.com> <E555C5F4-2B61-4705-B62C-998769E5FC1D@fugue.com> <CAKHUCzzToOM4YAeeJTdiqx4av2JMuFP1Vgo1-XLVQJBs11vuiA@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EzqPBIscfyrPMri4m9SgbZDRbKE>
Cc: John C Klensin <john-ietf@jck.com>, Alexey Melnikov <alexey.melnikov@isode.com>, Ned Freed <ned.freed@mrochek.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 20:04:09 -0000

--Apple-Mail=_E3E943B5-A5A1-4AB9-A3F0-AD288AEC972D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 13, 2017, at 2:52 PM, Dave Cridland <dave@cridland.net> wrote:
> Within JMAP, the semantics available are a proper superset of IMAP, so
> while the IMAP model can be exposed, so can a more gmail-like concept
> wherein the same message can appear in multiple mailboxes, for
> example. This means, as a casual observation, that the JMAP model (and
> therefore protocol) can be used to expose nearly every mailstore
> available. Curiously, this was the driver behind some of IMAP's design
> choices at the time.

Okay, thanks for clarifying.   The jmap.io <http://jmap.io/> site =
unfortunately has an invalid certificate, but had some useful info.   =
For some reason I thought you were proposing going back to the straight =
IMAP model instead of the new JMAP model, which would sadden me.   :)


--Apple-Mail=_E3E943B5-A5A1-4AB9-A3F0-AD288AEC972D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 13, 2017, at 2:52 PM, Dave Cridland &lt;<a =
href=3D"mailto:dave@cridland.net" class=3D"">dave@cridland.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 14px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Within JMAP, the semantics available are a =
proper superset of IMAP, so</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">while the IMAP model can be =
exposed, so can a more gmail-like concept</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">wherein the same message can =
appear in multiple mailboxes, for</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">example. This means, as a casual =
observation, that the JMAP model (and</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">therefore protocol) can be used =
to expose nearly every mailstore</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">available. Curiously, this was =
the driver behind some of IMAP's design</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">choices at the =
time.</span></div></blockquote></div><br class=3D""><div class=3D"">Okay, =
thanks for clarifying. &nbsp; The <a href=3D"http://jmap.io" =
class=3D"">jmap.io</a>&nbsp;site unfortunately has an invalid =
certificate, but had some useful info. &nbsp; For some reason I thought =
you were proposing going back to the straight IMAP model instead of the =
new JMAP model, which would sadden me. &nbsp; :)</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_E3E943B5-A5A1-4AB9-A3F0-AD288AEC972D--


From nobody Mon Feb 13 12:12:48 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF821293D6; Mon, 13 Feb 2017 12:12:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Chair <chair@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: IASA 2.0: Challenges and Opportunities Workshops
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148701676326.25013.13898050851695958169.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 12:12:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NBhbbeFr-UZq86YnjUn2XKEEDUk>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org, chair@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 20:12:43 -0000

Last year, we talked about the need to review and possibly rework our 
administrative arrangements at the IETF, dubbed the IASA 2.0 project [1].
We are now arranging a series of virtual workshops related to this effort.

For background, the IASA arrangements were created more than ten years
ago, when the IETF initially took charge of its own administration [2]. The
arrangements have served the IETF well, but there’s been considerable
change in the necessary tasks and in the world around us since then [3].
What administrative arrangements will best support the IETF going forward?

To make changes, we first need to understand what challenges or missed 
opportunities there are in the current system. We believe there are a
number of areas in which we are currently facing challenges: structural
issues regarding the roles and interfaces between the IETF, the IAOC,
ISOC, the IESG, and contractors; availability of staff, contractor, and
volunteer resources compared to the administrative workload; internal
IAOC organizational issues; and challenges to the IETF funding model.
But we want to hear from the community about what problems you
see, and what you think is working well.

To do that we’re setting up two virtual workshops, open to everyone from
the community and people who are or have worked in some of these
administrative roles. Those who are less familiar with IETF administration
are strongly encouraged to read BCP 101 and draft-daigle-iasa-retrospective
prior to the workshops.

The workshops are virtual meetings where the participants can provide
their experiences and suggestions. The primary focus is on identifying
current challenges and opportunities. Proposed changes and solutions
will be dealt with in a later phase. Meeting notes and an Internet Draft 
summarising the input will be produced afterwards.

The agenda will be the same for both workshops, but we are having two
to better accommodate participants in different time zones. The two
workshops are both on Tuesday February 28. The first one is at 11:00 UTC
(6:00AM ET / 12:00 noon CET) and the second one at 16:00 UTC (11:00AM
ET / 17:00 CET).

We will circulate a workshop agenda soon, but most of it will be about
giving you all an opportunity to provide your thoughts. Connection 
details will be sent later.

We may also reserve agenda time at IETF 98 for follow-up discussion
depending on the outcome of the workshops. We’ve also set up a
mailing list for discussions related to this topic at
https://www.ietf.org/mailman/listinfo/iasa20.

Please join one of the workshops and/or the mailing list and provide
your input!

Jari Arkko, IETF Chair
Alissa Cooper, Incoming IETF Chair

[1] https://www.ietf.org/blog/2016/11/proposed-project-ietf-administrative-support-2-0/
[2] http://tools.ietf.org/html/rfc4071
[3] http://tools.ietf.org/html/draft-daigle-iasa-retrospective


From nobody Mon Feb 13 12:36:12 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BEE2129795; Mon, 13 Feb 2017 12:36:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Charles Perkins <charles.perkins@earthlink.net>
To: <int-dir@ietf.org>
Subject: Review of draft-ietf-anima-grasp-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148701816643.25075.11558262573283847855.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 12:36:06 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PlJ9SgdwT5mdOPqF2fDDIfAeHMQ>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 20:36:06 -0000

Reviewer: Charles Perkins
Review result: On the Right Track

I think the document has some noteworthy issues.  A lot of text is
imprecise, which will surely lead to many misinterpretations. In some
places, ACP seems to be mandated, and in other places that is relaxed
to mean "a sufficient security mechanism".  It would be better to
identify the security requirements, and put them unmistakably in the
Security Considerations section, which deserves to have teeth.

Other language is erroneously broad and therefore misleading and
subject to
misinterpretation.  Other parts of the document seem more
philosophical than
prescriptive, adding to a general air of informality. These are noted
in the
annotated document below.

It should be considered to break the document into a Requirements
document and
a more rigorously defined protocol solution document.  I am guessing
that the
protocol solution included with this document will require some
iterations in order to be precise enough to really work, and in the
meantime the Requirements (separately) need to be a lot sharper.

Two specific editorial nits:

- "Exceptionally" is used to mean "as an exceptional case", the
opposite of "typically".  But common language for that term really
means something different enough to be confusing.  Besides, protocol
design either DOES or DOES NOT work for exceptional cases.  It has to
be decided; and if the design DOES work, then identifying a case as
atypical does not really matter.

- "Additionally" is almost always redundant and should be avoided.

A lot of other editorial comments are embedded in the following
"09cep" revised version of the document, preceded by my initials
"CEP". 

========================================================================



Network Working Group                                         C.
Bormann
Internet-Draft                                   Universitaet Bremen
TZI
Intended status: Standards Track                       B. Carpenter,
Ed.
Expires: June 18, 2017                                 Univ. of
Auckland
                                                             B. Liu,
Ed.
                                            Huawei Technologies Co.,
Ltd
                                                       December 15,
2016


             A Generic Autonomic Signaling Protocol (GRASP)
                       draft-ietf-anima-grasp-09cep

Abstract

   This document establishes requirements for a signaling protocol
that
   enables autonomic devices and autonomic service agents to
dynamically
   discover peers, to synchronize state with them, and to negotiate
   parameter settings with them.  The document then defines a
   general protocol for discovery, synchronization and negotiation,
   while the technical objectives for specific scenarios are to be
   described in separate documents.  An Appendix briefly discusses
   existing protocols with comparable features.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current
Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six
months
   and may be updated, replaced, or obsoleted by other documents at
any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on June 18, 2017.

Copyright Notice

   Copyright (c) 2016 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of



Bormann, et al.           Expires June 18, 2017                 [Page
1]

Internet-Draft                    GRASP                    December
2016


   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with
respect
   to this document.  Code Components extracted from this document
must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .  
3
   2.  Requirement Analysis of Discovery, Synchronization and
       Negotiation . . . . . . . . . . . . . . . . . . . . . . . . .  
4
     2.1.  Requirements for Discovery  . . . . . . . . . . . . . . .  
5
     2.2.  Requirements for Synchronization and Negotiation
           Capability  . . . . . . . . . . . . . . . . . . . . . . .  
6
     2.3.  Specific Technical Requirements . . . . . . . . . . . . .  
9
   3.  GRASP Protocol Overview . . . . . . . . . . . . . . . . . . . 
10
     3.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . . 
10
     3.2.  High Level Deployment Model . . . . . . . . . . . . . . . 
12
     3.3.  High Level Design Choices . . . . . . . . . . . . . . . . 
13
     3.4.  Quick Operating Overview  . . . . . . . . . . . . . . . . 
16
     3.5.  GRASP Protocol Basic Properties and Mechanisms  . . . . . 
16
       3.5.1.  Required External Security Mechanism  . . . . . . . . 
16
       3.5.2.  Constrained Instances . . . . . . . . . . . . . . . . 
17
       3.5.3.  Transport Layer Usage . . . . . . . . . . . . . . . . 
19
       3.5.4.  Discovery Mechanism and Procedures  . . . . . . . . . 
20
       3.5.5.  Negotiation Procedures  . . . . . . . . . . . . . . . 
23
       3.5.6.  Synchronization and Flooding Procedure  . . . . . . . 
25
     3.6.  GRASP Constants . . . . . . . . . . . . . . . . . . . . . 
27
     3.7.  Session Identifier (Session ID) . . . . . . . . . . . . . 
27
     3.8.  GRASP Messages  . . . . . . . . . . . . . . . . . . . . . 
28
       3.8.1.  Message Overview  . . . . . . . . . . . . . . . . . . 
28
       3.8.2.  GRASP Message Format  . . . . . . . . . . . . . . . . 
29
       3.8.3.  Message Size  . . . . . . . . . . . . . . . . . . . . 
29
       3.8.4.  Discovery Message . . . . . . . . . . . . . . . . . . 
30
       3.8.5.  Discovery Response Message  . . . . . . . . . . . . . 
31
       3.8.6.  Request Messages  . . . . . . . . . . . . . . . . . . 
32
       3.8.7.  Negotiation Message . . . . . . . . . . . . . . . . . 
33
       3.8.8.  Negotiation End Message . . . . . . . . . . . . . . . 
33
       3.8.9.  Confirm Waiting     Message . . . . . . . . . . . . . 
33
       3.8.10. Synchronization Message . . . . . . . . . . . . . . . 
34
       3.8.11. Flood Synchronization Message . . . . . . . . . . . . 
34
       3.8.12. Invalid Message . . . . . . . . . . . . . . . . . . . 
35
       3.8.13. No Operation Message  . . . . . . . . . . . . . . . . 
35
     3.9.  GRASP Options . . . . . . . . . . . . . . . . . . . . . . 
36
       3.9.1.  Format of GRASP Options . . . . . . . . . . . . . . . 
36
       3.9.2.  Divert Option . . . . . . . . . . . . . . . . . . . . 
36
       3.9.3.  Accept Option . . . . . . . . . . . . . . . . . . . . 
36



Bormann, et al.           Expires June 18, 2017                 [Page
2]

Internet-Draft                    GRASP                    December
2016


       3.9.4.  Decline Option  . . . . . . . . . . . . . . . . . . . 
37
       3.9.5.  Locator Options . . . . . . . . . . . . . . . . . . . 
37
     3.10. Objective Options . . . . . . . . . . . . . . . . . . . . 
39
       3.10.1.  Format of Objective Options  . . . . . . . . . . . . 
39
       3.10.2.  Objective flags  . . . . . . . . . . . . . . . . . . 
40
       3.10.3.  General Considerations for Objective Options . . . . 
41
       3.10.4.  Organizing of Objective Options  . . . . . . . . . . 
41
       3.10.5.  Experimental and Example Objective Options . . . . . 
43
   4.  Implementation Status [RFC Editor: please remove] . . . . . . 
43
     4.1.  BUPT C++ Implementation . . . . . . . . . . . . . . . . . 
43
     4.2.  Python Implementation . . . . . . . . . . . . . . . . . . 
44
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . 
45
   6.  CDDL Specification of GRASP . . . . . . . . . . . . . . . . . 
47
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . 
49
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . 
51
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . . 
51
     9.1.  Normative References  . . . . . . . . . . . . . . . . . . 
51
     9.2.  Informative References  . . . . . . . . . . . . . . . . . 
52
   Appendix A.  Open Issues [RFC Editor: Please remove if empty] . . 
55
   Appendix B.  Closed Issues [RFC Editor: Please remove]  . . . . . 
55
   Appendix C.  Change log [RFC Editor: Please remove] . . . . . . . 
63
   Appendix D.  Example Message Formats  . . . . . . . . . . . . . . 
69
     D.1.  Discovery Example . . . . . . . . . . . . . . . . . . . . 
69
     D.2.  Flood Example . . . . . . . . . . . . . . . . . . . . . . 
70
     D.3.  Synchronization Example . . . . . . . . . . . . . . . . . 
70
     D.4.  Simple Negotiation Example  . . . . . . . . . . . . . . . 
70
     D.5.  Complete Negotiation Example  . . . . . . . . . . . . . . 
71
   Appendix E.  Capability Analysis of Current Protocols . . . . . . 
72
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . 
75

1.  Introduction

   The success of the Internet has made IP-based networks bigger and
   more complicated.  Large-scale ISP and enterprise networks have
   become more and more problematic for human based management. 
Also,
   operational costs are growing quickly.  Consequently, there are
   increased requirements for autonomic behavior in the networks.
   General aspects of autonomic networks are discussed in [RFC7575]
and
   [RFC7576].

   One approach is to largely decentralize the logic of network
   management by migrating it into network elements.  A reference
model
   for autonomic networking on this basis is given in
   [I-D.ietf-anima-reference-model].  The reader should consult this
   document to understand how various autonomic components fit
together.
   In order to fulfill autonomy, devices that embody Autonomic
Service
   Agents (ASAs, [RFC7575]) have specific signaling requirements.  In
   particular they need to discover each other, to synchronize state



Bormann, et al.           Expires June 18, 2017                 [Page
3]

Internet-Draft                    GRASP                    December
2016


   with each other, and to negotiate parameters and resources
directly
   with each other.  There is no limitation on the types of
parameters
   and resources concerned, which can include very basic information
   needed for addressing and routing, as well as anything else that
   might be configured in a conventional non-autonomic network.  The
   atomic unit of discovery, synchronization or negotiation is
referred
   to as a technical objective, i.e, a configurable parameter or set
of
   parameters (defined more precisely in Section 3.1).

   Following this Introduction, Section 2 describes the requirements
for
   discovery, synchronization and negotiation.  Negotiation is an
   iterative process, requiring multiple message exchanges forming a
   closed loop between the negotiating entities.  In fact, these
   entities are ASAs, normally but not necessarily in different
network
   devices.  State synchronization, when needed, can be regarded as a
   special case of negotiation, without iteration.  Section 3.3
   describes a behavior model for a protocol intended to support
   discovery, synchronization and negotiation.  The design of GeneRic
   Autonomic Signaling Protocol (GRASP) in Section 3 of this document
is
   based on this behavior model.  The relevant capabilities of
   various existing protocols are reviewed in Appendix E.

   The proposed discovery mechanism is oriented towards
synchronization
   and negotiation objectives.  It is based on a neighbor discovery
   process, but also supports diversion to off-link peers.  There is
no
CEP: off-link needs a definition
   assumption of any particular form of network topology.  When a
device
   starts up with no pre-configuration, it has no knowledge of the
   topology.  The protocol itself is capable of being used in a small
   and/or flat network structure such as a small office or home
network
   as well as in a professionally managed network.  Therefore, the
   discovery mechanism needs to be able to allow a device to
bootstrap
   itself without making any prior assumptions about network
structure.

   Because GRASP can be used as part of a decision process among
   distributed devices or between networks, it must run in a secure
and
   strongly authenticated environment.

   In realistic deployments, not all devices will
   support GRASP.  Therefore, some autonomic service agents
   will directly manage a group of non-autonomic nodes, and other
   non-autonomic nodes will be managed traditionally.  Such mixed
   scenarios are not discussed in this specification.

2.  Requirement Analysis of Discovery, Synchronization and
Negotiation

   This section discusses the requirements for discovery, negotiation
   and synchronization capabilities.  The primary user of the
protocol
   is an autonomic service agent (ASA), so the requirements are
mainly



Bormann, et al.           Expires June 18, 2017                 [Page
4]

Internet-Draft                    GRASP                    December
2016


   expressed as the features needed by an ASA.  A single physical
device
   might contain several ASAs, and a single ASA might manage several
   technical objectives.  If a technical objective is managed by
several
   ASAs, any necessary coordination is outside the scope of the
   GRASP signaling protocol.
CEP: O.K., but a signaling protocol COULD certainly include
coordination

   Note that requirements for ASAs themselves, such as the processing
of
   Intent [RFC7575] or interfaces for coordination between ASAs are
out
   of scope for the present document.
CEP: Isn't the last clause a reiteration from the previous paragraph?

2.1.  Requirements for Discovery

   D1.  ASAs may be designed to manage anything, as required in
CEP: !?ANYTHING?!	... perhaps "for many purposes"?
   Section 2.2.  A basic requirement is therefore that the protocol
can
   represent and discover any kind of technical objective among
   arbitrary subsets of participating nodes.

   In an autonomic network we must assume that when a device starts
up
   it has no information about any peer devices, the network
structure,
   or what specific role it must play.  The ASA(s) inside the device
are
   in the same situation.  In some cases, when a new application
session
   starts up within a device, the device or ASA may again lack
   information about relevant peers.  For example, it might be
necessary
   to set up resources on multiple other devices, coordinated and
   matched to each other so that there is no wasted resource. 
Security
   settings might also need updating to allow for the new device or
   user.  The relevant peers may be different for different technical
   objectives.  Therefore discovery needs to be repeated as often as
   necessary to find peers capable of acting as counterparts for each
   objective that a discovery initiator needs to handle.  From this
   background we derive the next three requirements:

   D2.  When an ASA first starts up, it has no knowledge of the
specific
CEP: "has" --> "may have".  GRASP should not prohibit partial
preconfiguration
   network to which it is attached.  Therefore the discovery process
   must be able to support any network scenario, assuming only that
the
   device concerned is bootstrapped from factory condition.

   D3.  When an ASA starts up, it must require no configured location
   information about any peers in order to discover them.

   D4.  If an ASA supports multiple technical objectives, relevant
peers
   may be different for different discovery objectives, so discovery
   needs to be performed separately to find counterparts for each
   objective.  Thus, there must be a mechanism by which an ASA can
   separately discover peer ASAs for each of the technical objectives
   that it needs to manage, whenever necessary.





Bormann, et al.           Expires June 18, 2017                 [Page
5]

Internet-Draft                    GRASP                    December
2016


   D5.  Following discovery, an ASA will normally perform negotiation
or
   synchronization for the corresponding objectives.  The design
should
   allow for this by conveniently linking discovery to negotiation
and
   synchronization.  It may provide an optional mechanism to combine
   discovery and negotiation/synchronization in a single call.
CEP: "call" --> "protocol exchange" {unless RPC implementation is
mandatory}

   D6.  Some objectives may only be significant on the local link,
but
   others may be significant across the routed network and require
off-
   link operations.  Thus, the relevant peers might be immediate
   neighbors on the same layer 2 link, or they might be more distant
and
   only accessible via layer 3.  The mechanism must therefore provide
   both on-link and off-link discovery of ASAs supporting specific
   technical objectives.
CEP: Can GRASP *require* on-link?

   D7.  The discovery process should be flexible enough to allow for
   special cases, such as the following:

   o  During initialisation, a device must be able to establish
mutual
      trust with the rest of the network and join an authentication
CEP: "join" is the wrong word here.  Perhaps "participate in".
      mechanism.  Although this will inevitably start with a
discovery
      action, it is a special case precisely because trust is not yet
      established.  This topic is the subject of
      [I-D.ietf-anima-bootstrapping-keyinfra].  We require that once
      trust has been established for a device, all ASAs within the
      device inherit the device's credentials and are also trusted.
CEP: GRASP should not prohibit a device from having multiple
credentials!!

   o  Depending on the type of network involved, discovery of other
      centralized functions might be needed, such as the Network
Operations
      Center (NOC) [I-D.ietf-anima-stable-connectivity].  The
protocol
      must be capable of supporting such discovery during
      initialization, as well as discovery during ongoing operation.

   D8.  The discovery process must not generate excessive traffic and
   must take account of sleeping nodes.

   D9.  There must be a mechanism for handling stale discovery
results.

2.2.  Requirements for Synchronization and Negotiation Capability

   As background, consider the example of routing protocols, the
closest
   approximation to autonomic networking already in widespread use.
   Routing protocols use a largely autonomic model based on
distributed
   devices that communicate repeatedly with each other.  The focus is
   reachability, so current routing protocols mainly consider simple
   link status, i.e., up or down, and an underlying assumption is
that
   all nodes need a consistent view of the network topology in order
for
   the routing algorithm to converge.  Thus, routing is mainly based
on
CEP: not true for reactive routing protocols, unless the definition
for
	"consistent" is stretched out a good bit
   information synchronization between peers, rather than on bi-



Bormann, et al.           Expires June 18, 2017                 [Page
6]

Internet-Draft                    GRASP                    December
2016


   directional negotiation.  Other information, such as latency,
   congestion, capacity, and particularly unused capacity, would be
   helpful to get better path selection and utilization rate, but is
not
   normally used in distributed routing algorithms.
   Autonomic networks need to be able to manage many more dimensions,
   such as security settings, power saving, load balancing, etc. 
Status
   information and traffic metrics need to be shared between nodes
for
   dynamic adjustment of resources and for monitoring purposes. 
While
   this might be achieved by existing protocols when they are
available,
   the new protocol needs to be able to support parameter exchange,
   including mutual synchronization, even when no negotiation as such
is
   required.  In general, these parameters do not apply to all
   participating nodes, but only to a subset.

   SN1.  A basic requirement for the protocol is the ability
   to represent, discover, synchronize and negotiate almost any kind
of
   network parameter among selected subsets of participating nodes.

   SN2.  Negotiation is a request/response process that must be
   guaranteed to terminate (with success or failure)
CEP: Termination is ALWAYS required in reasonable protocol design -
	what is new here that characterizes "negotiation"?
                                                     and if necessary
it
   must contain tie-breaking rules for each technical objective that
   requires them.
CEP: if necessary it must contain ... <if required>: redundant
"MUST",
	but under ambiguous conditions...
	Could instead say: "MUST break any ties before termination."
                   While these must be defined specifically for each
use
   case, the protocol should have some general mechanisms in support
of
   loop and deadlock prevention, such as hop count limits or
timeouts.
CEP: SN2 would be just as good if it only contained this last
sentence.

   SN3.  Synchronization might concern small groups of nodes or very
   large groups.  Different solutions might be needed at different
   scales.
CEP: Does this mean that GRASP is multi-modal?  Or are multiple GRASPs
needed?

   SN4.  To avoid "reinventing the wheel", the protocol should be
able
   to encapsulate the data formats used by existing configuration
   protocols (such as NETCONF/YANG) in cases where that is
convenient.

   SN5.  Human intervention in complex situations is costly and
error-
   prone.  Therefore, synchronization or negotiation of parameters
   without human intervention is desirable whenever the coordination
of
   multiple devices can improve overall network performance.  It
   therefore follows that the protocol, as part of the Autonomic
   Networking Infrastructure, should be capable of running in any
device
   that would otherwise need human intervention.  The issue of
running
   in constrained nodes is discussed in
   [I-D.ietf-anima-reference-model].
CEP: I do not understand how SN5 could possibly be applied as a
criterion.

   SN6.  Human intervention in large networks is often replaced by
use
   of a top-down network management system (NMS).  It therefore
follows
   that the protocol, as part of the Autonomic Networking
   Infrastructure, should be capable of running in any device that
would




Bormann, et al.           Expires June 18, 2017                 [Page
7]

Internet-Draft                    GRASP                    December
2016


   otherwise be managed by an NMS, and that it can co-exist with an
NMS,
   and with protocols such as SNMP and NETCONF.

   SN7.  Some features are expected to be implemented by individual
   ASAs, but the protocol must be general enough to allow them:

   o  Dependencies and conflicts: In order to decide upon a
      configuration for a given device, the device may need
information
      from neighbors.  This can be established through the
negotiation
      procedure, or through synchronization if that is sufficient.
      However, a given item in a neighbor may depend on other
      information from its own neighbors, which may need another
      negotiation or synchronization procedure to obtain or decide.
      Therefore, there are potential dependencies and conflicts among
      negotiation or synchronization procedures.  Resolving
dependencies
      and conflicts is a matter for the individual ASAs involved.  To
      allow this, there need to be clear boundaries and convergence
      mechanisms for negotiations.  Also some mechanisms are needed
to
      avoid loop dependencies.  In such a case, the protocol's role
is
      limited to bilateral signaling between ASAs.
CEP: Does this mean: "If mechanisms are needed to avoid loop
dependencies,
                 then GRASP is limited to bilateral signaling between
ASAs."?
     This already excludes most routing protocols, which was the
prime
     example given to motivate GRASP.

   o  Recovery from faults and identification of faulty devices
should
      be as automatic as possible.  The protocol's role is limited to
      discovery, synchronization and negotiation.  These processes
can
      occur at any time, and an ASA may need to repeat any of these
      steps when the ASA detects an anomaly such as a negotiation
      counterpart failing.
CEP: O.K., but in IoT such things may be considered "normal", not
anomalous.

   o  Since the goal is to minimize human intervention, it is
necessary
CEP: "the goal" --> "a goal"
      that the network can in effect "think ahead" before changing
its
      parameters.  One aspect of this is an ASA that relies on a
      knowledge base to predict network behavior.  This is out of
scope
      for the signaling protocol.  However, another aspect is
      forecasting the effect of a change by a "dry run" negotiation
      before actually installing the change.  This will be an
      application of the protocol rather than a feature of the
protocol
      itself.
CEP: So, this is NOT a protocol requirement.

   o  Management logging, monitoring, alerts and tools for
intervention
      are required.  However, these can only be features of
individual
      ASAs.  Another document [I-D.ietf-anima-stable-connectivity]
      discusses how such agents may be linked into conventional OAM
      systems via an Autonomic Control Plane
      [I-D.ietf-anima-autonomic-control-plane].
CEP: So, these are NOT protocol requirements for GRASP?

   SN8.  The protocol will be able to deal with a wide variety of
   technical objectives, covering any type of network parameter.
CEP: Such broad statements invite skepticism about boiling the
ocean...
   Therefore the protocol will need a flexible and easily extensible



Bormann, et al.           Expires June 18, 2017                 [Page
8]

Internet-Draft                    GRASP                    December
2016


   format for describing objectives.
CEP: But, it was explicitly stated that Intent was out of scope!!
	--> notably, the document later also waffles on Intent

                                      At a later stage it may be
   desirable to adopt an explicit information model.  One
consideration
   is whether to adopt an existing information model or to design a
new
   one.

2.3.  Specific Technical Requirements

   T1.  It should be convenient for ASA designers to define new
   technical objectives and for programmers to express them, without
   excessive impact on run-time efficiency and footprint.  In
   particular, it should be possible for ASAs to be implemented
   independently of each other as user space programs rather than as
   kernel code.
CEP: This means: understanding of GRASP depends on choice of operating
system.
     --> is GRASP "off-limits" for implementation on kernel-only
devices?
                 The classes of device in which the protocol might
run
   is discussed in [I-D.ietf-anima-reference-model].

   T2.  The protocol should be easily extensible in case the
initially
   defined discovery, synchronization and negotiation mechanisms
prove
   to be insufficient.
CEP: This doesn't really say anything...

   T3.  To be a generic platform, the protocol payload format should
be
   independent of the transport protocol or IP version.  In
particular,
   it should be able to run over IPv6 or IPv4.  However, some
functions,
   such as multicasting on a link, might need to be IP version
   dependent.  In case of doubt, IPv6 should be preferred.
CEP: Either identify the source of doubt, or delete the last
sentence.

   T4.  The protocol must be able to access off-link counterparts via
   routable addresses, i.e., must not be restricted to link-local
   operation.

   T5.  It must also be possible for an external discovery mechanism
to
   be used, if appropriate for a given technical objective.  In other
   words, GRASP discovery must not be a prerequisite for GRASP
   negotiation or synchronization.

   T6.  The protocol must be capable of supporting multiple
simultaneous
   operations, especially when wait states occur.
CEP: To different devices, or to the same device?

   T7.  Intent: There must be provision for general Intent rules to
be
   applied by all devices in the network (e.g., security rules,
prefix
   length, resource sharing rules).  However, Intent distribution
might
   not use the signaling protocol itself, but its design should not
   exclude such use.
CEP: It's difficult to reconcile the inclusion of T7, with Intent out
of scope

   T8.  Management monitoring, alerts and intervention: Devices
should
   be able to report to a monitoring system.  Some events must be
able
   to generate operator alerts and some provision for emergency
   intervention must be possible (e.g.  to freeze synchronization or
   negotiation in a mis-behaving device).  These features might not
use



Bormann, et al.           Expires June 18, 2017                 [Page
9]

Internet-Draft                    GRASP                    December
2016


   the signaling protocol itself, but its design should not exclude
such
   use.

   T9.  The protocol needs to be fully secured against forged
messages
   and man-in-the middle attacks, and secured as much as reasonably
   possible against denial of service attacks.  It needs to be
capable
   of encryption in order to resist unwanted monitoring.  However, it
is
   not required that the protocol itself provides these security
   features; it may depend on an existing secure environment.
CEP: It seems this is NOT a requirement for GRASP.  It should be
relocated
	to the Security Considerations.

3.  GRASP Protocol Overview

3.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
and
   "OPTIONAL" in this document are to be interpreted as described in
   [RFC2119] when they appear in ALL CAPS.  When these words are not
in
   ALL CAPS (such as "should" or "Should"), they have their usual
   English meanings, and are not to be interpreted as [RFC2119] key
   words.

   This document uses terminology defined in [RFC7575].

   The following additional terms are used throughout this document:

   o  Autonomic Device: identical to Autonomic Node.

   o  Discovery: a process by which an ASA discovers peers according
to
      a specific discovery objective.  The discovery results may be
      different according to the different discovery objectives.  The
      discovered peers may later be used as negotiation counterparts
or
      as sources of synchronization data.

   o  Negotiation: a process by which two ASAs interact iteratively
to
      agree on parameter settings that best satisfy the objectives of
      both ASAs.

   o  State Synchronization: a process by which ASAs interact to
receive
      the current state of parameter values stored in other ASAs. 
This
      is a special case of negotiation in which information is sent
but
      the ASAs do not request their peers to change parameter
settings.
      All other definitions apply to both negotiation and
      synchronization.

   o  Technical Objective (usually abbreviated as Objective): A
      technical objective is a configurable parameter or set of
      parameters of some kind, which occurs in three contexts:



Bormann, et al.           Expires June 18, 2017                [Page
10]

Internet-Draft                    GRASP                    December
2016


      Discovery, Negotiation and Synchronization.  In the protocol,
an
      objective is represented by an identifier and, if relevant, a
      value.  Normally, a given objective will not occur in
negotiation
      and synchronization contexts simultaneously.

      *  One ASA may support multiple independent objectives.

      *  The parameter described by a given objective is naturally
based
         on a specific service or function or action.  It may in
         principle be anything that can be set to a specific logical,
         numerical or string value, or a more complex data structure,
by
         a network node.  That node is generally expected to contain
an
         ASA which may itself manage subsidiary non-autonomic nodes.
CEP: This does not seem to say anything.

      *  Discovery Objective: an objective in the process of
discovery.
         Its value may be undefined.

      *  Synchronization Objective: an objective whose specific
         technical content needs to be synchronized among two or more
         ASAs.
CEP: Is this one objective with distributed residence, or two
objectives?

      *  Negotiation Objective: an objective whose specific technical
         content needs to be decided in coordination with another
ASA.

      A detailed discussion of objectives, including their format, is
      found in Section 3.10.

   o  Discovery Initiator: an ASA that spontaneously starts discovery
by
      sending a discovery message referring to a specific discovery
      objective.
CEP: spontaneous is the wrong word for this.  "starts" is good
enough!

   o  Discovery Responder: a peer that either contains an ASA
supporting
      the discovery objective indicated by the discovery initiator,
or
      caches the locator(s) of the ASA(s) supporting the objective. 
It
      sends a Discovery Response, as described later.

   o  Synchronization Initiator: an ASA that spontaneously starts
      synchronization by sending a request message referring to a
      specific synchronization objective.
CEP: spontaneous is the wrong word for this.  "starts" is good
enough!

   o  Synchronization Responder: a peer ASA which responds with the
      value of a synchronization objective.

   o  Negotiation Initiator: an ASA that spontaneously starts
      negotiation by sending a request message referring to a
specific
      negotiation objective.
CEP: spontaneous is the wrong word for this.  "starts" is good
enough!





Bormann, et al.           Expires June 18, 2017                [Page
11]

Internet-Draft                    GRASP                    December
2016


   o  Negotiation Counterpart: a peer with which the Negotiation
      Initiator negotiates a specific negotiation objective.

3.2.  High Level Deployment Model

   It is expected that a GRASP implementation will reside in an
   autonomic node that also contains both the appropriate security
   environment, preferably the Autonomic Control Plane (ACP)
   [I-D.ietf-anima-autonomic-control-plane],
CEP: why is this one preferable? -- perhaps another would be better!!
					     and one or more Autonomic
   Service Agents (ASAs).  In the minimal case of a single-purpose
   device, these three components might be fully integrated.  A more
   common model is expected to be a multi-purpose device capable of
   containing several ASAs.  In this case it is expected that the
ACP,
   GRASP and the ASAs will be implemented as separate processes,
which
   are probably multi-threaded to support asynchronous and
simultaneous
   operations.  It is expected that GRASP will access the ACP by using
a
   typical socket interface.
CEP: The last sentence doesn't really belong here.
                              A well defined Application Programming
   Interface (API) will be needed between GRASP and the ASAs.  In
some
   implementations, ASAs would run in user space with a GRASP library
   providing the API, and this library would in turn communicate via
   system calls with core GRASP functions.  For further details of
   possible deployment models, see [I-D.ietf-anima-reference-model].

   A GRASP instance must be aware of its network interfaces, and of
its
   own global-scope and link-local addresses.
CEP: This should be considered in light of the "user-space"
requirement...
CEP: It should be allowed for GRASP to be aware of only a strict
subset.
                                                In the presence of
the
   ACP, such information will be available from the adjacency table
   discussed in [I-D.ietf-anima-reference-model].  In other cases,
GRASP
   must determine such information for itself.  Details depend on the
   operating system.

   Because GRASP needs to work whatever happens, especially during
CEP: This is another example of overly broad specification.  For
instance,
	GRASP would be very unlikely to work if the CPU has certain bugs.
   bootstrapping and during fault conditions, it is essential that
every
   implementation is as robust as possible.  For example, discovery
   failures, or any kind of socket error at any time, must not cause
CEP: What if the socket error changes every third instance of a 0x12
byte
	to instead be 0x14?
   irrecoverable failures in GRASP itself, and must return suitable
   error codes through the API so that ASAs can also recover.

   GRASP must always start up correctly after a system restart.  All
run
   time error conditions, and events such as address renumbering,
   network interface failures, and CPU sleep/wake cycles, must be
   handled in such a way that GRASP will still operate correctly and
   securely (Section 3.5.1) afterwards.
CEP: Why not just specify that GRASP must not depend upon nonvolatile
data?
CEP: Or, better, just delete the first sentence...

   An autonomic node will normally run a single instance of GRASP,
used
   by multiple ASAs.  However, scenarios where multiple instances of
   GRASP run in a single node, perhaps with different security
   properties, are not excluded.
CEP: So, the first sentence becomes superfluous and misleading.
                                  In this case, each instance MUST




Bormann, et al.           Expires June 18, 2017                [Page
12]

Internet-Draft                    GRASP                    December
2016


   listen independently for GRASP link-local multicasts in order for
   discovery and flooding to work correctly.
CEP: Better: should specify that each instance is activated by
reception
	of a single link-local multicast.
     Even better: specify that each instance should have its own IP
address,
	and all addresses belong to the same link-local multicast group.

3.3.  High Level Design Choices

   This section describes a behavior model and design choices for
GRASP,
   supporting discovery, synchronization and negotiation, to act as a
   platform for different technical objectives.

   o  A generic platform

      The protocol is designed as a generic platform, which is
      independent from the synchronization or negotiation contents. 
It
      takes care of the general intercommunication between
counterparts.
      The technical contents will vary according to the various
      technical objectives and the different pairs of counterparts.
CEP: Not clear about how a "protocol" can be a "platform".  Is DHCP a
	"platform"?  Better: describe as a "base protocol" with extensions.
	Even better: describe as three cooperative base protocols.


   o  The protocol is expected to form part of an Autonomic
Networking
      Infrastructure [I-D.ietf-anima-reference-model].  It will
provide
      services to ASAs via a suitable application programming
interface
      (API), which will reflect the protocol elements but will not
      necessarily be in one-to-one correspondence to them.  This API
is
      out of scope for the present document.
CEP: Not clear about why this belongs here.  It adds nothing
specific.


   o  It is normally expected that a single main instance of GRASP
will
      exist in an autonomic node, and that the protocol engine and
each
      ASA will run as independent asynchronous processes.  However,
      separate GRASP instances may exist for security-related reasons
      (Section 3.5.2).
CEP: Why does the number of instances of GRASP matter for this
document?? 


   o  Security infrastructure and trust relationship

      Because this negotiation protocol may directly cause changes to
      device configurations and bring significant impacts to a
running
      network, this protocol is required to run within an existing
      secure environment with strong authentication.  As a design
      choice, the protocol itself is not provided with built-in
security
      functionality.
CEP: Therefore, this text belongs in Security Considerations

      On the other hand, a limited negotiation model might be
deployed
      based on a limited trust relationship such as that between two
      administrative domains.  ASAs might then exchange limited
      information and negotiate some particular configurations.





Bormann, et al.           Expires June 18, 2017                [Page
13]

Internet-Draft                    GRASP                    December
2016


   o  Discovery, synchronization and negotiation are designed
together.

      The discovery method and the synchronization and negotiation
      methods are designed in the same way and can be combined when
this
      is useful, allowing a rapid mode of operation described in
      Section 3.5.4.  These processes can also be performed
      independently when appropriate.

      *  Thus, for some objectives, especially those concerned with
         application layer services, another discovery mechanism such
as
         the future DNS Service Discovery [RFC7558] MAY be used.  The
         choice is left to the designers of individual ASAs.


   o  A uniform pattern for technical objectives

      The synchronization and negotiation objectives are defined
      according to a uniform pattern.  The values that they contain
      could be carried either in a simple binary format or in a
complex
      object format.  The basic protocol design uses the Concise
Binary
      Object Representation (CBOR) [RFC7049], which is readily
      extensible for unknown future requirements.


   o  A flexible model for synchronization

      GRASP supports bilateral synchronization,
CEP: undefined term...
                                                 which could be used
to
      perform synchronization among a small number of nodes.  It also
      supports an unsolicited flooding mode when large groups of
nodes,
      possibly including all autonomic nodes, need data for the same
      technical objective.

      *  There may be some network parameters for which a more
         traditional flooding mechanism such as DNCP [RFC7787] is
         considered more appropriate.  GRASP can coexist with DNCP.


   o  A simple initiator/responder model for negotiation

      Multi-party negotiations are very complicated to model and
cannot
      readily be guaranteed to converge.  GRASP uses a simple
bilateral
      model and can support multi-party negotiations by indirect
steps.


   o  Organizing of synchronization or negotiation content

      The technical content transmitted by GRASP will be organized
      according to the relevant function or service.  The objectives
for



Bormann, et al.           Expires June 18, 2017                [Page
14]

Internet-Draft                    GRASP                    December
2016


      different functions or services are kept separate, because they
      may be negotiated or synchronized with different counterparts
or
      have different response times.  Thus a normal arrangement would
be
      a single ASA managing a small set of closely related
objectives,
      with a version of that ASA in each relevant autonomic node.
      Further discussion of this aspect is out of scope for the
current
      document.


   o  Requests and responses in negotiation procedures

      The initiator can negotiate a specific negotiation objective
with
      relevant counterpart ASAs.  It can request relevant information
      from a counterpart so that it can coordinate its local
      configuration.  It can request the counterpart to make a
matching
      configuration.  It can request simulation or forecast results
by
      sending some dry run conditions.

      Beyond the traditional yes/no answer, the responder can reply
with
      a suggested alternative value for the objective concerned. 
This
      would start a bi-directional negotiation ending in a compromise
      between the two ASAs.


   o  Convergence of negotiation procedures

      To enable convergence, when a responder suggests a new value or
      condition in a negotiation step reply, it should be as close as
      possible to the original request or previous suggestion.  The
      suggested value of later negotiation steps should be chosen
      between the suggested values from the previous two steps. 
GRASP
      provides mechanisms to guarantee convergence (or failure) in a
      small number of steps, i.e. a timeout and a maximum number of
      iterations.
CEP: Not clear why any such multi-step iterative negotiation would
exist.


   o  Extensibility

      GRASP does not have a version number.  In most cases new
semantics
      will be added by defining new synchronization or negotiation
      objectives.  However, the protocol could be extended by adding
new
      message types and options in future.
CEP: Lack of version number does not guarantee extensibility, and
seems
	far too detailed to matter at this level of description.







Bormann, et al.           Expires June 18, 2017                [Page
15]

Internet-Draft                    GRASP                    December
2016


3.4.  Quick Operating Overview

   GRASP is expected to run as an operating system core module,
   providing an API (such as [I-D.liu-anima-grasp-api]) to interface
to
   less privileged ASAs.
CEP: somehow doesn't sound like "user-space"...
                          Thus ASAs may operate without special
   privilege, unless they need it for other reasons (such as
configuring
   IP addresses or manipulating routing tables).

   The GRASP mechanisms used by the ASA are built around GRASP
   objectives defined as data structures containing administrative
   information such as the objective's unique name, and its current
   value.  The format and size of the value is not restricted by the
   protocol, except that it must be possible to serialise it for
   transmission in CBOR, which is no restriction at all in practice.

   The GRASP provides the following mechanisms:

   o  A discovery mechanism (M_DISCOVERY, M_RESPONSE), by which an
ASA
      can discover other ASAs supporting a given objective.

   o  A negotiation request mechanism (M_REQ_NEG), by which an ASA
can
      start negotiation of an objective with a counterpart ASA.  Once
a
      negotiation has started, the process is symmetrical, and there
is
      a negotiation step message (M_NEGOTIATE) for each ASA to use in
      turn.  Two other functions support negotiating steps (M_WAIT,
      M_END).

   o  A synchronization mechanism (M_REQ_SYN), by which an ASA can
      request the current value of an objective from a counterpart
ASA.
      With this, there is a corresponding response function (M_SYNCH)
      for an ASA that wishes to respond to synchronization requests.

   o  A flood mechanism (M_FLOOD), by which an ASA can cause the
current
      value of an objective to be flooded throughout the AN so that
any
CEP: Undefined term AN
      ASA can receive it.  One application of this is
      announcement, avoiding the need for discovery of a widely
      applicable objective.

   Some example messages and simple message flows are provided in
   Appendix D.

3.5.  GRASP Protocol Basic Properties and Mechanisms

3.5.1.  Required External Security Mechanism

   The protocol SHOULD always run within a secure Autonomic Control
   Plane (ACP) [I-D.ietf-anima-autonomic-control-plane].  The ACP is
   assumed to carry all messages securely, including link-local



Bormann, et al.           Expires June 18, 2017                [Page
16]

Internet-Draft                    GRASP                    December
2016


   multicast if possible.
CEP: The clauses of the preceding sentence seem contradictory.
                           A GRASP implementation MUST verify whether
   the ACP is operational.

   If there is no ACP, the protocol MUST use another form of strong
   authentication and SHOULD use a form of strong encryption.  See
   Section 3.5.2.1 for further discussion.

   The ACP, or in its absence another security mechanism, sets the
   boundary within which nodes are trusted as GRASP peers.  A GRASP
   implementation MUST refuse to execute GRASP synchronization and
   negotiation functions if there is neither an operational ACP nor
   another secure environment.

   Link-local multicast is used for discovery messages.  Responses to
   discovery messages MUST be secured, with one exception mentioned
in
   the next section.

3.5.2.  Constrained Instances

   This section describes some examples of cases where additional
   instances of GRASP subject to certain constraints are appropriate.

3.5.2.1.  No ACP

   As mentioned in Section 3.3, some GRASP operations might be
performed
   across an administrative domain boundary by mutual agreement,
without
   the benefit of an ACP.  Such operations MUST be confined to a
   separate instance of GRASP
CEP: "GRASP instance" is undefined.  How many nodes can run an
"instance"??
                              with its own copy of all GRASP data
   structures.  Messages MUST be authenticated and SHOULD be
encrypted.
   TLS [RFC5246] and DTLS [RFC6347] based on a Public Key
Infrastructure
   (PKI) [RFC5280] are RECOMMENDED for this purpose.  Further details
   are out of scope for this document.

3.5.2.2.  Discovery Unsolicited Link-Local

   Some services may need to use insecure GRASP discovery, response
and
   flood messages without being able to use pre-existing security
   associations.  Such operations being intrinsically insecure, they
   need to be confined to link-local use to minimise the risk of
   malicious actions.
CEP: This contradicts the unequivocal previous language prohibiting
it.
                       Possible examples include discovery of
candidate
   ACP neighbors [I-D.ietf-anima-autonomic-control-plane], discovery
of
   bootstrap proxies [I-D.ietf-anima-bootstrapping-keyinfra] or
perhaps
   initialisation services in networks using GRASP without being
fully
   autonomic (e.g., no ACP).  Such usage MUST be limited to
link-local
   operations and MUST be confined to a separate insecure instance of
   GRASP with its own copy of all GRASP data structures.  This
instance
   is nicknamed DULL - Discovery Unsolicited Link-Local.
CEP: :-)




Bormann, et al.           Expires June 18, 2017                [Page
17]

Internet-Draft                    GRASP                    December
2016


   The detailed rules for the DULL instance of GRASP are as follows:

   o  An initiator MUST only send Discovery or Flood Synchronization
      link-local multicast messages with a loop count of 1.  A
responder
      SHOULD NOT send a Discovery Response message unless it cannot
be
      avoided.  Other GRASP message types MUST NOT be sent.

   o  A responder MUST silently discard any message whose loop count
is
      not 1.

   o  A responder MUST silently discard any message referring to a
GRASP
      Objective that is not directly part of a service that requires
      this insecure mode.

   o  A responder MUST NOT relay any multicast messages.

   o  A Discovery Response MUST indicate a link-local address.

   o  A Discovery Response MUST NOT include a Divert option.

   o  A node MUST silently discard any message whose source address
is
      not link-local.

   GRASP traffic SHOULD be minimized by using only Flood
Synchronization
   to announce objectives and their associated locators, rather than
by
   using Discovery and Response.  Further details are out of scope
for
   this document.
CEP: Not clear why this paragraph is DULL.

3.5.2.3.  Secure Only Neighbor Negotiation

   Some services might use insecure on-link operations as in DULL,
but
   also use unicast synchronization or negotiation operations
protected
   by TLS.  A separate instance of GRASP is used, with its own copy
of
   all GRASP data structures.  This instance is nicknamed SONN -
Secure
   Only Neighbor Negotiation.

   The detailed rules for the SONN instance of GRASP are as follows:

   o  Any type of GRASP message MAY be sent.

   o  An initiator MUST send any Discovery or Flood Synchronization
      link-local multicast messages with a loop count of 1.

   o  A responder MUST silently discard any Discovery or Flood
      Synchronization message whose loop count is not 1.

   o  A responder MUST silently discard any message referring to a
GRASP
      Objective that is not directly part of the service concerned.



Bormann, et al.           Expires June 18, 2017                [Page
18]

Internet-Draft                    GRASP                    December
2016


   o  A responder MUST NOT relay any multicast messages.

   o  A Discovery Response MUST indicate a link-local address.

   o  A Discovery Response MUST NOT include a Divert option.

   o  A node MUST silently discard any message whose source address
is
      not link-local.

   Further details, including TLS and PKI usage, are out of scope for
   this document.
CEP: In that case, this section seems redundant to the last section.

3.5.3.  Transport Layer Usage

   GRASP discovery and flooding messages are designed for use over
link-
   local multicast UDP.  They MUST NOT be fragmented, and therefore
MUST
   NOT exceed the link MTU size.
CEP: What about 802.15.4 with IPv6 addresses and objective
parameters?
                                  Nothing in principle prevents them
   from working over some other method of sending packets to all
on-link
   neighbors, but this is out of scope for the present specification.
CEP: That is a lot different than "MUST NOT".

   All other GRASP messages are unicast and could in principle run
over
   any transport protocol.  An implementation MUST support use of
TCP.
   It MAY support use of another transport protocol.  However, GRASP
   itself does not provide for error detection or retransmission. 
Use
   of an unreliable transport protocol is therefore NOT RECOMMENDED.

   Nevertheless, when running within a secure ACP on reliable
   infrastructure, UDP MAY be used for unicast messages not exceeding
   the minimum IPv6 path MTU; however, TCP MUST be used for longer
   messages.  In other words, IPv6 fragmentation is avoided.  If a
node
   receives a UDP message but the reply is too long, it MUST open a
TCP
   connection to the peer for the reply.  Note that when the network
is
   under heavy load or in a fault condition, UDP might become
   unreliable.  Since this is when autonomic functions are most
   necessary, automatic fallback to TCP MUST be implemented.  The
   simplest implementation is therefore to use only TCP.

   For considerations when running without an ACP, see Section
3.5.2.1.

   For link-local multicast, the GRASP protocol listens to the well-
   known GRASP Listen Port (Section 3.6).  For unicast transport
   sessions used for discovery responses, synchronization and
   negotiation, the ASA concerned normally listens on its own
   dynamically assigned ports, which are communicated to its peers
   during discovery.  However, a minimal implementation MAY use the
   GRASP Listen Port for this purpose.





Bormann, et al.           Expires June 18, 2017                [Page
19]

Internet-Draft                    GRASP                    December
2016


3.5.4.  Discovery Mechanism and Procedures

3.5.4.1.  Separated discovery and negotiation mechanisms

   Although discovery and negotiation or synchronization are defined
   together in GRASP, they are separate mechanisms.  The discovery
   process could run independently from the negotiation or
   synchronization process.  Upon receiving a Discovery (Section
3.8.4)
   message, the recipient node should return a response message in
which
   it either indicates itself as a discovery responder or diverts the
   initiator towards another more suitable ASA.

   The discovery action (M_DISCOVERY) will normally be followed by a
   negotiation (M_REQ_NEG) or synchronization (M_REQ_SYN) action. 
The
   discovery results could be utilized by the negotiation protocol to
   decide which ASA the initiator will negotiate with.

   The initiator of a discovery action for a given objective need not
be
   capable of responding to that objective as a Negotiation
Counterpart,
   as a Synchronization Responder or as source for flooding.  For
   example, an ASA might perform discovery even if it only wishes to
act
   a Synchronization Initiator or Negotiation Initiator.  Such an ASA
   does not itself need to respond to discovery messages.

   It is also entirely possible to use GRASP discovery without any
   subsequent negotiation or synchronization action.  In this case,
the
   discovered objective is simply used as a name during the discovery
   process and any subsequent operations between the peers are
outside
   the scope of GRASP.

3.5.4.2.  Discovery Overview

   A complete discovery process will start with a multicast (of
   M_DISCOVERY) on the local link.  On-link neighbors supporting the
   discovery objective will respond directly (with M_RESPONSE).  A
   neighbor with multiple interfaces will respond with a cached
   discovery response if any.  However, it SHOULD NOT respond with a
   cached response on an interface if it learnt that information from
   the same interface.
CEP: Should explain the reasoning for this restriction.
                       If it has no cached response, it will relay
the
   discovery on its other interfaces, for example reaching a higher-
   level gateway in a hierarchical network.
CEP: Does this imply that the relaying node is itself a gateway?
CEP: It should be allowed for some or all other interfaces to be
silent.
                                            If a node receiving the
   relayed discovery supports the discovery objective, it will
respond
   to the relayed discovery.  If it has a cached response, it will
   respond with that.  If not, it will repeat the discovery process,
   which thereby becomes recursive.
CEP: "recursive" --> "iterative", or perhaps better "multi-hop"
                                     The loop count and timeout will
   ensure that the process ends.





Bormann, et al.           Expires June 18, 2017                [Page
20]

Internet-Draft                    GRASP                    December
2016


   A Discovery message MAY be sent unicast (via UDP or
   TCP) to a peer node, which will then proceed exactly as if the
   message had been multicast, except that when TCP is used, the
   response will be on the same socket as the query.
CEP: How does a node decide between unicast and multicast?
                                                      However, this
mode
   does not guarantee successful discovery in the general case.
CEP: Nothing guarantees success!  However, unicast may fail more
often
	than multicast in lightly-loaded networks.  On the other hand,
	wireless multicast presents its own long list of protocol issues.

3.5.4.3.  Discovery Procedures

   Discovery starts as an on-link operation.  The Divert option can
tell
   the discovery initiator to contact an off-link ASA for that
discovery
   objective.  Every Discovery message is sent by a discovery
initiator
   via UDP to the ALL_GRASP_NEIGHBOR link-local multicast address
   (Section 3.6).
CEP: This contradicts the previous section "MAY be sent unicast"
                   Every network device that supports GRASP always
   listens to a well-known UDP port to capture the discovery
messages.
   Because this port is unique in a device, this is a function of the
   GRASP core and not of an individual ASA.  As a result, each ASA
will
CEP: "core" --> base protocol
   need to register the objectives that it supports with the GRASP
core.
CEP: is this a protocol operation or a configuration requirement?
CEP: probably the latter, but it needs to be made clear that this
	pertains to ASAs on a single device.

   If an ASA in a neighbor device supports the requested discovery
   objective, the device SHOULD respond to the link-local multicast
with
   a unicast Discovery Response message (Section 3.8.5) with locator
   option(s), unless it is temporarily unavailable.  Otherwise, if
the
   neighbor has cached information about an ASA that supports the
   requested discovery objective (usually because it discovered the
same
   objective before), it SHOULD respond with a Discovery Response
   message with a Divert option pointing to the appropriate Discovery
   Responder.

   If a device has no information about the requested discovery
   objective, and is not acting as a discovery relay (see below) it
MUST
   silently discard the Discovery message.

   If no discovery response is received within a reasonable timeout
   (default GRASP_DEF_TIMEOUT milliseconds, Section 3.6), the
Discovery
   message MAY be repeated, with a newly generated Session ID
   (Section 3.7).  An exponential backoff SHOULD be used for
subsequent
   repetitions, to limit the load during busy periods.  Frequent
   repetition might be symptomatic of a denial of service attack.
CEP: Previous IESG guidance has required MUST for exponential
backoff.
	(and exponent MUST be 2).  (I don't necessarily agree with this)

   After a GRASP device successfully discovers a locator for a
Discovery
   Responder supporting a specific objective, it MUST cache this
   information, including the identifier of the interface by which it
was
   discovered.  This cached information MAY be used for future
negotiation or
   synchronization, and the locator SHOULD be passed on when
appropriate
   as a Divert option to another Discovery Initiator.

   The cache mechanism MUST include a lifetime for each entry.  The
   lifetime is derived from a time-to-live (ttl) parameter in each



Bormann, et al.           Expires June 18, 2017                [Page
21]

Internet-Draft                    GRASP                    December
2016


   Discovery Response message.  Cached entries MUST be ignored or
   deleted after their lifetime expires.  In some environments,
   unplanned address renumbering might occur.  In such cases, the
   lifetime SHOULD be short compared to the typical address lifetime
and
   a mechanism to flush the discovery cache SHOULD be implemented. 
The
CEP: SHOULD --> MUST flush!, especially given "divert" feature
   discovery mechanism needs to track the node's current address to
   ensure that Discovery Responses always indicate the correct
address.

   If multiple Discovery Responders are found for the same objective,
   they SHOULD all be cached, unless this creates a resource
shortage.
   The method of choosing between multiple responders is an
   implementation choice.  This choice MUST be available to each ASA
but
   the GRASP implementation SHOULD provide a default choice.

   Because Discovery Responders will be cached in a finite cache,
they
   might be deleted at any time.  In this case, discovery will need
to
   be repeated.  If an ASA exits for any reason, its locator might
still
   be cached for some time, and attempts to connect to it will fail.
   ASAs need to be robust in these circumstances.

3.5.4.4.  Discovery Relaying

   A GRASP instance with multiple link-layer interfaces (typically
   running in a router) MUST support discovery on all interfaces.  We
   refer to this as a 'relaying instance'.
CEP: This seems to be a mistake.  Why shouldn't a device be allowed
to
	have non-participating interfaces?

   However, different interfaces can be at different security levels:
   each group of interfaces with the same security level SHOULD be
   serviced by the same GRASP process, except for Limited Security
   Instances Section 3.5.2 which are always single-interface
instances
   and MUST NOT perform discovery relaying.
CEP: This seems already to contradict the last paragraph.

   If a relaying instance receives a Discovery message on a given
   interface for a specific objective that it does not support and
for
   which it has not previously cached a Discovery Responder, it MUST
   relay the query by re-issuing a Discovery message as a link-local
   multicast on its other interfaces.

   The relayed discovery message MUST have the same Session ID as the
   incoming discovery message and MUST be tagged with the IP address
of
   its original initiator (see Section 3.8.4).  Note that this
initiator
   address is only used to allow for disambiguation of the Session ID
   and is never used to address Response packets.
CEP: But, section 3.8.5.  Discovery Response Message has:
>   It is sent to the sender of the Discovery message via TCP at the
port
>   used to send the Discovery message (as explained in Section
3.8.4).
	Wouldn't this allow the Response to be sent to the initiator?

   Since the relay device is unaware of the timeout set by the
original
   initiator it SHOULD set a timeout at least equal to
GRASP_DEF_TIMEOUT
   milliseconds.




Bormann, et al.           Expires June 18, 2017                [Page
22]

Internet-Draft                    GRASP                    December
2016


   The relaying instance MUST decrement the loop count within the
   objective, and MUST NOT relay the Discovery message if the result
is
   zero.  Also, it MUST limit the total rate at which it relays
   discovery messages to a reasonable value, in order to mitigate
   possible denial of service attacks.  It MUST cache the Session ID
   value and initiator address of each relayed Discovery message
until
   any Discovery Responses have arrived or the discovery process has
   timed out.  To prevent loops, it MUST NOT relay a Discovery
message
   which carries a given cached Session ID and initiator address more
   than once.  These precautions avoid discovery loops and mitigate
   potential overload.

   The discovery results received by the relaying instance MUST in
turn
   be sent as a Discovery Response message to the Discovery message
that
   caused the relay action.
CEP: This seems to contradict the language above:
                                                           "initiator
   address is only used to allow for disambiguation of the Session ID
   and is never used to address Response packets."

   This relayed discovery mechanism, with caching of the results,
should
   be sufficient to support most network bootstrapping scenarios.
CEP: Not clear why this sentence is included...

3.5.4.5.  Rapid Mode (Discovery/Negotiation binding)

   A Discovery message MAY include a Negotiation Objective option. 
This
   allows a rapid mode of negotiation described in Section 3.5.5.  A
   similar mechanism is defined for synchronization in Section 3.5.6.

   Note that rapid mode is currently limited to a single objective
for
   simplicity of design and implementation.  A possible future
extension
   is to allow multiple objectives in rapid mode for greater
efficiency.
CEP: O.K. but the extension seems quite straightforward.

3.5.5.  Negotiation Procedures

   A negotiation initiator sends a negotiation request to a
counterpart
   ASA, including a specific negotiation objective.  It may request
the
   negotiation counterpart to make a specific configuration.
   Alternatively, it may request a certain simulation or forecast
result
   by sending a dry run configuration.  The details, including the
   distinction between dry run and an actual configuration change,
will
   be defined separately for each type of negotiation objective.

   If no reply message of any kind is received within a reasonable
   timeout (default GRASP_DEF_TIMEOUT milliseconds, Section 3.6), the
   negotiation request MAY be repeated, with a newly generated
Session
   ID (Section 3.7).  An exponential backoff SHOULD be used for
   subsequent repetitions.

   If the counterpart can immediately apply the requested
configuration,
   it will give an immediate positive (O_ACCEPT) answer (using
M_END).
   This will end the negotiation phase immediately.  Otherwise, it
will



Bormann, et al.           Expires June 18, 2017                [Page
23]

Internet-Draft                    GRASP                    December
2016


   negotiate (using M_NEGOTIATE).  It will reply with a proposed
   alternative configuration that it can apply (typically, a
   configuration that uses fewer resources than requested by the
   negotiation initiator).  This will start a bi-directional
negotiation
   (using M_NEGOTIATE) to reach a compromise between the two ASAs.

   The negotiation procedure is ended when one of the negotiation
peers
   sends a Negotiation Ending (M_END) message, which contains an
accept
   (O_ACCEPT) or decline (O_DECLINE) option and does not need a
response
   from the negotiation peer.  Negotiation may also end in failure
   (equivalent to a decline) if a timeout is exceeded or a loop count
is
   exceeded.

   A negotiation procedure concerns one objective and one
counterpart.
   Both the initiator and the counterpart may take part in
simultaneous
   negotiations with various other ASAs, or in simultaneous
negotiations
   about different objectives.  Thus, GRASP is expected to be used in
a
   multi-threaded mode.  Certain negotiation objectives may have
   restrictions on multi-threading, for example to avoid
over-allocating
   resources.

   Some configuration actions, for example wavelength switching in
   optical networks, might take considerable time to execute.  The
ASA
   concerned needs to allow for this by design, but GRASP does allow
for
   a peer to insert latency in a negotiation process if necessary
   (Section 3.8.9, M_WAIT).

3.5.5.1.  Rapid Mode (Discovery/Negotiation Linkage)

   A Discovery message MAY include a Negotiation Objective option. 
In
   this case it is as if the initiator sent the sequence M_DISCOVERY,
   immediately followed by M_REQ_NEG.  This has implications for the
   construction of the GRASP core, as it must carefully pass the
   contents of the Negotiation Objective option to the ASA so that it
   may evaluate the objective directly.  When a Negotiation Objective
   option is present the ASA replies with an M_NEGOTIATE message (or
   M_END with O_ACCEPT if it is immediately satisfied with the
   proposal), rather than with an M_RESPONSE.  However, if the
recipient
   node does not support rapid mode, discovery will continue
normally.

   It is possible that a Discovery Response will arrive from a
responder
   that does not support rapid mode, before such a Negotiation
message
   arrives.  In this case, rapid mode will not occur.

   This rapid mode could reduce the interactions between nodes so that
a
   higher efficiency could be achieved.  However, a network in which
   some nodes support rapid mode and others do not will have complex
   timing-dependent behaviors.  Therefore, the rapid negotiation



Bormann, et al.           Expires June 18, 2017                [Page
24]

Internet-Draft                    GRASP                    December
2016


   function SHOULD be configured off by default and MAY be configured
on
   or off by Intent.
CEP: citation needed.

3.5.6.  Synchronization and Flooding Procedure

   A synchronization initiator sends a synchronization request to a
   counterpart, including a specific synchronization objective.  The
   counterpart responds with a Synchronization message (Section
3.8.10)
   containing the current value of the requested synchronization
   objective.  No further messages are needed.
CEP: Specify here that it is unicast.  Section title should reflect
that
	it is for a single objective.

   If no reply message of any kind is received within a reasonable
   timeout (default GRASP_DEF_TIMEOUT milliseconds, Section 3.6), the
   synchronization request MAY be repeated, with a newly generated
   Session ID (Section 3.7).  An exponential backoff SHOULD be used
for
   subsequent repetitions.
CEP: SHOULD --> MUST

3.5.6.1.  Flooding

   In the case just described, the message exchange is unicast and
   concerns only one synchronization objective.  For large groups of
   nodes requiring the same data, synchronization flooding is
available.
   For this, a flooding initiator MAY send an unsolicited Flood
   Synchronization message containing one or more Synchronization
   Objective option(s), if and only if the specification of those
   objectives permits it.  This is sent as a multicast message to the
   ALL_GRASP_NEIGHBOR multicast address (Section 3.6).

   Every network device that supports GRASP always listens to a well-
   known UDP port to capture flooding messages.  Because this port is
   unique in a device, this is a function of the GRASP core.
CEP: already said this.

   To ensure that flooding does not result in a loop, the originator
of
   the Flood Synchronization message MUST set the loop count in the
   objectives to a suitable value (the default is GRASP_DEF_LOOPCT).
   Also, a suitable mechanism is needed to avoid excessive multicast
   traffic.  This mechanism MUST be defined as part of the
specification
   of the synchronization objective(s) concerned.  It might be a
simple
   rate limit or a more complex mechanism such as the Trickle
algorithm
   [RFC6206].

   A GRASP device with multiple link-layer interfaces (typically a
   router) MUST support synchronization flooding on all interfaces. 
If
   it receives a multicast Flood Synchronization message on a given
   interface, it MUST relay it by re-issuing a Flood Synchronization
   message on its other interfaces.  The relayed message MUST have
the
   same Session ID as the incoming message and MUST be tagged with
the
   IP address of its original initiator.
CEP: I am pretty sure this is a mistake.



Bormann, et al.           Expires June 18, 2017                [Page
25]

Internet-Draft                    GRASP                    December
2016


   Link-layer Flooding is supported by GRASP by setting the loop
count
   to 1, and sending with a link-local source address.  Floods with
   link-local source addresses and a loop count other than 1 are
   invalid, and such messages MUST be discarded.

   The relaying device MUST decrement the loop count within the first
   objective, and MUST NOT relay the Flood Synchronization message if
   the result is zero.  Also, it MUST limit the total rate at which
it
   relays Flood Synchronization messages to a reasonable value, in
order
   to mitigate possible denial of service attacks.  It MUST cache the
   Session ID value and initiator address of each relayed Flood
   Synchronization message for a time not less than twice
   GRASP_DEF_TIMEOUT milliseconds.  To prevent loops, it MUST NOT
relay
   a Flood Synchronization message which carries a given cached
Session
   ID and initiator address more than once.  These precautions avoid
   synchronization loops and mitigate potential overload.

   Note that this mechanism is unreliable in the case of sleeping
nodes,
   or new nodes that join the network, or nodes that rejoin the
network
   after a fault.  An ASA that initiates a flood SHOULD repeat the
flood
   at a suitable frequency and SHOULD also act as a synchronization
   responder for the objective(s) concerned.  Thus nodes that require
an
   objective subject to flooding can either wait for the next flood
or
   request unicast synchronization for that objective.

   The multicast messages for synchronization flooding are subject to
   the security rules in Section 3.5.1.  In practice this means that
   they MUST NOT be transmitted and MUST be ignored on receipt unless
   there is an operational ACP or equivalent strong security in
place.
   However, because of the security weakness of link-local multicast
   (Section 5), synchronization objectives that are flooded SHOULD
NOT
   contain unencrypted private information and SHOULD be validated by
   the recipient ASA.

3.5.6.2.  Rapid Mode (Discovery/Synchronization Linkage)

   A Discovery message MAY include a Synchronization Objective
option.
   In this case the Discovery message also acts as a Request
   Synchronization message to indicate to the Discovery Responder
that
   it could directly reply to the Discovery Initiator with a
   Synchronization message Section 3.8.10 with synchronization data
for
   rapid processing, if the discovery target supports the
corresponding
   synchronization objective.  The design implications are similar to
   those discussed in Section 3.5.5.1.

   It is possible that a Discovery Response will arrive from a
responder
   that does not support rapid mode, before such a Synchronization
   message arrives.  In this case, rapid mode will not occur.



Bormann, et al.           Expires June 18, 2017                [Page
26]

Internet-Draft                    GRASP                    December
2016


   This rapid mode could reduce the interactions between nodes so that
a
   higher efficiency could be achieved.  However, a network in which
   some nodes support rapid mode and others do not will have complex
   timing-dependent behaviors.  Therefore, the rapid synchronization
   function SHOULD be configured off by default and MAY be configured
on
   or off by Intent.

3.6.  GRASP Constants

   o  ALL_GRASP_NEIGHBOR
CEP: Why not "ALL_GRASP_NEIGHBORS"?

      A link-local scope multicast address used by a GRASP-enabled
      device to discover GRASP-enabled neighbor (i.e., on-link)
devices
      . All devices that support GRASP are members of this multicast
CEP: orphan '.'
      group.

      *  IPv6 multicast address: TBD1

      *  IPv4 multicast address: TBD2

   o  GRASP_LISTEN_PORT (TBD3)

      A well-known UDP user port that every GRASP-enabled network
device
      MUST always listen to for link-local multicasts.
      This user port MAY be also used to listen for TCP or UDP
unicast
      messages in a simple implementation of GRASP (Section 3.5.3).

   o  GRASP_DEF_TIMEOUT (60000 milliseconds)

      The default timeout used to determine that a discovery etc. has
      failed to complete.
CEP: That's a long, long time...

   o  GRASP_DEF_LOOPCT (6)

      The default loop count used to determine that a negotiation has
      failed to complete, and to avoid looping messages.

   o  GRASP_DEF_MAX_SIZE (2048)

      The default maximum message size in bytes.

3.7.  Session Identifier (Session ID)

   This is an 32-bit opaque value used to distinguish multiple
   sessions between the same two devices.  A new Session ID MUST be
   generated by the initiator for every new Discovery, Flood
   Synchronization or Request message.  All responses and follow-up




Bormann, et al.           Expires June 18, 2017                [Page
27]

Internet-Draft                    GRASP                    December
2016


   messages in the same discovery, synchronization or negotiation
   procedure MUST carry the same Session ID.

   The Session ID SHOULD have a very low collision rate locally.  It
   MUST be generated by a pseudo-random algorithm using a locally
   generated seed which is unlikely to be used by any other device in
   the same network [RFC4086].  When allocating a new Session ID,
GRASP
   MUST check that the value is not already in use and SHOULD check
that
   it has not been used recently, by consulting a cache of current
and
   recent sessions.  In the unlikely event of a clash, GRASP MUST
   generate a new value.

   However, there is a finite probability that two nodes might
generate
   the same Session ID value.  For that reason, when a Session ID is
   communicated via GRASP, the receiving node MUST tag it with the
   initiator's IP address to allow disambiguation.  In the highly
   unlikely event of two peers opening sessions with the same Session
ID
   value, this tag will allow the two sessions to be distinguished.
   Multicast GRASP messages and their responses, which may be relayed
   between links, therefore include a field that carries the
initiator's
   global IP address.

   There is a highly unlikely race condition in which two peers start
   simultaneous negotiation sessions with each other using the same
   Session ID value.  Depending on various implementation choices,
this
   might lead to the two sessions being confused.  See Section 3.8.6
for
   details of how to avoid this.

3.8.  GRASP Messages

3.8.1.  Message Overview

   This section defines the GRASP message format and message types.
   Message types not listed here are reserved for future use.

   The messages currently defined are:
CEP: Please include the specific names here.

      Discovery and Discovery Response.

      Request Negotiation, Negotiation, Confirm Waiting and
Negotiation
      End.

      Request Synchronization, Synchronization, and Flood
      Synchronization.

      No Operation.





Bormann, et al.           Expires June 18, 2017                [Page
28]

Internet-Draft                    GRASP                    December
2016


3.8.2.  GRASP Message Format

   GRASP messages share an identical header format and a variable
format
   area for options.  GRASP message headers and options are
transmitted
   in Concise Binary Object Representation (CBOR) [RFC7049].  In this
   specification, they are described using CBOR data definition
language
   (CDDL) [I-D.greevenbosch-appsawg-cbor-cddl].  Fragmentary CDDL is
   used to describe each item in this section.  A complete and
normative
   CDDL specification of GRASP is given in Section 6, including
   constants such as message types.

   Every GRASP message, except the No Operation message, carries a
   Session ID (Section 3.7).  Options are then presented serially in
the
   options field.

   In fragmentary CDDL, every GRASP message follows the pattern:

     grasp-message = (message .within message-structure) /
noop-message

     message-structure = [MESSAGE_TYPE, session-id, ?initiator,
                          *grasp-option]

     MESSAGE_TYPE = 1..255
     session-id = 0..4294967295 ;up to 32 bits
     grasp-option = any

   The MESSAGE_TYPE indicates the type of the message and thus
defines
   the expected options.  Any options received that are not
consistent
   with the MESSAGE_TYPE SHOULD be silently discarded.

   The No Operation (noop) message is described in Section 3.8.13.

   The various MESSAGE_TYPE values are defined in Section 6.

   All other message elements are described below and formally
defined
   in Section 6.

3.8.3.  Message Size

   GRASP nodes MUST be able to receive messages of at least
   GRASP_DEF_MAX_SIZE bytes.  GRASP nodes MUST NOT send messages
longer
   than GRASP_DEF_MAX_SIZE bytes unless a longer size is explicitly
   allowed for the objective concerned.  For example, GRASP
negotiation
   itself could be used to agree on a longer message size.

   The message parser used by GRASP should be configured to know
about
   the GRASP_DEF_MAX_SIZE, or any larger negotiated message size, so
   that it may defend against overly long messages.



Bormann, et al.           Expires June 18, 2017                [Page
29]

Internet-Draft                    GRASP                    December
2016


3.8.4.  Discovery Message

   In fragmentary CDDL, a Discovery message follows the pattern:

     discovery-message = [M_DISCOVERY, session-id, initiator,
objective]

   A discovery initiator sends a Discovery message to initiate a
   discovery process for a particular objective option.

   The discovery initiator sends all Discovery messages via UDP to
port
   GRASP_LISTEN_PORT at the link-local ALL_GRASP_NEIGHBOR multicast
   address on each link-layer interface in use by GRASP.  It then
   listens for unicast TCP responses on a given port, and stores the
   discovery results (including responding discovery objectives and
   corresponding unicast locators).

   The listening port used for TCP MUST be the same port as used for
   sending the Discovery UDP multicast, on a given interface.  In a
low-
   end implementation this MAY be GRASP_LISTEN_PORT.  In a more
complex
   implementation, the GRASP discovery mechanism will find, for each
   interface, a dynamic port that it can bind to for both UDP and TCP
   before initiating any discovery.

   The 'initiator' field in the message is a globally unique IP
address
   of the initiator, for the sole purpose of disambiguating the
Session
   ID in other nodes.  If for some reason the initiator does not have
a
   globally unique IP address, it MUST use a link-local address for
this
   purpose that is highly likely to be unique, for example using
   [RFC7217].

   A Discovery message MUST include exactly one of the following:

   o  a discovery objective option (Section 3.10.1).  Its loop count
      MUST be set to a suitable value to prevent discovery loops
      (default value is GRASP_DEF_LOOPCT).  If the discovery
initiator
      requires only on-link responses, the loop count MUST be set to
1.

   o  a negotiation objective option (Section 3.10.1).  This is used
      both for the purpose of discovery and to indicate to the
discovery
      target that it MAY directly reply to the discovery initiatior
with
      a Negotiation message for rapid processing, if it could act as
the
      corresponding negotiation counterpart.  The sender of such a
      Discovery message MUST initialize a negotiation timer and loop
      count in the same way as a Request Negotiation message
      (Section 3.8.6).

   o  a synchronization objective option (Section 3.10.1).  This is
used
      both for the purpose of discovery and to indicate to the
discovery



Bormann, et al.           Expires June 18, 2017                [Page
30]

Internet-Draft                    GRASP                    December
2016


      target that it MAY directly reply to the discovery initiator
with
      a Synchronization message for rapid processing, if it could act
as
      the corresponding synchronization counterpart.  Its loop count
      MUST be set to a suitable value to prevent discovery loops
      (default value is GRASP_DEF_LOOPCT).

   A Discovery message MAY be sent unicast to a peer
   node, which will then proceed exactly as if the message had been
   multicast.

3.8.5.  Discovery Response Message

   In fragmentary CDDL, a Discovery Response message follows the
   pattern:

     response-message = [M_RESPONSE, session-id, initiator, ttl,
                        (+locator-option // divert-option),
?objective)]

     ttl = 0..4294967295 ; in milliseconds

   A node which receives a Discovery message SHOULD send a Discovery
   Response message if and only if it can respond to the discovery.

      It MUST contain the same Session ID and initiator as the
Discovery
      message.

      It MUST contain a time-to-live (ttl) for the validity of the
      response, given as a positive integer value in milliseconds. 
Zero
      is treated as the default value GRASP_DEF_TIMEOUT (Section
3.6).

      It MAY include a copy of the discovery objective from the
      Discovery message.

   It is sent to the sender of the Discovery message via TCP at the
port
   used to send the Discovery message (as explained in Section
3.8.4).

   If the responding node supports the discovery objective of the
   discovery, it MUST include at least one kind of locator option
   (Section 3.9.5) to indicate its own location.  A sequence of
multiple
   kinds of locator options (e.g.  IP address option and FQDN option)
is
   also valid.

   If the responding node itself does not support the discovery
   objective, but it knows the locator of the discovery objective,
then
   it SHOULD respond to the discovery message with a divert option
   (Section 3.9.2) embedding a locator option or a combination of
   multiple kinds of locator options which indicate the locator(s) of
   the discovery objective.



Bormann, et al.           Expires June 18, 2017                [Page
31]

Internet-Draft                    GRASP                    December
2016


   More details on the processing of Discovery Responses are given in
   Section 3.5.4.

3.8.6.  Request Messages

   In fragmentary CDDL, Request Negotiation and Request
Synchronization
   messages follow the patterns:


   request-negotiation-message = [M_REQ_NEG, session-id, objective]

   request-synchronization-message = [M_REQ_SYN, session-id,
objective]


   A negotiation or synchronization requesting node sends the
   appropriate Request message to the unicast address (directly
stored
   or resolved from an FQDN or URI) of the negotiation or
   synchronization counterpart, using the appropriate protocol and
port
   numbers (selected from the discovery results).

   A Request message MUST include the relevant objective option.  In
the
   case of Request Negotiation, the objective option MUST include the
   requested value.

   When an initiator sends a Request Negotiation message, it MUST
   initialize a negotiation timer for the new negotiation thread. 
The
   default is GRASP_DEF_TIMEOUT milliseconds.  Unless this timeout is
   modified by a Confirm Waiting message (Section 3.8.9), the
initiator
   will consider that the negotiation has failed when the timer
expires.

   Similarly, when an initiator sends a Request Synchronization, it
   SHOULD initialize a synchronization timer.  The default is
   GRASP_DEF_TIMEOUT milliseconds.  The initiator will consider that
   synchronization has failed if there is no response before the
timer
   expires.

   When an initiator sends a Request message, it MUST initialize the
   loop count of the objective option with a value defined in the
   specification of the option or, if no such value is specified,
with
   GRASP_DEF_LOOPCT.

   If a node receives a Request message for an objective for which no
   ASA is currently listening, it MUST immediately close the relevant
   socket to indicate this to the initiator.  This is to avoid
   unnecessary timeouts if, for example, an ASA exits prematurely but
   the GRASP core is listening on its behalf.





Bormann, et al.           Expires June 18, 2017                [Page
32]

Internet-Draft                    GRASP                    December
2016


   To avoid the highly unlikely race condition in which two nodes
   simultaneously request sessions with each other using the same
   Session ID (Section 3.7), when a node receives a Request message,
it
   MUST verify that the received Session ID is not already locally
   active.  In case of a clash, it MUST discard the Request message,
in
   which case the initiator will detect a timeout.

3.8.7.  Negotiation Message

   In fragmentary CDDL, a Negotiation message follows the pattern:

     negotiate-message = [M_NEGOTIATE, session-id, objective]

   A negotiation counterpart sends a Negotiation message in response
to
   a Request Negotiation message, a Negotiation message, or a
Discovery
   message in Rapid Mode.  A negotiation process MAY include multiple
   steps.

   The Negotiation message MUST include the relevant Negotiation
   Objective option, with its value updated according to progress in
the
   negotiation.  The sender MUST decrement the loop count by 1.  If
the
   loop count becomes zero the message MUST NOT be sent.  In this
case
   the negotiation session has failed and will time out.

3.8.8.  Negotiation End Message

   In fragmentary CDDL, a Negotiation End message follows the
pattern:

     end-message = [M_END, session-id, accept-option /
decline-option]

   A negotiation counterpart sends an Negotiation End message to
close
   the negotiation.  It MUST contain either an accept or a decline
   option, defined in Section 3.9.3 and Section 3.9.4.  It could be
sent
   either by the requesting node or the responding node.

3.8.9.  Confirm Waiting Message

   In fragmentary CDDL, a Confirm Waiting message follows the
pattern:

     wait-message = [M_WAIT, session-id, waiting-time]
     waiting-time = 0..4294967295 ; in milliseconds

   A responding node sends a Confirm Waiting message to ask the
   requesting node to wait for a further negotiation response.  It
might
   be that the local process needs more time or that the negotiation
   depends on another triggered negotiation.  This message MUST NOT
   include any other options.  When received, the waiting time value




Bormann, et al.           Expires June 18, 2017                [Page
33]

Internet-Draft                    GRASP                    December
2016


   overwrites and restarts the current negotiation timer
   (Section 3.8.6).

   The responding node SHOULD send a Negotiation, Negotiation End or
   another Confirm Waiting message before the negotiation timer
expires.
   If not, the initiator MUST abandon or restart the negotiation
   procedure, to avoid an indefinite wait.

3.8.10.  Synchronization Message

   In fragmentary CDDL, a Synchronization message follows the
pattern:

     synch-message = [M_SYNCH, session-id, objective]

   A node which receives a Request Synchronization, or a Discovery
   message in Rapid Mode, sends back a unicast Synchronization
message
   with the synchronization data, in the form of a GRASP Option for
the
   specific synchronization objective present in the Request
   Synchronization.

3.8.11.  Flood Synchronization Message

   In fragmentary CDDL, a Flood Synchronization message follows the
   pattern:

     flood-message = [M_FLOOD, session-id, initiator, ttl,
                     +[objective, (locator-option / [])]]

     ttl = 0..4294967295 ; in milliseconds

   A node MAY initiate flooding by sending an unsolicited Flood
   Synchronization Message with synchronization data.  This MAY be
sent
   to the link-local ALL_GRASP_NEIGHBOR multicast address, in
accordance
   with the rules in Section 3.5.6.

      The initiator address is provided, as described for Discovery
      messages (Section 3.8.4), only to disambiguate the Session ID.

      The message MUST contain a time-to-live (ttl) for the validity
of
      the contents, given as a positive integer value in
milliseconds.
      There is no default; zero indicates an indefinite lifetime.

      The synchronization data are in the form of GRASP Option(s) for
      specific synchronization objective(s).  The loop count(s) MUST
be
      set to a suitable value to prevent flood loops (default value
is
      GRASP_DEF_LOOPCT).





Bormann, et al.           Expires June 18, 2017                [Page
34]

Internet-Draft                    GRASP                    December
2016


      Each objective option MAY be followed by a locator option
      associated with the flooded objective.  In its absence, an
empty
      option MUST be included to indicate a null locator.

   A node that receives a Flood Synchronization message MUST cache
the
   received objectives for use by local ASAs.  Each cached objective
   MUST be tagged with the locator option sent with it, or with a
null
   tag if an empty locator option was sent.  If a subsequent Flood
   Synchronization message carrying the same objective arrives with
the
   same tag, the corresponding cached copy of the objective MUST be
   overwritten.  If a subsequent Flood Synchronization message
carrying
   the same objective arrives with a different tag, a new cached
entry
   MUST be created.

   Note: the purpose of this mechanism is to allow the recipient of
   flooded values to distinguish between different senders of the
same
   objective, and if necessary communicate with them using the
locator,
   protocol and port included in the locator option.  Many objectives
   will not need this mechanism, so they will be flooded with a null
   locator.

   Cached entries MUST be ignored or deleted after their lifetime
   expires.

3.8.12.  Invalid Message

   In fragmentary CDDL, an Invalid message follows the pattern:

     invalid-message = [M_INVALID, session-id, ?any]

   This message MAY be sent by an implementation in response to an
   incoming message that it considers invalid.  The session-id MUST
be
   copied from the incoming message.  The content SHOULD be
diagnostic
   information such as a partial copy of the invalid message.  An
   M_INVALID message MAY be silently ignored by a recipient. 
However,
   it could be used in support of extensibility, since it indicates
that
   the remote node does not support a new or obsolete message or
option.
CEP: missing '.'

   An M_INVALID message MUST NOT be sent in response to an M_INVALID
   message.

3.8.13.  No Operation Message

   In fragmentary CDDL, a No Operation message follows the pattern:

     noop-message = [M_NOOP]





Bormann, et al.           Expires June 18, 2017                [Page
35]

Internet-Draft                    GRASP                    December
2016


   This message MAY be sent by an implementation that for practical
   reasons needs to activate a socket.  It MUST be silently ignored by
a
   recipient.
CEP: ?? what does it mean to "activate" a socket?  Is there something
about
	how long a socket may remain open but not used?

3.9.  GRASP Options

   This section defines the GRASP options for the negotiation and
   synchronization protocol signaling.  Additional options may be
   defined in the future.

3.9.1.  Format of GRASP Options

   GRASP options are CBOR objects that MUST start with an unsigned
   integer identifying the specific option type carried in this
option.
   These option types are formally defined in Section 6.  Apart from
   that the only format requirement is that each option MUST be a
well-
   formed CBOR object.  In general a CBOR array format is RECOMMENDED
to
   limit overhead.

   GRASP options are usually scoped by using encapsulation.  However,
   this is not a requirement
CEP: missing '.'
CEP: What does this use of "scoped" mean?

3.9.2.  Divert Option

   The Divert option is used to redirect a GRASP request to another
   node, which may be more appropriate for the intended negotiation
or
   synchronization.  It may redirect to an entity that is known as a
   specific negotiation or synchronization counterpart (on-link or
off-
   link) or a default gateway.  The divert option MUST only be
   encapsulated in Discovery Response messages.  If found elsewhere,
it
   SHOULD be silently ignored.

   A discovery initiator MAY ignore a Divert option if it only
requires
   direct discovery responses.

   In fragmentary CDDL, the Divert option follows the pattern:

     divert-option = [O_DIVERT, +locator-option]

   The embedded Locator Option(s) (Section 3.9.5) points to diverted
   destination target(s) in response to a Discovery message.

3.9.3.  Accept Option

   The accept option is used to indicate to the negotiation
counterpart
   that the proposed negotiation content is accepted.





Bormann, et al.           Expires June 18, 2017                [Page
36]

Internet-Draft                    GRASP                    December
2016


   The accept option MUST only be encapsulated in Negotiation End
   messages.  If found elsewhere, it SHOULD be silently ignored.

   In fragmentary CDDL, the Accept option follows the pattern:

     accept-option = [O_ACCEPT]

3.9.4.  Decline Option

   The decline option is used to indicate to the negotiation
counterpart
   the proposed negotiation content is declined and end the
negotiation
   process.

   The decline option MUST only be encapsulated in Negotiation End
   messages.  If found elsewhere, it SHOULD be silently ignored.

   In fragmentary CDDL, the Decline option follows the pattern:

     decline-option = [O_DECLINE, ?reason]
     reason = text  ;optional error message

   Note: there are scenarios where a negotiation counterpart wants to
   decline the proposed negotiation content and continue the
negotiation
   process.  For these scenarios, the negotiation counterpart SHOULD
use
   a Negotiate message, with either an objective option that contains
a
   data field set to indicate a meaningless initial value, or a
specific
   objective option that provides further conditions for convergence.
CEP: Why is this better than simply initiating a new Negotiation?

3.9.5.  Locator Options

   These locator options are used to present reachability information
   for an ASA, a device or an interface.  They are Locator IPv6
Address
   Option, Locator IPv4 Address Option, Locator FQDN (Fully Qualified
   Domain Name) Option and URI (Uniform Resource Identifier) Option.

   Since ASAs will normally run as independent user programs, locator
   options need to indicate the network layer locator plus the
transport
   protocol and port number for reaching the target.  For this
reason,
   the Locator Options for IP addresses and FQDNs include this
   information explicitly.  In the case of the URI Option, this
   information can be encoded in the URI itself.

   Note: It is assumed that all locators are in scope throughout the
   GRASP domain.  GRASP is not intended to work across disjoint
   addressing or naming realms.
CEP: It's hard to imagine the practical effect of making this
statement.






Bormann, et al.           Expires June 18, 2017                [Page
37]

Internet-Draft                    GRASP                    December
2016


3.9.5.1.  Locator IPv6 address option

   In fragmentary CDDL, the IPv6 address option follows the pattern:

     ipv6-locator-option = [O_IPv6_LOCATOR, ipv6-address,
                            transport-proto, port-number]
     ipv6-address = bytes .size 16

     transport-proto = IPPROTO_TCP / IPPROTO_UDP
     IPPROTO_TCP = 6
     IPPROTO_UDP = 17
     port-number = 0..65535

   The content of this option is a binary IPv6 address followed by
the
   protocol number and port number to be used.

   Note 1: The IPv6 address MUST normally have global scope.
   During initialisation, a link-local address MAY be
   used for specific objectives only (Section 3.5.2).  In this case
the
   corresponding Discovery Response message MUST be sent via the
   interface to which the link-local address applies.

   Note 2: A link-local IPv6 address MUST NOT be used when this
option
   is included in a Divert option.

3.9.5.2.  Locator IPv4 address option

   In fragmentary CDDL, the IPv4 address option follows the pattern:

     ipv4-locator-option = [O_IPv4_LOCATOR, ipv4-address,
                            transport-proto, port-number]
     ipv4-address = bytes .size 4

   The content of this option is a binary IPv4 address followed by
the
   protocol number and port number to be used.

   Note: If an operator has internal network address translation for
   IPv4, this option MUST NOT be used within the Divert option.

3.9.5.3.  Locator FQDN option

   In fragmentary CDDL, the FQDN option follows the pattern:

     fqdn-locator-option = [O_FQDN_LOCATOR, text,
                            transport-proto, port-number]

   The content of this option is the Fully Qualified Domain Name of
the
   target followed by the protocol number and port number to be used.



Bormann, et al.           Expires June 18, 2017                [Page
38]

Internet-Draft                    GRASP                    December
2016


   Note 1: Any FQDN which might not be valid throughout the network
in
   question, such as a Multicast DNS name [RFC6762], MUST NOT be used
   when this option is used within the Divert option.

   Note 2: Normal GRASP operations are not expected to use this
option.
   It is intended for special purposes such as discovering external
   services.

3.9.5.4.  Locator URI option

   In fragmentary CDDL, the URI option follows the pattern:

     uri-locator = [O_URI_LOCATOR, text]

   The content of this option is the Uniform Resource Identifier of
the
   target [RFC3986].

   Note 1: Any URI which might not be valid throughout the network in
   question, such as one based on a Multicast DNS name [RFC6762],
MUST
   NOT be used when this option is used within the Divert option.

   Note 2: Normal GRASP operations are not expected to use this
option.
   It is intended for special purposes such as discovering external
   services.

3.10.  Objective Options

3.10.1.  Format of Objective Options

   An objective option is used to identify objectives for the
purposes
   of discovery, negotiation or synchronization.  All objectives MUST
be
   in the following format, described in fragmentary CDDL:

     objective = [objective-name, objective-flags, loop-count, ?any]

     objective-name = text
     loop-count = 0..255

   All objectives are identified by a unique name which is a case-
   sensitive UTF-8 string.

   The names of generic objectives MUST NOT include a colon (":") and
   MUST be registered with IANA (Section 7).

   The names of privately defined objectives MUST include at least
one
   colon (":").  The string preceding the last colon in the name MUST
be
   globally unique and in some way identify the entity or person




Bormann, et al.           Expires June 18, 2017                [Page
39]

Internet-Draft                    GRASP                    December
2016


   defining the objective.  The following three methods MAY be used
to
   create such a globally unique string:

   1.  The unique string is a decimal number representing a
registered
       32 bit Private Enterprise Number (PEN) [I-D.liang-iana-pen]
that
       uniquely identifies the enterprise defining the objective.

   2.  The unique string is a fully qualified domain name that
uniquely
       identifies the entity or person defining the objective.

   3.  The unique string is an email address that uniquely identifies
       the entity or person defining the objective.

   The GRASP protocol treats the objective name as an opaque string.
   For example, "EX1", "411:EX1", "example.com:EX1", "example.org:EX1
   and "user@example.org:EX1" would be five different objectives.

   The 'objective-flags' field is described below.

   The 'loop-count' field is used for terminating negotiation as
   described in Section 3.8.7.  It is also used for terminating
   discovery as described in Section 3.5.4, and for terminating
flooding
   as described in Section 3.5.6.1.
CEP: It would be much more intuitive to put "loop-count" in the
message format.

   The 'any' field is to express the actual value of a negotiation or
   synchronization objective.  Its format is defined in the
   specification of the objective and may be a single value or a data
   structure of any kind.  It is optional because it is optional in a
   Discovery or Discovery Response message.

3.10.2.  Objective flags

   An objective may be relevant for discovery only, for discovery and
   negotiation, or for discovery and synchronization.  This is
expressed
   in the objective by logical flag bits:

     objective-flags = uint .bits objective-flag
     objective-flag = &(
     F_DISC: 0    ; valid for discovery
     F_NEG: 1     ; valid for negotiation
     F_SYNCH: 2   ; valid for synchronization
     F_NEG_DRY: 3 ; negotiation is dry-run
     )

   These bits are independent and may be combined appropriately, e.g.
   (F_DISC and F_SYNCH) or (F_DISC and F_NEG) or (F_DISC and F_NEG
and
   F_NEG_DRY).




Bormann, et al.           Expires June 18, 2017                [Page
40]

Internet-Draft                    GRASP                    December
2016


   Note that for a given negotiation session, an objective must be
   either used for negotiation, or for dry-run negotiation.  Mixing
the
   two modes in a single negotiation is not possible.

3.10.3.  General Considerations for Objective Options

   As mentioned above, Objective Options MUST be assigned a unique
name.
   As long as privately defined Objective Options obey the rules
above,
   this document does not restrict their choice of name, but the
entity
   or person concerned SHOULD publish the names in use.

   All Objective Options MUST respect the CBOR patterns defined above
as
   "objective" and MUST replace the "any" field with a valid CBOR
data
   definition for the relevant use case and application.

   An Objective Option that contains no additional fields beyond its
   "loop-count" can only be a discovery objective and MUST only be
used
   in Discovery and Discovery Response messages.

   The Negotiation Objective Options contain negotiation objectives,
   which vary according to different functions/services.  They MUST
be
   carried by Discovery, Request Negotiation or Negotiation messages
   only.  The negotiation initiator MUST set the initial "loop-count"
to
   a value specified in the specification of the objective or, if no
   such value is specified, to GRASP_DEF_LOOPCT.

   For most scenarios, there should be initial values in the
negotiation
   requests.  Consequently, the Negotiation Objective options MUST
   always be completely presented in a Request Negotiation message,
or
   in a Discovery message in rapid mode.  If there is no initial
value,
   the bits in the value field SHOULD all be set to indicate a
   meaningless value, unless this is inappropriate for the specific
   negotiation objective.
CEP: Maybe better to require such objective descriptions to mandate a
	particular O_INVALID_VALUE, whenever needed.

   Synchronization Objective Options are similar, but MUST be carried
by
   Discovery, Discovery Response, Request Synchronization, or Flood
   Synchronization messages only.  They include value fields only in
   Synchronization or Flood Synchronization messages.

3.10.4.  Organizing of Objective Options

   Generic objective options MUST be specified in documents available
to
   the public and SHOULD be designed to use either the negotiation or
   the synchronization mechanism described above.

   As noted earlier, one negotiation objective is handled by each
GRASP
   negotiation thread.  Therefore, a negotiation objective, which is
   based on a specific function or action, SHOULD be organized as a



Bormann, et al.           Expires June 18, 2017                [Page
41]

Internet-Draft                    GRASP                    December
2016


   single GRASP option.  It is NOT RECOMMENDED to organize multiple
   negotiation objectives into a single option, nor to split a single
   function or action into multiple negotiation objectives.

   It is important to understand that GRASP negotiation does not
support
   transactional integrity.  If transactional integrity is needed for
a
   specific objective, this must be ensured by the ASA.  For example,
an
   ASA might need to ensure that it only participates in one
negotiation
   thread at the same time.  Such an ASA would need to stop listening
   for incoming negotiation requests before generating an outgoing
   negotiation request.

   A synchronization objective SHOULD be organized as a single GRASP
   option.

   Some objectives will support more than one operational mode.  An
   example is a negotiation objective with both a "dry run" mode
(where
   the negotiation is to find out whether the other end can in fact
make
   the requested change without problems) and a "live" mode.  Such
modes
   will be defined in the specification of such an objective.  These
   objectives SHOULD include flags indicating the applicable mode(s).
CEP: Dry Run has a significant flaw.  Namely, it appears to be
stateless,
	so that subsequent simulation steps would not be acting in the
	stateful environment that a true negotiation (or true simulation)
	would be.

   An objective may have multiple parameters.  Parameters can be
   categorized into two classes: the obligatory ones presented as
fixed
   fields; and the optional ones presented in CBOR sub-options or
some
   other form of data structure embedded in CBOR.  The format might
be
   inherited from an existing management or configuration protocol,
the
   objective option acting as a carrier for that format.  The data
   structure might be defined in a formal language, but that is a
matter
   for the specifications of individual objectives.  There are many
   candidates, according to the context, such as ABNF, RBNF, XML
Schema,
   possibly YANG, etc.  The GRASP protocol itself is agnostic on
these
   questions.
CEP: It not clear what effect, if any, this text could have.  Delete?

   It is NOT RECOMMENDED to split parameters in a single objective
into
   multiple options, unless they have different response periods.  An
   exception scenario may also be described by split objectives.

   All objectives MUST support GRASP discovery.  However, as
mentioned
   in Section 3.3, it is acceptable for an ASA to use an alternative
   method of discovery.

   Normally, a GRASP objective will refer to specific technical
   parameters as explained in Section 3.1.  However, it is acceptable
to
   define an abstract objective for the purpose of managing or
   coordinating ASAs.  It is also acceptable to define a
special-purpose
   objective for purposes such as trust bootstrapping or formation of
   the ACP.
CEP: This doesn't really seem to specify anything.



Bormann, et al.           Expires June 18, 2017                [Page
42]

Internet-Draft                    GRASP                    December
2016


   To guarantee convergence, a limited number of rounds or a timeout
is
   needed for each negotiation objective.  Therefore, the definition
of
   each negotiation objective SHOULD clearly specify this, for example
a
   default loop count and timeout, so that the negotiation can always
be
   terminated properly.  If not, the GRASP defaults will apply.

   There must be a well-defined procedure for concluding that a
   negotiation cannot succeed, and if so deciding what happens next
   (e.g., deadlock resolution, tie-breaking, or revert to best-effort
   service).  This MUST be specified for individual negotiation
   objectives.

3.10.5.  Experimental and Example Objective Options

   The names "EX0" through "EX9" have been reserved for experimental
   options.  Multiple names have been assigned because a single
   experiment may use multiple options simultaneously.  These
   experimental options are highly likely to have different meanings
   when used for different experiments.  Therefore, they SHOULD NOT
be
   used without an explicit human decision and SHOULD NOT be used in
   unmanaged networks such as home networks.

   These names are also RECOMMENDED for use in documentation
examples.

4.  Implementation Status [RFC Editor: please remove]

   Two prototype implementations of GRASP have been made.

4.1.  BUPT C++ Implementation

   o  Name: BaseNegotiator.cpp, msg.cpp, Client.cpp, Server.cpp

   o  Description: C++ implementation of GRASP core and API

   o  Maturity: Prototype code, interoperable between Ubuntu.

   o  Coverage: Corresponds to draft-carpenter-anima-gdn-protocol-03.
      Since it was implemented based on the old version draft, the
most
      significant limitations comparing to current protocol design
      include:

      *  Not support CBOR

      *  Not support Flooding

      *  Not support loop avoidance

      *  only coded for IPv6, any IPv4 is accidental



Bormann, et al.           Expires June 18, 2017                [Page
43]

Internet-Draft                    GRASP                    December
2016


   o  Licensing: Huawei License.

   o  Experience:
https://github.com/liubingpang/IETF-Anima-Signaling-
      Protocol/blob/master/README.md

   o  Contact: https://github.com/liubingpang/IETF-Anima-Signaling-
      Protocol

4.2.  Python Implementation

   o  Name: graspy

   o  Description: Python 3 implementation of GRASP core and API.

   o  Maturity: Prototype code, interoperable between Windows 7 and
      Linux.

   o  Coverage: Corresponds to draft-ietf-anima-grasp-08. 
Limitations
      include:

      *  insecure: uses a dummy ACP module and does not implement TLS

      *  only coded for IPv6, any IPv4 is accidental

      *  FQDN and URI locators incompletely supported

      *  no code for rapid mode

      *  relay code is lazy (no rate control)

      *  all unicast transactions use TCP (no unicast UDP).
         Experimental code for unicast UDP proved to be complex and
         brittle.

      *  optional Objective option in Response messages not
implemented

      *  workarounds for defects in Python socket module and Windows
         socket peculiarities

   o  Licensing: Simplified BSD

   o  Experience:
https://www.cs.auckland.ac.nz/~brian/graspy/graspy.pdf

   o  Contact: https://www.cs.auckland.ac.nz/~brian/graspy/







Bormann, et al.           Expires June 18, 2017                [Page
44]

Internet-Draft                    GRASP                    December
2016


5.  Security Considerations

   A successful attack on negotiation-enabled nodes
   would be extremely harmful, as such nodes might end up with an
   undesirable configuration that would also adversely affect
   their peers.  GRASP nodes and messages therefore require full
   protection.

   - Authentication

      A cryptographically authenticated identity for each device is
      needed in an autonomic network.  It is not safe to assume that
a
      large network is physically secured against interference or
that
      all personnel are trustworthy.  Each autonomic node MUST be
      capable of proving its identity and authenticating its
messages.
      GRASP relies on a separate external certificate-based security
      mechanism to support authentication, data integrity protection,
      and anti-replay protection.

      Since GRASP is intended to be deployed in a single
administrative
      domain operating its own trust anchor and CA, there is no need
for
      a trusted public third party.  In a network requiring "air gap"
      security, such a dependency would be unacceptable.
CEP: More explanation is needed for this.

      If GRASP is used temporarily without an external security
      mechanism, for example during system bootstrap (Section 3.5.1),
      the Session ID (Section 3.7) will act as a nonce to provide
      limited protection against third parties injecting responses. 
A
      full analysis of the secure bootstrap process is out of scope
for
      the present document.
CEP: That is very surprising, given that it is crucial to make a
secure
	bootstrap process.  Is there another document?  Please cite.

   - Authorization and Roles

      The GRASP protocol is agnostic about the role of individual
ASAs
CEP: the concept of "role" does not seem to be well-defined.
      and about which objectives a particular ASA is authorized to
      support.  An implementation might support precautions such as
      allowing only one ASA in a given node to modify a given
objective,
      but this may not be appropriate in all cases.  For example, it
      might be operationally useful to allow an old and a new version
of
      the same ASA to run simultaneously during an overlap period.
      These questions are out of scope for the present specification.
CEP: Not clear what is the value of this text.

   - Privacy and confidentiality

      Generally speaking, no personal information is expected to be
      involved in the signaling protocol, so there should be no
direct
      impact on personal privacy.  Nevertheless, traffic flow paths,
      VPNs, etc. could be negotiated, which could be of interest for



Bormann, et al.           Expires June 18, 2017                [Page
45]

Internet-Draft                    GRASP                    December
2016


      traffic analysis.  Also, operators generally want to conceal
      details of their network topology and traffic density from
      outsiders.  Therefore, since insider attacks cannot be excluded
in
      a large network, the security mechanism for the protocol MUST
      provide message confidentiality.  This is why Section 3.5.1
      requires either an ACP or an alternative security mechanism.

   - Link-local multicast security

      GRASP has no reasonable alternative to using link-local
multicast
      for Discovery or Flood Synchronization messages and these
messages
      are sent in clear and with no authentication.  They are
therefore
      available to on-link eavesdroppers, and could be forged by
on-link
      attackers.  In the case of Discovery, the Discovery Responses
are
      unicast and will therefore be protected (Section 3.5.1), and an
      untrusted forger will not be able to receive responses.  In the
      case of Flood Synchronization, an on-link eavesdropper will be
      able to receive the flooded objectives but there is no response
      message to consider.  Some precautions for Flood
Synchronization
      messages are suggested in Section 3.5.6.1.

   - DoS Attack Protection

      GRASP discovery partly relies on insecure link-local multicast.
      Since routers participating in GRASP sometimes relay discovery
      messages from one link to another, this could be a vector for
      denial of service attacks.  Some mitigations are specified in
      Section 3.5.4.  However, malicious code installed inside the
      Autonomic Control Plane could always launch DoS attacks
consisting
      of spurious discovery messages, or of spurious discovery
      responses.  It is of great importance that firewalls
      prevent any GRASP messages from entering the domain from an
      untrusted source.
CEP: If so, need to specify how a source establishes trust with a
firewall.

   - Security during bootstrap and discovery

      A node cannot authenticate GRASP traffic from other nodes until
it
      has identified the trust anchor and can validate certificates
for
      other nodes.  Also, until it has succesfully enrolled
      [I-D.ietf-anima-bootstrapping-keyinfra] it cannot assume that
      other nodes are able to authenticate its own traffic. 
Therefore,
      GRASP discovery during the bootstrap phase for a new device
will
      inevitably be insecure and GRASP synchronization and
negotiation
      will be impossible until enrollment is complete.  Further
details
      are given in Section 3.5.2.
CEP: Other places in the document allow for alternative security
mechanisms.

   - Security of discovered locators




Bormann, et al.           Expires June 18, 2017                [Page
46]

Internet-Draft                    GRASP                    December
2016


      When GRASP discovery returns an IP address, it MUST be that of
a
      node within the secure environment (Section 3.5.1).  If it
returns
      an FQDN or a URI, the ASA that receives it MUST NOT assume that
      the target of the locator is within the secure environment.

6.  CDDL Specification of GRASP

  <CODE BEGINS>
  grasp-message = (message .within message-structure) / noop-message

  message-structure = [MESSAGE_TYPE, session-id, ?initiator,
                       *grasp-option]

  MESSAGE_TYPE = 0..255
  session-id = 0..4294967295 ;up to 32 bits
  grasp-option = any

  message /= discovery-message
  discovery-message = [M_DISCOVERY, session-id, initiator, objective]

  message /= response-message ;response to Discovery
  response-message = [M_RESPONSE, session-id, initiator, ttl,
                     (+locator-option // divert-option), ?objective]

  message /= synch-message ;response to Synchronization request
  synch-message = [M_SYNCH, session-id, objective]

  message /= flood-message
  flood-message = [M_FLOOD, session-id, initiator, ttl,
                  +[objective, (locator-option / [])]]

  message /= request-negotiation-message
  request-negotiation-message = [M_REQ_NEG, session-id, objective]

  message /= request-synchronization-message
  request-synchronization-message = [M_REQ_SYN, session-id,
objective]

  message /= negotiation-message
  negotiation-message = [M_NEGOTIATE, session-id, objective]

  message /= end-message
  end-message = [M_END, session-id, accept-option / decline-option ]

  message /= wait-message
  wait-message = [M_WAIT, session-id, waiting-time]

  message /= invalid-message
  invalid-message = [M_INVALID, session-id, ?any]



Bormann, et al.           Expires June 18, 2017                [Page
47]

Internet-Draft                    GRASP                    December
2016


  noop-message = [M_NOOP]

  divert-option = [O_DIVERT, +locator-option]

  accept-option = [O_ACCEPT]

  decline-option = [O_DECLINE, ?reason]
  reason = text  ;optional error message

  waiting-time = 0..4294967295 ; in milliseconds
  ttl = 0..4294967295 ; in milliseconds

  locator-option /= [O_IPv4_LOCATOR, ipv4-address,
                     transport-proto, port-number]
  ipv4-address = bytes .size 4

  locator-option /= [O_IPv6_LOCATOR, ipv6-address,
                     transport-proto, port-number]
  ipv6-address = bytes .size 16

  locator-option /= [O_FQDN_LOCATOR, text, transport-proto,
port-number]

  transport-proto = IPPROTO_TCP / IPPROTO_UDP
  IPPROTO_TCP = 6
  IPPROTO_UDP = 17
  port-number = 0..65535

  locator-option /= [O_URI_LOCATOR, text]

  initiator = ipv4-address / ipv6-address

  objective-flags = uint .bits objective-flag

  objective-flag = &(
    F_DISC: 0    ; valid for discovery
    F_NEG: 1     ; valid for negotiation
    F_SYNCH: 2   ; valid for synchronization
    F_NEG_DRY: 3 ; negotiation is dry-run
  )

  objective = [objective-name, objective-flags, loop-count, ?any]

  objective-name = text ;see specification for uniqueness rules

  loop-count = 0..255

  ; Constants for message types and option types




Bormann, et al.           Expires June 18, 2017                [Page
48]

Internet-Draft                    GRASP                    December
2016


  M_NOOP = 0
  M_DISCOVERY = 1
  M_RESPONSE = 2
  M_REQ_NEG = 3
  M_REQ_SYN = 4
  M_NEGOTIATE = 5
  M_END = 6
  M_WAIT = 7
  M_SYNCH = 8
  M_FLOOD = 9
  M_INVALID = 99

  O_DIVERT = 100
  O_ACCEPT = 101
  O_DECLINE = 102
  O_IPv6_LOCATOR = 103
  O_IPv4_LOCATOR = 104
  O_FQDN_LOCATOR = 105
  O_URI_LOCATOR = 106
  <CODE ENDS>

7.  IANA Considerations

   This document defines the GeneRic Autonomic Signaling Protocol
   (GRASP).

   Section 3.6 explains the following link-local multicast addresses,
   which IANA is requested to assign for use by GRASP:

   ALL_GRASP_NEIGHBOR multicast address  (IPv6): (TBD1).  Assigned in
      the IPv6 Link-Local Scope Multicast Addresses registry.

   ALL_GRASP_NEIGHBOR multicast address  (IPv4): (TBD2).  Assigned in
      the IPv4 Multicast Local Network Control Block.

   Section 3.6 explains the following User Port, which IANA is
requested
   to assign for use by GRASP for both UDP and TCP:

   GRASP_LISTEN_PORT: (TBD3)
   Service Name: Generic Autonomic Signaling Protocol (GRASP)
   Transport Protocols: UDP, TCP
   Assignee: iesg@ietf.org
   Contact: chair@ietf.org
   Description: See Section 3.6
   Reference: RFC XXXX (this document)






Bormann, et al.           Expires June 18, 2017                [Page
49]

Internet-Draft                    GRASP                    December
2016


   The IANA is requested to create a GRASP Parameter Registry
including
   two registry tables.  These are the GRASP Messages and Options
   Table and the GRASP Objective Names Table.

   GRASP Messages and Options Table.  The values in this table are
names
   paired with decimal integers.  Future values MUST be assigned
using
   the Standards Action policy defined by [RFC5226].  The following
   initial values are assigned by this document:

   M_NOOP = 0
   M_DISCOVERY = 1
   M_RESPONSE = 2
   M_REQ_NEG = 3
   M_REQ_SYN = 4
   M_NEGOTIATE = 5
   M_END = 6
   M_WAIT = 7
   M_SYNCH = 8
   M_FLOOD = 9
   M_INVALID = 99

   O_DIVERT = 100
   O_ACCEPT = 101
   O_DECLINE = 102
   O_IPv6_LOCATOR = 103
   O_IPv4_LOCATOR = 104
   O_FQDN_LOCATOR = 105
   O_URI_LOCATOR = 106

   GRASP Objective Names Table.  The values in this table are UTF-8
   strings.  Future values MUST be assigned using the Specification
   Required policy defined by [RFC5226].  The following initial
values
   are assigned by this document:

    EX0
    EX1
    EX2
    EX3
    EX4
    EX5
    EX6
    EX7
    EX8
    EX9







Bormann, et al.           Expires June 18, 2017                [Page
50]

Internet-Draft                    GRASP                    December
2016


8.  Acknowledgements

   A major contribution to the original version of this document was
   made by Sheng Jiang.  Significant review inputs were received from
   Joel Halpern, Toerless Eckert and Michael Richardson.

   Valuable comments were received from Michael Behringer, Jeferson
   Campos Nobre, Laurent Ciavaglia, Zongpeng Du, Yu Fu, Zhenbin Li,
   Dimitri Papadimitriou, Pierre Peloso, Reshad Rahman, Markus
Stenberg,
   Rene Struik, Dacheng Zhang, and other participants in the NMRG
   research group and the ANIMA working group.

9.  References

9.1.  Normative References

   [I-D.greevenbosch-appsawg-cbor-cddl]
              Vigano, C. and H. Birkholz, "CBOR data definition
language
              (CDDL): a notational convention to express CBOR data
              structures", draft-greevenbosch-appsawg-cbor-cddl-09
(work
              in progress), September 2016.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119,
              DOI 10.17487/RFC2119, March 1997,
              <http://www.rfc-editor.org/info/rfc2119>.

   [RFC3986]  Berners-Lee, T., Fielding, R., and L. Masinter,
"Uniform
              Resource Identifier (URI): Generic Syntax", STD 66,
              RFC 3986, DOI 10.17487/RFC3986, January 2005,
              <http://www.rfc-editor.org/info/rfc3986>.

   [RFC4086]  Eastlake 3rd, D., Schiller, J., and S. Crocker,
              "Randomness Requirements for Security", BCP 106, RFC
4086,
              DOI 10.17487/RFC4086, June 2005,
              <http://www.rfc-editor.org/info/rfc4086>.

   [RFC5246]  Dierks, T. and E. Rescorla, "The Transport Layer
Security
              (TLS) Protocol Version 1.2", RFC 5246,
              DOI 10.17487/RFC5246, August 2008,
              <http://www.rfc-editor.org/info/rfc5246>.

   [RFC5280]  Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,
              Housley, R., and W. Polk, "Internet X.509 Public Key
              Infrastructure Certificate and Certificate Revocation
List
              (CRL) Profile", RFC 5280, DOI 10.17487/RFC5280, May
2008,
              <http://www.rfc-editor.org/info/rfc5280>.




Bormann, et al.           Expires June 18, 2017                [Page
51]

Internet-Draft                    GRASP                    December
2016


   [RFC6347]  Rescorla, E. and N. Modadugu, "Datagram Transport Layer
              Security Version 1.2", RFC 6347, DOI 10.17487/RFC6347,
              January 2012, <http://www.rfc-editor.org/info/rfc6347>.

   [RFC7049]  Bormann, C. and P. Hoffman, "Concise Binary Object
              Representation (CBOR)", RFC 7049, DOI 10.17487/RFC7049,
              October 2013, <http://www.rfc-editor.org/info/rfc7049>.

   [RFC7217]  Gont, F., "A Method for Generating Semantically Opaque
              Interface Identifiers with IPv6 Stateless Address
              Autoconfiguration (SLAAC)", RFC 7217,
              DOI 10.17487/RFC7217, April 2014,
              <http://www.rfc-editor.org/info/rfc7217>.

9.2.  Informative References

   [I-D.chaparadza-intarea-igcp]
              Behringer, M., Chaparadza, R., Petre, R., Li, X., and
H.
              Mahkonen, "IP based Generic Control Protocol (IGCP)",
              draft-chaparadza-intarea-igcp-00 (work in progress),
July
              2011.

   [I-D.ietf-anima-autonomic-control-plane]
              Behringer, M., Eckert, T., and S. Bjarnason, "An
Autonomic
              Control Plane", draft-ietf-anima-autonomic-control-
              plane-04 (work in progress), October 2016.

   [I-D.ietf-anima-bootstrapping-keyinfra]
              Pritikin, M., Richardson, M., Behringer, M., Bjarnason,
              S., and K. Watsen, "Bootstrapping Remote Secure Key
              Infrastructures (BRSKI)",
draft-ietf-anima-bootstrapping-
              keyinfra-04 (work in progress), October 2016.

   [I-D.ietf-anima-reference-model]
              Behringer, M., Carpenter, B., Eckert, T., Ciavaglia,
L.,
              Pierre, P., Liu, B., Nobre, J., and J. Strassner, "A
              Reference Model for Autonomic Networking", draft-ietf-
              anima-reference-model-02 (work in progress), July 2016.

   [I-D.ietf-anima-stable-connectivity]
              Eckert, T. and M. Behringer, "Using Autonomic Control
              Plane for Stable Connectivity of Network OAM",
draft-ietf-
              anima-stable-connectivity-01 (work in progress), July
              2016.







Bormann, et al.           Expires June 18, 2017                [Page
52]

Internet-Draft                    GRASP                    December
2016


   [I-D.ietf-netconf-restconf]
              Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
              Protocol", draft-ietf-netconf-restconf-18 (work in
              progress), October 2016.

   [I-D.liang-iana-pen]
              Liang, P., Melnikov, A., and D. Conrad, "Private
              Enterprise Number (PEN) practices and Internet Assigned
              Numbers Authority (IANA) registration considerations",
              draft-liang-iana-pen-06 (work in progress), July 2015.

   [I-D.liu-anima-grasp-api]
              Carpenter, B., Liu, B., Wang, W., and X. Gong, "Generic
              Autonomic Signaling Protocol Application Program
Interface
              (GRASP API)", draft-liu-anima-grasp-api-02 (work in
              progress), September 2016.

   [I-D.stenberg-anima-adncp]
              Stenberg, M., "Autonomic Distributed Node Consensus
              Protocol", draft-stenberg-anima-adncp-00 (work in
              progress), March 2015.

   [RFC2205]  Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and
S.
              Jamin, "Resource ReSerVation Protocol (RSVP) -- Version
1
              Functional Specification", RFC 2205, DOI
10.17487/RFC2205,
              September 1997,
<http://www.rfc-editor.org/info/rfc2205>.

   [RFC2334]  Luciani, J., Armitage, G., Halpern, J., and N.
Doraswamy,
              "Server Cache Synchronization Protocol (SCSP)", RFC
2334,
              DOI 10.17487/RFC2334, April 1998,
              <http://www.rfc-editor.org/info/rfc2334>.

   [RFC2608]  Guttman, E., Perkins, C., Veizades, J., and M. Day,
              "Service Location Protocol, Version 2", RFC 2608,
              DOI 10.17487/RFC2608, June 1999,
              <http://www.rfc-editor.org/info/rfc2608>.

   [RFC2865]  Rigney, C., Willens, S., Rubens, A., and W. Simpson,
              "Remote Authentication Dial In User Service (RADIUS)",
              RFC 2865, DOI 10.17487/RFC2865, June 2000,
              <http://www.rfc-editor.org/info/rfc2865>.

   [RFC3209]  Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan,
V.,
              and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
              Tunnels", RFC 3209, DOI 10.17487/RFC3209, December
2001,
              <http://www.rfc-editor.org/info/rfc3209>.





Bormann, et al.           Expires June 18, 2017                [Page
53]

Internet-Draft                    GRASP                    December
2016


   [RFC3315]  Droms, R., Ed., Bound, J., Volz, B., Lemon, T.,
Perkins,
              C., and M. Carney, "Dynamic Host Configuration Protocol
              for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315,
July
              2003, <http://www.rfc-editor.org/info/rfc3315>.

   [RFC3416]  Presuhn, R., Ed., "Version 2 of the Protocol Operations
              for the Simple Network Management Protocol (SNMP)",
              STD 62, RFC 3416, DOI 10.17487/RFC3416, December 2002,
              <http://www.rfc-editor.org/info/rfc3416>.

   [RFC4861]  Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
              "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
              DOI 10.17487/RFC4861, September 2007,
              <http://www.rfc-editor.org/info/rfc4861>.

   [RFC5226]  Narten, T. and H. Alvestrand, "Guidelines for Writing
an
              IANA Considerations Section in RFCs", BCP 26, RFC 5226,
              DOI 10.17487/RFC5226, May 2008,
              <http://www.rfc-editor.org/info/rfc5226>.

   [RFC5971]  Schulzrinne, H. and R. Hancock, "GIST: General Internet
              Signalling Transport", RFC 5971, DOI 10.17487/RFC5971,
              October 2010, <http://www.rfc-editor.org/info/rfc5971>.

   [RFC6206]  Levis, P., Clausen, T., Hui, J., Gnawali, O., and J.
Ko,
              "The Trickle Algorithm", RFC 6206, DOI
10.17487/RFC6206,
              March 2011, <http://www.rfc-editor.org/info/rfc6206>.

   [RFC6241]  Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J.,
Ed.,
              and A. Bierman, Ed., "Network Configuration Protocol
              (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011,
              <http://www.rfc-editor.org/info/rfc6241>.

   [RFC6733]  Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
              Ed., "Diameter Base Protocol", RFC 6733,
              DOI 10.17487/RFC6733, October 2012,
              <http://www.rfc-editor.org/info/rfc6733>.

   [RFC6762]  Cheshire, S. and M. Krochmal, "Multicast DNS", RFC
6762,
              DOI 10.17487/RFC6762, February 2013,
              <http://www.rfc-editor.org/info/rfc6762>.

   [RFC6763]  Cheshire, S. and M. Krochmal, "DNS-Based Service
              Discovery", RFC 6763, DOI 10.17487/RFC6763, February
2013,
              <http://www.rfc-editor.org/info/rfc6763>.






Bormann, et al.           Expires June 18, 2017                [Page
54]

Internet-Draft                    GRASP                    December
2016


   [RFC6887]  Wing, D., Ed., Cheshire, S., Boucadair, M., Penno, R.,
and
              P. Selkirk, "Port Control Protocol (PCP)", RFC 6887,
              DOI 10.17487/RFC6887, April 2013,
              <http://www.rfc-editor.org/info/rfc6887>.

   [RFC7558]  Lynn, K., Cheshire, S., Blanchet, M., and D. Migault,
              "Requirements for Scalable DNS-Based Service Discovery
              (DNS-SD) / Multicast DNS (mDNS) Extensions", RFC 7558,
              DOI 10.17487/RFC7558, July 2015,
              <http://www.rfc-editor.org/info/rfc7558>.

   [RFC7575]  Behringer, M., Pritikin, M., Bjarnason, S., Clemm, A.,
              Carpenter, B., Jiang, S., and L. Ciavaglia, "Autonomic
              Networking: Definitions and Design Goals", RFC 7575,
              DOI 10.17487/RFC7575, June 2015,
              <http://www.rfc-editor.org/info/rfc7575>.

   [RFC7576]  Jiang, S., Carpenter, B., and M. Behringer, "General
Gap
              Analysis for Autonomic Networking", RFC 7576,
              DOI 10.17487/RFC7576, June 2015,
              <http://www.rfc-editor.org/info/rfc7576>.

   [RFC7787]  Stenberg, M. and S. Barth, "Distributed Node Consensus
              Protocol", RFC 7787, DOI 10.17487/RFC7787, April 2016,
              <http://www.rfc-editor.org/info/rfc7787>.

   [RFC7788]  Stenberg, M., Barth, S., and P. Pfister, "Home
Networking
              Control Protocol", RFC 7788, DOI 10.17487/RFC7788,
April
              2016, <http://www.rfc-editor.org/info/rfc7788>.

Appendix A.  Open Issues [RFC Editor: Please remove if empty]

   o  63.  Placeholder

Appendix B.  Closed Issues [RFC Editor: Please remove]

   o  1.  UDP vs TCP: For now, this specification suggests UDP and
TCP
      as message transport mechanisms.  This is not clarified yet. 
UDP
      is good for short conversations, is necessary for multicast
      discovery, and generally fits the discovery and divert
scenarios
      well.  However, it will cause problems with large messages. 
TCP
      is good for stable and long sessions, with a little bit of time
      consumption during the session establishment stage.  If
messages
      exceed a reasonable MTU, a TCP mode will be required in any
case.
      This question may be affected by the security discussion.

      RESOLVED by specifying UDP for short message and TCP for longer
      one.



Bormann, et al.           Expires June 18, 2017                [Page
55]

Internet-Draft                    GRASP                    December
2016


   o  2.  DTLS or TLS vs built-in security mechanism.  For now, this
      specification has chosen a PKI based built-in security
mechanism
      based on asymmetric cryptography.  However, (D)TLS might be
chosen
      as security solution to avoid duplication of effort.  It also
      allows essentially similar security for short messages over UDP
      and longer ones over TCP.  The implementation trade-offs are
      different.  The current approach requires expensive asymmetric
      cryptographic calculations for every message.  (D)TLS has
startup
      overheads but cheaper crypto per message.  DTLS is less mature
      than TLS.

      RESOLVED by specifying external security (ACP or (D)TLS).

   o  The following open issues applied only if the original security
      model was retained:

      *  2.1.  For replay protection, GRASP currently requires every
         participant to have an NTP-synchronized clock.  Is this OK
for
         low-end devices, and how does it work during device
         bootstrapping?  We could take the Timestamp out of signature
         option, to become an independent and OPTIONAL (or
RECOMMENDED)
         option.

      *  2.2.  The Signature Option states that this option could be
any
         place in a message.  Wouldn't it be better to specify a
         position (such as the end)?  That would be much simpler to
         implement.

      RESOLVED by changing security model.

   o  3.  DoS Attack Protection needs work.

      RESOLVED by adding text.

   o  4.  Should we consider preferring a text-based approach to
      discovery (after the initial discovery needed for
bootstrapping)?
      This could be a complementary mechanism for multicast based
      discovery, especially for a very large autonomic network.
      Centralized registration could be automatically deployed
      incrementally.  At the very first stage, the repository could
be
      empty; then it could be filled in by the objectives discovered
by
      different devices (for example using Dynamic DNS Update).  The
      more records are stored in the repository, the less the
multicast-
      based discovery is needed.  However, if we adopt such a
mechanism,
      there would be challenges: stateful solution, and security.

      RESOLVED for now by adding optional use of DNS-SD by ASAs.
      Subsequently removed by editors as irrelevant to GRASP istelf.



Bormann, et al.           Expires June 18, 2017                [Page
56]

Internet-Draft                    GRASP                    December
2016


   o  5.  Need to expand description of the minimum requirements for
the
      specification of an individual discovery, synchronization or
      negotiation objective.

      RESOLVED for now by extra wording.

   o  6.  Use case and protocol walkthrough.  A description of how a
      node starts up, performs discovery, and conducts negotiation
and
      synchronisation for a sample use case would help readers to
      understand the applicability of this specification.  Maybe it
      should be an artificial use case or maybe a simple real one,
based
      on a conceptual API.  However, the authors have not yet decided
      whether to have a separate document or have it in the protocol
      document.

      RESOLVED: recommend a separate document.

   o  7.  Cross-check against other ANIMA WG documents for
consistency
      and gaps.

      RESOLVED: Satisfied by WGLC.

   o  8.  Consideration of ADNCP proposal.

      RESOLVED by adding optional use of DNCP for flooding-type
      synchronization.

   o  9.  Clarify how a GDNP instance knows whether it is running
inside
      the ACP.  (Sheng)

      RESOLVED by improved text.

   o  10.  Clarify how a non-ACP GDNP instance initiates (D)TLS.
      (Sheng)

      RESOLVED by improved text and declaring DTLS out of scope for
this
      draft.

   o  11.  Clarify how UDP/TCP choice is made.  (Sheng) [Like DNS? -
      Brian]

      RESOLVED by improved text.

   o  12.  Justify that IP address within ACP or (D)TLS environment
is
      sufficient to prove AN identity; or explain how Device Identity
      Option is used.  (Sheng)





Bormann, et al.           Expires June 18, 2017                [Page
57]

Internet-Draft                    GRASP                    December
2016


      RESOLVED for now: we assume that all ASAs in a device are
trusted
      as soon as the device is trusted, so they share credentials. 
In
      that case the Device Identity Option is useless.  This needs to
be
      reviewed later.

   o  13.  Emphasise that negotiation/synchronization are independent
      from discovery, although the rapid discovery mode includes the
      first step of a negotiation/synchronization.  (Sheng)

      RESOLVED by improved text.

   o  14.  Do we need an unsolicited flooding mechanism for discovery
      (for discovery results that everyone needs), to reduce scaling
      impact of flooding discovery messages?  (Toerless)

      RESOLVED: Yes, added to requirements and solution.

   o  15.  Do we need flag bits in Objective Options to distinguish
      distinguish Synchronization and Negotiation "Request" or rapid
      mode "Discovery" messages?  (Bing)

      RESOLVED: yes, work on the API showed that these flags are
      essential.

   o  16.  (Related to issue 14).  Should we revive the "unsolicited
      Response" for flooding synchronisation data?  This has to be
done
      carefully due to the well-known issues with flooding, but it
could
      be useful, e.g. for Intent distribution, where DNCP doesn't
seem
      applicable.

      RESOLVED: Yes, see #14.

   o  17.  Ensure that the discovery mechanism is completely proof
      against loops and protected against duplicate responses.

      RESOLVED: Added loop count mechanism.

   o  18.  Discuss the handling of multiple valid discovery
responses.

      RESOLVED: Stated that the choice must be available to the ASA
but
      GRASP implementation should pick a default.

   o  19.  Should we use a text-oriented format such as JSON/CBOR
      instead of native binary TLV format?

      RESOLVED: Yes, changed to CBOR.





Bormann, et al.           Expires June 18, 2017                [Page
58]

Internet-Draft                    GRASP                    December
2016


   o  20.  Is the Divert option needed?  If a discovery response
      provides a valid IP address or FQDN, the recipient doesn't gain
      any extra knowledge from the Divert.  On the other hand, the
      presence of Divert informs the receiver that the target is off-
      link, which might be useful sometimes.

      RESOLVED: Decided to keep Divert option.

   o  21.  Rename the protocol as GRASP (GeneRic Autonomic Signaling
      Protocol)?

      RESOLVED: Yes, name changed.

   o  22.  Does discovery mechanism scale robustly as needed?  Need
hop
      limit on relaying?

      RESOLVED: Added hop limit.

   o  23.  Need more details on TTL for caching discovery responses.

      RESOLVED: Done.

   o  24.  Do we need "fast withdrawal" of discovery responses?

      RESOLVED: This doesn't seem necessary.  If an ASA exits or
stops
      supporting a given objective, peers will fail to start future
      sessions and will simply repeat discovery.

   o  25.  Does GDNP discovery meet the needs of multi-hop DNS-SD?

      RESOLVED: Decided not to consider this further as a GRASP
protocol
      issue.  GRASP objectives could embed DNS-SD formats if needed.

   o  26.  Add a URL type to the locator options (for security
bootstrap
      etc.)

      RESOLVED: Done, later renamed as URI.

   o  27.  Security of Flood multicasts (Section 3.5.6.1).

      RESOLVED: added text.

   o  28.  Does ACP support secure link-local multicast?

      RESOLVED by new text in the Security Considerations.

   o  29.  PEN is used to distinguish vendor options.  Would it be
      better to use a domain name?  Anything unique will do.



Bormann, et al.           Expires June 18, 2017                [Page
59]

Internet-Draft                    GRASP                    December
2016


      RESOLVED: Simplified this by removing PEN field and changing
      naming rules for objectives.

   o  30.  Does response to discovery require randomized delays to
      mitigate amplification attacks?

      RESOLVED: WG feedback is that it's unnecessary.

   o  31.  We have specified repeats for failed discovery etc.  Is
that
      sufficient to deal with sleeping nodes?

      RESOLVED: WG feedback is that it's unnecessary to say more.

   o  32.  We have one-to-one synchronization and flooding
      synchronization.  Do we also need selective flooding to a
subset
      of nodes?

      RESOLVED: This will be discussed as a protocol extension in a
      separate draft (draft-liu-anima-grasp-distribution).

   o  33.  Clarify if/when discovery needs to be repeated.

      RESOLVED: Done.

   o  34.  Clarify what is mandatory for running in ACP, expand
      discussion of security boundary when running with no ACP -
might
      rely on the local PKI infrastructure.

      RESOLVED: Done.

   o  35.  State that role-based authorization of ASAs is out of
scope
      for GRASP.  GRASP doesn't recognize/handle any "roles".

      RESOLVED: Done.

   o  36.  Reconsider CBOR definition for PEN syntax.  (
objective-name
      = text / [pen, text] ; pen = uint )

      RESOLVED: See issue 29.

   o  37.  Are URI locators really needed?

      RESOLVED: Yes, e.g. for security bootstrap discovery, but added
      note that addresses are the normal case (same for FQDN
locators).

   o  38.  Is Session ID sufficient to identify relayed responses?
      Isn't the originator's address needed too?




Bormann, et al.           Expires June 18, 2017                [Page
60]

Internet-Draft                    GRASP                    December
2016


      RESOLVED: Yes, this is needed for multicast messages and their
      responses.

   o  39.  Clarify that a node will contain one GRASP instance
      supporting multiple ASAs.

      RESOLVED: Done.

   o  40.  Add a "reason" code to the DECLINE option?

      RESOLVED: Done.

   o  41.  What happens if an ASA cannot conveniently use one of the
      GRASP mechanisms?  Do we (a) add a message type to GRASP, or
(b)
      simply pass the discovery results to the ASA so that it can
open
      its own socket?

      RESOLVED: Both would be possible, but (b) is preferred.

   o  42.  Do we need a feature whereby an ASA can bypass the ACP and
      use the data plane for efficiency/throughput?  This would
require
      discovery to return non-ACP addresses and would evade ACP
      security.

      RESOLVED: This is considered out of scope for GRASP, but a
comment
      has been added in security considerations.

   o  43.  Rapid mode synchronization and negotiation is currently
      limited to a single objective for simplicity of design and
      implementation.  A future consideration is to allow multiple
      objectives in rapid mode for greater efficiency.

      RESOLVED: This is considered out of scope for this version.

   o  44.  In requirement T9, the words that encryption "may not be
      required in all deployments" were removed.  Is that OK?.

      RESOLVED: No objections.

   o  45.  Device Identity Option is unused.  Can we remove it
      completely?.

      RESOLVED: No objections.  Done.

   o  46.  The 'initiator' field in DISCOVER, RESPONSE and FLOOD
      messages is intended to assist in loop prevention.  However, we
      also have the loop count for that.  Also, if we create a new
      Session ID each time a DISCOVER or FLOOD is relayed, that ID
can



Bormann, et al.           Expires June 18, 2017                [Page
61]

Internet-Draft                    GRASP                    December
2016


      be disambiguated by recipients.  It would be simpler to remove
the
      initiator from the messages, making parsing more uniform.  Is
that
      OK?

      RESOLVED: Yes. Done.

   o  47.  REQUEST is a dual purpose message (request negotiation or
      request synchronization).  Would it be better to split this
into
      two different messages (and adjust various message names
      accordingly)?

      RESOLVED: Yes. Done.

   o  48.  Should the Appendix "Capability Analysis of Current
      Protocols" be deleted before RFC publication?

      RESOLVED: No (per WG meeting at IETF 96).

   o  49.  Section 3.5.1 Should say more about signaling between two
      autonomic networks/domains.

      RESOLVED: Description of separate GRASP instance added.

   o  50.  Is Rapid mode limited to on-link only?  What happens if
first
      discovery responder does not support Rapid Mode?  Section
3.5.5,
      Section 3.5.6)

      RESOLVED: Not limited to on-link.  First responder wins.

   o  51.  Should flooded objectives have a time-to-live before they
are
      deleted from the flood cache?  And should they be tagged in the
      cache with their source locator?

      RESOLVED: TTL added to Flood (and Discovery Response) messages.
      Cached flooded objectives must be tagged with their originating
      ASA locator, and multiple copies must be kept if necessary.

   o  52.  Describe in detail what is allowed and disallowed in an
      insecure instance of GRASP.

      RESOLVED: Done.

   o  53.  Tune IANA Considerations to support early assignment
request.


   o  54.  Is there a highly unlikely race condition if two peers
      simultaneously choose the same Session ID and send each other
      simultaneous M_REQ_NEG messages?



Bormann, et al.           Expires June 18, 2017                [Page
62]

Internet-Draft                    GRASP                    December
2016


      RESOLVED: Yes. Enhanced text on Session ID generation, and
added
      precaution when receiving a Request message.

   o  55.  Could discovery be performed over TCP?

      RESOLVED: Unicast discovery added as an option.

   o  56.  Change Session-ID to 32 bits?

      RESOLVED: Done.

   o  57.  Add M_INVALID message?

      RESOLVED: Done.

   o  58.  Maximum message size?

      RESOLVED by specifying default maximum message size (2048
bytes).

   o  59.  Add F_NEG_DRY flag to specify a "dry run" objective?.

      RESOLVED: Done.

   o  60.  Change M_FLOOD syntax to associate a locator with each
      objective?

      RESOLVED: Done.

   o  61.  Is the SONN constrained instance really needed?

      RESOLVED: Retained but only as an option.

   o  62.  Is it helpful to tag descriptive text with message names
      (M_DISCOVER etc.)?

      RESOLVED: Yes, done in various parts of the text.

Appendix C.  Change log [RFC Editor: Please remove]

   draft-ietf-anima-grasp-09, 2016-12-15:

   Protocol change: Add F_NEG_DRY flag to specify a "dry run"
objective.

   Protocol change: Change M_FLOOD syntax to associate a locator with
   each objective.

   Concentrated mentions of TLS in one section, with all details out
of
   scope.



Bormann, et al.           Expires June 18, 2017                [Page
63]

Internet-Draft                    GRASP                    December
2016


   Clarified text around constrained instances of GRASP.

   Strengthened text restricting LL addresses in locator options.

   Clarified description of rapid mode processsing.

   Specified that cached discovery results should not be returned on
the
   same interface where they were learned.

   Shortened text in "High Level Design Choices"

   Dropped the word 'kernel' to avoid confusion with o/s kernel mode.

   Editorial improvements and clarifications.

   draft-ietf-anima-grasp-08, 2016-10-30:

   Protocol change: Added M_INVALID message.

   Protocol change: Increased Session ID space to 32 bits.

   Enhanced rules to avoid Session ID clashes.

   Corrected and completed description of timeouts for Request
messages.

   Improved wording about exponential backoff and DoS.

   Clarified that discovery relaying is not done by limited security
   instances.

   Corrected and expanded explanation of port used for Discovery
   Response.

   Noted that Discovery message could be sent unicast in special
cases.

   Added paragraph on extensibility.

   Specified default maximum message size.

   Added Appendix for sample messages.

   Added short protocol overview.

   Editorial fixes, including minor re-ordering for readability.

   draft-ietf-anima-grasp-07, 2016-09-13:

   Protocol change: Added TTL field to Flood message (issue 51).



Bormann, et al.           Expires June 18, 2017                [Page
64]

Internet-Draft                    GRASP                    December
2016


   Protocol change: Added Locator option to Flood message (issue 51).

   Protocol change: Added TTL field to Discovery Response message
   (corrollary to issue 51).

   Clarified details of rapid mode (issues 43 and 50).

   Description of inter-domain GRASP instance added (issue 49).

   Description of limited security GRASP instances added (issue 52).

   Strengthened advice to use TCP rather than UDP.

   Updated IANA considerations and text about well-known port usage
   (issue 53).

   Amended text about ASA authorization and roles to allow for
   overlapping ASAs.

   Added text recommending that Flood should be repeated
periodically.

   Editorial fixes.

   draft-ietf-anima-grasp-06, 2016-06-27:

   Added text on discovery cache timeouts.

   Noted that ASAs that are only initiators do not need to respond to
   discovery message.

   Added text on unexpected address changes.

   Added text on robust implementation.

   Clarifications and editorial fixes for numerous review comments

   Added open issues for some review comments.

   draft-ietf-anima-grasp-05, 2016-05-13:

   Noted in requirement T1 that it should be possible to implement
ASAs
   independently as user space programs.

   Protocol change: Added protocol number and port to discovery
   response.  Updated protocol description, CDDL and IANA
considerations
   accordingly.





Bormann, et al.           Expires June 18, 2017                [Page
65]

Internet-Draft                    GRASP                    December
2016


   Clarified that discovery and flood multicasts are handled by the
   GRASP core, not directly by ASAs.

   Clarified that a node may discover an objective without supporting
it
   for synchronization or negotiation.

   Added Implementation Status section.

   Added reference to SCSP.

   Editorial fixes.

   draft-ietf-anima-grasp-04, 2016-03-11:

   Protocol change: Restored initiator field in certain messages and
   adjusted relaying rules to provide complete loop detection.

   Updated IANA Considerations.

   draft-ietf-anima-grasp-03, 2016-02-24:

   Protocol change: Removed initiator field from certain messages and
   adjusted relaying requirement to simplify loop detection.  Also
   clarified narrative explanation of discovery relaying.

   Protocol change: Split Request message into two (Request
Negotiation
   and Request Synchronization) and updated other message names for
   clarity.

   Protocol change: Dropped unused Device ID option.

   Further clarified text on transport layer usage.

   New text about multicast insecurity in Security Considerations.

   Various other clarifications and editorial fixes, including moving
   some material to Appendix.

   draft-ietf-anima-grasp-02, 2016-01-13:

   Resolved numerous issues according to WG discussions.

   Renumbered requirements, added D9.

   Protocol change: only allow one objective in rapid mode.

   Protocol change: added optional error string to DECLINE option.




Bormann, et al.           Expires June 18, 2017                [Page
66]

Internet-Draft                    GRASP                    December
2016


   Protocol change: removed statement that seemed to say that a
Request
   not preceded by a Discovery should cause a Discovery response. 
That
   made no sense, because there is no way the initiator would know
where
   to send the Request.

   Protocol change: Removed PEN option from vendor objectives,
changed
   naming rule accordingly.

   Protocol change: Added FLOOD message to simplify coding.

   Protocol change: Added SYNCH message to simplify coding.

   Protocol change: Added initiator id to DISCOVER, RESPONSE and
FLOOD
   messages.  But also allowed the relay process for DISCOVER and
FLOOD
   to regenerate a Session ID.

   Protocol change: Require that discovered addresses must be global
   (except during bootstrap).

   Protocol change: Receiver of REQUEST message must close socket if
no
   ASA is listening for the objective.

   Protocol change: Simplified Waiting message.

   Protocol change: Added No Operation message.

   Renamed URL locator type as URI locator type.

   Updated CDDL definition.

   Various other clarifications and editorial fixes.

   draft-ietf-anima-grasp-01, 2015-10-09:

   Updated requirements after list discussion.

   Changed from TLV to CBOR format - many detailed changes, added co-
   author.

   Tightened up loop count and timeouts for various cases.

   Noted that GRASP does not provide transactional integrity.

   Various other clarifications and editorial fixes.

   draft-ietf-anima-grasp-00, 2015-08-14:

   File name and protocol name changed following WG adoption.



Bormann, et al.           Expires June 18, 2017                [Page
67]

Internet-Draft                    GRASP                    December
2016


   Added URL locator type.

   draft-carpenter-anima-gdn-protocol-04, 2015-06-21:

   Tuned wording around hierarchical structure.

   Changed "device" to "ASA" in many places.

   Reformulated requirements to be clear that the ASA is the main
   customer for signaling.

   Added requirement for flooding unsolicited synch, and added it to
   protocol spec.  Recognized DNCP as alternative for flooding synch
   data.

   Requirements clarified, expanded and rearranged following design
team
   discussion.

   Clarified that GDNP discovery must not be a prerequisite for GDNP
   negotiation or synchronization (resolved issue 13).

   Specified flag bits for objective options (resolved issue 15).

   Clarified usage of ACP vs TLS/DTLS and TCP vs UDP (resolved issues
   9,10,11).

   Updated DNCP description from latest DNCP draft.

   Editorial improvements.

   draft-carpenter-anima-gdn-protocol-03, 2015-04-20:

   Removed intrinsic security, required external security

   Format changes to allow DNCP co-existence

   Recognized DNS-SD as alternative discovery method.

   Editorial improvements

   draft-carpenter-anima-gdn-protocol-02, 2015-02-19:

   Tuned requirements to clarify scope,

   Clarified relationship between types of objective,

   Clarified that objectives may be simple values or complex data
   structures,



Bormann, et al.           Expires June 18, 2017                [Page
68]

Internet-Draft                    GRASP                    December
2016


   Improved description of objective options,

   Added loop-avoidance mechanisms (loop count and default timeout,
   limitations on discovery relaying and on unsolicited responses),

   Allow multiple discovery objectives in one response,

   Provided for missing or multiple discovery responses,

   Indicated how modes such as "dry run" should be supported,

   Minor editorial and technical corrections and clarifications,

   Reorganized future work list.

   draft-carpenter-anima-gdn-protocol-01, restructured the logical
flow
   of the document, updated to describe synchronization completely,
add
   unsolicited responses, numerous corrections and clarifications,
   expanded future work list, 2015-01-06.

   draft-carpenter-anima-gdn-protocol-00, combination of draft-jiang-
   config-negotiation-ps-03 and
draft-jiang-config-negotiation-protocol-
   02, 2014-10-08.

Appendix D.  Example Message Formats

   For readers unfamiliar with CBOR, this appendix shows a number of
   example GRASP messages conforming to the CDDL syntax given in
   Section 6.  Each message is shown three times in the following
   formats:

   1.  CBOR diagnostic notation.

   2.  Similar, but showing the names of the constants.  (Details of
the
       flag bit encoding are omitted.)

   3.  Hexadecimal version of the CBOR wire format.

   Long lines are split for display purposes only.

D.1.  Discovery Example

   The initiator (2001:db8:f000:baaa:28cc:dc4c:9703:6781) multicasts
a
   discovery message looking for objective EX1:







Bormann, et al.           Expires June 18, 2017                [Page
69]

Internet-Draft                    GRASP                    December
2016


   [1, 13948744, h'20010db8f000baaa28ccdc4c97036781', ["EX1", 5, 2,
0]]
   [M_DISCOVERY, 13948744, h'20010db8f000baaa28ccdc4c97036781',
                 ["EX1", F_SYNCH_bits, 2, 0]]
  
h'84011a00d4d7485020010db8f000baaa28ccdc4c970367818463455831050200'

   A peer (2001:0db8:f000:baaa:f000:baaa:f000:baaa) responds with a
   locator:

   [2, 13948744, h'20010db8f000baaa28ccdc4c97036781', 60000,
                 [103, h'20010db8f000baaaf000baaaf000baaa', 6,
49443]]
   [M_RESPONSE, 13948744, h'20010db8f000baaa28ccdc4c97036781', 60000,
                 [O_IPv6_LOCATOR,
h'20010db8f000baaaf000baaaf000baaa',
                  IPPROTO_TCP, 49443]]
   h'85021a00d4d7485020010db8f000baaa28ccdc4c9703678119ea6084186750
     20010db8f000baaaf000baaaf000baaa0619c123'

D.2.  Flood Example

   The initiator multicasts a flood message.  The single objective has
a
   null locator.  There is no response:

[9, 3504974, h'20010db8f000baaa28ccdc4c97036781', 10000,
             [["EX1", 5, 2, ["Example 1 value=", 100]],[] ] ]
[M_FLOOD, 3504974, h'20010db8f000baaa28ccdc4c97036781', 10000,
             [["EX1", F_SYNCH_bits, 2, ["Example 1 value=", 100]],[] ]
]
h'86091a00357b4e5020010db8f000baaa28ccdc4c97036781192710
  828463455831050282704578616d706c6520312076616c75653d186480'

D.3.  Synchronization Example

   Following successful discovery of objective EX2, the initiator
   unicasts a request:

   [4, 4038926, ["EX2", 5, 5, 0]]
   [M_REQ_SYN, 4038926, ["EX2", F_SYNCH_bits, 5, 0]]
   h'83041a003da10e8463455832050500'

   The peer responds with a value:

 [8, 4038926, ["EX2", 5, 5, ["Example 2 value=", 200]]]
 [M_SYNCH, 4038926, ["EX2", F_SYNCH_bits, 5, ["Example 2 value=",
200]]]

h'83081a003da10e8463455832050582704578616d706c6520322076616c75653d18c8'

D.4.  Simple Negotiation Example

   Following successful discovery of objective EX3, the initiator
   unicasts a request:




Bormann, et al.           Expires June 18, 2017                [Page
70]

Internet-Draft                    GRASP                    December
2016


   [3, 802813, ["EX3", 3, 6, ["NZD", 47]]]
   [M_REQ_NEG, 802813, ["EX3", F_NEG_bits, 6, ["NZD", 47]]]
   h'83031a000c3ffd8463455833030682634e5a44182f'

   The peer responds with immediate acceptance.  Note that no
objective
   is needed, because the initiator's request was accepted without
   change:

   [6, 802813, [101]]
   [M_END , 802813, [O_ACCEPT]]
   h'83061a000c3ffd811865'

D.5.  Complete Negotiation Example

   Again the initiator unicasts a request:

   [3, 13767778, ["EX3", 3, 6, ["NZD", 410]]]
   [M_REQ_NEG, 13767778, ["EX3", F_NEG_bits, 6, ["NZD", 410]]]
   h'83031a00d214628463455833030682634e5a4419019a'

   The responder starts to negotiate (making an offer):

   [5, 13767778, ["EX3", 3, 6, ["NZD", 80]]]
   [M_NEGOTIATE, 13767778, ["EX3", F_NEG_bits, 6, ["NZD", 80]]]
   h'83051a00d214628463455833030682634e5a441850'

   The initiator continues to negotiate (reducing its request, and
note
   that the loop count is decremented):

   [5, 13767778, ["EX3", 3, 5, ["NZD", 307]]]
   [M_NEGOTIATE, 13767778, ["EX3", F_NEG_bits, 5, ["NZD", 307]]]
   h'83051a00d214628463455833030582634e5a44190133'

   The responder asks for more time:

   [7, 13767778, 34965]
   [M_WAIT, 13767778, 34965]
   h'83071a00d21462198895'

   The responder continues to negotiate (increasing its offer):

   [5, 13767778, ["EX3", 3, 4, ["NZD", 120]]]
   [M_NEGOTIATE, 13767778, ["EX3", F_NEG_bits, 4, ["NZD", 120]]]
   h'83051a00d214628463455833030482634e5a441878'

   The initiator continues to negotiate (reducing its request):





Bormann, et al.           Expires June 18, 2017                [Page
71]

Internet-Draft                    GRASP                    December
2016


   [5, 13767778, ["EX3", 3, 3, ["NZD", 246]]]
   [M_NEGOTIATE, 13767778, ["EX3", F_NEG_bits, 3, ["NZD", 246]]]
   h'83051a00d214628463455833030382634e5a4418f6'

   The responder refuses to negotiate further:

   [6, 13767778, [102, "Insufficient funds"]]
   [M_END , 13767778, [O_DECLINE, "Insufficient funds"]]
   h'83061a00d2146282186672496e73756666696369656e742066756e6473'

   This negotiation has failed.  If either side had sent [M_END,
   13767778, [O_ACCEPT]] it would have succeeded, converging on the
   objective value in the preceding M_NEGOTIATE.  Note that apart
from
   the initial M_REQ_NEG, the process is symmetrical.

Appendix E.  Capability Analysis of Current Protocols

   This appendix discusses various existing protocols with properties
   related to the requirements described in Section 2.  The purpose
is
   to evaluate whether any existing protocol, or a simple combination
of
   existing protocols, can meet those requirements.

   Numerous protocols include some form of discovery, but these all
   appear to be very specific in their applicability.  Service
Location
   Protocol (SLP) [RFC2608] provides service discovery for managed
   networks, but requires configuration of its own servers.  DNS-SD
   [RFC6763] combined with mDNS [RFC6762] provides service discovery
for
   small networks with a single link layer.  [RFC7558] aims to extend
   this to larger autonomous networks but this is not yet
standardized.
   However, both SLP and DNS-SD appear to target primarily
application
   layer services, not the layer 2 and 3 objectives relevant to basic
   network configuration.  Both SLP and DNS-SD are text-based
protocols.

   Routing protocols are mainly one-way information announcements. 
The
   receiver makes independent decisions based on the received
   information and there is no direct feedback information to the
   announcing peer.  This remains true even though the protocol is
used
   in both directions between peer routers; there is state
   synchronization, but no negotiation, and each peer runs its route
   calculations independently.

   Simple Network Management Protocol (SNMP) [RFC3416] uses a
command/
   response model not well suited for peer negotiation.  Network
   Configuration Protocol (NETCONF) [RFC6241] uses an RPC model that
   does allow positive or negative responses from the target system,
but
   this is still not adequate for negotiation.





Bormann, et al.           Expires June 18, 2017                [Page
72]

Internet-Draft                    GRASP                    December
2016


   There are various existing protocols that have elementary
negotiation
   abilities, such as Dynamic Host Configuration Protocol for IPv6
   (DHCPv6) [RFC3315], Neighbor Discovery (ND) [RFC4861], Port
Control
   Protocol (PCP) [RFC6887], Remote Authentication Dial In User
Service
   (RADIUS) [RFC2865], Diameter [RFC6733], etc.  Most of them are
   configuration or management protocols.  However, they either
provide
   only a simple request/response model in a master/slave context or
   very limited negotiation abilities.

   There are some signaling protocols with an element of negotiation.
   For example Resource ReSerVation Protocol (RSVP) [RFC2205] was
   designed for negotiating quality of service parameters along the
path
   of a unicast or multicast flow.  RSVP is a very specialised
protocol
   aimed at end-to-end flows.  However, it has some flexibility,
having
   been extended for MPLS label distribution [RFC3209].  A more
generic
   design is General Internet Signalling Transport (GIST) [RFC5971],
but
   it is complex, tries to solve many problems, and is also aimed at
   per-flow signaling across many hops rather than at
device-to-device
   signaling.  However, we cannot completely exclude extended RSVP or
   GIST as a synchronization and negotiation protocol.  They do not
   appear to be directly useable for peer discovery.

   We now consider two protocols that are works in progress at the
time
   of this writing.  Firstly, RESTCONF [I-D.ietf-netconf-restconf] is
a
   protocol intended to convey NETCONF information expressed in the
YANG
   language via HTTP, including the ability to transit HTML
   intermediaries.  While this is a powerful approach in the context
of
   centralised configuration of a complex network, it is not well
   adapted to efficient interactive negotiation between peer devices,
   especially simple ones that might not include YANG processing
   already.

   Secondly, we consider Distributed Node Consensus Protocol (DNCP)
   [RFC7787].  This is defined as a generic form of state
   synchronization protocol, with a proposed usage profile being the
   Home Networking Control Protocol (HNCP) [RFC7788] for configuring
   Homenet routers.  A specific application of DNCP for autonomic
   networking was proposed in [I-D.stenberg-anima-adncp].

   DNCP "is designed to provide a way for each participating node to
   publish a set of TLV (Type-Length-Value) tuples, and to provide a
   shared and common view about the data published... DNCP is most
   suitable for data that changes only infrequently... If constant
rapid
   state changes are needed, the preferable choice is to use an
   additional point-to-point channel..."

   Specific features of DNCP include:




Bormann, et al.           Expires June 18, 2017                [Page
73]

Internet-Draft                    GRASP                    December
2016


   o  Every participating node has a unique node identifier.

   o  DNCP messages are encoded as a sequence of TLV objects, sent
over
      unicast UDP or TCP, with or without (D)TLS security.

   o  Multicast is used only for discovery of DNCP neighbors when
lower
      security is acceptable.

   o  Synchronization of state is maintained by a flooding process
using
      the Trickle algorithm.  There is no bilateral synchronization
or
      negotiation capability.

   o  The HNCP profile of DNCP is designed to operate between
directly
      connected neighbors on a shared link using UDP and link-local
IPv6
      addresses.

   DNCP does not meet the needs of a general negotiation protocol,
   because it is designed specifically for flooding synchronization.
   Also, in its HNCP profile it is limited to link-local messages and
to
   IPv6.  However, at the minimum it is a very interesting test case
for
   this style of interaction between devices without needing a
central
   authority, and it is a proven method of network-wide state
   synchronization by flooding.

   The Server Cache Synchronization Protocol (SCSP) [RFC2334] also
   describes a method for cache synchronization and cache replication
   among a group of nodes.

   A proposal was made some years ago for an IP based Generic Control
   Protocol (IGCP) [I-D.chaparadza-intarea-igcp].  This was aimed at
   information exchange and negotiation but not directly at peer
   discovery.  However, it has many points in common with the present
   work.

   None of the above solutions appears to completely meet the needs
of
   generic discovery, state synchronization and negotiation in a
single
   solution.  Many of the protocols assume that they are working in a
   traditional top-down or north-south scenario, rather than a fluid
   peer-to-peer scenario.  Most of them are specialized in one way or
   another.  As a result, we have not identified a combination of
   existing protocols that meets the requirements in Section 2. 
Also,
   we have not identified a path by which one of the existing
protocols
   could be extended to meet the requirements.








Bormann, et al.           Expires June 18, 2017                [Page
74]

Internet-Draft                    GRASP                    December
2016


Authors' Addresses

   Carsten Bormann
   Universitaet Bremen TZI
   Postfach 330440
   D-28359 Bremen
   Germany

   Email: cabo@tzi.org


   Brian Carpenter (editor)
   Department of Computer Science
   University of Auckland
   PB 92019
   Auckland  1142
   New Zealand

   Email: brian.e.carpenter@gmail.com


   Bing Liu (editor)
   Huawei Technologies Co., Ltd
   Q14, Huawei Campus
   No.156 Beiqing Road
   Hai-Dian District, Beijing  100095
   P.R. China

   Email: leo.liubing@huawei.com






















Bormann, et al.           Expires June 18, 2017                [Page
75]



From nobody Mon Feb 13 13:08:11 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 69141129526; Mon, 13 Feb 2017 13:08:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-6man-rfc4291bis-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:08:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HYH8jjqfFl4bayAITI3dWxs410M>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:08:09 -0000

Reviewer: Robert Sparks
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc4291bis-07
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-03-02

Summary:

I have three small points for the group to consider:

1) In editing for this bis document, one bit of text was lost. 
RFC4291 said this in its section 2.4.5:
"Global Unicast addresses that start with
 binary 000 have no such constraint on the size or structure of the
 interface ID field."
Without it, the various places remaining the the document that say
things like "except those that start with the binary value 0000"
such as that appearing in section 2.4 of _this_ document leave
the reason behind the exception a mystery.

2) At the point in the text where the modified EUI-64 format
interface
identifier text was moved to the appendix, this document notes that 
these derived interface identifiers are no longer recommended (end of
2.4.1). Consider repeating that at the first line of the new Appendix
A.

3) Appendix B looks like something groups normally ask the RFC Editor
to
delete. If that was your intent, please add instructions to the RFC
Editor
so they don't have to ask. If you planned to leave it, a summary of
the
changes rather than a chronolog of what draft version changes were
made
in would be much more useful to future readers. (Such a summary would
be welcome in any case.)






From nobody Mon Feb 13 13:10:13 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A01C41298C6; Mon, 13 Feb 2017 13:10:11 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 y_t-88jS3QY6; Mon, 13 Feb 2017 13:10:10 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 61B6D129584; Mon, 13 Feb 2017 13:10:10 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1DLA9PG049421 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 13 Feb 2017 15:10:09 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc4291bis-07
To: gen-art@ietf.org
References: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <f093a040-6b11-2985-9256-877f1675adea@nostrum.com>
Date: Mon, 13 Feb 2017 15:10:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148702008942.25043.12909317206946516033.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fDEHTWgzjkx-uAexJ1rLbRakKV4>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:10:11 -0000

And the tracker caught this, but to be complete in the archives, the 
Summary should have said
"Ready for publication as an Internet Standard but with nits that should 
be considered before proceeding"


On 2/13/17 3:08 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-6man-rfc4291bis-07
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-03-01
> IESG Telechat date: 2017-03-02
>
> Summary:

>
> I have three small points for the group to consider:
>
> 1) In editing for this bis document, one bit of text was lost.
> RFC4291 said this in its section 2.4.5:
> "Global Unicast addresses that start with
>   binary 000 have no such constraint on the size or structure of the
>   interface ID field."
> Without it, the various places remaining the the document that say
> things like "except those that start with the binary value 0000"
> such as that appearing in section 2.4 of _this_ document leave
> the reason behind the exception a mystery.
>
> 2) At the point in the text where the modified EUI-64 format
> interface
> identifier text was moved to the appendix, this document notes that
> these derived interface identifiers are no longer recommended (end of
> 2.4.1). Consider repeating that at the first line of the new Appendix
> A.
>
> 3) Appendix B looks like something groups normally ask the RFC Editor
> to
> delete. If that was your intent, please add instructions to the RFC
> Editor
> so they don't have to ask. If you planned to leave it, a summary of
> the
> changes rather than a chronolog of what draft version changes were
> made
> in would be much more useful to future readers. (Such a summary would
> be welcome in any case.)
>
>
>
>
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Mon Feb 13 13:23:45 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ADA12958B for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 13:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5R2-RwtdAai3 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 13:23:42 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 05947129957 for <ietf@ietf.org>; Mon, 13 Feb 2017 13:23:41 -0800 (PST)
X-Halon-ID: aa1a1d32-f232-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Mon, 13 Feb 2017 22:23:29 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Bernard Aboba <bernard.aboba@gmail.com>, slim@ietf.org, ietf@ietf.org
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <64c8d9d7-9df8-023e-6d47-4807cc0e30b7@omnitor.se>
Date: Mon, 13 Feb 2017 22:23:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------C46E57F1D025166BA2EA8432"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cuI64nWIT4pHoXmQViCjnq_80Jw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:23:45 -0000

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

Bernard,

I just issued comments where I also included the "silly states" topic 
with similar views as yours.


Den 2017-02-13 kl. 20:06, skrev Bernard Aboba:
> Looking over Section 5.4, it seems to me that the title "Silly States" 
> may not be appropriate, because it mixes discussion of combinations of 
> media and language that have an "undefined" meaning with combinations 
> for which normative guidance can be provided  So rather than having a 
> single "Silly States" section, perhaps we can have a section on 
> "Undefined States" (for those combinations which have an undefined 
> meaning) provide normative guidance on defined combinations elsewhere.
>
>
>       5.4
>       <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4>.
>       Silly States
>
>
>
>     It is possible to specify a "silly state" where the language
>     specified does not make sense for the media type, such as specifying
>     a signed language for an audio media stream.
>     An offer MUST NOT be created where the language does not make sense
>     for the media type.  If such an offer is received, the receiver MAY
>     reject the media, ignore the language specified, or attempt to
>     interpret the intent (e.g., if American Sign Language is specified
>     for an audio media stream, this might be interpreted as a desire to
>     use spoken English).
>
>     A spoken language tag for a video stream in conjunction with an audio
>     stream with the same language might indicate a request for
>     supplemental video to see the speaker.
> [BA] Rather than using terms like "might" for combinations that could have a
> defined meaning, I would like to see the specification provide normative
> language on these use cases. In particular, I would like the specification to describe:
> a. What it means when a spoken language tag is included for a video stream.
> Is this to be interpreted as a request for captioning?
> b. What it means when a signed language tag is included for an audio stream.
> Is the meaning of this "undefined" and if so, should it be ignored?
> c. What it means when a signed language tag is included for a text stream.
> If some of these scenarios are not defined, the specification can say
> "this combination does not have a defined meaning" or something like that.
See my recent comments for more views. I support the idea to be 
normative and specific when possible.
A complication is that there is no difference between language tags for 
written and spoken language.

So we have the following possible combinations and interpretations of 
"silly states"

1. Spoken/written tag in video media, can mean to see a speaking person, 
or to provide captions overlayed on video.
With some hesitation I suggest to let it mean to see a speaking person. 
The draft adds a requirement to have the same language in the audio 
stream in the same direction to have that interpretation. Should that 
mean that if there is another language in the audio stream, then the 
spoken/written tag in the video stream should mean captions in the 
specified language? That sounds useful for some cases, but complex to 
interpret and unfair to the users who would benefit from captions in the 
same language as in audio.
Summary: I think we had better to use the interpretation to see a 
speaking person regardless of what language is indicated for audio.

2. Signed language tag in audio media, can mean audio from a signing 
person. That could be anything between near silence and spoken words 
corresponding to the signed signs as far as feasible. This is usually 
seen as disturbing to sign language users but it exists, e.g. when one 
erson needs to communicate with both hearing and deaf persons 
simultaneously. There are also variants of signing, called sign 
supported language, with signs expressed with spoken language word order 
and grammar. That can more easily be combined with spoken language, but 
would more likely be indicated by spoken language tag in audio media.
Summary: I am inclined to let signed language tag in audio media mean 
audio from the signing person and possibly used for the rare cases when 
it has some relevance for language communication.

3. Sign language tag in text media. There are some ways to represent 
sign language in various kinds of symbol or text representation. Some 
are represented in Unicode. One is a system called Sign Writing. Some 
fingerspelling methods also have fonts corresponding to characters in 
code pages. There is also an informal way to write manuscripts for 
signing in words with capitals approximately corresponding to signs, 
often with some notation added for unique sign language ways of 
expression that has no direct correspondance to words. None of these 
systems above are common in real-time conversation, but I have seen 
examples of such use.
Summary: I think we can leave freedom here and just specify that a sign 
language tag in text media means some representation of sign language or 
a corresponding fingerspelling system in text media.

If these conclusions are accepted, we can formulate modified text. Note 
that the case with spoken/written language tag in video media is 
mentioned in two places in the draft.

Regards
Gunnar

>
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


--------------C46E57F1D025166BA2EA8432
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Bernard,</p>
    <p>I just issued comments where I also included the "silly states"
      topic with similar views as yours.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">Den 2017-02-13 kl. 20:06, skrev Bernard
      Aboba:<br>
    </div>
    <blockquote
cite="mid:CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com"
      type="cite">
      <div dir="ltr"><span class="gmail-im" style="font-size:12.8px">
          <div>Looking over Section 5.4, it seems to me that the title
            "Silly States" may not be appropriate, because it mixes
            discussion of combinations<span style="font-size:12.8px"> of
              media and language that have an "undefined" meaning with
              combinations </span><span style="font-size:12.8px">for
              which normative guidance can be provided  So rather than
              having a single "Silly States" section, perhaps we can
              have a section on "Undefined States" (for those
              combinations which have an undefined meaning) provide
              normative guidance on defined combinations elsewhere.</span></div>
          <div><br>
          </div>
          <div>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class="gmail-h3" style="line-height:0pt;display:inline;font-size:1em;font-weight:bold"><h3 style="line-height:0pt;display:inline;font-size:1em"><a moz-do-not-send="true" class="gmail-selflink" name="section-5.4" href="https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4" style="color:black;text-decoration:none">5.4</a>.  Silly States</h3></span>

   It is possible to specify a "silly state" where the language
   specified does not make sense for the media type, such as specifying
   a signed language for an audio media stream.</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   An offer MUST NOT be created where the language does not make sense
   for the media type.  If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent (e.g., if American Sign Language is specified
   for an audio media stream, this might be interpreted as a desire to
   use spoken English).

   A spoken language tag for a video stream in conjunction with an audio
   stream with the same language might indicate a request for
   supplemental video to see the speaker.</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">[BA] Rather than using terms like "might" for combinations that could have a</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">defined meaning, I would like to see the specification provide normative </pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">language on these use cases. In particular, I would like the specification to describe: </pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">a. What it means when a spoken language tag is included for a video stream. </pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is this to be interpreted as a request for captioning?</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">b. What it means when a signed language tag is included for an audio stream.</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is the meaning of this "undefined" and if so, should it be ignored?</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">c. What it means when a signed language tag is included for a text stream.</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">If some of these scenarios are not defined, the specification can say</pre>
            <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">"this combination does not have a defined meaning" or something like that.</pre>
          </div>
        </span></div>
    </blockquote>
    See my recent comments for more views. I support the idea to be
    normative and specific when possible.<br>
    A complication is that there is no difference between language tags
    for written and spoken language. <br>
    <br>
    So we have the following possible combinations and interpretations
    of "silly states"<br>
    <br>
    1. Spoken/written tag in video media, can mean to see a speaking
    person, or to provide captions overlayed on video.<br>
    With some hesitation I suggest to let it mean to see a speaking
    person. The draft adds a requirement to have the same language in
    the audio stream in the same direction to have that interpretation. 
    Should that mean that if there is another language in the audio
    stream, then the spoken/written tag in the video stream should mean
    captions in the specified language? That sounds useful for some
    cases, but complex to interpret and unfair to the users who would
    benefit from captions in the same language as in audio. <br>
    Summary: I think we had better to use the interpretation to see a
    speaking person regardless of what language is indicated for audio.<br>
    <br>
    2. Signed language tag in audio media, can mean audio from a signing
    person. That could be anything between near silence and spoken words
    corresponding to the signed signs as far as feasible. This is
    usually seen as disturbing to sign language users but it exists,
    e.g. when one erson needs to communicate with both hearing and deaf
    persons simultaneously. There are also variants of signing, called
    sign supported language, with signs expressed with spoken language
    word order and grammar. That can more easily be combined with spoken
    language, but would more likely be indicated by spoken language tag
    in audio media.<br>
    Summary: I am inclined to let signed language tag in audio media
    mean audio from the signing person and possibly used for the rare
    cases when it has some relevance for language communication. <br>
    <br>
    3. Sign language tag in text media. There are some ways to represent
    sign language in various kinds of symbol or text representation.
    Some are represented in Unicode. One is a system called Sign
    Writing. Some fingerspelling methods also have fonts corresponding
    to characters in code pages. There is also an informal way to write
    manuscripts for signing in words with capitals approximately
    corresponding to signs, often with some notation added for unique
    sign language ways of expression that has no direct correspondance
    to words. None of these systems above are common in real-time
    conversation, but I have seen examples of such use.<br>
    Summary: I think we can leave freedom here and just specify that a
    sign language tag in text media means some representation of sign
    language or a corresponding fingerspelling system in text media. <br>
         <br>
    If these conclusions are accepted, we can formulate modified text.
    Note that the case with spoken/written language tag in video media
    is mentioned in two places in the draft.<br>
    <br>
    Regards<br>
    Gunnar<br>
     <br>
    <blockquote
cite="mid:CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com"
      type="cite">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
SLIM mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SLIM@ietf.org">SLIM@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/slim">https://www.ietf.org/mailman/listinfo/slim</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
-----------------------------------------
Gunnar Hellström
Omnitor
<a class="moz-txt-link-abbreviated" href="mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</a>
+46 708 204 288</pre>
  </body>
</html>

--------------C46E57F1D025166BA2EA8432--


From nobody Mon Feb 13 13:29:09 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A9384129959; Mon, 13 Feb 2017 13:29:08 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <secdir@ietf.org>
Subject: Review of draft-ietf-grow-mrt-add-paths-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702134865.24993.7015216971422780095.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:29:08 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XxDYdPZxwiGYOAHb-ri7dO5r6IA>
Cc: draft-ietf-grow-mrt-add-paths.all@ietf.org, grow@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:29:08 -0000

Reviewer: Robert Sparks
Review result: Ready

I have reviewed this document as part of the security directorate's
ongoing effort to review all IETF documents being processed by the
IESG.  These comments were written primarily for the benefit of the
security area directors.  Document editors and WG chairs should treat
these comments just like any other last call comments.

Document : draft-ietf-grow-mrt-add-paths-03

Summary: Ready for publication as Proposed Standard

This document simply carries an extension to BGP forward into this
routing
information export format. It notes in its security consideration
section
that including the information the BGP extension allows to be
conveyed
increases the detail of the network path information exposed to any 
recipient (intended or otherwise). I agree that it adds no further new

security considerations.


From nobody Mon Feb 13 13:39:38 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84357129444; Mon, 13 Feb 2017 13:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HHvQ83ApLgoN; Mon, 13 Feb 2017 13:39:33 -0800 (PST)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (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 89F7E129955; Mon, 13 Feb 2017 13:39:33 -0800 (PST)
Received: by mail-qk0-x242.google.com with SMTP id e1so16805367qkh.1; Mon, 13 Feb 2017 13:39:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=vbKmHyjfhfVWXR1qM6IoYIcwA4yHzG4Valx0vJ8e01g=; b=uhdPn+Gkx0p0Rc6ZDBBI842zxJjxWocLxkYTtgdea7ZymHRgyA4LuZmmqFuw19dcvh ESTZE55/wuN5kPx3BmRWNXz1tq+f/3/Z0BUs4E9As6/2Up8kiPmxXgiQzdrKbzA2RNr4 zVgojDWN/UCWp/tOJkM/J892FVodM1+UOu4bUof+ylZwiQUq0neGiTH5A0JbLEfNbTVQ DekXWsQ/Oc8ob/YsljlJhkud3leMHGEHwHxogDnsDwxXlSDS5+Fy8C62bBh3yu3zGiDl KOaq04tRZzVHg/n+1EX1qVq64kbb4DCFbqRfggrK5yBEQykrR53xqubnB/iHTdUBFeas Grpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=vbKmHyjfhfVWXR1qM6IoYIcwA4yHzG4Valx0vJ8e01g=; b=Ne46EdHyF44xQ/ymevzaCJKIblnLoPUavqqxkjU6ZBTqhJh10IE6nnXo7FgnrNOT8S xBa5O1d7FXaHA514nmXG4IVLvD0ubQUKlEGSXeaAjy/Ung/KXsTi4ZTMsKBisHUfxUhF 5Vuw9m67vikEw6xpTnZi3lGGEh+PR+W2ArHSuhPt5HDJ8/xWlvCcNS+MUZuyzk2CsxjL GTFjmbKv05w0VPBYbPeUJa24wyqMhv/Snhh+sDsYegWkdUlKkY83elgOCviTIwNHvIWW 716l8TFGoTMsKGp9591mf+BRQwDVLDPD7juo2p0LTiMEQwEgX43X+Q19nSV0DODMsPio UA5A==
X-Gm-Message-State: AMke39kEyLzsRuTHxtRtJGMsE2dbL4xa7cMEEXOEZvz9FI9nF06fSahnmxgxZEXr5zACbg==
X-Received: by 10.55.195.148 with SMTP id r20mr24166467qkl.45.1487021972474; Mon, 13 Feb 2017 13:39:32 -0800 (PST)
Received: from [172.19.33.129] ([2601:184:4980:a321:881a:2ae6:4859:c421]) by smtp.gmail.com with ESMTPSA id d77sm6582338qkc.54.2017.02.13.13.39.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 13:39:31 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: Bad Attitude Pecha Kucha in Chicago
Date: Mon, 13 Feb 2017 16:39:30 -0500
Message-ID: <5A87EA52-FE48-4327-9638-793741EA623F@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_61B4FFC6-5E84-4088-BAC6-DEBC816AC5EA_="
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mJNJnZ487WefizP94Kz3UgWDnBM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:39:35 -0000

--=_MailMate_61B4FFC6-5E84-4088-BAC6-DEBC816AC5EA_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

This is a heads-up that I=E2=80=99m planning to arrange for another Pecha=
Kucha =

event at IETF-98 in Chicago.

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin and Seoul PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_61B4FFC6-5E84-4088-BAC6-DEBC816AC5EA_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">This is a heads-up that I=E2=80=99m planning to arrange f=
or another PechaKucha event at IETF-98 in Chicago.</p>

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).<br></li=
>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>]. </li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_61B4FFC6-5E84-4088-BAC6-DEBC816AC5EA_=--


From nobody Mon Feb 13 13:42:30 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4643A129954; Mon, 13 Feb 2017 13:42:29 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-leiba-rfc2119-update-01
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:42:29 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r4hz9Qz3hOLOPNJzJ2Cq7Xi5jOo>
Cc: draft-leiba-rfc2119-update.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:42:29 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-leiba-rfc2119-update-01
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-03-09
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as part of BCP 14.

I personally find the first bullet in the NEW section to be chatty,
and think it could be reduced while strengthening the message, but
enough eyes have been on this that I don't object to it going through
as is.

Major issues:

Minor issues:

Nits/editorial comments: 



From nobody Mon Feb 13 13:51:42 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 28EC512998E; Mon, 13 Feb 2017 13:51:40 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-mpls-residence-time-13
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 13:51:40 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kK1bw7Qb2I-G0DdGA2dBY9v0IrA>
Cc: mpls@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:51:40 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-residence-time-13
Reviewer: Robert Sparks
Review Date: 2017-02-13
IETF LC End Date: 2017-01-17
IESG Telechat date: 2017-03-02

Summary: Ready for publication as PS

Thanks for addressing my comments.
(I still think some discussion about taking arrival and departure time
measurements would be helpful, even if it only said "do it
consistently so you don't indicate jitter that's not really there".)


From nobody Mon Feb 13 13:58:27 2017
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6745B1298C2; Mon, 13 Feb 2017 13:58:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-oxuQ_tK314; Mon, 13 Feb 2017 13:58:23 -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 263D812999A; Mon, 13 Feb 2017 13:58:23 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id x75so69526773vke.2; Mon, 13 Feb 2017 13:58:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ypas3XVQ5I03Rxr8AopWeugndkhd5CZLUAaFm/cj0ZM=; b=kj7h3mKt7p26Fct/jpZ2Fnpq2+Tz5sxl2BxJerOWhA+XmybQN29foFOB46czaUsJ4d TSVM//aNkkqgUUtby30+MKU0irqRCYmJeabvO4b44ssvqc51JItVOXMXn8cYuFqD/v56 Vghjt5QTEQIbKmz4pxfBUTqs0iD12seDUXWI8cQhioyH4i9d8h0sTy+hMdPXXlFLw5Bn HDFtzBmGVjvKLNFp5fiPLTObAeYQzYsuqZYF1BVq3LRvryVPDEqTIaZAmIbUYa5K0NBP 7ZRABjLY468sAI5+zQGCdXHivQEdv+31zE5VDEo+eivxmxr7aSmPdD9HXjjZUrMpbQDx kg3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ypas3XVQ5I03Rxr8AopWeugndkhd5CZLUAaFm/cj0ZM=; b=Qeixb+quLB1U2Tt4JyZBSeBlxNkVv9fkW28UV/dku6SGmgIGeZqFM/7Z471MIOeT+F D9r05ftCCD0UzFObjP6flAhu8lPQKhm3Ac+SmQUbS0c/jeWK1pMVeWd1q/NkCfDv35Nr z+BzlboJj80OJxdTaP1n48wo1fHSu76gHM6Cj/dvOcv4VsmzNg2fBelNQvrWb4uXVNpH Ffra/d82Wax7kWhVOkyIReQXU9bkNxDaBj3+EXXjV9LDS8jL2nBDcyddSekMzOWJZ6L5 UazAPjLwqZSo2WXcOaZlLP1KSph3QbPxfcITk5VcyTUMGBckCrhT3xEQRlWEVEE9zEIr 7s8w==
X-Gm-Message-State: AMke39nSdj4gbXrOXqW6ncoC71MYAaajbbH4L3YFH1g7PagNBqCDnfrfm5N1fBkiJVQDZGbE/FyK0Wb9J3ABuQ==
X-Received: by 10.31.205.133 with SMTP id d127mr12359828vkg.18.1487023102142;  Mon, 13 Feb 2017 13:58:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.88.90 with HTTP; Mon, 13 Feb 2017 13:58:01 -0800 (PST)
In-Reply-To: <64c8d9d7-9df8-023e-6d47-4807cc0e30b7@omnitor.se>
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com> <64c8d9d7-9df8-023e-6d47-4807cc0e30b7@omnitor.se>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 13 Feb 2017 13:58:01 -0800
Message-ID: <CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com>
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: =?UTF-8?Q?Gunnar_Hellstr=C3=B6m?= <gunnar.hellstrom@omnitor.se>
Content-Type: multipart/alternative; boundary=001a114dcffac6b08e0548708bab
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DZJxxH1FM-9QvjbX9nQjmMe_Qrg>
Cc: slim@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 21:58:25 -0000

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

Gunnar said:

"With some hesitation I suggest to let it mean to see a speaking person."

[BA] Is this for the purpose of enabling lip reading?

Assuming that we go that way, how would captioning be negotiated?

On Mon, Feb 13, 2017 at 1:23 PM, Gunnar Hellstr=C3=B6m <
gunnar.hellstrom@omnitor.se> wrote:

> Bernard,
>
> I just issued comments where I also included the "silly states" topic wit=
h
> similar views as yours.
>
> Den 2017-02-13 kl. 20:06, skrev Bernard Aboba:
>
> Looking over Section 5.4, it seems to me that the title "Silly States" ma=
y
> not be appropriate, because it mixes discussion of combinations of media
> and language that have an "undefined" meaning with combinations for which
> normative guidance can be provided  So rather than having a single "Silly
> States" section, perhaps we can have a section on "Undefined States" (for
> those combinations which have an undefined meaning) provide normative
> guidance on defined combinations elsewhere.
>
> 5.4 <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-langua=
ge-06#section-5.4>.  Silly States
>
>    It is possible to specify a "silly state" where the language
>    specified does not make sense for the media type, such as specifying
>    a signed language for an audio media stream.
>
>    An offer MUST NOT be created where the language does not make sense
>    for the media type.  If such an offer is received, the receiver MAY
>    reject the media, ignore the language specified, or attempt to
>    interpret the intent (e.g., if American Sign Language is specified
>    for an audio media stream, this might be interpreted as a desire to
>    use spoken English).
>
>    A spoken language tag for a video stream in conjunction with an audio
>    stream with the same language might indicate a request for
>    supplemental video to see the speaker.
>
> [BA] Rather than using terms like "might" for combinations that could hav=
e a
>
> defined meaning, I would like to see the specification provide normative
>
> language on these use cases. In particular, I would like the specificatio=
n to describe:
>
> a. What it means when a spoken language tag is included for a video strea=
m.
>
> Is this to be interpreted as a request for captioning?
>
> b. What it means when a signed language tag is included for an audio stre=
am.
>
> Is the meaning of this "undefined" and if so, should it be ignored?
>
> c. What it means when a signed language tag is included for a text stream=
.
>
> If some of these scenarios are not defined, the specification can say
>
> "this combination does not have a defined meaning" or something like that=
.
>
> See my recent comments for more views. I support the idea to be normative
> and specific when possible.
> A complication is that there is no difference between language tags for
> written and spoken language.
>
> So we have the following possible combinations and interpretations of
> "silly states"
>
> 1. Spoken/written tag in video media, can mean to see a speaking person,
> or to provide captions overlayed on video.
> With some hesitation I suggest to let it mean to see a speaking person.
> The draft adds a requirement to have the same language in the audio strea=
m
> in the same direction to have that interpretation.  Should that mean that
> if there is another language in the audio stream, then the spoken/written
> tag in the video stream should mean captions in the specified language?
> That sounds useful for some cases, but complex to interpret and unfair to
> the users who would benefit from captions in the same language as in audi=
o.
> Summary: I think we had better to use the interpretation to see a speakin=
g
> person regardless of what language is indicated for audio.
>
> 2. Signed language tag in audio media, can mean audio from a signing
> person. That could be anything between near silence and spoken words
> corresponding to the signed signs as far as feasible. This is usually see=
n
> as disturbing to sign language users but it exists, e.g. when one erson
> needs to communicate with both hearing and deaf persons simultaneously.
> There are also variants of signing, called sign supported language, with
> signs expressed with spoken language word order and grammar. That can mor=
e
> easily be combined with spoken language, but would more likely be indicat=
ed
> by spoken language tag in audio media.
> Summary: I am inclined to let signed language tag in audio media mean
> audio from the signing person and possibly used for the rare cases when i=
t
> has some relevance for language communication.
>
> 3. Sign language tag in text media. There are some ways to represent sign
> language in various kinds of symbol or text representation. Some are
> represented in Unicode. One is a system called Sign Writing. Some
> fingerspelling methods also have fonts corresponding to characters in cod=
e
> pages. There is also an informal way to write manuscripts for signing in
> words with capitals approximately corresponding to signs, often with some
> notation added for unique sign language ways of expression that has no
> direct correspondance to words. None of these systems above are common in
> real-time conversation, but I have seen examples of such use.
> Summary: I think we can leave freedom here and just specify that a sign
> language tag in text media means some representation of sign language or =
a
> corresponding fingerspelling system in text media.
>
> If these conclusions are accepted, we can formulate modified text. Note
> that the case with spoken/written language tag in video media is mentione=
d
> in two places in the draft.
>
> Regards
> Gunnar
>
>
>
>
> _______________________________________________
> SLIM mailing listSLIM@ietf.orghttps://www.ietf.org/mailman/listinfo/slim
>
>
> --
> -----------------------------------------
> Gunnar Hellstr=C3=B6m
> Omnitorgunnar.hellstrom@omnitor.se
> +46 708 204 288
>
>

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

<div dir=3D"ltr">Gunnar said:=C2=A0<div><br></div><div>&quot;<span style=3D=
"font-size:12.8px">With some hesitation I suggest to let it mean to see a s=
peaking person.&quot;</span></div><div><span style=3D"font-size:12.8px"><br=
></span></div><div><span style=3D"font-size:12.8px">[BA] Is this for the pu=
rpose of enabling lip reading?</span></div><div><br></div><div><span style=
=3D"font-size:12.8px">Assuming that we go that way, how would captioning be=
 negotiated? =C2=A0</span></div></div><div class=3D"gmail_extra"><br><div c=
lass=3D"gmail_quote">On Mon, Feb 13, 2017 at 1:23 PM, Gunnar Hellstr=C3=B6m=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:gunnar.hellstrom@omnitor.se" targe=
t=3D"_blank">gunnar.hellstrom@omnitor.se</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>Bernard,</p>
    <p>I just issued comments where I also included the &quot;silly states&=
quot;
      topic with similar views as yours.<br>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_-5938956729983911409moz-cite-prefix">Den 2017-02-13 kl.=
 20:06, skrev Bernard
      Aboba:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr"><span class=3D"m_-5938956729983911409gmail-im" style=
=3D"font-size:12.8px">
          <div>Looking over Section 5.4, it seems to me that the title
            &quot;Silly States&quot; may not be appropriate, because it mix=
es
            discussion of combinations<span style=3D"font-size:12.8px">=C2=
=A0of
              media and language that have an &quot;undefined&quot; meaning=
 with
              combinations=C2=A0</span><span style=3D"font-size:12.8px">for
              which normative guidance can be provided =C2=A0So rather than
              having a single &quot;Silly States&quot; section, perhaps we =
can
              have a section on &quot;Undefined States&quot; (for those
              combinations which have an undefined meaning) provide
              normative guidance on defined combinations elsewhere.</span><=
/div>
          <div><br>
          </div>
          <div>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span c=
lass=3D"m_-5938956729983911409gmail-h3" style=3D"line-height:0pt;display:in=
line;font-size:1em;font-weight:bold"><h3 style=3D"line-height:0pt;display:i=
nline;font-size:1em"><a class=3D"m_-5938956729983911409gmail-selflink" name=
=3D"m_-5938956729983911409_section-5.4" href=3D"https://tools.ietf.org/html=
/draft-ietf-slim-negotiating-human-language-06#section-5.4" style=3D"color:=
black;text-decoration:none" target=3D"_blank">5.4</a>.  Silly States</h3></=
span>

   It is possible to specify a &quot;silly state&quot; where the language
   specified does not make sense for the media type, such as specifying
   a signed language for an audio media stream.</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   An o=
ffer MUST NOT be created where the language does not make sense
   for the media type.  If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent (e.g., if American Sign Language is specified
   for an audio media stream, this might be interpreted as a desire to
   use spoken English).

   A spoken language tag for a video stream in conjunction with an audio
   stream with the same language might indicate a request for
   supplemental video to see the speaker.</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">[BA] Ra=
ther than using terms like &quot;might&quot; for combinations that could ha=
ve a</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">defined=
 meaning, I would like to see the specification provide normative </pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">languag=
e on these use cases. In particular, I would like the specification to desc=
ribe: </pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">a. What=
 it means when a spoken language tag is included for a video stream. </pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is this=
 to be interpreted as a request for captioning?</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">b. What=
 it means when a signed language tag is included for an audio stream.</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is the =
meaning of this &quot;undefined&quot; and if so, should it be ignored?</pre=
>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">c. What=
 it means when a signed language tag is included for a text stream.</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">If some=
 of these scenarios are not defined, the specification can say</pre>
            <pre class=3D"m_-5938956729983911409gmail-newpage" style=3D"fon=
t-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">&quot;t=
his combination does not have a defined meaning&quot; or something like tha=
t.</pre>
          </div>
        </span></div>
    </blockquote></div></div>
    See my recent comments for more views. I support the idea to be
    normative and specific when possible.<br>
    A complication is that there is no difference between language tags
    for written and spoken language. <br>
    <br>
    So we have the following possible combinations and interpretations
    of &quot;silly states&quot;<br>
    <br>
    1. Spoken/written tag in video media, can mean to see a speaking
    person, or to provide captions overlayed on video.<br>
    With some hesitation I suggest to let it mean to see a speaking
    person. The draft adds a requirement to have the same language in
    the audio stream in the same direction to have that interpretation.=C2=
=A0
    Should that mean that if there is another language in the audio
    stream, then the spoken/written tag in the video stream should mean
    captions in the specified language? That sounds useful for some
    cases, but complex to interpret and unfair to the users who would
    benefit from captions in the same language as in audio. <br>
    Summary: I think we had better to use the interpretation to see a
    speaking person regardless of what language is indicated for audio.<br>
    <br>
    2. Signed language tag in audio media, can mean audio from a signing
    person. That could be anything between near silence and spoken words
    corresponding to the signed signs as far as feasible. This is
    usually seen as disturbing to sign language users but it exists,
    e.g. when one erson needs to communicate with both hearing and deaf
    persons simultaneously. There are also variants of signing, called
    sign supported language, with signs expressed with spoken language
    word order and grammar. That can more easily be combined with spoken
    language, but would more likely be indicated by spoken language tag
    in audio media.<br>
    Summary: I am inclined to let signed language tag in audio media
    mean audio from the signing person and possibly used for the rare
    cases when it has some relevance for language communication. <br>
    <br>
    3. Sign language tag in text media. There are some ways to represent
    sign language in various kinds of symbol or text representation.
    Some are represented in Unicode. One is a system called Sign
    Writing. Some fingerspelling methods also have fonts corresponding
    to characters in code pages. There is also an informal way to write
    manuscripts for signing in words with capitals approximately
    corresponding to signs, often with some notation added for unique
    sign language ways of expression that has no direct correspondance
    to words. None of these systems above are common in real-time
    conversation, but I have seen examples of such use.<br>
    Summary: I think we can leave freedom here and just specify that a
    sign language tag in text media means some representation of sign
    language or a corresponding fingerspelling system in text media. <br>
    =C2=A0=C2=A0 =C2=A0 <br>
    If these conclusions are accepted, we can formulate modified text.
    Note that the case with spoken/written language tag in video media
    is mentioned in two places in the draft.<br>
    <br>
    Regards<br>
    Gunnar<br>
    =C2=A0<br>
    <blockquote type=3D"cite">
      <br>
      <fieldset class=3D"m_-5938956729983911409mimeAttachmentHeader"></fiel=
dset>
      <br>
      <pre>______________________________<wbr>_________________
SLIM mailing list
<a class=3D"m_-5938956729983911409moz-txt-link-abbreviated" href=3D"mailto:=
SLIM@ietf.org" target=3D"_blank">SLIM@ietf.org</a>
<a class=3D"m_-5938956729983911409moz-txt-link-freetext" href=3D"https://ww=
w.ietf.org/mailman/listinfo/slim" target=3D"_blank">https://www.ietf.org/ma=
ilman/<wbr>listinfo/slim</a><span class=3D"HOEnZb"><font color=3D"#888888">
</font></span></pre><span class=3D"HOEnZb"><font color=3D"#888888">
    </font></span></blockquote><span class=3D"HOEnZb"><font color=3D"#88888=
8">
    <br>
    <pre class=3D"m_-5938956729983911409moz-signature" cols=3D"72">--=20
------------------------------<wbr>-----------
Gunnar Hellstr=C3=B6m
Omnitor
<a class=3D"m_-5938956729983911409moz-txt-link-abbreviated" href=3D"mailto:=
gunnar.hellstrom@omnitor.se" target=3D"_blank">gunnar.hellstrom@omnitor.se<=
/a>
+46 708 204 288</pre>
  </font></span></div>

</blockquote></div><br></div>

--001a114dcffac6b08e0548708bab--


From nobody Mon Feb 13 14:21:45 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27A5B12998C; Mon, 13 Feb 2017 14:21:41 -0800 (PST)
X-Quarantine-ID: <zRPJPoCsGk1r>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 zRPJPoCsGk1r; Mon, 13 Feb 2017 14:21:39 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2C38512942F; Mon, 13 Feb 2017 14:21:39 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 13 Feb 2017 14:13:52 -0800
Mime-Version: 1.0
Message-Id: <p06240608d4c7de63a70f@[99.111.97.136]>
In-Reply-To: <21d6ddb3-ebbd-833e-f5ff-800bdf144d2d@omnitor.se>
References: <148639487217.18865.13611191877947090796.idtracker@ietfa.amsl.com> <21d6ddb3-ebbd-833e-f5ff-800bdf144d2d@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Mon, 13 Feb 2017 14:18:15 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, "slim@ietf.org" <slim@ietf.org>, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] Last Call:  <draft-ietf-slim-negotiating-human-language-06.txt> (Negotiating Human  Language in Real-Time Communications) to Proposed Standard
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a5RSewUfJ2ytpF8rqragU9vHiK4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:21:41 -0000

Hi Gunnar,

Please see inline.

At 11:34 AM +0100 2/13/17, Gunnar Hellstr=F6m wrote:

>  I have reviewed=20
> draft-ietf-slim-negotiating-human-language-06.txt=20
> and have composed a proposed edited version=20
> adjusted for my comments below, and=20
> additionally for some minor editorial issues.
>
>  The attached version is a rough edit of the txt=20
> file version. Accepted edits need to be re-done=20
> in the XML version.
>
>  Please use a diff to find all edit proposals.=20
> The main ones are listed below with reference=20
> to sections in the files.
>
>=20
> --------------------------------------------------------------------------=
-----------------------
>
>  1. Inexact wording about the syntax of the new attributes.
>
>  Sections 5 and 5.2,  .
>
>  The text sometimes indicate that the value of=20
> the attributes is a language tag, and sometimes=20
> a language tag with an optionally appended=20
> asterisk. The syntax shown in section 5.2 is=20
> also not in alignment with the syntax shown in=20
> section 6. In 5.2 it is shown without the=20
> optional asterisk, and in 6 with the optional=20
> asterisk.

I will delete the syntax description from 5.2 to avoid confusion.

>
>  Proposed action:  Make the attribute syntax=20
> equal in sections 5.2 and 6. Make sure that=20
> when "Language-Tag" is mentioned, it is only=20
> about the language tag part of the attribute=20
> value, and when the attribute value is=20
> mentioned, it is about the complete value,=20
> including the optional modifier.
>
>  Changes:
>
>  Last line in 5.  Change "be" to "contain"
>
>  Add [ asterisk ] last in both syntax lines in 5.2.

I will adjust the text in the last line of 5 and=20
clarify the text for the use of "the values" in=20
5.2.

>
>  Multiple small changes in section 5.2. to=20
> adjust wording to be more exact. - See attached=20
> draft.
>
>=20
> --------------------------------------------------------------------------=
------------------------------------------------------
>
>  2. Reminiscense of earlier syntax.
>
>  In a couple of places, there is wording left=20
> over from a recently abandoned syntax for the=20
> attributes. In an earlier version, each=20
> attribute value could contain multiple=20
> language-tags. Now, there is just one=20
> language-tag in each attribute value.
>
>  Changes:
>  At end of page 6:
>  Old:  "The values constitute a list of languages in preference order"
>
>  New: "The values from multiple attributes=20
> constitute a list of languages in preference=20
> order per direction"
>
>  At end of Section 5.3, the comparison with=20
> Accept-Language syntax is not valid anymore.
>
>  Delete: "(similar to SIP Accept-Language syntax)"

OK.

>
>=20
> --------------------------------------------------------------------------=
--------------------------------------------------------
>
>  3. Inexact wording about O/A procedure in section 5.2
>
>  The answers are called "accepted language", but=20
> within paranthesis it is mentioned that it is=20
> only in most cases that it is selected from the=20
> offer. More suitable is then to just call it=20
> just "language":
>
>  Old:
>  " In an answer, 'humintlang-send' is the accepted language the answerer
>  will send (which in most cases is one of the languages in the offer's
>  'humintlang-recv'), and 'humintlang-recv' is the accepted language
>  the answerer expects to receive (which in most cases is one of the
>  languages in the offer's 'humintlang-send')."
>
>  New:
>
>  "In an answer, 'humintlang-send' indicates the language the answerer
>  will send (which in most cases is one of the languages in the offer's
>  'humintlang-recv'), and 'humintlang-recv' indicates the language
>  the answerer expects to receive (which in most cases is one of the
>  languages in the offer's 'humintlang-send')."

I will delete the two instances of "accepted" in 5.3.

>
>=20
> --------------------------------------------------------------------------=
---------------------
>
>  4. Inexact note at end of section 5.2.
>
>  The note at end of 5.2 has a short discussion=20
> about accepted media as if it should possibly=20
> be influenced by the matching languages. This=20
> discussion is not really valid. A media section=20
> is a request to set up a media stream,=20
> unrelated to the language indications. The=20
> devices should deny media because they are not=20
> needed for language communication. This is made=20
> more clear in an extended note.
>
>  Old:
>
>      "Note that media and language negotiation might result in more media
>      streams being accepted than are needed by the users (e.g., if more
>      preferred and less preferred combinations of media and language are
>      all accepted)."
>
>  New:
>
>  "Note that media and language negotiation might result in more media
>  streams being accepted than are needed by the users for language
>  exchange (e.g., if more preferred and less preferred combinations
>  of media and language are all accepted). This is normal and accepted,
>  because the humintlang attribute is not intended to restrict media
>  streams to be used only for language exchange."

I'll clarify the text.

>
>=20
> --------------------------------------------------------------------------=
-------
>
>  5. Make use of the asterisk modifier on media=20
> level with session scope also for media level=20
> purposes
>
>  The asterisk modifier optionally appended on=20
> attribute values has in the original -06 draft=20
> only a session effect. It is specified to=20
> indicate if the call should be rejected or not=20
> if languages do not match. It can be appended=20
> to any humintlang attribute in the whole SDP=20
> without any change in effect. This independancy=20
> of placement indicates that it is wrongly=20
> placed. With the current definition, it should=20
> be a single separate session level attribute.=20
> Instead of specifying a separate session level=20
> attribute, it is proposed that the asterisk=20
> gets an expanded definition, so that its=20
> placement conveys meaning of value for the=20
> successful language negotiation.
>
>  It has been discussed in the SLIM WG that the=20
> specification lacks two functions, required by=20
> the specifications by other bodies who are=20
> waiting for the results of SLIM real-time work.=20
> (e.g. 3GPP TS 22.228 and ETSI TR 103 201). 3GPP=20
> TS 22.228 requires "The system should be able=20
> to negotiate the user's desired language(s) and=20
> modalities, per media stream and/or session, in=20
> order of preference." Thus negotiation
>  with preference indication within the session=20
> is required, not only within each media.
>  ETSI TR 103 201 says "the Total Conversation=20
> user should be able to indicate the preferred=20
> method of communication for each direction of=20
> the session, so that the call-taker can be=20
> selected appropriately or an appropriate=20
> assisting service be invoked. " Saying=20
> "preferred" means
>  that it should also be possible to indicate less preferred alternatives.
>
>  The most urgent of these functions can be=20
> fulfilled in a simple but sufficient way by=20
> extending the meaning of the asterisk. That is=20
> the possibility to indicate a difference in=20
> preference between languages in different=20
> modalities. There is an apparent risk that many=20
> calls will start and continue in an=20
> inconvenient modaity if this differentiation is=20
> not introduced. See the proposed replaced=20
> section 5.3 and extended examples in section=20
> 5.5.
>
>  Earlier discussions on this topic has not=20
> resulted in a sufficiently simple mechanism.=20
> The extended use of the asterisk proposed here=20
> is intended to introduce the required=20
> simplification, and yet meet the most urgent=20
> needs.

The WG discussed various proposals regarding the=20
asterisk and did not reach a conclusion to change=20
what is in the draft.

>
>
>  Changes:
>
>  In 5.2
>
>  Old:
>
>  "In an offer, each language tag value MAY have an asterisk appended as
>  the last character (after the language tag).  The asterisk indicates
>  a request by the caller to not fail the call if there is no language
>  in common."
>
>  New:
>
>  "In an offer or answer, each attribute value=20
> MAY have a modifier appended as the last=20
> character (after the Language-Tag). This=20
> specification defines one value for the=20
> modifier; an asterisk ("*"). The asterisk=20
> included in a humintlang attribute value in the=20
> SDP indicates a lower preference for the=20
> indicated language and a request by the caller=20
> to not reject the call if there is no language=20
> in common."
>
>  In 5.3. The whole section replaced by:
>
>  "
>  5.3.  Preferences within the session
>
>  It is of high importance for a smooth start of a call that the
>  answering party is answering the call using the best matching
>  language(s) and modality(ies) suitable for the continuation of the call.
>  Switching language and modality during the call by agreement between
>  the participants is often time consuming. Without support of detailed
>  language and modality negotiation the particiants may have a tendency
>  to continue the call in the initial language and modality even if a
>  more convenient common language and modality combination is available.
>  In order to support the decision on which of the available language(s)
>  and modality(ies) to use initially in the call, a simple two-level
>  preference indicator is specified here for inclusion as a modifier
>  in the humintlang attribute values. The preference indicator is also
>  used as an indicator that the call SHOULD be established even if no
>  language match is found.
>
>  The asterisk ("*") is used as a preference indicator within the session.
>  Low relative preference for a language and modality to be used in the
>  session SHOULD be indicated by appending an asterisk after the language
>  tag in the attribute value. This indication from the offering party
>  SHOULD be interpreted by the answering party as a request to use a
>  higher preferred language and modality when answering the call if
>  available, but otherwise accept a lower preferred language and
>  modality combination if that is available. When satisfying languages
>  and modalities in the offer is regarded to be so important that the
>  whole call SHOULD be rejected if no match can be provided in the
>  session in one or both directions, then the asterisk shall not be
>  appended on any indicated language in the whole session description.
>  For the case when no specific preference is desired, but the offering
>  party does not want the call to be rejected, all indicated languages
>  and modalities SHOULD have an asterisk appended.
>
>  In an answer, the language(s) and modality(ies) that the answering
>  party will use initially in the answer SHOULD be indicated without
>  an appended asterisk. Any language and modality available for later
>  use in the session MAY be indicated by a language tag with an
>  appended asterisk.
>
>  In the case when more than two parties participate in the call,
>  the language and modality indications provided to each party
>  SHOULD be the sum of the indications from the other parties.
>
>  The use of the preference indicator as specified above does
>  not provide for distinguishing between the case when two or
>  more language/modality combinations in the same direction
>  are desired for use simultaneously versus the case when two
>  or more language/modality combinations for the same directions
>  are provided as selectable alternatives without specific
>  preference differentiation. The context or other specifications
>  may introduce the possibility to distinguish between these cases.
>  When a party in a call has no indications that two or more
>  language/modality combinations for each direction are desired
>  simultaeously in the call, the party SHOULD assume that
>  satisfying one is sufficient.
>
>  Other specifications may add other attribute value modifiers than
>  the asterisk. If an unknown modifier is detected, the modifier
>  SHALL be ignored."
>
>  In section 6.
>
>  Reference to semantics in the attribute=20
> registrations are expanded from 5.2 to 5.2-5.3.
>
>=20
> --------------------------------------------------------------------------=
-------------------------
>
>  6. The cases in the "Silly states" section 5.4 are not all silly.
>
>  Section 5.4 contains some proposed=20
> interpretations of unusual language indications.
>
>  They are not silly, but just unusual. Therefore=20
> change the name of the section to
>
>  "5.4 Unusual indications"
>
>  The section contains too weak specification=20
> about what to do with the unusual indications.=20
> That may cause a risk that a user who gets=20
> accustomed to one behavior in contact with=20
> certain UAs, suddeenly gets another behavior in=20
> contact with another UA.
>
>  Change:
>  Old:
>
>  "An offer MUST NOT be created where the language does not make sense
>  for the media type.  If such an offer is received, the receiver MAY
>  reject the media, ignore the language specified, or attempt to
>  interpret the intent (e.g., if American Sign Language is specified
>  for an audio media stream, this might be interpreted as a desire to
>  use spoken English)."
>
>  To:
>
>  "An offer MUST NOT be created where the language does not make sense
>  for the media type.  If such an offer is received, the receiver SHOULD
>  ignore the language specified."

OK.

>
>
>  Also add the following at the end of 5.4 to=20
> explain the choice of interpretation of a=20
> spoken/written language tag in a video medium=20
> to be a request to see the speaker rather than=20
> having text captions overlayed on video.
>
>  "There is no difference between language tags for spoken and written
>  languages. The spoken or written language tag indicated for a video
>  stream could therefore be interpreted as a capability or request to
>  use text captions overlayed on the video stream. The interpretation
>  according to this specification SHALL however be to have a view of
>  the speaker."

I don't think we need to talk about how to=20
interpret non-signed language tags in a video=20
stream.

>
>=20
> --------------------------------------------------------------------------=
---------------------------------
>
>  7. Examples section 5.5 requires expansion
>
>  Section 5.5 Examples has very little=20
> explanations and show just a few cases. The=20
> section is proposed to be expanded, with O/A=20
> examples with descriptions and alternative=20
> outcomes in order to more thoroughly describe=20
> the intended use.
>
>  See 5.5 in the the attached file for the proposed expansion.
>
>=20
> --------------------------------------------------------------------------=
----------------------------------
>
>  8. Include more fields for attribute registration from 4566bis
>
>  Section 6 has the form for attribute=20
> registration by IANA. There are a couple of=20
> fields missing that will be important for use=20
> of the specification in the WebRTC environment.=20
> Include these fields if that is allowable=20
> according to current IANA procedures and if=20
> that does not delay the publication of this=20
> draft. These fields are needed for use of text=20
> media in WebRTC.
>
>  Change:
>
>  In two locations from:
>      "Usage Level:  media"
>
>  to:
>
>      "Usage Level:  media, dcsa(subprotocol)"
>
>  Insert in two locations in the registration forms:
>  "Mux Category: NORMAL"


I think this suggestion exceeds a simple=20
editorial change, and therefore would need to be=20
discussed on the WG list with WG consensus before=20
it can be adopted.  I would also note that these=20
fields can be added to the attribute registration=20
later, according to the rules for the registry=20
(http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml),=20
which I believe are "Specification Required."

>
>=20
> --------------------------------------------------------------------------=
-------------------------------------
>
>
>  With these proposed modifications accepted I am=20
> convinced that the result will be useful for=20
> its purpose.
>
>  Regards
>
>  Gunnar Hellstrom
>
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288
>
>
>
>
>  Den 2017-02-06 kl. 16:27, skrev The IESG:
>>  The IESG has received a request from the Selection of Language for
>>  Internet Media WG (slim) to consider the following document:
>>  - 'Negotiating Human Language in Real-Time Communications'
>>     <draft-ietf-slim-negotiating-human-language-06.txt> as Proposed
>>  Standard
>>
>>  The IESG plans to make a decision in the next few weeks, and solicits
>>  final comments on this action. Please send substantive comments to the
>>  ietf@ietf.org mailing lists by 2017-02-20. Exceptionally, comments may b=
e
>>  sent to iesg@ietf.org instead. In either case, please retain the
>>  beginning of the Subject line to allow automated sorting.
>>
>>  Abstract
>>
>>
>>      Users have various human (natural) language needs, abilities, and
>>      preferences regarding spoken, written, and signed languages.  When
>>      establishing interactive communication ("calls") there needs to be a
>>      way to negotiate (communicate and match) the caller's language and
>>      media needs with the capabilities of the called party.  This is
>>      especially important with emergency calls, where a call can be
>>      handled by a call taker capable of communicating with the user, or a
>>      translator or relay operator can be bridged into the call during
>>      setup, but this applies to non-emergency calls as well (as an
>>      example, when calling a company call center).
>>
>>      This document describes the need and a solution using new SDP stream
>>      attributes.
>>
>>
>>
>>
>>  The file can be obtained via
>>  https://datatracker.ietf.org/doc/draft-ietf-slim-negotiating-human-langu=
age/
>>
>>  IESG discussion can be tracked via
>>=20
>> https://datatracker.ietf.org/doc/draft-ietf-slim-negotiating-human-langua=
ge/ballot/
>>
>>
>>  No IPR declarations have been submitted directly on this I-D.
>>
>>
>>  The document contains these normative downward references.
>>  See RFC 3967 for additional information:
>>       draft-saintandre-sip-xmpp-chat:=20
>> Interworking between the Session Initiation=20
>> Protocol (SIP) and the Extensible Messaging=20
>> and Presence Protocol (XMPP): One-to-One Text=20
>> Chat (None - )
>>  Note that some of these references may already=20
>> be listed in the acceptable Downref Registry.
>>
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288
>
>
>
>
>  Attachment converted:=20
> TiLand:draft-ietf-slim-nego#41BE1A.txt=20
> (TEXT/R*ch) (0041BE1A)
>  _______________________________________________
>  SLIM mailing list
>  SLIM@ietf.org
>  https://www.ietf.org/mailman/listinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Voltaire said "The art of government consists of taking as much money
as possible from one party of citizens to give to the other."  The
difference between the dominant political parties is which groups they
assign which roles.


From nobody Mon Feb 13 14:23:22 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80FE11299A2 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 14:23:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 bN0-iUhwG2Ml for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 14:23:17 -0800 (PST)
Received: from bin-vsp-out-03.atm.binero.net (bin-mail-out-05.binero.net [195.74.38.228]) (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 6D8C5129994 for <ietf@ietf.org>; Mon, 13 Feb 2017 14:23:17 -0800 (PST)
X-Halon-ID: f7c137f6-f23a-11e6-9c99-0050569116f7
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-03.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Mon, 13 Feb 2017 23:22:55 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Bernard Aboba <bernard.aboba@gmail.com>
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com> <64c8d9d7-9df8-023e-6d47-4807cc0e30b7@omnitor.se> <CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <6dc77c0f-6d3d-5945-e936-6f7523003b9c@omnitor.se>
Date: Mon, 13 Feb 2017 23:23:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------D4945B31890E75A6F10555B3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cOMhHrFyr4jSvif1-tg0rZlJv2c>
Cc: slim@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:23:20 -0000

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

Den 2017-02-13 kl. 22:58, skrev Bernard Aboba:
> Gunnar said:
>
> "With some hesitation I suggest to let it mean to see a speaking person."
>
> [BA] Is this for the purpose of enabling lip reading?
Yes
>
> Assuming that we go that way, how would captioning be negotiated?
It is best placed in text media.

But captions overlayed on video in the media stream is a used technology 
so it would be good to be able to specify it.
That we cannot do it is again a sad effect of the language tags not 
distinguishing between spoken and written modality.
I once had an ambition to try to specify a notation for that to be added 
to BCP 47, but did not succeed to get any real discussion going on the 
topic.

Eventually there may be a need to specify a Modality attribute. That may 
be needed for media specified e.g. as m=application where the protocol 
can carry all kinds of modality and it is not apparent from the m-line 
what it is. These are however not common for real-time conversational 
purposes, so I do not think it is urgent to solve the problem for 
m=application now.  But maybe for captioning in video media?

/Gunnar


>
> On Mon, Feb 13, 2017 at 1:23 PM, Gunnar Hellström 
> <gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>> wrote:
>
>     Bernard,
>
>     I just issued comments where I also included the "silly states"
>     topic with similar views as yours.
>
>
>     Den 2017-02-13 kl. 20:06, skrev Bernard Aboba:
>>     Looking over Section 5.4, it seems to me that the title "Silly
>>     States" may not be appropriate, because it mixes discussion of
>>     combinations of media and language that have an "undefined"
>>     meaning with combinations for which normative guidance can be
>>     provided  So rather than having a single "Silly States" section,
>>     perhaps we can have a section on "Undefined States" (for those
>>     combinations which have an undefined meaning) provide normative
>>     guidance on defined combinations elsewhere.
>>
>>
>>           5.4
>>           <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4>.
>>           Silly States
>>
>>
>>
>>         It is possible to specify a "silly state" where the language
>>         specified does not make sense for the media type, such as specifying
>>         a signed language for an audio media stream.
>>         An offer MUST NOT be created where the language does not make sense
>>         for the media type.  If such an offer is received, the receiver MAY
>>         reject the media, ignore the language specified, or attempt to
>>         interpret the intent (e.g., if American Sign Language is specified
>>         for an audio media stream, this might be interpreted as a desire to
>>         use spoken English).
>>
>>         A spoken language tag for a video stream in conjunction with an audio
>>         stream with the same language might indicate a request for
>>         supplemental video to see the speaker.
>>     [BA] Rather than using terms like "might" for combinations that could have a
>>     defined meaning, I would like to see the specification provide normative
>>     language on these use cases. In particular, I would like the specification to describe:
>>     a. What it means when a spoken language tag is included for a video stream.
>>     Is this to be interpreted as a request for captioning?
>>     b. What it means when a signed language tag is included for an audio stream.
>>     Is the meaning of this "undefined" and if so, should it be ignored?
>>     c. What it means when a signed language tag is included for a text stream.
>>     If some of these scenarios are not defined, the specification can say
>>     "this combination does not have a defined meaning" or something like that.
>     See my recent comments for more views. I support the idea to be
>     normative and specific when possible.
>     A complication is that there is no difference between language
>     tags for written and spoken language.
>
>     So we have the following possible combinations and interpretations
>     of "silly states"
>
>     1. Spoken/written tag in video media, can mean to see a speaking
>     person, or to provide captions overlayed on video.
>     With some hesitation I suggest to let it mean to see a speaking
>     person. The draft adds a requirement to have the same language in
>     the audio stream in the same direction to have that
>     interpretation.  Should that mean that if there is another
>     language in the audio stream, then the spoken/written tag in the
>     video stream should mean captions in the specified language? That
>     sounds useful for some cases, but complex to interpret and unfair
>     to the users who would benefit from captions in the same language
>     as in audio.
>     Summary: I think we had better to use the interpretation to see a
>     speaking person regardless of what language is indicated for audio.
>
>     2. Signed language tag in audio media, can mean audio from a
>     signing person. That could be anything between near silence and
>     spoken words corresponding to the signed signs as far as feasible.
>     This is usually seen as disturbing to sign language users but it
>     exists, e.g. when one erson needs to communicate with both hearing
>     and deaf persons simultaneously. There are also variants of
>     signing, called sign supported language, with signs expressed with
>     spoken language word order and grammar. That can more easily be
>     combined with spoken language, but would more likely be indicated
>     by spoken language tag in audio media.
>     Summary: I am inclined to let signed language tag in audio media
>     mean audio from the signing person and possibly used for the rare
>     cases when it has some relevance for language communication.
>
>     3. Sign language tag in text media. There are some ways to
>     represent sign language in various kinds of symbol or text
>     representation. Some are represented in Unicode. One is a system
>     called Sign Writing. Some fingerspelling methods also have fonts
>     corresponding to characters in code pages. There is also an
>     informal way to write manuscripts for signing in words with
>     capitals approximately corresponding to signs, often with some
>     notation added for unique sign language ways of expression that
>     has no direct correspondance to words. None of these systems above
>     are common in real-time conversation, but I have seen examples of
>     such use.
>     Summary: I think we can leave freedom here and just specify that a
>     sign language tag in text media means some representation of sign
>     language or a corresponding fingerspelling system in text media.
>
>     If these conclusions are accepted, we can formulate modified text.
>     Note that the case with spoken/written language tag in video media
>     is mentioned in two places in the draft.
>
>     Regards
>     Gunnar
>
>>
>>
>>     _______________________________________________
>>     SLIM mailing list
>>     SLIM@ietf.org <mailto:SLIM@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/slim
>>     <https://www.ietf.org/mailman/listinfo/slim>
>
>     -- 
>     -----------------------------------------
>     Gunnar Hellström
>     Omnitor
>     gunnar.hellstrom@omnitor.se <mailto:gunnar.hellstrom@omnitor.se>
>     +46 708 204 288
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim
-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288

--------------D4945B31890E75A6F10555B3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Den 2017-02-13 kl. 22:58, skrev Bernard Aboba:<br>
    <blockquote
cite="mid:CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com"
      type="cite">
      <div dir="ltr">Gunnar said: 
        <div><br>
        </div>
        <div>"<span style="font-size:12.8px">With some hesitation I
            suggest to let it mean to see a speaking person."</span></div>
      </div>
    </blockquote>
    <blockquote
cite="mid:CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><span style="font-size:12.8px"><br>
          </span></div>
        <div><span style="font-size:12.8px">[BA] Is this for the purpose
            of enabling lip reading?</span></div>
      </div>
    </blockquote>
    Yes<br>
    <blockquote
cite="mid:CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div><span style="font-size:12.8px">Assuming that we go that
            way, how would captioning be negotiated?  <br>
          </span></div>
      </div>
    </blockquote>
    It is best placed in text media. <br>
    <br>
    But captions overlayed on video in the media stream is a used
    technology so it would be good to be able to specify it.<br>
    That we cannot do it
    is again a sad effect of the language tags not distinguishing
    between spoken and written modality.<br>
    I once had an ambition to try to specify a notation for that to be
    added to BCP 47, but did not succeed to get any real discussion
    going on the topic. <br>
    <br>
    Eventually there may be a need to specify a Modality attribute. That
    may be needed for media specified e.g. as m=application where the
    protocol can carry all kinds of modality and it is not apparent from
    the m-line what it is. These are however not common for real-time
    conversational purposes, so I do not think it is urgent to solve the
    problem for m=application now.  But maybe for captioning in video
    media?<br>
    <br>
    /Gunnar <br>
    <br>
    <br>
    <blockquote
cite="mid:CAOW+2dsncmCrGxcFBeBJ33eGuVT8gnF2CD8QvHbVFT5NzN5F8A@mail.gmail.com"
      type="cite">
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Feb 13, 2017 at 1:23 PM, Gunnar
          Hellström <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:gunnar.hellstrom@omnitor.se" target="_blank">gunnar.hellstrom@omnitor.se</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000">
              <p>Bernard,</p>
              <p>I just issued comments where I also included the "silly
                states" topic with similar views as yours.<br>
              </p>
              <div>
                <div class="h5"> <br>
                  <div class="m_-5938956729983911409moz-cite-prefix">Den
                    2017-02-13 kl. 20:06, skrev Bernard Aboba:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr"><span
                        class="m_-5938956729983911409gmail-im"
                        style="font-size:12.8px">
                        <div>Looking over Section 5.4, it seems to me
                          that the title "Silly States" may not be
                          appropriate, because it mixes discussion of
                          combinations<span style="font-size:12.8px"> of
                            media and language that have an "undefined"
                            meaning with combinations </span><span
                            style="font-size:12.8px">for which normative
                            guidance can be provided  So rather than
                            having a single "Silly States" section,
                            perhaps we can have a section on "Undefined
                            States" (for those combinations which have
                            an undefined meaning) provide normative
                            guidance on defined combinations elsewhere.</span></div>
                        <div><br>
                        </div>
                        <div>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><span class="m_-5938956729983911409gmail-h3" style="line-height:0pt;display:inline;font-size:1em;font-weight:bold"><h3 style="line-height:0pt;display:inline;font-size:1em"><a moz-do-not-send="true" class="m_-5938956729983911409gmail-selflink" name="m_-5938956729983911409_section-5.4" href="https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4" style="color:black;text-decoration:none" target="_blank">5.4</a>.  Silly States</h3></span>

   It is possible to specify a "silly state" where the language
   specified does not make sense for the media type, such as specifying
   a signed language for an audio media stream.</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   An offer MUST NOT be created where the language does not make sense
   for the media type.  If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent (e.g., if American Sign Language is specified
   for an audio media stream, this might be interpreted as a desire to
   use spoken English).

   A spoken language tag for a video stream in conjunction with an audio
   stream with the same language might indicate a request for
   supplemental video to see the speaker.</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">[BA] Rather than using terms like "might" for combinations that could have a</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">defined meaning, I would like to see the specification provide normative </pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">language on these use cases. In particular, I would like the specification to describe: </pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">a. What it means when a spoken language tag is included for a video stream. </pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is this to be interpreted as a request for captioning?</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">b. What it means when a signed language tag is included for an audio stream.</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Is the meaning of this "undefined" and if so, should it be ignored?</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">c. What it means when a signed language tag is included for a text stream.</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">If some of these scenarios are not defined, the specification can say</pre>
                          <pre class="m_-5938956729983911409gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">"this combination does not have a defined meaning" or something like that.</pre>
                        </div>
                      </span></div>
                  </blockquote>
                </div>
              </div>
              See my recent comments for more views. I support the idea
              to be normative and specific when possible.<br>
              A complication is that there is no difference between
              language tags for written and spoken language. <br>
              <br>
              So we have the following possible combinations and
              interpretations of "silly states"<br>
              <br>
              1. Spoken/written tag in video media, can mean to see a
              speaking person, or to provide captions overlayed on
              video.<br>
              With some hesitation I suggest to let it mean to see a
              speaking person. The draft adds a requirement to have the
              same language in the audio stream in the same direction to
              have that interpretation.  Should that mean that if there
              is another language in the audio stream, then the
              spoken/written tag in the video stream should mean
              captions in the specified language? That sounds useful for
              some cases, but complex to interpret and unfair to the
              users who would benefit from captions in the same language
              as in audio. <br>
              Summary: I think we had better to use the interpretation
              to see a speaking person regardless of what language is
              indicated for audio.<br>
              <br>
              2. Signed language tag in audio media, can mean audio from
              a signing person. That could be anything between near
              silence and spoken words corresponding to the signed signs
              as far as feasible. This is usually seen as disturbing to
              sign language users but it exists, e.g. when one erson
              needs to communicate with both hearing and deaf persons
              simultaneously. There are also variants of signing, called
              sign supported language, with signs expressed with spoken
              language word order and grammar. That can more easily be
              combined with spoken language, but would more likely be
              indicated by spoken language tag in audio media.<br>
              Summary: I am inclined to let signed language tag in audio
              media mean audio from the signing person and possibly used
              for the rare cases when it has some relevance for language
              communication. <br>
              <br>
              3. Sign language tag in text media. There are some ways to
              represent sign language in various kinds of symbol or text
              representation. Some are represented in Unicode. One is a
              system called Sign Writing. Some fingerspelling methods
              also have fonts corresponding to characters in code pages.
              There is also an informal way to write manuscripts for
              signing in words with capitals approximately corresponding
              to signs, often with some notation added for unique sign
              language ways of expression that has no direct
              correspondance to words. None of these systems above are
              common in real-time conversation, but I have seen examples
              of such use.<br>
              Summary: I think we can leave freedom here and just
              specify that a sign language tag in text media means some
              representation of sign language or a corresponding
              fingerspelling system in text media. <br>
                   <br>
              If these conclusions are accepted, we can formulate
              modified text. Note that the case with spoken/written
              language tag in video media is mentioned in two places in
              the draft.<br>
              <br>
              Regards<br>
              Gunnar<br>
               <br>
              <blockquote type="cite"> <br>
                <fieldset
                  class="m_-5938956729983911409mimeAttachmentHeader"></fieldset>
                <br>
                <pre>______________________________<wbr>_________________
SLIM mailing list
<a moz-do-not-send="true" class="m_-5938956729983911409moz-txt-link-abbreviated" href="mailto:SLIM@ietf.org" target="_blank">SLIM@ietf.org</a>
<a moz-do-not-send="true" class="m_-5938956729983911409moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/slim" target="_blank">https://www.ietf.org/mailman/<wbr>listinfo/slim</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
    </font></span></blockquote><span class="HOEnZb"><font color="#888888">
    

    <pre class="m_-5938956729983911409moz-signature" cols="72">-- 
------------------------------<wbr>-----------
Gunnar Hellström
Omnitor
<a moz-do-not-send="true" class="m_-5938956729983911409moz-txt-link-abbreviated" href="mailto:gunnar.hellstrom@omnitor.se" target="_blank">gunnar.hellstrom@omnitor.se</a>
+46 708 204 288</pre>
  </font></span></div>

</blockquote></div>
</div>


<fieldset class="mimeAttachmentHeader"></fieldset>
<pre wrap="">_______________________________________________
SLIM mailing list
<a class="moz-txt-link-abbreviated" href="mailto:SLIM@ietf.org">SLIM@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/slim">https://www.ietf.org/mailman/listinfo/slim</a>
</pre>

</blockquote>
<pre class="moz-signature" cols="72">-- 
-----------------------------------------
Gunnar Hellström
Omnitor
<a class="moz-txt-link-abbreviated" href="mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</a>
+46 708 204 288</pre></body></html>
--------------D4945B31890E75A6F10555B3--


From nobody Mon Feb 13 14:27:38 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35828129997; Mon, 13 Feb 2017 14:27:32 -0800 (PST)
X-Quarantine-ID: <NApbPRhqef7U>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 NApbPRhqef7U; Mon, 13 Feb 2017 14:27:30 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id C45BF129439; Mon, 13 Feb 2017 14:27:30 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 13 Feb 2017 14:19:44 -0800
Mime-Version: 1.0
Message-Id: <p06240609d4c7e2c0acbf@[99.111.97.136]>
In-Reply-To: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com>
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Mon, 13 Feb 2017 14:26:28 -0800
To: Bernard Aboba <bernard.aboba@gmail.com>, slim@ietf.org, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gpksURbVnrMNTlIhmSDLKkCkl64>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:27:32 -0000

At 11:06 AM -0800 2/13/17, Bernard Aboba wrote:

>  Looking over Section 5.4, it seems to me that the title "Silly 
> States" may not be appropriate, because it mixes discussion of 
> combinations of media and language that have an "undefined" meaning 
> with combinations for which normative guidance can be provided  So 
> rather than having a single "Silly States" section, perhaps we can 
> have a section on "Undefined States" (for those combinations which 
> have an undefined meaning) provide normative guidance on defined 
> combinations elsewhere.
>
> 
> <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4>5.4. 
> Silly States
>
>
>
>     It is possible to specify a "silly state" where the language
>     specified does not make sense for the media type, such as specifying
>     a signed language for an audio media stream.
>     An offer MUST NOT be created where the language does not make sense
>     for the media type.  If such an offer is received, the receiver MAY
>     reject the media, ignore the language specified, or attempt to
>     interpret the intent (e.g., if American Sign Language is specified
>     for an audio media stream, this might be interpreted as a desire to
>     use spoken English).
>
>     A spoken language tag for a video stream in conjunction with an audio
>     stream with the same language might indicate a request for
>     supplemental video to see the speaker.
>
>  [BA] Rather than using terms like "might" for combinations that could have a
>  defined meaning, I would like to see the specification provide normative
>  language on these use cases. In particular, I would like the 
> specification to describe:
>
>  a. What it means when a spoken language tag is included for a video stream.
>  Is this to be interpreted as a request for captioning?
>  b. What it means when a signed language tag is included for an audio stream.
>  Is the meaning of this "undefined" and if so, should it be ignored?
>  c. What it means when a signed language tag is included for a text stream.
>
>  If some of these scenarios are not defined, the specification can say
>  "this combination does not have a defined meaning" or something like that.

I will change the section title to "Undefined Combinations" and 
replace the text with:

    Specifying a non-signed language tag for a video media stream, or a
    signed language tag for a non-video media stream, is not defined.  An
    offer with such a combination SHOULD NOT be created.  If such an
    offer is received, the receiver MAY ignore the language specified.

I think this retains the intent of the old section while avoiding 
wading into the unclear issue of intent of such combinations.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
I suppose when it gets to that point, we shan't know how it does it.
    --Alan Turing


From nobody Mon Feb 13 14:32:37 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 966551299B0 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 14:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FgQ7kWKoFn5N for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 14:32:31 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 4FE6C1299AC for <ietf@ietf.org>; Mon, 13 Feb 2017 14:32:29 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id BD432124 for <ietf@ietf.org>; Mon, 13 Feb 2017 22:32:28 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RinbbomY9lsb for <ietf@ietf.org>; Mon, 13 Feb 2017 16:32:28 -0600 (CST)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 7A3D680F for <ietf@ietf.org>; Mon, 13 Feb 2017 16:32:28 -0600 (CST)
Received: by mail-ua0-f197.google.com with SMTP id a88so81198613uaa.1 for <ietf@ietf.org>; Mon, 13 Feb 2017 14:32:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CetrN8LgU6+R6+kT/yWcnhJ6HLCCY54+U2itsrcc4SM=; b=AyNyn4hRWhkjYnCK/vArztlmI+eClaEoFqduVlVCtz4rq59XBks5kpo3N/ory/zAaM FfBhsTMUTAw8KtsqasGjQlW17auJ+egXgCE03LajfZDo2Yx+i5kvQRwliOdBhstFCovI mz64jbX08zfBZ/ZbbfYE6hJCPzi4o0EgEuJ2VUl7xLJqibUMn+BzC2xfZLyeb05sSSXb h1+6nc7UcTQxzTmOWS7E1YVmVGdCaMHiDWgUG0/UfgcK6ZDSWwIYufjr0VwhZB/WVCT8 jiv6pgIUustBiJSizy1tD0vlbXYouZueOAf5+RyKdnk5Oq+m5Cxyeymt7mHA5pCssra8 dquQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CetrN8LgU6+R6+kT/yWcnhJ6HLCCY54+U2itsrcc4SM=; b=V4So7NINTZrh4MTmUXb7UVCdmZazrSKxWOmNXMB0XbkA54K0iuzubEjbra6pVWrcyt 80vUlOGMZL6ojL6MzVG/QzyB5yikxLLZENDOuy9fPb6tSk+Z7caVJpP/D9fI02fudOMy e57qsJG4evCgDjR5j5StXSYMrpKyUYdfO7oZummwle33eUHzMEgunTTiRHa8g45WiAtB d2LwAZ1cmlWqvP13li5hlhLE6RGQCEbtWNKpOMjm02FftlMN4whQF5i3hUYm3EqZGN7B v2443Nx8eXP2vOI/72fwORNvquU9l4EwnCz1oh7s/sHC+KtjJi9Q/p46CxERKrpkV1Er PrXw==
X-Gm-Message-State: AMke39nncpAjoJGlQm19Q0cR45Lv+eKemX3Uk2R1KQzCINDbDh8cGR1mHq4hRZYJb0dSOtPsL/KOFqOVIgpvMw6YftHfewQFUvbjv2uwVNzCShSYQ44PmAImHGlbYrCVXs7DsQOIdojtjfLZhtM=
X-Received: by 10.31.252.77 with SMTP id a74mr12680085vki.46.1487025147903; Mon, 13 Feb 2017 14:32:27 -0800 (PST)
X-Received: by 10.31.252.77 with SMTP id a74mr12680072vki.46.1487025147649; Mon, 13 Feb 2017 14:32:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Mon, 13 Feb 2017 14:32:27 -0800 (PST)
In-Reply-To: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com>
From: David Farmer <farmer@umn.edu>
Date: Mon, 13 Feb 2017 16:32:27 -0600
Message-ID: <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c149b28b2b5a205487105ea
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TFzOQxVx_l6st8u5fAkE4JAkVQY>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Announce <ietf-announce@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:32:32 -0000

--94eb2c149b28b2b5a205487105ea
Content-Type: text/plain; charset=UTF-8

I have concerns with the following text;

   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
   on inter-router point-to-point links. However, the Interface ID of
   all unicast addresses, except those that start with the binary value
   000, is required to be 64 bits long.  The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421]

The third sentence seems to limit exceptions to 64 bit IIDs to exclusively
addresses that start with binary vale of 000.  There are at least two other
exceptions from standards track RFCs, that should be more clear accounted
for in this text.  First is [RFC6164] point-to-point links, as mentioned in
the previous sentence.  I think the clear intent of [RFC6164] is to allow
one(1) Bit IIDs for point to point-to-point links using any Global Unicast
Address, not just those that start with 000.  Second is, [RFC6052], which
updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
Global Unicast Address when used for IPv4/IPv6 translation, referred to as
""Network-Specific Prefix" unique to the organization deploying the address
translators," in section 2.2 of [RFC6052].

Thanks.

On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'IP Version 6 Addressing Architecture'
>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This specification defines the addressing architecture of the IP
>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
>    model, text representations of IPv6 addresses, definition of IPv6
>    unicast addresses, anycast addresses, and multicast addresses, and an
>    IPv6 node's required addresses.
>
>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>    Architecture".
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr">I have concerns with the following text;<br><br>=C2=A0 =C2=
=A0IPv6 unicast routing is based on prefixes of any valid length up to<br>=
=C2=A0 =C2=A0128 [BCP198].=C2=A0 For example, [RFC6164] standardises 127 bi=
t prefixes<br>=C2=A0 =C2=A0on inter-router point-to-point links. However, t=
he Interface ID of<br>=C2=A0 =C2=A0all unicast addresses, except those that=
 start with the binary value<br>=C2=A0 =C2=A0000, is required to be 64 bits=
 long.=C2=A0 The rationale for the 64 bit<br>=C2=A0 =C2=A0boundary in IPv6 =
addresses can be found in [RFC7421]<br><br>The third sentence seems to limi=
t exceptions to 64 bit IIDs to exclusively addresses that start with binary=
 vale of 000.=C2=A0 There are at least two other exceptions from standards =
track RFCs, that should be more clear accounted for in this text.=C2=A0 Fir=
st is [RFC6164] point-to-point links, as mentioned in the previous sentence=
.=C2=A0 I think the clear intent of [RFC6164]=C2=A0is to allow one(1) Bit I=
IDs for point to point-to-point links using any Global Unicast Address, not=
 just those that start with 000.=C2=A0 Second is, [RFC6052], which updates =
[RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any Global Uni=
cast Address when used for IPv4/IPv6 translation, referred to as &quot;&quo=
t;Network-Specific Prefix&quot; unique to the organization deploying the ad=
dress translators,&quot; in section 2.2 of [RFC6052].<div><br></div><div>Th=
anks.<br><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Wed, Feb 1, 2017 at 5:51 PM, The IESG <span dir=3D"ltr">&lt;<a href=3D"mail=
to:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@ietf.org</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
The IESG has received a request from the IPv6 Maintenance WG (6man) to<br>
consider the following document:<br>
- &#39;IP Version 6 Addressing Architecture&#39;<br>
=C2=A0 &lt;draft-ietf-6man-rfc4291bis-07<wbr>.txt&gt; as Internet Standard<=
br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2017-03-01. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a=
> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=C2=A0 =C2=A0This specification defines the addressing architecture of the =
IP<br>
=C2=A0 =C2=A0Version 6 (IPv6) protocol.=C2=A0 The document includes the IPv=
6 addressing<br>
=C2=A0 =C2=A0model, text representations of IPv6 addresses, definition of I=
Pv6<br>
=C2=A0 =C2=A0unicast addresses, anycast addresses, and multicast addresses,=
 and an<br>
=C2=A0 =C2=A0IPv6 node&#39;s required addresses.<br>
<br>
=C2=A0 =C2=A0This document obsoletes RFC 4291, &quot;IP Version 6 Addressin=
g<br>
=C2=A0 =C2=A0Architecture&quot;.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/" re=
l=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wbr>oc/dr=
aft-ietf-6man-rfc4291bis/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ball=
ot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/d<wb=
r>oc/draft-ietf-6man-rfc4291bis/<wbr>ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">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/l<wb=
r>istinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail-m_-9129348408829699367gmail-m_-6629733456784693811gmail_signature=
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a hr=
ef=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu=
</a><br>Networking &amp; Telecommunication Services<br>Office of Informatio=
n Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave=
 SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612)%20626-0815" valu=
e=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>Minneapolis, MN 55=
414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-9952" value=3D"+16128=
129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div></div></div>

--94eb2c149b28b2b5a205487105ea--


From nobody Mon Feb 13 14:50:02 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 394BA1299D6; Mon, 13 Feb 2017 14:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4BEcGJN6NvDs; Mon, 13 Feb 2017 14:49:57 -0800 (PST)
Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::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 967EA1299DB; Mon, 13 Feb 2017 14:49:52 -0800 (PST)
Received: by mail-it0-x231.google.com with SMTP id 203so7587045ith.0; Mon, 13 Feb 2017 14:49:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=c++aBm9KTTIH/cU1ME57cMGAvgw3MPr0bsj1sziZvlg=; b=O9otzFfRS2/xIB3QG3fNlSddfaimY6v5QDYyM3U0wmvPM62SBPB3oCIXgBhdY0I1SQ W/s4JftCSwUWZ0/GDIe+0A4a8EOP7Xp92Yy3LdnTVICVhmqFcO/Ui4Q1pW5wt+JpLeKx 2WwbpcIukDdjSNIA/OjtLV3kdpS4VwBSUP9H1SxHvwh22a7KjWSZYfYd/PZuwX3Dd3pI lfmsF4Rb8dX0V60yifV7dBQpAV2DZwzsSHaNzqm6MosT2THMJpb4kAU0IXUvzTMOgolp iNHFzOd1ve9M8zPAv/E5/2h7Ez/vmFgIkxwtQASJd6L3WhkX4Etq8MThOULj8IacLl4x CUHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=c++aBm9KTTIH/cU1ME57cMGAvgw3MPr0bsj1sziZvlg=; b=QQSP4oKPBojxMAC492G+OWsVbbWeHEmlVKPtOky7tWikq18JOsQ+/HRdkKHlRJyrJs QxLXE7ifpbuzvGZGLD9IKNQV0JjbyLVwhS6YJoetl5y76EG4DpROJNJQvX81hpJr7z1o +XBp1+DHUP0LtDJKENdCdDnTq+k7s+jwENTEBw3xcdDj+nT7rVEtcHHis3tKVHO1bg8C laq2/DWzWACcAUSAvyShRSFm6P8wCoUiDAPbToyDARooxxi2+hwvP7NIQ0WsTdQTvHgE fSCW3vcCSalBgF+nsg8gjUWGuKuw6qIYqS7rtiyOuajIiOO9Ax3AWu6eb1otRmDSrTuq omJg==
X-Gm-Message-State: AMke39mb2gN8E1jAXguk1jpLA7aGvBXVpxIMrHiQNt9Et4s03nTGbiBhjuxVbkITkSQmotkUKlKxVcgOJDb66g==
X-Received: by 10.36.65.105 with SMTP id x102mr765168ita.32.1487026191936; Mon, 13 Feb 2017 14:49:51 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Mon, 13 Feb 2017 14:49:51 -0800 (PST)
In-Reply-To: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
References: <148702214924.24989.16410820532879872973.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 13 Feb 2017 17:49:51 -0500
X-Google-Sender-Auth: H_Pk51nIYvXoqwWsiK2r8mBsybw
Message-ID: <CALaySJJ_2sDviT=N6gf_i34gO2S2xXPw3e+YBS=rcgCMa5zC=w@mail.gmail.com>
Subject: Re: Review of draft-leiba-rfc2119-update-01
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aVC5u206KAeDa_9mYRWyN8Q-fMA>
Cc: General Area Review Team <gen-art@ietf.org>, draft-leiba-rfc2119-update.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:50:00 -0000

Thanks, Robert, for the review.

Barry

On Mon, Feb 13, 2017 at 4:42 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-leiba-rfc2119-update-01
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-03-09
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Ready for publication as part of BCP 14.
>
> I personally find the first bullet in the NEW section to be chatty,
> and think it could be reduced while strengthening the message, but
> enough eyes have been on this that I don't object to it going through
> as is.
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
>


From nobody Mon Feb 13 14:53:58 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B5521299D5; Mon, 13 Feb 2017 14:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IlnWNx05BuUm; Mon, 13 Feb 2017 14:53:55 -0800 (PST)
Received: from mail-ot0-x242.google.com (mail-ot0-x242.google.com [IPv6:2607:f8b0:4003:c0f::242]) (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 9C196129453; Mon, 13 Feb 2017 14:53:55 -0800 (PST)
Received: by mail-ot0-x242.google.com with SMTP id 73so13963127otj.1; Mon, 13 Feb 2017 14:53:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4Rv5f+XTTIu+WHVC+KzOSqgTeJM7NZ/Rzpcnc+r12wo=; b=lBs6Xtz5CJCyt813lqGDCnqNjpJNwOulbhLOkxBAiOWQyXXlwO4CY3Qpj+72GTWyVv H2IjoT0NAPD6mM7lhN5LTTUJgaq+vvJUeu3Q6jmiqYVQhfPgiK3K+HETvmPmdQgfJmor mfltYbZkfeUmoPYd31xnVQxRp7xvko9+Y3oWJI3Py2bJvTezaRVDctsm6YsiIpGbMNVh 34Sxx16t2/khL7M+DzKEpn4sehzJM4cXYG4KbdCaDZ9STKKWZd8N4N2+QeNhp5DdABmD ow0s+/4t8VdH2/SojIUF1FjRWJivPifLcFFkTOD75oE4loumaKBxS/oYU7RE1SaOIMIf 1Qqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=4Rv5f+XTTIu+WHVC+KzOSqgTeJM7NZ/Rzpcnc+r12wo=; b=ak8kKq/tVqzWmBntciFbvrnxQKdlVxgp/ABjZsXRSSylSqebsVXDMWRuBeeN6+wcbE YkwPmZElgO3oyxllbUMKTpCncpX4PMB9HOI42f7RhJ2Xpw8D/ca45xemSd0StIynjXoL sjUidWRTa6zMLW/7FXJ1vlP2T62Jh1otrFDhj+Zca4xSI7uRKbPTYn7qapLYwCy5aQ09 Xu6EwDXSrH9IMh7qo1GCkkarOeqdVZcHd3JQHGt/w6+0S4/Iklc+Ktx1WX4OE8eWbHho 5c3athlAE5UI7nR3K8qcfMbKnpUY/2RZG2uuImonxmQ7BBm7nCo7XhIGdbP3ABkpOggh Q/+Q==
X-Gm-Message-State: AMke39nP+M0D5GNCRLJmtYE4nrWgQtdGGMlCyLd7VF6vHdUIzLPapl2xKqmRJn41CXj0og==
X-Received: by 10.98.89.195 with SMTP id k64mr28181611pfj.126.1487026434927; Mon, 13 Feb 2017 14:53:54 -0800 (PST)
Received: from [130.216.38.149] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.149]) by smtp.gmail.com with ESMTPSA id u14sm22813125pfg.18.2017.02.13.14.53.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 14:53:54 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>, IETF-Discussion Discussion <ietf@ietf.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
Date: Tue, 14 Feb 2017 11:53:51 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pzw3DGn9BBrozPT5axKhEnTEJLM>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 22:53:57 -0000

At an earlier stage I suggested restricting the applicability
of the "However..." sentence to SLAAC [RFC4862]. A short way
of doing this would be

However, the Interface ID of unicast addresses used for
Stateless Address Autoconfiguration [RFC4862] is required
to be 64 bits long.

Regards
   Brian

On 14/02/2017 11:32, David Farmer wrote:
> I have concerns with the following text;
> 
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links. However, the Interface ID of
>    all unicast addresses, except those that start with the binary value
>    000, is required to be 64 bits long.  The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
> 
> The third sentence seems to limit exceptions to 64 bit IIDs to exclusively
> addresses that start with binary vale of 000.  There are at least two other
> exceptions from standards track RFCs, that should be more clear accounted
> for in this text.  First is [RFC6164] point-to-point links, as mentioned in
> the previous sentence.  I think the clear intent of [RFC6164] is to allow
> one(1) Bit IIDs for point to point-to-point links using any Global Unicast
> Address, not just those that start with 000.  Second is, [RFC6052], which
> updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
> Global Unicast Address when used for IPv4/IPv6 translation, referred to as
> ""Network-Specific Prefix" unique to the organization deploying the address
> translators," in section 2.2 of [RFC6052].
> 
> Thanks.
> 
> On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org> wrote:
> 
>>
>> The IESG has received a request from the IPv6 Maintenance WG (6man) to
>> consider the following document:
>> - 'IP Version 6 Addressing Architecture'
>>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    This specification defines the addressing architecture of the IP
>>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
>>    model, text representations of IPv6 addresses, definition of IPv6
>>    unicast addresses, anycast addresses, and multicast addresses, and an
>>    IPv6 node's required addresses.
>>
>>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>>    Architecture".
>>
>>
>>
>>
>> The file can be obtained via
>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>>
>> IESG discussion can be tracked via
>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>>
>>
>>
>> --------------------------------------------------------------------
>> 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 Mon Feb 13 15:07:22 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822D81299E5 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:07:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FCRcDDnTVqFc for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:07:14 -0800 (PST)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 1FCDD1299DB for <ietf@ietf.org>; Mon, 13 Feb 2017 15:07:12 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id AFA53B13 for <ietf@ietf.org>; Mon, 13 Feb 2017 23:07:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UtFBAIG-JQpe for <ietf@ietf.org>; Mon, 13 Feb 2017 17:07:11 -0600 (CST)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 41014B20 for <ietf@ietf.org>; Mon, 13 Feb 2017 17:07:11 -0600 (CST)
Received: by mail-ua0-f197.google.com with SMTP id d38so81679255uad.4 for <ietf@ietf.org>; Mon, 13 Feb 2017 15:07:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yOzdeb5J5pMgqaAbmhYBYEEwgQAKxYuCKLUcRUysFS4=; b=mcmTbfetYUCt+ptDEgOT5Xt/ibaKmp+onq/Ai6zq4f5oFjK0R/67zF/3ljwIhdtIW2 V0YOTUJSfiM6PgpP+syHEh7kGG9cPpUQVOua+Ph5v74hDludYwEn0LHCyYLB16BW4+jC DcW0fwJF8K24VxjDfXtLaHqunParB+GrR0dZFLKlj2BULEYlMXgpB8Igli3b4IkHxmyy qmajj6Gu1VW8E4JZIMzWKQxxBs0nLtoDgITBfjHvCOlzbpnDvoflJpbFHkb8UOQNVURr zOemXXJxbQkD7tXRegkQdp2oPp/fQqu9QKXhhrEtsONiR8MsqQPiX8ntFG5I5oOY/BJ8 ssag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yOzdeb5J5pMgqaAbmhYBYEEwgQAKxYuCKLUcRUysFS4=; b=fqUbCj6P0qlOv47/MUAT9kk+aM2efEfk7HHVCORRkgphmBrHEIrHnIWkPaGDMt5XyG 1SCvq/OnfF2jj0WKmWH2+tYydyXk+FpGGLomYjTm61MvNgDgxodW5AYhpBXu7kmV+nvD zIhzTIBIwG5JXr5XYfejmdkdJPKlOaBr8A/+cfWTABzXbGvbjJRoWVNUnMAQwGPrNEfr OikYjPw/X5XX9IHE9gVFwF/lbbtbQ0LQMdMjmQCnNNzi+twpkJ7dqTvumZhS7Eg8aGYM u3AP9T39xbYigm/nXfoJ98icPuPgDECOStfiVeO+df1B+aM/B7nkpK00SuV9o47plB/g LVxw==
X-Gm-Message-State: AMke39lkoR57Q8mWbe5q6pR4khtkvYnROkNe6OPOK2ptMxpo4Wns/p70y0A/rVt2f7x8GXsk9uiUcjOx4qv/wuo06sSdArbSKZrLR5QpEXhAZfMn6QOrWb1f+VoSS1LjbPhGQiLQKknWAX1Yu38=
X-Received: by 10.159.32.38 with SMTP id 35mr13559413uam.12.1487027230711; Mon, 13 Feb 2017 15:07:10 -0800 (PST)
X-Received: by 10.159.32.38 with SMTP id 35mr13559401uam.12.1487027230507; Mon, 13 Feb 2017 15:07:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Mon, 13 Feb 2017 15:07:10 -0800 (PST)
In-Reply-To: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Mon, 13 Feb 2017 17:07:10 -0600
Message-ID: <CAN-Dau0guXVeskOhF0fPskWhPXF6vFBqmN-u5aKvTkWLFnRXPw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c04cac2d89a3905487181b8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/do_q5pwQLycSEGpkUJjNCufLwxE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 23:07:16 -0000

--94eb2c04cac2d89a3905487181b8
Content-Type: text/plain; charset=UTF-8

I'll bet it comes as no surprise that I find your suggestion the preferred
solution to the issue I raise.  However, there are a number of other ways
to solve this issue, less acceptable to me than the one you suggest, but
they maybe more acceptable to others.

Thanks.

On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> At an earlier stage I suggested restricting the applicability
> of the "However..." sentence to SLAAC [RFC4862]. A short way
> of doing this would be
>
> However, the Interface ID of unicast addresses used for
> Stateless Address Autoconfiguration [RFC4862] is required
> to be 64 bits long.
>
> Regards
>    Brian
>
> On 14/02/2017 11:32, David Farmer wrote:
> > I have concerns with the following text;
> >
> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
> >    on inter-router point-to-point links. However, the Interface ID of
> >    all unicast addresses, except those that start with the binary value
> >    000, is required to be 64 bits long.  The rationale for the 64 bit
> >    boundary in IPv6 addresses can be found in [RFC7421]
> >
> > The third sentence seems to limit exceptions to 64 bit IIDs to
> exclusively
> > addresses that start with binary vale of 000.  There are at least two
> other
> > exceptions from standards track RFCs, that should be more clear accounted
> > for in this text.  First is [RFC6164] point-to-point links, as mentioned
> in
> > the previous sentence.  I think the clear intent of [RFC6164] is to allow
> > one(1) Bit IIDs for point to point-to-point links using any Global
> Unicast
> > Address, not just those that start with 000.  Second is, [RFC6052], which
> > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
> > Global Unicast Address when used for IPv4/IPv6 translation, referred to
> as
> > ""Network-Specific Prefix" unique to the organization deploying the
> address
> > translators," in section 2.2 of [RFC6052].
> >
> > Thanks.
> >
> > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org>
> wrote:
> >
> >>
> >> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> >> consider the following document:
> >> - 'IP Version 6 Addressing Architecture'
> >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
> >>
> >> The IESG plans to make a decision in the next few weeks, and solicits
> >> final comments on this action. Please send substantive comments to the
> >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may
> be
> >> sent to iesg@ietf.org instead. In either case, please retain the
> >> beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>
> >>    This specification defines the addressing architecture of the IP
> >>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
> >>    model, text representations of IPv6 addresses, definition of IPv6
> >>    unicast addresses, anycast addresses, and multicast addresses, and an
> >>    IPv6 node's required addresses.
> >>
> >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
> >>    Architecture".
> >>
> >>
> >>
> >>
> >> The file can be obtained via
> >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
> >>
> >> IESG discussion can be tracked via
> >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> >> 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
> > --------------------------------------------------------------------
> >
>



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr">I&#39;ll bet it comes as no surprise that I find your sugg=
estion the preferred solution to the issue I raise.=C2=A0 However, there ar=
e a number of other ways to solve this issue, less acceptable to me than th=
e one you suggest, but they maybe more acceptable to others.<div><br></div>=
<div>Thanks.=C2=A0<br><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <span dir=3D"ltr">&=
lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e=
.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">At an earlier stage I suggested restricting the applicability<br>
of the &quot;However...&quot; sentence to SLAAC [RFC4862]. A short way<br>
of doing this would be<br>
<br>
However, the Interface ID of unicast addresses used for<br>
Stateless Address Autoconfiguration [RFC4862] is required<br>
to be 64 bits long.<br>
<br>
Regards<br>
=C2=A0 =C2=A0Brian<br>
<br>
On 14/02/2017 11:32, David Farmer wrote:<br>
&gt; I have concerns with the following text;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid le=
ngth up to<br>
&gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For example, [RFC6164] standardises 1=
27 bit prefixes<br>
&gt;=C2=A0 =C2=A0 on inter-router point-to-point links. However, the Interf=
ace ID of<br>
&gt;=C2=A0 =C2=A0 all unicast addresses, except those that start with the b=
inary value<br>
&gt;=C2=A0 =C2=A0 000, is required to be 64 bits long.=C2=A0 The rationale =
for the 64 bit<br>
&gt;=C2=A0 =C2=A0 boundary in IPv6 addresses can be found in [RFC7421]<br>
&gt;<br>
&gt; The third sentence seems to limit exceptions to 64 bit IIDs to exclusi=
vely<br>
&gt; addresses that start with binary vale of 000.=C2=A0 There are at least=
 two other<br>
&gt; exceptions from standards track RFCs, that should be more clear accoun=
ted<br>
&gt; for in this text.=C2=A0 First is [RFC6164] point-to-point links, as me=
ntioned in<br>
&gt; the previous sentence.=C2=A0 I think the clear intent of [RFC6164] is =
to allow<br>
&gt; one(1) Bit IIDs for point to point-to-point links using any Global Uni=
cast<br>
&gt; Address, not just those that start with 000.=C2=A0 Second is, [RFC6052=
], which<br>
&gt; updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for a=
ny<br>
&gt; Global Unicast Address when used for IPv4/IPv6 translation, referred t=
o as<br>
&gt; &quot;&quot;Network-Specific Prefix&quot; unique to the organization d=
eploying the address<br>
&gt; translators,&quot; in section 2.2 of [RFC6052].<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; On Wed, Feb 1, 2017 at 5:51 PM, The IESG &lt;<a href=3D"mailto:iesg-se=
cretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; The IESG has received a request from the IPv6 Maintenance WG (6man=
) to<br>
&gt;&gt; consider the following document:<br>
&gt;&gt; - &#39;IP Version 6 Addressing Architecture&#39;<br>
&gt;&gt;=C2=A0 =C2=A0&lt;draft-ietf-6man-rfc4291bis-<wbr>07.txt&gt; as Inte=
rnet Standard<br>
&gt;&gt;<br>
&gt;&gt; The IESG plans to make a decision in the next few weeks, and solic=
its<br>
&gt;&gt; final comments on this action. Please send substantive comments to=
 the<br>
&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists b=
y 2017-03-01. Exceptionally, comments may be<br>
&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead=
. In either case, please retain the<br>
&gt;&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;&gt;<br>
&gt;&gt; Abstract<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 This specification defines the addressing architectur=
e of the IP<br>
&gt;&gt;=C2=A0 =C2=A0 Version 6 (IPv6) protocol.=C2=A0 The document include=
s the IPv6 addressing<br>
&gt;&gt;=C2=A0 =C2=A0 model, text representations of IPv6 addresses, defini=
tion of IPv6<br>
&gt;&gt;=C2=A0 =C2=A0 unicast addresses, anycast addresses, and multicast a=
ddresses, and an<br>
&gt;&gt;=C2=A0 =C2=A0 IPv6 node&#39;s required addresses.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 This document obsoletes RFC 4291, &quot;IP Version 6 =
Addressing<br>
&gt;&gt;=C2=A0 =C2=A0 Architecture&quot;.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The file can be obtained via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc429=
1bis/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<w=
br>doc/draft-ietf-6man-<wbr>rfc4291bis/</a><br>
&gt;&gt;<br>
&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc429=
1bis/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf=
.org/<wbr>doc/draft-ietf-6man-<wbr>rfc4291bis/ballot/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>--------<br>
&gt;&gt; IETF IPv6 working group mailing list<br>
&gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/l=
istinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/<wbr>listinfo/ipv6</a><br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>--------<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&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" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt;<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarm=
er@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; =
Telecommunication Services<br>Office of Information Technology<br>Universit=
y of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: =
612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D </div>
</div></div></div>

--94eb2c04cac2d89a3905487181b8--


From nobody Mon Feb 13 15:10:08 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA961294D6 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:10:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 wr8CCA1Y9-xj for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:10:00 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 D8CBF1299DB for <ietf@ietf.org>; Mon, 13 Feb 2017 15:09:59 -0800 (PST)
X-Halon-ID: 84449b9f-f241-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Tue, 14 Feb 2017 00:09:48 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Randall Gellens <rg+ietf@randy.pensive.org>, Bernard Aboba <bernard.aboba@gmail.com>, slim@ietf.org, ietf@ietf.org
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com> <p06240609d4c7e2c0acbf@[99.111.97.136]>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <5625f5e6-740c-6364-1d64-5006a49f0581@omnitor.se>
Date: Tue, 14 Feb 2017 00:09:55 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240609d4c7e2c0acbf@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zM7nQ1wh2WGpP0NKdrPO_rVMVR0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 23:10:02 -0000

Randall,

I prefer that you wait for conclusion on the topic of "silly states".

And I agree with Bernard that we should (and can) be normative and 
explicit in how to interpret all the unusual combinations.

/Gunnar


Den 2017-02-13 kl. 23:26, skrev Randall Gellens:
> At 11:06 AM -0800 2/13/17, Bernard Aboba wrote:
>
>>  Looking over Section 5.4, it seems to me that the title "Silly 
>> States" may not be appropriate, because it mixes discussion of 
>> combinations of media and language that have an "undefined" meaning 
>> with combinations for which normative guidance can be provided  So 
>> rather than having a single "Silly States" section, perhaps we can 
>> have a section on "Undefined States" (for those combinations which 
>> have an undefined meaning) provide normative guidance on defined 
>> combinations elsewhere.
>>
>>
>> <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-06#section-5.4>5.4. 
>> Silly States
>>
>>
>>
>>     It is possible to specify a "silly state" where the language
>>     specified does not make sense for the media type, such as specifying
>>     a signed language for an audio media stream.
>>     An offer MUST NOT be created where the language does not make sense
>>     for the media type.  If such an offer is received, the receiver MAY
>>     reject the media, ignore the language specified, or attempt to
>>     interpret the intent (e.g., if American Sign Language is specified
>>     for an audio media stream, this might be interpreted as a desire to
>>     use spoken English).
>>
>>     A spoken language tag for a video stream in conjunction with an 
>> audio
>>     stream with the same language might indicate a request for
>>     supplemental video to see the speaker.
>>
>>  [BA] Rather than using terms like "might" for combinations that 
>> could have a
>>  defined meaning, I would like to see the specification provide 
>> normative
>>  language on these use cases. In particular, I would like the 
>> specification to describe:
>>
>>  a. What it means when a spoken language tag is included for a video 
>> stream.
>>  Is this to be interpreted as a request for captioning?
>>  b. What it means when a signed language tag is included for an audio 
>> stream.
>>  Is the meaning of this "undefined" and if so, should it be ignored?
>>  c. What it means when a signed language tag is included for a text 
>> stream.
>>
>>  If some of these scenarios are not defined, the specification can say
>>  "this combination does not have a defined meaning" or something like 
>> that.
>
> I will change the section title to "Undefined Combinations" and 
> replace the text with:
>
>    Specifying a non-signed language tag for a video media stream, or a
>    signed language tag for a non-video media stream, is not defined.  An
>    offer with such a combination SHOULD NOT be created.  If such an
>    offer is received, the receiver MAY ignore the language specified.
>
> I think this retains the intent of the old section while avoiding 
> wading into the unclear issue of intent of such combinations.
>

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Mon Feb 13 15:10:15 2017
Return-Path: <doug@ewellic.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D28AB1299EE for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:10:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.786
X-Spam-Level: 
X-Spam-Status: No, score=-3.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 LIuJEXzqLKGD for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 15:10:03 -0800 (PST)
Received: from p3plwbeout03-04.prod.phx3.secureserver.net (p3plsmtp03-04-2.prod.phx3.secureserver.net [72.167.218.216]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9224E1298C6 for <ietf@ietf.org>; Mon, 13 Feb 2017 15:10:02 -0800 (PST)
Received: from localhost ([72.167.218.132]) by p3plwbeout03-04.prod.phx3.secureserver.net with bizsmtp id kPA21u0042rz53401PA20z; Mon, 13 Feb 2017 16:10:02 -0700
X-SID: kPA21u0042rz53401
Received: (qmail 1405 invoked by uid 99); 13 Feb 2017 23:10:02 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.189
User-Agent: Workspace Webmail 6.6.2
Message-Id: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email03.godaddy.com>
From: "Doug Ewell" <doug@ewellic.org>
To: "=?UTF-8?Q?Gunnar=5FHellstr=C3=B6m?=" <gunnar.hellstrom@omnitor.se>, "Bernard Aboba" <bernard.aboba@gmail.com>
Subject: RE: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
Date: Mon, 13 Feb 2017 16:10:00 -0700
Mime-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KCFC9W-Gur2KZxSpTt0C4NAUfaE>
Cc: slim@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 23:10:05 -0000

Gunnar Hellstr=C3=B6m wrote:=0A=0A> But captions overlayed on video in the =
media stream is a used=0A> technology so it would be good to be able to spe=
cify it.=0A> That we cannot do it is again a sad effect of the language tag=
s not=0A> distinguishing between spoken and written modality.=0A=0Ase-Latn =
=3D Swedish written in Latin script=0Ase-Cyrl =3D Swedish written in Cyrill=
ic script=0Ase-Maya =3D Swedish written in Mayan hieroglyphs=0A=0Ase-Zxxx =
=3D Swedish, explicitly not written=0A=0A"se-Zxxx, fi-Latn" =3D content inc=
ludes non-written Swedish plus Finnish=0Awritten in Latin script=0A=0AExamp=
les of multiple streams of content, such as video in one language=0Athat is=
 subtitled in another, call for multiple language tags. That is=0Anot a sho=
rtcoming or failure of the language tag mechanism. See RFC=0A5646, Section =
4.3.=0A=0AAll of this was discussed in the WG by the same parties.=0A=0A> I=
 once had an ambition to try to specify a notation for that to be=0A> added=
 to BCP 47, but did not succeed to get any real discussion going=0A> on the=
 topic. =0A =0AI searched the ietf-languages archives and did not find any =
sort of post=0Aor proposal from you. I forwarded one of your messages from =
SLIM to that=0Alist in November 2015, expecting you to follow up with a pro=
posal, but=0Anothing materialized.=0A =0A--=0ADoug Ewell | Thornton, CO, US=
 | ewellic.org=0A


From nobody Mon Feb 13 15:19:16 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAAD21299EF; Mon, 13 Feb 2017 15:19:05 -0800 (PST)
X-Quarantine-ID: <hjABq6TuFWbF>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 hjABq6TuFWbF; Mon, 13 Feb 2017 15:19:04 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF6D1299E3; Mon, 13 Feb 2017 15:19:02 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Mon, 13 Feb 2017 15:11:14 -0800
Mime-Version: 1.0
Message-Id: <p0624060bd4c7eedd8397@[99.111.97.136]>
In-Reply-To: <5625f5e6-740c-6364-1d64-5006a49f0581@omnitor.se>
References: <CAOW+2du3zqYfS9iu4XjrQ6Rr6B5C50OXk49=u7Wrg0-1TE7QzA@mail.gmail.com> <p06240609d4c7e2c0acbf@[99.111.97.136]> <5625f5e6-740c-6364-1d64-5006a49f0581@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Mon, 13 Feb 2017 15:18:58 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Bernard Aboba <bernard.aboba@gmail.com>, slim@ietf.org, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qCZMjaHPm5w0nCYg4z4UGCE_SVc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 23:19:06 -0000

At 12:09 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:

>  I prefer that you wait for conclusion on the topic of "silly states".
>
>  And I agree with Bernard that we should (and=20
> can) be normative and explicit in how to=20
> interpret all the unusual combinations.

I think we're better off not saying what the=20
meaning is since we do not have a deployed base=20
of experience.  The replacement text allows=20
cooperating implementations to send such states=20
if they wish.  If consensus emerges later as to=20
what such states mean, a revised draft or an=20
extension draft can be published that spells it=20
out.



>  Den 2017-02-13 kl. 23:26, skrev Randall Gellens:
>>  At 11:06 AM -0800 2/13/17, Bernard Aboba wrote:
>>
>>>   Looking over Section 5.4, it seems to me=20
>>> that the title "Silly States" may not be=20
>>> appropriate, because it mixes discussion of=20
>>> combinations of media and language that have=20
>>> an "undefined" meaning with combinations for=20
>>> which normative guidance can be provided  So=20
>>> rather than having a single "Silly States"=20
>>> section, perhaps we can have a section on=20
>>> "Undefined States" (for those combinations=20
>>> which have an undefined meaning) provide=20
>>> normative guidance on defined combinations=20
>>> elsewhere.
>>>
>>>
>>>=20
>>> <https://tools.ietf.org/html/draft-ietf-slim-negotiating-human-language-=
06#section-5.4>5.4.=20
>>> Silly States
>>>
>>>
>>>
>>>      It is possible to specify a "silly state" where the language
>>>      specified does not make sense for the media type, such as specifyin=
g
>>>      a signed language for an audio media stream.
>>>      An offer MUST NOT be created where the language does not make sense
>>>      for the media type.  If such an offer is received, the receiver MAY
>>>      reject the media, ignore the language specified, or attempt to
>>>      interpret the intent (e.g., if American Sign Language is specified
>>>      for an audio media stream, this might be interpreted as a desire to
>>>      use spoken English).
>>>
>>>      A spoken language tag for a video stream in conjunction with an aud=
io
>>>      stream with the same language might indicate a request for
>>>      supplemental video to see the speaker.
>>>
>>>   [BA] Rather than using terms like "might"=20
>>> for combinations that could have a
>>>   defined meaning, I would like to see the specification provide normati=
ve
>>>   language on these use cases. In particular,=20
>>> I would like the specification to describe:
>>>
>>>   a. What it means when a spoken language tag=20
>>> is included for a video stream.
>>>   Is this to be interpreted as a request for captioning?
>>>   b. What it means when a signed language tag=20
>>> is included for an audio stream.
>>>   Is the meaning of this "undefined" and if so, should it be ignored?
>>>   c. What it means when a signed language tag is included for a text str=
eam.
>>>
>>>   If some of these scenarios are not defined, the specification can say
>>>   "this combination does not have a defined meaning" or something like t=
hat.
>>
>>  I will change the section title to "Undefined=20
>> Combinations" and replace the text with:
>>
>>     Specifying a non-signed language tag for a video media stream, or a
>>     signed language tag for a non-video media stream, is not defined.  An
>>     offer with such a combination SHOULD NOT be created.  If such an
>>     offer is received, the receiver MAY ignore the language specified.
>>
>>  I think this retains the intent of the old=20
>> section while avoiding wading into the unclear=20
>> issue of intent of such combinations.
>>
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288
>
>  _______________________________________________
>  SLIM mailing list
>  SLIM@ietf.org
>  https://www.ietf.org/mailman/listinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Please take note:
Do not read this fortune under penalty of law.
Violators will be prosecuted.
(Penal Code sec. 2.3.2 (II.a.))


From nobody Mon Feb 13 15:41:50 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E9301294D6; Mon, 13 Feb 2017 15:41: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7KQzxYG_veh8; Mon, 13 Feb 2017 15:41:47 -0800 (PST)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (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 41A97129461; Mon, 13 Feb 2017 15:41:47 -0800 (PST)
Received: by mail-it0-x242.google.com with SMTP id r141so1288736ita.1; Mon, 13 Feb 2017 15:41:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6uEPmS2TusE1QK8nMRXGjIlL5zJ2WtXgxio3/Y/YPJY=; b=IWKmG+/fOO2+r0rHRIpg8l9vhpsJcGeIH12Se583SXVF9OqxGZV3IiXGlUvStkyLM3 zPSd6mgB6wxdmvGyuRjJ009ecEHmoUfA+bi7yEykpqzU/X6Dv2M/GiWORIiruC+VXQnw 4wSdRIMBvnTHa7RhvBqXF/ovR1PdLiM3zHHdtzqXDcAGbBRNotRcDBhDKpBFyDNmHi7s G342w3fh0gARxYhH9YPpQgQb3u5MxtVQpPWJPVcdB+hc9lByP/NNLKuswQY6maZgO9pN +sfCIOrXN4ygU00vWnZKmicPfo/gObqqlivrTi4uGJhLO4pcnC+7aILpsDDIoXFNEyLG RdGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6uEPmS2TusE1QK8nMRXGjIlL5zJ2WtXgxio3/Y/YPJY=; b=SFqVYJdXL3LgujsjQwS+RZfNlN8aEiS/9RX7LB4H/L2LEZFbXxqQDIJS0fXQgINf/o KaIY26zyg9nqBkQNB3nf3F4z7g6UfIY3JbArFXKwO/fJ7TZOuIujzjiQ+ymFkSiC2SER e8+gQeIu9kFpARRV6vaSwm2AyeddFC8B9BDqs4pOGGi5r8NKHvOBtHPV5RIQvKm2sedS Z/nlwGrA3/79h05ZFjMVPoh5IYPfcEB8v5hC+HDVmflBFvIKa8c20BgpMX0Vv6fN4fBb LUatPhFCUvKIir5UV0L6SjMAZHR/UleEaFmF2iyTqZPJ16f0V1v1VPCeRO3qmaB4xXqD 832Q==
X-Gm-Message-State: AMke39kXbN+Iz5tZ+kl1drpMPdyDanN0jc0uy/5uqrxQ3Llq+UFIrI0rQ6EHAJpCyr7M+g==
X-Received: by 10.99.0.196 with SMTP id 187mr29764956pga.139.1487029306624; Mon, 13 Feb 2017 15:41:46 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id a76sm16574129pfe.131.2017.02.13.15.41.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 15:41:45 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
Date: Mon, 13 Feb 2017 15:41:43 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <17A55E00-8F28-4F1C-9FC8-3D5B9A1D8487@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L28AEl9ehsr2IZWQjau_7abMPrI>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Feb 2017 23:41:48 -0000

> On Feb 13, 2017, at 2:53 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> However, the Interface ID of unicast addresses used for
> Stateless Address Autoconfiguration [RFC4862] is required
> to be 64 bits long.

To my understanding, that is exactly the case with SLAAC. One could use =
the algorithm with any number one chose, but the chosen number is 64. =
Restricting the limitation to algorithms that require such a limitation =
makes sense to me. Extending it from there to algorithms that have no =
such limitation doesn't.=


From nobody Mon Feb 13 16:16:11 2017
Return-Path: <doug@ewellic.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4E7B129436 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 16:16:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 r3mRoncMbbp6 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 16:16:09 -0800 (PST)
Received: from p3plwbeout03-03.prod.phx3.secureserver.net (p3plsmtp03-03-2.prod.phx3.secureserver.net [72.167.218.215]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A558129452 for <ietf@ietf.org>; Mon, 13 Feb 2017 16:16:08 -0800 (PST)
Received: from localhost ([72.167.218.135]) by p3plwbeout03-03.prod.phx3.secureserver.net with bizsmtp id kQG81u0022vs63s01QG8tY; Mon, 13 Feb 2017 17:16:08 -0700
X-SID: kQG81u0022vs63s01
Received: (qmail 30421 invoked by uid 99); 14 Feb 2017 00:16:08 -0000
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"
X-Originating-IP: 208.51.143.189
User-Agent: Workspace Webmail 6.6.3
Message-Id: <20170213171605.665a7a7059d7ee80bb4d670165c8327d.fce7ee4dbe.wbe@email03.godaddy.com>
From: "Doug Ewell" <doug@ewellic.org>
To: "Paul Kyzivat" <paul.kyzivat@comcast.net>, slim@ietf.org, ietf@ietf.org
Subject: RE: [Slim] Last Call: <draft-ietf-slim-negotiating-human-language-06.txt> (Negotiating Human Language in Real-Time Communications) to Proposed Standard
Date: Mon, 13 Feb 2017 17:16:05 -0700
Mime-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RuLKOr2YTlDqqSYSRRqtjqzXi2s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 00:16:10 -0000

Paul Kyzivat wrote:=0A=0A> Gunnar's comment makes multiple points. You have=
 highlighted one of=0A> them and ignored the others.=0A=0ASome of Gunnar's =
points were excellent, such as the observation that the=0Aterminology is in=
consistent as to whether the asterisk is part of the=0Atag.=0A=0AI did not =
attempt to respond to all of Gunnar's points, nor did I think=0Athat was ne=
cessary.=0A=0A> I accept the WG's decision not to address the "preference" =
issue. But=0A> this attachment to the "ugly child", if not addressed, invit=
es getting=0A> IESG LC comments.=0A=0AI'm not sure what this refers to, but=
 I'm happy to refrain from further=0Acomments on this LC if you think they =
might put the draft in jeopardy.=0A=0A--=0ADoug Ewell | Thornton, CO, US | =
ewellic.org=0A


From nobody Mon Feb 13 16:44:24 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E3FE712979D; Mon, 13 Feb 2017 16:44:22 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-pals-mpls-tp-dual-homing-coordination-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
Date: Mon, 13 Feb 2017 16:44:22 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2T1OjgLGJgutMxOKz2V4Z7I82y4>
Cc: draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org, ietf@ietf.org, pals@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 00:44:23 -0000

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-coordination-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-13
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary:

The document is ready. I have few questions, though, that most likely
are obvious to the document authors and to the WG.

Major issues:

None.

Minor issues:

Not really an issue, but more of thinking out loud. There is no text
in Section 3.2. what happens, say, when PE1 sends DHC+Status TLV and
PE2 sends DHC+Switching TLV both reporting a failure of PW1. I am not
sure if this is a relevant case, but I could expect there can be a
sequence of events that cause these DHC messages to cross between PE1
and PE2?

Nits/editorial comments: 

* The document uses few acronyms without expanding them. Those should
be checked.

* In Section 3.2.  s/table 1 ./Table 1.

*  There are multiple occurrences of "table 1" that should be "Table
1".
   There are multiple occurrences of "figure 5" that should be "Figure
5".
   There are multiple occurrences of "figure 1" that should be "Figure
1".

* Section 3.2. says "..using the DHC message above." Since the message
is quite a bit above I would rewrite this as "..using the DHC message
defined in Section 3.1."

* Section 3.2. protection procedures would greatly benefit
clarity/readability having one or two signaling flow figures assisting
the textual description how the PW failures are signaled between the
PEs (using the DHCs and sometimes assisted with OAM messaging).


From nobody Mon Feb 13 16:46:49 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2A9B12944B; Mon, 13 Feb 2017 16:46:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bvTNlRgVh-cD; Mon, 13 Feb 2017 16:46:44 -0800 (PST)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0125.outbound.protection.outlook.com [104.47.42.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0FF4129404; Mon, 13 Feb 2017 16:46:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qcsvxrSQxA1TT4f4nKow61qxkar+GLNltUMle5rE1cA=; b=JDL4bh0aLULq/wVSe5phgXuxz0QuzKdCXUGrqdfkhs8MlRJjzRTDJ2fntPI9GBHYwOHXidudISNsZt2hmQmVU2MVMGFBlvOAG7Y8DP6VqUFYt5V9u6/cxTJ8zuuZuQwV6ay2vBvWG0A0k+T+DPVWKERoHzpd3apTzvTwwQb1t1s=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Tue, 14 Feb 2017 00:46:42 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.0888.030; Tue, 14 Feb 2017 00:46:42 +0000
From: Orit Levin <oritl@microsoft.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
Subject: Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
Thread-Topic: Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
Thread-Index: AdKGUyRrA62VAoYfSbKLtLScPr2Ehw==
Date: Tue, 14 Feb 2017 00:46:42 +0000
Message-ID: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=oritl@microsoft.com; 
x-originating-ip: [73.157.101.212]
x-ms-office365-filtering-correlation-id: 69f771db-ccee-42a5-2c66-08d45472f1be
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:CY1PR0301MB2122; 
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2122; 7:2+yEOnJYaNXXaceTcwyxMOzMSTsm+Hky7X7uYt7Y7IRt27yxadfLblBLWtonNzaOpB4W0mXV0KeeQaQr7l25YFIRkJLbewHnPJha96Ry/b6+7fWxmTNA8lEqwCnusH5JTSQ2zi4+R8C7m2McC8p4c+XU6oaflNQgsEUzmOWtTYj+pwsk2C9yB2iGT6Oj8CgtUr/O6zEiJwd4aTYDk64bQq9uAwZE1iaD3lKJADLUqro/VrJDqr/WY9w40TZOu6Rg7kWKbpF3SIYus+LaOgvkftGRORwui27JuqySuvyGHJiBp0vcVIiuA/gLBtNlWAFkLBn0YrR/eZS2yZsSzS7XQVooTAjAoLlLgO8jGGTLxWAkmoXtpU/+hGCReG6n4WiLwk77BP5IMskYZybQUQ3HPBuAY12bI2p+h+qa389Sj3Gv4aPtVfGz3dNOGlw4PFvLdnQyX10TNrtJzjif8S04go6WNc1SMn07gZG/v1wZrokbwAHqScKGzIRB8YpAx5EbR7ysYbX+mkSBtf7lG5jWn+udbu05Vvedin5pDAL7QFU=
x-microsoft-antispam-prvs: <CY1PR0301MB2122680CF37FD6F06B5DF237AD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123555025)(20161123562025)(20161123564025)(20161123558025)(20161123560025)(6072148); SRVR:CY1PR0301MB2122; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2122; 
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(7916002)(39850400002)(39860400002)(39450400003)(39840400002)(39410400002)(189002)(377424004)(199003)(5005710100001)(6916009)(86612001)(10090500001)(8676002)(33656002)(5630700001)(68736007)(2351001)(106356001)(5660300001)(101416001)(81156014)(81166006)(81003)(10290500002)(2501003)(50986999)(105586002)(54356999)(6436002)(606005)(92566002)(236005)(9686003)(5640700003)(8936002)(25786008)(74316002)(230783001)(8990500004)(7906003)(6506006)(2900100001)(54906002)(55016002)(6306002)(54896002)(66066001)(99286003)(7696004)(7736002)(97736004)(4326007)(122556002)(6116002)(790700001)(102836003)(3846002)(189998001)(86362001)(3280700002)(2906002)(53936002)(110136004)(53946003)(38730400002)(3660700001)(77096006)(579004); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2122; H:CY1PR0301MB2122.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2017 00:46:42.2788 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2122
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lm4HacO3xAuqUTEOtlE4vDb5x6k>
Cc: "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 00:46:47 -0000

--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.



For more information, please see the FAQ at



<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.



Document: draft-ietf-sidr-delta-protocol-06

Reviewer: Orit Levin

Review Date: 2017-02-13

IETF LC End Date: 2017-01-31

IESG Telechat date: (if known)



Summary:

This draft is basically ready for publication. I only suggest adding the ac=
ronym "RRDP" (in brackets) to the title of the document and replacing the e=
xpression "this delta protocol" with "RRDP" in 3.1 and 3.2.

Thanks,

Orit.



--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"ProgId" content=3D"Word.Document">
<meta name=3D"Generator" content=3D"Microsoft Word 15">
<meta name=3D"Originator" content=3D"Microsoft Word 15">
<link rel=3D"File-List" href=3D"cid:filelist.xml@01D28618.986C09C0"><!--[if=
 gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:Zoom>120</w:Zoom>
<w:SpellingState>Clean</w:SpellingState>
<w:TrackMoves/>
<w:TrackFormatting/>
<w:EnvelopeVis/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val=3D"Cambria Math"/>
<m:brkBin m:val=3D"before"/>
<m:brkBinSub m:val=3D"&#45;-"/>
<m:smallFrac m:val=3D"off"/>
<m:dispDef/>
<m:lMargin m:val=3D"0"/>
<m:rMargin m:val=3D"0"/>
<m:defJc m:val=3D"centerGroup"/>
<m:wrapIndent m:val=3D"1440"/>
<m:intLim m:val=3D"subSup"/>
<m:naryLim m:val=3D"undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState=3D"false" DefUnhideWhenUsed=3D"false" DefSem=
iHidden=3D"false" DefQFormat=3D"false" DefPriority=3D"99" LatentStyleCount=
=3D"374">
<w:LsdException Locked=3D"false" Priority=3D"0" QFormat=3D"true" Name=3D"No=
rmal"/>
<w:LsdException Locked=3D"false" Priority=3D"9" QFormat=3D"true" Name=3D"he=
ading 1"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 2"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 3"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 4"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 5"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 6"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 7"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 8"/>
<w:LsdException Locked=3D"false" Priority=3D"9" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" QFormat=3D"true" Name=3D"heading 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index 9"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 1"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 2"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 3"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 4"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 5"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 6"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 7"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 8"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"toc 9"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"header"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footer"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"index heading"/>
<w:LsdException Locked=3D"false" Priority=3D"35" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"caption"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of figures"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"envelope return"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"footnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"line number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"page number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote reference"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"endnote text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"table of authorities"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"macro"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"toa heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Bullet 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Number 5"/>
<w:LsdException Locked=3D"false" Priority=3D"10" QFormat=3D"true" Name=3D"T=
itle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Closing"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Signature"/>
<w:LsdException Locked=3D"false" Priority=3D"1" SemiHidden=3D"true" UnhideW=
henUsed=3D"true" Name=3D"Default Paragraph Font"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"List Continue 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Message Header"/>
<w:LsdException Locked=3D"false" Priority=3D"11" QFormat=3D"true" Name=3D"S=
ubtitle"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Salutation"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Date"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text First Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Note Heading"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Body Text Indent 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Block Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"FollowedHyperlink"/>
<w:LsdException Locked=3D"false" Priority=3D"22" QFormat=3D"true" Name=3D"S=
trong"/>
<w:LsdException Locked=3D"false" Priority=3D"20" QFormat=3D"true" Name=3D"E=
mphasis"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Document Map"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Plain Text"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"E-mail Signature"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Top of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Bottom of Form"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal (Web)"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Acronym"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Address"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Cite"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Code"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Definition"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Keyboard"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Preformatted"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Sample"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Typewriter"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"HTML Variable"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Normal Table"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"annotation subject"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"No List"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Outline List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Simple 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Classic 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Colorful 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Columns 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Grid 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 4"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 5"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 7"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table List 8"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table 3D effects 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Contemporary"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Elegant"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Professional"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Subtle 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 2"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Web 3"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Balloon Text"/>
<w:LsdException Locked=3D"false" Priority=3D"59" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"Table Grid"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Table Theme"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Placeholder Te=
xt"/>
<w:LsdException Locked=3D"false" Priority=3D"1" QFormat=3D"true" Name=3D"No=
 Spacing"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1"/=
>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2"/=
>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading"/=
>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
1"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" Name=3D"Revision"/>
<w:LsdException Locked=3D"false" Priority=3D"34" QFormat=3D"true" Name=3D"L=
ist Paragraph"/>
<w:LsdException Locked=3D"false" Priority=3D"29" QFormat=3D"true" Name=3D"Q=
uote"/>
<w:LsdException Locked=3D"false" Priority=3D"30" QFormat=3D"true" Name=3D"I=
ntense Quote"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 1=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 1"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
2"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 2=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 2"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
3"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 3=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 3"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
4"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 4=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 4"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
5"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 5=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 5"/>
<w:LsdException Locked=3D"false" Priority=3D"60" Name=3D"Light Shading Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"61" Name=3D"Light List Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"62" Name=3D"Light Grid Accent =
6"/>
<w:LsdException Locked=3D"false" Priority=3D"63" Name=3D"Medium Shading 1 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"64" Name=3D"Medium Shading 2 A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"65" Name=3D"Medium List 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"66" Name=3D"Medium List 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"67" Name=3D"Medium Grid 1 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"68" Name=3D"Medium Grid 2 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"69" Name=3D"Medium Grid 3 Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"70" Name=3D"Dark List Accent 6=
"/>
<w:LsdException Locked=3D"false" Priority=3D"71" Name=3D"Colorful Shading A=
ccent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"72" Name=3D"Colorful List Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"73" Name=3D"Colorful Grid Acce=
nt 6"/>
<w:LsdException Locked=3D"false" Priority=3D"19" QFormat=3D"true" Name=3D"S=
ubtle Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"21" QFormat=3D"true" Name=3D"I=
ntense Emphasis"/>
<w:LsdException Locked=3D"false" Priority=3D"31" QFormat=3D"true" Name=3D"S=
ubtle Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"32" QFormat=3D"true" Name=3D"I=
ntense Reference"/>
<w:LsdException Locked=3D"false" Priority=3D"33" QFormat=3D"true" Name=3D"B=
ook Title"/>
<w:LsdException Locked=3D"false" Priority=3D"37" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" Name=3D"Bibliography"/>
<w:LsdException Locked=3D"false" Priority=3D"39" SemiHidden=3D"true" Unhide=
WhenUsed=3D"true" QFormat=3D"true" Name=3D"TOC Heading"/>
<w:LsdException Locked=3D"false" Priority=3D"41" Name=3D"Plain Table 1"/>
<w:LsdException Locked=3D"false" Priority=3D"42" Name=3D"Plain Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"43" Name=3D"Plain Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"44" Name=3D"Plain Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"45" Name=3D"Plain Table 5"/>
<w:LsdException Locked=3D"false" Priority=3D"40" Name=3D"Grid Table Light"/=
>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"Grid Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"Grid Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"Grid Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"Grid Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"Grid Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"Grid Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"Grid Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark"=
/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 1"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 1"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 2"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 2"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 3"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 3"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 4"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 4"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 5"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 5"/>
<w:LsdException Locked=3D"false" Priority=3D"46" Name=3D"List Table 1 Light=
 Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"47" Name=3D"List Table 2 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"48" Name=3D"List Table 3 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"49" Name=3D"List Table 4 Accen=
t 6"/>
<w:LsdException Locked=3D"false" Priority=3D"50" Name=3D"List Table 5 Dark =
Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"51" Name=3D"List Table 6 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" Priority=3D"52" Name=3D"List Table 7 Color=
ful Accent 6"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Mention"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Smart Hyperlink"/>
<w:LsdException Locked=3D"false" SemiHidden=3D"true" UnhideWhenUsed=3D"true=
" Name=3D"Hashtag"/>
</w:LatentStyles>
</xml><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;
	mso-font-charset:1;
	mso-generic-font-family:roman;
	mso-font-pitch:variable;
	mso-font-signature:0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:-536859905 -1073732485 9 0 511 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-unhide:no;
	mso-style-qformat:yes;
	mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-noshow:yes;
	mso-style-priority:99;
	color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	mso-bidi-font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-style-unhide:no;
	mso-ansi-font-size:11.0pt;
	mso-bidi-font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-unhide:no;
	mso-style-locked:yes;
	mso-style-link:"Plain Text";
	mso-bidi-font-size:10.5pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-default-props:yes;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-fareast-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1956404582;
	mso-list-type:hybrid;
	mso-list-template-ids:1772529444 67698703 67698713 67698715 67698703 67698=
713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 10]><style>/* Style Definitions */
table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-priority:99;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-ascii-font-family:Calibri;
	mso-hansi-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
</style><![endif]--><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"tab-interval:.=
5in">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">I am the assigned Gen-ART reviewer for this draft=
. The General Area Review Team (Gen-ART) reviews all IETF documents being p=
rocessed by the IESG for the IETF Chair.<span style=3D"mso-spacerun:yes">&n=
bsp;
</span>Please treat these comments just like any other last call comments.<=
o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">For more information, please see the FAQ at<o:p><=
/o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&lt;<a href=3D"http://wiki.tools.ietf.org/area/ge=
n/trac/wiki/GenArtfaq">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArt=
faq</a>&gt;.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Document: draft-ietf-sidr-delta-protocol-06<o:p><=
/o:p></p>
<p class=3D"MsoPlainText">Reviewer: Orit Levin<o:p></o:p></p>
<p class=3D"MsoPlainText">Review Date: 2017-02-13<o:p></o:p></p>
<p class=3D"MsoPlainText">IETF LC End Date: 2017-01-31<o:p></o:p></p>
<p class=3D"MsoPlainText">IESG <span class=3D"SpellE">Telechat</span> date:=
 (if known)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Summary:<o:p></o:p></p>
<p class=3D"MsoPlainText">This draft is basically ready for publication. I =
only suggest adding the acronym &#8220;RRDP&#8221; (in brackets) to the tit=
le of the document and replacing the expression &#8220;this delta protocol&=
#8221; with &#8220;RRDP&#8221; in 3.1 and 3.2.<o:p></o:p></p>
<p class=3D"MsoPlainText">Thanks,<o:p></o:p></p>
<p class=3D"MsoPlainText">Orit.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span style=3D"mso-ascii-font-family:Calibri;mso-far=
east-font-family:Calibri;mso-hansi-font-family:Calibri;mso-bidi-font-family=
:&quot;Times New Roman&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580CY1PR0301MB2122_--


From nobody Mon Feb 13 17:02:57 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 444EE129497; Mon, 13 Feb 2017 17:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PODCHytKHhxx; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 9D109129401; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 65so81843752otq.2; Mon, 13 Feb 2017 17:02:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QEBURqKCSBHqeVDeaTyUw/AU/WUunC+sXE3guKdOb60=; b=tdSrl1szKdkNeiL95U3lsHOIa15eoF8P/RiwNVIJ+Krv865bP+8gEqGeNzd7Hgll0L 2RrqaMT8jRH2JiFv20N4F67aOsEvEkNm0Vih8PpUM10vAaeLXLP15E3j6z6kX5h5gLDZ I9HgScV39wk2xnOpagVtELevqCQ/2bb+QhpmwaUkaxLreituqC+HvP/27KVPZEypsK+s uuEqHaZ4Jlb9tYz50yzWb8KV50tc2vfEUklkthyVWCZ2XGHeDqvoB4LBplDn9Hkmu7bW 4BtEljY/3XRzCR9o5kYrCP4BKy7o7ncgms/Se4S/b7xQgekQ/gdJZirEYdMiDXDYuhqt eYug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QEBURqKCSBHqeVDeaTyUw/AU/WUunC+sXE3guKdOb60=; b=um52FlSLtcz33Q+TxuOqPh2qSz2oys2nyh1JCOU+E4oXEHSRqzbnGHGkmeyxgtzck7 pAQamvMMCRvw25AxGHhyAbZufAmibUpMWNB4+NzPsHNfJqNs0CuA1QwOQUWGoIvc2mG4 q6DQ+iAeDcqIRa4QwyY0NDI4ozWqDRV5l7e4NmrMR511rnswKIax+2M2OYKHPWJ4xzWy sZV+cxKjbiK8eDE65/B7sDFPXWakmWDqM4jgXzDQU/PRN/h2hO5oq9EmRNwGkqCqz28g Bx8D6eqAeQ5lGdKcP93dyWGZgSh1Qy354/jgKtxQukTgygrv9bJTYQFiEslfzkyPFsT+ ziIA==
X-Gm-Message-State: AMke39k+86MnzichCRqGvPZ7dL9uj+MZQvMkZyzT3FzX3UipumnqaDA8VE2eqY1eOWIhtOA19EixteSFYEuDyQ==
X-Received: by 10.157.17.5 with SMTP id g5mr16747282ote.118.1487034164910; Mon, 13 Feb 2017 17:02:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Mon, 13 Feb 2017 17:02:44 -0800 (PST)
In-Reply-To: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 13 Feb 2017 17:02:44 -0800
Message-ID: <CA+RyBmUW5GvYefTL2X+b1x7W8xhEpuVQHt0AphOyck51Aig1sg@mail.gmail.com>
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a1145009e2b34b20548731f7d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PWUNQnB-zxQxKJ8rooBIX8Xl8iE>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 01:02:47 -0000

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

Hi Robert,
thank you for your review and patience as we've been working on the
document. The text you've proposed is indeed useful to implementer and I'll
add it with the next update.

Regards,
Greg

On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-mpls-residence-time-13
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-01-17
> IESG Telechat date: 2017-03-02
>
> Summary: Ready for publication as PS
>
> Thanks for addressing my comments.
> (I still think some discussion about taking arrival and departure time
> measurements would be helpful, even if it only said "do it
> consistently so you don't indicate jitter that's not really there".)
>
>

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

<div dir=3D"ltr">Hi Robert,<div>thank you for your review and patience as w=
e&#39;ve been working on the document. The text you&#39;ve proposed is inde=
ed useful to implementer and I&#39;ll add it with the next update.=C2=A0</d=
iv><div><br></div><div>Regards,</div><div>Greg</div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, R=
obert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" =
target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Reviewer: Robert Sparks<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-mpls-residence-<wbr>time-13<br>
Reviewer: Robert Sparks<br>
Review Date: 2017-02-13<br>
IETF LC End Date: 2017-01-17<br>
IESG Telechat date: 2017-03-02<br>
<br>
Summary: Ready for publication as PS<br>
<br>
Thanks for addressing my comments.<br>
(I still think some discussion about taking arrival and departure time<br>
measurements would be helpful, even if it only said &quot;do it<br>
consistently so you don&#39;t indicate jitter that&#39;s not really there&q=
uot;.)<br>
<br>
</blockquote></div><br></div>

--001a1145009e2b34b20548731f7d--


From nobody Mon Feb 13 19:09:44 2017
Return-Path: <chengweiqiang@chinamobile.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 004C6129409; Mon, 13 Feb 2017 19:09:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=unavailable autolearn_force=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 KHblW8a4_PqV; Mon, 13 Feb 2017 19:09:41 -0800 (PST)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 282EC129991; Mon, 13 Feb 2017 19:03:51 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec58a27390d0a-8416f; Tue, 14 Feb 2017 11:03:45 +0800 (CST)
X-RM-TRANSID: 2eec58a27390d0a-8416f
X-RM-SPAM-FLAG: 00000000
Received: from cmcc (unknown[10.2.51.86]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee458a2738fe69-56c71; Tue, 14 Feb 2017 11:03:44 +0800 (CST)
X-RM-TRANSID: 2ee458a2738fe69-56c71
From: "Weiqiang Cheng" <chengweiqiang@chinamobile.com>
To: "'Jouni Korhonen'" <jounikor@gmail.com>, <gen-art@ietf.org>
References: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
In-Reply-To: <148703306292.22169.5868946919175397612.idtracker@ietfa.amsl.com>
Subject: Re: [Pals] Review of draft-ietf-pals-mpls-tp-dual-homing-coordination-05
Date: Tue, 14 Feb 2017 11:03:52 +0800
Message-ID: <011201d2866e$f8f2ec40$ead8c4c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AdKGW5D/ERp+i/EBTWC4nomVg8XnNgAExSNA
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/52Ao0888-qBOiWgL5v5QEj8tiF8>
Cc: pals@ietf.org, ietf@ietf.org, draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 03:09:42 -0000

Hi Jouni,
Thank you very much for your careful review and valuable comments.
We authors will fix those issues late.

B.R.
Weiqiang Cheng

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: Pals [mailto:pals-bounces@ietf.org] =B4=FA=B1=ED =
Jouni Korhonen
=B7=A2=CB=CD=CA=B1=BC=E4: 2017=C4=EA2=D4=C214=C8=D5 8:44
=CA=D5=BC=FE=C8=CB: gen-art@ietf.org
=B3=AD=CB=CD: =
draft-ietf-pals-mpls-tp-dual-homing-coordination.all@ietf.org;
ietf@ietf.org; pals@ietf.org
=D6=F7=CC=E2: [Pals] Review of =
draft-ietf-pals-mpls-tp-dual-homing-coordination-05

Reviewer: Jouni Korhonen
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area =
Review
Team (Gen-ART) reviews all IETF documents being processed by the IESG =
for
the IETF Chair.  Please treat these comments just like any other last =
call
comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pals-mpls-tp-dual-homing-coordination-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-13
IETF LC End Date: 2017-02-13
IESG Telechat date: 2017-03-02

Summary:

The document is ready. I have few questions, though, that most likely =
are
obvious to the document authors and to the WG.

Major issues:

None.

Minor issues:

Not really an issue, but more of thinking out loud. There is no text in
Section 3.2. what happens, say, when PE1 sends DHC+Status TLV and
PE2 sends DHC+Switching TLV both reporting a failure of PW1. I am not =
sure
if this is a relevant case, but I could expect there can be a sequence =
of
events that cause these DHC messages to cross between PE1 and PE2?

Nits/editorial comments:=20

* The document uses few acronyms without expanding them. Those should be
checked.

* In Section 3.2.  s/table 1 ./Table 1.

*  There are multiple occurrences of "table 1" that should be "Table 1".
   There are multiple occurrences of "figure 5" that should be "Figure =
5".
   There are multiple occurrences of "figure 1" that should be "Figure =
1".

* Section 3.2. says "..using the DHC message above." Since the message =
is
quite a bit above I would rewrite this as "..using the DHC message =
defined
in Section 3.1."

* Section 3.2. protection procedures would greatly benefit
clarity/readability having one or two signaling flow figures assisting =
the
textual description how the PW failures are signaled between the PEs =
(using
the DHCs and sometimes assisted with OAM messaging).

_______________________________________________
Pals mailing list
Pals@ietf.org
https://www.ietf.org/mailman/listinfo/pals




From nobody Mon Feb 13 20:51:56 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F089129543 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 20:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CQQ_De9lgEmD for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 20:51:54 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37F361294C8 for <ietf@ietf.org>; Mon, 13 Feb 2017 20:51:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487047914; x=1518583914; h=from:to:subject:date:message-id:mime-version; bh=mq2ecNKmR0bt9j8CYAzQ3LIZ+K5TheEDBAXZ5oveCIo=; b=nAmOqWEm1tp2W3LHIdjhr6j4fvl9v8Bm5mmMUE22Qvh4TvuFlyPD+0p0 Hq93+IFmdqAx1126j1MHIvC5UNbFUpK7qjEhGVcZAE2nmJKJC9yVNzhRw qnXYjvQhG2cQIIIhstDzLa3Zxx1WTnhUMCjBWevaP+xH5wY5QpN6kqiNv A=;
X-IronPort-AV: E=Sophos;i="5.35,159,1484035200"; d="scan'208";a="358009939"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by wolverine02.qualcomm.com with ESMTP; 13 Feb 2017 20:51:53 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8438"; a="900035135"
Received: from unknown (HELO [10.64.104.243]) ([10.64.104.243]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 13 Feb 2017 20:51:52 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "IETF discussion list" <ietf@ietf.org>
Subject: To "lose the argument in the WG"
Date: Mon, 13 Feb 2017 22:50:57 -0600
Message-ID: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; markup=markdown
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l4Mi7p-KJanEP1FuEmCDclo6REA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 04:51:55 -0000

Twice in as many days I've seen folks make the argument that a WG 
participant ought not bring up an issue during IETF Last Call that was 
already discussed in the WG because that participant "lost the argument" 
in the WG. I hate the construction, and I think even making the claim 
harms the process.

In one case, it appears that the chair judged that the WG couldn't come 
to consensus on a definitive statement and therefore concluded that a 
compromise statement was appropriate. It is quite appropriate for WG 
participants to say during Last Call, "We think the chair made an error. 
There remains a technical failing in this document that is not 
appropriately addressed by the compromise language. We tried to convince 
the chair of this, to no avail, and hope that others in the community 
review this particular point and maybe try to make the case clearer than 
we were able to." That's going to require some rehashing, though 
hopefully the chair and/or AD can fairly summarize the arguments and why 
they came to the conclusion they did, which should shorten the 
discussion. But the points need to be brought out, the in-the-rough WG 
participants should be able to identify where the perceived error was 
made, and the community can put in its two cents. You can't say, at this 
point, that anyone "lost the argument", and certainly not that they 
ought to be quiet.

(In that particular case, I've also seen people say, "I give up; I'm not 
discussing it anymore". That's a pain, since the issue hasn't gone away, 
even if the proponent has, so the chair or AD is left to make sure it 
gets dealt with without help. We really need to stop that.)

In the other case, my understanding is that the chair and/or AD judged 
that a particular set of functionality was outside of the scope of the 
document and/or chartered-work in question. The WG participant who felt 
that the functionality should be in-scope and is perfectly within bounds 
to make the case that the functionality is somehow necessary during Last 
Call. The chair and/or AD should summarize why they judged the 
functionality to be out of scope. Others in the community might want to 
take up the argument and explain why it should be added. But again, 
saying that the participant cannot make an argument that was "not won" 
in the WG is unreasonable.

Do note that in both cases, I think it's only fair that the person 
bringing up the issue clearly states what's going on. For instance, in 
the second case the person should really have said, "This was judged 
out-of-scope by the WG/chair, but I think it ought not be out-of-scope 
because of X, Y, and Z". Simply saying, "Please make this change to the 
document" as if it were never discussed before is not helpful to the 
rest of the list during Last Call.

In any event, I think it's vital that the chair and/or AD actively 
manage the Last Call discussion when these sorts of things happen. They 
are the judges of consensus, and they are the ones that are going to 
have to make the call in the end, so having them explain their thinking 
is vital.

End of rant.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Mon Feb 13 21:07:29 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 234441295EF for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R0yMkCCKq1Hh for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:07:27 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 812371295DE for <ietf@ietf.org>; Mon, 13 Feb 2017 21:07:27 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1E59935005701 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 13 Feb 2017 21:09:09 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1487048949; bh=ngOBBFEBYHeRXcgN77u3kqxpPWJsBOvbA/nhXQxTlvE=; h=Subject:To:References:From:Reply-To:Date:In-Reply-To:From; b=K1GemZITwLawlc1BZ3XHmGPfVf2LwsoE0MCctbcwcOkahDqo55iSyE8ON9UNWPWXT GGr2R+VTIJELuwS4gcDzgnwzI+P6DYZo+tauc4kAGqytUr7mKJwYWFSeBSDfxkKa9+ xZRBwMNH4j7Ep3bJ58tUXGTe+thjijUZU6JPihQk=
Subject: Re: To "lose the argument in the WG"
To: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
Date: Mon, 13 Feb 2017 21:07:17 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bT_Y-P7gO6q0H_s3jQ3CPs541uQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 05:07:28 -0000

On 2/13/2017 8:50 PM, Pete Resnick wrote:
> The WG participant who felt that the functionality should be in-scope
> and is perfectly within bounds to make the case that the functionality
> is somehow necessary during Last Call. The chair and/or AD should
> summarize why they judged the functionality to be out of scope. Others
> in the community might want to take up the argument and explain why it
> should be added.


This sounds like reasonable theory, but is actually rather destructive 
practice.

It takes the position that Last Call is acceptable to use as a form of 
appeals process, where folk who have been working on the topic for an 
extended time have to defend their choices to a collection of other folk 
who are new to the topic and are, therefore, making snap judgements.

While, yes, there will be times that the new folk see something new or 
better, that's not the usual occurrence.  The usual occurrence is that 
folk who are experienced with the topic and are tired from the extended 
effort have to rehash their work and defend it to folk who have not done 
their homework.

Either working groups are where the work really does get done or they 
aren't.  The burden of having to worry about and deal with a larger, 
less-involved community being frankly encouraged to second-guess the 
folk who have actual skin in the game, is an example of what makes the 
formality of IETF process onerous.

Last Call should not require a working group to be subject to random 
demands to defend itself.  It should be for independent reviews that see 
something the working group missed.  Missed is different from "we had a 
choice and we made it".

If a fresh reviewer really does do their homework and really does 
present a good case for making a different decision, that's fine.  But 
it also is quite different than supporting the re-hashing exercise that 
occurrs when an existing wg participant expresses dissatisfaction with a 
decision made during normal wg processes.

d/

ps. Pete's other point was about a claim that an issue didn't really get 
settled and needs further review.  That's quite a different case.  Maybe 
it's worthy for LC discussion.  Maybe it isn't.  Dunno.

pps. There's at least one case where I chose to attempt to use LC as a 
kind of appeals process, since I deemed the wg process to have been 
significantly flawed, including the cognizant AD.  Like all good rules, 
there need to be some exceptions thoughtfully permitted, though of 
course my effort in this example of an exception bore no fruit...

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Mon Feb 13 21:19:21 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE1B1296D6 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:19:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4f6mxc-kAjgN for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:19:16 -0800 (PST)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::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 7D51B12947B for <ietf@ietf.org>; Mon, 13 Feb 2017 21:19:16 -0800 (PST)
Received: by mail-qk0-x232.google.com with SMTP id 11so112910898qkl.3 for <ietf@ietf.org>; Mon, 13 Feb 2017 21:19:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=QYh9h4ou55ikNdNor67Zr2BYcRpdF04pzWXmIOnE/Qo=; b=NSTeGb34Ge0k34mTYfD2rFh1mJPzk1B4Usd0FQLmhuzURhefDYIPf9PHWrdvx9mver N9sgjl3F0ZYdci0wMunAyuFYzEzsudhYyyhvHps8AhXS5FvGL1wCdTcuG3sUG2VjeOsL qOU4VKFUcd9NzI1O5m4PA6we5rWrVtzcpUW3Yi+ffKhpsQ1nR+weJkLHF3lFw5c2n44U Dg4DJnZAuUIaCZirOrG8VyXqumW/SqpB2g04Zt8Uw5hDrxC8sK49WhHXtpSxjkWM/RyK 1AFXrP1gUSM8TH4A0a7tC9WK4cs0NFvJ3C3B4D5z7m3KsSoo9/IIshYXkO5G2I3dNkdv Gheg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=QYh9h4ou55ikNdNor67Zr2BYcRpdF04pzWXmIOnE/Qo=; b=OEoArSdamRK4cPYLP2ZEZ9fhClAvShwLkZeW6xy39/6OIs6cu/1xrvuPHfebqC8UvW 49ks0ldaqFOSSMmcHkALi2H56VMHdZfcMG90c3f5ppu2XNwAArBv+OpBGiw0qi1VFzzG OSSdC0ryhHd36oV0/6+11TVnPKZgpvGebAzMr2WpX9GtMDifuBtXe1NRcsdKwRhTmJy5 8yjK3T4W/ItK7VmT8VbGVkbeBpTgK/rxYjVMzOFceM3Pnk//3SHpph14u8Bt2eoiObHU uuBfnhzAjedjX7SfQMwZ2ktVI3FKmQ8OcMjMCvPC4EkQD7hj0y49/kx8tjuI89sLUyJe rbZQ==
X-Gm-Message-State: AMke39n/4aPlSsnmksNdAEq9llPs9E9P7Cp9RJRihmdbnUc/r04lV6C2hODByzlBwfcdbQ==
X-Received: by 10.55.123.129 with SMTP id w123mr24887157qkc.20.1487049555486;  Mon, 13 Feb 2017 21:19:15 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 13sm7193363qtn.57.2017.02.13.21.19.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 21:19:14 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <10867D09-9904-4F0D-BCC3-62195C037706@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_807240BD-E34A-4514-9E0B-692D0A70A471"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 00:19:12 -0500
In-Reply-To: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xuT31maTEMlAcM9-xuBze4Q0OKQ>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 05:19:18 -0000

--Apple-Mail=_807240BD-E34A-4514-9E0B-692D0A70A471
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 13, 2017, at 11:50 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
> I think it's only fair that the person bringing up the issue clearly =
states what's going on. For instance, in the second case the person =
should really have said, "This was judged out-of-scope by the WG/chair, =
but I think it ought not be out-of-scope because of X, Y, and Z". Simply =
saying, "Please make this change to the document" as if it were never =
discussed before is not helpful to the rest of the list during Last =
Call.

Since I was one of the people who made that point, I should say that =
"the chair made a mistake" is a different statement than "the working =
group decided, and I was part of that conversation, and I don't agree, =
so let's discuss it again."



--Apple-Mail=_807240BD-E34A-4514-9E0B-692D0A70A471
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 13, 2017, at 11:50 PM, Pete Resnick &lt;<a =
href=3D"mailto:presnick@qti.qualcomm.com" =
class=3D"">presnick@qti.qualcomm.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">I think it's only =
fair that the person bringing up the issue clearly states what's going =
on. For instance, in the second case the person should really have said, =
"This was judged out-of-scope by the WG/chair, but I think it ought not =
be out-of-scope because of X, Y, and Z". Simply saying, "Please make =
this change to the document" as if it were never discussed before is not =
helpful to the rest of the list during Last =
Call.</span></div></blockquote></div><br class=3D""><div class=3D"">Since =
I was one of the people who made that point, I should say that "the =
chair made a mistake" is a different statement than "the working group =
decided, and I was part of that conversation, and I don't agree, so =
let's discuss it again."</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_807240BD-E34A-4514-9E0B-692D0A70A471--


From nobody Mon Feb 13 21:20:04 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9613E1293F2; Mon, 13 Feb 2017 21:19:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TUh48_2MheQo; Mon, 13 Feb 2017 21:19:53 -0800 (PST)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6EDC12947B; Mon, 13 Feb 2017 21:19:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1487049591; bh=oQL8LJ6JXMs2JvYPClb8bnZ1wKrcwZo0B48V KdgI39Q=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=Go617Mm hd1IapmbNf1rZnFYJ+NFgTLvJvJGZSDcoHvEy7FsM1N5YXHLmAM2txhzKj+ct7vGrcq wxrihlgq/Vq9VKfmJePpsctYVGQ4sT7Qp6PTmJY5mL8gALlqNIwzHRwyOcSxBo2nUXf 6THOOVzSTp4EXwndtsVKCzNTKM8ntZX+iCGfQmPX4aj4qHthAQt0aZjUZPcVbAE/Rbt mY691TloIA9Hm4gW7lA3tO3nPx7zyb0t1hXgbgGnyfyN8Yl+//js/BxfqiVBLXr+2j8 sb9UP1t6X/znzX8cjNTkmE3ZNvqg5itiBvrsYAw+ZnKrlxzmH74L5B0aBJUCRBUIi2w ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=DhvR0B69kFGg/8vEOlRmbCkPxhpttcNF9gEzxBAJRqrecxA14mhLcjDE2PoSUH8ljWjrnRcjEvL1zrh/fkYTgDIrc+F3wRVgLfF5DezlgtaS/uf15ScECCBD/xhIVBDr8dCY1bun12qWZMawMNBSJSjlvtePXzThnXLcKT0kadmRAB6Okn87Qs8x00xXkePANsBHOs/iu9g7oVFgk1AWKZ+93b6ImGd1cIui7JpGX5NFFw4i6xXhhhj7vixAfeb3Up5Jl+y85Wr5idXahLTPUF7Xox9MF8ytdvODpOn/o7lD3cOxafZR8xlN95AkfFQqqMqH/jbEJ5+Mz/uaVqEhgw==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-banded.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1cdVWX-0005Kc-CJ; Tue, 14 Feb 2017 00:19:33 -0500
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
To: "Dale R. Worley" <worley@ariadne.com>
References: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <d59427a0-a105-9c10-9de1-86755386d43e@earthlink.net>
Date: Mon, 13 Feb 2017 21:19:27 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <87efz2wzoz.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac7598ed599bdacb1532843c9b011678fe5350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wElIJepMugkfCDlNtfO68GwYRlo>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 05:19:55 -0000

Hello Dale,

Follow-up below...

On 2/12/2017 7:13 PM, Dale R. Worley wrote:
>
>> There is a sort of "hidden" disadvantage to long names, especially for
>> tiny devices using constrained link layers.  Namely, a longer name makes
>> it more likely to require lower-layer fragmentation.  I'm not sure that
>> it should be the job of a layer-3 mobility entity to parse URNs and
>> determine if two different flavors are supposed to be equivalent.
>>
>> Other than that, I don't have any real objection to reorganizing the
>> namespace, but I'd like some additional confirmation that it's a good idea.
> There are a couple of reasons I like this idea.
>
> One is that EPC seems to have a policy of providing a URN form for all
> of the identifier classes it defines.  Making a single URN MNID type
> means that you've incorporated all future classes of identifier that EPC
> defines.
>
> A single URN MNID type would incorporate any of the defined URN
> namespaces that turn out to be useful for anybody.  This isn't so
> interesting for really large deployments, since they could ask for a new
> MNID type, but experimental or small-scale deployments may want to
> define their own identifiers, and URNs provide several convenient ways
> to do that.
>
> It removes a certain amount of redundancy, in that each RFID class now
> has three representations, for a total of 20 MNID types, whereas they
> could all be collapsed into one MNID type.
>
> The negatives I see are:
>
> Some URN schemes do not have a unique representation as a character
> string.  In practice, this is combated by either (1) Code that handles
> URNs of arbitrary namespace copies and compares them as character
> strings.  Users of such systems know to write URNs that have multiple
> representations in a canonical form.  Or, (2) Code that handles one or a
> small fixed set of URN namespaces knows the canonicalization/comparison
> rules for those namespaces.  Generally, using these processes doesn't
> cause problems in practice.  I expect that whatever receives the MNID
> and looks it up in appropriate databases would not be a constrained
> device, so it could process URNs carefully.
>
> If the link layer is constrained, longer identifiers may require
> fragmentation.  Changing a 96-bit binary representation into a URN seems
> to add something like 40 octets, given the examples I've found online.
> OTOH, it seems that the MNID is only transmitted when attaching to a
> network, and so having that one packet require extra work doesn't seem
> to be much of a penalty.
>
> The all-URN ides envisions embedding IMSI and possibly MSISDN into the
> gsma URN namespace.  (IMEI is already embedded as urn:gsma:imei:...)
> That would take additional specification, although I don't see that
> being controversial.  (Andrew Allen <aallen@blackberry.com> would be a
> good contact for doing this.)

I am hesitant to replace so many MNID types by a single URN type with 
substructure.  What would you think about replacing the existing 
RFID-*-URI types with a single URN type, but leaving the existing binary 
types?  This gets the benefit you suggest for future extensibility, but 
retains the shorter forms that may often be advantageous.



>>> 5.  Security Considerations
>>>
>>> The base MNID specification, RFC 4283, gives these security
>>> considerations (sec 4), which ought to be referenced and probably
>>> summarized in this section:
>>>
>>>      Moreover, MNIDs containing sensitive identifiers might only be used
>>>      for signaling during initial network entry.  Subsequent binding
>>>      update exchanges might then rely on a temporary identifier allocated
>>>      during the initial network entry, perhaps using mechanisms not
>>>      standardized within the IETF.  Managing the association between long-
>>>      lived and temporary identifiers is outside the scope of this
>>>      document.
>>>
>>> What is the meaning of the word "might" in paragraph 3?  I suspect
>>> that the purpose is to qualify this paragraph with "One way to
>>> address
>>> these vulnerabilities is to only use MNIDs containing ...".  But if
>>> that is the meaning, that expanded wording should be used.  Otherwise
>>> the text reads as if it is hypothetical.
>> This text was meant to be generally descriptive, so that people wanting
>> to include the Mobile Node Identifier Option with the relevant MNIDs
>> could understand how the identifiers are actually used in various
>> circumstances.  I could replace constructions using "might" with "in
>> some specifications" or "in some situations" if needed.  Is it also
>> necessary to include citations to the relevant documents of the external
>> SDO?
> I'd definitely prefer some other term than "might".  I'm not sure why,
> but I think that it's because "might" isn't used much in specifications
>
> ....

I changed the text as follows:

>     Some MNIDs contain sensitive identifiers which, as used in protocols
>     specified by other SDOs, are only used for signaling during initial
>     network entry.  In such protocols, subsequent exchanges then rely on
>     a temporary identifier allocated during the initial network entry.
>     Managing the association between long-lived and temporary identifiers
>     is outside the scope of this document.


I can't remember exactly why this text was added - it was a long time 
ago.  But anyway the main point is to simply mention that there may be 
associations between some of the MNID types that might be important from 
a security standpoint, without meaning to go into examples.

Regards,
Charlie P.


From nobody Mon Feb 13 21:25:29 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280541299A6 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:25:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov0us-vu4_rm for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 21:25:26 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DC17129680 for <ietf@ietf.org>; Mon, 13 Feb 2017 21:25:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487049926; x=1518585926; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=2L9CIbYnRadjbu4GlEZSv5KYhvE+dxRpPnBHwUdwTsw=; b=A12C2RTsCsmWtZrMNKK3OIlptnHBC+2SmJFd5D7NasXbDCDu3tDWsilz 4IcTy1O1JDwJUFj9RNBObs1fSv6Gmpk4myzC45NKR2v5bSGohWpQ5hq8V FetQ1hT8jNhSsQ/Tb1FOxgwQQJBkngmO+4J+SlXxY+suYaNlII+IJl7Qe M=;
X-IronPort-AV: E=Sophos;i="5.35,159,1484035200";  d="scan'208,217";a="358013707"
Received: from unknown (HELO ironmsg02-L.qualcomm.com) ([10.53.140.109]) by wolverine02.qualcomm.com with ESMTP; 13 Feb 2017 21:25:03 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8438"; a="866297730"
Received: from unknown (HELO [10.64.121.67]) ([10.64.121.67]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 13 Feb 2017 21:25:01 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: dcrocker@bbiw.net
Subject: Re: To "lose the argument in the WG"
Date: Mon, 13 Feb 2017 23:25:00 -0600
Message-ID: <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com>
In-Reply-To: <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_495708F6-2CDD-485C-945A-975185162DC3_="
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mGCtkubQViCuXfuhU3VUPwNF8C4>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 05:25:28 -0000

--=_MailMate_495708F6-2CDD-485C-945A-975185162DC3_=
Content-Type: text/plain; format=flowed; markup=markdown

On 13 Feb 2017, at 23:07, Dave Crocker wrote:

> On 2/13/2017 8:50 PM, Pete Resnick wrote:
>> The WG participant who felt that the functionality should be in-scope
>> and is perfectly within bounds to make the case that the 
>> functionality
>> is somehow necessary during Last Call. The chair and/or AD should
>> summarize why they judged the functionality to be out of scope. 
>> Others
>> in the community might want to take up the argument and explain why 
>> it
>> should be added.
>
>
> This sounds like reasonable theory, but is actually rather destructive 
> practice.
>
> It takes the position that Last Call is acceptable to use as a form of 
> appeals process, where folk who have been working on the topic for an 
> extended time have to defend their choices to a collection of other 
> folk who are new to the topic and are, therefore, making snap 
> judgements.
>
> While, yes, there will be times that the new folk see something new or 
> better, that's not the usual occurrence.  The usual occurrence is that 
> folk who are experienced with the topic and are tired from the 
> extended effort have to rehash their work and defend it to folk who 
> have not done their homework.
>
> Either working groups are where the work really does get done or they 
> aren't.  The burden of having to worry about and deal with a larger, 
> less-involved community being frankly encouraged to second-guess the 
> folk who have actual skin in the game, is an example of what makes the 
> formality of IETF process onerous.
>
> Last Call should not require a working group to be subject to random 
> demands to defend itself.  It should be for independent reviews that 
> see something the working group missed.  Missed is different from "we 
> had a choice and we made it".
>
> If a fresh reviewer really does do their homework and really does 
> present a good case for making a different decision, that's fine.  But 
> it also is quite different than supporting the re-hashing exercise 
> that occurrs when an existing wg participant expresses dissatisfaction 
> with a decision made during normal wg processes.

Would that we disagreed.

Nowhere did I say that Last Call should be an opportunity to simply 
rehash, without having done homework. Indeed, you will note where I 
said:

>> Do note that in both cases, I think it's only fair that the person 
>> bringing up the issue clearly states what's going on. For instance, 
>> in the second case the person should really have said, "This was 
>> judged out-of-scope by the WG/chair, but I think it ought not be 
>> out-of-scope because of X, Y, and Z". Simply saying, "Please make 
>> this change to the document" as if it were never discussed before is 
>> not helpful to the rest of the list during Last Call.

For a WG participant to just throw out the same argument made earlier 
without explanation *and* with the expectation that the WG ought be 
required to relitigate the whole discussion is *not* reasonable. The 
case needs to be made that the WG (or the chair in judging) did in fact 
miss something when they came to rough consensus. The chair, not the 
entire WG, should explain why the conclusion was arrived at. (That 
should really be written up in the shepherd report, if we're being 
diligent.) Others can choose to ask questions or push back on either 
position if they think something serious has been missed. But to 
dismiss, out of hand, any such claim with "too late, already decided" is 
also unreasonable.

Homework is required. Pointing out the failure is required. Avoiding 
simply restating a preference is required. I'm just objecting to the 
blanket statement, "If the WG came to consensus, even roughly, the 
discussion is over."

(As I said earlier, in the case of something being declared 
out-of-scope, I'd expect the person bringing up the point to explain why 
being in-scope was essential. To fail to do so is bogus.)

> ps. Pete's other point was about a claim that an issue didn't really 
> get settled and needs further review.  That's quite a different case.  
> Maybe it's worthy for LC discussion.  Maybe it isn't.  Dunno.
>
> pps. There's at least one case where I chose to attempt to use LC as a 
> kind of appeals process, since I deemed the wg process to have been 
> significantly flawed, including the cognizant AD.  Like all good 
> rules, there need to be some exceptions thoughtfully permitted, though 
> of course my effort in this example of an exception bore no fruit...

I also agree that this should be fairly unusual. Again, what got to me 
was the automatic rejection of such an argument.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_495708F6-2CDD-485C-945A-975185162DC3_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 13 Feb 2017, at 23:07, Dave Crocker wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">On 2/13/2017 8:50 PM, Pete Resnick wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">The WG participant who felt that the functionality should=
 be in-scope<br>
and is perfectly within bounds to make the case that the functionality<br=
>
is somehow necessary during Last Call. The chair and/or AD should<br>
summarize why they judged the functionality to be out of scope. Others<br=
>
in the community might want to take up the argument and explain why it<br=
>
should be added.</p>
</blockquote>

<p dir=3D"auto">This sounds like reasonable theory, but is actually rathe=
r destructive practice.</p>

<p dir=3D"auto">It takes the position that Last Call is acceptable to use=
 as a form of appeals process, where folk who have been working on the to=
pic for an extended time have to defend their choices to a collection of =
other folk who are new to the topic and are, therefore, making snap judge=
ments.</p>

<p dir=3D"auto">While, yes, there will be times that the new folk see som=
ething new or better, that's not the usual occurrence.  The usual occurre=
nce is that folk who are experienced with the topic and are tired from th=
e extended effort have to rehash their work and defend it to folk who hav=
e not done their homework.</p>

<p dir=3D"auto">Either working groups are where the work really does get =
done or they aren't.  The burden of having to worry about and deal with a=
 larger, less-involved community being frankly encouraged to second-guess=
 the folk who have actual skin in the game, is an example of what makes t=
he formality of IETF process onerous.</p>

<p dir=3D"auto">Last Call should not require a working group to be subjec=
t to random demands to defend itself.  It should be for independent revie=
ws that see something the working group missed.  Missed is different from=
 "we had a choice and we made it".</p>

<p dir=3D"auto">If a fresh reviewer really does do their homework and rea=
lly does present a good case for making a different decision, that's fine=
=2E  But it also is quite different than supporting the re-hashing exerci=
se that occurrs when an existing wg participant expresses dissatisfaction=
 with a decision made during normal wg processes.</p>
</blockquote>

<p dir=3D"auto">Would that we disagreed.</p>

<p dir=3D"auto">Nowhere did I say that Last Call should be an opportunity=
 to simply rehash, without having done homework. Indeed, you will note wh=
ere I said:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">Do note that in both cases, I think it's only fair that t=
he person bringing up the issue clearly states what's going on. For insta=
nce, in the second case the person should really have said, "This was jud=
ged out-of-scope by the WG/chair, but I think it ought not be out-of-scop=
e because of X, Y, and Z". Simply saying, "Please make this change to the=
 document" as if it were never discussed before is not helpful to the res=
t of the list during Last Call.</p>
</blockquote>
</blockquote>

<p dir=3D"auto">For a WG participant to just throw out the same argument =
made earlier without explanation <em>and</em> with the expectation that t=
he WG ought be required to relitigate the whole discussion is <em>not</em=
> reasonable. The case needs to be made that the WG (or the chair in judg=
ing) did in fact miss something when they came to rough consensus. The ch=
air, not the entire WG, should explain why the conclusion was arrived at.=
 (That should really be written up in the shepherd report, if we're being=
 diligent.) Others can choose to ask questions or push back on either pos=
ition if they think something serious has been missed. But to dismiss, ou=
t of hand, any such claim with "too late, already decided" is also unreas=
onable.</p>

<p dir=3D"auto">Homework is required. Pointing out the failure is require=
d. Avoiding simply restating a preference is required. I'm just objecting=
 to the blanket statement, "If the WG came to consensus, even roughly, th=
e discussion is over."</p>

<p dir=3D"auto">(As I said earlier, in the case of something being declar=
ed out-of-scope, I'd expect the person bringing up the point to explain w=
hy being in-scope was essential. To fail to do so is bogus.)</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">ps. Pete's other point was about a claim that an issue di=
dn't really get settled and needs further review.  That's quite a differe=
nt case.  Maybe it's worthy for LC discussion.  Maybe it isn't.  Dunno.</=
p>

<p dir=3D"auto">pps. There's at least one case where I chose to attempt t=
o use LC as a kind of appeals process, since I deemed the wg process to h=
ave been significantly flawed, including the cognizant AD.  Like all good=
 rules, there need to be some exceptions thoughtfully permitted, though o=
f course my effort in this example of an exception bore no fruit...</p>
</blockquote>

<p dir=3D"auto">I also agree that this should be fairly unusual. Again, w=
hat got to me was the automatic rejection of such an argument.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_495708F6-2CDD-485C-945A-975185162DC3_=--


From nobody Mon Feb 13 22:02:07 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDAC1294EF for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 22:02:05 -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 autolearn_force=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 JWFi2H6Rw1Gd for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 22:02:04 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 830DA12940B for <ietf@ietf.org>; Mon, 13 Feb 2017 22:02:04 -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)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id DAF9E349476; Tue, 14 Feb 2017 06:02:01 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id C48E6160053; Tue, 14 Feb 2017 06:02:01 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id AFE54160050; Tue, 14 Feb 2017 06:02:01 +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 Ma5Lz9EJydym; Tue, 14 Feb 2017 06:02:01 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 0FCC016004C; Tue, 14 Feb 2017 06:02:01 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 73B32639AEDF; Tue, 14 Feb 2017 17:01:56 +1100 (EST)
To: dcrocker@bbiw.net
From: Mark Andrews <marka@isc.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
Subject: Re: To "lose the argument in the WG"
In-reply-to: Your message of "Mon, 13 Feb 2017 21:07:17 -0800." <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
Date: Tue, 14 Feb 2017 17:01:56 +1100
Message-Id: <20170214060156.73B32639AEDF@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6M3cQvTSP2HKcvk95TDklc5j3Is>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 06:02:05 -0000

In message <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>, Dave Crocker wr
ites:
> On 2/13/2017 8:50 PM, Pete Resnick wrote:
> > The WG participant who felt that the functionality should be in-scope
> > and is perfectly within bounds to make the case that the functionality
> > is somehow necessary during Last Call. The chair and/or AD should
> > summarize why they judged the functionality to be out of scope. Others
> > in the community might want to take up the argument and explain why it
> > should be added.
> 
> 
> This sounds like reasonable theory, but is actually rather destructive 
> practice.
> 
> It takes the position that Last Call is acceptable to use as a form of 
> appeals process, where folk who have been working on the topic for an 
> extended time have to defend their choices to a collection of other folk 
> who are new to the topic and are, therefore, making snap judgements.
> 
> While, yes, there will be times that the new folk see something new or 
> better, that's not the usual occurrence.  The usual occurrence is that 
> folk who are experienced with the topic and are tired from the extended 
> effort have to rehash their work and defend it to folk who have not done 
> their homework.

And workgroups get it wrong.

I gave up trying to convince behave that the DNS64 DNSSEC processing
was insane.  Validating clients send both <DO=1,CD=1> and <DO=1,CD=0>
queries.  You can't expect synthesised AAAA response to be accepted
with either set of flags.  They wanted a flag that said that the
client is validating and that DOES NOT EXIST in DNSSEC.  DO=1 say
a client MAY be validating.  DO=0 indicates that it is NOT validating.
CD is independent of whether the client is validating or not.  Lots
of wishful thinking when that section was written.

I also gave up trying to get 5.9. "Always Set the CD Bit on Queries"
removed from the draft for RFC 6840.  Named totally ignores that
section because it just plain bad advice.  Recursive servers need
to honour CD as originally specified or there are failure modes
that are not recoverable when some of the authorative servers are
broken or the recursive server is under attack unless CD is
controllable.

You need to be able to control validation in the entire chain of
recursive servers for DNSSEC to work.  There are a number of different
failure senarios in DNSSEC.  Some require CD=1 to recover from (if
you initially set CD=0), some require CD=0 to recover from (if you
initially sent CD=1).  In both cases CD needs to passed down the
entire chain for the recovery to work.

Should I have raise these again at IETF last call?

Mark

> Either working groups are where the work really does get done or they 
> aren't.  The burden of having to worry about and deal with a larger, 
> less-involved community being frankly encouraged to second-guess the 
> folk who have actual skin in the game, is an example of what makes the 
> formality of IETF process onerous.
> 
> Last Call should not require a working group to be subject to random 
> demands to defend itself.  It should be for independent reviews that see 
> something the working group missed.  Missed is different from "we had a 
> choice and we made it".
> 
> If a fresh reviewer really does do their homework and really does 
> present a good case for making a different decision, that's fine.  But 
> it also is quite different than supporting the re-hashing exercise that 
> occurrs when an existing wg participant expresses dissatisfaction with a 
> decision made during normal wg processes.
> 
> d/
> 
> ps. Pete's other point was about a claim that an issue didn't really get 
> settled and needs further review.  That's quite a different case.  Maybe 
> it's worthy for LC discussion.  Maybe it isn't.  Dunno.
> 
> pps. There's at least one case where I chose to attempt to use LC as a 
> kind of appeals process, since I deemed the wg process to have been 
> significantly flawed, including the cognizant AD.  Like all good rules, 
> there need to be some exceptions thoughtfully permitted, though of 
> course my effort in this example of an exception bore no fruit...
> 
> -- 
> 
>    Dave Crocker
>    Brandenburg InternetWorking
>    bbiw.net
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb 13 23:06:33 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42CE3129A1F for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:06:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 e5NtO4D-5KQN for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:06:18 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 78C911294FD for <ietf@ietf.org>; Mon, 13 Feb 2017 23:06:18 -0800 (PST)
X-Halon-ID: 0e14430b-f284-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Tue, 14 Feb 2017 08:06:06 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Doug Ewell <doug@ewellic.org>, Bernard Aboba <bernard.aboba@gmail.com>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email03.godaddy.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se>
Date: Tue, 14 Feb 2017 08:06:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email03.godaddy.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wXYcVq9cfx3C1fb1wNNSOM_loHQ>
Cc: slim@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 07:06:21 -0000

Doug,

Thanks for pointing at the Zxxx script subtag for non-written content.

I think we can document the use of it for the view of a speaker in video 
media when indicated by a spoken/written language tag.

I have tried before to propose to use the script subtag to indicate 
written language, but got opposition because many languages have their 
main script subtag suppressed. However, the language around suppressed 
script subtags indicate that there are cases when the use is 
appropriate. We  can document that text captions in the video stream 
shall (or should) be indicated with a script subtag.

But, to keep it simple, the use of Zxxx scrit subtag on the view of a 
speaker should be sufficient.

That could conclude the unusual combinations:

1. Spoken/written tag in video media, can mean to see a speaking person, 
or to provide captions overlayed on video.

When the intention is to indicate overlayed captions in the video 
stream, the script subtag Zxxx SHALL be used.

Otherwise, a view of a speaking person is indicated.

2. Signed language tag in audio media,
means audio from a person using sign language, and SHOULD only be used 
for rare cases when it has some relevance for language communication.

3. Sign language tag in text media.

SHALL be used for any approximate text coded representation of sign 
language or fingerspelling.

I suggest that these conclusions form the base for a redefined section 5.4.

--------------------------------------------------------------------------
About my efforts to discuss modality in the language list: The list was 
closed when I tried to subscribe or send to it, and I did not see any 
response on a question I sent about how to get a discussion on the 
modality topic.

But I am happy now with your pointing out the Zxxx script. a 
spoken/written language with Zxxx script is quite obviously not written 
and not signed, so then it is spoken. Good.

Thanks

Gunnar


Den 2017-02-14 kl. 00:10, skrev Doug Ewell:
> Gunnar Hellström wrote:
>
>> But captions overlayed on video in the media stream is a used
>> technology so it would be good to be able to specify it.
>> That we cannot do it is again a sad effect of the language tags not
>> distinguishing between spoken and written modality.
> se-Latn = Swedish written in Latin script
> se-Cyrl = Swedish written in Cyrillic script
> se-Maya = Swedish written in Mayan hieroglyphs
>
> se-Zxxx = Swedish, explicitly not written
>
> "se-Zxxx, fi-Latn" = content includes non-written Swedish plus Finnish
> written in Latin script
>
> Examples of multiple streams of content, such as video in one language
> that is subtitled in another, call for multiple language tags. That is
> not a shortcoming or failure of the language tag mechanism. See RFC
> 5646, Section 4.3.
>
> All of this was discussed in the WG by the same parties.
>
>> I once had an ambition to try to specify a notation for that to be
>> added to BCP 47, but did not succeed to get any real discussion going
>> on the topic.
>   
> I searched the ietf-languages archives and did not find any sort of post
> or proposal from you. I forwarded one of your messages from SLIM to that
> list in November 2015, expecting you to follow up with a proposal, but
> nothing materialized.
>   
> --
> Doug Ewell | Thornton, CO, US | ewellic.org
>
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Mon Feb 13 23:29:04 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 797101294A9 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:29:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cyh_XvSmteAk for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:29:01 -0800 (PST)
Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::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 E5EC812947A for <ietf@ietf.org>; Mon, 13 Feb 2017 23:29:00 -0800 (PST)
Received: by mail-wr0-x235.google.com with SMTP id i10so163839891wrb.0 for <ietf@ietf.org>; Mon, 13 Feb 2017 23:29:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=lQHHJwnVygxHXSlJqK0vON325f75LrN9+2YsWiFpvsw=; b=vXQbermmjIvlOUaD8nbfgSe5vEx8wl652Hccvv2VyxrLIQSr3KSeugqhX/KCfcDLcn yWtoU+3PA13yI7vVGVtOnJC1r5wF1x6BhEkCKj7KzNhZ7lDztu30UlwlMQwTRQEwWAn2 D2FLUj2zfhJV0QE/wLeEHpJxqch/wIiHzN2St39aUPTMq6BI4ZNV0nJKrpy2mWFKbfNi QS3GeMJtTrcG/IJSBkbyx2pbuEHZMD35ww/7hcciGHPJeTvg9J04LU+zpMsVSUG7HJ42 Ew1ASKMjltAzh8a6ffGIg3g+MeOd5TTe1QLsANm3Y1zXOA8oYxNAWtuY1Ozujp0Tli1V 912g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=lQHHJwnVygxHXSlJqK0vON325f75LrN9+2YsWiFpvsw=; b=Dwjnr5Q+JoBS7f0BLVjacLqegWwRaubDtyyJlpEnjBXEpvsMIlz4IZc1v/MQ+z6I6p G3igNZUHbPI9+PgehL2kvweYi6neJF8/7nJuj+cv2xI6W/zYxcR1l1b5fgUQtRi6auF6 Ugr5gpWGRGjDkWLObhskj5Iqvb8KU4kRJDoMDKXH1R5E5yL+1agBLyj/pbfMo4Nij2Qn /ETomSQk2MQ9W+S3ruYZvTKVdSBIPmWv0hIH/heLvCPAmrRfYkBMgAmksN+JZ8L84UNw 69XtQ5IgzowfOKTruHulpKbkFwCFSLM1cZXGgw9C6WQfQYv0YjUN9pZuRg3bq0dr7PG1 JJ5A==
X-Gm-Message-State: AMke39kux9N6Rbpaw24RTScGLYSn9D6T5VvD+aQFzt1j95OL533PG5SqoFmUyhtgQ2OOJQ==
X-Received: by 10.223.163.81 with SMTP id d17mr23285870wrb.93.1487057339351; Mon, 13 Feb 2017 23:28:59 -0800 (PST)
Received: from [192.168.137.219] ([109.253.229.215]) by smtp.gmail.com with ESMTPSA id e71sm75356wma.8.2017.02.13.23.28.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Feb 2017 23:28:58 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_176808A1-A3CB-4CDF-90D8-ABAA551BCDDA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 09:28:53 +0200
In-Reply-To: <20170214060156.73B32639AEDF@rock.dv.isc.org>
To: Mark Andrews <marka@isc.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/86yLCYfODCAS3ONTz0E7XtlFheY>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Dave CROCKER <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 07:29:02 -0000

--Apple-Mail=_176808A1-A3CB-4CDF-90D8-ABAA551BCDDA
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_B4CBF689-90F7-4783-BA32-4775E43DCFC2"


--Apple-Mail=_B4CBF689-90F7-4783-BA32-4775E43DCFC2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 14 Feb 2017, at 8:01, Mark Andrews <marka@isc.org> wrote:
>=20
>=20
> And workgroups get it wrong.
>=20
> I gave up trying to convince behave that the DNS64 DNSSEC processing
> was insane.

<snip />

> Should I have raise these again at IETF last call?

If at IETF LC you said something along the lines of =E2=80=9CThe =
specification does this, and I think it=E2=80=99s insane because XXX. It =
was raised in the WG [1] but was rejected [2],[3].  I still think it=E2=80=
=99s insane and that the spec should not go forward as it is.=E2=80=9D

I think that would be fine, but anyone jumping to agree with you would =
be properly asked why they didn=E2=80=99t participate in the WG. In any =
case, it could be useful input for the IESG who are the ultimate judges =
of IETF consensus.

Yoav



--Apple-Mail=_B4CBF689-90F7-4783-BA32-4775E43DCFC2
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""><br class=3D""><div><div class=3D"">On 14 Feb 2017, at 8:01, =
Mark Andrews &lt;<a href=3D"mailto:marka@isc.org" =
class=3D"">marka@isc.org</a>&gt; wrote:</div><blockquote type=3D"cite" =
class=3D""><br class=3D"Apple-interchange-newline"><div class=3D""><br =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">And workgroups get it wrong.</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><br style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">I gave up trying to convince behave that =
the DNS64 DNSSEC processing</span><br style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">was insane. &nbsp;</span><br =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""></div></blockquote><div><br =
class=3D""></div>&lt;snip /&gt;</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Should I have raise =
these again at IETF last call?</span><br class=3D""></div></blockquote><br=
 class=3D""></div><div>If at IETF LC you said something along the lines =
of =E2=80=9CThe specification does this, and I think it=E2=80=99s insane =
because XXX. It was raised in the WG [1] but was rejected [2],[3]. =
&nbsp;I still think it=E2=80=99s insane and that the spec should not go =
forward as it is.=E2=80=9D</div><div><br class=3D""></div><div>I think =
that would be fine, but anyone jumping to agree with you would be =
properly asked why they didn=E2=80=99t participate in the WG. In any =
case, it could be useful input for the IESG who are the ultimate judges =
of IETF consensus.</div><div><br class=3D""></div><div>Yoav</div><div><br =
class=3D""></div><br class=3D""></body></html>=

--Apple-Mail=_B4CBF689-90F7-4783-BA32-4775E43DCFC2--

--Apple-Mail=_176808A1-A3CB-4CDF-90D8-ABAA551BCDDA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYorG2AAoJELhJCxUKWMyZUvgH/0BMrxj+Rs6rpxLdPrXG4ip4
CSNRemy3Vx7l14nduH8B+oTPsDyiBZmUNe1a8Phm2lAmhh9eDdqOgvxv/3S/DhAC
01ZofRuYbCXQHXbcf1jlsAe7NyMAOYwcQpxcqk7fJRLryQtLuIuWcLw6kpZKclmJ
sfB408Bb0Yl/qP+Z35Ain7H0OomdoYmaIybdYEOWD7etZ/684XIxz/+UKPHX18jb
VNibEjJXb3dy3O0c+yjBnJaoYqJ3L3/JczexpHPOtToiZwtzk1GODl9l5qWeySEH
zqwYvmkD5DRK2+usVZzvSguTtUY5vMlxpxpdsL8x/S5tnYrfniVFSF5w5qfAWHc=
=cIvf
-----END PGP SIGNATURE-----

--Apple-Mail=_176808A1-A3CB-4CDF-90D8-ABAA551BCDDA--


From nobody Mon Feb 13 23:43:23 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CFD21294A9 for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:43: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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 Ll-KGusIq3Xx for <ietf@ietfa.amsl.com>; Mon, 13 Feb 2017 23:43:19 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB5AF1204D9 for <ietf@ietf.org>; Mon, 13 Feb 2017 23:43:19 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdXlc-000GLj-DA; Tue, 14 Feb 2017 02:43:16 -0500
Date: Tue, 14 Feb 2017 02:43:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net
Subject: Re: To "lose the argument in the WG"
Message-ID: <C8DC848672108BF32D41ADAC@PSB>
In-Reply-To: <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iRclKztc1bLjY9tAoJV47-P7R9o>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 07:43:21 -0000

Pete,

I'm probably going to regret being drawn into this, but I think
you (and Dave) are missing two additional cases, ones that
complicate your analysis considerably even if  they don't change
your key conclusion.

As the Internet and IETF evolve, I see increasing frequency of
very homogenous WGs, ones whose active participants consist
entirely, or almost entirely, of people who represent one
perspective and who are narrowly focused on that WG's topic
area.  I addition to all of the usual possibilities, including
the ones you mentioned, such WGs run multiple risks.  To keep
this from becoming over-long, the one that probably represents
the case we see most often goes like this...

The WG reaches fairly strong consensus on a particular set of
issues, with only one or two people in the minority, taking
positions the WG has decided are not interesting or not
relevant.  In that case, unless we require omniscience as well
as fairness of WG Chairs, there is no error: the WG has reached
rough consensus on a topic and those one or two participants are
in the rough _within_ the WG.   For that case, if IETF Last Call
and the idea of cross-area review are to be more than rituals to
support our mythology, it is absolutely necessary that someone
who participated in the WG be able to come to IETF Last Call and
say "look, the perspective of the WG was too narrow and, as a
consequence, these issues that affect other things didn't get a
reasonable hearing and the IETF as a whole should really
reexamine them independent of the conclusions the WG reached
(and/or the community should reexamine whether the WG was, in
retrospect, properly chartered, constituted, and composed and,
if not, whether its consensus and request for document
publication should be taken seriously,

FWIW, I believe that "strong consensus, but still wrong" was one
of the cases you addressed with RFC 7282.

I think that "too homogeneous a WG and too narrow a perspective"
argument, if plausibly explained and justified, has to be taken
serious even if there are no (other) new arguments or additional
"homework".    I also think it is a particularly difficult type
of problem because, if the consensus recommendation from such a
WG to publish a document is accepted, it reflects badly on the
AD who authorized the Last Call as well as on the WG and its
leadership.  While it doesn't make "I lost the argument in the
WG" is not helpful as a means of ending the conversation, "I
lost the argument in the WG for what I believe were the
following reasons ... and the IETF should review those issues"
may be exactly what we need to hear as part of document review.

That argument is very different from either "the WG CHair made
an error" or "I was on the losing side and I want to keep
whining about it and rehash the argument".

Whether IETF Last Call is the right way to deal what that type
of issue is a separate question.   You and others have heard me
say from time to time that we don't have nearly enough appeals.
I think ADs should be monitoring WGs for sufficient technical
diversity and range of perspectives and that someone
participating in a WG who believes that the profile of
participants in the WG is too narrow to encourage or allow
arguing against WG conclusions on the basis of broader Internet
considerations (whether decisions about WG scope get involved or
not) should be encouraged to discuss that issue with the
relevant AD and, if necessary carry the appeals process further,
rather than quibbling about specific technical issues on Last
Call.  However, success in such an appeal would probably require
shutting down a WG that has an active mailing list and meetings
and is producing results.  Our track record for such shutdowns
is fairly close to non-existent.

That same argument for appeals applies when people who are not
part of the homogeneous majority are treated dismissively or
otherwise discouraged from continuing to participate.  We ought
to be able to deal with those situations as instances of
bullying, but if that has ever worked successfully, I'm not
aware of it -- maybe you know of examples that I don't.

Where I think we agree is that, while there should be a
presumption that a WG that produces a draft and claims consensus
for it has done its work and gotten it right, that presumption
should not be very strong, should be easy to challenge, and that
the position of someone who disagreed with the WG decision
should not be dismissed on that basis.

best,
    john






From nobody Tue Feb 14 00:40:58 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C970112952F for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 00:40:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 78wauuLQLcsi for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 00:40:56 -0800 (PST)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 382E3129546 for <ietf@ietf.org>; Tue, 14 Feb 2017 00:40:56 -0800 (PST)
Received: by mail-wm0-x243.google.com with SMTP id u63so2355317wmu.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 00:40:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=pgS6uBgyNVNLNbew8D3mW4/tGm+8/gVnqgXVWoalq3Y=; b=sn8dikzSElLmySEsPUXd9SJ5ob9sqFLQr/DcX7ecE9fsmi6E77YJMfdfwcA9OdQOK7 86Qxoq/VY7Ou4siiFE+QVdOaLjA19YOYcGUtjwy6QUteyUA1FybIWHr4KvuBTDohtHTz ctXYVnA/YsutPYsTzPCfl9aCJK2YtTpVsPkFR+9DDbnbVWCvUhCZfpHH6FcaOBOSeoA6 erZsaanRA2S9pTVWYOZ4BmJxxKmEpzm189Vq5FhsNIIahFok7E84RgCiBp9nef4z1ZO8 gHWz2yqdYSLYZtxbpLtHcFwgSq/7al+Qiu0c+i2NUDfavecE6rgo/RvfRTMk5hCjCYvG k+Ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=pgS6uBgyNVNLNbew8D3mW4/tGm+8/gVnqgXVWoalq3Y=; b=d/x0ny17UHgUqn5cYDiuZcLj4j+VeM24Mpj8dxefmPD6URvjx0sw/QBb1DEfnA8sZZ 8gbfHEUVj3uSXHfmJlvXQtQB56I1GbzPPdGvDtR9vgQScSp270sLdS8TUuNXsxItZeOI 1Kld2UKpApEH+ZxuCiVCEolszUfgWdiHb8z4q1nPZk3/Tsp6EfMG/dUwhHiGZ9afzQ1r 8RhU5UNtvnMPR3l0e7hsOQ7IoKGXvJGUu5qC5XaZag3NkmuYNCyNapWxrmQQM2RtxqJG +PT52J7/YKnwBrPDT1k6jrFMQg46Xcu2ju3KISObqp3kBMDGvY5VgVydMHP8m57S/q9d MRzw==
X-Gm-Message-State: AMke39lDkWP2Re6PMCDzDfTBv5m9rpq0tTGVLoFSyIFmyxQpwiJPgtsi2c0Q0Sf6QCoDVw==
X-Received: by 10.28.182.6 with SMTP id g6mr1972695wmf.11.1487061654706; Tue, 14 Feb 2017 00:40:54 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id o2sm16955152wra.42.2017.02.14.00.40.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 00:40:54 -0800 (PST)
Subject: Re: To "lose the argument in the WG"
To: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com> <C8DC848672108BF32D41ADAC@PSB>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <bce0454f-9c51-b5ca-3270-19486f72c972@gmail.com>
Date: Tue, 14 Feb 2017 08:40:50 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <C8DC848672108BF32D41ADAC@PSB>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uGz68ir6HrNaNHj4AhPnP-nB9Mk>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 08:40:58 -0000

On 14/02/2017 07:43, John C Klensin wrote:
> Where I think we agree is that, while there should be a
> presumption that a WG that produces a draft and claims consensus
> for it has done its work and gotten it right, that presumption
> should not be very strong, should be easy to challenge, and that
> the position of someone who disagreed with the WG decision
> should not be dismissed on that basis.

Yes, it is the prospect of a complete re-run of the argument at IETF LC
that keeps WGs honest.

We have to accept the real possibility that fresh eyes on the text
or fresh ears listening to the contra-arguments may consider the WG
to have made an incorrect decision. That is the whole purpose of
IETF LC, and we should do nothing to constrain this important
element of our quality control process.

- Stewart



From nobody Tue Feb 14 00:50:34 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E505129546 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 00:50:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 jN4ly-xbIkFQ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 00:50:31 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 A668F12947A for <ietf@ietf.org>; Tue, 14 Feb 2017 00:50:30 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1E8oR0p027082 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:50:27 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A659E201E20 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:50: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 9D3D2201DF3 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:50: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 v1E8oRAG010104 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:50:27 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <2d64ffef-9e03-6191-d319-22d88d31a470@gmail.com>
Date: Tue, 14 Feb 2017 09:49:54 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Wdi10jpKzkbYaZWEo747JU7Uo_4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 08:50:32 -0000

Hi Brian,

With all due respect, but this is my comment:

Le 13/02/2017 à 23:53, Brian E Carpenter a écrit :
> At an earlier stage I suggested restricting the applicability
> of the "However..." sentence to SLAAC [RFC4862]. A short way
> of doing this would be
>
> However, the Interface ID of unicast addresses used for
> Stateless Address Autoconfiguration [RFC4862] is required
> to be 64 bits long.

SLAAC RFC4862 does _not_ require that IID to be 64bit long.  It is 
RFC2464 IP/Eth which requires it so.  And that RFC is being updated also.

I am very much against continuing with this 64bit limit.

I am struggling on at least two different occasions, with two different 
deployments, because of this 64bit limit.

Smiley :-)

Alex

>
> Regards
>    Brian
>
> On 14/02/2017 11:32, David Farmer wrote:
>> I have concerns with the following text;
>>
>>    IPv6 unicast routing is based on prefixes of any valid length up to
>>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>>    on inter-router point-to-point links. However, the Interface ID of
>>    all unicast addresses, except those that start with the binary value
>>    000, is required to be 64 bits long.  The rationale for the 64 bit
>>    boundary in IPv6 addresses can be found in [RFC7421]
>>
>> The third sentence seems to limit exceptions to 64 bit IIDs to exclusively
>> addresses that start with binary vale of 000.  There are at least two other
>> exceptions from standards track RFCs, that should be more clear accounted
>> for in this text.  First is [RFC6164] point-to-point links, as mentioned in
>> the previous sentence.  I think the clear intent of [RFC6164] is to allow
>> one(1) Bit IIDs for point to point-to-point links using any Global Unicast
>> Address, not just those that start with 000.  Second is, [RFC6052], which
>> updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
>> Global Unicast Address when used for IPv4/IPv6 translation, referred to as
>> ""Network-Specific Prefix" unique to the organization deploying the address
>> translators," in section 2.2 of [RFC6052].
>>
>> Thanks.
>>
>> On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org> wrote:
>>
>>>
>>> The IESG has received a request from the IPv6 Maintenance WG (6man) to
>>> consider the following document:
>>> - 'IP Version 6 Addressing Architecture'
>>>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>>>
>>> The IESG plans to make a decision in the next few weeks, and solicits
>>> final comments on this action. Please send substantive comments to the
>>> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
>>> sent to iesg@ietf.org instead. In either case, please retain the
>>> beginning of the Subject line to allow automated sorting.
>>>
>>> Abstract
>>>
>>>
>>>    This specification defines the addressing architecture of the IP
>>>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
>>>    model, text representations of IPv6 addresses, definition of IPv6
>>>    unicast addresses, anycast addresses, and multicast addresses, and an
>>>    IPv6 node's required addresses.
>>>
>>>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>>>    Architecture".
>>>
>>>
>>>
>>>
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>>>
>>> IESG discussion can be tracked via
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
>>>
>>>
>>> No IPR declarations have been submitted directly on this I-D.
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------
>>> 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 Tue Feb 14 01:59:24 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F531298C1; Tue, 14 Feb 2017 01:59:22 -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 autolearn_force=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 0Dp7elkb36nJ; Tue, 14 Feb 2017 01:59:21 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13E151294C4; Tue, 14 Feb 2017 01:59:16 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdZtD-000HGz-Kq; Tue, 14 Feb 2017 04:59:15 -0500
Date: Tue, 14 Feb 2017 04:59:08 -0500
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: Last Call: <draft-freytag-lager-variant-rules-02.txt> (Variant Rules) to Informational RFC
Message-ID: <ED9D6B23A636DFCB94044ABD@PSB>
In-Reply-To: <148467380280.32070.11213613399948034139.idtracker@ietfa.amsl.com>
References: <148467380280.32070.11213613399948034139.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZvDlEQEclIYcNB9ece3p2nk2hO4>
Cc: alexey.melnikov@isode.com, draft-freytag-lager-variant-rules@ietf.org, =?UTF-8?Q?Patrik_F=C3=A4ltstr=C3=B6m?= <patrik@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 09:59:23 -0000

--On Tuesday, January 17, 2017 09:23 -0800 The IESG
<iesg-secretary@ietf.org> wrote:

> 
> The IESG has received a request from an individual submitter
> to consider the following document:
> - 'Variant Rules'
>   <draft-freytag-lager-variant-rules-02.txt> as Informational
> RFC
> 
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action. Please send
> substantive comments to the ietf@ietf.org mailing lists by
> 2017-02-14. 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.

Summary: This document should not be published in the IETF
Stream, at least in its present form, proposed status, and
relationship to other documents.  An explanation and some
alternatives appear below. 

Details:

This is a difficult document for me to review for multiple
reasons, including a conviction that the intentions are the
very best but that the document is artificially constrained by
essentially political decisions taken outside the IETF or any
other process that would meet traditional IETF criteria for
openness, transparency, fairness, and rough consensus.

For IETF decision-making, a largely procedural issue is as, or
perhaps more, important.  The document bears a relationship to
the standards-track RFC 7940 that is confusing at best.   The
"Document Quality" section of the proposed approval notice
starts "The document largely reflects experience gathered from
implementing RFC 7940 and creating rulesets based on it".  That
is a worthy goal and entirely consistent with the "rough
consensus and running code" principle.  The author has done
what I believe is a laudable job of coming up with a
semi-mathematical and testable alternative to the rather
lengthy, complex, and less easily validated and texted, XML of
RFC 7940.

If the document were submitted to the ISE as a "I think this
would be a better way to do things while meeting the same goals
as RFC 7940" or even as "this is what ICANN is doing (or
proposes to do) and the community should know about it" piece,
I'd have little or no objection to it.  However, as an IETF
stream document that apparently is intended to replace (or at
least provide an alternative to) large sections of 7940 with a
different strategy, either 

  -- it should be a standards-track document that explicitly
	updates and replaces those portions of 7940, with all of
	the documentation and explanation the IESG requires of such
	updates.  OR

 -- it should be a standards-track document that provides an
	alternative to 7940 and that explains the choices and
	tradeoffs.

As an IETF Stream Informational specification, it is an
apparent IETF Informational document that encourages the
practice of something other than an IETF Proposed Standard that
addresses the same topics and requirements, with no
Applicability Statement or other guidance as to when or if it
should be applied.

I do not believe it should be published on that basis.

Without descending into details and nitpicking, there are also a
pair of technical problems.

(1) As RFC 7940 points out, the concept of "variant" and hence
the relationships needed to express the "increased
requirements of contemporary IDN variant policies" [RFC7940,
Section 9] has moved considerably beyond the definition of that
term and concept in RFC 3743 (aka "the JET specification").
This document further refines the description of those
relationships.  However, if one is going to move beyond the JET
concept -- one tailored to the relationship between Simplified
and Traditional Chinese characters and not about, e.g., visual
confusion at all -- it is not clear that there is a technical
basis for saying "these things are variants and those others
are not".  The "others" can include synonyms, translations,
orthographic variations that cannot be expressed in simple
character (or even character sequence) mappings, and so on.  

ICANN made a serious of decisions (IMO, some of them almost by
accident and others by side-effect or more political reasons)
as to what kinds of relationships might be considered variant
candidates, at least for the root zone.  The grammar proposed
in this document (and the one of 7940) exclude those other,
non-ICANN-sanctioned, relationships and cannot, in general,
represent them in spite of the fact that they might be quite
appropriate (as least for blocking) in non-root zones and have
been used in exactly that way (indeed, two of the key areas of
friction between IDNA2008 and Unicode UTS #46 can be seen in
exactly those terms).    To a certain extent, that is a
criticism of 7940 rather than this document, but there is an
important difference, at least IMO: The grammar of 7940 is
essentially descriptive and, like most good XML structures,
could easily be expanded with additional elements or element
components if the need arose.  It is far less clear how one
would expand a quasi-mathematical grammar, especially one that
is heavily dependent on special operator symbos and strict
typologies, like this one.  Even if one were to figure out how
to expand this as requirements evolve outside ICANN's control,
such extensions would raise questions of how to keep this
document and 7940 synchronized.  That issue might be another
reason for standards track status and either a more explicit
discussion of relationships and mapping; one or more IANA
registries or operators, types, and elements; or both.

(2) Independent of the web and the convenience of HTTP redirect
facilities, it is not only not clear how to implement delegated
variants in a way taht is not damaging to the Internet and the
DNS.  The opportunities for combinatorial explosion and
consequent operational and zone management problems in all but
a few very special cases (including, historically, the one that
at least some of the JET designers had in mind) are
considerable.  The ICANN solution of "just delegate them all to
the same party and make it their problem" may be satisfactory
from their corporate point of view, but is not a way to make
the Internet work better, especially in the context of
potentially hundreds of names that have to be kept synchronized
in a way that leads to consistent behavior across all
protocols.  RFC 7940 exposes some of this problem as well, but,
again, is rather more descriptive than this document, which
moves much closer to a set of executable tests that establish
what is valid (and presumably reasonable) and what is not. 

I, and a few others, have suggested in other contexts that
"variant" has become part of a magical ritual in which one looks
at a complex DNS-related problem, solemnly chants the word a
propitious number of times, and the problem is then assumed to
disappear or be solved.  The issues above are only a few of the
cases to which variations on that ritual have been applied.
Unless the IETF has better solutions than magic, it should not
be legitimizing the magical thinking by publishing documents
that appear to encourage delegation of "variants".

Two additional nits, the first an important procedural one and
both to provide illustrative examples that this document would
need work even if none of the considerations above applied.

(i) At least since RFC 3552, we have not allowed documents in
the IETF stream that say "There are no security considerations
for this memo.".   And yet that is exactly what Section 18 has
to say.

(ii) Section 16 ("Corresponding XML Notation") is a good idea, 
but, rather than providing a comprehensive mapping, it
essentially says "here are some examples of the mapping between
notations; everything else is left as an exercise for the
reader".  I think that is confusing and unfortunate but, if it
really is what the IETF and the author want to do, it should be
made much more explicit.


thanks,
   John Klensin




From nobody Tue Feb 14 01:59:58 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783261294C4; Tue, 14 Feb 2017 01:59:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CFxRgFf09we0; Tue, 14 Feb 2017 01:59:44 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 1273A129416; Tue, 14 Feb 2017 01:50:41 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id r18so2634974wmd.3; Tue, 14 Feb 2017 01:50:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=mmZ3mA+s6xe9pbQ7REALZWgqnwuowm0B9vu9jbK6CaE=; b=WrTXm9+lv9xun1UBXmS62jZZuC2zlEPyMiSUlklbovWr7Pk0MX1Ml+5PmXkv+0YrnA np2kthZg1wgvYTCf85MR0l2D9JDXro7K3jT1uo2oqoVQpnFmczvmajg9GdcBaMgmSsY9 jj8ZP2sdd7gS9QWL0COQdrGz9/xbQiLchtM194a3I+qsbm4AqbeVZBmzaAhXW7h4zNcB KeJYVb9hokQsoHiMBqWVPsMmTeQAPaL7QcMZKDhR6q2fpgy+N2KW1/7kxCq4JEjfMHrz peKPBT1vRSLitF7qvVcq/89vU85CZi67QYp401+HlOjpvp+VAPZcDYi5BYDiU1r3N9h8 OJ4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=mmZ3mA+s6xe9pbQ7REALZWgqnwuowm0B9vu9jbK6CaE=; b=NZ2erBaFpihXTQCm4HMuTQwvQ8q9bRSxftZK+S/58qvzNAp8k5WrZtp1Zq0qcZd5S5 GuTu2EVKv3v5GykpShetvFpoW1M3CbSLwB8xP9InDB6Rdh/ih321xp0i0VAjQ+SXee1q ggihsDUfK/kBFeDerjtvO2asqdlPW1e31HpiTx03ha60pszgIR3eaWP6l8/fEMPekE+D pveFafEORVJVcvCpDQEJY5Rxyse+6v2ygbilEs2Gdd/kCgOYMIqRnxlf7PEVi6c3S1HB DCaCOlJxqnM8h8ygO94NBTRs1SXHVi71EsGVHCPvnkX1oMdeHBqMANcrIN4U9dTNkw9Q j46w==
X-Gm-Message-State: AMke39kNBC1xLNWohuiueheEtznB6El8hw/r5zG9duNmTZMJczwBxIgODoTY/OjAhjHNPQ==
X-Received: by 10.28.140.140 with SMTP id o134mr2418826wmd.87.1487065839261; Tue, 14 Feb 2017 01:50:39 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 136sm514751wms.32.2017.02.14.01.50.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 01:50:38 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
Date: Tue, 14 Feb 2017 09:50:37 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CmjGYU19VSoh2A27ktgeubNCVTY>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 09:59:46 -0000

Hi Fred

Looks like a good point on RFC4821.

As to you first point remember that the convergence process disrupts the 
traffic flow as it does so, and that this will repeat every 10 mins as 
it tries to re-optimise.

- Stewart


On 10/02/2017 15:38, Templin, Fred L wrote:
> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
> converge to the minimum MTU of all paths in the multipath, and so it is
> still OK to store the MTU in the network layer where it would be shared
> by all flows.
>
> ECMP does present challenges for RFC4821, however. If a first transport
> session discovers a large MTU and shares it with a second transport
> session, the second session may take a very different path where there
> is a smaller MTU and encounter a black hole. IMHO, it might be a good
> idea to file an erratum to RFC4821 explaining how ECMP might cause
> problems if discovered MTUs are shared between sessions.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> -----Original Message-----
>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>> Sent: Friday, February 10, 2017 2:21 AM
>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>
>>
>>
>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>> Stewart,
>>>
>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>> ...
>>>> I wonder if we would best serve both our future and our heritage
>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>> or declared it as historic and wrote a new text from a clean start?
>>> I don't see that. It's a stable, widely deployed, interoperable
>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>> across the Internet.
>> I will not debate whether it is faulty or not, but it seems that in
>> practice the
>> Internet breaks the mechanism. However it breaks it is a way that seems
>> disruptive to some user traffic. The document is really guidance
>> one how hosts might use  ICMP for optimization, and arguable need
>> not be a standard at all.
>>
>> My remark about heritage is that this vintage draft is very much a
>> product of
>> its time, and really needs modernizing, and after modernizing ought to
>> look quite different, and thus maybe we should employ a procedure
>> other than a simple replacement.
>>
>>
>>> ...
>>>> It is concerning that the draft does not talk in any detail about
>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>> the PMTU may be different depending on the transport layer port
>>>> numbers.
>>> Has this problem been analysed for, say, IPv4? And does the real world
>>> contain ECMP setups with different MTUs on different paths?
>> I don't know if anyone has looked. Since the mechanism is
>> self-correcting albeit
>> with some disruption to user traffic it looks to the application and the
>> application
>> user, just like the Internet not working for a few moments.
>>
>> In a well managed SP network there should not be, but neither should there
>> be asymmetric path costs, but there are. The less well manage private
>> networks are less well managed.
>>
>>
>>>> Given that a very large fraction of packets will traverse an MPLS
>>>> network at some point, I am surprised that there is no text talking
>>>> about the importance of providing support for this feature in the
>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>> I don't understand. How does the fact that there might be some MPLS
>>> segments along the path affect end-to-end PMTUD?
>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>> and the
>> PE has to fragment or has to reply with an ICMP error message to support
>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>> result
>> in the right response at the end node.
>>
>> My point is that the draft is silent on the subject, and perhaps it
>> should not be.
>>
>> However your question make me ask a further question. The draft is also
>> silent
>> on NATs. Is there any advice needed for people designing and configuring
>> NATs?
>>
>>>> ======
>>>>
>>>>      If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>      could use the flow id as the local representation of a path. Packets
>>>>      sent to a particular destination but belonging to different flows may
>>>>      use different paths, with the choice of path depending on the flow
>>>>      id.  This approach will result in the use of optimally sized packets
>>>>      on a per-flow basis, providing finer granularity than PMTU values
>>>>      maintained on a per-destination basis.
>>>>
>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>> SB> and thus routers tended to glean information from the packet themselves.
>>> This is future-proofing. Agreed, usage today is limited.
>>>
>>> (But it would be better to call it the Flow Label for consistency with other
>>> recent RFCs.)
>> Well the question is whether it is simply limited today, or broken today
>> in a manner that
>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>> approach
>> is the five-tuple. There is something akin to the flow label being
>> deployed in MPLS. However
>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>> removed) by the
>> service provider and is therefore trusted by the service provider.
>>
>>> I think your other comments are all valuable.
>> Thank you.
>>
>> Stewart
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 02:01:54 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DECE6129564 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 02:01:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 aFQWaX6U65jC for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 02:01:50 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 00ABA129416 for <ietf@ietf.org>; Tue, 14 Feb 2017 02:01:49 -0800 (PST)
X-Halon-ID: 97e150fd-f29c-11e6-af90-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Tue, 14 Feb 2017 11:01:45 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Bernard Aboba <bernard.aboba@gmail.com>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email03.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se>
Date: Tue, 14 Feb 2017 11:01:45 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se>
Content-Type: multipart/alternative; boundary="------------2CC544CEA01C203ECDFDC8F6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hH6W4OMi48WZGmUn_EOeQSP5_5I>
Cc: slim@ietf.org, ietf@ietf.org, Doug Ewell <doug@ewellic.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 10:01:53 -0000

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

My proposal for a reworded section 5.4 is:

5.4.  Unusual language indications

It is possible to specify an unusual indication where the language
specified may look unexpected for the media type.

For such cases the following guidance SHALL be applied for the 
humintlang attributes used in these situations.

 1. A view of a speaking person in the video stream SHALL, when it has
    relevance for speech perception, be indicated by a Language-Tag for
    spoken/written language with the "Zxxx" script subtag to indicate
    that the contents is not written.

 2. Text captions included in the video stream SHALL be indicated by a
    Language-Tag for spoken/written language.

 3. Any approximate representation of sign language or fingerspelling in
    the text media stream SHALL be indicated by a Language-Tag for a
    sign language in text media.

 4. When sign language related audio from a person using sign language
    is of importance for language communication, this SHALL be indicated
    by a Language-Tag for a sign language in audio media.

-------------------------------------------------------------------------------
This paragraph in 5.2 should be deleted because it is a duplication.

"   Note that while signed language tags are used with a video stream to
    indicate sign language, a spoken language tag for a video stream in
    parallel with an audio stream with the same spoken language tag
    indicates a request for a supplemental video stream to see the
    speaker."

Regards

Gunnar

Den 2017-02-14 kl. 08:06, skrev Gunnar Hellström:
> Doug,
>
> Thanks for pointing at the Zxxx script subtag for non-written content.
>
> I think we can document the use of it for the view of a speaker in 
> video media when indicated by a spoken/written language tag.
>
> I have tried before to propose to use the script subtag to indicate 
> written language, but got opposition because many languages have their 
> main script subtag suppressed. However, the language around suppressed 
> script subtags indicate that there are cases when the use is 
> appropriate. We  can document that text captions in the video stream 
> shall (or should) be indicated with a script subtag.
>
> But, to keep it simple, the use of Zxxx scrit subtag on the view of a 
> speaker should be sufficient.
>
> That could conclude the unusual combinations:
>
> 1. Spoken/written tag in video media, can mean to see a speaking 
> person, or to provide captions overlayed on video.
>
> When the intention is to indicate overlayed captions in the video 
> stream, the script subtag Zxxx SHALL be used.
>
> Otherwise, a view of a speaking person is indicated.
>
> 2. Signed language tag in audio media,
> means audio from a person using sign language, and SHOULD only be used 
> for rare cases when it has some relevance for language communication.
>
> 3. Sign language tag in text media.
>
> SHALL be used for any approximate text coded representation of sign 
> language or fingerspelling.
>
> I suggest that these conclusions form the base for a redefined section 
> 5.4.
>
> -------------------------------------------------------------------------- 
>
> About my efforts to discuss modality in the language list: The list 
> was closed when I tried to subscribe or send to it, and I did not see 
> any response on a question I sent about how to get a discussion on the 
> modality topic.
>
> But I am happy now with your pointing out the Zxxx script. a 
> spoken/written language with Zxxx script is quite obviously not 
> written and not signed, so then it is spoken. Good.
>
> Thanks
>
> Gunnar
>
>
> Den 2017-02-14 kl. 00:10, skrev Doug Ewell:
>> Gunnar Hellström wrote:
>>
>>> But captions overlayed on video in the media stream is a used
>>> technology so it would be good to be able to specify it.
>>> That we cannot do it is again a sad effect of the language tags not
>>> distinguishing between spoken and written modality.
>> se-Latn = Swedish written in Latin script
>> se-Cyrl = Swedish written in Cyrillic script
>> se-Maya = Swedish written in Mayan hieroglyphs
>>
>> se-Zxxx = Swedish, explicitly not written
>>
>> "se-Zxxx, fi-Latn" = content includes non-written Swedish plus Finnish
>> written in Latin script
>>
>> Examples of multiple streams of content, such as video in one language
>> that is subtitled in another, call for multiple language tags. That is
>> not a shortcoming or failure of the language tag mechanism. See RFC
>> 5646, Section 4.3.
>>
>> All of this was discussed in the WG by the same parties.
>>
>>> I once had an ambition to try to specify a notation for that to be
>>> added to BCP 47, but did not succeed to get any real discussion going
>>> on the topic.
>>   I searched the ietf-languages archives and did not find any sort of 
>> post
>> or proposal from you. I forwarded one of your messages from SLIM to that
>> list in November 2015, expecting you to follow up with a proposal, but
>> nothing materialized.
>>   --
>> Doug Ewell | Thornton, CO, US | ewellic.org
>>
>>
>> _______________________________________________
>> SLIM mailing list
>> SLIM@ietf.org
>> https://www.ietf.org/mailman/listinfo/slim
>

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>My proposal for a reworded section 5.4 is:</p>
    <p>5.4.  Unusual language indications<br>
    </p>
    <p>It is possible to specify an unusual indication where the
      language<br>
      specified may look unexpected for the media type.</p>
    <p>For such cases the following guidance SHALL be applied for the
      humintlang attributes used in these situations.</p>
    <ol>
      <li>A view of a speaking person in the video stream SHALL, when it
        has relevance for speech perception, be indicated by a
        Language-Tag for spoken/written language with the "Zxxx" script
        subtag to indicate that the contents is not written.<br>
        <br>
      </li>
      <li>Text captions included in the video stream SHALL be indicated
        by a Language-Tag for spoken/written language.<br>
        <br>
      </li>
      <li>Any approximate representation of sign language or
        fingerspelling in the text media stream SHALL be indicated by a
        Language-Tag for a sign language in text media.<br>
        <br>
      </li>
      <li>When sign language related audio from a person using sign
        language is of importance for language communication, this SHALL
        be indicated by a Language-Tag for a sign language in audio
        media.  <br>
      </li>
    </ol>
-------------------------------------------------------------------------------<br>
    This paragraph in 5.2 should be deleted because it is a duplication.<br>
    <br>
    "   Note that while signed language tags are used with a video
    stream to<br>
       indicate sign language, a spoken language tag for a video stream
    in<br>
       parallel with an audio stream with the same spoken language tag<br>
       indicates a request for a supplemental video stream to see the<br>
       speaker."<br>
    <br>
    Regards<br>
    <br>
    Gunnar<br>
    <br>
    <div class="moz-cite-prefix">Den 2017-02-14 kl. 08:06, skrev Gunnar
      Hellström:<br>
    </div>
    <blockquote
      cite="mid:ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se"
      type="cite">Doug,
      <br>
      <br>
      Thanks for pointing at the Zxxx script subtag for non-written
      content.
      <br>
      <br>
      I think we can document the use of it for the view of a speaker in
      video media when indicated by a spoken/written language tag.
      <br>
      <br>
      I have tried before to propose to use the script subtag to
      indicate written language, but got opposition because many
      languages have their main script subtag suppressed. However, the
      language around suppressed script subtags indicate that there are
      cases when the use is appropriate. We  can document that text
      captions in the video stream shall (or should) be indicated with a
      script subtag.
      <br>
      <br>
      But, to keep it simple, the use of Zxxx scrit subtag on the view
      of a speaker should be sufficient.
      <br>
      <br>
      That could conclude the unusual combinations:
      <br>
      <br>
      1. Spoken/written tag in video media, can mean to see a speaking
      person, or to provide captions overlayed on video.
      <br>
      <br>
      When the intention is to indicate overlayed captions in the video
      stream, the script subtag Zxxx SHALL be used.
      <br>
      <br>
      Otherwise, a view of a speaking person is indicated.
      <br>
      <br>
      2. Signed language tag in audio media,
      <br>
      means audio from a person using sign language, and SHOULD only be
      used for rare cases when it has some relevance for language
      communication.
      <br>
      <br>
      3. Sign language tag in text media.
      <br>
      <br>
      SHALL be used for any approximate text coded representation of
      sign language or fingerspelling.
      <br>
      <br>
      I suggest that these conclusions form the base for a redefined
      section 5.4.
      <br>
      <br>
--------------------------------------------------------------------------
      <br>
      About my efforts to discuss modality in the language list: The
      list was closed when I tried to subscribe or send to it, and I did
      not see any response on a question I sent about how to get a
      discussion on the modality topic.
      <br>
      <br>
      But I am happy now with your pointing out the Zxxx script. a
      spoken/written language with Zxxx script is quite obviously not
      written and not signed, so then it is spoken. Good.
      <br>
      <br>
      Thanks
      <br>
      <br>
      Gunnar
      <br>
      <br>
      <br>
      Den 2017-02-14 kl. 00:10, skrev Doug Ewell:
      <br>
      <blockquote type="cite">Gunnar Hellström wrote:
        <br>
        <br>
        <blockquote type="cite">But captions overlayed on video in the
          media stream is a used
          <br>
          technology so it would be good to be able to specify it.
          <br>
          That we cannot do it is again a sad effect of the language
          tags not
          <br>
          distinguishing between spoken and written modality.
          <br>
        </blockquote>
        se-Latn = Swedish written in Latin script
        <br>
        se-Cyrl = Swedish written in Cyrillic script
        <br>
        se-Maya = Swedish written in Mayan hieroglyphs
        <br>
        <br>
        se-Zxxx = Swedish, explicitly not written
        <br>
        <br>
        "se-Zxxx, fi-Latn" = content includes non-written Swedish plus
        Finnish
        <br>
        written in Latin script
        <br>
        <br>
        Examples of multiple streams of content, such as video in one
        language
        <br>
        that is subtitled in another, call for multiple language tags.
        That is
        <br>
        not a shortcoming or failure of the language tag mechanism. See
        RFC
        <br>
        5646, Section 4.3.
        <br>
        <br>
        All of this was discussed in the WG by the same parties.
        <br>
        <br>
        <blockquote type="cite">I once had an ambition to try to specify
          a notation for that to be
          <br>
          added to BCP 47, but did not succeed to get any real
          discussion going
          <br>
          on the topic.
          <br>
        </blockquote>
          I searched the ietf-languages archives and did not find any
        sort of post
        <br>
        or proposal from you. I forwarded one of your messages from SLIM
        to that
        <br>
        list in November 2015, expecting you to follow up with a
        proposal, but
        <br>
        nothing materialized.
        <br>
          --
        <br>
        Doug Ewell | Thornton, CO, US | ewellic.org
        <br>
        <br>
        <br>
        _______________________________________________
        <br>
        SLIM mailing list
        <br>
        <a class="moz-txt-link-abbreviated" href="mailto:SLIM@ietf.org">SLIM@ietf.org</a>
        <br>
        <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/slim">https://www.ietf.org/mailman/listinfo/slim</a>
        <br>
      </blockquote>
      <br>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
-----------------------------------------
Gunnar Hellström
Omnitor
<a class="moz-txt-link-abbreviated" href="mailto:gunnar.hellstrom@omnitor.se">gunnar.hellstrom@omnitor.se</a>
+46 708 204 288</pre>
  </body>
</html>

--------------2CC544CEA01C203ECDFDC8F6--


From nobody Tue Feb 14 05:37:18 2017
Return-Path: <talmi@marvell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBBD31295D9; Tue, 14 Feb 2017 05:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 CdvaWRQjvAyL; Tue, 14 Feb 2017 05:37:15 -0800 (PST)
Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) (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 4B55012948D; Tue, 14 Feb 2017 05:37:15 -0800 (PST)
Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1EDYuET022912; Tue, 14 Feb 2017 05:37:13 -0800
Received: from il-exch01.marvell.com ([199.203.130.101]) by mx0b-0016f401.pphosted.com with ESMTP id 28kgn853ru-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 14 Feb 2017 05:37:13 -0800
Received: from IL-EXCH01.marvell.com (10.4.102.220) by IL-EXCH01.marvell.com (10.4.102.220) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 14 Feb 2017 15:37:10 +0200
Received: from IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36]) by IL-EXCH01.marvell.com ([fe80::5d63:81cd:31e2:fc36%20]) with mapi id 15.00.1210.000; Tue, 14 Feb 2017 15:37:10 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: RE: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AdKF/X9u+WIK+SvpTdCAbZfIxgfsEgABO8eAADEQ/AA=
Date: Tue, 14 Feb 2017 13:37:10 +0000
Message-ID: <eeaa0cc49e104cc68c5b2ae23c44e355@IL-EXCH01.marvell.com>
References: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com> <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com>
In-Reply-To: <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.4.102.210]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-14_08:, , signatures=0
X-Proofpoint-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702140135
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f2wZubvVmnBiv55-Q5MS_ES9abM>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 13:37:17 -0000

SGkgTWFyaywNCg0KSSBjZXJ0YWlubHkgYWdyZWUgdGhhdCBob3AtYnktaG9wIGluc2VydGlvbi9t
b2RpZmljYXRpb24gaW50cm9kdWNlcyBwb3RlbnRpYWwgc2VjdXJpdHkgdnVsbmVyYWJpbGl0aWVz
Lg0KVGhlcmVmb3JlLCBhcyBJIHBvaW50ZWQgb3V0IGJlbG93LCBJIHdvdWxkIHJlY29tbWVuZCB0
byB0YWNrbGUgdGhpcyBieSBkZWZpbmluZyBzb21ldGhpbmcgYWxvbmcgdGhlIGxpbmVzIG9mIOKA
nEhvcC1ieS1ob3AgZXh0ZW5zaW9ucyBjYW4gYmUgaW5zZXJ0ZWQvcmVtb3ZlZC9tb2RpZmllZC9w
cm9jZXNzZWQgYnkgaW50ZXJtZWRpYXRlIG5vZGVzICppZiogW+KApuKApi4uXSBhbmQgdGhlIHBv
c3NpYmxlIGNvbnNlcXVlbmNlcyBhcmUgW+KApuKApi4uXeKAnQ0KDQpGb3IgZXhhbXBsZSwgaG9w
LWJ5LWhvcCBoYW5kbGluZyBjYW4gYmUgcmVzdHJpY3RlZCBvbmx5IHRvIGEgc2luZ2xlIGFkbWlu
aXN0cmF0aXZlIGRvbWFpbiwgb3Igb25seSB0byB0dW5uZWxzIChhcyBpbiB0aGUgemVybyBjaGVj
a3N1bSBjYXNlKS4gDQoNClJlZ2FyZHMsDQpUYWwuDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KPkZyb206IE1hcmsgU21pdGggW21haWx0bzptYXJrenp6c21pdGhAZ21haWwuY29tXQ0K
PlNlbnQ6IE1vbmRheSwgRmVicnVhcnkgMTMsIDIwMTcgNjowNyBQTQ0KPlRvOiBUYWwgTWl6cmFo
aQ0KPkNjOiA2bWFuQGlldGYub3JnOyBJRVRGIERpc2N1c3Npb24gbGlzdDsgZHJhZnQtaWV0Zi02
bWFuLQ0KPnJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmc7IDZtYW4tY2hhaXJzQGlldGYub3JnDQo+
U3ViamVjdDogW0VYVF0gUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtNm1hbi1yZmMyNDYwYmlz
LTA4LnR4dD4gKEludGVybmV0DQo+UHJvdG9jb2wsIFZlcnNpb24gNiAoSVB2NikgU3BlY2lmaWNh
dGlvbikgdG8gSW50ZXJuZXQgU3RhbmRhcmQNCj4NCj5FeHRlcm5hbCBFbWFpbA0KPg0KPi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCj5IaSwNCj4NCj4NCj4NCj5PbiAxNCBGZWJydWFyeSAyMDE3IGF0IDAwOjQzLCBU
YWwgTWl6cmFoaSA8dGFsbWlAbWFydmVsbC5jb20+IHdyb3RlOg0KPj4gSGksDQo+Pg0KPj4NCj4+
DQo+PiBHb29kIGRpc2N1c3Npb24gcmVnYXJkaW5nIHRoZSB0ZXh0IGFib3V0IHRoZSBob3AtYnkt
aG9wIGV4dGVuc2lvbi4NCj4+DQo+Pg0KPj4NCj4+IEluIG15IG9waW5pb24gdGhlcmUgaXMgYSB2
YWxpZCB1c2UgY2FzZSBmb3IgaW50ZXJtZWRpYXRlIG5vZGVzIHRoYXQNCj4+IGluc2VydC9yZW1v
dmUvbW9kaWZ5L3Byb2Nlc3MgaG9wLWJ5LWhvcCBleHRlbnNpb25zLiBFeGFtcGxlczogSU9BTSwg
SU5ULg0KPj4NCj4+IFNpbmNlIHRoZXJlIGlzIGEgdXNlIGNhc2UsIEkgYmVsaWV2ZSB3ZSBuZWVk
IGV4cGxpY2l0IHRleHQgYWJvdXQNCj4+IGludGVybWVkaWF0ZSBoYW5kbGluZyBvZiBob3AtYnkt
aG9wIGV4dGVuc2lvbnMuDQo+Pg0KPg0KPg0KPkltYWdpbmUgeW91IHNlbnQgYSBsZXR0ZXIgdGhy
b3VnaCB0aGUgcG9zdGFsIHN5c3RlbSwgYW5kIHRoZSBwb3N0YWwgc3lzdGVtDQo+d2FudGVkIHRv
IGFkZCBpbmZvcm1hdGlvbiB0byB0aGF0IGxldHRlciwgdGhhdCBpcyB0aGVuIHRvIGJlIHJlbW92
ZWQgYmVmb3JlIHRoZQ0KPmxldHRlciBhcnJpdmVzIGF0IGl0cyBmaW5hbCBkZXN0aW5hdGlvbi4N
Cj4NCj5UaGUgcG9zdGFsIHN5c3RlbSBoYXZlIGF0IGxlYXN0IHR3byBjaG9pY2VzIGFzIHRvIGhv
dyB0byBhZGQgdGhhdCBpbmZvcm1hdGlvbi4NCj5UaGV5IGNvdWxkOg0KPg0KPihhKSB1bnN0aWNr
IHlvdXIgZW52ZWxvcGUncyBzZWFsLCBpbnNlcnQgdGhlIGluZm9ybWF0aW9uLCByZXNlYWwgdGhl
IGVudmVsb3BlIHNvDQo+d2VsbCB5b3UgY2FuJ3QgdGVsbCBhbmQgc2VuZCBpdCBvbiBpdHMgd2F5
LCBzb21lIGhvdyBmbGFnZ2luZyB0byBhIGRlc3RpbmF0aW9uDQo+ZGV2aWNlIHdpdGhpbiB0aGUg
cG9zdGFsIHN5c3RlbSB0aGF0IHRoaXMgc3BlY2lmaWMgZW52ZWxvcCBuZWVkcyB0byBiZSBvcGVu
bmVkLCBhDQo+c3BlY2lmaWMgcGFnZSByZW1vdmVkLCBhbmQgdGhlbiByZXNlYWxlZC4NCj4NCj4o
YikgdGFrZSBhIG5ldyBlbnZlbG9wZSB3aXRoIG5ldyBpbnRlcm5hbCBwb3N0YWwgc3lzdGVtIHNv
dXJjZSBhbmQgZGVzdGluYXRpb24NCj5hZGRyZXNzIGluZm9ybWF0aW9uLCBpbnNlcnQgeW91ciBs
ZXR0ZXIgd2l0aG91dCB0b3VjaGluZyBpdCBpbiBhZGRpdGlvbiB0byB0aGUgbmV3DQo+aW5mb3Jt
YXRpb24sIGFuZCB0aGVuIHNlbmRpbmcgaXQgb24gaXRzIHdheS4NCj4NCj5JbWFnaW5lIHRoYXQg
dGhlIGluZm9ybWF0aW9uIHRvIGJlIGFkZGVkIGJ5IHRoZSBwb3N0YWwgc3lzdGVtIGlzIHByaW50
ZWQgb24gdGhlDQo+c2FtZSB0eXBlIG9mIHBhcGVyIGFuZCBpcyB3cml0dGVuIGluIHRoZSBzYW1l
IGZvbnQgYXMgeW91J3ZlIGNob3NlbiB0byB1c2UgdG8NCj53cml0ZSB5b3VyIGxldHRlci4NCj4N
Cj5IYXZlIGEgdGhpbmsgYWJvdXQgdGhlc2UgdHdvIG1ldGhvZHMsIHdoYXQgY291bGQgZmFpbCB3
aXRoIGVhY2ggb2YgdGhlbSwgYW5kDQo+d2hhdCB0aGUgY29uc2VxdWVuY2VzIG1heSBiZSBpZiBh
bnkgb2YgdGhvc2UgZmFpbHVyZXMgb2NjdXIuDQo+SGF2ZSBhIHRoaW5rIG9mIHRoZSBiZW5lZml0
cyBvZiBlYWNoIG1ldGhvZCwgYW5kIHdoZXRoZXIgdGhleSdyZSB3b3J0aCBpdA0KPmNvbXBhcmVk
IHRvIHRoZSBmYWlsdXJlIG1vZGUgY29zdHMgYW5kIGNvbnNlcXVlbmNlcyBmb3IgdGhlIG1ldGhv
ZC4NCj4NCj4+DQo+Pg0KPj4gVGhpcyBbc29tZXdoYXRdIHJlbWluZHMgbWUgb2YgdGhlIGRpc2N1
c3Npb24gYSBmZXcgeWVhcnMgYWdvIGFib3V0IHRoZQ0KPj4gSVB2Ni9VRFAgemVybyBjaGVja3N1
bS4gVGhlIFdHIGVuZGVkIHVwIGRlZmluaW5nIHRoYXQg4oCcWmVybyBjaGVja3N1bQ0KPj4gaXMg
cGVybWl0dGVkIGluIElQdjYvVURQICppZiogW+KApuKApi4uXSBhbmQgdGhlIHBvc3NpYmxlIGNv
bnNlcXVlbmNlcyBhcmUgW+KApuKApi4uXeKAnS4NCj4+DQo+Pg0KPg0KPlRoYXQgaXMgYSBmYXIg
bW9yZSB0cml2aWFsIGNoYW5nZSB0byB0aGUgcGFja2V0IC0gaXQgaXMgYWxsb3dpbmcgYSB2YWx1
ZSBpbiBhbiBleGlzdGluZw0KPmZpZWxkIHRoYXQgd2FzIGZvcm1lcmx5IHByb2hpYml0ZWQsIGFu
ZCBub2RlcyB0aGF0IGRpZCBub3QgdW5kZXJzdGFuZCB0aGF0IHZhbHVlDQo+d291bGQgZHJvcCB0
aGUgcGFja2V0IGJlY2F1c2UgdGhhdCBpcyB3aGF0IHRoZXkgaGFkIGJlZW4gc3BlY2lmaWVkIHRv
IGRvIGlmIHRoZXkNCj5yZWNlaXZlZCB0aGlzIHByb2hpYml0ZWQgdmFsdWUuIEluIG90aGVyIHdv
cmRzLCBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnMgJw0KPmJlaGF2aW91ciB3aGVuIHRoaXMgZm9y
bWVybHkgdW5leHBlY3RlZCB2YWx1ZSB3YXMgZW5jb3VudGVyZWQgaGFkIGFscmVhZHkNCj5iZWVu
IHNwZWNpZmllZCBhbmQgZGVwbG95ZWQuDQo+DQo+DQo+Pg0KPj4gSSB3b3VsZCBhcmd1ZSB0aGF0
IHJlZ2FyZGluZyBob3AtYnktaG9wIGV4dGVuc2lvbiBoYW5kbGluZyB3ZSBhbHNvDQo+PiBuZWVk
IHRvIGRlZmluZSB0aGF0IOKAnEhvcC1ieS1ob3AgZXh0ZW5zaW9ucyBjYW4gYmUNCj4+IGluc2Vy
dGVkL3JlbW92ZWQvbW9kaWZpZWQvcHJvY2Vzc2VkIGJ5IGludGVybWVkaWF0ZSBub2RlcyAqaWYq
IFvigKbigKYuLl0NCj4+IGFuZCB0aGUgcG9zc2libGUgY29uc2VxdWVuY2VzIGFyZSBb4oCm4oCm
Li5d4oCdLg0KPj4NCj4NCj5Tb21lIHRoaW5ncyB0aGF0IGFyZSBwb3NzaWJsZSB0byBkbyBpbiB0
aGVvcnkgc2hvdWxkbid0IGJlIGRvbmUgaW4gcHJhY3RpY2UsDQo+YmVjYXVzZSB0aGUgY29uc2Vx
dWVuY2VzIHdoZW4gdGhlaXIgaW1wbGVtZW50YXRpb25zIGZhaWwgY2FuIGJlIHNldmVyZSBhbmQN
Cj5vdXR3ZWlnaCB0aGUgYmVuZWZpdHMuDQo+DQo+SW4gdGhlb3J5LCBpbnNlcnRlZCBFSHMgd2ls
bCBiZSByZW1vdmVkIDEwMCUgb2YgdGhlIHRpbWUuIEluIHByYWN0aWNlIHRoZXkgd29uJ3QNCj5i
ZSwgYmVjYXVzZSBpbXBsZW1lbnRhdGlvbnMgY2FuIGhhdmUgYnVncyBhbmQgdGhleSBjYW4gYWxz
byBmYWlsIGluIHVuZXhwZWN0ZWQNCj53YXlzIGUuZy4sIGhhcmR3YXJlIGZhdWx0cy4NCj4NCj5S
ZWdhcmRzLA0KPk1hcmsuDQo=


From nobody Tue Feb 14 06:27:29 2017
Return-Path: <davidm@mellanox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC19C129A63; Tue, 14 Feb 2017 06:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.889
X-Spam-Level: 
X-Spam-Status: No, score=-3.889 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mellanox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rh8xD6ODeblj; Tue, 14 Feb 2017 06:27:20 -0800 (PST)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0043.outbound.protection.outlook.com [104.47.0.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C2D1129A60; Tue, 14 Feb 2017 06:27:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=LVgjNVg1sloo5qRTipk0nsKatX6vsckayGzDtr+IiLI=; b=hy5x4uxl/hsbLwi1jFz4w5fOxKMMp4q4aFn/Mw8Krnsy7uCYXoizUIPGj7QFSXKjiuj6ALnTHfNzjo7d7gL9iPFZLLd+YALMF48izXpttkDh3u3Avqn8yZMlhhmBvZ0rvX3+7HnDgyU79oW0vQNldyy1gna439sxr/U6jvCWag8=
Received: from HE1PR0501MB2138.eurprd05.prod.outlook.com (10.167.246.22) by HE1PR0501MB2137.eurprd05.prod.outlook.com (10.167.246.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Tue, 14 Feb 2017 14:27:16 +0000
Received: from HE1PR0501MB2138.eurprd05.prod.outlook.com ([10.167.246.22]) by HE1PR0501MB2138.eurprd05.prod.outlook.com ([10.167.246.22]) with mapi id 15.01.0888.026; Tue, 14 Feb 2017 14:27:16 +0000
From: David Mozes <davidm@mellanox.com>
To: Tal Mizrahi <talmi@marvell.com>, Mark Smith <markzzzsmith@gmail.com>
Subject: RE: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Topic: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Thread-Index: AdKF/X9u+WIK+SvpTdCAbZfIxgfsEgABO8eAADEQ/AAAAQ+oAA==
Date: Tue, 14 Feb 2017 14:27:16 +0000
Message-ID: <HE1PR0501MB21381B97CAB3707DB7D20F31B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
References: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com> <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com> <eeaa0cc49e104cc68c5b2ae23c44e355@IL-EXCH01.marvell.com>
In-Reply-To: <eeaa0cc49e104cc68c5b2ae23c44e355@IL-EXCH01.marvell.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=davidm@mellanox.com; 
x-originating-ip: [193.47.165.251]
x-ms-office365-filtering-correlation-id: f60b0022-94d6-4f2d-df85-08d454e5936e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081); SRVR:HE1PR0501MB2137; 
x-microsoft-exchange-diagnostics: 1; HE1PR0501MB2137; 7:gV5Ee7/6kXtJWVMpHIpPtcAR1s4BrVO2WeckwPZ7kA3ys/PCoKzrTQ43cD7l7xd4V2JVeFp32ueVocn3wvgudESNb1gVpqvnlwTAPpJhwqLp2NAlciBpFREmKaVTaO5okMT4DQJ8exzP9qAhtCNxPcfsruDuT7yU6wousaym47ctY+PNf62Ytot5Idn0VOD2tbq5nwuwkZl6ytpr6pVtwEcrMjhcVNwHillgvBX0ukqBbhuFGkSGd/vp17jP3EbR0YXzR5+z6oEackCKeN72UOemNzhFJPIBQZ4Al6ufdCUzIbwB4CI7oxW6lXY0KMqJ/teaxx9e97s29lxrXXXHvtjSQGnE8D1+G+bPMNE/3U5hGYZNp7FYarO7s0LZfhVn5pbQXuWWBN83rPMro/2f00XsrWKz6TnONMmiTGG9TBLD6NgSRqcrlQVSBsjjNsCiLtVhzFK0aDM80FCSJSuWdNLhTJQrgO/vi+9hpUTu5xI7g+R8+3aJi6Y8GD7oXbrOAHIH3SKm88at8phTGRNdgQ==
x-microsoft-antispam-prvs: <HE1PR0501MB21376282FBDD5D2B34575F87B6580@HE1PR0501MB2137.eurprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123558025)(20161123560025)(20161123562025)(20161123564025)(20161123555025)(6072148); SRVR:HE1PR0501MB2137; BCL:0; PCL:0; RULEID:; SRVR:HE1PR0501MB2137; 
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(39860400002)(39850400002)(39840400002)(39410400002)(189002)(199003)(377454003)(13464003)(24454002)(51444003)(92566002)(230783001)(25786008)(55016002)(54906002)(74316002)(66066001)(33656002)(99286003)(68736007)(8676002)(6436002)(2906002)(9686003)(6506006)(81166006)(97736004)(77096006)(3280700002)(54075001)(6306002)(305945005)(50986999)(7736002)(2900100001)(81156014)(53936002)(4326007)(8936002)(2950100002)(106356001)(229853002)(76176999)(54356999)(6116002)(122556002)(3846002)(86362001)(7696004)(38730400002)(105586002)(3660700001)(5660300001)(6246003)(189998001)(39060400002)(101416001)(102836003)(81003); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR0501MB2137; H:HE1PR0501MB2138.eurprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: Mellanox.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Feb 2017 14:27:16.1655 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0501MB2137
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jOwzvhbmf6TIjObbDlffCQULvsY>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 14:27:23 -0000

SGkgKiAsDQpJIGFtIGFsc28gc3VwcG9ydGluZyB0aGUgaW5zZXJ0aW9uIG9mIGluLWJhbmQgdGVs
ZW1ldHJ5IGxpa2UgSU5UIGFsb25nIHdpdGggdGhlICBhY3R1YWwgZGF0YSBwYWNrZXQgLg0KSXQg
aXMgZm9yIHN1cmUgYSB2YWxpZCB1c2UgY2FzZSBmb3IgdGhlIG1vZGVybiBuZXR3b3JraW5nIGlu
Y2x1ZGluZyBkYXRhIGNlbnRlci4gDQpUaGVyZSBhcmUgc2V2ZXJhbCBwcm9wb3NhbHMgaG93IHRv
IGVtYmVkZGVkIHRlbGVtZXRyeSBpbmZvcm1hdGlvbiAgIHNvbWUgb2YgdGhlbSBhcmUgd2l0aCBp
biBudm8zIHRhbm5saW5nIHByb3RvY29scyANCihWeGxhbi1HUEUsR2VuZXZlKSBTcHJpbmcgYW5k
IG90aGVyICAuIA0KSSB0aGluayB0aGF0IGlwdjYgaGJoIGlzIHRoZSAiY2xlYW5lc3QiICB3YXkg
dG8gYWRkIHN1Y2ggaW5mby4NCgkxKSBJIGRvbid0IHNlZSBhbnkgYW5kIGFkdmFudGFnZXMgb24g
dGhlIG90aGVyICBwcm9wb3NhbHMgKE5WTzMgLFNQUklORykgb3ZlciBJUFY2IGhiaC4NCgkyKSlB
cyBmYXIgYXMgc2VjdXJpdHkgSW4gdGhlIElQc2VjIGNvbW11bml0eSwgQUggaXMgcHJldHR5IG11
Y2ggY29uc2lkZXJlZCBkZXByZWNhdGVkLCBhIGZhaWxlZCBleHBlcmltZW50LlRoZXkgIGFyZSAg
cHJlZmVyIHRvIHVzZSAgIEVTUCBmb3IgYXV0aGVudGljYXRpb24gYXMgd2VsbC4NCiANClRoZSBw
b3N0YWwgc3lzdGVtIGFuZCB0aGUgbGV0dGVyIGlzIHZlcnkgbmljZSBlIGV4YW1wbGUgIC4gSSB3
aWxsIHRyZWF0IHRoZSBhZGRpbmcgaXB2Ni1oYmggaW5mbyBhcyBzdGFtcHMgb24gdGhlIGVudmVs
b3BzICxzaW5jZSB3ZSBhcmUgbm90IHRvdWNoaW5nICB0aGUgZGF0YSBncmFtIGl0c2VsZiBqdXN0
IHRoZSBlbnZlbG9wZQ0KDQpUaHgNCkRhdmlkDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0K
RnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIFRh
bCBNaXpyYWhpDQpTZW50OiBUdWVzZGF5LCBGZWJydWFyeSAxNCwgMjAxNyAzOjM3IFBNDQpUbzog
TWFyayBTbWl0aCA8bWFya3p6enNtaXRoQGdtYWlsLmNvbT4NCkNjOiBkcmFmdC1pZXRmLTZtYW4t
cmZjMjQ2MGJpc0B0b29scy5pZXRmLm9yZzsgNm1hbkBpZXRmLm9yZzsgSUVURiBEaXNjdXNzaW9u
IGxpc3QgPGlldGZAaWV0Zi5vcmc+OyA2bWFuLWNoYWlyc0BpZXRmLm9yZw0KU3ViamVjdDogUkU6
IFtFWFRdIFJlOiBMYXN0IENhbGw6IDxkcmFmdC1pZXRmLTZtYW4tcmZjMjQ2MGJpcy0wOC50eHQ+
IChJbnRlcm5ldCBQcm90b2NvbCwgVmVyc2lvbiA2IChJUHY2KSBTcGVjaWZpY2F0aW9uKSB0byBJ
bnRlcm5ldCBTdGFuZGFyZA0KDQpIaSBNYXJrLA0KDQpJIGNlcnRhaW5seSBhZ3JlZSB0aGF0IGhv
cC1ieS1ob3AgaW5zZXJ0aW9uL21vZGlmaWNhdGlvbiBpbnRyb2R1Y2VzIHBvdGVudGlhbCBzZWN1
cml0eSB2dWxuZXJhYmlsaXRpZXMuDQpUaGVyZWZvcmUsIGFzIEkgcG9pbnRlZCBvdXQgYmVsb3cs
IEkgd291bGQgcmVjb21tZW5kIHRvIHRhY2tsZSB0aGlzIGJ5IGRlZmluaW5nIHNvbWV0aGluZyBh
bG9uZyB0aGUgbGluZXMgb2Yg4oCcSG9wLWJ5LWhvcCBleHRlbnNpb25zIGNhbiBiZSBpbnNlcnRl
ZC9yZW1vdmVkL21vZGlmaWVkL3Byb2Nlc3NlZCBieSBpbnRlcm1lZGlhdGUgbm9kZXMgKmlmKiBb
4oCm4oCmLi5dIGFuZCB0aGUgcG9zc2libGUgY29uc2VxdWVuY2VzIGFyZSBb4oCm4oCmLi5d4oCd
DQoNCkZvciBleGFtcGxlLCBob3AtYnktaG9wIGhhbmRsaW5nIGNhbiBiZSByZXN0cmljdGVkIG9u
bHkgdG8gYSBzaW5nbGUgYWRtaW5pc3RyYXRpdmUgZG9tYWluLCBvciBvbmx5IHRvIHR1bm5lbHMg
KGFzIGluIHRoZSB6ZXJvIGNoZWNrc3VtIGNhc2UpLiANCg0KUmVnYXJkcywNClRhbC4NCg0KPi0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+RnJvbTogTWFyayBTbWl0aCBbbWFpbHRvOm1hcmt6
enpzbWl0aEBnbWFpbC5jb21dDQo+U2VudDogTW9uZGF5LCBGZWJydWFyeSAxMywgMjAxNyA2OjA3
IFBNDQo+VG86IFRhbCBNaXpyYWhpDQo+Q2M6IDZtYW5AaWV0Zi5vcmc7IElFVEYgRGlzY3Vzc2lv
biBsaXN0OyBkcmFmdC1pZXRmLTZtYW4tIA0KPnJmYzI0NjBiaXNAdG9vbHMuaWV0Zi5vcmc7IDZt
YW4tY2hhaXJzQGlldGYub3JnDQo+U3ViamVjdDogW0VYVF0gUmU6IExhc3QgQ2FsbDogPGRyYWZ0
LWlldGYtNm1hbi1yZmMyNDYwYmlzLTA4LnR4dD4gDQo+KEludGVybmV0IFByb3RvY29sLCBWZXJz
aW9uIDYgKElQdjYpIFNwZWNpZmljYXRpb24pIHRvIEludGVybmV0IA0KPlN0YW5kYXJkDQo+DQo+
RXh0ZXJuYWwgRW1haWwNCj4NCj4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+SGksDQo+DQo+DQo+DQo+T24gMTQg
RmVicnVhcnkgMjAxNyBhdCAwMDo0MywgVGFsIE1penJhaGkgPHRhbG1pQG1hcnZlbGwuY29tPiB3
cm90ZToNCj4+IEhpLA0KPj4NCj4+DQo+Pg0KPj4gR29vZCBkaXNjdXNzaW9uIHJlZ2FyZGluZyB0
aGUgdGV4dCBhYm91dCB0aGUgaG9wLWJ5LWhvcCBleHRlbnNpb24uDQo+Pg0KPj4NCj4+DQo+PiBJ
biBteSBvcGluaW9uIHRoZXJlIGlzIGEgdmFsaWQgdXNlIGNhc2UgZm9yIGludGVybWVkaWF0ZSBu
b2RlcyB0aGF0IA0KPj4gaW5zZXJ0L3JlbW92ZS9tb2RpZnkvcHJvY2VzcyBob3AtYnktaG9wIGV4
dGVuc2lvbnMuIEV4YW1wbGVzOiBJT0FNLCBJTlQuDQo+Pg0KPj4gU2luY2UgdGhlcmUgaXMgYSB1
c2UgY2FzZSwgSSBiZWxpZXZlIHdlIG5lZWQgZXhwbGljaXQgdGV4dCBhYm91dCANCj4+IGludGVy
bWVkaWF0ZSBoYW5kbGluZyBvZiBob3AtYnktaG9wIGV4dGVuc2lvbnMuDQo+Pg0KPg0KPg0KPklt
YWdpbmUgeW91IHNlbnQgYSBsZXR0ZXIgdGhyb3VnaCB0aGUgcG9zdGFsIHN5c3RlbSwgYW5kIHRo
ZSBwb3N0YWwgDQo+c3lzdGVtIHdhbnRlZCB0byBhZGQgaW5mb3JtYXRpb24gdG8gdGhhdCBsZXR0
ZXIsIHRoYXQgaXMgdGhlbiB0byBiZSANCj5yZW1vdmVkIGJlZm9yZSB0aGUgbGV0dGVyIGFycml2
ZXMgYXQgaXRzIGZpbmFsIGRlc3RpbmF0aW9uLg0KPg0KPlRoZSBwb3N0YWwgc3lzdGVtIGhhdmUg
YXQgbGVhc3QgdHdvIGNob2ljZXMgYXMgdG8gaG93IHRvIGFkZCB0aGF0IGluZm9ybWF0aW9uLg0K
PlRoZXkgY291bGQ6DQo+DQo+KGEpIHVuc3RpY2sgeW91ciBlbnZlbG9wZSdzIHNlYWwsIGluc2Vy
dCB0aGUgaW5mb3JtYXRpb24sIHJlc2VhbCB0aGUgDQo+ZW52ZWxvcGUgc28gd2VsbCB5b3UgY2Fu
J3QgdGVsbCBhbmQgc2VuZCBpdCBvbiBpdHMgd2F5LCBzb21lIGhvdyANCj5mbGFnZ2luZyB0byBh
IGRlc3RpbmF0aW9uIGRldmljZSB3aXRoaW4gdGhlIHBvc3RhbCBzeXN0ZW0gdGhhdCB0aGlzIA0K
PnNwZWNpZmljIGVudmVsb3AgbmVlZHMgdG8gYmUgb3Blbm5lZCwgYSBzcGVjaWZpYyBwYWdlIHJl
bW92ZWQsIGFuZCB0aGVuIHJlc2VhbGVkLg0KPg0KPihiKSB0YWtlIGEgbmV3IGVudmVsb3BlIHdp
dGggbmV3IGludGVybmFsIHBvc3RhbCBzeXN0ZW0gc291cmNlIGFuZCANCj5kZXN0aW5hdGlvbiBh
ZGRyZXNzIGluZm9ybWF0aW9uLCBpbnNlcnQgeW91ciBsZXR0ZXIgd2l0aG91dCB0b3VjaGluZyBp
dCANCj5pbiBhZGRpdGlvbiB0byB0aGUgbmV3IGluZm9ybWF0aW9uLCBhbmQgdGhlbiBzZW5kaW5n
IGl0IG9uIGl0cyB3YXkuDQo+DQo+SW1hZ2luZSB0aGF0IHRoZSBpbmZvcm1hdGlvbiB0byBiZSBh
ZGRlZCBieSB0aGUgcG9zdGFsIHN5c3RlbSBpcyANCj5wcmludGVkIG9uIHRoZSBzYW1lIHR5cGUg
b2YgcGFwZXIgYW5kIGlzIHdyaXR0ZW4gaW4gdGhlIHNhbWUgZm9udCBhcyANCj55b3UndmUgY2hv
c2VuIHRvIHVzZSB0byB3cml0ZSB5b3VyIGxldHRlci4NCj4NCj5IYXZlIGEgdGhpbmsgYWJvdXQg
dGhlc2UgdHdvIG1ldGhvZHMsIHdoYXQgY291bGQgZmFpbCB3aXRoIGVhY2ggb2YgDQo+dGhlbSwg
YW5kIHdoYXQgdGhlIGNvbnNlcXVlbmNlcyBtYXkgYmUgaWYgYW55IG9mIHRob3NlIGZhaWx1cmVz
IG9jY3VyLg0KPkhhdmUgYSB0aGluayBvZiB0aGUgYmVuZWZpdHMgb2YgZWFjaCBtZXRob2QsIGFu
ZCB3aGV0aGVyIHRoZXkncmUgd29ydGggDQo+aXQgY29tcGFyZWQgdG8gdGhlIGZhaWx1cmUgbW9k
ZSBjb3N0cyBhbmQgY29uc2VxdWVuY2VzIGZvciB0aGUgbWV0aG9kLg0KPg0KPj4NCj4+DQo+PiBU
aGlzIFtzb21ld2hhdF0gcmVtaW5kcyBtZSBvZiB0aGUgZGlzY3Vzc2lvbiBhIGZldyB5ZWFycyBh
Z28gYWJvdXQgDQo+PiB0aGUgSVB2Ni9VRFAgemVybyBjaGVja3N1bS4gVGhlIFdHIGVuZGVkIHVw
IGRlZmluaW5nIHRoYXQg4oCcWmVybyANCj4+IGNoZWNrc3VtIGlzIHBlcm1pdHRlZCBpbiBJUHY2
L1VEUCAqaWYqIFvigKbigKYuLl0gYW5kIHRoZSBwb3NzaWJsZSBjb25zZXF1ZW5jZXMgYXJlIFvi
gKbigKYuLl3igJ0uDQo+Pg0KPj4NCj4NCj5UaGF0IGlzIGEgZmFyIG1vcmUgdHJpdmlhbCBjaGFu
Z2UgdG8gdGhlIHBhY2tldCAtIGl0IGlzIGFsbG93aW5nIGEgDQo+dmFsdWUgaW4gYW4gZXhpc3Rp
bmcgZmllbGQgdGhhdCB3YXMgZm9ybWVybHkgcHJvaGliaXRlZCwgYW5kIG5vZGVzIHRoYXQgDQo+
ZGlkIG5vdCB1bmRlcnN0YW5kIHRoYXQgdmFsdWUgd291bGQgZHJvcCB0aGUgcGFja2V0IGJlY2F1
c2UgdGhhdCBpcyANCj53aGF0IHRoZXkgaGFkIGJlZW4gc3BlY2lmaWVkIHRvIGRvIGlmIHRoZXkg
cmVjZWl2ZWQgdGhpcyBwcm9oaWJpdGVkIHZhbHVlLiBJbiBvdGhlciB3b3JkcywgZXhpc3Rpbmcg
aW1wbGVtZW50YXRpb25zICcNCj5iZWhhdmlvdXIgd2hlbiB0aGlzIGZvcm1lcmx5IHVuZXhwZWN0
ZWQgdmFsdWUgd2FzIGVuY291bnRlcmVkIGhhZCANCj5hbHJlYWR5IGJlZW4gc3BlY2lmaWVkIGFu
ZCBkZXBsb3llZC4NCj4NCj4NCj4+DQo+PiBJIHdvdWxkIGFyZ3VlIHRoYXQgcmVnYXJkaW5nIGhv
cC1ieS1ob3AgZXh0ZW5zaW9uIGhhbmRsaW5nIHdlIGFsc28gDQo+PiBuZWVkIHRvIGRlZmluZSB0
aGF0IOKAnEhvcC1ieS1ob3AgZXh0ZW5zaW9ucyBjYW4gYmUgDQo+PiBpbnNlcnRlZC9yZW1vdmVk
L21vZGlmaWVkL3Byb2Nlc3NlZCBieSBpbnRlcm1lZGlhdGUgbm9kZXMgKmlmKiBb4oCm4oCmLi5d
IA0KPj4gYW5kIHRoZSBwb3NzaWJsZSBjb25zZXF1ZW5jZXMgYXJlIFvigKbigKYuLl3igJ0uDQo+
Pg0KPg0KPlNvbWUgdGhpbmdzIHRoYXQgYXJlIHBvc3NpYmxlIHRvIGRvIGluIHRoZW9yeSBzaG91
bGRuJ3QgYmUgZG9uZSBpbiANCj5wcmFjdGljZSwgYmVjYXVzZSB0aGUgY29uc2VxdWVuY2VzIHdo
ZW4gdGhlaXIgaW1wbGVtZW50YXRpb25zIGZhaWwgY2FuIA0KPmJlIHNldmVyZSBhbmQgb3V0d2Vp
Z2ggdGhlIGJlbmVmaXRzLg0KPg0KPkluIHRoZW9yeSwgaW5zZXJ0ZWQgRUhzIHdpbGwgYmUgcmVt
b3ZlZCAxMDAlIG9mIHRoZSB0aW1lLiBJbiBwcmFjdGljZSANCj50aGV5IHdvbid0IGJlLCBiZWNh
dXNlIGltcGxlbWVudGF0aW9ucyBjYW4gaGF2ZSBidWdzIGFuZCB0aGV5IGNhbiBhbHNvIA0KPmZh
aWwgaW4gdW5leHBlY3RlZCB3YXlzIGUuZy4sIGhhcmR3YXJlIGZhdWx0cy4NCj4NCj5SZWdhcmRz
LA0KPk1hcmsuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KSUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBs
aXN0DQppcHY2QGlldGYub3JnDQpBZG1pbmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pcHY2DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K


From nobody Tue Feb 14 07:12:57 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B822A1295DA for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RxWQwrPVgNcB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:12:54 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 6EAC71299BF for <ietf@ietf.org>; Tue, 14 Feb 2017 07:12:54 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id x49so112987073qtc.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 07:12:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t7bvCCTBimLmUhU6TUm8jUBZW7ZrYpvAMiR5xvydemw=; b=LvLcglxYQr2XfbupfF1YtKQ2xZ8TcO4MwbWHgqvisCVAZlEKEqgtIiyMvlgYVUwuuQ FIGFCqgZU3rEHADa6Lx2tL8SItba+DVDT8isvJMVPuj2vzUEcMJHd3vZ1vNduGHU5vrX TW2iP8xP852UEf5Up2y2audvKcjk+qhvr41lgyXR2/qQhZQngF5AB4Bolnl4hlXypz4+ kbNZWSXauH6tUTHttFvYxTXmAVuJfmLWdnzoNYkTG/A3vt3HYegXzlGI5yDhPevxg2z+ 8jKtb4o4YZ2s/2jpVjCTP89eJ1guh9bsNVRlbiwK5cAlBuPZg+ZufmXeXc7YoSgIqWDA W/cQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=t7bvCCTBimLmUhU6TUm8jUBZW7ZrYpvAMiR5xvydemw=; b=qfj1GSlLRR7MQpfKgDPnLAgd4dLEaMNNvCmDUgqMYL0ud5mFiB8zwsyxjvFYbCdecC NPhn2nis3jbBWv6FDtfoyED+P0XtnJtZzM6sF+ov6CWCnXB651lgjC2yiOiunSKfnPM+ Fc1ZNZbdfIUN25+VacH4+s5j2zGPHl+RTKfS3KrdzZzrQi2cc70mbbnSA4YId7Kj0yFk Ekt22NTdS01L/6G15EytrxihIgnPh/JRFUURY/LxeCMpDc6uU4Q2brSAUYv1cKldVH9U ALgYpyIP098NK2JGbRVNi4OIDOJ7c9VptWS/AofDB17Jnk8PTUcADbSXV6Bdy085x/2Y GPVg==
X-Gm-Message-State: AMke39n7zyKrQfRxhWofcEtOTTJyeg5n3CtbqbN8golxovrE2vAt6tzReYTeah9c2FMK/g==
X-Received: by 10.200.47.217 with SMTP id m25mr30237071qta.283.1487085173551;  Tue, 14 Feb 2017 07:12:53 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 23sm475639qtp.20.2017.02.14.07.12.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 07:12:52 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com>
Date: Tue, 14 Feb 2017 10:12:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nEgm9GUe5wwZl6CtXyp6WA5o8MU>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Dave CROCKER <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:12:56 -0000

On Feb 14, 2017, at 2:28 AM, Yoav Nir <ynir.ietf@gmail.com> wrote:
> I think that would be fine, but anyone jumping to agree with you would =
be properly asked why they didn=E2=80=99t participate in the WG. In any =
case, it could be useful input for the IESG who are the ultimate judges =
of IETF consensus.

Er, no.  The most important point of last call is to make sure that =
people who did not have time to participate in the last call in the =
working group, but who have relevant knowledge, get a chance to weigh =
in.


From nobody Tue Feb 14 07:32:50 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F06E9129624 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzweTCsZ1Krz for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:32:48 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 5F17C1295CE for <ietf@ietf.org>; Tue, 14 Feb 2017 07:32:48 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1EFYSVO029993 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 14 Feb 2017 07:34:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1487086469; bh=5D8lDf1M5ghkPHS3V55D6FvQlxPJQkpiae+oGCeLwn8=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=GQfL6YssZwD7EsIVWmbP+5y7Cv2bzMX3NC9DM6XHbIfKRg8punIBqXmObhCK15hPl RBgPMogT6qg8LLMp4hXfi1Vonnkwoi7WQph9P9z6WLAILPeUvcw7gLurD8VWBSDpxA MpvTiNBLhxARdkaKypJk5Db97Vbn2YBbOz2ftsRc=
Subject: Re: To "lose the argument in the WG"
To: Stewart Bryant <stewart.bryant@gmail.com>, John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com> <C8DC848672108BF32D41ADAC@PSB> <bce0454f-9c51-b5ca-3270-19486f72c972@gmail.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b317aeb0-ea9b-e70c-17a8-d75d8fb24e83@dcrocker.net>
Date: Tue, 14 Feb 2017 07:32:36 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <bce0454f-9c51-b5ca-3270-19486f72c972@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hvI0uP8HiZbqKoKxaHcKBLsYax0>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:32:49 -0000

On 2/14/2017 12:40 AM, Stewart Bryant wrote:
>
> Yes, it is the prospect of a complete re-run of the argument at IETF LC
> that keeps WGs honest.


In theory, perhaps.  In practice, no it doesn't.

What it does do is to help make the IETF process onerous, and therefore 
aid in making the IETF a place to avoid when possible.

Having folk spend months (or years) working on a detailed specification 
and then have to go through a detailed defense at the end is 
disrespectful of their effort.  It is also impractical, because it 
essentially requires re-creating the context for making various 
decisions made along the way, months (or years) later, to folk who have 
no skin in the game.

For those rare cases in which there really is a problem that needs 
fixing, forcing a wg to go through this random defense process mostly 
speaks to failures in oversight and review that should be happening 
along the way, not at the end of the process.

And, again, note that it almost never works.  While it creates 
additional work and pain for those who are tired from the lengthy 
process, it rarely (if ever) produces serious benefit.

For the folk who think this is an essential bit of IETF quality control, 
please produce documentation of the times this defense is required and 
compare when it has produced meaningful change and when it hasn't.  Just 
coming up with stray examples of benefits ignores the larger number of 
cases where it incurs costs without benefits.[*]

To the extent that a working group does need course-correction, then 
let's look for ways to do that that are effective and efficient and 
much, much earlier.

d/

[*] Please remember that the trigger for this sub-thread is a 
sour-grapes effort by an existing wg participant to force review of a 
(potentially much) earlier wg decision they didn't like.  A separate 
case is of fresh, non-wg eyes that might see something none of the 
older, more-tired eyes of wg participants caught.  The former case 
really is sour grapes.  The latter case could be naivete or it could be 
insight.  Mostly of the time it is the former.  That ought to mitigate 
the certitude of the fresh eyes, but it usually doesn't.

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Tue Feb 14 07:33:08 2017
Return-Path: <denis.ietf@free.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA5D12968D; Tue, 14 Feb 2017 07:33:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 yVRQaZdeorK5; Tue, 14 Feb 2017 07:33:04 -0800 (PST)
Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) (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 3F67612967F; Tue, 14 Feb 2017 07:33:01 -0800 (PST)
Received: from [192.168.0.13] (unknown [88.182.125.39]) by smtp6-g21.free.fr (Postfix) with ESMTP id 477D07803B5; Tue, 14 Feb 2017 16:32:58 +0100 (CET)
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-jwsreq-12.txt
To: oauth@ietf.org
References: <148700937892.24914.355439693543276110.idtracker@ietfa.amsl.com>
From: Denis <denis.ietf@free.fr>
Message-ID: <759cb8f3-1178-087a-65d6-16ebc64c5454@free.fr>
Date: Tue, 14 Feb 2017 16:32:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148700937892.24914.355439693543276110.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ibAWE_EkeedkwIGJA8Me3mjAFeI>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:33:06 -0000

Nat,

This new version 12 contains nice editorial improvements. However, you 
have not yet responded to my email
from February 9 th sent during the LC which contains substantial comments.

Denis

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Web Authorization Protocol of the IETF.
>
>          Title           : The OAuth 2.0 Authorization Framework: JWT Secured Authorization Request (JAR)
>          Authors         : Nat Sakimura
>                            John Bradley
> 	Filename        : draft-ietf-oauth-jwsreq-12.txt
> 	Pages           : 26
> 	Date            : 2017-02-13
>
> Abstract:
>     The authorization request in OAuth 2.0 described in RFC 6749 utilizes
>     query parameter serialization, which means that Authorization Request
>     parameters are encoded in the URI of the request and sent through
>     user agents such as web browsers.  While it is easy to implement, it
>     means that (a) the communication through the user agents are not
>     integrity protected and thus the parameters can be tainted, and (b)
>     the source of the communication is not authenticated.  Because of
>     these weaknesses, several attacks to the protocol have now been put
>     forward.
>
>     This document introduces the ability to send request parameters in a
>     JSON Web Token (JWT) instead, which allows the request to be signed
>     with JSON Web Signature (JWS) and/or encrypted with JSON Web
>     Encryption (JWE) so that the integrity, source authentication and
>     confidentiality property of the Authorization Request is attained.
>     The request can be sent by value or by reference.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-oauth-jwsreq/
>
> There's also a htmlized version available at:
> https://tools.ietf.org/html/draft-ietf-oauth-jwsreq-12
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-oauth-jwsreq-12
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth



From nobody Tue Feb 14 07:37:19 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AA62129624 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:37:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qFUi-UanCR6 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:37:14 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 BF46D129530 for <ietf@ietf.org>; Tue, 14 Feb 2017 07:37:14 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 1137F668 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:27:41 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kGSQQZ1ibeT7 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:27:40 -0600 (CST)
Received: from mail-vk0-f72.google.com (mail-vk0-f72.google.com [209.85.213.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id B6E6E277 for <ietf@ietf.org>; Tue, 14 Feb 2017 09:27:40 -0600 (CST)
Received: by mail-vk0-f72.google.com with SMTP id x75so90183603vke.5 for <ietf@ietf.org>; Tue, 14 Feb 2017 07:27:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bnX9VKFjPW63YET6hyeolID+/lH6vsAx1o7TgRKdXoM=; b=VwzJzJsybqXrg9AwsuEjACiN03oaD3wt1yNHPRHCEP67zeL4cEPeyUITkW32w0gO9q aqExRYUnnuKQud4M9oXbLGNAScuuGRctFpIJGkoi5726sZ/YlSFJmZtxWPv4FelpIZO+ scBTwd+pomeJ22KXXYPwQUOjogg71d08gB3gnnYBoetmQvcN4C0N/nVSznT66Qjg6ahs 3XOZnaFzEnEqdXZBhcN/t16OPfBnMd4a7o630cezgFz+IizlgY+GOuoPKzn/GYrI80h3 /yr89xfbpVs3Em5wdmb5DYf11vEgmv0bq8Jp63nCOWYq/Ti6anYbLqT4bkD4c8HRUuRu FL7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bnX9VKFjPW63YET6hyeolID+/lH6vsAx1o7TgRKdXoM=; b=oSmPBmTapRhq2UbJf8fp53z6/do3ups6t3pYhjscRUq7NzTzFse4MduIRgUgjmVgTe N7v5ui4Q2RlEpEfUFLSO+T6DaGknBQDSGrDq1zUz/01T33yanKkwQD0DXOGccKEYZ6en xP32zrSd1PxRNt7KvKqbRT4r/gbJacUlu57hkFzbAIN8AXJ0ODwaio0phecLr4RFINc2 2MUslfwrQumT8icM61OTlQbb5xmDfxddMt9Y3O7oH6fsW23xqne8R2iSKGu+eNryh6nY UKfaj48mFTkiEr1qf3YSynglj2JH8bAqDxM8oRwQ4rtll/SKi8DWmOoqeSSZ5JYaCntr F8uQ==
X-Gm-Message-State: AMke39lb67MbCQF8cigk2Cc4KQ4WSHsuSWkLMYWid0+2z9rVvvPeIlWIzG+bV/LhpeBaBuqzLriZghbkLzlR++HTaSQN1ejW7TTo15TsIHzC3Kxgpa3pEKH0G0EyIezeomeWTtXHMGRuSH6nfJU=
X-Received: by 10.176.5.134 with SMTP id e6mr15592564uae.108.1487086060174; Tue, 14 Feb 2017 07:27:40 -0800 (PST)
X-Received: by 10.176.5.134 with SMTP id e6mr15592547uae.108.1487086059879; Tue, 14 Feb 2017 07:27:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Tue, 14 Feb 2017 07:27:39 -0800 (PST)
In-Reply-To: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Tue, 14 Feb 2017 09:27:39 -0600
Message-ID: <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c12318c59bbd305487f34b9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yBOAr_rMYKK8FIyGGV3eldIDeko>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:37:16 -0000

--94eb2c12318c59bbd305487f34b9
Content-Type: text/plain; charset=UTF-8

Actually, in addition to your text there still needs to be a recommendation
for 64 bit IIDs in all other cases.  64 bit IIDs are(and should remain) the
norm for IPv6, I do not want to change that.  But the current language say
IIDs are always 64 bit except when an address begins with binary 000,
leaving no room for any other exception.  And this is plainly incorrect, I
provided two clear exceptions that are already standardized.  Furthermore,
IIDs other than 64 bits are in operational use, with manual configuration
and DHCPv6.

So I'd suggest;

However, the Interface ID of unicast addresses used for
Stateless Address Autoconfiguration [RFC4862] is required
to be 64 bits long, in all other cases it is recommended to
be 64 bits long.

The other option is to enumerate all the exceptions, requiring the document
to be updated every time a new exception is standardized.

On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> At an earlier stage I suggested restricting the applicability
> of the "However..." sentence to SLAAC [RFC4862]. A short way
> of doing this would be
>
> However, the Interface ID of unicast addresses used for
> Stateless Address Autoconfiguration [RFC4862] is required
> to be 64 bits long.
>
> Regards
>    Brian
>
> On 14/02/2017 11:32, David Farmer wrote:
> > I have concerns with the following text;
> >
> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
> >    on inter-router point-to-point links. However, the Interface ID of
> >    all unicast addresses, except those that start with the binary value
> >    000, is required to be 64 bits long.  The rationale for the 64 bit
> >    boundary in IPv6 addresses can be found in [RFC7421]
> >
> > The third sentence seems to limit exceptions to 64 bit IIDs to
> exclusively
> > addresses that start with binary vale of 000.  There are at least two
> other
> > exceptions from standards track RFCs, that should be more clear accounted
> > for in this text.  First is [RFC6164] point-to-point links, as mentioned
> in
> > the previous sentence.  I think the clear intent of [RFC6164] is to allow
> > one(1) Bit IIDs for point to point-to-point links using any Global
> Unicast
> > Address, not just those that start with 000.  Second is, [RFC6052], which
> > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for any
> > Global Unicast Address when used for IPv4/IPv6 translation, referred to
> as
> > ""Network-Specific Prefix" unique to the organization deploying the
> address
> > translators," in section 2.2 of [RFC6052].
> >
> > Thanks.
> >
> > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org>
> wrote:
> >
> >>
> >> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> >> consider the following document:
> >> - 'IP Version 6 Addressing Architecture'
> >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
> >>
> >> The IESG plans to make a decision in the next few weeks, and solicits
> >> final comments on this action. Please send substantive comments to the
> >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may
> be
> >> sent to iesg@ietf.org instead. In either case, please retain the
> >> beginning of the Subject line to allow automated sorting.
> >>
> >> Abstract
> >>
> >>
> >>    This specification defines the addressing architecture of the IP
> >>    Version 6 (IPv6) protocol.  The document includes the IPv6 addressing
> >>    model, text representations of IPv6 addresses, definition of IPv6
> >>    unicast addresses, anycast addresses, and multicast addresses, and an
> >>    IPv6 node's required addresses.
> >>
> >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
> >>    Architecture".
> >>
> >>
> >>
> >>
> >> The file can be obtained via
> >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
> >>
> >> IESG discussion can be tracked via
> >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
> >>
> >>
> >> No IPR declarations have been submitted directly on this I-D.
> >>
> >>
> >>
> >>
> >> --------------------------------------------------------------------
> >> 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
> > --------------------------------------------------------------------
> >
>



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr">Actually, in addition to your text there still needs to be=
 a recommendation for 64 bit IIDs in all other cases. =C2=A064 bit IIDs are=
(and should remain) the norm for IPv6, I do not want to change that.=C2=A0 =
But the current language say IIDs are always 64 bit except when an address =
begins with binary 000, leaving no room for any other exception.=C2=A0 And =
this is plainly incorrect, I provided two clear exceptions that are already=
 standardized.=C2=A0 Furthermore, IIDs other than 64 bits are in operationa=
l use, with manual configuration and DHCPv6. =C2=A0<div><br></div><div>So I=
&#39;d suggest;</div><div><br></div>However, the Interface ID of unicast ad=
dresses used for<br>Stateless Address Autoconfiguration [RFC4862] is requir=
ed<br><div>to be 64 bits long, in all other cases it is recommended to=C2=
=A0</div><div>be 64 bits long.=C2=A0=C2=A0</div><div><div class=3D"gmail_ex=
tra">=C2=A0</div><div class=3D"gmail_extra">The other option is to enumerat=
e all the exceptions, requiring the document to be updated every time a new=
 exception is standardized.</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">At an earlier stage I suggested restrictin=
g the applicability<br>
of the &quot;However...&quot; sentence to SLAAC [RFC4862]. A short way<br>
of doing this would be<br>
<br>
However, the Interface ID of unicast addresses used for<br>
Stateless Address Autoconfiguration [RFC4862] is required<br>
to be 64 bits long.<br>
<br>
Regards<br>
=C2=A0 =C2=A0Brian<br>
<br>
On 14/02/2017 11:32, David Farmer wrote:<br>
&gt; I have concerns with the following text;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid le=
ngth up to<br>
&gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For example, [RFC6164] standardises 1=
27 bit prefixes<br>
&gt;=C2=A0 =C2=A0 on inter-router point-to-point links. However, the Interf=
ace ID of<br>
&gt;=C2=A0 =C2=A0 all unicast addresses, except those that start with the b=
inary value<br>
&gt;=C2=A0 =C2=A0 000, is required to be 64 bits long.=C2=A0 The rationale =
for the 64 bit<br>
&gt;=C2=A0 =C2=A0 boundary in IPv6 addresses can be found in [RFC7421]<br>
&gt;<br>
&gt; The third sentence seems to limit exceptions to 64 bit IIDs to exclusi=
vely<br>
&gt; addresses that start with binary vale of 000.=C2=A0 There are at least=
 two other<br>
&gt; exceptions from standards track RFCs, that should be more clear accoun=
ted<br>
&gt; for in this text.=C2=A0 First is [RFC6164] point-to-point links, as me=
ntioned in<br>
&gt; the previous sentence.=C2=A0 I think the clear intent of [RFC6164] is =
to allow<br>
&gt; one(1) Bit IIDs for point to point-to-point links using any Global Uni=
cast<br>
&gt; Address, not just those that start with 000.=C2=A0 Second is, [RFC6052=
], which<br>
&gt; updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for a=
ny<br>
&gt; Global Unicast Address when used for IPv4/IPv6 translation, referred t=
o as<br>
&gt; &quot;&quot;Network-Specific Prefix&quot; unique to the organization d=
eploying the address<br>
&gt; translators,&quot; in section 2.2 of [RFC6052].<br>
&gt;<br>
&gt; Thanks.<br>
&gt;<br>
&gt; On Wed, Feb 1, 2017 at 5:51 PM, The IESG &lt;<a href=3D"mailto:iesg-se=
cretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; The IESG has received a request from the IPv6 Maintenance WG (6man=
) to<br>
&gt;&gt; consider the following document:<br>
&gt;&gt; - &#39;IP Version 6 Addressing Architecture&#39;<br>
&gt;&gt;=C2=A0 =C2=A0&lt;draft-ietf-6man-rfc4291bis-<wbr>07.txt&gt; as Inte=
rnet Standard<br>
&gt;&gt;<br>
&gt;&gt; The IESG plans to make a decision in the next few weeks, and solic=
its<br>
&gt;&gt; final comments on this action. Please send substantive comments to=
 the<br>
&gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists b=
y 2017-03-01. Exceptionally, comments may be<br>
&gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead=
. In either case, please retain the<br>
&gt;&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;&gt;<br>
&gt;&gt; Abstract<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 This specification defines the addressing architectur=
e of the IP<br>
&gt;&gt;=C2=A0 =C2=A0 Version 6 (IPv6) protocol.=C2=A0 The document include=
s the IPv6 addressing<br>
&gt;&gt;=C2=A0 =C2=A0 model, text representations of IPv6 addresses, defini=
tion of IPv6<br>
&gt;&gt;=C2=A0 =C2=A0 unicast addresses, anycast addresses, and multicast a=
ddresses, and an<br>
&gt;&gt;=C2=A0 =C2=A0 IPv6 node&#39;s required addresses.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 This document obsoletes RFC 4291, &quot;IP Version 6 =
Addressing<br>
&gt;&gt;=C2=A0 =C2=A0 Architecture&quot;.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; The file can be obtained via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc429=
1bis/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<w=
br>doc/draft-ietf-6man-<wbr>rfc4291bis/</a><br>
&gt;&gt;<br>
&gt;&gt; IESG discussion can be tracked via<br>
&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-rfc429=
1bis/ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf=
.org/<wbr>doc/draft-ietf-6man-<wbr>rfc4291bis/ballot/</a><br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>--------<br>
&gt;&gt; IETF IPv6 working group mailing list<br>
&gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/l=
istinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mai=
lman/<wbr>listinfo/ipv6</a><br>
&gt;&gt; ------------------------------<wbr>------------------------------<=
wbr>--------<br>
&gt;&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&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" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman=
/<wbr>listinfo/ipv6</a><br>
&gt; ------------------------------<wbr>------------------------------<wbr>=
--------<br>
&gt;<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email=
:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Offic=
e of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218=
 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minnea=
polis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div></div>

--94eb2c12318c59bbd305487f34b9--


From nobody Tue Feb 14 07:50:41 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CA7E129453; Tue, 14 Feb 2017 07:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ZkHenFffo_XV; Tue, 14 Feb 2017 07:50:35 -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 C44B71293DC; Tue, 14 Feb 2017 07:50:31 -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 v1EFoUI9054338; Tue, 14 Feb 2017 08:50:30 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EFoScr054328 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 08:50:28 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 07:50:28 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 07:50:27 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSw
Date: Tue, 14 Feb 2017 15:50:27 +0000
Message-ID: <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
In-Reply-To: <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CTSdbWiXG3F6cuTqN8p4s6LGpPA>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:50:39 -0000

HI Stewart,

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 1:51 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; Stewart Bryant
> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Hi Fred
>=20
> Looks like a good point on RFC4821.

OK.

> As to you first point remember that the convergence process disrupts the
> traffic flow as it does so, and that this will repeat every 10 mins as
> it tries to re-optimise.

Yes, you are right. So, even in the case of RFC1981bis it might not be a
good idea to store discovered MTUs in the network layer when there
is ECMP in the path. (Which could be any time at all.)

You briefly mentioned the authorship in your earlier post. As you well
know, the corporate affiliation of two of the authors no longer exists.

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

> - Stewart
>=20
>=20
> On 10/02/2017 15:38, Templin, Fred L wrote:
> > Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in =
the
> > network as long as ICMP PTBs are not blocked. RFC1981bis will eventuall=
y
> > converge to the minimum MTU of all paths in the multipath, and so it is
> > still OK to store the MTU in the network layer where it would be shared
> > by all flows.
> >
> > ECMP does present challenges for RFC4821, however. If a first transport
> > session discovers a large MTU and shares it with a second transport
> > session, the second session may take a very different path where there
> > is a smaller MTU and encounter a black hole. IMHO, it might be a good
> > idea to file an erratum to RFC4821 explaining how ECMP might cause
> > problems if discovered MTUs are shared between sessions.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> -----Original Message-----
> >> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
> >> Sent: Friday, February 10, 2017 2:21 AM
> >> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <s=
tewart@g3ysx.org.uk>; gen-art@ietf.org
> >> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.=
org
> >> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>
> >>
> >>
> >> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>> Stewart,
> >>>
> >>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>> ...
> >>>> I wonder if we would best serve both our future and our heritage
> >>>> if we declared RFC1981 as historic, and either left the idea there,
> >>>> or declared it as historic and wrote a new text from a clean start?
> >>> I don't see that. It's a stable, widely deployed, interoperable
> >>> mechanism. That is rather orthogonal to the issue that has been raise=
d,
> >>> which is that faulty ICMPv6 filtering blocks it on many, many paths
> >>> across the Internet.
> >> I will not debate whether it is faulty or not, but it seems that in
> >> practice the
> >> Internet breaks the mechanism. However it breaks it is a way that seem=
s
> >> disruptive to some user traffic. The document is really guidance
> >> one how hosts might use  ICMP for optimization, and arguable need
> >> not be a standard at all.
> >>
> >> My remark about heritage is that this vintage draft is very much a
> >> product of
> >> its time, and really needs modernizing, and after modernizing ought to
> >> look quite different, and thus maybe we should employ a procedure
> >> other than a simple replacement.
> >>
> >>
> >>> ...
> >>>> It is concerning that the draft does not talk in any detail about
> >>>> how modern ECMP works, i.e. using the five tuple, and noting that
> >>>> the PMTU may be different depending on the transport layer port
> >>>> numbers.
> >>> Has this problem been analysed for, say, IPv4? And does the real worl=
d
> >>> contain ECMP setups with different MTUs on different paths?
> >> I don't know if anyone has looked. Since the mechanism is
> >> self-correcting albeit
> >> with some disruption to user traffic it looks to the application and t=
he
> >> application
> >> user, just like the Internet not working for a few moments.
> >>
> >> In a well managed SP network there should not be, but neither should t=
here
> >> be asymmetric path costs, but there are. The less well manage private
> >> networks are less well managed.
> >>
> >>
> >>>> Given that a very large fraction of packets will traverse an MPLS
> >>>> network at some point, I am surprised that there is no text talking
> >>>> about the importance of providing support for this feature in the
> >>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
> >>> I don't understand. How does the fact that there might be some MPLS
> >>> segments along the path affect end-to-end PMTUD?
> >> The point that RFC3988 makes is that MPLS looks like a single hop to I=
P
> >> and the
> >> PE has to fragment or has to reply with an ICMP error message to suppo=
rt
> >> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
> >> result
> >> in the right response at the end node.
> >>
> >> My point is that the draft is silent on the subject, and perhaps it
> >> should not be.
> >>
> >> However your question make me ask a further question. The draft is als=
o
> >> silent
> >> on NATs. Is there any advice needed for people designing and configuri=
ng
> >> NATs?
> >>
> >>>> =3D=3D=3D=3D=3D=3D
> >>>>
> >>>>      If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementati=
on
> >>>>      could use the flow id as the local representation of a path. Pa=
ckets
> >>>>      sent to a particular destination but belonging to different flo=
ws may
> >>>>      use different paths, with the choice of path depending on the f=
low
> >>>>      id.  This approach will result in the use of optimally sized pa=
ckets
> >>>>      on a per-flow basis, providing finer granularity than PMTU valu=
es
> >>>>      maintained on a per-destination basis.
> >>>>
> >>>> SB> How widely is flow-id supported in networks? I thought that the
> >>>> SB> current position was that it was unreliable as an ECMP indicator
> >>>> SB> and thus routers tended to glean information from the packet the=
mselves.
> >>> This is future-proofing. Agreed, usage today is limited.
> >>>
> >>> (But it would be better to call it the Flow Label for consistency wit=
h other
> >>> recent RFCs.)
> >> Well the question is whether it is simply limited today, or broken tod=
ay
> >> in a manner that
> >> is irrecoverable? I don't know, but I do know that the mainstream ECMP
> >> approach
> >> is the five-tuple. There is something akin to the flow label being
> >> deployed in MPLS. However
> >> what distinguishes the MPLS Entropy Label is that it is inserted (and
> >> removed) by the
> >> service provider and is therefore trusted by the service provider.
> >>
> >>> I think your other comments are all valuable.
> >> Thank you.
> >>
> >> Stewart
> >>
> >> --------------------------------------------------------------------
> >> IETF IPv6 working group mailing list
> >> ipv6@ietf.org
> >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >> --------------------------------------------------------------------
> >
>=20



From nobody Tue Feb 14 07:55:42 2017
Return-Path: <prvs=1218062e19=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E040D129483 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:55:40 -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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lv6QELne3WyI for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 07:55:39 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49397129453 for <ietf@ietf.org>; Tue, 14 Feb 2017 07:55:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1487087607; x=1487692407; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=e7hvvC91v+Psesf+k8R72vAFN 735HCD9ztaONUFqh4I=; b=gL3RCEBC1MIdlTBqPPm0i/iP68Penm7HlTsA0EMtB OCbUx++za93xe2weOd4ROhqryLki7ucW8IGxO/6e1Tu55Oqn/KSKv3NOqf9Nlems TBlcn01LrYUtAtRU8NAdy1aE9E+TapF4xpE1J5cX3qA5Cyc57+aEqof6zF02EXQE CU=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=WKb81CBBIgS6RtaDImN6yBXPYHtMlD1SIqulcq2CvZps0R+QqFfzOPVHn97A uFBZj73qsLjErpbPH3ZTkOi2ziCH99IyZ6TVKgd2ppM8t727ojA17/w38 DYpFFQHebgJxbsIMZqGDzMMopBOSL+atxE+9nL1HDWqOFC/05LO/W0=;
X-MDAV-Processed: mail.consulintel.es, Tue, 14 Feb 2017 16:53:27 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 14 Feb 2017 16:53:26 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005367310.msg for <ietf@ietf.org>; Tue, 14 Feb 2017 16:53:25 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170214:md50005367310::3jR+6QjTOIwrqCxh:000009DZ
X-Return-Path: prvs=1218062e19=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Tue, 14 Feb 2017 16:53:24 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
Message-ID: <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es>
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com>
In-Reply-To: <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SLA-S8hltmmnu5lGdBVjx9fqYSs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 15:55:41 -0000

Agree, we shouldn=E2=80=99t change that. Must be 64 bits.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn.edu>
Responder a: <farmer@umn.edu>
Fecha: martes, 14 de febrero de 2017, 16:27
Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>, 6man WG =
<ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Ad=
dressing Architecture) to Internet Standard

    Actually, in addition to your text there still needs to be a recommenda=
tion for 64 bit IIDs in all other cases.  64 bit IIDs are(and should remain=
) the norm for IPv6, I do not want to change that.  But the current languag=
e say IIDs are always 64 bit except when an address begins with binary 000,=
 leaving no room for any other exception.  And this is plainly incorrect, I=
 provided two clear exceptions that are already standardized.  Furthermore,=
 IIDs other than 64 bits are in operational use, with manual configuration =
and DHCPv6. =20
    So I'd suggest;
   =20
    However, the Interface ID of unicast addresses used for
    Stateless Address Autoconfiguration [RFC4862] is required
    to be 64 bits long, in all other cases it is recommended to=20
    be 64 bits long. =20
    =20
    The other option is to enumerate all the exceptions, requiring the docu=
ment to be updated every time a new exception is standardized.
   =20
    On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <brian.e.carpenter@g=
mail.com> wrote:
   =20
    At an earlier stage I suggested restricting the applicability
    of the "However..." sentence to SLAAC [RFC4862]. A short way
    of doing this would be
   =20
    However, the Interface ID of unicast addresses used for
    Stateless Address Autoconfiguration [RFC4862] is required
    to be 64 bits long.
   =20
    Regards
       Brian
   =20
    On 14/02/2017 11:32, David Farmer wrote:
    > I have concerns with the following text;
    >
    >    IPv6 unicast routing is based on prefixes of any valid length up t=
o
    >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixe=
s
    >    on inter-router point-to-point links. However, the Interface ID of
    >    all unicast addresses, except those that start with the binary val=
ue
    >    000, is required to be 64 bits long.  The rationale for the 64 bit
    >    boundary in IPv6 addresses can be found in [RFC7421]
    >
    > The third sentence seems to limit exceptions to 64 bit IIDs to exclus=
ively
    > addresses that start with binary vale of 000.  There are at least two=
 other
    > exceptions from standards track RFCs, that should be more clear accou=
nted
    > for in this text.  First is [RFC6164] point-to-point links, as mentio=
ned in
    > the previous sentence.  I think the clear intent of [RFC6164] is to a=
llow
    > one(1) Bit IIDs for point to point-to-point links using any Global Un=
icast
    > Address, not just those that start with 000.  Second is, [RFC6052], w=
hich
    > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for =
any
    > Global Unicast Address when used for IPv4/IPv6 translation, referred =
to as
    > ""Network-Specific Prefix" unique to the organization deploying the a=
ddress
    > translators," in section 2.2 of [RFC6052].
    >
    > Thanks.
    >
    > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org> wr=
ote:
    >
    >>
    >> The IESG has received a request from the IPv6 Maintenance WG (6man) =
to
    >> consider the following document:
    >> - 'IP Version 6 Addressing Architecture'
    >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
    >>
    >> The IESG plans to make a decision in the next few weeks, and solicit=
s
    >> final comments on this action. Please send substantive comments to t=
he
    >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments m=
ay be
    >> sent to iesg@ietf.org instead. In either case, please retain the
    >> beginning of the Subject line to allow automated sorting.
    >>
    >> Abstract
    >>
    >>
    >>    This specification defines the addressing architecture of the IP
    >>    Version 6 (IPv6) protocol.  The document includes the IPv6 addres=
sing
    >>    model, text representations of IPv6 addresses, definition of IPv6
    >>    unicast addresses, anycast addresses, and multicast addresses, an=
d an
    >>    IPv6 node's required addresses.
    >>
    >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
    >>    Architecture".
    >>
    >>
    >>
    >>
    >> The file can be obtained via
    >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
    >>
    >> IESG discussion can be tracked via
    >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
    >>
    >>
    >> No IPR declarations have been submitted directly on this I-D.
    >>
    >>
    >>
    >>
    >> --------------------------------------------------------------------
    >> 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
    > --------------------------------------------------------------------
    >
   =20
   =20
   =20
   =20
   =20
   =20
    --=20
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    David Farmer               Email:farmer@umn.edu <mailto:Email%3Afarmer@=
umn.edu>
    Networking & Telecommunication Services
    Office of Information Technology
    University of Minnesota  =20
    2218 University Ave SE        Phone: 612-626-0815
    Minneapolis, MN 55414-3029   Cell: 612-812-9952
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
   =20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Feb 14 08:03:47 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BB312962B for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:03:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RV56NrbSDGa4 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:03:43 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 AB2D81295B2 for <ietf@ietf.org>; Tue, 14 Feb 2017 08:03:39 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 39861995 for <ietf@ietf.org>; Tue, 14 Feb 2017 16:03:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ydw1y8Gu_fKj for <ietf@ietf.org>; Tue, 14 Feb 2017 10:03:39 -0600 (CST)
Received: from mail-vk0-f72.google.com (mail-vk0-f72.google.com [209.85.213.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id D2C54B52 for <ietf@ietf.org>; Tue, 14 Feb 2017 10:03:38 -0600 (CST)
Received: by mail-vk0-f72.google.com with SMTP id r136so91714724vke.6 for <ietf@ietf.org>; Tue, 14 Feb 2017 08:03:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BeUZq8i08TQdL9fMrfZ5+vcksCA6gghqFs/CxfPIN7k=; b=NqWGPAmyWigEOzMFuPPLzXB4cJN3Nxx21RkQ4SbZoVTBLOLlgT+AC/QdwDlyboAsLI 87TrLK9FOrUSFbK2Aw7d6EKbJTgnKWeUMjhbn2N81Rn9ImjbbE/X8UrJWJlfAluoY68E 0MFH+38hwMvKeULuzUiuT9d2HX9mbz8tr2fIob0lNocITRwbQm0qRxZhEMjvtIjfvHX6 3rypnAxiV0wK7HLzYwgZH8si86xcaGDeC7x4gySMetAEfiRXXY70yBNL7Fvnhs9hxNkU XJWYEELiKpOhvZj8cyS9Yiv2rVZQR6AxPazLPLIsPFsF05QxbHGxKlpU356oHWZsKvBF gwZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BeUZq8i08TQdL9fMrfZ5+vcksCA6gghqFs/CxfPIN7k=; b=oEu5h3zY3EZBqY67xeoWnvybFDbQS3+UQYHGfCuqVJ02Im73wZ56dVsYNZ1t0jaCLl Ts557eRtoa7nj2+Fxy0ecey+PCzsDeW/zxZJHCpK4Rd7U2r9JQnTIu3e4EjmiZi88VJE DMaLFtrrICe44Cmg2/Hri/g8lgOPfKbw+nIXeG7w+OeNOPoMdwMVBqSXn4v2rDH+/iS/ giOt66kI9p99dMtob9/69RCYj06Mrdmr4JsPHihv9cpG8K5cjN5EpxGPvHGTfZdVY/3s gdQOiYypTkdgcCTvQiWGgnKgiYZUCUttXOdW2gvr2WqNG1VX6pqAHUd8IFdNzU7WEpYz YI4A==
X-Gm-Message-State: AMke39kwF4w8RPr+EzRhCnacctoEWtjuqxjQDpQPjf8Akyw0m8D9AImNxKl3sIZKYzwccDx4qqJtq+Se5Tl6W5GhbnVIIIkKRwiCRj2L3yicRGdL4QtDp6EogO06VeEpXj4c8cUvHbwgW3/Djus=
X-Received: by 10.176.6.3 with SMTP id f3mr13010901uaf.37.1487088218227; Tue, 14 Feb 2017 08:03:38 -0800 (PST)
X-Received: by 10.176.6.3 with SMTP id f3mr13010876uaf.37.1487088217941; Tue, 14 Feb 2017 08:03:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Tue, 14 Feb 2017 08:03:37 -0800 (PST)
In-Reply-To: <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es>
From: David Farmer <farmer@umn.edu>
Date: Tue, 14 Feb 2017 10:03:37 -0600
Message-ID: <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Jordi Palet Martinez <jordi.palet@consulintel.es>
Content-Type: multipart/alternative; boundary=94eb2c048440fb71f405487fb403
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/--KkL2c8lM_mAt3OeKxzYfG9FT4>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:03:45 -0000

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

The problem we want it to be 64 bits except when it's not suppose to be,
such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv6 translators
with /96 Network-Specific Prefix.

On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> Agree, we shouldn=E2=80=99t change that. Must be 64 bits.
>
> Regards,
> Jordi
>
>
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn.ed=
u
> >
> Responder a: <farmer@umn.edu>
> Fecha: martes, 14 de febrero de 2017, 16:27
> Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>, 6man
> WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
> Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6
> Addressing Architecture) to Internet Standard
>
>     Actually, in addition to your text there still needs to be a
> recommendation for 64 bit IIDs in all other cases.  64 bit IIDs are(and
> should remain) the norm for IPv6, I do not want to change that.  But the
> current language say IIDs are always 64 bit except when an address begins
> with binary 000, leaving no room for any other exception.  And this is
> plainly incorrect, I provided two clear exceptions that are already
> standardized.  Furthermore, IIDs other than 64 bits are in operational us=
e,
> with manual configuration and DHCPv6.
>     So I'd suggest;
>
>     However, the Interface ID of unicast addresses used for
>     Stateless Address Autoconfiguration [RFC4862] is required
>     to be 64 bits long, in all other cases it is recommended to
>     be 64 bits long.
>
>     The other option is to enumerate all the exceptions, requiring the
> document to be updated every time a new exception is standardized.
>
>     On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>     At an earlier stage I suggested restricting the applicability
>     of the "However..." sentence to SLAAC [RFC4862]. A short way
>     of doing this would be
>
>     However, the Interface ID of unicast addresses used for
>     Stateless Address Autoconfiguration [RFC4862] is required
>     to be 64 bits long.
>
>     Regards
>        Brian
>
>     On 14/02/2017 11:32, David Farmer wrote:
>     > I have concerns with the following text;
>     >
>     >    IPv6 unicast routing is based on prefixes of any valid length up
> to
>     >    128 [BCP198].  For example, [RFC6164] standardises 127 bit
> prefixes
>     >    on inter-router point-to-point links. However, the Interface ID =
of
>     >    all unicast addresses, except those that start with the binary
> value
>     >    000, is required to be 64 bits long.  The rationale for the 64 b=
it
>     >    boundary in IPv6 addresses can be found in [RFC7421]
>     >
>     > The third sentence seems to limit exceptions to 64 bit IIDs to
> exclusively
>     > addresses that start with binary vale of 000.  There are at least
> two other
>     > exceptions from standards track RFCs, that should be more clear
> accounted
>     > for in this text.  First is [RFC6164] point-to-point links, as
> mentioned in
>     > the previous sentence.  I think the clear intent of [RFC6164] is to
> allow
>     > one(1) Bit IIDs for point to point-to-point links using any Global
> Unicast
>     > Address, not just those that start with 000.  Second is, [RFC6052],
> which
>     > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes fo=
r
> any
>     > Global Unicast Address when used for IPv4/IPv6 translation, referre=
d
> to as
>     > ""Network-Specific Prefix" unique to the organization deploying the
> address
>     > translators," in section 2.2 of [RFC6052].
>     >
>     > Thanks.
>     >
>     > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org>
> wrote:
>     >
>     >>
>     >> The IESG has received a request from the IPv6 Maintenance WG (6man=
)
> to
>     >> consider the following document:
>     >> - 'IP Version 6 Addressing Architecture'
>     >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>     >>
>     >> The IESG plans to make a decision in the next few weeks, and
> solicits
>     >> final comments on this action. Please send substantive comments to
> the
>     >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments
> may be
>     >> sent to iesg@ietf.org instead. In either case, please retain the
>     >> beginning of the Subject line to allow automated sorting.
>     >>
>     >> Abstract
>     >>
>     >>
>     >>    This specification defines the addressing architecture of the I=
P
>     >>    Version 6 (IPv6) protocol.  The document includes the IPv6
> addressing
>     >>    model, text representations of IPv6 addresses, definition of IP=
v6
>     >>    unicast addresses, anycast addresses, and multicast addresses,
> and an
>     >>    IPv6 node's required addresses.
>     >>
>     >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>     >>    Architecture".
>     >>
>     >>
>     >>
>     >>
>     >> The file can be obtained via
>     >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>     >>
>     >> IESG discussion can be tracked via
>     >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot=
/
>     >>
>     >>
>     >> No IPR declarations have been submitted directly on this I-D.
>     >>
>     >>
>     >>
>     >>
>     >> ------------------------------------------------------------
> --------
>     >> IETF IPv6 working group mailing list
>     >> ipv6@ietf.org
>     >> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv=
6
>     >> ------------------------------------------------------------
> --------
>     >>
>     >
>     >
>     >
>     >
>     >
>     > -------------------------------------------------------------------=
-
>     > IETF IPv6 working group mailing list
>     > ipv6@ietf.org
>     > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>     > -------------------------------------------------------------------=
-
>     >
>
>
>
>
>
>
>     --
>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>     David Farmer               Email:farmer@umn.edu <mailto:
> Email%3Afarmer@umn.edu>
>     Networking & Telecommunication Services
>     Office of Information Technology
>     University of Minnesota
>     2218 University Ave SE        Phone: 612-626-0815
>     Minneapolis, MN 55414-3029   Cell: 612-812-9952
>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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

<div dir=3D"ltr">The problem we want it to be 64 bits except when it&#39;s =
not suppose to be, such as RFC6164 for point-to-point and RFC6052 for IPv4/=
IPv6 translators with /96 Network-Specific Prefix.<br><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Tue, Feb 14, 2017 at 9:53 AM, JORDI=
 PALET MARTINEZ <span dir=3D"ltr">&lt;<a href=3D"mailto:jordi.palet@consuli=
ntel.es" target=3D"_blank">jordi.palet@consulintel.es</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">Agree, we shouldn=E2=
=80=99t change that. Must be 64 bits.<br>
<br>
Regards,<br>
Jordi<br>
<br>
<br>
-----Mensaje original-----<br>
De: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org=
</a>&gt; en nombre de David Farmer &lt;<a href=3D"mailto:farmer@umn.edu">fa=
rmer@umn.edu</a>&gt;<br>
Responder a: &lt;<a href=3D"mailto:farmer@umn.edu">farmer@umn.edu</a>&gt;<b=
r>
Fecha: martes, 14 de febrero de 2017, 16:27<br>
Para: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;<br>
CC: &lt;<a href=3D"mailto:draft-ietf-6man-rfc4291bis@ietf.org">draft-ietf-6=
man-rfc4291bis@<wbr>ietf.org</a>&gt;, &lt;<a href=3D"mailto:6man-chairs@iet=
f.org">6man-chairs@ietf.org</a>&gt;, 6man WG &lt;<a href=3D"mailto:ipv6@iet=
f.org">ipv6@ietf.org</a>&gt;, IETF-Discussion Discussion &lt;<a href=3D"mai=
lto:ietf@ietf.org">ietf@ietf.org</a>&gt;<br>
Asunto: Re: Last Call: &lt;draft-ietf-6man-rfc4291bis-<wbr>07.txt&gt; (IP V=
ersion 6 Addressing Architecture) to Internet Standard<br>
<br>
=C2=A0 =C2=A0 Actually, in addition to your text there still needs to be a =
recommendation for 64 bit IIDs in all other cases.=C2=A0 64 bit IIDs are(an=
d should remain) the norm for IPv6, I do not want to change that.=C2=A0 But=
 the current language say IIDs are always 64 bit except when an address beg=
ins with binary 000, leaving no room for any other exception.=C2=A0 And thi=
s is plainly incorrect, I provided two clear exceptions that are already st=
andardized.=C2=A0 Furthermore, IIDs other than 64 bits are in operational u=
se, with manual configuration and DHCPv6.<br>
=C2=A0 =C2=A0 So I&#39;d suggest;<br>
<br>
=C2=A0 =C2=A0 However, the Interface ID of unicast addresses used for<br>
=C2=A0 =C2=A0 Stateless Address Autoconfiguration [RFC4862] is required<br>
=C2=A0 =C2=A0 to be 64 bits long, in all other cases it is recommended to<b=
r>
=C2=A0 =C2=A0 be 64 bits long.<br>
<br>
=C2=A0 =C2=A0 The other option is to enumerate all the exceptions, requirin=
g the document to be updated every time a new exception is standardized.<br=
>
<br>
=C2=A0 =C2=A0 On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter &lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt=
; wrote:<br>
<br>
=C2=A0 =C2=A0 At an earlier stage I suggested restricting the applicability=
<br>
=C2=A0 =C2=A0 of the &quot;However...&quot; sentence to SLAAC [RFC4862]. A =
short way<br>
=C2=A0 =C2=A0 of doing this would be<br>
<br>
=C2=A0 =C2=A0 However, the Interface ID of unicast addresses used for<br>
=C2=A0 =C2=A0 Stateless Address Autoconfiguration [RFC4862] is required<br>
=C2=A0 =C2=A0 to be 64 bits long.<br>
<br>
=C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian<br>
<br>
=C2=A0 =C2=A0 On 14/02/2017 11:32, David Farmer wrote:<br>
=C2=A0 =C2=A0 &gt; I have concerns with the following text;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes o=
f any valid length up to<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For example, [RFC6164] =
standardises 127 bit prefixes<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 on inter-router point-to-point links. Howev=
er, the Interface ID of<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 all unicast addresses, except those that st=
art with the binary value<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 000, is required to be 64 bits long.=C2=A0 =
The rationale for the 64 bit<br>
=C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 boundary in IPv6 addresses can be found in =
[RFC7421]<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The third sentence seems to limit exceptions to 64 bit I=
IDs to exclusively<br>
=C2=A0 =C2=A0 &gt; addresses that start with binary vale of 000.=C2=A0 Ther=
e are at least two other<br>
=C2=A0 =C2=A0 &gt; exceptions from standards track RFCs, that should be mor=
e clear accounted<br>
=C2=A0 =C2=A0 &gt; for in this text.=C2=A0 First is [RFC6164] point-to-poin=
t links, as mentioned in<br>
=C2=A0 =C2=A0 &gt; the previous sentence.=C2=A0 I think the clear intent of=
 [RFC6164] is to allow<br>
=C2=A0 =C2=A0 &gt; one(1) Bit IIDs for point to point-to-point links using =
any Global Unicast<br>
=C2=A0 =C2=A0 &gt; Address, not just those that start with 000.=C2=A0 Secon=
d is, [RFC6052], which<br>
=C2=A0 =C2=A0 &gt; updates [RFC4921] and seems to allow 32 bit IIDs or /96 =
prefixes for any<br>
=C2=A0 =C2=A0 &gt; Global Unicast Address when used for IPv4/IPv6 translati=
on, referred to as<br>
=C2=A0 =C2=A0 &gt; &quot;&quot;Network-Specific Prefix&quot; unique to the =
organization deploying the address<br>
=C2=A0 =C2=A0 &gt; translators,&quot; in section 2.2 of [RFC6052].<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; Thanks.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; On Wed, Feb 1, 2017 at 5:51 PM, The IESG &lt;<a href=3D"=
mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; The IESG has received a request from the IPv6 Mainte=
nance WG (6man) to<br>
=C2=A0 =C2=A0 &gt;&gt; consider the following document:<br>
=C2=A0 =C2=A0 &gt;&gt; - &#39;IP Version 6 Addressing Architecture&#39;<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0&lt;draft-ietf-6man-rfc4291bis-<wbr>07.t=
xt&gt; as Internet Standard<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; The IESG plans to make a decision in the next few we=
eks, and solicits<br>
=C2=A0 =C2=A0 &gt;&gt; final comments on this action. Please send substanti=
ve comments to the<br>
=C2=A0 =C2=A0 &gt;&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> m=
ailing lists by 2017-03-01. Exceptionally, comments may be<br>
=C2=A0 =C2=A0 &gt;&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.o=
rg</a> instead. In either case, please retain the<br>
=C2=A0 =C2=A0 &gt;&gt; beginning of the Subject line to allow automated sor=
ting.<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; Abstract<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 This specification defines the addressi=
ng architecture of the IP<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 Version 6 (IPv6) protocol.=C2=A0 The do=
cument includes the IPv6 addressing<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 model, text representations of IPv6 add=
resses, definition of IPv6<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 unicast addresses, anycast addresses, a=
nd multicast addresses, and an<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 IPv6 node&#39;s required addresses.<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 This document obsoletes RFC 4291, &quot=
;IP Version 6 Addressing<br>
=C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 Architecture&quot;.<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; The file can be obtained via<br>
=C2=A0 =C2=A0 &gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ie=
tf-6man-rfc4291bis/" rel=3D"noreferrer" target=3D"_blank">https://datatrack=
er.ietf.org/<wbr>doc/draft-ietf-6man-<wbr>rfc4291bis/</a><br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; IESG discussion can be tracked via<br>
=C2=A0 =C2=A0 &gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ie=
tf-6man-rfc4291bis/ballot/" rel=3D"noreferrer" target=3D"_blank">https://da=
tatracker.ietf.org/<wbr>doc/draft-ietf-6man-<wbr>rfc4291bis/ballot/</a><br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; No IPR declarations have been submitted directly on =
this I-D.<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; ------------------------------<wbr>-----------------=
-------------<wbr>--------<br>
=C2=A0 =C2=A0 &gt;&gt; IETF IPv6 working group mailing list<br>
=C2=A0 =C2=A0 &gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><b=
r>
=C2=A0 =C2=A0 &gt;&gt; Administrative Requests: <a href=3D"https://www.ietf=
.org/mailman/listinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://ww=
w.ietf.org/mailman/<wbr>listinfo/ipv6</a><br>
=C2=A0 =C2=A0 &gt;&gt; ------------------------------<wbr>-----------------=
-------------<wbr>--------<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; ------------------------------<wbr>---------------------=
---------<wbr>--------<br>
=C2=A0 =C2=A0 &gt; IETF IPv6 working group mailing list<br>
=C2=A0 =C2=A0 &gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
=C2=A0 =C2=A0 &gt; Administrative Requests: <a href=3D"https://www.ietf.org=
/mailman/listinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">https://www.ie=
tf.org/mailman/<wbr>listinfo/ipv6</a><br>
=C2=A0 =C2=A0 &gt; ------------------------------<wbr>---------------------=
---------<wbr>--------<br>
=C2=A0 =C2=A0 &gt;<br>
<br>
<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 --<br>
=C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
=C2=A0 =C2=A0 David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0<a href=3D"mailto:Email%3Afarmer@umn.edu">Email:farmer@umn.edu</a> &l=
t;mailto:<a href=3D"mailto:Email%253Afarmer@umn.edu">Email%3Afarmer@umn.edu=
</a><wbr>&gt;<br>
=C2=A0 =C2=A0 Networking &amp; Telecommunication Services<br>
=C2=A0 =C2=A0 Office of Information Technology<br>
=C2=A0 =C2=A0 University of Minnesota<br>
=C2=A0 =C2=A0 2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a h=
ref=3D"tel:612-626-0815" value=3D"+16126260815">612-626-0815</a><br>
=C2=A0 =C2=A0 Minneapolis, MN 55414-3029=C2=A0 =C2=A0Cell: <a href=3D"tel:6=
12-812-9952" value=3D"+16128129952">612-812-9952</a><br>
=C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
******************************<wbr>****************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" rel=3D"noreferrer" target=3D"_blank">=
http://www.consulintel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.<br>
<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email=
:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Offic=
e of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218=
 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minnea=
polis, MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c048440fb71f405487fb403--


From nobody Tue Feb 14 08:09:25 2017
Return-Path: <prvs=1218062e19=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C10FF129674 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:09: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] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZgK1ailn3QEl for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:09:22 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC8B6129653 for <ietf@ietf.org>; Tue, 14 Feb 2017 08:09:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1487088436; x=1487693236; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=4wRiAOzFSgI8vPyjP+nKDsvYE KvLdUI2KuGh2/+cTYA=; b=jtLb6ol9Nd3x0tCFDuEsOXU4qoOGZxxmFFx4jmEms 3iAaxiJSdWnzbwm4KpjCjrd4c7Dnm5tQHjTUdQlmzYtwOcPLUObLZ6pPZ1/k8pCv x7BZZYjDGlBxGnGkLTEd2fEdfbQlHCfwjIKSL4DGBt9f48YuYy81R3BAOs06FBuM UA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=U2j0POE3G8Lba75LS4XJZ8tJhPPzumZuQYqWdLdTQxgH1Nz2lJjJtm/mLMyJ qhJPG5r0fIW5SdCIXQfaWPjisL8AXz8jVCbS3pBHCceTcfw+OXVzHvNip 4Ywbj2plVJz0Gw+l9o9v5lTZMMqn9LdQK+NGb7j7atkAWkAvcJZ5oU=;
X-MDAV-Processed: mail.consulintel.es, Tue, 14 Feb 2017 17:07:16 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 14 Feb 2017 17:07:15 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005367324.msg for <ietf@ietf.org>; Tue, 14 Feb 2017 17:07:14 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170214:md50005367324::X7ucdnzz1hT+95Xl:00002RP5
X-Return-Path: prvs=1218062e19=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1e.0.170107
Date: Tue, 14 Feb 2017 17:07:09 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: 6man WG <ipv6@ietf.org>, <draft-ietf-6man-rfc4291bis@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org>
Message-ID: <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es>
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com>
In-Reply-To: <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gOo8WgKBXndNW7tQq9t42z6tkwo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:09:24 -0000

I understand that, but those are two clear exceptions, no others should be =
=E2=80=9Callowed=E2=80=9D by default.

Keeping the door open is not good in my opinion. Specific exceptions must b=
e taken in consideration one by one.

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn.edu>
Responder a: <farmer@umn.edu>
Fecha: martes, 14 de febrero de 2017, 17:03
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: 6man WG <ipv6@ietf.org>, <draft-ietf-6man-rfc4291bis@ietf.org>, IETF-Di=
scussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org>
Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Ad=
dressing Architecture) to Internet Standard

    The problem we want it to be 64 bits except when it's not suppose to be=
, such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv6 translators =
with /96 Network-Specific Prefix.
   =20
    On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ <jordi.palet@cons=
ulintel.es> wrote:
   =20
    Agree, we shouldn=E2=80=99t change that. Must be 64 bits.
   =20
    Regards,
    Jordi
   =20
   =20
    -----Mensaje original-----
    De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn.=
edu>
    Responder a: <farmer@umn.edu>
    Fecha: martes, 14 de febrero de 2017, 16:27
    Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
    CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>, 6man=
 WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
    Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version =
6 Addressing Architecture) to Internet Standard
   =20
        Actually, in addition to your text there still needs to be a recomm=
endation for 64 bit IIDs in all other cases.  64 bit IIDs are(and should re=
main) the norm for IPv6, I do not want to change that.  But the current lan=
guage say IIDs are always 64 bit except when an address begins with binary =
000, leaving no room for any other exception.  And this is plainly incorrec=
t, I provided two clear exceptions that are already standardized.  Furtherm=
ore, IIDs other than 64 bits are in operational use, with manual configurat=
ion and DHCPv6.
        So I'd suggest;
   =20
        However, the Interface ID of unicast addresses used for
        Stateless Address Autoconfiguration [RFC4862] is required
        to be 64 bits long, in all other cases it is recommended to
        be 64 bits long.
   =20
        The other option is to enumerate all the exceptions, requiring the =
document to be updated every time a new exception is standardized.
   =20
        On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <brian.e.carpent=
er@gmail.com> wrote:
   =20
        At an earlier stage I suggested restricting the applicability
        of the "However..." sentence to SLAAC [RFC4862]. A short way
        of doing this would be
   =20
        However, the Interface ID of unicast addresses used for
        Stateless Address Autoconfiguration [RFC4862] is required
        to be 64 bits long.
   =20
        Regards
           Brian
   =20
        On 14/02/2017 11:32, David Farmer wrote:
        > I have concerns with the following text;
        >
        >    IPv6 unicast routing is based on prefixes of any valid length =
up to
        >    128 [BCP198].  For example, [RFC6164] standardises 127 bit pre=
fixes
        >    on inter-router point-to-point links. However, the Interface I=
D of
        >    all unicast addresses, except those that start with the binary=
 value
        >    000, is required to be 64 bits long.  The rationale for the 64=
 bit
        >    boundary in IPv6 addresses can be found in [RFC7421]
        >
        > The third sentence seems to limit exceptions to 64 bit IIDs to ex=
clusively
        > addresses that start with binary vale of 000.  There are at least=
 two other
        > exceptions from standards track RFCs, that should be more clear a=
ccounted
        > for in this text.  First is [RFC6164] point-to-point links, as me=
ntioned in
        > the previous sentence.  I think the clear intent of [RFC6164] is =
to allow
        > one(1) Bit IIDs for point to point-to-point links using any Globa=
l Unicast
        > Address, not just those that start with 000.  Second is, [RFC6052=
], which
        > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes =
for any
        > Global Unicast Address when used for IPv4/IPv6 translation, refer=
red to as
        > ""Network-Specific Prefix" unique to the organization deploying t=
he address
        > translators," in section 2.2 of [RFC6052].
        >
        > Thanks.
        >
        > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org=
> wrote:
        >
        >>
        >> The IESG has received a request from the IPv6 Maintenance WG (6m=
an) to
        >> consider the following document:
        >> - 'IP Version 6 Addressing Architecture'
        >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
        >>
        >> The IESG plans to make a decision in the next few weeks, and sol=
icits
        >> final comments on this action. Please send substantive comments =
to the
        >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, commen=
ts may be
        >> sent to iesg@ietf.org instead. In either case, please retain the
        >> beginning of the Subject line to allow automated sorting.
        >>
        >> Abstract
        >>
        >>
        >>    This specification defines the addressing architecture of the=
 IP
        >>    Version 6 (IPv6) protocol.  The document includes the IPv6 ad=
dressing
        >>    model, text representations of IPv6 addresses, definition of =
IPv6
        >>    unicast addresses, anycast addresses, and multicast addresses=
, and an
        >>    IPv6 node's required addresses.
        >>
        >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
        >>    Architecture".
        >>
        >>
        >>
        >>
        >> The file can be obtained via
        >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
        >>
        >> IESG discussion can be tracked via
        >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ball=
ot/
        >>
        >>
        >> No IPR declarations have been submitted directly on this I-D.
        >>
        >>
        >>
        >>
        >> ----------------------------------------------------------------=
----
        >> IETF IPv6 working group mailing list
        >> ipv6@ietf.org
        >> Administrative Requests: https://www.ietf.org/mailman/listinfo/i=
pv6
        >> ----------------------------------------------------------------=
----
        >>
        >
        >
        >
        >
        >
        > -----------------------------------------------------------------=
---
        > IETF IPv6 working group mailing list
        > ipv6@ietf.org
        > Administrative Requests: https://www.ietf.org/mailman/listinfo/ip=
v6
        > -----------------------------------------------------------------=
---
        >
   =20
   =20
   =20
   =20
   =20
   =20
        --
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
        David Farmer               Email:farmer@umn.edu <mailto:Email%3Afar=
mer@umn.edu> <mailto:Email%3Afarmer@umn.edu <mailto:Email%253Afarmer@umn.ed=
u>>
        Networking & Telecommunication Services
        Office of Information Technology
        University of Minnesota
        2218 University Ave SE        Phone: 612-626-0815 <tel:612-626-0815=
>
        Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:612-812-9952>
        =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
   =20
   =20
   =20
   =20
   =20
   =20
   =20
    **********************************************
    IPv4 is over
    Are you ready for the new Internet ?
    http://www.consulintel.es
    The IPv6 Company
   =20
    This electronic message contains information which may be privileged or=
 confidential. The information is intended to be for the use of the individ=
ual(s) named above. If you are not the intended recipient be aware that any=
 disclosure, copying, distribution or use of the contents of this informati=
on, including attached files, is prohibited.
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
   =20
    --=20
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    David Farmer               Email:farmer@umn.edu <mailto:Email%3Afarmer@=
umn.edu>
    Networking & Telecommunication Services
    Office of Information Technology
    University of Minnesota  =20
    2218 University Ave SE        Phone: 612-626-0815
    Minneapolis, MN 55414-3029   Cell: 612-812-9952
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Tue Feb 14 08:13:10 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F41F11294BF; Tue, 14 Feb 2017 08:13:08 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nFU-s9xb1fqP; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (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 7E14212967F; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
Received: by mail-wm0-x243.google.com with SMTP id r18so4282887wmd.3; Tue, 14 Feb 2017 08:13:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=aFYRlUp+zT3cRyTuc5QfAuwZevJdSQ7XkY44NGrREJA=; b=o57p4trTCV2S669d9jhozhYNhwjISSEcqt9PDfPy4SZEQhnEDRzaG3BQCTbT3ldCVy UOFvNt57Hf3MDqsOygpLzAXEMQJWuZpQwT/udHPIbtB/Wt9myTg4XPNg5QW1MbzBKdBO 99C4LK3c8WEV1sno5IMp8d7hF21n/1w25Qq/jQEju4y3BTBPRVk4JeQw+zxrtcyMfDwr 3NHKB4MkiraOcwihRyhZg95sV1AvryL4hNgRLKvE5zV2HwGp3qH11NEYu7iiqRPLfI8A BSThZ2Y3FMsQ3KGU1EOwl5Hx5mDnNs9O3q5/+5Xdf9oNbbkPipw9qxyGzHbkq06dnB6M fNCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=aFYRlUp+zT3cRyTuc5QfAuwZevJdSQ7XkY44NGrREJA=; b=gEMc2K3hAhtZh0szOU/we4ZTh+wNEiOhTf+l34g6atafSz8cUrRLFqJVezQ2vboVRN Cdfi+Vx6oS+2OIqZL+ezlz94aWYOy9eJ77dkT22IJaKTIHRgTYzgissPSThvCme2OLgl udsNDV+0SXFMBEaxH/lgGGb2m3kgztRduunFCxdLIO1fECkQh1k19NewSCnC1F3S6IKj 12B9jF9GTHmpAcKiHO3Ib3oB4wa9BmVH2Ae/SyoZuxTuy0UUtIXyhdyhbzrWwfzzG9EH 7XxcsrFtEJ4zxqhd56lYXjhOq1NIA+ZO09Ca5Ws9OhLfGkOs1FhnFLFsVctZ7j0IM+C8 jEiA==
X-Gm-Message-State: AMke39m4LeP0DrOo8ubEUKy7K7IgS/wuUoWggBXoSDVngweSMbPLBonoAzS6wIBmz+uZZg==
X-Received: by 10.28.185.77 with SMTP id j74mr4122365wmf.76.1487088784984; Tue, 14 Feb 2017 08:13:04 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 8sm4414020wmg.1.2017.02.14.08.13.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 08:13:04 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
Date: Tue, 14 Feb 2017 16:13:03 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N4UWD2Zk4XrFb4B9U0G1yelwJBQ>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:13:09 -0000

On 14/02/2017 15:50, Templin, Fred L wrote:
>
>> As to you first point remember that the convergence process disrupts the
>> traffic flow as it does so, and that this will repeat every 10 mins as
>> it tries to re-optimise.
> Yes, you are right. So, even in the case of RFC1981bis it might not be a
> good idea to store discovered MTUs in the network layer when there
> is ECMP in the path. (Which could be any time at all.)

Yes, I think if you really care about disruption due to packet loss your 
best bet is
to go with the minimum supported MTU.

Forwarding performance is not a issue these days, and core link are over 
provisioned
so you have to wonder how important the efficiency gain is in practice.  
The efficiency
gain produced by this protocol in most networks (1276 vs 1496) is only 
about 15% anyway.

>
> You briefly mentioned the authorship in your earlier post. As you well
> know, the corporate affiliation of two of the authors no longer exists.
My concern was that some authors cannot take part in Auth48 due to not 
providing
active email addresses.

- Stewart

>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>> - Stewart
>>
>>
>> On 10/02/2017 15:38, Templin, Fred L wrote:
>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
>>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
>>> converge to the minimum MTU of all paths in the multipath, and so it is
>>> still OK to store the MTU in the network layer where it would be shared
>>> by all flows.
>>>
>>> ECMP does present challenges for RFC4821, however. If a first transport
>>> session discovers a large MTU and shares it with a second transport
>>> session, the second session may take a very different path where there
>>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
>>> problems if discovered MTUs are shared between sessions.
>>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>> -----Original Message-----
>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>>>> Sent: Friday, February 10, 2017 2:21 AM
>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>>>
>>>>
>>>>
>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>>>> Stewart,
>>>>>
>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>>>> ...
>>>>>> I wonder if we would best serve both our future and our heritage
>>>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>>>> or declared it as historic and wrote a new text from a clean start?
>>>>> I don't see that. It's a stable, widely deployed, interoperable
>>>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>>>> across the Internet.
>>>> I will not debate whether it is faulty or not, but it seems that in
>>>> practice the
>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>> disruptive to some user traffic. The document is really guidance
>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>> not be a standard at all.
>>>>
>>>> My remark about heritage is that this vintage draft is very much a
>>>> product of
>>>> its time, and really needs modernizing, and after modernizing ought to
>>>> look quite different, and thus maybe we should employ a procedure
>>>> other than a simple replacement.
>>>>
>>>>
>>>>> ...
>>>>>> It is concerning that the draft does not talk in any detail about
>>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>>>> the PMTU may be different depending on the transport layer port
>>>>>> numbers.
>>>>> Has this problem been analysed for, say, IPv4? And does the real world
>>>>> contain ECMP setups with different MTUs on different paths?
>>>> I don't know if anyone has looked. Since the mechanism is
>>>> self-correcting albeit
>>>> with some disruption to user traffic it looks to the application and the
>>>> application
>>>> user, just like the Internet not working for a few moments.
>>>>
>>>> In a well managed SP network there should not be, but neither should there
>>>> be asymmetric path costs, but there are. The less well manage private
>>>> networks are less well managed.
>>>>
>>>>
>>>>>> Given that a very large fraction of packets will traverse an MPLS
>>>>>> network at some point, I am surprised that there is no text talking
>>>>>> about the importance of providing support for this feature in the
>>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>>>> I don't understand. How does the fact that there might be some MPLS
>>>>> segments along the path affect end-to-end PMTUD?
>>>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>>>> and the
>>>> PE has to fragment or has to reply with an ICMP error message to support
>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>>>> result
>>>> in the right response at the end node.
>>>>
>>>> My point is that the draft is silent on the subject, and perhaps it
>>>> should not be.
>>>>
>>>> However your question make me ask a further question. The draft is also
>>>> silent
>>>> on NATs. Is there any advice needed for people designing and configuring
>>>> NATs?
>>>>
>>>>>> ======
>>>>>>
>>>>>>       If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>>>       could use the flow id as the local representation of a path. Packets
>>>>>>       sent to a particular destination but belonging to different flows may
>>>>>>       use different paths, with the choice of path depending on the flow
>>>>>>       id.  This approach will result in the use of optimally sized packets
>>>>>>       on a per-flow basis, providing finer granularity than PMTU values
>>>>>>       maintained on a per-destination basis.
>>>>>>
>>>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>>>> SB> and thus routers tended to glean information from the packet themselves.
>>>>> This is future-proofing. Agreed, usage today is limited.
>>>>>
>>>>> (But it would be better to call it the Flow Label for consistency with other
>>>>> recent RFCs.)
>>>> Well the question is whether it is simply limited today, or broken today
>>>> in a manner that
>>>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>>>> approach
>>>> is the five-tuple. There is something akin to the flow label being
>>>> deployed in MPLS. However
>>>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>>>> removed) by the
>>>> service provider and is therefore trusted by the service provider.
>>>>
>>>>> I think your other comments are all valuable.
>>>> Thank you.
>>>>
>>>> Stewart
>>>>
>>>> --------------------------------------------------------------------
>>>> IETF IPv6 working group mailing list
>>>> ipv6@ietf.org
>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 08:24:20 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC9801293DC for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:24:17 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkaMlWYzCzgm for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:24:16 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (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 BEE0F129641 for <ietf@ietf.org>; Tue, 14 Feb 2017 08:24:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 9FC3532BAF7; Tue, 14 Feb 2017 08:24:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487089456; bh=VZpW9uZAtoxXNnwzygzqC7kW50HouYiNd6nVDDj3x54=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=beiuTsk9aBksmUyIeFCfnV1WphisDD6lIkLW9s9uz+yYYYwdnoyGMJEb78QRxLEU5 /UroLj2gQMlt8IkrWt/Cd2JcKddtm7rB05fAaVKYJeYHs6AqbhzrVqnZwXXjg0zfW/ Z9t0r/EvvzinpQq9Wr7++5TAWDRwZ9EIDvp783GM=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id F06F132BAF6; Tue, 14 Feb 2017 08:24:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com>
Date: Tue, 14 Feb 2017 11:24:15 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rTzoO5XB-c5KeRvBflciddjst-E>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:24:17 -0000

I want to reinforce this.

There are two separate but related issues here.  One is what behavior we 
want to require.  The other is whether we make the document clear.

I think choosing to leave a document going to Internet Standard 
ambiguous is a serious mistake, bordering on failure.  We know that the 
choice of permitting insertion of extension headers has interoperability 
implications.  There are weveral ways we can clarify the text.
o We could say "MUST NOT" be added.  Preferably with explaantion of the 
problems being avoided.
o We could say "MUST NOT unless some other standards track RFC says it 
is okay" which is technically correct but confusing.
o We can say "SHOULD NOT unless ..." as long as we can write a clear 
description of the conditions under which it is safe.
o We can say "AMY< but note that doing so has the following risks" if 
that is the IETF rough consensus.

But leaving it ambiguous ought to be a non-starter.

Personally, I would go with "MUST NOT", as I think that is the robust 
and interoperable answer.  But that is MUCH less important to me than 
our being unambiguous.

Yours,
Joel

On 2/11/17 2:24 PM, Brian E Carpenter wrote:
> On 12/02/2017 01:36, otroan@employees.org wrote:
>> Brian,
>>
>>>>> If people who were not involved in the 6man debate have opinions, it
>>>>> would be useful to hear from them. I agree that there is no point in
>>>>> the same people repeating the same arguments.
>>>>
>>>> in the absence of a (somewhat unbiased) summary of the critical
>>>> issues(s), what do you suggest?
>>>
>>> I was going to say this off list, but what the heck?
>>>
>>> To be honest I'm trying to stay quiet. I think I've made my opinion
>>> plain, and although I am of course the only human being alive who doesn't
>>> suffer from confirmation bias, I'd *really* like to hear what people
>>> think whose opinion I haven't already heard 20 times.
>>>
>>> I try not to be a purist. If the right answer is to allow packet
>>> modifications that break PMTUD and IPsec/AH, let's do it, but let's
>>> also say we're doing it. (I happen to think it's the wrong answer,
>>> but that's my problem.) Leaving the text open to interpretation
>>> would make a mockery of promoting it to Standard.
>>
>> This is really not the discussion we ought to be having.
>> "Allowing" or in any way specifying how header insertion could possibly be made to work is far outside of the scope of advancing 2460 to Internet standard.
>
> If so, how can it be OK to leave the text ambiguous?
>
>     Brian
>
>


From nobody Tue Feb 14 08:25:37 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2940129641; Tue, 14 Feb 2017 08:25:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 jwtTfMG-yEXl; Tue, 14 Feb 2017 08:25:28 -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 3B976129696; Tue, 14 Feb 2017 08:25:28 -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 v1EGPRJ3051436; Tue, 14 Feb 2017 09:25:27 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EGPGg0051233 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 09:25:16 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 08:25:15 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 08:25:15 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEA==
Date: Tue, 14 Feb 2017 16:25:15 +0000
Message-ID: <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
In-Reply-To: <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HCEj9sv6kYfAb5NIos0zHmnPLyE>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:25:29 -0000

Hi Stewart,

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 8:13 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; Stewart Bryant
> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
>=20
>=20
> On 14/02/2017 15:50, Templin, Fred L wrote:
> >
> >> As to you first point remember that the convergence process disrupts t=
he
> >> traffic flow as it does so, and that this will repeat every 10 mins as
> >> it tries to re-optimise.
> > Yes, you are right. So, even in the case of RFC1981bis it might not be =
a
> > good idea to store discovered MTUs in the network layer when there
> > is ECMP in the path. (Which could be any time at all.)
>=20
> Yes, I think if you really care about disruption due to packet loss your
> best bet is
> to go with the minimum supported MTU.
>=20
> Forwarding performance is not a issue these days, and core link are over
> provisioned
> so you have to wonder how important the efficiency gain is in practice.
> The efficiency
> gain produced by this protocol in most networks (1276 vs 1496) is only
> about 15% anyway.

So, that would leave us with RFC4821 plus per {session,destination}
probing instead of just per-destination probing. Or, just stick with the
IPv6 minMTU (1280)?

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

> > You briefly mentioned the authorship in your earlier post. As you well
> > know, the corporate affiliation of two of the authors no longer exists.
> My concern was that some authors cannot take part in Auth48 due to not
> providing
> active email addresses.
>=20
> - Stewart
>=20
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >> - Stewart
> >>
> >>
> >> On 10/02/2017 15:38, Templin, Fred L wrote:
> >>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used i=
n the
> >>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventua=
lly
> >>> converge to the minimum MTU of all paths in the multipath, and so it =
is
> >>> still OK to store the MTU in the network layer where it would be shar=
ed
> >>> by all flows.
> >>>
> >>> ECMP does present challenges for RFC4821, however. If a first transpo=
rt
> >>> session discovers a large MTU and shares it with a second transport
> >>> session, the second session may take a very different path where ther=
e
> >>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
> >>> idea to file an erratum to RFC4821 explaining how ECMP might cause
> >>> problems if discovered MTUs are shared between sessions.
> >>>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>> -----Original Message-----
> >>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryan=
t
> >>>> Sent: Friday, February 10, 2017 2:21 AM
> >>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant =
<stewart@g3ysx.org.uk>; gen-art@ietf.org
> >>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@iet=
f.org
> >>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>>>
> >>>>
> >>>>
> >>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>>>> Stewart,
> >>>>>
> >>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>>>> ...
> >>>>>> I wonder if we would best serve both our future and our heritage
> >>>>>> if we declared RFC1981 as historic, and either left the idea there=
,
> >>>>>> or declared it as historic and wrote a new text from a clean start=
?
> >>>>> I don't see that. It's a stable, widely deployed, interoperable
> >>>>> mechanism. That is rather orthogonal to the issue that has been rai=
sed,
> >>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
> >>>>> across the Internet.
> >>>> I will not debate whether it is faulty or not, but it seems that in
> >>>> practice the
> >>>> Internet breaks the mechanism. However it breaks it is a way that se=
ems
> >>>> disruptive to some user traffic. The document is really guidance
> >>>> one how hosts might use  ICMP for optimization, and arguable need
> >>>> not be a standard at all.
> >>>>
> >>>> My remark about heritage is that this vintage draft is very much a
> >>>> product of
> >>>> its time, and really needs modernizing, and after modernizing ought =
to
> >>>> look quite different, and thus maybe we should employ a procedure
> >>>> other than a simple replacement.
> >>>>
> >>>>
> >>>>> ...
> >>>>>> It is concerning that the draft does not talk in any detail about
> >>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
> >>>>>> the PMTU may be different depending on the transport layer port
> >>>>>> numbers.
> >>>>> Has this problem been analysed for, say, IPv4? And does the real wo=
rld
> >>>>> contain ECMP setups with different MTUs on different paths?
> >>>> I don't know if anyone has looked. Since the mechanism is
> >>>> self-correcting albeit
> >>>> with some disruption to user traffic it looks to the application and=
 the
> >>>> application
> >>>> user, just like the Internet not working for a few moments.
> >>>>
> >>>> In a well managed SP network there should not be, but neither should=
 there
> >>>> be asymmetric path costs, but there are. The less well manage privat=
e
> >>>> networks are less well managed.
> >>>>
> >>>>
> >>>>>> Given that a very large fraction of packets will traverse an MPLS
> >>>>>> network at some point, I am surprised that there is no text talkin=
g
> >>>>>> about the importance of providing support for this feature in the
> >>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental=
.
> >>>>> I don't understand. How does the fact that there might be some MPLS
> >>>>> segments along the path affect end-to-end PMTUD?
> >>>> The point that RFC3988 makes is that MPLS looks like a single hop to=
 IP
> >>>> and the
> >>>> PE has to fragment or has to reply with an ICMP error message to sup=
port
> >>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate =
to
> >>>> result
> >>>> in the right response at the end node.
> >>>>
> >>>> My point is that the draft is silent on the subject, and perhaps it
> >>>> should not be.
> >>>>
> >>>> However your question make me ask a further question. The draft is a=
lso
> >>>> silent
> >>>> on NATs. Is there any advice needed for people designing and configu=
ring
> >>>> NATs?
> >>>>
> >>>>>> =3D=3D=3D=3D=3D=3D
> >>>>>>
> >>>>>>       If flows [I-D.ietf-6man-rfc2460bis] are in use, an implement=
ation
> >>>>>>       could use the flow id as the local representation of a path.=
 Packets
> >>>>>>       sent to a particular destination but belonging to different =
flows may
> >>>>>>       use different paths, with the choice of path depending on th=
e flow
> >>>>>>       id.  This approach will result in the use of optimally sized=
 packets
> >>>>>>       on a per-flow basis, providing finer granularity than PMTU v=
alues
> >>>>>>       maintained on a per-destination basis.
> >>>>>>
> >>>>>> SB> How widely is flow-id supported in networks? I thought that th=
e
> >>>>>> SB> current position was that it was unreliable as an ECMP indicat=
or
> >>>>>> SB> and thus routers tended to glean information from the packet t=
hemselves.
> >>>>> This is future-proofing. Agreed, usage today is limited.
> >>>>>
> >>>>> (But it would be better to call it the Flow Label for consistency w=
ith other
> >>>>> recent RFCs.)
> >>>> Well the question is whether it is simply limited today, or broken t=
oday
> >>>> in a manner that
> >>>> is irrecoverable? I don't know, but I do know that the mainstream EC=
MP
> >>>> approach
> >>>> is the five-tuple. There is something akin to the flow label being
> >>>> deployed in MPLS. However
> >>>> what distinguishes the MPLS Entropy Label is that it is inserted (an=
d
> >>>> removed) by the
> >>>> service provider and is therefore trusted by the service provider.
> >>>>
> >>>>> I think your other comments are all valuable.
> >>>> Thank you.
> >>>>
> >>>> Stewart
> >>>>
> >>>> --------------------------------------------------------------------
> >>>> IETF IPv6 working group mailing list
> >>>> ipv6@ietf.org
> >>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> >>>> --------------------------------------------------------------------
> >
>=20



From nobody Tue Feb 14 08:29:39 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC90612969C for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:29:37 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i2Q_bqLVe5tD for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 08:29:36 -0800 (PST)
Received: from mxa2.tigertech.net (mxa2.tigertech.net [208.80.4.162]) (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 0E1841296A1 for <ietf@ietf.org>; Tue, 14 Feb 2017 08:29:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id EE6CB3A0742; Tue, 14 Feb 2017 08:29:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487089775; bh=7wwQDND/OXb5W6YL6YRnvMlKBxj2sZausixR3IwyC7Y=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=UyWARY6mURg3G1fx5iZiV2bs5KnDhvkW4igVMQPAtZDe5OU9f3QZJqK+idnBHAol0 xUb5x6ABg8fp/W5dtzbH9FEttZ5VXbHbskLq+QRufEuqEq4EXBV6jZbkuTq4eaJwZy YQ9GLsUOa+ItGvy9gSSrhq4QwRPUf7LJKt77c5Qw=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 55BB13A0722; Tue, 14 Feb 2017 08:29:35 -0800 (PST)
Subject: Re: To "lose the argument in the WG"
To: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <28ab55e0-fabd-9ea4-9eb2-842b22091388@joelhalpern.com>
Date: Tue, 14 Feb 2017 11:29:34 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <F4592855-640C-4A32-989F-275C359C89EE@qti.qualcomm.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kh9RaLf1MKoHDp0arp3pq67NrUY>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:29:38 -0000

I just posted a note on the IETF list in one of the two discussions Pete 
is refering to.

Yes, I watched the discussion in the WG.
It took me a while to realize that the WG had really ended up in the 
state it did.  A state I consider a failure in terms of the document.
So it seems to me that I need to say so during the IETF LC.

Yours,
Joel

On 2/14/17 12:25 AM, Pete Resnick wrote:
> On 13 Feb 2017, at 23:07, Dave Crocker wrote:
>
>     On 2/13/2017 8:50 PM, Pete Resnick wrote:
>
>         The WG participant who felt that the functionality should be
>         in-scope
>         and is perfectly within bounds to make the case that the
>         functionality
>         is somehow necessary during Last Call. The chair and/or AD should
>         summarize why they judged the functionality to be out of scope.
>         Others
>         in the community might want to take up the argument and explain
>         why it
>         should be added.
>
>     This sounds like reasonable theory, but is actually rather
>     destructive practice.
>
>     It takes the position that Last Call is acceptable to use as a form
>     of appeals process, where folk who have been working on the topic
>     for an extended time have to defend their choices to a collection of
>     other folk who are new to the topic and are, therefore, making snap
>     judgements.
>
>     While, yes, there will be times that the new folk see something new
>     or better, that's not the usual occurrence. The usual occurrence is
>     that folk who are experienced with the topic and are tired from the
>     extended effort have to rehash their work and defend it to folk who
>     have not done their homework.
>
>     Either working groups are where the work really does get done or
>     they aren't. The burden of having to worry about and deal with a
>     larger, less-involved community being frankly encouraged to
>     second-guess the folk who have actual skin in the game, is an
>     example of what makes the formality of IETF process onerous.
>
>     Last Call should not require a working group to be subject to random
>     demands to defend itself. It should be for independent reviews that
>     see something the working group missed. Missed is different from "we
>     had a choice and we made it".
>
>     If a fresh reviewer really does do their homework and really does
>     present a good case for making a different decision, that's fine.
>     But it also is quite different than supporting the re-hashing
>     exercise that occurrs when an existing wg participant expresses
>     dissatisfaction with a decision made during normal wg processes.
>
> Would that we disagreed.
>
> Nowhere did I say that Last Call should be an opportunity to simply
> rehash, without having done homework. Indeed, you will note where I said:
>
>         Do note that in both cases, I think it's only fair that the
>         person bringing up the issue clearly states what's going on. For
>         instance, in the second case the person should really have said,
>         "This was judged out-of-scope by the WG/chair, but I think it
>         ought not be out-of-scope because of X, Y, and Z". Simply
>         saying, "Please make this change to the document" as if it were
>         never discussed before is not helpful to the rest of the list
>         during Last Call.
>
> For a WG participant to just throw out the same argument made earlier
> without explanation /and/ with the expectation that the WG ought be
> required to relitigate the whole discussion is /not/ reasonable. The
> case needs to be made that the WG (or the chair in judging) did in fact
> miss something when they came to rough consensus. The chair, not the
> entire WG, should explain why the conclusion was arrived at. (That
> should really be written up in the shepherd report, if we're being
> diligent.) Others can choose to ask questions or push back on either
> position if they think something serious has been missed. But to
> dismiss, out of hand, any such claim with "too late, already decided" is
> also unreasonable.
>
> Homework is required. Pointing out the failure is required. Avoiding
> simply restating a preference is required. I'm just objecting to the
> blanket statement, "If the WG came to consensus, even roughly, the
> discussion is over."
>
> (As I said earlier, in the case of something being declared
> out-of-scope, I'd expect the person bringing up the point to explain why
> being in-scope was essential. To fail to do so is bogus.)
>
>     ps. Pete's other point was about a claim that an issue didn't really
>     get settled and needs further review. That's quite a different case.
>     Maybe it's worthy for LC discussion. Maybe it isn't. Dunno.
>
>     pps. There's at least one case where I chose to attempt to use LC as
>     a kind of appeals process, since I deemed the wg process to have
>     been significantly flawed, including the cognizant AD. Like all good
>     rules, there need to be some exceptions thoughtfully permitted,
>     though of course my effort in this example of an exception bore no
>     fruit...
>
> I also agree that this should be fairly unusual. Again, what got to me
> was the automatic rejection of such an argument.
>
> pr
> --
> Pete Resnick http://www.qualcomm.com/~presnick/
> <http://www.qualcomm.com/%7Epresnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>


From nobody Tue Feb 14 08:45:28 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F7E112968E; Tue, 14 Feb 2017 08:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RIrkd1xf6cEs; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (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 1A4B9129674; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
Received: by mail-wm0-x244.google.com with SMTP id v77so4417102wmv.0; Tue, 14 Feb 2017 08:45:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Le87WbpJqsUA9ApP9SxYAyK+ngTySjoywXo7oQ51DaU=; b=QMA/oYlmC8RHT9uRzxD4lkyW7ExrHeLj4BIVcpxyT55PVeV/+pYvnMvBHqIQARkx/R FBfB3uCSI9CdM9aZ6DTpxjz+FmrI4xQez0WaGtRpzWguRyXNjJE5iUAbmNCwn0IqcEWO m1yuxtWqPCiyz7F2IsZjvue1dsOik1mw5/69BgSjc2AK4OMohF/9nfxzKDkGECvMDGEM aMpPGraU/ZYSQw+Osxo+PtAnQ2FmbIpDfHx4ievrvGaLDdyUAserJVmzSX74qchy7l+Y FprjoAXPRns+GfTEIESzeKDrN5lHq3zm3lcfN24to9xBy1Rgyb1oFNHybrPOKS4BUqOX SXZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Le87WbpJqsUA9ApP9SxYAyK+ngTySjoywXo7oQ51DaU=; b=eF8DT7ZqTQkZw2c8KhVsAE4Hnp/oIRMu4shK99X46Wl4swBwGQ0WLi8sYFigoOK7JZ I5TNvOwgLQv5ug7bBRHs73jneWyJXTAqR/x4lAERFWY+cFGvT/ehjFeH3R/fJiADXQFT eWGJL+JdTpbePlbdQcRpLziaaw4lS2RZgWheVF3iFkyyMm3F5zxc7nxkbA+RHQ8PU5S1 fg49j9amCx/0yk2rv5ufWmV/x5Hbgi5FPuPBMpm5IvNOromW0YNU5lX6A0HEAydEEBSd eqj1WqWY0pTBOZaj4KfJ5Aa7gMDE/ZD0FO7kJDvSB+f4yyT+EkDWDlhNHHXwxbZ/OdPs rI9w==
X-Gm-Message-State: AMke39m+2aCcaJuxqHVN8MBCnPi+pAAjX4PMQW4LiKUHZVoPUIsKCJlBRSsRxqSIJaciaA==
X-Received: by 10.28.109.218 with SMTP id b87mr4112682wmi.52.1487090706509; Tue, 14 Feb 2017 08:45:06 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 45sm1414641wrx.60.2017.02.14.08.45.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 08:45:05 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
Date: Tue, 14 Feb 2017 16:45:04 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vSMrXNXXqiO5DbcqLTE466PE1xA>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 16:45:10 -0000

Fred
*If*  you care about packet loss, then your only option is to probe the 
path with with
synthetic data that exactly mimics the live data, or not to probe at all 
and live
with the 1280. As I said 1280 is pretty close to 1496 which is all most 
networks
will give you in practice.

When I think about the people asking for fast re-route to minimise 
packet loss, it seems
very strange to deliberately induce loss to try to stretch the MTU by 15%.

- Stewart


On 14/02/2017 16:25, Templin, Fred L wrote:
> Hi Stewart,
>
>> -----Original Message-----
>> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
>> Sent: Tuesday, February 14, 2017 8:13 AM
>> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant
>> <stewart@g3ysx.org.uk>; gen-art@ietf.org
>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>
>>
>>
>> On 14/02/2017 15:50, Templin, Fred L wrote:
>>>> As to you first point remember that the convergence process disrupts the
>>>> traffic flow as it does so, and that this will repeat every 10 mins as
>>>> it tries to re-optimise.
>>> Yes, you are right. So, even in the case of RFC1981bis it might not be a
>>> good idea to store discovered MTUs in the network layer when there
>>> is ECMP in the path. (Which could be any time at all.)
>> Yes, I think if you really care about disruption due to packet loss your
>> best bet is
>> to go with the minimum supported MTU.
>>
>> Forwarding performance is not a issue these days, and core link are over
>> provisioned
>> so you have to wonder how important the efficiency gain is in practice.
>> The efficiency
>> gain produced by this protocol in most networks (1276 vs 1496) is only
>> about 15% anyway.
> So, that would leave us with RFC4821 plus per {session,destination}
> probing instead of just per-destination probing. Or, just stick with the
> IPv6 minMTU (1280)?
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>>> You briefly mentioned the authorship in your earlier post. As you well
>>> know, the corporate affiliation of two of the authors no longer exists.
>> My concern was that some authors cannot take part in Auth48 due to not
>> providing
>> active email addresses.
>>
>> - Stewart
>>
>>> Thanks - Fred
>>> fred.l.templin@boeing.com
>>>
>>>> - Stewart
>>>>
>>>>
>>>> On 10/02/2017 15:38, Templin, Fred L wrote:
>>>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used in the
>>>>> network as long as ICMP PTBs are not blocked. RFC1981bis will eventually
>>>>> converge to the minimum MTU of all paths in the multipath, and so it is
>>>>> still OK to store the MTU in the network layer where it would be shared
>>>>> by all flows.
>>>>>
>>>>> ECMP does present challenges for RFC4821, however. If a first transport
>>>>> session discovers a large MTU and shares it with a second transport
>>>>> session, the second session may take a very different path where there
>>>>> is a smaller MTU and encounter a black hole. IMHO, it might be a good
>>>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
>>>>> problems if discovered MTUs are shared between sessions.
>>>>>
>>>>> Thanks - Fred
>>>>> fred.l.templin@boeing.com
>>>>>
>>>>>> -----Original Message-----
>>>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bryant
>>>>>> Sent: Friday, February 10, 2017 2:21 AM
>>>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryant <stewart@g3ysx.org.uk>; gen-art@ietf.org
>>>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
>>>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
>>>>>>> Stewart,
>>>>>>>
>>>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
>>>>>>> ...
>>>>>>>> I wonder if we would best serve both our future and our heritage
>>>>>>>> if we declared RFC1981 as historic, and either left the idea there,
>>>>>>>> or declared it as historic and wrote a new text from a clean start?
>>>>>>> I don't see that. It's a stable, widely deployed, interoperable
>>>>>>> mechanism. That is rather orthogonal to the issue that has been raised,
>>>>>>> which is that faulty ICMPv6 filtering blocks it on many, many paths
>>>>>>> across the Internet.
>>>>>> I will not debate whether it is faulty or not, but it seems that in
>>>>>> practice the
>>>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>>>> disruptive to some user traffic. The document is really guidance
>>>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>>>> not be a standard at all.
>>>>>>
>>>>>> My remark about heritage is that this vintage draft is very much a
>>>>>> product of
>>>>>> its time, and really needs modernizing, and after modernizing ought to
>>>>>> look quite different, and thus maybe we should employ a procedure
>>>>>> other than a simple replacement.
>>>>>>
>>>>>>
>>>>>>> ...
>>>>>>>> It is concerning that the draft does not talk in any detail about
>>>>>>>> how modern ECMP works, i.e. using the five tuple, and noting that
>>>>>>>> the PMTU may be different depending on the transport layer port
>>>>>>>> numbers.
>>>>>>> Has this problem been analysed for, say, IPv4? And does the real world
>>>>>>> contain ECMP setups with different MTUs on different paths?
>>>>>> I don't know if anyone has looked. Since the mechanism is
>>>>>> self-correcting albeit
>>>>>> with some disruption to user traffic it looks to the application and the
>>>>>> application
>>>>>> user, just like the Internet not working for a few moments.
>>>>>>
>>>>>> In a well managed SP network there should not be, but neither should there
>>>>>> be asymmetric path costs, but there are. The less well manage private
>>>>>> networks are less well managed.
>>>>>>
>>>>>>
>>>>>>>> Given that a very large fraction of packets will traverse an MPLS
>>>>>>>> network at some point, I am surprised that there is no text talking
>>>>>>>> about the importance of providing support for this feature in the
>>>>>>>> MPLS domain. RFC3988 talks to this point, but is only experimental.
>>>>>>> I don't understand. How does the fact that there might be some MPLS
>>>>>>> segments along the path affect end-to-end PMTUD?
>>>>>> The point that RFC3988 makes is that MPLS looks like a single hop to IP
>>>>>> and the
>>>>>> PE has to fragment or has to reply with an ICMP error message to support
>>>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrate to
>>>>>> result
>>>>>> in the right response at the end node.
>>>>>>
>>>>>> My point is that the draft is silent on the subject, and perhaps it
>>>>>> should not be.
>>>>>>
>>>>>> However your question make me ask a further question. The draft is also
>>>>>> silent
>>>>>> on NATs. Is there any advice needed for people designing and configuring
>>>>>> NATs?
>>>>>>
>>>>>>>> ======
>>>>>>>>
>>>>>>>>        If flows [I-D.ietf-6man-rfc2460bis] are in use, an implementation
>>>>>>>>        could use the flow id as the local representation of a path. Packets
>>>>>>>>        sent to a particular destination but belonging to different flows may
>>>>>>>>        use different paths, with the choice of path depending on the flow
>>>>>>>>        id.  This approach will result in the use of optimally sized packets
>>>>>>>>        on a per-flow basis, providing finer granularity than PMTU values
>>>>>>>>        maintained on a per-destination basis.
>>>>>>>>
>>>>>>>> SB> How widely is flow-id supported in networks? I thought that the
>>>>>>>> SB> current position was that it was unreliable as an ECMP indicator
>>>>>>>> SB> and thus routers tended to glean information from the packet themselves.
>>>>>>> This is future-proofing. Agreed, usage today is limited.
>>>>>>>
>>>>>>> (But it would be better to call it the Flow Label for consistency with other
>>>>>>> recent RFCs.)
>>>>>> Well the question is whether it is simply limited today, or broken today
>>>>>> in a manner that
>>>>>> is irrecoverable? I don't know, but I do know that the mainstream ECMP
>>>>>> approach
>>>>>> is the five-tuple. There is something akin to the flow label being
>>>>>> deployed in MPLS. However
>>>>>> what distinguishes the MPLS Entropy Label is that it is inserted (and
>>>>>> removed) by the
>>>>>> service provider and is therefore trusted by the service provider.
>>>>>>
>>>>>>> I think your other comments are all valuable.
>>>>>> Thank you.
>>>>>>
>>>>>> Stewart
>>>>>>
>>>>>> --------------------------------------------------------------------
>>>>>> IETF IPv6 working group mailing list
>>>>>> ipv6@ietf.org
>>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>>>>>> --------------------------------------------------------------------
>


From nobody Tue Feb 14 09:05:22 2017
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3879E1296CB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 09:05:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.792
X-Spam-Level: 
X-Spam-Status: No, score=-1.792 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eGvd1gRlv47H for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 09:05:19 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 13E1312968E for <ietf@ietf.org>; Tue, 14 Feb 2017 09:05:19 -0800 (PST)
Received: from [192.168.1.168] (76-218-8-128.lightspeed.sntcca.sbcglobal.net [76.218.8.128]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id v1EH6xAP001688 (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 14 Feb 2017 09:06:59 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1487092020; bh=dEdOu4MZClRf/EnQOQF2oFmGEI84WYW4tZT7uGpcRng=; h=Subject:To:References:Cc:From:Reply-To:Date:In-Reply-To:From; b=Hz02DLX6bEvV4JCK4WHmkoz6BH1ixnrz9iz3jKQI63AfvHvLbRPR6N2iavCXL513s sUDxIUeL7quEh1gbgwd4HqDQ3cJdLiiMoIJFNTRIQoI3jRSpP8cduQjir/VeXnLYvF FlyZchVDde6X5aH3xJxfLPNayTyxJ8nBHKhAyUTY=
Subject: Re: To "lose the argument in the WG"
To: Ted Lemon <mellon@fugue.com>, Yoav Nir <ynir.ietf@gmail.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net>
Date: Tue, 14 Feb 2017 09:05:07 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Cwgmou7CidJC5LHylEyCwhDTqik>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 17:05:20 -0000

On 2/14/2017 7:12 AM, Ted Lemon wrote:
> Er, no.  The most important point of last call is to make sure that people who did not have time to participate in the last call in the working group, but who have relevant knowledge, get a chance to weigh in.


Unfortunately:

    Last Call Guidance to the Community
    https://www.ietf.org/iesg/statement/last-call-guidance.html

does not provide useful guidance about the purpose and substance of 
doing an IETF Last Call.

The IETF's formal process document on standards:

    The Internet Standards Process -- Revision 3
    https://www.ietf.org/rfc/rfc2026.txt

says nothing about Last Call.

So the formal IETF specification for the role of Last Call is in:

      IETF Working Group Guidelines and Procedures
      https://tools.ietf.org/html/rfc2418

>    This Last Call will announce the intention of
>    the IESG to consider the document, and it will solicit final comments
>    from the IETF within a period of two weeks.  It is important to note
>    that a Last-Call is intended as a brief, final check with the
>    Internet community, to make sure that no important concerns have been
>    missed or misunderstood. The Last-Call should not serve as a more
>    general, in-depth review.

(I should note that that text dates back to the original version of the 
document that Erik Huizer and I wrote, in RFC 1871, in 1994.)


What folks are doing is spontaneously changing the role of this step, 
ignoring the considerable costs and detriments, while relying on a 
theory of benefit that is very, very, very rarely actually demonstrated.

To Ted's point, indulging folk who 'did not have time' to participate 
earlier is frankly abusive of all those who did.

RFC 2416 (and the original, RFC 1871) has explicit text about revisiting 
a topic:

>    It is occasionally appropriate to revisit a topic, to re-evaluate
>    alternatives or to improve the group's understanding of a relevant
>    decision.  However, unnecessary repeated discussions on issues can be
>    avoided if the Chair makes sure that the main arguments in the
>    discussion (and the outcome) are summarized and archived after a
>    discussion has come to conclusion. It is also good practice to note
>    important decisions/consensus reached by email in the minutes of the
>    next 'live' session, and to summarize briefly the decision-making
>    history in the final documents the WG produces.
>
>    To facilitate making forward progress, a Working Group Chair may wish
>    to decide to reject or defer the input from a member, based upon the
>    following criteria:
>
>    Old
>    The input pertains to a topic that already has been resolved and is
>    redundant with information previously available;
>
>    Minor
>    The input is new and pertains to a topic that has already been
>    resolved, but it is felt to be of minor import to the existing
>    decision;
>
>    Timing
>    The input pertains to a topic that the working group has not yet
>    opened for discussion; or
>
>    Scope
>    The input is outside of the scope of the working group charter.



d/

ps. RFC
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net


From nobody Tue Feb 14 09:16:27 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E86E1294A5 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 09:16:25 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 1Hmmx_jg6UaA for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 09:16:23 -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 A8E0112941A for <ietf@ietf.org>; Tue, 14 Feb 2017 09:16:23 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 2746282981; Tue, 14 Feb 2017 18:16:18 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <f5ced76c-91ab-a927-5296-ac3d8ae9a8ad@si6networks.com>
Date: Tue, 14 Feb 2017 14:10:32 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NemLLge74WkBUlxuZkCMj1fGmEo>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 17:16:25 -0000

On 02/14/2017 01:24 PM, Joel M. Halpern wrote:
> I want to reinforce this.
> 
> There are two separate but related issues here.  One is what behavior we
> want to require.  The other is whether we make the document clear.
> 
> I think choosing to leave a document going to Internet Standard
> ambiguous is a serious mistake, bordering on failure.  We know that the
> choice of permitting insertion of extension headers has interoperability
> implications.  There are weveral ways we can clarify the text.
[...]
> 
> But leaving it ambiguous ought to be a non-starter.
> 
> Personally, I would go with "MUST NOT", as I think that is the robust
> and interoperable answer.  But that is MUCH less important to me than
> our being unambiguous.

Agreed with the quoted part above.

Now regarding the possible options, may I ask: How could we possibly
allow EH insertion in this document, and still move rfc2460 to full
standard?

Allowing EH insertion in rfc2460bis would essentially preclude us from
moving it to full standard.

OTOH, as you correctly note, "I think choosing to leave a document going
to Internet Standard ambiguous is a serious mistake, bordering on failure".

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 14 09:40:22 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C79441294DC; Tue, 14 Feb 2017 09:40:17 -0800 (PST)
X-Quarantine-ID: <dT1Ypiy9kXio>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 dT1Ypiy9kXio; Tue, 14 Feb 2017 09:40:16 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 22902128E18; Tue, 14 Feb 2017 09:40:16 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 09:32:19 -0800
Mime-Version: 1.0
Message-Id: <p06240603d4c8f105055e@[99.111.97.136]>
In-Reply-To: <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 09:40:11 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Bernard Aboba <bernard.aboba@gmail.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eBgdsmuJqnNF1F2jnVoSitfISUo>
Cc: slim@ietf.org, ietf@ietf.org, Doug Ewell <doug@ewellic.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 17:40:18 -0000

At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:

>  My proposal for a reworded section 5.4 is:
>
>  5.4.  Unusual language indications
>
>  It is possible to specify an unusual indication where the language
>  specified may look unexpected for the media type.
>
>  For such cases the following guidance SHALL be=20
> applied for the humintlang attributes used in=20
> these situations.
>
>  1.	A view of a speaking person in the video=20
> stream SHALL, when it has relevance for speech=20
> perception, be indicated by a Language-Tag for=20
> spoken/written language with the "Zxxx" script=20
> subtag to indicate that the contents is not=20
> written.
>
>  2.	Text captions included in the video=20
> stream SHALL be indicated by a Language-Tag for=20
> spoken/written language.
>
>  3.	Any approximate representation of sign=20
> language or fingerspelling in the text media=20
> stream SHALL be indicated by a Language-Tag for=20
> a sign language in text media.
>
>  4.	When sign language related audio from a=20
> person using sign language is of importance for=20
> language communication, this SHALL be indicated=20
> by a Language-Tag for a sign language in audio=20
> media.

[RG] As I said, I think we should avoid=20
specifying this until we have deployment=20
experience.


>
>=20
> --------------------------------------------------------------------------=
-----
>  This paragraph in 5.2 should be deleted because it is a duplication.
>
>  "   Note that while signed language tags are used with a video stream to
>     indicate sign language, a spoken language tag for a video stream in
>     parallel with an audio stream with the same spoken language tag
>     indicates a request for a supplemental video stream to see the
>     speaker."

[RG] I agree and will delete the paragraph.



>
>  Regards
>
>  Gunnar
>
>  Den 2017-02-14 kl. 08:06, skrev Gunnar Hellstr=F6m:
>
>>  Doug,
>>
>>  Thanks for pointing at the Zxxx script subtag for non-written content.
>>
>>  I think we can document the use of it for the=20
>> view of a speaker in video media when=20
>> indicated by a spoken/written language tag.
>>
>>  I have tried before to propose to use the=20
>> script subtag to indicate written language,=20
>> but got opposition because many languages have=20
>> their main script subtag suppressed. However,=20
>> the language around suppressed script subtags=20
>> indicate that there are cases when the use is=20
>> appropriate. We  can document that text=20
>> captions in the video stream shall (or should)=20
>> be indicated with a script subtag.
>>
>>  But, to keep it simple, the use of Zxxx scrit=20
>> subtag on the view of a speaker should be=20
>> sufficient.
>>
>>  That could conclude the unusual combinations:
>>
>>  1. Spoken/written tag in video media, can mean=20
>> to see a speaking person, or to provide=20
>> captions overlayed on video.
>>
>>  When the intention is to indicate overlayed=20
>> captions in the video stream, the script=20
>> subtag Zxxx SHALL be used.
>>
>>  Otherwise, a view of a speaking person is indicated.
>>
>>  2. Signed language tag in audio media,
>>  means audio from a person using sign language,=20
>> and SHOULD only be used for rare cases when it=20
>> has some relevance for language communication.
>>
>>  3. Sign language tag in text media.
>>
>>  SHALL be used for any approximate text coded=20
>> representation of sign language or=20
>> fingerspelling.
>>
>>  I suggest that these conclusions form the base for a redefined section 5=
=2E4.
>>
>>  ------------------------------------------------------------------------=
--
>>  About my efforts to discuss modality in the=20
>> language list: The list was closed when I=20
>> tried to subscribe or send to it, and I did=20
>> not see any response on a question I sent=20
>> about how to get a discussion on the modality=20
>> topic.
>>
>>  But I am happy now with your pointing out the=20
>> Zxxx script. a spoken/written language with=20
>> Zxxx script is quite obviously not written and=20
>> not signed, so then it is spoken. Good.
>>
>>  Thanks
>>
>>  Gunnar
>>
>>
>>  Den 2017-02-14 kl. 00:10, skrev Doug Ewell:
>>
>>>  Gunnar Hellstr=F6m wrote:
>>>
>>>>  But captions overlayed on video in the media stream is a used
>>>>  technology so it would be good to be able to specify it.
>>>>  That we cannot do it is again a sad effect of the language tags not
>>>>  distinguishing between spoken and written modality.
>>>>
>>>  se-Latn =3D Swedish written in Latin script
>>>  se-Cyrl =3D Swedish written in Cyrillic script
>>>  se-Maya =3D Swedish written in Mayan hieroglyphs
>>>
>>>  se-Zxxx =3D Swedish, explicitly not written
>>>
>>>  "se-Zxxx, fi-Latn" =3D content includes non-written Swedish plus Finnis=
h
>>>  written in Latin script
>>>
>>>  Examples of multiple streams of content, such as video in one language
>>>  that is subtitled in another, call for multiple language tags. That is
>>>  not a shortcoming or failure of the language tag mechanism. See RFC
>>>  5646, Section 4.3.
>>>
>>>  All of this was discussed in the WG by the same parties.
>>>
>>>>  I once had an ambition to try to specify a notation for that to be
>>>>  added to BCP 47, but did not succeed to get any real discussion going
>>>>  on the topic.
>>>>
>>>    I searched the ietf-languages archives and did not find any sort of p=
ost
>>>  or proposal from you. I forwarded one of your messages from SLIM to tha=
t
>>>  list in November 2015, expecting you to follow up with a proposal, but
>>>  nothing materialized.
>>>    --
>>>  Doug Ewell | Thornton, CO, US | ewellic.org
>>>
>>>
>>>  _______________________________________________
>>>  SLIM mailing list
>>>  <mailto:SLIM@ietf.org>SLIM@ietf.org
>>>=20
>>> <https://www.ietf.org/mailman/listinfo/slim>https://www.ietf.org/mailman=
/listinfo/slim
>>>
>>
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  <mailto:gunnar.hellstrom@omnitor.se>gunnar.hellstrom@omnitor.se
>  +46 708 204 288
>
>  _______________________________________________
>  SLIM mailing list
>  SLIM@ietf.org
>  https://www.ietf.org/mailman/listinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If you would look up bad labor relations in the dictionary, you
would have an American Airlines logo beside it.
    --U.S. District Judge Joe Kendall, issuing a restraining order
against an American Airlines APA pilot union sick out, 10 Feb 1999.


From nobody Tue Feb 14 10:05:50 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5085E1296CB for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 10:05:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.288
X-Spam-Level: 
X-Spam-Status: No, score=-3.288 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 w40sZ3QOKtbZ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 10:05:47 -0800 (PST)
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) (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 2BB021295EE for <ietf@ietf.org>; Tue, 14 Feb 2017 10:05:47 -0800 (PST)
Received: by mail-oi0-f43.google.com with SMTP id j15so74753277oih.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 10:05:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=I5vroMVmhS90OVta4OI6RehwsmVzRpc/ApKN9RdqPF4=; b=atVtz2ym4HF8odMPynV2HmWBCeovOnRXZmyKVZiebnFyJ3Dybxq1DJFlNSCvjy8UuA 3SlbR56TCecgLXVRMjvrNsDDTOPUpOhTWY7M6WxWXbhbSrJrzCjIgBtquEb95wYcLM7y aa0A6ze7A4nhr8c4dfX482EcxS/3Cu46eCPWJkkcv4fOOWMdXIOP+81R/c8yz8Ztk72r tLn4wE9yEiMomv4sGI+GRxuYj0hKmyt5p1obfcKr2rW/m2VUXH15v0+NDw+utJwryY51 u6LXVvdU3d2SCypDdbvaRNxTejrKVEZzGskpFcyhRkxObt383x/F4rFde2Tod6NAPbYK bsdQ==
X-Gm-Message-State: AMke39n8EPTYv+UemiQBFXG3MayobQ5POLLPwYrfczUXbu7ThCtTNF6XSXJ9npKA43ny16sX
X-Received: by 10.84.245.1 with SMTP id i1mr38046550pll.131.1487095546089; Tue, 14 Feb 2017 10:05:46 -0800 (PST)
Received: from [192.168.1.114] (c-50-143-178-150.hsd1.ca.comcast.net. [50.143.178.150]) by smtp.gmail.com with ESMTPSA id j185sm2578852pgd.35.2017.02.14.10.05.45 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 10:05:45 -0800 (PST)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: ietf@ietf.org
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu>
Date: Tue, 14 Feb 2017 10:05:47 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240603d4c8f105055e@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ycmlE0w7kb3pqEtCq54Ygf98Pc0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:05:48 -0000

Hi -

On 2/14/2017 9:40 AM, Randall Gellens wrote:
> At 11:01 AM +0100 2/14/17, Gunnar Hellström wrote:
>
>>  My proposal for a reworded section 5.4 is:
>>
>>  5.4.  Unusual language indications
>>
>>  It is possible to specify an unusual indication where the language
>>  specified may look unexpected for the media type.
>>
>>  For such cases the following guidance SHALL be applied for the
>> humintlang attributes used in these situations.
>>
>>  1.    A view of a speaking person in the video stream SHALL, when it
>> has relevance for speech perception, be indicated by a Language-Tag
>> for spoken/written language with the "Zxxx" script subtag to indicate
>> that the contents is not written.
>>
>>  2.    Text captions included in the video stream SHALL be indicated
>> by a Language-Tag for spoken/written language.
>>
>>  3.    Any approximate representation of sign language or
>> fingerspelling in the text media stream SHALL be indicated by a
>> Language-Tag for a sign language in text media.
>>
>>  4.    When sign language related audio from a person using sign
>> language is of importance for language communication, this SHALL be
>> indicated by a Language-Tag for a sign language in audio media.
>
> [RG] As I said, I think we should avoid specifying this until we have
> deployment experience.
...

 From a process perspective, it's far easier to remove constraints
as a specification advances than it is to add them.

Randy


From nobody Tue Feb 14 10:31:49 2017
Return-Path: <asmusf@ix.netcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC3B1296CA; Tue, 14 Feb 2017 10:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (384-bit key) header.from=asmusf@ix.netcom.com header.d=ix.netcom.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id obGDdNcKgjuW; Tue, 14 Feb 2017 10:31:45 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 562311296FC; Tue, 14 Feb 2017 10:31:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=ix.netcom.com; b=fpxNFw0udtXw8SZH2XR6eDq4eM+EuaKLbkXlxgMv2rYxwF9eC+X4YmaM893XK1GQ; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [71.212.94.37] (helo=[192.168.0.5]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <asmusf@ix.netcom.com>) id 1cdhsc-0002tA-N4; Tue, 14 Feb 2017 13:31:11 -0500
Subject: Re: Last Call: <draft-freytag-lager-variant-rules-02.txt> (Variant Rules) to Informational RFC
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
References: <148467380280.32070.11213613399948034139.idtracker@ietfa.amsl.com> <ED9D6B23A636DFCB94044ABD@PSB>
From: Asmus Freytag <asmusf@ix.netcom.com>
Message-ID: <16b7beac-71e2-0a89-adc1-6a576597ab31@ix.netcom.com>
Date: Tue, 14 Feb 2017 10:31:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ED9D6B23A636DFCB94044ABD@PSB>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 464f085de979d7246f36dc87813833b2b92c5f0aecc81b51518f82b9d8697e82aa8226b48fbdfbca350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.212.94.37
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bK_Zo_4GLlIAMm38gvVi4dU4tSg>
Cc: alexey.melnikov@isode.com, draft-freytag-lager-variant-rules@ietf.org, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <patrik@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:31:48 -0000

John,

I can't feel but that there's somewhat of a disconnect between what the
document is actually about and the issues that are being discussed here.

The document is not about policy. It is also not about domain names
exclusively. The same is true for RFC7940 by the way.

RFC7940 is about how you write down a specification for label generation
rules. It is not a specification for designing them. It is also not a 
specification
for what should be possible in label generation rules for IDNs in the DNS.

In other words, it is a protocol for capturing a wide range of possible
policies for a range of possible identifier systems, of which domain names
are the most prominent (and first) example.

Variant mechanisms exist today in at least two different RFCs, one for
Arabic and one for Chinese. RFC 7940 provides the tools to express them
rigorously, without passing any judgement on the feasibility or desirability
of defining a policy that allows variants.

The XML formalism is hard to follow for many people and obscures to them
what is happening underneath. Because it is broad enough to cover all pre-
existing schemes, it is also possible to create policies with edge-cases 
that can
get you in trouble, where a label generation ruleset may not be 
"well-behaved"
in an  implementation sense. The current draft is aimed at explaining these
technical aspects, again without addressing the question whether variants
are desirable for the DNS.

There's nothing here that sets policy for the DNS. If that was desirable, it
should be done in a different document. I concur, that such a document
would be the correct place to address questions around the issues of what
is implementable in terms of *delegated* variants in the DNS, and even
that such a document would seem desirable. I fully agree with what is
described as the "magical thinking" around variants. But it is not something
addressed in this draft and not the place of this draft to discuss any of
these issues, and they should not be part of this draft.

RFC7940 is an XML schema. The current draft doesn't change anything
about this schema, therefore, it is not, in my view, material for an 
"update"
to RFC7940.

If you think of RC7940 like a programming language for LGRs, the current
document is a style guide. These are two entirely different things. Whether
using standards-track for a style guide is appropriate, I have no opinion
on, but I am clear that this draft neither updates nor supercedes any part
of RFC 7940.

The JET documents contain a combination of information: how to capture
a variant relationship in a multi-column plain text format on the one hand,
and what to base the relationship on, on the other hand.

RFC7940 only (!) addresses the first point. It does not address what variant
relations are desirable (or should be allowed) in any zone in the DNS.

The current document goes a step further and examines what kind of
assumptions about the nature of supportable variants go into the design
of the LGR formalism. Contrary to what is claimed, the draft is intended
to make clear that "variants" that are not 1:1 substitutions are effectively
not tractable with this mechanism.

If you have a relationship between two labels that can be characterized
by a distance in perceptual space, and where you define some arbitrary
but non-zero distance as defining confusability between such labels, then
of three labels, two may be confusable with the third, but not confusable
with each other: the relationship is not transitive.

Non-transitive relationships are not handled well with RFC7940, because
it does not have a way of allocating distances (or locations) in perceptual
space. (Language to that effect is definitely in the latest draft I 
wrote, but
I don't know whether it's already in the -02).

If your relationships between blocked variants are symmetric and transitive,
collision checking becomes an 0(1) operation, somewhat like a hash.
This makes blocked variants attractive for cases where, in case of a 
collision,
there is no doubt that the labels are clearly colliding. (Collisions 
based on
perceptual distance suffer from the arbitrary selection of the minimal
required distance and are always open to pressures to override or make
case-by-case exceptions, see .br).

One could capture the confusables data in UTS#46 in the form of RFC7940
and mechanically make the transitive and symmetric (as they are not
specified that way, although they appear to at least be intended to be
implicitly symmetric). If that is done, one finds that the transitivity
requirement would lead to mapping a number of clearly distinct labels
to each other; for others, the variant relation could be transitive as well.

RFC7940 allows symmetric only LGRs, and with suitable tools these
could be used to implement blocking, but the optimizations available
for the transitive case would not hold. (That is something that could
be described in a section in the draft, if it was considered helpful;
however, this author has no information on best strategies for implementing
blocking in a symmetric only case).

The Arabic RFC defined positional variants (a necessary feature for that
script) but the context rules for variants that this requires can lead to
undesirable edge cases when one violates the underlying assumption
of symmetry: if I substitute a variant code point in a label it must satisfy
the same context rule, otherwise the mapping is not symmetric.

(The types of context rules one tends to use in Arabic happen to be well-
behaved)

RFC7940 does not require variant relations to be symmetric and transitive;
it is not unreasonable to be able to have a tool to mechanically complete
the specifications of mappings, but to want the input file to be formally
valid under the XML schema, even if in practice one would want to not
use an LGR that isn't symmetric and transitive.

The work required to prove that an XML is symmetric and transitive
as far as the mappings are concerned, is practically the same as enforcing
that constraint, by the way.

The notation used in this draft is simply a shorthand for the formalisms
available in RFC7940, so that it is possible to succinctly write down
examples that aren't overburdened with XML syntax. Really nothing more
and nothing less. If RFC7940 were extended in the future, so could this
symbolic shorthand notation.

I believe it is factually incorrect to say that either RFC7940 or this 
draft are
in any way constrained to what "ICANN has decided to allow for the Root".
The expert group hired by ICANN has followed some of the reasoning found
in this draft to recommend against some details in certain proposed 
definitions
of variants, because they were realized to lead to ambiguous edge cases.

The suggestion that the section showing the correspondence is too cursory
I take as constructive. There's no requirement that prevents it from being
more comprehensive.

A./


On 2/14/2017 1:59 AM, John C Klensin wrote:
> --On Tuesday, January 17, 2017 09:23 -0800 The IESG
> <iesg-secretary@ietf.org> wrote:
>
>> The IESG has received a request from an individual submitter
>> to consider the following document:
>> - 'Variant Rules'
>>    <draft-freytag-lager-variant-rules-02.txt> as Informational
>> RFC
>>
>> The IESG plans to make a decision in the next few weeks, and
>> solicits final comments on this action. Please send
>> substantive comments to the ietf@ietf.org mailing lists by
>> 2017-02-14. 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.
> Summary: This document should not be published in the IETF
> Stream, at least in its present form, proposed status, and
> relationship to other documents.  An explanation and some
> alternatives appear below.
>
> Details:
>
> This is a difficult document for me to review for multiple
> reasons, including a conviction that the intentions are the
> very best but that the document is artificially constrained by
> essentially political decisions taken outside the IETF or any
> other process that would meet traditional IETF criteria for
> openness, transparency, fairness, and rough consensus.
>
> For IETF decision-making, a largely procedural issue is as, or
> perhaps more, important.  The document bears a relationship to
> the standards-track RFC 7940 that is confusing at best.   The
> "Document Quality" section of the proposed approval notice
> starts "The document largely reflects experience gathered from
> implementing RFC 7940 and creating rulesets based on it".  That
> is a worthy goal and entirely consistent with the "rough
> consensus and running code" principle.  The author has done
> what I believe is a laudable job of coming up with a
> semi-mathematical and testable alternative to the rather
> lengthy, complex, and less easily validated and texted, XML of
> RFC 7940.
>
> If the document were submitted to the ISE as a "I think this
> would be a better way to do things while meeting the same goals
> as RFC 7940" or even as "this is what ICANN is doing (or
> proposes to do) and the community should know about it" piece,
> I'd have little or no objection to it.  However, as an IETF
> stream document that apparently is intended to replace (or at
> least provide an alternative to) large sections of 7940 with a
> different strategy, either
>
>    -- it should be a standards-track document that explicitly
> 	updates and replaces those portions of 7940, with all of
> 	the documentation and explanation the IESG requires of such
> 	updates.  OR
>
>   -- it should be a standards-track document that provides an
> 	alternative to 7940 and that explains the choices and
> 	tradeoffs.
>
> As an IETF Stream Informational specification, it is an
> apparent IETF Informational document that encourages the
> practice of something other than an IETF Proposed Standard that
> addresses the same topics and requirements, with no
> Applicability Statement or other guidance as to when or if it
> should be applied.
>
> I do not believe it should be published on that basis.
>
> Without descending into details and nitpicking, there are also a
> pair of technical problems.
>
> (1) As RFC 7940 points out, the concept of "variant" and hence
> the relationships needed to express the "increased
> requirements of contemporary IDN variant policies" [RFC7940,
> Section 9] has moved considerably beyond the definition of that
> term and concept in RFC 3743 (aka "the JET specification").
> This document further refines the description of those
> relationships.  However, if one is going to move beyond the JET
> concept -- one tailored to the relationship between Simplified
> and Traditional Chinese characters and not about, e.g., visual
> confusion at all -- it is not clear that there is a technical
> basis for saying "these things are variants and those others
> are not".  The "others" can include synonyms, translations,
> orthographic variations that cannot be expressed in simple
> character (or even character sequence) mappings, and so on.
>
> ICANN made a serious of decisions (IMO, some of them almost by
> accident and others by side-effect or more political reasons)
> as to what kinds of relationships might be considered variant
> candidates, at least for the root zone.  The grammar proposed
> in this document (and the one of 7940) exclude those other,
> non-ICANN-sanctioned, relationships and cannot, in general,
> represent them in spite of the fact that they might be quite
> appropriate (as least for blocking) in non-root zones and have
> been used in exactly that way (indeed, two of the key areas of
> friction between IDNA2008 and Unicode UTS #46 can be seen in
> exactly those terms).    To a certain extent, that is a
> criticism of 7940 rather than this document, but there is an
> important difference, at least IMO: The grammar of 7940 is
> essentially descriptive and, like most good XML structures,
> could easily be expanded with additional elements or element
> components if the need arose.  It is far less clear how one
> would expand a quasi-mathematical grammar, especially one that
> is heavily dependent on special operator symbos and strict
> typologies, like this one.  Even if one were to figure out how
> to expand this as requirements evolve outside ICANN's control,
> such extensions would raise questions of how to keep this
> document and 7940 synchronized.  That issue might be another
> reason for standards track status and either a more explicit
> discussion of relationships and mapping; one or more IANA
> registries or operators, types, and elements; or both.
>
> (2) Independent of the web and the convenience of HTTP redirect
> facilities, it is not only not clear how to implement delegated
> variants in a way taht is not damaging to the Internet and the
> DNS.  The opportunities for combinatorial explosion and
> consequent operational and zone management problems in all but
> a few very special cases (including, historically, the one that
> at least some of the JET designers had in mind) are
> considerable.  The ICANN solution of "just delegate them all to
> the same party and make it their problem" may be satisfactory
> from their corporate point of view, but is not a way to make
> the Internet work better, especially in the context of
> potentially hundreds of names that have to be kept synchronized
> in a way that leads to consistent behavior across all
> protocols.  RFC 7940 exposes some of this problem as well, but,
> again, is rather more descriptive than this document, which
> moves much closer to a set of executable tests that establish
> what is valid (and presumably reasonable) and what is not.
>
> I, and a few others, have suggested in other contexts that
> "variant" has become part of a magical ritual in which one looks
> at a complex DNS-related problem, solemnly chants the word a
> propitious number of times, and the problem is then assumed to
> disappear or be solved.  The issues above are only a few of the
> cases to which variations on that ritual have been applied.
> Unless the IETF has better solutions than magic, it should not
> be legitimizing the magical thinking by publishing documents
> that appear to encourage delegation of "variants".
>
> Two additional nits, the first an important procedural one and
> both to provide illustrative examples that this document would
> need work even if none of the considerations above applied.
>
> (i) At least since RFC 3552, we have not allowed documents in
> the IETF stream that say "There are no security considerations
> for this memo.".   And yet that is exactly what Section 18 has
> to say.
>
> (ii) Section 16 ("Corresponding XML Notation") is a good idea,
> but, rather than providing a comprehensive mapping, it
> essentially says "here are some examples of the mapping between
> notations; everything else is left as an exercise for the
> reader".  I think that is confusing and unfortunate but, if it
> really is what the IETF and the author want to do, it should be
> made much more explicit.
>
>
> thanks,
>     John Klensin
>
>
>
>


From nobody Tue Feb 14 10:33:08 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB2A1296CA; Tue, 14 Feb 2017 10:33:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2N-O6NDYEI8; Tue, 14 Feb 2017 10:33:06 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 1D8741296F5; Tue, 14 Feb 2017 10:33:06 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 18:33:05 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 64618D788B; Tue, 14 Feb 2017 10:33:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=2Udc1oFlG6DgKxvFdQ/STFKHWJg=; b= hJuTcP4qepEsGMzxZoNIrWWSI9UjA1Op8WZJLnmRejHpy1vnspHWCCVNE9sIvFWY 8KM7+QLacSwlZQiYCxt2CLVepE/9X7z/lxB4b2tvfbf60F44JnsWrosLW81CEECY VtFwlVQdFHztlk5Irlqiyp7EWzl+HtgD6bevinlJvTk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=i8i3vG4MX8m7qmdsKqQrULc 4NlgC0t6JjQdAhJVxB7hkH1KvQ3zoL84YDnLH3HsLF5WPJ0oSLd6qAw4pTCE2jYE drKDtft6v2uFMwOatf2SfktuonMn/vgamF/HSKGDF5FeZmoG80XfuPg7e+rulv0Z zIZBlBneffvHFrzhJ4aw=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id EAD4AD788D; Tue, 14 Feb 2017 10:33:04 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 0A7208AD77E0; Tue, 14 Feb 2017 19:33:10 +0100 (CET)
From: otroan@employees.org
Message-Id: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Date: Tue, 14 Feb 2017 19:33:09 +0100
In-Reply-To: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uyf2RoSJgfd112lU3DQBHC-zYEg>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:33:07 -0000

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Stewart,

> *If*  you care about packet loss, then your only option is to probe =
the path with with
> synthetic data that exactly mimics the live data, or not to probe at =
all and live
> with the 1280. As I said 1280 is pretty close to 1496 which is all =
most networks
> will give you in practice.

Yes, but sending at 1280 does not work for IP tunnels. The whole purpose =
of the minimum MTU was to give space for tunnel headers (1500-1280).

> When I think about the people asking for fast re-route to minimise =
packet loss, it seems
> very strange to deliberately induce loss to try to stretch the MTU by =
15%.

Please show the data that there is significant loss. The measurements I =
have found has not shown that.
If not, then let's please leave that argument on the shelf.

(And please don't read me wrong, I think we should get DNS fixed, that =
we should fix the IP tunnelling protocols, and that we should get IP =
fragmentation deprecated).

But right here, right now. PMTUD is for many problems the only solution =
on the table.
We as a community can choose not to elevate the standard of course, and =
that will of course not have any big consequence.
Are you afraid that elevating 1981, will hinder people from working on =
new and better solutions?

Best regards,
Ole

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYo01lAAoJEL7aWKiYQt92u0IP/2lXtgePm1tB/H1AzQng3S7t
olEJPQSkETUOIDopR48/04S3XxRfBGf+5Uh8suPHnZnTiVNZ3goRFZldY02/GRoR
Rfzc45vZBuWOfBwlqsHmgXz8T+rFeJzlzJ+v7feBQ645KPPKHjBMrGs36ojJTdI7
M07bKNFR4uLEXFTlxvC8UCy731Itla0jCwQg4NBB7d45EODIgUl1TocsOsArP05m
XQNW5Ex8E1inNHDIRamHpwd//PTfXnAG4ME+Xrgz6L5RtUX/YiXgIIY2Nadd1/Cv
X+B6BbhM8cjmB/SbEqGu9aPCPlw8UNkpo/s2HFbht0G3U5QnnRDCJSIG9w3tfQhc
YJ3nHpojHg7EHu4g77sMFJzmI9jz9p1TF232DzFzbiNPsbHMIaNF3w104b3Xb1dq
744ED8ZzGNxMTQzHhie/n6tm0Ft4a0RIvwXEjXY8VasUiwMF7HqLW4z8vBsGL0tI
wOzaA0X1R95v2WpJ6zuZz2AfVuwCXTXU2oj/mRD5WAg1bCVdc7Kp02+uFsMBqcp7
awrp7Va3cYAR0Hx6ziqSe7lIbDQlAIk/DTRJyxnsCUZcJaR1bxfUos8bePlKlxks
vuFgkB8+6Ajlz2tUb4+FeeqHqhFILkCJdAPPwQQJJrFnc8gB3P3I8eJDCEAtSkml
2Eif1J254Ib81r6zh4YE
=iCl+
-----END PGP SIGNATURE-----

--Apple-Mail=_F1E3D5C1-E491-43B4-8CCA-75F706C739AE--


From nobody Tue Feb 14 10:36:22 2017
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3148129A86; Tue, 14 Feb 2017 10:36:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 x3aPDU0VTMBd; Tue, 14 Feb 2017 10:36:14 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C48A129685; Tue, 14 Feb 2017 10:36:14 -0800 (PST)
Received: from linne.localnet (91.96.120.134) by linfreserv (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 08FD9E; Tue, 14 Feb 2017 19:36:06 +0100
From: Karsten Thomann <karsten_thomann@linfre.de>
To: ipv6@ietf.org, jordi.palet@consulintel.es
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <1513056.oYYGoBVvp1@linne>
User-Agent: KMail/4.13.0.22 (Windows/6.1; KDE/4.14.3; i686; git-c97962a; 2016-07-14)
In-Reply-To: <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="cp 1252"
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 7
Date: Tue, 14 Feb 2017 10:36:14 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T9A9DsmfQ_qMHQroEdO1A1-jWLg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:36:16 -0000

In my opinion the sentence should be restricted to cases where it's req=
uired=20
to be 64 bit (SLAAC) and allow everything else.

There are enough examples where /127, /126 and /124bit masks are used.

So my favorite version is the one from Brian
>         However, the Interface ID of unicast addresses used for
>         Stateless Address Autoconfiguration [RFC4862] is required
>         to be 64 bits long.

Followed by David's version extended with recommendation of 64bit IID.

Regards
Karsten

Am Dienstag, 14. Februar 2017, 17:07:09 schrieb JORDI PALET MARTINEZ:
> I understand that, but those are two clear exceptions, no others shou=
ld be
> =93allowed=94 by default.
>=20
> Keeping the door open is not good in my opinion. Specific exceptions =
must be
> taken in consideration one by one.
>=20
> Regards,
> Jordi
>=20
>=20
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@um=
n.edu>
> Responder a: <farmer@umn.edu>
> Fecha: martes, 14 de febrero de 2017, 17:03
> Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
> CC: 6man WG <ipv6@ietf.org>, <draft-ietf-6man-rfc4291bis@ietf.org>,
> IETF-Discussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org> As=
unto:
> Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addr=
essing
> Architecture) to Internet Standard
>=20
>     The problem we want it to be 64 bits except when it's not suppose=
 to be,
> such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv6 translat=
ors
> with /96 Network-Specific Prefix.
>=20
>     On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es> wrote:
>=20
>     Agree, we shouldn=92t change that. Must be 64 bits.
>=20
>     Regards,
>     Jordi
>=20
>=20
>     -----Mensaje original-----
>     De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer
> <farmer@umn.edu> Responder a: <farmer@umn.edu>
>     Fecha: martes, 14 de febrero de 2017, 16:27
>     Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
>     CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>=
, 6man
> WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org> Asunto=
: Re:
> Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressi=
ng
> Architecture) to Internet Standard
>=20
>         Actually, in addition to your text there still needs to be a
> recommendation for 64 bit IIDs in all other cases.  64 bit IIDs are(a=
nd
> should remain) the norm for IPv6, I do not want to change that.  But =
the
> current language say IIDs are always 64 bit except when an address be=
gins
> with binary 000, leaving no room for any other exception.  And this i=
s
> plainly incorrect, I provided two clear exceptions that are already
> standardized.  Furthermore, IIDs other than 64 bits are in operationa=
l use,
> with manual configuration and DHCPv6. So I'd suggest;
>=20
>         However, the Interface ID of unicast addresses used for
>         Stateless Address Autoconfiguration [RFC4862] is required
>         to be 64 bits long, in all other cases it is recommended to
>         be 64 bits long.
>=20
>         The other option is to enumerate all the exceptions, requirin=
g the
> document to be updated every time a new exception is standardized.
>=20
>         On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>=20
>         At an earlier stage I suggested restricting the applicability=

>         of the "However..." sentence to SLAAC [RFC4862]. A short way
>         of doing this would be
>=20
>         However, the Interface ID of unicast addresses used for
>         Stateless Address Autoconfiguration [RFC4862] is required
>         to be 64 bits long.
>=20
>         Regards
>            Brian
>=20
>         On 14/02/2017 11:32, David Farmer wrote:
>         > I have concerns with the following text;
>         >=20
>         >    IPv6 unicast routing is based on prefixes of any valid l=
ength
>         >    up to
>         >    128 [BCP198].  For example, [RFC6164] standardises 127 b=
it
>         >    prefixes
>         >    on inter-router point-to-point links. However, the Inter=
face ID
>         >    of
>         >    all unicast addresses, except those that start with the =
binary
>         >    value
>         >    000, is required to be 64 bits long.  The rationale for =
the 64
>         >    bit
>         >    boundary in IPv6 addresses can be found in [RFC7421]
>         >=20
>         > The third sentence seems to limit exceptions to 64 bit IIDs=
 to
>         > exclusively
>         > addresses that start with binary vale of 000.  There are at=
 least
>         > two other
>         > exceptions from standards track RFCs, that should be more c=
lear
>         > accounted
>         > for in this text.  First is [RFC6164] point-to-point links,=
 as
>         > mentioned in
>         > the previous sentence.  I think the clear intent of [RFC616=
4] is
>         > to allow
>         > one(1) Bit IIDs for point to point-to-point links using any=
 Global
>         > Unicast
>         > Address, not just those that start with 000.  Second is,
>         > [RFC6052], which
>         > updates [RFC4921] and seems to allow 32 bit IIDs or /96 pre=
fixes
>         > for any
>         > Global Unicast Address when used for IPv4/IPv6 translation,=

>         > referred to as
>         > ""Network-Specific Prefix" unique to the organization deplo=
ying
>         > the address
>         > translators," in section 2.2 of [RFC6052].
>         >=20
>         > Thanks.
>         >=20
>         > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ie=
tf.org>=20
wrote:
>         >> The IESG has received a request from the IPv6 Maintenance =
WG
>         >> (6man) to
>         >> consider the following document:
>         >> - 'IP Version 6 Addressing Architecture'
>         >>=20
>         >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard=

>         >>=20
>         >> The IESG plans to make a decision in the next few weeks, a=
nd
>         >> solicits
>         >> final comments on this action. Please send substantive com=
ments
>         >> to the
>         >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally,
>         >> comments may be
>         >> sent to iesg@ietf.org instead. In either case, please reta=
in the
>         >> beginning of the Subject line to allow automated sorting.
>         >>=20
>         >> Abstract
>         >>=20
>         >>    This specification defines the addressing architecture =
of the
>         >>    IP
>         >>    Version 6 (IPv6) protocol.  The document includes the I=
Pv6
>         >>    addressing
>         >>    model, text representations of IPv6 addresses, definiti=
on of
>         >>    IPv6
>         >>    unicast addresses, anycast addresses, and multicast add=
resses,
>         >>    and an
>         >>    IPv6 node's required addresses.
>         >>   =20
>         >>    This document obsoletes RFC 4291, "IP Version 6 Address=
ing
>         >>    Architecture".
>         >>=20
>         >> The file can be obtained via
>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bi=
s/
>         >>=20
>         >> IESG discussion can be tracked via
>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bi=
s/ballo
>         >> t/
>         >>=20
>         >>=20
>         >> No IPR declarations have been submitted directly on this I=
-D.
>         >>=20
>         >>=20
>         >>=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
>         > -----------------------------------------------------------=
-------
>         > --
>=20
>         --
>         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D
>         David Farmer               Email:farmer@umn.edu
> <mailto:Email%3Afarmer@umn.edu> <mailto:Email%3Afarmer@umn.edu
> <mailto:Email%253Afarmer@umn.edu>> Networking & Telecommunication Ser=
vices
>         Office of Information Technology
>         University of Minnesota
>         2218 University Ave SE        Phone: 612-626-0815 <tel:612-62=
6-0815>
> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:612-812-9952>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>=20
>=20
>=20
>=20
>=20
>=20
>=20
>     **********************************************
>     IPv4 is over
>     Are you ready for the new Internet ?
>     http://www.consulintel.es
>     The IPv6 Company
>=20
>     This electronic message contains information which may be privile=
ged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be a=
ware
> that any disclosure, copying, distribution or use of the contents of =
this
> information, including attached files, is prohibited.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>=20
> This electronic message contains information which may be privileged =
or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be a=
ware
> that any disclosure, copying, distribution or use of the contents of =
this
> information, including attached files, is prohibited.
>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue Feb 14 10:54:36 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71D0B1297AA; Tue, 14 Feb 2017 10:54:30 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6_en8OkY62uV; Tue, 14 Feb 2017 10:54:29 -0800 (PST)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (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 D7FCB1297A5; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
Received: by mail-it0-x242.google.com with SMTP id e137so6522345itc.0; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zoljRW9e/UePysa9t3UpARD6TJXQUjGQNMwSDSa/q3M=; b=fXQYCVFPG+GY38kyzGQMn8DYSvLqS9kuXBaeaPoXTPlzMqQK6hiM+N1wUt9VBJvSX/ p7EmOEnJ/VHEt8mPSJGaTg+brVntzh0jSgp26OobbcvTwot+kPsy6kJJg4U4JMvWmp1A n7/uNVjBfGkQWWvupsLvC0suAVOpdypy+8lKlCEKOjZj8q7IO19rtx1BDM5ZHJgcome5 +3Yv00mcboBLSBfxuvIF8WVpd8RsFvrSO1/q74yRpRGluhJ9BxgiHBQyGvp2icXBmhsb GwcuaIcEB08wbYQJd3xsXOw5YryRgcnJZvX3pdwGRjF2g8Ex9IF761TSo7FnPjmvMYcr VUcw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=zoljRW9e/UePysa9t3UpARD6TJXQUjGQNMwSDSa/q3M=; b=tEnSTg+wqgugwIYg2SmhIajf4pmQ2Plxsq3eIIYKtfIeWGb42Ny0UiBclaxf58f9oB QXk/XKCLtzw5bpITXoIB1OGEmki/xpR3WaQn1Bap086fk2hQmr33SzaYl3I2ve5ReMh2 I50Drt7BmV99hmn59bm8sPdXB7usleO2rd12EWcQghuhAtvqcWrK0a5a2BFDyOclBMzv muQixDHG9aOuGNBG9GqRX1Qa4+Li4WZPqIUejDJKziUz0uR/d7raK6pGwnXsaZTdpd9P DiCc9nJWo51mob0qrsuZMGAkbcq/oMZpqJAGzP7oKQUvHPcbS+gulRDahvrMBimp5nxV M86Q==
X-Gm-Message-State: AMke39mhFO+wXWjkL5QkNpypfcbUWTQlRI0F95NLcAHOcJle0J1FHe+DFmjvA7Htju2/WA==
X-Received: by 10.84.131.130 with SMTP id d2mr5396174pld.41.1487098468212; Tue, 14 Feb 2017 10:54:28 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id r78sm2698005pfl.63.2017.02.14.10.54.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 10:54:27 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Date: Tue, 14 Feb 2017 10:54:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC4EEF4D-45E6-4E1B-8FCA-226E5E55BEEF@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uAXRbYUlkbY-HXJWbuP-H8eqANk>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:54:30 -0000

> On Feb 14, 2017, at 10:33 AM, otroan@employees.org wrote:
>=20
>> *If*  you care about packet loss, then your only option is to probe =
the path with with
>> synthetic data that exactly mimics the live data, or not to probe at =
all and live
>> with the 1280. As I said 1280 is pretty close to 1496 which is all =
most networks
>> will give you in practice.
>=20
> Yes, but sending at 1280 does not work for IP tunnels. The whole =
purpose of the minimum MTU was to give space for tunnel headers =
(1500-1280).

I'm confused by that statement. =
https://tools.ietf.org/html/rfc7676#section-3.2 indicates that a GRE =
tunnel on IPv6 and carrying an IPv6 payload works with a PMTU of 1280, =
and AFAIK it is among the larger tunnel headers. What tunnels does a =
PMTU of 1280 not work for?=


From nobody Tue Feb 14 10:55:18 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 233FD129A9F; Tue, 14 Feb 2017 10:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 8Vjswx_p9F03; Tue, 14 Feb 2017 10:55:11 -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 1A280129AA8; Tue, 14 Feb 2017 10:54:44 -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 v1EIshnx015092; Tue, 14 Feb 2017 11:54:43 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EIsYLf014962 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 11:54:34 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 10:54:33 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 10:54:33 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>, Stewart Bryant <stewart.bryant@gmail.com>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAAEjdGhAACokzA=
Date: Tue, 14 Feb 2017 18:54:33 +0000
Message-ID: <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4z1Bv4IrDdCov3_nhABPTEkU6Ao>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:55:13 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Tuesday, February 14, 2017 10:33 AM
> To: Stewart Bryant <stewart.bryant@gmail.com>
> Cc: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <brian=
.e.carpenter@gmail.com>; gen-art@ietf.org; 6man WG
> <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Stewart,
>=20
> > *If*  you care about packet loss, then your only option is to probe the=
 path with with
> > synthetic data that exactly mimics the live data, or not to probe at al=
l and live
> > with the 1280. As I said 1280 is pretty close to 1496 which is all most=
 networks
> > will give you in practice.
>=20
> Yes, but sending at 1280 does not work for IP tunnels. The whole purpose =
of the minimum MTU was to give space for tunnel headers
> (1500-1280).

But, if non-tunnel links set a 1280 MTU which is perfectly OK with the stan=
dard then
there is no space for headers. Given the issues with classical PMTUD then (=
plus the
non-applicability of RFC4821 for tunnels) the only solution for tunnels is =
fragmentation.
I'll let Joe step in if he wants to.

Thanks - Fred

> > When I think about the people asking for fast re-route to minimise pack=
et loss, it seems
> > very strange to deliberately induce loss to try to stretch the MTU by 1=
5%.
>=20
> Please show the data that there is significant loss. The measurements I h=
ave found has not shown that.
> If not, then let's please leave that argument on the shelf.
>=20
> (And please don't read me wrong, I think we should get DNS fixed, that we=
 should fix the IP tunnelling protocols, and that we should
> get IP fragmentation deprecated).
>=20
> But right here, right now. PMTUD is for many problems the only solution o=
n the table.
> We as a community can choose not to elevate the standard of course, and t=
hat will of course not have any big consequence.
> Are you afraid that elevating 1981, will hinder people from working on ne=
w and better solutions?
>=20
> Best regards,
> Ole


From nobody Tue Feb 14 10:59:47 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F36721294C2 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 10:59:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-d3dj9R7dpe for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 10:59:44 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id EBCC2129739 for <ietf@ietf.org>; Tue, 14 Feb 2017 10:59:43 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 18:59:43 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 9BC6BD788A; Tue, 14 Feb 2017 10:59:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=YkVufYEEk23ImnRC0oVrvTFRi5Y=; b= sX99y3UJqgr2MdNIiXS9oEBiX+nlKuoE565us0x5opCEa4VuYU0ejbL5rLnXi1MJ 2fGfoVH/exulkSDDB752Dy8JmfmuUwBXjVBMnVK2DlX4FHIimjILNdBH8bxkWttd Q9h4JAgaM41ZXHQVoo0lArfrEXuRUxOCr9/GLILQlR4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=i2fk2nGL9i1qfWWWuKKrSnZ /U4NbKZequUWIT+kCIFYVKirnxJEWY46d6aEv6kRiPNFYpvXNYgC2Chq3Xc6Gedr vHvwa361xwiAFsJmTH+wAD1b8w2Wi3jk22FcohVLvBM9XXE+mzC1vXu0r/6kWuAq UrCPQzb93oKZTKoxu8ak=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3EE4DD788E; Tue, 14 Feb 2017 10:59:43 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 388148ADFA4F; Tue, 14 Feb 2017 19:59:49 +0100 (CET)
From: otroan@employees.org
Message-Id: <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_61DD03A2-BF32-430C-B198-CAC7EFDDC689"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Tue, 14 Feb 2017 19:59:48 +0100
In-Reply-To: <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <EA7E5B60-F136-47C6-949C-D123FB8DA70E@cisco.com> <00af01d27e11$fe539500$4001a8c0@gateway.2wire.net> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J8giGeofl5di7_0VfVw750ox7po>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 18:59:46 -0000

--Apple-Mail=_61DD03A2-BF32-430C-B198-CAC7EFDDC689
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joel,

> There are two separate but related issues here.  One is what behavior =
we want to require.  The other is whether we make the document clear.
>=20
> I think choosing to leave a document going to Internet Standard =
ambiguous is a serious mistake, bordering on failure.  We know that the =
choice of permitting insertion of extension headers has interoperability =
implications.  There are weveral ways we can clarify the text.
> o We could say "MUST NOT" be added.  Preferably with explaantion of =
the problems being avoided.

Yes.

> o We could say "MUST NOT unless some other standards track RFC says it =
is okay" which is technically correct but confusing.

That's redundant. A new standards RFC can always be written that will =
override this.

> o We can say "SHOULD NOT unless ..." as long as we can write a clear =
description of the conditions under which it is safe.

As the 6man chair we declared that as out of scope in the context of =
advancing 2460 to Internet standard.

> o We can say "AMY< but note that doing so has the following risks" if =
that is the IETF rough consensus.

Middleboxes live in unregulated territory, there was no support (or even =
suggestion) in the working group for explicitly permitting header =
insertion.

> But leaving it ambiguous ought to be a non-starter.

Why?
Leaving it as it was, including describing what we would imagine it =
would break was the preferred solution in the working group.
Note that both IPv4 and IPv6 has this so-called ambiguity, that has =
caused no known interoperability issues and has existed for decades.

This is perceived as an ambiguity only because we as a community have =
accepted layer violations for so long.
This can be exemplified by discussions on maximum extension header =
length in IPv6. The only reason that discussion happens is because =
middleboxes require access to the transport header and beyond. In a =
purist 2460 view a router doing 5-tuple ECMP is not compliant with the =
specification. Clarifying that ambiguity would probably not make the =
operational community proud of us.

The only purpose an outright ban would achieve, would be a pre-emptive =
strike against potential future standardisation.

So when you think long enough about it, which choice you pick will =
unlikely have much consequence either way. It has no effect on =
implementations, it is not testable. In the context of 2460 this isn't a =
debate with many technical points.

Which is why the working group could not reach a consensus, and we ended =
up decided it with a poll. Do you prefer your bike shed red, yellow or =
green. You have added a couple of more colours.

> Personally, I would go with "MUST NOT", as I think that is the robust =
and interoperable answer.  But that is MUCH less important to me than =
our being unambiguous.

There is an infinite set of creative (ab)uses of 2460 that hasn't been =
banned. I would claim it would be impossible to write a document which =
would MUST NOT every potential abuse.

Best regards,
Ole

--Apple-Mail=_61DD03A2-BF32-430C-B198-CAC7EFDDC689
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYo1OlAAoJEL7aWKiYQt92GN4QAIhLKKvkYpKjtnReEvgDWIcz
2952qyR5E6wDN6NRwbvFLmpE2F6QxFvOZ/ra+Hn4H/wmxcmA7lALRQBHVWxq39VU
8Ca3K7ynUu8OH1A3JolHHguofLd9QnIuXM9Zer+LoI8SjvuCqFc8R7PGtIui3JJA
s4Y/OEHdwqAXRFVWDSZcRkRHJGrl4csvtp6W8TC1Zu/VggkXSdmIxg86UltIN3nT
qF283HJ0oMuI3/YevhRRYBkbqjIECb03N0gn9ibouBxBcsvxUw3w+KEu6NAbLh3t
vvIAk+BdyKYO6dtGk6jxKhfQAtCeCFz69zV1R/A2TgOmeOhlMgh9Td9E5pNDP3Zh
evroLy15BvUnBmfXm/If8rhqiTiDOktpPodwDwHqNffyrLR6UWBEcH15NldFWX1a
xQ5PfZOlDawMZ9KNCXAlrz7F+nv5/2frTEKRKiOYFaczutILGH2nqLTnx2gMa84q
iFLHG7OYe2HhkmyRco5Gi8jQiaIS63n09cGCp7+Mu0xqxM7Txqt0kHY4PLPst82t
R+yJhcTcSPH2Brodf4M3P+a0djYWJ3Cc1+z2+Zt7FVxVKsijcaGP38eGeZShakb6
+Wz0i6JKVhBx62LY/2pse6EIidpjFjhVIjzwOuBcl/+UaOBRHty7X0d2BSqvKp87
RkgBcj5WIv7du1IDXDe3
=OX3F
-----END PGP SIGNATURE-----

--Apple-Mail=_61DD03A2-BF32-430C-B198-CAC7EFDDC689--


From nobody Tue Feb 14 11:05:15 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379481294C2 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:05:14 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eTBEErNmfJf9 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:05:12 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (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 DA6401296DD for <ietf@ietf.org>; Tue, 14 Feb 2017 11:05:12 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id C12BA32E455; Tue, 14 Feb 2017 11:05:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487099112; bh=gy9Danh/rFFMlL5NgCN/6mskrWK1bfdwQwj4RZFbmRQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=mPFs+CyBIxG3V/KznLLR7a/D7YW9lsMhciSZRFRxVqpMXfAodqpXnwnnZJnH/5ZxF dXUHoTU0V0Uen3VvjTVsxank7Orng1Iy6P/HmyTnCYWVh0K0SYEFfm3vBMWoFDLMtU 0zCnhpus0CkizdcHcUhoRUPX3qkkAoIl4h7Xot90=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 282F932E452; Tue, 14 Feb 2017 11:05:12 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com>
Date: Tue, 14 Feb 2017 14:05:11 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N34R4qiwT7hBkNaI5lHm_2kzS4c>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:05:14 -0000

Ole, it is true that we write in English, and there is always room for
"interpretation", sometimes reasoanble room, sometimes not.

But in this case we have a demonstrated difference in how people
understand the existing text.  When we have such a demonstrated
difference, we have an obligation to address it.

Yours,
Joel

PS: The ability to do ECMP is why I helped with and supported the effort 
to get the flow label use for ECMP entropy documented.  That would 
ameliorate a number of problems.  I do not expect this revision of 2460 
to fix that, particularly since there seems to be little adoption.  I 
try not to get distracted looking for perfection.


On 2/14/17 1:59 PM, otroan@employees.org wrote:
> Joel,
>
>> There are two separate but related issues here.  One is what
>> behavior we want to require.  The other is whether we make the
>> document clear.
>>
>> I think choosing to leave a document going to Internet Standard
>> ambiguous is a serious mistake, bordering on failure.  We know that
>> the choice of permitting insertion of extension headers has
>> interoperability implications.  There are weveral ways we can
>> clarify the text. o We could say "MUST NOT" be added.  Preferably
>> with explaantion of the problems being avoided.
>
> Yes.
>
>> o We could say "MUST NOT unless some other standards track RFC says
>> it is okay" which is technically correct but confusing.
>
> That's redundant. A new standards RFC can always be written that will
> override this.
>
>> o We can say "SHOULD NOT unless ..." as long as we can write a
>> clear description of the conditions under which it is safe.
>
> As the 6man chair we declared that as out of scope in the context of
> advancing 2460 to Internet standard.
>
>> o We can say "AMY< but note that doing so has the following risks"
>> if that is the IETF rough consensus.
>
> Middleboxes live in unregulated territory, there was no support (or
> even suggestion) in the working group for explicitly permitting
> header insertion.
>
>> But leaving it ambiguous ought to be a non-starter.
>
> Why? Leaving it as it was, including describing what we would imagine
> it would break was the preferred solution in the working group. Note
> that both IPv4 and IPv6 has this so-called ambiguity, that has caused
> no known interoperability issues and has existed for decades.
>
> This is perceived as an ambiguity only because we as a community have
> accepted layer violations for so long. This can be exemplified by
> discussions on maximum extension header length in IPv6. The only
> reason that discussion happens is because middleboxes require access
> to the transport header and beyond. In a purist 2460 view a router
> doing 5-tuple ECMP is not compliant with the specification.
> Clarifying that ambiguity would probably not make the operational
> community proud of us.
>
> The only purpose an outright ban would achieve, would be a
> pre-emptive strike against potential future standardisation.
>
> So when you think long enough about it, which choice you pick will
> unlikely have much consequence either way. It has no effect on
> implementations, it is not testable. In the context of 2460 this
> isn't a debate with many technical points.
>
> Which is why the working group could not reach a consensus, and we
> ended up decided it with a poll. Do you prefer your bike shed red,
> yellow or green. You have added a couple of more colours.
>
>> Personally, I would go with "MUST NOT", as I think that is the
>> robust and interoperable answer.  But that is MUCH less important
>> to me than our being unambiguous.
>
> There is an infinite set of creative (ab)uses of 2460 that hasn't
> been banned. I would claim it would be impossible to write a document
> which would MUST NOT every potential abuse.
>
> Best regards, Ole
>


From nobody Tue Feb 14 11:06:20 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600721294C2; Tue, 14 Feb 2017 11:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qdXurjnGDnPz; Tue, 14 Feb 2017 11:06:13 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id DE972129699; Tue, 14 Feb 2017 11:06:13 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 19:06:13 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 8BDCED788A; Tue, 14 Feb 2017 11:06:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=tUgPBc96MmL2tyhZIFs0PkSUU3g=; b= lDPPfGtcQO0Z97m/KwvFHrrs4ikmh892fJ03aPwBntXEuLcEPls/BzocPYOiXxBo lhAPl7lj6UgGiqpnnOwycdP8Tu2Mr9S85KbKPzcEqo5IyMHycvaYJ6jS14iEJuYD t8Rxez2y5EVPfJziPE52oM7rB4lc9ebUuIsB2YTQgmQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=C8Z//jemiiJLjSIfcQ6W61e iGpcEFnmDkBDDE4QPzXFPRSrSVo3ALnDTQGCcdXUX6+JX1IeE67snlrIw9Uv1Fxg IUCPwf1BVNoUZCmYPfzMmF9zYQhjI/4Ifz97ZW+QvZfZ54AeLjwjBewiIZfz+Qt4 4nNs3uzXqwO5ITCcVXPo=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 36301D788F; Tue, 14 Feb 2017 11:06:13 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2A0388AE114B; Tue, 14 Feb 2017 20:06:19 +0100 (CET)
From: otroan@employees.org
Message-Id: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_8238D4C0-DA5D-4EEE-BBEF-654D580924CF"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Tue, 14 Feb 2017 20:06:18 +0100
In-Reply-To: <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXEmVzsgyN4JPnvCxuL49t1fazc>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:06:15 -0000

--Apple-Mail=_8238D4C0-DA5D-4EEE-BBEF-654D580924CF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

> At an earlier stage I suggested restricting the applicability
> of the "However..." sentence to SLAAC [RFC4862]. A short way
> of doing this would be
>=20
> However, the Interface ID of unicast addresses used for
> Stateless Address Autoconfiguration [RFC4862] is required
> to be 64 bits long.

Brian, changing the 64 bit boundary is such a big change that I would =
claim it is far outside the scope of advancing 4291 to Internet =
standard.

See https://tools.ietf.org/html/rfc7421 (which you by the way are the =
author of), for the set of documents that would have to change.
There are unknown interoperability issues here as well. As well as =
architectural considerations that probably should have IAB involvement.

Best regards,
Ole



> On 14/02/2017 11:32, David Farmer wrote:
>> I have concerns with the following text;
>>=20
>>   IPv6 unicast routing is based on prefixes of any valid length up to
>>   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>>   on inter-router point-to-point links. However, the Interface ID of
>>   all unicast addresses, except those that start with the binary =
value
>>   000, is required to be 64 bits long.  The rationale for the 64 bit
>>   boundary in IPv6 addresses can be found in [RFC7421]
>>=20
>> The third sentence seems to limit exceptions to 64 bit IIDs to =
exclusively
>> addresses that start with binary vale of 000.  There are at least two =
other
>> exceptions from standards track RFCs, that should be more clear =
accounted
>> for in this text.  First is [RFC6164] point-to-point links, as =
mentioned in
>> the previous sentence.  I think the clear intent of [RFC6164] is to =
allow
>> one(1) Bit IIDs for point to point-to-point links using any Global =
Unicast
>> Address, not just those that start with 000.  Second is, [RFC6052], =
which
>> updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixes for =
any
>> Global Unicast Address when used for IPv4/IPv6 translation, referred =
to as
>> ""Network-Specific Prefix" unique to the organization deploying the =
address
>> translators," in section 2.2 of [RFC6052].
>>=20
>> Thanks.
>>=20
>> On Wed, Feb 1, 2017 at 5:51 PM, The IESG <iesg-secretary@ietf.org> =
wrote:
>>=20
>>>=20
>>> The IESG has received a request from the IPv6 Maintenance WG (6man) =
to
>>> consider the following document:
>>> - 'IP Version 6 Addressing Architecture'
>>>  <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>>>=20
>>> The IESG plans to make a decision in the next few weeks, and =
solicits
>>> final comments on this action. Please send substantive comments to =
the
>>> ietf@ietf.org mailing lists by 2017-03-01. 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.
>>>=20
>>> Abstract
>>>=20
>>>=20
>>>   This specification defines the addressing architecture of the IP
>>>   Version 6 (IPv6) protocol.  The document includes the IPv6 =
addressing
>>>   model, text representations of IPv6 addresses, definition of IPv6
>>>   unicast addresses, anycast addresses, and multicast addresses, and =
an
>>>   IPv6 node's required addresses.
>>>=20
>>>   This document obsoletes RFC 4291, "IP Version 6 Addressing
>>>   Architecture".
>>>=20
>>>=20
>>>=20
>>>=20
>>> The file can be obtained via
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>>>=20
>>> IESG discussion can be tracked via
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
>>>=20
>>>=20
>>> No IPR declarations have been submitted directly on this I-D.
>>>=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
>>=20
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------


--Apple-Mail=_8238D4C0-DA5D-4EEE-BBEF-654D580924CF
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYo1UqAAoJEL7aWKiYQt92ZbIP/i8SAJz8w909hkAUt5ne/Wo5
sRthP7IzeBB8XbTCorsGs5n9qGOJJ2mjirBH+kE0d9GHq4Glq3rc+xsl9wtEtg+W
+SlZuTmUie6WVPhiL8QHTS0ccA/GzMFgt6HlI78IrTtReVDtI2KYGVyN8cgSECQb
5oajhgT7pD0EkfvUcAiOB80r5OOA/cXqUvRLB8txh5sZcA70DZEdYefGMZniLqeJ
ctEFp93TLVRQLf6KzYYw01PQcSeAIwPNOivzhcoP3uaJQQvUHjoR+RaXsdmKHT+W
bJSOVTj9aznKs/Oa1orSTp8n3v05vTayeSug7B4uUbHyjtiiuOBZC5IFwjK02UCU
mrl/msGjxAoVyHlXi6SCnIHWJKaj1TqeuIdwq3aljEzbFkUyL6GMXvtxwNopre6B
cjp4X6z0hs3UAmSFUMcyl15nou7MjwUFuB2F0Uces/2Ubt/bMuUizwTEcDH+IHG2
TDat+WcdkLLF37uwcMfgtXkt+rDwjOp991yflCp5K7m7siCZkSqNmLEcjd9WhLkU
Pw5TzUiiUPl6w7YTOtvA/JpnwK0qlZnU7brKv8PI3L6rb5ayXPAq/KhULKSN8Bn9
EDSUkSsr3je0E941MK20OztkQdLEl7mlEJTKQRrQEQX/Q1Gb/kFITTGHlbZpRexy
aFf19Pc5wb5iDsoNKb/c
=/4Im
-----END PGP SIGNATURE-----

--Apple-Mail=_8238D4C0-DA5D-4EEE-BBEF-654D580924CF--


From nobody Tue Feb 14 11:12:55 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E21812970A for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:12:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GLYJpP84mi4G for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:12:52 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id A70031294C2 for <ietf@ietf.org>; Tue, 14 Feb 2017 11:12:52 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 19:12:52 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 5AAEED788E; Tue, 14 Feb 2017 11:12:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=J0U122sRmw+OECQOMorB7Jg+5Qc=; b= qJsX+MugKiEiQatYaK+MZWIV237hvV8j5xBRtDcW9SzAb2+pDVO1ORrC7yx7jfvZ b7mzZyPLAz0+VwiofvyRyvnTic876mrD4IeglFABSiOtY6G3U7JSjyjQV1Ju/Qzt EQkK73zio0yh4tOFJLp6K29EmFuSQYBBJR+LoaADeB8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=YZQuwKBH3tiObx4d7MzcUrw eDZhVP71SdX57uC/7KrnHyxzG4PXUzMkyF28wfEjMYN2fnLBhqG/crG9D/Rf5BVl wm+mUKhfIha0UzqhaCV4VX7lVqdNoBNJEUqg0fV2PpC2uf9axsN3DWMe4OFbiHV8 eXA0shKkjFlaX2OxCn2k=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id E1E75D788B; Tue, 14 Feb 2017 11:12:51 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 71DC28AE2ED5; Tue, 14 Feb 2017 20:12:57 +0100 (CET)
From: otroan@employees.org
Message-Id: <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_437B81B8-3B90-444C-8ACE-58116BED0314"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Tue, 14 Feb 2017 20:12:57 +0100
In-Reply-To: <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <60F01869-8B32-46D3-80B1-A140DF1DDA8A@employees.org> <8D401C5B-C3C3-4378-9DFA-BF4ACC8E9DAF@qti.qualcomm.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F7zsBQoksj5AICwJ1A-hwb4mx_Y>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:12:54 -0000

--Apple-Mail=_437B81B8-3B90-444C-8ACE-58116BED0314
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joel,

> Ole, it is true that we write in English, and there is always room for
> "interpretation", sometimes reasoanble room, sometimes not.
>=20
> But in this case we have a demonstrated difference in how people
> understand the existing text.  When we have such a demonstrated
> difference, we have an obligation to address it.

This particular issue has caused no interoperability issue, and only a =
single question to the working group 20 years ago.
The current debate has been caused by a set of new proposals, =
independently of 2460, where the authors have in a creative reading of =
the current text figured out that they can shoe-horn header insertion in =
without actually violating the specification. Now, if clarifying the =
text was done, then I presume these proposals would just adapt to update =
2460bis instead. The real battle would in any case have to be over those =
documents, not this one.

Now for the snarkiness; an issue that has created real problems is both =
IETF specifications (although experimental) and implementations of =
address rewriting by intermediate boxes. And there isn't a explicit ban =
on address rewriting in 2460. Should we add that? Would it help?

> PS: The ability to do ECMP is why I helped with and supported the =
effort to get the flow label use for ECMP entropy documented.  That =
would ameliorate a number of problems.  I do not expect this revision of =
2460 to fix that, particularly since there seems to be little adoption.  =
I try not to get distracted looking for perfection.

Yes, and that's greatly appreciated!

Best regards,
Ole


--Apple-Mail=_437B81B8-3B90-444C-8ACE-58116BED0314
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYo1a5AAoJEL7aWKiYQt923qUP/2ltwAaF7WpmrDobXTCEU672
1+n2VuCVbXlTmIJLU/OaPOHBDcJ+VbouzdHPG1h9jrUstLoShgzmmMe5txjNrRN4
mdsBJ6o/8Y/CG65OAglKPxCk21M8hop3BRB8x6d5ZtU79NXGF/4cDqnLSGO1WFmT
f2hq/7QivK0vkcXjydcB7tAPAgD7f2Eap0h14wA/dfGsxgMw7t2uqJPwlSreNsSj
XXOuHzB209GQxVVJqH9uVbpWhMT++TGiuV6HyiEnc/kXLskVud0ybqt17jKJkFrW
xo+e/GS23/UEI1wTG8tDWEKgB7W+sa3WgD4OLfOSPf7yLDEtoFSX6msrAsJdLGUu
EOS/HgZxAwl2Hevcuf8lRi6CVcQl2iNgQRjb7UmL62ilW8hUVIB7MH6syAm6YE/a
7H8xyFM2bTghv1omptY1n7fqq1D6PZh8H//ipa2JusR0+24ISeyOrXC+A8KGQ9A2
xa8OL7iduyysCOsYnw6iO22zT9Znd56QdsJaWMpwAiwmAUxhltnfheGw8fuM/rFB
TzrS3xPfI0KLLd1o8UCHu4eQmlu0Gp15koj+QUl6OATvBYImtnEuwyBDXCVyqA0X
4+vEkMV4Yml6cR0MF4S0q+CUtdK+oJYMHAG0EJtpaXKiTBuVMkFp07igco1GtYBk
WCgnbq5+yfTmGDVeXbCj
=Hm3E
-----END PGP SIGNATURE-----

--Apple-Mail=_437B81B8-3B90-444C-8ACE-58116BED0314--


From nobody Tue Feb 14 11:16:54 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B71E11296B2; Tue, 14 Feb 2017 11:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZVjaTKiFuvW3; Tue, 14 Feb 2017 11:16:51 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 301B9129603; Tue, 14 Feb 2017 11:16:51 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 14 Feb 2017 19:16:51 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E5B67D788A; Tue, 14 Feb 2017 11:16:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=wPMheHye/k6TPP7yBAQ3/E5Lf+8=; b= Prnp1qMQ3lJVha8eIgu9mPhoGeU4UJN6pqwiPZPYXV4qacjQGZRh5OS/qRzh//+a eU+xpDOrc/TGrzdIBhl9qRYutWQ6s8TjiVt7q/CJhFtaDy8FwA77gX1JzDXCzdZz LqNFrngL1SvzDsJ/qeg1c0arG/6Qw065Eq+5qREmnTU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=I8EVsHdJz8SFNAno7z5w7aA aWZlCpTpYXbEkwNF9EMEjTm9q2saGpNp8Ywk60U37HXr82i41YLS9O9RFaaWr+jG AGi2Sr3Svgx8eO3doaU0K3cSAfwNcTVz5QV12/xmIxkyA5BNdyS2JNUKboM+9E6D Ia4+KH2iVJUEZYE1SgVc=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B18BED788E; Tue, 14 Feb 2017 11:16:50 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id AB8CD8AE4338; Tue, 14 Feb 2017 20:16:56 +0100 (CET)
From: otroan@employees.org
Message-Id: <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Date: Tue, 14 Feb 2017 20:16:56 +0100
In-Reply-To: <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uaUSzfqfjB1ub_dLFp7RBVjTmrE>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:16:53 -0000

--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fred,

>> Yes, but sending at 1280 does not work for IP tunnels. The whole =
purpose of the minimum MTU was to give space for tunnel headers
>> (1500-1280).
>=20
> But, if non-tunnel links set a 1280 MTU which is perfectly OK with the =
standard then
> there is no space for headers. Given the issues with classical PMTUD =
then (plus the
> non-applicability of RFC4821 for tunnels) the only solution for =
tunnels is fragmentation.
> I'll let Joe step in if he wants to.

You are correct. "Does not work for IP tunnels without fragmenting the =
outer header" is what I should have written.
Of course it appears IPv6 fragments have a order of magnitude higher =
drop probability than ICMP PMTUD messages.

Pick your poison.

Best regards,
Ole


--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYo1eoAAoJEL7aWKiYQt92YoYP/R3MJD4Hc99194o2w19VE3Vj
rxE6NM5DQ+oIH/qvh4Wwc4HwkM0vc/Mv28YzDIfwiOeJk1QvBGi8M4vuOJkpQ7/6
IEtG2oJ9ZPs8pI9HmiQw2EKKDoWVbXBd35zhStLOoyJrMOMDPZ/Z23+0oxJUZO3P
dcW//+cdSlGV6z81feohMMgrMsxBLBeEx8YBIxJg2OyDe0DeL3YRSxiShBDY/46h
/qdyprHOWDp3g9Wo1xEU9oaF1pPMmeQGZiiIqATWWxdVCbtWNj/5OJWlUCZLUfyd
Sa06NN3xLFDfdrwtqbBcRoAetSPBHt8VtJE2w5vrM7KQaQQthWWMhXpikVCaGY65
kKctNgHDiaCBgwZDL1OdipEHKBl0HLMAI1mSMAijr6yk2wvl4iBR2niAq/PhLBPd
+pTatokpJMh6H0qO8HEelrJWjSugu694uuR8Fwpy52FJttAsrCQ2pC7lk1Z9iP3F
Em2tYVqwsASlCIZEVKvjh1Er4BY1Ye74O/kJOXw5dnrqOF3YBvcsIADHDmGzRUUo
/ltoqasex4YwMxKePWH7BsU9cjO+cr1LDHWy+mLrTiL0X0kVfXeRq7+Jg97MjeED
wUqnsbgkNKsAz4u+IGwG5o8Fuu8pLMQoGEoIAHTz656xqCt7d8aSjXFn7qEuIuxR
YA43s9akUE8SmcwjFJTl
=xIgR
-----END PGP SIGNATURE-----

--Apple-Mail=_2694A017-1EEE-4F68-9975-E62A7DADF56B--


From nobody Tue Feb 14 11:18:34 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7914129603 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:18:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FjW5PWwqlLBe for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:18:30 -0800 (PST)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 288D51297BE for <ietf@ietf.org>; Tue, 14 Feb 2017 11:18:27 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id ABBD9A7A for <ietf@ietf.org>; Tue, 14 Feb 2017 19:18:26 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8lL01uoEDTm for <ietf@ietf.org>; Tue, 14 Feb 2017 13:18:26 -0600 (CST)
Received: from mail-ua0-f199.google.com (mail-ua0-f199.google.com [209.85.217.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 3A1B597E for <ietf@ietf.org>; Tue, 14 Feb 2017 13:18:26 -0600 (CST)
Received: by mail-ua0-f199.google.com with SMTP id a88so100615688uaa.1 for <ietf@ietf.org>; Tue, 14 Feb 2017 11:18:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BWJI2BCQPDmyv/Jyy0TxV3rQ/+V+7x7JtmxMmeapMGo=; b=F0VQbVZoZFmvsPTyrG5raf94LNSICmLzZ1yG72ztyXVLtGcRYRSNabptSdM0Uy2M+G MyxYls6f1XxwCM4XeWUE+uRg2G4pxO/gNpVIkqVNySR6kIsN4aM05B2EOsLuaAdSHBS4 9U3CJJ2q9KPfidzXrGRIj6ichpL/4Z8ZmyiTQ41fJCO6tnNFQ3SjklDyKN+3Dagt/AQk 5m6bSVLrrCYd0CVRP0qrkV15R/S8SJ8YdH03OPSg4VneCzxCg5tR97vBZ5qzpffydYvw daJizzInYBUs/cP+HmrOj8MMNWTgGHP3BBCEvmFxr/RF8vi8jfKcmOzhlS6xG0fmvH5u VwXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BWJI2BCQPDmyv/Jyy0TxV3rQ/+V+7x7JtmxMmeapMGo=; b=Hgmo6p5d9UbhsrhgLBz6NrI2Ok+U/udZw3DeiZDxyw1i/seSUsq8hXgHszW/OiWptC n69Naanj6MDA/3n8l7tTt3hBOV0tt3Wt+j2C2ZviZw9gIABr6Uj4NndYlaq41ZcFPybe eoFkWOjBgKEBdpqFZiEMDbNQfG1rxJqHqOL9OpovdLy1k+JXSyCgXqtth127yW1oVrk/ X7ylrJqtDl7sBlcBlmqy9bXxUgQhvzqc7WosGNKCuhN7tHw0ObMJvh1FVaBTAeg6OOMJ t+HDr0+YRUtvQBbyRWGf9OusLuh6pwsJSOuk4TRQN0BbXN52Zp1KYZWp2otAUoIaHgG9 Y9VA==
X-Gm-Message-State: AMke39lV/+ey9c8OObmkV83JeR9EQHJTpQHgTWwIIlLdagP90KS92Upg6mlkoxqtmFgVOVMPU82JegZqMnYyxSWjvbOHKCLkpzXIte8IjUN0V+uTi00a8GXuaZLFRnab0Q3yhx7/ubm4CVYs2ag=
X-Received: by 10.31.204.197 with SMTP id c188mr15385584vkg.31.1487099905515;  Tue, 14 Feb 2017 11:18:25 -0800 (PST)
X-Received: by 10.31.204.197 with SMTP id c188mr15385574vkg.31.1487099905240;  Tue, 14 Feb 2017 11:18:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Tue, 14 Feb 2017 11:18:24 -0800 (PST)
In-Reply-To: <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es>
From: David Farmer <farmer@umn.edu>
Date: Tue, 14 Feb 2017 13:18:24 -0600
Message-ID: <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Jordi Palet Martinez <jordi.palet@consulintel.es>
Content-Type: multipart/alternative; boundary=001a114dd5d0990a190548826dc5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IH3D1zpwhGyL0DCiGM4-uwLAsow>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:18:32 -0000

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

So I hear you saying something like the following would be appropriate in
your opinion;

However, the Interface ID of all unicast addresses is required to be 64 bit
with the exception of the following; addresses for point-to-point links
[RFC6164], Network-Specific Prefixes used for IPv4/IPv6 Translators
[RFC6052], and addresses that start with the binary value 000.

While this is the less preferred approach as far as I'm concerned, I
believe it resolves the issue I raised.

Thanks.

On Tue, Feb 14, 2017 at 10:07 AM, JORDI PALET MARTINEZ <
jordi.palet@consulintel.es> wrote:

> I understand that, but those are two clear exceptions, no others should b=
e
> =E2=80=9Callowed=E2=80=9D by default.
>
> Keeping the door open is not good in my opinion. Specific exceptions must
> be taken in consideration one by one.
>
> Regards,
> Jordi
>
>
> -----Mensaje original-----
> De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn.ed=
u
> >
> Responder a: <farmer@umn.edu>
> Fecha: martes, 14 de febrero de 2017, 17:03
> Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
> CC: 6man WG <ipv6@ietf.org>, <draft-ietf-6man-rfc4291bis@ietf.org>,
> IETF-Discussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org>
> Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6
> Addressing Architecture) to Internet Standard
>
>     The problem we want it to be 64 bits except when it's not suppose to
> be, such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv6
> translators with /96 Network-Specific Prefix.
>
>     On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ <
> jordi.palet@consulintel.es> wrote:
>
>     Agree, we shouldn=E2=80=99t change that. Must be 64 bits.
>
>     Regards,
>     Jordi
>
>
>     -----Mensaje original-----
>     De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <
> farmer@umn.edu>
>     Responder a: <farmer@umn.edu>
>     Fecha: martes, 14 de febrero de 2017, 16:27
>     Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
>     CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>,
> 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
>     Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP
> Version 6 Addressing Architecture) to Internet Standard
>
>         Actually, in addition to your text there still needs to be a
> recommendation for 64 bit IIDs in all other cases.  64 bit IIDs are(and
> should remain) the norm for IPv6, I do not want to change that.  But the
> current language say IIDs are always 64 bit except when an address begins
> with binary 000, leaving no room for any other exception.  And this is
> plainly incorrect, I provided two clear exceptions that are already
> standardized.  Furthermore, IIDs other than 64 bits are in operational us=
e,
> with manual configuration and DHCPv6.
>         So I'd suggest;
>
>         However, the Interface ID of unicast addresses used for
>         Stateless Address Autoconfiguration [RFC4862] is required
>         to be 64 bits long, in all other cases it is recommended to
>         be 64 bits long.
>
>         The other option is to enumerate all the exceptions, requiring th=
e
> document to be updated every time a new exception is standardized.
>
>         On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>         At an earlier stage I suggested restricting the applicability
>         of the "However..." sentence to SLAAC [RFC4862]. A short way
>         of doing this would be
>
>         However, the Interface ID of unicast addresses used for
>         Stateless Address Autoconfiguration [RFC4862] is required
>         to be 64 bits long.
>
>         Regards
>            Brian
>
>         On 14/02/2017 11:32, David Farmer wrote:
>         > I have concerns with the following text;
>         >
>         >    IPv6 unicast routing is based on prefixes of any valid lengt=
h
> up to
>         >    128 [BCP198].  For example, [RFC6164] standardises 127 bit
> prefixes
>         >    on inter-router point-to-point links. However, the Interface
> ID of
>         >    all unicast addresses, except those that start with the
> binary value
>         >    000, is required to be 64 bits long.  The rationale for the
> 64 bit
>         >    boundary in IPv6 addresses can be found in [RFC7421]
>         >
>         > The third sentence seems to limit exceptions to 64 bit IIDs to
> exclusively
>         > addresses that start with binary vale of 000.  There are at
> least two other
>         > exceptions from standards track RFCs, that should be more clear
> accounted
>         > for in this text.  First is [RFC6164] point-to-point links, as
> mentioned in
>         > the previous sentence.  I think the clear intent of [RFC6164] i=
s
> to allow
>         > one(1) Bit IIDs for point to point-to-point links using any
> Global Unicast
>         > Address, not just those that start with 000.  Second is,
> [RFC6052], which
>         > updates [RFC4921] and seems to allow 32 bit IIDs or /96 prefixe=
s
> for any
>         > Global Unicast Address when used for IPv4/IPv6 translation,
> referred to as
>         > ""Network-Specific Prefix" unique to the organization deploying
> the address
>         > translators," in section 2.2 of [RFC6052].
>         >
>         > Thanks.
>         >
>         > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <
> iesg-secretary@ietf.org> wrote:
>         >
>         >>
>         >> The IESG has received a request from the IPv6 Maintenance WG
> (6man) to
>         >> consider the following document:
>         >> - 'IP Version 6 Addressing Architecture'
>         >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>         >>
>         >> The IESG plans to make a decision in the next few weeks, and
> solicits
>         >> final comments on this action. Please send substantive comment=
s
> to the
>         >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally,
> comments may be
>         >> sent to iesg@ietf.org instead. In either case, please retain
> the
>         >> beginning of the Subject line to allow automated sorting.
>         >>
>         >> Abstract
>         >>
>         >>
>         >>    This specification defines the addressing architecture of
> the IP
>         >>    Version 6 (IPv6) protocol.  The document includes the IPv6
> addressing
>         >>    model, text representations of IPv6 addresses, definition o=
f
> IPv6
>         >>    unicast addresses, anycast addresses, and multicast
> addresses, and an
>         >>    IPv6 node's required addresses.
>         >>
>         >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>         >>    Architecture".
>         >>
>         >>
>         >>
>         >>
>         >> The file can be obtained via
>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>         >>
>         >> IESG discussion can be tracked via
>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
> ballot/
>         >>
>         >>
>         >> No IPR declarations have been submitted directly on this I-D.
>         >>
>         >>
>         >>
>         >>
>         >> ------------------------------------------------------------
> --------
>         >> IETF IPv6 working group mailing list
>         >> ipv6@ietf.org
>         >> Administrative Requests: https://www.ietf.org/mailman/l
> istinfo/ipv6
>         >> ------------------------------------------------------------
> --------
>         >>
>         >
>         >
>         >
>         >
>         >
>         > ------------------------------------------------------------
> --------
>         > IETF IPv6 working group mailing list
>         > ipv6@ietf.org
>         > Administrative Requests: https://www.ietf.org/mailman/l
> istinfo/ipv6
>         > ------------------------------------------------------------
> --------
>         >
>
>
>
>
>
>
>         --
>         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>         David Farmer               Email:farmer@umn.edu <mailto:
> Email%3Afarmer@umn.edu> <mailto:Email%3Afarmer@umn.edu <mailto:
> Email%253Afarmer@umn.edu>>
>         Networking & Telecommunication Services
>         Office of Information Technology
>         University of Minnesota
>         2218 University Ave SE        Phone: 612-626-0815 <tel:
> 612-626-0815>
>         Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:612-812-9952=
>
>         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>
>
>
>
>
>
>
>     **********************************************
>     IPv4 is over
>     Are you ready for the new Internet ?
>     http://www.consulintel.es
>     The IPv6 Company
>
>     This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>
>
>
>
>
>
>
>     --
>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>     David Farmer               Email:farmer@umn.edu <mailto:
> Email%3Afarmer@umn.edu>
>     Networking & Telecommunication Services
>     Office of Information Technology
>     University of Minnesota
>     2218 University Ave SE        Phone: 612-626-0815
>     Minneapolis, MN 55414-3029   Cell: 612-812-9952
>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
>
>
>
>
>
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.consulintel.es
> The IPv6 Company
>
> This electronic message contains information which may be privileged or
> confidential. The information is intended to be for the use of the
> individual(s) named above. If you are not the intended recipient be aware
> that any disclosure, copying, distribution or use of the contents of this
> information, including attached files, is prohibited.
>
>
>
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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

<div dir=3D"ltr">So I hear you saying something like the following would be=
 appropriate in your opinion;<div><br></div><div><span style=3D"font-size:1=
2.8px">However, the Interface ID of all unicast addresses is required to be=
 64 bit with the exception of the following; addresses for point-to-point l=
inks [RFC6164], Network-Specific Prefixes used for IPv4/IPv6 Translators [R=
FC6052], and=C2=A0</span><span style=3D"font-size:12.8px">addresses=C2=A0</=
span><span style=3D"font-size:12.8px">that start with the binary value 000.=
</span><br></div><div><span style=3D"font-size:12.8px"><br></span></div><di=
v><span style=3D"font-size:12.8px">While this is the less preferred approac=
h as far as I&#39;m concerned, I believe it resolves the issue I raised. =
=C2=A0</span></div><div><span style=3D"font-size:12.8px"><br></span></div><=
div><span style=3D"font-size:12.8px">Thanks.</span></div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Tue, Feb 14, 2017 at 10:07 AM, J=
ORDI PALET MARTINEZ <span dir=3D"ltr">&lt;<a href=3D"mailto:jordi.palet@con=
sulintel.es" target=3D"_blank">jordi.palet@consulintel.es</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">I understand that=
, but those are two clear exceptions, no others should be =E2=80=9Callowed=
=E2=80=9D by default.<br>
<br>
Keeping the door open is not good in my opinion. Specific exceptions must b=
e taken in consideration one by one.<br>
<br>
Regards,<br>
Jordi<br>
<br>
<br>
-----Mensaje original-----<br>
De: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blank">iet=
f-bounces@ietf.org</a>&gt; en nombre de David Farmer &lt;<a href=3D"mailto:=
farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;<br>
Responder a: &lt;<a href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer=
@umn.edu</a>&gt;<br>
Fecha: martes, 14 de febrero de 2017, 17:03<br>
Para: Jordi Palet Martinez &lt;<a href=3D"mailto:jordi.palet@consulintel.es=
" target=3D"_blank">jordi.palet@consulintel.es</a>&gt;<br>
CC: 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@iet=
f.org</a>&gt;, &lt;<a href=3D"mailto:draft-ietf-6man-rfc4291bis@ietf.org" t=
arget=3D"_blank">draft-ietf-6man-rfc4291bis@ie<wbr>tf.org</a>&gt;, IETF-Dis=
cussion Discussion &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">i=
etf@ietf.org</a>&gt;, &lt;<a href=3D"mailto:6man-chairs@ietf.org" target=3D=
"_blank">6man-chairs@ietf.org</a>&gt;<br>
Asunto: Re: Last Call: &lt;draft-ietf-6man-rfc4291bis-07<wbr>.txt&gt; (IP V=
ersion 6 Addressing Architecture) to Internet Standard<br>
<br>
=C2=A0 =C2=A0 The problem we want it to be 64 bits except when it&#39;s not=
 suppose to be, such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv=
6 translators with /96 Network-Specific Prefix.<br>
<br>
=C2=A0 =C2=A0 On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ &lt;<a =
href=3D"mailto:jordi.palet@consulintel.es" target=3D"_blank">jordi.palet@co=
nsulintel.es</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 Agree, we shouldn=E2=80=99t change that. Must be 64 bits.<br>
<br>
=C2=A0 =C2=A0 Regards,<br>
=C2=A0 =C2=A0 Jordi<br>
<br>
<br>
=C2=A0 =C2=A0 -----Mensaje original-----<br>
=C2=A0 =C2=A0 De: ietf &lt;<a href=3D"mailto:ietf-bounces@ietf.org" target=
=3D"_blank">ietf-bounces@ietf.org</a>&gt; en nombre de David Farmer &lt;<a =
href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;<br>
=C2=A0 =C2=A0 Responder a: &lt;<a href=3D"mailto:farmer@umn.edu" target=3D"=
_blank">farmer@umn.edu</a>&gt;<br>
=C2=A0 =C2=A0 Fecha: martes, 14 de febrero de 2017, 16:27<br>
=C2=A0 =C2=A0 Para: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpent=
er@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;<br>
=C2=A0 =C2=A0 CC: &lt;<a href=3D"mailto:draft-ietf-6man-rfc4291bis@ietf.org=
" target=3D"_blank">draft-ietf-6man-rfc4291bis@ie<wbr>tf.org</a>&gt;, &lt;<=
a href=3D"mailto:6man-chairs@ietf.org" target=3D"_blank">6man-chairs@ietf.o=
rg</a>&gt;, 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">=
ipv6@ietf.org</a>&gt;, IETF-Discussion Discussion &lt;<a href=3D"mailto:iet=
f@ietf.org" target=3D"_blank">ietf@ietf.org</a>&gt;<br>
=C2=A0 =C2=A0 Asunto: Re: Last Call: &lt;draft-ietf-6man-rfc4291bis-07<wbr>=
.txt&gt; (IP Version 6 Addressing Architecture) to Internet Standard<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Actually, in addition to your text there still =
needs to be a recommendation for 64 bit IIDs in all other cases.=C2=A0 64 b=
it IIDs are(and should remain) the norm for IPv6, I do not want to change t=
hat.=C2=A0 But the current language say IIDs are always 64 bit except when =
an address begins with binary 000, leaving no room for any other exception.=
=C2=A0 And this is plainly incorrect, I provided two clear exceptions that =
are already standardized.=C2=A0 Furthermore, IIDs other than 64 bits are in=
 operational use, with manual configuration and DHCPv6.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 So I&#39;d suggest;<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 However, the Interface ID of unicast addresses =
used for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stateless Address Autoconfiguration [RFC4862] i=
s required<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to be 64 bits long, in all other cases it is re=
commended to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 be 64 bits long.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 The other option is to enumerate all the except=
ions, requiring the document to be updated every time a new exception is st=
andardized.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpen=
ter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">br=
ian.e.carpenter@gmail.com</a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 At an earlier stage I suggested restricting the=
 applicability<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 of the &quot;However...&quot; sentence to SLAAC=
 [RFC4862]. A short way<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 of doing this would be<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 However, the Interface ID of unicast addresses =
used for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stateless Address Autoconfiguration [RFC4862] i=
s required<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 to be 64 bits long.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Brian<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 On 14/02/2017 11:32, David Farmer wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; I have concerns with the following text;<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 IPv6 unicast routing is based=
 on prefixes of any valid length up to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For examp=
le, [RFC6164] standardises 127 bit prefixes<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 on inter-router point-to-poin=
t links. However, the Interface ID of<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 all unicast addresses, except=
 those that start with the binary value<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 000, is required to be 64 bit=
s long.=C2=A0 The rationale for the 64 bit<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;=C2=A0 =C2=A0 boundary in IPv6 addresses ca=
n be found in [RFC7421]<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; The third sentence seems to limit exceptio=
ns to 64 bit IIDs to exclusively<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; addresses that start with binary vale of 0=
00.=C2=A0 There are at least two other<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; exceptions from standards track RFCs, that=
 should be more clear accounted<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; for in this text.=C2=A0 First is [RFC6164]=
 point-to-point links, as mentioned in<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; the previous sentence.=C2=A0 I think the c=
lear intent of [RFC6164] is to allow<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; one(1) Bit IIDs for point to point-to-poin=
t links using any Global Unicast<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Address, not just those that start with 00=
0.=C2=A0 Second is, [RFC6052], which<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; updates [RFC4921] and seems to allow 32 bi=
t IIDs or /96 prefixes for any<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Global Unicast Address when used for IPv4/=
IPv6 translation, referred to as<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; &quot;&quot;Network-Specific Prefix&quot; =
unique to the organization deploying the address<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; translators,&quot; in section 2.2 of [RFC6=
052].<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Thanks.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; On Wed, Feb 1, 2017 at 5:51 PM, The IESG &=
lt;<a href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secret=
ary@ietf.org</a>&gt; wrote:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; The IESG has received a request from t=
he IPv6 Maintenance WG (6man) to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; consider the following document:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; - &#39;IP Version 6 Addressing Archite=
cture&#39;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0&lt;draft-ietf-6man-rfc429=
1bis-0<wbr>7.txt&gt; as Internet Standard<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; The IESG plans to make a decision in t=
he next few weeks, and solicits<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; final comments on this action. Please =
send substantive comments to the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; <a href=3D"mailto:ietf@ietf.org" targe=
t=3D"_blank">ietf@ietf.org</a> mailing lists by 2017-03-01. Exceptionally, =
comments may be<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; sent to <a href=3D"mailto:iesg@ietf.or=
g" target=3D"_blank">iesg@ietf.org</a> instead. In either case, please reta=
in the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; beginning of the Subject line to allow=
 automated sorting.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; Abstract<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 This specification define=
s the addressing architecture of the IP<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 Version 6 (IPv6) protocol=
.=C2=A0 The document includes the IPv6 addressing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 model, text representatio=
ns of IPv6 addresses, definition of IPv6<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 unicast addresses, anycas=
t addresses, and multicast addresses, and an<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 IPv6 node&#39;s required =
addresses.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 This document obsoletes R=
FC 4291, &quot;IP Version 6 Addressing<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;=C2=A0 =C2=A0 Architecture&quot;.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; The file can be obtained via<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; <a href=3D"https://datatracker.ietf.or=
g/doc/draft-ietf-6man-rfc4291bis/" rel=3D"noreferrer" target=3D"_blank">htt=
ps://datatracker.ietf.org/d<wbr>oc/draft-ietf-6man-rfc4291bis/</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; IESG discussion can be tracked via<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; <a href=3D"https://datatracker.ietf.or=
g/doc/draft-ietf-6man-rfc4291bis/ballot/" rel=3D"noreferrer" target=3D"_bla=
nk">https://datatracker.ietf.org/d<wbr>oc/draft-ietf-6man-rfc4291bis/<wbr>b=
allot/</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; No IPR declarations have been submitte=
d directly on this I-D.<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; ------------------------------<wbr>---=
---------------------------<wbr>--------<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; IETF IPv6 working group mailing list<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; <a href=3D"mailto:ipv6@ietf.org" targe=
t=3D"_blank">ipv6@ietf.org</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; Administrative Requests: <a href=3D"ht=
tps://www.ietf.org/mailman/listinfo/ipv6" rel=3D"noreferrer" target=3D"_bla=
nk">https://www.ietf.org/mailman/l<wbr>istinfo/ipv6</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt; ------------------------------<wbr>---=
---------------------------<wbr>--------<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; ------------------------------<wbr>-------=
-----------------------<wbr>--------<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; IETF IPv6 working group mailing list<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; <a href=3D"mailto:ipv6@ietf.org" target=3D=
"_blank">ipv6@ietf.org</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; Administrative Requests: <a href=3D"https:=
//www.ietf.org/mailman/listinfo/ipv6" rel=3D"noreferrer" target=3D"_blank">=
https://www.ietf.org/mailman/l<wbr>istinfo/ipv6</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt; ------------------------------<wbr>-------=
-----------------------<wbr>--------<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 &gt;<br>
<br>
<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 --<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0<a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_bl=
ank">Email:farmer@umn.edu</a> &lt;mailto:<a href=3D"mailto:Email%253Afarmer=
@umn.edu" target=3D"_blank">Email%3Afarmer@umn.edu</a><wbr>&gt; &lt;mailto:=
<a href=3D"mailto:Email%253Afarmer@umn.edu" target=3D"_blank">Email%3Afarme=
r@umn.edu</a> &lt;mailto:<a href=3D"mailto:Email%25253Afarmer@umn.edu" targ=
et=3D"_blank">Email%253Afarmer@umn.e<wbr>du</a>&gt;&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Networking &amp; Telecommunication Services<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Office of Information Technology<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 University of Minnesota<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 Phone: <a href=3D"tel:612-626-0815" value=3D"+16126260815" target=3D"_b=
lank">612-626-0815</a> &lt;tel:<a href=3D"tel:612-626-0815" value=3D"+16126=
260815" target=3D"_blank">612-626-0815</a>&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Minneapolis, MN 55414-3029=C2=A0 =C2=A0Cell: <a=
 href=3D"tel:612-812-9952" value=3D"+16128129952" target=3D"_blank">612-812=
-9952</a> &lt;tel:<a href=3D"tel:612-812-9952" value=3D"+16128129952" targe=
t=3D"_blank">612-812-9952</a>&gt;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 ******************************<wbr>****************<br>
=C2=A0 =C2=A0 IPv4 is over<br>
=C2=A0 =C2=A0 Are you ready for the new Internet ?<br>
=C2=A0 =C2=A0 <a href=3D"http://www.consulintel.es" rel=3D"noreferrer" targ=
et=3D"_blank">http://www.consulintel.es</a><br>
=C2=A0 =C2=A0 The IPv6 Company<br>
<br>
=C2=A0 =C2=A0 This electronic message contains information which may be pri=
vileged or confidential. The information is intended to be for the use of t=
he individual(s) named above. If you are not the intended recipient be awar=
e that any disclosure, copying, distribution or use of the contents of this=
 information, including attached files, is prohibited.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 --<br>
=C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
=C2=A0 =C2=A0 David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0<a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:far=
mer@umn.edu</a> &lt;mailto:<a href=3D"mailto:Email%253Afarmer@umn.edu" targ=
et=3D"_blank">Email%3Afarmer@umn.edu</a><wbr>&gt;<br>
=C2=A0 =C2=A0 Networking &amp; Telecommunication Services<br>
=C2=A0 =C2=A0 Office of Information Technology<br>
=C2=A0 =C2=A0 University of Minnesota<br>
=C2=A0 =C2=A0 2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a h=
ref=3D"tel:612-626-0815" value=3D"+16126260815" target=3D"_blank">612-626-0=
815</a><br>
=C2=A0 =C2=A0 Minneapolis, MN 55414-3029=C2=A0 =C2=A0Cell: <a href=3D"tel:6=
12-812-9952" value=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>
=C2=A0 =C2=A0 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<br>
<br>
<br>
<br>
<br>
<br>
<br>
******************************<wbr>****************<br>
IPv4 is over<br>
Are you ready for the new Internet ?<br>
<a href=3D"http://www.consulintel.es" rel=3D"noreferrer" target=3D"_blank">=
http://www.consulintel.es</a><br>
The IPv6 Company<br>
<br>
This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.<br>
<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"m_-5483544062180123307gmail-m_-4661475874675982537gmail_signature">=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>Dav=
id Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"=
mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><b=
r>Networking &amp; Telecommunication Services<br>Office of Information Tech=
nology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612)%20626-0815" value=3D"+=
16126260815" target=3D"_blank">612-626-0815</a><br>Minneapolis, MN 55414-30=
29=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-9952" value=3D"+16128129952=
" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--001a114dd5d0990a190548826dc5--


From nobody Tue Feb 14 11:46:22 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFB912943B; Tue, 14 Feb 2017 11:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 A5oYeT-FnMMj; Tue, 14 Feb 2017 11:46:16 -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 951521297C6; Tue, 14 Feb 2017 11:46:16 -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 v1EJkFEi011586; Tue, 14 Feb 2017 12:46:16 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EJk7Ts011118 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 12:46:07 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 11:46:06 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 11:46:06 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAAEjdGhAACokzAAEaEMAAAQAsUw
Date: Tue, 14 Feb 2017 19:46:06 +0000
Message-ID: <9ef36e63256448b0b17c91e145ad6fde@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org> <097680c30ae64d74b0c30ffcaeb4c112@XCH15-06-08.nw.nos.boeing.com> <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
In-Reply-To: <6E42D46A-06BC-4C6D-8411-FA969164CD41@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OofzsWNep6vgqh5MHWyXbkZi-CI>
Cc: 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:46:18 -0000

Hi Ole,

> -----Original Message-----
> From: otroan@employees.org [mailto:otroan@employees.org]
> Sent: Tuesday, February 14, 2017 11:17 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: Stewart Bryant <stewart.bryant@gmail.com>; Brian E Carpenter <brian.e=
.carpenter@gmail.com>; gen-art@ietf.org; 6man WG
> <ipv6@ietf.org>; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Fred,
>=20
> >> Yes, but sending at 1280 does not work for IP tunnels. The whole purpo=
se of the minimum MTU was to give space for tunnel
> headers
> >> (1500-1280).
> >
> > But, if non-tunnel links set a 1280 MTU which is perfectly OK with the =
standard then
> > there is no space for headers. Given the issues with classical PMTUD th=
en (plus the
> > non-applicability of RFC4821 for tunnels) the only solution for tunnels=
 is fragmentation.
> > I'll let Joe step in if he wants to.
>=20
> You are correct. "Does not work for IP tunnels without fragmenting the ou=
ter header" is what I should have written.
> Of course it appears IPv6 fragments have a order of magnitude higher drop=
 probability than ICMP PMTUD messages.

Right. Depending on the encapsulation, however, fragmentation might occur a=
s
some mid-layer between the outer and inner IP headers. For example, a UDP
encapsulation that includes its own fragmentation control fields. In that w=
ay,
the network would only see UDP/IP packets - it would not see IPv6 fragments=
.

GUE is an example UDP encapsulation that include its own fragmentation
control fields:

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

> Pick your poison.

As far as RFC 2473 is concerned, you are right. Other encapsulations that
can do the fragmentation at a mid-layer between the inner and outer
IP headers should be OK.

Thanks - Fred

> Best regards,
> Ole



From nobody Tue Feb 14 11:59:25 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF70C129559 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 UdWRsdbBfEzX for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 11:59:17 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 F15581297D0 for <ietf@ietf.org>; Tue, 14 Feb 2017 11:59:16 -0800 (PST)
X-Halon-ID: 0988c81c-f2f0-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Tue, 14 Feb 2017 20:59:04 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>, ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se>
Date: Tue, 14 Feb 2017 20:59:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_YfMSXD4CVZoSq7pT0edRmjs88M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:59:20 -0000

Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:

> Hi -
>
> On 2/14/2017 9:40 AM, Randall Gellens wrote:
>> At 11:01 AM +0100 2/14/17, Gunnar Hellström wrote:
>>
>>>  My proposal for a reworded section 5.4 is:
>>>
>>>  5.4.  Unusual language indications
>>>
>>>  It is possible to specify an unusual indication where the language
>>>  specified may look unexpected for the media type.
>>>
>>>  For such cases the following guidance SHALL be applied for the
>>> humintlang attributes used in these situations.
>>>
>>>  1.    A view of a speaking person in the video stream SHALL, when it
>>> has relevance for speech perception, be indicated by a Language-Tag
>>> for spoken/written language with the "Zxxx" script subtag to indicate
>>> that the contents is not written.
>>>
>>>  2.    Text captions included in the video stream SHALL be indicated
>>> by a Language-Tag for spoken/written language.
>>>
>>>  3.    Any approximate representation of sign language or
>>> fingerspelling in the text media stream SHALL be indicated by a
>>> Language-Tag for a sign language in text media.
>>>
>>>  4.    When sign language related audio from a person using sign
>>> language is of importance for language communication, this SHALL be
>>> indicated by a Language-Tag for a sign language in audio media.
>>
>> [RG] As I said, I think we should avoid specifying this until we have
>> deployment experience.
> ...
>
> From a process perspective, it's far easier to remove constraints
> as a specification advances than it is to add them.
I agree. It is often better to specify normatively as far as you can 
imagine, so that interoperability and good functionality is achieved. 
Stopping halfway and have MAY in the specifications creates uncertainty 
and less useful specifications.

Furthermore, in this case we succeeded to discuss and sort out the 
interpretation of the unusual combinations.
I am very glad that we sorted out the difference between 1 and 2, and 
they are both real-life cases.

3 is not at all common, but I have seen products claiming to work for 
real-time communication with sign representation in text. So it is good 
to have it settled.

4. Is a bit more far fetched and may cause some questioning if there are 
real cases, and where the line should be drawn between indicating a 
spoken languge in the audio stream and indicating a sign language in the 
audio stream.
As I wiew it now, this combination will be very rare, but it is anyway 
good to be specific and normative about its coding.

Gunnar

>
> Randy
>

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Tue Feb 14 11:59:57 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 403E31297D4; Tue, 14 Feb 2017 11:59:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZwl6iKMcnAy; Tue, 14 Feb 2017 11:59:49 -0800 (PST)
Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::243]) (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 DCE7C129420; Tue, 14 Feb 2017 11:59:43 -0800 (PST)
Received: by mail-oi0-x243.google.com with SMTP id x84so3645304oix.2; Tue, 14 Feb 2017 11:59:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=6Frf95Jc1E4K0s5Vg6+OVBUibpAZHAWj1jw7fo3Bc84=; b=Uu5QDQ1WD6Uu4nDLFUlKxDqqlGRBux/BL51tTSPO/s4IOmOE01xKAuRzDCtW/RlN6E BE90oAn3LNKpAX6+vKLLw1WmcpuNoYn3AaGnjR/PhEQExh9acbhU/mkR9CpJjgcV163n EhAKYy8sYIl8ev3oxu7m3MEutsvxnmmKWmgFr8OEF4qfgNGUuuw/+lVuJQu+1Qc6SjVw UdFsHQrqoZdL6tqY2biCzIA43jBATvcjGIPWEk4JySiGrsmsC96ufADhtzemRD7pF8+M ODgKnNc2V+/oVFjQSR9kNhJ9KzD5jpwUJ2Cu6pfoGSLQJQgfyEzPmq1iamDQYzX3lxqD ZdtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=6Frf95Jc1E4K0s5Vg6+OVBUibpAZHAWj1jw7fo3Bc84=; b=YlB6L+9Ewcr0sMCGm4rKFCgNPjohVg5v5pQtPQu+yJGdd3eMtlJUF57ihE9Y9UeH36 QyINQSb8Sv9XCUgAqLUIjoFRuGV3UYNRyutLfNTvkDG3TObb57FUsyjcYStAD9R5ja7i VZ5BlCyCr3NctmI1iooXtSZmqlCOtGJkAMvqz6l8X01pg6Vl5NX6Im9+dxBWfJbS5I7i fMzqxCzJymKqO78MRJWnF0+giDscjDLxECu85b1KZT0T99m++u7pXOTM/F2E+L2qcqvt Ax8J2HqvgodIDxNekwH5OenWw0hqYXKA3SkCQ3pZ2IC9IUqlRc36cLz72f8twt7cHTMW MDkw==
X-Gm-Message-State: AMke39np/5sK3dNWLmBIo4A2X6oTyaOglyU0ff59M0tKaqhyzNy/AypSdb0MNiuGFcUMMA==
X-Received: by 10.84.229.76 with SMTP id d12mr37386526pln.21.1487102383040; Tue, 14 Feb 2017 11:59:43 -0800 (PST)
Received: from [192.168.178.21] ([118.148.78.74]) by smtp.gmail.com with ESMTPSA id w16sm2878517pgc.15.2017.02.14.11.59.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 11:59:42 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>, Jordi Palet Martinez <jordi.palet@consulintel.es>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <cd45eabb-6dd4-1ffc-ff92-aaa395f1fabf@gmail.com>
Date: Wed, 15 Feb 2017 08:59:41 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MaUjgr2w3FgiC428tc5o5GiXC-I>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 19:59:51 -0000

I certainly agree with that approach too.

In answer to Alexandre: you are correct that this value is a parameter fo=
r
RFC4862. But for reasons we have discussed often, it needs to be fixed
by the architecture.

Regards
   Brian

On 15/02/2017 08:18, David Farmer wrote:
> So I hear you saying something like the following would be appropriate =
in
> your opinion;
>=20
> However, the Interface ID of all unicast addresses is required to be 64=
 bit
> with the exception of the following; addresses for point-to-point links=

> [RFC6164], Network-Specific Prefixes used for IPv4/IPv6 Translators
> [RFC6052], and addresses that start with the binary value 000.
>=20
> While this is the less preferred approach as far as I'm concerned, I
> believe it resolves the issue I raised.
>=20
> Thanks.
>=20
> On Tue, Feb 14, 2017 at 10:07 AM, JORDI PALET MARTINEZ <
> jordi.palet@consulintel.es> wrote:
>=20
>> I understand that, but those are two clear exceptions, no others shoul=
d be
>> =E2=80=9Callowed=E2=80=9D by default.
>>
>> Keeping the door open is not good in my opinion. Specific exceptions m=
ust
>> be taken in consideration one by one.
>>
>> Regards,
>> Jordi
>>
>>
>> -----Mensaje original-----
>> De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <farmer@umn=
=2Eedu
>>>
>> Responder a: <farmer@umn.edu>
>> Fecha: martes, 14 de febrero de 2017, 17:03
>> Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
>> CC: 6man WG <ipv6@ietf.org>, <draft-ietf-6man-rfc4291bis@ietf.org>,
>> IETF-Discussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org>
>> Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version=
 6
>> Addressing Architecture) to Internet Standard
>>
>>     The problem we want it to be 64 bits except when it's not suppose =
to
>> be, such as RFC6164 for point-to-point and RFC6052 for IPv4/IPv6
>> translators with /96 Network-Specific Prefix.
>>
>>     On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ <
>> jordi.palet@consulintel.es> wrote:
>>
>>     Agree, we shouldn=E2=80=99t change that. Must be 64 bits.
>>
>>     Regards,
>>     Jordi
>>
>>
>>     -----Mensaje original-----
>>     De: ietf <ietf-bounces@ietf.org> en nombre de David Farmer <
>> farmer@umn.edu>
>>     Responder a: <farmer@umn.edu>
>>     Fecha: martes, 14 de febrero de 2017, 16:27
>>     Para: Brian E Carpenter <brian.e.carpenter@gmail.com>
>>     CC: <draft-ietf-6man-rfc4291bis@ietf.org>, <6man-chairs@ietf.org>,=

>> 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
>>     Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP
>> Version 6 Addressing Architecture) to Internet Standard
>>
>>         Actually, in addition to your text there still needs to be a
>> recommendation for 64 bit IIDs in all other cases.  64 bit IIDs are(an=
d
>> should remain) the norm for IPv6, I do not want to change that.  But t=
he
>> current language say IIDs are always 64 bit except when an address beg=
ins
>> with binary 000, leaving no room for any other exception.  And this is=

>> plainly incorrect, I provided two clear exceptions that are already
>> standardized.  Furthermore, IIDs other than 64 bits are in operational=
 use,
>> with manual configuration and DHCPv6.
>>         So I'd suggest;
>>
>>         However, the Interface ID of unicast addresses used for
>>         Stateless Address Autoconfiguration [RFC4862] is required
>>         to be 64 bits long, in all other cases it is recommended to
>>         be 64 bits long.
>>
>>         The other option is to enumerate all the exceptions, requiring=
 the
>> document to be updated every time a new exception is standardized.
>>
>>         On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter <
>> brian.e.carpenter@gmail.com> wrote:
>>
>>         At an earlier stage I suggested restricting the applicability
>>         of the "However..." sentence to SLAAC [RFC4862]. A short way
>>         of doing this would be
>>
>>         However, the Interface ID of unicast addresses used for
>>         Stateless Address Autoconfiguration [RFC4862] is required
>>         to be 64 bits long.
>>
>>         Regards
>>            Brian
>>
>>         On 14/02/2017 11:32, David Farmer wrote:
>>         > I have concerns with the following text;
>>         >
>>         >    IPv6 unicast routing is based on prefixes of any valid le=
ngth
>> up to
>>         >    128 [BCP198].  For example, [RFC6164] standardises 127 bi=
t
>> prefixes
>>         >    on inter-router point-to-point links. However, the Interf=
ace
>> ID of
>>         >    all unicast addresses, except those that start with the
>> binary value
>>         >    000, is required to be 64 bits long.  The rationale for t=
he
>> 64 bit
>>         >    boundary in IPv6 addresses can be found in [RFC7421]
>>         >
>>         > The third sentence seems to limit exceptions to 64 bit IIDs =
to
>> exclusively
>>         > addresses that start with binary vale of 000.  There are at
>> least two other
>>         > exceptions from standards track RFCs, that should be more cl=
ear
>> accounted
>>         > for in this text.  First is [RFC6164] point-to-point links, =
as
>> mentioned in
>>         > the previous sentence.  I think the clear intent of [RFC6164=
] is
>> to allow
>>         > one(1) Bit IIDs for point to point-to-point links using any
>> Global Unicast
>>         > Address, not just those that start with 000.  Second is,
>> [RFC6052], which
>>         > updates [RFC4921] and seems to allow 32 bit IIDs or /96 pref=
ixes
>> for any
>>         > Global Unicast Address when used for IPv4/IPv6 translation,
>> referred to as
>>         > ""Network-Specific Prefix" unique to the organization deploy=
ing
>> the address
>>         > translators," in section 2.2 of [RFC6052].
>>         >
>>         > Thanks.
>>         >
>>         > On Wed, Feb 1, 2017 at 5:51 PM, The IESG <
>> iesg-secretary@ietf.org> wrote:
>>         >
>>         >>
>>         >> The IESG has received a request from the IPv6 Maintenance W=
G
>> (6man) to
>>         >> consider the following document:
>>         >> - 'IP Version 6 Addressing Architecture'
>>         >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>>         >>
>>         >> The IESG plans to make a decision in the next few weeks, an=
d
>> solicits
>>         >> final comments on this action. Please send substantive comm=
ents
>> to the
>>         >> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally,
>> comments may be
>>         >> sent to iesg@ietf.org instead. In either case, please retai=
n
>> the
>>         >> beginning of the Subject line to allow automated sorting.
>>         >>
>>         >> Abstract
>>         >>
>>         >>
>>         >>    This specification defines the addressing architecture o=
f
>> the IP
>>         >>    Version 6 (IPv6) protocol.  The document includes the IP=
v6
>> addressing
>>         >>    model, text representations of IPv6 addresses, definitio=
n of
>> IPv6
>>         >>    unicast addresses, anycast addresses, and multicast
>> addresses, and an
>>         >>    IPv6 node's required addresses.
>>         >>
>>         >>    This document obsoletes RFC 4291, "IP Version 6 Addressi=
ng
>>         >>    Architecture".
>>         >>
>>         >>
>>         >>
>>         >>
>>         >> The file can be obtained via
>>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis=
/
>>         >>
>>         >> IESG discussion can be tracked via
>>         >> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis=
/
>> ballot/
>>         >>
>>         >>
>>         >> No IPR declarations have been submitted directly on this I-=
D.
>>         >>
>>         >>
>>         >>
>>         >>
>>         >> -----------------------------------------------------------=
-
>> --------
>>         >> IETF IPv6 working group mailing list
>>         >> ipv6@ietf.org
>>         >> Administrative Requests: https://www.ietf.org/mailman/l
>> istinfo/ipv6
>>         >> -----------------------------------------------------------=
-
>> --------
>>         >>
>>         >
>>         >
>>         >
>>         >
>>         >
>>         > ------------------------------------------------------------=

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

>> --------
>>         >
>>
>>
>>
>>
>>
>>
>>         --
>>         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>>         David Farmer               Email:farmer@umn.edu <mailto:
>> Email%3Afarmer@umn.edu> <mailto:Email%3Afarmer@umn.edu <mailto:
>> Email%253Afarmer@umn.edu>>
>>         Networking & Telecommunication Services
>>         Office of Information Technology
>>         University of Minnesota
>>         2218 University Ave SE        Phone: 612-626-0815 <tel:
>> 612-626-0815>
>>         Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:612-812-9=
952>
>>         =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
>>
>>
>>
>>
>>
>>
>>
>>     **********************************************
>>     IPv4 is over
>>     Are you ready for the new Internet ?
>>     http://www.consulintel.es
>>     The IPv6 Company
>>
>>     This electronic message contains information which may be privileg=
ed
>> or confidential. The information is intended to be for the use of the
>> individual(s) named above. If you are not the intended recipient be aw=
are
>> that any disclosure, copying, distribution or use of the contents of t=
his
>> information, including attached files, is prohibited.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>     --
>>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>>     David Farmer               Email:farmer@umn.edu <mailto:
>> Email%3Afarmer@umn.edu>
>>     Networking & Telecommunication Services
>>     Office of Information Technology
>>     University of Minnesota
>>     2218 University Ave SE        Phone: 612-626-0815
>>     Minneapolis, MN 55414-3029   Cell: 612-812-9952
>>     =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=

>>
>>
>>
>>
>>
>>
>> **********************************************
>> IPv4 is over
>> Are you ready for the new Internet ?
>> http://www.consulintel.es
>> The IPv6 Company
>>
>> This electronic message contains information which may be privileged o=
r
>> confidential. The information is intended to be for the use of the
>> individual(s) named above. If you are not the intended recipient be aw=
are
>> that any disclosure, copying, distribution or use of the contents of t=
his
>> information, including attached files, is prohibited.
>>
>>
>>
>>
>=20
>=20


From nobody Tue Feb 14 12:01:45 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AECA129847 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 12:01: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 eLe24wRtljS9 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 12:01:42 -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 6A97E1297E7 for <ietf@ietf.org>; Tue, 14 Feb 2017 12:01:32 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 0A26082B01; Tue, 14 Feb 2017 21:01:28 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com>
Date: Tue, 14 Feb 2017 17:00:56 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UdEGabe8yzomQqUxeaL_tfrHkX8>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 20:01:44 -0000

On 02/14/2017 04:12 PM, otroan@employees.org wrote:
> Joel,
> 
>> Ole, it is true that we write in English, and there is always room for
>> "interpretation", sometimes reasoanble room, sometimes not.
>>
>> But in this case we have a demonstrated difference in how people
>> understand the existing text.  When we have such a demonstrated
>> difference, we have an obligation to address it.
> 
> This particular issue has caused no interoperability issue,

May I ask what's the data that support this statement?

You certainly have no way of knowing this, or whether interoperability
issues may arise in the future.

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 14 12:37:33 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 470E0129841; Tue, 14 Feb 2017 12:37:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Second Call for Nominations: ART AD Vacancy
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148710465225.10022.2206479317678451583.idtracker@ietfa.amsl.com>
Date: Tue, 14 Feb 2017 12:37:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WguJPYwncwWafWSgUCNZ4t4uL8c>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 20:37:32 -0000

All -

A reminder that we are still actively seeking candidates -

We have had two individuals accept their nominations already and feedback
is open: https://datatracker.ietf.org/nomcom/2016/feedback/ You can also
send also send feedback to: nomcom-2016@ietf.org We depend on your input
and look forward to hearing from you.

The calendar for our process can be found here:
https://datatracker.ietf.org/nomcom/2016/

Details on the nomination process:

The 2016-17 Nominating Committee (NomCom) is seeking nominations from now
until February 17, 2017 for the position of ART AD. This appoint will fill
the 1 year vacancy created by Alissa Cooper's resignation as she moves to
the IETF Chair seat.

https://datatracker.ietf.org/nomcom/2016/

Nominations may be made by selecting the Nominate link at the top of the
NomCom 2016 home page, or by visiting the following URL:

https://datatracker.ietf.org/nomcom/2016/nominate/

  {Note that nominations made using the web tool require an ietf.org
   datatracker account. You can create a datatracker ietf.org account
   if you don't have one already by visiting the following URL:
   https://datatracker.ietf.org/accounts/create/ }

If you are unable to use the web form, nominations may instead be made by
email to nomcom-16@ietf.org. If using email, please include the word
"Nominate" in the Subject and indicate in the email who is being nominated
and their email address (to confirm acceptance of the nomination).

If you are nominating someone other than yourself, please tell us if we  
may tell the nominee that you were the one who made the nomination.

Self-nomination is welcome!

Willing nominees will be asked to fill out a questionnaire for the ART AD
position. The questionnaires will be available February 8, 2017 and have a
submission deadline of February 17, 2017.

Thanks -

Lucy Lynch
NomCom Chair 2016-2017


From nobody Tue Feb 14 12:40:01 2017
Return-Path: <prvs=211126882=addison@lab126.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32AA12985D; Tue, 14 Feb 2017 12:39:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 OzeGsLoScjzk; Tue, 14 Feb 2017 12:39:58 -0800 (PST)
Received: from smtp-fw-33001.amazon.com (smtp-fw-33001.amazon.com [207.171.190.10]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EB7B1296B2; Tue, 14 Feb 2017 12:39:58 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,162,1484006400"; d="scan'208";a="654281352"
Received: from sea19-co-svc-lb5-vlan3.sea.amazon.com (HELO email-inbound-relay-60015.pdx1.amazon.com) ([10.47.22.166]) by smtp-border-fw-out-33001.sea14.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Feb 2017 20:39:56 +0000
Received: from EX13MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan3.pdx.amazon.com [10.236.137.198]) by email-inbound-relay-60015.pdx1.amazon.com (8.14.7/8.14.7) with ESMTP id v1EKdsix011955 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 14 Feb 2017 20:39:55 GMT
Received: from EX13D08UWB003.ant.amazon.com (10.43.161.186) by EX13MTAUWB001.ant.amazon.com (10.43.161.249) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 14 Feb 2017 20:39:55 +0000
Received: from EX13D08UWB002.ant.amazon.com (10.43.161.168) by EX13D08UWB003.ant.amazon.com (10.43.161.186) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 14 Feb 2017 20:39:55 +0000
Received: from EX13D08UWB002.ant.amazon.com ([10.43.161.168]) by EX13D08UWB002.ant.amazon.com ([10.43.161.168]) with mapi id 15.00.1104.000; Tue, 14 Feb 2017 20:39:55 +0000
From: "Phillips, Addison" <addison@lab126.com>
To: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>, "Randy Presuhn" <randy_presuhn@alumni.stanford.edu>, "ietf@ietf.org" <ietf@ietf.org>, "slim@ietf.org" <slim@ietf.org>
Subject: RE: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
Thread-Topic: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
Thread-Index: AQHShk5MdWFzLzaSL0G26SF4TAiur6FoFQsAgAAxCoCAAIAWgIAAJxpAgAAIijA=
Date: Tue, 14 Feb 2017 20:39:55 +0000
Message-ID: <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se>
In-Reply-To: <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.160.56]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: Bulk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yGTpl-YGE7PswAWE8YRRyLCnWTQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 20:40:00 -0000

I have some allergy to the SHALL language: there is no way to automatically=
 determine conformance. Many language tags represent nonsensical values, du=
e to the nature of language tag composition. Content providers need to use =
care in selecting the tags that they use and this section is merely pointin=
g out good guidance for tag selection, albeit in a heavy-handed way. BCP47 =
RFC 5646 Section 4.1 [1] already provides most of this guidance and a refer=
ence to that source might be useful here, if only because that document req=
uires it:

<quote>
   Standards, protocols, and applications that reference this document
   normatively but apply different rules to the ones given in this
   section MUST specify how language tag selection varies from the
   guidelines given here.
</quote>

I would suggest reducing the SHALL items to SHOULD.

I'm not sure what #2 really means. Shouldn't text captions be indicated by =
the written language rather than the spoken language? And I'm not sure what=
 "spoken/written language" means.

Regards,

Addison

Addison Phillips
Principal SDE, I18N Architect (Amazon)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.

[1] https://tools.ietf.org/html/bcp47#section-4.1

-----Original Message-----
From: SLIM [mailto:slim-bounces@ietf.org] On Behalf Of Gunnar Hellstr=F6m
Sent: Tuesday, February 14, 2017 11:59 AM
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>; ietf@ietf.org; slim@=
ietf.org
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-la=
nguage (Section 5.4)

Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:

> Hi -
>
> On 2/14/2017 9:40 AM, Randall Gellens wrote:
>> At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>
>>>  My proposal for a reworded section 5.4 is:
>>>
>>>  5.4.  Unusual language indications
>>>
>>>  It is possible to specify an unusual indication where the language =20
>>> specified may look unexpected for the media type.
>>>
>>>  For such cases the following guidance SHALL be applied for the=20
>>> humintlang attributes used in these situations.
>>>
>>>  1.    A view of a speaking person in the video stream SHALL, when it
>>> has relevance for speech perception, be indicated by a Language-Tag=20
>>> for spoken/written language with the "Zxxx" script subtag to=20
>>> indicate that the contents is not written.
>>>
>>>  2.    Text captions included in the video stream SHALL be indicated
>>> by a Language-Tag for spoken/written language.
>>>
>>>  3.    Any approximate representation of sign language or
>>> fingerspelling in the text media stream SHALL be indicated by a=20
>>> Language-Tag for a sign language in text media.
>>>
>>>  4.    When sign language related audio from a person using sign
>>> language is of importance for language communication, this SHALL be=20
>>> indicated by a Language-Tag for a sign language in audio media.
>>
>> [RG] As I said, I think we should avoid specifying this until we have=20
>> deployment experience.
> ...
>
> From a process perspective, it's far easier to remove constraints as a=20
> specification advances than it is to add them.
I agree. It is often better to specify normatively as far as you can imagin=
e, so that interoperability and good functionality is achieved.=20
Stopping halfway and have MAY in the specifications creates uncertainty and=
 less useful specifications.

Furthermore, in this case we succeeded to discuss and sort out the interpre=
tation of the unusual combinations.
I am very glad that we sorted out the difference between 1 and 2, and they =
are both real-life cases.

3 is not at all common, but I have seen products claiming to work for real-=
time communication with sign representation in text. So it is good to have =
it settled.

4. Is a bit more far fetched and may cause some questioning if there are re=
al cases, and where the line should be drawn between indicating a spoken la=
nguge in the audio stream and indicating a sign language in the audio strea=
m.
As I wiew it now, this combination will be very rare, but it is anyway good=
 to be specific and normative about its coding.

Gunnar

>
> Randy
>

--
-----------------------------------------
Gunnar Hellstr=F6m
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288

_______________________________________________
SLIM mailing list
SLIM@ietf.org
https://www.ietf.org/mailman/listinfo/slim


From nobody Tue Feb 14 14:01:59 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B427B129863 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 14:01:57 -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 autolearn_force=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 QNDy1W0v8eUZ for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 14:01:56 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D52A129421 for <ietf@ietf.org>; Tue, 14 Feb 2017 14:01:56 -0800 (PST)
Received: (qmail 2652 invoked from network); 14 Feb 2017 22:01:54 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 14 Feb 2017 22:01:54 -0000
Date: 14 Feb 2017 22:01:32 -0000
Message-ID: <20170214220132.15450.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: To "lose the argument in the WG"
In-Reply-To: <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JKuB3uUXo8V02ZXEeWVORnXvYbw>
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 22:01:58 -0000

In article <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> you write:
>While, yes, there will be times that the new folk see something new or 
>better, that's not the usual occurrence.  The usual occurrence is that 
>folk who are experienced with the topic and are tired from the extended 
>effort have to rehash their work and defend it to folk who have not done 
>their homework.

Sometimes that's true, but sometimes the situation arises to which
John Klensin alluded: a WG does something that crosses topics, and
what they decide makes sense from the viewpoint of topic A but not
from topic B.  I've certainly seen that happen a few times in the
recent past.

R's,
John


From nobody Tue Feb 14 14:35:15 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E951297C3; Tue, 14 Feb 2017 14:35:08 -0800 (PST)
X-Quarantine-ID: <VywZs4CehUDL>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 VywZs4CehUDL; Tue, 14 Feb 2017 14:35:07 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7603A12944F; Tue, 14 Feb 2017 14:35:07 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 14:27:08 -0800
Mime-Version: 1.0
Message-Id: <p06240607d4c9359416e2@[99.111.97.136]>
In-Reply-To: <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 14:35:02 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Bernard Aboba <bernard.aboba@gmail.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7lRBcFfUvQZYcZSb6jnp9K6l59I>
Cc: slim@ietf.org, ietf@ietf.org, Doug Ewell <doug@ewellic.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 22:35:09 -0000

At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:

>  My proposal for a reworded section 5.4 is:
>
>  5.4.  Unusual language indications
>
>  It is possible to specify an unusual indication where the language
>  specified may look unexpected for the media type.
>
>  For such cases the following guidance SHALL be=20
> applied for the humintlang attributes used in=20
> these situations.
>
>  1.	A view of a speaking person in the video=20
> stream SHALL, when it has relevance for speech=20
> perception, be indicated by a Language-Tag for=20
> spoken/written language with the "Zxxx" script=20
> subtag to indicate that the contents is not=20
> written.

What does "relevance for speech perception" mean=20
in the spec, and how is it determined?

>
>  2.	Text captions included in the video=20
> stream SHALL be indicated by a Language-Tag for=20
> spoken/written language.

Is this commonly supported such that it makes=20
sense to include in the current draft?  Perhaps=20
it should wait for an update that might include=20
similar functionality such as text captions for=20
audio streams.

>
>  3.	Any approximate representation of sign=20
> language or fingerspelling in the text media=20
> stream SHALL be indicated by a Language-Tag for=20
> a sign language in text media.

Same comment as for (2).

>
>  4.	When sign language related audio from a=20
> person using sign language is of importance for=20
> language communication, this SHALL be indicated=20
> by a Language-Tag for a sign language in audio=20
> media.

Same comment as for (1).


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
They say that 90 per cent of TV is junk.  But 90 per cent
of *everything* is junk.
      --Gene Roddenberry, interview in TV Guide, Apr. 27, 1974
      (quoting Sturgeon's Revelation: "Ninety percent of
      everything is crap.")


From nobody Tue Feb 14 14:39:55 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9F71293E3; Tue, 14 Feb 2017 14:39:53 -0800 (PST)
X-Quarantine-ID: <1Dt_4kyLjWE7>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 1Dt_4kyLjWE7; Tue, 14 Feb 2017 14:39:52 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id AA9B91293D9; Tue, 14 Feb 2017 14:39:52 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 14:31:55 -0800
Mime-Version: 1.0
Message-Id: <p06240608d4c936a2565a@[99.111.97.136]>
In-Reply-To: <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 14:39:50 -0800
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MK6l6HadkLZgLtI_MVEc5crjP8w>
Cc: slim@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 22:39:53 -0000

At 10:05 AM -0800 2/14/17, Randy Presuhn wrote:

>  Hi -
>
>  On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>  At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>
>>>   My proposal for a reworded section 5.4 is:
>>>
>>>   5.4.  Unusual language indications
>>>
>>>   It is possible to specify an unusual indication where the language
>>>   specified may look unexpected for the media type.
>>>
>>>   For such cases the following guidance SHALL be applied for the
>>>  humintlang attributes used in these situations.
>>>
>>>   1.    A view of a speaking person in the video stream SHALL, when it
>>>  has relevance for speech perception, be indicated by a Language-Tag
>>>  for spoken/written language with the "Zxxx" script subtag to indicate
>>>  that the contents is not written.
>>>
>>>   2.    Text captions included in the video stream SHALL be indicated
>>>  by a Language-Tag for spoken/written language.
>>>
>>>   3.    Any approximate representation of sign language or
>>>  fingerspelling in the text media stream SHALL be indicated by a
>>>  Language-Tag for a sign language in text media.
>>>
>>>   4.    When sign language related audio from a person using sign
>>>  language is of importance for language communication, this SHALL be
>>>  indicated by a Language-Tag for a sign language in audio media.
>>
>>  [RG] As I said, I think we should avoid specifying this until we have
>>  deployment experience.
>  ...
>
>  From a process perspective, it's far easier to remove constraints
>  as a specification advances than it is to add them.

Which supports the text I proposed on Monday:

    Specifying a non-signed language tag for a video media stream, or a
    signed language tag for a non-video media stream, is not defined.  An
    offer with such a combination SHOULD NOT be created.  If such an
    offer is received, the receiver MAY ignore the language specified.

This proposed text has a mild constraint to not=20
include such combinations.  By using "SHOULD NOT"=20
and "MAY" we allow cooperating implementations to=20
use it without imposing semantic implications now=20
that might not be what we need in the future.=20
After we have some experience, we can either use=20
the existing attributes and language tags to=20
impose meanings as Gunnar suggests, or we might=20
find we need a different mechanism that has more=20
functionality.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The solution to a problem changes the nature of the problem.


From nobody Tue Feb 14 14:44:48 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C873D12943C; Tue, 14 Feb 2017 14:44:43 -0800 (PST)
X-Quarantine-ID: <NzDusL1yPUYV>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 NzDusL1yPUYV; Tue, 14 Feb 2017 14:44:41 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id C65AC12940D; Tue, 14 Feb 2017 14:44:41 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 14:36:44 -0800
Mime-Version: 1.0
Message-Id: <p06240609d4c937dc9ff8@[99.111.97.136]>
In-Reply-To: <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 14:43:34 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K9amxa1TfG15BpM9N-zETZnhCJs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 22:44:44 -0000

At 8:59 PM +0100 2/14/17, Gunnar Hellstr=F6m wrote:

>  Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>
>>  Hi -
>>
>>  On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>  At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>>
>>>>   My proposal for a reworded section 5.4 is:
>>>>
>>>>   5.4.  Unusual language indications
>>>>
>>>>   It is possible to specify an unusual indication where the language
>>>>   specified may look unexpected for the media type.
>>>>
>>>>   For such cases the following guidance SHALL be applied for the
>>>>  humintlang attributes used in these situations.
>>>>
>>>>   1.    A view of a speaking person in the video stream SHALL, when it
>>>>  has relevance for speech perception, be indicated by a Language-Tag
>>>>  for spoken/written language with the "Zxxx" script subtag to indicate
>>>>  that the contents is not written.
>>>>
>>>>   2.    Text captions included in the video stream SHALL be indicated
>>>>  by a Language-Tag for spoken/written language.
>>>>
>>>>   3.    Any approximate representation of sign language or
>>>>  fingerspelling in the text media stream SHALL be indicated by a
>>>>  Language-Tag for a sign language in text media.
>>>>
>>>>   4.    When sign language related audio from a person using sign
>>>>  language is of importance for language communication, this SHALL be
>>>>  indicated by a Language-Tag for a sign language in audio media.
>>>
>>>  [RG] As I said, I think we should avoid specifying this until we have
>>>  deployment experience.
>>  ...
>>
>>  From a process perspective, it's far easier to remove constraints
>>  as a specification advances than it is to add them.
>  I agree. It is often better to specify=20
> normatively as far as you can imagine, so that=20
> interoperability and good functionality is=20
> achieved. Stopping halfway and have MAY in the=20
> specifications creates uncertainty and less=20
> useful specifications.

My reading of what Randy says is the opposite of=20
Gunnar's.  In my reading, Randy points out that=20
is it easier to remove the SHOULD NOT in the=20
future then it is to change the meaning of the=20
combinations or switch to a different mechanism.

In my experience, it's better to specify only=20
what we know we need and what we know we=20
understand.  Speculative specifications "as far=20
as you can imagine" more often lead to=20
interoperability problems, unnecessary=20
complexity, limitations on what's needed in the=20
future, and divergent implementations.

>
>  Furthermore, in this case we succeeded to=20
> discuss and sort out the interpretation of the=20
> unusual combinations.
>  I am very glad that we sorted out the=20
> difference between 1 and 2, and they are both=20
> real-life cases.
>
>  3 is not at all common, but I have seen=20
> products claiming to work for real-time=20
> communication with sign representation in text.=20
> So it is good to have it settled.
>
>  4. Is a bit more far fetched and may cause some=20
> questioning if there are real cases, and where=20
> the line should be drawn between indicating a=20
> spoken languge in the audio stream and=20
> indicating a sign language in the audio stream.
>  As I wiew it now, this combination will be very=20
> rare, but it is anyway good to be specific and=20
> normative about its coding.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
A day for firm decisions!!!!!  Or is it?


From nobody Tue Feb 14 15:01:08 2017
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA7712943C; Tue, 14 Feb 2017 15:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 7xI5hLsRBuYW; Tue, 14 Feb 2017 15:00:56 -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 19231129407; Tue, 14 Feb 2017 15:00:56 -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 v1EN0t9e037093; Tue, 14 Feb 2017 16:00:55 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1EN0mhG037037 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Tue, 14 Feb 2017 16:00:48 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 14 Feb 2017 15:00:47 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1263.000; Tue, 14 Feb 2017 15:00:47 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Topic: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Thread-Index: AQHSg01qd1t1l5P4r0CAXezaoK6tiaFijiOA///QkXCABnBjgP//3WSwgACNdoD//3ylEAARiaQAAAQYGSA=
Date: Tue, 14 Feb 2017 23:00:47 +0000
Message-ID: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
In-Reply-To: <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GH8FZdZ1KJj1l5rkM5YjKZMCc5c>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:00:58 -0000

Hi Stewart,

> *If*  you care about packet loss

I can say that, for air traffic communications at least, we do care very
much about packet loss.

> then your only option is to probe the path with with
> synthetic data that exactly mimics the live data

Yes, that is exactly correct - so, the probing must be on a per
(session,destination) basis and not just per-destination.

> or not to probe at all and live with the 1280

That is the case for tunnels for sure, but many tunneling specs have
been published with an "optimistic" outlook assuming that the
network can support as much as 1500 minus the length of the=20
encapsulation headers. Unless there is operational assurance of
some size X>1280, however, tunnels have to use fragmentation to
guarantee that - at a minimum - packets up to 1280 will get through.

> As I said 1280 is pretty close to 1496 which is all most networks
> will give you in practice.

Still, I wish for the day that we may eventually see larger path MTUs.
It seems that the only way for sources to safely discover them
however is to employ per-session RFC4821.

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

> -----Original Message-----
> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> Sent: Tuesday, February 14, 2017 8:45 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Stewart Bryant <stewart.=
bryant@gmail.com>; Brian E Carpenter
> <brian.e.carpenter@gmail.com>; gen-art@ietf.org
> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.org
> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
>=20
> Fred
> *If*  you care about packet loss, then your only option is to probe the
> path with with
> synthetic data that exactly mimics the live data, or not to probe at all
> and live
> with the 1280. As I said 1280 is pretty close to 1496 which is all most
> networks
> will give you in practice.
>=20
> When I think about the people asking for fast re-route to minimise
> packet loss, it seems
> very strange to deliberately induce loss to try to stretch the MTU by 15%=
.
>=20
> - Stewart
>=20
>=20
> On 14/02/2017 16:25, Templin, Fred L wrote:
> > Hi Stewart,
> >
> >> -----Original Message-----
> >> From: Stewart Bryant [mailto:stewart.bryant@gmail.com]
> >> Sent: Tuesday, February 14, 2017 8:13 AM
> >> To: Templin, Fred L <Fred.L.Templin@boeing.com>; Brian E Carpenter <br=
ian.e.carpenter@gmail.com>; Stewart Bryant
> >> <stewart@g3ysx.org.uk>; gen-art@ietf.org
> >> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@ietf.=
org
> >> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>
> >>
> >>
> >> On 14/02/2017 15:50, Templin, Fred L wrote:
> >>>> As to you first point remember that the convergence process disrupts=
 the
> >>>> traffic flow as it does so, and that this will repeat every 10 mins =
as
> >>>> it tries to re-optimise.
> >>> Yes, you are right. So, even in the case of RFC1981bis it might not b=
e a
> >>> good idea to store discovered MTUs in the network layer when there
> >>> is ECMP in the path. (Which could be any time at all.)
> >> Yes, I think if you really care about disruption due to packet loss yo=
ur
> >> best bet is
> >> to go with the minimum supported MTU.
> >>
> >> Forwarding performance is not a issue these days, and core link are ov=
er
> >> provisioned
> >> so you have to wonder how important the efficiency gain is in practice=
.
> >> The efficiency
> >> gain produced by this protocol in most networks (1276 vs 1496) is only
> >> about 15% anyway.
> > So, that would leave us with RFC4821 plus per {session,destination}
> > probing instead of just per-destination probing. Or, just stick with th=
e
> > IPv6 minMTU (1280)?
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> >>> You briefly mentioned the authorship in your earlier post. As you wel=
l
> >>> know, the corporate affiliation of two of the authors no longer exist=
s.
> >> My concern was that some authors cannot take part in Auth48 due to not
> >> providing
> >> active email addresses.
> >>
> >> - Stewart
> >>
> >>> Thanks - Fred
> >>> fred.l.templin@boeing.com
> >>>
> >>>> - Stewart
> >>>>
> >>>>
> >>>> On 10/02/2017 15:38, Templin, Fred L wrote:
> >>>>> Hi, about ECMP I think RFC1981bis should be OK even if ECMP is used=
 in the
> >>>>> network as long as ICMP PTBs are not blocked. RFC1981bis will event=
ually
> >>>>> converge to the minimum MTU of all paths in the multipath, and so i=
t is
> >>>>> still OK to store the MTU in the network layer where it would be sh=
ared
> >>>>> by all flows.
> >>>>>
> >>>>> ECMP does present challenges for RFC4821, however. If a first trans=
port
> >>>>> session discovers a large MTU and shares it with a second transport
> >>>>> session, the second session may take a very different path where th=
ere
> >>>>> is a smaller MTU and encounter a black hole. IMHO, it might be a go=
od
> >>>>> idea to file an erratum to RFC4821 explaining how ECMP might cause
> >>>>> problems if discovered MTUs are shared between sessions.
> >>>>>
> >>>>> Thanks - Fred
> >>>>> fred.l.templin@boeing.com
> >>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Stewart Bry=
ant
> >>>>>> Sent: Friday, February 10, 2017 2:21 AM
> >>>>>> To: Brian E Carpenter <brian.e.carpenter@gmail.com>; Stewart Bryan=
t <stewart@g3ysx.org.uk>; gen-art@ietf.org
> >>>>>> Cc: ipv6@ietf.org; ietf@ietf.org; draft-ietf-6man-rfc1981bis.all@i=
etf.org
> >>>>>> Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> On 10/02/2017 03:25, Brian E Carpenter wrote:
> >>>>>>> Stewart,
> >>>>>>>
> >>>>>>> On 10/02/2017 04:19, Stewart Bryant wrote:
> >>>>>>> ...
> >>>>>>>> I wonder if we would best serve both our future and our heritage
> >>>>>>>> if we declared RFC1981 as historic, and either left the idea the=
re,
> >>>>>>>> or declared it as historic and wrote a new text from a clean sta=
rt?
> >>>>>>> I don't see that. It's a stable, widely deployed, interoperable
> >>>>>>> mechanism. That is rather orthogonal to the issue that has been r=
aised,
> >>>>>>> which is that faulty ICMPv6 filtering blocks it on many, many pat=
hs
> >>>>>>> across the Internet.
> >>>>>> I will not debate whether it is faulty or not, but it seems that i=
n
> >>>>>> practice the
> >>>>>> Internet breaks the mechanism. However it breaks it is a way that =
seems
> >>>>>> disruptive to some user traffic. The document is really guidance
> >>>>>> one how hosts might use  ICMP for optimization, and arguable need
> >>>>>> not be a standard at all.
> >>>>>>
> >>>>>> My remark about heritage is that this vintage draft is very much a
> >>>>>> product of
> >>>>>> its time, and really needs modernizing, and after modernizing ough=
t to
> >>>>>> look quite different, and thus maybe we should employ a procedure
> >>>>>> other than a simple replacement.
> >>>>>>
> >>>>>>
> >>>>>>> ...
> >>>>>>>> It is concerning that the draft does not talk in any detail abou=
t
> >>>>>>>> how modern ECMP works, i.e. using the five tuple, and noting tha=
t
> >>>>>>>> the PMTU may be different depending on the transport layer port
> >>>>>>>> numbers.
> >>>>>>> Has this problem been analysed for, say, IPv4? And does the real =
world
> >>>>>>> contain ECMP setups with different MTUs on different paths?
> >>>>>> I don't know if anyone has looked. Since the mechanism is
> >>>>>> self-correcting albeit
> >>>>>> with some disruption to user traffic it looks to the application a=
nd the
> >>>>>> application
> >>>>>> user, just like the Internet not working for a few moments.
> >>>>>>
> >>>>>> In a well managed SP network there should not be, but neither shou=
ld there
> >>>>>> be asymmetric path costs, but there are. The less well manage priv=
ate
> >>>>>> networks are less well managed.
> >>>>>>
> >>>>>>
> >>>>>>>> Given that a very large fraction of packets will traverse an MPL=
S
> >>>>>>>> network at some point, I am surprised that there is no text talk=
ing
> >>>>>>>> about the importance of providing support for this feature in th=
e
> >>>>>>>> MPLS domain. RFC3988 talks to this point, but is only experiment=
al.
> >>>>>>> I don't understand. How does the fact that there might be some MP=
LS
> >>>>>>> segments along the path affect end-to-end PMTUD?
> >>>>>> The point that RFC3988 makes is that MPLS looks like a single hop =
to IP
> >>>>>> and the
> >>>>>> PE has to fragment or has to reply with an ICMP error message to s=
upport
> >>>>>> PMTUD. MPLS has ICMP extensions, but I don't know if they integrat=
e to
> >>>>>> result
> >>>>>> in the right response at the end node.
> >>>>>>
> >>>>>> My point is that the draft is silent on the subject, and perhaps i=
t
> >>>>>> should not be.
> >>>>>>
> >>>>>> However your question make me ask a further question. The draft is=
 also
> >>>>>> silent
> >>>>>> on NATs. Is there any advice needed for people designing and confi=
guring
> >>>>>> NATs?
> >>>>>>
> >>>>>>>> =3D=3D=3D=3D=3D=3D
> >>>>>>>>
> >>>>>>>>        If flows [I-D.ietf-6man-rfc2460bis] are in use, an implem=
entation
> >>>>>>>>        could use the flow id as the local representation of a pa=
th. Packets
> >>>>>>>>        sent to a particular destination but belonging to differe=
nt flows may
> >>>>>>>>        use different paths, with the choice of path depending on=
 the flow
> >>>>>>>>        id.  This approach will result in the use of optimally si=
zed packets
> >>>>>>>>        on a per-flow basis, providing finer granularity than PMT=
U values
> >>>>>>>>        maintained on a per-destination basis.
> >>>>>>>>
> >>>>>>>> SB> How widely is flow-id supported in networks? I thought that =
the
> >>>>>>>> SB> current position was that it was unreliable as an ECMP indic=
ator
> >>>>>>>> SB> and thus routers tended to glean information from the packet=
 themselves.
> >>>>>>> This is future-proofing. Agreed, usage today is limited.
> >>>>>>>
> >>>>>>> (But it would be better to call it the Flow Label for consistency=
 with other
> >>>>>>> recent RFCs.)
> >>>>>> Well the question is whether it is simply limited today, or broken=
 today
> >>>>>> in a manner that
> >>>>>> is irrecoverable? I don't know, but I do know that the mainstream =
ECMP
> >>>>>> approach
> >>>>>> is the five-tuple. There is something akin to the flow label being
> >>>>>> deployed in MPLS. However
> >>>>>> what distinguishes the MPLS Entropy Label is that it is inserted (=
and
> >>>>>> removed) by the
> >>>>>> service provider and is therefore trusted by the service provider.
> >>>>>>
> >>>>>>> I think your other comments are all valuable.
> >>>>>> Thank you.
> >>>>>>
> >>>>>> Stewart
> >>>>>>
> >>>>>> ------------------------------------------------------------------=
--
> >>>>>> IETF IPv6 working group mailing list
> >>>>>> ipv6@ietf.org
> >>>>>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv=
6
> >>>>>> ------------------------------------------------------------------=
--
> >
>=20



From nobody Tue Feb 14 15:12:38 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A2261296EE for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GE3wrDecq1nu for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:34 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE89A129407 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:12:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487113954; x=1518649954; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=N/mj9RhnkDVWbeVPSCvezaimkmxqyZmq6h4Y6+eBf7o=; b=rAsxBrvx3GA6PuM9HxD0U06bJ2jfabJcORAqBabexxx++5y58dASBGpY YrMGPwcTeJFMP3mFQd0sw6IIF7CQYOWPUqlQLZaNbTjcdRsTOCO+OTuzs RnWF1SbI+3eK8Vf2FUk71uT/0TXThUowgOYLzATlM3dAhj2ZKJvc3/yQf U=;
X-IronPort-AV: E=Sophos;i="5.35,163,1484035200"; d="scan'208";a="358262163"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 14 Feb 2017 15:12:34 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8439"; a="1313690643"
Received: from unknown (HELO [10.64.121.67]) ([10.64.121.67]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Feb 2017 15:12:33 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: dcrocker@bbiw.net
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 15:01:31 -0800
Message-ID: <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
In-Reply-To: <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hLbMTFvAMvI2PfzlHidZzdBRoCE>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:12:36 -0000

On 14 Feb 2017, at 9:05, Dave Crocker wrote:

> The IETF's formal process document on standards:
>
>    The Internet Standards Process -- Revision 3
>    https://www.ietf.org/rfc/rfc2026.txt
>
> says nothing about Last Call.

Well, of course, except for defining it in section 14:

    Last-Call - A public comment period used to gage the level of
       consensus about the reasonableness of a proposed standards 
action.

> So the formal IETF specification for the role of Last Call is in:
>
>      IETF Working Group Guidelines and Procedures
>      https://tools.ietf.org/html/rfc2418
>
>
>>    This Last Call will announce the intention of
>>    the IESG to consider the document, and it will solicit final 
>> comments
>>    from the IETF within a period of two weeks.  It is important to 
>> note
>>    that a Last-Call is intended as a brief, final check with the
>>    Internet community, to make sure that no important concerns have 
>> been
>>    missed or misunderstood. The Last-Call should not serve as a more
>>    general, in-depth review.

Indeed. If Last Call results in an issue that requires a more general, 
in-depth review, I think the presumption of that text is that it's time 
to send it back to the WG.

> What folks are doing is spontaneously changing the role of this step, 
> ignoring the considerable costs and detriments, while relying on a 
> theory of benefit that is very, very, very rarely actually 
> demonstrated.

I think you've conflated two things: Yes, Last Call should serve as a 
brief final check, not to have a long re-hashed technical discussion. 
But that doesn't mean the outcome of that brief final check is always 
brief and final: When Last Call identifies an issue that was missed or 
mis-evaluated by the WG (perhaps due to JCK's observation about WGs that 
remain homogeneous and insulated), considerable cost and detriment 
should be expected, and is probably appropriate. We have all seen 
efforts that have gone completely off the rails, perhaps due to bad 
management choices, and it is a sign of pathology if that's only noticed 
at Last Call time. Yes, it should probably have been handled during the 
WG process or by interim appeals, but if Last Call is where it's finally 
dealt with, deal with it we must.

Someone described it in private email to me this way: Last Call 
shouldn't be used to argue for a choice where the only consequence is 
"flavor"; it should only be used when the WG has made a choice this is 
"jumping-off-the-cliff". I agree with that in general (allowing that 
people's judgement of how close to the cliff one is might differ), and 
it's the responsibility of everyone to keep their comments to things in 
the latter category.

My main complaint is that people are treating this as a game, with 
points that are "won" or "lost". Telling people that they "lost" or that 
"it's just sour grapes" is obnoxious and has no place in the discussion. 
If someone is abusing the process by bringing up previously 
well-considered topics, of course the person running the Last Call has 
to shut that down. I can even tolerate the occasional random participant 
saying, "Pete, you know this issue was discussed at length, and you 
didn't even bother to fairly say why you think the WG came to the wrong 
conclusion, so this is really just rehashing." Challenging folks to come 
up with why this is not just a "flavor preference" is reasonable: Where 
is the cliff? But just dismissing them with, "Sorry, you were ruled a 
loser" is not how this is supposed to go.

(Speaking for myself: It appears to me that the 2460bis discussion did 
identify a point that is appropriate for the larger community to weigh 
in on. On the other hand, I have yet to be convinced that the major 
point brought up on the SLIM is other than a "flavor preference". In 
neither case should anyone be yelling "sour grapes". That's impugning 
motives and simply ad hominem.)

> To Ted's point, indulging folk who 'did not have time' to participate 
> earlier is frankly abusive of all those who did.

Yeah, I don't find Ted's point at all convincing either. On the other 
hand, if the WG didn't seek out required expertise and someone does 
notice a showstopper, that's not abusive. The WG screwed up.

(I don't think Dave and I centrally disagree on this.)

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Feb 14 15:12:44 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA79129407 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.021
X-Spam-Level: 
X-Spam-Status: No, score=-7.021 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGxgJBYvNY5H for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:12:36 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5410129454 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:12:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487113956; x=1518649956; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version; bh=3NwP9wS1HIX2igbYRlDnQeyc+qRkUT3QxQRgBauXLRs=; b=CH24hJnKPscLvsQF6fJyQiQr9VvBeyagAEiQMsU4TXkMQIwkoxdX666P +kdpQy/gvpQARkv3SHQ/7BJY6FkTZSE8ddNWTbIENtE1qk9jVGKrFboeO KZ8cL7Bsa7o/MeYlRvI6XnXy/++j3BGHXau+lcWJNlEEY18h0ZimNYr/R I=;
X-IronPort-AV: E=Sophos;i="5.35,163,1484035200";  d="scan'208,217";a="358262169"
Received: from unknown (HELO Ironmsg03-L.qualcomm.com) ([10.53.140.110]) by wolverine02.qualcomm.com with ESMTP; 14 Feb 2017 15:12:36 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8439"; a="1313690670"
Received: from unknown (HELO [10.64.121.67]) ([10.64.121.67]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Feb 2017 15:12:36 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "Mark Andrews" <marka@isc.org>
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 15:12:04 -0800
Message-ID: <2E079756-5944-4EF5-A82C-E983B9E8F237@qti.qualcomm.com>
In-Reply-To: <20170214060156.73B32639AEDF@rock.dv.isc.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_A009120F-ADFE-49CB-9EC9-C58EAFC1E7A2_="
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1Qa4kjGLb17YzOc_7g7OjukqsAs>
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:12:38 -0000

--=_MailMate_A009120F-ADFE-49CB-9EC9-C58EAFC1E7A2_=
Content-Type: text/plain; format=flowed; markup=markdown

On 13 Feb 2017, at 22:01, Mark Andrews wrote:

> I gave up trying to convince behave that the DNS64 DNSSEC processing
> was insane.  [...]
>
> I also gave up trying to get 5.9. "Always Set the CD Bit on Queries"
> removed from the draft for RFC 6840.  [...]
>
> Should I have raise these again at IETF last call?

I would hope that you would have appealed to the chair at the time of 
the chair declaring the document ready for Last Call, and if that failed 
appealed to the AD. And it should have gone to Last Call with a note in 
the shepherd writeup indicating that a participant identified what he 
thought were two essential objections, and the reasoning for why the WG 
still felt that the outcome was reasonable. If that all happened, then 
no, you shouldn't bring it up at Last Call, except perhaps to identify 
the issue to others with expertise in the area who weren't part of the 
discussion and who might be able to better explain why these were 
"WG-running-off-the-cliff" issues and not 
"reasonable-engineering-tradeoffs". But you had better say *that*, not 
simply rehash the issue. Last Call should be about "something went wrong 
in the judgement of consensus", not "I prefer a different outcome".

Now, if Last Call was the first time that you noticed the issue, that 
would suck, but then it is reasonable to bring it up.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478
--=_MailMate_A009120F-ADFE-49CB-9EC9-C58EAFC1E7A2_=
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">On 13 Feb 2017, at 22:01, Mark Andrews wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">I gave up trying to convince behave that the DNS64 DNSSEC=
 processing<br>
was insane.  [...]</p>

<p dir=3D"auto">I also gave up trying to get 5.9. "Always Set the CD Bit =
on Queries"<br>
removed from the draft for RFC 6840.  [...]</p>

<p dir=3D"auto">Should I have raise these again at IETF last call?</p>
</blockquote>

<p dir=3D"auto">I would hope that you would have appealed to the chair at=
 the time of the chair declaring the document ready for Last Call, and if=
 that failed appealed to the AD. And it should have gone to Last Call wit=
h a note in the shepherd writeup indicating that a participant identified=
 what he thought were two essential objections, and the reasoning for why=
 the WG still felt that the outcome was reasonable. If that all happened,=
 then no, you shouldn't bring it up at Last Call, except perhaps to ident=
ify the issue to others with expertise in the area who weren't part of th=
e discussion and who might be able to better explain why these were "WG-r=
unning-off-the-cliff" issues and not "reasonable-engineering-tradeoffs". =
But you had better say <em>that</em>, not simply rehash the issue. Last C=
all should be about "something went wrong in the judgement of consensus",=
 not "I prefer a different outcome".</p>

<p dir=3D"auto">Now, if Last Call was the first time that you noticed the=
 issue, that would suck, but then it is reasonable to bring it up.</p>

<p dir=3D"auto">pr<br>
-- <br>
Pete Resnick <a href=3D"http://www.qualcomm.com/%7Epresnick/" style=3D"co=
lor:#3983C4">http://www.qualcomm.com/~presnick/</a><br>
Qualcomm Technologies, Inc. - +1 (858)651-4478</p>
</div>
</div>
</body>
</html>

--=_MailMate_A009120F-ADFE-49CB-9EC9-C58EAFC1E7A2_=--


From nobody Tue Feb 14 15:18:43 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CE9129766 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:18:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G15KRctZ_Z8i for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:18:39 -0800 (PST)
Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::243]) (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 234D51296D4 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:18:39 -0800 (PST)
Received: by mail-io0-x243.google.com with SMTP id m98so10532832iod.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:18:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=SxOkS35g+26wXfQTbNb3jYj24S01YOEs5JcUJiO6nQU=; b=W6gQ/eNLcAIq9ZAAu/dUG1xxnX/dYwUyiLk3OVCbQ2ih5+kIC5I+GDaCsFenKrsaf4 MKlNQF1wVdJL+AxRJL4oBg4dEPI2NM3sbHwOykCcj0wMQHKqjBaJ5bhl7x4/VQujh4KV SXw4qo81v1oEd5oMdwfDwrMC7TJoF5mWPoNUfXmONERlAAqwBxmTXymFePPiLJiWGpoX audE+dDECOWxspmA10zwCfU3ac3w4SKs1i8BIoGGR97jzZqgouVj+wU2ZHTzbwjZO1Rn 4gYX6wrMJCc9zUt68IBXPMX3f34b87NqGFpr6ms7wC6bToYaE6uIsuPVqqfv2oGFXo2m FClw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=SxOkS35g+26wXfQTbNb3jYj24S01YOEs5JcUJiO6nQU=; b=f18dd/x46goC2uahJCTce29U6HrSmiErGcZbJU7zrunDNi6p8ndeUegwLKho0bklXN DJexjyfPg62NOWhAUaMNR660UB3yQz3k0n4Cn2ZpEyLXwDo5JQLnYNDT1J2U8b8oB2RY mwnWMuZESTdQ+qyg4zj2poUhlJd4c/uxZWS1CrBNY+ZBD/9AqcmUp9LxbMmSRtwnbXjt OiKx3zdn609Jv1NMMupJlkV02M1/J2sxwvxqzbjaiiUeE27JxRrP8V15lOQsHFznLMic vOeN0etS5mNIRWLdjOz2fZVG1OvhK+M0pVumNcVSL4lbOq8OVF+6yqAy4Y2m9b66IJJH +98Q==
X-Gm-Message-State: AMke39mvMUGp8OIfZLvHnJ/f8Z6Qk1wbITNz18Zv/7934boWs9DfvZ9J9AYKYpx+KZ0kXA==
X-Received: by 10.98.72.216 with SMTP id q85mr34747992pfi.75.1487114318485; Tue, 14 Feb 2017 15:18:38 -0800 (PST)
Received: from [192.168.178.21] ([118.148.78.74]) by smtp.gmail.com with ESMTPSA id p129sm3128620pfp.118.2017.02.14.15.18.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 15:18:37 -0800 (PST)
Subject: Re: To "lose the argument in the WG"
To: dcrocker@bbiw.net, Ted Lemon <mellon@fugue.com>, Yoav Nir <ynir.ietf@gmail.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com>
Date: Wed, 15 Feb 2017 12:18:37 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zjk_q2sGea7LZaFNBxtGhH3x4mo>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:18:41 -0000

On 15/02/2017 06:05, Dave Crocker wrote:
...
>       IETF Working Group Guidelines and Procedures
>       https://tools.ietf.org/html/rfc2418
> 
>>    This Last Call will announce the intention of
>>    the IESG to consider the document, and it will solicit final comments
>>    from the IETF within a period of two weeks.  It is important to note
>>    that a Last-Call is intended as a brief, final check with the
>>    Internet community, to make sure that no important concerns have been
>>    missed or misunderstood. The Last-Call should not serve as a more
>>    general, in-depth review.
> 
> (I should note that that text dates back to the original version of the 
> document that Erik Huizer and I wrote, in RFC 1871, in 1994.)
> 
> 
> What folks are doing is spontaneously changing the role of this step, 
> ignoring the considerable costs and detriments, while relying on a 
> theory of benefit that is very, very, very rarely actually demonstrated.

Two points on this:

1. A claim that a choice made by the WG is not only harmful to the
protocol under review but *also* harmful to the Internet as a whole
would, I hope, always be legitimate under "no important concerns
have been missed" during IETF Last Call. That's certainly the basis
of an issue that I raised recently.

2. As a Gen-ART reviewer I've often seen drafts at IETF LC that
really *need* a general, in-depth review. As a matter of fact, as
a document editor, I just received such a review yesterday (whether
needed or not is not for me to say). So I'd say that that phrase in
RFC2418 takes a very optimistic view of quality control by WGs.

    Brian


From nobody Tue Feb 14 15:19:03 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35793129976 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:19:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06W-4wQvgp05 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:19:00 -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 7E05E129766 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:19:00 -0800 (PST)
Received: by mail-qk0-x230.google.com with SMTP id 11so136897954qkl.3 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:19:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FteD8LD78ht2qJa/b7EEasGRXaeemDvM92xbbb2H38Q=; b=x38C5CFUYL0sAcze92zXQ2x2zwo4S7YHLl8kUYVhXlK4dKYLpoBqZc+SXB+HPhy7KV 2seEK3rwE06t0hf/lJW/ggvEXGgnGdhXIMwbO8J9c95d7j0Og6TSt4Da98zx4lNVGz9w hsFzcufU8+WryDbmBFVo4g3Kxi8jQSYGqn9Ot8u9HplZdVR8AEjJfCE9dhVqYrO0/42l EzMS4o+j/6rkefJviO4C9Fr4Hl+RhwkH/yqKAtMPnskbKbw+9OM+7bdoopA/Zxq36BQY c4cEqgNsKohxGMVRnX0PWokaqo4O84M6KyUKbmWseQogqvsr1EtyLGDcVqqVP1ohk84N dCSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FteD8LD78ht2qJa/b7EEasGRXaeemDvM92xbbb2H38Q=; b=UbTEkzlNHFyLb8iV6shqif1NSaQxskNMEUM+uZb5vyE2ahz+rteE+vgxwL/nUifWjg Rt3Bb63ODnAI4N4pSGbbyxAmSHIUGxvY+KtQoV1jTmEHFGvDvWmLct/tugDFSXA15YJC XXf0bubNS8Qif0ojb0P0Bch7GX3U/3irdLybpv7UHAs6tzzuDgylOXx/bJAiVYnAWq5K ebpkQYVjTznT7P4HwFWV/F/CZFR0RqDG9sqf7k/p0i3w+boWdwpULQofssaNbbJtjb2i yprOvCZSo/6hj1yxmCdKSHb+I0m8VmV/SSMiw7/uWBdPXU8RRWigoMQ+Vr9Jk7XfqgY6 zNjA==
X-Gm-Message-State: AMke39mz+dz/FV+RQbVSBebEUQQSuCkcntnmW5UTLVUySsHEBgln6fGuORzokOH0JHL48Q==
X-Received: by 10.55.42.207 with SMTP id q76mr17627525qkq.35.1487114339638; Tue, 14 Feb 2017 15:18:59 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id z8sm1207630qkz.42.2017.02.14.15.18.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 15:18:58 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <2F13B46F-AFE5-4E49-9724-3737781B4883@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_59F068D9-BB41-4279-A3E7-57DA20F0FA4F"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 18:18:57 -0500
In-Reply-To: <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EaTCwLCsnRcT7jEFe-9BWp7DIoQ>
Cc: Dave CROCKER <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:19:02 -0000

--Apple-Mail=_59F068D9-BB41-4279-A3E7-57DA20F0FA4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 14, 2017, at 6:01 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:
>> To Ted's point, indulging folk who 'did not have time' to participate =
earlier is frankly abusive of all those who did.
>=20
> Yeah, I don't find Ted's point at all convincing either. On the other =
hand, if the WG didn't seek out required expertise and someone does =
notice a showstopper, that's not abusive. The WG screwed up.

Wow.   You must have a lot more free time than I do, Pete.   My =
experience is that there are lots of things that get worked on in =
working groups that I don't even have time to be aware of, and 99% of =
the time the fact that I wasn't aware of them is not a problem at all.   =
But 1% of the time it is, and last call is (hopefully) where I become =
aware of that and say something.   Are you really calling this abusive?


--Apple-Mail=_59F068D9-BB41-4279-A3E7-57DA20F0FA4F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 14, 2017, at 6:01 PM, Pete Resnick &lt;<a =
href=3D"mailto:presnick@qti.qualcomm.com" =
class=3D"">presnick@qti.qualcomm.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D""><blockquote =
type=3D"cite" style=3D"font-family: Menlo-Regular; font-size: 14px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; orphans: auto; text-align: start; text-indent: =
0px; text-transform: none; white-space: normal; widows: auto; =
word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">To Ted's point, indulging =
folk who 'did not have time' to participate earlier is frankly abusive =
of all those who did.<br class=3D""></blockquote><br style=3D"font-family:=
 Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">Yeah, I don't find Ted's point =
at all convincing either. On the other hand, if the WG didn't seek out =
required expertise and someone does notice a showstopper, that's not =
abusive. The WG screwed up.</span></div></div></blockquote></div><br =
class=3D""><div class=3D"">Wow. &nbsp; You must have a lot more free =
time than I do, Pete. &nbsp; My experience is that there are lots of =
things that get worked on in working groups that I don't even have time =
to be aware of, and 99% of the time the fact that I wasn't aware of them =
is not a problem at all. &nbsp; But 1% of the time it is, and last call =
is (hopefully) where I become aware of that and say something. &nbsp; =
Are you really calling this abusive?</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_59F068D9-BB41-4279-A3E7-57DA20F0FA4F--


From nobody Tue Feb 14 15:35:02 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A2A129977; Tue, 14 Feb 2017 15:34: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tThZqLDYgpXJ; Tue, 14 Feb 2017 15:34:55 -0800 (PST)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (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 12BE51289B0; Tue, 14 Feb 2017 15:34:55 -0800 (PST)
Received: by mail-it0-x242.google.com with SMTP id r141so7949195ita.1; Tue, 14 Feb 2017 15:34:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BsDxUdwSZ4IbhcIDWw+T4my2mrFK/sH4nNJX0F9KIcM=; b=KNP38UVhTQW+iSA5o+4Z68e/mm0Jtx1458KeKrd8O2QbMjnn4Oy8a7SwfXL9Fg+mvn JONdfc7yqHEvRUmhZscVMB9zlFwgR1ICtvjrMHJ2DD6MqZKsky5ZVEWDKnzou/aLh3Zx IkqMo/UvVRK+h7vyVrAbc9MME9TGYJWeYXgQzlexn4+m6cNFKqVAtx/e9D96SrORpBrj p2zJomfJISZ2B3DmjZjFxANxWi/J7BWAPRUCcgw3CtC6sP26UDisbxSzalrGtOgmvO7L H+RjvHWvFoP6fSTEVGBvbgbFHfmUays21r/Qcq7+JLLWUkN9OtW0xLK8UAsowqHwqpXB KvmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=BsDxUdwSZ4IbhcIDWw+T4my2mrFK/sH4nNJX0F9KIcM=; b=reLnRH1QNhtfz7yS/T7vQnP/GiuFYbDKYTYaEyPyrlvmswXTB6mDd7dKPeo1HyJyop bJqQ4SgcJ0peFIsVL/BWMvjRM61+Bq9yGhEFW1/zESXfQqwOKWe1OxtmRPioGKXIyVI/ MmyMFx0uTT2YtB/4rYL2uye3XQg4lix8mUle1BJMrSCqMj9nxUrmwj+985OSdyAnpNiL nQNtLqxNBudN+LEnh2C5v2HiDZ1WLEhj2TIBieS+snP1RBxMyWkCcQ7/RULXtHZnKxyU mCT19EEg3l6hHlqnvHJ4N3EZzdK6FY2BfskWu+zCrjFGMpKUuRzPOoSnH33Q7DwNcQ3j 15ow==
X-Gm-Message-State: AMke39l69Y3K+8vMHQj9ycKeuSavd9LIGJvZBQLIuo0rjonkQWd34MBSD8eQ6bVsQYsymA==
X-Received: by 10.99.199.69 with SMTP id v5mr35559369pgg.90.1487115294259; Tue, 14 Feb 2017 15:34:54 -0800 (PST)
Received: from [192.168.178.21] ([118.148.78.74]) by smtp.gmail.com with ESMTPSA id t22sm3165060pfa.114.2017.02.14.15.34.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 15:34:53 -0800 (PST)
Subject: Re: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: David Mozes <davidm@mellanox.com>, Tal Mizrahi <talmi@marvell.com>, Mark Smith <markzzzsmith@gmail.com>
References: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com> <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com> <eeaa0cc49e104cc68c5b2ae23c44e355@IL-EXCH01.marvell.com> <HE1PR0501MB21381B97CAB3707DB7D20F31B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7415f49b-0669-4291-99e2-49d21a3c0299@gmail.com>
Date: Wed, 15 Feb 2017 12:34:52 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <HE1PR0501MB21381B97CAB3707DB7D20F31B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TEguO37jzVOPB2yBITXuaH9Liy0>
Cc: "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, "6man@ietf.org" <6man@ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:34:57 -0000

David, Tal,

Note that if a HbH option is tagged "1 - Option Data may change en-route"=

it is excluded from AH anyway. But if you insert an option, or extend
its length while modifying it, you will break all forms of PMTUD.

Regards
   Brian

On 15/02/2017 03:27, David Mozes wrote:
> Hi * ,
> I am also supporting the insertion of in-band telemetry like INT along =
with the  actual data packet .
> It is for sure a valid use case for the modern networking including dat=
a center.=20
> There are several proposals how to embedded telemetry information   som=
e of them are with in nvo3 tannling protocols=20
> (Vxlan-GPE,Geneve) Spring and other  .=20
> I think that ipv6 hbh is the "cleanest"  way to add such info.
> 	1) I don't see any and advantages on the other  proposals (NVO3 ,SPRIN=
G) over IPV6 hbh.
> 	2))As far as security In the IPsec community, AH is pretty much consid=
ered deprecated, a failed experiment.They  are  prefer to use   ESP for a=
uthentication as well.
> =20
> The postal system and the letter is very nice e example  . I will treat=
 the adding ipv6-hbh info as stamps on the envelops ,since we are not tou=
ching  the data gram itself just the envelope
>=20
> Thx
> David
> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Tal Mizrahi
> Sent: Tuesday, February 14, 2017 3:37 PM
> To: Mark Smith <markzzzsmith@gmail.com>
> Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org; 6man@ietf.org; IETF Disc=
ussion list <ietf@ietf.org>; 6man-chairs@ietf.org
> Subject: RE: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (=
Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
>=20
> Hi Mark,
>=20
> I certainly agree that hop-by-hop insertion/modification introduces pot=
ential security vulnerabilities.
> Therefore, as I pointed out below, I would recommend to tackle this by =
defining something along the lines of =E2=80=9CHop-by-hop extensions can =
be inserted/removed/modified/processed by intermediate nodes *if* [=E2=80=
=A6=E2=80=A6..] and the possible consequences are [=E2=80=A6=E2=80=A6..]=E2=
=80=9D
>=20
> For example, hop-by-hop handling can be restricted only to a single adm=
inistrative domain, or only to tunnels (as in the zero checksum case).=20
>=20
> Regards,
> Tal.
>=20
>> -----Original Message-----
>> From: Mark Smith [mailto:markzzzsmith@gmail.com]
>> Sent: Monday, February 13, 2017 6:07 PM
>> To: Tal Mizrahi
>> Cc: 6man@ietf.org; IETF Discussion list; draft-ietf-6man-=20
>> rfc2460bis@tools.ietf.org; 6man-chairs@ietf.org
>> Subject: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt>=20
>> (Internet Protocol, Version 6 (IPv6) Specification) to Internet=20
>> Standard
>>
>> External Email
>>
>> ----------------------------------------------------------------------=

>> Hi,
>>
>>
>>
>> On 14 February 2017 at 00:43, Tal Mizrahi <talmi@marvell.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> Good discussion regarding the text about the hop-by-hop extension.
>>>
>>>
>>>
>>> In my opinion there is a valid use case for intermediate nodes that=20
>>> insert/remove/modify/process hop-by-hop extensions. Examples: IOAM, I=
NT.
>>>
>>> Since there is a use case, I believe we need explicit text about=20
>>> intermediate handling of hop-by-hop extensions.
>>>
>>
>>
>> Imagine you sent a letter through the postal system, and the postal=20
>> system wanted to add information to that letter, that is then to be=20
>> removed before the letter arrives at its final destination.
>>
>> The postal system have at least two choices as to how to add that info=
rmation.
>> They could:
>>
>> (a) unstick your envelope's seal, insert the information, reseal the=20
>> envelope so well you can't tell and send it on its way, some how=20
>> flagging to a destination device within the postal system that this=20
>> specific envelop needs to be openned, a specific page removed, and the=
n resealed.
>>
>> (b) take a new envelope with new internal postal system source and=20
>> destination address information, insert your letter without touching i=
t=20
>> in addition to the new information, and then sending it on its way.
>>
>> Imagine that the information to be added by the postal system is=20
>> printed on the same type of paper and is written in the same font as=20
>> you've chosen to use to write your letter.
>>
>> Have a think about these two methods, what could fail with each of=20
>> them, and what the consequences may be if any of those failures occur.=

>> Have a think of the benefits of each method, and whether they're worth=
=20
>> it compared to the failure mode costs and consequences for the method.=

>>
>>>
>>>
>>> This [somewhat] reminds me of the discussion a few years ago about=20
>>> the IPv6/UDP zero checksum. The WG ended up defining that =E2=80=9CZe=
ro=20
>>> checksum is permitted in IPv6/UDP *if* [=E2=80=A6=E2=80=A6..] and the=
 possible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>>>
>>>
>>
>> That is a far more trivial change to the packet - it is allowing a=20
>> value in an existing field that was formerly prohibited, and nodes tha=
t=20
>> did not understand that value would drop the packet because that is=20
>> what they had been specified to do if they received this prohibited va=
lue. In other words, existing implementations '
>> behaviour when this formerly unexpected value was encountered had=20
>> already been specified and deployed.
>>
>>
>>>
>>> I would argue that regarding hop-by-hop extension handling we also=20
>>> need to define that =E2=80=9CHop-by-hop extensions can be=20
>>> inserted/removed/modified/processed by intermediate nodes *if* [=E2=80=
=A6=E2=80=A6..]=20
>>> and the possible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>>>
>>
>> Some things that are possible to do in theory shouldn't be done in=20
>> practice, because the consequences when their implementations fail can=
=20
>> be severe and outweigh the benefits.
>>
>> In theory, inserted EHs will be removed 100% of the time. In practice =

>> they won't be, because implementations can have bugs and they can also=
=20
>> fail in unexpected ways e.g., hardware faults.
>>
>> Regards,
>> Mark.
> --------------------------------------------------------------------
> 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
> --------------------------------------------------------------------
>=20


From nobody Tue Feb 14 15:43:12 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E7D91298C8 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:43:10 -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 autolearn_force=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 QpIRqyUVxCP0 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:43:09 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E33801294DC for <ietf@ietf.org>; Tue, 14 Feb 2017 15:43:08 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cdmkS-000ISy-HL; Tue, 14 Feb 2017 18:43:04 -0500
Date: Tue, 14 Feb 2017 18:42:57 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, dcrocker@bbiw.net
Subject: Re: To "lose the argument in the WG"
Message-ID: <9C56754A894D7289BB6DC500@PSB>
In-Reply-To: <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UBuXBnr_rMSob1Bl92i1lMaJpJo>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:43:10 -0000

Pete,

I an in complete agreement with this note, but want to expand on
one point...

--On Tuesday, February 14, 2017 15:01 -0800 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> On 14 Feb 2017, at 9:05, Dave Crocker wrote:

>...
>> To Ted's point, indulging folk who 'did not have time' to
>> participate  earlier is frankly abusive of all those who did.
> 
> Yeah, I don't find Ted's point at all convincing either. On
> the other hand, if the WG didn't seek out required expertise
> and someone does notice a showstopper, that's not abusive. The
> WG screwed up.

I think this is key (and another reason I worry about excessive
homogeneity).  It is the WG's responsibility to understand the
context of whatever they are proposing, to seek out additional
expertise if it is needed, and to incorporate relevant work
before requesting IETF Last Call.  While one can go too far
about this (I would not propose a Rule), if a serious issue is
identified during  Last Call, even or especially one that takes
a lot of time and energy to resolve, it should generally be
treated as "shame on the WG for not anticipating and dealing
with the issue" not "shame on the person who finds the problem
for not finding the time and resources to participate in the WG.
This isn't a matter of casting blame, but comments resembling
"you didn't participate in the WG so you have no standing to
raise that objection during Last Call" is as obnoxious and
likely to be harmful to the process as "you raised that issue
and lost, shut up".

best,
    john


From nobody Tue Feb 14 15:51:44 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5791D129989 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.022
X-Spam-Level: 
X-Spam-Status: No, score=-7.022 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qti.qualcomm.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ilpH5pTuiqj9 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:51:40 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08963129985 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:51:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1487116300; x=1518652300; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=0LPAHuyfXRlaS/Lu9LBh7tsHtBRmrPhcKssE/Gn1a0o=; b=EEXW79t8egpRz4wGr+yivwAo+MXnBUmXnOrUbvv4NAKVxN3LW3ugL3LT TdGO4RJFFsaSiTdcBOXQ4WmKHbkBodcuR8/vAgP3hv1+mDRZdjiMBs5fM S2VXoFtIIH9Lc+qQ3h+OYFDyaF+5efuvC7v4elMBJirVH+vbztAfwvsGM I=;
X-IronPort-AV: E=Sophos;i="5.35,163,1484035200"; d="scan'208";a="262868163"
Received: from unknown (HELO Ironmsg04-L.qualcomm.com) ([10.53.140.111]) by wolverine01.qualcomm.com with ESMTP; 14 Feb 2017 15:51:39 -0800
X-IronPort-AV: E=McAfee;i="5800,7501,8439"; a="1290855054"
Received: from unknown (HELO [10.64.121.67]) ([10.64.121.67]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 14 Feb 2017 15:51:38 -0800
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "Ted Lemon" <mellon@fugue.com>
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 15:51:38 -0800
Message-ID: <7EAC6978-01B4-42A5-B949-A21AD9568190@qti.qualcomm.com>
In-Reply-To: <2F13B46F-AFE5-4E49-9724-3737781B4883@fugue.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <2F13B46F-AFE5-4E49-9724-3737781B4883@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vidBJxUg5bf7HhmJhGIlOWpt1eE>
Cc: Dave CROCKER <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:51:42 -0000

On 14 Feb 2017, at 15:18, Ted Lemon wrote:

>  My experience is that there are lots of things that get worked on in 
> working groups that I don't even have time to be aware of, and 99% of 
> the time the fact that I wasn't aware of them is not a problem at all. 
>   But 1% of the time it is, and last call is (hopefully) where I 
> become aware of that and say something.   Are you really calling this 
> abusive?

Nope. I simply disagreed with you that Last Call is a way to account for 
people who didn’t have time. The WG should have sought the expertise. 
Last Call ought not be relied upon to bring in experts who didn’t 
participate, due to lack of time or otherwise. The process can't depend 
on a single participant's time.

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Feb 14 15:55:35 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 878BE1298C6 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1cn5cPgidRy for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:55:32 -0800 (PST)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::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 3CAB7129484 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:55:32 -0800 (PST)
Received: by mail-qt0-x231.google.com with SMTP id x49so124917544qtc.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:55:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=IBSumjNF3gjW4qcwRcwaH7PXahBl6pumKz6i4DScz08=; b=cGAjzFZ7/7/jBVQ4kCqBU1CD5Y3eQK3ey8btA9g74udQENAyRgzWKVn00Vh/gw1j8s nfacv4Fs6t2Xl9NJ1vB6UZ2MN36SzEhSdlLDiwPEzw8CWAgn6wSxNxDkpD1cVlPbpe/Z h5LAP5O63kqz975gSDw8zQHZ9SQYfu4pgM6grIixdTGON4hWFm4v87O5znA5HLudeqET uH9k1uaEPDMEWtbq3454tgu6cuvag6ZuDpbpW/YTkelvtuESblLeEMiYzkPJ4PzYsJ/1 tSOD7rH/0E8ELIIEh5KnMe1P+K/2itlgOaDoMo2YiqO5ZTEGzNH1PO10W3US7qBrqLcS H6Zg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=IBSumjNF3gjW4qcwRcwaH7PXahBl6pumKz6i4DScz08=; b=bfVoscQRlB826v0vMubdr0JDdPNniNS+wZUq5ft5p1RgqhaqiGBkDHmQfS/PcO8ec4 5Mzv6dxUcQyKuswLeT24eQQBDpdlKMOro6IQT9HR6wXy21r1WpmXUzw+Zt54JsMpXDHK nQNXCgdgAaxDBsWl8dAoCFGfyJ/typK3zW9yinLRip5y+yHOhX7PZx6dz8K+ywavSCqQ OONvN/rc4GqO8wmCLdCgXTRFj6H6MFYmtAZybSTqLiqt4MhrJjikGOugRtDwlFNPI7aj Ik2CGPJojGTAzAN/pXrAbqc/pMTphdNgo4oqsODtneloLH8q/wrq0CnueK5uKGE5gFox Hx3g==
X-Gm-Message-State: AMke39ncAZjhkg5yjhgcvJ1ohgzf11atI7xsJEbHjeXqqJTGww/n/jm2betZxpcsfdYDrw==
X-Received: by 10.200.44.1 with SMTP id d1mr29221492qta.215.1487116531382; Tue, 14 Feb 2017 15:55:31 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id l53sm1264830qtl.41.2017.02.14.15.55.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 15:55:30 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <C1A6EB5D-7E9B-4812-BF67-4B5FBAA1E8B0@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_298D07F6-B1F5-4853-A2D7-BE359B207F66"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Tue, 14 Feb 2017 18:55:29 -0500
In-Reply-To: <7EAC6978-01B4-42A5-B949-A21AD9568190@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <2F13B46F-AFE5-4E49-9724-3737781B4883@fugue.com> <7EAC6978-01B4-42A5-B949-A21AD9568190@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hUDuhdTwpvV9GW6Tmv6Vc9zJwtA>
Cc: Dave CROCKER <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:55:33 -0000

--Apple-Mail=_298D07F6-B1F5-4853-A2D7-BE359B207F66
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Feb 14, 2017, at 6:51 PM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> The WG should have sought the expertise.

This appears to be a rule quite frequently honored in the breach.


--Apple-Mail=_298D07F6-B1F5-4853-A2D7-BE359B207F66
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Feb 14, 2017, at 6:51 PM, Pete Resnick &lt;<a href="mailto:presnick@qti.qualcomm.com" class="">presnick@qti.qualcomm.com</a>&gt; wrote:<div><blockquote type="cite" class=""><div class=""><span style="font-family: Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">The WG should have sought the expertise.</span></div></blockquote></div><br class=""><div class="">This appears to be a rule quite frequently honored in the breach.</div><div class=""><br class=""></div></body></html>
--Apple-Mail=_298D07F6-B1F5-4853-A2D7-BE359B207F66--


From nobody Tue Feb 14 15:56:33 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B31B129989 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:56:32 -0800 (PST)
X-Quarantine-ID: <3ti2D8UuNI97>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 3ti2D8UuNI97 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 15:56:31 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 016D7129981 for <ietf@ietf.org>; Tue, 14 Feb 2017 15:56:30 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 15:48:32 -0800
Mime-Version: 1.0
Message-Id: <p0624060ad4c94966bc39@[99.111.97.136]>
In-Reply-To: <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 15:56:28 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, dcrocker@bbiw.net, Ted Lemon <mellon@fugue.com>, Yoav Nir <ynir.ietf@gmail.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: To "lose the argument in the WG"
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vjT6b-RpHLtUEmoiTKB-GOPqcfQ>
Cc: Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Feb 2017 23:56:32 -0000

At 12:18 PM +1300 2/15/17, Brian E Carpenter wrote:

>  2. As a Gen-ART reviewer I've often seen drafts at IETF LC that
>  really *need* a general, in-depth review.

As a document author, I appreciate the area reviews done by GEN, SEC, 
etc.  However, I think they would be just as useful and perhaps more 
timely if done during WGLC (assuming the WG does a WGLC).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
    The highlight of the annual Computer Bowl occurred when Bill Gates,
who was a judge, posed the following question to the contestants:
    "What contest, held via Usenet, is dedicated to examples of weird,
obscure, bizarre, and really bad programming?"
    After a moment of silence, Jean-Louis Gassee (ex-honcho at Apple)
hit his buzzer and answered "Windows."
                                          --Recounted by Adam C. Engst


From nobody Tue Feb 14 16:06:32 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166C412998B for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:06:31 -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, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kbJD9FNrZ32a for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:06:29 -0800 (PST)
Received: from mxa2.tigertech.net (mxa2.tigertech.net [208.80.4.162]) (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 C567B1298C6 for <ietf@ietf.org>; Tue, 14 Feb 2017 16:06:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4BB0BDC0113; Tue, 14 Feb 2017 16:06:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487117189; bh=UtOQR8n9nmkykt9sxeB4gtORpRQnicqb2XDhSFG+5dM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=AfUJIlJ92hykpNatDM9VwmMsIobWS2NV4ctbZ4p5+4ybKMqQz9ZrEGGi8hvGuI0BJ ScZJtTM74B+3i/alr5ZRtCYRDbsGdWIB0SCFxclkSqyOQFBqxwxbI2SAfAGOE2IjFf XjSZ4TYQt9fQhtrilQmQtjk6QBQiz2XcydrCARi8=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id D6004DC0116; Tue, 14 Feb 2017 16:06:28 -0800 (PST)
Subject: Re: To "lose the argument in the WG"
To: Randall Gellens <rg+ietf@randy.pensive.org>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com> <p0624060ad4c94966bc39@[99.111.97.136]>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <4965a53f-1e45-b444-1430-7d56ac413d50@joelhalpern.com>
Date: Tue, 14 Feb 2017 19:06:27 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p0624060ad4c94966bc39@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XQs5z51_ASgxCoDOuBRHcRh-DRs>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 00:06:31 -0000

There is a procedure (that I thought was pretty widely known) that 
allows chairs to request early cross-are review when they think it is 
helpful.  I know that several of the review teams support this.

Yours,
Joel

On 2/14/17 6:56 PM, Randall Gellens wrote:
> At 12:18 PM +1300 2/15/17, Brian E Carpenter wrote:
>
>>  2. As a Gen-ART reviewer I've often seen drafts at IETF LC that
>>  really *need* a general, in-depth review.
>
> As a document author, I appreciate the area reviews done by GEN, SEC,
> etc.  However, I think they would be just as useful and perhaps more
> timely if done during WGLC (assuming the WG does a WGLC).
>


From nobody Tue Feb 14 16:21:39 2017
Return-Path: <randy_presuhn@alumni.stanford.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD47A12953B for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level: 
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=no autolearn_force=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 y5OIrR1cdWM2 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:21:36 -0800 (PST)
Received: from mail-it0-f48.google.com (mail-it0-f48.google.com [209.85.214.48]) (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 DCB6812946E for <ietf@ietf.org>; Tue, 14 Feb 2017 16:21:35 -0800 (PST)
Received: by mail-it0-f48.google.com with SMTP id x75so54664092itb.0 for <ietf@ietf.org>; Tue, 14 Feb 2017 16:21:35 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=sK/tpB20jxzOLqJ60lPzTXfGAxvLfj8oyttxQYZakos=; b=CImgZpVJXJ73N+zs7ipgHMoE2cYR2l6vJVHlto6oCpwHyejQTCV4Vb4n0mXjHTsuxu untbJk377og16kbQTTf4kO+Tahu63HQxRX+YePwHx+rqLT4kq0cuygB0MfhlqQJI0OlA 7feQeF2wUwh4lNBvqSGtz8NQoGqnH033MOyNFrOFfsl0uH1ky0BKcQv2b4s5oMoX1056 ihcc/YHVJleaUVbcD1bNA7trY0eNaPwskeU5tAb0xQ6tghE4iLKV7Bil9VBw008pCm5Z dX6tBrl16P2t0FkPIyE092ySrNH66VEcrTwe5sywNLDtlp1zAWM2ZkROB3+4XcWu5rkd Bk0w==
X-Gm-Message-State: AMke39mwxAj8x92h5RRWTJPsVfYocXHyF+GhuJdNdFSXCLjaLooHQ4BqH4iZoqPH8EcuJKl0
X-Received: by 10.84.236.9 with SMTP id q9mr35996783plk.96.1487118095087; Tue, 14 Feb 2017 16:21:35 -0800 (PST)
Received: from [192.168.1.114] (c-50-143-178-150.hsd1.ca.comcast.net. [50.143.178.150]) by smtp.gmail.com with ESMTPSA id g85sm3329042pfe.38.2017.02.14.16.21.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 16:21:34 -0800 (PST)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu>
Date: Tue, 14 Feb 2017 16:21:35 -0800
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240609d4c937dc9ff8@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s31306oSwQnwWCLKepJOdMqTgxY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 00:21:37 -0000

Hi -

On 2/14/2017 2:43 PM, Randall Gellens wrote:
> At 8:59 PM +0100 2/14/17, Gunnar Hellström wrote:
>
>>  Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>>
>>>  Hi -
>>>
>>>  On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>>  At 11:01 AM +0100 2/14/17, Gunnar Hellström wrote:
>>>>
>>>>>   My proposal for a reworded section 5.4 is:
>>>>>
>>>>>   5.4.  Unusual language indications
>>>>>
>>>>>   It is possible to specify an unusual indication where the language
>>>>>   specified may look unexpected for the media type.
>>>>>
>>>>>   For such cases the following guidance SHALL be applied for the
>>>>>  humintlang attributes used in these situations.
>>>>>
>>>>>   1.    A view of a speaking person in the video stream SHALL, when it
>>>>>  has relevance for speech perception, be indicated by a Language-Tag
>>>>>  for spoken/written language with the "Zxxx" script subtag to indicate
>>>>>  that the contents is not written.
>>>>>
>>>>>   2.    Text captions included in the video stream SHALL be indicated
>>>>>  by a Language-Tag for spoken/written language.
>>>>>
>>>>>   3.    Any approximate representation of sign language or
>>>>>  fingerspelling in the text media stream SHALL be indicated by a
>>>>>  Language-Tag for a sign language in text media.
>>>>>
>>>>>   4.    When sign language related audio from a person using sign
>>>>>  language is of importance for language communication, this SHALL be
>>>>>  indicated by a Language-Tag for a sign language in audio media.
>>>>
>>>>  [RG] As I said, I think we should avoid specifying this until we have
>>>>  deployment experience.
>>>  ...
>>>
>>>  From a process perspective, it's far easier to remove constraints
>>>  as a specification advances than it is to add them.
>>  I agree. It is often better to specify normatively as far as you can
>> imagine, so that interoperability and good functionality is achieved.
>> Stopping halfway and have MAY in the specifications creates
>> uncertainty and less useful specifications.
>
> My reading of what Randy says is the opposite of Gunnar's.  In my
> reading, Randy points out that is it easier to remove the SHOULD NOT in
> the future then it is to change the meaning of the combinations or
> switch to a different mechanism.
>
> In my experience, it's better to specify only what we know we need and
> what we know we understand.  Speculative specifications "as far as you
> can imagine" more often lead to interoperability problems, unnecessary
> complexity, limitations on what's needed in the future, and divergent
> implementations.

I think the difference in your positions comes down to

   (1) your respective notions of "what we know we need and what we
       know we understand";

   (2) whether you believe that the interoperability and conformance
       consequences of removing a "SHOULD NOT" could be the same
       as those merely retaining a "MUST" or "SHALL" - this determines
       whether Randy G.'s proposal provides a path for some future
       revision to mandate (if deployment experience substantiates the
       need/understanding) the behavior proposed by Gunnar.  That path
       is not at all obvious to me.

Randy


From nobody Tue Feb 14 16:39:29 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD1A12953B; Tue, 14 Feb 2017 16:39:25 -0800 (PST)
X-Quarantine-ID: <BOoRFRq1mXJg>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 BOoRFRq1mXJg; Tue, 14 Feb 2017 16:39:24 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 2893212945D; Tue, 14 Feb 2017 16:39:24 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 14 Feb 2017 16:31:25 -0800
Mime-Version: 1.0
Message-Id: <p0624060dd4c9523fcf2a@[99.111.97.136]>
In-Reply-To: <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu>
X-Mailer: Eudora for Mac OS X
Date: Tue, 14 Feb 2017 16:39:21 -0800
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>, ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NangosFQfIprJqN5pKwOEz8WLEs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 00:39:26 -0000

At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:

>  Hi -
>
>  On 2/14/2017 2:43 PM, Randall Gellens wrote:
>>  At 8:59 PM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>
>>>   Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>>>
>>>>   Hi -
>>>>
>>>>   On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>>>   At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>>>>
>>>>>>    My proposal for a reworded section 5.4 is:
>>>>>>
>>>>>>    5.4.  Unusual language indications
>>>>>>
>>>>>>    It is possible to specify an unusual indication where the language
>>>>>>    specified may look unexpected for the media type.
>>>>>>
>>>>>>    For such cases the following guidance SHALL be applied for the
>>>>>>   humintlang attributes used in these situations.
>>>>>>
>>>>>>    1.    A view of a speaking person in the video stream SHALL, when =
it
>>>>>>   has relevance for speech perception, be indicated by a Language-Tag
>>>>>>   for spoken/written language with the "Zxxx" script subtag to indica=
te
>>>>>>   that the contents is not written.
>>>>>>
>>>>>>    2.    Text captions included in the video stream SHALL be indicate=
d
>>>>>>   by a Language-Tag for spoken/written language.
>>>>>>
>>>>>>    3.    Any approximate representation of sign language or
>>>>>>   fingerspelling in the text media stream SHALL be indicated by a
>>>>>>   Language-Tag for a sign language in text media.
>>>>>>
>>>>>>    4.    When sign language related audio from a person using sign
>>>>>>   language is of importance for language communication, this SHALL be
>>>>>>   indicated by a Language-Tag for a sign language in audio media.
>>>>>
>>>>>   [RG] As I said, I think we should avoid specifying this until we hav=
e
>>>>>   deployment experience.
>>>>   ...
>>>>
>>>>   From a process perspective, it's far easier to remove constraints
>>>>   as a specification advances than it is to add them.
>>>   I agree. It is often better to specify normatively as far as you can
>>>  imagine, so that interoperability and good functionality is achieved.
>>>  Stopping halfway and have MAY in the specifications creates
>>>  uncertainty and less useful specifications.
>>
>>  My reading of what Randy says is the opposite of Gunnar's.  In my
>>  reading, Randy points out that is it easier to remove the SHOULD NOT in
>>  the future then it is to change the meaning of the combinations or
>>  switch to a different mechanism.
>>
>>  In my experience, it's better to specify only what we know we need and
>>  what we know we understand.  Speculative specifications "as far as you
>>  can imagine" more often lead to interoperability problems, unnecessary
>>  complexity, limitations on what's needed in the future, and divergent
>>  implementations.
>
>  I think the difference in your positions comes down to
>
>    (1) your respective notions of "what we know we need and what we
>        know we understand";
>
>    (2) whether you believe that the interoperability and conformance
>        consequences of removing a "SHOULD NOT" could be the same
>        as those merely retaining a "MUST" or "SHALL" - this determines
>        whether Randy G.'s proposal provides a path for some future
>        revision to mandate (if deployment experience substantiates the
>        need/understanding) the behavior proposed by Gunnar.  That path
>        is not at all obvious to me.

The purpose of the draft is to enable the two=20
endpoints of a real-time communication session to=20
agree which languages and media to use for=20
interactive communication.  We have a mechanism=20
of adding language tags to media stream=20
negotiations.  In most cases, the language and=20
media modality are an obvious fit.  There are=20
combinations of media and language where the=20
meaning is not so obvious, specifically, signed=20
language tags with a audio or text, and=20
non-signed language tags with video.  My proposal=20
is that we say offerer SHOULD NOT send such=20
combinations and answerer MAY ignore language.=20
This allows future specifications for the=20
underlying uses Gunnar wants (such as real-time=20
subtitles in video and signed equivalents in=20
text).  Such future specifications could define a=20
use for the language and media combinations and=20
remove the SHOULD NOT send and MAY ignore, or=20
could define a new mechanism.  I don't think we=20
know enough now to dictate what the solution=20
should be.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Dogs have owners.  Cats have staff.


From nobody Tue Feb 14 16:51:43 2017
Return-Path: <ggm@algebras.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63BFA12998A for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v0E1Ha1zdPN4 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 16:51:40 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 82609129430 for <ietf@ietf.org>; Tue, 14 Feb 2017 16:51:40 -0800 (PST)
Received: by mail-vk0-x234.google.com with SMTP id k127so90654480vke.0 for <ietf@ietf.org>; Tue, 14 Feb 2017 16:51:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=+QBC99nkaWvMYchcXpxAL5FhbGr5h8zj9usCzb9n6Zw=; b=sjFUCTZxjSNyiKezI2s2yAivruJ4by/w2E9p4t6tBGaO3LQCTnbFPwYZgXRAjvnYQ9 kFRu/VWhgc9Hdd/oKFetta+MDFX1Zrrkt94HWZjFlz01yfkqezOcwAvLmeINNWMmr3ix khwcfwtNSvCcpSGS99IX9g8POk24St2G13JwEwsz3EK1u5BoY6YmNZ8+3Rl5tIDQ+h77 SK6oR8n4ntivma5lKh3W3cQlNyI1kQ5etOd9RIDZH6o2Q3QZM0wjlbUNkHy8BA/EKUS9 HSs0w8uEpokhKGxt64DM7DHCdJStfgVj6VjSLXGOSkxfVifaK8wCyjyc3TXrnF2jpSth YzBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=+QBC99nkaWvMYchcXpxAL5FhbGr5h8zj9usCzb9n6Zw=; b=kJ7goJOrMs3xHj4yHycm7GvmZy6Y52mg/QcNgmvpdl3s/1twyX6xz1e5nDSeKzyMal qLk00EV5fdXGbW0g+zZftBvyaZzzBVLZt+s8UQNmgh5XdF3aobDGH619EH4GPbmfL+B8 sXDuf8xSdzrN1006/UFovp+O7V3GjVaZ+Wg9Vg8PQbOgbsObrdhzS4LyibDN4ZF07xMD bL/+r0vebREbgyEJGjs+rn7KRqaoQgpgyTl8vrH2LhK9Ihb1lrTfOyZWQCsIWp81Abmx JRUGbWQc980tQNno+Y/6hpN9di0fyq8dhyQ/nJLguW9cMjf7TfK30zESQIg8cjhx41cn Jqug==
X-Gm-Message-State: AMke39n4kFsQ7ZtGcykk4QupscFyZOzdU3JJUmRMu9Fcpu6K4atmi/As+JBeByslxpAHzcIxScthM1ZbBVp6Ow==
X-Received: by 10.31.149.15 with SMTP id x15mr14139183vkd.130.1487119899393; Tue, 14 Feb 2017 16:51:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.48.211 with HTTP; Tue, 14 Feb 2017 16:51:38 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:ade9:eeb6:e48a:6187]
In-Reply-To: <4965a53f-1e45-b444-1430-7d56ac413d50@joelhalpern.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com> <p0624060ad4c94966bc39@99.111.97.136> <4965a53f-1e45-b444-1430-7d56ac413d50@joelhalpern.com>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 15 Feb 2017 02:51:38 +0200
Message-ID: <CAKr6gn0qF5rsukEB5Xc3V_=TgnEsqtdAyfLsVjuW-DJPqMLm5g@mail.gmail.com>
Subject: Re: To "lose the argument in the WG"
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kE0gAIYDfUux_2-2I_O17LRKhLg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 00:51:42 -0000

I'm pretty much not in consensus in DNSOP right now, and I take that
in good part because working consensus is a pretty high value
proposition.

I think if I was 'outside the church' on a matter of technical merit
I'd feel more like standing up and shouting about it. But, mostly,
that WG is talking politics when I chose to disagree (I hate to
mis-characterize it, but thats what I see the ALT and related
discussion as: it has next to no technical merit to me, its a politics
conversation)

People in the WG talk to me outside of the list, and likewise. I'm ok
with that, because in the end, consensus is a high value thing. When
an author says to me "Its AUTH48 and we're in IESG process, if you
make me re-do this it has to go back into the WG to get signed off, so
tell me now: is this real, or just opinion" I take that on board.

So I draw a personal distinction between matters of substance, and
matters of opinion, in how I chose to flag dissent. and I would
encourage others to do the same: try and approach the question from
the perspective of:

  "is this materially relating to bits on the wire, and how protocol
endpoints work"

distinct from

  "is this something about a human process, I just don't agree with"

If you're talking about UTF-8 labels and encoded ASN.1 strings, its
case 1. If you're talking which of IAB and ICANN have primacy
determining what labels exist, you're case 2.

-G

On Wed, Feb 15, 2017 at 2:06 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> There is a procedure (that I thought was pretty widely known) that allows
> chairs to request early cross-are review when they think it is helpful.  I
> know that several of the review teams support this.
>
> Yours,
> Joel
>
>
> On 2/14/17 6:56 PM, Randall Gellens wrote:
>>
>> At 12:18 PM +1300 2/15/17, Brian E Carpenter wrote:
>>
>>>  2. As a Gen-ART reviewer I've often seen drafts at IETF LC that
>>>  really *need* a general, in-depth review.
>>
>>
>> As a document author, I appreciate the area reviews done by GEN, SEC,
>> etc.  However, I think they would be just as useful and perhaps more
>> timely if done during WGLC (assuming the WG does a WGLC).
>>
>


From nobody Tue Feb 14 17:04:26 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49421129955 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 40TC2kVl26cX for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:04:23 -0800 (PST)
Received: from resqmta-ch2-08v.sys.comcast.net (resqmta-ch2-08v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:40]) (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 12F4212953B for <ietf@ietf.org>; Tue, 14 Feb 2017 17:04:23 -0800 (PST)
Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-08v.sys.comcast.net with SMTP id do17cIDENy4bMdo18caaXV; Wed, 15 Feb 2017 01:04:22 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-02v.sys.comcast.net with SMTP id do16cIP3uanCido17cdSBQ; Wed, 15 Feb 2017 01:04:22 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1F14K3c028393; Tue, 14 Feb 2017 20:04:20 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1F14JIs028390; Tue, 14 Feb 2017 20:04:19 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Charlie Perkins <charles.perkins@earthlink.net>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
In-Reply-To: <d59427a0-a105-9c10-9de1-86755386d43e@earthlink.net> (charles.perkins@earthlink.net)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 14 Feb 2017 20:04:19 -0500
Message-ID: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfKS5k4ydAZv1A456HK1fKqO6j5y19L1ZpbVVuQFDzw5RJynsm4EAMW/wcjOfIV/X2s1VMEvayTR3vLd+fyExBbJ4s+untlG2qrb6SFcan1fbUFhjyWJi BuWJ2XhXWcrJM9lz9/6nA+ONc7YRHvEIZzAN6p6B9Mj+SD33E4czqMy3Q/LYHEvDJI+QY3qSNkzvw2XpIoLuwqBEyYtWSo35V6QdQZOBWEt02DkGEokD6VkX qaVRCcr4CJFrMjY+moCAJVvIRT2bi5AXh8g2OMgkykVP8wp5PlSLFJlZv7DcnV7T
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OV40ZTO3bTXkPuQAoEtXjHiA3ww>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:04:24 -0000

Charlie Perkins <charles.perkins@earthlink.net> writes:
> I am hesitant to replace so many MNID types by a single URN type with 
> substructure.  What would you think about replacing the existing 
> RFID-*-URI types with a single URN type, but leaving the existing binary 
> types?  This gets the benefit you suggest for future extensibility, but 
> retains the shorter forms that may often be advantageous.

Suddenly today I realized something I should have realized in the
review, which would have saved us much time in discussion.  Viz.,
consider this proposal:

- one MNID type for *all* the EPC binary schemes

- one MNID type for *all* URNs, *including* the EPC URI forms

This would work, since (1) (not surprisingly) the EPC binary schemes are
all differentiated by their first 8 bits.  (see table on page 19 of the
tag-data standard,
http://www.gs1.org/gsmp/kc/epcglobal/tds/tds_1_1_rev_1_27-standard-20050510.pdf)
and (2) all URNs are differentiated by their namespace part.

(This parallels using one MNID number for all DUID types, since DUIDs
have an internal indicator for the four types.)

This approach has all the desirable properties anyone has mentioned so
far:

- includes all EPC binary and URI forms
- automatically includes all existing and future EPC binary forms
- automatically includes all existing and future URN forms *including*
  all existing and future EPC URI forms
- doesn't have a proliferation of MNID type numbers which duplicate
  information that can be fairly easily extracted from the
  identifier itself
- includes all the short EPC forms, allowing brevity when that is
  desirable

This seems to be practical, simple, and almost as elegant as possible.
What do you think?

> I changed the text as follows:
>
>>     Some MNIDs contain sensitive identifiers which, as used in protocols
>>     specified by other SDOs, are only used for signaling during initial
>>     network entry.  In such protocols, subsequent exchanges then rely on
>>     a temporary identifier allocated during the initial network entry.
>>     Managing the association between long-lived and temporary identifiers
>>     is outside the scope of this document.
>
> I can't remember exactly why this text was added - it was a long time 
> ago.  But anyway the main point is to simply mention that there may be 
> associations between some of the MNID types that might be important from 
> a security standpoint, without meaning to go into examples.

Certainly the new text is clear enough.

Dale


From nobody Tue Feb 14 17:26:42 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70C7E129404 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f6JO00WQhKJg for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:26:41 -0800 (PST)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::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 8598812953B for <ietf@ietf.org>; Tue, 14 Feb 2017 17:26:39 -0800 (PST)
Received: by mail-vk0-x233.google.com with SMTP id x75so90951943vke.2 for <ietf@ietf.org>; Tue, 14 Feb 2017 17:26:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6ny14r/Pk3fJd+usqrLRZQv2u8cMyFIO97F1TfVsHFY=; b=fUqDxn1OCpeWJ0DG3IYYN3JUaxaiyFbVcdbjtItUU4mumg8JqbHcmHola+76WK0bJm N0DjLYt2YhnYHcZnGH8SkrwZap5OMzjMsBIEkhpbv4bAziYKzctehm8OGxhAFG37bLa1 61cWoufLhB8H6pFraUYPsWaLUInRc1Hv/eDB0dCIw2UdRURFC2Q2i2CKmV/gAXRmp60h sUKrMd51MCCyqVms/YsLNmDt71tpb531YuyfNRuzMSbK52sHEm1STRGX+suCfEjZspDm AQz1s7ka7VOz06l0hwF0h5hHE+4CQjcl//dNEoTQmSXYmEZk5V9T4ygslKMCtl6OaxY3 vLMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6ny14r/Pk3fJd+usqrLRZQv2u8cMyFIO97F1TfVsHFY=; b=NR9xNQeG08yP48SqcCgQaPQgQl+0W+x20o/qgmiRvS8c+CIi8A+dnrb0Wc5vzR70OJ cZTUfY6x8m0es/UUe4A+QvzAvOvxIeNVttn04i5pGAK1YrhPUrH4UdyI9hQ4Lb9vUifb EKrsTKEZxCiA6aG6hp0wDFdLg8qNWh+qyPS2wkzGxFvDYEJhbi4klXR7W3kHd8SHbwff YPs6S67eTopa9INvb+joJYn63K1FlNAsCO01p7CAzzR09ddmJyWoNGjsDAv2aH5Mkben tlAyrOaK3Q38GvdLTGRUuseEJlpaBgkpUaimMtaaIjShKI7rseEiJd4LomoPTsoUIOpg 2bag==
X-Gm-Message-State: AMke39n+ywhSMrzgf9+J9Uldj7+ky8BLy2KSAxS0gehEoeWUnxIeqnMzYMf2j/dFNSbMLVCzGJ0nRSlZu4MIIJmE
X-Received: by 10.31.59.197 with SMTP id i188mr12985572vka.45.1487121998409; Tue, 14 Feb 2017 17:26:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Tue, 14 Feb 2017 17:26:17 -0800 (PST)
In-Reply-To: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 14 Feb 2017 17:26:17 -0800
Message-ID: <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a1142f178745874054887922a
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZWqyxzSU8je_gQnlmpkzcAxsVr0>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:26:41 -0000

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

On Tue, Feb 14, 2017 at 11:06 AM, <otroan@employees.org> wrote:

> Brian, changing the 64 bit boundary is such a big change that I would
> claim it is far outside the scope of advancing 4291 to Internet standard.
>

Agreed.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Feb 14, 2017 at 11:06 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otro=
an@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">Brian, changing the 64 bit boundary i=
s such a big change that I would claim it is far outside the scope of advan=
cing 4291 to Internet standard.<br></blockquote><div><br></div><div>Agreed.=
</div></div></div></div>

--001a1142f178745874054887922a--


From nobody Tue Feb 14 17:31:24 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89293129493; Tue, 14 Feb 2017 17:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cx_T4NJqzeDf; Tue, 14 Feb 2017 17:31:22 -0800 (PST)
Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (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 657BD129404; Tue, 14 Feb 2017 17:31:22 -0800 (PST)
Received: by mail-io0-x242.google.com with SMTP id m98so10909276iod.2; Tue, 14 Feb 2017 17:31:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=O8a6WprLUWQlwKsao0ng5DaOgjhB1/x/uT4GbIH1LB0=; b=mL0a8pYm7W5kDYzbye7Vdc38oMtuSbDsNP6I2BF0Y5BLrVEayPD+27t3/ozSe6vWZU qyRZOO8KykKzKBFjAQ0S860c4kGbREbP38QylsEduD7F6tWSk2g2DLKcG9iSJjcHsvYT Y2gONO9RAYWPm7pH2zBY3ZX9i5wdLuFP8B3NdJ2RL++gMFc2DZCbkyQfpEcrP/guGar1 Bwyb6cTq2LzSa44N6gDu6YsSHqb5VM6UjNzyjvSv//PHZxv5cHPMoYsJhDpOQQkgmU6O tj+CwpSmySk7Xk4UMMjx4AnbSRLQajQRiGe4wy3MT6lWyW6DRhHhdncZH2NuIuL9CoVn qEAw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=O8a6WprLUWQlwKsao0ng5DaOgjhB1/x/uT4GbIH1LB0=; b=OVJgJJhCeiYtSZ6YpXpLcvZEjK28eWZPW+N/6Tg6WhEqL7G0y/gD0D7hDV+2ubCymR OO6m+oG9AMjqM56xYvkKQJDZrqveICGg54IvFbjy6DwrfXCkLiu1orzcJZ0mQYU6GUfu ph/e0K2yQKR44Yf/Pq6MXqIzraB+X7QMPnGH0QkT06eEVH6Bl8rubvBB0bt0PtYtvjjt 1huv4mbEpbJqv+nxn3NtiVAp1bUSl8cUPo6fUyaMR+eXXTqSCeXNKukaV8Ma4rf6TnYE 3fhRaWpWdtYLZGuyCK/mMnWm3bJRduCdHFQlMkSZcXElp0DJKByUIwK8kxm+QKj1kKCj WgpQ==
X-Gm-Message-State: AMke39nv/EAVmaIv7CfJUOW6vRbV8LAXf+r/Hqiio1Jt8Vrg3zSgCYO8kNMepcT5dSpPTw==
X-Received: by 10.98.111.194 with SMTP id k185mr34618771pfc.83.1487122281727;  Tue, 14 Feb 2017 17:31:21 -0800 (PST)
Received: from [192.168.178.21] ([118.148.78.74]) by smtp.gmail.com with ESMTPSA id 199sm3393022pfu.91.2017.02.14.17.31.18 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Feb 2017 17:31:21 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>, Ole Troan <otroan@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com>
Date: Wed, 15 Feb 2017 14:31:20 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T6vsOU5o764sJYZQg6PXZ9-3bVU>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:31:23 -0000

On 15/02/2017 14:26, Lorenzo Colitti wrote:
> On Tue, Feb 14, 2017 at 11:06 AM, <otroan@employees.org> wrote:
> 
>> Brian, changing the 64 bit boundary is such a big change that I would
>> claim it is far outside the scope of advancing 4291 to Internet standard.
>>
> 
> Agreed.

Of course. The point is only that it's a parameter in the design of SLAAC,
whose value is set by the address architecture.

   Brian


From nobody Tue Feb 14 17:32:23 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFC18129493 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hc8QjK3Jhat for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 17:32:18 -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 9DA36129961 for <ietf@ietf.org>; Tue, 14 Feb 2017 17:32:16 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id t8so91117406vke.3 for <ietf@ietf.org>; Tue, 14 Feb 2017 17:32:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jPWJTD09pXCdsH/SgGA8dXvJiiYjBAEwcSgwHzGCvp8=; b=CVlUaE2OEhSVu/snfEbmPx7cvKvdWL821uiUrAVEDr0hSeb/ksAJEea4FH7MDNOTi9 lHaEOOBL8ftwxz3DjoNeeuUEAsZetZ14Nusjyqp46PDRueejEIH2D99bIyXU1CcG2VNw lxl9HoTmx/x0wFMTgNpsLQ0I8ur3Ryj2A15Z4F2dDbbgWr9YQsArExxBSXasBZ1bI/kg Cem/SM3NWTpei9I7Lmpfi1MdSWxJ8JDHqLFxuv7hjEl4cMiMLeWPzVrBpM4c//a7jaf2 ewLaT6rTWnfmEhJ3CMi/mqDbkd2L6NeBzAqUJgoZvP6XnHf5HlDc4vbZsQBPTzOzKjIa TIbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jPWJTD09pXCdsH/SgGA8dXvJiiYjBAEwcSgwHzGCvp8=; b=NE//Ql9YFkPRpTXwYF8AUaOxYr3Nav08q5T+qDaEZTFpvpx0YEwL12uoh6z3PEEBZ9 ZETxwoN67VYF+Fob26aySE4UqHkiogYGi6Q6NIUjw6Kh8SdBBjb/4lxVrfc1lnqyfRpl WDPiPe8kbNiY0UWQ0Q5qPp+KmlbvSssdZLlnR0dNiU49Ije+/UJa0+wJ6mDyT/UB7e83 d5rlnW21YRnaen7/wLXRiwOk8MQIfLZKWid9GRXxTJ47L/rh+YE9VVYkUQGIg/+hftBW pgZrSPouxWpkMPsdaBobu/EPInKb5qKscI6IG1uWJSYSjz0owSrH8ICC+fQA9gHbna8E Diog==
X-Gm-Message-State: AMke39mTHdXsEi6ui4S5Jo1j+vEaJ4+zO9amp2T3St6xvyfXulLsKDV5BtlW5nxaaBDDmpJ8N3bYiBsCRn+2pTIo
X-Received: by 10.31.142.68 with SMTP id q65mr16503731vkd.83.1487122335512; Tue, 14 Feb 2017 17:32:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Tue, 14 Feb 2017 17:31:54 -0800 (PST)
In-Reply-To: <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 14 Feb 2017 17:31:54 -0800
Message-ID: <CAKD1Yr3Bt34A0uhujKgfBwf9BHw=nNgnm1DR9o80qrNdvWJ9Mw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=001a1143703a8c05c3054887a63f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Pe_A-8YrsMJFaTA8CbgPaZBRV5g>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Jordi Palet Martinez <jordi.palet@consulintel.es>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 01:32:20 -0000

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

On Tue, Feb 14, 2017 at 11:18 AM, David Farmer <farmer@umn.edu> wrote:

> However, the Interface ID of all unicast addresses is required to be 64
> bit with the exception of the following; addresses for point-to-point links
> [RFC6164], Network-Specific Prefixes used for IPv4/IPv6 Translators
> [RFC6052], and addresses that start with the binary value 000.
>

I don't think it makes sense to cite RFC6052 here, since in RFC 6052
addresses it's not really possible to define the IID in way that makes
sense. See
https://mailarchive.ietf.org/arch/msg/ipv6/lyZl3I4rXhnmXYFCAQTRWyohfyI .

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Feb 14, 2017 at 11:18 AM, David Farmer <span dir=3D"ltr">&lt;<a href=3D=
"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div><span style=3D"font-size:12.8px">However, the Interface ID of all unica=
st addresses is required to be 64 bit with the exception of the following; =
addresses for point-to-point links [RFC6164], Network-Specific Prefixes use=
d for IPv4/IPv6 Translators [RFC6052], and=C2=A0</span><span style=3D"font-=
size:12.8px">addresses=C2=A0</span><span style=3D"font-size:12.8px">that st=
art with the binary value 000.</span></div></div></blockquote><div><br></di=
v><div>I don&#39;t think it makes sense to cite RFC6052 here, since in RFC =
6052 addresses it&#39;s not really possible to define the IID in way that m=
akes sense. See=C2=A0<a href=3D"https://mailarchive.ietf.org/arch/msg/ipv6/=
lyZl3I4rXhnmXYFCAQTRWyohfyI">https://mailarchive.ietf.org/arch/msg/ipv6/lyZ=
l3I4rXhnmXYFCAQTRWyohfyI</a> .</div></div></div></div>

--001a1143703a8c05c3054887a63f--


From nobody Tue Feb 14 18:51:57 2017
Return-Path: <john@jlc.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 045CC129507 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 18:51:55 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 4eWFHQU8XsPd for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 18:51:49 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 61C5A12957F for <ietf@ietf.org>; Tue, 14 Feb 2017 18:51:49 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 8EF8B908C88; Tue, 14 Feb 2017 21:50:55 -0500 (EST)
Date: Tue, 14 Feb 2017 21:50:55 -0500
From: John Leslie <john@jlc.net>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: To "lose the argument in the WG"
Message-ID: <20170215025055.GW10525@verdi>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MWdCiWt3B_eCNGIKEPVV_giUSYo>
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 02:51:55 -0000

   I would like to weigh in to support Pete's viewpoint.

Pete Resnick <presnick@qti.qualcomm.com> wrote:
> 
> Indeed. If Last Call results in an issue that requires a more general, 
> in-depth review, I think the presumption of that text is that it's time 
> to send it back to the WG.

   A lot of the problem is that responsible ADs don't do this often enough.

   (The <ietf> list is a _really_bad_ place to try to resolve such things.
We _always_ find WG participants calling "Foul!" and I'm sure there are
others thinking it...)

> When Last Call identifies an issue that was missed or mis-evaluated
> by the WG (perhaps due to JCK's observation about WGs that remain
> homogeneous and insulated), considerable cost and detriment should
> be expected, and is probably appropriate.

   (It's hard to fully support Pete here, but I do. "Appropriate",
however, doesn't mean "something to die for": it merely means "the
world would be a better place if it worked this way".)

> We have all seen efforts that have gone completely off the rails,
> perhaps due to bad> management choices,

   Pete certainly knows we get what we pay for, when it comes to
management skills...

> and it is a sign of pathology if that's only noticed at Last Call
> time. Yes, it should probably have been handled during the WG process
> or by interim appeals,

   We're scared of appeals, without good reason. (Heck, _I_ was scared
of them five years ago!)

   The IESG, IMHO, is far better able to process appeals than it was
five years ago; and I believe they're essentially ready to formalize
a way to deal with appeals without shooting the messenger.

> but if Last Call is where it's finally dealt with, deal with it we must.

   (Pete _is_ the eternal optimist here: there-aint-no-such-thing-as
"must".)

   But I quite agree, the world would be a better place if we dealt with
it when it comes up in last-call rather than leave it for implementors
to deal with in incompatible ways.
 
> My main complaint is that people are treating this as a game, with 
> points that are "won" or "lost".

   YES!!!!

> Telling people that they "lost" or that "it's just sour grapes" is
> obnoxious and has no place in the discussion. 

   There's the eternal optimist, again...

   Name-calling _is_ the IETF way, :^( :^(

   We've exhausted yet-another IETF Chair trying to cure people of
discourtesy so obvious that you'd get sued for it in a normal world.
I'm not fool enough to think I'll have any better luck; but I can
at least speak in support of Pete!

> If someone is abusing the process by bringing up previously 
> well-considered topics, of course the person running the Last Call has 
> to shut that down.

   Reality check!

   There isn't anybody "running last-call".

   If there were, s/he would have no tools to "shut that down".

> I can even tolerate the occasional random participant saying,
> "Pete, you know this issue was discussed at length, and you didn't
> even bother to fairly say why you think the WG came to the wrong 
> conclusion, so this is really just rehashing."

   (We ought to be able to find a way to ensure someone says that in
private email...)

   But I have a suggestion (which I guess is why I'm bothering to type
this):

   We have pretty good archive tools availabe for every IETF mail-list.

   Occasionally, I see a posting, "Please read the thread starting at

https://mailarchive.ietf.org/arch/msg/ietf/l4Mi7p-KJanEP1FuEmCDclo6REA

before posting any more on this subject."

   This is actually helpful!

   If the person has read the thread and _is_ merely repeating things
already said in that thread, s/he deserves censure, and this will be
obvious to anyone checking that thread.

   If this is new material to the person so advised, it will multiply
greatly the "clue" level going forward.

   If the person can't be bothered to read the cited thread, then a referral
to the sergeant-at-arms is justified.

   And people thinking of joining in will have the opportunity to increase
their clue level _before_ making a fool of themselves.

>> To Ted's point, indulging folk who 'did not have time' to participate 
>> earlier is frankly abusive of all those who did.
> 
> Yeah, I don't find Ted's point at all convincing either. On the other 
> hand, if the WG didn't seek out required expertise and someone does 
> notice a showstopper, that's not abusive. The WG screwed up.

   I agree with Pete here, too.

   But I don't agree it's likely the WG Chairs or participants are likely
to see it that way. Somebody will have to help them see this. The obvious
choice is the Responsible AD; but if we limit our choices of ADs to those
who agree this is their job, we might have trouble filling AD slots.

   :^( :^(

--
John Leslie <john@jlc.net>


From nobody Tue Feb 14 20:06:41 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FCA7129984; Tue, 14 Feb 2017 20:06:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpFpSLNjuPdM; Tue, 14 Feb 2017 20:06:38 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 F41D0129586; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id 65so108868934otq.2; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WIY/rdVxy09tB7PrJoES46Zjm2UJ5syfwN9D8wrDtXM=; b=N/BJgCrWjZV/WTDeAdfBmDpkky/wyepCQ/abnpWLNa9Z4goxO8+W+dnqEBETdKrw49 a+QWsEZ5F7AfDZNkarhwTpIrzKLG/7L4SEoJ99r30pHsRFx6CaESa/15H8tLSHmyfTpn /T/0b5LmZwDIKetkHZEiTAAXzgQMinodyW8Bjkfqo6SW2WWjK4NCNgbDKlO7pRZoQDdr qX1HC391LUWMetcJpWKNJp+Eu0+zfiw+EjJXvTTWgfYVee4v+kAM2ztSBJgsHESv+sYC 1tC7XK0g7qApzoTZ7EaNQnjvxac2/DmENUF8P/ueiaAJzW3szv5NIL8ppiN9+LXvL+4b xvFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WIY/rdVxy09tB7PrJoES46Zjm2UJ5syfwN9D8wrDtXM=; b=kGqJuK+AaITqa7Mx9AB+6wFwRI4CTWfZyKD+gFKqrFHKhsss1Pc4WCvcdlOkh3sWs5 uhdKbUOrYhvoIzjyu68N64rvgaol1I8k15ofkYb66wFMhapSMqeCJyoTUrCYoU57jqVP n1r814YeiISysrfmNfLD4Yqf5/8sYhj8u3NZ6sYpzQHP3KbioC9MRoK8HXkkfQvB7gJX HS6Bn3r8i2jYVdr4Ky3huNiVLabWvWYC4lWIuwBJ3Y0ZLaJua6+Pe/WhX3p8508DFMw5 ud1OuGf3MDLbQSV/LiVPFCoPVLhKiOBpdrE0B0slpt2rUBR9BsBvwYtMyxLNOuacWssl x+KQ==
X-Gm-Message-State: AMke39nYJzmEk6BPd3FxLwa+yMDbORoKkNztSb/RsJRissnMBTrhiQMdVyvAcF31AL83c7UCQn3gKnL/NoFTxQ==
X-Received: by 10.157.9.242 with SMTP id 47mr46600otz.128.1487131597225; Tue, 14 Feb 2017 20:06:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Tue, 14 Feb 2017 20:06:36 -0800 (PST)
In-Reply-To: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Tue, 14 Feb 2017 20:06:36 -0800
Message-ID: <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a113e451c964681054889cea9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ibiSjbEPkjbmCYFK6Qbtz2DEP6o>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 04:06:39 -0000

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

Hi Robert,
Section 5 Data Plane Theory of Operation has the following recommendation
on reading time value at ingress and egress:

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.


Do you find the text sufficient in providing guidance to an implementer of RTM?


Regards,

Greg


On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com> wrote:

> Reviewer: Robert Sparks
> Review result: Ready
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-mpls-residence-time-13
> Reviewer: Robert Sparks
> Review Date: 2017-02-13
> IETF LC End Date: 2017-01-17
> IESG Telechat date: 2017-03-02
>
> Summary: Ready for publication as PS
>
> Thanks for addressing my comments.
> (I still think some discussion about taking arrival and departure time
> measurements would be helpful, even if it only said "do it
> consistently so you don't indicate jitter that's not really there".)
>
>

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

<div dir=3D"ltr">Hi Robert,<div>Section 5 Data Plane Theory of Operation ha=
s the following recommendation on reading time value at ingress and egress:=
</div><div><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin=
-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre><pre class=3D"gmai=
l-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;co=
lor:rgb(0,0,0)"><br></pre><pre class=3D"gmail-newpage" style=3D"font-size:1=
3.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the=
 text sufficient in providing guidance to an implementer of RTM?</pre><pre =
class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-=
bottom:0px;color:rgb(0,0,0)"><br></pre><pre class=3D"gmail-newpage" style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">=
Regards,</pre><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;mar=
gin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre></div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Feb 13, 2017 a=
t 1:51 PM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@n=
ostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Reviewer: Robert Sparks<br>
Review result: Ready<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair. Please wait for direction from your<br>
document shepherd or AD before posting a new version of the draft.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-mpls-residence-<wbr>time-13<br>
Reviewer: Robert Sparks<br>
Review Date: 2017-02-13<br>
IETF LC End Date: 2017-01-17<br>
IESG Telechat date: 2017-03-02<br>
<br>
Summary: Ready for publication as PS<br>
<br>
Thanks for addressing my comments.<br>
(I still think some discussion about taking arrival and departure time<br>
measurements would be helpful, even if it only said &quot;do it<br>
consistently so you don&#39;t indicate jitter that&#39;s not really there&q=
uot;.)<br>
<br>
</blockquote></div><br></div>

--001a113e451c964681054889cea9--


From nobody Tue Feb 14 22:55:38 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5027129482 for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 22:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWaa88NNqDpn for <ietf@ietfa.amsl.com>; Tue, 14 Feb 2017 22:55:31 -0800 (PST)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 340B1129480 for <ietf@ietf.org>; Tue, 14 Feb 2017 22:55:31 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 95B149CF for <ietf@ietf.org>; Wed, 15 Feb 2017 06:55:30 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oH4cWTHHTi11 for <ietf@ietf.org>; Wed, 15 Feb 2017 00:55:30 -0600 (CST)
Received: from mail-vk0-f69.google.com (mail-vk0-f69.google.com [209.85.213.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 605259C3 for <ietf@ietf.org>; Wed, 15 Feb 2017 00:55:30 -0600 (CST)
Received: by mail-vk0-f69.google.com with SMTP id x75so103098151vke.5 for <ietf@ietf.org>; Tue, 14 Feb 2017 22:55:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YmQxYidt5uwIzvLW7YQfCGGiYo6eymCxwc1CXEh14Mg=; b=mPq7mXSG03n2PWg2Cp3kaEuW6P8CNoqIdVmpH6Gytqkfem7BbgVN21yblOKLMA69aB oHHrHelW1jcedgbqbKuoXDf0hwhXKLdWP7ftItImObbvGc9kdkG/gFWBGYMRBZehENYZ n2pOJKzP+bSyEy2YDWKb6dVHxYJZCxRquG4eBPXs6ap0IkJXGiMcn1FdV7us5TXAkG+s gur/fruzOBBODXvygJLCaX63zNGK81YQQA1s9HARbhqEN4R6ylpWfTWIN6WHa4JdVrvi H5n3p6kLyLjmWY6r/Sq9Oi7XOAWjIX3ccH3nVX4sn1X/vll8p+GwJAm0rKRGYC+lH03v XTdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YmQxYidt5uwIzvLW7YQfCGGiYo6eymCxwc1CXEh14Mg=; b=U8bcoFkxSq+0xYR+WE1mjYcJ6qZ86E31P3oe1xw/Jv2skVLgrV5yHCy53FxJcbpqKg 3CiuzUf5Q/E83N+ntY5jNpczi4OFcvfPvAx47ZdeWoxVrQTYm23td0kmbCGb8TU4PFFL uPV1Licni+6UmvUIqb9MHZjwfe/GaSp7EV93oWBv7elDuuI08rahvQhugG+UNueLpHwI JyeBpbY0QmNPY3cPxlRd2/jVFKuW0Z0MXYSEYZ3SowI+Ft4E5ih7zHzBn8XTKzneY9Zo WG5Tk/ZH172nzL1iJV2vGYIGUEVXKRGBtdJks6lwo39eJZ8Oq7ESqzaBunmRhTBanp3R w6GA==
X-Gm-Message-State: AMke39l+tmIMGiVkhdShBzuI1JZhMvTPP3pEUwVdIXmSF5aG8COrMioEf3dv4yupsyTyx82myCoklXc40rL3g3YdgVYh+Cmjd1dljYWwX/OGjHrc5pongaIygtqDXhT5iv0SMqnI9xiIfzS0u2E=
X-Received: by 10.31.114.133 with SMTP id n127mr16826770vkc.129.1487141729621;  Tue, 14 Feb 2017 22:55:29 -0800 (PST)
X-Received: by 10.31.114.133 with SMTP id n127mr16826764vkc.129.1487141729383;  Tue, 14 Feb 2017 22:55:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Tue, 14 Feb 2017 22:55:28 -0800 (PST)
In-Reply-To: <CAKD1Yr3Bt34A0uhujKgfBwf9BHw=nNgnm1DR9o80qrNdvWJ9Mw@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com> <CAKD1Yr3Bt34A0uhujKgfBwf9BHw=nNgnm1DR9o80qrNdvWJ9Mw@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 15 Feb 2017 00:55:28 -0600
Message-ID: <CAN-Dau1Z+_nYJMi_pNSRzpXRO8H8qV5rZApTK6m0_Eg5yCReFA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=94eb2c1497b482d6ba05488c2a10
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ud2H_KHhuy6WzTXfm6uNRd5W8vY>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Jordi Palet Martinez <jordi.palet@consulintel.es>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 06:55:34 -0000

--94eb2c1497b482d6ba05488c2a10
Content-Type: text/plain; charset=UTF-8

On Tue, Feb 14, 2017 at 7:31 PM, Lorenzo Colitti <lorenzo@google.com> wrote:

> On Tue, Feb 14, 2017 at 11:18 AM, David Farmer <farmer@umn.edu> wrote:
>
>> However, the Interface ID of all unicast addresses is required to be 64
>> bit with the exception of the following; addresses for point-to-point links
>> [RFC6164], Network-Specific Prefixes used for IPv4/IPv6 Translators
>> [RFC6052], and addresses that start with the binary value 000.
>>
>
> I don't think it makes sense to cite RFC6052 here, since in RFC 6052
> addresses it's not really possible to define the IID in way that makes
> sense. See https://mailarchive.ietf.org/arch/msg/ipv6/
> lyZl3I4rXhnmXYFCAQTRWyohfyI .
>

I conceded that is probably true for most of the IPv4-Embedded IPv6 Address
Formats in section 2.2 of RFC6052, but the /96 format seems
indistinguishable from other IPv6 addresses with embedded IPv4 addresses
described in Section 2.4.5 of this draft.

And the following text from from section 2.4.4 of this draft seems to
strongly imply that IPv6 address with embedded IPv4 addresses have an IID
length other than 64.

   As noted in Section 2.4, all Global Unicast addresses other than
   those that start with binary 000 have a 64-bit interface ID field
   (i.e., n + m = 64), formatted as described in Section 2.4.1.  Global
   Unicast addresses that start with binary 000 have no such constraint
   on the size or structure of the interface ID field.

   Examples of Global Unicast addresses that start with binary 000 are
   the IPv6 address with embedded IPv4 addresses described in
   Section 2.4.5.....

Further, the fact that RFC6052 describes it as a /96 prefix, also seems to
strongly imply a 32 bit IID length.  Now I can imagine counter arguments
along the line that IPv6 addresses with embedded IPv4 addresses don't have
IIDs either, but pulling on that string puts me at a loss to explain the
rationale of the exclusion for addresses that start with binary 000 at all.


So, I suppose we limit the statement to the /96 Network-Specific Prefixes.

Also, as I've read through RFC6052 several times, I wonder if there should
be a reference to RFC6052 added in section 2.4.5. of this draft.  Maybe
something like the follow added to the end of the paragraph for section 2.4.5
.

Additional IPv6 address that carry an IPv4 address are defined in IPv6
Addressing of IPv4/IPv6 Translators [RFC6052].

Thanks.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr"><div><br></div><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">On Tue, Feb 14, 2017 at 7:31 PM, Lorenzo Colitti <span dir=3D"lt=
r">&lt;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@goog=
le.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quot=
e">On Tue, Feb 14, 2017 at 11:18 AM, David Farmer <span dir=3D"ltr">&lt;<a =
href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div><span style=3D"font-size:12.8px">However, the Interface ID of al=
l unicast addresses is required to be 64 bit with the exception of the foll=
owing; addresses for point-to-point links [RFC6164], Network-Specific Prefi=
xes used for IPv4/IPv6 Translators [RFC6052], and=C2=A0</span><span style=
=3D"font-size:12.8px">addresses=C2=A0</span><span style=3D"font-size:12.8px=
">that start with the binary value 000.</span></div></div></blockquote><div=
><br></div><div>I don&#39;t think it makes sense to cite RFC6052 here, sinc=
e in RFC 6052 addresses it&#39;s not really possible to define the IID in w=
ay that makes sense. See=C2=A0<a href=3D"https://mailarchive.ietf.org/arch/=
msg/ipv6/lyZl3I4rXhnmXYFCAQTRWyohfyI" target=3D"_blank">https://mailarchive=
.ietf.<wbr>org/arch/msg/ipv6/<wbr>lyZl3I4rXhnmXYFCAQTRWyohfyI</a> .</div></=
div></div></div>
</blockquote></div><br>I conceded that is probably true for most of the IPv=
4-Embedded IPv6 Address Formats in section 2.2 of RFC6052, but the /96 form=
at seems indistinguishable=C2=A0from other IPv6 addresses with=C2=A0embedde=
d IPv4 addresses described in Section 2.4.5 of this draft.<div><br></div><d=
iv><div>And the following text from from section 2.4.4 of this draft seems =
to strongly imply that IPv6 address with=C2=A0embedded IPv4 addresses have =
an IID length other than 64.</div><div><br></div><div><div>=C2=A0 =C2=A0As =
noted in Section 2.4, all Global Unicast addresses other than</div><div>=C2=
=A0 =C2=A0those that start with binary 000 have a 64-bit interface ID field=
</div><div>=C2=A0 =C2=A0(i.e., n + m =3D 64), formatted as described in Sec=
tion 2.4.1.=C2=A0 Global</div><div>=C2=A0 =C2=A0Unicast addresses that star=
t with binary 000 have no such constraint</div><div>=C2=A0 =C2=A0on the siz=
e or structure of the interface ID field.</div><div><br></div><div>=C2=A0 =
=C2=A0Examples of Global Unicast addresses that start with binary 000 are</=
div><div>=C2=A0 =C2=A0the IPv6 address with embedded IPv4 addresses describ=
ed in</div><div>=C2=A0 =C2=A0Section 2.4.5.....</div></div><div><br></div><=
div>Further, the fact that RFC6052 describes it as a /96 prefix, also seems=
 to strongly imply a 32 bit IID length.=C2=A0 Now I can imagine counter arg=
uments along the line that IPv6 addresses with=C2=A0embedded IPv4 addresses=
 don&#39;t have IIDs either, but pulling on that string puts me at a loss t=
o explain the rationale of the exclusion for addresses that start with bina=
ry 000 at all. =C2=A0</div></div><div><br></div><div>So, I suppose we limit=
 the statement to the /96=C2=A0<span style=3D"font-size:12.8px">Network-Spe=
cific Prefixes.</span></div><div><span style=3D"font-size:12.8px"><br></spa=
n></div><div><span style=3D"font-size:12.8px">Also, as I&#39;ve read throug=
h RFC6052 several times, I wonder if there should be a reference=C2=A0to=C2=
=A0</span><span style=3D"font-size:12.8px">RFC6052</span><span style=3D"fon=
t-size:12.8px">=C2=A0added in section=C2=A0</span>2.4.5. of this draft.=C2=
=A0 Maybe something like the follow added to the end of the paragraph for=
=C2=A0<span style=3D"font-size:12.8px">section=C2=A0</span>2.4.5 .</div><di=
v><br></div><div>Additional=C2=A0<span style=3D"color:rgb(0,0,0);font-size:=
13.3333px">IPv6 address that carry an IPv4 address </span>are defined in IP=
v6 Addressing of IPv4/IPv6 Translators [RFC6052].</div><div><br></div><div>=
Thanks.</div><div><br></div>-- <br><div class=3D"gmail_signature">=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Em=
ail%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Network=
ing &amp; Telecommunication Services<br>Office of Information Technology<br=
>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=
=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c1497b482d6ba05488c2a10--


From nobody Wed Feb 15 00:00:52 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F201128B37 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 00:00:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IZHnLKpwRMch for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 00:00:49 -0800 (PST)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (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 D3689128AC9 for <ietf@ietf.org>; Wed, 15 Feb 2017 00:00:48 -0800 (PST)
Received: by mail-wr0-x241.google.com with SMTP id c4so4663671wrd.1 for <ietf@ietf.org>; Wed, 15 Feb 2017 00:00:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kn6yhiwGxTUBssLGgsAsu2U9Zp0YKgvLk7roxk4yJH0=; b=XXV722UtBMFmxuY6qc8OxIBV03+u/Nw4P+Zgix5fgFbRRRpP/B7s3LwtnMzE0XlLCH /VRwTI5nS2Ttnsxf/kT9IyuehQJRMUo7UzrEXIzygiVvNG2QBiqm4GR91WZfWuFm57J7 +XasFDh/Zf/D808vvwkDfC1nJT7qXCrfUpIL7oqBRpAqthTF6QlvbNImk8dvDWL7WbdF Q5av9DWpFLjUEnFq0cBdkVZ6jpOC9QhcCteQ0/eKtszy+DiELItJEt3nGLxNgYp/v9UJ dIlt5fxvAWiguj3+6xDvWVGWHiZLhfqsRZyff4zZPQNHbUCBHFtmphwa40jDKkDjdlj/ rn5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kn6yhiwGxTUBssLGgsAsu2U9Zp0YKgvLk7roxk4yJH0=; b=T7oke79FiuyAgjmBcRP6EJvvqnhOKCq0hqtD8kt6YiyKj+Rl7PBb63Ekzg9pKCBsoX cle+VILih4QfMK0Xmj+wE3DRz4vwIjFLozp2YuBpq0NhkYQn0fPPNueu6gkOJ0BNgoGk mE5cp2CtNH8FoC2giQ/B0NlFEQEd3S98ACjPcFJ/n2cmbUdlkvpZU8EVmlfaw6tfi01M II4Q5NTkVImXwtFyiWPswTqitkHauAJzq3b4/u1WQkLxCmBaTdI2LAHllB5ba6oXfJZS hLJoxsfZ872jLwFYQjYwSo+hKnl3DffT3PrUL9kf2wdH2Tf8sujljjxOtw1FSWgH7Pqr D4RQ==
X-Gm-Message-State: AMke39m41uPR969yFhvOkwiRiVuMmkDSeefEkjDnwMx3k79ue30mhMrYeum3CFnvZKuiXQ==
X-Received: by 10.223.169.164 with SMTP id b33mr30727218wrd.132.1487145647388;  Wed, 15 Feb 2017 00:00:47 -0800 (PST)
Received: from [192.168.137.219] ([176.12.228.45]) by smtp.gmail.com with ESMTPSA id y30sm3792603wrc.23.2017.02.15.00.00.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 00:00:46 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <E23DB7CC-BFDD-48B7-B655-8FD3461FDEE8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_1FFCEDFB-3924-4E00-A5B2-7EACCC438BF6"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Wed, 15 Feb 2017 10:00:35 +0200
In-Reply-To: <4965a53f-1e45-b444-1430-7d56ac413d50@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <9e0de86c-ceb3-8d05-8191-bdfd68521f00@gmail.com> <p0624060ad4c94966bc39@[99.111.97.136]> <4965a53f-1e45-b444-1430-7d56ac413d50@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aAtdpjZHnoioHjoueBMXyYCUgKs>
Cc: Randall Gellens <rg+ietf@randy.pensive.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 08:00:50 -0000

--Apple-Mail=_1FFCEDFB-3924-4E00-A5B2-7EACCC438BF6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

In case it isn=E2=80=99t widely known, there is a button on the =
datatracker page for the draft ( =
https://datatracker.ietf.org/doc/draft-ietf-something-or-other ) that =
says =E2=80=9CRequest review=E2=80=9D.

Click that and request from any of the 8 review teams.

Yoav

> On 15 Feb 2017, at 2:06, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>=20
> There is a procedure (that I thought was pretty widely known) that =
allows chairs to request early cross-are review when they think it is =
helpful.  I know that several of the review teams support this.
>=20
> Yours,
> Joel
>=20
> On 2/14/17 6:56 PM, Randall Gellens wrote:
>> At 12:18 PM +1300 2/15/17, Brian E Carpenter wrote:
>>=20
>>> 2. As a Gen-ART reviewer I've often seen drafts at IETF LC that
>>> really *need* a general, in-depth review.
>>=20
>> As a document author, I appreciate the area reviews done by GEN, SEC,
>> etc.  However, I think they would be just as useful and perhaps more
>> timely if done during WGLC (assuming the WG does a WGLC).
>>=20
>=20


--Apple-Mail=_1FFCEDFB-3924-4E00-A5B2-7EACCC438BF6
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYpAqkAAoJELhJCxUKWMyZHJMIALH4jpTyP4ruANRcNVAIJ4Ns
uXyV8qID+mBppi3OQM7EQT8CDDWgdr9oUeYR2bNvuOCcif5d9VV+A3n+5P8vN3nU
3j+fRJZfDhNJRL688ENz1JC9V9HwhWD93aBR9AUseQg8jwNm+ihZP1Ym6AAZj9Mb
flsAo2cDRHa15lNmQpLRdt+bJWs9P+HGiITXP1hSI1U3iSjZ36zFssF3QOQMrjeM
PiaxjFGh0E5ZNOgauyFx7IqARZmiP9uC3e//+6YRylic1z6gCFS4fwnHwGSBknPD
aU+Rc5yqrVTABdLvthnCE8XUxrelz67zkxkG1sFAwP30AekPUg3ylnEuugJmx2I=
=N0Dq
-----END PGP SIGNATURE-----

--Apple-Mail=_1FFCEDFB-3924-4E00-A5B2-7EACCC438BF6--


From nobody Wed Feb 15 00:22:37 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF481294CD; Wed, 15 Feb 2017 00:22:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.131
X-Spam-Level: 
X-Spam-Status: No, score=-2.131 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 f41AFD9NQ-zU; Wed, 15 Feb 2017 00:22:33 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 602F5129446; Wed, 15 Feb 2017 00:22:33 -0800 (PST)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id 2939D1B001C9; Wed, 15 Feb 2017 10:19:51 +0000 (GMT)
Message-ID: <58A33D08.4090505@erg.abdn.ac.uk>
Date: Tue, 14 Feb 2017 18:23:20 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com>
In-Reply-To: <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I6H5Cpv8O6x2K4esGJn4vqHz_XM>
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>, "tsv-area@ietf.org" <tsv-area@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 08:22:36 -0000

I have some late transport comments on this ID. The update seems to 
retain a lot of thinking that is really historical and I'd really 
encourage people to look again to making the document uptodate.

Detailed comments follow.

Best wishes,

Gorry

----
The following text strikes me as a little odd in an update:
  " Moreover, TCP implementations that follow the "slow-
    start" congestion-avoidance algorithm [CONG] typically calculate and
    cache several other values derived from the PMTU.  It may be simpler
    to receive asynchronous notification when the PMTU changes, so that
    these variables may be updated.”
- A modern TCP caches at least some path information in the TCB, why 
start with this clause at all:
  "Moreover, TCP implementations that follow the "slow start" 
congestion-avoidance algorithm [CONG] typically calculate and”
and simply replace this with something like:
"TCP implementations”?
—---

The following text also seems to not reflect a modern TCP stack:
" It is sufficient
    to treat this as any other dropped segment, and wait until the
    retransmission timer expires to cause retransmission of the segment.”
(and following 3 paras).
Could this be replaced by text that does not exclude modern 
retransmission methods:
" It is sufficient
    to treat this in the same way as any other dropped segment, and
    will be recovered by normal retransmission methods."
—
There is a block of text that describes retransmission triggered by ICMPv6.
Has this code been implemented in modern releases of TCP?:
"   Alternatively, the retransmission could be done in immediate response
    to a notification that the Path MTU has changed, but only for the
    specific connection specified by the Packet Too Big message.”
- It seems to expose a number of attack vectors that really should not 
be exposed!!
---
The discussion of NFS may still be a reasonable historic example, but to 
be current it should really refer also to NFSv4/TCP as utlising the MTU 
discovery provided by TCP, since UDP-based NFS is no longer a key 
application.
---
There is no mention that paths including tunnels can eat ICMPv6 PTB 
messages on the tunnel segment, blackholing them, which prevents 
reaching the destination.
---
I think the security consideration is naive!

This statement in particular seems to open DOS vulnerability:
"
   When a node receives a Packet Too Big message, it MUST reduce its
    estimate of the PMTU for the relevant path, based on the value of the
    MTU field in the message."
- Introdueces a significant vulnerability.  A rogue PTB message that 
reduces the PMTU to a minimum, can result in a path too small to carry 
an encapsulated packet. (Recently noted by Fernando Gont).

Moreover, other layers view ICMP messages with suspicion and have long 
noted the need to check ICMP payload and match only packets that relate 
to actual 5-tuples in use (effectively reducing vulnerability to 
off-path attacks). For example, the Guidelines for UDP, rfc5405bis, state:

" Applications SHOULD appropriately validate the payload of ICMP
    messages to ensure these are received in response to transmitted
    traffic (i.e., a reported error condition that corresponds to a UDP
    datagram actually sent by the application). …“
- clearly handling this in IP-layer tunnels can be troublesome, but 
that's a problem that should be described, not obscured.

——

I’d finally  like to add my concerns about the understatement of the 
value of PLPMTUD, which seems to not reflect the recommendations to use 
this method:
“  It defines a method for Packetization Layer Path
    MTU Discovery (PLPMTUD) designed for use over paths where delivery of
    ICMP messages to a host is not assured.”
This  seems under-stating the value and recommendations to deploy 
PLMTUD, compared with current transport-area recommendations, for 
instance, the UDP Guidelines provide much more on this important design 
consideration:

"   Packetization Layer Path MTU Discovery (PLPMTUD) [RFC4821] does not
    rely upon network support for ICMP messages and is therefore
    considered more robust than standard PMTUD.  It is not susceptible to
    "black holing" of ICMP message.  To operate, PLPMTUD requires changes
    to the way the transport is used, both to transmit probe packets, and
    to account for the loss or success of these probes.  This updates not
    only the PMTU algorithm, it also impacts loss recovery, congestion
    control, etc.  These updated mechanisms can be implemented within a
    connection-oriented transport (e.g., TCP, SCTP, DCCP), but are not a
    part of UDP, but this type of feedback is not typically present for
    unidirectional applications."

----

The examples used in the definition of  "upper layer" and "link" also 
makes this document appear as historic, rather than a new RFC!


From nobody Wed Feb 15 00:56:34 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F21A212940E; Wed, 15 Feb 2017 00:56:30 -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 autolearn_force=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 yzaFgVJF5wc3; Wed, 15 Feb 2017 00:56:28 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 E0EE7128AC9; Wed, 15 Feb 2017 00:56:27 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cdvNl-0001aD-N4; Wed, 15 Feb 2017 08:56:14 +0000
Date: Wed, 15 Feb 2017 17:56:10 +0900
Message-ID: <m237ffhlxx.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Karsten Thomann <karsten_thomann@linfre.de>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <1513056.oYYGoBVvp1@linne>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <1513056.oYYGoBVvp1@linne>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8axH7y8YWOVpjNk52S4XMh8-OVc>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, ipv6@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, jordi.palet@consulintel.es, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 08:56:31 -0000

> In my opinion the sentence should be restricted to cases where it's
> required to be 64 bit (SLAAC) and allow everything else.

thank you.

this classful bleep should have been gone a decade ago.  i can see
slaac, but for the rest, pfui.  enough already.

randy


From nobody Wed Feb 15 01:31:09 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8551F128AC9; Wed, 15 Feb 2017 01:31: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ndS1-S5W9u6R; Wed, 15 Feb 2017 01:31:06 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 0B28112947A; Wed, 15 Feb 2017 01:31:05 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 15 Feb 2017 09:31:04 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 82295D788D; Wed, 15 Feb 2017 01:31:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=SwXvuwgeeybb7r8dO9ydnUicQcU=; b= F7KwG7osoNE/27LZY/pWQLykaOV05TQeTOYb5NvWVDzbURvQn2oSPA9T0EcMBUzo zaIyZbfEa2rrLobmAwe7mErizvhBSDZB+GSBrCY47ybaQ5d1yKwMFEFkDy/bdQl6 53PraPaUx2chPvmPLjGfpb0VWGVrvToC74Ki7g5FNt0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=i1bafG5n+dmbKKlAX7V9A8j Az4cKcp5hofUexPNNA0RN5OiGxd3YKPoPDAKJcWC5gjpqAJMflkWL/d+6ZNfZfKC EQ7exaGmaQnrMeXmvsdDP2SaTvjetLRQVMmVArTAehjpwVUCx3wFZKzsuKlPiuBu a5TIviTOQLadUVqZMoCc=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 563FED788B; Wed, 15 Feb 2017 01:31:04 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 901CA8AF7EE8; Wed, 15 Feb 2017 10:31:13 +0100 (CET)
From: otroan@employees.org
Message-Id: <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_1A0B9780-2FA9-4801-BEC1-37239C67092D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Wed, 15 Feb 2017 10:31:12 +0100
In-Reply-To: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xlUi3PxiT_GZ3w1jMh4UhoBEtCc>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 09:31:07 -0000

--Apple-Mail=_1A0B9780-2FA9-4801-BEC1-37239C67092D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

>>> Brian, changing the 64 bit boundary is such a big change that I =
would
>>> claim it is far outside the scope of advancing 4291 to Internet =
standard.
>>>=20
>>=20
>> Agreed.
>=20
> Of course. The point is only that it's a parameter in the design of =
SLAAC,
> whose value is set by the address architecture.

If your statement is that we only have the 64 bit boundary because of =
SLAAC I believe you are wrong.
Can you provide any support for that view?

If I understand you correctly, your proposal is to change the fixed 64 =
bit Interface-ID length in IPv6 to a variable one, with an exception for =
links where SLAAC is used.

How do you practically suggest to do this, given the issues raised in =
https://tools.ietf.org/html/rfc7421#section-4.1 ?

Do you think this change is appropriate in the context of advancing =
4291?

Do you have implementation reports and are there not interoperability =
problems here?

Best regards,
Ole




--Apple-Mail=_1A0B9780-2FA9-4801-BEC1-37239C67092D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpB/hAAoJEL7aWKiYQt92/qoQAKJA1qH1tQqAaaxX3xnOpaN8
luD5BwT5E4aEYEfTgkqBbxfNzRolQrkbaNa+YAO2/bOGmnnhea0cxCu7eu2oSjLW
2Ki3J4psqt45klUax2tq9ZZELGAGn5jJ0FIBcMi/GvYCzVwJOhO806zRNujg/gVE
bXWhmItPLUCrP9ZTgHVPnY+5TUZl9Ii7HHj4V9PlzHzLb+BBtfAmUQ8i9LT1JiLL
aAzvoZed2vsndFezEf8WIJiHLnDGppq20cEzlqiXAJzbQmJKr8B6xn1d6+7IvKzr
B1qVc4iYo+0tWQUGwDSKuSuXU9+Eu4kVNhD1QvsvYYU5oXjSuYCydAVv8UilxAdr
ZMpH5bGCB/w88My5aBixkxkJ6bkJwjLRZVcCyED7HxI5q1QhKurN+K6gNfi6Cv7p
10w9tv8lyU/MatavVNPW7/KTHpwk17Rv12ojDENJzBXH6JcVtBSMtfAeUdrJFLfx
rALeL/Bai7QeUlqnfgd3EZqL1mZ8j1Uukuy10Y9hRTfnZSK3MEIKaBEg/TxXhR+G
Ixpa0udbTz1Twp4N0xhlxqFu5xx/f9AKI0DzMwotO6TvsMIMTBrNrzrbKDNW2g57
OQBe/ePmHOQ13V/1tl5mKjq0jaCU5Kk7mFzKoqbRYEw2TuWrJde001cgG0GWsCHo
kJdGk4dyqcOLfGqc1Dpk
=sqUw
-----END PGP SIGNATURE-----

--Apple-Mail=_1A0B9780-2FA9-4801-BEC1-37239C67092D--


From nobody Wed Feb 15 01:41:14 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8075D1294F7 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 01:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 HMGcdT-0ekuW for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 01:41:06 -0800 (PST)
Received: from bin-vsp-out-03.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 42DDC1294E6 for <ietf@ietf.org>; Wed, 15 Feb 2017 01:41:06 -0800 (PST)
X-Halon-ID: d244c837-f362-11e6-9c99-0050569116f7
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-03.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 10:40:43 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
Date: Wed, 15 Feb 2017 10:41:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p0624060dd4c9523fcf2a@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kS4joEFvn53ip72RJCfidXYsV7s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 09:41:10 -0000

Den 2017-02-15 kl. 01:39, skrev Randall Gellens:
> At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:
>
>>  Hi -
>>
>>  On 2/14/2017 2:43 PM, Randall Gellens wrote:
>>>  At 8:59 PM +0100 2/14/17, Gunnar Hellström wrote:
>>>
>>>>   Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>>>>
>>>>>   Hi -
>>>>>
>>>>>   On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>>>>   At 11:01 AM +0100 2/14/17, Gunnar Hellström wrote:
>>>>>>
>>>>>>>    My proposal for a reworded section 5.4 is:
>>>>>>>
>>>>>>>    5.4.  Unusual language indications
>>>>>>>
>>>>>>>    It is possible to specify an unusual indication where the 
>>>>>>> language
>>>>>>>    specified may look unexpected for the media type.
>>>>>>>
>>>>>>>    For such cases the following guidance SHALL be applied for the
>>>>>>>   humintlang attributes used in these situations.
>>>>>>>
>>>>>>>    1.    A view of a speaking person in the video stream SHALL, 
>>>>>>> when it
>>>>>>>   has relevance for speech perception, be indicated by a 
>>>>>>> Language-Tag
>>>>>>>   for spoken/written language with the "Zxxx" script subtag to 
>>>>>>> indicate
>>>>>>>   that the contents is not written.
>>>>>>>
>>>>>>>    2.    Text captions included in the video stream SHALL be 
>>>>>>> indicated
>>>>>>>   by a Language-Tag for spoken/written language.
>>>>>>>
>>>>>>>    3.    Any approximate representation of sign language or
>>>>>>>   fingerspelling in the text media stream SHALL be indicated by a
>>>>>>>   Language-Tag for a sign language in text media.
>>>>>>>
>>>>>>>    4.    When sign language related audio from a person using sign
>>>>>>>   language is of importance for language communication, this 
>>>>>>> SHALL be
>>>>>>>   indicated by a Language-Tag for a sign language in audio media.
>>>>>>
>>>>>>   [RG] As I said, I think we should avoid specifying this until 
>>>>>> we have
>>>>>>   deployment experience.
>>>>>   ...
>>>>>
>>>>>   From a process perspective, it's far easier to remove constraints
>>>>>   as a specification advances than it is to add them.
>>>>   I agree. It is often better to specify normatively as far as you can
>>>>  imagine, so that interoperability and good functionality is achieved.
>>>>  Stopping halfway and have MAY in the specifications creates
>>>>  uncertainty and less useful specifications.
>>>
>>>  My reading of what Randy says is the opposite of Gunnar's. In my
>>>  reading, Randy points out that is it easier to remove the SHOULD 
>>> NOT in
>>>  the future then it is to change the meaning of the combinations or
>>>  switch to a different mechanism.
>>>
>>>  In my experience, it's better to specify only what we know we need and
>>>  what we know we understand.  Speculative specifications "as far as you
>>>  can imagine" more often lead to interoperability problems, unnecessary
>>>  complexity, limitations on what's needed in the future, and divergent
>>>  implementations.
>>
>>  I think the difference in your positions comes down to
>>
>>    (1) your respective notions of "what we know we need and what we
>>        know we understand";
>>
>>    (2) whether you believe that the interoperability and conformance
>>        consequences of removing a "SHOULD NOT" could be the same
>>        as those merely retaining a "MUST" or "SHALL" - this determines
>>        whether Randy G.'s proposal provides a path for some future
>>        revision to mandate (if deployment experience substantiates the
>>        need/understanding) the behavior proposed by Gunnar. That path
>>        is not at all obvious to me.
>
> The purpose of the draft is to enable the two endpoints of a real-time 
> communication session to agree which languages and media to use for 
> interactive communication.  We have a mechanism of adding language 
> tags to media stream negotiations.  In most cases, the language and 
> media modality are an obvious fit.  There are combinations of media 
> and language where the meaning is not so obvious, specifically, signed 
> language tags with a audio or text, and non-signed language tags with 
> video.  My proposal is that we say offerer SHOULD NOT send such 
> combinations and answerer MAY ignore language. This allows future 
> specifications for the underlying uses Gunnar wants (such as real-time 
> subtitles in video and signed equivalents in text).  Such future 
> specifications could define a use for the language and media 
> combinations and remove the SHOULD NOT send and MAY ignore, or could 
> define a new mechanism.  I don't think we know enough now to dictate 
> what the solution should be.
We have a fresh example from our own discussions in the SLIM group how 
unfortunate it is to not be sufficiently explicit in the first edition 
of a standard. The SDP Lang attribute in RFC 4566, where you (Randall) 
say it is intended for specifying a set of languages that all must be 
used in a session, while I say that it is intended for negotiation of at 
least one initial language. By having that uncertainty in a 
specification that has been published makes it very hard to sharpen up 
the specification afterwards because it would possibly make some 
implementations non conformant. And it makes potential implementors 
hesitant to use the current specifications, as it was with the SLIM work.

For 5.4.

I am OK with modifying from my latest proposal, but we need to be specific.
I am also OK with reducing the SHALLs to SHOULDs as Addison requested.

The situation is not that we lack knowledge. Here is what we know about 
the 4 cases of "unusual" indications:

1. View of the speaker in video. Very important for speech perception. 
Quality requirements are documented in ITU-T H-series Supplement 1. Of 
real use only as a complement to the same spoken language in audio. Now, 
when we know about the Zxxx notation for non-written, we also have a 
good way of specifying it precisely.
This case was also described in section 5.2 already.

2. Text captions in the video stream.
This can be either text merged into video and communicated as true part 
of the video image, or it can be a text component of a multimedia 
system, as MPEG-4, declared in SDP as m=video.
It has been used in some videophone products, but I have not seen it 
used lately.
It is a clearly defined case, and we can specify coding for it, but we 
do not at the moment know if it will be important to specify it.

3. Sign language or fingerspelling in the text stream.
I have seen a product using it for claimed sign language conversation. 
It is also in use in the simple text form with words in capitals 
approximately representing signs between persons involved in preparation 
of sign language productions and translations. But in that case it is in 
a session where they agree in other ways to start using the text stream 
for that purpose. So I think we can say that this is rare, and its use 
can be agreed by other means between the users. Still it is a clearly 
defined case.

4. Audio from signing person related to sign language. This is more 
vague than the others.  It may be a person signing in video and adding 
spoken words in audio to signing, but influenced by the word order and 
grammar of sign language with some ambition to make it reasonably 
understandable for both deaf and hearing participants. There are even 
some spoken words created from sign language that are commonly used by 
hearing persons in such situations. But for that case I anyway think it 
is better to define the audio part as the spoken language it is derived 
from, because of its intention to be understandable for hearing persons. 
All other variants I can imagine are even closer to the spoken language 
and should be specified with spoken language tag. If we only want to 
have the audio stream established to hear the background in the signing 
situation, then we should not specify language use of the audio stream.
Even if we know what sign language tag in audio stream would be, it may 
be just as good to leave it undefined.
------------------------------------------------------------------------------------------------------------------------------------------------
So, new proposal:

5.4.  Unusual language indications

    It is possible to specify an unusual indication where the language
    specified may look unexpected for the media type.

    For such cases the following guidance SHOULD be applied for the
   humintlang attributes used in these situations.

    1.    A view of a speaking person in the video stream SHOULD, when it
   has relevance for speech perception, be indicated by a humintlang 
attribute with a Language-Tag
   for a spoken/written language with the "Zxxx" script subtag to indicate
   that the contents is not written.

    2.    Text captions included in the video stream SHOULD be indicated
   by a humintlang attribute with Language-Tag for spoken/written language.

    3.    A Language-Tag for a sign language specified in a humintlang 
attribute for a text stream MAY be interpreted as use of an approximate 
representation of sign language or fingerspelling in the text media 
stream. The use of such representation is rare and usually conveniently 
agreed by other means between the users during an established session. 
Common support of this indication SHOULD NOT be assumed or required.

    4.    A Language-Tag for a sign language specified in a humintlang 
attribute for an audio stream SHOULD NOT be indicated and MAY be ignored 
on reception. Any use of spoken words or spoken language in the audio 
stream SHOULD, when it can be of importance for language communication, 
be indicated by the corresponding Language-Tag for spoken language in a 
humintlang attribute for the audio stream.




Gunnar


-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 15 02:07:55 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39CEA129A0F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 6Ks1kmBP-hY3 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:07:51 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 2206B1294FD for <ietf@ietf.org>; Wed, 15 Feb 2017 02:07:50 -0800 (PST)
X-Halon-ID: 9523edf9-f366-11e6-a131-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 11:07:39 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: "Phillips, Addison" <addison@lab126.com>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, "ietf@ietf.org" <ietf@ietf.org>, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <ba7f397b-59ae-c549-cd1a-e22e1b73b3c1@omnitor.se>
Date: Wed, 15 Feb 2017 11:07:46 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x-twgWVRUG0au0PmJjdGEc3tLbE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 10:07:53 -0000

Addison,

Den 2017-02-14 kl. 21:39, skrev Phillips, Addison:
> I have some allergy to the SHALL language: there is no way to automatically determine conformance. Many language tags represent nonsensical values, due to the nature of language tag composition. Content providers need to use care in selecting the tags that they use and this section is merely pointing out good guidance for tag selection, albeit in a heavy-handed way. BCP47 RFC 5646 Section 4.1 [1] already provides most of this guidance and a reference to that source might be useful here, if only because that document requires it:
>
> <quote>
>     Standards, protocols, and applications that reference this document
>     normatively but apply different rules to the ones given in this
>     section MUST specify how language tag selection varies from the
>     guidelines given here.
> </quote>
>
> I would suggest reducing the SHALL items to SHOULD.
Accepted.
That also opens up for another use we have discussed before but been 
advised to not use. That is to indicate use of written language by 
attaching a script subtag even if the script subtag we use is suppressed 
by BCP 47. We can dro that need however, with the use of the Zxxx script 
subtag for non-written, and clearly include that usage in our 
specification as required from BCP 47.
>
> I'm not sure what #2 really means. Shouldn't text captions be indicated by the written language rather than the spoken language? And I'm not sure what "spoken/written language" means.
#2 was: "

2.    Text captions included in the video stream SHALL be indicated
by a Language-Tag for spoken/written language."

Yes, the intention is to use written language in the video stream. There 
are technologies for that.
Since the language subtags in the IANA registry are combined for spoken 
languages and written languages, I call them Language-Tags for 
spoken/written language.
It would be misleading to say that we use a Language-Tag for a written 
language, because the same tag could in another context mean a spoken 
language.
Since we have the script subtag Zxxx for non-written, we do not need to 
construct an explicit tag for the written language tag, it should be 
sufficient with our specification of the use in our case.

In my latest recent proposal, I still have a very similar wording. Since 
you had problems understanding it, there might still be a need to tune 
it. Can you propose wording?
This is the current proposal:

"   2.    Text captions included in the video stream SHOULD be indicated
   by a humintlang attribute with Language-Tag for spoken/written language.
"

Regards
Gunnar
>
> Regards,
>
> Addison
>
> Addison Phillips
> Principal SDE, I18N Architect (Amazon)
> Chair (W3C I18N WG)
>
> Internationalization is not a feature.
> It is an architecture.
>
> [1] https://tools.ietf.org/html/bcp47#section-4.1
>
> -----Original Message-----
> From: SLIM [mailto:slim-bounces@ietf.org] On Behalf Of Gunnar Hellström
> Sent: Tuesday, February 14, 2017 11:59 AM
> To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>; ietf@ietf.org; slim@ietf.org
> Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
>
> Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>
>> Hi -
>>
>> On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>> At 11:01 AM +0100 2/14/17, Gunnar Hellström wrote:
>>>
>>>>   My proposal for a reworded section 5.4 is:
>>>>
>>>>   5.4.  Unusual language indications
>>>>
>>>>   It is possible to specify an unusual indication where the language
>>>> specified may look unexpected for the media type.
>>>>
>>>>   For such cases the following guidance SHALL be applied for the
>>>> humintlang attributes used in these situations.
>>>>
>>>>   1.    A view of a speaking person in the video stream SHALL, when it
>>>> has relevance for speech perception, be indicated by a Language-Tag
>>>> for spoken/written language with the "Zxxx" script subtag to
>>>> indicate that the contents is not written.
>>>>
>>>>   2.    Text captions included in the video stream SHALL be indicated
>>>> by a Language-Tag for spoken/written language.
>>>>
>>>>   3.    Any approximate representation of sign language or
>>>> fingerspelling in the text media stream SHALL be indicated by a
>>>> Language-Tag for a sign language in text media.
>>>>
>>>>   4.    When sign language related audio from a person using sign
>>>> language is of importance for language communication, this SHALL be
>>>> indicated by a Language-Tag for a sign language in audio media.
>>> [RG] As I said, I think we should avoid specifying this until we have
>>> deployment experience.
>> ...
>>
>>  From a process perspective, it's far easier to remove constraints as a
>> specification advances than it is to add them.
> I agree. It is often better to specify normatively as far as you can imagine, so that interoperability and good functionality is achieved.
> Stopping halfway and have MAY in the specifications creates uncertainty and less useful specifications.
>
> Furthermore, in this case we succeeded to discuss and sort out the interpretation of the unusual combinations.
> I am very glad that we sorted out the difference between 1 and 2, and they are both real-life cases.
>
> 3 is not at all common, but I have seen products claiming to work for real-time communication with sign representation in text. So it is good to have it settled.
>
> 4. Is a bit more far fetched and may cause some questioning if there are real cases, and where the line should be drawn between indicating a spoken languge in the audio stream and indicating a sign language in the audio stream.
> As I wiew it now, this combination will be very rare, but it is anyway good to be specific and normative about its coding.
>
> Gunnar
>
>> Randy
>>
> --
> -----------------------------------------
> Gunnar Hellström
> Omnitor
> gunnar.hellstrom@omnitor.se
> +46 708 204 288
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 15 02:18:46 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF48C1296AF for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qRACteTaP26F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:18:43 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 457601294BD for <ietf@ietf.org>; Wed, 15 Feb 2017 02:18:43 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 15 Feb 2017 10:18:43 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B34EED788F; Wed, 15 Feb 2017 02:18:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=zkmW95BAHZTQ38zdC4Z9FXRUOkM=; b= ZkVp6aiHVam30aB1ce548GDTFd8bX2R5f9mriiUh6Geii+X/U7qOD+6i44b8rs32 4uNoM/38aT+z4iTY3ICFqWmNLqoEVW2JAe7JLxCR9SGpaIncR7bhDhN07IFiiDZw c08+uylAezffO9GI5V0S5n/pP8D1WIKmFbxdpnGfa50=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=Ls20WnHDSL0fN1iotjzfsqJ G6H7soRlSEGTNtAE6Uq54dA2MGq3u0M8OA7Zi3Pdg9FamO93tv5R7GukNklHzRdz h8nxp1csF8xrB1yxpDJL5C6CgWnR7CUuU+f5zgRt7AN4WdY201p0+HlBOz34yDhq wlSxqCHcheVOj1Rogev8=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3E61FD788B; Wed, 15 Feb 2017 02:18:42 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 5FA048B05D00; Wed, 15 Feb 2017 11:18:51 +0100 (CET)
From: otroan@employees.org
Message-Id: <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_31A68F48-1047-4EEE-AE77-1A1CD6FF8A5C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Wed, 15 Feb 2017 11:18:50 +0100
In-Reply-To: <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <D2D907D5-84B4-43BB-9103-F87DA9F122EB@employees.org> <33DC7B74-D240-4FF2-A8FF-C9C5A66809EE@qti.qualcomm.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KDsP2aI2jhXNrgvcZCCnDzU8bXI>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 10:18:45 -0000

--Apple-Mail=_31A68F48-1047-4EEE-AE77-1A1CD6FF8A5C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


>>> Ole, it is true that we write in English, and there is always room =
for
>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>=20
>>> But in this case we have a demonstrated difference in how people
>>> understand the existing text.  When we have such a demonstrated
>>> difference, we have an obligation to address it.
>>=20
>> This particular issue has caused no interoperability issue,
>=20
> May I ask what's the data that support this statement?

=46rom the shepherd's writeup:
   IPv6 is implemented on most platforms (hosts, routers, servers, =
etc.),
   including proprietary and open source.  A list of products that have
   received the IPV6 Ready logo can be found at:

   https://www.ipv6ready.org/db/index.php/public/?o=3D4

> You certainly have no way of knowing this, or whether interoperability
> issues may arise in the future.

Yes, we do know if our protocols have interoperability issues.
Have you implemented RFC2460? I have. So have many others on this list.
In the context of implementing 2460 there just is no ambiguity and this =
issue will never arise.

What you are talking about is something else. You are talking about the =
hypothetical "What if someone standardised something new in the future?"

Ole

--Apple-Mail=_31A68F48-1047-4EEE-AE77-1A1CD6FF8A5C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpCsLAAoJEL7aWKiYQt92w7kP/jBRYUf08J0ZzDH93oS/5PY5
JHFd0/OR1+L+A5CLUbl9aq7x+xjlxsLLJd6zrh98Rp9PnRTh+RclDZkspeSDtwx/
n2YVdcuZiC41we39025o42eoi+5AyCiDysOcqhcu18esZGsmLxqLw2xhFQlynNCT
LkmQCwDIIv9Ggz2k+BWUuwuVi5RSJJmnRzEUXGDxN2KsoczJl8vKZjYUBeRYTE12
LgfZqWyqxm+3MjCVdXoi5vgG/ColJKP0EZetrIG2esZS8xUrsC8pCZaU+VkbBYcp
Vnr+tWWDSezStLuOVVT68ZihouM4cUFUjrN9EjKCZvT5LaoGygt0mXjqq6peGnHc
pJ5fh/fALo9KzYUHwB4jGpbLPQuQ35Ogd/BArHMCWUcT6ctUvKx+LToZqSlnrSrK
wenUDV8XW7fujuhSW27Q0wZt+xnvrOhsPm+rWAH24bF8LR43Nw+rVvx9PoCl/A2P
3MAMnx1tlVQZdCtF7qMrpUloJ2ldMSmkv1RUeBXl0TpKvJ5KkycrLcSNd/OdxRYf
xpo5EkQIvG1j9qxWnzgpbQgaf5rbALZgHNHUcfjmlBk711UYu7cybbGHM437xFIZ
WKb21s9NuxucbLcPsmHvJ9cYnVxl4KvtByR8WG9P+oqrLebuqOOVPehqMd4BRibt
xupqyBrKQyH5jCx++rdT
=LFIF
-----END PGP SIGNATURE-----

--Apple-Mail=_31A68F48-1047-4EEE-AE77-1A1CD6FF8A5C--


From nobody Wed Feb 15 02:54:30 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA9F12952F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:54:28 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4-LG13cOjE9j for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 02:54:28 -0800 (PST)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 A4AE6129416 for <ietf@ietf.org>; Wed, 15 Feb 2017 02:54:26 -0800 (PST)
Received: by mail-ua0-x22f.google.com with SMTP id 96so103342101uaq.3 for <ietf@ietf.org>; Wed, 15 Feb 2017 02:54:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ysrgyj+7vGyISwXR9h/zJsI5NKkeI80/cDUt/NxRMTI=; b=beuIDdypNaE6ltu+cByfTllNZVw8qlGZua/w3vriuKQ+yUJNPNmh0/b73/OGmS3rVU r6re/ll524rshFnaU+D0jvImZEj/R6pd70jgtScGWkCU1JmBofo8/Kta+GVMEyrBGGuv Mb0KfftQo91dt8dDE8K70ALK3Q3lCrDA2tEdG0g2h7i9475w4vG23wOK+vsWViyauGui E6jZpj9sOhPqyLubGqP7TSWJuotwIenvZOGgjzXRTNXNCXgswrNhBO/LMZJmuXb4O3mt +yh4ugTARc6nxXDm/DPZB+/6x2Mhv9Rr2hiDC0yJAhu1r7AkCKyJWu6r/lhW+xAW9oMb nNbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ysrgyj+7vGyISwXR9h/zJsI5NKkeI80/cDUt/NxRMTI=; b=R5DRcRTHcoHDLNO7AlQkkyXiS+PdvtDTRJNFmCQAv1E3cha8tWu95ehTuaLQpDc/8q GjsONE/l8jb5+HYK8RfBe/a17lP0ROdqDEATzdkHMgYZukD/aAhUZZwvhpS0U5tJFUu+ zoBBD+iEYriqlUmpLHlPRJSFtPAaiqUn24aQtxRM8vWgOJYuJadIqM5EvEU2vjSbZXT7 Zf3X0tRd/yIMfjLO2cQjp1gdo7MHku3ASwD+wC5cKX9lcJoihLPwrGYbehyyJSCO4nMy bB8sdQThNdq5A0QZllTjnUdcpWueVIGw4TcpADM55EHeBUh9GVZocHxXPr5TKwbRskeZ ap2w==
X-Gm-Message-State: AMke39nrpygmtNN+nZFla9YQWXT11G5Eog92/SQreDQuesIEMfPCXVASmeCoBqWo9Lx1hw1Hnsyv0bjf9JtU/RCK
X-Received: by 10.159.49.66 with SMTP id n2mr18450501uab.72.1487156065541; Wed, 15 Feb 2017 02:54:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 15 Feb 2017 02:54:04 -0800 (PST)
In-Reply-To: <CAN-Dau1Z+_nYJMi_pNSRzpXRO8H8qV5rZApTK6m0_Eg5yCReFA@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com> <CAKD1Yr3Bt34A0uhujKgfBwf9BHw=nNgnm1DR9o80qrNdvWJ9Mw@mail.gmail.com> <CAN-Dau1Z+_nYJMi_pNSRzpXRO8H8qV5rZApTK6m0_Eg5yCReFA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 15 Feb 2017 02:54:04 -0800
Message-ID: <CAKD1Yr3M8n7a5uFTiHmqv5TZj-7ShChRSSseHwYyjwC0X-hREA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=f403045e2fee03697a05488f81d4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/A2xTG-WYNoHDAWLhp9QyLAnO7Io>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Jordi Palet Martinez <jordi.palet@consulintel.es>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 10:54:29 -0000

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

On Tue, Feb 14, 2017 at 10:55 PM, David Farmer <farmer@umn.edu> wrote:

> I conceded that is probably true for most of the IPv4-Embedded IPv6
> Address Formats in section 2.2 of RFC6052, but the /96 format seems
> indistinguishable from other IPv6 addresses with embedded IPv4 addresses
> described in Section 2.4.5 of this draft.
>

Could we say that the IID is 64 bits long "for all addresses except those
that start with binary 000, and those that embed IPv4 addresses [RFC 6052]"?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Feb 14, 2017 at 10:55 PM, David Farmer <span dir=3D"ltr">&lt;<a href=3D=
"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I conceded that=
 is probably true for most of the IPv4-Embedded IPv6 Address Formats in sec=
tion 2.2 of RFC6052, but the /96 format seems indistinguishable=C2=A0from o=
ther IPv6 addresses with=C2=A0embedded IPv4 addresses described in Section =
2.4.5 of this draft.</div></div></blockquote><div><br></div><div>Could we s=
ay that the IID is 64 bits long &quot;for all addresses except those that s=
tart with binary 000, and those that embed IPv4 addresses [RFC 6052]&quot;?=
</div></div></div></div>

--f403045e2fee03697a05488f81d4--


From nobody Wed Feb 15 03:14:23 2017
Return-Path: <sthaug@nethelp.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A26A012952F; Wed, 15 Feb 2017 03:14:21 -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 autolearn_force=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 R5IAOD9B002s; Wed, 15 Feb 2017 03:14:19 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with ESMTP id A92A0129446; Wed, 15 Feb 2017 03:14:19 -0800 (PST)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 4A06AE6065; Wed, 15 Feb 2017 12:14:17 +0100 (CET)
Date: Wed, 15 Feb 2017 12:14:17 +0100 (CET)
Message-Id: <20170215.121417.74676483.sthaug@nethelp.no>
To: lorenzo@google.com
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: sthaug@nethelp.no
In-Reply-To: <CAKD1Yr3M8n7a5uFTiHmqv5TZj-7ShChRSSseHwYyjwC0X-hREA@mail.gmail.com>
References: <CAKD1Yr3Bt34A0uhujKgfBwf9BHw=nNgnm1DR9o80qrNdvWJ9Mw@mail.gmail.com> <CAN-Dau1Z+_nYJMi_pNSRzpXRO8H8qV5rZApTK6m0_Eg5yCReFA@mail.gmail.com> <CAKD1Yr3M8n7a5uFTiHmqv5TZj-7ShChRSSseHwYyjwC0X-hREA@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N27iEewbOidK1EnifN4aJ29Zj98>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 11:14:21 -0000

> > I conceded that is probably true for most of the IPv4-Embedded IPv6
> > Address Formats in section 2.2 of RFC6052, but the /96 format seems
> > indistinguishable from other IPv6 addresses with embedded IPv4 addresses
> > described in Section 2.4.5 of this draft.
> >
> 
> Could we say that the IID is 64 bits long "for all addresses except those
> that start with binary 000, and those that embed IPv4 addresses [RFC 6052]"?

This is demonstrably false (there are lots of IPv6 interfaces with for
instance /124 or /126 masks, among others). I don't expect all of these
IPv6 interfaces to be changed to /64 even if an RFC says so.

So the question is, what do you gain by stating this in an RFC?

(I know, the discussion is old and I don't expect any views to change.
It stills seems wrong to publish an RFC with such an obviously wrong
statement.)

Steinar Haug, AS2116


From nobody Wed Feb 15 04:33:06 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DD2E1295C9 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:33:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 o86nGSetMCjR for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:33:03 -0800 (PST)
Received: from bin-vsp-out-03.atm.binero.net (bin-mail-out-05.binero.net [195.74.38.228]) (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 82191127735 for <ietf@ietf.org>; Wed, 15 Feb 2017 04:33:03 -0800 (PST)
X-Halon-ID: e2eb9301-f37a-11e6-9c99-0050569116f7
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-03.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 13:32:57 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA registrations)
To: ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
Date: Wed, 15 Feb 2017 13:32:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dv7vXr39boq0X2r3r1Icsqj5K-A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 12:33:05 -0000

in issue 8, I propose:

(Look in the edited draft -06g that I attached some days ago for how the 
proposal appears in the text )


------------------------------------------------------------------------------------------------------------ 


8. Include more fields for attribute registration from 4566bis

Section 6 has the form for attribute registration by IANA. There are a 
couple of fields missing that will be important for use of the 
specification in the WebRTC environment.  Include these fields if that 
is allowable according to current IANA procedures and if that does not 
delay the publication of this draft. These fields are needed for use of 
text media in WebRTC.

Change:

In two locations from:
     "Usage Level:  media"

to:

     "Usage Level:  media, dcsa(subprotocol)"

Insert in two locations in the registration forms:
"Mux Category: NORMAL"
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------

I checked in current IANA registrations, and found that all SDP 
attribute registrations now include the "Mux Category".

So, I assume that we are obliged to do so also and hope that we can 
agree on that.
As far as I understand the logic, we should specify NORMAL.

I saw no trace yet of registrations of  "Usage Level: dcsa(subprotocol)"

I would like to get advice from someone with insight in the SDP 
attribute registration and the status of the dsca(subprotocol) value on 
how we should proceed in order to get the dsca(subprotocol)  included in 
a smooth way without causing exessive delay.


Regards
Gunnar


From nobody Wed Feb 15 04:45:21 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDE9212946F for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:45:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 iVnjxVRYHH_X for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 04:45:17 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 310081295DF for <ietf@ietf.org>; Wed, 15 Feb 2017 04:45:15 -0800 (PST)
X-Halon-ID: 97b43a5c-f37c-11e6-af90-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 13:45:12 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA registrations)
To: ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se> <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <4cfebe3f-1bf9-c5dd-f736-a503a3f608c9@omnitor.se>
Date: Wed, 15 Feb 2017 13:45:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7NbpMFQx_BSIvj5SYCYwE94Z0XA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 12:45:20 -0000

More info below.


Den 2017-02-15 kl. 13:32, skrev Gunnar Hellström:
> in issue 8, I propose:
>
> (Look in the edited draft -06g that I attached some days ago for how 
> the proposal appears in the text )
>
>
> ------------------------------------------------------------------------------------------------------------ 
>
>
> 8. Include more fields for attribute registration from 4566bis
>
> Section 6 has the form for attribute registration by IANA. There are a 
> couple of fields missing that will be important for use of the 
> specification in the WebRTC environment.  Include these fields if that 
> is allowable according to current IANA procedures and if that does not 
> delay the publication of this draft. These fields are needed for use 
> of text media in WebRTC.
>
> Change:
>
> In two locations from:
>     "Usage Level:  media"
>
> to:
>
>     "Usage Level:  media, dcsa(subprotocol)"
>
> Insert in two locations in the registration forms:
> "Mux Category: NORMAL"
> --------------------------------------------------------------------------------------------------------------- 
>
> --------------------------------------------------------------------------------------------------------------- 
>
>
> I checked in current IANA registrations, and found that all SDP 
> attribute registrations now include the "Mux Category".
>
> So, I assume that we are obliged to do so also and hope that we can 
> agree on that.
> As far as I understand the logic, we should specify NORMAL.
>
> I saw no trace yet of registrations of  "Usage Level: dcsa(subprotocol)"
>
> I would like to get advice from someone with insight in the SDP 
> attribute registration and the status of the dsca(subprotocol) value 
> on how we should proceed in order to get the dsca(subprotocol)  
> included in a smooth way without causing exessive delay.
I found in 
https://tools.ietf.org/html/draft-ietf-mmusic-data-channel-sdpneg-11#section-8.3 
that the registration of dcsa(subprotocol)  seems to require a specific 
actual subprotocol. That is further away in time, and if that conclusion 
is right, we need to include MUX Category but exclude "Usage Level: 
dcsa(subprotocol)"  from the registration.
>
>
> Regards
> Gunnar
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 15 05:06:21 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5153D129573; Wed, 15 Feb 2017 05:06:17 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: <gen-art@ietf.org>
Subject: Review of draft-freytag-lager-variant-rules-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148716397728.17360.7152265828165061314.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 05:06:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sY1CBDup_e5XwwtwxgFk1aCypcY>
Cc: draft-freytag-lager-variant-rules.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 13:06:17 -0000

Reviewer: Francis Dupont
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-freytag-lager-variant-rules-??
Reviewer: Francis Dupont
Review Date: 2017-02-15
IETF LC End Date: 2017-02-14
IESG Telechat date: 2017-02-16

Summary: Ready with Issues

Major issues: None

Minor issues: As I explained in my review of the 02 version this
document introduction should warn that the RFC 7940 must be read
before...

Nits/editorial comments: 



From nobody Wed Feb 15 05:45:02 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50DB11294D7 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 05:45:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 zYqYlEr8BRCt for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 05:44:58 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 8FD281295E2 for <ietf@ietf.org>; Wed, 15 Feb 2017 05:44:58 -0800 (PST)
X-Halon-ID: ee58662c-f384-11e6-af90-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 14:44:52 +0100 (CET)
Subject: Re: [Slim] Last Call: <draft-ietf-slim-negotiating-human-language-06.txt> (Issue 5, section 5.3 )
To: Paul Kyzivat <paul.kyzivat@comcast.net>, slim@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
References: <20170213105355.665a7a7059d7ee80bb4d670165c8327d.1c694c05b8.wbe@email03.godaddy.com> <d0a78f56-9723-0190-f121-cefa23c2b444@comcast.net>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <324a9954-8b52-598d-e1c8-3c1bc17dea38@omnitor.se>
Date: Wed, 15 Feb 2017 14:44:52 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <d0a78f56-9723-0190-f121-cefa23c2b444@comcast.net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GJq86Cz5u1oOTrnJHnX9j1uz8hM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 13:45:01 -0000

Den 2017-02-14 kl. 00:44, skrev Paul Kyzivat:

> On 2/13/17 12:53 PM, Doug Ewell wrote:
>
>> Gunnar, who participated extensively in the SLIM WG, appears to be
>> attempting to re-introduce a mechanism to indicate preference of
>> modality which was considered and rejected multiple times by the WG.
>>
>> WG rejection of Gunnar's previous proposals to do this was based on
>> reluctance to try to solve this particular problem in the first version
>> of the spec, not on any of the specific mechanisms proposed to solve the
>> problem. Proposing a new or modified mechanism during IETF LC appears to
>> be an attempt to rehash an argument made, but not won, in the WG.
>>
>> If this concerns a different issue, not merely a different way of
>> approaching it, please accept my apology and explain more clearly how it
>> is different.
You are partly right, but the new proposal concerns more issues and is 
suggested to be a simplified solution to them.

The proposal adds media level influence to the asterisk humintlang 
attribute value parameter. In draft -06 the asterisk is said to be a 
media level parameter. But it does not change any influence on media 
level depending on which media or humintlang attribute you append it to. 
It just has session influence. That clearly indicates that with the 
current definition, the asterisk parameter  is misplaced.

It can also be seen that it has quite vague and unprecise influence on 
the session level.

This is the essential part of section 5.3 where this parameter is defined:

"The mechanism for indicating this preference is that, in an offer, if
    the last character of any of the 'humintlang-recv' or 'humintlang-
    send' values is an asterisk, this indicates a request to not fail the
    call (similar to SIP Accept-Language syntax).  Either way, the called
    party MAY ignore this, e.g., for the emergency services use case, a
    PSAP will likely not fail the call."

So, the lack of the parameter everywhere in the SDP MAY be seen as a 
request to reject the call, but that request may be ignored.

The real effect of this parameter is therefore in fact a preference. In 
order to motivate its existence on the media level, I proposed the 
extension of its meaning with an influence depending on on which 
humintlang attribute(s) it is attached.
Since the lack of the parameter apparently indicates a stronger 
preference for getting the call through, I suggest that the placement of 
an asterisk on a specific humintlang attribute indicates lower 
preference for matching that language/modality/direction versus some 
other language/modality combination specified for the same direction.
The one who want the call rejected if the highest preferred 
language/modality could not be matched is likely less interested in 
providing lower preferenced alternatives, so the session influence can 
be maintained.

By that we both sort out inconsistencies with the use of the asterisk 
and add value to it that will enable much more satisfied users and more 
calls going through.
And the solution is simpler than all earlier proposals and much more 
simple than not acting on the addressed issues now.

My proposed wording is available in issue 5 in my initial mail from Feb 13.


  Regards
Gunnar

>
> Gunnar's comment makes multiple points. You have highlighted one of 
> them and ignored the others.
>
> Even if you reject that one, consider the others. Notably:
>
> - The text needs to be improved simply to properly explain and define 
> the syntax related to the "*" as you intend to use it.
>
> - the use of the "*" to indicate what it does is confusing. It is 
> using a media level attribute "parameter" to signify a session level 
> property. This has been brought up before, but simply rejected without 
> (IMO) adequate justification. There seems to be some love for this 
> particular syntax. ISTM that in part Gunnar is trying to adapt this 
> syntax so that it both makes sense as a media-level attribute and 
> simultaneously can satisfy the session level need that has been 
> identified.
>
> I accept the WG's decision not to address the "preference" issue. But 
> this attachment to the "ugly child", if not addressed, invites getting 
> IESG LC comments.
>
>     Thanks,
>     Paul
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 15 06:09:14 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03DDC129623; Wed, 15 Feb 2017 06:09:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2n_v_QTkurfq; Wed, 15 Feb 2017 06:09:11 -0800 (PST)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::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 CF863129561; Wed, 15 Feb 2017 06:09:11 -0800 (PST)
Received: by mail-it0-x22b.google.com with SMTP id c7so63392741itd.1; Wed, 15 Feb 2017 06:09:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-transfer-encoding; bh=zVZV2SOuacsl+7MBoJNBJ98sg4dpNIv6P+0Cmhd8y+g=; b=NkHZIbdEKBoCLfe5d8nRuQXgcK/U6JcehEBP+WNrL4HZ9vR+47GGb5B5ADtG3mXp+H V1uJau4IELuo1jY5jkjMKaLSXZDfFBMZixCh2+xOlHewPCGmYeO0PqLbjA04B7YA+w3E vsUmvQd8ag47UdiNiKuylSSFqUxVyOWQ3MRYI9n8PjFFC73hbPwcC7sfrUgsaev9I2bn M1PqXNcoQA+ft9fABt7GWxal86dw/qUDt0BVDmKk3R9rgbgPX/xLVS5c6DqHtCkYILeD Yl4wp51qROZhvaGQyJu1O84GTb5KOpkNFwmbnfInkP+8Wp+0WDSyg02s0EO38EpAFKaT 42NA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-transfer-encoding; bh=zVZV2SOuacsl+7MBoJNBJ98sg4dpNIv6P+0Cmhd8y+g=; b=YO9VFqADKAQ+CqCqnhlyu1RhqT14q97jo5oHDweyaBnxcxH/+YcZn42rEfazTokuSd f0GWWEU7q6ZN5viNf6CZkmRhxPC48YDwc8wx6IN1+US11a7E/nAPxBd4SwSO2JwH1Z4Q 6MJZLQ9MI0rshdaM5MFrNb5f4vfYs5ztqpntjKUGFkSKJJO30VzwY34xBRpMFHbcefxC /VMFv8Nkun1je4EuhuY5/pPZUvkDXoJ/OPWH8BPULBBiIqpHs4MqbeknY26f0Gc7FWLZ i8ga+vXh1vfN8orHTfxZA4NOVZms3/4v1AqEg/sWiPTuM1ywj2NdUOMSgCPsidIhvC4m reTg==
X-Gm-Message-State: AMke39ng6ZhvsbrSKtSs4XPYCCg3+l0U3BcGRo2eb99vy2v9vQsrUtOusnAvVX7FDQTiPH3bgzqGuplsarGxNw==
X-Received: by 10.36.77.10 with SMTP id l10mr8698717itb.59.1487167751197; Wed, 15 Feb 2017 06:09:11 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Wed, 15 Feb 2017 06:09:10 -0800 (PST)
In-Reply-To: <148716644690.17360.10659757673489892672.idtracker@ietfa.amsl.com>
References: <148716644690.17360.10659757673489892672.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Wed, 15 Feb 2017 09:09:10 -0500
X-Google-Sender-Auth: 2XxKPwqGPq2psnK8NGtctAdxd2I
Message-ID: <CALaySJLcb=vhCPsbDZEBrtiioX4zMhauOZ=ts1_PX2NQcgBr=g@mail.gmail.com>
Subject: Re: Review of draft-leiba-rfc2119-update-01
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Lj1sb21pblbrXdH_0SkzQMKFtGo>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-leiba-rfc2119-update.all@ietf.org, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 14:09:13 -0000

Thanks for the review, J=C3=BCrgen.

Barry

On Wed, Feb 15, 2017 at 8:47 AM,  <"J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
<j.schoenwaelder@jac"@ietfa.amsl.com> wrote:
> Reviewer: J=C3=BCrgen Sch=C3=B6nw=C3=A4lder
> Review result: Ready
>
> This document has no direct operational impact on the Internet.
>
> Given my experience with RFC 2119 related discussions over the years,
> I would have preferred a broader update of RFC 2119 but perhaps this
> is the best we can get.
>
>


From nobody Wed Feb 15 07:49:44 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB4AE1294FA; Wed, 15 Feb 2017 07:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 d8tZ9jlIxlgO; Wed, 15 Feb 2017 07:49:41 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 A27F5129630; Wed, 15 Feb 2017 07:43:02 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1FFh0Sd047339 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 15 Feb 2017 09:43:01 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
Date: Wed, 15 Feb 2017 09:43:00 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8A6A2E153845792501B20E33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IUh5cyjsWspT5l2or-Wzw_23jwI>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 15:49:43 -0000

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



On 2/14/17 10:06 PM, Greg Mirsky wrote:
> Hi Robert,
> Section 5 Data Plane Theory of Operation has the following 
> recommendation on reading time value at ingress and egress:
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface;
>     this should be done as close to the physical layer as possible to
>     ensure precise accuracy in time determination.
> Do you find the text sufficient in providing guidance to an implementer of RTM?
Well, no - that was point in the text from my review of -12 that caused 
me to make comment in the first place.

What does "precise accuracy" even _MEAN_? You're waving your hands with 
words that don't help the reader guess what you mean at the moment. The 
subsequent email exchange said the important part was that you measure 
_precisely_ (in that the measurements are always taken the same way), 
but accuracy isn't that important (you've (and here by "you" I mean the 
set of people that have responded to the review") told me it's not 
important whether the reading is taken at the beginning of the 
bit-stream, the end, or several 1000 nanoseconds after the last bit came 
off the physical media as long as it's done the same way for each 
packet). The fact that you're carrying a measurement that can talk about 
times smaller than the interarrival time for individual bits for some 
real world line speeds says that different implementations taking the 
measurement different ways is going to result in different residence 
time measurements, even if the residence time was really identical. 
You've told me that's not important to the protocol using the 
measurement as long as the an individual implementation doesn't 
introduce something that will look to the using protocol like jitter 
that's not really there.

The text does not say that to an implementer right now.

To restate that long paragraph with maybe a longer one,  assume a 
simplified world where everything is perfectly constant. Packets are all 
flowing at the same size and same rate. For reference, I assert that the 
time between the first bit of a packet entering the system taking the 
measurement and the first bit of that packet leaving the system is 
exactly T (every time). You are telling me that if the system returns cT 
for some constant T other than 1 (and not necessarily  close to 1), 
everything is fine. You're also telling me that if you replace the 
system with another that preserves T, but measures differently so that 
it returns c'T where c' != c, everything is fine. The important part to 
you is that c and c' don't change for their respective systems. (That 
surprises me, I can see how the way the clocks are going to use this 
will do the right thing, but I can't help but think someone later will 
look at the difference between the two systems and say something is 
wrong with one of them). What you've told me is not fine is that if you 
drop i a third system that also preserves T but reports aT where a 
_varies_ over some range.

Have I heard you correctly?
> Regards,
> Greg
>
> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>     Reviewer: Robert Sparks
>     Review result: Ready
>
>     I am the assigned Gen-ART reviewer for this draft. The General Area
>     Review Team (Gen-ART) reviews all IETF documents being processed
>     by the IESG for the IETF Chair. Please wait for direction from your
>     document shepherd or AD before posting a new version of the draft.
>
>     For more information, please see the FAQ at
>
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>     <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>
>     Document: draft-ietf-mpls-residence-time-13
>     Reviewer: Robert Sparks
>     Review Date: 2017-02-13
>     IETF LC End Date: 2017-01-17
>     IESG Telechat date: 2017-03-02
>
>     Summary: Ready for publication as PS
>
>     Thanks for addressing my comments.
>     (I still think some discussion about taking arrival and departure time
>     measurements would be helpful, even if it only said "do it
>     consistently so you don't indicate jitter that's not really there".)
>
>


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/14/17 10:06 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>Section 5 Data Plane Theory of Operation has the following
          recommendation on reading time value at ingress and egress:</div>
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
        </div>
      </div>
    </blockquote>
    Well, no - that was point in the text from my review of -12 that
    caused me to make comment in the first place.<br>
    <br>
    What does "precise accuracy" even _MEAN_? You're waving your hands
    with words that don't help the reader guess what you mean at the
    moment. The subsequent email exchange said the important part was
    that you measure _precisely_ (in that the measurements are always
    taken the same way), but accuracy isn't that important (you've (and
    here by "you" I mean the set of people that have responded to the
    review") told me it's not important whether the reading is taken at
    the beginning of the bit-stream, the end, or several 1000
    nanoseconds after the last bit came off the physical media as long
    as it's done the same way for each packet). The fact that you're
    carrying a measurement that can talk about times smaller than the
    interarrival time for individual bits for some real world line
    speeds says that different implementations taking the measurement
    different ways is going to result in different residence time
    measurements, even if the residence time was really identical.
    You've told me that's not important to the protocol using the
    measurement as long as the an individual implementation doesn't
    introduce something that will look to the using protocol like jitter
    that's not really there.<br>
    <br>
    The text does not say that to an implementer right now.<br>
    <br>
    To restate that long paragraph with maybe a longer one,  assume a
    simplified world where everything is perfectly constant. Packets are
    all flowing at the same size and same rate. For reference, I assert
    that the time between the first bit of a packet entering the system
    taking the measurement and the first bit of that packet leaving the
    system is exactly T (every time). You are telling me that if the
    system returns cT for some constant T other than 1 (and not
    necessarily  close to 1), everything is fine. You're also telling me
    that if you replace the system with another that preserves T, but
    measures differently so that it returns c'T where c' != c,
    everything is fine. The important part to you is that c and c' don't
    change for their respective systems. (That surprises me, I can see
    how the way the clocks are going to use this will do the right
    thing, but I can't help but think someone later will look at the
    difference between the two systems and say something is wrong with
    one of them). What you've told me is not fine is that if you drop i
    a third system that also preserves T but reports aT where a _varies_
    over some range.<br>
    <br>
    Have I heard you correctly?<br>
    <blockquote
cite="mid:CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">
</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
          <pre class="gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, Robert
          Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer:
            Robert Sparks<br>
            Review result: Ready<br>
            <br>
            I am the assigned Gen-ART reviewer for this draft. The
            General Area<br>
            Review Team (Gen-ART) reviews all IETF documents being
            processed<br>
            by the IESG for the IETF Chair. Please wait for direction
            from your<br>
            document shepherd or AD before posting a new version of the
            draft.<br>
            <br>
            For more information, please see the FAQ at<br>
            <br>
            &lt;<a moz-do-not-send="true"
              href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
              rel="noreferrer" target="_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq</a>&gt;.<br>
            <br>
            Document: draft-ietf-mpls-residence-<wbr>time-13<br>
            Reviewer: Robert Sparks<br>
            Review Date: 2017-02-13<br>
            IETF LC End Date: 2017-01-17<br>
            IESG Telechat date: 2017-03-02<br>
            <br>
            Summary: Ready for publication as PS<br>
            <br>
            Thanks for addressing my comments.<br>
            (I still think some discussion about taking arrival and
            departure time<br>
            measurements would be helpful, even if it only said "do it<br>
            consistently so you don't indicate jitter that's not really
            there".)<br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------8A6A2E153845792501B20E33--


From nobody Wed Feb 15 08:00:54 2017
Return-Path: <skh@ndzh.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E51BF12960B; Wed, 15 Feb 2017 08:00:52 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Susan Hares <skh@ndzh.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-sidr-delta-protocol-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148717445293.17297.12773284406281280107.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 08:00:52 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WuGdi-eJO_x9Rozgt6qq2ez9C4E>
Cc: draft-ietf-sidr-delta-protocol.all@ietf.org, ietf@ietf.org, sidr@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:00:53 -0000

Reviewer: Susan Hares
Review result: Has Nits

Rob, Tim, Oleg, Bryan:

I have reviewed this document as part of the Operational directorate's

ongoing effort to review all IETF documents being processed by the
IESG.  These 
comments were written with the intent of improving the operational
aspects of the 
IETF drafts. Comments that are not addressed in last call may be
included in AD reviews 
during the IESG review.  Document editors and WG chairs should treat
these comments 
just like any other last call comments.

Status:  Ready with NITS – 

Overall comment:   Thank you for creating this draft that helps the
SIDR RPKI repositories better. 
What I’ve checked (for OPS-AD/NM-ADs):  Check texted, updates to other
protocols  

The details are belowl 

Sue Hares
------------------------

Editorial NITS list: 

Overall –comment: Each of these nits has a sub-status 
a)	Really needed – confusing – the document suffers from being
confusing unless you fix it
b)	Style – your choice, but the style of the text made it a bit
confusing 
c)	Go Check – security section that is out of my depth as reviewer 

#1 comment, 3.3.2 Publishing Updates, p. 6 

Status:  really needed – confusing 
Why: You are describing the delta files and then the handling of the
file is a different bullet.
         Please make it one format. 

Old:/

   o  This delta file MUST be made available at a URL that is unique
to
      the current session_id and serial number, so that it can be
cached
      indefinitely.

   o  The format and caching concerns for delta files are explained
in
      more detail in Section 3.5.3.
/
New: / 

   o  This delta file MUST be made available at a URL that is unique
to
      the current session_id and serial number, so that it can be
cached
      indefinitely. The format and caching concerns for delta files
are explained in
      more detail in Section 3.5.3.
/ 



#2, comment, 3.3.2, Publishing updates, p. 6 

#2 Status; really needed – confusing 
Why:  you are describing the snapshot and then the file handling.  It
should be one bullet. 

Old:/
   o  The snapshot file MUST be made available at a URL that is
unique
      to this session and new serial, so that it can be cached
      indefinitely.

  o  The format and caching concerns for snapshot files are explained
      in more detail in Section 3.5.2.
/
New/

   o  The snapshot file MUST be made available at a URL that is
unique
      to this session and new serial, so that it can be cached
      indefinitely.  The format and caching concerns for snapshot
files are explained
      in more detail in Section 3.5.2.
/

#3, comment, 3.3.2, Publishing updates, p. 6 

Status: really needed – confusing 
Why: You are describing the notification files and then the file
format. 

Old:/
   o  A new notification file MUST now be created by the repository
      server.  This new notification file MUST include a reference to
      the new snapshot file, and all delta files selected in the
      previous steps.

   o  The format and caching concerns for update notification files
are
      explained in more detail in Section 3.5.1.
/
New: / 

   o  A new notification file MUST now be created by the repository
      server.  This new notification file MUST include a reference to
      the new snapshot file, and all delta files selected in the
      previous steps. The format and caching concerns for update
notification files are
      explained in more detail in Section 3.5.1.
/

#4 section 3.4.1:entire section 

Status: style/confusing 

Comment: The first paragraph is the description of how Relying Party
(RP) when it learns about a valid certificate with a SIA entry for the
RRDP protocol.   The section does not make it clear. 

Easy fix:  

Old/this protocol as follows/
New/this protocol as follows:/

+ indent each paragraph as part of list 

#5 page 8 section 3.4.2 –general comment 

Status: really-needed 

The last paragraph “RP SHOUD NOT Remove objects”, the sentences as
follows:

      The RP could use
      additional strategies to determine if an object is still
relevant
      for validation before removing it from its local storage.  In
      particular objects should not be removed if they are included in
a
      current validated manifest.

If you suggest this, I suspect that all of you know what your
implementations are doing.  However, the specification is for other
people who want to also implement this protocol or checks to this
protocol.  An example or a pointer to an example would be very useful.


It does not break the protocol, so this did not rise to the level of
“minor”.  However it is piece of the specification you could tie down
operationally.  

#6 page 14, section 3.5.3.3 – file format and validation 

Status: style/nice to have – makes it easier for reader. 

Old:/   Note that a formal RELAX NG specification of this file format
is
   included later in this document.  A RP MUST NOT process any delta
   file that is incomplete or not well-formed./

New:/   Note that a formal RELAX NG specification of this file format
is
   included in section 3.5.4 in this document.  A RP MUST NOT process
any delta
   file that is incomplete or not well-formed.
     / 


#7 section 6, paragraph 3 status: 

Status: Please check with security person 

Paragraph: /
   Supporting both RRDP and rsync necessarily increases the number of
   opportunities for a malicious RPKI CA to perform denial of service
   attacks on relying parties, by expanding the number of URIs which
the
   RP may need to contact in order to complete a validation run.
   However, other than the relative cost of HTTPS versus rsync,
adding
   RRDP to the mix does not change this picture significantly: with
   either RRDP or rsync a malicious CA can supply an effectively
   infinite series of URIs for the RP to follow.  The only real
solution
   to this is for the RP to apply some kind of bound to the amount of
   work it is willing to do.  Note also that the attacker in this
   scenario must be an RPKI CA, since otherwise the normal RPKI
object
   security checks would reject the malicious URIs./

I’m really out of my depth to state how this works as security expert
or 
As operational expert.  It just raised questions of “oh really.. “



From nobody Wed Feb 15 08:18:20 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8919129560; Wed, 15 Feb 2017 08:18:18 -0800 (PST)
X-Quarantine-ID: <gPTxySb73zXm>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 gPTxySb73zXm; Wed, 15 Feb 2017 08:18:16 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id A453A126579; Wed, 15 Feb 2017 08:18:16 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 15 Feb 2017 08:10:11 -0800
Mime-Version: 1.0
Message-Id: <p06240603d4ca2e9c7548@[99.111.97.136]>
In-Reply-To: <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Wed, 15 Feb 2017 08:18:12 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZFb4d4zA8bnCy414-1ruu1KgWvc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:18:19 -0000

At 10:41 AM +0100 2/15/17, Gunnar Hellstr=F6m wrote:

>  Den 2017-02-15 kl. 01:39, skrev Randall Gellens:
>>  At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:
>>
>>>   Hi -
>>>
>>>   On 2/14/2017 2:43 PM, Randall Gellens wrote:
>>>>   At 8:59 PM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>>>
>>>>>    Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>>>>>
>>>>>>    Hi -
>>>>>>
>>>>>>    On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>>>>>    At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>>>>>>>
>>>>>>>>     My proposal for a reworded section 5.4 is:
>>>>>>>>
>>>>>>>>     5.4.  Unusual language indications
>>>>>>>>
>>>>>>>>     It is possible to specify an unusual indication where the langu=
age
>>>>>>>>     specified may look unexpected for the media type.
>>>>>>>>
>>>>>>>>     For such cases the following guidance SHALL be applied for the
>>>>>>>>    humintlang attributes used in these situations.
>>>>>>>>
>>>>>>>>     1.    A view of a speaking person in=20
>>>>>>>> the video stream SHALL, when it
>>>>>>>>    has relevance for speech perception, be indicated by a Language-=
Tag
>>>>>>>>    for spoken/written language with the=20
>>>>>>>> "Zxxx" script subtag to indicate
>>>>>>>>    that the contents is not written.
>>>>>>>>
>>>>>>>>     2.    Text captions included in the video stream SHALL be indic=
ated
>>>>>>>>    by a Language-Tag for spoken/written language.
>>>>>>>>
>>>>>>>>     3.    Any approximate representation of sign language or
>>>>>>>>    fingerspelling in the text media stream SHALL be indicated by a
>>>>>>>>    Language-Tag for a sign language in text media.
>>>>>>>>
>>>>>>>>     4.    When sign language related audio from a person using sign
>>>>>>>>    language is of importance for language communication, this SHALL=
 be
>>>>>>>>    indicated by a Language-Tag for a sign language in audio media.
>>>>>>>
>>>>>>>    [RG] As I said, I think we should avoid specifying this until we =
have
>>>>>>>    deployment experience.
>>>>>>    ...
>>>>>>
>>>>>>    From a process perspective, it's far easier to remove constraints
>>>>>>    as a specification advances than it is to add them.
>>>>>    I agree. It is often better to specify normatively as far as you ca=
n
>>>>>   imagine, so that interoperability and good functionality is achieved=
=2E
>>>>>   Stopping halfway and have MAY in the specifications creates
>>>>>   uncertainty and less useful specifications.
>>>>
>>>>   My reading of what Randy says is the opposite of Gunnar's. In my
>>>>   reading, Randy points out that is it easier to remove the SHOULD NOT =
in
>>>>   the future then it is to change the meaning of the combinations or
>>>>   switch to a different mechanism.
>>>>
>>>>   In my experience, it's better to specify only what we know we need an=
d
>>>>   what we know we understand.  Speculative specifications "as far as yo=
u
>>>>   can imagine" more often lead to interoperability problems, unnecessar=
y
>>>>   complexity, limitations on what's needed in the future, and divergent
>>>>   implementations.
>>>
>>>   I think the difference in your positions comes down to
>>>
>>>     (1) your respective notions of "what we know we need and what we
>>>         know we understand";
>>>
>>>     (2) whether you believe that the interoperability and conformance
>>>         consequences of removing a "SHOULD NOT" could be the same
>>>         as those merely retaining a "MUST" or "SHALL" - this determines
>>>         whether Randy G.'s proposal provides a path for some future
>>>         revision to mandate (if deployment experience substantiates the
>>>         need/understanding) the behavior proposed by Gunnar. That path
>>>         is not at all obvious to me.
>>
>>  The purpose of the draft is to enable the two=20
>> endpoints of a real-time communication session=20
>> to agree which languages and media to use for=20
>> interactive communication.  We have a=20
>> mechanism of adding language tags to media=20
>> stream negotiations.  In most cases, the=20
>> language and media modality are an obvious=20
>> fit.  There are combinations of media and=20
>> language where the meaning is not so obvious,=20
>> specifically, signed language tags with a=20
>> audio or text, and non-signed language tags=20
>> with video.  My proposal is that we say=20
>> offerer SHOULD NOT send such combinations and=20
>> answerer MAY ignore language. This allows=20
>> future specifications for the underlying uses=20
>> Gunnar wants (such as real-time subtitles in=20
>> video and signed equivalents in text).  Such=20
>> future specifications could define a use for=20
>> the language and media combinations and remove=20
>> the SHOULD NOT send and MAY ignore, or could=20
>> define a new mechanism.  I don't think we know=20
>> enough now to dictate what the solution should=20
>> be.
>  We have a fresh example from our own=20
> discussions in the SLIM group how unfortunate=20
> it is to not be sufficiently explicit in the=20
> first edition of a standard. The SDP Lang=20
> attribute in RFC 4566, where you (Randall) say=20
> it is intended for specifying a set of=20
> languages that all must be used in a session,=20
> while I say that it is intended for negotiation=20
> of at least one initial language. By having=20
> that uncertainty in a specification that has=20
> been published makes it very hard to sharpen up=20
> the specification afterwards because it would=20
> possibly make some implementations non=20
> conformant. And it makes potential implementors=20
> hesitant to use the current specifications, as=20
> it was with the SLIM work.

I don't believe the two cases are comparable.=20
The original SDP language attribute was unclear=20
how it was used.  The new attributes specified in=20
the current draft are clearly defined for the set=20
of cases that has been the target solution space=20
all along: allowing the two sides to agree on=20
which language will be used in interactive=20
communications.  You want to extend them for a=20
related solution space, which is additional=20
services to foster communication, such as adding=20
real-time captioning to video.  I think it's=20
better to do that add-on work in a subsequent=20
draft.

>
>  For 5.4.
>
>  I am OK with modifying from my latest proposal, but we need to be specifi=
c.
>  I am also OK with reducing the SHALLs to SHOULDs as Addison requested.
>
>  The situation is not that we lack knowledge.=20
> Here is what we know about the 4 cases of=20
> "unusual" indications:
>
>  1. View of the speaker in video. Very important=20
> for speech perception. Quality requirements are=20
> documented in ITU-T H-series Supplement 1. Of=20
> real use only as a complement to the same=20
> spoken language in audio. Now, when we know=20
> about the Zxxx notation for non-written, we=20
> also have a good way of specifying it precisely.
>  This case was also described in section 5.2 already.

It's already possible to negotiate a video stream.

>
>  2. Text captions in the video stream.
>  This can be either text merged into video and=20
> communicated as true part of the video image,=20
> or it can be a text component of a multimedia=20
> system, as MPEG-4, declared in SDP as m=3Dvideo.
>  It has been used in some videophone products,=20
> but I have not seen it used lately.
>  It is a clearly defined case, and we can=20
> specify coding for it, but we do not at the=20
> moment know if it will be important to specify=20
> it.

I believe this is an additional service that=20
should be specified in a subsequent draft.

>
>  3. Sign language or fingerspelling in the text stream.
>  I have seen a product using it for claimed sign=20
> language conversation. It is also in use in the=20
> simple text form with words in capitals=20
> approximately representing signs between=20
> persons involved in preparation of sign=20
> language productions and translations. But in=20
> that case it is in a session where they agree=20
> in other ways to start using the text stream=20
> for that purpose. So I think we can say that=20
> this is rare, and its use can be agreed by=20
> other means between the users. Still it is a=20
> clearly defined case.

I believe this is an additional service that=20
should be specified in a subsequent draft.

>
>  4. Audio from signing person related to sign=20
> language. This is more vague than the others.=20
> It may be a person signing in video and adding=20
> spoken words in audio to signing, but=20
> influenced by the word order and grammar of=20
> sign language with some ambition to make it=20
> reasonably understandable for both deaf and=20
> hearing participants. There are even some=20
> spoken words created from sign language that=20
> are commonly used by hearing persons in such=20
> situations. But for that case I anyway think it=20
> is better to define the audio part as the=20
> spoken language it is derived from, because of=20
> its intention to be understandable for hearing=20
> persons. All other variants I can imagine are=20
> even closer to the spoken language and should=20
> be specified with spoken language tag. If we=20
> only want to have the audio stream established=20
> to hear the background in the signing=20
> situation, then we should not specify language=20
> use of the audio stream.
>  Even if we know what sign language tag in audio=20
> stream would be, it may be just as good to=20
> leave it undefined.

I believe this is an additional service that=20
should be specified in a subsequent draft.

>=20
> --------------------------------------------------------------------------=
----------------------------------------------------------------------
>  So, new proposal:
>
>  5.4.  Unusual language indications
>
>     It is possible to specify an unusual indication where the language
>     specified may look unexpected for the media type.
>
>     For such cases the following guidance SHOULD be applied for the
>    humintlang attributes used in these situations.
>
>     1.    A view of a speaking person in the video stream SHOULD, when it
>    has relevance for speech perception, be=20
> indicated by a humintlang attribute with a=20
> Language-Tag
>    for a spoken/written language with the "Zxxx" script subtag to indicate
>    that the contents is not written.
>
>     2.    Text captions included in the video stream SHOULD be indicated
>    by a humintlang attribute with Language-Tag for spoken/written language=
=2E
>
>     3.    A Language-Tag for a sign language=20
> specified in a humintlang attribute for a text=20
> stream MAY be interpreted as use of an=20
> approximate representation of sign language or=20
> fingerspelling in the text media stream. The=20
> use of such representation is rare and usually=20
> conveniently agreed by other means between the=20
> users during an established session. Common=20
> support of this indication SHOULD NOT be=20
> assumed or required.
>
>     4.    A Language-Tag for a sign language=20
> specified in a humintlang attribute for an=20
> audio stream SHOULD NOT be indicated and MAY be=20
> ignored on reception. Any use of spoken words=20
> or spoken language in the audio stream SHOULD,=20
> when it can be of importance for language=20
> communication, be indicated by the=20
> corresponding Language-Tag for spoken language=20
> in a humintlang attribute for the audio stream.
>
>
>
>
>  Gunnar
>
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Think airlines.  Here a durable competitive advantage has proven
elusive ever since the days of the Wright Brothers.  Indeed, if a
farsighted capitalist had been present at Kitty Hawk, he would have
done his successors a huge favor by shooting Orville down.
        --"Oracle of Omaha," Warren Buffett


From nobody Wed Feb 15 08:27:02 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A02C1298C1; Wed, 15 Feb 2017 08:27:01 -0800 (PST)
X-Quarantine-ID: <YCQ6-vts2vdl>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 YCQ6-vts2vdl; Wed, 15 Feb 2017 08:26:59 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 27EAB129AD4; Wed, 15 Feb 2017 08:26:59 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 15 Feb 2017 08:18:53 -0800
Mime-Version: 1.0
Message-Id: <p06240604d4ca31180a3d@[99.111.97.136]>
In-Reply-To: <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se> <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Wed, 15 Feb 2017 08:26:56 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, ietf@ietf.org, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA  registrations)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ISNxLuJvC9lh5A6EisenwnrxwhM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:27:01 -0000

At 1:32 PM +0100 2/15/17, Gunnar Hellstr=F6m wrote:

>  in issue 8, I propose:
>
>  (Look in the edited draft -06g that I attached=20
> some days ago for how the proposal appears in=20
> the text )
>
>
>=20
> --------------------------------------------------------------------------=
----------------------------------
>
>  8. Include more fields for attribute registration from 4566bis
>
>  Section 6 has the form for attribute=20
> registration by IANA. There are a couple of=20
> fields missing that will be important for use=20
> of the specification in the WebRTC environment.=20
> Include these fields if that is allowable=20
> according to current IANA procedures and if=20
> that does not delay the publication of this=20
> draft. These fields are needed for use of text=20
> media in WebRTC.
>
>  Change:
>
>  In two locations from:
>      "Usage Level:  media"
>
>  to:
>
>      "Usage Level:  media, dcsa(subprotocol)"
>
>  Insert in two locations in the registration forms:
>  "Mux Category: NORMAL"
>=20
> --------------------------------------------------------------------------=
-------------------------------------
>=20
> --------------------------------------------------------------------------=
-------------------------------------
>
>  I checked in current IANA registrations, and=20
> found that all SDP attribute registrations now=20
> include the "Mux Category".
>
>  So, I assume that we are obliged to do so also=20
> and hope that we can agree on that.
>  As far as I understand the logic, we should specify NORMAL.

This is not required.  See the IANA registry at=20
http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml.=20
It is governed by RFC 4566.

As I've written twice before, my concern is that=20
this suggestion exceeds a simple editorial=20
change, and therefore may need to be discussed on=20
the WG list with WG consensus before it can be=20
adopted.  These fields can be added to the=20
attribute registration later, according to the=20
rules for the registry=20
(http://www.iana.org/assignments/sdp-parameters/sdp-parameters.xhtml).


>  I saw no trace yet of registrations of  "Usage Level: dcsa(subprotocol)"
>
>  I would like to get advice from someone with=20
> insight in the SDP attribute registration and=20
> the status of the dsca(subprotocol) value on=20
> how we should proceed in order to get the=20
> dsca(subprotocol)  included in a smooth way=20
> without causing exessive delay.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Asking if computers can think is like asking if submarines can swim.


From nobody Wed Feb 15 08:29:43 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50353129A5E for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 08:29:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.786
X-Spam-Level: 
X-Spam-Status: No, score=-3.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1iXU1z-47A4 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 08:29:40 -0800 (PST)
Received: from nm1-vm10.bullet.mail.gq1.yahoo.com (nm1-vm10.bullet.mail.gq1.yahoo.com [98.136.218.89]) (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 E772F129A1D for <ietf@ietf.org>; Wed, 15 Feb 2017 08:29:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487176179; bh=vmD1XoDhhRcrBqewBts+GlAlNN6itvEVUxEVjsQrWFk=; h=Date:From:Reply-To:To:Cc:Subject:References:From:Subject; b=kVanUGPkJERj1PicjHpX2fsykvUP02vLTXzGa6aRs+jeTe645pyso1fa473RbE4oAtL2r84IokfNIbqVPU/zaxqgUksEaFP7IgWzf0eICAypj5K0YugGX2keAnZ/uf/FGY4hy/7myVaJQwkuR3BijNnmhXcLnmOyu0uiP4ZKpRwBZtkDeWdXsqjuEPZvh0/mw5QD+2SsTP8WvOSPfAQeMbQrPNiLoRmFBPnf60lmS5BHjlnQrI17wJ8QRYNvFKFcxSGe7Lgestt2t3Uzbvm0f07OxNWN4+egIcR+wmD4g6j7QvEr2rjWZkrucEgerhWmQXay305ghlEUkOZYksNeLA==
Received: from [98.137.12.191] by nm1.bullet.mail.gq1.yahoo.com with NNFMP; 15 Feb 2017 16:29:39 -0000
Received: from [98.137.12.234] by tm12.bullet.mail.gq1.yahoo.com with NNFMP; 15 Feb 2017 16:29:39 -0000
Received: from [127.0.0.1] by omp1042.mail.gq1.yahoo.com with NNFMP; 15 Feb 2017 16:29:39 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 494748.2585.bm@omp1042.mail.gq1.yahoo.com
X-YMail-OSG: y.3rkx4VM1n3gBrHoRnkitkZFS.PaYeOIOO04Tumd5wYXfs1l_tvNJhg6nGfdya 7PFw.Pk0T5nkF.eF63M3PaRqq1ZdcOLluehrTmSLSS1EU7kOajPItHg0epCT2Ds7sUxkMkOxaX_O 69IB21VY8ke20vw0yVw0USlOeST4Cb9AMwJIBN32DwH.wHIu3hKbwS7tCM5z6qoZDW1cK0AfbRpa rt3wNkJ9TQUc8U8Tm9owPVh2I.Oedl1B5d_YkvyE0SwCfMlCES9eOtjTFNZwK4VGP.rUSxVTNFc1 .rpzaOo3K09BGcvLzQiaF9knR.3Qh_PM738u0MHsHwTmUmoKqf6ujYHXvtvUbwznCtEveGPLd0lv tCHFuRroS8KMihhiAvQnbRtLUPFO96WEo06siQNtE5p2gNM1aglMqrVX0qeaxROHA0SC.JndhJYG FF6omyhtIAoMqlWbk5kXDROcmi0RhleBwlqmGgXExsJDXCF48.WcwmJFDtKIAqlgixBc_TBoce_. PNu8.oMTMiosgzeVpdVx.7Y4AtdAH.C9WIF2RjxW8F1zqyukCf5iqKC71ayUYHomFpE1DFdw976ux
Received: from jws300081.mail.gq1.yahoo.com by sendmailws132.mail.gq1.yahoo.com; Wed, 15 Feb 2017 16:29:39 +0000; 1487176179.126
Date: Wed, 15 Feb 2017 16:29:38 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: IETF Discussion List <ietf@ietf.org>
Message-ID: <1302911527.6950973.1487176178877@mail.yahoo.com>
Subject: Internet Research Labs Draft
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o_i4r5WpqUirkgX5fYlv5E4HIo0>
Cc: Harish Chowdhary <harish@nixi.in>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:29:41 -0000

All,
 
If anyone is interested, we have just done an I-D for a proposed concept for "Internet Labs".   We hope this will be of interest. 

https://tools.ietf.org/html/draft-chowbat-irl-00 

The abstract is here: 

Many people learn technical concepts best in a hands-on environment, 
and Internet protocols and standards are no exception. Internet 
Research Labs (IRL) will facilitate a platform and encourage the 
technical community (seasoned professionals and newcomers alike) to 
discuss, collaborate, design and develop utilities, ideas, sample 
code and solutions that show practical implementations (Proof of 
Concept) of existing IETF standards. These labs may also be used by 
the IETF Mentoring Program and/or EDU teams for hands-on training to 
mentees or newcomers. This base draft intends to provide a high-level 
overview of the concept of Internet Research Labs in terms of 
objectives, requirements, challenges and deliverables without going 
into details of a specific lab, technology or an IETF Working Group 
(WG). After this draft matures and gains traction within the IETF 
community, we foresee more and more Internet drafts for the specific 
labs. 

Thanks,

Nalini Elkins
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


From nobody Wed Feb 15 08:50:46 2017
Return-Path: <sgundave@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 633CA1295B2; Wed, 15 Feb 2017 08:50:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level: 
X-Spam-Status: No, score=-14.522 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ok8EPOgBdOIU; Wed, 15 Feb 2017 08:50:38 -0800 (PST)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E745D1294BF; Wed, 15 Feb 2017 08:50:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4817; q=dns/txt; s=iport; t=1487177438; x=1488387038; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LvaLyYXBEHd/sV2pU29zz1G76QP7etmzTklSI2CI5R0=; b=P9/il7gp/kWRZodNyqfenNij1OWOt1m3F44EcOl0ws6iZUsPtZpvXhyQ R5mnwpY1g1I5NOpUetexUjh7YW/X5kSXAHlvL5/I81hkhSu3Shrc4wSav rzSrbFJgwxkSw+Xub0xk1jHddlAQ5BrF954LvSc255U8X2JfJMWg9Rmfx M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BtAQBVhqRY/4UNJK1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1KBageNWqdGggyGIgKCEz8YAQIBAQEBAQEBYiiEcQYOLCsUEAIBCDY?= =?us-ascii?q?QMiUCBA4FiWuyVIs8AQEBAQEBAQEBAQEBAQEBAQEBAQEehk2Eb4QmEQGGAQWbd?= =?us-ascii?q?wGSE4F7hReJdJMWAR84eAhRFYUCHYFhdYgkgSGBDAEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,166,1484006400"; d="scan'208";a="386049403"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Feb 2017 16:50:36 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v1FGoaqY008674 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Feb 2017 16:50:36 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 15 Feb 2017 10:50:35 -0600
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1210.000; Wed, 15 Feb 2017 10:50:35 -0600
From: "Sri Gundavelli (sgundave)" <sgundave@cisco.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Topic: [DMM] Review of draft-ietf-dmm-4283mnids-04
Thread-Index: AQHSh6ugGmBv2a9UCEeirDF7S0m5iA==
Date: Wed, 15 Feb 2017 16:50:35 +0000
Message-ID: <D4C9C46E.259E23%sgundave@cisco.com>
References: <D4C63E24.2598D8%sgundave@cisco.com> <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
In-Reply-To: <87wpcuuj1n.fsf@hobgoblin.ariadne.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.32.246.215]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <581AF40AA8C8B448A365053BBAEE2D0C@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/J64jtd2A3pVy7CfmQsezJ1xGlb8>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-dmm-4283mnids.all@ietf.org" <draft-ietf-dmm-4283mnids.all@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 16:50:39 -0000

HI Dale,

Thanks again for the comments. Please see inline.




On 2/13/17, 8:55 AM, "Dale R. Worley" <worley@ariadne.com> wrote:

>"Sri Gundavelli (sgundave)" <sgundave@cisco.com> writes:
>> When we discussed this issue in the past, the general feedback from
>> the WG was that the draft should provide some minimal amount of
>> details on the new identifier types, what the identifier is, how the
>> identifier is constructed, what is the access technology and a
>> reference to the specification that provides that definition. The idea
>> is NOT TO provide extensive details on the spec, but to enable a
>> reader with some high level details and a pointer to the
>> specification. I tend to think the text in the current specification
>> just does that. If the text is seen as redundant text, we can
>> certainly add a statement saying that the definition for the
>> identifier is provided in spec-XYZ and is repeated here for
>> convenience. May be other folks in the WG have some views on this.
>
>I take it that the following are typical comments from the WG:
>
>> Comments from 10/11/2015 email:
>>
>> "Some text on the motivation for defining new Types may be
>> helpful. Document is not just standardizing the currently
>> in-use/popular identifier types, its also introducing new types are
>> not in use. The reasons/interest for defining identifiers that are
>> tied to the physical elements of the device (RFID, MAC address ..etc)
>> and how it helps in deployment of the technology may be useful. Few
>> lines of text will really help."
>>
>> "I was hoping to see a sub-section for each of the types. We cannot
>> standardize a identifier type without providing any explanation on the
>> identifier type or the references to the base definitions. This can be
>> painful, but I'd have a small section for each of the types. It can be
>> 3 line text on the a.) Definition b.) Format c.) Example format d.)
>> Reference to the base spec that defines those identifiers."
>
>I can understand these desires, and I agree with following them.
>
>In regard to the first message, it seems to request "The
>reasons/interest for defining identifiers that are tied to the physical
>elements of the device (RFID, MAC address ..etc) and how it helps in
>deployment of the technology may be useful."  As far as I can tell, this
>isn't handled in section 4.9 (which is the part I was complaining
>about).  And I don't recall if the earlier parts of the draft are
>specific about "the reasons/interest" for any of the new types.  I
>believe from this discussion that the reason an identifier was included
>is that somebody told the authors that they wanted to use the identifier
>in question -- and that is quite legitimate.  Perhaps saying it
>explicitly in the early parts of the draft would help.
>
>In regard to the second message, it seems to request
>
>    a small section for each of the types. It can be
>    3 line text on the
>	a.) Definition
>	b.) Format
>	c.) Example format
>	d.) Reference to the base spec that defines those identifiers.
>
>Of course, (d) "reference to base spec" is necessary, and the
>sub-sections of 4.9 do that for each format, as does Table 1.
>
>For (a) "definition", the texts in 4.9 proper seem to be fairly good.
>E.g.,
>
>   The EPC encoding scheme for SGTIN permits the direct embedding of
>   EAN.UCC System standard GTIN and Serial Number codes on EPC tags.  In
>   all cases, the check digit is not encoded.  Two encoding schemes are
>   specified, SGTIN-64 (64 bits) and SGTIN-96 (96 bits).
>
>Based on that alone, I couldn't possibly construct a SGTIN-64 myself,
>but I have some idea of the information it contains and the technical
>terms to look up to find the real definition of the data items.
>
>However (b) "format" seems to be missing (except in the most abstract
>sense) and (c) "example format" seem to be missing entirely.  OTOH, I'm
>not sure that the space needed to specify those would be worth the
>effort.

[Sri] I agree. The goal was to make the spec complete. What ever
identifiers we are carrying in this option, we provide the format,
structure and semantics of construction and not treat it like an opaque
container. But, its a delicate balance, not ending up with a lot of
duplicated text, vs incomplete specification. I agree, its not worth the
efforts doing a significant re-write. The current text is probably fine.


>
>Summary:  After thinking about it more, I think it's not worth the
>effort to revise 4.9 heavily.  Most of that information is for the use
>of people who are familiar with the RFID identifiers and their formats,
>and if they are happy with it, there's no reason to change it.

[Sri] I agree with your summary.




>
>Dale


From nobody Wed Feb 15 09:12:51 2017
Return-Path: <prvs=21264b967=addison@lab126.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40D721296AA; Wed, 15 Feb 2017 09:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 ChWjgJv3xvDS; Wed, 15 Feb 2017 09:12:48 -0800 (PST)
Received: from smtp-fw-4101.amazon.com (smtp-fw-4101.amazon.com [72.21.198.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8F12129459; Wed, 15 Feb 2017 09:12:47 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,166,1484006400"; d="scan'208";a="663823921"
Received: from iad6-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-25015.iad12.amazon.com) ([10.124.125.6]) by smtp-border-fw-out-4101.iad4.amazon.com with ESMTP/TLS/DHE-RSA-AES256-SHA;  15 Feb 2017 17:12:46 +0000
Received: from EX13MTAUWB001.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan2.iad.amazon.com [10.40.159.162]) by email-inbound-relay-25015.iad12.amazon.com (8.14.7/8.14.7) with ESMTP id v1FHC9JI000777 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 15 Feb 2017 17:12:45 GMT
Received: from EX13D08UWB003.ant.amazon.com (10.43.161.186) by EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 15 Feb 2017 17:12:44 +0000
Received: from EX13D08UWB002.ant.amazon.com (10.43.161.168) by EX13D08UWB003.ant.amazon.com (10.43.161.186) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 15 Feb 2017 17:12:44 +0000
Received: from EX13D08UWB002.ant.amazon.com ([10.43.161.168]) by EX13D08UWB002.ant.amazon.com ([10.43.161.168]) with mapi id 15.00.1104.000; Wed, 15 Feb 2017 17:12:44 +0000
From: "Phillips, Addison" <addison@lab126.com>
To: =?iso-8859-1?Q?Gunnar_Hellstr=F6m?= <gunnar.hellstrom@omnitor.se>, "Randy Presuhn" <randy_presuhn@alumni.stanford.edu>, "ietf@ietf.org" <ietf@ietf.org>, "slim@ietf.org" <slim@ietf.org>
Subject: RE: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
Thread-Topic: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
Thread-Index: AQHShk5MdWFzLzaSL0G26SF4TAiur6FoFQsAgAAxCoCAAIAWgIAAJxpAgAAIijCAAORJAIAAbwXw
Date: Wed, 15 Feb 2017 17:12:44 +0000
Message-ID: <e1ce6bbaaf624c1e88d31c72440093ba@EX13D08UWB002.ant.amazon.com>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com> <ba7f397b-59ae-c549-cd1a-e22e1b73b3c1@omnitor.se>
In-Reply-To: <ba7f397b-59ae-c549-cd1a-e22e1b73b3c1@omnitor.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.162.155]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: Bulk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N1a0lTrKM7UZc8_oPL55oUaeYLM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 17:12:49 -0000

Gunnar replied:
>=20
> Den 2017-02-14 kl. 21:39, skrev Phillips, Addison:
> > I have some allergy to the SHALL language: there is no way to automatic=
ally
> determine conformance. Many language tags represent nonsensical values, d=
ue
> to the nature of language tag composition. Content providers need to use =
care
> in selecting the tags that they use and this section is merely pointing o=
ut good
> guidance for tag selection, albeit in a heavy-handed way. BCP47 RFC 5646
> Section 4.1 [1] already provides most of this guidance and a reference to=
 that
> source might be useful here, if only because that document requires it:
> >
> > <quote>
> >     Standards, protocols, and applications that reference this document
> >     normatively but apply different rules to the ones given in this
> >     section MUST specify how language tag selection varies from the
> >     guidelines given here.
> > </quote>
> >
> > I would suggest reducing the SHALL items to SHOULD.
> Accepted.
> That also opens up for another use we have discussed before but been advi=
sed
> to not use. That is to indicate use of written language by attaching a sc=
ript
> subtag even if the script subtag we use is suppressed by BCP 47. We can d=
ro that
> need however, with the use of the Zxxx script subtag for non-written, and=
 clearly
> include that usage in our specification as required from BCP 47.

I don't necessarily think that mandating a script subtag as a signal of wri=
tten content (vs. spoken content) is that useful. In most protocols, the wr=
itten nature of the content is indicated by the presence of text. Trying to=
 coerce the language modality via language tags seems complicated, especial=
ly since most language tags are harvested from the original source. Introdu=
cing processes to evaluate and insert or remove script subtags seems unnece=
ssary to me. That said, I have no objection to content using script subtags=
 if they are useful.=20

> >
> > I'm not sure what #2 really means. Shouldn't text captions be indicated=
 by the
> written language rather than the spoken language? And I'm not sure what
> "spoken/written language" means.
> #2 was: "
>=20
> 2.    Text captions included in the video stream SHALL be indicated
> by a Language-Tag for spoken/written language."
>=20
> Yes, the intention is to use written language in the video stream. There =
are
> technologies for that.

I'm aware of that. My concern is that in this case "spoken/written" is appl=
ied to "text captions", which are not spoken be definition? This section is=
 talking about the differences between identifying spoken and written langu=
age. The text captions fall into the written side of the equation, no?

I'd probably prefer to see something like "2. Text captions included in the=
 video stream SHOULD include a Language-Tag to identify the language."

> Since the language subtags in the IANA registry are combined for spoken
> languages and written languages, I call them Language-Tags for spoken/wri=
tten
> language.

The language subtags are for languages--all modalities. My comment here is =
that "spoken/written" adds no information.

> It would be misleading to say that we use a Language-Tag for a written
> language, because the same tag could in another context mean a spoken
> language.

One uses a Language-Tag for indicating the language. When the text is writt=
en, sometimes the user will pick a different language tag (zh-Hant-HK) than=
 they might choose for spoken text (yue-HK, zh-cmn-HK, etc.). Sometimes (ac=
tually, nearly all the time except for special cases) the language tag for =
the spoken and written language is the same tag (en-US, de-CH, ja-JP, etc.)=
. Again, the modality of the language is a separate consideration from the =
language. Nearly always, it is better to use the same tag for both spoken a=
nd written content rather than trying to use the tag to distinguish between=
 them: different Content-Types require different decoders anyway, but it is=
 really useful to say "give me all of the 'en-US' content you have" or "do =
you have content for a user who speaks 'es'"

> Since we have the script subtag Zxxx for non-written, we do not need to
> construct an explicit tag for the written language tag, it should be suff=
icient with
> our specification of the use in our case.

In case it isn't clear aboe, I oppose introducing the 'Zxxx' subtag save fo=
r cases where the non-written nature of the content is super-important to t=
he identification of the language.
>=20
> In my latest recent proposal, I still have a very similar wording. Since =
you had
> problems understanding it, there might still be a need to tune it. Can yo=
u
> propose wording?
> This is the current proposal:
>=20
> "   2.    Text captions included in the video stream SHOULD be indicated
>    by a humintlang attribute with Language-Tag for spoken/written languag=
e.
> "

I did that above. I think it is useful not to over-think it. When I see "Co=
ntent-Type: video/mpeg; Content-Language: en-GB", I rather expect audio con=
tent in English and not written content (although the video stream might al=
so includes pictures of English text such as the titles in a movie). When, =
as in this case, setting up a negotiated language experience, interoperabil=
ity is most aided by matching the customer's language preferences to availa=
ble resources. This is easiest when customers do not get carried away with =
complex language tags (ranges in BCP 47 parlance, e.g. tlh-Cyrl-AQ-fonupa) =
and systems do not have to introspect the language tags, inserting and remo=
ving script subtags to match the various language modes.

Addison


From nobody Wed Feb 15 09:21:00 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B46E129698; Wed, 15 Feb 2017 09:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5T4O587CNnWC; Wed, 15 Feb 2017 09:20:57 -0800 (PST)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::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 CFAD6129696; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
Received: by mail-ot0-x22e.google.com with SMTP id 19so10190279oti.2; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rRy/Ira7tW7hiadGek2cEb3JfgqVyhLnuAc3yFRlVts=; b=RbfEq1MYKaDltVnDd86h/Y/n8V/QES6hVcIXk4WsV4IbgqnnLzVMplLXZh2JiLUNab V8D2VQ6i2RfppjmgSSCrmkmmEKhdKR5jyuwQ24RsqS9/rV2Rx6oMuj4ZyCjgVGs2yHSo sFbAtUOalzzEZ15/UqaBS1lCLVmMJjdu9ZG6FYq7v1eO3sfnMUDddLrdB7FJhIYx048F kIMWJpn0t+Nvc8bceO2IBMduTNG5gCkOLAj+ev+yKEfPtz40MCFfWTzN35q0PKTFRxbb awh1CCWIsi+jwydoLquat+oPs9fQ8yzISWyd/ecDiQjlpOqQiWD/rXWgt9yZS0PdReox TNUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rRy/Ira7tW7hiadGek2cEb3JfgqVyhLnuAc3yFRlVts=; b=CoO+qECGbRDm9YyQTR94qq4784vTpyZ63FjzLP0aBDNgG5nXnMlnAZadPyALBV6qk6 wOLUp0I09wQfuso6FMI15MJ8/WBkafScwJ08NY8CQqTtjYdnJKXh/lMVNif2ucKJZI5u j+NR6iUNzJSFKGILk8HiuGAYN/d6BLyXEThBc6OwBOmGZy2SuJCoV9ZFYwSGno42u9zD 89EJWMjV+LhBMxx7wt69sVK1nVJ5J4U0j8PByWAQvBVcSs6S1bRwzS5E/VV7cVtWWJYW JzLQT+vPzOgsfikXEP/Fg16RS6kO7mKxn+nS4NRG2GBlinviQrekuUGsgL0DIMjth8ti Ju4w==
X-Gm-Message-State: AMke39krRQ9Dg+ZqYlyTn33PvF+PAoGz1M5VN3ss91xlLPenQvaUIMCE18ztz/cXfS9VW3fbG9Zu/ascogKf7g==
X-Received: by 10.157.16.9 with SMTP id h9mr18682836ote.40.1487179256229; Wed, 15 Feb 2017 09:20:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Wed, 15 Feb 2017 09:20:55 -0800 (PST)
In-Reply-To: <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 15 Feb 2017 09:20:55 -0800
Message-ID: <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a11402c0248f5be054894e765
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/V2bgiwlCr1nKc9LZHKs1fqXBbNA>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 17:20:59 -0000

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

Hi Robert,
yes, you've absolutely correct in your example. The importance of RTM is to
exclude and quantify, as much as possible, jitter from propagation delay.
I've updated the wording to reflect that. Below is new text I propose,
please let me know if it makes it clearer.

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.

Regards,

Greg


On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

>
>
> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>
> Hi Robert,
> Section 5 Data Plane Theory of Operation has the following recommendation
> on reading time value at ingress and egress:
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface;
>    this should be done as close to the physical layer as possible to
>    ensure precise accuracy in time determination.
>
> Do you find the text sufficient in providing guidance to an implementer of RTM?
>
> Well, no - that was point in the text from my review of -12 that caused me
> to make comment in the first place.
>
> What does "precise accuracy" even _MEAN_? You're waving your hands with
> words that don't help the reader guess what you mean at the moment. The
> subsequent email exchange said the important part was that you measure
> _precisely_ (in that the measurements are always taken the same way), but
> accuracy isn't that important (you've (and here by "you" I mean the set of
> people that have responded to the review") told me it's not important
> whether the reading is taken at the beginning of the bit-stream, the end,
> or several 1000 nanoseconds after the last bit came off the physical media
> as long as it's done the same way for each packet). The fact that you're
> carrying a measurement that can talk about times smaller than the
> interarrival time for individual bits for some real world line speeds says
> that different implementations taking the measurement different ways is
> going to result in different residence time measurements, even if the
> residence time was really identical. You've told me that's not important to
> the protocol using the measurement as long as the an individual
> implementation doesn't introduce something that will look to the using
> protocol like jitter that's not really there.
>
> The text does not say that to an implementer right now.
>
> To restate that long paragraph with maybe a longer one,  assume a
> simplified world where everything is perfectly constant. Packets are all
> flowing at the same size and same rate. For reference, I assert that the
> time between the first bit of a packet entering the system taking the
> measurement and the first bit of that packet leaving the system is exactly
> T (every time). You are telling me that if the system returns cT for some
> constant T other than 1 (and not necessarily  close to 1), everything is
> fine. You're also telling me that if you replace the system with another
> that preserves T, but measures differently so that it returns c'T where c'
> != c, everything is fine. The important part to you is that c and c' don't
> change for their respective systems. (That surprises me, I can see how the
> way the clocks are going to use this will do the right thing, but I can't
> help but think someone later will look at the difference between the two
> systems and say something is wrong with one of them). What you've told me
> is not fine is that if you drop i a third system that also preserves T but
> reports aT where a _varies_ over some range.
>
> Have I heard you correctly?
>
> Regards,
>
> Greg
>
>
> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>> Reviewer: Robert Sparks
>> Review result: Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair. Please wait for direction from your
>> document shepherd or AD before posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-mpls-residence-time-13
>> Reviewer: Robert Sparks
>> Review Date: 2017-02-13
>> IETF LC End Date: 2017-01-17
>> IESG Telechat date: 2017-03-02
>>
>> Summary: Ready for publication as PS
>>
>> Thanks for addressing my comments.
>> (I still think some discussion about taking arrival and departure time
>> measurements would be helpful, even if it only said "do it
>> consistently so you don't indicate jitter that's not really there".)
>>
>>
>
>

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

<div dir=3D"ltr">Hi Robert,<div>yes, you&#39;ve absolutely correct in your =
example. The importance of RTM is to exclude and quantify, as much as possi=
ble, jitter from propagation delay. I&#39;ve updated the wording to reflect=
 that. Below is new text I propose, please let me know if it makes it clear=
er.</div><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-spa=
ce:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre><pre style=3D"color:rgb(0,0,0);word=
-wrap:break-word;white-space:pre-wrap">Regards,</pre><pre style=3D"color:rg=
b(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre></div></div><=
div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 15, 20=
17 at 7:43 AM, Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjspar=
ks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <p><br>
    </p>
    <br>
    <div class=3D"m_3072934530585377958moz-cite-prefix">On 2/14/17 10:06 PM=
, Greg Mirsky wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <div>Section 5 Data Plane Theory of Operation has the following
          recommendation on reading time value at ingress and egress:</div>
        <div>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RT=
M-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you fin=
d the text sufficient in providing guidance to an implementer of RTM?</pre>
        </div>
      </div>
    </blockquote></span>
    Well, no - that was point in the text from my review of -12 that
    caused me to make comment in the first place.<br>
    <br>
    What does &quot;precise accuracy&quot; even _MEAN_? You&#39;re waving y=
our hands
    with words that don&#39;t help the reader guess what you mean at the
    moment. The subsequent email exchange said the important part was
    that you measure _precisely_ (in that the measurements are always
    taken the same way), but accuracy isn&#39;t that important (you&#39;ve =
(and
    here by &quot;you&quot; I mean the set of people that have responded to=
 the
    review&quot;) told me it&#39;s not important whether the reading is tak=
en at
    the beginning of the bit-stream, the end, or several 1000
    nanoseconds after the last bit came off the physical media as long
    as it&#39;s done the same way for each packet). The fact that you&#39;r=
e
    carrying a measurement that can talk about times smaller than the
    interarrival time for individual bits for some real world line
    speeds says that different implementations taking the measurement
    different ways is going to result in different residence time
    measurements, even if the residence time was really identical.
    You&#39;ve told me that&#39;s not important to the protocol using the
    measurement as long as the an individual implementation doesn&#39;t
    introduce something that will look to the using protocol like jitter
    that&#39;s not really there.<br>
    <br>
    The text does not say that to an implementer right now.<br>
    <br>
    To restate that long paragraph with maybe a longer one,=C2=A0 assume a
    simplified world where everything is perfectly constant. Packets are
    all flowing at the same size and same rate. For reference, I assert
    that the time between the first bit of a packet entering the system
    taking the measurement and the first bit of that packet leaving the
    system is exactly T (every time). You are telling me that if the
    system returns cT for some constant T other than 1 (and not
    necessarily=C2=A0 close to 1), everything is fine. You&#39;re also tell=
ing me
    that if you replace the system with another that preserves T, but
    measures differently so that it returns c&#39;T where c&#39; !=3D c,
    everything is fine. The important part to you is that c and c&#39; don&=
#39;t
    change for their respective systems. (That surprises me, I can see
    how the way the clocks are going to use this will do the right
    thing, but I can&#39;t help but think someone later will look at the
    difference between the two systems and say something is wrong with
    one of them). What you&#39;ve told me is not fine is that if you drop i
    a third system that also preserves T but reports aT where a _varies_
    over some range.<br>
    <br>
    Have I heard you correctly?<span class=3D""><br>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"></pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</=
pre>
          <pre class=3D"m_3072934530585377958gmail-newpage" style=3D"font-s=
ize:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Mon, Feb 13, 2017 at 1:51 PM, Robert
          Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.c=
om" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Reviewer:
            Robert Sparks<br>
            Review result: Ready<br>
            <br>
            I am the assigned Gen-ART reviewer for this draft. The
            General Area<br>
            Review Team (Gen-ART) reviews all IETF documents being
            processed<br>
            by the IESG for the IETF Chair. Please wait for direction
            from your<br>
            document shepherd or AD before posting a new version of the
            draft.<br>
            <br>
            For more information, please see the FAQ at<br>
            <br>
            &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" r=
el=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wik=
i/GenArtfaq</a>&gt;.<br>
            <br>
            Document: draft-ietf-mpls-residence-time<wbr>-13<br>
            Reviewer: Robert Sparks<br>
            Review Date: 2017-02-13<br>
            IETF LC End Date: 2017-01-17<br>
            IESG Telechat date: 2017-03-02<br>
            <br>
            Summary: Ready for publication as PS<br>
            <br>
            Thanks for addressing my comments.<br>
            (I still think some discussion about taking arrival and
            departure time<br>
            measurements would be helpful, even if it only said &quot;do it=
<br>
            consistently so you don&#39;t indicate jitter that&#39;s not re=
ally
            there&quot;.)<br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </span></div>

</blockquote></div><br></div>

--001a11402c0248f5be054894e765--


From nobody Wed Feb 15 11:15:43 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C2841293E0; Wed, 15 Feb 2017 11:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 oQibP_bl5vs5; Wed, 15 Feb 2017 11:15:30 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 9F9581296F2; Wed, 15 Feb 2017 11:15:30 -0800 (PST)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1FJFSuQ072323 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 15 Feb 2017 13:15:29 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
Date: Wed, 15 Feb 2017 13:15:28 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------8EF8ACD6F400BCC5968C8777"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SHuj1bWWJKb7h3Qa3EomV4WcgZ4>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 19:15:34 -0000

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



On 2/15/17 11:20 AM, Greg Mirsky wrote:
> Hi Robert,
> yes, you've absolutely correct in your example. The importance of RTM 
> is to exclude and quantify, as much as possible, jitter from 
> propagation delay. I've updated the wording to reflect that. Below is 
> new text I propose, please let me know if it makes it clearer.
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface.
>     These actions should be done as close to the physical layer as
>     possible at the same point of packet processing striving to avoid
>     introduction of jitter in propogation delay to ensure precise
>     accuracy in time determination.
perhaps change "avoid introduction of jitter" to "avoid introducing the 
appearance of jitter that's not really there"?

(I'm about to board a plane, so further responses will be very delayed).
> Regards,
> Greg
>
> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>
>
>     On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>     Hi Robert,
>>     Section 5 Data Plane Theory of Operation has the following
>>     recommendation on reading time value at ingress and egress:
>>         Each RTM-capable
>>         node on the explicit path receives an RTM packet and records the time
>>         at which it receives that packet at its ingress interface as well as
>>         the time at which it transmits that packet from its egress interface;
>>         this should be done as close to the physical layer as possible to
>>         ensure precise accuracy in time determination.
>>     Do you find the text sufficient in providing guidance to an implementer of RTM?
>     Well, no - that was point in the text from my review of -12 that
>     caused me to make comment in the first place.
>
>     What does "precise accuracy" even _MEAN_? You're waving your hands
>     with words that don't help the reader guess what you mean at the
>     moment. The subsequent email exchange said the important part was
>     that you measure _precisely_ (in that the measurements are always
>     taken the same way), but accuracy isn't that important (you've
>     (and here by "you" I mean the set of people that have responded to
>     the review") told me it's not important whether the reading is
>     taken at the beginning of the bit-stream, the end, or several 1000
>     nanoseconds after the last bit came off the physical media as long
>     as it's done the same way for each packet). The fact that you're
>     carrying a measurement that can talk about times smaller than the
>     interarrival time for individual bits for some real world line
>     speeds says that different implementations taking the measurement
>     different ways is going to result in different residence time
>     measurements, even if the residence time was really identical.
>     You've told me that's not important to the protocol using the
>     measurement as long as the an individual implementation doesn't
>     introduce something that will look to the using protocol like
>     jitter that's not really there.
>
>     The text does not say that to an implementer right now.
>
>     To restate that long paragraph with maybe a longer one, assume a
>     simplified world where everything is perfectly constant. Packets
>     are all flowing at the same size and same rate. For reference, I
>     assert that the time between the first bit of a packet entering
>     the system taking the measurement and the first bit of that packet
>     leaving the system is exactly T (every time). You are telling me
>     that if the system returns cT for some constant T other than 1
>     (and not necessarily  close to 1), everything is fine. You're also
>     telling me that if you replace the system with another that
>     preserves T, but measures differently so that it returns c'T where
>     c' != c, everything is fine. The important part to you is that c
>     and c' don't change for their respective systems. (That surprises
>     me, I can see how the way the clocks are going to use this will do
>     the right thing, but I can't help but think someone later will
>     look at the difference between the two systems and say something
>     is wrong with one of them). What you've told me is not fine is
>     that if you drop i a third system that also preserves T but
>     reports aT where a _varies_ over some range.
>
>     Have I heard you correctly?
>>     Regards,
>>     Greg
>>
>>     On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks
>>     <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>
>>         Reviewer: Robert Sparks
>>         Review result: Ready
>>
>>         I am the assigned Gen-ART reviewer for this draft. The
>>         General Area
>>         Review Team (Gen-ART) reviews all IETF documents being processed
>>         by the IESG for the IETF Chair. Please wait for direction
>>         from your
>>         document shepherd or AD before posting a new version of the
>>         draft.
>>
>>         For more information, please see the FAQ at
>>
>>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>>         <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>>
>>         Document: draft-ietf-mpls-residence-time-13
>>         Reviewer: Robert Sparks
>>         Review Date: 2017-02-13
>>         IETF LC End Date: 2017-01-17
>>         IESG Telechat date: 2017-03-02
>>
>>         Summary: Ready for publication as PS
>>
>>         Thanks for addressing my comments.
>>         (I still think some discussion about taking arrival and
>>         departure time
>>         measurements would be helpful, even if it only said "do it
>>         consistently so you don't indicate jitter that's not really
>>         there".)
>>
>>
>
>


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/15/17 11:20 AM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>yes, you've absolutely correct in your example. The
          importance of RTM is to exclude and quantify, as much as
          possible, jitter from propagation delay. I've updated the
          wording to reflect that. Below is new text I propose, please
          let me know if it makes it clearer.</div>
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
        </div>
      </div>
    </blockquote>
    perhaps change "avoid introduction of jitter" to "avoid introducing
    the appearance of jitter that's not really there"?<br>
    <br>
    (I'm about to board a plane, so further responses will be very
    delayed). <br>
    <blockquote
cite="mid:CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Feb 15, 2017 at 7:43 AM, Robert
          Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"><span class="">
                <p><br>
                </p>
                <br>
                <div class="m_3072934530585377958moz-cite-prefix">On
                  2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="ltr">Hi Robert,
                    <div>Section 5 Data Plane Theory of Operation has
                      the following recommendation on reading time value
                      at ingress and egress:</div>
                    <div>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
                    </div>
                  </div>
                </blockquote>
              </span> Well, no - that was point in the text from my
              review of -12 that caused me to make comment in the first
              place.<br>
              <br>
              What does "precise accuracy" even _MEAN_? You're waving
              your hands with words that don't help the reader guess
              what you mean at the moment. The subsequent email exchange
              said the important part was that you measure _precisely_
              (in that the measurements are always taken the same way),
              but accuracy isn't that important (you've (and here by
              "you" I mean the set of people that have responded to the
              review") told me it's not important whether the reading is
              taken at the beginning of the bit-stream, the end, or
              several 1000 nanoseconds after the last bit came off the
              physical media as long as it's done the same way for each
              packet). The fact that you're carrying a measurement that
              can talk about times smaller than the interarrival time
              for individual bits for some real world line speeds says
              that different implementations taking the measurement
              different ways is going to result in different residence
              time measurements, even if the residence time was really
              identical. You've told me that's not important to the
              protocol using the measurement as long as the an
              individual implementation doesn't introduce something that
              will look to the using protocol like jitter that's not
              really there.<br>
              <br>
              The text does not say that to an implementer right now.<br>
              <br>
              To restate that long paragraph with maybe a longer one, 
              assume a simplified world where everything is perfectly
              constant. Packets are all flowing at the same size and
              same rate. For reference, I assert that the time between
              the first bit of a packet entering the system taking the
              measurement and the first bit of that packet leaving the
              system is exactly T (every time). You are telling me that
              if the system returns cT for some constant T other than 1
              (and not necessarily  close to 1), everything is fine.
              You're also telling me that if you replace the system with
              another that preserves T, but measures differently so that
              it returns c'T where c' != c, everything is fine. The
              important part to you is that c and c' don't change for
              their respective systems. (That surprises me, I can see
              how the way the clocks are going to use this will do the
              right thing, but I can't help but think someone later will
              look at the difference between the two systems and say
              something is wrong with one of them). What you've told me
              is not fine is that if you drop i a third system that also
              preserves T but reports aT where a _varies_ over some
              range.<br>
              <br>
              Have I heard you correctly?<span class=""><br>
                <blockquote type="cite">
                  <div dir="ltr">
                    <div>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                      <pre class="m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                    </div>
                  </div>
                  <div class="gmail_extra"><br>
                    <div class="gmail_quote">On Mon, Feb 13, 2017 at
                      1:51 PM, Robert Sparks <span dir="ltr">&lt;<a
                          moz-do-not-send="true"
                          href="mailto:rjsparks@nostrum.com"
                          target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0 0
                        0 .8ex;border-left:1px #ccc
                        solid;padding-left:1ex">Reviewer: Robert Sparks<br>
                        Review result: Ready<br>
                        <br>
                        I am the assigned Gen-ART reviewer for this
                        draft. The General Area<br>
                        Review Team (Gen-ART) reviews all IETF documents
                        being processed<br>
                        by the IESG for the IETF Chair. Please wait for
                        direction from your<br>
                        document shepherd or AD before posting a new
                        version of the draft.<br>
                        <br>
                        For more information, please see the FAQ at<br>
                        <br>
                        &lt;<a moz-do-not-send="true"
                          href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
                          rel="noreferrer" target="_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                        <br>
                        Document: draft-ietf-mpls-residence-time<wbr>-13<br>
                        Reviewer: Robert Sparks<br>
                        Review Date: 2017-02-13<br>
                        IETF LC End Date: 2017-01-17<br>
                        IESG Telechat date: 2017-03-02<br>
                        <br>
                        Summary: Ready for publication as PS<br>
                        <br>
                        Thanks for addressing my comments.<br>
                        (I still think some discussion about taking
                        arrival and departure time<br>
                        measurements would be helpful, even if it only
                        said "do it<br>
                        consistently so you don't indicate jitter that's
                        not really there".)<br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </blockquote>
                <br>
              </span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------8EF8ACD6F400BCC5968C8777--


From nobody Wed Feb 15 12:08:12 2017
Return-Path: <bishopbilly84@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79C71297BE for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 12:08:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6u5akElgqUdt for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 12:08:09 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 3ED32129A2F for <ietf@ietf.org>; Wed, 15 Feb 2017 12:08:09 -0800 (PST)
Received: by mail-vk0-x234.google.com with SMTP id k127so106013934vke.0 for <ietf@ietf.org>; Wed, 15 Feb 2017 12:08:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=GT/LU6Am1qslGHJGIBjQs5KOEIUy529ypvw00xuMinM=; b=XlvkMjdVbVHB6iI9zYpVn6sTekgm6tif/bO1ClMSrCwMkhxXsJOmKlAa9f2P0rJnUu lWwZlgzd5YwXuZKvkqmJTwnNQQaXsn4ABy07qTZWnwSTd+H4DgBA1n+e/xoohxeumbBE Ma4m+2V77RwnIMY0LVokniH0GRaP3KHcQFA0Tl1UAWROytaPwnVYRaJxnLQoBnAjOhjY DICoHBrf+2fC07Y/P15iF4h4ROhc5qdeoXBd5g3D8LrRSqJBJirHlM9DxAQvrK2VOkBM j0wbT6d1cXoZTK2ybVbFwikVsmW+5XhkYk4SM8M+kUIQYFkdqrTD/XHa0+4fVh3XguPa Kkhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=GT/LU6Am1qslGHJGIBjQs5KOEIUy529ypvw00xuMinM=; b=hXka1rLWG0FZTwNIoP6V2iTYX3xuOWfhBMDPVf77I29iOb2MOhl8z8UsLGPF4rFBEY +oyv51cf3mFT+R+Q0q0soWQEBTqr+VlyfyKco7wYnqqfvZObNSZiHuXCTF+pYvwa+ee6 xBD4z32dmLfxZM19K0+4kdHvXe3RP4p4HNr/+v9TfHFTrwluvBjmEFj8EN+LRG7Vx/3x MVsE+h8E0xeqpA0VWQdqX1UuoGx9WGI3q0d+jiuqD90tOQX2PQhHjE/PR8adUQODLQfX hHmoaBMzWvUWNHaUthGEZANTHy0PkIHEch/54M3YujK3fR6cYARPY7clqM+wLPA+nxYA cGTg==
X-Gm-Message-State: AMke39nOfVfP0irWdf83hrYhbc9yx2hYpV34Nkn1QPiSTu+QJF1UqvkTjUzcp+a9+Ru9hwaJp5XRxJC8H47N/Q==
X-Received: by 10.31.146.209 with SMTP id u200mr18560390vkd.163.1487189288214;  Wed, 15 Feb 2017 12:08:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.8.153 with HTTP; Wed, 15 Feb 2017 12:08:07 -0800 (PST)
Received: by 10.176.8.153 with HTTP; Wed, 15 Feb 2017 12:08:07 -0800 (PST)
In-Reply-To: <148718908812.31454.5452489853774556097.idtracker@ietfa.amsl.com>
References: <148718908812.31454.5452489853774556097.idtracker@ietfa.amsl.com>
From: Billy Bishop <bishopbilly84@gmail.com>
Date: Wed, 15 Feb 2017 12:08:07 -0800
Message-ID: <CAApmNcQUqkd=jgYTh3Sbr7PojCqqeLneED_ZXx=rOFp6OB4opg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-pce-inter-layer-ext-12.txt> (Extensions to the Path Computation Element communication Protocol (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering) to Proposed Standard
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a11438c223d00850548973d6b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w4L3Ni-NQypLSFa2fHisnVz01qE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:08:11 -0000

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

On Feb 15, 2017 2:05 PM, "The IESG" <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the Path Computation Element WG
> (pce) to consider the following document:
> - 'Extensions to the Path Computation Element communication Protocol
>    (PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering'
>   <draft-ietf-pce-inter-layer-ext-12.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    The Path Computation Element (PCE) provides path computation
>    functions in support of traffic engineering in Multiprotocol Label
>    Switching (MPLS) and Generalized MPLS (GMPLS) networks.
>
>    MPLS and GMPLS networks may be constructed from layered service
>    networks.  It is advantageous for overall network efficiency to
>    provide end-to-end traffic engineering across multiple network layers
>    through a process called inter-layer traffic engineering.  PCE is a
>    candidate solution for such requirements.
>
>    The PCE communication Protocol (PCEP) is designed as a communication
>    protocol between Path Computation Clients (PCCs) and PCEs.  This
>    document presents PCEP extensions for inter-layer traffic
>    engineering.
>
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-pce-inter-layer-ext/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-pce-inter-layer-ext/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> The document contains these normative downward references.
> See RFC 3967 for additional information:
>     draft-ietf-pce-pce-initiated-lsp: PCEP Extensions for PCE-initiated
> LSP Setup in a Stateful PCE Model (None - IETF stream)
> Note that some of these references may already be listed in the acceptable
> Downref Registry.
>
>
>

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

<div dir=3D"auto"></div><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Feb 15, 2017 2:05 PM, &quot;The IESG&quot; &lt;<a href=3D"mailto:=
iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br type=3D"=
attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"><br>
The IESG has received a request from the Path Computation Element WG<br>
(pce) to consider the following document:<br>
- &#39;Extensions to the Path Computation Element communication Protocol<br=
>
=C2=A0 =C2=A0(PCEP) for Inter-Layer MPLS and GMPLS Traffic Engineering&#39;=
<br>
=C2=A0 &lt;draft-ietf-pce-inter-layer-<wbr>ext-12.txt&gt; as Proposed Stand=
ard<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-03=
-01. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=C2=A0 =C2=A0The Path Computation Element (PCE) provides path computation<b=
r>
=C2=A0 =C2=A0functions in support of traffic engineering in Multiprotocol L=
abel<br>
=C2=A0 =C2=A0Switching (MPLS) and Generalized MPLS (GMPLS) networks.<br>
<br>
=C2=A0 =C2=A0MPLS and GMPLS networks may be constructed from layered servic=
e<br>
=C2=A0 =C2=A0networks.=C2=A0 It is advantageous for overall network efficie=
ncy to<br>
=C2=A0 =C2=A0provide end-to-end traffic engineering across multiple network=
 layers<br>
=C2=A0 =C2=A0through a process called inter-layer traffic engineering.=C2=
=A0 PCE is a<br>
=C2=A0 =C2=A0candidate solution for such requirements.<br>
<br>
=C2=A0 =C2=A0The PCE communication Protocol (PCEP) is designed as a communi=
cation<br>
=C2=A0 =C2=A0protocol between Path Computation Clients (PCCs) and PCEs.=C2=
=A0 This<br>
=C2=A0 =C2=A0document presents PCEP extensions for inter-layer traffic<br>
=C2=A0 =C2=A0engineering.<br>
<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-inter-layer-ext/=
" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>do=
c/draft-ietf-pce-inter-<wbr>layer-ext/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-pce-inter-layer-ext/=
ballot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/=
<wbr>doc/draft-ietf-pce-inter-<wbr>layer-ext/ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.<br>
<br>
<br>
The document contains these normative downward references.<br>
See RFC 3967 for additional information:<br>
=C2=A0 =C2=A0 draft-ietf-pce-pce-initiated-<wbr>lsp: PCEP Extensions for PC=
E-initiated LSP Setup in a Stateful PCE Model (None - IETF stream)<br>
Note that some of these references may already be listed in the acceptable =
Downref Registry.<br>
<br>
<br>
</blockquote></div></div>

--001a11438c223d00850548973d6b--


From nobody Wed Feb 15 12:08:32 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BAF2D129A99; Wed, 15 Feb 2017 12:08:30 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <ops-dir@ietf.org>
Subject: Review of draft-ietf-bmwg-virtual-net-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.43.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148718931072.31507.17292789125260012486.idtracker@ietfa.amsl.com>
Date: Wed, 15 Feb 2017 12:08:30 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L6pAy3f_XSZEaz31gD1mXiobm3k>
Cc: draft-ietf-bmwg-virtual-net.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:08:30 -0000

Reviewer: Jouni Korhonen
Review result: Ready

This document was good informational read. No complaints.

Two editorials:

Line  338: "...possibility of benchmark curation during development of
new..."
  Is it curation or creation?

Line 409: "..VNF, or something as simple as a new poicy to implement
in a VNF, .."
  s/poicy/policy



From nobody Wed Feb 15 12:40:39 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 640EC1297EB; Wed, 15 Feb 2017 12:40:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVHchg1zRCfF; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::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 ADF8012943B; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id u143so92644911oif.3; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HknoOHI9NMdmFphiMYNbbn6Y4TjOkHz+lwQ2ajNqUjo=; b=kntMMhXl08J6pHJpI7dtzaRyJaX4gnjQRGgn6PDdv7jfEgt3KneScMxVTK07ZQogIq cpCDkURhgbAn7PGX5XZj+4fkEuVeExKkDLN+eWZuIOjfd6ZxSrccYQGApgrte/Ajv7N9 YsrtDKe1GZMN6YHTQCu8QlWwp3H+nH0mvEv1yDkYyUkBgD3a1pvbBQelRc3QmEAAhemH 7rQ4SIzzTN/jcTohTyNby0mWGTAEJ1bqt49g/T/3tlQAISGJybb8OR3V744qXlhuKadS EuVA4VMhg2LwgbNTmZFwg33MiY/ZzsQCeS5GhCMpVpR72p0hhukSui3O8qk87TCg1Sp3 x6BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HknoOHI9NMdmFphiMYNbbn6Y4TjOkHz+lwQ2ajNqUjo=; b=pXu46Ogb3JA7T969Af15gufFLh2Nc3s7a1N1RcG27u5hjwsHn3U4xwwUzllSv53EUv EHG7zkpvEgXvCLrNJQ5sh2nIA8w2/hgPDofoGvnD+bQDkUFsGAlM6c+07Il+qwyUacBU YbNlXkYPaPiTtp2KQthJ41bJsMzTVotLz0OnSI7xU6enGmpQCMaah/eQkNcvi/IslaWv yy7PuR9fNT1z+HcJvSqfjVlkZ5QfDCufo+XJDNPrI7su/XW6xpegAwYcEFWxOGXzripH /uQCmayg4hUqt+wRyiUSTlEqgVF3IrnzdVjd79je88Dqolmzx1OnlWFuk66O2ffYtM3k /tXw==
X-Gm-Message-State: AMke39mqCaMjnHkJtpcGYVkygl+Nn+1Iqkck5Qc2HStP6WJvHwxLE+8cuO4wCvdKK0KDREAxL+6t+NWRJdV0Sg==
X-Received: by 10.202.232.77 with SMTP id f74mr18251472oih.60.1487191229023; Wed, 15 Feb 2017 12:40:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.1.103 with HTTP; Wed, 15 Feb 2017 12:40:28 -0800 (PST)
In-Reply-To: <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 15 Feb 2017 12:40:28 -0800
Message-ID: <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=001a1141b0a0eb4d66054897b029
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oQTM6eC_uTz72JsA_sWJWfNtoDM>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:40:32 -0000

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

Hi Robert,
safe travel and here's another version for your consideration. The point
I'm trying to convey is that the jitter is real but must be accounted not
as part of propagation delay but as residence time. Hope I'm getting close.

   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time.

Regards,

Greg


On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com>
wrote:

>
>
> On 2/15/17 11:20 AM, Greg Mirsky wrote:
>
> Hi Robert,
> yes, you've absolutely correct in your example. The importance of RTM is
> to exclude and quantify, as much as possible, jitter from propagation
> delay. I've updated the wording to reflect that. Below is new text I
> propose, please let me know if it makes it clearer.
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface.
>    These actions should be done as close to the physical layer as
>    possible at the same point of packet processing striving to avoid
>    introduction of jitter in propogation delay to ensure precise
>    accuracy in time determination.
>
> perhaps change "avoid introduction of jitter" to "avoid introducing the
> appearance of jitter that's not really there"?
>
> (I'm about to board a plane, so further responses will be very delayed).
>
> Regards,
>
> Greg
>
>
> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>
>> Hi Robert,
>> Section 5 Data Plane Theory of Operation has the following recommendation
>> on reading time value at ingress and egress:
>>
>>    Each RTM-capable
>>    node on the explicit path receives an RTM packet and records the time
>>    at which it receives that packet at its ingress interface as well as
>>    the time at which it transmits that packet from its egress interface;
>>    this should be done as close to the physical layer as possible to
>>    ensure precise accuracy in time determination.
>>
>> Do you find the text sufficient in providing guidance to an implementer of RTM?
>>
>> Well, no - that was point in the text from my review of -12 that caused
>> me to make comment in the first place.
>>
>> What does "precise accuracy" even _MEAN_? You're waving your hands with
>> words that don't help the reader guess what you mean at the moment. The
>> subsequent email exchange said the important part was that you measure
>> _precisely_ (in that the measurements are always taken the same way), but
>> accuracy isn't that important (you've (and here by "you" I mean the set of
>> people that have responded to the review") told me it's not important
>> whether the reading is taken at the beginning of the bit-stream, the end,
>> or several 1000 nanoseconds after the last bit came off the physical media
>> as long as it's done the same way for each packet). The fact that you're
>> carrying a measurement that can talk about times smaller than the
>> interarrival time for individual bits for some real world line speeds says
>> that different implementations taking the measurement different ways is
>> going to result in different residence time measurements, even if the
>> residence time was really identical. You've told me that's not important to
>> the protocol using the measurement as long as the an individual
>> implementation doesn't introduce something that will look to the using
>> protocol like jitter that's not really there.
>>
>> The text does not say that to an implementer right now.
>>
>> To restate that long paragraph with maybe a longer one,  assume a
>> simplified world where everything is perfectly constant. Packets are all
>> flowing at the same size and same rate. For reference, I assert that the
>> time between the first bit of a packet entering the system taking the
>> measurement and the first bit of that packet leaving the system is exactly
>> T (every time). You are telling me that if the system returns cT for some
>> constant T other than 1 (and not necessarily  close to 1), everything is
>> fine. You're also telling me that if you replace the system with another
>> that preserves T, but measures differently so that it returns c'T where c'
>> != c, everything is fine. The important part to you is that c and c' don't
>> change for their respective systems. (That surprises me, I can see how the
>> way the clocks are going to use this will do the right thing, but I can't
>> help but think someone later will look at the difference between the two
>> systems and say something is wrong with one of them). What you've told me
>> is not fine is that if you drop i a third system that also preserves T but
>> reports aT where a _varies_ over some range.
>>
>> Have I heard you correctly?
>>
>> Regards,
>>
>> Greg
>>
>>
>> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>
>>> Reviewer: Robert Sparks
>>> Review result: Ready
>>>
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair. Please wait for direction from your
>>> document shepherd or AD before posting a new version of the draft.
>>>
>>> For more information, please see the FAQ at
>>>
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>
>>> Document: draft-ietf-mpls-residence-time-13
>>> Reviewer: Robert Sparks
>>> Review Date: 2017-02-13
>>> IETF LC End Date: 2017-01-17
>>> IESG Telechat date: 2017-03-02
>>>
>>> Summary: Ready for publication as PS
>>>
>>> Thanks for addressing my comments.
>>> (I still think some discussion about taking arrival and departure time
>>> measurements would be helpful, even if it only said "do it
>>> consistently so you don't indicate jitter that's not really there".)
>>>
>>>
>>
>>
>
>

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

<div dir=3D"ltr">Hi Robert,<div>safe travel and here&#39;s another version =
for your consideration. The point I&#39;m trying to convey is that the jitt=
er is real but must be accounted not as part of propagation delay but as re=
sidence time. Hope I&#39;m getting close.</div><div><pre style=3D"color:rgb=
(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre><pre style=3D"color:rgb(0,0,0);word-wrap:break-wor=
d;white-space:pre-wrap">Regards,</pre><pre style=3D"color:rgb(0,0,0);word-w=
rap:break-word;white-space:pre-wrap">Greg</pre></div></div><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,=
 Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com=
" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span class=3D"">
    <p><br>
    </p>
    <br>
    <div class=3D"m_2800513769154960288moz-cite-prefix">On 2/15/17 11:20 AM=
, Greg Mirsky wrote:<br>
    </div>
    </span><blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <span class=3D""><div>yes, you&#39;ve absolutely correct in your ex=
ample. The
          importance of RTM is to exclude and quantify, as much as
          possible, jitter from propagation delay. I&#39;ve updated the
          wording to reflect that. Below is new text I propose, please
          let me know if it makes it clearer.</div>
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
        </div>
      </span></div>
    </blockquote>
    perhaps change &quot;avoid introduction of jitter&quot; to &quot;avoid =
introducing
    the appearance of jitter that&#39;s not really there&quot;?<br>
    <br>
    (I&#39;m about to board a plane, so further responses will be very
    delayed). <br><div><div class=3D"h5">
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Regards,</pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 7:43 AM, Robert
          Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.c=
om" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                <p><br>
                </p>
                <br>
                <div class=3D"m_2800513769154960288m_3072934530585377958moz=
-cite-prefix">On
                  2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                </div>
                <blockquote type=3D"cite">
                  <div dir=3D"ltr">Hi Robert,
                    <div>Section 5 Data Plane Theory of Operation has
                      the following recommendation on reading time value
                      at ingress and egress:</div>
                    <div>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidanc=
e to an implementer of RTM?</pre>
                    </div>
                  </div>
                </blockquote>
              </span> Well, no - that was point in the text from my
              review of -12 that caused me to make comment in the first
              place.<br>
              <br>
              What does &quot;precise accuracy&quot; even _MEAN_? You&#39;r=
e waving
              your hands with words that don&#39;t help the reader guess
              what you mean at the moment. The subsequent email exchange
              said the important part was that you measure _precisely_
              (in that the measurements are always taken the same way),
              but accuracy isn&#39;t that important (you&#39;ve (and here b=
y
              &quot;you&quot; I mean the set of people that have responded =
to the
              review&quot;) told me it&#39;s not important whether the read=
ing is
              taken at the beginning of the bit-stream, the end, or
              several 1000 nanoseconds after the last bit came off the
              physical media as long as it&#39;s done the same way for each
              packet). The fact that you&#39;re carrying a measurement that
              can talk about times smaller than the interarrival time
              for individual bits for some real world line speeds says
              that different implementations taking the measurement
              different ways is going to result in different residence
              time measurements, even if the residence time was really
              identical. You&#39;ve told me that&#39;s not important to the
              protocol using the measurement as long as the an
              individual implementation doesn&#39;t introduce something tha=
t
              will look to the using protocol like jitter that&#39;s not
              really there.<br>
              <br>
              The text does not say that to an implementer right now.<br>
              <br>
              To restate that long paragraph with maybe a longer one,=C2=A0
              assume a simplified world where everything is perfectly
              constant. Packets are all flowing at the same size and
              same rate. For reference, I assert that the time between
              the first bit of a packet entering the system taking the
              measurement and the first bit of that packet leaving the
              system is exactly T (every time). You are telling me that
              if the system returns cT for some constant T other than 1
              (and not necessarily=C2=A0 close to 1), everything is fine.
              You&#39;re also telling me that if you replace the system wit=
h
              another that preserves T, but measures differently so that
              it returns c&#39;T where c&#39; !=3D c, everything is fine. T=
he
              important part to you is that c and c&#39; don&#39;t change f=
or
              their respective systems. (That surprises me, I can see
              how the way the clocks are going to use this will do the
              right thing, but I can&#39;t help but think someone later wil=
l
              look at the difference between the two systems and say
              something is wrong with one of them). What you&#39;ve told me
              is not fine is that if you drop i a third system that also
              preserves T but reports aT where a _varies_ over some
              range.<br>
              <br>
              Have I heard you correctly?<span><br>
                <blockquote type=3D"cite">
                  <div dir=3D"ltr">
                    <div>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Regards,</pre>
                      <pre class=3D"m_2800513769154960288m_3072934530585377=
958gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom=
:0px;color:rgb(0,0,0)">Greg</pre>
                    </div>
                  </div>
                  <div class=3D"gmail_extra"><br>
                    <div class=3D"gmail_quote">On Mon, Feb 13, 2017 at
                      1:51 PM, Robert Sparks <span dir=3D"ltr">&lt;<a href=
=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a>=
&gt;</span>
                      wrote:<br>
                      <blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Robert Spark=
s<br>
                        Review result: Ready<br>
                        <br>
                        I am the assigned Gen-ART reviewer for this
                        draft. The General Area<br>
                        Review Team (Gen-ART) reviews all IETF documents
                        being processed<br>
                        by the IESG for the IETF Chair. Please wait for
                        direction from your<br>
                        document shepherd or AD before posting a new
                        version of the draft.<br>
                        <br>
                        For more information, please see the FAQ at<br>
                        <br>
                        &lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/=
GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.ietf.org/trac/=
ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                        <br>
                        Document: draft-ietf-mpls-residence-time<wbr>-13<br=
>
                        Reviewer: Robert Sparks<br>
                        Review Date: 2017-02-13<br>
                        IETF LC End Date: 2017-01-17<br>
                        IESG Telechat date: 2017-03-02<br>
                        <br>
                        Summary: Ready for publication as PS<br>
                        <br>
                        Thanks for addressing my comments.<br>
                        (I still think some discussion about taking
                        arrival and departure time<br>
                        measurements would be helpful, even if it only
                        said &quot;do it<br>
                        consistently so you don&#39;t indicate jitter that&=
#39;s
                        not really there&quot;.)<br>
                        <br>
                      </blockquote>
                    </div>
                    <br>
                  </div>
                </blockquote>
                <br>
              </span></div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div>

--001a1141b0a0eb4d66054897b029--


From nobody Wed Feb 15 12:41:09 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BD5129B6E for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 12:40:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QShHv6niIkG1 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 12:40:37 -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 B50D4129B64 for <ietf@ietf.org>; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
Received: by mail-pf0-x229.google.com with SMTP id c73so30554900pfb.0 for <ietf@ietf.org>; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=zpsU83HZUABHROuNLA5qxCxvMEac8TxHWj8C1bSZAfI=; b=Tw3EzgMBN+S109+1tBcxsC+d2wUvv/Qe/aOS4oRIwHhZzGAWOPWKAn+Q8rwbQMansi X+6N6f1k6S+59p8M7sS+qXUuoSBApnL9ZhiPNRHB6OPYnJW7N+Qg00nJ87BrmIkj3YNh 7w/Gk7LqA41Hs1kcTk/tsnN+O2DWvbqa09+hb7oFyvoP+ZCl3qIGTKyX30JRkgLdvs7n 635xVu4FJ0HqAjOZBJMIwAcSF/UQjrfqjAkiWTce7L+BVkszt4vPMwqu4CBje8afsmqs 07lKnVm96FnkGO9CTK85mC8r61uca8RF7pxloGxrRxSa2gj15/tiWSuwREs59mGpHd95 yfNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=zpsU83HZUABHROuNLA5qxCxvMEac8TxHWj8C1bSZAfI=; b=CWlA0yd0q5Ojv65cl/15LnX86xvPTdICYtrp/a78t7E65svPQoRA0/ZWAiCIPYXhA7 7F2YskAbb2Wpia63jhzG58ObaRytjIirSVZwkBvxpXdqjwNefWEV0+iwU6ZyKCoVlgmP 8XpHHQo5q1zVBVV/iAQs+UY0v0Q16N/Y0vGzZiLEweK1hXwAVpBpUnkA9eA1vIPgB/jB 9uxDFNYEq7w+YDD+JHbLpJAceNwSDgRewhujcznZkUR1vfoDr/cosNPk8WpUfOtSN8OD htSEx3/yDwmkfO3MkMjtEo0n3YuiMkMEDoYc3sTwn6vvn7e0j5fUOItaYnoSPfvaE2nP iarw==
X-Gm-Message-State: AMke39m69iKYkC3w9QBPRm+2gBjLxVAV65w/6LpZRx9KVuVVNhfjKo3l9KQwsX0HVypejyat
X-Received: by 10.99.39.70 with SMTP id n67mr40570667pgn.203.1487191234190; Wed, 15 Feb 2017 12:40:34 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id a25sm9209081pgd.26.2017.02.15.12.40.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 12:40:33 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <99AFD44C-06B7-435D-A14C-951680EA2355@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
Date: Wed, 15 Feb 2017 12:40:32 -0800
In-Reply-To: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
To: "ietf@ietf.org" <ietf@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OkjnjZ8VNxgdNeGKtfH1Ggv_iVs>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:40:38 -0000

--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 14, 2017, at 15:00, Templin, Fred L <Fred.L.Templin@boeing.com> =
wrote:
>=20
> Unless there is operational assurance of some size X>1280, however, =
tunnels have to use fragmentation to guarantee that - at a minimum - =
packets up to 1280 will get through.

Given the growing prevalence of IPv6 using 6LoWPAN on IEEE 802.15.4, =
which is always MTU=3D1280 everywhere, c.f. RFC 4944, I think we can =
forget about ever getting that operational assurance in practice.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 14, 2017, at 15:00, Templin, Fred L &lt;<a =
href=3D"mailto:Fred.L.Templin@boeing.com" =
class=3D"">Fred.L.Templin@boeing.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">Unless there is operational assurance =
of&nbsp;</span><span style=3D"font-family: Menlo-Regular; font-size: =
11px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">some size X&gt;1280, however, =
tunnels have to use fragmentation to&nbsp;</span><span =
style=3D"font-family: Menlo-Regular; font-size: 11px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">guarantee that - at a minimum - packets up to =
1280 will get through.</span></div></blockquote><br =
class=3D""></div><div>Given the growing prevalence of IPv6 using 6LoWPAN =
on IEEE 802.15.4, which is always MTU=3D1280 everywhere, c.f. RFC 4944, =
I think we can forget about ever getting that operational assurance in =
practice.</div><div><br class=3D""></div><br class=3D""><div class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_84E8C621-C295-4C92-ADE5-C75036D27CE0--


From nobody Wed Feb 15 12:42:04 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0011297CD; Wed, 15 Feb 2017 12:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8qb3UdXOEsG; Wed, 15 Feb 2017 12:41:51 -0800 (PST)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::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 93D9C12943B; Wed, 15 Feb 2017 12:41:50 -0800 (PST)
Received: by mail-ua0-x22b.google.com with SMTP id 96so113756649uaq.3; Wed, 15 Feb 2017 12:41:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=tRO1/JwjloxzaaDLnA+Pr6Y37uxXrzmKqYreEiCnE3Y=; b=pttWczG0+SPIAgfhelWG6lWkDgjhhe/L7dcQqB5DBH1ZMwCIDcG1U10/LElO13rNIq nLJ1DXd5J+28jj8JDHu0QH1ciUzRbj+knlCg7vY3RRSvcDyaqWKUqG3a9MQWoJUQKO88 +nSEks7zJaAYTB08DOqFq2cGFNvN7cBTR06AY4+x0Y1Eri3qKiWLdWlY4v3CMDEI3R3g TO31N3aGMuTWIOxGRODPUaChJ5iTGG85xj8/gHHVfS54X8jwrGBjp8Rcg+VoZaGhvQXf wNkk05MhD8NLUPR5E7RU83lNPfT5PpU556UjDy4dorhYumbhdnR2Uqld+FS7Zb0tS9pU s0YA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=tRO1/JwjloxzaaDLnA+Pr6Y37uxXrzmKqYreEiCnE3Y=; b=pjNqPsRgMRQw8O7TkpRaZujHT2iw3d1Rd7HVbpJPacNljiHprFdruicB0HEuFUNUYf EZ1dnzHOfVUNmHLa6iYtV63a5y1EOy96X+MnnPlAXB9S0VnEsmXa1usDSQ+z4LGtHzlQ Y1JPvO3aHKCq4YJis/jMN/8sZTzEvHALIGFXbhvD8SECjrd27795zQasgUSabZHlvTOM fMmOOQn/dDgo8dDc3fMOyw4vh4MyH5cowcWXQyUIKWGuVganp7ER2nsGtOxDlmKUDxoc /QIdEe37zTk4Ho8zQOA/ooRQYAyJ/bZBXu28Uuvc6GXoKHHtaIS60vNXpIOy2ZKzKaic gVlw==
X-Gm-Message-State: AMke39lGhBHlqp/jDX3qumXg8GYb2bHVrOID3IkVIpVN+xBYIb7qvDrF3rlGNME3hGe7kHXK5BWj8b80XDOYSA==
X-Received: by 10.176.3.44 with SMTP id 41mr19083081uat.157.1487191309528; Wed, 15 Feb 2017 12:41:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.81.230 with HTTP; Wed, 15 Feb 2017 12:41:19 -0800 (PST)
In-Reply-To: <HE1PR0501MB21381B97CAB3707DB7D20F31B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
References: <67ab3d39d55840c8a207e2104e6020cd@IL-EXCH01.marvell.com> <CAO42Z2zcc-wCtdbs4VFSu-yWUT0u2PX8r+wpe3Jsj-4vVZUwwg@mail.gmail.com> <eeaa0cc49e104cc68c5b2ae23c44e355@IL-EXCH01.marvell.com> <HE1PR0501MB21381B97CAB3707DB7D20F31B6580@HE1PR0501MB2138.eurprd05.prod.outlook.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 16 Feb 2017 07:41:19 +1100
Message-ID: <CAO42Z2wVBGexYezAzx-Lnmsig2CeErAnTqniv-+7TLRG7XBayQ@mail.gmail.com>
Subject: Re: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: David Mozes <davidm@mellanox.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cZ92f5DGGEeEGjc9SH4okFftbQY>
Cc: "6man@ietf.org" <6man@ietf.org>, "draft-ietf-6man-rfc2460bis@tools.ietf.org" <draft-ietf-6man-rfc2460bis@tools.ietf.org>, IETF Discussion list <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 20:41:53 -0000

On 15 February 2017 at 01:27, David Mozes <davidm@mellanox.com> wrote:
> Hi * ,
> I am also supporting the insertion of in-band telemetry like INT along wi=
th the  actual data packet .

I think it will cause more trouble than any benefits it provides - of
which nobody has described when I've asked multiple times, and the
only one I can think of is to avoid the overhead of full
encapsulation.

> It is for sure a valid use case for the modern networking including data =
center.
> There are several proposals how to embedded telemetry information   some =
of them are with in nvo3 tannling protocols
> (Vxlan-GPE,Geneve) Spring and other  .
> I think that ipv6 hbh is the "cleanest"  way to add such info.
>         1) I don't see any and advantages on the other  proposals (NVO3 ,=
SPRING) over IPV6 hbh.
>         2))As far as security In the IPsec community, AH is pretty much c=
onsidered deprecated, a failed experiment.They  are  prefer to use   ESP fo=
r authentication as well.
>
> The postal system and the letter is very nice e example

It is not an example of insertion. The postal system uses
encapsulation to add information to letters, leaving the envelope and
its contents alone. Envelops might be a thin integrity barrier,
however the postal system usually has laws to make that integrity
barrier much stronger.

>. I will treat the adding ipv6-hbh info as stamps on the envelops ,since w=
e are not touching  the data gram itself just the envelope

EH's are not equivalent to stamps on envelopes, they're equivalent to
pages inside the envelope. The pages inside the envelop are only
intended to be read by the recipient identified by the destination
address on the envelop.

Sorry for excessive bolding, but I'm getting tired of quoting this
text and having it ignored. RFC2460:

"With one exception, extension headers are *not* *examined* or *processed*
   by *any node* along a packet's *delivery path*, until the packet reaches
   the node (or each of the set of nodes, in the case of multicast)
   *identified* in the *Destination Address* field of the IPv6 header."

"The exception referred to in the preceding paragraph is the Hop-by-

   Hop Options header, which carries information that must be examined
   and processed by every node along a packet's delivery path, including
   the source and destination nodes.  The Hop-by-Hop Options header,
   when present, must immediately follow the IPv6 header.  Its presence
   is indicated by the value zero in the Next Header field of the IPv6
   header."

In other words no mid-flght insertion allowed, even of the HBH option.






>
> Thx
> David
> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Tal Mizrahi
> Sent: Tuesday, February 14, 2017 3:37 PM
> To: Mark Smith <markzzzsmith@gmail.com>
> Cc: draft-ietf-6man-rfc2460bis@tools.ietf.org; 6man@ietf.org; IETF Discus=
sion list <ietf@ietf.org>; 6man-chairs@ietf.org
> Subject: RE: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (In=
ternet Protocol, Version 6 (IPv6) Specification) to Internet Standard
>
> Hi Mark,
>
> I certainly agree that hop-by-hop insertion/modification introduces poten=
tial security vulnerabilities.
> Therefore, as I pointed out below, I would recommend to tackle this by de=
fining something along the lines of =E2=80=9CHop-by-hop extensions can be i=
nserted/removed/modified/processed by intermediate nodes *if* [=E2=80=A6=E2=
=80=A6..] and the possible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D
>
> For example, hop-by-hop handling can be restricted only to a single admin=
istrative domain, or only to tunnels (as in the zero checksum case).
>
> Regards,
> Tal.
>
>>-----Original Message-----
>>From: Mark Smith [mailto:markzzzsmith@gmail.com]
>>Sent: Monday, February 13, 2017 6:07 PM
>>To: Tal Mizrahi
>>Cc: 6man@ietf.org; IETF Discussion list; draft-ietf-6man-
>>rfc2460bis@tools.ietf.org; 6man-chairs@ietf.org
>>Subject: [EXT] Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt>
>>(Internet Protocol, Version 6 (IPv6) Specification) to Internet
>>Standard
>>
>>External Email
>>
>>----------------------------------------------------------------------
>>Hi,
>>
>>
>>
>>On 14 February 2017 at 00:43, Tal Mizrahi <talmi@marvell.com> wrote:
>>> Hi,
>>>
>>>
>>>
>>> Good discussion regarding the text about the hop-by-hop extension.
>>>
>>>
>>>
>>> In my opinion there is a valid use case for intermediate nodes that
>>> insert/remove/modify/process hop-by-hop extensions. Examples: IOAM, INT=
.
>>>
>>> Since there is a use case, I believe we need explicit text about
>>> intermediate handling of hop-by-hop extensions.
>>>
>>
>>
>>Imagine you sent a letter through the postal system, and the postal
>>system wanted to add information to that letter, that is then to be
>>removed before the letter arrives at its final destination.
>>
>>The postal system have at least two choices as to how to add that informa=
tion.
>>They could:
>>
>>(a) unstick your envelope's seal, insert the information, reseal the
>>envelope so well you can't tell and send it on its way, some how
>>flagging to a destination device within the postal system that this
>>specific envelop needs to be openned, a specific page removed, and then r=
esealed.
>>
>>(b) take a new envelope with new internal postal system source and
>>destination address information, insert your letter without touching it
>>in addition to the new information, and then sending it on its way.
>>
>>Imagine that the information to be added by the postal system is
>>printed on the same type of paper and is written in the same font as
>>you've chosen to use to write your letter.
>>
>>Have a think about these two methods, what could fail with each of
>>them, and what the consequences may be if any of those failures occur.
>>Have a think of the benefits of each method, and whether they're worth
>>it compared to the failure mode costs and consequences for the method.
>>
>>>
>>>
>>> This [somewhat] reminds me of the discussion a few years ago about
>>> the IPv6/UDP zero checksum. The WG ended up defining that =E2=80=9CZero
>>> checksum is permitted in IPv6/UDP *if* [=E2=80=A6=E2=80=A6..] and the p=
ossible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>>>
>>>
>>
>>That is a far more trivial change to the packet - it is allowing a
>>value in an existing field that was formerly prohibited, and nodes that
>>did not understand that value would drop the packet because that is
>>what they had been specified to do if they received this prohibited value=
. In other words, existing implementations '
>>behaviour when this formerly unexpected value was encountered had
>>already been specified and deployed.
>>
>>
>>>
>>> I would argue that regarding hop-by-hop extension handling we also
>>> need to define that =E2=80=9CHop-by-hop extensions can be
>>> inserted/removed/modified/processed by intermediate nodes *if* [=E2=80=
=A6=E2=80=A6..]
>>> and the possible consequences are [=E2=80=A6=E2=80=A6..]=E2=80=9D.
>>>
>>
>>Some things that are possible to do in theory shouldn't be done in
>>practice, because the consequences when their implementations fail can
>>be severe and outweigh the benefits.
>>
>>In theory, inserted EHs will be removed 100% of the time. In practice
>>they won't be, because implementations can have bugs and they can also
>>fail in unexpected ways e.g., hardware faults.
>>
>>Regards,
>>Mark.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Feb 15 13:09:14 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19E53129B67; Wed, 15 Feb 2017 13:09:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 q35r9USeQVjr; Wed, 15 Feb 2017 13:09:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 70598129B64; Wed, 15 Feb 2017 13:09:10 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FL8m87008923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:08:49 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: otroan@employees.org, Stewart Bryant <stewart.bryant@gmail.com>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <b7a65660-2cc5-8461-c1c4-21b94fd65166@isi.edu>
Date: Wed, 15 Feb 2017 13:08:47 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <57307617-C87C-4430-B92A-59E28C6779CD@employees.org>
Content-Type: multipart/alternative; boundary="------------007E84B2003B9732A6018B39"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sGTNgTerij6CnqRIMiIcgG3ROLU>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:09:12 -0000

This is a multi-part message in MIME format.
--------------007E84B2003B9732A6018B39
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Hi, Ole,


On 2/14/2017 10:33 AM, otroan@employees.org wrote:
>> *If*  you care about packet loss, then your only option is to probe the path with with
>> synthetic data that exactly mimics the live data, or not to probe at all and live
>> with the 1280. As I said 1280 is pretty close to 1496 which is all most networks
>> will give you in practice.
> Yes, but sending at 1280 does not work for IP tunnels. The whole purpose of the minimum MTU was to give space for tunnel headers (1500-1280).
I'm in the process of revising draft-intarea-tunnels to make this more
clear, as well as to provide a TSV ART review of this doc, but in preface:

There are two IPv6 minimum sizes: link MTU of 1280 and EMTU_R of 1500.

Support for source fragmentation and the difference between these two
values is what gives space for tunnel headers.

No amount of link MTU management can ever avoid source fragmentation
without violating the link MTU minimums in RFC2460.

Joe

--------------007E84B2003B9732A6018B39
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, Ole,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/14/2017 10:33 AM,
      <a class="moz-txt-link-abbreviated" href="mailto:otroan@employees.org">otroan@employees.org</a> wrote:<br>
    </div>
    <blockquote
      cite="mid:57307617-C87C-4430-B92A-59E28C6779CD@employees.org"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap=""><b class="moz-txt-star"><span class="moz-txt-tag">*</span>If<span class="moz-txt-tag">*</span></b>  you care about packet loss, then your only option is to probe the path with with
synthetic data that exactly mimics the live data, or not to probe at all and live
with the 1280. As I said 1280 is pretty close to 1496 which is all most networks
will give you in practice.
</pre>
      </blockquote>
      <pre wrap="">Yes, but sending at 1280 does not work for IP tunnels. The whole purpose of the minimum MTU was to give space for tunnel headers (1500-1280).
</pre>
    </blockquote>
    I'm in the process of revising draft-intarea-tunnels to make this
    more clear, as well as to provide a TSV ART review of this doc, but
    in preface:<br>
    <br>
    There are two IPv6 minimum sizes: link MTU of 1280 and EMTU_R of
    1500.<br>
    <br>
    Support for source fragmentation and the difference between these
    two values is what gives space for tunnel headers.<br>
    <br>
    No amount of link MTU management can ever avoid source fragmentation
    without violating the link MTU minimums in RFC2460.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------007E84B2003B9732A6018B39--


From nobody Wed Feb 15 13:12:50 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBCBA129B86; Wed, 15 Feb 2017 13:12:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 OuXQK4ryeb_2; Wed, 15 Feb 2017 13:12:41 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 7AF311297E4; Wed, 15 Feb 2017 13:12:41 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLCF9V009704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:12:15 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
Date: Wed, 15 Feb 2017 13:12:14 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com>
Content-Type: multipart/alternative; boundary="------------31EA21CD2E92C7ACFA919F7B"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o6_4MpBmX-jTRIMGWpP7fvp3bjU>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:12:43 -0000

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

Brian (et al.),


On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>> practice the
>> Internet breaks the mechanism. However it breaks it is a way that seems
>> disruptive to some user traffic. The document is really guidance
>> one how hosts might use  ICMP for optimization, and arguable need
>> not be a standard at all.
> I think that's a mischaracterisation of the mechanism (and the draft).
> PMTUD is not an optimisation. Without it, you get black holes
PMTUD is an optimization to avoid fragmentation.

Without it, you use fragmentation (which has overheads and other
consequences, notably for IPv4).

However, it is only *with* PMTUD (and ICMP blocking) that you get black
holes.

Joe

--------------31EA21CD2E92C7ACFA919F7B
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Brian (et al.),<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/10/2017 11:45 AM, Brian E
      Carpenter wrote:<br>
    </div>
    <blockquote
      cite="mid:9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">practice the
Internet breaks the mechanism. However it breaks it is a way that seems
disruptive to some user traffic. The document is really guidance
one how hosts might use  ICMP for optimization, and arguable need
not be a standard at all.
</pre>
      </blockquote>
      <pre wrap="">I think that's a mischaracterisation of the mechanism (and the draft).
PMTUD is not an optimisation. Without it, you get black holes</pre>
    </blockquote>
    PMTUD is an optimization to avoid fragmentation.<br>
    <br>
    Without it, you use fragmentation (which has overheads and other
    consequences, notably for IPv4).<br>
    <br>
    However, it is only *with* PMTUD (and ICMP blocking) that you get
    black holes. <br>
    <br>
    Joe<br>
  </body>
</html>

--------------31EA21CD2E92C7ACFA919F7B--


From nobody Wed Feb 15 13:19:45 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD2F129B8C; Wed, 15 Feb 2017 13:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1yaD72dShZB; Wed, 15 Feb 2017 13:19:38 -0800 (PST)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::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 CDC551297E8; Wed, 15 Feb 2017 13:19:38 -0800 (PST)
Received: by mail-pg0-x230.google.com with SMTP id z67so7923414pgb.1; Wed, 15 Feb 2017 13:19:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=nh9SNUUpdm9C/xHmZYhUSt0KWBBqFOBF1uOkKXZsXyg=; b=YRIGnOLTUX5FeObc8LFa85D+tuqINzcYE8pZ75+1qr/tTDa/wvxUhDn6zYg+xqOZAo OMs73r+jbmWTOpcp9NhA0AO/ETtCEccF9zq3FjtobEGKcMApWePhGL0Se0OT/QwYS44M 3XPyLFj1ga7ldc6UwyXyg/v4BO+FrAWtHFlBfv8ftAmdRD3lgnXNpBYMQ6PZreRlRf01 kI6BmZB4amzciqHZRsbXlfxxbPGRLnAGQnM9Tr2nte6zzsn5dhw8oGxvFWQqoKTngxH2 c2EwgplWq3NWvKCQ12jliS6tKzdfSBe8V9N6PWbyekqHE3r6v5FBQHmoD4Gr/mYeoYL1 15xA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=nh9SNUUpdm9C/xHmZYhUSt0KWBBqFOBF1uOkKXZsXyg=; b=N50uOEaP5iqCsKGSuQ7y5VSEtM32ZWX1iXFqCsepKSPp5p+mXKqe2rO2lHxrcbrPgk l/6P+01W/ukw6hsbtvxfTNwixPcRTSQHDmU4ce+u5fJ4p8O4PQGMICw58voLm5LIhv1G RRY36T3PE9VPSMbyPwRGIVS4gzTcYuWqb/NNenN8RRZ08nJVUIs4FtvUUjLKBWIKy7X/ cVJm7YfPXJjRMXWy01zPdallFOgAksBiQy2wdh0m29w4qgxnzHrEM6ZdWeAZPXQhzu8N hwTtOZJgBGU0zpvKo8cTGhmUa16d1HujSP5GRq1JhaniRUDZskCG8W4VvugCpAV02xdl l/Xg==
X-Gm-Message-State: AMke39nL+f8YfIxohlzQO9dF5siABL6HpdGS49dl7ZRv19FqjbvAXqgqE/d5tHOGWaNsRw==
X-Received: by 10.84.134.36 with SMTP id 33mr20815724plg.151.1487193578440; Wed, 15 Feb 2017 13:19:38 -0800 (PST)
Received: from [192.168.178.21] ([118.148.112.221]) by smtp.gmail.com with ESMTPSA id y6sm9341615pgc.1.2017.02.15.13.19.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 13:19:37 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: otroan@employees.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com>
Date: Thu, 16 Feb 2017 10:19:39 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i-LOglNi6EGszEKqcpY7xNZhuII>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:19:40 -0000

On 15/02/2017 22:31, otroan@employees.org wrote:
> Brian,
> 
>>>> Brian, changing the 64 bit boundary is such a big change that I would
>>>> claim it is far outside the scope of advancing 4291 to Internet standard.
>>>>
>>>
>>> Agreed.
>>
>> Of course. The point is only that it's a parameter in the design of SLAAC,
>> whose value is set by the address architecture.
> 
> If your statement is that we only have the 64 bit boundary because of SLAAC I believe you are wrong.
> Can you provide any support for that view?

No, that's not what I'm saying. I'm saying that SLAAC - by design - would work
with any reasonable IID length, but we've chosen to fix it at 64.

> If I understand you correctly, your proposal is to change the fixed 64 bit Interface-ID length in IPv6 to a variable one, with an exception for links where SLAAC is used.

No. At least not in the foreseeable future. But we should allow for the fact that if
prefixes between /64 and /127 are used, routing needs to just work. That's all.

> How do you practically suggest to do this, given the issues raised in https://tools.ietf.org/html/rfc7421#section-4.1 ?

I'm not suggesting any change to normal subnets, where all those issues apply.
I can't see how /64 can be changed for them, without changing a great many
things.
 
> Do you think this change is appropriate in the context of advancing 4291?

I don't think I have suggested text that would lead to a single instruction in
running code being changed.

    Brian

> Do you have implementation reports and are there not interoperability problems here?
> 
> Best regards,
> Ole
> 
> 
> 


From nobody Wed Feb 15 13:26:33 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DC0D129556; Wed, 15 Feb 2017 13:26:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 crYJjuRxfOya; Wed, 15 Feb 2017 13:26:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 2BCEF129849; Wed, 15 Feb 2017 13:26:27 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLP4gL012163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:25:05 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <196e8c39-784a-3a25-b6ab-d7eaa664f0fa@isi.edu>
Date: Wed, 15 Feb 2017 13:25:03 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <58A33D08.4090505@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S2EO2F2k5Gmu7bS8N6UDi52kbNc>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:26:28 -0000

Hi, Gorry (et al.),

On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
> There is no mention that paths including tunnels can eat ICMPv6 PTB
> messages on the tunnel segment, blackholing them, which prevents
> reaching the destination. 

Nor should there be, IMO.

A tunnel is a link layer to the network whose packets it transits.

ICMPs generated inside a tunnel aren't "eaten", so much as they operate
at a different layer for a different reason (e.g., to tune
ingress-egress source fragmentation of encapsulated packets).

PTB messages inside a tunnel are (IMO) most correctly interpreted by the
ingress (which is an *interface* on a router or host, most correctly
IMO) as changing the MTU of the tunnel as a link. If that MTU change
affects packets that arrive later, then it would be the router where the
ingress is attached that would generate the ICMP, never the (ingress)
interface whose MTU is insufficient.

Again, I'm in the process of updating draft-ietf-intarea-tunnels to be
much more clear on this point (the update should be issued in a day or two).

Joe


From nobody Wed Feb 15 13:26:57 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD891129556; Wed, 15 Feb 2017 13:26:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9fXaPWLlugr5; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 7394A129B96; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: by mail-pg0-x241.google.com with SMTP id 75so12085933pgf.3; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=oubWh6KObmZKhsFrc9dZol3y1lYgRBAryBnz3gPWMOM=; b=fho/bPrw9PNcJ05R3n1nqEAxNCTWmXX7O1qZfHb+swuq+BZ4g+tI1ET6yLa1Qc+Hpt mmICk1uXHWV/bB9PXOmUj+cVeF422LIHicLtRiveJlJygWGsM9aHus+QhNFF0Uq4RdoE UxDXtqEoz3Ye8O9hS72vnoUG7NS0b2FXQasJI94SmuwT/9EGUWcmYKDlcp6HkqyfaTS+ RRAadJvvLeapUEe8B477ZYBgTcXGmHhEG304dJvoF0PIJ3nfVXV6IXGTr4GQIwf2mgzY WlMreQvyxNPzQtvx2LjnVp9Tre4QW8EIPyf1MbZpTdm0UV3A4el79cIUcla8S21czqrk rEiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=oubWh6KObmZKhsFrc9dZol3y1lYgRBAryBnz3gPWMOM=; b=R6gt9/SEIRwfWRa7tWiZeGjNOA2vsskLs+HO3/EGV2Mus+fQe+hNDi4yBV5CclR9G3 idvxTZkykU2I0mxmEMOYJofeMkQsaDtlK6lBMxjT53ObV9Ek+ikZCgtIfQlY4wegcxHp PHtAmJZEEtD8X0Z0VqMuQKOGTkMvlgTUxXc6nSgyyI1e+/joZo1jastmuXJpwBM1xiNg tqhmW/fYZmvpYN9cj5HU57JN3mfPLxTwKlFQQoKBanWd78jVpj3FdM3z/8ErH8ErwVvS tkC6a4K0FqFrPdPTJZmIkeABaojlEN/YB2/72YOkjZ7vKaxVXmIi0P9PEMWilZTBlvKw rywQ==
X-Gm-Message-State: AMke39nnqJdItD3yHNKgTEArbmlEG+DGWDgwosr3GSSfACnFtKH+79463bkcfBgEoaxpwg==
X-Received: by 10.98.212.23 with SMTP id a23mr40461055pfh.18.1487194010033; Wed, 15 Feb 2017 13:26:50 -0800 (PST)
Received: from [192.168.178.21] ([118.148.112.221]) by smtp.gmail.com with ESMTPSA id n70sm9250021pfg.34.2017.02.15.13.26.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 13:26:49 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Joe Touch <touch@isi.edu>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com> <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
Date: Thu, 16 Feb 2017 10:26:50 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GPek12rmspVw13nFE6-jsw8EfWs>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:26:52 -0000

On 16/02/2017 10:12, Joe Touch wrote:
> Brian (et al.),
> 
> 
> On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>>> practice the
>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>> disruptive to some user traffic. The document is really guidance
>>> one how hosts might use  ICMP for optimization, and arguable need
>>> not be a standard at all.
>> I think that's a mischaracterisation of the mechanism (and the draft).
>> PMTUD is not an optimisation. Without it, you get black holes
> PMTUD is an optimization to avoid fragmentation.
> 
> Without it, you use fragmentation (which has overheads and other
> consequences, notably for IPv4).

In IPv6, you don't even know you *need* fragmentation without PMTUD,
since only the source is allowed to fragment. (That was one of the
many failure modes for 6to4, which is why the only safe approach was
to use 1280 always.) 

> However, it is only *with* PMTUD (and ICMP blocking) that you get black
> holes.

True for v4.

   Brian


From nobody Wed Feb 15 13:27:15 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9905B129BA5; Wed, 15 Feb 2017 13:27:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 r2EkeM5iOPLs; Wed, 15 Feb 2017 13:27:08 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 D2602129BA8; Wed, 15 Feb 2017 13:27:02 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLQOct012415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:26:24 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu>
Date: Wed, 15 Feb 2017 13:26:22 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <58A33D08.4090505@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yd-Wz7yH8PAqvVMmQHOQJXqH34M>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:27:09 -0000

Hi, Gorry (et al.),

Again, the following text should not drift into discussing how tunnels
are handled IMO. That should be addressed in a different document (and I
don't think it's troublesome at all if viewed correctly).

Joe


On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
> - Introdueces a significant vulnerability.  A rogue PTB message that
> reduces the PMTU to a minimum, can result in a path too small to carry
> an encapsulated packet. (Recently noted by Fernando Gont).
>
> Moreover, other layers view ICMP messages with suspicion and have long
> noted the need to check ICMP payload and match only packets that
> relate to actual 5-tuples in use (effectively reducing vulnerability
> to off-path attacks). For example, the Guidelines for UDP, rfc5405bis,
> state:
>
> " Applications SHOULD appropriately validate the payload of ICMP
>    messages to ensure these are received in response to transmitted
>    traffic (i.e., a reported error condition that corresponds to a UDP
>    datagram actually sent by the application). …“
> - clearly handling this in IP-layer tunnels can be troublesome, but
> that's a problem that should be described, not obscured. 


From nobody Wed Feb 15 13:32:53 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E515D129862; Wed, 15 Feb 2017 13:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 ngSgcK46G-_l; Wed, 15 Feb 2017 13:32:45 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 49B28129860; Wed, 15 Feb 2017 13:32:45 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1FLWMH2013445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 15 Feb 2017 13:32:22 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <9a1a0a47-d8fd-5cf9-0244-7ce624d58470@gmail.com> <aa18ed73-97e4-ac66-8667-8367d71bb03d@isi.edu> <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <9be213f6-59a4-459e-0312-7c3720c567b3@isi.edu>
Date: Wed, 15 Feb 2017 13:32:20 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <cdc76c31-933a-c17f-7efd-08d399768159@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WE6bDPooQfUTsYIAcVBI7s5arbY>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:32:47 -0000

Hi, Brian,


On 2/15/2017 1:26 PM, Brian E Carpenter wrote:
> On 16/02/2017 10:12, Joe Touch wrote:
>> Brian (et al.),
>>
>>
>> On 2/10/2017 11:45 AM, Brian E Carpenter wrote:
>>>> practice the
>>>> Internet breaks the mechanism. However it breaks it is a way that seems
>>>> disruptive to some user traffic. The document is really guidance
>>>> one how hosts might use  ICMP for optimization, and arguable need
>>>> not be a standard at all.
>>> I think that's a mischaracterisation of the mechanism (and the draft).
>>> PMTUD is not an optimisation. Without it, you get black holes
>> PMTUD is an optimization to avoid fragmentation.
>>
>> Without it, you use fragmentation (which has overheads and other
>> consequences, notably for IPv4).
> In IPv6, you don't even know you *need* fragmentation without PMTUD,
> since only the source is allowed to fragment. (That was one of the
> many failure modes for 6to4, which is why the only safe approach was
> to use 1280 always.) 
A compliant IPv6 source can send 1500 byte packets that a source without
PMTUD, which would need to be fragmented based on the assumption that
the path MTU is at its required minimum of 1280.

A compliant IPv6 source can send larger packets, which would work if the
receiver supported larger reassembly limits than 1500. There is no
currently standard mechanism to determine the receiver reassembly limit
in IPv6, but this IS supported in TCP.

Joe


From nobody Wed Feb 15 13:34:10 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E16EE129867; Wed, 15 Feb 2017 13:34:08 -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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAeQnTwd80HZ; Wed, 15 Feb 2017 13:34:07 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 1527E129866; Wed, 15 Feb 2017 13:34:07 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 15 Feb 2017 21:34:07 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id A574AD788E; Wed, 15 Feb 2017 13:34:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=ry+9XELTne46a3UwVqo10VqRgzg=; b= lqCncTsuzr7+COWLIcQ4CF7UzEVrJyAgMnlJJrQs1C5qZLsK3IAYeDrqnV/7reBt uODRy+yV0WfQ4Gc4IJ+cEYwXzgccWqtJO7Oa2PLuhn9411JXl+EfptxOQaeQF5C6 jm1Ux6/CptBw/8Gm02/Vs0tMoRGcSP8fToIbTJ2vnZo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=IEML55kw+rWhwe6EaXPA/pS mMzO7iiz7Jlq/TV39Vmr266QFZ3acB/HasmWl3BLBWMwRZOFjIINUyUmba+tdnEA L20nesukYiq8jOSEGEimKzCdePy0Rb9tnyCCc+5a3qkhpQ4gh/cVmva6yYx8WPat 61xjdvF+I20QzOOTjoHs=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 78DE3D788D; Wed, 15 Feb 2017 13:34:06 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id BA67A8BC9F36; Wed, 15 Feb 2017 22:34:14 +0100 (CET)
From: otroan@employees.org
Message-Id: <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_8DF724A5-A49A-42FC-94CA-A61B929DF27A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Wed, 15 Feb 2017 22:34:13 +0100
In-Reply-To: <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k0DAh8v7w7TbNEJFc__N7tci4MU>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:34:09 -0000

--Apple-Mail=_8DF724A5-A49A-42FC-94CA-A61B929DF27A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

>>>>> Brian, changing the 64 bit boundary is such a big change that I =
would
>>>>> claim it is far outside the scope of advancing 4291 to Internet =
standard.
>>>>>=20
>>>>=20
>>>> Agreed.
>>>=20
>>> Of course. The point is only that it's a parameter in the design of =
SLAAC,
>>> whose value is set by the address architecture.
>>=20
>> If your statement is that we only have the 64 bit boundary because of =
SLAAC I believe you are wrong.
>> Can you provide any support for that view?
>=20
> No, that's not what I'm saying. I'm saying that SLAAC - by design - =
would work
> with any reasonable IID length, but we've chosen to fix it at 64.
>=20
>> If I understand you correctly, your proposal is to change the fixed =
64 bit Interface-ID length in IPv6 to a variable one, with an exception =
for links where SLAAC is used.
>=20
> No. At least not in the foreseeable future. But we should allow for =
the fact that if
> prefixes between /64 and /127 are used, routing needs to just work. =
That's all.
>=20
>> How do you practically suggest to do this, given the issues raised in =
https://tools.ietf.org/html/rfc7421#section-4.1 ?
>=20
> I'm not suggesting any change to normal subnets, where all those =
issues apply.
> I can't see how /64 can be changed for them, without changing a great =
many
> things.
>=20
>> Do you think this change is appropriate in the context of advancing =
4291?
>=20
> I don't think I have suggested text that would lead to a single =
instruction in
> running code being changed.

CURRENT (RFC4291bis):

   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
   on inter-router point-to-point links.  However, the Interface ID of
   all unicast addresses, except those that start with the binary value
   000, is required to be 64 bits long.  The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421]

PROPOSED:

    IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
   on inter-router point-to-point links.  However, the Interface ID of =
unicast
   addresses used for Stateless Address Autoconfiguration [RFC4862] is =
required
   to be 64 bits long. The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421]


My reading of the proposed text, which certainly may be wrong, given =
that English is not my first language, is that it leaves the =
Interface-ID length of links _not_ using SLAAC undefined, i.e. not fixed =
at 64. Is there any other way to interpret this sentence?

The proposed text appears to make the Interface-ID length an operational =
choice.
How is that _not_ changing the 64 bit boundary?

Best regards,
Ole

--Apple-Mail=_8DF724A5-A49A-42FC-94CA-A61B929DF27A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpMlWAAoJEL7aWKiYQt92I0EP/jKt1FTOoNVaas0jPvrVy1vG
Wq8Cfksw3C6hAeK5xut/anp+HpMpN0OpTvKKWiZB8O17DNjCU9Y0woxMSvtfYSUx
EnuM9Oe4kq25M4zKXx99AANKfDpb+WwwXp+B7xFniS9w75GaNtbF4/w4psDolSng
UfE/OKMwKD1HHTTinkwoi+RNaGC27lundspMtW5QYyK4kLaYjbQ3GnnEqPCKt2vv
eEHm0zQhuXtAO5Tav+NccGpBID4tDZU9ZlSca55hvSI6n+ODLsrefLSGdUz0u/Vb
QrY5IqeIswMr4TgcnS81zZHyOZEcYVF3jLMdv0YD5BEpcacTBZsWRnYyOiWXonTG
+kvgaCR4Di5YFLMOPxYrhFoGyG99/cr9ogxY/0qmPbP65zurq93AKfd94cv2U/fP
aWpsK8ZEAYvy9cG8dn3UVqZ/oq49O519AJFLdD2Te7T9XREB2LHYmc51J6qkqdKL
svBhnIxSgQAYNg5J1KQMMC9d0rUcct3/BqFnA/BQHCjq0ZPNIBuq5y6DGFsu+5Qa
rE7Zzhr5rL4U+riyx38IikZ5qDT8zIIIdqr00AWvrc148p4n+uPc3b2lBqIb8NH3
T8MMoIQj9cz8K/pY4NkwlgYYGoXNTIKGgFbmofSs5h14uRlkucan9YfPwSaSv8Kf
6QhuhCpl9qG834omHois
=SpjS
-----END PGP SIGNATURE-----

--Apple-Mail=_8DF724A5-A49A-42FC-94CA-A61B929DF27A--


From nobody Wed Feb 15 13:36:38 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25B58129455 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 13:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 CUg-UNPYow5L for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 13:36:31 -0800 (PST)
Received: from bin-vsp-out-01.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 53EE71296D1 for <ietf@ietf.org>; Wed, 15 Feb 2017 13:36:31 -0800 (PST)
X-Halon-ID: ce14895f-f3c6-11e6-a561-005056917a89
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [83.209.158.27]) by bin-vsp-out-01.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 15 Feb 2017 22:36:26 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: "Phillips, Addison" <addison@lab126.com>, Randy Presuhn <randy_presuhn@alumni.stanford.edu>, "ietf@ietf.org" <ietf@ietf.org>, "slim@ietf.org" <slim@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com> <ba7f397b-59ae-c549-cd1a-e22e1b73b3c1@omnitor.se> <e1ce6bbaaf624c1e88d31c72440093ba@EX13D08UWB002.ant.amazon.com>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <a5df00c7-fe78-aee8-d7da-30d65e476d7f@omnitor.se>
Date: Wed, 15 Feb 2017 22:36:24 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <e1ce6bbaaf624c1e88d31c72440093ba@EX13D08UWB002.ant.amazon.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H-xATPEhcm5ZtbZPviVttMLZfCU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:36:35 -0000

Addison,

Den 2017-02-15 kl. 18:12, skrev Phillips, Addison:
> Gunnar replied:
>> Den 2017-02-14 kl. 21:39, skrev Phillips, Addison:
>>> I have some allergy to the SHALL language: there is no way to automatically
>> determine conformance. Many language tags represent nonsensical values, due
>> to the nature of language tag composition. Content providers need to use care
>> in selecting the tags that they use and this section is merely pointing out good
>> guidance for tag selection, albeit in a heavy-handed way. BCP47 RFC 5646
>> Section 4.1 [1] already provides most of this guidance and a reference to that
>> source might be useful here, if only because that document requires it:
>>> <quote>
>>>      Standards, protocols, and applications that reference this document
>>>      normatively but apply different rules to the ones given in this
>>>      section MUST specify how language tag selection varies from the
>>>      guidelines given here.
>>> </quote>
>>>
>>> I would suggest reducing the SHALL items to SHOULD.
>> Accepted.
>> That also opens up for another use we have discussed before but been advised
>> to not use. That is to indicate use of written language by attaching a script
>> subtag even if the script subtag we use is suppressed by BCP 47. We can dro that
>> need however, with the use of the Zxxx script subtag for non-written, and clearly
>> include that usage in our specification as required from BCP 47.
> I don't necessarily think that mandating a script subtag as a signal of written content (vs. spoken content) is that useful. In most protocols, the written nature of the content is indicated by the presence of text. Trying to coerce the language modality via language tags seems complicated, especially since most language tags are harvested from the original source. Introducing processes to evaluate and insert or remove script subtags seems unnecessary to me. That said, I have no objection to content using script subtags if they are useful.
In this case we are negotiating use of media streams before they are 
established, so that the connection will be made between best capable 
devices and call participants. There is no indication in the media 
coding parameters available to tell if text will be carried in video.  
So, if we want to be able to specify the three modalities possible in 
video we needto have differentiated notations for them: 1. view of a 
signing person, 2. view of a speaking person, 3. Text.      For 1. the 
signing person, it is simple, because the language subtags are explicit 
in that they indicate sign language. But for the two others I was not 
aware of any useful way before I was informed about the Zxxx script subtag.
Now, the reasoning about the need for these to be possible to 
distinguish caused me to specify that for the view of the signing person 
we use the Zxxx script subtag and for any text we do not need to specify 
any script subtag.
The view of the speaking person is the only very important alternative 
of the four identified "silly states", and that was already included in 
section 5.2. But both Bernard and I wanted to see the "silly states" 
chapter sharpened up and real alternatives sorted out and specified.
>
>>> I'm not sure what #2 really means. Shouldn't text captions be indicated by the
>> written language rather than the spoken language? And I'm not sure what
>> "spoken/written language" means.
>> #2 was: "
>>
>> 2.    Text captions included in the video stream SHALL be indicated
>> by a Language-Tag for spoken/written language."
>>
>> Yes, the intention is to use written language in the video stream. There are
>> technologies for that.
> I'm aware of that. My concern is that in this case "spoken/written" is applied to "text captions", which are not spoken be definition? This section is talking about the differences between identifying spoken and written language. The text captions fall into the written side of the equation, no?
>
> I'd probably prefer to see something like "2. Text captions included in the video stream SHOULD include a Language-Tag to identify the language."
Yes, that is a way to avoid mentioning spoken/written that apparently is 
confusing when the subtag in this case is used for written modality.
>
>> Since the language subtags in the IANA registry are combined for spoken
>> languages and written languages, I call them Language-Tags for spoken/written
>> language.
> The language subtags are for languages--all modalities. My comment here is that "spoken/written" adds no information.
Spoken/written is different from signed that is the "normal" modality 
for video.
>
>> It would be misleading to say that we use a Language-Tag for a written
>> language, because the same tag could in another context mean a spoken
>> language.
> One uses a Language-Tag for indicating the language. When the text is written, sometimes the user will pick a different language tag (zh-Hant-HK) than they might choose for spoken text (yue-HK, zh-cmn-HK, etc.). Sometimes (actually, nearly all the time except for special cases) the language tag for the spoken and written language is the same tag (en-US, de-CH, ja-JP, etc.). Again, the modality of the language is a separate consideration from the language. Nearly always, it is better to use the same tag for both spoken and written content rather than trying to use the tag to distinguish between them: different Content-Types require different decoders anyway, but it is really useful to say "give me all of the 'en-US' content you have" or "do you have content for a user who speaks 'es'"
>
>> Since we have the script subtag Zxxx for non-written, we do not need to
>> construct an explicit tag for the written language tag, it should be sufficient with
>> our specification of the use in our case.
> In case it isn't clear aboe, I oppose introducing the 'Zxxx' subtag save for cases where the non-written nature of the content is super-important to the identification of the language.
There is a possible alternative in RFC 4796, the SDP Content attribute, 
where "speaker" can be identified.  But that does not easily allow for 
describing alternative use of video for sign language or view of a 
speaking person.

So, the alternative to using Zxxx is as I see it to not be able to 
specify text in the video stream. Good interoperability of text in the 
text stream is so much more important so I am prepare to go that way if 
it is needed. Bernards view would be interesting here.
>> In my latest recent proposal, I still have a very similar wording. Since you had
>> problems understanding it, there might still be a need to tune it. Can you
>> propose wording?
>> This is the current proposal:
>>
>> "   2.    Text captions included in the video stream SHOULD be indicated
>>     by a humintlang attribute with Language-Tag for spoken/written language.
>> "
> I did that above. I think it is useful not to over-think it. When I see "Content-Type: video/mpeg; Content-Language: en-GB", I rather expect audio content in English and not written content (although the video stream might also includes pictures of English text such as the titles in a movie). When, as in this case, setting up a negotiated language experience, interoperability is most aided by matching the customer's language preferences to available resources. This is easiest when customers do not get carried away with complex language tags (ranges in BCP 47 parlance, e.g. tlh-Cyrl-AQ-fonupa) and systems do not have to introspect the language tags, inserting and removing script subtags to match the various language modes.
>
> Addison
/Gunnar
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 15 13:52:32 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10EB0129867; Wed, 15 Feb 2017 13:52:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wmjJJXQs0jdH; Wed, 15 Feb 2017 13:52:24 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 4E3A3129876; Wed, 15 Feb 2017 13:52:16 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id o64so8578844pfb.1; Wed, 15 Feb 2017 13:52:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=AhFYVlQ4vP4FaIspOr1u2rjZdyjqUTYiD0elAtMGkpU=; b=j8eh2r/1vbM3Ya5xq+ZogJcghMWy1Y5HdG92eK7ghrZmpRTM5bLhNJsraD73wRXSN9 9k560bmjA+SPL0MgQhbsM1lL6np2JSXXCqcjR4cH9caxxuKGPGZqO9yC7UzKSd9l6H+I EQWsnS28NiQWFyDAvjUdSFhoHpj607n70TjVnsiokYNgfRUb81tuTM/Yk5BU55Kay/dl fFKjou9vaZbslS9yTOStfrpso53D7YyNkr0CaUtCzqJlep/ndDhPc1LKPXkfI+fWhl9K u/RhDR7iEpQcs7Sc1NdMb8MQQxe7yRi5IiKNF7evFcDNpJyKLCAlYRlo8kQOQzVX/6wz xFKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=AhFYVlQ4vP4FaIspOr1u2rjZdyjqUTYiD0elAtMGkpU=; b=YCqINKQq2Ubw2h/B40Rx3FOER62AJeXKj2PLACUREqKyxqqfck9wCmRn89vL4Ol/xr QU41F4eMvp8LNI9dpD/n1JPQ2JToX2ZCcpKqiIdD7IpLUkuS6hXfrc1UlPk/fAxUNg5w ViSvnP1a8toWmCLDFM3k/JT/jqi/ZugeyTTOgMRiCAbxp42G/d1hq7vQGhxoSx5O0J66 qwTDVrP0sqJBcjqbdKgOcTBjc6HldT9/Mo7Jap8orydvdzgEEpc1dOriSOmJKHvYKBE4 4IJ4Vc2PIcbG5Zd3FZ1GXZXpWtdhfhCTR24OpY7018/vcCkVEcEDmJc6TpTiwjFFIPSj NdIQ==
X-Gm-Message-State: AMke39kM9NWymd6t59eP411/TD5NIf7t2ghi5JM/Td7VGTmFNrg8cX+kCtXfwP+Phc6aUg==
X-Received: by 10.99.8.194 with SMTP id 185mr41956145pgi.76.1487195535826; Wed, 15 Feb 2017 13:52:15 -0800 (PST)
Received: from [192.168.178.21] ([118.148.112.221]) by smtp.gmail.com with ESMTPSA id h68sm9195588pfj.124.2017.02.15.13.52.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 13:52:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: otroan@employees.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <9bd5456f-d9e2-bedf-abe2-7ab14bdc44e7@gmail.com>
Date: Thu, 16 Feb 2017 10:52:16 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nTZ6bSvHaatfgE7O4f0tz0xeAz8>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 21:52:26 -0000

On 16/02/2017 10:34, otroan@employees.org wrote:
> Brian,
> 
>>>>>> Brian, changing the 64 bit boundary is such a big change that I would
>>>>>> claim it is far outside the scope of advancing 4291 to Internet standard.
>>>>>>
>>>>>
>>>>> Agreed.
>>>>
>>>> Of course. The point is only that it's a parameter in the design of SLAAC,
>>>> whose value is set by the address architecture.
>>>
>>> If your statement is that we only have the 64 bit boundary because of SLAAC I believe you are wrong.
>>> Can you provide any support for that view?
>>
>> No, that's not what I'm saying. I'm saying that SLAAC - by design - would work
>> with any reasonable IID length, but we've chosen to fix it at 64.
>>
>>> If I understand you correctly, your proposal is to change the fixed 64 bit Interface-ID length in IPv6 to a variable one, with an exception for links where SLAAC is used.
>>
>> No. At least not in the foreseeable future. But we should allow for the fact that if
>> prefixes between /64 and /127 are used, routing needs to just work. That's all.
>>
>>> How do you practically suggest to do this, given the issues raised in https://tools.ietf.org/html/rfc7421#section-4.1 ?
>>
>> I'm not suggesting any change to normal subnets, where all those issues apply.
>> I can't see how /64 can be changed for them, without changing a great many
>> things.
>>
>>> Do you think this change is appropriate in the context of advancing 4291?
>>
>> I don't think I have suggested text that would lead to a single instruction in
>> running code being changed.
> 
> CURRENT (RFC4291bis):
> 
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
>    all unicast addresses, except those that start with the binary value
>    000, is required to be 64 bits long.  The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
> 
> PROPOSED:
> 
>     IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of unicast
>    addresses used for Stateless Address Autoconfiguration [RFC4862] is required
>    to be 64 bits long. The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
> 
> 
> My reading of the proposed text, which certainly may be wrong, given that English is not my first language, is that it leaves the Interface-ID length of links _not_ using SLAAC undefined, i.e. not fixed at 64. Is there any other way to interpret this sentence?
> 
> The proposed text appears to make the Interface-ID length an operational choice.

Ah, yes, there is a slight loophole there (but I think that somewhere else we
require all nodes to implement SLAAC, so maybe there isn't a real loophole.)
I would certainly agree to wording that closes that loophole. But the anomalies
people noted around the '000' subset need to fixed.

    Brian

> How is that _not_ changing the 64 bit boundary?
> 
> Best regards,
> Ole
> 


From nobody Wed Feb 15 15:01:16 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 273541293DA; Wed, 15 Feb 2017 15:01:10 -0800 (PST)
X-Quarantine-ID: <7Lf0T39jQkal>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7Lf0T39jQkal; Wed, 15 Feb 2017 15:01:08 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFA0129721; Wed, 15 Feb 2017 15:01:08 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 15 Feb 2017 14:52:59 -0800
Mime-Version: 1.0
Message-Id: <p06240606d4ca8c757453@[99.111.97.136]>
In-Reply-To: <e1ce6bbaaf624c1e88d31c72440093ba@EX13D08UWB002.ant.amazon.com>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <44474907d69a42a0adb66cdc4933603a@EX13D08UWB002.ant.amazon.com> <ba7f397b-59ae-c549-cd1a-e22e1b73b3c1@omnitor.se> <e1ce6bbaaf624c1e88d31c72440093ba@EX13D08UWB002.ant.amazon.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 15 Feb 2017 15:01:05 -0800
To: "Phillips, Addison" <addison@lab126.com>, Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, "Randy  Presuhn" <randy_presuhn@alumni.stanford.edu>, "ietf@ietf.org" <ietf@ietf.org>, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cD7c3zeBzvU8JYKHlP0q14yC0GI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 23:01:10 -0000

Hi Addison,

Please see in-line.

At 5:12 PM +0000 2/15/17, Addison Phillips wrote:

>  Gunnar replied:
>>
>>  Den 2017-02-14 kl. 21:39, skrev Phillips, Addison:
>>  > I have some allergy to the SHALL language: there is no way to 
>> automatically
>>  determine conformance. Many language tags represent nonsensical values, due
>>  to the nature of language tag composition. Content providers need 
>> to use care
>>  in selecting the tags that they use and this section is merely 
>> pointing out good
>>  guidance for tag selection, albeit in a heavy-handed way. BCP47 RFC 5646
>>  Section 4.1 [1] already provides most of this guidance and a 
>> reference to that
>>  source might be useful here, if only because that document requires it:
>>  >
>>  > <quote>
>>  >     Standards, protocols, and applications that reference this document
>>  >     normatively but apply different rules to the ones given in this
>>  >     section MUST specify how language tag selection varies from the
>>  >     guidelines given here.
>>  > </quote>
>>  >
>>  > I would suggest reducing the SHALL items to SHOULD.
>>  Accepted.
>>  That also opens up for another use we have discussed before but been advised
>>  to not use. That is to indicate use of written language by 
>> attaching a script
>>  subtag even if the script subtag we use is suppressed by BCP 47. 
>> We can dro that
>>  need however, with the use of the Zxxx script subtag for 
>> non-written, and clearly
>>  include that usage in our specification as required from BCP 47.
>
>  I don't necessarily think that mandating a script subtag as a 
> signal of written content (vs. spoken content) is that useful. In 
> most protocols, the written nature of the content is indicated by 
> the presence of text. Trying to coerce the language modality via 
> language tags seems complicated, especially since most language 
> tags are harvested from the original source. Introducing processes 
> to evaluate and insert or remove script subtags seems unnecessary 
> to me. That said, I have no objection to content using script 
> subtags if they are useful.
>
>>  >
>>  > I'm not sure what #2 really means. Shouldn't text captions be 
>> indicated by the
>>  written language rather than the spoken language? And I'm not sure what
>>  "spoken/written language" means.
>>  #2 was: "
>>
>>  2.    Text captions included in the video stream SHALL be indicated
>>  by a Language-Tag for spoken/written language."
>>
>>  Yes, the intention is to use written language in the video stream. There are
>>  technologies for that.
>
>  I'm aware of that. My concern is that in this case "spoken/written" 
> is applied to "text captions", which are not spoken be definition? 
> This section is talking about the differences between identifying 
> spoken and written language. The text captions fall into the 
> written side of the equation, no?

Keep in mind that the focus of the draft is enabling language 
negotiation along with media negotiation for interactive 
communications.  In this context, as I noted in previous replies, 
real-time text captions for sign language in video is a service.  A 
mechanism for requesting services needs to be carefully thought out 
in the WG and not added to the current draft at the last minute.

>
>  I'd probably prefer to see something like "2. Text captions 
> included in the video stream SHOULD include a Language-Tag to 
> identify the language."
>
>>  Since the language subtags in the IANA registry are combined for spoken
>>  languages and written languages, I call them Language-Tags for 
>> spoken/written
>>  language.
>
>  The language subtags are for languages--all modalities. My comment 
> here is that "spoken/written" adds no information.
>
>>  It would be misleading to say that we use a Language-Tag for a written
>>  language, because the same tag could in another context mean a spoken
>   > language.
>
>  One uses a Language-Tag for indicating the language. When the text 
> is written, sometimes the user will pick a different language tag 
> (zh-Hant-HK) than they might choose for spoken text (yue-HK, 
> zh-cmn-HK, etc.). Sometimes (actually, nearly all the time except 
> for special cases) the language tag for the spoken and written 
> language is the same tag (en-US, de-CH, ja-JP, etc.). Again, the 
> modality of the language is a separate consideration from the 
> language. Nearly always, it is better to use the same tag for both 
> spoken and written content rather than trying to use the tag to 
> distinguish between them: different Content-Types require different 
> decoders anyway, but it is really useful to say "give me all of the 
> 'en-US' content you have" or "do you have content for a user who 
> speaks 'es'"

Requesting all content available in a specific language is outside 
the scope of the draft, which is enabling language negotiation along 
with media negotiation for interactive communications.  One key 
example is a user placing an emergency call.  The call setup can 
negotiate both language and media for interactive communication 
between the emergency services answering point and the user.

>
>>  Since we have the script subtag Zxxx for non-written, we do not need to
>>  construct an explicit tag for the written language tag, it should 
>> be sufficient with
>>  our specification of the use in our case.
>
>  In case it isn't clear aboe, I oppose introducing the 'Zxxx' subtag 
> save for cases where the non-written nature of the content is 
> super-important to the identification of the language.
>>
>>  In my latest recent proposal, I still have a very similar wording. 
>> Since you had
>>  problems understanding it, there might still be a need to tune it. Can you
>>  propose wording?
>>  This is the current proposal:
>>
>>  "   2.    Text captions included in the video stream SHOULD be indicated
>>     by a humintlang attribute with Language-Tag for spoken/written language.
>>  "
>
>  I did that above. I think it is useful not to over-think it. When I 
> see "Content-Type: video/mpeg; Content-Language: en-GB", I rather 
> expect audio content in English and not written content (although 
> the video stream might also includes pictures of English text such 
> as the titles in a movie). When, as in this case, setting up a 
> negotiated language experience, interoperability is most aided by 
> matching the customer's language preferences to available 
> resources. This is easiest when customers do not get carried away 
> with complex language tags (ranges in BCP 47 parlance, e.g. 
> tlh-Cyrl-AQ-fonupa) and systems do not have to introspect the 
> language tags, inserting and removing script subtags to match the 
> various language modes.
>
>  Addison
>
>  _______________________________________________
>  SLIM mailing list
>  SLIM@ietf.org
>  https://www.ietf.org/mailman/listinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The First Amendment is often inconvenient. But that is besides the
point.  Inconvenience does not absolve the government of its
obligation to tolerate speech. --Justice Anthony Kennedy, in 91-155


From nobody Wed Feb 15 15:53:14 2017
Return-Path: <bernard.aboba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E99E129BF0; Wed, 15 Feb 2017 15:53:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xLOyFDa6h5aL; Wed, 15 Feb 2017 15:53:04 -0800 (PST)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::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 2611312995C; Wed, 15 Feb 2017 15:53:04 -0800 (PST)
Received: by mail-ua0-x22e.google.com with SMTP id 96so1162200uaq.3; Wed, 15 Feb 2017 15:53:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=aJir4W3O2MZUUnTTSLP66bMdSiGfXn9b7A2Da+LBahg=; b=GCcO4vZZk09fIx6xo0ky+N7euwklMgRlrQ3P2TChCfRmg9oiFooe6OPGH6w6Ddd8+o M3AORq56476ua/w8wwX/FL16a5CBrFOw0/ezAkxoPRjCRLf+qteCg7hVG5xkrCou38GC RruO1iTwVF3qc7i6ZW8SOamNnD8OVVPqYtHWBMFbMOPYZhF0OjMVcIQV895zNzQBBTqn BuSzBfWFPSxx5sQdNZdjb58DxeXakggds5Z41mPFWEzHD1+exgRYJ1HWczR9gTML4Dh5 D3z8NDy3DKHJV/MWhODfXY0/h21iCHFhWL5SORoTHYEnUUv80oiyXxlw4tQ9VphydDyH szbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=aJir4W3O2MZUUnTTSLP66bMdSiGfXn9b7A2Da+LBahg=; b=lTUpc65DgAaeLA3pBaCAcYRWDvguSiuWp3QFbOiBFs2Yv9A/XZd/ZZBVESYGBFhCk2 sQJiah2XrIau3sCO03TwL701vv3Ghdged7f0z223jlmKxQ3jLUjvMkkvsyu3M0H5x5yX RKHZqu/PVeT/wvNC4eIUKHzwmxTr5eq7W1w+ax6u8W2pihJdRsw/Ec9yl1MyTu2ocLaY OW8EBARJZi9XrxO1FFw7K9v65JlOSrLCTTFINoYOmZDMuhm3QFh1kWSAAttG3hl4EPlb Ro0/Iy/9cpg7ioQF3ZazNgHdQ5gJdN3k4iT1GEiG3q7IXGntSC/AaypiDk0lxe89E6ST H5aw==
X-Gm-Message-State: AMke39lgFxqrzbEaaAVJB7x/hBgpxa8hT8ux5TU0De+8UPOR5lMhiNuwlCaqQQInkHiaiBHIkLZX4/Ckqf8r3g==
X-Received: by 10.176.2.67 with SMTP id 61mr2250549uas.108.1487202783104; Wed, 15 Feb 2017 15:53:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.176.88.90 with HTTP; Wed, 15 Feb 2017 15:52:42 -0800 (PST)
In-Reply-To: <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
References: <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@99.111.97.136> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@99.111.97.136> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@99.111.97.136> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Wed, 15 Feb 2017 15:52:42 -0800
Message-ID: <CAOW+2dsQuWnF8r_1LMsKFf9WLa=r5vN=oZfQHZdLz2c9E8xkgQ@mail.gmail.com>
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Section 5.4)
To: =?UTF-8?Q?Gunnar_Hellstr=C3=B6m?= <gunnar.hellstrom@omnitor.se>
Content-Type: multipart/alternative; boundary=001a113dcd7a989c4b05489a6191
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZQ24F_SCKuO15L8zBU-uBoUJd5s>
Cc: "slim@ietf.org" <slim@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2017 23:53:07 -0000

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

Gunnar Hellstrom said:

"The SDP Lang attribute in RFC 4566, where you (Randall) say it is intended
for specifying a set of languages that all must be used in a session, while
I say that it is intended for negotiation of at least one initial language.=
"

[BA] At IETF 96 in Berlin, we had a discussion of the history of the SDP
Lang attribute within the MMUSIC WG.

The Lang attribute was originally specified in RFC 2327, which was
published in April 1998, more than four years prior to the publication of
Offer/Answer RFC 3264 (June 2002), and three years prior to publication of
the initial draft-rosenberg-mmusic-sdp-offer-answer-00 (April 26, 2001).

As a result, the Lang attribute could not have been designed for use in
Offer/Answer negotiation, but instead was intended for use in the
declarative SDP of multicast conferencing.  Note that the Lang attribute
was not mentioned in RFC 3264, and noone at the MMUSIC WG session was aware
of a subsequent SIP Offer/Answer implementation of it.









On Wed, Feb 15, 2017 at 1:41 AM, Gunnar Hellstr=C3=B6m <
gunnar.hellstrom@omnitor.se> wrote:

> Den 2017-02-15 kl. 01:39, skrev Randall Gellens:
>
>> At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:
>>
>>  Hi -
>>>
>>>  On 2/14/2017 2:43 PM, Randall Gellens wrote:
>>>
>>>>  At 8:59 PM +0100 2/14/17, Gunnar Hellstr=C3=B6m wrote:
>>>>
>>>>   Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>>>>>
>>>>>   Hi -
>>>>>>
>>>>>>   On 2/14/2017 9:40 AM, Randall Gellens wrote:
>>>>>>
>>>>>>>   At 11:01 AM +0100 2/14/17, Gunnar Hellstr=C3=B6m wrote:
>>>>>>>
>>>>>>>    My proposal for a reworded section 5.4 is:
>>>>>>>>
>>>>>>>>    5.4.  Unusual language indications
>>>>>>>>
>>>>>>>>    It is possible to specify an unusual indication where the
>>>>>>>> language
>>>>>>>>    specified may look unexpected for the media type.
>>>>>>>>
>>>>>>>>    For such cases the following guidance SHALL be applied for the
>>>>>>>>   humintlang attributes used in these situations.
>>>>>>>>
>>>>>>>>    1.    A view of a speaking person in the video stream SHALL,
>>>>>>>> when it
>>>>>>>>   has relevance for speech perception, be indicated by a
>>>>>>>> Language-Tag
>>>>>>>>   for spoken/written language with the "Zxxx" script subtag to
>>>>>>>> indicate
>>>>>>>>   that the contents is not written.
>>>>>>>>
>>>>>>>>    2.    Text captions included in the video stream SHALL be
>>>>>>>> indicated
>>>>>>>>   by a Language-Tag for spoken/written language.
>>>>>>>>
>>>>>>>>    3.    Any approximate representation of sign language or
>>>>>>>>   fingerspelling in the text media stream SHALL be indicated by a
>>>>>>>>   Language-Tag for a sign language in text media.
>>>>>>>>
>>>>>>>>    4.    When sign language related audio from a person using sign
>>>>>>>>   language is of importance for language communication, this SHALL
>>>>>>>> be
>>>>>>>>   indicated by a Language-Tag for a sign language in audio media.
>>>>>>>>
>>>>>>>
>>>>>>>   [RG] As I said, I think we should avoid specifying this until we
>>>>>>> have
>>>>>>>   deployment experience.
>>>>>>>
>>>>>>   ...
>>>>>>
>>>>>>   From a process perspective, it's far easier to remove constraints
>>>>>>   as a specification advances than it is to add them.
>>>>>>
>>>>>   I agree. It is often better to specify normatively as far as you ca=
n
>>>>>  imagine, so that interoperability and good functionality is achieved=
.
>>>>>  Stopping halfway and have MAY in the specifications creates
>>>>>  uncertainty and less useful specifications.
>>>>>
>>>>
>>>>  My reading of what Randy says is the opposite of Gunnar's. In my
>>>>  reading, Randy points out that is it easier to remove the SHOULD NOT =
in
>>>>  the future then it is to change the meaning of the combinations or
>>>>  switch to a different mechanism.
>>>>
>>>>  In my experience, it's better to specify only what we know we need an=
d
>>>>  what we know we understand.  Speculative specifications "as far as yo=
u
>>>>  can imagine" more often lead to interoperability problems, unnecessar=
y
>>>>  complexity, limitations on what's needed in the future, and divergent
>>>>  implementations.
>>>>
>>>
>>>  I think the difference in your positions comes down to
>>>
>>>    (1) your respective notions of "what we know we need and what we
>>>        know we understand";
>>>
>>>    (2) whether you believe that the interoperability and conformance
>>>        consequences of removing a "SHOULD NOT" could be the same
>>>        as those merely retaining a "MUST" or "SHALL" - this determines
>>>        whether Randy G.'s proposal provides a path for some future
>>>        revision to mandate (if deployment experience substantiates the
>>>        need/understanding) the behavior proposed by Gunnar. That path
>>>        is not at all obvious to me.
>>>
>>
>> The purpose of the draft is to enable the two endpoints of a real-time
>> communication session to agree which languages and media to use for
>> interactive communication.  We have a mechanism of adding language tags =
to
>> media stream negotiations.  In most cases, the language and media modali=
ty
>> are an obvious fit.  There are combinations of media and language where =
the
>> meaning is not so obvious, specifically, signed language tags with a aud=
io
>> or text, and non-signed language tags with video.  My proposal is that w=
e
>> say offerer SHOULD NOT send such combinations and answerer MAY ignore
>> language. This allows future specifications for the underlying uses Gunn=
ar
>> wants (such as real-time subtitles in video and signed equivalents in
>> text).  Such future specifications could define a use for the language a=
nd
>> media combinations and remove the SHOULD NOT send and MAY ignore, or cou=
ld
>> define a new mechanism.  I don't think we know enough now to dictate wha=
t
>> the solution should be.
>>
> We have a fresh example from our own discussions in the SLIM group how
> unfortunate it is to not be sufficiently explicit in the first edition of=
 a
> standard. The SDP Lang attribute in RFC 4566, where you (Randall) say it =
is
> intended for specifying a set of languages that all must be used in a
> session, while I say that it is intended for negotiation of at least one
> initial language. By having that uncertainty in a specification that has
> been published makes it very hard to sharpen up the specification
> afterwards because it would possibly make some implementations non
> conformant. And it makes potential implementors hesitant to use the curre=
nt
> specifications, as it was with the SLIM work.
>
> For 5.4.
>
> I am OK with modifying from my latest proposal, but we need to be specifi=
c.
> I am also OK with reducing the SHALLs to SHOULDs as Addison requested.
>
> The situation is not that we lack knowledge. Here is what we know about
> the 4 cases of "unusual" indications:
>
> 1. View of the speaker in video. Very important for speech perception.
> Quality requirements are documented in ITU-T H-series Supplement 1. Of re=
al
> use only as a complement to the same spoken language in audio. Now, when =
we
> know about the Zxxx notation for non-written, we also have a good way of
> specifying it precisely.
> This case was also described in section 5.2 already.
>
> 2. Text captions in the video stream.
> This can be either text merged into video and communicated as true part o=
f
> the video image, or it can be a text component of a multimedia system, as
> MPEG-4, declared in SDP as m=3Dvideo.
> It has been used in some videophone products, but I have not seen it used
> lately.
> It is a clearly defined case, and we can specify coding for it, but we do
> not at the moment know if it will be important to specify it.
>
> 3. Sign language or fingerspelling in the text stream.
> I have seen a product using it for claimed sign language conversation. It
> is also in use in the simple text form with words in capitals approximate=
ly
> representing signs between persons involved in preparation of sign langua=
ge
> productions and translations. But in that case it is in a session where
> they agree in other ways to start using the text stream for that purpose.
> So I think we can say that this is rare, and its use can be agreed by oth=
er
> means between the users. Still it is a clearly defined case.
>
> 4. Audio from signing person related to sign language. This is more vague
> than the others.  It may be a person signing in video and adding spoken
> words in audio to signing, but influenced by the word order and grammar o=
f
> sign language with some ambition to make it reasonably understandable for
> both deaf and hearing participants. There are even some spoken words
> created from sign language that are commonly used by hearing persons in
> such situations. But for that case I anyway think it is better to define
> the audio part as the spoken language it is derived from, because of its
> intention to be understandable for hearing persons. All other variants I
> can imagine are even closer to the spoken language and should be specifie=
d
> with spoken language tag. If we only want to have the audio stream
> established to hear the background in the signing situation, then we shou=
ld
> not specify language use of the audio stream.
> Even if we know what sign language tag in audio stream would be, it may b=
e
> just as good to leave it undefined.
> ------------------------------------------------------------
> ------------------------------------------------------------
> ------------------------
> So, new proposal:
>
> 5.4.  Unusual language indications
>
>    It is possible to specify an unusual indication where the language
>    specified may look unexpected for the media type.
>
>    For such cases the following guidance SHOULD be applied for the
>   humintlang attributes used in these situations.
>
>    1.    A view of a speaking person in the video stream SHOULD, when it
>   has relevance for speech perception, be indicated by a humintlang
> attribute with a Language-Tag
>   for a spoken/written language with the "Zxxx" script subtag to indicate
>   that the contents is not written.
>
>    2.    Text captions included in the video stream SHOULD be indicated
>   by a humintlang attribute with Language-Tag for spoken/written language=
.
>
>    3.    A Language-Tag for a sign language specified in a humintlang
> attribute for a text stream MAY be interpreted as use of an approximate
> representation of sign language or fingerspelling in the text media strea=
m.
> The use of such representation is rare and usually conveniently agreed by
> other means between the users during an established session. Common suppo=
rt
> of this indication SHOULD NOT be assumed or required.
>
>    4.    A Language-Tag for a sign language specified in a humintlang
> attribute for an audio stream SHOULD NOT be indicated and MAY be ignored =
on
> reception. Any use of spoken words or spoken language in the audio stream
> SHOULD, when it can be of importance for language communication, be
> indicated by the corresponding Language-Tag for spoken language in a
> humintlang attribute for the audio stream.
>
>
>
>
> Gunnar
>
>
> --
> -----------------------------------------
> Gunnar Hellstr=C3=B6m
> Omnitor
> gunnar.hellstrom@omnitor.se
> +46 708 204 288
>
> _______________________________________________
> SLIM mailing list
> SLIM@ietf.org
> https://www.ietf.org/mailman/listinfo/slim
>

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

<div dir=3D"ltr">Gunnar Hellstrom said:=C2=A0<div><br></div><div>&quot;<spa=
n style=3D"font-size:12.8px">The SDP Lang attribute in RFC 4566, where you =
(Randall) say it is intended for specifying a set of languages that all mus=
t be used in a session, while I say that it is intended for negotiation of =
at least one initial language.&quot;</span></div><div><span style=3D"font-s=
ize:12.8px"><br></span></div><div><span style=3D"font-size:12.8px">[BA] At =
IETF 96 in Berlin, we had a discussion of the history of the SDP Lang attri=
bute within the MMUSIC WG.=C2=A0</span></div><div><span style=3D"font-size:=
12.8px"><br></span></div><div><span style=3D"font-size:12.8px">The Lang att=
ribute was originally specified in RFC 2327, which was published in April 1=
998, more than four years prior to the publication of Offer/Answer RFC 3264=
 (June 2002), and three years prior to publication of the initial draft-ros=
enberg-mmusic-sdp-offer-answer-00 (April 26, 2001).=C2=A0</span></div><div>=
<br></div><div>As a result, the Lang attribute could not have been designed=
 for use in Offer/Answer negotiation, but instead was intended for use in t=
he declarative SDP of multicast conferencing.=C2=A0 Note that the Lang attr=
ibute was not mentioned in RFC 3264, and noone at the MMUSIC WG session was=
 aware of a subsequent SIP Offer/Answer implementation of it.</div><div><br=
></div><div><br></div><div><br></div><div><br></div><div><span style=3D"fon=
t-size:12.8px"><br></span></div><div><span style=3D"font-size:12.8px"><br><=
/span></div><div><span style=3D"font-size:12.8px"><br></span></div><div><sp=
an style=3D"font-size:12.8px"><br></span></div></div><div class=3D"gmail_ex=
tra"><br><div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 1:41 AM, Gunnar=
 Hellstr=C3=B6m <span dir=3D"ltr">&lt;<a href=3D"mailto:gunnar.hellstrom@om=
nitor.se" target=3D"_blank">gunnar.hellstrom@omnitor.se</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5=
">Den 2017-02-15 kl. 01:39, skrev Randall Gellens:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0Hi -<br>
<br>
=C2=A0On 2/14/2017 2:43 PM, Randall Gellens wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0At 8:59 PM +0100 2/14/17, Gunnar Hellstr=C3=B6m wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 Hi -<br>
<br>
=C2=A0 On 2/14/2017 9:40 AM, Randall Gellens wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 At 11:01 AM +0100 2/14/17, Gunnar Hellstr=C3=B6m wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0My proposal for a reworded section 5.4 is:<br>
<br>
=C2=A0 =C2=A05.4.=C2=A0 Unusual language indications<br>
<br>
=C2=A0 =C2=A0It is possible to specify an unusual indication where the lang=
uage<br>
=C2=A0 =C2=A0specified may look unexpected for the media type.<br>
<br>
=C2=A0 =C2=A0For such cases the following guidance SHALL be applied for the=
<br>
=C2=A0 humintlang attributes used in these situations.<br>
<br>
=C2=A0 =C2=A01.=C2=A0 =C2=A0 A view of a speaking person in the video strea=
m SHALL, when it<br>
=C2=A0 has relevance for speech perception, be indicated by a Language-Tag<=
br>
=C2=A0 for spoken/written language with the &quot;Zxxx&quot; script subtag =
to indicate<br>
=C2=A0 that the contents is not written.<br>
<br>
=C2=A0 =C2=A02.=C2=A0 =C2=A0 Text captions included in the video stream SHA=
LL be indicated<br>
=C2=A0 by a Language-Tag for spoken/written language.<br>
<br>
=C2=A0 =C2=A03.=C2=A0 =C2=A0 Any approximate representation of sign languag=
e or<br>
=C2=A0 fingerspelling in the text media stream SHALL be indicated by a<br>
=C2=A0 Language-Tag for a sign language in text media.<br>
<br>
=C2=A0 =C2=A04.=C2=A0 =C2=A0 When sign language related audio from a person=
 using sign<br>
=C2=A0 language is of importance for language communication, this SHALL be<=
br>
=C2=A0 indicated by a Language-Tag for a sign language in audio media.<br>
</blockquote>
<br>
=C2=A0 [RG] As I said, I think we should avoid specifying this until we hav=
e<br>
=C2=A0 deployment experience.<br>
</blockquote>
=C2=A0 ...<br>
<br>
=C2=A0 From a process perspective, it&#39;s far easier to remove constraint=
s<br>
=C2=A0 as a specification advances than it is to add them.<br>
</blockquote>
=C2=A0 I agree. It is often better to specify normatively as far as you can=
<br>
=C2=A0imagine, so that interoperability and good functionality is achieved.=
<br>
=C2=A0Stopping halfway and have MAY in the specifications creates<br>
=C2=A0uncertainty and less useful specifications.<br>
</blockquote>
<br>
=C2=A0My reading of what Randy says is the opposite of Gunnar&#39;s. In my<=
br>
=C2=A0reading, Randy points out that is it easier to remove the SHOULD NOT =
in<br>
=C2=A0the future then it is to change the meaning of the combinations or<br=
>
=C2=A0switch to a different mechanism.<br>
<br>
=C2=A0In my experience, it&#39;s better to specify only what we know we nee=
d and<br>
=C2=A0what we know we understand.=C2=A0 Speculative specifications &quot;as=
 far as you<br>
=C2=A0can imagine&quot; more often lead to interoperability problems, unnec=
essary<br>
=C2=A0complexity, limitations on what&#39;s needed in the future, and diver=
gent<br>
=C2=A0implementations.<br>
</blockquote>
<br>
=C2=A0I think the difference in your positions comes down to<br>
<br>
=C2=A0 =C2=A0(1) your respective notions of &quot;what we know we need and =
what we<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0know we understand&quot;;<br>
<br>
=C2=A0 =C2=A0(2) whether you believe that the interoperability and conforma=
nce<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0consequences of removing a &quot;SHOULD NOT&quot=
; could be the same<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0as those merely retaining a &quot;MUST&quot; or =
&quot;SHALL&quot; - this determines<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0whether Randy G.&#39;s proposal provides a path =
for some future<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0revision to mandate (if deployment experience su=
bstantiates the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0need/understanding) the behavior proposed by Gun=
nar. That path<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0is not at all obvious to me.<br>
</blockquote>
<br>
The purpose of the draft is to enable the two endpoints of a real-time comm=
unication session to agree which languages and media to use for interactive=
 communication.=C2=A0 We have a mechanism of adding language tags to media =
stream negotiations.=C2=A0 In most cases, the language and media modality a=
re an obvious fit.=C2=A0 There are combinations of media and language where=
 the meaning is not so obvious, specifically, signed language tags with a a=
udio or text, and non-signed language tags with video.=C2=A0 My proposal is=
 that we say offerer SHOULD NOT send such combinations and answerer MAY ign=
ore language. This allows future specifications for the underlying uses Gun=
nar wants (such as real-time subtitles in video and signed equivalents in t=
ext).=C2=A0 Such future specifications could define a use for the language =
and media combinations and remove the SHOULD NOT send and MAY ignore, or co=
uld define a new mechanism.=C2=A0 I don&#39;t think we know enough now to d=
ictate what the solution should be.<br>
</blockquote></div></div>
We have a fresh example from our own discussions in the SLIM group how unfo=
rtunate it is to not be sufficiently explicit in the first edition of a sta=
ndard. The SDP Lang attribute in RFC 4566, where you (Randall) say it is in=
tended for specifying a set of languages that all must be used in a session=
, while I say that it is intended for negotiation of at least one initial l=
anguage. By having that uncertainty in a specification that has been publis=
hed makes it very hard to sharpen up the specification afterwards because i=
t would possibly make some implementations non conformant. And it makes pot=
ential implementors hesitant to use the current specifications, as it was w=
ith the SLIM work.<br>
<br>
For 5.4.<br>
<br>
I am OK with modifying from my latest proposal, but we need to be specific.=
<br>
I am also OK with reducing the SHALLs to SHOULDs as Addison requested.<br>
<br>
The situation is not that we lack knowledge. Here is what we know about the=
 4 cases of &quot;unusual&quot; indications:<br>
<br>
1. View of the speaker in video. Very important for speech perception. Qual=
ity requirements are documented in ITU-T H-series Supplement 1. Of real use=
 only as a complement to the same spoken language in audio. Now, when we kn=
ow about the Zxxx notation for non-written, we also have a good way of spec=
ifying it precisely.<br>
This case was also described in section 5.2 already.<br>
<br>
2. Text captions in the video stream.<br>
This can be either text merged into video and communicated as true part of =
the video image, or it can be a text component of a multimedia system, as M=
PEG-4, declared in SDP as m=3Dvideo.<br>
It has been used in some videophone products, but I have not seen it used l=
ately.<br>
It is a clearly defined case, and we can specify coding for it, but we do n=
ot at the moment know if it will be important to specify it.<br>
<br>
3. Sign language or fingerspelling in the text stream.<br>
I have seen a product using it for claimed sign language conversation. It i=
s also in use in the simple text form with words in capitals approximately =
representing signs between persons involved in preparation of sign language=
 productions and translations. But in that case it is in a session where th=
ey agree in other ways to start using the text stream for that purpose. So =
I think we can say that this is rare, and its use can be agreed by other me=
ans between the users. Still it is a clearly defined case.<br>
<br>
4. Audio from signing person related to sign language. This is more vague t=
han the others.=C2=A0 It may be a person signing in video and adding spoken=
 words in audio to signing, but influenced by the word order and grammar of=
 sign language with some ambition to make it reasonably understandable for =
both deaf and hearing participants. There are even some spoken words create=
d from sign language that are commonly used by hearing persons in such situ=
ations. But for that case I anyway think it is better to define the audio p=
art as the spoken language it is derived from, because of its intention to =
be understandable for hearing persons. All other variants I can imagine are=
 even closer to the spoken language and should be specified with spoken lan=
guage tag. If we only want to have the audio stream established to hear the=
 background in the signing situation, then we should not specify language u=
se of the audio stream.<br>
Even if we know what sign language tag in audio stream would be, it may be =
just as good to leave it undefined.<br>
------------------------------<wbr>------------------------------<wbr>-----=
-------------------------<wbr>------------------------------<wbr>----------=
--------------<br>
So, new proposal:<span class=3D""><br>
<br>
5.4.=C2=A0 Unusual language indications<br>
<br>
=C2=A0 =C2=A0It is possible to specify an unusual indication where the lang=
uage<br>
=C2=A0 =C2=A0specified may look unexpected for the media type.<br>
<br></span>
=C2=A0 =C2=A0For such cases the following guidance SHOULD be applied for th=
e<span class=3D""><br>
=C2=A0 humintlang attributes used in these situations.<br>
<br></span>
=C2=A0 =C2=A01.=C2=A0 =C2=A0 A view of a speaking person in the video strea=
m SHOULD, when it<br>
=C2=A0 has relevance for speech perception, be indicated by a humintlang at=
tribute with a Language-Tag<br>
=C2=A0 for a spoken/written language with the &quot;Zxxx&quot; script subta=
g to indicate<span class=3D""><br>
=C2=A0 that the contents is not written.<br>
<br></span>
=C2=A0 =C2=A02.=C2=A0 =C2=A0 Text captions included in the video stream SHO=
ULD be indicated<br>
=C2=A0 by a humintlang attribute with Language-Tag for spoken/written langu=
age.<br>
<br>
=C2=A0 =C2=A03.=C2=A0 =C2=A0 A Language-Tag for a sign language specified i=
n a humintlang attribute for a text stream MAY be interpreted as use of an =
approximate representation of sign language or fingerspelling in the text m=
edia stream. The use of such representation is rare and usually convenientl=
y agreed by other means between the users during an established session. Co=
mmon support of this indication SHOULD NOT be assumed or required.<br>
<br>
=C2=A0 =C2=A04.=C2=A0 =C2=A0 A Language-Tag for a sign language specified i=
n a humintlang attribute for an audio stream SHOULD NOT be indicated and MA=
Y be ignored on reception. Any use of spoken words or spoken language in th=
e audio stream SHOULD, when it can be of importance for language communicat=
ion, be indicated by the corresponding Language-Tag for spoken language in =
a humintlang attribute for the audio stream.<span class=3D"HOEnZb"><font co=
lor=3D"#888888"><br>
<br>
<br>
<br>
<br>
Gunnar</font></span><span class=3D"im HOEnZb"><br>
<br>
<br>
-- <br>
------------------------------<wbr>-----------<br>
Gunnar Hellstr=C3=B6m<br>
Omnitor<br>
<a href=3D"mailto:gunnar.hellstrom@omnitor.se" target=3D"_blank">gunnar.hel=
lstrom@omnitor.se</a><br>
<a href=3D"tel:%2B46%20708%20204%20288" value=3D"+46708204288" target=3D"_b=
lank">+46 708 204 288</a><br>
<br></span><div class=3D"HOEnZb"><div class=3D"h5">
______________________________<wbr>_________________<br>
SLIM mailing list<br>
<a href=3D"mailto:SLIM@ietf.org" target=3D"_blank">SLIM@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/slim" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinfo/slim</a><br>
</div></div></blockquote></div><br></div>

--001a113dcd7a989c4b05489a6191--


From nobody Wed Feb 15 16:12:24 2017
Return-Path: <charles.perkins@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4AB1129C05; Wed, 15 Feb 2017 16:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.22
X-Spam-Level: 
X-Spam-Status: No, score=-2.22 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=charles.perkins@earthlink.net header.d=earthlink.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w_-DOq02oh9L; Wed, 15 Feb 2017 16:12:18 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D608129C04; Wed, 15 Feb 2017 16:12:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1487203937; bh=6xZt+yDlj3PAWRldWyCmsApEBdF76ryJU6LB bVM8DgI=; h=Received:Subject:To:References:Cc:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:Content-Type: Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP; b=hGb9JT+ gO6JsaPeYAo4M4Bu6R+8pwHfrvv5ZI4kdyTtC39VdXjWkWXwBrKholQfMNU6/sB0d5C xryWG8YwCCq9xLJu5GYQq0G0hbztxKosUUFYNESlZjXAzSyq9z+Cj7bDe2IW8YZiF56 K0De4fWpVKtcOoEE3l+qMzayfNMAXHQdGQSY42G0+5MpGH6/5ueav/WDqcmAywLlW2D fZ1sU+yJXMxI3N5PpOKVoNHUvpeVWviH/+MpFwvdvI5BvJNVtk2hHwoCKGaz+RIK+U/ SZJzLxF+gGGmR0MtrbklXCUQvv0UsXGp5qoAHzzk+t+HN0q7gTBSHVkCB8ROi9z25FA ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=NJ9LXRtzCBUu2iOnnG64fGcrPtXAAMzstu/6C+np+x1YvRRFM65Uo8K/BXdcuUQgQWOc6fGPLUqZLxha/BB4xeVdTIFjsZg1IXAQDKFTg1HLDax9Co4P+mYaqBNIzXt+LdjYTcoy92sJYj0PyqB8Gt4eZ0tClUmrOGeL8CCLpoGv+j1J1S3iERUqmFmSy+DpMzOTvY9TQIZBh5UjIhpLin5FeUhezJCUHO3MUizyfNVaGn+SH5/kqxCuObCvXe8xgbl8pEete8lmc1lRTNVNvtEqVjbK/lk4mLHhnTj0PTrF04jO/SXPqN+FDMBd2XPJeCb4uDQgB1Y89viFF0Ty2A==; h=Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [99.51.72.196] (helo=[192.168.1.82]) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <charles.perkins@earthlink.net>) id 1ce9gB-0002ZY-MQ; Wed, 15 Feb 2017 19:12:11 -0500
Subject: Re: [DMM] Review of draft-ietf-dmm-4283mnids-04
To: "Dale R. Worley" <worley@ariadne.com>
References: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
From: Charlie Perkins <charles.perkins@earthlink.net>
Message-ID: <f6e2cba3-6de8-af60-2a55-9c908863bb70@earthlink.net>
Date: Wed, 15 Feb 2017 16:12:04 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <87o9y4s1rg.fsf@hobgoblin.ariadne.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 137d7d78656ed6919973fd6a8f21c4f2d780f4a490ca6956527bd5036cbc8ac78030d2dc13a190b468de9a8be97af0f3350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.51.72.196
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hW0aDIQknsTws8r7KK90noAdNS0>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 00:12:19 -0000

Hello Dale,

O.K.  I will take a crack at making this reorganization.  If you have 
text of course that will be appreciated.  Right now I don't see why 
anyone in the WG would object, but I hope at least some people will take 
a look.

I can have the revised draft ready in a few days.  I think this resolves 
the last point of discussion that has been raised about the draft.

Regards,
Charlie P.


On 2/14/2017 5:04 PM, Dale R. Worley wrote:
> Charlie Perkins <charles.perkins@earthlink.net> writes:
>> I am hesitant to replace so many MNID types by a single URN type with
>> substructure.  What would you think about replacing the existing
>> RFID-*-URI types with a single URN type, but leaving the existing binary
>> types?  This gets the benefit you suggest for future extensibility, but
>> retains the shorter forms that may often be advantageous.
> Suddenly today I realized something I should have realized in the
> review, which would have saved us much time in discussion.  Viz.,
> consider this proposal:
>
> - one MNID type for *all* the EPC binary schemes
>
> - one MNID type for *all* URNs, *including* the EPC URI forms
>
> This would work, since (1) (not surprisingly) the EPC binary schemes are
> all differentiated by their first 8 bits.  (see table on page 19 of the
> tag-data standard,
> http://www.gs1.org/gsmp/kc/epcglobal/tds/tds_1_1_rev_1_27-standard-20050510.pdf)
> and (2) all URNs are differentiated by their namespace part.
>
> (This parallels using one MNID number for all DUID types, since DUIDs
> have an internal indicator for the four types.)
>
> This approach has all the desirable properties anyone has mentioned so
> far:
>
> - includes all EPC binary and URI forms
> - automatically includes all existing and future EPC binary forms
> - automatically includes all existing and future URN forms *including*
>    all existing and future EPC URI forms
> - doesn't have a proliferation of MNID type numbers which duplicate
>    information that can be fairly easily extracted from the
>    identifier itself
> - includes all the short EPC forms, allowing brevity when that is
>    desirable
>
> This seems to be practical, simple, and almost as elegant as possible.
> What do you think?
>
>> I changed the text as follows:
>>
>>>      Some MNIDs contain sensitive identifiers which, as used in protocols
>>>      specified by other SDOs, are only used for signaling during initial
>>>      network entry.  In such protocols, subsequent exchanges then rely on
>>>      a temporary identifier allocated during the initial network entry.
>>>      Managing the association between long-lived and temporary identifiers
>>>      is outside the scope of this document.
>> I can't remember exactly why this text was added - it was a long time
>> ago.  But anyway the main point is to simply mention that there may be
>> associations between some of the MNID types that might be important from
>> a security standpoint, without meaning to go into examples.
> Certainly the new text is clear enough.
>
> Dale
>


From nobody Wed Feb 15 16:26:53 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B406E12997C; Wed, 15 Feb 2017 16:26:52 -0800 (PST)
X-Quarantine-ID: <vHVyhV1HPm8Q>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 vHVyhV1HPm8Q; Wed, 15 Feb 2017 16:26:50 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 826101296EE; Wed, 15 Feb 2017 16:26:50 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 15 Feb 2017 16:18:41 -0800
Mime-Version: 1.0
Message-Id: <p0624060ad4caa20f847c@[99.111.97.136]>
In-Reply-To: <CAOW+2dsQuWnF8r_1LMsKFf9WLa=r5vN=oZfQHZdLz2c9E8xkgQ@mail.gmail.com>
References: <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@99.111.97.136> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@99.111.97.136> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@99.111.97.136> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se> <CAOW+2dsQuWnF8r_1LMsKFf9WLa=r5vN=oZfQHZdLz2c9E8xkgQ@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 15 Feb 2017 16:26:45 -0800
To: Bernard Aboba <bernard.aboba@gmail.com>, Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Section 5.4)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VUS6O3l9QpiEmHEAmNsB0NWU7Eo>
Cc: "slim@ietf.org" <slim@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 00:26:53 -0000

At 3:52 PM -0800 2/15/17, Bernard Aboba wrote:

>  Gunnar Hellstrom said:
>
>  "The SDP Lang attribute in RFC 4566, where you=20
> (Randall) say it is intended for specifying a=20
> set of languages that all must be used in a=20
> session, while I say that it is intended for=20
> negotiation of at least one initial language."
>
>  [BA] At IETF 96 in Berlin, we had a discussion=20
> of the history of the SDP Lang attribute within=20
> the MMUSIC WG.
>
>  The Lang attribute was originally specified in=20
> RFC 2327, which was published in April 1998,=20
> more than four years prior to the publication=20
> of Offer/Answer RFC 3264 (June 2002), and three=20
> years prior to publication of the initial=20
> draft-rosenberg-mmusic-sdp-offer-answer-00=20
> (April 26, 2001).
>
>  As a result, the Lang attribute could not have=20
> been designed for use in Offer/Answer=20
> negotiation, but instead was intended for use=20
> in the declarative SDP of multicast=20
> conferencing.  Note that the Lang attribute was=20
> not mentioned in RFC 3264, and noone at the=20
> MMUSIC WG session was aware of a subsequent SIP=20
> Offer/Answer implementation of it.

Which is what I was saying: it is descriptive of=20
the media, which is very different from=20
negotiation.  However, this is all moot now.



>  On Wed, Feb 15, 2017 at 1:41 AM, Gunnar=20
> Hellstr=F6m=20
> <<mailto:gunnar.hellstrom@omnitor.se>gunnar.hellstrom@omnitor.se>=20
> wrote:
>
>  Den 2017-02-15 kl. 01:39, skrev Randall Gellens:
>
>  At 4:21 PM -0800 2/14/17, Randy Presuhn wrote:
>
>   Hi -
>
>   On 2/14/2017 2:43 PM, Randall Gellens wrote:
>
>   At 8:59 PM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>
>    Den 2017-02-14 kl. 19:05, skrev Randy Presuhn:
>
>    Hi -
>
>    On 2/14/2017 9:40 AM, Randall Gellens wrote:
>
>    At 11:01 AM +0100 2/14/17, Gunnar Hellstr=F6m wrote:
>
>     My proposal for a reworded section 5.4 is:
>
>     5.4.  Unusual language indications
>
>     It is possible to specify an unusual indication where the language
>     specified may look unexpected for the media type.
>
>     For such cases the following guidance SHALL be applied for the
>    humintlang attributes used in these situations.
>
>     1.    A view of a speaking person in the video stream SHALL, when it
>    has relevance for speech perception, be indicated by a Language-Tag
>    for spoken/written language with the "Zxxx" script subtag to indicate
>    that the contents is not written.
>
>     2.    Text captions included in the video stream SHALL be indicated
>    by a Language-Tag for spoken/written language.
>
>     3.    Any approximate representation of sign language or
>    fingerspelling in the text media stream SHALL be indicated by a
>    Language-Tag for a sign language in text media.
>
>     4.    When sign language related audio from a person using sign
>    language is of importance for language communication, this SHALL be
>    indicated by a Language-Tag for a sign language in audio media.
>
>
>    [RG] As I said, I think we should avoid specifying this until we have
>    deployment experience.
>
>    ...
>
>    From a process perspective, it's far easier to remove constraints
>    as a specification advances than it is to add them.
>
>    I agree. It is often better to specify normatively as far as you can
>   imagine, so that interoperability and good functionality is achieved.
>   Stopping halfway and have MAY in the specifications creates
>   uncertainty and less useful specifications.
>
>
>   My reading of what Randy says is the opposite of Gunnar's. In my
>   reading, Randy points out that is it easier to remove the SHOULD NOT in
>   the future then it is to change the meaning of the combinations or
>   switch to a different mechanism.
>
>   In my experience, it's better to specify only what we know we need and
>   what we know we understand.  Speculative specifications "as far as you
>   can imagine" more often lead to interoperability problems, unnecessary
>   complexity, limitations on what's needed in the future, and divergent
>   implementations.
>
>
>   I think the difference in your positions comes down to
>
>     (1) your respective notions of "what we know we need and what we
>         know we understand";
>
>     (2) whether you believe that the interoperability and conformance
>         consequences of removing a "SHOULD NOT" could be the same
>         as those merely retaining a "MUST" or "SHALL" - this determines
>         whether Randy G.'s proposal provides a path for some future
>         revision to mandate (if deployment experience substantiates the
>         need/understanding) the behavior proposed by Gunnar. That path
>         is not at all obvious to me.
>
>
>  The purpose of the draft is to enable the two=20
> endpoints of a real-time communication session=20
> to agree which languages and media to use for=20
> interactive communication.  We have a mechanism=20
> of adding language tags to media stream=20
> negotiations.  In most cases, the language and=20
> media modality are an obvious fit.  There are=20
> combinations of media and language where the=20
> meaning is not so obvious, specifically, signed=20
> language tags with a audio or text, and=20
> non-signed language tags with video.  My=20
> proposal is that we say offerer SHOULD NOT send=20
> such combinations and answerer MAY ignore=20
> language. This allows future specifications for=20
> the underlying uses Gunnar wants (such as=20
> real-time subtitles in video and signed=20
> equivalents in text).  Such future=20
> specifications could define a use for the=20
> language and media combinations and remove the=20
> SHOULD NOT send and MAY ignore, or could define=20
> a new mechanism.  I don't think we know enough=20
> now to dictate what the solution should be.
>
>  We have a fresh example from our own=20
> discussions in the SLIM group how unfortunate=20
> it is to not be sufficiently explicit in the=20
> first edition of a standard. The SDP Lang=20
> attribute in RFC 4566, where you (Randall) say=20
> it is intended for specifying a set of=20
> languages that all must be used in a session,=20
> while I say that it is intended for negotiation=20
> of at least one initial language. By having=20
> that uncertainty in a specification that has=20
> been published makes it very hard to sharpen up=20
> the specification afterwards because it would=20
> possibly make some implementations non=20
> conformant. And it makes potential implementors=20
> hesitant to use the current specifications, as=20
> it was with the SLIM work.
>
>  For 5.4.
>
>  I am OK with modifying from my latest proposal, but we need to be specifi=
c.
>  I am also OK with reducing the SHALLs to SHOULDs as Addison requested.
>
>  The situation is not that we lack knowledge.=20
> Here is what we know about the 4 cases of=20
> "unusual" indications:
>
>  1. View of the speaker in video. Very important=20
> for speech perception. Quality requirements are=20
> documented in ITU-T H-series Supplement 1. Of=20
> real use only as a complement to the same=20
> spoken language in audio. Now, when we know=20
> about the Zxxx notation for non-written, we=20
> also have a good way of specifying it precisely.
>  This case was also described in section 5.2 already.
>
>  2. Text captions in the video stream.
>  This can be either text merged into video and=20
> communicated as true part of the video image,=20
> or it can be a text component of a multimedia=20
> system, as MPEG-4, declared in SDP as m=3Dvideo.
>  It has been used in some videophone products,=20
> but I have not seen it used lately.
>  It is a clearly defined case, and we can=20
> specify coding for it, but we do not at the=20
> moment know if it will be important to specify=20
> it.
>
>  3. Sign language or fingerspelling in the text stream.
>  I have seen a product using it for claimed sign=20
> language conversation. It is also in use in the=20
> simple text form with words in capitals=20
> approximately representing signs between=20
> persons involved in preparation of sign=20
> language productions and translations. But in=20
> that case it is in a session where they agree=20
> in other ways to start using the text stream=20
> for that purpose. So I think we can say that=20
> this is rare, and its use can be agreed by=20
> other means between the users. Still it is a=20
> clearly defined case.
>
>  4. Audio from signing person related to sign=20
> language. This is more vague than the others.=20
> It may be a person signing in video and adding=20
> spoken words in audio to signing, but=20
> influenced by the word order and grammar of=20
> sign language with some ambition to make it=20
> reasonably understandable for both deaf and=20
> hearing participants. There are even some=20
> spoken words created from sign language that=20
> are commonly used by hearing persons in such=20
> situations. But for that case I anyway think it=20
> is better to define the audio part as the=20
> spoken language it is derived from, because of=20
> its intention to be understandable for hearing=20
> persons. All other variants I can imagine are=20
> even closer to the spoken language and should=20
> be specified with spoken language tag. If we=20
> only want to have the audio stream established=20
> to hear the background in the signing=20
> situation, then we should not specify language=20
> use of the audio stream.
>  Even if we know what sign language tag in audio=20
> stream would be, it may be just as good to=20
> leave it undefined.
>=20
> --------------------------------------------------------------------------=
----------------------------------------------------------------------
>  So, new proposal:
>
>  5.4.  Unusual language indications
>
>     It is possible to specify an unusual indication where the language
>     specified may look unexpected for the media type.
>
>     For such cases the following guidance SHOULD be applied for the
>    humintlang attributes used in these situations.
>
>     1.    A view of a speaking person in the video stream SHOULD, when it
>    has relevance for speech perception, be=20
> indicated by a humintlang attribute with a=20
> Language-Tag
>    for a spoken/written language with the "Zxxx" script subtag to indicate
>    that the contents is not written.
>
>     2.    Text captions included in the video stream SHOULD be indicated
>    by a humintlang attribute with Language-Tag for spoken/written language=
=2E
>
>     3.    A Language-Tag for a sign language=20
> specified in a humintlang attribute for a text=20
> stream MAY be interpreted as use of an=20
> approximate representation of sign language or=20
> fingerspelling in the text media stream. The=20
> use of such representation is rare and usually=20
> conveniently agreed by other means between the=20
> users during an established session. Common=20
> support of this indication SHOULD NOT be=20
> assumed or required.
>
>     4.    A Language-Tag for a sign language=20
> specified in a humintlang attribute for an=20
> audio stream SHOULD NOT be indicated and MAY be=20
> ignored on reception. Any use of spoken words=20
> or spoken language in the audio stream SHOULD,=20
> when it can be of importance for language=20
> communication, be indicated by the=20
> corresponding Language-Tag for spoken language=20
> in a humintlang attribute for the audio stream.
>
>
>
>
>  Gunnar
>
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  <mailto:gunnar.hellstrom@omnitor.se>gunnar.hellstrom@omnitor.se
>  <tel:%2B46%20708%20204%20288>+46 708 204 288
>
>  _______________________________________________
>  SLIM mailing list
>  <mailto:SLIM@ietf.org>SLIM@ietf.org
>=20
> <https://www.ietf.org/mailman/listinfo/slim>https://www.ietf.org/mailman/l=
istinfo/slim


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Computers are not intelligent.  They only think they are.


From nobody Wed Feb 15 18:25:02 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C42DA129496; Wed, 15 Feb 2017 18:25:00 -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 autolearn_force=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 eDFY1BDgA3P0; Wed, 15 Feb 2017 18:24:59 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 A7125129462; Wed, 15 Feb 2017 18:24:59 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ceBke-0006nL-Op; Thu, 16 Feb 2017 02:24:57 +0000
Date: Thu, 16 Feb 2017 11:24:54 +0900
Message-ID: <m2y3x6eutl.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: otroan@employees.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rl6hWUHelG3HCJCcBtJPZBnvcMY>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 02:25:01 -0000

> If your statement is that we only have the 64 bit boundary because of
> SLAAC I believe you are wrong.

cite, please.  what else actually needs it?

randy


From nobody Wed Feb 15 18:27:52 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77DC5129496; Wed, 15 Feb 2017 18:27:51 -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 autolearn_force=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 I5x7Brcy1mLv; Wed, 15 Feb 2017 18:27:50 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 7FB83129428; Wed, 15 Feb 2017 18:27:50 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ceBnQ-0006od-SJ; Thu, 16 Feb 2017 02:27:49 +0000
Date: Thu, 16 Feb 2017 11:27:46 +0900
Message-ID: <m2wpcqeuot.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: otroan@employees.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kfe6WF8j6qGpTVeDeI5EYg7knjE>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 02:27:51 -0000

> PROPOSED:
> 
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
>    unicast addresses used for Stateless Address Autoconfiguration
>    [RFC4862] is required to be 64 bits long. The rationale for the 64
>    bit boundary in IPv6 addresses can be found in [RFC7421]

i can live with this.

randy


From nobody Wed Feb 15 21:06:15 2017
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB891294DB; Wed, 15 Feb 2017 21:06:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level: 
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 58ko8MBglH3G; Wed, 15 Feb 2017 21:06:13 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 348871294AC; Wed, 15 Feb 2017 21:06:13 -0800 (PST)
Received: from [127.0.0.1] (109.47.1.57) by linfreserv (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 28204D; Thu, 16 Feb 2017 06:06:04 +0100
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
X-Mailer: BlackBerry Email (10.3.2.2876)
Message-ID: <20170216050604.6025298.75841.77680@linfre.de>
Date: Thu, 16 Feb 2017 06:06:04 +0100
Subject: AW: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Karsten Thomann <karsten_thomann@linfre.de>
In-Reply-To: <m2wpcqeuot.wl-randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>, otroan@employees.org
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 6
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JKNVUD4LPy9alPHTLwdXAIYVJ_8>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 05:06:14 -0000

=C2=A0 Originalnachricht =C2=A0

> PROPOSED:
>=20
> IPv6 unicast routing is based on prefixes of any valid length up to
> 128 [BCP198]. For example, [RFC6164] standardises 127 bit prefixes
> on inter-router point-to-point links. However, the Interface ID of
> unicast addresses used for Stateless Address Autoconfiguration
> [RFC4862] is required to be 64 bits long. The rationale for the 64
> bit boundary in IPv6 addresses can be found in [RFC7421]

As Randy, I can live with it.=E2=80=8E

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


From nobody Wed Feb 15 23:09:09 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5094129759 for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 23:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level: 
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMz3t0c7nwqh for <ietf@ietfa.amsl.com>; Wed, 15 Feb 2017 23:09:06 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 039CE1295EA for <ietf@ietf.org>; Wed, 15 Feb 2017 23:09:05 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,168,1484035200"; d="scan'208";a="177158227"
Received: from hioexcmbx05-prd.hq.netapp.com ([10.122.105.38]) by mx144-out.netapp.com with ESMTP; 15 Feb 2017 22:59:51 -0800
Received: from VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) by hioexcmbx05-prd.hq.netapp.com (10.122.105.38) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 15 Feb 2017 23:08:33 -0800
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Wed, 15 Feb 2017 23:08:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=X4oi7sRtbsBs0sSHgy0xnbUfn5WcDUPNkZW8+DoAOAc=; b=mkiVEu6W2g9lqQ6mw0oIy7v5ijQ0f9qoCdhWWAroxIlTwiR6ul94BfnaBL6haOwcIdVJBoL6Og0YPH0SBXKbobWwSEPXJLmyRtSo67eWIUWeTNW2h9oEEauw0M+EBBfTYuIfesfWHH+KjXjpCMMAgdx9whN9v4OmJFhtyRyp/IU=
Received: from BY1PR0601MB1158.namprd06.prod.outlook.com (10.160.196.21) by BY1PR0601MB1159.namprd06.prod.outlook.com (10.160.196.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Thu, 16 Feb 2017 07:08:31 +0000
Received: from BY1PR0601MB1158.namprd06.prod.outlook.com ([10.160.196.21]) by BY1PR0601MB1158.namprd06.prod.outlook.com ([10.160.196.21]) with mapi id 15.01.0888.030; Thu, 16 Feb 2017 07:08:31 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>
Subject: Re: Internet Research Labs Draft
Thread-Topic: Internet Research Labs Draft
Thread-Index: AQHSh6ja4D9+mydB3Umi2m5w/ObCPaFrN6Ob
Date: Thu, 16 Feb 2017 07:08:31 +0000
Message-ID: <081BECEC-CB75-43C6-B522-B1B7E227E4B3@netapp.com>
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com>, <1302911527.6950973.1487176178877@mail.yahoo.com>
In-Reply-To: <1302911527.6950973.1487176178877@mail.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [2a01:598:b004:50af:84c2:6028:6697:8a7a]
x-ms-office365-filtering-correlation-id: 7b5a73c8-ccf1-4eb0-77c0-08d4563a9d46
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BY1PR0601MB1159; 
x-microsoft-exchange-diagnostics: 1; BY1PR0601MB1159; 7:3jRm899ytme3TMJPhsXcSVDBby5TBkNmD9uuixV1gZuSQgid+fuqtR16yRfUZsazHPsb9j+OUwEOFGAXDbu3KQcxzrJAHxm6mq+RUjfBqG+vpDsCiZrX3HxDI2CTtrrvaOddg/X/ZPqyGQ0Oo8WpKLvEUly/MnGBJ6IKzQdsYsMi/nry6vY/CwdnXgjcADkSJVoXk4iZ2flOb5Zpwlv2cVDytSFALXzrtz9qYiUE7y1ETRmLMudO7PwCxbSY7NmZ2W9qXrjZXBW0OHyyqlgo9GXWXBsL8MeSncD2dGEVrkybRv4XiARsPp1e1YtL0IImhYLA92o6fbSdEHOl67kOcg==
x-microsoft-antispam-prvs: <BY1PR0601MB11593F20B6B1F5AFAD2F7A5EA75A0@BY1PR0601MB1159.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(6072148); SRVR:BY1PR0601MB1159; BCL:0; PCL:0; RULEID:; SRVR:BY1PR0601MB1159; 
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(6009001)(7916002)(39450400003)(24454002)(189002)(199003)(6246003)(54356999)(86362001)(83716003)(97736004)(3480700004)(38730400002)(76176999)(8676002)(8936002)(82746002)(15974865002)(389900002)(6116002)(81156014)(122556002)(36756003)(3660700001)(53936002)(102836003)(81166006)(110136004)(105586002)(5660300001)(2906002)(106356001)(106116001)(6436002)(6506006)(2900100001)(4326007)(77096006)(68736007)(7736002)(99286003)(189998001)(5640700003)(3280700002)(50986999)(6486002)(6916009)(2950100002)(6512007)(2351001)(305945005)(101416001)(92566002)(229853002)(6306002)(25786008)(2501003)(33656002)(54906002)(104396002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY1PR0601MB1159; H:BY1PR0601MB1158.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 07:08:31.0003 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY1PR0601MB1159
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f3kAjG33AmGZjTOibgfPROph01A>
Cc: Harish Chowdhary <harish@nixi.in>, IETF Discussion List <ietf@ietf.org>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 07:09:08 -0000

How is this different from codestand?

--=20
Sent from a mobile device; please excuse typos.
+49 151 120 55791

> On Feb 15, 2017, at 17:30, "nalini.elkins@insidethestack.com" <nalini.elk=
ins@insidethestack.com> wrote:
>=20
>=20
>=20
>=20
>=20
> All,
>=20
> If anyone is interested, we have just done an I-D for a proposed concept =
for "Internet Labs".   We hope this will be of interest.=20
>=20
> https://tools.ietf.org/html/draft-chowbat-irl-00=20
>=20
> The abstract is here:=20
>=20
> Many people learn technical concepts best in a hands-on environment,=20
> and Internet protocols and standards are no exception. Internet=20
> Research Labs (IRL) will facilitate a platform and encourage the=20
> technical community (seasoned professionals and newcomers alike) to=20
> discuss, collaborate, design and develop utilities, ideas, sample=20
> code and solutions that show practical implementations (Proof of=20
> Concept) of existing IETF standards. These labs may also be used by=20
> the IETF Mentoring Program and/or EDU teams for hands-on training to=20
> mentees or newcomers. This base draft intends to provide a high-level=20
> overview of the concept of Internet Research Labs in terms of=20
> objectives, requirements, challenges and deliverables without going=20
> into details of a specific lab, technology or an IETF Working Group=20
> (WG). After this draft matures and gains traction within the IETF=20
> community, we foresee more and more Internet drafts for the specific=20
> labs.=20
>=20
> Thanks,
>=20
> Nalini Elkins
> Inside Products, Inc.
> www.insidethestack.com
> (831) 659-8360
>=20


From nobody Wed Feb 15 23:40:11 2017
Return-Path: <sthaug@nethelp.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 153DD1294DB; Wed, 15 Feb 2017 23:40:09 -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 autolearn_force=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 q7NVDjMefv7M; Wed, 15 Feb 2017 23:40:07 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC23129447; Wed, 15 Feb 2017 23:40:06 -0800 (PST)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 2F466E6065; Thu, 16 Feb 2017 08:40:04 +0100 (CET)
Date: Thu, 16 Feb 2017 08:40:04 +0100 (CET)
Message-Id: <20170216.084004.74672265.sthaug@nethelp.no>
To: randy@psg.com
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: sthaug@nethelp.no
In-Reply-To: <m2wpcqeuot.wl-randy@psg.com>
References: <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RLWFkEU6PrRliOQ1APHa7HP_jTU>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, ipv6@ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 07:40:09 -0000

> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
> >    on inter-router point-to-point links.  However, the Interface ID of
> >    unicast addresses used for Stateless Address Autoconfiguration
> >    [RFC4862] is required to be 64 bits long. The rationale for the 64
> >    bit boundary in IPv6 addresses can be found in [RFC7421]
> 
> i can live with this.

+1

Steinar Haug, AS2116


From nobody Thu Feb 16 00:23:41 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 615F61299C4; Thu, 16 Feb 2017 00:23:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NmSsJs1UZ--z; Thu, 16 Feb 2017 00:23:34 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 07F26129490; Thu, 16 Feb 2017 00:23:33 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Feb 2017 08:23:33 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 4A1DBD788B; Thu, 16 Feb 2017 00:23:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=KHjQx3ksNn6iX67grmhEZr2nLMo=; b= dA+hjTSjAbdmO790A6HmzMUrobdmhEFpUiKwSaK6OJIbWDjuj52IKQbv+ZRlT0pS 9jYc8JbGxjhhqaNzy1D4s0xrNygU1ra4nFB6/G/D9OIl3mrbzYi5WNR+PerMsikM 1DepEhGyJ4R5aZJQJl6R8TSx4eukWFbiPuaD6bUoxPw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=pRAeloWMSK+sE0ZZFQbVz8e DG/0tdM/uUOM7dED79joyJuiS8KM95z7O7HmBaDoh5GSSoYYiYxnQ+sT94fFLReI m4TI5hyziLicpJ4avBn1Y9WLQ/aojYOwXfJ9j22DurKLYA+YF39clxPmw32GB90g GyFzcKvmLgatcPHCqpRU=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 154DCD788A; Thu, 16 Feb 2017 00:23:33 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8DED48BD9238; Thu, 16 Feb 2017 09:23:45 +0100 (CET)
From: otroan@employees.org
Message-Id: <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7F25CA48-871D-40EE-BEB7-F665956D038B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 09:23:44 +0100
In-Reply-To: <m2y3x6eutl.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dYeFagXJ29NpHewGVGT3wU2U33U>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 08:23:35 -0000

--Apple-Mail=_7F25CA48-871D-40EE-BEB7-F665956D038B
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Dear Randy,

>> If your statement is that we only have the 64 bit boundary because of
>> SLAAC I believe you are wrong.
> 
> cite, please.  what else actually needs it?

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

Best regards,
Ole

--Apple-Mail=_7F25CA48-871D-40EE-BEB7-F665956D038B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpWGRAAoJEL7aWKiYQt92aqEP/3OSSuCVvbbAp4tj9c6+7cwv
QEVYsMCeDmN1uteMlSn4BnrqRXe4jK4dZ/ya9acK8bRK1uURouTaO7VXwn+8O5Wg
vdQxC+woFdOuVz0FY+ZMaxpHFwzlLVrzwmII5vv6rU/gQ+n1pU6tMbpP/xWrUf7A
p0SH4Gj2Mna70g+AmiLXmwGPlfYgfE2t2oMPZqyEeXyHe91zmJSOsiNqO54nU2BW
bDbhLuLqlhJRQ8TnQ01wpjjkEBGf9o1vdMY+3qMBtlzEe2gLddlpVBClT5nf6PBj
n2AxChUogKQ4HPGj02sLfX2ScrGjd3P3mK7G1dWxtpMyal+x/uzqzAxGQHjis4lT
Z8EvfY8BXd4VG65MFSKhMdkZf9piLbZbvaN07oRyA5IuJkyU17JR+V3RgB5dQkPR
q2Pi7gFqUDGHNztKM3j8qLMnig9wpL3Swr0aIpWkGtEcQN4npzmrFqboCin8v0rC
Op7EsPkwKIMst+XNUv3xeVQ06gy5Anwr6KtvCwR+6GBjMUyNYaN7uY6IKIbPp0+Q
qoy8+osR2eBNLtleUJHLwDfQ1PfIvOYfsOHryDYetje2iPIZcS+9/f3AmpGZ7l9S
np4ovEC9A7DarZ9f/f6H2HSA2OmDxJbB5lQGJ2CFje1WX89+n2V19de99bpBJe0u
lU/0pGW4yQFVnDx6BF57
=3q9z
-----END PGP SIGNATURE-----

--Apple-Mail=_7F25CA48-871D-40EE-BEB7-F665956D038B--


From nobody Thu Feb 16 00:39:56 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52BCD1295FA; Thu, 16 Feb 2017 00:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wK8-nMWoxGuA; Thu, 16 Feb 2017 00:39:50 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id E0345129538; Thu, 16 Feb 2017 00:39:50 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Feb 2017 08:39:50 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id B4483D788B; Thu, 16 Feb 2017 00:39:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=O2p9p3HcDMD96FZuJy+50ZB2USY=; b= CnbF6VyI7ere0ofzOFtVZX5kYLH3GPu6Bgb7WBqVgTHMDVXmyoWeRfXVumkqfKpB Rc2hcMFTrALJGYs0WSuDC66tqhnJIQKkOZf6MKQZl4C9b9ms781Rgpa/HGWS1nAI lAjSwRSwGiSlChIbYSAEtNFk4GzlkJFTcUcR7wp6W3c=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=i5LelZqJp7EIAlVoiUyb56T oKLwTpDCeLUYq1TPYfteA8T/tVivnlG0A7t31qB6NKajZ2C0qrqqQ92+ObSIj2lN +xHP7w7kW5nvGCl7Cq0BKJFkckA/Za5oDzIUcIn2G7Qw+8UPkigzlIvSpZRbw6XR FcFjJtuwOwJVgCuB9Zj0=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3DA44D788A; Thu, 16 Feb 2017 00:39:49 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 6AE3A8BD949D; Thu, 16 Feb 2017 09:40:02 +0100 (CET)
From: otroan@employees.org
Message-Id: <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_C4A368FC-FA21-4D21-B1FE-97FC692845BA"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 09:40:01 +0100
In-Reply-To: <m2wpcqeuot.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bQNax88ZhF_SW_7z1N9A03i32bw>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 08:39:52 -0000

--Apple-Mail=_C4A368FC-FA21-4D21-B1FE-97FC692845BA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Randy, Karsten, Steinar,

>> PROPOSED:
>>=20
>>   IPv6 unicast routing is based on prefixes of any valid length up to
>>   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>>   on inter-router point-to-point links.  However, the Interface ID of
>>   unicast addresses used for Stateless Address Autoconfiguration
>>   [RFC4862] is required to be 64 bits long. The rationale for the 64
>>   bit boundary in IPv6 addresses can be found in [RFC7421]
>=20
> i can live with this.

I presume the reason why you can live with it, is exactly because of the =
earlier pointed out loophole? :-)

You can't have it. At least not in this context. Write a draft.

See 7421, 6177, 7368, section 3.4.

There are many reasons for the 64 bit boundary.
  - Allowing identifier locator split: 8+8 / GSE that led to ILNP and =
NPT66
  - Simplicity in addressing (no more subnet masks)
  - A fair balance between the users and the providers of networks.
    Ensure that users get a fair share of addresses and try to avoid
    operators charging per address.

The 64 bit boundary is so embedded in the set of IPv6 specifications =
that it would be very hard to unravel at this point. It certainly cannot =
be a single paragraph put in during the advancement of 4291. Write a =
draft. Or write a book on protocol politics and the underlaying values =
reflected in the specifications...

Best regards,
Ole

PS: With an implementor hat on, I write code that can deal with any =
prefix length.

--Apple-Mail=_C4A368FC-FA21-4D21-B1FE-97FC692845BA
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpWViAAoJEL7aWKiYQt9230gP/0Ha55SxFWy5QJTNWE+zA0Nz
xIZ7c1ayqbV0Psjqw1IW9RQFEM/Qrb/H3FfrtK3RdvBB0+Awj3c/wl8qBgmGmi/7
3r1K2aiipWq0iN5MR6u/RNLACXq3n+U0Ii/LIVqTo14EPAJgWTUm2fH5EfjFUkqj
aqsDhhxaHIPAmKLxEOMIOQ9YakIoQeR9RAUg06BPJy6vaURzRMo9/Y/npSTynztN
Lb9UzXaC6h41SC/yCoahuPIXEzUmueIluSwt6iwy3waCx4lG2koxxR7ZKaV+K4bH
TfgHBLkLAharCyU4Alaw2b7BY5WQ+tKGdJiZtU+pslrNf4eg1RPYnKgMporPMXnj
vGxlXVbIh+Yv+aR3SmqrtnOUrcXDgA7N0+WVfIXyOeD+ZQlJLbqYlKAKiDK3tiaC
Aw8rej05NWVi4yRk6qlKAnXEhif5Koes87fhWu90+ivG/0VbprJMKuxaArCZZy8a
uUdjcUxkX3TcnmtXwKK+bOSpI+QSsAaZzKCwSiPIuRiQjda96bkITShX19aIk9hm
TSkwot+jdp6C6LRJeOuQ50X/hma7UhhJEI6bYWecwQ3/76ACoQYwtaoJukdOWXr5
w/9I6GZ2WLdVok2BeqZQkVgkM3nInxAykF0nJ3b4jjOZhjEVdHsoDD7dSKCjySD4
/XvX6WUSwrCTG6Mwe+3n
=NSLx
-----END PGP SIGNATURE-----

--Apple-Mail=_C4A368FC-FA21-4D21-B1FE-97FC692845BA--


From nobody Thu Feb 16 00:45:30 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA4CC129554; Thu, 16 Feb 2017 00:45:28 -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 autolearn_force=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 c8znmTh1PhLL; Thu, 16 Feb 2017 00:45:27 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 8A9F1129474; Thu, 16 Feb 2017 00:45:27 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ceHgp-0000pb-I7; Thu, 16 Feb 2017 08:45:24 +0000
Date: Thu, 16 Feb 2017 17:45:20 +0900
Message-ID: <m2lgt6ed7j.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: otroan@employees.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CqOveOEV9yntZJLwzxqvjQSjEck>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 08:45:29 -0000

>>> If your statement is that we only have the 64 bit boundary because of
>>> SLAAC I believe you are wrong.
>> 
>> cite, please.  what else actually needs it?
> 
> https://tools.ietf.org/html/rfc7421

that excuses it.  cite where it is actually needed to do something
useful other than slaac.


From nobody Thu Feb 16 00:52:38 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06E871294A9 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 00:52:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KCMKv7wMM5fg for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 00:52:31 -0800 (PST)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 612B31299E0 for <ietf@ietf.org>; Thu, 16 Feb 2017 00:52:29 -0800 (PST)
Received: by mail-vk0-x235.google.com with SMTP id x75so6354391vke.2 for <ietf@ietf.org>; Thu, 16 Feb 2017 00:52:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7Uvinm3bzdx1YT9pY+hA3zOYKoNkDrYkXSF2CHabCLE=; b=BYILDP+Tcq+yU9gi/N5FMTpq+QNOmcKYdNH/IOazya2N6s5MATAKuuckYyVdkCh0ZA wYL3j2l03R7wIvcpUKLPSSoXf3VFFuJEn+Hmuw1EoExlkjFfllEyGBuy6o23l+qvdQL6 DH0eGgrob7hQQKO8GVzxlYR5aGJKTgK+4ewHhFa6qtwsEhzgqkUu4HpwIrqyfjj1pC6j 3Efv94I5MvcRTIlA457urtDSdpyQtTCtTzUSY1XQYG8oAMNXKF2euGFwVaL8a16uCCAr hfbwZZ9gpg+8IGZIJ+cSlK3GBOf9smzjqFH4P0QQ7jBZVf6zHgvpaUV4ovBc4Pzhgi8d GTMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7Uvinm3bzdx1YT9pY+hA3zOYKoNkDrYkXSF2CHabCLE=; b=sc21uOeDb9F3xjiIASe+z+hDvkZmlK48KkgifAtraBqSbkVZhaINOsHp+2I7RXFc+3 SLJTPXMoXF/qFC5kn1yKVs6AcTmqZBJKoM5ybV9V2TaYS9WiEh40UYdr3SMEynNq+N7Z cw3PGU/TZvq95HfP4hTraRgLsbm8rsQuKbBlK5TiyjhpOGF3ekeh0GlV6okvi4il94w2 bOHDR0lVKZalWk2plMLeFfxoHfVc4kC+WMpnz9g/jWBQsObP6DyiMARuebIn+UCSBLNM XTVA/5uiAEWziU9FZYsxg1+2svT6sSDTBu8DSdP/NATJNE5Oo3+Avd/ZSvBlqH8vNN7k seSg==
X-Gm-Message-State: AMke39k6hKi+9n9K3loVMoS9GG62qN1+bie4wwiUwiOKPULmeUBZHX0xm5dgv6MT5FCKCvkkS3u9ZlLs7IKaqhpz
X-Received: by 10.31.170.15 with SMTP id t15mr471606vke.6.1487235148155; Thu, 16 Feb 2017 00:52:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 16 Feb 2017 00:52:07 -0800 (PST)
In-Reply-To: <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 16 Feb 2017 17:52:07 +0900
Message-ID: <CAKD1Yr0Wii_gknFy+uPt+MqTLa_=O_y6JT+qdR8psaHTjUztfA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a11432250b4a8da0548a1ea6c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iXzwjiQr0XT_o4kWfaAHaZKvueE>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 08:52:32 -0000

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

On Thu, Feb 16, 2017 at 5:40 PM, <otroan@employees.org> wrote:

> See 7421, 6177, 7368, section 3.4.
>
> There are many reasons for the 64 bit boundary.
>   - Allowing identifier locator split: 8+8 / GSE that led to ILNP and NPT66
>   - Simplicity in addressing (no more subnet masks)
>   - A fair balance between the users and the providers of networks.
>     Ensure that users get a fair share of addresses and try to avoid
>     operators charging per address.
>
> The 64 bit boundary is so embedded in the set of IPv6 specifications that
> it would be very hard to unravel at this point. It certainly cannot be a
> single paragraph put in during the advancement of 4291.


Right. If we want to change this we can, but the process for that is start
with "write a draft and get consensus in 6man". We cannot change it while
revving 4291 to full standard, because it's a substantial change.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 16, 2017 at 5:40 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:otroa=
n@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">See 7421, 6177, 736=
8, section 3.4.<br>
<br>
There are many reasons for the 64 bit boundary.<br>
=C2=A0 - Allowing identifier locator split: 8+8 / GSE that led to ILNP and =
NPT66<br>
=C2=A0 - Simplicity in addressing (no more subnet masks)<br>
=C2=A0 - A fair balance between the users and the providers of networks.<br=
>
=C2=A0 =C2=A0 Ensure that users get a fair share of addresses and try to av=
oid<br>
=C2=A0 =C2=A0 operators charging per address.<br>
<br>
The 64 bit boundary is so embedded in the set of IPv6 specifications that i=
t would be very hard to unravel at this point. It certainly cannot be a sin=
gle paragraph put in during the advancement of 4291.</blockquote><div><br><=
/div><div>Right. If we want to change this we can, but the process for that=
 is start with &quot;write a draft and get consensus in 6man&quot;.=C2=A0We=
 cannot change it while revving 4291 to full standard, because it&#39;s a s=
ubstantial change.</div></div></div></div>

--001a11432250b4a8da0548a1ea6c--


From nobody Thu Feb 16 01:09:34 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 897861299DC; Thu, 16 Feb 2017 01:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UaPik42AklZw; Thu, 16 Feb 2017 01:09:28 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id EBC1D129554; Thu, 16 Feb 2017 01:09:27 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Feb 2017 09:09:27 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 887D4D788D; Thu, 16 Feb 2017 01:09:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=wMh8D9NcT1rWDNlztaAbV+hEljc=; b= dxwLN40S3Tp1pRu0jU6ljlBvpSu5IaVn/FgpN9pIh7TrQx06EdHCV7G6f1uHqZD2 DKVpC3qzBfF2whIzU1gmUps/073X6G6j2i1bQek11Zx/FWYOLD9bYwvoTdEZnVfm dO0rWtxiR+1nAlj555GoAKySay5PYphPphC95GipgHQ=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=U3hWir+uxsIVSjEnaviurnr hjlY9vXuFJKjIj1+Kh5R27BcCL46i1lbhTZnzZG6mehdRYzE3XhuwaGPj0k+/l1D TPvol/jwBIlEfnLQ5L+k3LmT71aX98JvynPlJz7NNkJg8qwOBSbJkiJzo/Ui2WdH 54LSoVV+OlubiTFRXlzQ=
Received: from h.hanazo.no (219.103.92.62.static.cust.telenor.com [62.92.103.219]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 12B2AD788B; Thu, 16 Feb 2017 01:09:27 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 4C64B8BD9ACD; Thu, 16 Feb 2017 10:09:40 +0100 (CET)
From: otroan@employees.org
Message-Id: <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_299F18D2-B57A-46AA-9616-80990B180740"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 10:09:39 +0100
In-Reply-To: <m2lgt6ed7j.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7lGq2vUB5quAgV34Cu_4FZP97q8>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 09:09:29 -0000

--Apple-Mail=_299F18D2-B57A-46AA-9616-80990B180740
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dear Randy,

>>>> If your statement is that we only have the 64 bit boundary because =
of
>>>> SLAAC I believe you are wrong.
>>>=20
>>> cite, please.  what else actually needs it?
>>=20
>> https://tools.ietf.org/html/rfc7421
>=20
> that excuses it.  cite where it is actually needed to do something
> useful other than slaac.

"something useful" makes it subjective.

If you only care about technical issues, then:
SLAAC, NPT66, ILNP are the biggest one that I can think of.
Trivial to make SLAAC work with variable length prefixes of course.
As well as we don't know the consequences for implementations.
7421 seems to indicate it mostly works.

But then you have people who write code like this:
https://git.fd.io/vpp/tree/src/vnet/map/map.h#n332

Where it clearly will not work with a longer prefix than 64.
Feel free to contribute a patch, but make sure to count the cycles spent =
through that code.

I expect you'll find that most implementations deal with variable prefix =
length reasonably well, as long as you stay away from any of the above =
technologies.

There are many other issues here though, do we want to keep the option =
of an identifier and locator split open? Do the collective we trust the =
collective you to not put us into the same situation we had with IPv4 =
were users are forced to pay per address and instead chooses to deploy =
NAT?

It is upon you to provide evidence and justification for a proposed =
change. Not the other way around. Write a draft.

Best regards,
Ole


--Apple-Mail=_299F18D2-B57A-46AA-9616-80990B180740
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpWxUAAoJEL7aWKiYQt920hsQAJyrhD0ftQrbynO/bHJYitd2
GN4RE8aA5q+ZkLzAEPfa+ZI+2kHvcHhj+etj3gOmUuNoeEGvu3Kiwd6tHD23EJwM
Prvujb7hZ32E8GubU+tp72w1prfaoXfAypg++vs1xmObuNCvyEmU9UrprXz4EPzD
/0Hkq/UbeYkvG64mjhUw8C6z/yieGbQh9AaDEOS4oNRoEbcqv88LiA59xCPxQFEz
5E1e6B3kQp2YePcMA6h9lN3BP2Qo3QCZZ5b64GnKiEr7H3NSPUrALZWKa4zMnFrL
Hat2OQW5Nno99LsfsCwyYqZv26THAR6RioaEJzhFeVLPAF9jwhzwtYfE810MINOj
AnbvdO05eaOyPzloJAiScHL83KubLdwX7/lRmVA+GPtaPKOO5Xdtvhstpz6MA+J4
vwYX9OhrdNn7Out+lQjgIsYZP/cVengszqz/QYDgcLorewRaxd0ayQS6MKWnjGAc
X+WAebSmb1ZT5oYKe55xm1BH0nXNdDrhj0vplESk/U5PacehC7WeeOsk91yv0ct4
JfErD383jDkNELFdSDS6mTdxun+8SPYYrE8l1QVkzne3rhpPAlKeyJLmdwVxMFnk
HccQ9QozeKrCA91Rr4093eKrmj52xzBXJL/tk+jA5Rik9CKoMKjdNij6A5KMWFeA
3HZvdYsfeRdJiiT2ZY3X
=ckX8
-----END PGP SIGNATURE-----

--Apple-Mail=_299F18D2-B57A-46AA-9616-80990B180740--


From nobody Thu Feb 16 01:14:00 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62E5A1299E4; Thu, 16 Feb 2017 01:13:55 -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 autolearn_force=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 7682xltYZdKj; Thu, 16 Feb 2017 01:13:54 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 6EE911299E0; Thu, 16 Feb 2017 01:13:54 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ceI8O-00011Z-9P; Thu, 16 Feb 2017 09:13:52 +0000
Date: Thu, 16 Feb 2017 18:13:49 +0900
Message-ID: <m2k28qebw2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: otroan@employees.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TnoKh0q31_DMYDllHuf1i7RTk2s>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 09:13:55 -0000

> "something useful" makes it subjective.

some of us try to operate networks.  useful is what customers pay us to
do.

> SLAAC, NPT66, ILNP are the biggest one that I can think of.

slaac is real, used, and is useful in some environments that customers
want.

> Trivial to make SLAAC work with variable length prefixes of course.

64 for slaac is fine.

for the rest, we went to cidr over a decade back, when folk scammed mo
out of 8+8.

randy


From nobody Thu Feb 16 01:37:44 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8E331299D1 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 01:37:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 GmWGwuYT9DNL for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 01:37:39 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 A84681299CE for <ietf@ietf.org>; Thu, 16 Feb 2017 01:37:39 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id B372D280759; Thu, 16 Feb 2017 10:37:37 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id AD487280756; Thu, 16 Feb 2017 10:37:37 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id AB5A7B3800C; Thu, 16 Feb 2017 10:37:07 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id A8393406CE; Thu, 16 Feb 2017 10:37:07 +0100 (CET)
Date: Thu, 16 Feb 2017 10:37:07 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: nalini.elkins@insidethestack.com
Subject: Re: Internet Research Labs Draft
Message-ID: <20170216093707.z2ienyk52r3pbl7x@nic.fr>
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com> <1302911527.6950973.1487176178877@mail.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1302911527.6950973.1487176178877@mail.yahoo.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.8.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Awo8wKPmGWJOiCxlTa79GRBjhTA>
Cc: Harish Chowdhary <harish@nixi.in>, IETF Discussion List <ietf@ietf.org>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 09:37:42 -0000

On Wed, Feb 15, 2017 at 04:29:38PM +0000,
 nalini.elkins@insidethestack.com <nalini.elkins@insidethestack.com> wrote 
 a message of 34 lines which said:

> If anyone is interested, we have just done an I-D for a proposed
> concept for "Internet Labs".   We hope this will be of interest.

That's interesting, there is certainly a need for more resources for
the people who want to work on the practical side of the Internet
protocols.

> https://tools.ietf.org/html/draft-chowbat-irl-00

I find the proposal both too detailed ("access to IRL labs" with
discussion of CLI vs Blackberry...) and too vague. What will be the
actual services provided by these labs?

There are a lot of resources already available. (Really a lot: may be
the poeple who want to learn/work could use some guidance.) Did you
identify actual gaps (ideas: real-time BGP feed, repository of packet
captures, since pcapr.net seems de facto dead, etc)?

Editorial: for cloud services, please mention also non-US services
(like OVH or Gandi in France, examples from China, Russia, India, are
welcome).


From nobody Thu Feb 16 01:54:07 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 299B31299E8; Thu, 16 Feb 2017 01:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FbAY_iqovh4a; Thu, 16 Feb 2017 01:54:00 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 0E3D61294E2; Thu, 16 Feb 2017 01:54:00 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id y9so7406390uae.2; Thu, 16 Feb 2017 01:54:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+NSFFdjXo86szqFitD2jwW6/6qYMH0H+rJPEb6gzdhM=; b=ETN+sHSaPxPGRtEV6bs4UjIN5aU9Bx4Lr/uKPaLernk2gddl6wYAE2tUi8KBYRFd6d KCojRkQ0OfD9GRdazLJTKydrvCLffL/Aj67G1pp8TDHbdRqRrnuHZeEZ4OQm5Jg/o5NF lIIWX9xkKMagc45x14L6VEAzMWCl8e9V+N4s8eGsT+JH9TFvFGT6ujzEzJWkDyAeUG3y Us4ztAKdH24tdHF7MwvKeFqKne4u1PAqRqwuDLQXxmmdzwTe56d+xWjDIjIreMzSbpSE v3YAH+HbwYaubB4IXMiLG2QasUHfBDRYJFdHBUv3rckxUmCdAXPROluRSE894YDlKNez BBlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+NSFFdjXo86szqFitD2jwW6/6qYMH0H+rJPEb6gzdhM=; b=c+8whNZnepdnxev3aQqYaaVSaONmsLe6J2kYoIThS9LP8SCtIuwL4nC1lF0QdaHIGt EWfrbif9SpRAhW/XtWaHR5NWu0gwzbmLWjSXvAktkCI69sXLO46M9g5dVv9f+U9yMe9u LnUmPmuboCP9y8uRKez4WZOu16UEDA3PKRamOPl73hbRQJrS8TDw62hHh7UB6P3P4u/M Ua1/pifxuobl+poFGPzbRB7glumcTZheHFbBaVIuL/6hwY2dIoIfC8Bb7rrip2+BaPin ooVzjkoEHvVUmvYOLBgWzKMoOC5OHA3/QyKYX8riqxB0rYPZpTOJu5P0BQ+/zPXc3ZFX 81gg==
X-Gm-Message-State: AMke39ksFa2pZOg/AyeI1awI135xyhavAi9L8Hfw5GFOOBSy7rGb1sjR/SFQB33jR3hzBYJJgfHMVU2eyPW7OA==
X-Received: by 10.159.40.225 with SMTP id d88mr242889uad.98.1487238839189; Thu, 16 Feb 2017 01:53:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Thu, 16 Feb 2017 01:53:58 -0800 (PST)
Received: by 10.159.38.2 with HTTP; Thu, 16 Feb 2017 01:53:58 -0800 (PST)
In-Reply-To: <m2k28qebw2.wl-randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <m2k28qebw2.wl-randy@psg.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 16 Feb 2017 20:53:58 +1100
Message-ID: <CAO42Z2xiS2NM+oKQCG8XwB3HFMMKoFOJBk1P=EpaabBbdggc1A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=94eb2c122be8b4c8980548a2c6e1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jz1PGAE9-iDJa_aT6DmO2bbhfQw>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 09:54:01 -0000

--94eb2c122be8b4c8980548a2c6e1
Content-Type: text/plain; charset=UTF-8

On 16 Feb. 2017 8:14 pm, "Randy Bush" <randy@psg.com> wrote:

> "something useful" makes it subjective.

some of us try to operate networks.  useful is what customers pay us to
do.

> SLAAC, NPT66, ILNP are the biggest one that I can think of.

slaac is real, used, and is useful in some environments that customers
want.


One of the benefits of a /64 is that IIDs within it can be sparsely
distributed, making device discovery by unsolicited inbound address probing
ineffective.

I think a router having these sorts of sparse IIDs in its addresses would
be a useful mitigation against router control plane attacks, such as a syn
attack on port 179 from the Internet.


Regards,
Mark.


> Trivial to make SLAAC work with variable length prefixes of course.

64 for slaac is fine.

for the rest, we went to cidr over a decade back, when folk scammed mo
out of 8+8.

randy

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

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 16 Feb. 2017 8:14 pm, &quot;Randy Bush&quot; &lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt; wrote:<br type=
=3D"attribution"><blockquote class=3D"m_-5325686112877695867quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=
=3D"m_-5325686112877695867quoted-text">&gt; &quot;something useful&quot; ma=
kes it subjective.<br>
<br>
</div>some of us try to operate networks.=C2=A0 useful is what customers pa=
y us to<br>
do.<br>
<div class=3D"m_-5325686112877695867quoted-text"><br>
&gt; SLAAC, NPT66, ILNP are the biggest one that I can think of.<br>
<br>
</div>slaac is real, used, and is useful in some environments that customer=
s<br>
want.<br>
<div class=3D"m_-5325686112877695867quoted-text"></div></blockquote></div><=
/div></div><div dir=3D"auto"><br></div><div dir=3D"auto">One of the benefit=
s of a /64 is that IIDs within it can be sparsely distributed, making devic=
e discovery by unsolicited inbound address probing ineffective.</div><div d=
ir=3D"auto"><br></div><div dir=3D"auto">I think a router having these sorts=
 of sparse IIDs in its addresses would be a useful mitigation against route=
r control plane attacks, such as a syn attack on port 179 from the Internet=
.</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"=
auto">Regards,</div><div dir=3D"auto">Mark.</div><div dir=3D"auto"><br></di=
v><div dir=3D"auto"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
blockquote class=3D"m_-5325686112877695867quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"m_-532568611287=
7695867quoted-text"><br>
&gt; Trivial to make SLAAC work with variable length prefixes of course.<br=
>
<br>
</div>64 for slaac is fine.<br>
<br>
for the rest, we went to cidr over a decade back, when folk scammed mo<br>
out of 8+8.<br>
<font color=3D"#888888"><br>
randy<br>
</font><div class=3D"m_-5325686112877695867elided-text"><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">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/l<wb=
r>istinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
</div></blockquote></div><br></div></div></div>

--94eb2c122be8b4c8980548a2c6e1--


From nobody Thu Feb 16 03:58:09 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B248129735; Thu, 16 Feb 2017 03:58:05 -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 autolearn_force=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 44gzcTKTa0Ze; Thu, 16 Feb 2017 03:58:04 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D1D2B1294C8; Thu, 16 Feb 2017 03:58:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2A75A2CEB1; Thu, 16 Feb 2017 13:58:03 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xMQVPHAWHZll; Thu, 16 Feb 2017 13:58:02 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id AF53E2CCBA; Thu, 16 Feb 2017 13:58:02 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
Date: Thu, 16 Feb 2017 13:58:02 +0200
Message-Id: <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
References: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com>
To: Orit Levin <oritl@microsoft.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TFQET4Aqt4Kg8jOyzW4GV9mcqEI>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:58:05 -0000

--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Thanks for your review, Orit!

(Authors, did you note the comment?)

Jari


--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141
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

iQIcBAEBCgAGBQJYpZPKAAoJEM80gCTQU46qed4P/3pzWrR9+kmINEBeZ+wivV7s
cWdAOYiBhbRj/Qplm9dFbLGi7gWBVJ75sBrFhxsHvbow3rVty7aSZ45m/IpPArFV
nv9WVtbCGjjCl1dHNPoOmyMtYN4+d0DcJqpBDRs8VoC5BVmDYr8Uk/b6Mtk6Qd1r
dCffEyJ1pf0kOTH9+OGE7KOP5A2RDuugbtXBwtJ4g96NC7BgFHwOnZdVOZF7bonJ
EXfWU+AYz7ky7qLSm5FSU2bh/a8jNkNTQFz9/jGSc+dk/WDuBQovpAagXtHGpPU6
K7mrTJbNXBBys9/8Gn6VfSGxHXyRZ4+vQDXotmTy9psmtTr6dKCPbDatCphw22bN
GJMvz52ByZwM5c7esPAosETrXqmTI8/kYY49fyRf6JyE3YdxQ/VaGN+I61LBT+Zd
2N8QjoOKtVAKGbzjaEKy6b4X5hOhOo2VHzqnNARzWrH3O1n6aFFVd65TCN6ZfbDp
2JWmFyLQTSmUKKUg4JmI1zWDYbqINAGFGKjCJOsiHgIGN++6/qQZuBcH4Du/FKQ3
sf3JPzB0Baj6zf4b0nHpZvxv25vBi/HG0qDb90H5XNM7YN4O0cP+MfhnaGbVlEV6
VbUe9SuI2xD5DUauk3rXPbm7cP/yRMuLvYvL68yk30swDSSAFppKVCb57MWp6su9
fsDPTlv58+CGB8PxCuXq
=p2Da
-----END PGP SIGNATURE-----

--Apple-Mail=_EEEC1A6D-40D1-4940-A095-9BC8BAF07141--


From nobody Thu Feb 16 03:59:22 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18DC1129563 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 03:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 SDpy5c5nWMkl for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 03:59:18 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 47A18129735 for <ietf@ietf.org>; Thu, 16 Feb 2017 03:59:18 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 936B9280750 for <ietf@ietf.org>; Thu, 16 Feb 2017 12:59:16 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx4.nic.fr (Postfix) with ESMTP id 8F56F28074F for <ietf@ietf.org>; Thu, 16 Feb 2017 12:59:16 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay2.nic.fr (Postfix) with ESMTP id 8D998B38003 for <ietf@ietf.org>; Thu, 16 Feb 2017 12:58:46 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id 87AA1406FA; Thu, 16 Feb 2017 12:58:46 +0100 (CET)
Date: Thu, 16 Feb 2017 12:58:46 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Subject: [Wasting of time] "Let's Face Facts: We Need a New Industrial Internet"
Message-ID: <20170216115846.2of3fakuvthd5qtl@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.8.0-2-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Xd7__aDkxNUHPR0Gnjo-LApaB6A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 11:59:20 -0000

[Only if you are bored and have nothing useful to do.]

A guy solved all the problems of the Internet, thanks to a new
mathematical theory he developed, "∆Q" :

http://www.circleid.com/posts/20170214_lets_face_facts_we_need_a_new_industrial_internet/

He also calls us "unethical" but, among all its claims, this is the
least crazy :-)

Let's congratulate Circle ID (which, most of the time, publishes
interesting things) for its openness of mind: any random troll can
publish here.


From nobody Thu Feb 16 04:04:15 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA85F1294E6; Thu, 16 Feb 2017 04:04:04 -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 autolearn_force=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 khIB9vCfk830; Thu, 16 Feb 2017 04:04:02 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id 5939A129563; Thu, 16 Feb 2017 04:04:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AF6BA2CEB1; Thu, 16 Feb 2017 14:04:01 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gz-uZ9gl_iij; Thu, 16 Feb 2017 14:04:01 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 2A3632CCBA; Thu, 16 Feb 2017 14:04:01 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:04:00 +0200
Message-Id: <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com>
To: Roni Even <roni.even@mail01.huawei.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JWGuRcBNDRD3Sm_BzBJrfvEtYx8>
Cc: dhcwg@ietf.org, gen-art@ietf.org, ietf@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:04:04 -0000

--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Roni: thanks for your detailed review. I also appreciate
the responses and changes by you Tianxiang. I have
balloted no-objection for this document for today=92s
IESG telechat, and expect that the discussed changes
will find themselves into a new document version at
some point.

Jari


--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC
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

iQIcBAEBCgAGBQJYpZUwAAoJEM80gCTQU46qJrQP/2Q3KFZv7t9N/+MIRJoIej15
ZkQNNWzW/yp7Xw33FPLHet7cFA2Bz0Qijudj0UmplChFxLxzDLeAu8rKxN21yb6n
Vb6gJs7kITlHyWsyElialCKmVsCIULZ5oAzP5VmKQzPSNUzBh9abp+6eEP4NsmMb
k9FMxPt8iDWhCmfZGg4JHn8XPx5cMe0ccH5bs84tugEaQh4dQU34O/lhFH7I7uYd
8TZGV68W3hE6rZKSCp+Po7qlIDWZ0txT6UlmqFXLhvknm9uNLSev9RKvry+YFWSV
NvO+uXMd1xEpQjm5PPgihYpcqnvjFZA+d+gZdOKTCaqUYQUrYufu71NKrFmU4hSr
Wp4jEI6FaWPOXemapDIU/tsAHG0hEKpNDGH6Tky009oIQv4PS2R7BB6Otb6fU1zC
dtCoTgYAufK/hyuZxmO7rRskasSKO1k/0SOxQy8A06LmJFMcmDuOGK1KIAO0NVzq
3FNhG9Ta+K86eJXx0my/vUfEezdKcdmoBVx+qSS15qkUC8J4O1aFyleyA8I+AAo2
toKrWWuaPnG+mFoGLevGtJdAUf7sHsv5SpPIVq4N4XwuxbfUEQlvU/xy0et5xzcH
c6NqEMNPotWHfqlnJ9upn81ADghggwop9WlryRB7D4LA1Lw9t2uZ6Onng6myELPp
tRzqX6N/uNBaGjrQYX3/
=gTNY
-----END PGP SIGNATURE-----

--Apple-Mail=_71DD5588-1791-45C9-BDF1-12F2B162C3EC--


From nobody Thu Feb 16 04:25:11 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDFA129ABB; Thu, 16 Feb 2017 04:25:10 -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 autolearn_force=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 M-_MLEy6ZGkE; Thu, 16 Feb 2017 04:25:08 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id A1028129AB8; Thu, 16 Feb 2017 04:25:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id F0E562CEB1; Thu, 16 Feb 2017 14:25:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mFfAbCOkf2kk; Thu, 16 Feb 2017 14:25:06 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 637782CCBA; Thu, 16 Feb 2017 14:25:06 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Re: [Gen-art] Review of draft-ietf-dmm-4283mnids-04
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 14:25:05 +0200
Message-Id: <9FDE8001-485B-47F9-A05A-831680693868@piuha.net>
References: <148589124578.6067.10086408452323670298.idtracker@ietfa.amsl.com>
To: Dale Worley <worley@ariadne.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gZyWPVzS5qGKXEk2KY9c0kl8Baw>
Cc: gen-art@ietf.org, ietf@ietf.org, draft-ietf-dmm-4283mnids.all@ietf.org, dmm@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:25:10 -0000

--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Dale:

Many thanks for this review, which indeed was exceptionally useful. =
(=93Super=94 as Charlie put it.)

I have placed a no-objection position for this document for tonight=92s =
IESG telechat. But I think your discussion on the details of changes =
inspired by Dale=92s review probably needs to continue, and I also see =
that there are other points made by my AD colleagues =97 that is another =
discussion that needs to finish.

Jari


--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D
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

iQIcBAEBCgAGBQJYpZoiAAoJEM80gCTQU46qfEUQAKmmOFzjI9bnDohcwkO+U1pa
JNE7yIB6O7gL233Mc5rIAXA6HzvuLLf0BEL3oxZMzKitl7gRdxiU+spANxgCr/Gx
WpMDNFtXMa1Mh2rET0m2bQNI7/sHTFg14RfeH7PQIcV3jtVXGGhd/Zwou328s3Oo
xyj5JNNuX83/FAdqiklk+DTdh80km1yagx3836MVnUaieYCBQrN0XD0odnuKrzRa
14n6Bb6hIsd4O2M3zntwqPM+UAsJVoTgaPmULQnnZ28eky/4ZnuRXYs8iCsaPjGR
0NLjjNqY4Av96qk076YiCB2c+BewRmlND9ZzquHGCpGjCBxAohX0G+8LokNB0rNs
YWyT4nvi8i9a/nopFBagf0kLl/eVf6mszObuxU+k1epIUuygzEzJAlPbvGRSuj/p
8+MkKHIbd+gq85fH4tTQYicjxkDLTNUWibJAHIfarFxexYhtEtkQ5tkg+t2fOKwD
rNy5+j/3iO+kz11Qv5ouOnu/pHCTKQpyLQTm7DRpNP/Nl96sX+dA/TA9HF2nlWF6
LPp2yr1D0rewYICb5kXXAgvWvey5eReuNUH/GKhQq2RALzpPWZesChiTHeBbMRYn
4P/E5oIhRSXO2Do6BOjakpdo/QJATdZlfRq5vCH3Ji+wcDfvAXWQ3RWu3CAl8KVv
Rm2RtfguzVwT/OWQK6lT
=R9VL
-----END PGP SIGNATURE-----

--Apple-Mail=_FBA5DC3F-7D37-4E73-B0E2-F91051675E0D--


From nobody Thu Feb 16 04:53:36 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23078129AD7 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 04:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 7RZC_SzOXhV7 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 04:53:33 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 BCB42129495 for <ietf@ietf.org>; Thu, 16 Feb 2017 04:53:32 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1GCrUbr018561 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:53:30 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7B296209BE3 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:53:30 +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 70519209CE5 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:53:30 +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 v1GCrULF029734 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:53:30 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <CAN-Dau30OuJ7_57302shrSOs8+sc6iaoDgV27umxb59uwb_pZQ@mail.gmail.com> <E780DEC3-F0E9-4A35-B3EA-8D6961775276@consulintel.es> <CAN-Dau24tGpEvFEjk7xdu9tyN30bYwB6GmVMQjtKHs8LYFAJMQ@mail.gmail.com> <2A163C6E-FFBE-4502-BC2F-0DE8DF88C081@consulintel.es> <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <a38f4189-9f3f-25e4-f407-d02db3064aa0@gmail.com>
Date: Thu, 16 Feb 2017 13:52:55 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau2Qv1dww_yxgw_SCx+zmVjXrctkPRoTK9i1x2--zHrxRg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f4CIHB-PkHByYB5atR7aehnPJso>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:53:35 -0000

Le 14/02/2017 à 20:18, David Farmer a écrit :
> So I hear you saying something like the following would be appropriate
> in your opinion;
>
> However, the Interface ID of all unicast addresses is required to be 64
> bit with the exception of the following; addresses for point-to-point
> links [RFC6164], Network-Specific Prefixes used for IPv4/IPv6
> Translators [RFC6052], and addresses that start with the binary value 000.

... and other manually configured one-to-one subnets on shared Ethernet, 
using arbitrary prefix lengths such as /56 and /60, as witnessed in some 
trials[*].

Alex
[*] details available upon request.

>
> While this is the less preferred approach as far as I'm concerned, I
> believe it resolves the issue I raised.
>
> Thanks.
>
> On Tue, Feb 14, 2017 at 10:07 AM, JORDI PALET MARTINEZ
> <jordi.palet@consulintel.es <mailto:jordi.palet@consulintel.es>> wrote:
>
>     I understand that, but those are two clear exceptions, no others
>     should be “allowed” by default.
>
>     Keeping the door open is not good in my opinion. Specific exceptions
>     must be taken in consideration one by one.
>
>     Regards,
>     Jordi
>
>
>     -----Mensaje original-----
>     De: ietf <ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org>> en
>     nombre de David Farmer <farmer@umn.edu <mailto:farmer@umn.edu>>
>     Responder a: <farmer@umn.edu <mailto:farmer@umn.edu>>
>     Fecha: martes, 14 de febrero de 2017, 17:03
>     Para: Jordi Palet Martinez <jordi.palet@consulintel.es
>     <mailto:jordi.palet@consulintel.es>>
>     CC: 6man WG <ipv6@ietf.org <mailto:ipv6@ietf.org>>,
>     <draft-ietf-6man-rfc4291bis@ietf.org
>     <mailto:draft-ietf-6man-rfc4291bis@ietf.org>>, IETF-Discussion
>     Discussion <ietf@ietf.org <mailto:ietf@ietf.org>>,
>     <6man-chairs@ietf.org <mailto:6man-chairs@ietf.org>>
>     Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP
>     Version 6 Addressing Architecture) to Internet Standard
>
>         The problem we want it to be 64 bits except when it's not
>     suppose to be, such as RFC6164 for point-to-point and RFC6052 for
>     IPv4/IPv6 translators with /96 Network-Specific Prefix.
>
>         On Tue, Feb 14, 2017 at 9:53 AM, JORDI PALET MARTINEZ
>     <jordi.palet@consulintel.es <mailto:jordi.palet@consulintel.es>> wrote:
>
>         Agree, we shouldn’t change that. Must be 64 bits.
>
>         Regards,
>         Jordi
>
>
>         -----Mensaje original-----
>         De: ietf <ietf-bounces@ietf.org <mailto:ietf-bounces@ietf.org>>
>     en nombre de David Farmer <farmer@umn.edu <mailto:farmer@umn.edu>>
>         Responder a: <farmer@umn.edu <mailto:farmer@umn.edu>>
>         Fecha: martes, 14 de febrero de 2017, 16:27
>         Para: Brian E Carpenter <brian.e.carpenter@gmail.com
>     <mailto:brian.e.carpenter@gmail.com>>
>         CC: <draft-ietf-6man-rfc4291bis@ietf.org
>     <mailto:draft-ietf-6man-rfc4291bis@ietf.org>>, <6man-chairs@ietf.org
>     <mailto:6man-chairs@ietf.org>>, 6man WG <ipv6@ietf.org
>     <mailto:ipv6@ietf.org>>, IETF-Discussion Discussion <ietf@ietf.org
>     <mailto:ietf@ietf.org>>
>         Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP
>     Version 6 Addressing Architecture) to Internet Standard
>
>             Actually, in addition to your text there still needs to be a
>     recommendation for 64 bit IIDs in all other cases.  64 bit IIDs
>     are(and should remain) the norm for IPv6, I do not want to change
>     that.  But the current language say IIDs are always 64 bit except
>     when an address begins with binary 000, leaving no room for any
>     other exception.  And this is plainly incorrect, I provided two
>     clear exceptions that are already standardized.  Furthermore, IIDs
>     other than 64 bits are in operational use, with manual configuration
>     and DHCPv6.
>             So I'd suggest;
>
>             However, the Interface ID of unicast addresses used for
>             Stateless Address Autoconfiguration [RFC4862] is required
>             to be 64 bits long, in all other cases it is recommended to
>             be 64 bits long.
>
>             The other option is to enumerate all the exceptions,
>     requiring the document to be updated every time a new exception is
>     standardized.
>
>             On Mon, Feb 13, 2017 at 4:53 PM, Brian E Carpenter
>     <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
>     wrote:
>
>             At an earlier stage I suggested restricting the applicability
>             of the "However..." sentence to SLAAC [RFC4862]. A short way
>             of doing this would be
>
>             However, the Interface ID of unicast addresses used for
>             Stateless Address Autoconfiguration [RFC4862] is required
>             to be 64 bits long.
>
>             Regards
>                Brian
>
>             On 14/02/2017 11:32, David Farmer wrote:
>             > I have concerns with the following text;
>             >
>             >    IPv6 unicast routing is based on prefixes of any valid
>     length up to
>             >    128 [BCP198].  For example, [RFC6164] standardises 127
>     bit prefixes
>             >    on inter-router point-to-point links. However, the
>     Interface ID of
>             >    all unicast addresses, except those that start with the
>     binary value
>             >    000, is required to be 64 bits long.  The rationale for
>     the 64 bit
>             >    boundary in IPv6 addresses can be found in [RFC7421]
>             >
>             > The third sentence seems to limit exceptions to 64 bit
>     IIDs to exclusively
>             > addresses that start with binary vale of 000.  There are
>     at least two other
>             > exceptions from standards track RFCs, that should be more
>     clear accounted
>             > for in this text.  First is [RFC6164] point-to-point
>     links, as mentioned in
>             > the previous sentence.  I think the clear intent of
>     [RFC6164] is to allow
>             > one(1) Bit IIDs for point to point-to-point links using
>     any Global Unicast
>             > Address, not just those that start with 000.  Second is,
>     [RFC6052], which
>             > updates [RFC4921] and seems to allow 32 bit IIDs or /96
>     prefixes for any
>             > Global Unicast Address when used for IPv4/IPv6
>     translation, referred to as
>             > ""Network-Specific Prefix" unique to the organization
>     deploying the address
>             > translators," in section 2.2 of [RFC6052].
>             >
>             > Thanks.
>             >
>             > On Wed, Feb 1, 2017 at 5:51 PM, The IESG
>     <iesg-secretary@ietf.org <mailto:iesg-secretary@ietf.org>> wrote:
>             >
>             >>
>             >> The IESG has received a request from the IPv6 Maintenance
>     WG (6man) to
>             >> consider the following document:
>             >> - 'IP Version 6 Addressing Architecture'
>             >>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>             >>
>             >> The IESG plans to make a decision in the next few weeks,
>     and solicits
>             >> final comments on this action. Please send substantive
>     comments to the
>             >> ietf@ietf.org <mailto:ietf@ietf.org> mailing lists by
>     2017-03-01. Exceptionally, comments may be
>             >> sent to iesg@ietf.org <mailto:iesg@ietf.org> instead. In
>     either case, please retain the
>             >> beginning of the Subject line to allow automated sorting.
>             >>
>             >> Abstract
>             >>
>             >>
>             >>    This specification defines the addressing architecture
>     of the IP
>             >>    Version 6 (IPv6) protocol.  The document includes the
>     IPv6 addressing
>             >>    model, text representations of IPv6 addresses,
>     definition of IPv6
>             >>    unicast addresses, anycast addresses, and multicast
>     addresses, and an
>             >>    IPv6 node's required addresses.
>             >>
>             >>    This document obsoletes RFC 4291, "IP Version 6 Addressing
>             >>    Architecture".
>             >>
>             >>
>             >>
>             >>
>             >> The file can be obtained via
>             >>
>     https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/
>     <https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/>
>             >>
>             >> IESG discussion can be tracked via
>             >>
>     https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/
>     <https://datatracker.ietf.org/doc/draft-ietf-6man-rfc4291bis/ballot/>
>             >>
>             >>
>             >> No IPR declarations have been submitted directly on this I-D.
>             >>
>             >>
>             >>
>             >>
>             >>
>     --------------------------------------------------------------------
>             >> 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 <mailto:ipv6@ietf.org>
>             > Administrative Requests:
>     https://www.ietf.org/mailman/listinfo/ipv6
>     <https://www.ietf.org/mailman/listinfo/ipv6>
>             >
>     --------------------------------------------------------------------
>             >
>
>
>
>
>
>
>             --
>             ===============================================
>             David Farmer               Email:farmer@umn.edu
>     <mailto:Email%3Afarmer@umn.edu> <mailto:Email%3Afarmer@umn.edu
>     <mailto:Email%253Afarmer@umn.edu>> <mailto:Email%3Afarmer@umn.edu
>     <mailto:Email%253Afarmer@umn.edu> <mailto:Email%253Afarmer@umn.edu
>     <mailto:Email%25253Afarmer@umn.edu>>>
>             Networking & Telecommunication Services
>             Office of Information Technology
>             University of Minnesota
>             2218 University Ave SE        Phone: 612-626-0815
>     <tel:612-626-0815> <tel:612-626-0815 <tel:612-626-0815>>
>             Minneapolis, MN 55414-3029   Cell: 612-812-9952
>     <tel:612-812-9952> <tel:612-812-9952 <tel:612-812-9952>>
>             ===============================================
>
>
>
>
>
>
>
>         **********************************************
>         IPv4 is over
>         Are you ready for the new Internet ?
>         http://www.consulintel.es
>         The IPv6 Company
>
>         This electronic message contains information which may be
>     privileged or confidential. The information is intended to be for
>     the use of the individual(s) named above. If you are not the
>     intended recipient be aware that any disclosure, copying,
>     distribution or use of the contents of this information, including
>     attached files, is prohibited.
>
>
>
>
>
>
>
>
>
>         --
>         ===============================================
>         David Farmer               Email:farmer@umn.edu
>     <mailto:Email%3Afarmer@umn.edu> <mailto:Email%3Afarmer@umn.edu
>     <mailto:Email%253Afarmer@umn.edu>>
>         Networking & Telecommunication Services
>         Office of Information Technology
>         University of Minnesota
>         2218 University Ave SE        Phone: 612-626-0815 <tel:612-626-0815>
>         Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:612-812-9952>
>         ===============================================
>
>
>
>
>
>
>     **********************************************
>     IPv4 is over
>     Are you ready for the new Internet ?
>     http://www.consulintel.es
>     The IPv6 Company
>
>     This electronic message contains information which may be privileged
>     or confidential. The information is intended to be for the use of
>     the individual(s) named above. If you are not the intended recipient
>     be aware that any disclosure, copying, distribution or use of the
>     contents of this information, including attached files, is prohibited.
>
>
>
>
>
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> <mailto:Email%3Afarmer@umn.edu>
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815 <tel:(612)%20626-0815>
> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:(612)%20812-9952>
> ===============================================


From nobody Thu Feb 16 04:55:17 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA3C129495 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 04:55:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 EroNcgT37jf0 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 04:55: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 6298E12959B for <ietf@ietf.org>; Thu, 16 Feb 2017 04:55:14 -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 v1GCtBw8031551 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:55:11 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B494E2048A4 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:55:11 +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 A2110204857 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:55:11 +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 v1GCtBJA030765 for <ietf@ietf.org>; Thu, 16 Feb 2017 13:55:11 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6026d226-cdd1-e801-4bfa-5892a9c6e202@gmail.com>
Date: Thu, 16 Feb 2017 13:54:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wISg6amhlFWzWE7wqpDbF4QrnM8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 12:55:16 -0000

Le 15/02/2017 à 02:31, Brian E Carpenter a écrit :
> On 15/02/2017 14:26, Lorenzo Colitti wrote:
>> On Tue, Feb 14, 2017 at 11:06 AM, <otroan@employees.org> wrote:
>>
>>> Brian, changing the 64 bit boundary is such a big change that I would
>>> claim it is far outside the scope of advancing 4291 to Internet standard.
>>>
>>
>> Agreed.
>
> Of course. The point is only that it's a parameter in the design of SLAAC,
> whose value is set by the address architecture.

Can there be another IPv6 Architecture?

Alex

>
>    Brian
>
>


From nobody Thu Feb 16 05:19:41 2017
Return-Path: <acmorton@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7231295A7; Thu, 16 Feb 2017 05:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level: 
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 J5BUt3m1O0-2; Thu, 16 Feb 2017 05:19:39 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 395D6129481; Thu, 16 Feb 2017 05:19:36 -0800 (PST)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v1GDFJ9C018832; Thu, 16 Feb 2017 08:19:35 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 28nax6t0dy-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 08:19:35 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDJYng004856; Thu, 16 Feb 2017 08:19:34 -0500
Received: from mlpi408.sfdc.sbc.com (mlpi408.sfdc.sbc.com [130.9.128.240]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDJRQ7004726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Feb 2017 08:19:30 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Thu, 16 Feb 2017 13:19:20 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDJJXq001018; Thu, 16 Feb 2017 07:19:20 -0600
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.178.11]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDJFaW000859; Thu, 16 Feb 2017 07:19:15 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-blue.research.att.com (Postfix) with ESMTP id 5089CEF831; Thu, 16 Feb 2017 08:19:15 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Thu, 16 Feb 2017 08:19:15 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Joel Halpern <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: Review of draft-ietf-bmwg-virtual-net-04
Thread-Topic: Review of draft-ietf-bmwg-virtual-net-04
Thread-Index: AQHSf/jwpPG7afFfS0SRwGrkrzC5RaFrpodQ
Date: Thu, 16 Feb 2017 13:19:13 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF68BF69@njmtexg5.research.att.com>
References: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
In-Reply-To: <148633102421.31577.5350933097680027453.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.246.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160131
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g77WrD_-yOnq0vWNF2ZnruKzzTU>
Cc: "draft-ietf-bmwg-virtual-net.all@ietf.org" <draft-ietf-bmwg-virtual-net.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:19:40 -0000

SGkgSm9lbCwNClRoYW5rcyBmb3IgeW91ciByZXZpZXcsIHBsZWFzZSBzZWUgYmVsb3cuDQpBbA0K
DQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEpvZWwgSGFscGVybiBbbWFp
bHRvOmptaEBqb2VsaGFscGVybi5jb21dDQo+IFNlbnQ6IFN1bmRheSwgRmVicnVhcnkgMDUsIDIw
MTcgNDo0NCBQTQ0KPiBUbzogZ2VuLWFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1ibXdn
LXZpcnR1YWwtbmV0LmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4gYm13Z0BpZXRmLm9y
Zw0KPiBTdWJqZWN0OiBSZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA0DQo+
IA0KPiBSZXZpZXdlcjogSm9lbCBIYWxwZXJuDQo+IFJldmlldyByZXN1bHQ6IFJlYWR5DQo+IA0K
Li4uDQo+IERvY3VtZW50OiBkcmFmdC1pZXRmLWJtd2ctdmlydHVhbC1uZXQtPz8NCj4gUmV2aWV3
ZXI6IEpvZWwgSGFscGVybg0KPiBSZXZpZXcgRGF0ZTogMjAxNy0wMi0wNQ0KPiBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTAyLTE1DQo+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBm
b3IgYSB0ZWxlY2hhdA0KPiANCj4gU3VtbWFyeTogVGhpcyBkb2N1bWVudCBpcyByZWFkeSBmb3Ig
cHVibGljYXRpb24gYXMgYW4gSW5mb3JtYXRpb25hbA0KPiBSRkMuDQo+IA0KPiBNYWpvciBpc3N1
ZXM6DQo+IA0KPiBNaW5vciBpc3N1ZXM6DQo+ICAgICBUaGUgc2Vjb25kIGZpZ3VyZSBpbiBzZWN0
aW9uIDQuNCB0YWxrcyBhYm91dCB0aGUgdXNlIG9mIG11bHRpcGxlDQo+IDN4MyB0YWJsZXMsIGJ1
dCBhcHBlYXJzIHRvIHNob3cgdGhlIHVzZSBvZiBtdWx0aXBsZSA0eDQgdGFibGVzLiAgVGhpcw0K
PiByZWFkZXIgZm91bmQgaGltc2VsZiBjb25mdXNlZC4NCg0KW0FDTV0gDQpUaGUgIjN4MyBtYXRy
aXgiIHJlZmVycyB0byB0aGUgY2VsbHMgb2YgdGhlIHRhYmxlIHdoZXJlIA0KdXNlciBlbnRyaWVz
IGFwcGVhci4gVGhlIEhlYWRlciBSb3cgYW5kIEhlYWRlciBDb2x1bW4NCmFyZW4ndCBpbmNsdWRl
ZCBpbiB0aGUgM3gzIG1hdHJpeCwgYnV0IHRoZXkgZG8gbWFrZSB0aGUgDQp0YWJsZSBhcHBlYXIg
YXMgNHg0LCBhcyBpbiB0aGUgZmlyc3QgZmlndXJlIG9mIHNlYzQuNC4gDQpUaGUgSGVhZGluZ3Mg
ZGlzYXBwZWFyIGluIHRoZSBzZWNvbmQgZmlndXJlIA0KKGR1ZSB0byBzaXplIGNvbnN0cmFpbnRz
KSwgYnV0IHRoZSB0YWJsZXMgaW5jbHVkZQ0KdGhlIDN4MyBtYXRyaXggYXMgYmVmb3JlLg0KDQoN
Cj4gDQo+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPiANCg0K


From nobody Thu Feb 16 05:21:48 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F5F1129468 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 05:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level: 
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhLocG6OtXPq for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 05:21:44 -0800 (PST)
Received: from mx144.netapp.com (mx144.netapp.com [216.240.21.25]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D44B8127735 for <ietf@ietf.org>; Thu, 16 Feb 2017 05:21:44 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,169,1484035200";  d="asc'?scan'208";a="177195008"
Received: from vmwexchts02-prd.hq.netapp.com ([10.122.105.23]) by mx144-out.netapp.com with ESMTP; 16 Feb 2017 05:12:35 -0800
Received: from VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) by VMWEXCHTS02-PRD.hq.netapp.com (10.122.105.23) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 16 Feb 2017 05:21:17 -0800
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS04-PRD.hq.netapp.com (10.122.105.20) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Thu, 16 Feb 2017 05:21:18 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ic6FFYJMhhATS3XjvZ3KjPGUNBX4ZxOsvPqGLwrvNao=; b=BKCWGjFfRp33aHxceqInkcANTYLydAI7xiED0Y5Qt1wTo5Gih7K5WDtmVUUGS4i5LkOBqw/ce0JXOQc/ZNPWfBmP6ulOp2/rzMPflpHDv9FouQQVQvblyd/6guwMVYsmw+n5MriLl0XUWnb4HPrnWfX+aH2wqxMlE7cmZNLhdFI=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1156.namprd06.prod.outlook.com (10.160.157.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Thu, 16 Feb 2017 13:21:17 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0888.034; Thu, 16 Feb 2017 13:21:17 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com>
Subject: Re: Internet Research Labs Draft
Thread-Topic: Internet Research Labs Draft
Thread-Index: AQHSh6ja4D9+mydB3Umi2m5w/ObCPaFrN6ObgABoJQA=
Date: Thu, 16 Feb 2017 13:21:17 +0000
Message-ID: <83CA4A51-EFEA-4CA2-AF56-A01227B4CC43@netapp.com>
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com> <1302911527.6950973.1487176178877@mail.yahoo.com> <081BECEC-CB75-43C6-B522-B1B7E227E4B3@netapp.com>
In-Reply-To: <081BECEC-CB75-43C6-B522-B1B7E227E4B3@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: af8750b3-64c5-430c-b4ec-08d4566eb0be
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1156; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1156; 7:2j+iF2TEP8ZvhiC3kyGeJ5qJPeR+glE6vjDRYwFjcocgpdDk4nj+5Pmfg8gZRtsrW6lfRa1As2C0EWDqs1PWm16LM9rtr6QC8xUDtLzZxbaGzjJv4m1iO1noSdQb0mkQw3sfDtb7uJCg6YXwVSACoanZGSwSDrFASSG22WhHF7ShvMFA88DNiIW3hmbV+q9ay1s8NkKf+X3Y/OHkeOZ9Ch6Udq7jNuz57NJ7KKW4T04BZaWikIdiVTGFPVDtOh+xU+DTz8wo5tWmAJ8Uzk9B/2msFlLHYoRoTpAR7zf5iosq1PQECfJI6JLhk5kKxwy9HxGdf0/T+nMUXq0l4S2vjg==
x-microsoft-antispam-prvs: <BN3PR0601MB11562ADF739DD8E6EDCD1844A75A0@BN3PR0601MB1156.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123555025)(20161123560025)(20161123558025)(20161123564025)(20161123562025)(6072148); SRVR:BN3PR0601MB1156; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1156; 
x-forefront-prvs: 0220D4B98D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(189002)(199003)(24454002)(377424004)(15974865002)(101416001)(92566002)(6506006)(3280700002)(68736007)(82746002)(106116001)(77096006)(105586002)(6486002)(6116002)(3846002)(83716003)(106356001)(66066001)(54906002)(102836003)(2900100001)(389900003)(7736002)(6306002)(4326007)(4001150100001)(2906002)(97736004)(189998001)(99286003)(86362001)(57306001)(81156014)(8676002)(81166006)(6436002)(305945005)(6512007)(2351001)(99936001)(5640700003)(76176999)(25786008)(3480700004)(53546003)(50986999)(6246003)(5660300001)(122556002)(2501003)(110136004)(38730400002)(50226002)(3660700001)(8936002)(229853002)(53936002)(6916009)(2950100002)(36756003)(33656002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1156; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_6E276009-BB81-4CCA-A74A-6EB37066F26F"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2017 13:21:17.6980 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1156
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G-3rqBpnqHBl7m533SX1O-MkmrY>
Cc: Harish Chowdhary <harish@nixi.in>, IETF Discussion List <ietf@ietf.org>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:21:46 -0000

--Apple-Mail=_6E276009-BB81-4CCA-A74A-6EB37066F26F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-16, at 8:08, Eggert, Lars <lars@netapp.com> wrote:
> How is this different from codestand?

As in https://codestand.ietf.org/codestand/

On Feb 15, 2017, at 17:30, "nalini.elkins@insidethestack.com" =
<nalini.elkins@insidethestack.com> wrote:
>> All,
>>=20
>> If anyone is interested, we have just done an I-D for a proposed =
concept for "Internet Labs".   We hope this will be of interest.
>>=20
>> https://tools.ietf.org/html/draft-chowbat-irl-00
>>=20
>> The abstract is here:
>>=20
>> Many people learn technical concepts best in a hands-on environment,
>> and Internet protocols and standards are no exception. Internet
>> Research Labs (IRL) will facilitate a platform and encourage the
>> technical community (seasoned professionals and newcomers alike) to
>> discuss, collaborate, design and develop utilities, ideas, sample
>> code and solutions that show practical implementations (Proof of
>> Concept) of existing IETF standards. These labs may also be used by
>> the IETF Mentoring Program and/or EDU teams for hands-on training to
>> mentees or newcomers. This base draft intends to provide a high-level
>> overview of the concept of Internet Research Labs in terms of
>> objectives, requirements, challenges and deliverables without going
>> into details of a specific lab, technology or an IETF Working Group
>> (WG). After this draft matures and gains traction within the IETF
>> community, we foresee more and more Internet drafts for the specific
>> labs.
>>=20
>> Thanks,
>>=20
>> Nalini Elkins
>> Inside Products, Inc.
>> www.insidethestack.com
>> (831) 659-8360
>>=20
>=20


--Apple-Mail=_6E276009-BB81-4CCA-A74A-6EB37066F26F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYpadMAAoJEFS1wwm/cMFXR3gQALM6Ib3ezjY1LELyIiRcfVBH
uenZZpSzStYhY/Hot3vD0P/WT8Ha6SKe+34Vu+JDMv17u4T2MF6Q22lQ4kgTV3TW
Y6I7L961rfyxt/r7OlKPk56PS0HzJMdo1TDZW8UpTlyH37lUbF1pxEDTGGNmbUCQ
gaWnrq5o5c22C8TRkO+TerXDxnDXnxIDRnV8aZQYPG32iZ9gBOsAZFbsFKyCFth1
UBVQI9Cauo7V9vNAV5F0ZU4PJOKCYH6NY1PzhnijjCZLjN8DwJoeebUu/qHFzYDM
fvh9oJXnkYb/XO0h2dtCpEmolle7FrlsSSEiiWTYxaWx1JT/ZDSaBzwglXgEfunO
xMRsfLdrsekeVKlBWWFYlizxwDsqz0NhWNAvyiCWePuh39G36vB5FqPsNThBKZpL
a2C4LLlgPSKN1s1N3Wyw5UARBq/bcnKDtKXJcdNN6ehaQAN2fbFr8f8eMvMLNVi9
TFV53PPdA2pAvZmuJ4lTeTXsgBTnoNGKEQjxdZR/Hl6UmLFvpXElOCks7TZkzCAp
fIo3X6vyJf5e9QYAO3Lf2ig8iluaerKGBKUwH8qD1ULCNdoSIXGcu9thtvG7qZDq
VwwotR4KHJANT+bRFatLZDzKu6KbzU4Th6MrGLXMl2ffL4o9+xWSQqILT7NEvs2S
yr5xhVIL43OEY5KWhM6A
=pAq8
-----END PGP SIGNATURE-----

--Apple-Mail=_6E276009-BB81-4CCA-A74A-6EB37066F26F--


From nobody Thu Feb 16 05:25:37 2017
Return-Path: <acmorton@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7F91295C9; Thu, 16 Feb 2017 05:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 DW3ZDfp4a0kF; Thu, 16 Feb 2017 05:25:30 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) (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 DBD39129465; Thu, 16 Feb 2017 05:25:30 -0800 (PST)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id v1GDPSTu025932; Thu, 16 Feb 2017 08:25:30 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by mx0a-00191d01.pphosted.com with ESMTP id 28n2b69c33-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 16 Feb 2017 08:25:30 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDPSC9010131; Thu, 16 Feb 2017 08:25:28 -0500
Received: from mlpi407.sfdc.sbc.com (mlpi407.sfdc.sbc.com [130.9.128.239]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id v1GDPFXt009949 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Feb 2017 08:25:20 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by mlpi407.sfdc.sbc.com (RSA Interceptor); Thu, 16 Feb 2017 13:25:00 GMT
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDP0nS026663; Thu, 16 Feb 2017 07:25:00 -0600
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v1GDOp18026144; Thu, 16 Feb 2017 07:24:52 -0600
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-green.research.att.com (Postfix) with ESMTP id F3168E23AD; Thu, 16 Feb 2017 08:24:47 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Thu, 16 Feb 2017 08:24:51 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Jouni Korhonen <jounikor@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
Subject: RE: Review of draft-ietf-bmwg-virtual-net-04
Thread-Topic: Review of draft-ietf-bmwg-virtual-net-04
Thread-Index: AQHSh8dMy+22VXSnpEu6fE2ECw+4/aFrn1dA
Date: Thu, 16 Feb 2017 13:24:50 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF68BF88@njmtexg5.research.att.com>
References: <148718931072.31507.17292789125260012486.idtracker@ietfa.amsl.com>
In-Reply-To: <148718931072.31507.17292789125260012486.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.10.246.211]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-16_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702160132
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jXn68zCuUZxisRqZS9rmvjc6rsc>
Cc: "draft-ietf-bmwg-virtual-net.all@ietf.org" <draft-ietf-bmwg-virtual-net.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:25:32 -0000

VGhhbmtzIGZvciB5b3VyIHJldmlldywgSm91bmkhDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdl
LS0tLS0NCj4gRnJvbTogSm91bmkgS29yaG9uZW4gW21haWx0bzpqb3VuaWtvckBnbWFpbC5jb21d
DQo+IFNlbnQ6IFdlZG5lc2RheSwgRmVicnVhcnkgMTUsIDIwMTcgMzowOSBQTQ0KPiBUbzogb3Bz
LWRpckBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LmFsbEBpZXRm
Lm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4gYm13Z0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZXZpZXcg
b2YgZHJhZnQtaWV0Zi1ibXdnLXZpcnR1YWwtbmV0LTA0DQo+IA0KPiBSZXZpZXdlcjogSm91bmkg
S29yaG9uZW4NCj4gUmV2aWV3IHJlc3VsdDogUmVhZHkNCj4gDQo+IFRoaXMgZG9jdW1lbnQgd2Fz
IGdvb2QgaW5mb3JtYXRpb25hbCByZWFkLiBObyBjb21wbGFpbnRzLg0KPiANCj4gVHdvIGVkaXRv
cmlhbHM6DQo+IA0KPiBMaW5lICAzMzg6ICIuLi5wb3NzaWJpbGl0eSBvZiBiZW5jaG1hcmsgY3Vy
YXRpb24gZHVyaW5nIGRldmVsb3BtZW50IG9mDQo+IG5ldy4uLiINCj4gICBJcyBpdCBjdXJhdGlv
biBvciBjcmVhdGlvbj8NCltBQ01dIA0KY3VyYXRpb24sIG1lYW5pbmcgdGhhdCB3ZSdsbCByZXZp
ZXcgb3VyIGJlbmNobWFya3MgYW5kDQpwb3NzaWJseSByZXZpc2UgdGhlbSBhcyB3ZSBkZXZlbG9w
IG5ldyBtZXRob2RzIG9mIG1lYXN1cmVtZW50Lg0KDQo+IA0KPiBMaW5lIDQwOTogIi4uVk5GLCBv
ciBzb21ldGhpbmcgYXMgc2ltcGxlIGFzIGEgbmV3IHBvaWN5IHRvIGltcGxlbWVudA0KPiBpbiBh
IFZORiwgLi4iDQo+ICAgcy9wb2ljeS9wb2xpY3kNCj4gDQpbQUNNXSANCnRoYW5rcyBmb3IgY2F0
Y2hpbmcgdGhhdCwNCkFsDQoNCg0K


From nobody Thu Feb 16 05:43:32 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 488301294B6 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 05:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zfTFItDB02Nh for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 05:43:30 -0800 (PST)
Received: from nm4-vm7.bullet.mail.gq1.yahoo.com (nm4-vm7.bullet.mail.gq1.yahoo.com [98.136.218.166]) (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 17A1F1293E8 for <ietf@ietf.org>; Thu, 16 Feb 2017 05:43:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487252609; bh=aPswhjcKXTN9jz6sCeHKM/J+jNvAnoUA4Ioyomw2ZF0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=i5nA4FhDeFRZeWtJTdpWpYV42QRi8nxJUK6iQoJR2TYfvZEojbhPOQItQ3oDgunzV4RjqSW4HPHv/miyEQJFVn2AjWCsHA3Yo9HEPjsstv58appxdRNv7p3qHgeTsmGe2024/ku8Bj168aVr2ffIKhrFDcWqIw58HVoJzOLwcOwFpytOeqFuOfWKhwHB6diJuiCcmCnZcx9fvSiGRyASfHaoUDAo9nKcXYxSWY691umjtFWlTzwtK87nOTAiVg7+wug/mKWkCcuO7E6SDE29I6E6DIdyq6ei08TJeHEGZt1uhSOTkkaFKzxtZZjmjFN/8mxA9MWS2PRm3DtQmj8tGw==
Received: from [98.137.12.61] by nm4.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 13:43:29 -0000
Received: from [98.137.12.203] by tm6.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 13:43:29 -0000
Received: from [127.0.0.1] by omp1011.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 13:43:29 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 610786.30083.bm@omp1011.mail.gq1.yahoo.com
X-YMail-OSG: uZn6.J0VM1m0na5AJCtAYUyfgdpfxDAwTDKnM5SJH96f_eQOTtrIRgblkCwIJu2 RyCckANaVPkJRru2lqOKeQmWHn44X_EF2zkPKqvBEVLH1jyq4TkXjqwAnUK9xctOwn2cOJ0Dfaf3 A5uatUXx5wVxKsWWvHiGUQRsXzvtrIDo4vFLb9PPx5oxePF7iwXWAgqJcPzPlKyjFhvSBR0CK9br besVVGSKyv1xmxFaSLwGOgNqsSq1lW4gA7PEmgqSIE26wWrSIbkQK7PxD5AtPW8BNmmkZTolM3n4 d3gRvs_7AL89lbx6byiwIx0qjpcj9fU..J_o5boVOW6RH57i1viS.XlBwmnnDnESxjNIThcocE_Z ppZN3YrOtpxIhSN3QnfPcYjvQWNZXi9uoFzV18tWII7tZXMkIHVM75nh7YdYqjLOdrNaYQEfIHgJ EZFa24iRGWgZu95D.Zvz7g7yJY39xyNskm5dTYQMwZB72mMNwdtA8zxj4ER2uQzrHULWRAQa687p WQYta4PW1tBTA2QJgNgsbAlgZUJbkZep_28ErcoFuHWKxP8uNikDmjFBx.ipxtEL8qqR229L4grr X3qOptjn7
Received: from jws300057.mail.gq1.yahoo.com by sendmailws104.mail.gq1.yahoo.com; Thu, 16 Feb 2017 13:43:29 +0000; 1487252609.258
Date: Thu, 16 Feb 2017 13:43:17 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: "Eggert, Lars" <lars@netapp.com>
Message-ID: <14333220.701898.1487252597106@mail.yahoo.com>
In-Reply-To: <83CA4A51-EFEA-4CA2-AF56-A01227B4CC43@netapp.com>
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com> <1302911527.6950973.1487176178877@mail.yahoo.com> <081BECEC-CB75-43C6-B522-B1B7E227E4B3@netapp.com> <83CA4A51-EFEA-4CA2-AF56-A01227B4CC43@netapp.com>
Subject: Re: Internet Research Labs Draft
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uuEU-dGQD8mMZG7kuTZvuoH1EPQ>
Cc: Harish Chowdhary <harish@nixi.in>, IETF Discussion List <ietf@ietf.org>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 13:43:31 -0000

On 2017-2-16, at 8:08, Eggert, Lars <lars@netapp.com> wrote:
>> How is this different from codestand?

>As in https://codestand.ietf.org/codestand/


Lars,  I believe this is what started as the CodeMatch project.   We definitely want to work with them to showcase the work they have done.   But, my understanding of CodeStand was that it was a "dating service" to match people who wanted code done with people who wanted to do code.

Our concept is a bit different.  The idea is that if you want to see, for example, how TLS1.3 looks like without having to do all the implementation yourself, you can use one of the Internet Labs and be guided through.  Everything you need will be installed, including Wireshark, or another network analysis tool.

Does that make sense?

Nalini



On Feb 15, 2017, at 17:30, "nalini.elkins@insidethestack.com" <nalini.elkins@insidethestack.com> wrote:
>> All,
>> 
>> If anyone is interested, we have just done an I-D for a proposed concept for "Internet Labs".   We hope this will be of interest.
>> 
>> https://tools.ietf.org/html/draft-chowbat-irl-00
>> 
>> The abstract is here:
>> 
>> Many people learn technical concepts best in a hands-on environment,
>> and Internet protocols and standards are no exception. Internet
>> Research Labs (IRL) will facilitate a platform and encourage the
>> technical community (seasoned professionals and newcomers alike) to
>> discuss, collaborate, design and develop utilities, ideas, sample
>> code and solutions that show practical implementations (Proof of
>> Concept) of existing IETF standards. These labs may also be used by
>> the IETF Mentoring Program and/or EDU teams for hands-on training to
>> mentees or newcomers. This base draft intends to provide a high-level
>> overview of the concept of Internet Research Labs in terms of
>> objectives, requirements, challenges and deliverables without going
>> into details of a specific lab, technology or an IETF Working Group
>> (WG). After this draft matures and gains traction within the IETF
>> community, we foresee more and more Internet drafts for the specific
>> labs.
>> 
>> Thanks,
>> 
>> Nalini Elkins
>> Inside Products, Inc.
>> www.insidethestack.com
>> (831) 659-8360
>> 
> 


From nobody Thu Feb 16 06:04:48 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCD161295F9; Thu, 16 Feb 2017 06:04:33 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 iZZZls4XwHuD; Thu, 16 Feb 2017 06:04:32 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 056501295E3; Thu, 16 Feb 2017 06:04:32 -0800 (PST)
Received: from dhcp-207-155.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:b82b:6073:afb4:ddb0]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 701411B00055; Thu, 16 Feb 2017 16:02:18 +0000 (GMT)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <196e8c39-784a-3a25-b6ab-d7eaa664f0fa@isi.edu>
To: Joe Touch <touch@isi.edu>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683.
Message-ID: <8fbc3cbd-ff2d-f2c6-ccd7-13a20c6aa5ca@erg.abdn.ac.uk>
Date: Thu, 16 Feb 2017 14:04:28 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <196e8c39-784a-3a25-b6ab-d7eaa664f0fa@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i1kaKGBXkk2TeqyYgvNi-YZ6tw0>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 14:04:34 -0000

On 15/02/2017 21:25, Joe Touch wrote:
> Hi, Gorry (et al.),
>
> On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
>> There is no mention that paths including tunnels can eat ICMPv6 PTB
>> messages on the tunnel segment, blackholing them, which prevents
>> reaching the destination.
>
> Nor should there be, IMO.
>
> A tunnel is a link layer to the network whose packets it transits.
>
> ICMPs generated inside a tunnel aren't "eaten", so much as they operate
> at a different layer for a different reason (e.g., to tune
> ingress-egress source fragmentation of encapsulated packets).
>
> PTB messages inside a tunnel are (IMO) most correctly interpreted by the
> ingress (which is an *interface* on a router or host, most correctly
> IMO) as changing the MTU of the tunnel as a link. If that MTU change
> affects packets that arrive later, then it would be the router where the
> ingress is attached that would generate the ICMP, never the (ingress)
> interface whose MTU is insufficient.
>
> Again, I'm in the process of updating draft-ietf-intarea-tunnels to be
> much more clear on this point (the update should be issued in a day or two).
>
> Joe
>

I really disagree Joe - not in what you say about how things need to be, 
nor the relevance of draft-ietf-intarea-tunnels.

The point of disagreement, is that I think the text needs to explain 
enough that people do NOT blindly believe this always works. the current 
text mentions tunnels in more than one place, as if they are just 
another usage of PMTUD.

Tunnels can make path MTU diiscovery unreliable, because many deployed 
tunnel ingresses do not propagate ICMPv6 PTB messages upstream to 
reflect the limits of the Tunnel MTU. draft-ietf-intarea-tunnels 
discusses how a tunnel should be implemented to effectively work with a 
Tunnel MTU.

Gorry


From nobody Thu Feb 16 06:08:41 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC3431299D7; Thu, 16 Feb 2017 06:08:39 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 nmP7_RlAtJoB; Thu, 16 Feb 2017 06:08:38 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id BD0B81299BB; Thu, 16 Feb 2017 06:08:38 -0800 (PST)
Received: from dhcp-207-155.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:b82b:6073:afb4:ddb0]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 05FDF1B00055; Thu, 16 Feb 2017 16:06:28 +0000 (GMT)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu>
To: Joe Touch <touch@isi.edu>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683.
Message-ID: <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk>
Date: Thu, 16 Feb 2017 14:08:37 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/haI5XjT7u3DrMVp_0cImM43ycb0>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 14:08:40 -0000

The text below is not about tunnels - this is about  the operation of 
transport, and the quoted text is from the new UDP Guidelines ID.

On 15/02/2017 21:26, Joe Touch wrote:
> Hi, Gorry (et al.),
>
> Again, the following text should not drift into discussing how tunnels
> are handled IMO. That should be addressed in a different document (and I
> don't think it's troublesome at all if viewed correctly).
>
> Joe
>
>
> On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
>> - Introduces a significant vulnerability.  A rogue PTB message that
>> reduces the PMTU to a minimum, can result in a path too small to carry
>> an encapsulated packet. (Recently noted by Fernando Gont).
>>
>> Moreover, other layers view ICMP messages with suspicion and have long
>> noted the need to check ICMP payload and match only packets that
>> relate to actual 5-tuples in use (effectively reducing vulnerability
>> to off-path attacks). For example, the Guidelines for UDP, rfc5405bis,
>> state:
>>
>> " Applications SHOULD appropriately validate the payload of ICMP
>>    messages to ensure these are received in response to transmitted
>>    traffic (i.e., a reported error condition that corresponds to a UDP
>>    datagram actually sent by the application). …“

The comment below could easily be handled by something that clearly 
indicates the problem and points to the tunnel draft for guidance, I 
agree no need to go into algorithms/methods here.

>> - clearly handling this in IP-layer tunnels can be troublesome, but
>> that's a problem that should be described, not obscured.
>

Gorry


From nobody Thu Feb 16 06:22:23 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43DDB1294AD for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 06:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibXNSbfVMGBI for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 06:22:20 -0800 (PST)
Received: from nm3-vm6.bullet.mail.gq1.yahoo.com (nm3-vm6.bullet.mail.gq1.yahoo.com [98.136.218.149]) (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 9D2A9126BF7 for <ietf@ietf.org>; Thu, 16 Feb 2017 06:22:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1487254940; bh=xdnZZL7CjH8sQyBuXRgYsR9bL2ZXYktUdLL58Pt/4Lc=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=tGOJbFDHSsvb7Gb8zydsjSKPYPmBOgQgIuP4NPCpemFjA6jqbwEGod5zPEt/m877Q3cDTKrwFLTacm8PnVL6tPfnwJIPLgKNE7IVJZUgjDydRx2DyvARxmFAQ0F7BFZrHcQgP6BgUaGqWQmhuvFduc7+HQhXkIILl+w1VxNs2dD9S7y487NsLofZszs9wo2/zvif8XqkdI05S4jyLHq/7FMS8P6oaoRMHdct6E9+/Ik+cF/t0lLeju8r58fqY2OAdripX39d3SzbSWqhkJuXVdPPiV2XzEcfKxeepF9U0YkefyLdSUwJETpTI98wJv54T1dtnJ6lMI5S73E18wGkfA==
Received: from [98.137.12.62] by nm3.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 14:22:20 -0000
Received: from [98.137.12.195] by tm7.bullet.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 14:22:20 -0000
Received: from [127.0.0.1] by omp1003.mail.gq1.yahoo.com with NNFMP; 16 Feb 2017 14:22:20 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 142779.1957.bm@omp1003.mail.gq1.yahoo.com
X-YMail-OSG: Jw.7fpgVM1ntBtmp4gnTeh.lrXcfmBFdi379Ag6J6zv9fQQw5qTwdDyf8ZwJ4Eq VQ28hHKTCHYZuMglulxc_NAV2sdzHdS20HDUwDw48wPCEAWfsj_YMdL70FPLK7HgaffapU4nW4Yc 4DcDZJnvbttqFsBFb1iKsdN1g.AyZHDGURTU9JOkrL4VHD_d4TiC7C0RXtEEh9COiabu22ieAKb1 sfosPeDfd6oy9S_uQBJTXTglkJyi2_WXCrmhwSzdkkOGEX.CucOegvMbL7_OlQbJT_aZFhFOytnN v4kUQX9u1gSd9ebl.eoh1CYWU59MbJ5jauHw.6NGLuDogvWlrE75HaUBYfKA48Y.aExTFA9m.J7D eqrEGXglVbuyclDHnMmprGX471T9MD.b5XKHp7E5kVWFf12Rr2RQ4TZLLt6L81IQCvVVqB6DI7Y1 GvTYaAEMcrZBW8HSpy0jTbFpbs5MXPB5Vnuanma3oH.AvngIL8PrqA_cbx.QBKlse9aXBqbb6lc. POb699QucezfSim7Zbrmq0fIDkJPCQ_VHtZFMrY6Scxj90pLC9POfwaqQrSCjNfv49D.ze6Jhq4g PvBzxNY92cCD4Qd_5OtkQaQHLpUwixOhDVg--
Received: from jws300085.mail.gq1.yahoo.com by sendmailws131.mail.gq1.yahoo.com; Thu, 16 Feb 2017 14:22:19 +0000; 1487254939.754
Date: Thu, 16 Feb 2017 14:22:18 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Message-ID: <741499660.676310.1487254939010@mail.yahoo.com>
In-Reply-To: <20170216093707.z2ienyk52r3pbl7x@nic.fr>
References: <1302911527.6950973.1487176178877.ref@mail.yahoo.com> <1302911527.6950973.1487176178877@mail.yahoo.com> <20170216093707.z2ienyk52r3pbl7x@nic.fr>
Subject: Re: Internet Research Labs Draft
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aBuqbd0jLwgZqjL0YeI3M7pysYw>
Cc: Harish Chowdhary <harish@nixi.in>, IETF Discussion List <ietf@ietf.org>, Mohit Batra <mohit@nixi.in>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 14:22:22 -0000

Stephane,


On Wed, Feb 15, 2017 at 04:29:38PM +0000,
nalini.elkins@insidethestack.com <nalini.elkins@insidethestack.com> wrote 
a message of 34 lines which said:

>> If anyone is interested, we have just done an I-D for a proposed
>> concept for "Internet Labs".   We hope this will be of interest.

>That's interesting, there is certainly a need for more resources for
>the people who want to work on the practical side of the Internet
>protocols.


> https://tools.ietf.org/html/draft-chowbat-irl-00

>I find the proposal both too detailed ("access to IRL labs" with
>discussion of CLI vs Blackberry...) and too vague. What will be the
>actual services provided by these labs?

What we envision are drafts which describe each lab specifically, for example, DPRIVE, TLS, etc.


This draft is the "Base Framework".   That is, each lab should describe what hardware, software, training tools it has specifically.

I will talk with you offline about specifics of how to improve the draft.

>There are a lot of resources already available. (Really a lot: may be
>the poeple who want to learn/work could use some guidance.) 

As far as we can see, there are, too many resources for some things and not enough for others.  We cite this in our draft.    It is also the viewpoint or perspective towards the particular IETF draft / RFC that is missing.

Our goal is to enable more people to participate well in the IETF as well as to resolve possible discussions at a WG with actual running code or packet traces.


Let me give an example.   Let's say that one wants to start working in DPRIVE (maybe a group you know something about!), then the lab would specifically say that if you want to see implementation of "RFC7858: Specification for DNS over Transport Layer Security (TLS)", then here it is, and then have some sample scenarios or even traces that are captured.  Then, you may also have the implementation of DNS over DTLS & you can see the differences.

I know that for myself, if I can stare at a packet trace at the same time that I am reading a draft or RFC, then all of a sudden, I actually start understanding and can comment somewhat intelligently.   A few years ago, one of my friends & I used to have a standing meeting on Thursday nights where we would do various tests on IPv6 servers, trace them, look at them & talk together about what we were seeing.  It really allowed us to understand IPv6 concepts in a way that would have been much more difficult otherwise.  Then, you can go back to the RFC or draft & then it all starts making some kind of sense.  And, I think that I am not alone.  Many people cannot just read a draft and understand.

I know I have tried to find, for example, a DTLS trace when I wanted to learn about that & it was not so easy.  (Which is your point below about a packet trace repository.)

And, yes, I know I could do all the implementation of everything myself, but there are only 24 hours in a day!    

As far as your point on guidance, I think that is very much on target.  I think that people need a bit of a bridge to help them make the leap to becoming productive contributors.

>Did you identify actual gaps (ideas: real-time BGP feed, repository of packet

>captures, since pcapr.net seems de facto dead, etc)?

This is a very good idea.  I have used PCAPR.net myself in the past & it was a very useful service.   I think the indexing of packet traces by protocol function is quite necessary.  I know Wireshark tries to have a repository also.  But it is quite incomplete.  I will chat with the Wireshark core developers on this as a good repository is useful for them also & we need more resources to help! 

>Editorial: for cloud services, please mention also non-US services
>(like OVH or Gandi in France, examples from China, Russia, India, are

>welcome).

Great!  Please let us know more.

Thanks for your comments.

Nalini


From nobody Thu Feb 16 06:39:06 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A870129A35 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 06:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YVd_CCDkbwf5 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 06:39:01 -0800 (PST)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 48F99129A2B for <ietf@ietf.org>; Thu, 16 Feb 2017 06:39:00 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id C9254B0A for <ietf@ietf.org>; Thu, 16 Feb 2017 14:38:59 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cOU5Tkq_Zk47 for <ietf@ietf.org>; Thu, 16 Feb 2017 08:38:59 -0600 (CST)
Received: from mail-vk0-f72.google.com (mail-vk0-f72.google.com [209.85.213.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 8D9D724D for <ietf@ietf.org>; Thu, 16 Feb 2017 08:38:58 -0600 (CST)
Received: by mail-vk0-f72.google.com with SMTP id 123so9398986vkm.4 for <ietf@ietf.org>; Thu, 16 Feb 2017 06:38:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lBE5T7g+T8VK+HvU1gv3XaXRoy3afvHHUqf2WzIOThQ=; b=j4D4j2lncNZybdSy2tH2T/PtBuq6ZMX2kpf6ygIK9IvEWPfC/P4sqOymLKHthwMck/ PxLgNq5Q17TdXBaivaHPbFn+0vOaLGSFmLh4wyBx8fZhJsNilenxne6fONIZVOMK277Z JEikYDn4GnFoVy6kujrODvzTWnugxfRlcfcxmdRAo31iqvKK+HIzvq5kWE3akQ87rhlg 5YQgG8cSeXVtuwFmGtf3MrHoxXLWu28KNUm8HwHXVNgi8tV2iItmwF5igcCpWV3Y8fuM r2+Q4ERLZT5O0qgldRLP4SwMbH3He6LeB7qCngeIRSO9vui6WQQwoF5Z1FzyVrE04yOR Ajdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lBE5T7g+T8VK+HvU1gv3XaXRoy3afvHHUqf2WzIOThQ=; b=gdYtKO8ixtHmtHDzM6x3mPZs8DBk9rkICeiAR8WUMwQoUVzwjMjtxCd0P2pIwNIVa5 uAn1JgoKp04BvBD8hO0r3VMUAjryWItQ7F6aa65uEBNLNGJBOhmZKpl1HRopA5fD/udY CDG9lgI/yAtMKRyCtrL25b6mAmE0va37SQGbXTNWXAmVvBsMRHykg+MpEROBUNR+lXDZ 55XiUb7hHRdY5xQdSfx17xRYGmVqOglR01NgXuhrvhuZiqtEdSZLa5XrVxEaFNIu4K0m Wd0DFNdY4M4S5KPdST+BbvSloyzJ8DFT0Z2XxaijMzb4Qi3xRQ0r7Jmzgk4lb4povMel 3rhA==
X-Gm-Message-State: AMke39kcUZkbJmCCkDtbbr30fCObx8iWwc2gyGTMmf9SCMBzhVqUNAeNrJM9Z9N55lejwjgWwPGEIwXCAHrcWh8X2sP7nPJ5U5TbEdWYikIWMG272XOpKLEUuAEsfOsELHhuNo0cA2ABJhB7IS0=
X-Received: by 10.31.78.66 with SMTP id c63mr1309803vkb.117.1487255937685; Thu, 16 Feb 2017 06:38:57 -0800 (PST)
X-Received: by 10.31.78.66 with SMTP id c63mr1309786vkb.117.1487255937438; Thu, 16 Feb 2017 06:38:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.84.15 with HTTP; Thu, 16 Feb 2017 06:38:56 -0800 (PST)
In-Reply-To: <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org>
From: David Farmer <farmer@umn.edu>
Date: Thu, 16 Feb 2017 08:38:56 -0600
Message-ID: <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a1148481ed76d090548a6c123
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8J-f6pu1NRe0rNUXljQaMpqTCJ8>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 14:39:03 -0000

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

On Thu, Feb 16, 2017 at 3:09 AM, <otroan@employees.org> wrote:

> Dear Randy,
>
> >>>> If your statement is that we only have the 64 bit boundary because of
> >>>> SLAAC I believe you are wrong.
> >>>
> >>> cite, please.  what else actually needs it?
> >>
> >> https://tools.ietf.org/html/rfc7421
> >
> > that excuses it.  cite where it is actually needed to do something
> > useful other than slaac.
>
> "something useful" makes it subjective.
>
> If you only care about technical issues, then:
> SLAAC, NPT66, ILNP are the biggest one that I can think of.
> Trivial to make SLAAC work with variable length prefixes of course.
> As well as we don't know the consequences for implementations.
> 7421 seems to indicate it mostly works.
>
> But then you have people who write code like this:
> https://git.fd.io/vpp/tree/src/vnet/map/map.h#n332
>
> Where it clearly will not work with a longer prefix than 64.
> Feel free to contribute a patch, but make sure to count the cycles spent
> through that code.
>

So, is that code right or wrong?  To be honest, I feel the current text
says its correct to embed 64 in your code.  If you truly think current text
is correct, then have the courage of your convictions and embed 64 in your
code too.

However, I take your example as evidence that the current text doesn't have
the balance right.  Is the proposed text too far the other way?  Maybe.
Well... actually probably it is too far the other way, but I don't see you
even acknowledging there is an issue with the current text.

As far as I'm concerned, this is a policy statement masquerading as a
technical requirement.  Policy is all about nuance and shades of gray, and
technical requirements are about clarity and making things ether black or
white.  The problem as I see it is, we are trying to use technical
requirements language too describe something that is truly a policy issue.
So we are probably doomed to fail!

How do we move forward? What I think we need is to make it clear that there
are real exceptions to 64, and it is therefore not acceptable to embed 64
in code.  The historic exception of addresses that start with 000 has been
too amorphous, no one thinks it real. I've provided two exception that are
clearly based on current standards track work, but I fear that still isn't
enough.  I fear some will still embed 64 and just add code for the
exceptions, if it's even really needed.

Can you help me find something a little more?

What about an additional exception for manual configuration?

Thanks.
-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Feb 16, 2017 at 3:09 AM,  <span dir=3D"ltr">&lt;<a href=3D"mail=
to:otroan@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Dear Randy,=
<br>
<br>
&gt;&gt;&gt;&gt; If your statement is that we only have the 64 bit boundary=
 because of<br>
&gt;&gt;&gt;&gt; SLAAC I believe you are wrong.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; cite, please.=C2=A0 what else actually needs it?<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://tools.ietf.org/html/rfc7421" rel=3D"noreferrer"=
 target=3D"_blank">https://tools.ietf.org/html/<wbr>rfc7421</a><br>
&gt;<br>
&gt; that excuses it.=C2=A0 cite where it is actually needed to do somethin=
g<br>
&gt; useful other than slaac.<br>
<br>
&quot;something useful&quot; makes it subjective.<br>
<br>
If you only care about technical issues, then:<br>
SLAAC, NPT66, ILNP are the biggest one that I can think of.<br>
Trivial to make SLAAC work with variable length prefixes of course.<br>
As well as we don&#39;t know the consequences for implementations.<br>
7421 seems to indicate it mostly works.<br>
<br>
But then you have people who write code like this:<br>
<a href=3D"https://git.fd.io/vpp/tree/src/vnet/map/map.h#n332" rel=3D"noref=
errer" target=3D"_blank">https://git.fd.io/vpp/tree/<wbr>src/vnet/map/map.h=
#n332</a><br>
<br>
Where it clearly will not work with a longer prefix than 64.<br>
Feel free to contribute a patch, but make sure to count the cycles spent th=
rough that code.<br></blockquote><div><br></div><div>So, is that code right=
 or wrong?=C2=A0 To be honest, I feel the current text says its correct to =
embed 64 in your code.=C2=A0 If you truly think current text is correct, th=
en have the courage of your convictions and embed 64 in your code too.</div=
><div><br></div><div>However, I take your example as evidence that the curr=
ent text doesn&#39;t have the balance right.=C2=A0 Is the proposed text too=
 far the other way?=C2=A0 Maybe.=C2=A0 Well... actually probably it is too =
far the other way, but I don&#39;t see you even acknowledging there is an i=
ssue with the current text. =C2=A0 =C2=A0</div><div>=C2=A0</div><div>As far=
 as I&#39;m concerned, this is a policy statement masquerading as a technic=
al requirement.=C2=A0 Policy is all about nuance and shades of gray, and te=
chnical requirements are about clarity and making things ether black or whi=
te.=C2=A0 The problem as I see it is, we are trying to use technical requir=
ements language too describe something that is truly a policy issue.=C2=A0 =
So we are probably doomed to fail!</div><div><br></div><div>How do we move =
forward? What I think we need is to make it clear that there are real excep=
tions to 64, and it is therefore not acceptable to embed 64 in code.=C2=A0 =
The historic exception of addresses that start with 000 has been too amorph=
ous, no one thinks it real. I&#39;ve provided two exception that are clearl=
y based on current standards track work, but I fear that still isn&#39;t en=
ough.=C2=A0 I fear some will still embed 64 and just add code for the excep=
tions, if it&#39;s even really needed.</div><div><br></div><div>Can you hel=
p me find something a little more?</div><div><br></div><div>What about an a=
dditional exception for manual configuration? =C2=A0 =C2=A0</div></div><div=
><br></div><div>Thanks.</div>-- <br><div class=3D"gmail_signature">=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farme=
r=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:E=
mail%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networ=
king &amp; Telecommunication Services<br>Office of Information Technology<b=
r>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=
=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--001a1148481ed76d090548a6c123--


From nobody Thu Feb 16 07:20:37 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BBD1129509 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 07:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fv7m7ltOSbJl for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 07:20:29 -0800 (PST)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id 999AC1294AB for <ietf@ietf.org>; Thu, 16 Feb 2017 07:20:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1487258428; d=isode.com; s=june2016; i=@isode.com; bh=u0wotMcChp5T5RfBmWao3AZzIJGSRHEnXAumDML0co8=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=oioHCYUMhfSgPYkwtnZ20voByQMhdbDqqaXj+eeeMfisHR1lp9RZTdOmb/7FJ1bLLDMVHM j+Uupt0Khkn1NpgqD4qWUU1QWFfAew2li3u6A1J2whVImtT0FD+HBmgL9Z8Z1LvqKnldb+ bOsYEL3ZZ0l1ZJW6Sj20295Og+tCQy0=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by waldorf.isode.com (submission channel) via TCP with ESMTPSA  id <WKXDPAA6wzF3@waldorf.isode.com>; Thu, 16 Feb 2017 15:20:28 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol  (jmap) - reducing configuration complexity
To: John C Klensin <john-ietf@jck.com>, Ned Freed <ned.freed@mrochek.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB>
Message-ID: <8c81f385-7dfc-cff3-f97c-3c016fc72601@isode.com>
Date: Thu, 16 Feb 2017 15:20:12 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <1162BF5A37921B1555FF29F9@PSB>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------44B9F9D239802BFDC960BD6C"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FnhRE1i_TEvIx_JcLLVLPG_1zek>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:20:31 -0000

--------------44B9F9D239802BFDC960BD6C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

John and Ned,

On 12/02/2017 20:15, John C Klensin wrote:

> --On Wednesday, February 8, 2017 12:39 -0800 Ned Freed
> <ned.freed@mrochek.com>  wrote:
>
  [snip]
>> (2) in particular creates additional requirements that need to
>> be explicitly called out in the charter. In particular, it's
>> imperative that (a) It be reasonable to implement
>> JMAP->IMAP/SUBMIT proxies, even if that constrains JMAP in
>> ways some folks do not like, (b) The list of IMAP extensions
>> needed to properly implement JMAP be called out, and (c) The
>> security considerations involved in operating such a proxy
>> need to be described in detail.
I updated Charter text to mention these.
> Exactly.  If one expects JMAP to be wildly successful, and
> unless there is either a plausible plan to make all of those
> IMAP clients go away (even if there are no new ones), I think
> that list should include either its being reasonable to
> implement and support IMAP/SUBMIT-> JMAP proxies or other
> overlays or a charter requirement to discuss residual use cases
> for IMAP.    I'm particularly concerned about supporting
> IMAP-native clients with a JMAP-native mailstore.
>
>>> 2). Both are supported by the same software (i.e. Cyrus and
>>> Dovecot use case). I doubt that incremental cost of
>>> configuring both is much higher than just configuring one of
>>> them.
>>> In either case configuring JMAP clients is a simple(r)
>>> proposition: just distribute HTTP URI for a JMAP instance.
>>>> and to support, also for a long time, the ability to convert
>>>> between the two formats.
>>> There are no 2 formats, both IMAP and JMAP operate on RFC
>>> 5322 objects, so the rest of your argument is invalid.
>> Agreed. I have to say I really don't understand the confusion
>> surrounding this point. IMAP has bodystructure plus a couple
>> of other formats for returning message data, and a means of
>> creating new messages from pieces of other messages, none of
>> which look remotely like MIME/RFC 5322, and nobody cares.
>>
>> This is effectively the same thing; why should anyone care
>> here?
> I can't speak for anyone else, but I'm concerned about what it
> takes to create and maintain servers and mailstores that are
> compatible with both IMAP and JMAP.  If that means proxies, we
> either need to address the question of IMAP proxies over JMAP
> and JMAP mailstores as well as the JMAP over IMAP-compatible
> ones or I'd like the charter is require a good explanation of
> why that isn't necessary.  That might be "IMAP-based systems
> with JMAP overlays forever", but, the more people argue that
> JMAP will take over (rapidly or otherwise), the less plausible
> that position feels.
I've done some prototyping of existing JMAP proposal and I am quite 
confident that underlying models are close enough that implementing one 
on top of another is doable. IMAP+QRESYNC extension require IMAP 
mailstores to store change sequence numbers, which is required feature 
in JMAP.

Best Regards,
Alexey


--------------44B9F9D239802BFDC960BD6C
Content-Type: text/html; charset=utf-8
Content-transfer-encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3Dutf-8" http-equiv=3D"Content-Type"=
>
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>John and Ned,<br>
    </p>
    <p>On 12/02/2017 20:15, John C Klensin wrote:<br>
    </p>
    <blockquote cite=3D"mid:1162BF5A37921B1555FF29F9@PSB" type=3D"cite">
      <pre wrap=3D"">--On Wednesday, February 8, 2017 12:39 -0800 Ned Freed
<a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:ned.freed@mrochek.com">&lt=
;ned.freed@mrochek.com&gt;</a> wrote:

</pre>
    </blockquote>
    =C2=A0[snip]<br>
    <blockquote cite=3D"mid:1162BF5A37921B1555FF29F9@PSB" type=3D"cite">
      <blockquote type=3D"cite">
        <pre wrap=3D"">(2) in particular creates additional requirements tha=
t need to
be explicitly called out in the charter. In particular, it's
imperative that (a) It be reasonable to implement
JMAP-&gt;IMAP/SUBMIT proxies, even if that constrains JMAP in
ways some folks do not like, (b) The list of IMAP extensions
needed to properly implement JMAP be called out, and (c) The
security considerations involved in operating such a proxy
need to be described in detail.</pre>
      </blockquote>
    </blockquote>
    I updated Charter text to mention these.
    <blockquote cite=3D"mid:1162BF5A37921B1555FF29F9@PSB" type=3D"cite">
      <blockquote type=3D"cite"> </blockquote>
      <pre wrap=3D"">Exactly.  If one expects JMAP to be wildly successful, =
and
unless there is either a plausible plan to make all of those
IMAP clients go away (even if there are no new ones), I think
that list should include either its being reasonable to
implement and support IMAP/SUBMIT-&gt; JMAP proxies or other
overlays or a charter requirement to discuss residual use cases
for IMAP.    I'm particularly concerned about supporting
IMAP-native clients with a JMAP-native mailstore.

</pre>
      <blockquote type=3D"cite">
        <blockquote type=3D"cite">
          <pre wrap=3D"">2). Both are supported by the same software (i.e. C=
yrus and
Dovecot use case). I doubt that incremental cost of
configuring both is much higher than just configuring one of
them.
</pre>
        </blockquote>
        <blockquote type=3D"cite">
          <pre wrap=3D"">In either case configuring JMAP clients is a simple=
(r)
proposition: just distribute HTTP URI for a JMAP instance.
</pre>
        </blockquote>
        <blockquote type=3D"cite">
          <blockquote type=3D"cite">
            <pre wrap=3D"">and to support, also for a long time, the ability=
 to convert
between the two formats.
</pre>
          </blockquote>
        </blockquote>
        <blockquote type=3D"cite">
          <pre wrap=3D"">There are no 2 formats, both IMAP and JMAP operate =
on RFC
5322 objects, so the rest of your argument is invalid.
</pre>
        </blockquote>
        <pre wrap=3D"">Agreed. I have to say I really don't understand the c=
onfusion
surrounding this point. IMAP has bodystructure plus a couple
of other formats for returning message data, and a means of
creating new messages from pieces of other messages, none of
which look remotely like MIME/RFC 5322, and nobody cares.

This is effectively the same thing; why should anyone care
here?
</pre>
      </blockquote>
      <pre wrap=3D"">I can't speak for anyone else, but I'm concerned about =
what it
takes to create and maintain servers and mailstores that are
compatible with both IMAP and JMAP.  If that means proxies, we
either need to address the question of IMAP proxies over JMAP
and JMAP mailstores as well as the JMAP over IMAP-compatible
ones or I'd like the charter is require a good explanation of
why that isn't necessary.  That might be "IMAP-based systems
with JMAP overlays forever", but, the more people argue that
JMAP will take over (rapidly or otherwise), the less plausible
that position feels.</pre>
    </blockquote>
    I've done some prototyping of existing JMAP proposal and I am quite
    confident that underlying models are close enough that implementing
    one on top of another is doable. IMAP+QRESYNC extension require IMAP
    mailstores to store change sequence numbers, which is required
    feature in JMAP.<br>
    <br>
    Best Regards,<br>
    Alexey<br>
    <br>
  </body>
</html>

--------------44B9F9D239802BFDC960BD6C--


From nobody Thu Feb 16 07:30:07 2017
Return-Path: <tim@ripe.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58CAD12943F; Thu, 16 Feb 2017 07:30:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 FePiiU-q-ox3; Thu, 16 Feb 2017 07:30:01 -0800 (PST)
Received: from molamola.ripe.net (molamola.ripe.net [IPv6:2001:67c:2e8:11::c100:1371]) (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 493A6129509; Thu, 16 Feb 2017 07:30:01 -0800 (PST)
Received: from nene.ripe.net ([193.0.23.10]) by molamola.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1ceO0L-000Axr-EP; Thu, 16 Feb 2017 16:29:58 +0100
Received: from sslvpn.ripe.net ([193.0.20.230] helo=vpn-196.ripe.net) by nene.ripe.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84_2) (envelope-from <tim@ripe.net>) id 1ceO0L-00064R-B3; Thu, 16 Feb 2017 16:29:57 +0100
Subject: Re: Gen-Art Last Call review of draft-ietf-sidr-delta-protocol-06
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: text/plain; charset=us-ascii
From: Tim Bruijnzeels <tim@ripe.net>
In-Reply-To: <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
Date: Thu, 16 Feb 2017 16:29:57 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <32AE4173-90C7-4E4D-A196-B3AD7F99E099@ripe.net>
References: <CY1PR0301MB2122BA74E6B5A37D863D8E7FAD580@CY1PR0301MB2122.namprd03.prod.outlook.com> <4231A2C1-D57B-4896-9669-27B73D9463E4@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3124)
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: ---------
X-RIPE-Spam-Report: Spam Total Points:   -9.4 points pts rule name              description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED            Passed through trusted hosts only via SMTP -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 784d7acfe6559f2a0b602ec6519a0719029fab8b99d9f797342878b1d9335ce9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AwivTcOjxndpaUs0YTADjzPEJHg>
Cc: Orit Levin <oritl@microsoft.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "draft-ietf-sidr-delta-protocol.all@tools.ietf.org" <draft-ietf-sidr-delta-protocol.all@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:30:02 -0000

Hi Jari, all,

Comment noted and should make it to an update when we process the other =
comments received!

Tim


> On 16 Feb 2017, at 12:58, Jari Arkko <jari.arkko@piuha.net> wrote:
>=20
> Thanks for your review, Orit!
>=20
> (Authors, did you note the comment?)
>=20
> Jari
>=20


From nobody Thu Feb 16 07:30:38 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FE0A12964B for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 07:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhdfqHNevRQR for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 07:30:34 -0800 (PST)
Received: from mail-ot0-x22d.google.com (mail-ot0-x22d.google.com [IPv6:2607:f8b0:4003:c0f::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 432C412943F for <ietf@ietf.org>; Thu, 16 Feb 2017 07:30:34 -0800 (PST)
Received: by mail-ot0-x22d.google.com with SMTP id 45so13190707otd.2 for <ietf@ietf.org>; Thu, 16 Feb 2017 07:30:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=HzmpDguhp33xdLCQo3q5M5BEW7gTVPB5oH05fj5eiaw=; b=tu5j2eCrLra8ZhHF9OPGpZiN/8VdbZZex0nr1r1BTH10zScGz2UENhk95FsODaIb9q IFWY2C5bIE6eOwmVLq4s37fwFJvl5qeAxDFViuB4BkFWwZXv2ipVf0EPJm45z8depXQH FAGFRDLXIe3PkCUbRhCIp1tZTQw/9/hAA10ANU+HMFT/V28iv95TNhTOezoHtmp/Bsx+ b1Q8YqO87EMoL1rFRaLqu2ckpNJKw4SrE+AIyA+Oa5Lx8EvYTpJXFVNeUN0tO7BcYmJS g9nvco4shMRmOek/4TtT8go8KJ0YE324ImEAwk4ndjmarRJEAfAyYYZDA1menOH02kOw pULg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=HzmpDguhp33xdLCQo3q5M5BEW7gTVPB5oH05fj5eiaw=; b=mX/oVZxMgr2Wuukc0Wav2DHISGFi8KRr+eURjN83v/HOt7Qj8anOQYLFDPnYhsX/Ow 45nmYoVPNtEvhkxoQ7EAkYbMio9WcvDsBfDOFQPw4p2pEloYKnH+djkcN3oxKVb5GpyN jGifeWIl2ERhi/SotesVcoqJxGUtbU1oeUt1ZdXj7qtz3P6OMy71DMJLZ4p5QojtYmXP ayYyqoP8ntX2RwOYpegWyPFkt1usDtLObiCF+KGt0kQRFpPx1P1qOnV7FoccafD+Hpjy ET0NRZ4WKNtJTogKotPOT4zoaqnrWJopyPvrLDgsq3M4mu4d445ThVnru8roptgCwxq4 5nNw==
X-Gm-Message-State: AMke39kvjykOiw/31drdlzVLPIuJKVgdSyrcicG/D7TNYRKCTdPqY6Rv+2X+TJBd47ut+LHTZ0TC3BwTVBUOLsh+
X-Received: by 10.157.31.114 with SMTP id x47mr1312567otx.233.1487259033448; Thu, 16 Feb 2017 07:30:33 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.49.28 with HTTP; Thu, 16 Feb 2017 07:30:32 -0800 (PST)
In-Reply-To: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
From: Wei Chuang <weihaw@google.com>
Date: Thu, 16 Feb 2017 07:30:32 -0800
Message-ID: <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: "John R. Levine" <johnl@iecc.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a113d13bc66c4240548a77ad5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_Fl3CDzBbOoTCfdEfb1-Sg8cUeE>
Cc: IETF general list <ietf@ietf.org>, Ryan Sleevi <sleevi@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 15:30:36 -0000

--001a113d13bc66c4240548a77ad5
Content-Type: multipart/alternative; boundary=001a113d13bc6157a70548a77abf

--001a113d13bc6157a70548a77abf
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Sat, Feb 11, 2017 at 1:06 PM, John R. Levine <johnl@iecc.com> wrote:

> Once again, a CA with *ONLY* rfc822Name constraints should not be
>> able to able issue EE certificates with SmtpUtf8Name altNames that
>> conflict with its rfc822Name constraints.
>>
>
> How about if a CA with only rfc822Name constraints can't issue certs
> with SmtpUTF8Names at all, and of course vice versa.  If you want both
> kinds of names, the CA has to constrain both.
>
> R's,
> John
>
>
I had asked a few folks at Google for an opinion about the name
constraints.  Let me post Ryan Sleevi's (CC'ed) opinion:

https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg [the
above] basically says option 3 [the acceptable approach of the 3], but
unfortunately suffers from 'legacy' - namely, you cannot assume that all
rfc822Name clients will be updated to support SmtpUtf8Name, and short of
marking it critical (which would mean its undeployable), you can't assume
that an SmtpUtf8Name nameConstraint will constrain an rfc822Name.

...

There are a few approaches you could try:
- "Monkey Patch" RFC5280, 6.1.4 (g) (1) and (2) [and 6.1.2 (b) and (c)]
such that an rfc822Name present in the permittedSubtrees/excludedSubtrees
(or initial-permitted-subtrees / initial-excluded-subtrees, for 6.1.2) but
an Smtp8Utf8Name is not, or if an Smtp8UtfName is present but an rfc822Name
is not, then set permitted to the empty set for that name type / set
excluded to the wildcard set. However, https://tools.ietf.
org/html/draft-ietf-lamps-eai-addresses-06#section-6 leaves me completely
confused as to whether you support the empty set / wildcard set
construction.
- Require post-processing validation, namely
  - For each certificate in the validated certificate chain, clients that
recognize SmtpUtf8Name MUST NOT accept any certificate which contains an
nameConstraint that asserts a constraint for an rfc822Name in either the
permittedSubtrees or excludedSubtrees if it does not also assert a
nameConstraint for an SmtpUtf8Name in the same section. Similarly, clients
that recognize SmtpUtf8Name MUST NOT accept any certificate which contains
a nameConstraint for an SmtpUtf8Name ... if it does not also assert a
nameConstraint for an rfc822Name in the same section.

=====

We can update the draft to include the validation steps to preclude the
unexpected legacy path.

-Wei

--001a113d13bc6157a70548a77abf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, Feb 11, 2017 at 1:06 PM, John R. Levine <span dir="ltr">&lt;<a href="mailto:johnl@iecc.com" target="_blank">johnl@iecc.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Once again, a CA with *ONLY* rfc822Name constraints should not be<br>
able to able issue EE certificates with SmtpUtf8Name altNames that<br>
conflict with its rfc822Name constraints.<br>
</blockquote>
<br></span>
How about if a CA with only rfc822Name constraints can&#39;t issue certs<br>
with SmtpUTF8Names at all, and of course vice versa.  If you want both<br>
kinds of names, the CA has to constrain both.<br>
<br>
R&#39;s,<br>
John<br>
<br></blockquote><div><br></div><div>I had asked a few folks at Google for an opinion about the name constraints.  Let me post Ryan Sleevi&#39;s (CC&#39;ed) opinion: </div></div><br></div><div class="gmail_extra"><a href="https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg" target="_blank" style="font-size:12.8px">https://mailarchive.ietf.org/a<wbr>rch/msg/ietf/ngUOjvCHubjcyiG4u<wbr>Z0w16-5-fg</a><span style="font-size:12.8px"> [the above] basically says option 3 [the acceptable approach of the 3], but unfortunately suffers from &#39;legacy&#39; - namely, you cannot assume that all rfc822Name clients will be updated to support SmtpUtf8Name, and short of marking it critical (which would mean its undeployable), you can&#39;t assume that an SmtpUtf8Name nameConstraint will constrain an rfc822Name.</span><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">...</div><div class="gmail_extra"><br><!--
--></div><div class="gmail_extra"><div style="font-size:12.8px">There are a few approaches you could try:</div><div style="font-size:12.8px">- &quot;Monkey Patch&quot; RFC5280, 6.1.4 (g) (1) and (2) [and 6.1.2 (b) and (c)] such that an rfc822Name present in the permittedSubtrees/<wbr>excludedSubtrees (or initial-permitted-subtrees / initial-excluded-subtrees, for 6.1.2) but an Smtp8Utf8Name is not, or if an Smtp8UtfName is present but an rfc822Name is not, then set permitted to the empty set for that name type / set excluded to the wildcard set. However, <a href="https://tools.ietf.org/html/draft-ietf-lamps-eai-addresses-06#section-6" target="_blank">https://tools.ietf.<wbr>org/html/draft-ietf-lamps-eai-<wbr>addresses-06#section-6</a> leaves me completely confused as to whether you support the empty set / wildcard set construction.</div><div style="font-size:12.8px">- Require post-processing validation, namely</div><!--
--><div style="font-size:12.8px">  - For each certificate in the validated certificate chain, clients that recognize SmtpUtf8Name MUST NOT accept any certificate which contains an nameConstraint that asserts a constraint for an rfc822Name in either the permittedSubtrees or excludedSubtrees if it does not also assert a nameConstraint for an SmtpUtf8Name in the same section. Similarly, clients that recognize SmtpUtf8Name MUST NOT accept any certificate which contains a nameConstraint for an SmtpUtf8Name ... if it does not also assert a nameConstraint for an rfc822Name in the same section.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">=====</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">We can update the draft to include the validation steps to preclude the unexpected legacy path.</div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">-Wei</div></div></div>

--001a113d13bc6157a70548a77abf--

--001a113d13bc66c4240548a77ad5
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCBB+Bsl4FBEzqI203GaXM/4
dBnTDqlatLo+mBPiGSGobTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMTYxNTMwMzNaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAQaZbq6IuYhhuW52WGjyhNnC3fR361gf9w/PNRSlT
Es7nTXGIQziVDNh8X99Zk5Uo9mgpHzDpuhx4YQU2QJ2WNOwHs/m3kTRlVyn6+1/AedmNSsD6oN2q
OVTJVyKZS4r0kBNksz/K2MMuyk77MqcaEUy0sPFtvn4g4Op1P/f05cW9zciQgLSDvXgR2HtBMLo1
XIgm9pBO80vn+CgUYKe0k/VKqwn5/GJL27F7rhv7J0sVcsmo2IdiySULj41ogybXOqZmF3bHY2kA
x3H2i8aXeCsaLTWKTcM+ic6JcCe9yB/yYBk6E5L0OJKOO2zDm9r5r6/QmsqxWmF8RhzBJwoirw==
--001a113d13bc66c4240548a77ad5--


From nobody Thu Feb 16 08:00:12 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4887A129D66; Thu, 16 Feb 2017 08:00:08 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENByfhJsiiYm; Thu, 16 Feb 2017 08:00:02 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 104DE12944C; Thu, 16 Feb 2017 08:00:02 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id v77so3813303wmv.0; Thu, 16 Feb 2017 08:00:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=BOhvQRcmRYmHrD6F8dcTiu8EKCno78mChnG5Ca8PCvQ=; b=hoY+GrEg+VmvRzrXKj5m3/M9vzMwu+PM0VuX9tASZtKVHbSwvBCSnPpvGQ9hGY74pU D4ZRwx4ONrJ60Z6COcwQMF6uwQlL5Za+Uf3+HbVlyivtjiYeryTyxx6+AV3kKccKiWMR RPbhJ3V7nClGRNR+jJ8U+z/Lw0ofehyHkanEIOW9FmuUz8hvYPD97pxryM0bntwpBnkf uHN84R2oM7vgBYq08C+AUxh09ImnAuBQkN+lLIh4griTpdcTrDEm/tZWjYx1SWuyHGj5 xE0qNgG1HtA70LXPa5u5D0cYYTKYhzNrcMj077poq0caTlCgezLWMbvOrpBaCLMi+oa2 zQPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=BOhvQRcmRYmHrD6F8dcTiu8EKCno78mChnG5Ca8PCvQ=; b=HPFs0d6BFbNgYMMmxdXnsiaczyxsVGaP+72jo15dzOLtci6ERkqOM8jDtUBSzqMaIH XgtPPH0XHb4sqL34yaKvKXVA7c16vcaIIcQRa6mtI2ayQKNEwhOpUv0xu0RhlkzkAH0Q BBei4kGYZOnRpzpP1AuiuzaqGlm8bhpoRewOkRmg3V9TTH+XRqlZnydyAJeisEWuEGfU qMSl/2dZjmcFvrbQ2clJJCUoU9wYMXNzWjZStZ0BC+LCJoizw3PFf2NTuPySD94csr7e Cl3bQUVEeFcu+KrdHTLmlLgzdf/KSg6HTALfgRgaMRaCOJZEYGBnf29xyxtNMh/0dTXN NkHg==
X-Gm-Message-State: AMke39lSjTTaoZCcmEe82CMJCLS1d2aBWGlQv3tHTg7QOJDLpM+l9D40+fXFveoH3T7Hng==
X-Received: by 10.28.142.73 with SMTP id q70mr3225527wmd.3.1487260800492; Thu, 16 Feb 2017 08:00:00 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 65sm9442521wri.53.2017.02.16.07.59.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 07:59:59 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Date: Thu, 16 Feb 2017 15:59:56 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nDtLk5bItftmF5Mce9QDBOmK9kw>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 16:00:08 -0000

On 14/02/2017 23:00, Templin, Fred L wrote:
> Unless there is operational assurance of
> some size X>1280, however, tunnels have to use fragmentation to
> guarantee that - at a minimum - packets up to 1280 will get through.

In that case there really needs to be a note about MPLS.

You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.

Stewart


From nobody Thu Feb 16 08:00:47 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B011295F3; Thu, 16 Feb 2017 08:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 2z_PEEV2yxMq; Thu, 16 Feb 2017 08:00:34 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 6892B12962E; Thu, 16 Feb 2017 08:00:28 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GFxSao006367 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 07:59:30 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu> <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <2eb7f087-571e-d2be-2c57-1d287f443ad7@isi.edu>
Date: Thu, 16 Feb 2017 07:59:27 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OfpMvvKjsAreQdBMUjWz5CsS5iU>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 16:00:36 -0000

Hi, Gorry,


On 2/16/2017 6:08 AM, Gorry Fairhurst wrote:
>
> The text below is not about tunnels - this is about  the operation of
> transport, and the quoted text is from the new UDP Guidelines ID.
Oh - I was distracted by some of the text then - see below...

>
> On 15/02/2017 21:26, Joe Touch wrote:
>> Hi, Gorry (et al.),
>>
>> Again, the following text should not drift into discussing how tunnels
>> are handled IMO. That should be addressed in a different document (and I
>> don't think it's troublesome at all if viewed correctly).
>>
>> Joe
>>
>>
>> On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
>>> - Introduces a significant vulnerability.  A rogue PTB message that
>>> reduces the PMTU to a minimum, can result in a path too small to carry
>>> an encapsulated packet. (Recently noted by Fernando Gont). .

The issue is the IPv6 limit. Issues of "encapsulated packets" not
fitting in this limit are already handled by transport protocols using
IPv6 (if this is about layering encapsulation) and tunneling (if this is
about tunneling, which is how I inferred "encapsulated packets").

>>>
>>> Moreover, other layers view ICMP messages with suspicion and have long
>>> noted the need to check ICMP payload and match only packets that
>>> relate to actual 5-tuples in use (effectively reducing vulnerability
>>> to off-path attacks). For example, the Guidelines for UDP, rfc5405bis,
>>> state:
>>>
>>> " Applications SHOULD appropriately validate the payload of ICMP
>>>    messages to ensure these are received in response to transmitted
>>>    traffic (i.e., a reported error condition that corresponds to a UDP
>>>    datagram actually sent by the application). …“
>
> The comment below could easily be handled by something that clearly
> indicates the problem and points to the tunnel draft for guidance, I
> agree no need to go into algorithms/methods here.

The problem isn't unique to tunnels - it happens on any link whose MTU
can vary, and IMO the solution is the same. React to the change in
subsequent traffic, rather than attempting to rely in ICMP relaying from
signaling inside the link layer -- regardless of that link layer.

Joe

>
>>> - clearly handling this in IP-layer tunnels can be troublesome, but
>>> that's a problem that should be described, not obscured.
>>
>
> Gorry


From nobody Thu Feb 16 08:47:58 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 994E0129D81; Thu, 16 Feb 2017 08:47:46 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 Rxd_WhPCTjIo; Thu, 16 Feb 2017 08:47:43 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id 5CECA129DBC; Thu, 16 Feb 2017 08:47:28 -0800 (PST)
Received: from dhcp-207-155.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:b82b:6073:afb4:ddb0]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 91ED01B00055; Thu, 16 Feb 2017 18:45:12 +0000 (GMT)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu> <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk> <2eb7f087-571e-d2be-2c57-1d287f443ad7@isi.edu>
To: Joe Touch <touch@isi.edu>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683.
Message-ID: <f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk>
Date: Thu, 16 Feb 2017 16:47:17 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <2eb7f087-571e-d2be-2c57-1d287f443ad7@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fOZNsC5qVZBjcnFNZtqh-9gOm7s>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 16:47:46 -0000

On 16/02/2017 15:59, Joe Touch wrote:
> Hi, Gorry,
>
>
> On 2/16/2017 6:08 AM, Gorry Fairhurst wrote:
>>
>> The text below is not about tunnels - this is about  the operation of
>> transport, and the quoted text is from the new UDP Guidelines ID.
> Oh - I was distracted by some of the text then - see below...
>
>>
>> On 15/02/2017 21:26, Joe Touch wrote:
>>> Hi, Gorry (et al.),
>>>
>>> Again, the following text should not drift into discussing how tunnels
>>> are handled IMO. That should be addressed in a different document (and I
>>> don't think it's troublesome at all if viewed correctly).
>>>
>>> Joe
>>>
>>>
>>> On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
>>>> - Introduces a significant vulnerability.  A rogue PTB message that
>>>> reduces the PMTU to a minimum, can result in a path too small to carry
>>>> an encapsulated packet. (Recently noted by Fernando Gont). .
>
> The issue is the IPv6 limit. Issues of "encapsulated packets" not
> fitting in this limit are already handled by transport protocols using
> IPv6 (if this is about layering encapsulation) and tunneling (if this is
> about tunneling, which is how I inferred "encapsulated packets").
>
The point was that according to this spec (as currently written), an 
off-path attacker can trivially inject an ICMPv6 message into the 
traffic, which then causes a host to accept a different PathMTU. 
Normally a transport design would expect ICMP messages to be at least 
checked against the list of known connections, so that successfully 
mounting this attack required the  packet to correspond to ports that 
are in use. (Usually unknown to an off-path attacker).

>>>>
>>>> Moreover, other layers view ICMP messages with suspicion and have long
>>>> noted the need to check ICMP payload and match only packets that
>>>> relate to actual 5-tuples in use (effectively reducing vulnerability
>>>> to off-path attacks). For example, the Guidelines for UDP, rfc5405bis,
>>>> state:
>>>>
>>>> " Applications SHOULD appropriately validate the payload of ICMP
>>>>    messages to ensure these are received in response to transmitted
>>>>    traffic (i.e., a reported error condition that corresponds to a UDP
>>>>    datagram actually sent by the application). …“
>>
>> The comment below could easily be handled by something that clearly
>> indicates the problem and points to the tunnel draft for guidance, I
>> agree no need to go into algorithms/methods here.
>
> The problem isn't unique to tunnels - it happens on any link whose MTU
> can vary, and IMO the solution is the same. React to the change in
> subsequent traffic, rather than attempting to rely in ICMP relaying from
> signaling inside the link layer -- regardless of that link layer.
>
> Joe
>
I'd be fine with recommending that way of working - but if the host 
reacts to ICMP, it is important to try to verify ICMPv6 messages before 
accepting them.

>>
>>>> - clearly handling this in IP-layer tunnels can be troublesome, but
>>>> that's a problem that should be described, not obscured.
>>>
>>
>> Gorry
>
Gorry


From nobody Thu Feb 16 09:06:51 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFCC129660; Thu, 16 Feb 2017 09:06:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 V5-U7WdArfPf; Thu, 16 Feb 2017 09:06:41 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 91832129633; Thu, 16 Feb 2017 09:06:41 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GH5e5V027851 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 09:05:42 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu> <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk> <2eb7f087-571e-d2be-2c57-1d287f443ad7@isi.edu> <f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <68d2bffb-825a-5eee-e6c8-2c4241c98ae9@isi.edu>
Date: Thu, 16 Feb 2017 09:05:39 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk>
Content-Type: multipart/alternative; boundary="------------62D4C9D76F496C70E419C0C7"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kvgqBwfM1Qrn5dO_BQ4CJ_5qyS0>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 17:06:44 -0000

This is a multi-part message in MIME format.
--------------62D4C9D76F496C70E419C0C7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

Hi, Gorry,


On 2/16/2017 8:47 AM, Gorry Fairhurst wrote:
>>
> The point was that according to this spec (as currently written), an
> off-path attacker can trivially inject an ICMPv6 message into the
> traffic, which then causes a host to accept a different PathMTU.
> Normally a transport design would expect ICMP messages to be at least
> checked against the list of known connections, so that successfully
> mounting this attack required the  packet to correspond to ports that
> are in use. (Usually unknown to an off-path attacker).

Agreed - but IMO this has nothing to do with "encapsulation" or
tunneling, AFAICT.

>
>>>>>
>>>>> Moreover, other layers view ICMP messages with suspicion and have
>>>>> long
>>>>> noted the need to check ICMP payload and match only packets that
>>>>> relate to actual 5-tuples in use (effectively reducing vulnerability
>>>>> to off-path attacks). For example, the Guidelines for UDP,
>>>>> rfc5405bis,
>>>>> state:
>>>>>
>>>>> " Applications SHOULD appropriately validate the payload of ICMP
>>>>>    messages to ensure these are received in response to transmitted
>>>>>    traffic (i.e., a reported error condition that corresponds to a
>>>>> UDP
>>>>>    datagram actually sent by the application). …“
>>>
>>> The comment below could easily be handled by something that clearly
>>> indicates the problem and points to the tunnel draft for guidance, I
>>> agree no need to go into algorithms/methods here.
>>
>> The problem isn't unique to tunnels - it happens on any link whose MTU
>> can vary, and IMO the solution is the same. React to the change in
>> subsequent traffic, rather than attempting to rely in ICMP relaying from
>> signaling inside the link layer -- regardless of that link layer.
>>
>> Joe
>>
> I'd be fine with recommending that way of working - but if the host
> reacts to ICMP, it is important to try to verify ICMPv6 messages
> before accepting them. 

I think that's a fine punchline. The key is what "verification" means -
as you note, a transport connection might not want to react to
conflicting information and no entity (transport, OS, etc.) ought to
react to nonsensical info (attempts to push MTU below required minimums).

Joe


--------------62D4C9D76F496C70E419C0C7
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, Gorry,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/16/2017 8:47 AM, Gorry Fairhurst
      wrote:<br>
    </div>
    <blockquote
      cite="mid:f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk"
      type="cite">
      <blockquote type="cite" style="color: #000000;"><br>
      </blockquote>
      The point was that according to this spec (as currently written),
      an off-path attacker can trivially inject an ICMPv6 message into
      the traffic, which then causes a host to accept a different
      PathMTU. Normally a transport design would expect ICMP messages to
      be at least checked against the list of known connections, so that
      successfully mounting this attack required the  packet to
      correspond to ports that are in use. (Usually unknown to an
      off-path attacker).
      <br>
    </blockquote>
    <br>
    Agreed - but IMO this has nothing to do with "encapsulation" or
    tunneling, AFAICT.<br>
    <br>
    <blockquote
      cite="mid:f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk"
      type="cite">
      <br>
      <blockquote type="cite" style="color: #000000;">
        <blockquote type="cite" style="color: #000000;">
          <blockquote type="cite" style="color: #000000;">
            <blockquote type="cite" style="color: #000000;">
              <br>
              Moreover, other layers view ICMP messages with suspicion
              and have long
              <br>
              noted the need to check ICMP payload and match only
              packets that
              <br>
              relate to actual 5-tuples in use (effectively reducing
              vulnerability
              <br>
              to off-path attacks). For example, the Guidelines for UDP,
              rfc5405bis,
              <br>
              state:
              <br>
              <br>
              " Applications SHOULD appropriately validate the payload
              of ICMP
              <br>
                 messages to ensure these are received in response to
              transmitted
              <br>
                 traffic (i.e., a reported error condition that
              corresponds to a UDP
              <br>
                 datagram actually sent by the application). …“
              <br>
            </blockquote>
          </blockquote>
          <br>
          The comment below could easily be handled by something that
          clearly
          <br>
          indicates the problem and points to the tunnel draft for
          guidance, I
          <br>
          agree no need to go into algorithms/methods here.
          <br>
        </blockquote>
        <br>
        The problem isn't unique to tunnels - it happens on any link
        whose MTU
        <br>
        can vary, and IMO the solution is the same. React to the change
        in
        <br>
        subsequent traffic, rather than attempting to rely in ICMP
        relaying from
        <br>
        signaling inside the link layer -- regardless of that link
        layer.
        <br>
        <br>
        Joe
        <br>
        <br>
      </blockquote>
      I'd be fine with recommending that way of working - but if the
      host reacts to ICMP, it is important to try to verify ICMPv6
      messages before accepting them.
    </blockquote>
    <br>
    I think that's a fine punchline. The key is what "verification"
    means - as you note, a transport connection might not want to react
    to conflicting information and no entity (transport, OS, etc.) ought
    to react to nonsensical info (attempts to push MTU below required
    minimums).<br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------62D4C9D76F496C70E419C0C7--


From nobody Thu Feb 16 09:13:08 2017
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3675A12967A; Thu, 16 Feb 2017 09:13:07 -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 autolearn_force=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 K_ImCBmo-kuN; Thu, 16 Feb 2017 09:13:06 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:241:204::f0f0]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEED129680; Thu, 16 Feb 2017 09:13:06 -0800 (PST)
Received: from dhcp-207-155.erg.abdn.ac.uk (unknown [IPv6:2001:630:241:207:b82b:6073:afb4:ddb0]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 794E11B00055; Thu, 16 Feb 2017 19:10:55 +0000 (GMT)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <ed4e3ab5-e93e-d9ca-28c0-43f8bf22039a@isi.edu> <2fc3beb1-86d1-2436-71e1-a90c525cb0d6@erg.abdn.ac.uk> <2eb7f087-571e-d2be-2c57-1d287f443ad7@isi.edu> <f4050249-f606-c38b-2081-0303f5fa85b9@erg.abdn.ac.uk> <68d2bffb-825a-5eee-e6c8-2c4241c98ae9@isi.edu>
To: Joe Touch <touch@isi.edu>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683.
Message-ID: <68cef79a-7b7e-bd4d-9f08-2768ec6576a0@erg.abdn.ac.uk>
Date: Thu, 16 Feb 2017 17:13:05 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <68d2bffb-825a-5eee-e6c8-2c4241c98ae9@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iZcasISNjrnT8GAt1RZjVFAKGsA>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 17:13:07 -0000

I think we agreed.

Gorry

On 16/02/2017 17:05, Joe Touch wrote:
> Hi, Gorry,
>
>
> On 2/16/2017 8:47 AM, Gorry Fairhurst wrote:
>>>
>> The point was that according to this spec (as currently written), an
>> off-path attacker can trivially inject an ICMPv6 message into the
>> traffic, which then causes a host to accept a different PathMTU.
>> Normally a transport design would expect ICMP messages to be at least
>> checked against the list of known connections, so that successfully
>> mounting this attack required the  packet to correspond to ports that
>> are in use. (Usually unknown to an off-path attacker).
>
> Agreed - but IMO this has nothing to do with "encapsulation" or
> tunneling, AFAICT.
>
Yes. This simply to do wth input processing by the PMTUD routine.

>>
>>>>>>
>>>>>> Moreover, other layers view ICMP messages with suspicion and have
>>>>>> long
>>>>>> noted the need to check ICMP payload and match only packets that
>>>>>> relate to actual 5-tuples in use (effectively reducing vulnerability
>>>>>> to off-path attacks). For example, the Guidelines for UDP,
>>>>>> rfc5405bis,
>>>>>> state:
>>>>>>
>>>>>> " Applications SHOULD appropriately validate the payload of ICMP
>>>>>>    messages to ensure these are received in response to transmitted
>>>>>>    traffic (i.e., a reported error condition that corresponds to a
>>>>>> UDP
>>>>>>    datagram actually sent by the application). …“
>>>>
>>>> The comment below could easily be handled by something that clearly
>>>> indicates the problem and points to the tunnel draft for guidance, I
>>>> agree no need to go into algorithms/methods here.
>>>
>>> The problem isn't unique to tunnels - it happens on any link whose MTU
>>> can vary, and IMO the solution is the same. React to the change in
>>> subsequent traffic, rather than attempting to rely in ICMP relaying from
>>> signaling inside the link layer -- regardless of that link layer.
>>>
>>> Joe
>>>
>> I'd be fine with recommending that way of working - but if the host
>> reacts to ICMP, it is important to try to verify ICMPv6 messages
>> before accepting them.
>
> I think that's a fine punchline. The key is what "verification" means -
> as you note, a transport connection might not want to react to
> conflicting information and no entity (transport, OS, etc.) ought to
> react to nonsensical info (attempts to push MTU below required minimums).
>
> Joe
>

Gorry


From nobody Thu Feb 16 10:27:04 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3F8127077 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 10:27:02 -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 autolearn_force=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 pdGAVAeTbRSP for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 10:27:00 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F8641296A2 for <ietf@ietf.org>; Thu, 16 Feb 2017 10:26:30 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 51E1D282D54 for <ietf@ietf.org>; Thu, 16 Feb 2017 18:26:29 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com>
Date: Thu, 16 Feb 2017 13:26:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4XMlLehfKRXKLRV9_urdEYZ3y-g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:27:02 -0000

> On Feb 16, 2017, at 10:30 AM, Wei Chuang <weihaw@google.com> wrote:
>=20
>> How about if a CA with only rfc822Name constraints can't issue certs
>> with SmtpUTF8Names at all, and of course vice versa.  If you want =
both
>> kinds of names, the CA has to constrain both.
>=20
> I had asked a few folks at Google for an opinion about the name =
constraints.
> Let me post Ryan Sleevi's (CC'ed) opinion:=20
>=20
> https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg
> [the above] basically says option 3 [the acceptable approach of the =
3],
> but unfortunately suffers from 'legacy' - namely, you cannot assume =
that
> all rfc822Name clients will be updated to support SmtpUtf8Name, and =
short
> of marking it critical (which would mean its undeployable), you can't
> assume that an SmtpUtf8Name nameConstraint will constrain an =
rfc822Name.

Given that rfc822Name is a well-known legacy element, while SmtpUtf8Name
is a novel element, the prescription can be asymmetric.  Specifically,
all that's really needed (in the simpler model proposed by John) is
to disallow SmtpUtf8Name altnames when (only) rfc822Name constraints
are present.

The converse is not required, a parent CA that is SmtpUtf8Name aware
and wants to issue a child CA with SmtpUtf8Name constraints can and
should also include appropriate rfc822Name constraints that ensure
that the desired SmtpUtf8Name constraints are not bypassed via
unauthorized rfc822Name altnames.

The rfc822Name constraints can either permit only equivalent domain
names (LDH or A-label forms), or, if no rfc822Name can be compatible
with the SmtpUtf8Name constraints, permit only something like
"nouser@nodomain.invalid", thereby excluding all valid rfc822 addresses.

--=20
	Viktor.=


From nobody Thu Feb 16 10:47:44 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ADC1129615; Thu, 16 Feb 2017 10:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 gtceYG7Phd1o; Thu, 16 Feb 2017 10:47:33 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 6067E12953E; Thu, 16 Feb 2017 10:47:33 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GIkr89013536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 10:46:54 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc1981bis-04.txt> (Path MTU Discovery for IP version 6) to Internet Standard
To: gorry@erg.abdn.ac.uk
References: <148599312602.18643.4886733052828400859.idtracker@ietfa.amsl.com> <1859B1D9-9E42-4D65-98A8-7A326EDDE560@netapp.com> <f8291774-409e-2948-3b29-83dbb09d39d9@si6networks.com> <63eaf82e-b6d5-bff5-4d48-479e80ed4698@gmail.com> <2d36e28c-ee7d-20fc-3fec-54561e520691@si6networks.com> <C0A114C1-5E4A-4B8E-A408-55AF1E30873F@netapp.com> <3A5429F6-0EA6-436A-AF30-E55C9026F456@employees.org> <8cf1fe7d-bdfd-5e81-e61f-55d9ecd5d28a@isi.edu> <7E9AB9E8-3FCB-4475-BEEB-F18CFC4BC752@employees.org> <8076a1ea-182d-9cbe-f954-3e50f0fc53d9@isi.edu> <E11F9A4D-DE9E-4BFD-8D0D-252842719FC5@employees.org> <619f0dc52a514f07a70b44126aeb66f3@XCH15-06-08.nw.nos.boeing.com> <da3de0a5-fe7f-c874-db1d-da2684619213@si6networks.com> <706163b815ef439bbd9e0a17eba83512@XCH15-06-08.nw.nos.boeing.com> <e201c72e-b7c1-5a5f-eacb-93896cd7a7bb@si6networks.com> <58A33D08.4090505@erg.abdn.ac.uk> <196e8c39-784a-3a25-b6ab-d7eaa664f0fa@isi.edu> <8fbc3cbd-ff2d-f2c6-ccd7-13a20c6aa5ca@erg.abdn.ac.uk>
From: Joe Touch <touch@isi.edu>
Message-ID: <935cf01c-a0f2-af0c-b60b-89ff04091eb2@isi.edu>
Date: Thu, 16 Feb 2017 10:46:52 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8fbc3cbd-ff2d-f2c6-ccd7-13a20c6aa5ca@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bJsgKKOVhhikRzbK7X2jrXjxJ7w>
Cc: "tsv-area@ietf.org" <tsv-area@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, 6man WG <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis@ietf.org" <draft-ietf-6man-rfc1981bis@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:47:35 -0000

Hi, Gorry  (et al.),


On 2/16/2017 6:04 AM, Gorry Fairhurst wrote:
> On 15/02/2017 21:25, Joe Touch wrote:
>> Hi, Gorry (et al.),
>>
>> On 2/14/2017 9:23 AM, Gorry Fairhurst wrote:
>>> There is no mention that paths including tunnels can eat ICMPv6 PTB
>>> messages on the tunnel segment, blackholing them, which prevents
>>> reaching the destination.
>>
>> Nor should there be, IMO.
>>
>> A tunnel is a link layer to the network whose packets it transits.
>>
>> ICMPs generated inside a tunnel aren't "eaten", so much as they operate
>> at a different layer for a different reason (e.g., to tune
>> ingress-egress source fragmentation of encapsulated packets).
>>
>> PTB messages inside a tunnel are (IMO) most correctly interpreted by the
>> ingress (which is an *interface* on a router or host, most correctly
>> IMO) as changing the MTU of the tunnel as a link. If that MTU change
>> affects packets that arrive later, then it would be the router where the
>> ingress is attached that would generate the ICMP, never the (ingress)
>> interface whose MTU is insufficient.
>>
>> Again, I'm in the process of updating draft-ietf-intarea-tunnels to be
>> much more clear on this point (the update should be issued in a day
>> or two).
>>
>> Joe
>>
>
> I really disagree Joe - not in what you say about how things need to
> be, nor the relevance of draft-ietf-intarea-tunnels.
>
> The point of disagreement, is that I think the text needs to explain
> enough that people do NOT blindly believe this always works. the
> current text mentions tunnels in more than one place, as if they are
> just another usage of PMTUD.
>
> Tunnels can make path MTU diiscovery unreliable, because many deployed
> tunnel ingresses do not propagate ICMPv6 PTB messages upstream to
> reflect the limits of the Tunnel MTU. 

I'll send you a preview of the updated tunnel text privately (it will be
posted in a few days). Even the last version, however, explains why
individual PTB messages should not be relayed directly upstream.

The solution is as follows: PTB messages should update the ingress's
link MTU (where the tunnel is a link and the ingress is a network
interface). Subsequent messages at a router where the ingress is
attached would already generate the correct ICMP errors when they
receive later packets that are larger than that updated MTU.

> draft-ietf-intarea-tunnels discusses how a tunnel should be
> implemented to effectively work with a Tunnel MTU.
The above is a brief summary of what it discusses.

This document doesn't need to do much on this matter at all, except NOT
provide contradictory advise or imply otherwise.

IMO, whether a tunnel works correctly or not is a tunnel issue, not an
issue for a network protocol, just as this doc shouldn't enumerate other
link layer issues, such as problems with the need for broadcast on NBMA
links, etc.

Joe


From nobody Thu Feb 16 10:50:47 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CED91294F8; Thu, 16 Feb 2017 10:50:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 MAWj4OS1eig9; Thu, 16 Feb 2017 10:50:39 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 C1BD4127077; Thu, 16 Feb 2017 10:50:39 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GIo0Ch014046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 10:50:00 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
Date: Thu, 16 Feb 2017 10:49:58 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Njb0etOA5DJ5pVvsD206VcUUJw>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 18:50:41 -0000

On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>
>
> On 14/02/2017 23:00, Templin, Fred L wrote:
>> Unless there is operational assurance of
>> some size X>1280, however, tunnels have to use fragmentation to
>> guarantee that - at a minimum - packets up to 1280 will get through.
>
> In that case there really needs to be a note about MPLS.

IMO, this doc shouldn't be discussing tunneling as any different from
any other link.

> You can fragment into an IP tunnel, but not an MPLS tunnel, because
> you cannot fragment the payload as you can in IPv4 and you cannot
> fragment MPLS.

There's no such thing as an "MPLS tunnel"; at best, it's "MPLS over X",
e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
while it can't support fragmentation it would never need it either. It
would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
needed fragmentation.  If that can't be supported, then the addition of
MPLS would just reduce the effective MTU of the MPLS-over-X link.

Joe


From nobody Thu Feb 16 11:24:11 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA54B12941A; Thu, 16 Feb 2017 11:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 PTNhGirF-sY9; Thu, 16 Feb 2017 11:24:00 -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 84900126DFB; Thu, 16 Feb 2017 11:24:00 -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 v1GJO0tx005294; Thu, 16 Feb 2017 12:24:00 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1GJNvfm005282 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 16 Feb 2017 12:23:57 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 16 Feb 2017 11:23:57 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Thu, 16 Feb 2017 11:23:56 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "otroan@employees.org" <otroan@employees.org>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSh24+W9zOXyg8P0euxl6InNxVWqFrbvcAgABkQQCAADFvEA==
Date: Thu, 16 Feb 2017 19:23:56 +0000
Message-ID: <97b167753f2446b2adebc5fee91627b4@XCH15-06-11.nw.nos.boeing.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org>
In-Reply-To: <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NM248aPDrOnZBda4D_L6mcaUQuM>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:24:03 -0000

That RFC describes motivations for /64 that are mostly superseded. I still =
think we need to wean ourselves of the quasi-stateful address notion, in IP=
v6, at least for the remaining majority of the address space.

Bert

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of otroan@employees.org
Sent: Thursday, February 16, 2017 03:24
To: Randy Bush <randy@psg.com>
Cc: 6man WG <ipv6@ietf.org>; IETF-Discussion Discussion <ietf@ietf.org>; 6m=
an-chairs@ietf.org; draft-ietf-6man-rfc4291bis@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 A=
ddressing Architecture) to Internet Standard

Dear Randy,

>> If your statement is that we only have the 64 bit boundary because of
>> SLAAC I believe you are wrong.
>=20
> cite, please.  what else actually needs it?

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

Best regards,
Ole


From nobody Thu Feb 16 11:51:51 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 858DB12961D for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 11:51:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CdfmCvhwdaB7 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 11:51:32 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::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 E6AF3128E18 for <ietf@ietf.org>; Thu, 16 Feb 2017 11:51:30 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id c73so7745456pfb.0 for <ietf@ietf.org>; Thu, 16 Feb 2017 11:51:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=uLTwTkxoI3WTvZ2Sk7r0Il0AJX4UbfE4l80cFZtoFW4=; b=AY2YY6TyvEssYP8HYHsHVB0bg0wQL0y3a95YaDm/cc34STg/D5GqDcZ6tD7LUeWM2U h28bTBGMNCAgRGsg9SLUWq/J0KY30EjZ3FYD92VKFG6HS2GvthkWa2ZKscM6Yfh0Tv6O NvapJETFpDJwTT0gya3DDokuGt0ns8NF3xW+Al4v95N64LN6DTDtdrQdBMihP5dk+9/l jmHp/XddblLWpZBZ+F6XdcJnvCy34DE+wcJkRNNdPVz9QMAzMoym2IOQxA61ls524GjU mGO0vUwCW0Gh2yRY9Stp4ma8DuO3vxtpZkh8ozRDKfvKLz/+KtcCJbM9bsFaEIMyNZML f3pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=uLTwTkxoI3WTvZ2Sk7r0Il0AJX4UbfE4l80cFZtoFW4=; b=iPDKEqC2GIdjyuBuk67nGAbXERL7W/GGHiiGTf6uiZG/YyiqVjhyjb7wDMt9gqN6Zd 6NL/stbTZM6OthSvEt3Vm9geAvYRpB44tyNM8ZnqARLck0sH4NnBnl6YvwL7yQkJW08n fNW1/8z9Gmfzc+aRDFzBb+q7xR1EznMXFH1PTnlCweQC+apVKvVBq4hhT7TMjVbwRjRd k7iKLbfxIrPXvM1BsEK2l8o6zh6RBeymBW8qkulqd1a9nVAc7jSrlp/GptpaZXZUcF6G XJpjjWJ4ZbQHpiaP4QOQ14Lx6itjKHwr+hBxAmM4gvhgVYwQrPzGlFrmHrEG7D6hbe62 IIgA==
X-Gm-Message-State: AMke39kySuBGfy5FrbpWVbHP5qiYkWyq4POeElhEn9Td/K5ZOxfL6Wmji7MHulMA93oGd45a
X-Received: by 10.99.121.72 with SMTP id u69mr4875946pgc.207.1487274690157; Thu, 16 Feb 2017 11:51:30 -0800 (PST)
Received: from [100.107.14.163] ([100.107.14.163]) by smtp.gmail.com with ESMTPSA id 67sm15087863pfd.120.2017.02.16.11.51.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 11:51:29 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <1EB5A669-2B68-40C7-B470-453C83DD88E7@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_51A2306B-29AD-440D-9AA0-3BD32C1AFFD7"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 11:51:33 -0800
In-Reply-To: <m2lgt6ed7j.wl-randy@psg.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cwLNZrduuFtvXEldwpHqDGMp4xw>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:51:33 -0000

--Apple-Mail=_51A2306B-29AD-440D-9AA0-3BD32C1AFFD7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 16, 2017, at 00:45, Randy Bush <randy@psg.com> wrote:
>=20
>>>> If your statement is that we only have the 64 bit boundary because =
of
>>>> SLAAC I believe you are wrong.
>>>=20
>>> cite, please.  what else actually needs it?
>>=20
>> https://tools.ietf.org/html/rfc7421
>=20
> that excuses it.  cite where it is actually needed to do something
> useful other than slaac.

RFC 6282 compresses IPv6 headers over IEEE 802.15.4 in a way that =
depends on such networks always having 64-bit network prefix length.

--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_51A2306B-29AD-440D-9AA0-3BD32C1AFFD7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 16, 2017, at 00:45, Randy Bush &lt;<a =
href=3D"mailto:randy@psg.com" class=3D"">randy@psg.com</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">If your statement is =
that we only have the 64 bit boundary because of<br class=3D"">SLAAC I =
believe you are wrong.<br class=3D""></blockquote><br class=3D"">cite, =
please. &nbsp;what else actually needs it?<br class=3D""></blockquote><br =
class=3D""><a href=3D"https://tools.ietf.org/html/rfc7421" =
class=3D"">https://tools.ietf.org/html/rfc7421</a><br =
class=3D""></blockquote><br class=3D"">that excuses it. &nbsp;cite where =
it is actually needed to do something<br class=3D"">useful other than =
slaac.<br class=3D""></div></div></blockquote><br =
class=3D""></div><div>RFC 6282 compresses IPv6 headers over IEEE =
802.15.4 in a way that depends on such networks always having 64-bit =
network prefix length.</div><br class=3D""><div class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_51A2306B-29AD-440D-9AA0-3BD32C1AFFD7--


From nobody Thu Feb 16 11:59:14 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB6C8128E18; Thu, 16 Feb 2017 11:59:13 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-1xR3y5oRJE; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 5FC6512941A; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 5so2784828pgj.0; Thu, 16 Feb 2017 11:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=X1cwIjUWucI+Lm+4BgQ3TByDEhr7m1fkd2WkaXLhYIQ=; b=AkwYn8LKsSaiO5Ty8DO6eGNIf5O9pkzLFnAYMkmHdvEps5uAF8xCjLSP2Sj7Bp58Fr 3rC6Q2MOlvNg8PJaU/Sx/dox11ZH/cY2POgjiE7ptV8uBIy+rNtgTPdKUddZ8Cj7gKMR I2dyA24iaFPnDKR7nw/U/JoMjcVH1326IIdgdGmHL3OWg8vxlc0Jc7LOVTCTwf3sAlnv 5DezQiaFxSBkubZhMHeX3arvkzwFdCoPtK7BJejruSkiWLWZIDRU4z+60MwdFeULJnR1 VEENyhxyjiCZ2mXS2OVd+QGBhhIipFwl0O7vfSWN6310qVZdCYPomG1dsAxXm28gHBo3 sc7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=X1cwIjUWucI+Lm+4BgQ3TByDEhr7m1fkd2WkaXLhYIQ=; b=tyGgviY2CNzzafkD9TMfKWkRzBU94q67pEPLLS4gzLWf/7gYiOkTRVVKVwSFRq4ntJ yNiB8T+wXgvkGZ7f50qlFGUqDR5YjaOHyKs+S2H4eGnXpgCkfUbU6MXQXAaRti5FwxH/ F84T8gzB/lR2dYFTxxIRjcCAE+X4qUvV5S7ZMFAXuBa+BBRt1N3RnKukfOE/8TZhxmdg fbwCwq7kD4uzLG5q36EMQq0ADApil9joT2/FFxzDSVPmEykxnSr2lPwMixSy5MlxdPvf v650dnr4L9QIzrfumQcC5hgq+0y8fxdox8dJDzgaLmpyiAVSFVIUn9UPDkrCOd9fuwqu pWqA==
X-Gm-Message-State: AMke39lwl5mKP22P5/oIFspsmfT4RaRxKo1tZJWelmbtBnVbmXlBcXDKdg1CUCYE54lzHw==
X-Received: by 10.98.70.12 with SMTP id t12mr4734944pfa.47.1487275151951; Thu, 16 Feb 2017 11:59:11 -0800 (PST)
Received: from ?IPv6:2406:e007:68c5:1:28cc:dc4c:9703:6781? ([2406:e007:68c5:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id e129sm15210411pfe.8.2017.02.16.11.59.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 11:59:11 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
Date: Fri, 17 Feb 2017 08:59:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lvHWE8diyWOVNVw_eopJ2evMMiI>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 19:59:14 -0000

On 17/02/2017 04:59, Stewart Bryant wrote:
> 
> 
> On 14/02/2017 23:00, Templin, Fred L wrote:
>> Unless there is operational assurance of
>> some size X>1280, however, tunnels have to use fragmentation to
>> guarantee that - at a minimum - packets up to 1280 will get through.
> 
> In that case there really needs to be a note about MPLS.
> 
> You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
> cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.

I'm confused. A tunnel end point that accepts IPv6 packets MUST accept packets
of 1280 bytes (or shorter) and MUST emit them. How it gets them through the
tunnel is irrelevant - if it's an ATM tunnel it has to chop them into 48 byte
fragments and re-assemble them at the other end - if it's an avian carrier tunnel
it might have to use several pigeons per packet*. None of this matters to the IPv6
nodes concerned; the physical MTU of the tunnel technology is irrelevant except
to the tunnel end points.

   Brian

*In RFC 6214, we didn't consider this, but we should have.


From nobody Thu Feb 16 12:31:30 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68132129470; Thu, 16 Feb 2017 12:31:29 -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 autolearn_force=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 SEKCOPzG_46d; Thu, 16 Feb 2017 12:31:28 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 A505212941A; Thu, 16 Feb 2017 12:31:28 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ceSi4-0004ZB-2q; Thu, 16 Feb 2017 20:31:24 +0000
Date: Fri, 17 Feb 2017 05:31:20 +0900
Message-ID: <m2wpcpdgiv.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Farmer <farmer@umn.edu>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mL7XD2WrA-YsZ1pDmn3bNNHHCdg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 20:31:29 -0000

> What I think we need is to make it clear that there are real
> exceptions to 64, and it is therefore not acceptable to embed 64 in
> code.

close.  64 is the exception; so slaac can work.

hiding the steaming classful pile in cute places around the document
only gets folk more annoyed.

randy


From nobody Thu Feb 16 12:42:47 2017
Return-Path: <sean.gillies@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8EF129698; Thu, 16 Feb 2017 12:42:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4I_5rIBJSo0V; Thu, 16 Feb 2017 12:42:41 -0800 (PST)
Received: from mail-yb0-x235.google.com (mail-yb0-x235.google.com [IPv6:2607:f8b0:4002:c09::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 0FBCF129689; Thu, 16 Feb 2017 12:42:41 -0800 (PST)
Received: by mail-yb0-x235.google.com with SMTP id 123so7553062ybe.3; Thu, 16 Feb 2017 12:42:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ASuxZAkGbgv1Fvv0r0Ypf1THu1MrCidD4ZklsSlbgjE=; b=E9EFT02VmlYze/dBS386nL0GxrdbbrENPOe0QiE9hYfgpaYS57RuBpbFt51p6uUN41 xPimhTnfgFMibtarK6jyeiT/y16z10s0ccRHTWnq7oZW2vNUEEGZrYWTGATgajJxMysg Pm6VfdrHtCbF0BSESZqVsjJC50dMUsL0xVBpllDdQ2JvwbWsArfr9VbDCgY7fXktctgT OsBMERsZCN5dZ4AdbAbKFszKqgKgDQXelYP7NDglajuAu0vLwi8quhDBGHcD+8pAfzv2 dfcoGa1s4nnnsQdyGjOUG3VAp5EakAbhM1O7ZznLQuS9Mmlh5G7A4TYW6tjoz3tdWGrB s6tQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ASuxZAkGbgv1Fvv0r0Ypf1THu1MrCidD4ZklsSlbgjE=; b=snNmbS78LM+tP1mdM2Bo8QhIVWsXe8WfWfI0SiYXZpsWmbG9jcmcMy9JQxi3Npxwn1 JxfJOUc76SekQdwUjCElNt3K2ELHACtbW6KiorEBEfGlTwyTSw3And8gwWG7T35UCM+i CUBUDlI+nX9h6DslW4umXR+5WAAdCbEBfih/3HkmRXM5NetBdxTVCQiPlvUSSJzJgB0h PuYDW9jE36pNa0cc92ewSfdUslP6+on4ZP/aP+gJHu55bM7Gi7IIf3UiKcfRJys7i6gl nsJoGqRaO9NPvYSWlQkUVVFdU5dL1FzY9rRs70zkwYeRi4NvctzR/vXInybultOs0fVk BFfQ==
X-Gm-Message-State: AMke39kd3r4UyN8YcHS1ehWsoR4o79j5NnDJ5193KkSaTE9KRSZQA68JHwZNHHeowCDdkbq4nmqVwfnhCH0Frg==
X-Received: by 10.37.115.209 with SMTP id o200mr3255549ybc.124.1487277760130;  Thu, 16 Feb 2017 12:42:40 -0800 (PST)
MIME-Version: 1.0
Received: by 10.129.198.2 with HTTP; Thu, 16 Feb 2017 12:42:39 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20170125152635.0b3013d8@elandnews.com>
References: <148408490871.22265.1577792860557400710.idtracker@ietfa.amsl.com> <6.2.5.6.2.20170125152635.0b3013d8@elandnews.com>
From: Sean Gillies <sean.gillies@gmail.com>
Date: Thu, 16 Feb 2017 21:42:39 +0100
Message-ID: <CAOodmJrPbZ3zFJNVSGO3P3QBhA3_kbL-5AWgsgYrg=wkYtMAPA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-geojson-text-sequence-03.txt> (GeoJSON Text Sequences) to Proposed Standard
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=94eb2c096fe893373d0548abd608
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Fy-NXZgDWUP8ZTOXrN6mijkplf0>
Cc: draft-ietf-geojson-text-sequence@ietf.org, ietf@ietf.org, geojson@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 20:42:42 -0000

--94eb2c096fe893373d0548abd608
Content-Type: text/plain; charset=UTF-8

On Thu, Jan 26, 2017 at 12:35 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hello,
> At 13:48 10-01-2017, The IESG wrote:
>
>> The IESG has received a request from the Geographic JSON WG (geojson) to
>> consider the following document:
>> - 'GeoJSON Text Sequences'
>>   <draft-ietf-geojson-text-sequence-03.txt> as Proposed Standard
>>
>
> Is this draft intended to be Informational or a Proposed Standard?
>
> The Abstract does not provide much information about the document.  I
> suggest using text from Section 1 to explain what the document is about.
>
> Regards,
> S. Moonesamy
>

I agree and will do so, also mentioning the new media type.

Yours,

-- 
Sean Gillies

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

<div dir=3D"ltr">On Thu, Jan 26, 2017 at 12:35 AM, S Moonesamy <span dir=3D=
"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf=
@elandsys.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<span class=3D""><br=
>
At 13:48 10-01-2017, The IESG wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The IESG has received a request from the Geographic JSON WG (geojson) to<br=
>
consider the following document:<br>
- &#39;GeoJSON Text Sequences&#39;<br>
=C2=A0 &lt;draft-ietf-geojson-text-seque<wbr>nce-03.txt&gt; as Proposed Sta=
ndard<br>
</blockquote>
<br></span>
Is this draft intended to be Informational or a Proposed Standard?<br>
<br>
The Abstract does not provide much information about the document.=C2=A0 I =
suggest using text from Section 1 to explain what the document is about.<br=
>
<br>
Regards,<br>
S. Moonesamy<br></blockquote><div><br></div><div>I agree and will do so, al=
so mentioning the new media type.<br><br></div><div>Yours,<br></div><div><b=
r></div></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmail=
_signature">Sean Gillies</div>
</div></div>

--94eb2c096fe893373d0548abd608--


From nobody Thu Feb 16 12:53:27 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A317129689; Thu, 16 Feb 2017 12:53:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id el8IBdVekiwU; Thu, 16 Feb 2017 12:53:24 -0800 (PST)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 35B9912966D; Thu, 16 Feb 2017 12:53:24 -0800 (PST)
Received: by mail-ua0-x22d.google.com with SMTP id y9so18832183uae.2; Thu, 16 Feb 2017 12:53:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=LisVoQITGIQzRPgLJUrJMC8+386pHkyPo6Dw6SeDDSc=; b=tzdCbru3sGjTim95EI7Zq91k0MvABvQMDsZZKylfuoBa6moJZxar0n9+vOkooH+xmN 9TV9CyLevOeJp0DAo6Ooh8AV0/+VcFTL89dg6Kgr/FHbMffwppWsvJmeZeo8CcJM95By Obe/HUqIUctPL9HhEsKBcT0hLECUeTizvyWMBdrQoLlNTKQz9thfc5aDLVnLjrxQLfub mtrh/ikYRzTmWiCtaYhEVgnfW3lJYqOEU8J33ShC8OcOd+nILo0RhaENs1WGVTJ89LzP OOVc1tIykSH/UwF7QcudP6y++dY0hTTeLFIIlRtnrNU5NiJ7QhE8z2VzkvQEYKozL/Vo WN5A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LisVoQITGIQzRPgLJUrJMC8+386pHkyPo6Dw6SeDDSc=; b=B/vKh36oNA5xjVzvVro7rn8eSY08mrMLTOI9urOvx1lUFahWtlDJyIJKl9eUnBjFip fsfpr+kLm4Fr2hqemRmDeJgVe3/bee4XKcB5e8IuSvgkngRbIYW3h4BG+4r7N1i/UEG6 PDZ+RDIVfUh6lFfVpo7pvSxuuav/HCH5393W/MUoAjykTfxayl+CKDUNXm1kaOXoX94M ruuboy+dRSMIWg48pcUGdjx5QBRfPQvmuVozt/WOKq38zoYxdoQMv71BonlyPi89Nx34 jPRF4ssdZ5hz8JoF+cN4TI5uxyGcvXrNgnEIfmiyunYrx3yAimehPWs0oQArA/CpWqtH nWbg==
X-Gm-Message-State: AMke39l2xML6ohRlZ/MrLA2nIRgc9ZCON2k9sxZqnG3wn55PToTxEQVBRt50MGbrPSUltii8RJapNriZi6R4/w==
X-Received: by 10.176.67.196 with SMTP id l62mr2180086ual.89.1487278403255; Thu, 16 Feb 2017 12:53:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Thu, 16 Feb 2017 12:52:52 -0800 (PST)
In-Reply-To: <m2wpcpdgiv.wl-randy@psg.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <m2wpcpdgiv.wl-randy@psg.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 17 Feb 2017 07:52:52 +1100
Message-ID: <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WRAL-L3g4Vk6JAikEWHQC8OUgy8>
Cc: 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 20:53:25 -0000

On 17 February 2017 at 07:31, Randy Bush <randy@psg.com> wrote:
>> What I think we need is to make it clear that there are real
>> exceptions to 64, and it is therefore not acceptable to embed 64 in
>> code.
>
> close.  64 is the exception; so slaac can work.
>
> hiding the steaming classful pile in cute places around the document
> only gets folk more annoyed.
>

So what is your objection to having a well-known addressing structure?

Objecting to it, calling it "classful", is implying that it is exactly
the same as IPv4 classful addressing. I don't think IPv6 is.

My memory of classful IPv4 addressing is that it not only specified an
addressing structure, it also specified a forwarding method based on
that structure. (e.g., the default route was only used if there
weren't any routes in the table that had the class matching the class
of the destination address.)

IPv6 doesn't. The addressing structure doesn't specify how different
bits are used during forwarding - all 128 are, using a longest match
per BCP 198.

So IPv6 specifically separates the addressing structure from the
forwarding method. I think calling that "classful" is
mischaracterising it.

Regards,
Mark.


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


From nobody Thu Feb 16 12:55:39 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1872212943B; Thu, 16 Feb 2017 12:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 ivaCMy6YKV2j; Thu, 16 Feb 2017 12:55:34 -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 CB157129426; Thu, 16 Feb 2017 12:55:34 -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 v1GKtYS5004944; Thu, 16 Feb 2017 13:55:34 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1GKtRPL004750 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 16 Feb 2017 13:55:27 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 16 Feb 2017 12:55:26 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Thu, 16 Feb 2017 12:55:27 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: james woodyatt <jhw@google.com>, IETF-Discussion Discussion <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSh24+W9zOXyg8P0euxl6InNxVWqFrbvcAgABkQQCAAAYJAIAAuiSA//+Jk1A=
Date: Thu, 16 Feb 2017 20:55:27 +0000
Message-ID: <e4bcf222666d46dfaa3fdbcc8ab58d8d@XCH15-06-11.nw.nos.boeing.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <1EB5A669-2B68-40C7-B470-453C83DD88E7@google.com>
In-Reply-To: <1EB5A669-2B68-40C7-B470-453C83DD88E7@google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_e4bcf222666d46dfaa3fdbcc8ab58d8dXCH150611nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qLPL_FlxbI3VV8K-a_rHqGOnKeE>
Cc: 6man WG <ipv6@ietf.org>, "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 20:55:38 -0000

--_000_e4bcf222666d46dfaa3fdbcc8ab58d8dXCH150611nwnosboeingcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

My response to IEEE 802.15.4 would then be, but you can't assume that this =
same IPv6 header compression algorithm can be used in the unassigned IPv6 a=
ddress space.

The message has to be clear. I think all the niggling objections make matte=
rs worse, for the future, in which future we will discover that the egregio=
us waste caused by prefixes <=3D 64 bits creates a need for another IP vers=
ion. The assumption that 64-bit prefixes are more than enough can become in=
valid in nit time, e.g. with IoT device that require multiple internal subn=
ets.

Bert


From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of james woodyatt
Sent: Thursday, February 16, 2017 14:52
To: IETF-Discussion Discussion <ietf@ietf.org>
Cc: draft-ietf-6man-rfc4291bis@ietf.org; 6man WG <ipv6@ietf.org>; 6man-chai=
rs@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 A=
ddressing Architecture) to Internet Standard

On Feb 16, 2017, at 00:45, Randy Bush <randy@psg.com<mailto:randy@psg.com>>=
 wrote:

If your statement is that we only have the 64 bit boundary because of
SLAAC I believe you are wrong.

cite, please.  what else actually needs it?

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

that excuses it.  cite where it is actually needed to do something
useful other than slaac.

RFC 6282 compresses IPv6 headers over IEEE 802.15.4 in a way that depends o=
n such networks always having 64-bit network prefix length.

--james woodyatt <jhw@google.com<mailto:jhw@google.com>>




--_000_e4bcf222666d46dfaa3fdbcc8ab58d8dXCH150611nwnosboeingcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Times New Roman",serif;
	color:#0E25D0;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">My re=
sponse to IEEE 802.15.4 would then be, but you can&#8217;t assume that this=
 same IPv6 header compression algorithm can be used in the unassigned IPv6 =
address space.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">The m=
essage has to be clear. I think all the niggling objections make matters wo=
rse, for the future, in which future we will discover that the egregious wa=
ste caused by prefixes &lt;=3D 64 bits creates
 a need for another IP version. The assumption that 64-bit prefixes are mor=
e than enough can become invalid in nit time, e.g. with IoT device that req=
uire multiple internal subnets.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0">Bert<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0E25D0"><o:p>=
&nbsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> ipv6 [mailto:ipv6-bounces@ietf=
.org]
<b>On Behalf Of </b>james woodyatt<br>
<b>Sent:</b> Thursday, February 16, 2017 14:52<br>
<b>To:</b> IETF-Discussion Discussion &lt;ietf@ietf.org&gt;<br>
<b>Cc:</b> draft-ietf-6man-rfc4291bis@ietf.org; 6man WG &lt;ipv6@ietf.org&g=
t;; 6man-chairs@ietf.org<br>
<b>Subject:</b> Re: Last Call: &lt;draft-ietf-6man-rfc4291bis-07.txt&gt; (I=
P Version 6 Addressing Architecture) to Internet Standard<o:p></o:p></span>=
</p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">On Feb 16, 2017, at 00:45, Randy Bush &lt;<a href=3D=
"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote:<o:p></o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">If your statement is that we only have the 64 bit bo=
undary because of<br>
SLAAC I believe you are wrong.<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
cite, please. &nbsp;what else actually needs it?<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
<a href=3D"https://tools.ietf.org/html/rfc7421">https://tools.ietf.org/html=
/rfc7421</a><o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal"><br>
that excuses it. &nbsp;cite where it is actually needed to do something<br>
useful other than slaac.<o:p></o:p></p>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">RFC 6282 compresses IPv6 headers over IEEE 802.15.4 =
in a way that depends on such networks always having 64-bit network prefix =
length.<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">--james woodyatt &lt;<a href=3D"mailto:jhw@google.co=
m">jhw@google.com</a>&gt;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_e4bcf222666d46dfaa3fdbcc8ab58d8dXCH150611nwnosboeingcom_--


From nobody Thu Feb 16 13:10:58 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C781296DF; Thu, 16 Feb 2017 13:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 OrWqTj9udy46; Thu, 16 Feb 2017 13:10:31 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 22B001296A6; Thu, 16 Feb 2017 13:10:31 -0800 (PST)
Received: from [128.9.160.81] (nib.isi.edu [128.9.160.81]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1GL9fQK017392 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 13:09:42 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <9f298dea-88c9-3784-c87e-d33384fe8308@isi.edu>
Date: Thu, 16 Feb 2017 13:09:40 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <c65c6582-c874-9352-89cb-24c882c0516e@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3x3yC_sYomudC8SoByfzl5PCuSA>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:10:35 -0000

On 2/16/2017 11:59 AM, Brian E Carpenter wrote:
> On 17/02/2017 04:59, Stewart Bryant wrote:
>>
>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>> Unless there is operational assurance of
>>> some size X>1280, however, tunnels have to use fragmentation to
>>> guarantee that - at a minimum - packets up to 1280 will get through.
>> In that case there really needs to be a note about MPLS.
>>
>> You can fragment into an IP tunnel, but not an MPLS tunnel, because you 
>> cannot fragment the payload as you can in IPv4 and you cannot fragment MPLS.
> I'm confused. A tunnel end point that accepts IPv6 packets MUST accept packets
> of 1280 bytes (or shorter) and MUST emit them. How it gets them through the
> tunnel is irrelevant - if it's an ATM tunnel it has to chop them into 48 byte
> fragments and re-assemble them at the other end - if it's an avian carrier tunnel
> it might have to use several pigeons per packet*. None of this matters to the IPv6
> nodes concerned; the physical MTU of the tunnel technology is irrelevant except
> to the tunnel end points.
There are too many systems that try to optimize the link MTU to
represent the size of the payload of the link source, rather than the
reassembly limit of the link receiver.

It's trying to make PMTUD work multiple layers down rather than stopping
at the IP layer (which I think is where it should stop).

Joe


From nobody Thu Feb 16 13:12:44 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1B3B1296D3; Thu, 16 Feb 2017 13:12:30 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X73PFEC95euy; Thu, 16 Feb 2017 13:12:29 -0800 (PST)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::241]) (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 6AC311296C7; Thu, 16 Feb 2017 13:12:27 -0800 (PST)
Received: by mail-pg0-x241.google.com with SMTP id v184so2924961pgv.1; Thu, 16 Feb 2017 13:12:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g/NYos7tZtO9Y54BH1qYzZUB4TXV3j/LzDwDyJF0V0U=; b=ObquKpVMUcso7arGmXEGDLNr6eceVIJ7/RpuMxu/TCPBcyEhNwGjwxNxzappOBPQ1p T25m9jh3RdxxN9yWeaTvyyUKSs58KyV6tRoY+JWQJaN1huuj96+3fzv7QKlUZ9m1X397 W4ynzQwjoX73IyHGJmtl+JtBv7WCUGz8ZEkrmA6cfiU8WQIoUahoPdz9ldvfKO7Tr+V+ wipYh50I8DuyXegV/xbPYLSIteSlBjthGrypHl7CSISGDF145f355ToadTpRTwEe28Q5 SUjShoMFt5UcDhko6JptVnAAuqhgqlgUZ2PNVk9nWGnghfu1W7ud/MHasE/x5isE9jsZ bf4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g/NYos7tZtO9Y54BH1qYzZUB4TXV3j/LzDwDyJF0V0U=; b=a9cMUXf9o0giv2AEyDe0B+vA6xBBPURRqYh5ViLMGlPddFfPSB8IT5Xq84YGArx5qN +RypWcV1rRBrrdV0ok72eQej4CbXiafHQBy9GUer5uEyeW5nC5kEGI1kqZjXz5c/9XJq tovSr/IIuiT+mSscYzuPUwgor3i2rEOoPcB7d65xQdRT7S+kF02DK8m5pz0K/Qr/rw8t 5mz+MK7y4JJkcyQqTcpUlUKLy8KOvGbxz/yhGfWSG+dFrfWHeqExVTk3WRbZiQ7lV3Pt zdFx8BZuGtizToOKvHIFsjfqBZU+c98Cr45vKbm2DqmIDf6pAD4qnopoVws2pP73Q5Gr cDPA==
X-Gm-Message-State: AMke39kmGmaLKQ/L5c5FSmzrJcLLIUuDEKUMbE10Tn2C7yaMSjaRkJfiJadPt5rg0ukoTg==
X-Received: by 10.84.143.195 with SMTP id 61mr6056003plz.46.1487279547026; Thu, 16 Feb 2017 13:12:27 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id q22sm15241478pfj.77.2017.02.16.13.12.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 13:12:25 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
Date: Thu, 16 Feb 2017 13:12:28 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8FC1E12D-506D-428B-ABDD-ED260428CA08@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <m2wpcpdgiv.wl-randy@psg.com> <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>, Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yl6xGCkEDUSh74D5jPGweebG3Z4>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:12:30 -0000

On Feb 16, 2017, at 12:52 PM, Mark Smith <markzzzsmith@gmail.com> wrote:
> So what is your objection to having a well-known addressing structure?

I think the big problem is that it's well-known except when it isn't. We =
don't always have a 64 bit IID; we explicitly allow for prefixes like =
/127 (RFC 6164) etc in certain cases. It's a CIDR prefix (RFC 7608), =
meaning that prefixes in routing can be any length that makes sense =
operationally. 7608 was written in large part to advise chip vendors =
that prefix lengths longer than /64 needed to be OK.

So it isn't so very well-known. The 64 bit IID is a convention, not hard =
and fast. I would differ from Randy's characterization because of the =
kernel truth of RFC 7608, and with yours for the same reason.

And we seem to repeat this debate periodically. It gets boring.=


From nobody Thu Feb 16 13:24:58 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88B21296B1; Thu, 16 Feb 2017 13:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tmt7XuhegOCv; Thu, 16 Feb 2017 13:24:56 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 75F0A1296A4; Thu, 16 Feb 2017 13:24:55 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 16 Feb 2017 21:24:55 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 3113BD788B; Thu, 16 Feb 2017 13:24:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=57220XjCG3ryLCZNkzd4NG7G63k=; b= DjEQOjo9Zwq8hdSy4dVCl7ulRqkGKs7Lovaollw5LZwZA+84Sk+2DfSD6zy8c41+ PW2+kHerjVppIBlSr8rmN50rYUth18PiExu+BUk7K8XTwu/iZn4TIWKQqqtdpPRi TB4jzZwhkb+mqxS1XB/DK4a5JSJSUg3rYI734rTvyfs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=JivpXA1ykGRAHoQ1zVDm4C+ 1HzYRBI8AkDc6zG63lkC0PrdfDBoeOtFV+mbx25vnBOUqey9c4QCN2D2o6yL4ac4 hP2/1U2q+ZWnoLRqSuZUyCDsFoPz2QNt9X9GhkUmdEjtLTizJqcv7wF7SFjaMcbb RnGAaEGwJ5bTnYbfM8k0=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id B040CD788A; Thu, 16 Feb 2017 13:24:54 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id EE68A8BE0D6B; Thu, 16 Feb 2017 22:25:07 +0100 (CET)
From: otroan@employees.org
Message-Id: <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_23943D9E-475B-479C-864D-8EF10855354C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 22:25:06 +0100
In-Reply-To: <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MdpSLoUZTaKd8cK81S-4L1uryYg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:24:58 -0000

--Apple-Mail=_23943D9E-475B-479C-864D-8EF10855354C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

David,

[...]

> How do we move forward? What I think we need is to make it clear that =
there are real exceptions to 64, and it is therefore not acceptable to =
embed 64 in code.  The historic exception of addresses that start with =
000 has been too amorphous, no one thinks it real. I've provided two =
exception that are clearly based on current standards track work, but I =
fear that still isn't enough.  I fear some will still embed 64 and just =
add code for the exceptions, if it's even really needed.
>=20
> Can you help me find something a little more?

I have run out of ideas. :-)

The challenge is to find text that enforces the 64-bit boundary policy =
(ignoring the technical arguments for a moment), and at the same time =
ensures implementors do the right thing and make their code handle any =
prefix length. Of course these are interdependent and doing the latter =
makes it harder to enforce the first.

> What about an additional exception for manual configuration?

It's an architecture document. It should draw the big lines.
I don't think it should list exceptions, perhaps not even the 6164 one.

Learn to live with it?

(And I promise not to mention host-routes aka addresses with a /128 and =
interface-id length of 0.) :-)

Best regards,
Ole




--Apple-Mail=_23943D9E-475B-479C-864D-8EF10855354C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYphizAAoJEL7aWKiYQt92iaoP/2nXbL101p5wnRQYNoWRriPo
NrCkncuz5wQUizw84C7VCYfX3d7HSTbsbuv9Fmu3I6nMuBNmQwdYwQT0NcCyR7eC
hdlEWA9t/TfQCxfn+peVL9o2/fOycz1na6t5bUwH6T5LlSnjTzmFgWZESFFT0+6W
oV/Cug4wmGxwAQjhOI98AjrER596PH+bv3aTFTlFerfuyj+DVSLAOczDoq2/1C7w
HzVAsunAY2IcTTIyS8Jb4v4Jz8var10ToxOUIqt90TTAa8pwrpuZ68lEjqRd5jT+
eKtL81208QvtbYZD2ySZIFZCJtu20SxzNfG/guiT0+JoIm7iEMjcy4sWT3qpTnLw
S7vxis86iVZIZ1Y/BqK3jKW2u0jEjQG7oS68uwubfnxDkvDIvqIYjmhFzpIVJKLC
MDtWYVXLG7kE4erTrIjVq8k93T6lV2gKE6xef3MQhPepfiYiLarFWf91KNUvfGAV
6o8ilHf4pa5pHFFcLennPQAih16F7PrNwQJdgTNolQLQE7BaDJWgi0DfEfIbYOe9
mYokuHygYu2u1tPEAyjTwvo+NTfelefcP3MP8idOXKIeuAEJnX4pGcumRgdvrncT
rcfN7dxJsnQtT7IFzVZJPLVj3gk7NtswNNer8T41DoSTA47chljIibuWSQqVrkXA
zVz/bUGFICCSaIdV9cIA
=A/cT
-----END PGP SIGNATURE-----

--Apple-Mail=_23943D9E-475B-479C-864D-8EF10855354C--


From nobody Thu Feb 16 13:29:14 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5A71296E9; Thu, 16 Feb 2017 13:29:08 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCYJ35XzrAJz; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
Received: from mail-wm0-x242.google.com (mail-wm0-x242.google.com [IPv6:2a00:1450:400c:c09::242]) (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 8D423129541; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
Received: by mail-wm0-x242.google.com with SMTP id r18so4991354wmd.3; Thu, 16 Feb 2017 13:29:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=J1iz2LwaFavlvtuubgS3GA1kYV5QHMrJzw/sHBW46M0=; b=tlgU1Q9TsgAl2F1UfRetAlDfvJ0b9eGU64N4Q3nyLRgok2qURIYFZJKPnTKcLVW2VN kJkNpMmtQzfEfkQFXmGjAFGJHBUXG7ezujTyD7/Pl3o8ilmETGeTXxyB3jQpX938RStM rJZNmYL9ajHktG4+vV9oHmbqr14CPN4EFak4hvfKH6WpC7rF5m5h3QNBykwgDKoQqGcw Gxze/5130JjjPw5QO4g68Qvem8gGAU63e6VT9n/uqRgxC4+hRf4sWsvP9KkGIvFBPgxb HCWX2tQYKQIlrWmotcTelGfAhWQlPqq+W1rO2O6qbnZmKeLpZGQFHOrwz82SA4tqEAlX ovbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=J1iz2LwaFavlvtuubgS3GA1kYV5QHMrJzw/sHBW46M0=; b=FWtB+SYXRCG/joB6R5dZv3j0B0xsb089kCYmH872Gv/1O3N+g/Qx2+IWGmpzmgV7Ld 0/iV6Ga4+3NiQ+3HCXo+6/ORgJkPdqrIiw2SSXXWFoVzsGxQx35wo9bLJNiQVHzx6j4P FsKJLNtX2+6n1AH3a3DDYlVr8dFFeddUYhhWJFVLog/HjiH3nXU4BWJV1CzDp6viZNJW G8bkfM64xRLgwo5lPoPOce3xbN/FfM76esQt21Gt7k3AnjNWuv7IYzilMUYV3lLbsqC5 SQpZFjBN4nwVSAq7F2i4/+CfD0BsZGBUqELbfGb6ndZsd7K86w+Uz7vyft0/60vCWIvT 1n6w==
X-Gm-Message-State: AMke39kdyrRU2wvcNNlH860ZKj4uZJS2gKnh0jNNwzVhE+UFSu93Pvll5aH89JPHS0Iygw==
X-Received: by 10.28.11.83 with SMTP id 80mr4280124wml.71.1487280543693; Thu, 16 Feb 2017 13:29:03 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id d29sm1702337wmi.19.2017.02.16.13.29.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 13:29:03 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Joe Touch <touch@isi.edu>, "Templin, Fred L" <Fred.L.Templin@boeing.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
Date: Thu, 16 Feb 2017 21:29:02 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rrgmFzBxF8tqrC54o_KNfyyfRDE>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:29:08 -0000

On 16/02/2017 18:49, Joe Touch wrote:
>
> On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>>
>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>> Unless there is operational assurance of
>>> some size X>1280, however, tunnels have to use fragmentation to
>>> guarantee that - at a minimum - packets up to 1280 will get through.
>> In that case there really needs to be a note about MPLS.
> IMO, this doc shouldn't be discussing tunneling as any different from
> any other link.
>
>> You can fragment into an IP tunnel, but not an MPLS tunnel, because
>> you cannot fragment the payload as you can in IPv4 and you cannot
>> fragment MPLS.
> There's no such thing as an "MPLS tunnel";

In the MPLS world an "MPLS tunnel" is a common name for an MPLS LSP that
is used to carry some payload such as IP.

> at best, it's "MPLS over X",
> e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
> while it can't support fragmentation it would never need it either. It
> would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
> needed fragmentation.  If that can't be supported, then the addition of
> MPLS would just reduce the effective MTU of the MPLS-over-X link.

It was of course IPv6 over MPLS that concerned me.

S

>
> Joe


From nobody Thu Feb 16 13:43:24 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B418129629; Thu, 16 Feb 2017 13:43:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 S3zi_UkbCitB; Thu, 16 Feb 2017 13:43:13 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (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 0ADF512967D; Thu, 16 Feb 2017 13:43:13 -0800 (PST)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v1GLggFI007094 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 13:42:42 -0800 (PST)
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc1981bis-04
To: Stewart Bryant <stewart.bryant@gmail.com>, "Templin, Fred L" <Fred.L.Templin@boeing.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148665359396.20513.9749548375095869760.idtracker@ietfa.amsl.com> <2997d33f-3884-7831-50ed-1713c93b3867@gmail.com> <b9dfd941-0eba-c257-fef4-2f5e6bbd82a8@gmail.com> <078b28a9a26540da9e4caaba4c436cd3@XCH15-06-08.nw.nos.boeing.com> <440c60d3-0687-c7f1-f8b6-19620e6f618a@gmail.com> <6cb665e0a2244dae93e1b5b91bd9495a@XCH15-06-08.nw.nos.boeing.com> <fce8c0ef-25b7-9ba7-a5bf-9b5d7f2b19fc@gmail.com> <f4f81574e09e45169438d39afeb83369@XCH15-06-08.nw.nos.boeing.com> <1fb9a3ad-19e5-0b35-d15a-e74fed88bb8b@gmail.com> <cb03ceda3ecb4241ad867302a3195bf4@XCH15-06-08.nw.nos.boeing.com> <01055a07-c5b6-b9c2-f953-ad6aa45de511@gmail.com> <e6176571-2ff9-dd63-11b3-c713d61eebe2@isi.edu> <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <f2e2972e-04ca-ca9c-91e1-b12f816c9380@isi.edu>
Date: Thu, 16 Feb 2017 13:42:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <4c6539a9-75d1-81b8-be1e-5f5b26c10750@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h9EV4VkGu83QUuPsE7LqoUbgLb4>
Cc: "ipv6@ietf.org" <ipv6@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-6man-rfc1981bis.all@ietf.org" <draft-ietf-6man-rfc1981bis.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 21:43:14 -0000

On 2/16/2017 1:29 PM, Stewart Bryant wrote:
>
>
> On 16/02/2017 18:49, Joe Touch wrote:
>>
>> On 2/16/2017 7:59 AM, Stewart Bryant wrote:
>>>
>>> On 14/02/2017 23:00, Templin, Fred L wrote:
>>>> Unless there is operational assurance of
>>>> some size X>1280, however, tunnels have to use fragmentation to
>>>> guarantee that - at a minimum - packets up to 1280 will get through.
>>> In that case there really needs to be a note about MPLS.
>> IMO, this doc shouldn't be discussing tunneling as any different from
>> any other link.
>>
>>> You can fragment into an IP tunnel, but not an MPLS tunnel, because
>>> you cannot fragment the payload as you can in IPv4 and you cannot
>>> fragment MPLS.
>> There's no such thing as an "MPLS tunnel";
>
> In the MPLS world an "MPLS tunnel" is a common name for an MPLS LSP that
> is used to carry some payload such as IP.

MPLS just adds the label tags; there's no length field.  It's only a
tunnel when it goes over some other encapsulation layer, e.g., IP or
Ethernet.

>
>> at best, it's "MPLS over X",
>> e.g., MPLS over ethernet. MPLS doesn't indicate a message length so
>> while it can't support fragmentation it would never need it either. It
>> would be the next layer down (e.g., Ethernet, ATM, etc.) that might have
>> needed fragmentation.  If that can't be supported, then the addition of
>> MPLS would just reduce the effective MTU of the MPLS-over-X link.
>
> It was of course IPv6 over MPLS that concerned me.

IPv6 over MPLS isn't yet a tunnel. It would be IPv6 over MPLS over IPv6,
presumably (IPv6 over IPv4 isn't guaranteed to work because IPv4 EMTU_R
is only 576, and for an IPv6 tunnel it would be required to be at least
1280+encaps).

An IPv6 packet can traverse an IPv6 over MPLS over Ethernet tunnel (with
a 1500B payload) as long as the MPLS headers are smaller than 1500-1280
bytes.

An IPv6 packet can traverse an IPv6 over MPLS over IPv6 tunnel as long
as the MPLS + added IPv6 headers are smaller than 1500-1280 bytes.
However, if the arriving (transit) packet is larger than
1280-MPLS-IPv6ecaps, the MPLS tunnel ingress would need to do source
fragmentation inside the tunnel (with the egress doing reassembly).

Again, all these cases are discussed in draft-ietf-intarea-tunnels but
none have relevance IMO to this doc.

Joe


From nobody Thu Feb 16 14:09:58 2017
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5DD5129556; Thu, 16 Feb 2017 14:09:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 FVPAFdHBBJn4; Thu, 16 Feb 2017 14:09:54 -0800 (PST)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CF24129577; Thu, 16 Feb 2017 14:09:50 -0800 (PST)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1GM9nea007202; Thu, 16 Feb 2017 22:09:49 GMT
Received: from 950129200 ([176.241.251.4]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id v1GM9jD5007182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Feb 2017 22:09:47 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <148711263433.10090.8026814862201890553.idtracker@ietfa.amsl.com>
In-Reply-To: <148711263433.10090.8026814862201890553.idtracker@ietfa.amsl.com>
Subject: RE: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP Extensions for Stateful PCE) to Proposed Standard
Date: Thu, 16 Feb 2017 22:09:44 -0000
Message-ID: <0a3201d288a1$632ecf50$298c6df0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFxcgmRJRd+l0rmBvxaEPG5ui9ti6IuXg9w
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1679-8.1.0.1062-22890.003
X-TM-AS-Result: No--14.227-10.0-31-10
X-imss-scan-details: No--14.227-10.0-31-10
X-TMASE-MatchedRID: oCj5caaCQylfsB4HYR80ZggKAWhuC2ojb6bRSg4rpzvFJnEpmt9OE7k7 olbm2XYLL81jVSVU6+jAOFrAqMIwbNNvenzH/Dobr3X9gdfSLWUZKp0SZ4P+dSG8WMGwsRk0Kwz QglsQcHCsS77HibGxYdUkJMc7dlaf7bzFTf/STMpKTcBICU/vrXidToq2MMwDMTjIm0ynmGvEa7 47xSk2sfuZKsxDJQosKuNEza0pRs393AFKImnqn0hEDfw/93BuU2a5TLPrk1hct5jgLX72gKyJj slvt/ymnCy4x1pCAZWlWEq/lM4/aYaw96TXEsdWRsqQuQlRTh/4uJ1REX4MHfgnJH5vm2+gWA8c OQSmFM/V2P57aWVEz858tPB+L01c93MHmdSMa+tor4yxPAz7Wcx5q78WvFJkNOnYXKcDRxAH+7V 9+L9KUd2abg/+z3bUjufvcQiGaTaIUXxlE/cMzLiMC5wdwKqd81oVAsmRjwkLHKG+RPEVMxFG4E GBR4d4StHkUZfKYdTNHdrmQPx0Cfi/16LqVE8O8eSmTJSmEv1R3sGN+j7mNPQgoCjBjjk29kZ14 G/bCrSGGXuUR3ZPz6M0mp5DWdsD6c6GXyQATrqTEgTE0DYkgBacPYI/JssKDO+DX+rUwfY30EeC x5K2K3WVib4qoeH9Zrf0+NZ/Q01Nfs8n85Te8v7E6GNqs6ce3QfwsVk0UbtuRXh7bFKB7sQf4Ar ci9mfUL9uNj6Pv0gmsvwWWhoBuwWuOfSpyh/EaAZk0sEcY14=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OJetpQ4Ui2BY2xvJeTfql0CrEIk>
Cc: draft-ietf-pce-stateful-pce@ietf.org, pce@ietf.org, pce-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:09:56 -0000

IETF last call

I have read and commented on this document during its production by the
PCE working group. It constitutes a missing piece of the puzzle that we
started with RFC 4655.

The publication of this work as an RFC is long overdue to the point that
implementers have become confused over the last couple of years about
whether it would ever be published.

However, on re-reading this final version, I notice a few points.
Nothing major.

Thanks for the work,
Adrian

---
              
The reference to [I-D.ietf-pce-stateful-pce-app] is for some terms that
are fundamental to understanding this document.  It needs to be a 
normative reference.

---

3.1.3 has...
   Note that existing configuration tools and protocols can be used to
   set LSP state.
...which is true, but is lacking references for the inquisitive mind.

Just need some form of "(such as, ....)"

---

In the RBNF in section 6 there is some mismatch between hyphen and
underscore. Not only is there a mixture of uses, but sometime the
same construct is named in different ways (e.g., in 6.1 you have
<actual_attribute_list> and <actual_attribute-list>)

---

In 6.2, would it help show consistency with 6.1 and remove potential
confusion if

      <path>::= <intended_path><attribute-list>

read

      <path>::= <intended_path><intended-attribute-list>

---

The use of TBD in the document to flag where IANA allocations need to
be updated in the document is going to cause the RFC editor additional
work and is error prone. What you should probably do is use TBD1, TBD2,
etc. in the text and then include those flags in the IANA considerations
sections.

However (!) I note that early allocation has been done for most of the
code points. So...
- The IANA section should refer to this and ask IANA to confirm those
  allocations and update the registry to point to this document when it
  is an RFC
- The actual numbers can be filled in in place of all the TBDs
- It would help the reader/coder if you pointed forward to the new
  registries (for example, from 7.3.3 to 8.9)

---

7.3.2 Symbolic Path Name

You need to give some clues!
Is this supposed to be printable?
Is this in a particular character set?
Is it supposed to be null terminated (which would mean that if it was a
multiple of 4 octets you'd need another four octets of pad)

---

7.3.4
While 2205 is technically a good enough reference for the ERROR_SPEC
object, I wonder if the reader will automatically be aware of the
additional work on that object in 3471, 4201, and 4920.

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of The IESG
> Sent: 14 February 2017 22:51
> To: IETF-Announce
> Cc: draft-ietf-pce-stateful-pce@ietf.org; pce@ietf.org; pce-chairs@ietf.org
> Subject: [Pce] Last Call: <draft-ietf-pce-stateful-pce-18.txt> (PCEP
Extensions for
> Stateful PCE) to Proposed Standard
> 
> 
> The IESG has received a request from the Path Computation Element WG
> (pce) to consider the following document:
> - 'PCEP Extensions for Stateful PCE'
>   <draft-ietf-pce-stateful-pce-18.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-02-28. 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.


From nobody Thu Feb 16 14:21:21 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D40F1129658 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 14:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ji-oKWFLfUcd for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 14:21:18 -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 8A743129560 for <ietf@ietf.org>; Thu, 16 Feb 2017 14:21:18 -0800 (PST)
Received: by mail-pf0-x233.google.com with SMTP id 80so580247pfy.2 for <ietf@ietf.org>; Thu, 16 Feb 2017 14:21:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kheEmpcw6dfHTuKTw63Yss4BC89XLyNjEZOhyKiuGKI=; b=JmXTBJFzCAvOTQY4w1aH2QeyDHkRojxj8cLXfkC2NBdLyiKSAS+c/rIW/0Osq93V5B Y3mdJvEPa9IKkPGSZ8Iyi1nA1Kcmda65ElqtoQq9+RvTuDhd6qFATs86zTEZzUNboIRW u/AOWaQ3SOQN97wj1FuT6YbDrS+RPomZ5Zhko8z6FHC6YAwRyQPwTKjmb6bVPo7qBNAx UZQw8SCtWzfHbuVOHdvJj72UTw1mZpsYGqfojk4MMvD4VRykVNctrdYifJEis+vmI4gP nFgutu93Zkjc0jEJXa9Qoa2JlrNnIbtY1eIBBcZDwVF43KRadOos2qr0KfAFWLbS73e3 SdcQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=kheEmpcw6dfHTuKTw63Yss4BC89XLyNjEZOhyKiuGKI=; b=FKHd1zGNLDq8gXBoxXBkMNVGIMeJnM/Ge0rdrwoGx0ryfZ49NtACJ7q3dpODoTAqHP wKv27kear2H7kKooL1OrBf1nYpgA6WnP2IAshk1H3c7HP2tb8Jap4jyYTvcoqZtzLIr6 MwqBbwX2qFdNOBuWaVPiWT01sGYzOPCDiQBORh2TIdL8RSzsk4m1L32bDqLnm9JlDyD+ dbelt5w6fuYNBRnlT3Ey/eoXB64H8AyXMNUUQTZjlW5xS1Dn20wuvxMpwJT7MZhk1Uqv JHPLmuaAXYNgY4viik32EP3u4ICxn/N2ChBzip+qGjukyZvhGUsUagXXjD1Jd1KPNalm 4wDQ==
X-Gm-Message-State: AMke39mxOTGZsItCVSJ2SczXyD6fzyVrBh8NO5N0PYZv37KZe3AM+u1iUw9v/LLb19jAVZNz
X-Received: by 10.84.173.195 with SMTP id p61mr6405283plb.63.1487283678021; Thu, 16 Feb 2017 14:21:18 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id w89sm15324777pfk.133.2017.02.16.14.21.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Feb 2017 14:21:17 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_B8C728E4-78A4-4BBD-813F-498B8AB21D5B"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 16 Feb 2017 14:21:16 -0800
In-Reply-To: <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org>
To: IETF-Discussion Discussion <ietf@ietf.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x8x8wZA9BlAkpyH2R6s4ULegbng>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:21:20 -0000

--Apple-Mail=_B8C728E4-78A4-4BBD-813F-498B8AB21D5B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 16, 2017, at 13:25, otroan@employees.org wrote:
> On Feb 13, 2017, at 14:32, David Farmer <farmer@umn.edu> wrote:
>>=20
>> I have concerns with the following text;
>>=20
>>    IPv6 unicast routing is based on prefixes of any valid length up =
to
>>    128 [BCP198].  For example, [RFC6164] standardises 127 bit =
prefixes
>>    on inter-router point-to-point links. However, the Interface ID of
>>    all unicast addresses, except those that start with the binary =
value
>>    000, is required to be 64 bits long.  The rationale for the 64 bit
>>    boundary in IPv6 addresses can be found in [RFC7421]
>>=20
>> The third sentence seems to limit exceptions to 64 bit IIDs to =
exclusively addresses that start with binary vale of 000.  There are at =
least two other exceptions from standards track RFCs, that should be =
more clear accounted for in this text. [=E2=80=A6]
>=20
> [=E2=80=A6]
> The challenge is to find text that enforces the 64-bit boundary policy =
(ignoring the technical arguments for a moment), and at the same time =
ensures implementors do the right thing and make their code handle any =
prefix length. Of course these are interdependent and doing the latter =
makes it harder to enforce the first.


I propose the following:

>>> IPv6 unicast routing is based on prefixes of any valid length up to =
128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID =
of unicast addresses is generally required to be 64 bits in length, with =
exceptions only provided in special cases where expressly recognized in =
IETF standards track documents.


Trying to help out here.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_B8C728E4-78A4-4BBD-813F-498B8AB21D5B
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"">On Feb 16, 2017, at 13:25, <a =
href=3D"mailto:otroan@employees.org" class=3D"">otroan@employees.org</a> =
wrote:<br class=3D""><div><blockquote type=3D"cite" class=3D"">On Feb =
13, 2017, at 14:32, David Farmer &lt;<a href=3D"mailto:farmer@umn.edu" =
class=3D"">farmer@umn.edu</a>&gt; wrote:</blockquote><div><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D"">I have concerns with the following text;<br class=3D""><br =
class=3D"">&nbsp; &nbsp;IPv6 unicast routing is based on prefixes of any =
valid length up to<br class=3D"">&nbsp; &nbsp;128 [BCP198].&nbsp; For =
example, [RFC6164] standardises 127 bit prefixes<br class=3D"">&nbsp; =
&nbsp;on inter-router point-to-point links. However, the Interface ID =
of<br class=3D"">&nbsp; &nbsp;all unicast addresses, except those that =
start with the binary value<br class=3D"">&nbsp; &nbsp;000, is required =
to be 64 bits long.&nbsp; The rationale for the 64 bit<br =
class=3D"">&nbsp; &nbsp;boundary in IPv6 addresses can be found in =
[RFC7421]<br class=3D""></div></div></blockquote></blockquote><blockquote =
type=3D"cite" class=3D""><blockquote type=3D"cite" class=3D""><br =
class=3D""></blockquote></blockquote><blockquote type=3D"cite" =
class=3D""><blockquote type=3D"cite" class=3D"">The third sentence seems =
to limit exceptions to 64 bit IIDs to exclusively addresses that start =
with binary vale of 000.&nbsp; There are at least two other exceptions =
from standards track RFCs, that should be more clear accounted for in =
this text. [=E2=80=A6]</blockquote></blockquote><blockquote type=3D"cite" =
class=3D""><br class=3D""></blockquote><blockquote type=3D"cite" =
class=3D"">[=E2=80=A6]</blockquote></div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">The challenge is to find text =
that enforces the 64-bit boundary policy (ignoring the technical =
arguments for a moment), and at the same time ensures implementors do =
the right thing and make their code handle any prefix length. Of course =
these are interdependent and doing the latter makes it harder to enforce =
the first.<br class=3D""></div></div></blockquote></div><div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D"">I =
propose the following:</div></div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><blockquote type=3D"cite"=
 class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite"=
 class=3D"">IPv6 unicast routing is based on prefixes of any valid =
length up to 128 bits [BCP198]. However, as explained in [RFC7421], the =
Interface ID of unicast addresses is generally required to be 64 bits in =
length, with exceptions only provided in special cases where expressly =
recognized in IETF standards track =
documents.</blockquote></blockquote></blockquote></div></div><div =
class=3D""><br class=3D""></div><div class=3D"">Trying to help out =
here.</div><div class=3D""><br class=3D""></div><br class=3D""><div =
class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_B8C728E4-78A4-4BBD-813F-498B8AB21D5B--


From nobody Thu Feb 16 14:39:14 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00448129713; Thu, 16 Feb 2017 14:39:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 IkRBJEHlqMqX; Thu, 16 Feb 2017 14:39:02 -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 6F17212970A; Thu, 16 Feb 2017 14:39:02 -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 v1GMd17h062601; Thu, 16 Feb 2017 15:39:02 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1GMctUA062561 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Thu, 16 Feb 2017 15:38:55 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 16 Feb 2017 14:38:55 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Thu, 16 Feb 2017 14:38:55 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: james woodyatt <jhw@google.com>, IETF-Discussion Discussion <ietf@ietf.org>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSh24+W9zOXyg8P0euxl6InNxVWqFrbvcAgABkQQCAAAYJAIAABsyAgABcAACAAHF7AIAAD7IA//99KaA=
Date: Thu, 16 Feb 2017 22:38:55 +0000
Message-ID: <8767e370398045af989467a63747b29e@XCH15-06-11.nw.nos.boeing.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
In-Reply-To: <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_8767e370398045af989467a63747b29eXCH150611nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2EUXm-hWYqEPFbp86DWaXHvfJaA>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Feb 2017 22:39:04 -0000

--_000_8767e370398045af989467a63747b29eXCH150611nwnosboeingcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

UkZDIDc0MjEgaXMgaW5mb3JtYXRpb25hbC4gQW5kIG1hbnkgY29uc2lkZXJhdGlvbnMgYXJlIG5v
dCBzbyBjcml0aWNhbCBhbnltb3JlLCBvbiBhIHNwZWNpZmljIHN0YXRlZnVsIGZvcm1hdC4NCg0K
SSBkb27igJl0IHRoaW5rIHdlIG5lZWQgdG8gcmVpbmZvcmNlIHRoZSBub3Rpb24gdGhhdCBJUHY2
IG11c3QgaGF2ZSA2NC1iaXQgcHJlZml4ZXMsIHNpbmNlIHRoYXQgaXMgbm90IHRydWUgbm93LCBh
bmQgc2hvdWxkIG5vdCBldmVuIGJlIG1hZGUgdG8gYXBwbHkgdG8gdGhlIGN1cnJlbnRseSB1bnVz
ZWQgYWRkcmVzcyBzcGFjZS4gU28sIEnigJltIG9wcG9zZWQgdG8gdGV4dCB0aGF0IGltcGxpZXMg
YW55IHN1Y2ggcmVzdHJpY3Rpb24sIHdpdGggdGhlIGV4Y2VwdGlvbiBvZiAoYSkgY3VycmVudGx5
IHVzZWQgdW5pY2FzdCAgYWRkcmVzcyBzcGFjZSwgKGIpIFNMQUFDLCAoYykgVUxBLCBwb3NzaWJs
eSBvdGhlciBleGNlcHRpb25zLg0KDQpJbiBvdGhlciB3b3JkcywgZXhjZXB0aW9ucyBiZWxvbmcg
dG8gcmVxdWlyaW5nIHRoZSA2NC1iaXQgSUlELiBBbnkgUkZDIHRoYXQgaW1wbGllcyBvdGhlcndp
c2UsIElNTywgb3VnaHQgdG8gYmUgc3ViamVjdCB0byBhIOKAk2JpcyB2ZXJzaW9uLg0KDQpCZXJ0
DQoNCg0KRnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxm
IE9mIGphbWVzIHdvb2R5YXR0DQpTZW50OiBUaHVyc2RheSwgRmVicnVhcnkgMTYsIDIwMTcgMTc6
MjENClRvOiBJRVRGLURpc2N1c3Npb24gRGlzY3Vzc2lvbiA8aWV0ZkBpZXRmLm9yZz4NCkNjOiA2
bWFuIFdHIDxpcHY2QGlldGYub3JnPjsgZHJhZnQtaWV0Zi02bWFuLXJmYzQyOTFiaXNAaWV0Zi5v
cmc7IDZtYW4tY2hhaXJzQGlldGYub3JnDQpTdWJqZWN0OiBSZTogTGFzdCBDYWxsOiA8ZHJhZnQt
aWV0Zi02bWFuLXJmYzQyOTFiaXMtMDcudHh0PiAoSVAgVmVyc2lvbiA2IEFkZHJlc3NpbmcgQXJj
aGl0ZWN0dXJlKSB0byBJbnRlcm5ldCBTdGFuZGFyZA0KDQpPbiBGZWIgMTYsIDIwMTcsIGF0IDEz
OjI1LCBvdHJvYW5AZW1wbG95ZWVzLm9yZzxtYWlsdG86b3Ryb2FuQGVtcGxveWVlcy5vcmc+IHdy
b3RlOg0KT24gRmViIDEzLCAyMDE3LCBhdCAxNDozMiwgRGF2aWQgRmFybWVyIDxmYXJtZXJAdW1u
LmVkdTxtYWlsdG86ZmFybWVyQHVtbi5lZHU+PiB3cm90ZToNCg0KSSBoYXZlIGNvbmNlcm5zIHdp
dGggdGhlIGZvbGxvd2luZyB0ZXh0Ow0KDQogICBJUHY2IHVuaWNhc3Qgcm91dGluZyBpcyBiYXNl
ZCBvbiBwcmVmaXhlcyBvZiBhbnkgdmFsaWQgbGVuZ3RoIHVwIHRvDQogICAxMjggW0JDUDE5OF0u
ICBGb3IgZXhhbXBsZSwgW1JGQzYxNjRdIHN0YW5kYXJkaXNlcyAxMjcgYml0IHByZWZpeGVzDQog
ICBvbiBpbnRlci1yb3V0ZXIgcG9pbnQtdG8tcG9pbnQgbGlua3MuIEhvd2V2ZXIsIHRoZSBJbnRl
cmZhY2UgSUQgb2YNCiAgIGFsbCB1bmljYXN0IGFkZHJlc3NlcywgZXhjZXB0IHRob3NlIHRoYXQg
c3RhcnQgd2l0aCB0aGUgYmluYXJ5IHZhbHVlDQogICAwMDAsIGlzIHJlcXVpcmVkIHRvIGJlIDY0
IGJpdHMgbG9uZy4gIFRoZSByYXRpb25hbGUgZm9yIHRoZSA2NCBiaXQNCiAgIGJvdW5kYXJ5IGlu
IElQdjYgYWRkcmVzc2VzIGNhbiBiZSBmb3VuZCBpbiBbUkZDNzQyMV0NCg0KVGhlIHRoaXJkIHNl
bnRlbmNlIHNlZW1zIHRvIGxpbWl0IGV4Y2VwdGlvbnMgdG8gNjQgYml0IElJRHMgdG8gZXhjbHVz
aXZlbHkgYWRkcmVzc2VzIHRoYXQgc3RhcnQgd2l0aCBiaW5hcnkgdmFsZSBvZiAwMDAuICBUaGVy
ZSBhcmUgYXQgbGVhc3QgdHdvIG90aGVyIGV4Y2VwdGlvbnMgZnJvbSBzdGFuZGFyZHMgdHJhY2sg
UkZDcywgdGhhdCBzaG91bGQgYmUgbW9yZSBjbGVhciBhY2NvdW50ZWQgZm9yIGluIHRoaXMgdGV4
dC4gW+KApl0NCg0KW+KApl0NClRoZSBjaGFsbGVuZ2UgaXMgdG8gZmluZCB0ZXh0IHRoYXQgZW5m
b3JjZXMgdGhlIDY0LWJpdCBib3VuZGFyeSBwb2xpY3kgKGlnbm9yaW5nIHRoZSB0ZWNobmljYWwg
YXJndW1lbnRzIGZvciBhIG1vbWVudCksIGFuZCBhdCB0aGUgc2FtZSB0aW1lIGVuc3VyZXMgaW1w
bGVtZW50b3JzIGRvIHRoZSByaWdodCB0aGluZyBhbmQgbWFrZSB0aGVpciBjb2RlIGhhbmRsZSBh
bnkgcHJlZml4IGxlbmd0aC4gT2YgY291cnNlIHRoZXNlIGFyZSBpbnRlcmRlcGVuZGVudCBhbmQg
ZG9pbmcgdGhlIGxhdHRlciBtYWtlcyBpdCBoYXJkZXIgdG8gZW5mb3JjZSB0aGUgZmlyc3QuDQoN
CkkgcHJvcG9zZSB0aGUgZm9sbG93aW5nOg0KDQpJUHY2IHVuaWNhc3Qgcm91dGluZyBpcyBiYXNl
ZCBvbiBwcmVmaXhlcyBvZiBhbnkgdmFsaWQgbGVuZ3RoIHVwIHRvIDEyOCBiaXRzIFtCQ1AxOThd
LiBIb3dldmVyLCBhcyBleHBsYWluZWQgaW4gW1JGQzc0MjFdLCB0aGUgSW50ZXJmYWNlIElEIG9m
IHVuaWNhc3QgYWRkcmVzc2VzIGlzIGdlbmVyYWxseSByZXF1aXJlZCB0byBiZSA2NCBiaXRzIGlu
IGxlbmd0aCwgd2l0aCBleGNlcHRpb25zIG9ubHkgcHJvdmlkZWQgaW4gc3BlY2lhbCBjYXNlcyB3
aGVyZSBleHByZXNzbHkgcmVjb2duaXplZCBpbiBJRVRGIHN0YW5kYXJkcyB0cmFjayBkb2N1bWVu
dHMuDQoNClRyeWluZyB0byBoZWxwIG91dCBoZXJlLg0KDQoNCi0tamFtZXMgd29vZHlhdHQgPGpo
d0Bnb29nbGUuY29tPG1haWx0bzpqaHdAZ29vZ2xlLmNvbT4+DQoNCg0KDQo=

--_000_8767e370398045af989467a63747b29eXCH150611nwnosboeingcom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIixzZXJpZjsNCgljb2xvcjojMEUyNUQwOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglm
b250LXN0eWxlOm5vcm1hbDsNCgl0ZXh0LWRlY29yYXRpb246bm9uZSBub25lO30NCi5Nc29DaHBE
ZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7
fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBp
biAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rp
b24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1
bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzpp
ZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtl
bmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0i
cHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMEUyNUQwIj5SRkMgNzQyMSBp
cyBpbmZvcm1hdGlvbmFsLiBBbmQgbWFueSBjb25zaWRlcmF0aW9ucyBhcmUgbm90IHNvIGNyaXRp
Y2FsIGFueW1vcmUsIG9uIGEgc3BlY2lmaWMgc3RhdGVmdWwgZm9ybWF0LjxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0O2NvbG9yOiMwRTI1RDAiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2NvbG9yOiMwRTI1RDAi
PkkgZG9u4oCZdCB0aGluayB3ZSBuZWVkIHRvIHJlaW5mb3JjZSB0aGUgbm90aW9uIHRoYXQgSVB2
NiBtdXN0IGhhdmUgNjQtYml0IHByZWZpeGVzLCBzaW5jZSB0aGF0IGlzIG5vdCB0cnVlIG5vdywg
YW5kIHNob3VsZCBub3QgZXZlbiBiZSBtYWRlIHRvIGFwcGx5IHRvIHRoZSBjdXJyZW50bHkgdW51
c2VkIGFkZHJlc3Mgc3BhY2UuIFNvLA0KIEnigJltIG9wcG9zZWQgdG8gdGV4dCB0aGF0IGltcGxp
ZXMgYW55IHN1Y2ggcmVzdHJpY3Rpb24sIHdpdGggdGhlIGV4Y2VwdGlvbiBvZiAoYSkgY3VycmVu
dGx5IHVzZWQgdW5pY2FzdCAmbmJzcDthZGRyZXNzIHNwYWNlLCAoYikgU0xBQUMsIChjKSBVTEEs
IHBvc3NpYmx5IG90aGVyIGV4Y2VwdGlvbnMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBFMjVE
MCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBFMjVEMCI+SW4gb3RoZXIgd29yZHMs
DQo8Yj5leGNlcHRpb25zIGJlbG9uZyB0byByZXF1aXJpbmcgdGhlIDY0LWJpdCBJSUQ8L2I+LiBB
bnkgUkZDIHRoYXQgaW1wbGllcyBvdGhlcndpc2UsIElNTywgb3VnaHQgdG8gYmUgc3ViamVjdCB0
byBhIOKAk2JpcyB2ZXJzaW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2NvbG9yOiMwRTI1RDAiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0O2NvbG9yOiMwRTI1RDAiPkJlcnQ8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtj
b2xvcjojMEUyNUQwIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMEUyNUQwIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48
L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJy
aSZxdW90OyxzYW5zLXNlcmlmIj4gaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10N
CjxiPk9uIEJlaGFsZiBPZiA8L2I+amFtZXMgd29vZHlhdHQ8YnI+DQo8Yj5TZW50OjwvYj4gVGh1
cnNkYXksIEZlYnJ1YXJ5IDE2LCAyMDE3IDE3OjIxPGJyPg0KPGI+VG86PC9iPiBJRVRGLURpc2N1
c3Npb24gRGlzY3Vzc2lvbiAmbHQ7aWV0ZkBpZXRmLm9yZyZndDs8YnI+DQo8Yj5DYzo8L2I+IDZt
YW4gV0cgJmx0O2lwdjZAaWV0Zi5vcmcmZ3Q7OyBkcmFmdC1pZXRmLTZtYW4tcmZjNDI5MWJpc0Bp
ZXRmLm9yZzsgNm1hbi1jaGFpcnNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IExh
c3QgQ2FsbDogJmx0O2RyYWZ0LWlldGYtNm1hbi1yZmM0MjkxYmlzLTA3LnR4dCZndDsgKElQIFZl
cnNpb24gNiBBZGRyZXNzaW5nIEFyY2hpdGVjdHVyZSkgdG8gSW50ZXJuZXQgU3RhbmRhcmQ8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBGZWIgMTYsIDIw
MTcsIGF0IDEzOjI1LCA8YSBocmVmPSJtYWlsdG86b3Ryb2FuQGVtcGxveWVlcy5vcmciPg0Kb3Ry
b2FuQGVtcGxveWVlcy5vcmc8L2E+IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9j
a3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+T24gRmViIDEzLCAyMDE3LCBhdCAxNDozMiwgRGF2aWQgRmFybWVy
ICZsdDs8YSBocmVmPSJtYWlsdG86ZmFybWVyQHVtbi5lZHUiPmZhcm1lckB1bW4uZWR1PC9hPiZn
dDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2tx
dW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5JIGhhdmUgY29uY2VybnMgd2l0aCB0aGUgZm9sbG93aW5nIHRleHQ7
PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwO0lQdjYgdW5pY2FzdCByb3V0aW5nIGlzIGJhc2VkIG9u
IHByZWZpeGVzIG9mIGFueSB2YWxpZCBsZW5ndGggdXAgdG88YnI+DQombmJzcDsgJm5ic3A7MTI4
IFtCQ1AxOThdLiZuYnNwOyBGb3IgZXhhbXBsZSwgW1JGQzYxNjRdIHN0YW5kYXJkaXNlcyAxMjcg
Yml0IHByZWZpeGVzPGJyPg0KJm5ic3A7ICZuYnNwO29uIGludGVyLXJvdXRlciBwb2ludC10by1w
b2ludCBsaW5rcy4gSG93ZXZlciwgdGhlIEludGVyZmFjZSBJRCBvZjxicj4NCiZuYnNwOyAmbmJz
cDthbGwgdW5pY2FzdCBhZGRyZXNzZXMsIGV4Y2VwdCB0aG9zZSB0aGF0IHN0YXJ0IHdpdGggdGhl
IGJpbmFyeSB2YWx1ZTxicj4NCiZuYnNwOyAmbmJzcDswMDAsIGlzIHJlcXVpcmVkIHRvIGJlIDY0
IGJpdHMgbG9uZy4mbmJzcDsgVGhlIHJhdGlvbmFsZSBmb3IgdGhlIDY0IGJpdDxicj4NCiZuYnNw
OyAmbmJzcDtib3VuZGFyeSBpbiBJUHY2IGFkZHJlc3NlcyBjYW4gYmUgZm91bmQgaW4gW1JGQzc0
MjFdPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9ibG9j
a3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRv
bTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9ibG9ja3F1b3RlPg0KPC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRo
ZSB0aGlyZCBzZW50ZW5jZSBzZWVtcyB0byBsaW1pdCBleGNlcHRpb25zIHRvIDY0IGJpdCBJSURz
IHRvIGV4Y2x1c2l2ZWx5IGFkZHJlc3NlcyB0aGF0IHN0YXJ0IHdpdGggYmluYXJ5IHZhbGUgb2Yg
MDAwLiZuYnNwOyBUaGVyZSBhcmUgYXQgbGVhc3QgdHdvIG90aGVyIGV4Y2VwdGlvbnMgZnJvbSBz
dGFuZGFyZHMgdHJhY2sgUkZDcywgdGhhdCBzaG91bGQgYmUgbW9yZSBjbGVhciBhY2NvdW50ZWQg
Zm9yIGluIHRoaXMNCiB0ZXh0LiBb4oCmXTxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PC9ibG9ja3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvYmxvY2txdW90ZT4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W+KApl08bzpwPjwvbzpw
PjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10
b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlRoZSBjaGFsbGVuZ2UgaXMgdG8gZmluZCB0ZXh0IHRoYXQgZW5mb3JjZXMgdGhl
IDY0LWJpdCBib3VuZGFyeSBwb2xpY3kgKGlnbm9yaW5nIHRoZSB0ZWNobmljYWwgYXJndW1lbnRz
IGZvciBhIG1vbWVudCksIGFuZCBhdCB0aGUgc2FtZSB0aW1lIGVuc3VyZXMgaW1wbGVtZW50b3Jz
IGRvIHRoZSByaWdodCB0aGluZyBhbmQgbWFrZSB0aGVpciBjb2RlIGhhbmRsZSBhbnkgcHJlZml4
IGxlbmd0aC4gT2YgY291cnNlDQogdGhlc2UgYXJlIGludGVyZGVwZW5kZW50IGFuZCBkb2luZyB0
aGUgbGF0dGVyIG1ha2VzIGl0IGhhcmRlciB0byBlbmZvcmNlIHRoZSBmaXJzdC48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHByb3Bvc2UgdGhlIGZvbGxvd2luZzo8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8YmxvY2txdW90ZSBz
dHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+SVB2NiB1bmljYXN0IHJvdXRpbmcgaXMgYmFzZWQgb24gcHJlZml4ZXMgb2Yg
YW55IHZhbGlkIGxlbmd0aCB1cCB0byAxMjggYml0cyBbQkNQMTk4XS4gSG93ZXZlciwgYXMgZXhw
bGFpbmVkIGluIFtSRkM3NDIxXSwgdGhlIEludGVyZmFjZSBJRCBvZiB1bmljYXN0IGFkZHJlc3Nl
cyBpcyBnZW5lcmFsbHkgcmVxdWlyZWQgdG8gYmUgNjQgYml0cyBpbiBsZW5ndGgsIHdpdGggZXhj
ZXB0aW9ucyBvbmx5IHByb3ZpZGVkDQogaW4gc3BlY2lhbCBjYXNlcyB3aGVyZSBleHByZXNzbHkg
cmVjb2duaXplZCBpbiBJRVRGIHN0YW5kYXJkcyB0cmFjayBkb2N1bWVudHMuPG86cD48L286cD48
L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VHJ5aW5nIHRvIGhlbHAgb3V0
IGhlcmUuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0t
amFtZXMgd29vZHlhdHQgJmx0OzxhIGhyZWY9Im1haWx0bzpqaHdAZ29vZ2xlLmNvbSI+amh3QGdv
b2dsZS5jb208L2E+Jmd0OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_8767e370398045af989467a63747b29eXCH150611nwnosboeingcom_--


From nobody Thu Feb 16 17:22:08 2017
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8901296CA for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 17:22:07 -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_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 MMI628r3Vgjj for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 17:22:05 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 B8C28129550 for <ietf@ietf.org>; Thu, 16 Feb 2017 17:22:05 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QAYO8G5D8000F3PF@mauve.mrochek.com> for ietf@ietf.org; Thu, 16 Feb 2017 17:17:03 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QAR1CJ0NA80005AQ@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 16 Feb 2017 17:16:59 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01QAYO8E39Y40005AQ@mauve.mrochek.com>
Date: Thu, 16 Feb 2017 17:15:55 -0800 (PST)
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
In-reply-to: "Your message dated Thu, 16 Feb 2017 15:20:12 +0000" <8c81f385-7dfc-cff3-f97c-3c016fc72601@isode.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <8c81f385-7dfc-cff3-f97c-3c016fc72601@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ei9vAgWK-aZ2vvTPReh6PiAYZa0>
Cc: John C Klensin <john-ietf@jck.com>, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 01:22:07 -0000

> John and Ned,

> On 12/02/2017 20:15, John C Klensin wrote:

> > --On Wednesday, February 8, 2017 12:39 -0800 Ned Freed
> > <ned.freed@mrochek.com>  wrote:
> >
>   [snip]
> >> (2) in particular creates additional requirements that need to
> >> be explicitly called out in the charter. In particular, it's
> >> imperative that (a) It be reasonable to implement
> >> JMAP->IMAP/SUBMIT proxies, even if that constrains JMAP in
> >> ways some folks do not like, (b) The list of IMAP extensions
> >> needed to properly implement JMAP be called out, and (c) The
> >> security considerations involved in operating such a proxy
> >> need to be described in detail.

> I updated Charter text to mention these.

Good.

> > Exactly.  If one expects JMAP to be wildly successful, and
> > unless there is either a plausible plan to make all of those
> > IMAP clients go away (even if there are no new ones), I think
> > that list should include either its being reasonable to
> > implement and support IMAP/SUBMIT-> JMAP proxies or other
> > overlays or a charter requirement to discuss residual use cases
> > for IMAP.    I'm particularly concerned about supporting
> > IMAP-native clients with a JMAP-native mailstore.
> >
> >>> 2). Both are supported by the same software (i.e. Cyrus and
> >>> Dovecot use case). I doubt that incremental cost of
> >>> configuring both is much higher than just configuring one of
> >>> them.
> >>> In either case configuring JMAP clients is a simple(r)
> >>> proposition: just distribute HTTP URI for a JMAP instance.
> >>>> and to support, also for a long time, the ability to convert
> >>>> between the two formats.
> >>> There are no 2 formats, both IMAP and JMAP operate on RFC
> >>> 5322 objects, so the rest of your argument is invalid.
> >> Agreed. I have to say I really don't understand the confusion
> >> surrounding this point. IMAP has bodystructure plus a couple
> >> of other formats for returning message data, and a means of
> >> creating new messages from pieces of other messages, none of
> >> which look remotely like MIME/RFC 5322, and nobody cares.
> >>
> >> This is effectively the same thing; why should anyone care
> >> here?
> > I can't speak for anyone else, but I'm concerned about what it
> > takes to create and maintain servers and mailstores that are
> > compatible with both IMAP and JMAP.  If that means proxies, we
> > either need to address the question of IMAP proxies over JMAP
> > and JMAP mailstores as well as the JMAP over IMAP-compatible
> > ones or I'd like the charter is require a good explanation of
> > why that isn't necessary.  That might be "IMAP-based systems
> > with JMAP overlays forever", but, the more people argue that
> > JMAP will take over (rapidly or otherwise), the less plausible
> > that position feels.

> I've done some prototyping of existing JMAP proposal and I am quite
> confident that underlying models are close enough that implementing one
> on top of another is doable. IMAP+QRESYNC extension require IMAP
> mailstores to store change sequence numbers, which is required feature
> in JMAP.

I agree with the assessment, but what if the propsoal changes substantially?
That's the case I'm worried about.

				Ned


From nobody Thu Feb 16 18:31:13 2017
Return-Path: <peter416733@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D2C91297AA; Thu, 16 Feb 2017 18:31:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tzeFO1MENlrK; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
Received: from mail-ot0-x232.google.com (mail-ot0-x232.google.com [IPv6:2607:f8b0:4003:c0f::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 7BD65128B44; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
Received: by mail-ot0-x232.google.com with SMTP id k4so3649026otc.0; Thu, 16 Feb 2017 18:31:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=el0TV7Fss4KtkJo20COfFrqTMTOg84hSyPjho2dru5U=; b=c3zFCRvjpRt5Tzx3XaGYQzlC4njOiC/2ccjbc5cGKLm0RydVod9Kr1fYqx4V1+hPXT dwwvEN7B6QLELCiFpIKJR+Xpi1pV3D7n3fJKFpRKek4cIJXi7IogRJgeN1+rs3S4C8Sh hkPwEo8IMom52W7wrkvfH6a0Pe3+IwKwZoF8paNryASY1moZKgK/svPYYtf5pFThwrDR KinFOL4W3Q+140fsD6pnDYTzht+bEvj4BRL3ZCpI1o+LaUKaKu2C0gGPgXZZja7UHv60 FjRJwt7V+8sr9slj40C91y4/8E4tduitWZsbR4jDE4+Wnpiw3VeSs9+qbZ/vym/ib6B/ LMzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=el0TV7Fss4KtkJo20COfFrqTMTOg84hSyPjho2dru5U=; b=uLf1M2aU2CJbjb99o9y1blSKLjBF1W4JRhez/0tRm2S2SXdFpTMelX2jkMIq6zZg4f Q6KT2DXIt5WHH9kAqX7x9zk3jwaIN1wVyRkDfld2l3HPTJCynTdWieUYzgO0MtjerREX 7bgoDGUhmrruKEx+6qXnol6oQVKz55cz2tbtMYEBqaXGKUe+Qd3xwLJ/k/Ra2EKNGmmD P6dAXLhEiNljVeWsm62jTtN18y7vV3/rMMS6Kb/UjS+z/0n5NyXwOLwU8TJVE8UL6PQ9 x/XMtueLSs9vh7CVfwphTOFbFVYmrE01T6RIn9drCpQbUv2yjKyxkSb8j5d53HHiyYzP /uEg==
X-Gm-Message-State: AMke39lOGkpWMLAIiyqHj/qWB3fTLLB6Pbby5uDuPDCd0Bcqsjo+8yy3AgaKvYjrAfYZsLr4nBa3i3//nQlHDA==
X-Received: by 10.157.15.154 with SMTP id d26mr402068otd.186.1487298670854; Thu, 16 Feb 2017 18:31:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.1.202 with HTTP; Thu, 16 Feb 2017 18:30:30 -0800 (PST)
In-Reply-To: <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
References: <148568056700.24536.11691583944564362484.idtracker@ietfa.amsl.com> <DCA1FC02-8DE1-4271-99B1-02E0D7F6D8E0@piuha.net>
From: tianxiang li <peter416733@gmail.com>
Date: Fri, 17 Feb 2017 10:30:30 +0800
Message-ID: <CAFx+hEOMFF=bU3BUQfcbCAARs_0OyR9HuoAmjs5BLh29QFpEXg@mail.gmail.com>
Subject: Re: [Gen-art] Review of draft-ietf-dhc-dhcpv6-prefix-length-hint-issue-05
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary=001a113cf206f386ab0548b0b439
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fYm2oFsPhw3uj9fiRCUFkytMe4A>
Cc: dhcwg <dhcwg@ietf.org>, gen-art@ietf.org, Roni Even <roni.even@mail01.huawei.com>, ietf@ietf.org, draft-ietf-dhc-dhcpv6-prefix-length-hint-issue.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 02:31:12 -0000

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

Hi Jari,

Thank you for the support, and thanks to Roni as well as all the other kind
reviewers of this document.
We would update a new version of the document soon and cover the points
raised during last call.

Thanks and best regards,
Tianxiang

2017-02-16 20:04 GMT+08:00 Jari Arkko <jari.arkko@piuha.net>:

> Roni: thanks for your detailed review. I also appreciate
> the responses and changes by you Tianxiang. I have
> balloted no-objection for this document for today=E2=80=99s
> IESG telechat, and expect that the discussed changes
> will find themselves into a new document version at
> some point.
>
> Jari
>
>

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

<div dir=3D"ltr">Hi Jari,<div><br></div><div>Thank you for the support, and=
 thanks to Roni as well as all the other kind reviewers of this document.</=
div><div>We would update a new version of the document soon and cover the p=
oints raised during last call.=C2=A0</div><div><br></div><div>Thanks and be=
st regards,</div><div>Tianxiang</div></div><div class=3D"gmail_extra"><br><=
div class=3D"gmail_quote">2017-02-16 20:04 GMT+08:00 Jari Arkko <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.net" target=3D"_blank">jari=
.arkko@piuha.net</a>&gt;</span>:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Roni: th=
anks for your detailed review. I also appreciate<br>
the responses and changes by you Tianxiang. I have<br>
balloted no-objection for this document for today=E2=80=99s<br>
IESG telechat, and expect that the discussed changes<br>
will find themselves into a new document version at<br>
some point.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Jari<br>
<br>
</font></span></blockquote></div><br></div>

--001a113cf206f386ab0548b0b439--


From nobody Thu Feb 16 19:34:50 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 497391298AE for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 19:34:48 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VK6kwap56Otc for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 19:34:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFDAF1298A4 for <ietf@ietf.org>; Thu, 16 Feb 2017 19:34:41 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ceZJN-000PRI-Tj; Thu, 16 Feb 2017 22:34:21 -0500
Date: Thu, 16 Feb 2017 22:34:13 -0500
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Fwd: Re: [Jmap] Fwd: Re: WG Review: JSON Mail Access Protocol (jmap) - reducing configuration complexity
Message-ID: <F5245E92CB19F40A933B051D@PSB>
In-Reply-To: <01QAYO8E39Y40005AQ@mauve.mrochek.com>
References: <3b955910-12d0-2c56-0dc2-30279f98aea5@isode.com> <19fabdd7-77c5-fc13-616e-26d39d2f23df@isode.com> <20170208142241.GB84460@mx4.yitter.info> <217b1d1b-adba-2ebb-30ca-600f8dc77246@isode.com> <32D2801528D191A01AD4D3B2@PSB> <2fa724eb-18ba-b818-6a01-a07db5a9a9a4@isode.com> <01QANBYPRC140005AQ@mauve.mrochek.com> <1162BF5A37921B1555FF29F9@PSB> <8c81f385-7dfc-cff3-f97c-3c016fc72601@isode.com> <01QAYO8E39Y40005AQ@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/in9-ftJgT20vrpGvSZbx7NBHZlA>
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 03:34:48 -0000

+1 to both points.  With regard to changed proposals, the
charter improvements will help, but there have been several
comments that imply people have ideas about how to "do things
better" that would invalidate that compatibility assessment.
The combination of the charter, your choices about WG
leadership, and fairly aggressive monitoring need to prevent
such an outcome.

best,
   john


--On Thursday, February 16, 2017 17:15 -0800
ned+ietf@mauve.mrochek.com wrote:

>> John and Ned,
> 
>> On 12/02/2017 20:15, John C Klensin wrote:
> 
>> > --On Wednesday, February 8, 2017 12:39 -0800 Ned Freed
>> > <ned.freed@mrochek.com>  wrote:
>> > 
>>   [snip]
>> >> (2) in particular creates additional requirements that
>> >> need to be explicitly called out in the charter. In
>> >> particular, it's imperative that (a) It be reasonable to
>> >> implement JMAP->IMAP/SUBMIT proxies, even if that
>> >> constrains JMAP in ways some folks do not like, (b) The
>> >> list of IMAP extensions needed to properly implement JMAP
>> >> be called out, and (c) The security considerations
>> >> involved in operating such a proxy need to be described in
>> >> detail.
> 
>> I updated Charter text to mention these.
> 
> Good.
> 
>> > Exactly.  If one expects JMAP to be wildly successful, and
>> > unless there is either a plausible plan to make all of those
>> > IMAP clients go away (even if there are no new ones), I
>> > think that list should include either its being reasonable
>> > to implement and support IMAP/SUBMIT-> JMAP proxies or other
>> > overlays or a charter requirement to discuss residual use
>> > cases for IMAP.    I'm particularly concerned about
>> > supporting IMAP-native clients with a JMAP-native mailstore.
>> > 
>> >>> 2). Both are supported by the same software (i.e. Cyrus
>> >>> and Dovecot use case). I doubt that incremental cost of
>> >>> configuring both is much higher than just configuring one
>> >>> of them.
>> >>> In either case configuring JMAP clients is a simple(r)
>> >>> proposition: just distribute HTTP URI for a JMAP instance.
>> >>>> and to support, also for a long time, the ability to
>> >>>> convert between the two formats.
>> >>> There are no 2 formats, both IMAP and JMAP operate on RFC
>> >>> 5322 objects, so the rest of your argument is invalid.
>> >> Agreed. I have to say I really don't understand the
>> >> confusion surrounding this point. IMAP has bodystructure
>> >> plus a couple of other formats for returning message data,
>> >> and a means of creating new messages from pieces of other
>> >> messages, none of which look remotely like MIME/RFC 5322,
>> >> and nobody cares.
>> >> 
>> >> This is effectively the same thing; why should anyone care
>> >> here?
>> > I can't speak for anyone else, but I'm concerned about what
>> > it takes to create and maintain servers and mailstores that
>> > are compatible with both IMAP and JMAP.  If that means
>> > proxies, we either need to address the question of IMAP
>> > proxies over JMAP and JMAP mailstores as well as the JMAP
>> > over IMAP-compatible ones or I'd like the charter is
>> > require a good explanation of why that isn't necessary.
>> > That might be "IMAP-based systems with JMAP overlays
>> > forever", but, the more people argue that JMAP will take
>> > over (rapidly or otherwise), the less plausible that
>> > position feels.
> 
>> I've done some prototyping of existing JMAP proposal and I am
>> quite confident that underlying models are close enough that
>> implementing one on top of another is doable. IMAP+QRESYNC
>> extension require IMAP mailstores to store change sequence
>> numbers, which is required feature in JMAP.
> 
> I agree with the assessment, but what if the propsoal changes
> substantially?
> That's the case I'm worried about.
> 
> 				Ned
> 





From nobody Thu Feb 16 19:38:03 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 317231298C4; Thu, 16 Feb 2017 19:37:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Joel Halpern" <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-pce-stateful-pce-18
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Date: Thu, 16 Feb 2017 19:37:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lg4_CrVNFzDZjtB7ELqJfCccnYc>
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 03:37:58 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-stateful-pce-??
Reviewer: Joel Halpern
Review Date: 2017-02-16
IETF LC End Date: 2017-02-28
IESG Telechat date: 2017-03-16

Summary:

Major issues:

Minor issues:
   At the end of section 5.4, the text talks about a PCE accepting
status updates even if the  stateful capability has not been
negotiated.  Which is fine.  But as written, the text seems to say
that doing so means that the PCE will be able to "build and maintain
an up to date view of the state of the PCC's LSPs".  However, if the
capability has not been negotiated, I do not see how the PCE can count
on getting full and timely state reports.  Trying to infer why a PCC
is sending such a report in the absence of the agreement seems
problematic.

    This comment may be a misunderstanding or mis-expectation on my
part.  I would have expected one of the ways o using an active PCE is
to have the PCE decide (under suitable circumstances) that an LSP is
needed between two PCCs.  As far as I can tell, the text in section
5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
Update Request (in a PCUpd message) for an LSP that has been delegated
to it.  At that point I thought that a PCC could delegate a block of
unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states
that for each delegation, the PCC must request an initial path.  That
seems to prohibit delegating a block of LSPs for future updates.  Is
the intention to prohibit the driving of LSP creation from the PCE?

    I have looked but I can not find the text explaining the
significance and use of the Symbolic path name.  It is mandated by the
draft.  There seems to be an implicit assumption taht it is needed by
the PCE.  If the explanation of how or why it is needed is not
present, it should be.

Nits/editorial comments: 
    Should the text on the S bit in section 7.3 (the LSP Object
definition) note that it should be set to 0 on all messages sent by
the PCE?  Should that also be stated for the R bit?  And the O bits?

  Section 9.2 seems very odd.  It states that the IETF "SHOULD" do
some additional work.  I understand why teh work is needed.  But this
does not seem to match the RFC 2119 meaning of SHOULD as it does not
apply to eitehr the implementor or the implementation.



From nobody Thu Feb 16 20:36:22 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D67F512997D; Thu, 16 Feb 2017 20:36:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 pbyT7AwNwi3T; Thu, 16 Feb 2017 20:36:14 -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 AC8BA1294A3; Thu, 16 Feb 2017 20:36:13 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGQ31933; Fri, 17 Feb 2017 04:36:11 +0000 (GMT)
Received: from BLREML702-CAH.china.huawei.com (10.20.4.171) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 17 Feb 2017 04:36:10 +0000
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml702-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Fri, 17 Feb 2017 10:05:57 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: Joel Halpern <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM9gtp/PSv/bkEq3uaeNA/BLdaFsmcuQ
Date: Fri, 17 Feb 2017 04:35:56 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.40.100]
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.0A090203.58A67DBB.0124, 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: bc9b1df1e95a95ef020d370418be5c18
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/esAfbpfHb6X7fj0jgf3nj9FWGb8>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 04:36:17 -0000

Hi Joel,=20

Regarding your comment -=20

> Is the intention to prohibit the driving
> of LSP creation from the PCE?

This capability is described in -=20
https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07 (document e=
xpired recently, authors should refresh it)

Thanks,
Dhruv=20

> -----Original Message-----
> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
> Sent: 17 February 2017 09:08
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
>=20
> Reviewer: Joel Halpern
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-pce-stateful-pce-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-16
> IETF LC End Date: 2017-02-28
> IESG Telechat date: 2017-03-16
>=20
> Summary:
>=20
> Major issues:
>=20
> Minor issues:
>    At the end of section 5.4, the text talks about a PCE accepting status
> updates even if the  stateful capability has not been negotiated.  Which =
is
> fine.  But as written, the text seems to say that doing so means that the
> PCE will be able to "build and maintain an up to date view of the state o=
f
> the PCC's LSPs".  However, if the capability has not been negotiated, I d=
o
> not see how the PCE can count on getting full and timely state reports.  =
Trying
> to infer why a PCC is sending such a report in the absence of the agreeme=
nt
> seems problematic.
>=20
>     This comment may be a misunderstanding or mis-expectation on my part.
> I would have expected one of the ways o using an active PCE is to have th=
e
> PCE decide (under suitable circumstances) that an LSP is needed between t=
wo
> PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Upd=
ate
> Request (in a PCUpd message) for an LSP that has been delegated to it.  A=
t
> that point I thought that a PCC could delegate a block of unsetup LSPs to
> the PCE.  But then looking at 5.8.2, the text states that for each delega=
tion,
> the PCC must request an initial path.  That seems to prohibit delegating =
a
> block of LSPs for future updates.  Is the intention to prohibit the drivi=
ng
> of LSP creation from the PCE?
>=20
>     I have looked but I can not find the text explaining the significance
> and use of the Symbolic path name.  It is mandated by the draft.  There s=
eems
> to be an implicit assumption taht it is needed by the PCE.  If the explan=
ation
> of how or why it is needed is not present, it should be.
>=20
> Nits/editorial comments:
>     Should the text on the S bit in section 7.3 (the LSP Object
> definition) note that it should be set to 0 on all messages sent by the P=
CE?
> Should that also be stated for the R bit?  And the O bits?
>=20
>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some
> additional work.  I understand why teh work is needed.  But this does not
> seem to match the RFC 2119 meaning of SHOULD as it does not apply to eite=
hr
> the implementor or the implementation.
>=20
>=20
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce


From nobody Thu Feb 16 20:42:42 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 679B712956D; Thu, 16 Feb 2017 20:42:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lL-5ki5O1xCG; Thu, 16 Feb 2017 20:42:35 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (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 4F0E5129540; Thu, 16 Feb 2017 20:42:32 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 33E50A21ADA; Thu, 16 Feb 2017 20:42:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487306552; bh=5j6BM0KdaO7SJ1Ky9DrpJN3RMTl02OaEPIy9i8bv8ZM=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=KR4Y7dyzbptUnhOwAYsI2M5G3pyPEsQIX2Okki/bzkhoPZLbMLZi2Lwj8z8+MXGvP Jl8tX65JnSxiwwUYsRU03ErDeykcaqgaJy5qOkH1r8z5JW7LABnLm5gurUlYbUOW8l lrM4vj8cNRHte7IgpwM8qy9S3z6Ul1UgGD+tI61U=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 6BA2A1C02F3; Thu, 16 Feb 2017 20:42:31 -0800 (PST)
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Date: Thu, 16 Feb 2017 23:42:30 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LuX37EiYWASDprb4JeJJxE-PIAE>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 04:42:36 -0000

So it is intentional that this draft prohibits that behavior (PCE driven 
establishment)?

Yours,
Joel

On 2/16/17 11:35 PM, Dhruv Dhody wrote:
> Hi Joel,
>
> Regarding your comment -
>
>> Is the intention to prohibit the driving
>> of LSP creation from the PCE?
>
> This capability is described in -
> https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07 (document expired recently, authors should refresh it)
>
> Thanks,
> Dhruv
>
>> -----Original Message-----
>> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
>> Sent: 17 February 2017 09:08
>> To: gen-art@ietf.org
>> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
>> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
>>
>> Reviewer: Joel Halpern
>> Review result: Ready with Issues
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area Review
>> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
>> the IETF Chair.  Please treat these comments just like any other last call
>> comments.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-pce-stateful-pce-??
>> Reviewer: Joel Halpern
>> Review Date: 2017-02-16
>> IETF LC End Date: 2017-02-28
>> IESG Telechat date: 2017-03-16
>>
>> Summary:
>>
>> Major issues:
>>
>> Minor issues:
>>    At the end of section 5.4, the text talks about a PCE accepting status
>> updates even if the  stateful capability has not been negotiated.  Which is
>> fine.  But as written, the text seems to say that doing so means that the
>> PCE will be able to "build and maintain an up to date view of the state of
>> the PCC's LSPs".  However, if the capability has not been negotiated, I do
>> not see how the PCE can count on getting full and timely state reports.  Trying
>> to infer why a PCC is sending such a report in the absence of the agreement
>> seems problematic.
>>
>>     This comment may be a misunderstanding or mis-expectation on my part.
>> I would have expected one of the ways o using an active PCE is to have the
>> PCE decide (under suitable circumstances) that an LSP is needed between two
>> PCCs.  As far as I can tell, the text in section
>> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Update
>> Request (in a PCUpd message) for an LSP that has been delegated to it.  At
>> that point I thought that a PCC could delegate a block of unsetup LSPs to
>> the PCE.  But then looking at 5.8.2, the text states that for each delegation,
>> the PCC must request an initial path.  That seems to prohibit delegating a
>> block of LSPs for future updates.  Is the intention to prohibit the driving
>> of LSP creation from the PCE?
>>
>>     I have looked but I can not find the text explaining the significance
>> and use of the Symbolic path name.  It is mandated by the draft.  There seems
>> to be an implicit assumption taht it is needed by the PCE.  If the explanation
>> of how or why it is needed is not present, it should be.
>>
>> Nits/editorial comments:
>>     Should the text on the S bit in section 7.3 (the LSP Object
>> definition) note that it should be set to 0 on all messages sent by the PCE?
>> Should that also be stated for the R bit?  And the O bits?
>>
>>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some
>> additional work.  I understand why teh work is needed.  But this does not
>> seem to match the RFC 2119 meaning of SHOULD as it does not apply to eitehr
>> the implementor or the implementation.
>>
>>
>> _______________________________________________
>> Pce mailing list
>> Pce@ietf.org
>> https://www.ietf.org/mailman/listinfo/pce


From nobody Thu Feb 16 21:53:25 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 655851294FC for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 21:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.487
X-Spam-Level: 
X-Spam-Status: No, score=-4.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 gaEp8CEfZ53W for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 21:53:20 -0800 (PST)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B2E51294D2 for <ietf@ietf.org>; Thu, 16 Feb 2017 21:53:20 -0800 (PST)
Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1H5mh8O089362 for <ietf@ietf.org>; Fri, 17 Feb 2017 00:53:20 -0500
Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 28nrgkd6ap-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 17 Feb 2017 00:53:20 -0500
Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 16 Feb 2017 22:53:19 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e31.co.us.ibm.com (192.168.1.131) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 16 Feb 2017 22:53:16 -0700
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id DAB573E4003E for <ietf@ietf.org>; Thu, 16 Feb 2017 22:53:15 -0700 (MST)
Received: from b01ledav006.gho.pok.ibm.com (b01ledav006.gho.pok.ibm.com [9.57.199.111]) by b01cxnp22035.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v1H5rF7i58720344 for <ietf@ietf.org>; Fri, 17 Feb 2017 05:53:15 GMT
Received: from b01ledav006.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id DE947AC03A for <ietf@ietf.org>; Fri, 17 Feb 2017 00:53:13 -0500 (EST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b01ledav006.gho.pok.ibm.com (Postfix) with ESMTPS id B504AAC043 for <ietf@ietf.org>; Fri, 17 Feb 2017 00:53:13 -0500 (EST)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v1H5rDj4001421 for <ietf@ietf.org>; Fri, 17 Feb 2017 00:53:14 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v1H5rDaq001404 for ietf@ietf.org; Fri, 17 Feb 2017 00:53:13 -0500
From: narten@us.ibm.com
Date: Fri, 17 Feb 2017 00:53:13 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 17021705-8235-0000-0000-00000AFCAA85
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006631; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000203; SDB=6.00823106; UDB=6.00402750; IPR=6.00600552;  BA=6.00005146; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014317; XFM=3.00000011; UTC=2017-02-17 05:53:17
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17021705-8236-0000-0000-000039AC5761
Message-Id: <201702170553.v1H5rDaq001404@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-17_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=13 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702170055
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pvsv8va2uA-hU5sUqvtMGGOJRkA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 05:53:23 -0000

Total of 277 messages in the last 7 days.
 
script run at: Fri Feb 17 00:53:08 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  4.69% |   13 |  7.20% |   259397 | gunnar.hellstrom@omnitor.se
  5.42% |   15 |  4.50% |   162343 | otroan@employees.org
  1.81% |    5 |  7.89% |   284611 | charles.perkins@earthlink.net
  5.05% |   14 |  4.43% |   159796 | brian.e.carpenter@gmail.com
  4.69% |   13 |  4.46% |   160631 | rg+ietf@randy.pensive.org
  2.53% |    7 |  4.44% |   160212 | farmer@umn.edu
  3.97% |   11 |  2.78% |   100170 | touch@isi.edu
  2.89% |    8 |  2.79% |   100470 | mellon@fugue.com
  3.61% |   10 |  1.92% |    69138 | randy@psg.com
  2.89% |    8 |  2.62% |    94345 | stewart.bryant@gmail.com
  2.53% |    7 |  2.55% |    92064 | fred.l.templin@boeing.com
  2.53% |    7 |  2.00% |    72212 | rjsparks@nostrum.com
  2.53% |    7 |  1.96% |    70840 | john-ietf@jck.com
  2.53% |    7 |  1.80% |    64827 | jmh@joelhalpern.com
  2.17% |    6 |  1.88% |    67828 | presnick@qti.qualcomm.com
  1.81% |    5 |  2.06% |    74350 | markzzzsmith@gmail.com
  1.44% |    4 |  1.93% |    69717 | gregimirsky@gmail.com
  1.81% |    5 |  1.40% |    50489 | housley@vigilsec.com
  1.81% |    5 |  1.35% |    48561 | gorry@erg.abdn.ac.uk
  1.08% |    3 |  2.00% |    72205 | bernard.aboba@gmail.com
  1.81% |    5 |  1.28% |    46106 | barryleiba@computer.org
  1.44% |    4 |  1.47% |    53039 | suresh.krishnan@gmail.com
  1.44% |    4 |  1.09% |    39133 | lorenzo@google.com
  1.44% |    4 |  1.02% |    36699 | dhc@dcrocker.net
  1.08% |    3 |  1.30% |    46855 | worley@ariadne.com
  1.08% |    3 |  1.27% |    45828 | albert.e.manfredi@boeing.com
  0.72% |    2 |  1.55% |    55825 | talmi@marvell.com
  1.08% |    3 |  1.06% |    38238 | alexandre.petrescu@gmail.com
  1.08% |    3 |  1.02% |    36750 | lars@netapp.com
  1.08% |    3 |  1.00% |    36005 | jhw@google.com
  1.08% |    3 |  0.93% |    33405 | christer.holmberg@ericsson.com
  1.08% |    3 |  0.84% |    30139 | nalini.elkins@insidethestack.com
  0.36% |    1 |  1.52% |    54677 | oritl@microsoft.com
  1.08% |    3 |  0.78% |    28201 | dave@cridland.net
  0.72% |    2 |  1.11% |    40077 | suresh.krishnan@ericsson.com
  1.08% |    3 |  0.74% |    26855 | fredbaker.ietf@gmail.com
  1.08% |    3 |  0.65% |    23599 | jari.arkko@piuha.net
  1.08% |    3 |  0.65% |    23500 | ietf-dane@dukhovni.org
  0.72% |    2 |  1.00% |    36025 | heard@pobox.com
  1.08% |    3 |  0.63% |    22653 | doug@ewellic.org
  0.72% |    2 |  0.88% |    31605 | sgundave@cisco.com
  0.72% |    2 |  0.86% |    31123 | jordi.palet@consulintel.es
  0.72% |    2 |  0.70% |    25200 | addison@lab126.com
  0.72% |    2 |  0.67% |    24145 | ynir.ietf@gmail.com
  0.72% |    2 |  0.65% |    23512 | karsten_thomann@linfre.de
  0.72% |    2 |  0.61% |    21893 | marka@isc.org
  0.72% |    2 |  0.53% |    19134 | randy_presuhn@alumni.stanford.edu
  0.72% |    2 |  0.52% |    18659 | acmorton@att.com
  0.36% |    1 |  0.81% |    29243 | john_leddy@comcast.com
  0.72% |    2 |  0.45% |    16190 | fgont@si6networks.com
  0.72% |    2 |  0.39% |    14184 | bortzmeyer@nic.fr
  0.72% |    2 |  0.36% |    13010 | sthaug@nethelp.no
  0.72% |    2 |  0.33% |    11764 | jounikor@gmail.com
  0.36% |    1 |  0.67% |    24058 | evyncke@cisco.com
  0.36% |    1 |  0.60% |    21784 | asmusf@ix.netcom.com
  0.36% |    1 |  0.58% |    20815 | weihaw@google.com
  0.36% |    1 |  0.49% |    17756 | daedulus@btconnect.com
  0.36% |    1 |  0.44% |    15743 | davidm@mellanox.com
  0.36% |    1 |  0.40% |    14280 | alexey.melnikov@isode.com
  0.36% |    1 |  0.36% |    13113 | bishopbilly84@gmail.com
  0.36% |    1 |  0.31% |    11015 | skh@ndzh.com
  0.36% |    1 |  0.30% |    10918 | aaron.falk@gmail.com
  0.36% |    1 |  0.30% |    10837 | narten@us.ibm.com
  0.36% |    1 |  0.30% |    10701 | john@jlc.net
  0.36% |    1 |  0.30% |    10644 | adrian@olddog.co.uk
  0.36% |    1 |  0.29% |    10458 | dhruv.dhody@huawei.com
  0.36% |    1 |  0.29% |    10442 | jinmei@wide.ad.jp
  0.36% |    1 |  0.27% |     9866 | ggm@algebras.org
  0.36% |    1 |  0.27% |     9761 | ned+ietf@mauve.mrochek.com
  0.36% |    1 |  0.27% |     9674 | sean.gillies@gmail.com
  0.36% |    1 |  0.27% |     9557 | peter416733@gmail.com
  0.36% |    1 |  0.24% |     8684 | chengweiqiang@chinamobile.com
  0.36% |    1 |  0.23% |     8240 | denis.ietf@free.fr
  0.36% |    1 |  0.21% |     7704 | sob@sobco.com
  0.36% |    1 |  0.21% |     7686 | paul@nohats.ca
  0.36% |    1 |  0.21% |     7631 | chair@ietf.org
  0.36% |    1 |  0.20% |     7230 | tim@ripe.net
  0.36% |    1 |  0.20% |     7191 | pch-ipv6-ietf-3@u-1.phicoh.com
  0.36% |    1 |  0.19% |     6755 | johnl@iecc.com
  0.36% |    1 |  0.18% |     6653 | nomcom-chair-2016@ietf.org
  0.36% |    1 |  0.18% |     6324 | johnl@taugh.com
  0.36% |    1 |  0.17% |     6286 | ben@nostrum.com
  0.36% |    1 |  0.15% |     5489 | francis.dupont@fdupont.fr
  0.36% |    1 |  0.15% |     5443 | vijay.gurbani@alcatel-lucent.com
  0.36% |    1 |  0.14% |     4995 | mls.ietf@gmail.com
--------+------+--------+----------+------------------------
100.00% |  277 |100.00% |  3605210 | Total


From nobody Thu Feb 16 22:27:37 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45F1128DF6 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 22:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-coFxOQ4sNc for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 22:27:31 -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 749001295AA for <ietf@ietf.org>; Thu, 16 Feb 2017 22:27:29 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id t8so23908998vke.3 for <ietf@ietf.org>; Thu, 16 Feb 2017 22:27:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CjwGxpPrqhPEuUbVABHXOOTuk07regmRTXWQ6kDUYHo=; b=vBarxgaazMYXagelqYkeCiBuYsql5O9rxX7NH98DYIM7o4mCF4nO3mye1BNWAn+u2x U8tRpZKVf0HIZI083bDohRSlY05g9bljthY/mEUxi+KpncYgoNd8JWOj4AkJ9gmsGIyz ctPeH9TGDGALIt5ki+z5SFbAXMPgGyvxFLtKeNkglokC94xlZYlqcvCsht5Sw0nsHyVN Znu2zcs1/QZSNd7g8Q0EgTbi7ZohfivUlaGm4+AuOgaxggF8YBIdXA+VZhHNJs4xk/3k j7A5biGZMo6lIsnK+37cmm2T6LfPeqj0PK3hcitQ4nEpvp6N3PGezZf7+GMwuzKmClsm JbDw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CjwGxpPrqhPEuUbVABHXOOTuk07regmRTXWQ6kDUYHo=; b=YZCUMipu1Td6AypebGDPs2uhutKvkM3iVGt+rbSiHjtnuGnBSbvn5/6Wxa7ZBkYNVh mOVmNcFmxzc8gSYYAGdtCpy7gvcJ0xOIPbD34BHb3usQqR+diL+QRrtSO8IbrvmuKDdC d0vZElGKcfizHPxUzCe0zO7PotYm18odQZBIB2/VZt2zCmEs/dATql1AIot9SVzRapgY iqv6KHAztLHhPtS8Dy4wEBdlNdOo9vPFTB97KbkNIVAZU9JXuGqmXKiSGG31Ws0KwYTB w3MDvBAIFh7gserW5ixDUbfv9kLiCORHv/oNUAuc8wL8QWOi2zAMIz0DKnHPgWNY7w4k /Rhg==
X-Gm-Message-State: AMke39lyRZCUMkp6Vvag9fc15To2AXCX0BnkmvB+oex66ja8jMtAvEROULw58J100Ycqvo0m7rCjCm9ySRDHPurH
X-Received: by 10.31.192.204 with SMTP id q195mr3165737vkf.155.1487312848337;  Thu, 16 Feb 2017 22:27:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 16 Feb 2017 22:27:07 -0800 (PST)
In-Reply-To: <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <m2wpcpdgiv.wl-randy@psg.com> <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 17 Feb 2017 15:27:07 +0900
Message-ID: <CAKD1Yr3JM02-kLR30T8mVJW5g_y+5a+SP-9q9Yc_2HaLn6dqwQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a114388ccff26570548b40120
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/woO5eXEiXMdiRPhkGCyTwR-HXtQ>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 06:27:32 -0000

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

On Fri, Feb 17, 2017 at 5:52 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> Objecting to it, calling it "classful", is implying that it is exactly
> the same as IPv4 classful addressing. I don't think IPv6 is.
>

These days IPv4 is classful too, because routing occurs on a 32-bit address
and a 16 bit port.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 17, 2017 at 5:52 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Objecting to it, calling=
 it &quot;classful&quot;, is implying that it is exactly<br>
the same as IPv4 classful addressing. I don&#39;t think IPv6 is.<br></block=
quote><div><br></div><div>These days IPv4 is classful too, because routing =
occurs on a 32-bit address and a 16 bit port.</div></div></div></div>

--001a114388ccff26570548b40120--


From nobody Thu Feb 16 22:33:14 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC188129510 for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 22:33: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-vdREYAuGEN for <ietf@ietfa.amsl.com>; Thu, 16 Feb 2017 22:33:11 -0800 (PST)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 1BBC21295AC for <ietf@ietf.org>; Thu, 16 Feb 2017 22:33:07 -0800 (PST)
Received: by mail-ua0-x22f.google.com with SMTP id 35so24925393uak.1 for <ietf@ietf.org>; Thu, 16 Feb 2017 22:33:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=YZmFU8iN9e/DIVWgrISQKJh8STej/v4HQzM681yF8WA=; b=lGu+/XDemFYdIPsJdyBvtTHjxGAdRHosw5l8QOk7nd3qqg8fqbO1bHdEekEKUZjKAW HkDmE57NcRIN0U2vRX7MaI5C+cCE41pud4dTNoF9p8IkLsh3NtWufzpTnOLrZ2iF6mWv qiXpimO+IUBynyQgaM4Nv7KZLKaRS5y++aAoh4ljw1Fg5xn5gqJNdh2v0D1HKzSNpcjI 6L+cFTYcwrTlqG7ULxViWH2s3SrcCDtkoT6WUPh4dLyXekKOE+P4pFXRaW4eiqaSSedq smUXRNV6sKSj9EZG4Vbhck3SD8AaZvJ2YubjuKyO/NzTONhdLNRSyVrNPnVCi1xvdYgF rdfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=YZmFU8iN9e/DIVWgrISQKJh8STej/v4HQzM681yF8WA=; b=tXIF4rxgBWqUttz0CiKUy8bILR6QIZ05G7EgDEJnI68e5ano0m/pOqMFseVAr7XgPy cqdFlTO8npZ23ZKt545Y/yX1yucSHujOuKaljz8uK3jBsIlB0wmncXgV09eQDrOLd1SH esuC9SfcV6L0c+ZlUl3hKI4ahg3vYf5iLHl3nOMWaxJITX7XdyrZYJOzIvsCA9GK8vRe 30UfARM4txkGQuirmIZsuRFk3dKwDKnUGG6v5OiA/om3IIRLHtyVEC6qCteVzGatqZG2 aU+skTJst8OvyCCaah3KceuVfX3mXzLO3CeFUfhvxTUN+iWu9T4JI8Y+RLBf6brtWPEY Ibog==
X-Gm-Message-State: AMke39l+F8jsfhziv8BWRq/AmFLxRu/OVbe9Dt0OBSx088n7M8NVW1L1m2HOIh78JPr2jJSkBIW8YQyOBT/Snfou
X-Received: by 10.159.49.66 with SMTP id n2mr3457500uab.72.1487313186030; Thu, 16 Feb 2017 22:33:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 16 Feb 2017 22:32:45 -0800 (PST)
In-Reply-To: <8767e370398045af989467a63747b29e@XCH15-06-11.nw.nos.boeing.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <8767e370398045af989467a63747b29e@XCH15-06-11.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 17 Feb 2017 15:32:45 +0900
Message-ID: <CAKD1Yr2eg1VVetdURn7aH_1Y7sdqEjRQPzuP7a7=6vH0UQOQug@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=f403045e2fee1fd9d30548b41614
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/do4KY0QWUUhTwM49KcgdWYRg8Xo>
Cc: james woodyatt <jhw@google.com>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>, "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 06:33:13 -0000

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

That's a valid opinion but it does not reflect the current state of the
IPv6 standards.

Again, let's bear in mind that this discussion is not about changing the
standard, but about reclassifying the existing standards. We can discuss
changing this part of the standard to our heart's content, but *in 6man, on
another document*, not here.

I would be rather surprised if such a discussion ever reached consensus,
but I certainly wouldn't want to dissuade anyone from trying.

On Fri, Feb 17, 2017 at 7:38 AM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> RFC 7421 is informational. And many considerations are not so critical
> anymore, on a specific stateful format.
>
>
>
> I don=E2=80=99t think we need to reinforce the notion that IPv6 must have=
 64-bit
> prefixes, since that is not true now, and should not even be made to appl=
y
> to the currently unused address space. So, I=E2=80=99m opposed to text th=
at implies
> any such restriction, with the exception of (a) currently used unicast
>  address space, (b) SLAAC, (c) ULA, possibly other exceptions.
>
>
>
> In other words, *exceptions belong to requiring the 64-bit IID*. Any RFC
> that implies otherwise, IMO, ought to be subject to a =E2=80=93bis versio=
n.
>
>
>
> Bert
>
>
>
>
>
> *From:* ipv6 [mailto:ipv6-bounces@ietf.org] *On Behalf Of *james woodyatt
> *Sent:* Thursday, February 16, 2017 17:21
> *To:* IETF-Discussion Discussion <ietf@ietf.org>
> *Cc:* 6man WG <ipv6@ietf.org>; draft-ietf-6man-rfc4291bis@ietf.org;
> 6man-chairs@ietf.org
> *Subject:* Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version
> 6 Addressing Architecture) to Internet Standard
>
>
>
> On Feb 16, 2017, at 13:25, otroan@employees.org wrote:
>
> On Feb 13, 2017, at 14:32, David Farmer <farmer@umn.edu> wrote:
>
>
>
> I have concerns with the following text;
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links. However, the Interface ID of
>    all unicast addresses, except those that start with the binary value
>    000, is required to be 64 bits long.  The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
>
>
>
> The third sentence seems to limit exceptions to 64 bit IIDs to exclusivel=
y
> addresses that start with binary vale of 000.  There are at least two oth=
er
> exceptions from standards track RFCs, that should be more clear accounted
> for in this text. [=E2=80=A6]
>
>
>
> [=E2=80=A6]
>
> The challenge is to find text that enforces the 64-bit boundary policy
> (ignoring the technical arguments for a moment), and at the same time
> ensures implementors do the right thing and make their code handle any
> prefix length. Of course these are interdependent and doing the latter
> makes it harder to enforce the first.
>
>
>
> I propose the following:
>
>
>
> IPv6 unicast routing is based on prefixes of any valid length up to 128
> bits [BCP198]. However, as explained in [RFC7421], the Interface ID of
> unicast addresses is generally required to be 64 bits in length, with
> exceptions only provided in special cases where expressly recognized in
> IETF standards track documents.
>
>
>
> Trying to help out here.
>
>
>
>
>
> --james woodyatt <jhw@google.com>
>
>
>
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>

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

<div dir=3D"ltr">That&#39;s a valid opinion but it does not reflect the cur=
rent state of the IPv6 standards.<div><br></div><div>Again, let&#39;s bear =
in mind that this discussion is not about changing the standard, but about =
reclassifying the existing standards. We can discuss changing this part of =
the standard to our heart&#39;s content, but *in 6man, on another document*=
, not here.</div><div><br></div><div>I would be rather surprised if such a =
discussion ever reached consensus, but I certainly wouldn&#39;t want to dis=
suade anyone from trying.</div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Fri, Feb 17, 2017 at 7:38 AM, Manfredi, Albert E <span dir=
=3D"ltr">&lt;<a href=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_bla=
nk">albert.e.manfredi@boeing.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-4753189871988625434m_-8279061134009960360WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0">RFC 7=
421 is informational. And many considerations are not so critical anymore, =
on a specific stateful format.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0"><u></=
u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0">I don=
=E2=80=99t think we need to reinforce the notion that IPv6 must have 64-bit=
 prefixes, since that is not true now, and should not even be made to apply=
 to the currently unused address space. So,
 I=E2=80=99m opposed to text that implies any such restriction, with the ex=
ception of (a) currently used unicast =C2=A0address space, (b) SLAAC, (c) U=
LA, possibly other exceptions.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0"><u></=
u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0">In ot=
her words,
<b>exceptions belong to requiring the 64-bit IID</b>. Any RFC that implies =
otherwise, IMO, ought to be subject to a =E2=80=93bis version.<u></u><u></u=
></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0"><u></=
u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0">Bert<=
u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0"><u></=
u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;color:#0e25d0"><u></=
u>=C2=A0<u></u></span></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,sans-serif">From:</span></b><span style=3D"font-size:11.0pt;=
font-family:&quot;Calibri&quot;,sans-serif"> ipv6 [mailto:<a href=3D"mailto=
:ipv6-bounces@ietf.org" target=3D"_blank">ipv6-bounces@ietf.org</a>]
<b>On Behalf Of </b>james woodyatt<br>
<b>Sent:</b> Thursday, February 16, 2017 17:21<br>
<b>To:</b> IETF-Discussion Discussion &lt;<a href=3D"mailto:ietf@ietf.org" =
target=3D"_blank">ietf@ietf.org</a>&gt;<br>
<b>Cc:</b> 6man WG &lt;<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">i=
pv6@ietf.org</a>&gt;; <a href=3D"mailto:draft-ietf-6man-rfc4291bis@ietf.org=
" target=3D"_blank">draft-ietf-6man-rfc4291bis@iet<wbr>f.org</a>; <a href=
=3D"mailto:6man-chairs@ietf.org" target=3D"_blank">6man-chairs@ietf.org</a>=
<span><br>
<b>Subject:</b> Re: Last Call: &lt;draft-ietf-6man-rfc4291bis-07<wbr>.txt&g=
t; (IP Version 6 Addressing Architecture) to Internet Standard<u></u><u></u=
></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">On Feb 16, 2017, at 13:25, <a href=3D"mailto:otroan@=
employees.org" target=3D"_blank">
otroan@employees.org</a> wrote:<u></u><u></u></p><div><div class=3D"m_-4753=
189871988625434h5">
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">On Feb 13, 2017, at 14:32, David Farmer &lt;<a href=
=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt; wrote:<=
u></u><u></u></p>
</blockquote>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">I have concerns with the following text;<br>
<br>
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to<br>
=C2=A0 =C2=A0128 [BCP198].=C2=A0 For example, [RFC6164] standardises 127 bi=
t prefixes<br>
=C2=A0 =C2=A0on inter-router point-to-point links. However, the Interface I=
D of<br>
=C2=A0 =C2=A0all unicast addresses, except those that start with the binary=
 value<br>
=C2=A0 =C2=A0000, is required to be 64 bits long.=C2=A0 The rationale for t=
he 64 bit<br>
=C2=A0 =C2=A0boundary in IPv6 addresses can be found in [RFC7421]<u></u><u>=
</u></p>
</div>
</div>
</blockquote>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</blockquote>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">The third sentence seems to limit exceptions to 64 b=
it IIDs to exclusively addresses that start with binary vale of 000.=C2=A0 =
There are at least two other exceptions from standards track RFCs, that sho=
uld be more clear accounted for in this
 text. [=E2=80=A6]<u></u><u></u></p>
</blockquote>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</blockquote>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">[=E2=80=A6]<u></u><u></u></p>
</blockquote>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal">The challenge is to find text that enforces the 64-b=
it boundary policy (ignoring the technical arguments for a moment), and at =
the same time ensures implementors do the right thing and make their code h=
andle any prefix length. Of course
 these are interdependent and doing the latter makes it harder to enforce t=
he first.<u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">I propose the following:<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">IPv6 unicast routing is based on prefixes of any val=
id length up to 128 bits [BCP198]. However, as explained in [RFC7421], the =
Interface ID of unicast addresses is generally required to be 64 bits in le=
ngth, with exceptions only provided
 in special cases where expressly recognized in IETF standards track docume=
nts.<u></u><u></u></p>
</blockquote>
</blockquote>
</blockquote>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Trying to help out here.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">--james woodyatt &lt;<a href=3D"mailto:jhw@google.co=
m" target=3D"_blank">jhw@google.com</a>&gt;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div></div></div>
</div>

<br>------------------------------<wbr>------------------------------<wbr>-=
-------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">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/l<wb=
r>istinfo/ipv6</a><br>
------------------------------<wbr>------------------------------<wbr>-----=
---<br>
<br></blockquote></div><br></div></div>

--f403045e2fee1fd9d30548b41614--


From nobody Thu Feb 16 23:44:17 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E332D12951F; Thu, 16 Feb 2017 23:44:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nyAZe_x3iWns; Thu, 16 Feb 2017 23:44:10 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id C78F6120725; Thu, 16 Feb 2017 23:44:10 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 07:44:07 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 8D88AD788D; Thu, 16 Feb 2017 23:44:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=eLOGcZ/M7ZRKuaX4WX3pN0D4Gis=; b= J9bigSVB1RJNv3wsEGRHduSMb2gR/rVgy1cKOGqtSMtVRr5ZmpI/C/49xfRNXDkx 6PaMJydTuMczZjIvxHCFuN6NSswlxD99vcvu1/wlzVEIGvP/spjGAegqtR/epQMf SBoqPmna+nEYkIbSdqfYqUQvcfmXTI7vNmmYS2kSNSc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=DTYWh4/kVUYXFXtH80zFump N4DgGDgIZmViqCcGDSK+aQZKphLqBTXq/4WjaXV8hlp0Zvg4ksDzDqABWrpLEu/2 dX3iUYQwNPFqpO8jalNYH8uM2o2+Ekihp19Oc829ZIs+Nbfv4EwudvkI6F88K1m/ VfVMpsMU23XBjfunKRow=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 58FF0D788B; Thu, 16 Feb 2017 23:44:07 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id A4D3F8BEA6D6; Fri, 17 Feb 2017 08:44:21 +0100 (CET)
From: otroan@employees.org
Message-Id: <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_9D922476-13A8-44EA-96F3-AB592440A936"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 17 Feb 2017 08:44:20 +0100
In-Reply-To: <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
To: james woodyatt <jhw@google.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C7VNDlfNUGlbxOm0UyzOhgrrUkw>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 07:44:12 -0000

--Apple-Mail=_9D922476-13A8-44EA-96F3-AB592440A936
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

James,

4291:
   For all unicast addresses, except those that start with the binary
   value 000, Interface IDs are required to be 64 bits long and to be
   constructed in Modified EUI-64 format.

4291bis:
   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
   on inter-router point-to-point links.  However, the Interface ID of
   all unicast addresses, except those that start with the binary value
   000, is required to be 64 bits long.  The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421]

Proposal:
   IPv6 unicast routing is based on prefixes of any valid length up to
  128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
   of unicast addresses is generally required to be 64 bits in length, with
   exceptions only provided in special cases where expressly recognised
   in IETF standards track documents.

I think that's a good proposal.
Perhaps with s/is generally required to be/are/

Best regards,
Ole

--Apple-Mail=_9D922476-13A8-44EA-96F3-AB592440A936
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpqnVAAoJEL7aWKiYQt922ZcQALAgKJ2Q+aUoRKkf527JGFoW
pFyLTc17MSDTu55NgEVGTnXl0PMkCwxM2Us3rBeyFFLySpc7FZAjwWPIRKhoQqjp
xS+x08X9F5v0CxMP/MNP9OMPXAN2ECOkuzdr2gT6qkHEhGvylDOsN6IC+7wN35YV
r9tojVjecyuAooG9DAHlB3yqBZPYVPM9h64d6OtT22qQxGomZsb/cnOcUmrPEIL+
WoyJ1QLJoZOBgtg1uax7ZbVrmlN4DoK5vnnY+uVczXQjacyGVYRCj6BdKURlXuLU
2QEmVTqS0XtRayn++Zp6vs312DnDYGmD377Ekxsndwwnm8n+tuOZvpMlXhdnbmXj
NStYrflppqO8ClaOxqkly3FaYI4X38vjGmd57+GIjbT7n0GZ4K5CCQgMUe0VRz5b
9CYIU66IFBvGcKftv41+jQZb/5x3vfLhkhatH82mHbvHRg6zzJZb4O086q1u67OT
m1htAZxRAWQ3Gr0ENwrq3BYlI9xpm9sIlHidqbs9UQsul4KOQg9Wz/CUXtiVEJM6
Naarfb1xufQGlrh1LNOUSkL0WqpIAA03fGczp5fUuERtSm7hyQyiXgnaPFWqvKT9
qrtMVkBCVAqskYlpusO8/uSR8KZtcyCQEfJkZio2r2iDexu7fdJueKqrvFIXJJBO
1p/FJAryOJiQ+ypF+qQ7
=jbY1
-----END PGP SIGNATURE-----

--Apple-Mail=_9D922476-13A8-44EA-96F3-AB592440A936--


From nobody Fri Feb 17 02:32:52 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693521297C4 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:32:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.332
X-Spam-Level: 
X-Spam-Status: No, score=-5.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 CCZln3ItK1CB for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:32:49 -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 CDBE41296DE for <ietf@ietf.org>; Fri, 17 Feb 2017 02:32:48 -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 v1HAWkuR013996 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:46 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9851D2044F9 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:46 +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 8E3F7202A0D for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:46 +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 v1HAWjmh020761 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:45 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <m2wpcpdgiv.wl-randy@psg.com> <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <7248f845-7ee4-4448-aefa-b48dda486ac7@gmail.com>
Date: Fri, 17 Feb 2017 11:32:44 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t71RJit7U-JnPdlCaPa67WlnIAM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 10:32:50 -0000

Le 16/02/2017 à 21:52, Mark Smith a écrit :
> On 17 February 2017 at 07:31, Randy Bush <randy@psg.com> wrote:
>>> What I think we need is to make it clear that there are real
>>> exceptions to 64, and it is therefore not acceptable to embed 64
>>> in code.
>>
>> close.  64 is the exception; so slaac can work.
>>
>> hiding the steaming classful pile in cute places around the
>> document only gets folk more annoyed.
>>
>
> So what is your objection to having a well-known addressing
> structure?
>
> Objecting to it, calling it "classful", is implying that it is
> exactly the same as IPv4 classful addressing. I don't think IPv6 is.

Perhaps not precisely the same, because there are no 'IPv6 classes'.

But, an IPv4 Class C is quite the same as an IPv6 prefix/64.  The limit
is 24bit in IPv4, and 64bit in IPv6.  True, the forwarding in IPv6 is on
bit-boundary where classful IPv4 is on byte-boundary, yet an otherwise
bit-boundary IPv6 _>/64_ route can not reach computers relying on
SLAAC/Ethernet /64.

That makes it a limit, which in turn generates what appears to be an
'IPv6 class' - the leftmost 64bits.

Alex

>
> My memory of classful IPv4 addressing is that it not only specified
> an addressing structure, it also specified a forwarding method based
> on that structure. (e.g., the default route was only used if there
> weren't any routes in the table that had the class matching the class
> of the destination address.)
>
> IPv6 doesn't. The addressing structure doesn't specify how different
>  bits are used during forwarding - all 128 are, using a longest match
>  per BCP 198.
>
> So IPv6 specifically separates the addressing structure from the
> forwarding method. I think calling that "classful" is
> mischaracterising it.
>
> Regards, Mark.
>
>
>> randy
>>
>> --------------------------------------------------------------------
>>
>>
>>
IETF IPv6 working group mailing list
>> ipv6@ietf.org Administrative Requests:
>> https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
>>
>


From nobody Fri Feb 17 02:38:02 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7701297C4 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:38:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 18A9j-4DQsoA for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:37:58 -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 0019D1298D2 for <ietf@ietf.org>; Fri, 17 Feb 2017 02:37:57 -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 v1HAbtib026211 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:37:55 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BE2E120464C for <ietf@ietf.org>; Fri, 17 Feb 2017 11:37:55 +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 B4F32202A0D for <ietf@ietf.org>; Fri, 17 Feb 2017 11:37:55 +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 v1HAbtvG027908 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:37:55 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <8767e370398045af989467a63747b29e@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr2eg1VVetdURn7aH_1Y7sdqEjRQPzuP7a7=6vH0UQOQug@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b21935d0-e9f0-5e2e-6529-5c35f34b1bd3@gmail.com>
Date: Fri, 17 Feb 2017 11:37:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr2eg1VVetdURn7aH_1Y7sdqEjRQPzuP7a7=6vH0UQOQug@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D7TrTC2yNEQX5Dr21XRcqUMmJP0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 10:38:01 -0000

Le 17/02/2017 à 07:32, Lorenzo Colitti a écrit :
> That's a valid opinion but it does not reflect the current state of the
> IPv6 standards.
>
> Again, let's bear in mind that this discussion is not about changing the
> standard, but about reclassifying the existing standards.

I disagree.

The discussion is about advancing a certain standard.

The advancement direction in which limits are reinforced (64bit seems 
now 'required') is not the right direction.

I prefer the old "IPv6 architecture".

Alex

> We can discuss
> changing this part of the standard to our heart's content, but *in 6man,
> on another document*, not here.
>
> I would be rather surprised if such a discussion ever reached consensus,
> but I certainly wouldn't want to dissuade anyone from trying.
>
> On Fri, Feb 17, 2017 at 7:38 AM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>> wrote:
>
>     RFC 7421 is informational. And many considerations are not so
>     critical anymore, on a specific stateful format.____
>
>     __ __
>
>     I don’t think we need to reinforce the notion that IPv6 must have
>     64-bit prefixes, since that is not true now, and should not even be
>     made to apply to the currently unused address space. So, I’m opposed
>     to text that implies any such restriction, with the exception of (a)
>     currently used unicast  address space, (b) SLAAC, (c) ULA, possibly
>     other exceptions.____
>
>     __ __
>
>     In other words, *exceptions belong to requiring the 64-bit IID*. Any
>     RFC that implies otherwise, IMO, ought to be subject to a –bis
>     version.____
>
>     __ __
>
>     Bert____
>
>     __ __
>
>     __ __
>
>     *From:*ipv6 [mailto:ipv6-bounces@ietf.org
>     <mailto:ipv6-bounces@ietf.org>] *On Behalf Of *james woodyatt
>     *Sent:* Thursday, February 16, 2017 17:21
>     *To:* IETF-Discussion Discussion <ietf@ietf.org <mailto:ietf@ietf.org>>
>     *Cc:* 6man WG <ipv6@ietf.org <mailto:ipv6@ietf.org>>;
>     draft-ietf-6man-rfc4291bis@ietf.org
>     <mailto:draft-ietf-6man-rfc4291bis@ietf.org>; 6man-chairs@ietf.org
>     <mailto:6man-chairs@ietf.org>
>     *Subject:* Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP
>     Version 6 Addressing Architecture) to Internet Standard____
>
>     __ __
>
>     On Feb 16, 2017, at 13:25, otroan@employees.org
>     <mailto:otroan@employees.org> wrote:____
>
>         On Feb 13, 2017, at 14:32, David Farmer <farmer@umn.edu
>         <mailto:farmer@umn.edu>> wrote:____
>
>             __ __
>
>             I have concerns with the following text;
>
>                IPv6 unicast routing is based on prefixes of any valid
>             length up to
>                128 [BCP198].  For example, [RFC6164] standardises 127
>             bit prefixes
>                on inter-router point-to-point links. However, the
>             Interface ID of
>                all unicast addresses, except those that start with the
>             binary value
>                000, is required to be 64 bits long.  The rationale for
>             the 64 bit
>                boundary in IPv6 addresses can be found in [RFC7421]____
>
>             __ __
>
>             The third sentence seems to limit exceptions to 64 bit IIDs
>             to exclusively addresses that start with binary vale of
>             000.  There are at least two other exceptions from standards
>             track RFCs, that should be more clear accounted for in this
>             text. […]____
>
>         __ __
>
>         […]____
>
>         The challenge is to find text that enforces the 64-bit boundary
>         policy (ignoring the technical arguments for a moment), and at
>         the same time ensures implementors do the right thing and make
>         their code handle any prefix length. Of course these are
>         interdependent and doing the latter makes it harder to enforce
>         the first.____
>
>     __ __
>
>     I propose the following:____
>
>     __ __
>
>                 IPv6 unicast routing is based on prefixes of any valid
>                 length up to 128 bits [BCP198]. However, as explained in
>                 [RFC7421], the Interface ID of unicast addresses is
>                 generally required to be 64 bits in length, with
>                 exceptions only provided in special cases where
>                 expressly recognized in IETF standards track documents.____
>
>     __ __
>
>     Trying to help out here.____
>
>     __ __
>
>     __ __
>
>     --james woodyatt <jhw@google.com <mailto:jhw@google.com>>____
>
>     __ __
>
>     __ __
>
>     __ __
>
>
>     --------------------------------------------------------------------
>     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>
>     --------------------------------------------------------------------
>
>


From nobody Fri Feb 17 02:42:49 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96F141294EF for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T2M0KpzMwPgt for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 02:42:46 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 65CCD129986 for <ietf@ietf.org>; Fri, 17 Feb 2017 02:42:41 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 10:42:40 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 70B7ED788D; Fri, 17 Feb 2017 02:42:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=iSK2i4vQL2u59dTHMDPZCG1NQVQ=; b= hjWe/qeoa+HnGGBDbrVNFg6sZ+Tmi1+kCZoyxuX7xwI7rqGnFbktQFInxAvyPTEa UbNbD/eLI6Dpt8Jnr0rAViajf1zkEuAukCADtjIFBi11u6WNg1J9Yvpr1cy0aW1E d25VHaMlpHkgvfLaYYb2O9FHQJAiW8CJVzLxZrqNi5g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=QL4krqg1LdCjL+fea9F7M+9 9JxGThr0Tak96/ptPAI/oa9rUOcUnRGgj1KxMLkKEMBLG+rDdYb5mDTk7EDHxLnk pVSt3wqaw3C8tOOmDyoG7SkdT6CaBmhLy7A0nZt8oicJLIDOMLTj7zUHg9X9Ottw 1E4ot4u/QH8PsYadlJGo=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 3C1AAD788B; Fri, 17 Feb 2017 02:42:40 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D76BC8C1FA47; Fri, 17 Feb 2017 11:42:54 +0100 (CET)
From: otroan@employees.org
Message-Id: <ED07BD47-5305-4DAC-92C0-D3D923B64879@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_DE8A1A6C-263A-45F6-9343-B4C5EA8EC381"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 17 Feb 2017 11:42:53 +0100
In-Reply-To: <7248f845-7ee4-4448-aefa-b48dda486ac7@gmail.com>
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <m2wpcpdgiv.wl-randy@psg.com> <CAO42Z2xVFsV2CvPsJa3yZnsVg2_Ln1-4GP4e-GU2saJSMw3j2w@mail.gmail.com> <7248f845-7ee4-4448-aefa-b48dda486ac7@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iKf3RQ11npfR1i32JSf-QgdIqd4>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 10:42:47 -0000

--Apple-Mail=_DE8A1A6C-263A-45F6-9343-B4C5EA8EC381
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> Objecting to it, calling it "classful", is implying that it is
>> exactly the same as IPv4 classful addressing. I don't think IPv6 is.
>=20
> Perhaps not precisely the same, because there are no 'IPv6 classes'.
>=20
> But, an IPv4 Class C is quite the same as an IPv6 prefix/64.  The =
limit
> is 24bit in IPv4, and 64bit in IPv6.  True, the forwarding in IPv6 is =
on
> bit-boundary where classful IPv4 is on byte-boundary, yet an otherwise
> bit-boundary IPv6 _>/64_ route can not reach computers relying on
> SLAAC/Ethernet /64.
>=20
> That makes it a limit, which in turn generates what appears to be an
> 'IPv6 class' - the leftmost 64bits.

Having a single class does not make it classful.

If you want the 64-bit boundary changed. This is not the right context =
for it.
Write a draft. Justify why 64-bits of prefix isn't enough for you.

Ole

--Apple-Mail=_DE8A1A6C-263A-45F6-9343-B4C5EA8EC381
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYptOuAAoJEL7aWKiYQt9253IP/3DB9k+8af5ONNlQa1E7RADw
VUDZ8BCRxIj+Pv2B6URh+NFPgpF6vIcK3oQdfKFHpdAJDXvX8141PnKaj91Ko845
umT2cr2aIpULYF8qhddhFgHR01fBy6BURVVs1iEnM4fE1z9CoxGDkm1YtDFRzMcE
aH0opcKKzccP95mMiSzW6xpExEdV5wnYlxDJwJ9LVb0Md/TBzvj5O93S39Dz+zqN
LvEVOMMEQC5IWGlIBfzvbER4Scj1kraDgb0TrA41xmxqEoHDGxzaHaEF5lq6mSBW
OmIoVPtD/uCQaUIUuV2uTm3L/LfLg4btn9y216aky2EqrK5S/0h1WQOwV5ruy+9R
+K5zMEuwlq4V0OboIM3b6InInvUwqwyxm/NHytVhAOdfLZx8SwpdXKt0jg2w1ywI
BTDEoTJ/XbgZ1rT+ONsBnuEH0RBv7ReBCtTJUFFjjDEQ2RReKW1Aj32Zss8HYI57
MajZvR+Wkrd5J3VsnilfL5HIuNyr5EJ74dEFB29/EQnQ9zCWs8fmmNkvr8umkjXQ
0T5p1VpqJLcX8XXq8TQU935xdvK+vsup9g9Uy73sKLmM4GuzPAEF1gIp14XraMMS
zJ1dho7Vk3lKGaTgQnRFtdsjKl8FNfcsUamVOFP43Vd8uIBx7If0biZ/9AYpJZBH
0udDtb73y9rzhvW/hRri
=Zx4/
-----END PGP SIGNATURE-----

--Apple-Mail=_DE8A1A6C-263A-45F6-9343-B4C5EA8EC381--


From nobody Fri Feb 17 04:11:21 2017
Return-Path: <dhruv.dhody@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 899191299BD; Fri, 17 Feb 2017 04:11:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 l908I6ahpKjU; Fri, 17 Feb 2017 04:11:03 -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 D7C8B1299C5; Fri, 17 Feb 2017 04:11:01 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml706-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAU18360; Fri, 17 Feb 2017 12:10:59 +0000 (GMT)
Received: from BLREML701-CAH.china.huawei.com (10.20.4.170) by lhreml706-cah.china.huawei.com (10.201.5.182) with Microsoft SMTP Server (TLS) id 14.3.301.0; Fri, 17 Feb 2017 12:10:58 +0000
Received: from BLREML501-MBB.china.huawei.com ([10.20.5.200]) by blreml701-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Fri, 17 Feb 2017 17:40:48 +0530
From: Dhruv Dhody <dhruv.dhody@huawei.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Subject: RE: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Topic: [Pce] Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM9gtp/PSv/bkEq3uaeNA/BLdaFsmcuQ//+o4ACAAMp5QA==
Date: Fri, 17 Feb 2017 12:10:47 +0000
Message-ID: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.195.40.180]
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.0A020202.58A6E853.0312, 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: 7a98ac300b3205c6cd833c86bba88d68
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXNz6q6e6MzmBEQDqa-_kr4-KuA>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:11:05 -0000

Hi Joel,=20

In my opinion the motivation behind section 5.8.2 is to make sure that, if =
a PCC needs to request a path to be computed by PCE immediately, PCC should=
 use the existing PCReq message to achieve that.=20
=20
Can the PCC delegate an unsignalled LSP to PCE via PCRpt message? In my int=
erpretation it can, in some cases[1]. I would let the authors confirm on th=
is.=20

Thanks,
Dhruv

[1] https://mailarchive.ietf.org/arch/msg/pce/bexK_Nc2wHgQzV-XUC8lqMec8zY

> -----Original Message-----
> From: Joel M. Halpern [mailto:jmh@joelhalpern.com]
> Sent: 17 February 2017 10:13
> To: Dhruv Dhody <dhruv.dhody@huawei.com>; gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
>=20
> So it is intentional that this draft prohibits that behavior (PCE driven
> establishment)?
>=20
> Yours,
> Joel
>=20
> On 2/16/17 11:35 PM, Dhruv Dhody wrote:
> > Hi Joel,
> >
> > Regarding your comment -
> >
> >> Is the intention to prohibit the driving of LSP creation from the
> >> PCE?
> >
> > This capability is described in -
> > https://tools.ietf.org/html/draft-ietf-pce-pce-initiated-lsp-07
> > (document expired recently, authors should refresh it)
> >
> > Thanks,
> > Dhruv
> >
> >> -----Original Message-----
> >> From: Pce [mailto:pce-bounces@ietf.org] On Behalf Of Joel Halpern
> >> Sent: 17 February 2017 09:08
> >> To: gen-art@ietf.org
> >> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org;
> >> ietf@ietf.org
> >> Subject: [Pce] Review of draft-ietf-pce-stateful-pce-18
> >>
> >> Reviewer: Joel Halpern
> >> Review result: Ready with Issues
> >>
> >> I am the assigned Gen-ART reviewer for this draft. The General Area
> >> Review Team (Gen-ART) reviews all IETF documents being processed by
> >> the IESG for the IETF Chair.  Please treat these comments just like
> >> any other last call comments.
> >>
> >> For more information, please see the FAQ at
> >>
> >> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> >>
> >> Document: draft-ietf-pce-stateful-pce-??
> >> Reviewer: Joel Halpern
> >> Review Date: 2017-02-16
> >> IETF LC End Date: 2017-02-28
> >> IESG Telechat date: 2017-03-16
> >>
> >> Summary:
> >>
> >> Major issues:
> >>
> >> Minor issues:
> >>    At the end of section 5.4, the text talks about a PCE accepting
> >> status updates even if the  stateful capability has not been
> >> negotiated.  Which is fine.  But as written, the text seems to say
> >> that doing so means that the PCE will be able to "build and maintain
> >> an up to date view of the state of the PCC's LSPs".  However, if the
> >> capability has not been negotiated, I do not see how the PCE can
> >> count on getting full and timely state reports.  Trying to infer why
> >> a PCC is sending such a report in the absence of the agreement seems
> problematic.
> >>
> >>     This comment may be a misunderstanding or mis-expectation on my pa=
rt.
> >> I would have expected one of the ways o using an active PCE is to
> >> have the PCE decide (under suitable circumstances) that an LSP is
> >> needed between two PCCs.  As far as I can tell, the text in section
> >> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
> >> Update Request (in a PCUpd message) for an LSP that has been
> >> delegated to it.  At that point I thought that a PCC could delegate a
> >> block of unsetup LSPs to the PCE.  But then looking at 5.8.2, the
> >> text states that for each delegation, the PCC must request an initial
> >> path.  That seems to prohibit delegating a block of LSPs for future
> >> updates.  Is the intention to prohibit the driving of LSP creation fro=
m
> the PCE?
> >>
> >>     I have looked but I can not find the text explaining the
> >> significance and use of the Symbolic path name.  It is mandated by
> >> the draft.  There seems to be an implicit assumption taht it is
> >> needed by the PCE.  If the explanation of how or why it is needed is n=
ot
> present, it should be.
> >>
> >> Nits/editorial comments:
> >>     Should the text on the S bit in section 7.3 (the LSP Object
> >> definition) note that it should be set to 0 on all messages sent by th=
e
> PCE?
> >> Should that also be stated for the R bit?  And the O bits?
> >>
> >>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do
> >> some additional work.  I understand why teh work is needed.  But this
> >> does not seem to match the RFC 2119 meaning of SHOULD as it does not
> >> apply to eitehr the implementor or the implementation.
> >>
> >>
> >> _______________________________________________
> >> Pce mailing list
> >> Pce@ietf.org
> >> https://www.ietf.org/mailman/listinfo/pce


From nobody Fri Feb 17 04:48:32 2017
Return-Path: <nite@hq.sk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD2FB129A14; Fri, 17 Feb 2017 04:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0XE4I5kSsI6; Fri, 17 Feb 2017 04:48:26 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB86129A12; Fri, 17 Feb 2017 04:48:25 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id 7203D240529; Fri, 17 Feb 2017 13:48:22 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487335702; bh=oX6kpQsn5dx7CI9Zbold9Pk2bux/AGqRGlPDAOP+AGA=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=V2b53Mwl9hDnAJf8flTVN8mvCTyvMfZy6+TL12Ta67OIGuN1xd1Z+Ew74o3q+d8go NAN7754+hreOOgv4t9B727fHlItKimbW3Y0eiJsGS9ZOb8R9+1mfOGyZI8Z2cdSCeK dqqdkH6UH8728K8471ixVKlsxiZ86u3/+kctqgpk=
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: Dhruv Dhody <dhruv.dhody@huawei.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com> <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
From: Robert Varga <nite@hq.sk>
Message-ID: <473033f8-4883-40e9-79e0-3bd15428655e@hq.sk>
Date: Fri, 17 Feb 2017 13:48:13 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SqdVNxODsMp80xP53OVVMx3OCm2MNjDps"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZdO-T4uF20W7bnzQzpKECMuInjA>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:48:28 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--SqdVNxODsMp80xP53OVVMx3OCm2MNjDps
Content-Type: multipart/mixed; boundary="w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: Dhruv Dhody <dhruv.dhody@huawei.com>,
 "Joel M. Halpern" <jmh@joelhalpern.com>, "gen-art@ietf.org"
 <gen-art@ietf.org>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org"
 <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <473033f8-4883-40e9-79e0-3bd15428655e@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
 <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
 <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
 <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>
In-Reply-To: <23CE718903A838468A8B325B80962F9B8CA7205F@blreml501-mbb>

--w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 01:10 PM, Dhruv Dhody wrote:
> Hi Joel,=20
>=20
> In my opinion the motivation behind section 5.8.2 is to make sure that,=
 if a PCC needs to request a path to be computed by PCE immediately, PCC =
should use the existing PCReq message to achieve that.=20
> =20
> Can the PCC delegate an unsignalled LSP to PCE via PCRpt message? In my=
 interpretation it can, in some cases[1]. I would let the authors confirm=
 on this.=20

Yes, it can.

The second paragraph on 5.8.2 is not intended to restrict usage of
delegation, but rather highlight the scenario where the LSP is
established without PCE's help.

Regards,
Robert


--w5DVhE6HMMwdnkNnNpAJbcasS3s9dpOqF--

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

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvEOCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDTwPwP/1NyUwji
DBvCawC7rMMlStn+vqkjO9oZ64b4SqnWu5rrfOzDZO5ilSLsu0M/ghnCQDkZws48
mV1gSxSXrP8q2bCAddwyMjaAoQUa8JkO1ID1Tmvr4j+anghZXZs4IH1ruB1JJ1w7
EcexCePLgQ/rAA7M4wq2CD0p64wr0EOUAex8tvK30H8uwyDcR0EvK+lA42IWByR+
A0/PBZwJMpatPAytt1EechnkXC9rBGCedjrFmaBHphQFe5JiVKR/9Uuk1ywmONGs
McBRyJjYwhNBkmypnCu6MftZlZhDWPy6IRHGM6Re/Tzh56SWnTglYv1R0v50IGCe
x3ydjvn51uD6C/ldbt8fYnJ6cnF9ootPs+n9j+K2/qscQ4Yy1WwPeHfqwhsuP3LN
0IFsTB7zZLN1JIyTrEW0n1E/NKOeXqSAzijY4fb5DZUZo8QcYx4CEMk+N2NE9Jrx
9GlqmRDcN52Cougs3D50RZBByyOyMorayiLPQjysZrBxOI6KcumDmlshdDlb/1p0
Il0UMwIZAIUrOwcYNfhy8REQhaIZLBVZukuJGQJ6xiKzfNtLcQfyPLX3bIEAFF44
keGbxR7iShlvNDe2IM80lPVyO0vi/78p6oncXqy0RrdtdaentnTWDD3F9YQC5fIN
gC0AmGEsVygVtaXAbD7XW+J9iFgBdoAcxFg8
=wpRh
-----END PGP SIGNATURE-----

--SqdVNxODsMp80xP53OVVMx3OCm2MNjDps--


From nobody Fri Feb 17 04:49:43 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D39A71299BD; Fri, 17 Feb 2017 04:49:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.788
X-Spam-Level: 
X-Spam-Status: No, score=-3.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctuSZYsEMUVj; Fri, 17 Feb 2017 04:49:40 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40094.outbound.protection.outlook.com [40.107.4.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2AE4129A14; Fri, 17 Feb 2017 04:49:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=rjQjsPieW0u/lftixV/1hva+/qDeGRFpML0/43Q3cGk=; b=NrNOJVg2gfmkwYgMI999T7KMXTLxF9FAQtGhMUqUBFAEuudxUDIEq6UF/Ur/VOOpROv0cPgwOMkWv/NqrtQcf4X458H5QuffgKF8OoWjHRYq9PoS2ku8Z9mkFtAKH4aLd2ZGh04XeSHyZ1aw8N9cScRM/01aaYS1f0roRD4nd3o=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Fri, 17 Feb 2017 12:49:37 +0000
Message-ID: <031601d2891b$eec55dc0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <otroan@employees.org>, james woodyatt <jhw@google.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 17 Feb 2017 12:46:46 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB5PR0301CA0008.eurprd03.prod.outlook.com (2603:10a6:0:2c::18) To DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9)
X-MS-Office365-Filtering-Correlation-Id: 074ec713-66e2-4909-298d-08d457336ea5
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR07MB1559;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 3:Z9GVYJQj2cbOFX0vDmf5SPuVoxteqSgdhtOnlxFvmBXptRCoFQb9fIO8KcjAD4Uqys8R9WKtnWsvrZ0Ah0vIa/UAm9ReNJIInl2Y6bQfDLB+3rz7YVyUEzCyfF2t/ryVq9HzoSfTR0kSYo1L1hwVKN1H4BACKWhPtM4TcV/zrQCL8HoM7d74985tkUnn+yKvAXG0FNNDpOB4HzGRTNb8vmTWRSIMYo7BM4O+C7K0XCJks+rezeZbX7egkUA26kEZAd+0iFBjDyRJjgWyMOrLNg==; 25:1xcxLIbPD/WuHT3NJ/ebaLTOEPQ3z9fVA+trSCdBkWogbTY+iI3JoFXaPmf4KtT+MvnJQj+MndqKT4DzcbdcbNDVzQLDYroeGCyP8SyypOaR/nVN21jDUyOB9q9TpSe+tI46QCiv7mnwfRX34XesX8cvm1nEVANUxBhfD/AYXnMorm/sWcTypI3IhazGchxLjF+FcmxmolPOjSXLT82yvOJjFFvJrqMhrOsscYKF3BwVbunyjcSfRbtl2Z9UEPCbbBhuu4Oxya2UNfl8+M/pYMnWFhCF5914R7kzMjR5rMtYxSvreVFnsJC8gVhDNhryr+u6TGKQ+ZsSJBxbATWZwX5CVT1rawHOYXm/Pt+gPJVoD4zslfoVSs1Wj4OcurWydW2w5NA1eB6e2FliCol3RjFQFpo936CwDez5cHX793Snii2hmB0PDLH3YeYy5qFaWX5LrIky1cfRflGSQx1qmQ==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 31:TMO2RfdDZY0DNZFKUvKLNtCd2qgiTVPtnySj0G/0WhdOPKi7k7JextQSnL74LoLsdUi3beYat9KKg6m8AcVvXcg35viWUYRbfye6b7Bh3pXXgX/7TAFVEyX3K4XY2EjKMvecPx3Rgw8Fu35ZtsuD4i9yJ2G1mL1o3NekP1ZLPHfNvFbxluLGkGWu5UsqpBztT2pcVJA8YCN93pTCbsoBxCMSQ7hiBfn4DWUSn1I6cvDu4A+FsPQNwb5rjOB2GpWE0aDSiF8ioRqrLmdfCribFeCIH0cQLut+8yWxp/CBIPU=
X-Microsoft-Antispam-PRVS: <DB5PR07MB1559452B7D63BD88EFC1C635C65D0@DB5PR07MB1559.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(211936372134217)(100405760836317);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123555025)(20161123564025)(20161123558025)(20161123560025)(20161123562025)(6072148); SRVR:DB5PR07MB1559; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1559; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 4:gP0qcQB+CpsgMOcMY6qukkMhRXsOWUg7+3TlOriprmqFPtZamN/462eFDsuK6KkFA7QGfbOSiXwfsufhVMK2fYVgF3Eq3Gvl5Q5FCfQLBGDS57BLVcgZ3bldJ0JYf3FrNuz0SCitE+OtT1DSxIjKqGx+Omvr7Sw6Biu2D8iamei0FChaDEsxYt/9RkHJd6PbgjMYWQkapQBcAvkSH+B3mUE0of/Sts+gBzE/N1mWi1j6gvlah0ShFtE8NcJSBJ8spZnt7tAw9cLbMOKtom469cOAImgXp8cg3osPDX0h6YvS42EKe8Uxd8CmrqDWBaqZpkYNn0byvinFHeXWkNJmuQTNfPh8IzHB4wVhatsT3OrcQp326IVt9Zaz72wHq0rajxhO7mscizx7Z75nxiLHdRPlOrHZhps2X3sWTRV9zOr4pmYSfQ2aSSdn0W454dgyW9yEOTITVgpStwMu1C1BC8iBG0ujLeXG0TVnO8Kqr8M8l+vQM4hFtEuEitM+4LdydkqD4O/h3fYm2E2u+skYsScrHJnT69fo3EftJ6eeTJgT55aEzYlI0ttIevdbV372FDvDw4WkrzlELBnRxJH+kTSKmVVls67dFIqvnZe+Cve5uZG8DLkOh+MgExJBuSH82p0K+mGXn2cdqiAe2SfA7T5NdFy8bOjD8q0OZxzG3SApKWvAQlJXPjsjY5BR7l0z
X-Forefront-PRVS: 02213C82F8
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(199003)(51444003)(377454003)(189002)(6486002)(1556002)(7736002)(106356001)(33646002)(86362001)(81166006)(44736005)(101416001)(81686999)(62236002)(4720700003)(8676002)(50226002)(54906002)(2906002)(230700001)(230783001)(44716002)(561944003)(92566002)(6666003)(9686003)(116806002)(81156014)(93886004)(23756003)(53936002)(38730400002)(6496005)(42186005)(50986999)(6246003)(61296003)(14496001)(47776003)(76176999)(6116002)(3846002)(81816999)(1456003)(105586002)(97736004)(50466002)(4326007)(189998001)(5660300001)(68736007)(66066001)(229853002)(84392002)(305945005)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1559; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; DB5PR07MB1559; 23:3HuRkN0XLzi+0KVDQPSj8gnj7qU9SIjmCfwRyz1?= =?iso-8859-1?Q?e9BnVSDQc/Hnit29AQ3bwvTOehwAks4Ci2rleyIvm3FDI4Xei5gnhtl7vf?= =?iso-8859-1?Q?GPqHZtF9Fc2cmkt7CszJkY61GyR+ZoL/he+wjlhCwtcKcg5439aFaqSh58?= =?iso-8859-1?Q?VhNucjU3gUv9X59GasrCxMzXr9ML63G4E90fUOUXJvugYPflWbx64Xh4gE?= =?iso-8859-1?Q?sybmaBhR8dINc0VIRZozyhG5nMI4amEO0j+hKEOGcvMZQUSRocXYxRZrwm?= =?iso-8859-1?Q?07A6nPo2zTZrgOWKbunDNeB+pB5Wg6DTegAX4yjoIrM+jsStNLZunvLHeG?= =?iso-8859-1?Q?HUN1exKb3Me+ruyGmDGsOpLtRG5MLbFwk4BfUJFrLG1k411teBAm7mbyN9?= =?iso-8859-1?Q?A/ULLKKD/nmmCCI8EVesU2+lIipYjZC9c/39OFPRMK7BOMMQC+hBofgnwy?= =?iso-8859-1?Q?BIaptnwSrUvdDvII3KW3FT3CPqGzcfQ4UqtWIbCVQnRfHeqnHTx38COsqn?= =?iso-8859-1?Q?PncyMOvuRMvZSUlru065NRVcwRsWw2/qgF2K0k/8/BFvymDG2GEb1POqBM?= =?iso-8859-1?Q?HEObhhCwx8p17FfmPwXzh8NyBtbUwIcuWRAU2Y/Tgcfa0bxTpeEA0jcMgf?= =?iso-8859-1?Q?63mH2AjvTli9aDGfvjJm7i+K+lp3j5Fvq7DbhhBFuL+/hj1Tn6rULjIk7K?= =?iso-8859-1?Q?a9tSAI03CS6NZurO+9npGvweu1fFgnGM2UIoBycSieZAqdmf65kb0smFZQ?= =?iso-8859-1?Q?w9RAKBfSv7IF8tmKCurqIPEWoQdlT/1qEhoDwCtbNxR4Pi+dIWsyBqfuLX?= =?iso-8859-1?Q?epixhVvRhjc+BS6KiGPPVlJ3Ogk8EMuJWawfTrQQ090LrvbD1MYg8YT3ai?= =?iso-8859-1?Q?1lXExXjXE11mFZel0lpD5q2BL85ILxBNWUU1Zi2HSJUY4b7q+CB+eJUXdG?= =?iso-8859-1?Q?r5EduByCiYck9QD0ho5CEgj3bq2BTAsL2IyixxQxvkaUpLsdnomrlJCa1V?= =?iso-8859-1?Q?Cj6LeQdYt1AWEPmMBD8J1f/LeuDaYE8HAFG3QewUCMc/AoE4vgA/Yhmk+h?= =?iso-8859-1?Q?vG+B10QxFwCftve5zQTQbxR6gsmdsWS22MlLZl6C4/Z/TxJ+kO3s5MF7z8?= =?iso-8859-1?Q?54fopecwLdhoiDedxLyPUwUoOUGxbmOaLL5L/Fq1PoHoLPBHZyYmil4La/?= =?iso-8859-1?Q?JQZTLdtrq3gKpuPWTtxZoApoRxOiutFxs1OX+QVzKtjR5vHj7kyZwLWox9?= =?iso-8859-1?Q?I9XYXPkIEmR/D/6zjIxCdF+ZaR83fbWleT5MaKtruUm0TwojQv2bbgL+ac?= =?iso-8859-1?Q?bUwd7kBX+KsCvemPywyhRiFIoFemLD5VV57mVYzn7ZObcc8/qLpqSvBBDL?= =?iso-8859-1?Q?zIolquEjRGl88oq0AB4mAX0qwMwJy26CfPxCdH+UyKR+JupPypqOzpr3VX?= =?iso-8859-1?Q?JlEqzT/N/K3xY1zL0lSVWEkDyRf2DxnD0RD9Qa4m1ZQzuHku5fQHnh5ac5?= =?iso-8859-1?Q?1Pndw+kk6XTaflwtWjls=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 6:mGMUeFN/4rJT3/wkWsunPUklnC4XmEMz0GR15fS456V8e52WNp46DreISNAgaQn2oBE/acYKlgSxsr7TU5EMb4mTc3Vf0Aih3nB7qYH2tZNqg73folbEGKZy+VPB8BIzD9smjqdVmazBcyVuUYQPY4KA1z3J4pXnlkG0Yz87CmSkxFAH5mZqThSDimiqzllw16TeHzoG/mNbqHBeZVpFpV0hiRiJo+QDvLlkkcQ6kVoCA01M1n8w0juDNT866bdAE/uz6ks5SvryeiwnaTmH0DgvyDCNrwaesd0cWM8DekMEns5TwQGNd5+WuqiJ0jp/9QXOuij+kHzcPKTHg4kRFhTtcGU4uV/Bh+PKUUTEYRwjHHRlzLcZvPkjkpGlJh7zWe2LWGKkr+i/PYJA9iw8Kw==; 5:GK2l+GX/9laTbq4BEIF9JkUV4KfyRAqf4Le6g8APDMrb+h3zMwXiTqiN7PneQ6O4xk9wKP0mww9wAYO+CWJv94ZOU/UJ4lT6b6/iPsiCVz/sVyyBMtJbxo217VxU3Xa4iABHVE3XRYAoDtsMwUjopQ==; 24:0h3NtSeom7cbYgxta5RcPBxHBFlD1j2rpYpnFYZfViQpMJmhBybK9PMch8WDz3kBLO1Ai5pAmX3qpqoHSONTlhc/IQIZDDQMWUkatoww2I0=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 7:eKaX/7QJ+oq+0uLW/IiQfP3IHO20HOgViXdWFiHYOo9NdvSh1oVCxOjNQbDI+y0voC332QcLDqSBzIGmZKWpPBoPyEVUO1PmcGjNWHabuu2oNDsZrX0fbee/45nCCXM8u8ZI8OwAy/OPmSLSvymR3FlhCehXbWcmCFdSwzfcHJah0sdepqdC9p4YyeWMXtDkkzpHW7wM7k24Lml1Hyg31uEJQdxqqkDBoUG1af7fQielUfPYtTVSczjjrrNRaIH2jlrNTyWt1/KGQPqAYNQuB6qSwtErTGCEaSu+iqIcywQ4YGUWtVY8pNgFF5R/QgOVEXKGcM722tTPwnZld6hbKw==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 17 Feb 2017 12:49:37.3285 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1559
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CtRnFfbXAfh5HvTITrhHsiM90hA>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:49:42 -0000

From: <otroan@employees.org>
To: "james woodyatt" <jhw@google.com>
Cc: <draft-ietf-6man-rfc4291bis@ietf.org>; "6man WG" <ipv6@ietf.org>;
"IETF-Discussion Discussion" <ietf@ietf.org>; <6man-chairs@ietf.org>
Sent: Friday, February 17, 2017 7:44 AM

> James,
>
> 4291:
>    For all unicast addresses, except those that start with the binary
>    value 000, Interface IDs are required to be 64 bits long and to be
>    constructed in Modified EUI-64 format.
>
> 4291bis:
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
>    all unicast addresses, except those that start with the binary
value
>    000, is required to be 64 bits long.  The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
>
> Proposal:
>    IPv6 unicast routing is based on prefixes of any valid length up to
>   128 bits [BCP198]. However, as explained in [RFC7421], the Interface
ID
>    of unicast addresses is generally required to be 64 bits in length,
with
>    exceptions only provided in special cases where expressly
recognised
>    in IETF standards track documents.
>
> I think that's a good proposal.
> Perhaps with s/is generally required to be/are/

Ole

I would go further on the grounds that this is still somewhat woolly.  I
would say

Proposal':
  IPv6 unicast routing is based on prefixes of any valid length up to
 128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
  of unicast addresses is required to be 64 bits in length; any
exceptions
  must be specified in IETF standards track documents.


It would be nice to have something IANA-like with different categories
of what can update what, with this being at the higher level, the bar
set higher for an Interface ID that is not 64 bits in length, but when
we say 'standards track' we are calling for IETF consensus and IESG
approval and it is hard to see what more could be called for, unless we
say that this is architectural and so the IAB must approve it!

Tom Petch

> Best regards,
> Ole
>
>


From nobody Fri Feb 17 04:52:34 2017
Return-Path: <nite@hq.sk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D0B129735; Fri, 17 Feb 2017 04:52:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aru9aJgDQjMF; Fri, 17 Feb 2017 04:52:27 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85D31299D6; Fri, 17 Feb 2017 04:52:27 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id 2F2D1240529; Fri, 17 Feb 2017 13:52:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487335946; bh=nYHBf/DxSJJFBIwUat3UILzGdypD2N0/k62t6go4k2A=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=S35AkkIQQcrPYgG0w4dpbERrQDLrQ8NUfYSr0Gsnjcim5Fe+wrYcU90ss05LM/AZP z8PResfVGifIhSREV20/42ZEMQE8ThuRpxyw4S7U0bezNnK9cZxFNDEHhOJPFGQDeR ibcyiTgYJz3wyocHQ3PAGsZ0InIXcHzWwEYYZw0I=
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb> <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
From: Robert Varga <nite@hq.sk>
Message-ID: <d6cf2dbd-98d2-345e-521c-b8847fc894da@hq.sk>
Date: Fri, 17 Feb 2017 13:52:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1R7x5xp7b5khfUNbkIOyiMfQtqQ>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:52:29 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj
Content-Type: multipart/mixed; boundary="spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: "Joel M. Halpern" <jmh@joelhalpern.com>,
 Dhruv Dhody <dhruv.dhody@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org"
 <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>,
 "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <d6cf2dbd-98d2-345e-521c-b8847fc894da@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
 <23CE718903A838468A8B325B80962F9B8CA71836@blreml501-mbb>
 <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>
In-Reply-To: <eacd0409-ad8c-58d4-5270-8c147ba3ae84@joelhalpern.com>

--spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 05:42 AM, Joel M. Halpern wrote:
> So it is intentional that this draft prohibits that behavior (PCE drive=
n
> establishment)?

Yes, it is intentional. pce-stateful-pce is designed so that the PCC
remains the ultimate master of state, in line with RFC5440.

Regards,
Robert


--spadLqQMQw6FnCFVxPXw8UXwnkoH1naPE--

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

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvIHCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDT4bUP/iBiP3ul
HVtc07NLW+y3g2od/95Lx7+OIToyQcv0mA45JJrI/ZPw/Iq8UQfhMQYEejy0/M0n
R3jp1bF2QHcMUqi5Zb1lhioLXDpNZ4AHHpIyjLguc0sE715YIXKTv2jjZrkxYThc
NslqIq0ejfrtB3icfTqe/me9XIH/tP2cwPkqd6jV6FbJj1PsY15IT39daU2kaM/j
hiQVOnpH6QfFx7ewpPtekS+GUR7Y4+462sr0rYhYukpuI26bcb3r88LUkfqOZtCi
HYW5er0HKEojaulZzOxrV1cxwNe+PSxhtbmTWncUALmxF9SVA52+7FIK/BjTfNpe
q4l7FCflUYUnDE057CRjZwovh/aygN4bweLUW+eWqSQpHc8mUgy/q5JLM9XIWr6g
zqw7P4tAlkwSL+fa+SG8TDEKCtLkWftxBdKNty8/LiHHJDMa3Hw4XdqQoalVdz3D
sYmLryebz7rDtNC0N209NK7vo595HOD2Gt348SnwKzGp4NcPh7qkecd47NjkoQh4
Djxn51TR973+kCJHcowNrTneQzeXFlQCS9Zog/Tz6oK0xGQaw2OFW9XyDhKKEsta
PKYrmbnED0LXcfP+QhQdzVPERPpGv8dgadLUZzKs5wQqL1KKoA15iVz8O8Zq8ESf
seEH78Ge0ikgm0QPgLd6JCFmnleKSxP4peYw
=CPFo
-----END PGP SIGNATURE-----

--k4sN8c2s0J89slX2dnBP0b64aqXCrHxfj--


From nobody Fri Feb 17 04:53:22 2017
Return-Path: <prvs=1221b41efe=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A00B129A1A for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 04:53:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsfG_3xG-LMq for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 04:53:19 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 350D1129A11 for <ietf@ietf.org>; Fri, 17 Feb 2017 04:53:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1487335994; x=1487940794; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:CC:Message-ID: Thread-Topic:References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=L5exN/hWb7v9OxI9Oal1tocPV iiDJLx+Zwh7U862HIY=; b=oavAwo3QNWlb4/c7xDwYvU6yBByrst5HHoc4Jfu30 ZkI8GWy6x2MAVhKwuxNd1tkYyWdo1+txQqtfb1tKsuSaJDelPLIJN6SxRUBvvcLb Lim4enPidVKA6Cw0wxIjLeon1eqklEqb4AlR0Ufg3xJ/Sdhw128KLAIITDAiGFyK Rk=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=drMaVAxBVDiYmrQnKC6SVkKUlRczS+dsRvLmIJtHR7Z0oEhBpQ09YlMtlPzo n8ToFceE43cdHsML6PpdWpF1QFvw4cU8r7syYf7etc1/W86+oF8uWRNOv b7vXN6C3jsOb7mZT3CPXOiB5+c21IrK9C8aU16AAuMNQErRh17S5OU=;
X-MDAV-Processed: mail.consulintel.es, Fri, 17 Feb 2017 13:53:14 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 17 Feb 2017 13:53:13 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005369301.msg for <ietf@ietf.org>; Fri, 17 Feb 2017 13:53:12 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170217:md50005369301::B7aun1547AdWnWRB:0000885h
X-Return-Path: prvs=1221b41efe=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1f.0.170216
Date: Fri, 17 Feb 2017 13:53:09 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: <daedulus@btconnect.com>, <otroan@employees.org>, james woodyatt <jhw@google.com>
Message-ID: <ABDEA717-595D-4C41-98EF-A3F33445F5DD@consulintel.es>
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <031601d2891b$eec55dc0$4001a8c0@gateway.2wire.net>
In-Reply-To: <031601d2891b$eec55dc0$4001a8c0@gateway.2wire.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-McB9F-FojpX5YSFbJMmB_-InVg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 12:53:21 -0000

+1

Regards,
Jordi
 

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de "tom p." <daedulus@btconnect.com>
Responder a: <daedulus@btconnect.com>
Fecha: viernes, 17 de febrero de 2017, 13:46
Para: <otroan@employees.org>, james woodyatt <jhw@google.com>
CC: <draft-ietf-6man-rfc4291bis@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, <6man-chairs@ietf.org>
Asunto: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard

    From: <otroan@employees.org>
    To: "james woodyatt" <jhw@google.com>
    Cc: <draft-ietf-6man-rfc4291bis@ietf.org>; "6man WG" <ipv6@ietf.org>;
    "IETF-Discussion Discussion" <ietf@ietf.org>; <6man-chairs@ietf.org>
    Sent: Friday, February 17, 2017 7:44 AM
    
    > James,
    >
    > 4291:
    >    For all unicast addresses, except those that start with the binary
    >    value 000, Interface IDs are required to be 64 bits long and to be
    >    constructed in Modified EUI-64 format.
    >
    > 4291bis:
    >    IPv6 unicast routing is based on prefixes of any valid length up to
    >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
    >    on inter-router point-to-point links.  However, the Interface ID of
    >    all unicast addresses, except those that start with the binary
    value
    >    000, is required to be 64 bits long.  The rationale for the 64 bit
    >    boundary in IPv6 addresses can be found in [RFC7421]
    >
    > Proposal:
    >    IPv6 unicast routing is based on prefixes of any valid length up to
    >   128 bits [BCP198]. However, as explained in [RFC7421], the Interface
    ID
    >    of unicast addresses is generally required to be 64 bits in length,
    with
    >    exceptions only provided in special cases where expressly
    recognised
    >    in IETF standards track documents.
    >
    > I think that's a good proposal.
    > Perhaps with s/is generally required to be/are/
    
    Ole
    
    I would go further on the grounds that this is still somewhat woolly.  I
    would say
    
    Proposal':
      IPv6 unicast routing is based on prefixes of any valid length up to
     128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
      of unicast addresses is required to be 64 bits in length; any
    exceptions
      must be specified in IETF standards track documents.
    
    
    It would be nice to have something IANA-like with different categories
    of what can update what, with this being at the higher level, the bar
    set higher for an Interface ID that is not 64 bits in length, but when
    we say 'standards track' we are calling for IETF consensus and IESG
    approval and it is hard to see what more could be called for, unless we
    say that this is architectural and so the IAB must approve it!
    
    Tom Petch
    
    > Best regards,
    > Ole
    >
    >
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.




From nobody Fri Feb 17 05:12:31 2017
Return-Path: <nite@hq.sk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23D7D129A4D; Fri, 17 Feb 2017 05:12:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=hq.sk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r8uhI40ZxM3l; Fri, 17 Feb 2017 05:12:24 -0800 (PST)
Received: from mail.hq.sk (hq.sk [81.89.59.181]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABA72129A48; Fri, 17 Feb 2017 05:12:23 -0800 (PST)
Received: from [10.137.2.13] (chello085216197060.chello.sk [85.216.197.60]) by mail.hq.sk (Postfix) with ESMTPSA id D34BF240529; Fri, 17 Feb 2017 14:12:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=hq.sk; s=mail; t=1487337142; bh=o5jAr1OUb7BO7sKdh69cuhwaX18XoFa8MjAZFePEx0k=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=JPs7KLiK2nEMOmGRJluDEeDgv1PuAJFfh0f0JgxsP2H50zirKXs0JAzwilDjR/w4o MLyNNfjDlANQLDP6G2M1FlOZbnJLHmC3j5PaRkLadEhvJjrowOwUx28o9k8uCeYRJT Fho8lO2KNl7XhCgNTa77BbDFisiIVtECkn63PQI8=
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
From: Robert Varga <nite@hq.sk>
Message-ID: <ff31899f-23f5-f3b2-41c8-89fc16586c38@hq.sk>
Date: Fri, 17 Feb 2017 14:12:12 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lUwm7gLEv86NcSfEV6VWGrtB49E>
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 13:12:25 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp
Content-Type: multipart/mixed; boundary="CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va";
 protected-headers="v1"
From: Robert Varga <nite@hq.sk>
To: Joel Halpern <jmh@joelhalpern.com>, gen-art@ietf.org
Cc: draft-ietf-pce-stateful-pce.all@ietf.org, pce@ietf.org, ietf@ietf.org
Message-ID: <ff31899f-23f5-f3b2-41c8-89fc16586c38@hq.sk>
Subject: Re: [Pce] Review of draft-ietf-pce-stateful-pce-18
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>

--CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 02/17/2017 04:37 AM, Joel Halpern wrote:
>=20
>     This comment may be a misunderstanding or mis-expectation on my
> part.  I would have expected one of the ways o using an active PCE is
> to have the PCE decide (under suitable circumstances) that an LSP is
> needed between two PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP
> Update Request (in a PCUpd message) for an LSP that has been delegated
> to it.  At that point I thought that a PCC could delegate a block of
> unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states
> that for each delegation, the PCC must request an initial path.  That
> seems to prohibit delegating a block of LSPs for future updates.  Is
> the intention to prohibit the driving of LSP creation from the PCE?

I think this may be a case consistency rotting over the years this draft
has been out there, which also affects my recollection of reasoning
behind the text.

Sections 5.8.1 and 5.8.2 govern how to transition from 'passive
stateful' mode of operation, where the PCC uses PCRpt to communicate
state and PCReq to solicit updates. They are not meant (or at least not
when they were originally written) to restrict the delegation procedure.

The wording of 5.8.2's first paragraph has an implicit unstated goal of
ensuring that the LSP will be set up, i.e. the PCC first makes an
explicit request to acquire the parameters needed to signal the LSP and
then delegates the LSP, thus ensuring a computation is made.

I think it is still valid for PCC to delegate an LSP without performing
5.8.1, in which case the PCE decides when (and if) to push the
parameters required to make the LSP operational.

I do see this as a problem, as the PCC is free to revoke the delegation,
based solely on its local policy, if the PCE fails to fill in the LSP
parameters in a reasonable time frame -- reverting to either local
control or to 5.8.1 mechanics.

Regards,
Robert


--CgMqLfu5gFaSdVclD62Lp9Ku6fOBAL2va--

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

-----BEGIN PGP SIGNATURE-----

iQIoBAEBCgASBQJYpvasCxxuaXRlQGhxLnNrAAoJECsDwSqgzwDTfNQP/3zMSesO
uwaSxSg5QBneclZjThLE51SeaZRjyQ2Qm8lt+zv25WdfQB4uhRQsBl9rfCvadMBT
NMIkIpBzS+o6YePoyi/BswWaAjFeByou4EsBvTttLqvZHkqDa2kKsfNUv0i7oEZr
+x78WedrUC8wxTjHKmRin8eTCjdf/25uRvgLmQBcH7i0tuwn7UQdEj/9+hyeB++8
ZYC8tIORFeJDwB9HTsiNSi2DpBf1nO214fbC9H+8EJF8IGNDheMOwwJWjVqX19ee
U+u1GMU5GVuPeucWATOe1S6DqkQs6zRLuCJShO7WMmn/EKiRq7hVmyzJs1xV+MvB
Og/EASSIyp+5QS/Wp6jHK9dQ3MQ1Dzda2cd/Rud0d6NNE4b5w8haiS8ikRgit0Qn
nlhQlymTjH01b+phjkIJ/AQ5dB3DS1UfKHt3/I5TZ2cr+DZJ58tuLIaFJc2qJQkj
AL9hsYUo62rIn7EeSh/6blv/rmuaWenZDC/BSf18u8q0cKjXy25Q66I2DvbCYwHm
x2/aQF+K3xc5z6NHJEg9mCYlpcHvK0s5+6pe+xV0EBtzGybydPOU0guYf0qCOZRV
P4ZkuWik2GjALYp7AD3zr0wf8VPe1os/3sb5JWJBzHk3bIXu47xiq2qSTaOZ5en5
ITCiVqsWDPJoazom+vIH5VkCyAZmP6mC0J9D
=wNuR
-----END PGP SIGNATURE-----

--2m9KfO1DrPm9cwDIFXFDSXcIamgfLfetp--


From nobody Fri Feb 17 05:37:01 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B276129A20 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 05:37:00 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 KY0iueFXs9iH for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 05:36:58 -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 14EEB1295E1 for <ietf@ietf.org>; Fri, 17 Feb 2017 05:36:58 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 4174880EBC; Fri, 17 Feb 2017 14:36:50 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com>
Date: Fri, 17 Feb 2017 09:40:19 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gdyZd_Ct9TFZzx9oSy6UFydRJ1s>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 13:37:00 -0000

On 02/15/2017 07:18 AM, otroan@employees.org wrote:
> 
>>>> Ole, it is true that we write in English, and there is always room for
>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>
>>>> But in this case we have a demonstrated difference in how people
>>>> understand the existing text.  When we have such a demonstrated
>>>> difference, we have an obligation to address it.
>>>
>>> This particular issue has caused no interoperability issue,
>>
>> May I ask what's the data that support this statement?
> 
> From the shepherd's writeup:
>    IPv6 is implemented on most platforms (hosts, routers, servers, etc.),
>    including proprietary and open source.  A list of products that have
>    received the IPV6 Ready logo can be found at:
> 
>    https://www.ipv6ready.org/db/index.php/public/?o=4

This has nothing to do wth the interoperability problems that may be
caused by a middlebox that inserts EHs.



>> You certainly have no way of knowing this, or whether interoperability
>> issues may arise in the future.
> 
> Yes, we do know if our protocols have interoperability issues.
> Have you implemented RFC2460? I have. So have many others on this list.
> In the context of implementing 2460 there just is no ambiguity and this issue will never arise.

Huh?  Yes, if you connect two IPv6 devices, without a middle-box
inserting EHs in the middle, you will not experience the associated
possible problems. What's the news here?



> What you are talking about is something else. You are talking about the hypothetical "What if someone standardised something new in the future?"

:-)

C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, EH
insertion has reportedly been deployed as a result of the implementation
of such initial versions of the I-D.


You can clarify that EH insertion is banned, and move rfc2460bis to full
stanard (since that's what's supposed to be mature)

You can delay rfc2460->std, and work to update rfc2460.

Now, moving rfc2460 to full std knowingly leaving a hole there such that
after rfc2460 is std you completely change the architecture (e2e vs
!e2e) with EH insertion doesn't seem a serious thing to do, IMO.

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 17 06:12:46 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B880F1295FF for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:12:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FLw8-DkuwX4e for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:12:43 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 0D7DC129558 for <ietf@ietf.org>; Fri, 17 Feb 2017 06:12:42 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 14:12:42 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id C7E29D788E; Fri, 17 Feb 2017 06:12:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=vrNKzF3WTlvtXc3slAupwcyp8Qw=; b= k9RYmG/6k5E5kAFAWGcl6PT3RHLO587q+5r7Xj1b5YmkNgE+cegFvzzlFidyItOL +Je9YPo9wOVmdaiMQJC3ph3+dcJn0mH7yhfjcJW7bOmFMvKXdQyekGo+I/2NseDM NVyjQ99YxJUlQGunNYg3unC5r+E7dPAJQ+D9IXZOFjU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=Yp1riJEpLCQbtnOpV/gvbB1 i7i/wnwXFA1YH9VWACARCUVKoUVslxIPtE+oMnrDtXFbY9BA8DE/TglyBV9HdGE9 TDkXnKfi9DPYPOkC/ANjIzn5wqGeWZeOeVQFNXoHA7UJV0nxwJLh61axhYmGlEuW JgHoe8k54Rwfm58olvsU=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 6B829D788B; Fri, 17 Feb 2017 06:12:41 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 8D5718C5E787; Fri, 17 Feb 2017 15:12:55 +0100 (CET)
From: otroan@employees.org
Message-Id: <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_2CC80298-7A05-4B94-9CA3-18EAD202B496"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 15:12:54 +0100
In-Reply-To: <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FxEHu83mxS-dd7Y1QkdwiDkSGRg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 14:12:44 -0000

--Apple-Mail=_2CC80298-7A05-4B94-9CA3-18EAD202B496
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

It is a simple logical consequence.

Middleboxes do not exist in the IPv6 architecture.
There is no interpretation of 2460 that can lead to an implementor =
inserting headers other places than at the source.
Therefore, there is no interoperability issue in RFC2460 nor any =
ambiguity that needs to be resolved in RFC2460.

We're not writing law, we're writing interoperable protocol.

Ole


> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> wrote:
>=20
> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>=20
>>>>> Ole, it is true that we write in English, and there is always room =
for
>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>=20
>>>>> But in this case we have a demonstrated difference in how people
>>>>> understand the existing text.  When we have such a demonstrated
>>>>> difference, we have an obligation to address it.
>>>>=20
>>>> This particular issue has caused no interoperability issue,
>>>=20
>>> May I ask what's the data that support this statement?
>>=20
>> =46rom the shepherd's writeup:
>>   IPv6 is implemented on most platforms (hosts, routers, servers, =
etc.),
>>   including proprietary and open source.  A list of products that =
have
>>   received the IPV6 Ready logo can be found at:
>>=20
>>   https://www.ipv6ready.org/db/index.php/public/?o=3D4
>=20
> This has nothing to do wth the interoperability problems that may be
> caused by a middlebox that inserts EHs.
>=20
>=20
>=20
>>> You certainly have no way of knowing this, or whether =
interoperability
>>> issues may arise in the future.
>>=20
>> Yes, we do know if our protocols have interoperability issues.
>> Have you implemented RFC2460? I have. So have many others on this =
list.
>> In the context of implementing 2460 there just is no ambiguity and =
this issue will never arise.
>=20
> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
> inserting EHs in the middle, you will not experience the associated
> possible problems. What's the news here?
>=20
>=20
>=20
>> What you are talking about is something else. You are talking about =
the hypothetical "What if someone standardised something new in the =
future?"
>=20
> :-)
>=20
> C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, =
EH
> insertion has reportedly been deployed as a result of the =
implementation
> of such initial versions of the I-D.
>=20
>=20
> You can clarify that EH insertion is banned, and move rfc2460bis to =
full
> stanard (since that's what's supposed to be mature)
>=20
> You can delay rfc2460->std, and work to update rfc2460.
>=20
> Now, moving rfc2460 to full std knowingly leaving a hole there such =
that
> after rfc2460 is std you completely change the architecture (e2e vs
> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>=20
> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492


--Apple-Mail=_2CC80298-7A05-4B94-9CA3-18EAD202B496
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpwTnAAoJEL7aWKiYQt92+40P/3NNUYAn786VQXjBJX+uHgBS
RXNUXy10LpGxze785DnQPMO2bZNRpIEQ18OQBykapB/IE9MVOEAppYmMMJ20rfqL
FrMQF+pRfMAI7B3Z0Gvccj6S3UMO9ydfutZ95EU5MwBLmuvzWL8cAJDcxGb914l8
tCbZyeF7SAl/r0rAqelffgAQbml9qpTRQCiOsazgMd9dPEmD2MR2rf/fnp/Dp2y9
Gw9xxLvs4CUejkV0ObheGk2MlEti4aj2cpwvO2UjSTguVS2PriPElkcrAtoqYqgg
ODdJgp3SfbvP8/VhR8nA2P4XJs1ojN55hkGtN1e69AL02+JEugssZPzRsneWGH05
ZhBF9WdTL7GQgbvMOfftcbscy76LgbQJgL3Q2vsbWbOu1esqLBSYEiJEe9r/2hS8
5kA+ytNpVCb/J3+th9yhi6nndQQxjap3nfOwZ5N77an8JfOdyFIklOc6IE9zGkLy
SuAQAvpAY1LUQwE6okMVBXEIeb1r+3ygB93l95WiV4MqNwbwHTsBDfji4mpZxDef
FoYmItfoilG5aunj1W7ZWAWlHLPqjwWwXpda6jP3oZeYdm2snTxgYyMQlIqricAR
FI42LnWZHgQbFq+MI7Hpdbk2qyL63QU1uqrzN8MwPs4f+PCdRoa3RMaysnwN2KaA
hURSbWV45NMmAqREL/T0
=IB9u
-----END PGP SIGNATURE-----

--Apple-Mail=_2CC80298-7A05-4B94-9CA3-18EAD202B496--


From nobody Fri Feb 17 06:28:30 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC8FB129AA2 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:28:28 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 U52B2GLeO-Ic for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:28:27 -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 5E9D2129AA0 for <ietf@ietf.org>; Fri, 17 Feb 2017 06:28:27 -0800 (PST)
Received: from [IPv6:2001:1291:200:42e::2] (cl-1071.udi-01.br.sixxs.net [IPv6:2001:1291:200:42e::2]) (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 F020B80C03; Fri, 17 Feb 2017 15:28:23 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <292a9832-7d8f-431c-6916-5e1da96a0e83@si6networks.com>
Date: Fri, 17 Feb 2017 11:28:12 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-mLBL6IjuWxp8o1NoaGds0XsZSs>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 14:28:29 -0000

On 02/17/2017 11:12 AM, otroan@employees.org wrote:
> Fernando,
> 
> It is a simple logical consequence.
> 
> Middleboxes do not exist in the IPv6 architecture.
> There is no interpretation of 2460 that can lead to an implementor inserting headers other places than at the source.
> Therefore, there is no interoperability issue in RFC2460 nor any ambiguity that needs to be resolved in RFC2460.

lAt the Last 6man meeting there was a bunch of people arguing that
inserting EHs was "ok" because "it was not explicitly banned" -- the
"interpretation" :-) at the time being that "'processed' doesn't mean
'inserted'"

I asked you whether EH insertion was allowed, and you didn't answer the
question, even after asking multiple times (it should be in the audio
recordings).

Now you say the above. When did you change your mind?


Simple:

1) It was clear to everyone that EH insertion wasn't allowed.

2) Some folks came with a funny interpretation, such that EHs could be
inserted.

3) Lots of supporters of EH-insertion (mostly from the same company)
argued that "it wasn't forbidden". And this wasted lots of people's time.

So a clarification is warranted. That's it.

P.S.: And then folks wonder why people "give up"??

Me, I'm not wasting more time on this. It should be pretty clear to the
IESG what's going on here.

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 17 06:40:06 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E6D6129AAA for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sH75QuFn-KwF for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 06:40:04 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE98129AA7 for <ietf@ietf.org>; Fri, 17 Feb 2017 06:40:03 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 14:40:04 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id AF12ED788A; Fri, 17 Feb 2017 06:40:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=wK/aS4jY5DK0I6gRI8h/l5XbpR8=; b= XSm9xa30q2kX4IHcEXu6qYn1/tdU+rH/7pMffYi9Gdc9o57DxWnx5rRmdi/lv/Ow kazJLZjL2Bpoy2xCU5JO0Ch2wKRkW/QK1XsjjlcvjBMY6wyOOGV27P5HJzS1E4bx 52R6L4Aybjc+h3Y5n4dKGC8Dh8v3vh6PHJMbvaGw4xY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=oeoNihkL039AAtqqxoHlLVK wDgmScZJyFhaifiAcCediodI8McWQX0QH7lkyI5TYD2PcN8bup3mdJt33zK1FGrN YeWWVU/swoahHbtpjHaFvtg3v7AlBeYfgGoB3Ry3e2ZtDNoEynLlr9HfzxvTntty lhgy71Wa3DctZZg3ZwNM=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 42865D788F; Fri, 17 Feb 2017 06:40:03 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 650758C657F9; Fri, 17 Feb 2017 15:40:17 +0100 (CET)
From: otroan@employees.org
Message-Id: <A1EE2939-724D-4683-A119-2D7478C336DA@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_95A8EBFF-5B54-4000-905E-CE79BB5FD852"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 15:40:16 +0100
In-Reply-To: <292a9832-7d8f-431c-6916-5e1da96a0e83@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <292a9832-7d8f-431c-6916-5e1da96a0e83@si6networks.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oyqmMN_DFL5ABbA6GdC9fIDmldg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 14:40:06 -0000

--Apple-Mail=_95A8EBFF-5B54-4000-905E-CE79BB5FD852
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Fernando,

>> It is a simple logical consequence.
>>=20
>> Middleboxes do not exist in the IPv6 architecture.
>> There is no interpretation of 2460 that can lead to an implementor =
inserting headers other places than at the source.
>> Therefore, there is no interoperability issue in RFC2460 nor any =
ambiguity that needs to be resolved in RFC2460.
>=20
> lAt the Last 6man meeting there was a bunch of people arguing that
> inserting EHs was "ok" because "it was not explicitly banned" -- the
> "interpretation" :-) at the time being that "'processed' doesn't mean
> 'inserted'"
>=20
> I asked you whether EH insertion was allowed, and you didn't answer =
the
> question, even after asking multiple times (it should be in the audio
> recordings).
>=20
> Now you say the above. When did you change your mind?

Huh?
I'm not saying anything about header insertion outside the context of =
2460 being allowed or not.
I'm saying that in the context of implementing 2460 header insertion =
cannot come up.

> Simple:
>=20
> 1) It was clear to everyone that EH insertion wasn't allowed.
>=20
> 2) Some folks came with a funny interpretation, such that EHs could be
> inserted.
>=20
> 3) Lots of supporters of EH-insertion (mostly from the same company)
> argued that "it wasn't forbidden". And this wasted lots of people's =
time.
>=20
> So a clarification is warranted. That's it.
>=20
> P.S.: And then folks wonder why people "give up"??
>=20
> Me, I'm not wasting more time on this. It should be pretty clear to =
the
> IESG what's going on here.

Sorry, you lost me.

Ole


--Apple-Mail=_95A8EBFF-5B54-4000-905E-CE79BB5FD852
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpwtRAAoJEL7aWKiYQt92sPQP+QEIxLfZMKckh/rUMS0k7K74
CBNVrY0dl2q1OZeJrCymCGGLnwR/pyjTGn0uhs8KrOVqnfKDuy9jR92Va7xzmjb5
V9hjt9RES/LCrnRYOP1fnn9Z1MDr5I8wTXAxbEVMQ+IOl3LbuktPXYklcZLU6xaB
PcCZZ08BQafg9x4FwterKxzzMEJHiFRE21H5BJ2rdWdelB1P6wuBtedGcMbzQvFA
PqSGvr67QJyDr8ech5I/POM0VgwavjFbF1zAD7fWr6YNqEl/wNNFIcZ+UjdIWL2w
FFergp7bitAaR0pbylo/6n01K8KqL6Rclga+EIZsZ0NuK7Hk54nJfhMEHS8/9GQq
q5pgnlFC6yWnW4dFpjsLB5+Ck4KX8OREnLBdcSDswQM8xO502v2XLBrbuFroZ9hx
UNFl7gkHEZmUPGygA73sSZuhbz1YXeFfJO4BpsZ1y1pt7Z/MHzCmbVRctB6iEHEx
RQTgQDF3tkn7k9r84kU7Njp7eFDo1f/eFC+hKF24mJJcx0TUZ8dZTrErCV065Tks
SInfcEA4kfzADCKHyHLLFScuTQVeLx8Cu+cca7qC49RqL862eOo3Yc99Mdr/xUbW
qTAdHajCORZUsM0/uszmxD6bSzRTjcREtryAqL/d7zRCq5zAgOeWnvt+UqNvMQm1
92U4pphWUZaJFWOjYWKw
=nFCf
-----END PGP SIGNATURE-----

--Apple-Mail=_95A8EBFF-5B54-4000-905E-CE79BB5FD852--


From nobody Fri Feb 17 08:22:33 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20597129487 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 08:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18yRKfxuWEU6 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 08:22:30 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (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 BD85A129561 for <ietf@ietf.org>; Fri, 17 Feb 2017 08:22:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A5EBC3C2E5F; Fri, 17 Feb 2017 08:22:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487348549; bh=SdzbVElrft4EJXyF06rAT9c+9qtYy+4mVAm6K1zhYNk=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=p+sRZEcEtkyysSiTnX5C76fxaVyTOoYuWafeJicZrB5qI4TglQpCkB5YL9fvWISEd TAE5hOyWTHpoCDOoFk87gEV4uGhvC867TIewPl4awo559jp6HzoDQX9aueuIPXXVa6 /A95PTGeTwroaRay0L80IITaZ6G1vxiDtcTC46Uw=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 2B9D13C2E60; Fri, 17 Feb 2017 08:22:29 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, Fernando Gont <fgont@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com>
Date: Fri, 17 Feb 2017 11:22:28 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kdwQMWPnWpijLRHZLu9F3b4m5NI>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 16:22:32 -0000

Given that different people have interpreted 2460 as permitting or 
prohibiting the addition of Extension Headers by intermediate devices, 
there clearly is an ambiguity.


That is the point that concerns me.

Yours,
Joel

On 2/17/17 9:12 AM, otroan@employees.org wrote:
> Fernando,
>
> It is a simple logical consequence.
>
> Middleboxes do not exist in the IPv6 architecture.
> There is no interpretation of 2460 that can lead to an implementor inserting headers other places than at the source.
> Therefore, there is no interoperability issue in RFC2460 nor any ambiguity that needs to be resolved in RFC2460.
>
> We're not writing law, we're writing interoperable protocol.
>
> Ole
>
>
>> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>>
>>>>>> Ole, it is true that we write in English, and there is always room for
>>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>>
>>>>>> But in this case we have a demonstrated difference in how people
>>>>>> understand the existing text.  When we have such a demonstrated
>>>>>> difference, we have an obligation to address it.
>>>>>
>>>>> This particular issue has caused no interoperability issue,
>>>>
>>>> May I ask what's the data that support this statement?
>>>
>>> From the shepherd's writeup:
>>>   IPv6 is implemented on most platforms (hosts, routers, servers, etc.),
>>>   including proprietary and open source.  A list of products that have
>>>   received the IPV6 Ready logo can be found at:
>>>
>>>   https://www.ipv6ready.org/db/index.php/public/?o=4
>>
>> This has nothing to do wth the interoperability problems that may be
>> caused by a middlebox that inserts EHs.
>>
>>
>>
>>>> You certainly have no way of knowing this, or whether interoperability
>>>> issues may arise in the future.
>>>
>>> Yes, we do know if our protocols have interoperability issues.
>>> Have you implemented RFC2460? I have. So have many others on this list.
>>> In the context of implementing 2460 there just is no ambiguity and this issue will never arise.
>>
>> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
>> inserting EHs in the middle, you will not experience the associated
>> possible problems. What's the news here?
>>
>>
>>
>>> What you are talking about is something else. You are talking about the hypothetical "What if someone standardised something new in the future?"
>>
>> :-)
>>
>> C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, EH
>> insertion has reportedly been deployed as a result of the implementation
>> of such initial versions of the I-D.
>>
>>
>> You can clarify that EH insertion is banned, and move rfc2460bis to full
>> stanard (since that's what's supposed to be mature)
>>
>> You can delay rfc2460->std, and work to update rfc2460.
>>
>> Now, moving rfc2460 to full std knowingly leaving a hole there such that
>> after rfc2460 is std you completely change the architecture (e2e vs
>> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>>
>> 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 17 09:15:00 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EEF5129488 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:14:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 91pTwyt8QNkS for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:14:57 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (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 6783B126579 for <ietf@ietf.org>; Fri, 17 Feb 2017 09:14:56 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 4BD323AA2268; Fri, 17 Feb 2017 12:14:54 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BG5dw7pDz8yE; Fri, 17 Feb 2017 12:14:51 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 735303AA2252; Fri, 17 Feb 2017 12:14:51 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
Date: Fri, 17 Feb 2017 12:14:51 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
To: otroan@employees.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CwrljLpZd8HRZfJwDIrPGqpNvxA>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:14:58 -0000

> On Feb 17, 2017, at 9:12 AM, otroan@employees.org wrote:
>=20
> Fernando,
>=20
> It is a simple logical consequence.
>=20
> Middleboxes do not exist in the IPv6 architecture.

firewalls do not exist in IPv6????
load balancers do not exist in IPv6???
content redirectors do not exist in IPv6???
=E2=80=A6

Scott

> There is no interpretation of 2460 that can lead to an implementor =
inserting headers other places than at the source.
> Therefore, there is no interoperability issue in RFC2460 nor any =
ambiguity that needs to be resolved in RFC2460.
>=20
> We're not writing law, we're writing interoperable protocol.
>=20
> Ole
>=20
>=20
>> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> =
wrote:
>>=20
>> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>>=20
>>>>>> Ole, it is true that we write in English, and there is always =
room for
>>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>>=20
>>>>>> But in this case we have a demonstrated difference in how people
>>>>>> understand the existing text.  When we have such a demonstrated
>>>>>> difference, we have an obligation to address it.
>>>>>=20
>>>>> This particular issue has caused no interoperability issue,
>>>>=20
>>>> May I ask what's the data that support this statement?
>>>=20
>>> =46rom the shepherd's writeup:
>>>  IPv6 is implemented on most platforms (hosts, routers, servers, =
etc.),
>>>  including proprietary and open source.  A list of products that =
have
>>>  received the IPV6 Ready logo can be found at:
>>>=20
>>>  https://www.ipv6ready.org/db/index.php/public/?o=3D4
>>=20
>> This has nothing to do wth the interoperability problems that may be
>> caused by a middlebox that inserts EHs.
>>=20
>>=20
>>=20
>>>> You certainly have no way of knowing this, or whether =
interoperability
>>>> issues may arise in the future.
>>>=20
>>> Yes, we do know if our protocols have interoperability issues.
>>> Have you implemented RFC2460? I have. So have many others on this =
list.
>>> In the context of implementing 2460 there just is no ambiguity and =
this issue will never arise.
>>=20
>> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
>> inserting EHs in the middle, you will not experience the associated
>> possible problems. What's the news here?
>>=20
>>=20
>>=20
>>> What you are talking about is something else. You are talking about =
the hypothetical "What if someone standardised something new in the =
future?"
>>=20
>> :-)
>>=20
>> C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, =
EH
>> insertion has reportedly been deployed as a result of the =
implementation
>> of such initial versions of the I-D.
>>=20
>>=20
>> You can clarify that EH insertion is banned, and move rfc2460bis to =
full
>> stanard (since that's what's supposed to be mature)
>>=20
>> You can delay rfc2460->std, and work to update rfc2460.
>>=20
>> Now, moving rfc2460 to full std knowingly leaving a hole there such =
that
>> after rfc2460 is std you completely change the architecture (e2e vs
>> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>>=20
>> Thanks,
>> --
>> Fernando Gont
>> SI6 Networks
>> e-mail: fgont@si6networks.com
>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20


From nobody Fri Feb 17 09:15:17 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D59E129646 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:15: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, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0qx-1HQZvm_j for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:15:13 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 54A1A1294E0 for <ietf@ietf.org>; Fri, 17 Feb 2017 09:15:13 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 17:15:12 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 4662BD788D; Fri, 17 Feb 2017 09:15:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=9N1moh+D3t/6vLb7NtA6QtGE5Zk=; b= e3fJ32WdHJbS62bMghHF0cW0UXkY6LUrWZ6dRX9Cu7xTkGLMyHyjKXjXUFg6Xroy Sc758KZwlnLMrwpd1P/Vmqdt9k6FZB7b7ZXSBV8Af1TNqznoDkyYUGwDe8jGaqOa jJd3Gu+/pgyx89oX0ZwEzYZlHZBO+vTJOBsS61cJIX8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=PKik+1y392TW2UWEVx9giqm HGnzCGq4CzL4cKEpAEku0waBf0+4Yf6MfNeaAgl5rzQwK+cPaEtFQ/QexPipkS7q z07MDK1CJNMM1Kd+d5it+TihNY21QIb81vyruF5H5DqcH8f1BrdUXL/OAeMJQLGc kfMPb4RiUWVGbc+Yiq0I=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id E65ABD788B; Fri, 17 Feb 2017 09:15:11 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2DB648C9373B; Fri, 17 Feb 2017 18:15:26 +0100 (CET)
From: otroan@employees.org
Message-Id: <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_445BBDE0-BC03-46D4-8E73-EABE245B804D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 18:15:25 +0100
In-Reply-To: <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r5ZLywnOYP2NFpOX-JvqXKxOYUg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:15:15 -0000

--Apple-Mail=_445BBDE0-BC03-46D4-8E73-EABE245B804D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joel,

> Given that different people have interpreted 2460 as permitting or =
prohibiting the addition of Extension Headers by intermediate devices, =
there clearly is an ambiguity.

I'm a little uncertain if I'm unclear or if you simply didn't read my =
message. :-)

Do we agree that you can see this at two different angles?

1) Are there any interoperability issue or ambiguity in the protocol =
specification of 2460 and how implementors of 2460 have interpreted =
that?

2) Is 2460 "future-ambiguous", i.e it is unclear if 2460 permits a =
future extension? Like ECMP, Header insertion NAT...

The answer to 1 is no. And no-one has claimed otherwise in these =
discussions.

For 2, that would be in the area of stating the law for what future =
extensions of IPv6 can or cannot do.
If we want to go there 2460, yes there are ambiguities. It's hard to =
predict what the IETF can possible invent in the future and if that =
should be permitted or not. And of course what effect that would have on =
future documents regardless.

Clear?

Best regards,
Ole




>=20
>=20
> That is the point that concerns me.
>=20
> Yours,
> Joel
>=20
> On 2/17/17 9:12 AM, otroan@employees.org wrote:
>> Fernando,
>>=20
>> It is a simple logical consequence.
>>=20
>> Middleboxes do not exist in the IPv6 architecture.
>> There is no interpretation of 2460 that can lead to an implementor =
inserting headers other places than at the source.
>> Therefore, there is no interoperability issue in RFC2460 nor any =
ambiguity that needs to be resolved in RFC2460.
>>=20
>> We're not writing law, we're writing interoperable protocol.
>>=20
>> Ole
>>=20
>>=20
>>> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> =
wrote:
>>>=20
>>> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>>>=20
>>>>>>> Ole, it is true that we write in English, and there is always =
room for
>>>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>>>=20
>>>>>>> But in this case we have a demonstrated difference in how people
>>>>>>> understand the existing text.  When we have such a demonstrated
>>>>>>> difference, we have an obligation to address it.
>>>>>>=20
>>>>>> This particular issue has caused no interoperability issue,
>>>>>=20
>>>>> May I ask what's the data that support this statement?
>>>>=20
>>>> =46rom the shepherd's writeup:
>>>>  IPv6 is implemented on most platforms (hosts, routers, servers, =
etc.),
>>>>  including proprietary and open source.  A list of products that =
have
>>>>  received the IPV6 Ready logo can be found at:
>>>>=20
>>>>  https://www.ipv6ready.org/db/index.php/public/?o=3D4
>>>=20
>>> This has nothing to do wth the interoperability problems that may be
>>> caused by a middlebox that inserts EHs.
>>>=20
>>>=20
>>>=20
>>>>> You certainly have no way of knowing this, or whether =
interoperability
>>>>> issues may arise in the future.
>>>>=20
>>>> Yes, we do know if our protocols have interoperability issues.
>>>> Have you implemented RFC2460? I have. So have many others on this =
list.
>>>> In the context of implementing 2460 there just is no ambiguity and =
this issue will never arise.
>>>=20
>>> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
>>> inserting EHs in the middle, you will not experience the associated
>>> possible problems. What's the news here?
>>>=20
>>>=20
>>>=20
>>>> What you are talking about is something else. You are talking about =
the hypothetical "What if someone standardised something new in the =
future?"
>>>=20
>>> :-)
>>>=20
>>> C'mon, Ole. Take a look at the initial versions of the SR I-D -- =
and, EH
>>> insertion has reportedly been deployed as a result of the =
implementation
>>> of such initial versions of the I-D.
>>>=20
>>>=20
>>> You can clarify that EH insertion is banned, and move rfc2460bis to =
full
>>> stanard (since that's what's supposed to be mature)
>>>=20
>>> You can delay rfc2460->std, and work to update rfc2460.
>>>=20
>>> Now, moving rfc2460 to full std knowingly leaving a hole there such =
that
>>> after rfc2460 is std you completely change the architecture (e2e vs
>>> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>>>=20
>>> Thanks,
>>> --
>>> Fernando Gont
>>> SI6 Networks
>>> e-mail: fgont@si6networks.com
>>> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>>=20


--Apple-Mail=_445BBDE0-BC03-46D4-8E73-EABE245B804D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpy+tAAoJEL7aWKiYQt92qu8QAKcWVJlio1EHLg09SR5xDfBv
aHd9uIUppo8qATzPYry0E46cBf+ew1J4r6lgu4W44exSXKTUsARquXHelbkRiLJ+
Qpfeaj4VsNRM9SoasCkFDb0FnQ4tojWLCuhFTqMXP0cyjwHXPXt8NDAlV6gc+RtL
OoZDOJ/9rnesO5rD0wh0+3Kco0EV8TdWRzASRpOI7K5RylOP30eI+E7A2O/HtAKi
1K0YWWQiuGthJS1FSYxkwdJUPvxJW6ZaqwHvJn/ZKeklwK2i3SHYnLzY6xOC7u8t
OWsIgtuVle1dU2WZaAq0KS3jUrRCCgcN0Uv9l5YzLKX0b1VOHDHnKDQvH/kXtwnB
DNAR1RVOI+L3OAkcG91h2BfUccHQtbHQ9GRebRiE5DbEd3xXp2lUR/XwFgS0kj8Z
NERfZcfDjImMpD7qUEZOGGBKd5UfYFyCEUbw8KqGSvOo2SwxkPk+vkqx6K+kzmGX
ZJzFx4Dsi8WK0EG2/dwpw42beRxj8jjTQNppiothFujOJucrsZXS28OhxVPueKU6
ecqcGqxIG0WEvDbsnQmLJxkYT/IwBJLCUmvpQMRDS4E2Y8L3H+IgThSqiyUwFyw9
jLiXEGDh+sxlTC+7LUmNXnJohZED1KxLvZvELybeYZ6OpeiDzVBxVDFnNOLWfWSW
Zv3jQAHEacEqCin+j6Vl
=wfPR
-----END PGP SIGNATURE-----

--Apple-Mail=_445BBDE0-BC03-46D4-8E73-EABE245B804D--


From nobody Fri Feb 17 09:26:58 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF08129AD3 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:26:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ww6eRMbA_t4D for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:26:54 -0800 (PST)
Received: from mxa2.tigertech.net (mxa2.tigertech.net [208.80.4.162]) (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 5215112949B for <ietf@ietf.org>; Fri, 17 Feb 2017 09:26:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 3B1A7AE00EC; Fri, 17 Feb 2017 09:26:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487352414; bh=DD/nhFdvOTvFkRTROmpTnoLRnHPWxzvI7Q/u2iFDEog=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=pOPTssKV9QbqiNtZ21of64uoA2Pr7lRSAvSHzCmIReNxqecZKW/BhAuP1m/noVX6E 0VyTJ8PyIGowYNmKgr3pXMoyyYcor9vOhA4KHAggqxAKqCN2heEB0WQzzOjjY266yS OY/BqBj63knl94OjJReeoWx+S825WrQ6tBdhlLno=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 834D724676C; Fri, 17 Feb 2017 09:26:53 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com>
Date: Fri, 17 Feb 2017 12:26:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/L4gdyXIMLsCRbQ0rKSKakFsTLLo>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:26:56 -0000

I am not sure what youa re asking with either of your quesitons.

With regard to question 1, you seem to be asking whether we have seen 
folks adding EHs, and whether it has been observed to cause 
difficulties.  We have seen folks trying to standardize exactly such 
additions.  So I presume they have already implemented them.  And we 
have seen folks explaining a range of cases where it causes problems.

With regard to 2, you seem to be you seem to be constructing a very odd 
reading of an RFC.  Some people have clearly said that they read the 
existing RFC as permitting additions of EHs.  That is not a matter of 
future RFCs, but of current readers.  Other people have said that they 
read the text as clearly prohibiting such behavior.  Which would at a 
minimum mean that any IETF effort to change it would be required to 
explain why it was acceptable and interoperable to change the rules.

Given that the existing wording has been interpreted in different ways 
by different people, and that there is good reason to beileve that the 
differing interpretations will (if they have not already) cause 
interoperability issues, it seems to me incumbent on the WG to be clear 
about what it means.

The usual approach to this is to use RFC 2119 terminology and careful 
wording.

Yours,
Joel

On 2/17/17 12:15 PM, otroan@employees.org wrote:
> Joel,
>
>> Given that different people have interpreted 2460 as permitting or prohibiting the addition of Extension Headers by intermediate devices, there clearly is an ambiguity.
>
> I'm a little uncertain if I'm unclear or if you simply didn't read my message. :-)
>
> Do we agree that you can see this at two different angles?
>
> 1) Are there any interoperability issue or ambiguity in the protocol specification of 2460 and how implementors of 2460 have interpreted that?
>
> 2) Is 2460 "future-ambiguous", i.e it is unclear if 2460 permits a future extension? Like ECMP, Header insertion NAT...
>
> The answer to 1 is no. And no-one has claimed otherwise in these discussions.
>
> For 2, that would be in the area of stating the law for what future extensions of IPv6 can or cannot do.
> If we want to go there 2460, yes there are ambiguities. It's hard to predict what the IETF can possible invent in the future and if that should be permitted or not. And of course what effect that would have on future documents regardless.
>
> Clear?
>
> Best regards,
> Ole
>
>
>
>
>>
>>
>> That is the point that concerns me.
>>
>> Yours,
>> Joel
>>
>> On 2/17/17 9:12 AM, otroan@employees.org wrote:
>>> Fernando,
>>>
>>> It is a simple logical consequence.
>>>
>>> Middleboxes do not exist in the IPv6 architecture.
>>> There is no interpretation of 2460 that can lead to an implementor inserting headers other places than at the source.
>>> Therefore, there is no interoperability issue in RFC2460 nor any ambiguity that needs to be resolved in RFC2460.
>>>
>>> We're not writing law, we're writing interoperable protocol.
>>>
>>> Ole
>>>
>>>
>>>> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> wrote:
>>>>
>>>> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>>>>
>>>>>>>> Ole, it is true that we write in English, and there is always room for
>>>>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>>>>
>>>>>>>> But in this case we have a demonstrated difference in how people
>>>>>>>> understand the existing text.  When we have such a demonstrated
>>>>>>>> difference, we have an obligation to address it.
>>>>>>>
>>>>>>> This particular issue has caused no interoperability issue,
>>>>>>
>>>>>> May I ask what's the data that support this statement?
>>>>>
>>>>> From the shepherd's writeup:
>>>>>  IPv6 is implemented on most platforms (hosts, routers, servers, etc.),
>>>>>  including proprietary and open source.  A list of products that have
>>>>>  received the IPV6 Ready logo can be found at:
>>>>>
>>>>>  https://www.ipv6ready.org/db/index.php/public/?o=4
>>>>
>>>> This has nothing to do wth the interoperability problems that may be
>>>> caused by a middlebox that inserts EHs.
>>>>
>>>>
>>>>
>>>>>> You certainly have no way of knowing this, or whether interoperability
>>>>>> issues may arise in the future.
>>>>>
>>>>> Yes, we do know if our protocols have interoperability issues.
>>>>> Have you implemented RFC2460? I have. So have many others on this list.
>>>>> In the context of implementing 2460 there just is no ambiguity and this issue will never arise.
>>>>
>>>> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
>>>> inserting EHs in the middle, you will not experience the associated
>>>> possible problems. What's the news here?
>>>>
>>>>
>>>>
>>>>> What you are talking about is something else. You are talking about the hypothetical "What if someone standardised something new in the future?"
>>>>
>>>> :-)
>>>>
>>>> C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, EH
>>>> insertion has reportedly been deployed as a result of the implementation
>>>> of such initial versions of the I-D.
>>>>
>>>>
>>>> You can clarify that EH insertion is banned, and move rfc2460bis to full
>>>> stanard (since that's what's supposed to be mature)
>>>>
>>>> You can delay rfc2460->std, and work to update rfc2460.
>>>>
>>>> Now, moving rfc2460 to full std knowingly leaving a hole there such that
>>>> after rfc2460 is std you completely change the architecture (e2e vs
>>>> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>>>>
>>>> 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 17 09:31:37 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 638341299C1 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mgAafOFvZJxB for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:31:35 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 48EDA12962C for <ietf@ietf.org>; Fri, 17 Feb 2017 09:31:35 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 17:31:35 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0A013D788A; Fri, 17 Feb 2017 09:31:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=yP1dYVh0EZ6eaw3kEwec+2LKWD0=; b= bm1cEXk//cj62aHx2I9nk9/HYqybVcXUSczVwM4Hw6OypBbRrUjIMBCrB05ebsuT woen0T7EZdZ7cuVH3OgycBH9deQQYe7gZBXqNzHpTvdeB6qCzlQBtmgwPsUXnmYN NYEcgL5SwNispYVcfSGNYJVwResZcG9d5teey7UcIzw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=j5Oc9ahQCdK/IyqA3pm/vli jKRPcfw8+2Z8wMnmwM8J6Va5enkDhXfqhjEEpIshmJINU3M9HNqwOyBjsp/aYmci XlYgNDu3x2Zkp4pB0UuwuwFqbQm5BEDDaOxnsWS+SQ8q/FxNwoU1GIn/CQs1XM/O Tp1LS3O4/6goa0qveUM8=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id D21D4D788F; Fri, 17 Feb 2017 09:31:34 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 7F8148C987B4; Fri, 17 Feb 2017 18:31:49 +0100 (CET)
From: otroan@employees.org
Message-Id: <AD79F64F-A143-4C42-A7FA-FF67CAF3E3BB@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_728D65EC-2F98-4CEB-BD55-FC094D505498"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 18:31:48 +0100
In-Reply-To: <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com>
To: "Scott O. Bradner" <sob@sobco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dGo2KBnVmZKaoBE6qVdNYh1rmBw>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:31:36 -0000

--Apple-Mail=_728D65EC-2F98-4CEB-BD55-FC094D505498
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Scott,

>> It is a simple logical consequence.
>>=20
>> Middleboxes do not exist in the IPv6 architecture.
>=20
> firewalls do not exist in IPv6????
> load balancers do not exist in IPv6???
> content redirectors do not exist in IPv6???
> =E2=80=A6

In the world view of RFC2460, the world consists of hosts and routers =
connected with links.
That's largely the IETF specification perspective too...
We don't write our protocols to accommodate middleboxes on the path.

Cheers,
Ole

--Apple-Mail=_728D65EC-2F98-4CEB-BD55-FC094D505498
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpzOFAAoJEL7aWKiYQt92eUIQAMI6adqYERLfff2fR+Jy7CXS
bRxkdQKNLj6CqxURYCaBpxagAL5ZIRoT6fnz2lKPgurOtA2e1qwyvgZ67XhUi2zo
Jm70X0Gm66Q8u/2wp9x0dqLv0DoepNOOYYDOdGBNyOvfLUdLaEpxc3SHkpyWBUFQ
xzJa75QLCQ1WdVKYBdEW/z/L0Q9eMCmWcs0Ocs293c181YeyDjtBm1nkXCe8BkqW
5jwfB2zqBLwTYomDbReCphISOErF/CXjKVm0prePZuwW7VM0mE4PcL67onNoTvwY
gtF2qRYMmfjZ5O6HcQ5L4N7VCpah9Dp6gkxTg4VxG1PQQ6W/I2jrehYBlsT3qfoF
s8d2xjyILxX8sC/CaDokcGIh/NbJu2uTgKH+Cd5m8uoUFCWWyQPkpIDlBIsLn64W
CMubQpnKzQHZyI7rlX2kuHSOv1vdeSAOA/GBBN5U/XwAtrZJYCF9SD6AC929no6s
eVzASwvuf6/KwRYBtWG3dFPYRuJciX0C8xNprXpZcPgTIZGHTtERP+tj03No//pg
CRVpd7l6LCJJrCIV+zX1awNc4SYm2kga0MgbeB9evSbqPl3UT8Ua8DHfRgDx75/5
bAOW8kfQFpgCau9HsNvESyUC9ygwrQ15Xq7wIIy1Q3T8Xe4gZnGOj+HFy9l0Hjyf
hXquThlXM5whENiQQ5dO
=h++U
-----END PGP SIGNATURE-----

--Apple-Mail=_728D65EC-2F98-4CEB-BD55-FC094D505498--


From nobody Fri Feb 17 09:32:50 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EC82129ADB for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_TXhvqPO4gR for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:32:46 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 A13CC1295D3 for <ietf@ietf.org>; Fri, 17 Feb 2017 09:32:46 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 2A1879B8 for <ietf@ietf.org>; Fri, 17 Feb 2017 17:32:46 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id friGA0vl2Kf0 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:46 -0600 (CST)
Received: from mail-ua0-f198.google.com (mail-ua0-f198.google.com [209.85.217.198]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id E798C61A for <ietf@ietf.org>; Fri, 17 Feb 2017 11:32:45 -0600 (CST)
Received: by mail-ua0-f198.google.com with SMTP id t17so29502867uae.3 for <ietf@ietf.org>; Fri, 17 Feb 2017 09:32:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=E2kWQ4ULLlDTLwTDqL+DY4G8htYdqFYvHS+KripBCuo=; b=jzxNw+ei/ICqbrAn0VSBuoBwl55NbiFGjyR0xCSVJWOY1UIpdRTqVOUZbC1vdu5ver x8+wsvxSttKKuEFYH9y2NtiA2PVq66W3AB8cxcw1YAKpsuO4aRJLwh+L+ttX2T4cEDcY v+4dZNMBCbFtb1VzBHGnyvhFUgtZdgvfr8eJf0I0liwcXtOgUBnjKoUkWzgnw/UyKJAt 28EUuZQr//LYAh9XdgSxAi4TO2xa0cEzUa3CCLfqRYkbQyTP8akFUobonECtOPCo9lKt 2xOFjdYqb0xtZYR1lzsu6ROYI0cXc5cLUz3Vqjs15dqcD7eq7jwNpow7QPVf5GBedkk5 eHag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=E2kWQ4ULLlDTLwTDqL+DY4G8htYdqFYvHS+KripBCuo=; b=FQICdgHGaFj7ify2n+67Gxz1QZV6kT2SUBn6fc8OroR+OzC4uDRBM3TwON6UOVJCh6 PzS3TL/yuQ1iFyhpjhmswvHqwl/w4/461FoDq7b+UG96/d7MnTiMWiFDJ2PNPqXJWXwM RIKoLhn2Ax/OkxOEF2ObYRJ4nNXkyLuWpPU5CqwJR7NKhq9CrvsZxepVu/lIy05uNy7a jx+XLiduefD/wKRGIoTMWYHYqfsmMfgY7MMgshHsrl1ZRWbO/wC0uEzhwNC9t52pY4q5 iywRelp0hIkHbSEirv1J2lHPC+hybPg4Xr849UOKxM7m9GAfMk0JVERDZoMzvjARdkf0 /kKQ==
X-Gm-Message-State: AMke39nJL6DZDQrtiRaRma93XXYQL0jRaCqoDExIKIHTvRm2IIVyBiUNwB9jBk91235RRIEfRDHv+UUYADTK0T2yTd1HGGuQxtIauGYxWtTkneBzSEOo5v0ERPbqZYnZZPnALfVaayDZizyarIQ=
X-Received: by 10.31.49.81 with SMTP id x78mr4498667vkx.82.1487352765369; Fri, 17 Feb 2017 09:32:45 -0800 (PST)
X-Received: by 10.31.49.81 with SMTP id x78mr4498653vkx.82.1487352765180; Fri, 17 Feb 2017 09:32:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.13 with HTTP; Fri, 17 Feb 2017 09:32:43 -0800 (PST)
In-Reply-To: <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org>
From: David Farmer <farmer@umn.edu>
Date: Fri, 17 Feb 2017 11:32:43 -0600
Message-ID: <CAN-Dau3gXG8O2Fx_rdBJD8cokKMDJFN7D_MDsmzORmpgDUfVPQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=001a114388b0397b690548bd4d9f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/79jMrlpcYU7VYrG_2v53Gahmhs4>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:32:49 -0000

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

I had an epiphany this morning and I have to jump back to Brian's proposed
text.

On Wed, Feb 15, 2017 at 3:34 PM, <otroan@employees.org> wrote:
>
> >> Do you think this change is appropriate in the context of advancing
> 4291?
> >
> > I don't think I have suggested text that would lead to a single
> instruction in
> > running code being changed.
>
> CURRENT (RFC4291bis):
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
>    all unicast addresses, except those that start with the binary value
>    000, is required to be 64 bits long.  The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
>
> PROPOSED:
>
>     IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
> unicast
>    addresses used for Stateless Address Autoconfiguration [RFC4862] is
> required
>    to be 64 bits long. The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421]
>
>
> My reading of the proposed text, which certainly may be wrong, given that
> English is not my first language, is that it leaves the Interface-ID length
> of links _not_ using SLAAC undefined, i.e. not fixed at 64. Is there any
> other way to interpret this sentence?
>

I would add ", in all other cases it is recommended to be 64 bits long."


> The proposed text appears to make the Interface-ID length an operational
> choice.
> How is that _not_ changing the 64 bit boundary?
>

This has always been an operational choice.  You are mis-interrupting the
intent of the 64 bit boundary, you seem to be saying it intends to specify
the IID length for every interface on the Internet. If that was the intent,
then RA's would never have needed a prefix length, nor would you need to
specify a prefix length when manually configuring an interface.  If this
requirement intended to specify the IID length of every interface on the
Internet, then the requirement would have been sufficient by itself, we
would have been done at that point. However, the fact that RAs have prefix
lengths, and we specify a prefix length when manually configuring an
interface, belies the argument that this was not intended to be an
operational choice from the beginning.

So, for other than SLAAC, the 64 bit boundary has only ever been in
operational guidance, there are serious consequences to not following the
IETF's operational guidance in this regard, this is discussed in
[RFC7421].  However, it is an operational choice to follow that guidance or
not. Interpreting this requirement as ever taking away that operational
choice, shows this as a false imperative.

Best regards,
> Ole
>

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr">I had an epiphany this morning and I have to jump back to =
Brian&#39;s proposed text.=C2=A0<br><div class=3D"gmail_extra"><br><div cla=
ss=3D"gmail_quote">On Wed, Feb 15, 2017 at 3:34 PM,  <span dir=3D"ltr">&lt;=
<a href=3D"mailto:otroan@employees.org" target=3D"_blank">otroan@employees.=
org</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt;&gt; Do you think this change is appropriate in the context of advancin=
g 4291?<br>
&gt;<br>
&gt; I don&#39;t think I have suggested text that would lead to a single in=
struction in<br>
&gt; running code being changed.<br>
<br>
CURRENT (RFC4291bis):<br>
<br>
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to<br>
=C2=A0 =C2=A0128 [BCP198].=C2=A0 For example, [RFC6164] standardises 127 bi=
t prefixes<br>
=C2=A0 =C2=A0on inter-router point-to-point links.=C2=A0 However, the Inter=
face ID of<br>
=C2=A0 =C2=A0all unicast addresses, except those that start with the binary=
 value<br>
=C2=A0 =C2=A0000, is required to be 64 bits long.=C2=A0 The rationale for t=
he 64 bit<br>
=C2=A0 =C2=A0boundary in IPv6 addresses can be found in [RFC7421]<br>
<br>
PROPOSED:<br>
<br>
=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid length=
 up to<br>
=C2=A0 =C2=A0128 [BCP198].=C2=A0 For example, [RFC6164] standardises 127 bi=
t prefixes<br>
=C2=A0 =C2=A0on inter-router point-to-point links.=C2=A0 However, the Inter=
face ID of unicast<br>
=C2=A0 =C2=A0addresses used for Stateless Address Autoconfiguration [RFC486=
2] is required<br>
=C2=A0 =C2=A0to be 64 bits long. The rationale for the 64 bit<br>
=C2=A0 =C2=A0boundary in IPv6 addresses can be found in [RFC7421]<br>
<br>
<br>
My reading of the proposed text, which certainly may be wrong, given that E=
nglish is not my first language, is that it leaves the Interface-ID length =
of links _not_ using SLAAC undefined, i.e. not fixed at 64. Is there any ot=
her way to interpret this sentence?<br></blockquote><div><br></div><div>I w=
ould add &quot;<span style=3D"font-size:12.8px">, in all other cases it is =
recommended to=C2=A0</span><span style=3D"font-size:12.8px">be 64 bits long=
.&quot; =C2=A0</span></div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex">
The proposed text appears to make the Interface-ID length an operational ch=
oice.<br>
How is that _not_ changing the 64 bit boundary?<br></blockquote><div><br></=
div><div>This has always been an operational choice.=C2=A0 You are mis-inte=
rrupting the intent of the 64 bit boundary, you seem to be saying it intend=
s to specify the IID length for every interface on the Internet. If that wa=
s the intent, then RA&#39;s would never have needed a prefix length, nor wo=
uld you need to specify a prefix length when manually configuring an interf=
ace.=C2=A0 If this requirement intended to specify the IID length of every =
interface on the Internet, then the requirement would have been sufficient =
by itself, we would have been done at that point. However, the fact that RA=
s have prefix lengths, and we specify a prefix length when manually configu=
ring an interface, belies the argument that this was not intended to be an =
operational choice from the beginning.</div><div>=C2=A0<br></div><div>So, f=
or other than SLAAC, the 64 bit boundary has only ever been in operational =
guidance, there are serious consequences to not following the IETF&#39;s op=
erational guidance in this regard, this is discussed in [RFC7421].=C2=A0 Ho=
wever, it is an operational choice to follow that guidance or not. Interpre=
ting this requirement as ever taking away that operational choice, shows th=
is as a false imperative. =C2=A0=C2=A0</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
Best regards,<br>
Ole<br>
</blockquote></div><div><br></div>-- <br><div class=3D"gmail-m_-61204858071=
22484370m_1215708161095176577m_5144403573517215221gmail-m_72217169162646104=
18gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">E=
mail:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>O=
ffice of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>=
2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(61=
2)%20626-0815" value=3D"+16126260815" target=3D"_blank">612-626-0815</a><br=
>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-99=
52" value=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--001a114388b0397b690548bd4d9f--


From nobody Fri Feb 17 09:39:33 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10B9A129AEA for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X9KIucTmeMom for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:39:29 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 4B0A0129AE5 for <ietf@ietf.org>; Fri, 17 Feb 2017 09:39:29 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 17:39:29 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id E1E26D788D; Fri, 17 Feb 2017 09:39:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=4/S6lvv+k9fmF98lsISIeOsHe+Q=; b= CD20VGaLAgiSm3QICYncuyRWQOf7upLgo0fnmObZi+PEfvaix75Iro2bisEVLLUm lm6MQzsz4SJnCq8YwfcmpedSaJbqoPsPOdPk5WZtpPopYxuer16nM/5fmi/Y+pzX ibxOm8ovYxGdGmLNYLSivsZ+08QqOWa56fL5ILObwY0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=m+C6Kb/whL1FcC3eT3gxw4U JPbxMSadV9EKMVAeQQz3XiOTZ8GVyJTi7jlH1BNVPU+zRHoXEClYMFT9qeAlxmbE cfW1nlU1t+vRTZqm9fW5ygEQESyf4PcHkUlIRM8MJmSWgcDu/IXiQbpd5WMWHBkN Fz6R3cnuOVF0jCfUzYgE=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id 8514BD788A; Fri, 17 Feb 2017 09:39:28 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id D4B6D8C9AD86; Fri, 17 Feb 2017 18:39:42 +0100 (CET)
From: otroan@employees.org
Message-Id: <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_A61DDFA8-B91F-48C7-87EB-E81478ECF108"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 18:39:42 +0100
In-Reply-To: <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-JY-gaIuviWBp4O5R6z7uzVSwek>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:39:31 -0000

--Apple-Mail=_A61DDFA8-B91F-48C7-87EB-E81478ECF108
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Joel,

> I am not sure what youa re asking with either of your quesitons.
>=20
> With regard to question 1, you seem to be asking whether we have seen =
folks adding EHs, and whether it has been observed to cause =
difficulties.  We have seen folks trying to standardize exactly such =
additions.  So I presume they have already implemented them.  And we =
have seen folks explaining a range of cases where it causes problems.

No, that's not what I'm asking.
I'm asking if an implementor of the 2460 specification has interpreted =
the text as ambiguous and if that has led to interoperability issues.
The answer to that is no.

Do you see my point here? That this point is important for advancing =
RFC2460. There is no shown ambiguity that has had any consequence for =
2460 implementors.

Header insertion just doesn't exist in the context of implementing 2460.

> With regard to 2, you seem to be you seem to be constructing a very =
odd reading of an RFC.  Some people have clearly said that they read the =
existing RFC as permitting additions of EHs.  That is not a matter of =
future RFCs, but of current readers.  Other people have said that they =
read the text as clearly prohibiting such behavior.  Which would at a =
minimum mean that any IETF effort to change it would be required to =
explain why it was acceptable and interoperable to change the rules.
>=20
> Given that the existing wording has been interpreted in different ways =
by different people, and that there is good reason to beileve that the =
differing interpretations will (if they have not already) cause =
interoperability issues, it seems to me incumbent on the WG to be clear =
about what it means.

Can you please explain how that can create interoperability issues? An =
implementation of 2460 does not do header insertion.
You must be talking about some future specification (there are drafts) =
that specify header insertion.
_Those_ specifications will create interoperability problems. I think we =
should not standardise those.

Sure you could ban NAT's, ECMP and header insertion, and whatever else =
you can imagine in 2460, but how exactly is that going to prohibit =
anyone from writing the above set of specs? We're not writing law, we're =
writing interoperable protocols.

Cheers,
Ole

--Apple-Mail=_A61DDFA8-B91F-48C7-87EB-E81478ECF108
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpzVeAAoJEL7aWKiYQt921hoQAMAN9E7XN26IT7UB5TC8C1xy
u+NqKW2nS5Rdun66zfLz05tS8U6xSGDG+64qhc/vMLVQryVPABs509Z8k9RFrmKb
V0or99nXMQcvQNHN7KD8elPe97nveqdfEIYLYbFNKJ0aqcyzqhbgy+HTV3q1sujt
ZUMu+Ha9RsPJGzjAMbi7InnutL+HxgJC2McRk94T7pY8YAW4KQUnglxk2sB+523s
prdicw0a/e2zELCWm6aAafQ9Qfs1bpNgT9fVN0yhX4n/T/VJzPv7lwOQGycRxMmI
a1G4jmoBWKc+B9g5bOhyOa1e7+XMwB/HmcH9rWGr7SxDYGiTpgEHub7jypKdUWw3
Nz+wBQbirtL/f47fa213Hx6YfXcnCr/X6q7pkh8WfhmGAFB/OQlMlAaqTkup0Ga4
p5lEHIXlK+yUBPXcydpAquTBoHUEHc8I35jGeS50RSqIBTpyU7F0HNZNqSn244nW
rak6iH15jLjyElfcItZ+T7Py7Z+Npuki/ykQunzGI5+8tWEeC6vr+8Pfx8pLeKLX
9KwDdWHcPSiNRPf1U9VUym+XQqQGjMeF8xLLbrJhgBNF+DtUizXPggcW2gQFrGMT
1OImNiuiBnSgQbQszcViG/S23ZuLz/6JKmvLmwYtvhae8+Uqyoj2gmI0A2UegsgU
IAZWdez0cWBxuQkTeVa+
=3Zgu
-----END PGP SIGNATURE-----

--Apple-Mail=_A61DDFA8-B91F-48C7-87EB-E81478ECF108--


From nobody Fri Feb 17 09:44:49 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF52E12957B for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7CGPwvUS5bTe for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:44:46 -0800 (PST)
Received: from mxb2.tigertech.net (mxb2.tigertech.net [208.80.4.164]) (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 A552E12955C for <ietf@ietf.org>; Fri, 17 Feb 2017 09:44:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 8E8A53C2FCF; Fri, 17 Feb 2017 09:44:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1487353486; bh=cAJre5d1w62ArEAQkDapbPB8kWjOJt9ahFzlnIrrDQs=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=VakjlrLL6MYBiRI3yuCEqxecWlrh2RKmJS2wcGZR0KevGYJEAi4V4Tg6cRx0FfjwO FDApb5HPbTLlGB4qzCLPP7V1ES7WhmT6xLSDrmt3Nf8SKL2FUFJfaNUAw1mLLpk6TJ o9T+TbaYIElZpVJg6TeDFl2G1ErGz8KdbjpRg5gQ=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 221B61C02F3; Fri, 17 Feb 2017 09:44:46 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com> <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <7394db7d-fbd9-7a65-673a-857c438c3796@joelhalpern.com>
Date: Fri, 17 Feb 2017 12:44:45 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8il7nruxJvRZf-WZJwkI3OCJ284>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:44:48 -0000

I disagree with your interpretation of the bar the document must meet.
I believe I have clearly stated my concern.
I will leave that judgment to the relevant ADs and IESG when they review 
the last call results.

Yours,
Joel

On 2/17/17 12:39 PM, otroan@employees.org wrote:
> Joel,
>
>> I am not sure what youa re asking with either of your quesitons.
>>
>> With regard to question 1, you seem to be asking whether we have seen folks adding EHs, and whether it has been observed to cause difficulties.  We have seen folks trying to standardize exactly such additions.  So I presume they have already implemented them.  And we have seen folks explaining a range of cases where it causes problems.
>
> No, that's not what I'm asking.
> I'm asking if an implementor of the 2460 specification has interpreted the text as ambiguous and if that has led to interoperability issues.
> The answer to that is no.
>
> Do you see my point here? That this point is important for advancing RFC2460. There is no shown ambiguity that has had any consequence for 2460 implementors.
>
> Header insertion just doesn't exist in the context of implementing 2460.
>
>> With regard to 2, you seem to be you seem to be constructing a very odd reading of an RFC.  Some people have clearly said that they read the existing RFC as permitting additions of EHs.  That is not a matter of future RFCs, but of current readers.  Other people have said that they read the text as clearly prohibiting such behavior.  Which would at a minimum mean that any IETF effort to change it would be required to explain why it was acceptable and interoperable to change the rules.
>>
>> Given that the existing wording has been interpreted in different ways by different people, and that there is good reason to beileve that the differing interpretations will (if they have not already) cause interoperability issues, it seems to me incumbent on the WG to be clear about what it means.
>
> Can you please explain how that can create interoperability issues? An implementation of 2460 does not do header insertion.
> You must be talking about some future specification (there are drafts) that specify header insertion.
> _Those_ specifications will create interoperability problems. I think we should not standardise those.
>
> Sure you could ban NAT's, ECMP and header insertion, and whatever else you can imagine in 2460, but how exactly is that going to prohibit anyone from writing the above set of specs? We're not writing law, we're writing interoperable protocols.
>
> Cheers,
> Ole
>


From nobody Fri Feb 17 09:58:37 2017
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18BAA129AC5 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:58:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.108
X-Spam-Level: 
X-Spam-Status: No, score=-1.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 WzZ1sHeWBTd6 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 09:58:35 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) (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 8C30212955C for <ietf@ietf.org>; Fri, 17 Feb 2017 09:58:35 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id A6A4F3AA2DE8; Fri, 17 Feb 2017 12:58:34 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NpSlrbkN_shs; Fri, 17 Feb 2017 12:58:34 -0500 (EST)
Received: from golem.sobco.com (golem.sobco.com [136.248.127.162]) by sobco.sobco.com (Postfix) with ESMTPSA id 26D2F3AA2DD7; Fri, 17 Feb 2017 12:58:34 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
From: "Scott O. Bradner" <sob@sobco.com>
In-Reply-To: <AD79F64F-A143-4C42-A7FA-FF67CAF3E3BB@employees.org>
Date: Fri, 17 Feb 2017 12:58:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <85116639-34B5-4D3A-9090-8C74BB63CB57@sobco.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com> <AD79F64F-A143-4C42-A7FA-FF67CAF3E3BB@employees.org>
To: otroan@employees.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VB03ZLKFgDj0Zh9tGZWcbRaJufg>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 17:58:36 -0000

> On Feb 17, 2017, at 12:31 PM, otroan@employees.org wrote:
>=20
> Scott,
>=20
>>> It is a simple logical consequence.
>>>=20
>>> Middleboxes do not exist in the IPv6 architecture.
>>=20
>> firewalls do not exist in IPv6????
>> load balancers do not exist in IPv6???
>> content redirectors do not exist in IPv6???
>> =E2=80=A6
>=20
> In the world view of RFC2460, the world consists of hosts and routers =
connected with links.
> That's largely the IETF specification perspective too...
> We don't write our protocols to accommodate middleboxes on the path.

parellel universe

Scott

>=20
> Cheers,
> Ole


From nobody Fri Feb 17 10:00:58 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342C3129633 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:00: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YtGJSpsygkD4 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:00:55 -0800 (PST)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 3ED3712960B for <ietf@ietf.org>; Fri, 17 Feb 2017 10:00:55 -0800 (PST)
Received: by mail-wr0-x242.google.com with SMTP id z61so5262122wrc.3 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:00:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=E8ZRABD2MUCNZAeP/rz+C0azWAl3g0CMaLTyKwdKd/A=; b=JUyu1cIkz6BHkl4OvWeZCY9TWhAuRlDSw0Z3pEGCFkLa70en/BgAIjJmdIHXh1RYeu FLe+CKM1E+gUTVbqpNOIIEqAS0Kye+P3dRuBwa3LbvuZoiAOeI40mIvoibKiqI6rkf9w ubaJNxuKC9sqSK7QYgXaCU+ekD/ZK8XaHsAByX5LvnRrIxJsMdi12LdYQTFNvoQ44+LC +4W+siwXK4SKR2QmY8G18TcftHh6owCBOuxarvnw37qPwgVeVbm3Ry5TWMlAgskpu3FM E3k+YUPEAJeuo/c2G7kzP9dyeD5LlE7yAudDFxkHYJvd5VccNYThKnRfF4GaUrvbib7H 644w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=E8ZRABD2MUCNZAeP/rz+C0azWAl3g0CMaLTyKwdKd/A=; b=CAcLkGsboMOWxrrGsy904HhcDZr3rU05DuY3QWkCB5xhThr6ExCnUTXQ3wWrXEGLxP Hl1OGdkc62UXwpFTvo7hcDifmKOoL1ZN91xnaoGZoL6yknIP566KWjlhll1Z+uaHqeY5 IxoC43Osk1LSjBJ7BDVLbC58fOjdorH3ELKmDpf3a+fo4nRntsIVRyf1HHyBvN6UHtBW 6s6M0oRsHmkSNufW0i/islW9zQVTzK/STgelYhPU3ENiZWQFoISmAPCbrj3cfYA/jYWb S9sG7UeMlyYuURJENXRoh3IlEckRrTrMUQ9zX1OPxPtp9dMPT8X6JldPxrhvLhtBifTz y1jg==
X-Gm-Message-State: AMke39mju05RcwVh8eDM+DqyYRGPWTKXhrTAQil/+IYlSmx92CnB4s0l/hWOmwlOKcppRg==
X-Received: by 10.223.177.142 with SMTP id q14mr3220590wra.194.1487354453522;  Fri, 17 Feb 2017 10:00:53 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id b87sm2567208wmi.0.2017.02.17.10.00.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 10:00:52 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org, "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com> <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com>
Date: Fri, 17 Feb 2017 18:00:51 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h9SeTYOUYaMzgypQzWK701qNWF8>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 18:00:57 -0000

Ole

Are you saying:

A correct implementation of RFC2460 MUST NOT insert an EH at any point 
along the path other than at the packet source.

Or

A correct implementation of RFC2460 MAY insert an EH at any point along 
the path.

Either way, why not add that line to the text to remove any possible 
ambiguity in interpretation?

- Stewart



From nobody Fri Feb 17 10:10:15 2017
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0AF212957B for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:10:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 y7fBXb3gBG4Z for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:10:13 -0800 (PST)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (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 E6379129453 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:10:12 -0800 (PST)
Received: from [10.32.60.120] (142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176]) (authenticated bits=0) by mail.proper.com (8.15.2/8.14.9) with ESMTPSA id v1HI8p5m080910 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 17 Feb 2017 11:08:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 142-254-101-176.dsl.dynamic.fusionbroadband.com [142.254.101.176] claimed to be [10.32.60.120]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: ietf@ietf.org
Subject: Re: Last Call: Uplifting RFC5289 from informational to proposed standard
Date: Fri, 17 Feb 2017 10:10:14 -0800
Message-ID: <43652E06-5DC6-4467-9BBF-6B4BBABEC6F0@vpnc.org>
In-Reply-To: <148735040735.19992.5678820892795925914.idtracker@ietfa.amsl.com>
References: <148735040735.19992.5678820892795925914.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
X-Mailer: MailMate (1.9.6r5344)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/izbJ6EcfcLuEyQnxCZTNMgi6v08>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 18:10:14 -0000

Moving these algorithms to standards track is a good idea, and long 
overdue.

On the other hand, turning "uplifting" into a verb is a terrible idea. 
"Promoting" is a perfectly valid term for this action.

--Paul Hoffman


From nobody Fri Feb 17 10:13:10 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1620129644 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:13:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4iu4bE9v85GB for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:13:07 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 8B97712955C for <ietf@ietf.org>; Fri, 17 Feb 2017 10:13:07 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 18:13:07 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 21529D788A; Fri, 17 Feb 2017 10:13:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=VTqfzo461qv2SVv/swrufKL9RCA=; b= RLyt1UGzbDHf0S1N5lgvHD6mWgckauRRrMirRAj3Y7vfRAIE4RqbsPbWQ/oZwg1E wfpGoQirbn4mW6q1TV36cLFso25Csyx5nBJdg1Vj1iKdgsTiZpfPApshDDr/3OG8 cKriwuFASIpk4U9YKBAuqSn0HElPdpbvIoXo8lGvblM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=CXmwpTGUDQIue0wPkPWDZ6G h1KdshD5TqiA+zqsateZhISKHG4eQYGB/CxY4F4d/DENHeGzx3PDD65iRiRZVZtI 19cf3uF5ayTJaNKJdmiY0aJ03C7Ew1x5SbSJLn4fc6/3UQ2gDYO8LYvDSfWkURyX dEczvgEkYsKtpurFEooE=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id EA142D788D; Fri, 17 Feb 2017 10:13:06 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 004B28CA526F; Fri, 17 Feb 2017 19:13:20 +0100 (CET)
From: otroan@employees.org
Message-Id: <AC99CD5F-2413-4128-8992-E8A7013641A1@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_24ACC29E-A01E-4380-BC8A-BE8F02F65972"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 19:13:20 +0100
In-Reply-To: <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com> <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org> <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HUQsAniM95Y1rRamvgkxTefuoA8>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 18:13:09 -0000

--Apple-Mail=_24ACC29E-A01E-4380-BC8A-BE8F02F65972
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Stewart,

> Are you saying:
>=20
> A correct implementation of RFC2460 MUST NOT insert an EH at any point =
along the path other than at the packet source.
>=20
> Or
>=20
> A correct implementation of RFC2460 MAY insert an EH at any point =
along the path.

No, I'm saying that for a correct implementation of RFC2460 the issue =
doesn't ever arise.

> Either way, why not add that line to the text to remove any possible =
ambiguity in interpretation?

Yes, we could. We couldn't find consensus for that in the working group =
though.
I'm trying out the argument of declaring the whole question of ambiguity =
out of scope. To see if there is better consensus for that.

Best regards,
Ole

--Apple-Mail=_24ACC29E-A01E-4380-BC8A-BE8F02F65972
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYpz1AAAoJEL7aWKiYQt92d2MP/3TQ3pC8/hgDKb1dZViLfFpr
CcJQN4UMNpbfJEtSipLQ94f6jmFcUffsCMlf1a/KT4zTBOT12qoi5Z2SpSBzbPmT
KgOQPfuT006yCN1b9KUsgPWaEBGv4rQtpYmA29mtcz6y4QslXDfc5Gql46/ucuJX
8lVEBJFIQcc+VBQRtyZgRFySITXk99YnVWPERphXVeXt2zSv62r7OAv80bsPkjVN
+4qqeLKVFYdu21AzCRRzxuUFDj3ukOTnpJY73ZZAOHx+r2G/uS98tKh126gKC+qV
z4vKtS9dza5e+3hMKXLDkzOms9STTMo6sCP90CZXX/twW7O0u79/YYVC6D5cdTwC
4jVc/PlPYclIIbwnVxAiIxSODWiGzZCQEuv5+gFCdltWS3gQROAAT6aBbVQIbkio
7gT08XFkmyLxD7h52hbjP3MAOnBNzVK7tqvcv7BVVKOxg9rYUjRlUjzFT4lXbvcw
Kc2cS5Mj+EOJ3AAElVvFnFOSOeIbtNiyurwe5Kma+Tr0l6Bjyy+1eG4ocA1qMKX+
haaq+F69ikSwW+EC7Yq1yJwv3oQ6ZuhE7OdpQ+9R882ltE+FLk3+4y8iN0AqQVsb
IZ7ghoHvjaE2IOs+T0N+v6VXdiADDO94X1gCc+bDM2juUeVPo78gm1THUJ6dauvm
XhAWrZQP/VrFz2K88FRA
=r2CF
-----END PGP SIGNATURE-----

--Apple-Mail=_24ACC29E-A01E-4380-BC8A-BE8F02F65972--


From nobody Fri Feb 17 10:16:35 2017
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DEA1295A6 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Pt8VRAFLeVi for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:16:31 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 72374129588 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:16:31 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id w20so46914699qtb.1 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:16:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding; bh=pHcVRkitm0nmJdk9/ifxY6HrCpJoO6tGoK7iVKebC1k=; b=ig23lHXKoNroQRotxKYO+SjKrhOL1tuyHie6sYli1ZNr3PBrez/A/tHmmZ88QuVWEv IlYw/2xus32ZJLvDD2WXxEp6DOZGzCpV9YkZ9k8RJX3kkl9IjKV8wXqVJ6lyzLqUfVfj 6iBszGhdP3U/MXf5zzcgCEnyqXUncvci/rY2daJX0Y8YVl8wFWNFhsBrDREzVlxv7BVO joHQ9UsyvYR8xc0baUvG3tcN108Ahj8zkP0bAxRwPLvA3yQaLNpvODbrJoqkWVCbGU/F NU4aRPrbmIFFnl5EDAqVoh814/UaHLbGHCww86KdbYaRyKD+dFgOjAGnL7l+zZdEwfCs 9qmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=pHcVRkitm0nmJdk9/ifxY6HrCpJoO6tGoK7iVKebC1k=; b=ZfMQyat2ye59Pw6hUFp/mAhIOcHDjvz7pY0jwe9oNF4PMxuX79ymzF4+dCnAQBh7+W o31ddRRgbt+kZAT3EMTLSDtEjUVCHmFXSuKQPOQ3mX7FV6ZBvgh8ovwOi6jegarkV6LD pXre0oPxaxlHncAz6sQ3jAMX1S8t3OEQF9xfQ4bsHowMUj8FPHEEayw0XFN25htrBO55 U2kMkH2aA72IszTJ4nYfWpaHm3lwdNHBFJM3oXnBOj+WuERjlqYwoXzNIZJw+5Qra9ZY xuhTQExwC75VDR6umL968fUIp45kTZ9FXpU2gv/nvl/ImBwIj8WrQW/PFDGyaTrItqCr htJg==
X-Gm-Message-State: AMke39kU7A7/JzfaOEvofZbYyR93lUhCVLYr59CPPVr4ZDU3cp7+5RFZxMFWsOIZKI5khw==
X-Received: by 10.237.37.71 with SMTP id w7mr8474725qtc.287.1487355390297; Fri, 17 Feb 2017 10:16:30 -0800 (PST)
Received: from 87-7-200.lacnic.net.uy ([2001:13c7:7001:7000:e1bb:95d3:2cc:220a]) by smtp.gmail.com with ESMTPSA id 136sm6938198qkg.34.2017.02.17.10.16.28 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 10:16:29 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Message-ID: <f685b229-c187-81a0-852d-779aa5fe0f97@gmail.com>
Date: Fri, 17 Feb 2017 15:16:26 -0300
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <8637862F-DAE8-4520-9997-F4DD61629EA7@sobco.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/q_XqWx3s0Tjo7jVNxA2u9pR9CgU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 18:16:33 -0000

El 17/2/17 a las 2:14 p.m., Scott O. Bradner escribió:
>> On Feb 17, 2017, at 9:12 AM, otroan@employees.org wrote:
>>
>> Fernando,
>>
>> It is a simple logical consequence.
>>
>> Middleboxes do not exist in the IPv6 architecture.
> firewalls do not exist in IPv6????
> load balancers do not exist in IPv6???
> content redirectors do not exist in IPv6???
> …

I was about to ask the same question

> Scott
>
>> There is no interpretation of 2460 that can lead to an implementor inserting headers other places than at the source.
>> Therefore, there is no interoperability issue in RFC2460 nor any ambiguity that needs to be resolved in RFC2460.
>>
>> We're not writing law, we're writing interoperable protocol.
>>
>> Ole
>>
>>
>>> On 17 Feb 2017, at 13:40, Fernando Gont <fgont@si6networks.com> wrote:
>>>
>>> On 02/15/2017 07:18 AM, otroan@employees.org wrote:
>>>>>>> Ole, it is true that we write in English, and there is always room for
>>>>>>> "interpretation", sometimes reasoanble room, sometimes not.
>>>>>>>
>>>>>>> But in this case we have a demonstrated difference in how people
>>>>>>> understand the existing text.  When we have such a demonstrated
>>>>>>> difference, we have an obligation to address it.
>>>>>> This particular issue has caused no interoperability issue,
>>>>> May I ask what's the data that support this statement?
>>>> From the shepherd's writeup:
>>>>  IPv6 is implemented on most platforms (hosts, routers, servers, etc.),
>>>>  including proprietary and open source.  A list of products that have
>>>>  received the IPV6 Ready logo can be found at:
>>>>
>>>>  https://www.ipv6ready.org/db/index.php/public/?o=4
>>> This has nothing to do wth the interoperability problems that may be
>>> caused by a middlebox that inserts EHs.
>>>
>>>
>>>
>>>>> You certainly have no way of knowing this, or whether interoperability
>>>>> issues may arise in the future.
>>>> Yes, we do know if our protocols have interoperability issues.
>>>> Have you implemented RFC2460? I have. So have many others on this list.
>>>> In the context of implementing 2460 there just is no ambiguity and this issue will never arise.
>>> Huh?  Yes, if you connect two IPv6 devices, without a middle-box
>>> inserting EHs in the middle, you will not experience the associated
>>> possible problems. What's the news here?
>>>
>>>
>>>
>>>> What you are talking about is something else. You are talking about the hypothetical "What if someone standardised something new in the future?"
>>> :-)
>>>
>>> C'mon, Ole. Take a look at the initial versions of the SR I-D -- and, EH
>>> insertion has reportedly been deployed as a result of the implementation
>>> of such initial versions of the I-D.
>>>
>>>
>>> You can clarify that EH insertion is banned, and move rfc2460bis to full
>>> stanard (since that's what's supposed to be mature)
>>>
>>> You can delay rfc2460->std, and work to update rfc2460.
>>>
>>> Now, moving rfc2460 to full std knowingly leaving a hole there such that
>>> after rfc2460 is std you completely change the architecture (e2e vs
>>> !e2e) with EH insertion doesn't seem a serious thing to do, IMO.
>>>
>>> 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 17 10:37:57 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA9A129680 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:37:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uR7NoWOxp2i3 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 10:37:55 -0800 (PST)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (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 A4116129530 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:37:54 -0800 (PST)
Received: by mail-wr0-x244.google.com with SMTP id q39so6123611wrb.2 for <ietf@ietf.org>; Fri, 17 Feb 2017 10:37:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=2mcahEeCc0uQAPWQ7xRBn3Lb0KErzj8gdlTmdL0WlJE=; b=FjHUptuT00u6zF8T6WEhTeu6N1J+Ysjv1vc1UKO9M1I3E23+7EY/0sJWO779dEuIB0 K1l3L3eKx9S9MtiShK/dbMrWV28MfhbQCtU3bvGKg34rCmT/7OqvbYfFMS2tTR8gRr6y 3+I/01oJJoXvzj4vHB3VreUHBn2toZBNdQxDu5JaCZ2+B4n1Og1QvqycS4ykuiUwbQcp pG73o83HCdJLbqkhBVR60mNHHeCjT1+Prs2XUu+rYbFPfpR1lgCkiS98O6j86DnsQMWe W3+L5j0gz0qZAp2KKglOEX86CFJR8SwfvDIZqAPNhEkMy+wNRs8ZsiaM+dlUpa/N+7yb yDsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=2mcahEeCc0uQAPWQ7xRBn3Lb0KErzj8gdlTmdL0WlJE=; b=JI1zZ9mrDeor6g4WuR5J+X9Pz7cAZkal81GOs4mRXUMLyDaCm6JsgGCjGuIdeFq4O3 7QPvEsgnJFocPbSTyCPQOtFH2NyfjyZPUHS+yN8kGTwVyC4hswKIpkGEak3CzBpTd6tl odHOh8YlB7iidrcB4bQN7pJh1K2Bc+GCMDlo8rprJEg1yHoh5itZK9TUNrsoDJ0Ke9ek TA1ST2OxG08MMdmPFVKQ823/a98/kR8Nr7JiAKE5ViOsxxqQWLsAoPVIiLr1za6yePDo rhjpHP0zyAlay7zjUK22H9uguy7o7lIW9hdP/aclGHoAvvpB0ZJ/2i0+KbMK4fTzoJr5 vdrA==
X-Gm-Message-State: AMke39minXr95CBL04w9NgWvdi3UXGUT3+yEEoK+Z1FOgf3WEmmkcRoiwGyM9cMw8hKjOg==
X-Received: by 10.223.134.173 with SMTP id 42mr8490723wrx.95.1487356672815; Fri, 17 Feb 2017 10:37:52 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 94sm13879023wrl.50.2017.02.17.10.37.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 10:37:52 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com> <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org> <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com> <AC99CD5F-2413-4128-8992-E8A7013641A1@employees.org>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <046765b1-8a34-962d-257e-9c229ff1da32@gmail.com>
Date: Fri, 17 Feb 2017 18:37:51 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <AC99CD5F-2413-4128-8992-E8A7013641A1@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BasnI01Byn4c0nC2v2DYp0vQsjM>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 18:37:56 -0000

On 17/02/2017 18:13, otroan@employees.org wrote:
> Stewart,
>
>> Are you saying:
>>
>> A correct implementation of RFC2460 MUST NOT insert an EH at any point along the path other than at the packet source.
>>
>> Or
>>
>> A correct implementation of RFC2460 MAY insert an EH at any point along the path.
> No, I'm saying that for a correct implementation of RFC2460 the issue doesn't ever arise.
>
>

That seems somewhat like Schroedinger's cat.

Given that RFC2460 defines EHs only one of those statements can be true 
for any EH type.

- Stewart



From nobody Fri Feb 17 11:34:31 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67C2C129B47 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 11:34:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYECK5mP7uDe for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 11:34:27 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 C612B129B48 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:34:27 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id o64so4673905pfb.1 for <ietf@ietf.org>; Fri, 17 Feb 2017 11:34:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=T9999rVH/hv3mdj23EYbrA7ACzDWl5pdLgLaRRw3EDI=; b=QpxzT3VPwLNBsd3JQy5F5+9DQK1EXUThR7bG5AsQjPMAWI3wbskcaT22xOB/R2QQgg 36mbrvTB2ad6LSQ0RP8uAiEGj28TM2H5c5o2UGqnFUrZVcwtV0+PGRV5kjaCFTxZ9fyB 1NJN+zvKYYzI1pUnMPqrcAZr5K1qqsrSWmtZn0hhUmsi2lDCdIuktoybw/VkKPOHiMFD OPbYxQWki0vda9ZSkPuQzlbhu5U9pAW7mYjhgCAC74IeGNrN3hAcVVpfbWBcKQiUsYS/ UBpSravzQ76Wpw831ReKaue2jq1oAeWy64HhSs2mkQWB7H+LNAZD2atsEtMmqAjYlYl0 wxRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=T9999rVH/hv3mdj23EYbrA7ACzDWl5pdLgLaRRw3EDI=; b=SCkcXT3rgIbYJ8sW5DsSO7Ul+7xOhAGkkUXLx0RU/SB7lUwqenFsN5eRZlPc2zz9rC qYGlZZaMXZBtOGYplHuos+OIyVmvD49dRVwvEzpcPMsGKlZPcDCs6XUWsnmKblX+90eM TG1xz9IF7Px1BbpKpg/IbODZmyb8EVSsUR1iEhSybaqiir2jKCU1b7K9uX6W9NU0o2BO EMFXZEWlSLUGfyrMFJXT/JUVBnMBZs0fdBog/3EhiGL/RaIMOI8q0WmapIR099nwE0KY Kw6s0aqerySyNkMXxAS0pZKKBnn+5J4M7GdV1bucP/orSI0WbVzGM98ZpaC3FEF9Elga EGwg==
X-Gm-Message-State: AMke39nfpTKpBO+olNz+zWWghPbo8cl0hUwZdQSGoZpZOrHlSy+SJRK4ZHyoC+xPDwka1w==
X-Received: by 10.84.194.165 with SMTP id h34mr13363355pld.70.1487360067428; Fri, 17 Feb 2017 11:34:27 -0800 (PST)
Received: from ?IPv6:2406:e007:5b5c:1:28cc:dc4c:9703:6781? ([2406:e007:5b5c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id y6sm21299941pgc.1.2017.02.17.11.34.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 11:34:26 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Stewart Bryant <stewart.bryant@gmail.com>, otroan@employees.org, "Joel M. Halpern" <jmh@joelhalpern.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <8ac0ada8-b8c6-6299-cbd7-615c207caa53@joelhalpern.com> <67A86E2D-80A3-4EC7-858E-A838160934CC@employees.org> <f547185e-61b5-f534-eeed-6617e1a803f9@joelhalpern.com> <8AF7D4B5-A126-4D17-A070-85F1ADDB76D5@employees.org> <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <50a79d32-046b-3851-8afe-55fba104e44f@gmail.com>
Date: Sat, 18 Feb 2017 08:34:32 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <5dd9cce6-d87b-4d97-66d3-7f94fbe00629@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2ULJXZT4uXjp4J4iOKMD2tNUksU>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 19:34:29 -0000

On 18/02/2017 07:00, Stewart Bryant wrote:
> Ole
> 
> Are you saying:
> 
> A correct implementation of RFC2460 MUST NOT insert an EH at any point 
> along the path other than at the packet source.
> 
> Or
> 
> A correct implementation of RFC2460 MAY insert an EH at any point along 
> the path.

Ole doesn't, apparently, want to say either of those things.

I want to say the first *as part of the promotion to Internet Standard*
because it was the clear and documented intent of the authors and WG
of RFC 1883, which became RFC 2460. (Documented in the ancient email I dug
out a while back.) And it has been assumed by subsequent work such
as PMTUD and IPsec/AH.

If we want to *change* it, that's a separate discussion from promoting
the current standard. We can do it afterwards.

(And in answer to some other comments, I'll note that RFC 791 does not
forbid NAT, but I bet the authors would have done so if they'd thought
of it. When did forbidding something in an RFC ever prevent people from
implementing it in a limited domain?)

    Brian


From nobody Fri Feb 17 12:20:08 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A02129692 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:20:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id supWzikHlhqV for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:20:05 -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 16DAF129B73 for <ietf@ietf.org>; Fri, 17 Feb 2017 12:20:04 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id c73so15791463pfb.0 for <ietf@ietf.org>; Fri, 17 Feb 2017 12:20:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EK90MEdXhL4HHJzUlMb/azjAa8pkepDCb43Feprp4Z8=; b=ZnhVO9KdwtBDk6Ll3Wbwaqlc5lYZESHETBIlUyK9/IFjfMJ0sjN+Ixsr2v/2eVo6vR UvYhaN10gU5gi5OubuSJ6ncOuV9fzyOtdl1jdVYVUMZ76Wl81VcmSq99CAHHQ6wNDhdn tV2xZgCOUDTEfeorIisHy17Wj0QEJqWM9VEpMdk2GSaTyAox9mGCZ58Y4dGFCUfCIguF FAYA0GWxrLdu7RMWido8OXDYEzgwbaDkKunRnfdYmnmEI8KlL7eD3ung5IHD1HeIkiq0 +m0Xn/7NcoeT5YVH/PNzqRk3jys3xLDr/v8SqCI/CNE5vQC67LBAy3yhZhzBWUOsqusF cmtw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EK90MEdXhL4HHJzUlMb/azjAa8pkepDCb43Feprp4Z8=; b=ZD+jNwvIqtA6X3PZX3dbuQVRF70ZIanoo9+6w1g8NKGKsVdZkUiZ2V2f1Jm3cMC5JC c7oixmW6Rv3RM47MulL2MjntZ3xdQ2bbcgLPZQQJD6amydnuuxiXL/FldUAz4d1MlEMm OFK7jpSVvFowMYay+7Ig/Q+7vXX/vSZuPgcTtXIfa7r04rNJ3AokFAOZsErT+IxmrzG8 SnvB6qjB2gc6xdFc6dDvhlG1iBDY+S7a2Xwew6NcK3Q/zcWXmu+tLdSEE+WateE8kqU6 +ETBROsVRCKvCaOupumcbayobWArqoTLW8B7f75+MNEzXtqNJcK38QQMVBmTuawJbbct WUxA==
X-Gm-Message-State: AMke39kwboGz1labETzgSMWGL47DQM2lJkHjOTyEANGNSBuuc8/4iAgF+UpsSNeQwJuoR0A/
X-Received: by 10.99.99.5 with SMTP id x5mr12259540pgb.225.1487362803349; Fri, 17 Feb 2017 12:20:03 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id p26sm21181574pfj.23.2017.02.17.12.20.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 12:20:02 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8DD71669-8100-418B-B9CC-802136EBDA8A"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 17 Feb 2017 12:20:01 -0800
In-Reply-To: <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
To: IETF-Discussion Discussion <ietf@ietf.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_L7aKeOuYaIS0FCmZ0Ei7LkxVXU>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 20:20:06 -0000

--Apple-Mail=_8DD71669-8100-418B-B9CC-802136EBDA8A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 16, 2017, at 14:21, james woodyatt <jhw@google.com> wrote:
>> [=E2=80=A6]
>> The challenge is to find text that enforces the 64-bit boundary =
policy (ignoring the technical arguments for a moment), and at the same =
time ensures implementors do the right thing and make their code handle =
any prefix length. Of course these are interdependent and doing the =
latter makes it harder to enforce the first.
>=20
>=20
> I propose the following:
>=20
>>>> IPv6 unicast routing is based on prefixes of any valid length up to =
128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID =
of unicast addresses is generally required to be 64 bits in length, with =
exceptions only provided in special cases where expressly recognized in =
IETF standards track documents.

In response to various comments to this message, I=E2=80=99d like to =
propose a refinement:

> IPv6 unicast routing is based on prefixes of any valid length up to =
128 bits [BCP198]. However, in accordance with the reasoning explained =
in [RFC7421], the Interface ID part of host interface addresses is =
generally 64 bits, with exceptions only provided in special cases =
expressly recognized in IETF standards track documents.

I disagree with the view that advancing RFC 4291 to standards track =
admits the opportunity to relax the applicability of the 64-bit boundary =
to only those cases where SLAAC is used. That would be a technical =
change to the specification that I=E2=80=99m not comfortable promoting =
at IETF Last Call. In support of that position, I note that the =
reasoning in RFC 7421 covers cases beyond just SLAAC, and I have =
previously written about a case not mentioned in RFC 7421, the =
LOWPAN_IPHC header compression scheme, which is used in various LLN =
schemes, e.g. IEEE 802.15.4, for compressing IPv6 addresses using the =
assumption that network prefixes are 64 bits.

For my personal part, I=E2=80=99d prefer to see a clear statement here =
using RFC 2119 requirements language keywords, but I recognize that =
consensus probably requires compromise on that point. Hence, the =
proposed refinement above, which does not use RFC 2119 keywords. (Here =
is how I would write this with keywords: =E2=80=9CIPv6 unicast routing =
is based on network prefixes that MAY have any valid length up to 128 =
bits [BCP198]. However, in accordance with the reasoning explained in =
[RFC7421], the Interface ID part of host interface addresses SHOULD be =
64 bits with exceptions only provided in special cases expressly =
recognized in IETF standards track documents.=E2=80=9D)


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_8DD71669-8100-418B-B9CC-802136EBDA8A
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"">On Feb 16, 2017, at 14:21, james woodyatt &lt;<a =
href=3D"mailto:jhw@google.com" class=3D"">jhw@google.com</a>&gt; =
wrote:<br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;" class=3D""><div =
class=3D""><div class=3D""><blockquote type=3D"cite" =
class=3D"">[=E2=80=A6]</blockquote></div><blockquote type=3D"cite" =
class=3D""><div class=3D""><div class=3D"">The challenge is to find text =
that enforces the 64-bit boundary policy (ignoring the technical =
arguments for a moment), and at the same time ensures implementors do =
the right thing and make their code handle any prefix length. Of course =
these are interdependent and doing the latter makes it harder to enforce =
the first.<br class=3D""></div></div></blockquote></div><div =
class=3D""><br class=3D""></div><div class=3D""><div class=3D"">I =
propose the following:</div></div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D""><blockquote type=3D"cite"=
 class=3D""><blockquote type=3D"cite" class=3D""><blockquote type=3D"cite"=
 class=3D"">IPv6 unicast routing is based on prefixes of any valid =
length up to 128 bits [BCP198]. However, as explained in [RFC7421], the =
Interface ID of unicast addresses is generally required to be 64 bits in =
length, with exceptions only provided in special cases where expressly =
recognized in IETF standards track =
documents.</blockquote></blockquote></blockquote></div></div></div></div><=
/blockquote><br class=3D""></div><div>In response to various comments to =
this message, I=E2=80=99d like to propose a refinement:</div><div><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D"">IPv6 unicast =
routing is based on prefixes of any valid length up to 128 bits =
[BCP198]. However, in accordance with the reasoning explained in =
[RFC7421], the Interface ID part of host interface addresses is =
generally 64 bits, with exceptions only provided in special cases =
expressly recognized in IETF standards track documents.</blockquote><br =
class=3D""></div><div>I disagree with the view that advancing RFC 4291 =
to standards track admits the opportunity to relax the applicability of =
the 64-bit boundary to only those cases where SLAAC is used. That would =
be a technical change to the specification that I=E2=80=99m not =
comfortable promoting at IETF Last Call. In support of that position, I =
note that the reasoning in RFC 7421 covers cases beyond just SLAAC, and =
I have previously written about a case not mentioned in RFC 7421, the =
LOWPAN_IPHC header compression scheme, which is used in various LLN =
schemes, e.g. IEEE 802.15.4, for compressing IPv6 addresses using the =
assumption that network prefixes are 64 bits.</div><div><br =
class=3D""></div><div>For my personal part, I=E2=80=99d prefer to see a =
clear statement here using RFC 2119 requirements language keywords, but =
I recognize that consensus probably requires compromise on that point. =
Hence, the proposed refinement above, which does not use RFC 2119 =
keywords. (Here is how I would write this with keywords: =E2=80=9CIPv6 =
unicast routing is based on network prefixes that MAY have any valid =
length up to 128 bits [BCP198]. However, in accordance with the =
reasoning explained in [RFC7421], the Interface ID part of host =
interface addresses SHOULD be 64 bits with exceptions only provided in =
special cases expressly recognized in IETF standards track =
documents.=E2=80=9D)</div><div><br class=3D""></div><br class=3D""><div =
class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_8DD71669-8100-418B-B9CC-802136EBDA8A--


From nobody Fri Feb 17 12:24:48 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A841298C7 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:24:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WZdxjXEUwTuf for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:24:45 -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 A5C161294C6 for <ietf@ietf.org>; Fri, 17 Feb 2017 12:24:45 -0800 (PST)
Received: by mail-pf0-x22f.google.com with SMTP id e4so15745268pfg.1 for <ietf@ietf.org>; Fri, 17 Feb 2017 12:24:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ac0YEFeRuv98MG/EytY8qPMBMazKspRZahbDsSVnRHA=; b=X2UNCDfQFfZ3qU9eyEpHpXmq+9dCzLQ5HwXaYDuqPoDa7Fxeh+4nnPkRj/SaoT1COA hmCrrmgvEcFNHyI4uZUqrt5+Nw/6J+o0nzHupkMLR7Qvh0zRQAg+ltQSGOm8HyDq4u+c P8NBBJKTUlWmDM5qSxCKZzRHEhHX753sW59wrk4BJfQemWAr8v2zGX4CiqFc4mqZ3sB/ +ZjpKqAiTQqeKaV3sry/E+MUvHc2nOg3Ri6UouRzfFyMwNVMfuHtkIzCmzdRorQZWUlP Im0lx8JDZtrzYimnhG4UjxixxSgciT5OKF0RIDGCCbT5FYnCEqyhjdocWmCkh+E3EfSq oL3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ac0YEFeRuv98MG/EytY8qPMBMazKspRZahbDsSVnRHA=; b=tseY5M0Y/gtEK93VQHGlKAiJ/LBRvd2e9ZZp/4hmG5mDzckBrt7RtN77GVvnZUBO8t Gqegfp64W/viHH6sZUR3qISUqAaJDSSFw77+XHa1S26EK+sThhBmhMTpYDTcRXb9uU9Y k09JV1hQ7INIBWAvnnhEM/T8eLAgAq5Ccf5x94sRd54uz47xEO06f51/89rBkmNIJHJE rOgR1xrQ+cMdqAeNe1eA7HNwLbUCx9ADjDn0hOiGK+fKnsiIIUOsUCanYyLO+H6QzX/l 1RWMK1uqXXv0Klzd+tNJFmcJdUjw6TM81/9hA1ka9yo3fdexOnyvT/aCMvh/KSqLywLa xvgA==
X-Gm-Message-State: AMke39kwQxGhJUrk9XAjh2U0nSMJ+XWiSNaRIt8JNkua8K8d4JnmyMkfCPlzWk/NH8Kr+aRY
X-Received: by 10.99.161.17 with SMTP id b17mr12269346pgf.72.1487363085200; Fri, 17 Feb 2017 12:24:45 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id q7sm21112534pfb.98.2017.02.17.12.24.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Feb 2017 12:24:44 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <3CA34394-71EA-4D65-8A5D-0FB25C62D065@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A748BE53-6130-4C59-AAE0-58BEE02E4E65"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 12:24:43 -0800
In-Reply-To: <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
To: otroan@employees.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VD9ul4w2hXALQgPKAYffPOiBGx8>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 20:24:47 -0000

--Apple-Mail=_A748BE53-6130-4C59-AAE0-58BEE02E4E65
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

On Feb 17, 2017, at 06:12, otroan@employees.org wrote:
> 
> Middleboxes do not exist in the IPv6 architecture.

I wish I had known that when I was writing RFC 6092.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_A748BE53-6130-4C59-AAE0-58BEE02E4E65
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Feb 17, 2017, at 06:12, <a href="mailto:otroan@employees.org" class="">otroan@employees.org</a> wrote:<br class=""><div><blockquote type="cite" class=""><br class=""><div class=""><div class="">Middleboxes do not exist in the IPv6 architecture.<br class=""></div></div></blockquote><br class=""></div><div>I wish I had known that when I was writing RFC 6092.</div><div><br class=""></div><br class=""><div class="">
<div class="">--james woodyatt &lt;<a href="mailto:jhw@google.com" class="">jhw@google.com</a>&gt;</div><div class=""><br class=""></div><br class="Apple-interchange-newline">

</div>
<br class=""></body></html>
--Apple-Mail=_A748BE53-6130-4C59-AAE0-58BEE02E4E65--


From nobody Fri Feb 17 12:48:40 2017
Return-Path: <otroan@employees.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80152129BD5 for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=employees.org; domainkeys=pass (1024-bit key) header.from=otroan@employees.org header.d=employees.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P_G4ZaopnEhl for <ietf@ietfa.amsl.com>; Fri, 17 Feb 2017 12:48:37 -0800 (PST)
Received: from esa01.kjsl.com (esa01.kjsl.com [IPv6:2607:7c80:54:3::87]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFE7129BD3 for <ietf@ietf.org>; Fri, 17 Feb 2017 12:48:37 -0800 (PST)
Received: from cowbell.employees.org ([198.137.202.74]) by esa01.kjsl.com with ESMTP; 17 Feb 2017 20:48:37 +0000
Received: from cowbell.employees.org (localhost [127.0.0.1]) by cowbell.employees.org (Postfix) with ESMTP id 0E731D788D; Fri, 17 Feb 2017 12:48:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; s=selector1; bh=wgrXCSCXmcBIKDsTEGDIUl2slRQ=; b= A2JqcKQtrhRB48VzwPBoGSjrwcqqmjd23AtGzdNcOSjeidWdIHqIWjn71BYiX4At r1qy7zmg8Fv7qVERVuPjIIZIqks50RcoJNu63nmphb/2GcptqKxSjfSrF3h8wGiX Bo+wlyOCEUUlQ1gJxyqC40YClsomfcd21RWokLh1UZw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=from :message-id:content-type:mime-version:subject:date:in-reply-to :cc:to:references; q=dns; s=selector1; b=sbFxfINVAt2KQOKyCVAVu2P LtX+6O+y0xm2KtvIAFMwAxY+2lkJr2OBD7VCkEOd69WLn9bj4vtwVqP1Nc2KnO4g uQjK7F12HZXpEEuR6eUZ7RL8K5dQPFaRhDdeOXdeD4q+NOR2UK5wRv0gRknkaf6t uikkSVUh6TyHFYQNaOKI=
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by cowbell.employees.org (Postfix) with ESMTPSA id CEFDBD788A; Fri, 17 Feb 2017 12:48:36 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id 2FA5C8CD42E8; Fri, 17 Feb 2017 21:48:51 +0100 (CET)
From: otroan@employees.org
Message-Id: <54FA4C6E-435A-47F8-9761-FE7FC7018F02@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_B3C7A7D8-6292-4AFE-9D61-74E398C27C5A"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Date: Fri, 17 Feb 2017 21:48:50 +0100
In-Reply-To: <3CA34394-71EA-4D65-8A5D-0FB25C62D065@google.com>
To: james woodyatt <jhw@google.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <1179DE45-3971-44A1-9630-28F76D2D652D@employees.org> <2ea64b3c-d69d-6b6c-cb04-fe63727a8bee@si6networks.com> <23C46409-337C-468D-BCDC-34027BB56CAD@employees.org> <30715b9e-e9b7-320e-f9e2-fc3f64615d5c@si6networks.com> <CAJE_bqcKu1XVQOPzcd+8b68WcQyjH9QmszaSvKWhT8SvHJ0ppg@mail.gmail.com> <m2y3xdpmjd.wl-randy@psg.com> <5333378B-0F8D-4966-82B2-DFF9639CEC7D@fugue.com> <3a180e40-936b-956b-9fc3-5ecdd4d905ee@gmail.com> <m2poippisc.wl-randy@psg.com> <13830253-67ab-cb26-4fa0-f40a24f1a5bc@gmail.com> <76D87C97-1ECB-4E92-8FE7-ADAF464DB8FD@employees.org> <a0aaa86f-db08-4363-f9c6-0b55ceadc3b9@gmail.com> <48b1988d-2074-3e60-62ba-5943e6ec8b91@joelhalpern.com> <523D6E9B-5504-4AA6-81B7-81B68E742E6E@employees.org> <79f04816-0249-c0b8-a72a-5d5bdf77d3f5@joelhalpern.com> <35A94D95-63B8-41BA-8CA1-010544DE1252@employees.org> <eedfd457-14a7-1c98-f765-68f2c5a84860@si6networks.com> <8D0C4CBD-8AB1-42A4-ACF6-6F2E40F9C464@employees.org> <553cdd65-e5a5-8081-fb9a-c66d34496025@si6networks.com> <8E5FC183-DE9B-4CBE-B1EA-301A08300A66@employees.org> <3CA34394-71EA-4D65-8A5D-0FB25C62D065@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mKSgS4TtJtQihTDBBgKAwQHG6vI>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 20:48:38 -0000

--Apple-Mail=_B3C7A7D8-6292-4AFE-9D61-74E398C27C5A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> Middleboxes do not exist in the IPv6 architecture.
>=20
> I wish I had known that when I was writing RFC 6092.

Indeed what a shame. Well if you encounter any of them, please let me =
know and I'll send you instructions for how to get them repurposed into =
routers with the IETF approved 40 byte header inspection limiter =
installed. I've just added an IETF hackathon proposal to improve the =
IETF approved router reference software to insert a small header in each =
packet it forwards: "This packet is certified to be IETF compliant.".

Oh Fridays...

Best regards,
Ole

--Apple-Mail=_B3C7A7D8-6292-4AFE-9D61-74E398C27C5A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIcBAEBCgAGBQJYp2GyAAoJEL7aWKiYQt92ZyEQAKdYeUHCRH52GEVXf9O+aUjZ
KoOUDH0AXDGDlfuoZvtdNxJ+z4ZJ9DNRbJ5QTvVPosFB3yq6bmXom1YCyKrOU/pH
COb0WsG8cnORyUestYhVd7hmmxdCC9u/IA/AhEmhfAcnP/PK3+ctSj5uCa+NdsJb
9VcyOHNGsZ/a9RkqsHGvNhjFBrZtTkjyCW0L2xAfEGeBdXCqjfr94Hfbig9uYWhu
VY61JFI6MRhKrzloq5vwpAtROlI6gvYpBgwSBbQO3uZvQUhm0mproGDtYq8pzlXk
2mGZOgkb7ldFiQsmIBKTIlSMexGn7TN/IjBubowuGzaf2Wz3PSz2M3cT8AUIaUXq
eEU83UEVAsQo4UOiWn9RoyV+7+LAuItgbx1q/w89UE3TQihy5Kskau+cmXPujGle
jwiBhlFPpUasimpCmBYE+/Xc8YJcpPcbW31gevFal++gXD7pN6AQMKfIWOJf+OSg
qXKv2KceYJJt0PrPHsQiEYsivQ8jwJbVwAnx78U5FqMbp9iIvfD94bn39xbYYYX2
oCjeLziAUfFotHk2mkvStIx1wIIj/CdGjQGNRcDpEMmJXZAUzXiNhgnYxNCm/peD
eH3dhocH8nxbqZ5qBOA/sP7P0COBC06HvQeDEIKdxw+tn++asn1C3DNyGKyVuvTw
1qt3iz6Z5rYLD+3G/teF
=N9t1
-----END PGP SIGNATURE-----

--Apple-Mail=_B3C7A7D8-6292-4AFE-9D61-74E398C27C5A--


From nobody Fri Feb 17 18:32:27 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B19E129449; Fri, 17 Feb 2017 18:32:25 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Dale Worley" <worley@ariadne.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-slim-negotiating-human-language-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
Date: Fri, 17 Feb 2017 18:32:25 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2oy_YjKUZrZBpF4UbLV3h1vksfI>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 02:32:25 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-slim-negotiating-human-language-06
Reviewer:  Dale R. Worley
Review Date:  2017-02-17
IETF LC End Date:  2017-02-20
IESG Telechat date:  [unknown]

Summary:
       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

* Technical comments

A. Call failure

If a call fails due to no available language match, in what way(s)
does it fail?  Section 5.3 says

   If such an offer is received, the receiver MAY
   reject the media, ignore the language specified, or attempt to
   interpret the intent

But I suspect it's also allowed for the UAS to fail the call at the
SIP level.  Whether or not that is allowed (or at least envisioned)
should be described.  And what response code(s)/warn-code(s) should
be
used for that?

B. Audio/Video coordination

   5.2.  New 'humintlang-send' and 'humintlang-recv' attributes

   Note that while signed language tags are used with a video stream
to
   indicate sign language, a spoken language tag for a video stream
in
   parallel with an audio stream with the same spoken language tag
   indicates a request for a supplemental video stream to see the
   speaker.

And there's a similar paragraph in 5.4:

>    A spoken language tag for a video stream in conjunction with an
audio
>    stream with the same language might indicate a request for
>    supplemental video to see the speaker.

I think this mechanism needs to be described more exactly, and in
particular, it should not depend on the UA understanding which
language tags are spoken language tags.  It seems to me that a
workable rule is that there is an audio stream and a video stream and
they specify exactly the same language tag in their respective
humintlang attributes.  In that case, it is a request for a spoken
language with simultaneous video of the speaker, and those requests
should be considered satisfied only if both streams can be
established.

* The following three items are adjustments to the design which I'd
like to know have been considered.

C. "humintlang" seems long to me

Given the excessive length of SDP in practice, it seems to me that a
shorter attribute name would be desirable.  E.g., "humlang" as was
used in some previous versions.  Or is there a coordinated usage with
other names in the "hum*lang" pattern?

D. Use the Accept-Language syntax

It seems to me that it would better to use the Accept-Language syntax
for the attribute values.  This allows (1) specifiying the quality of
language experience, allowing clear description of bilingualism, (2)
a
unified method of specifying whether or not arbitrary languages are
acceptable, and (3) abbreviating SDP descriptions.

In a way, the fact that the current proposal seems to require (but
does not directly specify) the coordinated absence/presence of an
asterisk on all of the repetitions of humintlang-send or
humintlang-recv is a warning that the syntax doesn't represent the
semantics as well as it might.

E. Have an attribute to abbreviate the bidirectionally-symmetric case

Note that all examples are bidirectionally symmetric, and the text
says that requests and responses SHOULD be bidirectionally symmetric.
So it would be a very useful abbreviation to define
"humintlang=<value>" to be equivalent to the combination of
"humintlang-send=<value>" and "humintlang-recv=<value>".

Combining proposals C, D, and E, the examples become

      m=audio 49170 RTP/AVP 0
      a=humlang:en

      m=video 51372 RTP/AVP 31 32
      a=humlang:ase,*;q=0.1

      m=audio 49250 RTP/AVP 20
      a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1

      m=text 45020 RTP/AVP 103 104
      a=humlang:gr

which requires about half as many characters as they have now.

* Editorial comments and nits

Abstract

   This document describes the need and a solution using new SDP
stream
   attributes.

I don't think the term "stream attribute" is used in RFC 4566.
Instead, it uses "media attribute".

1.  Introduction

   caller and callee know each other or there is contextual or out of
   band information from which the language(s) and media modalities
can

I think this context, it's preferred to hyphenate "out-of-band" to
make it clearly be an adjective.

   This approach has a number of benefits, including that it is
generic
   (applies to all interactive communications negotiated using SDP)
and
   not limited to emergency calls.

I think s/and not limited to/and is not limited to/ reads more
smoothly.

   But it is clearly useful in many other cases.  For
   example, someone calling a company call center or a Public Safety
   Answering Point (PSAP) should be able to indicate if one or more
   specific signed, written, and/or spoken languages are preferred,
the
   callee should be able to indicate its capabilities in this area,
and
   the call proceed using in-common language(s) and media forms.

I think s/preferred, the callee/preferred; the callee/ because the
sentence is the concatenation of two sentences.

Perhaps s/in-common/shared/.

   Including the user's human (natural) language preferences in the
   session establishment negotiation is independent of the use of a
   relay service and is transparent to a voice service provider. 

I think it's even broader than "transparent to a voice service
provider" -- it's transparent to any serivice provider, assuming that
the media are language-neutral.

   In the case of a call to e.g., an airline, the call could be
   automatically handled by a Spanish-speaking agent.

I think s/handled by/routed to/ is the usual usage.

3.  Desired Semantics

   The desired solution is a media attribute (preferably per
direction)
   that may be used within an offer to indicate the preferred
language
   of each (direction of a) media stream, and within an answer to
   indicate the accepted language.

In this one instance, I think you want to use "language(s)" to drive
home that that multiple languages can be specified:  "within an offer
to indicate the preferred language(s)".

   (Negotiating multiple simultaneous languages within a media stream
is
   out of scope, as the complexity of doing so outweighs the
   usefulness.)

You might want to say instead "(Negotiating multiple simultaneous
languages within a media stream is out of scope for this document.)"
to ensure that nobody decides to argue whether "the complexity of
doing so outweighs the usefulness".

4.  The existing 'lang' attribute

   RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
   similar to what is needed here, but is not sufficiently detailed
for
   use here.

"for use here" isn't quite right.  Maybe "is not sufficiently
specific
or flexible to satisfy the requirements".

   In addition, it is not mentioned in [RFC3264]

"it" is somewhat ambiguous here, perhaps change to "the 'lang'
attribute".

5.  Proposed Solution

Perhaps /Proposed Solution/Solution/, since once this draft is
approved, it becomes the solution.

5.2.  New 'humintlang-send' and 'humintlang-recv' attributes

      a=humintlang-send:<language tag>
      a=humintlang-recv:<language tag>

This is presented as the generic form of the attributes, but there is
no indication of the posible asterisk.

   The values constitute a list of languages
   in preference order (first is most preferred).

"The values" isn't very clear, because the values are in successive
attributes.  You want to say something like "The sequence of values
in
the occurrences of one of these attributes constitutes ...". 
However,
see the technical comments above.

   When placing an emergency call, and in any other case where the
   language cannot be assumed from context, each media stream in an
   offer primarily intended for human language communication SHOULD
   specify both (or in some cases, one of) the 'humintlang-send' and
   'humintlang-recv' attributes.

Probably s/assumed/inferred/.

Could you be more accurate by
s/or in some cases/or for unidirectional streams/?

5.3.  Advisory vs Required

   The mechanism for indicating this preference is that, in an offer,
if
   the last character of any of the 'humintlang-recv' or 'humintlang-
   send' values is an asterisk, this indicates a request to not fail
the
   call (similar to SIP Accept-Language syntax).  Either way, the
called
   party MAY ignore this, e.g., for the emergency services use case,
a
   PSAP will likely not fail the call.

The construction of this paragraph isn't quite complete.  It says
that
if an asterisk is present, a request shouldn't fail, but it doesn't
say that if no asterisk is present, a request should fail if there is
no language match.  And it's the latter condition that makes the
second sentence meaningful.  So I think you want to insert between
the
two sentences one regarding the absence of an asterisk.

5.5.  Examples

Given that the combined audio/video mechanism is the only
irregularity
in this system, there ought to be an example of it.  E.g.,

   An example of a supplemental video stream with a spoken language
   audio stream:

      m=video 51372 RTP/AVP 31 32
      a=humintlang-send:en
      a=humintlang-recv:en

      m=audio 49250 RTP/AVP 20
      a=humintlang-send:en
      a=humintlang-recv:en

6.  IANA Considerations

      humintlang-value =  Language-Tag [ asterisk ]
                          ; Language-Tag defined in RFC 5646
      asterisk         =  "*"

s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
5646/

But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
tracks the current version of language tags.

Appendix A.  Historic Alternative Proposal: Caller-prefs

   This
   results in a more fragile solution since the media modality and
   language would be negotiated using SIP, and then the specific
media
   formats (which inherently include the modality) would be
negotiated
   at a different level (typically SDP, especially in the emergency
   calling cases), making it easier to have mismatches (such as where
   the media modality negotiated in SIP don't match what was
negotiated
   using SDP).

"the media modality and language would be negotiated using SIP" isn't
quite the right way to say it because SIP isn't explicitly
negotiating
the modality.  Better would be

   ... the language (and by implication the media modality) would be
   negotiated using SIP, and then the specific media (which
inherently
   include the modalities and formats) would be negotiated at a
   different level ...

[END]



From nobody Sat Feb 18 01:54:07 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E434C1294CC for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 01:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=VyQSBhL8; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=OZHlm0cx
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCHRUljWyMlj for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 01:54:05 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 110A9129431 for <ietf@ietf.org>; Sat, 18 Feb 2017 01:54:05 -0800 (PST)
Received: from sm-THINK.elandsys.com ([197.226.55.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1I9rfr2015189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Feb 2017 01:53:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1487411637; x=1487498037; bh=d6efrhEBh+XOqeurfUoT0VTQZX94udwg8faWsH8xV40=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VyQSBhL8f5RAzBxs9Q2oebY/yF+z29RbJtPWnhMEvBCRQKL5tAC0w6b521Ycy40Yv dYYsQAQUxoYmYmmvNZVOH+TxfLJD6NuzPcr44XAzuqypEq5nMpYeUQ7ahNwxSYeLi5 oTtF8pjG1mTSWixNgYnY1VbzBuTxZnYrvqCV5VwQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1487411637; x=1487498037; i=@elandsys.com; bh=d6efrhEBh+XOqeurfUoT0VTQZX94udwg8faWsH8xV40=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=OZHlm0cx/eSO/bl/PTx19UaaWq4qE9uoIBsxjd7HrL43hq+XHFAYALd35T/eOjXu/ GBQ/fzA527Fs1GZKxuHvJmaJHTOjrvA66KzxFRI056jwKRHVnXBl+D1iTTkNNmVAsX 3Wev3TKg7mqXLV9lkXNQ0Io6uvLVPVzlMoP+Lezc=
Message-Id: <6.2.5.6.2.20170218010720.0b845c18@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 18 Feb 2017 01:33:40 -0800
To: John Leslie <john@jlc.net>, dcrocker@bbiw.net, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: To "lose the argument in the WG"
In-Reply-To: <20170215025055.GW10525@verdi>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fxV9wU34CEk4F_kfrXfMIX-4ITI>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 09:54:06 -0000

Hi John, Dave,
At 06:50 PM 2/14/2017, John Leslie wrote:
>    We're scared of appeals, without good reason. (Heck, _I_ was scared
>of them five years ago!)
>
>    The IESG, IMHO, is far better able to process appeals than it was
>five years ago; and I believe they're essentially ready to formalize
>a way to deal with appeals without shooting the messenger.

There isn't any reason to be scared of appeals if the WG took an 
informed decision.  It might be better to do that instead of going 
through a lengthy discussion.

>    Name-calling _is_ the IETF way, :^( :^(
>
>    We've exhausted yet-another IETF Chair trying to cure people of
>discourtesy so obvious that you'd get sued for it in a normal world.
>I'm not fool enough to think I'll have any better luck; but I can
>at least speak in support of Pete!

Name-calling does not help in a discussion.  At least the IETF Chair 
tried to address uncivil discussions publicly instead of looking the 
other way.  It is obviously an exhausting effort.

>    There isn't anybody "running last-call".
>
>    If there were, s/he would have no tools to "shut that down".

It is possible to take a decision.  That does not shut down the 
discussion; it tells other  people whether it is useful to keep 
discussing about the issue.

>    But I have a suggestion (which I guess is why I'm bothering to type
>this):
>
>    We have pretty good archive tools availabe for every IETF mail-list.
>
>    Occasionally, I see a posting, "Please read the thread starting at
>
>https://mailarchive.ietf.org/arch/msg/ietf/l4Mi7p-KJanEP1FuEmCDclo6REA
>
>before posting any more on this subject."
>
>    This is actually helpful!
>
>    If the person has read the thread and _is_ merely repeating things
>already said in that thread, s/he deserves censure, and this will be
>obvious to anyone checking that thread.
>
>    If this is new material to the person so advised, it will multiply
>greatly the "clue" level going forward.

Wouldn't it be better to summarize the thread instead of asking a 
participant to go through a long thread?

At 09:05 AM 2/14/2017, Dave Crocker wrote:
>To Ted's point, indulging folk who 'did not have time' to 
>participate earlier is frankly abusive of all those who did.

It is a matter of how the comment is framed.  For example, a comment 
along the lines of "I don't know whether the WG considered this 
issue" is not a problem as it should be possible to point to the 
resolution (re. issue tracker, decision posted to the WG mailing list, etc.)

Regards,
S. Moonesamy  


From nobody Sat Feb 18 04:29:45 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4BFA1294EE; Sat, 18 Feb 2017 04:29:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.789
X-Spam-Level: 
X-Spam-Status: No, score=-3.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzlhkzsBzRdV; Sat, 18 Feb 2017 04:29:42 -0800 (PST)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40105.outbound.protection.outlook.com [40.107.4.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D291294E1; Sat, 18 Feb 2017 04:29:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eaE3nYhhPugHmR2kHcX689J7Zs8fINdjIgAnobz4rxU=; b=boMi51vGmmgYvzRviNTzbrG/qEZ0baOtm2chvkTNMtV8mQQyvanDaf5GAub9+P3pQQo/W9O0xNKRFp6fHrqiPbSnZxRyZxvbRgrIc7d8Bqrcqr8/Wms2o00mA61+QjlL+utKLoqPIOJjr1A4PyTo0sGYG8UzpkWIR2xFvR4jniI=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by VI1PR07MB1566.eurprd07.prod.outlook.com (10.165.239.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Sat, 18 Feb 2017 12:29:38 +0000
Message-ID: <017c01d289e2$4d9832c0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: james woodyatt <jhw@google.com>, IETF-Discussion Discussion <ietf@ietf.org>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Sat, 18 Feb 2017 11:48:38 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: HE1PR0801CA0022.eurprd08.prod.outlook.com (10.167.184.32) To VI1PR07MB1566.eurprd07.prod.outlook.com (10.165.239.12)
X-MS-Office365-Filtering-Correlation-Id: 677f9a3c-1bca-4b6b-8a18-08d457f9ce97
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:VI1PR07MB1566;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1566; 3:1toUUwCIWKKhRFQ435f6UACScpaJ4B9DZXMMZqwHWgrnPnxBFCi/VaOALdY3s3s/IlnJ8Vd5tKFfaocaZvPmHLLoLvzo8BqZTdMsFGTvRDDrzass9R2UxWgDy9nRUNQ6gzz6MZc2ppc9fiQ5s5+JcRijGL7l6vIf24BTPZffC1dhXIIbocGpYGL3eW2kExcVeqrQDK56qOKkCxwWJOR3EGA3w6dWbi/XVDh5ozzmOQms+9RAIarHT4eJngbGz6+WmI7FCfiaU59rSz2wfmcSCw==; 25:dCovBtfg92gmoSJed0ZTmAOwhdSg6AHFGuqrTAhCDUb9VEZOUfm9P/NCINoF3TvmTleIPBpVzRnIjT2w8gMiXkX0jeS4kXJCmrkINy86oCjgrqlaB53bw9DoGbKGk3knL890mxjBdHKMIIySgChzqBTVR7to/QnBo4WxWdA66ef9p+VMBZrZM5MuYkE2Tk8JBUjty/Ssx+iq1JjSBvAFes8Omp6iRb/UTQm8WCZjBRe+Z4dZRhbkddgEu4nrUCUKIKKcuPFIPfQCk8gJycUiBiaYc/0k7VkCbK1cAIa3x3WV69H+Yc7OkfJy27uSN+5W9f419cHXdX8NtkFmiuwX5ABwQXMINCW6d0jLVwlT3ppZvrAdPu5kJYsUBhGL/OW+Km9ZAqR+xedlMeXNOyE32HUsw9IDZ0YVWgXyKHygcl8SX+jp0i3f9jnsw0OxhS2sR7VQxBUOCYrxqjYhhOnH9w==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1566; 31:QdR3UATiV5VYpolgyftaf8vLWVkYsZSNH0hWeRuZSRQptSo1FdNCv4LBGya7MDz2XWhS9MrKEG6XSudbF+/6Qhq9W5qNZPR6Lf8xt9aKJxt2/7CsAJsY5knhv38g7FVqaIsfGsBZWAbZYJESdFyuozv8Ww4SZ7d0uSfKIiP6It22NLOfP4xy57K7CwdA3uCdOxH6Q4Qv9Wdrhd0g97nSoT8sTFYV+iuRFBZRPVqcvyP0igcFzcfkV0fB8Nb9SsqKG4sz22q4TI/7EIjh3J231Q==
X-Microsoft-Antispam-PRVS: <VI1PR07MB1566FD58D3FC34895199D131C65C0@VI1PR07MB1566.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(211936372134217)(100405760836317);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123558025)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:VI1PR07MB1566; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1566; 
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1566; 4:O7ih6JZ29aBawgxWw3eqpbkR/3SHutM01Be9fidBwWBVXGBhOG9Z5dYyXp/OKqQKVJtpxxJgTr7L5lBrKLLqMWKsbcwH9zLaRgbvZo1q4dg5aw5gR8x9B3vBueqjQ7jF23O/tjMuGPXB1nhfF9YO0LfNb+nDbeaDmIRrlJ3athNfDVOffozPiqrHeaZIg0wrkFfUruZFco4zH7VjzeGH1uAmZG8wG5Kx0A95tIZ3sO6hAg5wT8EOGT4VAD9BENiCfnGg6WsToSLJ0ShSzvE0oZ6o4XcgN40bEqscfgzyHSpFqS3MY86gcBtTl6BDgl0y6w8AyD6+6gHiDs21n5sk/eg6IuP40gdg9cPdDxuTHeeiXsoUM0Cz77BCtWXTsSKOx3I2fLP8zQtu1naz9y8tqJniIiMMRmU7jmKEwf6cfcTI8FCiWwv+GE68XlfcJZRUuMKoE4hEpoxAWdFzfhhlHw/XZ+BdQs6q95Re+Myrt6zBwDAwC2ezVxBTxVT3CbgiC5dWBQK0+BYKSL3dNAJIl0jQWnpForXgW1UZinqIa/bgB9hGrRbMDcpw6UikVB8zgfjdrYwE6DnKB2+eCfrYUY5dxo2lXhJeUkAs8O8r0eBl7QWB2UQBxDlxILYsz2CcMVXYXoJ9aoXOstdSbQzmkdZfMpfmVxlGkyRW4RA+f2LZW58loDDD9aszA0aWssDu
X-Forefront-PRVS: 02229A4115
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(189002)(377454003)(24454002)(199003)(13464003)(230783001)(9686003)(54906002)(97736004)(6486002)(5660300001)(93886004)(2870700001)(229853002)(1456003)(106356001)(116806002)(1556002)(47776003)(105586002)(44736005)(42186005)(61296003)(4720700003)(92566002)(2906002)(25786008)(68736007)(189998001)(4326007)(84392002)(86362001)(8676002)(101416001)(50466002)(50226002)(7736002)(44716002)(305945005)(62236002)(66066001)(81156014)(6116002)(3846002)(81166006)(76176999)(6496005)(50986999)(81816999)(81686999)(33646002)(23676002)(6246003)(38730400002)(14496001)(53936002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1566; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtWSTFQUjA3TUIxNTY2OzIzOmt6eDhqWnFpZ2czVzFabUF6cFl6cXBILzRW?= =?utf-8?B?eDJsK2V6UFlYUkV3UG5uU1V0QTRlc0pUdUlNTk9DSkxGL2JHbGdSbE1uU0Z3?= =?utf-8?B?d1dtWWVnUWxxbGhZcVdCZUpwZytqaGhYcE94WkVFZXcvZUg5L2ExSm8wZ0hI?= =?utf-8?B?OTFtVnhDRUUzRGRXczVZbEEyNnBkMmtpcHViUjNHT1ROK1g2WmJsQmhRWGFU?= =?utf-8?B?RnlZdGpRYTFBc0lRYkNFSCs2aDU0alFlSmx4UFViYlNQVTlCbzZpTEZ3bHR6?= =?utf-8?B?aHFud0NSQ1YxSEI1UnFKaEFaOEN3ODBFakkrR0poY3RXeU5lZGZZSTRWWGlQ?= =?utf-8?B?YmVWaEc0SUJ3VERJQUN2Y0NsUlljcjR2OEY4REpaZ2lzMjdsQUZZc2RjTUZX?= =?utf-8?B?TndyM1F5bUdYZXA5RUVCc29SbzdTbDdVclF4eWVEaURmM0xPckdFSzA1WHJP?= =?utf-8?B?dDhEbUUwWDdUSWpNMkNZWUg1UTM1aW1tK3BjR0NzclZFVi9JOEpzWmlUVU9n?= =?utf-8?B?aFkza1d1WTBTQTk3b3VGOVc2V2tjb0djL0Y4b2JIajE2MUp4dUZ0RGU1UG9L?= =?utf-8?B?RFkrQkVFVGxndUJHM09xdHI1bURhZkVZWWUvbG93SU5sMVpZNjJIcG1xN24z?= =?utf-8?B?ZjBNbEQ1V3hIVGloS1pRTmxOMUhzOEt3cnkwVHZkSmg3b1RmWkFXdEdNaTZ0?= =?utf-8?B?dkZoNWNiQ0kxeHdOK1V5VGtuQXRCcDV1TGYxWUxwVUtaSHY5QjlWY2QvcXJB?= =?utf-8?B?MDczbnU1OHBxOHplOW9DSWR6WUpJd2NyTHZjWUxnaEJvWU51THhsZ2pwcWJH?= =?utf-8?B?RVlUaXFEclRMSVhTYmU4ek5hQUdsbFNUT0w1ZlpTRWZpZVBTcmlLU1NwT2JH?= =?utf-8?B?TTVCL2w3blZ0TjAyS0JManNoYVd0dHRvclZXclFMWTZmbmhRLzZRV04wZHhL?= =?utf-8?B?OVltRVZPNkMyU0VVLzhDYzBUWlMvOTNtTkJOUWtwZGYrVTVOVGh6UmVuR1dD?= =?utf-8?B?NU1lb2QzSlkvcUZsQ2pHWkdoMUJiMnpDNUtWYXFZenc2RmJKa3BBVUNLZFlF?= =?utf-8?B?bGtGaE1rRHFLRXh6dE5JQkR6dDJPaUdwYlkxRW15QU5BdkRQQjRuMVo2azJj?= =?utf-8?B?VTI2UGkrSkhpQnpENXh0ME1mT2dIWHlBVUhWSTNhZkRIOVg3QkswTDFPOHJs?= =?utf-8?B?aDN2SXBNNElzcFBVMTd6Z3FadjBNekxpNExiNjZHRkxaRktwOUxFS21ZMDhW?= =?utf-8?B?WHVnSzE5N0c0R05SbFYwZXZycFkxNFpUTHRRZnR2SEc3M1NleGFkS0ZLd0gy?= =?utf-8?B?T1pQRHFIdk9BMFY3V2ZqQ200ZTkzV0QwQXBRd2ViN0w3TkVkYkIyUjNodTd0?= =?utf-8?B?bDROTEJTTGZNb2dKT05ldkZZejZ3ZUF6TEpKRmtwN0NSaFB5bUJYamR6N0JI?= =?utf-8?B?OUFoUEdmUWRJeUk5OEQ2L3JBZm5FbmZRWHNEVXovTyt3S2xXVGJOaVZ2bnhX?= =?utf-8?B?T2lwNXBmeU9PdHA4LzZnYytHT2xnbDFZVk84TytVLzJLM1hsQkVBYzYzSXJq?= =?utf-8?B?OU5lSWM0TE1Bc3V1ZVhvdjBWTTVxdStEMW1BdDErV2dTamNuMHBrRWJpY21T?= =?utf-8?B?Zngrc2RvcURZK0N2NFM2NVFjQUJkaUFsYlUvZlVkZzZGRWUvQk1iYkRQeS9w?= =?utf-8?B?Y3o0TkgveE84S2FiWkprNUoxZE03QnpOLy9FY3BwaEVOS1VXZ1FVZGZsUlVH?= =?utf-8?B?ZlRKVEpIZTVNRmF5TUt0SEZMUzM0M3k3bUJtSkZ6UksyRkhjUUFlcFY3WERP?= =?utf-8?B?K05RclZ2c3Q3cU9id2dTNUJ6K3k1aVN6dDdJVGZ3dXF2RDdnMVFNaUMzZGRr?= =?utf-8?B?RjZ3Q2pLSnVzcVM0ZSt1Mk1TcXRnS3R4OExwaW9DY3JMWDR3aXk1YXlSM1F1?= =?utf-8?Q?m42RYXGb9YDfeci3E3a0fu3Go9ueOI=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1566; 6:wNKExGO2h/UfXi//dKhMK4ORhnoegbtnWx/ljjVOXIPymIKPnbXyHaEv6Qu+0AdU+GcU+UMTHYK2/84u5gY1L2rzeKtaP5lxJdF5VvJRqHiExSMGTeQQhzS69wm1087eibBccBoycFws4/Rrf0wEXc1OrmDBRenDDFYxstoSDdevP+8KjgLNRn0FDUJoWAWFCQBGEklyiYXS+AJQULfTp9H4u81UThvi3GF2nA0rjFA8XFXg8s6Ktqpg2wDxil1u5UhnilY940VWJ/v1fiL70Vmrge3pzLIkk5MMdZHF9PuI/Vd8fzKAfq1IqpAv9qzz+rJf2lUhxeBpnbOULvWiyTAaKzB6aQjsjJ2AvvEM3MRAmINpUN1s762OOK0Bc3md7G1zlpy8mW5BDFsLpvjsjg==; 5:kleHKDOFzweTM/aLzw6vUARS/RKFT7d6lxQrDFEhBQ+iBXzfkJCC206zjN2rodXzUbtuvd596LZAQo/zEzHyywaEm/pmta/FqirF70uwMELRhrcjg+FOc1JPV6/zPz9jXGsiP+f27o5qcOzj6jnR3g==; 24:lMTvC2ChujgVXyCNJSEd/iFZ76ZnOQb1Rs9jzE99Y1ryZv6o1xbs0ajZNhz8DUc5LiJEw7lhvYZnkT/5MNrJ0dUHcL+pWaBaMYzOUJtJ1n8=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1566; 7:dVXrxwu8xa3jd+wKBuoYAVOaVBNsVDHuojPvAR/dRvm4xi1P34Kb7vEKl0Cjkt+kAhU7RlmfQNpTccMhwuYZUhainAR7/TkimDs/FHpgimt0QI5uXeID41tvyvii+9RBTRn+rzB3BY6XFI/xkQ9X9vU/SdplBoa3rhF8MDJrqgeziw4Zj+MhLjNxkWvi0D3+mR3bfhdACLxspdog9dAgeSUZlrf3zo8UpDAEJoTZa015ZaM7yiys/VRp3J7rUk5CZVDJe4GmcdSBesqRQTLVJI21AogceKHX0h07hHeqpnqdxQWqxMrRDEPvHZr9KY32Wp3h4wuQlTzOgzZ12cqzDg==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Feb 2017 12:29:38.3157 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1566
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PebP51Zxtc2Q1DkU0w8nlH7YmG0>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 12:29:45 -0000

---- Original Message -----
From: "james woodyatt" <jhw@google.com>
Sent: Friday, February 17, 2017 8:20 PM

On Feb 16, 2017, at 14:21, james woodyatt <jhw@google.com> wrote:
>> […]
>> The challenge is to find text that enforces the 64-bit boundary
policy (ignoring the technical arguments for a moment), and at the same
time ensures implementors do the right thing and make their code handle
any prefix length. Of course these are interdependent and doing the
latter makes it harder to enforce the first.
>
>
> I propose the following:
>
>>>> IPv6 unicast routing is based on prefixes of any valid length up to
128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
of unicast addresses is generally required to be 64 bits in length, with
exceptions only provided in special cases where expressly recognized in
IETF standards track documents.

In response to various comments to this message, I’d like to propose a
refinement:

> IPv6 unicast routing is based on prefixes of any valid length up to
128 bits [BCP198]. However, in accordance with the reasoning explained
in [RFC7421], the Interface ID part of host interface addresses is
generally 64 bits, with exceptions only provided in special cases
expressly recognized in IETF standards track documents.

I disagree with the view that advancing RFC 4291 to standards track
admits the opportunity to relax the applicability of the 64-bit boundary
to only those cases where SLAAC is used. That would be a technical
change to the specification that I’m not comfortable promoting at IETF
Last Call. In support of that position, I note that the reasoning in RFC
7421 covers cases beyond just SLAAC, and I have previously written about
a case not mentioned in RFC 7421, the LOWPAN_IPHC header compression
scheme, which is used in various LLN schemes, e.g. IEEE 802.15.4, for
compressing IPv6 addresses using the assumption that network prefixes
are 64 bits.

For my personal part, I’d prefer to see a clear statement here using RFC
2119 requirements language keywords, but I recognize that consensus
probably requires compromise on that point. Hence, the proposed
refinement above, which does not use RFC 2119 keywords. (Here is how I
would write this with keywords: “IPv6 unicast routing is based on
network prefixes that MAY have any valid length up to 128 bits [BCP198].
However, in accordance with the reasoning explained in [RFC7421], the
Interface ID part of host interface addresses SHOULD be 64 bits with
exceptions only provided in special cases expressly recognized in IETF
standards track documents.”)

<tp>
James

The issue of introducing RFC2119 keywords into a xxxxbis document for
which the original did not have them was a topic of discussion in the
WG; their absence reflects the consensus of the WG so to suggest them,
even obliquely, opens up another can of worms to add the ones we already
have on this set of I-Ds in these threads.

I think we already have enough cans open to keep me fishing for the rest
of my life!

Tom Petch

-james woodyatt <jhw@google.com <mailto:jhw@google.com>>





From nobody Sat Feb 18 04:59:47 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34D31294D2 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 04:59:45 -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 autolearn_force=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 5QNIv2tvSnBn for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 04:59:44 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id C42DB126CD8 for <ietf@ietf.org>; Sat, 18 Feb 2017 04:59:42 -0800 (PST)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cf4bw-0000FfC; Sat, 18 Feb 2017 13:59:36 +0100
Message-Id: <m1cf4bw-0000FfC@stereo.hq.phicoh.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard 
From: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "Sat, 18 Feb 2017 08:34:32 +1300 ." <50a79d32-046b-3851-8afe-55fba104e44f@gmail.com> 
Date: Sat, 18 Feb 2017 13:59:35 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GxRJGS1jzWLgm2VXptYGigmer1w>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 12:59:46 -0000

>> Are you saying:
>> 
>> A correct implementation of RFC2460 MUST NOT insert an EH at any point 
>> along the path other than at the packet source.
>> 
>> Or
>> 
>> A correct implementation of RFC2460 MAY insert an EH at any point along 
>> the path.
>
>Ole doesn't, apparently, want to say either of those things.
>
>I want to say the first *as part of the promotion to Internet Standard*
>because it was the clear and documented intent of the authors and WG
>of RFC 1883, which became RFC 2460. (Documented in the ancient email I dug
>out a while back.) And it has been assumed by subsequent work such
>as PMTUD and IPsec/AH.
>
>If we want to *change* it, that's a separate discussion from promoting
>the current standard. We can do it afterwards.
>
>(And in answer to some other comments, I'll note that RFC 791 does not
>forbid NAT, but I bet the authors would have done so if they'd thought
>of it. When did forbidding something in an RFC ever prevent people from
>implementing it in a limited domain?)

I agree.

Personally, I wish we could allow routers to insert fragmentation headers.
There is some crazy interaction between DNS and fragmentation that doesn't
happen in IPv4.

But in any case, a stronger text doesn't have much impact on parties outside
the IETF. If, as a random example, I came to the conclusion that I can
reduce PMTU problems by having one of my routers fragment IPv6 packets, then
that may violate the spec, but it is possible that the gains are worth it.

So the only purpose of a stronger text against inserting extension headers
would be to prevent IETF working groups from publishing RFCs that use
that technique. 

Then the question becomes, why would we need to pre-emptively constrain
ourselves? 

If we expect that there is some real world use case where insering
extension headers along the way brings a lot of benefit, then it is much
better to prepare for that situation then writing text to disallow it.



From nobody Sat Feb 18 07:26:49 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BCDE129532 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 07:26: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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 tJ2E5MO-mooF for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 07:26:45 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69F9812952F for <ietf@ietf.org>; Sat, 18 Feb 2017 07:26:45 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cf6u7-0003bx-IQ; Sat, 18 Feb 2017 10:26:31 -0500
Date: Sat, 18 Feb 2017 10:26:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, John Leslie <john@jlc.net>, dcrocker@bbiw.net, ietf@ietf.org
Subject: Re: To "lose the argument in the WG"
Message-ID: <AB7BB4019CE95D16CA7B0B8D@PSB>
In-Reply-To: <6.2.5.6.2.20170218010720.0b845c18@elandnews.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JnmJE_xMfobxRNcpWRnf2N3EWfk>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 15:26:47 -0000

--On Saturday, February 18, 2017 01:33 -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

>...
> At 09:05 AM 2/14/2017, Dave Crocker wrote:
>> To Ted's point, indulging folk who 'did not have time' to 
>> participate earlier is frankly abusive of all those who did.
> 
> It is a matter of how the comment is framed.  For example, a
> comment along the lines of "I don't know whether the WG
> considered this issue" is not a problem as it should be
> possible to point to the resolution (re. issue tracker,
> decision posted to the WG mailing list, etc.)

It can be something else as well.  We could be more careful
about our vocabulary (but probably won't be), but consider a
scenario in which someone, even someone who is quite expert in a
given topic, looks at a WG charter and likely leadership and
participants and says to herself "This is unlikely to produce
anything harmful or go off into the weeds or is sufficiently
narrowly scoped to not pose a general problem.  I do not have
unlimited time to spend on IETF work, and my knowledge and
skills are needed elsewhere".  That is an "I don't have time"
scenario, but it is a vote of confidence in those actively
participating in the WG (and the WG Chair and AD involved) not
abusive of them.  If it then turns out that the WG, in her
opinion, does go off into the weeds, produces someone harmful to
the Internet or other work, or even produces something outside
the scope of the charter, I think the community needs her to
speak up and that any attempt to dismiss the concerns on the
grounds of "you should have participated more and earlier" are
not only abusive but pose a danger to the IETF.

The only solution to that sort of time conflict is for the IETF
to become much less ambitious about how much work can be done in
parallel, possibly by constraining the number of WGs.  The
latter has been proposed a few times, but has gone nowhere, I
think in part because even its advocates want whatever work they
want to do next to be treated exceptionally.

I also note that a Last Call complaint (or appeal, or suggestion
of intent to appeal) on the grounds that a document on which an
IETF Last Call has been initiated exceeds the scope of the
relevant WG Charter has ever gone anywhere.  It isn't clear to
me how cases like that should be handled because the work has
typically been completed and there is no obvious basis for
sending the document back to the WG for technical corrections.
The community should probably fire ADs who let that sort of
thing happen, but (without guessing at what discussions occur
within the Nomcom) there is little evidence of community
willingness to do that either.

      john


From nobody Sat Feb 18 15:15:41 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C127129675 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 15:15:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dxvTTliHMFNs for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 15:15:38 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D75F129667 for <ietf@ietf.org>; Sat, 18 Feb 2017 15:15:38 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id C6F586AAF6 for <ietf@ietf.org>; Sat, 18 Feb 2017 18:15:32 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; s=sasl; bh=0ir ndjj8PjILfcnXOsRWeYZyK4I=; b=xpife6wdh4/rQPJrYNGMzgvO4jMsLkcapFS XUisV8r1JKUVs68LWV8SWJeIqnsD0js3VhzJiYSGKp4xqsQnT4MIOcqjrWPP2xc2 ZJWT1j/FG4kt50cLRAHLoRaYea5+w6YNKXtThrfCG+zuUTb80GV7x9cG+OEYpP5I wAMAJ2fM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:cc:content-type; q=dns; s=sasl; b= gf9IfeQZIbQiW3djz4g2qMGqj4wMP/SiCA6wTpg+kWZeVVfMBMjFXbGJAOXUYk4t dj2f1u2ybRQ72fkQl5IJWphREq7JDclfAExcPvtUcr2fFh4VCleAqqaM3q9XEcqM vgioaEaUj3kFPEERkzSjMCmxxWbBT3CcSLRJIJ+qgF0=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id BEC9A6AAF5 for <ietf@ietf.org>; Sat, 18 Feb 2017 18:15:32 -0500 (EST)
Received: from mail-qt0-f179.google.com (unknown [209.85.216.179]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id B9FB26AAF1 for <ietf@ietf.org>; Sat, 18 Feb 2017 18:15:31 -0500 (EST)
Received: by mail-qt0-f179.google.com with SMTP id b16so15514076qte.0 for <ietf@ietf.org>; Sat, 18 Feb 2017 15:15:31 -0800 (PST)
X-Gm-Message-State: AMke39l8tpIAY1J60als1sHpsQ+3soqGQbCHP5zwtuE64oyvL/Py5MG/gTy000LPmfAiwarNFo501/qj2E0Lcg==
X-Received: by 10.200.49.167 with SMTP id h36mr13255506qte.11.1487459731289; Sat, 18 Feb 2017 15:15:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sat, 18 Feb 2017 15:15:10 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Sat, 18 Feb 2017 15:15:10 -0800
X-Gmail-Original-Message-ID: <CACL_3VG2WW_gKbdKznYMMdHTofAweSS1xrHo1Kahg85rsUutSA@mail.gmail.com>
Message-ID: <CACL_3VG2WW_gKbdKznYMMdHTofAweSS1xrHo1Kahg85rsUutSA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: 24CEF378-F630-11E6-B247-FE3F13518317-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Kp7UTbAhztvYx63E8vKLaPeCNGA>
Cc: Ole Troan <ot@cisco.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 18 Feb 2017 23:15:40 -0000

On 2017-02-17 Joel M. Halpern wrote:
> I disagree with your interpretation of the bar the document must meet.
> I believe I have clearly stated my concern.
> I will leave that judgment to the relevant ADs and IESG when they
> review the last call results.

Thank you for saying this.  I am glad to see that someone who was not
involved in the WG discussion has chosen to speak out in support of
that position.

During the WG discussion, I said:

"If I were on the IESG and a spec came to me with a known ambiguity,
 I would vote to send it back to the WG with instructions to resubmit
 it after the ambiguity was fixed."

I would base that on the following language from RFC 2127, Section
3.1 (which replaces similar language in RFC 2026, Section 4.1.1):

   A Proposed Standard will have no known technical omissions with
   respect to the requirements placed upon it.

The relevant ADs and IESG may see this differently, but in my view,
language that has been shown to admit conflicting interpretations,
either by implementors or by authors of subsequent specifications,
constitutes a "known technical omission," and if that's not good
enough for PS, it's clearly not good enough for IS, either.

There is ample evidence in the record that the language in both 2460
and now in 2460bis has led to conflicting interpretations regarding
the admissibility of insertion of extension headers by any node other
than the one originating the packet.  The main discussion in 6man
focused on the segment routing header, where versions of
draft-previdi-6man-segment-routing-header up through 07 called for
insertion of that header by a border router, and according to
https://www.ietf.org/mail-archive/web/ipv6/current/msg20892.html and
https://www.ietf.org/mail-archive/web/ipv6/current/msg24145.html,
that behavior was actually implemented (for further evidence, see
also https://lwn.net/Articles/698841/).  That behavior was removed
in favor of encapsulation in the -08 version of the draft and also in
the version adopted by 6man (draft-ietf-6man-segment-routing-header),
but the older implementations apparently linger on.

The early SRH drafts, however, are not the only examples of conflicting
interpretations of the language in 2460. RFC 6621 Section 6.1.3 says:

   If a digest collision is detected at an SMF ingress point, the H-DPD
   option header is constructed with a randomly generated HAV.  An HAV
   is recalculated as needed to produce a non-colliding hash value prior
   to forwarding.  The multicast packet is then forwarded with the added
   IPv6 SMF_DPD option header.

By contrast, RFC 4782 (Quick Start) and RFC 6971 (Depth-First Forwarding)
were careful to specify that the HBH options defined therein were either
inserted by the source node or that encapsulation was used if inserted
by a non-originating node.

I couldn't find any discussion of 6621 or 6971 in the 6man archive.
I did see 4782 mentioned as problematic, but I didn't get that from
reading the RFC, which carefully discussed compatibility with AH.

On 2017-02-17, Ole Troan wrote:
> Do we agree that you can see this at two different angles?
>
> 1) Are there any interoperability issue or ambiguity in the protocol
>    specification of 2460 and how implementors of 2460 have interpreted
>    that?
>
> 2) Is 2460 "future-ambiguous", i.e it is unclear if 2460 permits a
>    future extension? Like ECMP, Header insertion NAT...

Question #1 is incomplete, as it fails to ask if there is an ambiguity
that has tripped up authors of specifications extending IPv6. That is
demonstrably the case. And it is equally clear from the discussion
on record that insertion of extension headers by intermediate nodes
breaks fundamental assumptions of IPv6 and causes some of the
core specifications to fail.

Question #2 is also incomplete, as it fails to acknowledge the
difference between extensions that break parts of the core
specifications and those that do not.

> I'm trying out the argument of declaring the whole question of
> ambiguity out of scope. To see if there is better consensus for
> that.

And I am hoping that the community and the IESG do not buy this.

Best regards,

Mike Heard


From nobody Sat Feb 18 16:03:19 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22E4B1296A2 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level: 
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=uEsihd5T; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=iDmXogaz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vWj4s3MPDC2w for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:03:17 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E9AA2129401 for <ietf@ietf.org>; Sat, 18 Feb 2017 16:03:16 -0800 (PST)
Received: from sm-THINK.elandsys.com ([197.226.55.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1J02ubG019412 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Feb 2017 16:03:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1487462591; x=1487548991; bh=N1SbMYEHtTJAlsierYTA4Oqat2nuyTQoTU3O9SIFcn4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=uEsihd5T04Hq0ZiFzihW5KAuXopdkoKrjMMTHp7priO7rkDPhzYxClTnM8I391VbY flVpjeBg2aMBIz/UpJFhHxXDtuCmFbJWRQL5/RHx8WgQyBsUEY6kdLOpsGbmdRcALh WES0XHdbiDJg3YTOsUyHh3MFHSlVYpqDcvQ6hRig=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1487462591; x=1487548991; i=@elandsys.com; bh=N1SbMYEHtTJAlsierYTA4Oqat2nuyTQoTU3O9SIFcn4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iDmXogazVi5BqSwraQ67g/1m4feHR7Monj6nKhr+L0mDuckM+EOW8Rb6kD7zKuBrG oSFt87ehsOI+pYn+LrpXxJvlxb0O8886V/MCcKfpkPsObpuTsH6owpZS71P4v0PoBZ +MGmQAkI3FAEF23os+JkYF+iDiBKvdKY8GZHPHQI=
Message-Id: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 18 Feb 2017 15:59:06 -0800
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: To "lose the argument in the WG"
In-Reply-To: <AB7BB4019CE95D16CA7B0B8D@PSB>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/x0BXeZFIzY94aMLda4aRtD62jzo>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 00:03:18 -0000

Hi John,
At 07:26 AM 2/18/2017, John C Klensin wrote:
>It can be something else as well.  We could be more careful
>about our vocabulary (but probably won't be), but consider a
>scenario in which someone, even someone who is quite expert in a
>given topic, looks at a WG charter and likely leadership and
>participants and says to herself "This is unlikely to produce
>anything harmful or go off into the weeds or is sufficiently
>narrowly scoped to not pose a general problem.  I do not have
>unlimited time to spend on IETF work, and my knowledge and
>skills are needed elsewhere".  That is an "I don't have time"
>scenario, but it is a vote of confidence in those actively
>participating in the WG (and the WG Chair and AD involved) not
>abusive of them.  If it then turns out that the WG, in her
>opinion, does go off into the weeds, produces someone harmful to
>the Internet or other work, or even produces something outside
>the scope of the charter, I think the community needs her to
>speak up and that any attempt to dismiss the concerns on the
>grounds of "you should have participated more and earlier" are
>not only abusive but pose a danger to the IETF.

There are two message from Ted and Pete about "abusive" [1][2].  Pete 
made an interesting comment: "The process can't depend on a single 
participant's time."  In the above-mentioned scenario, and assuming 
that it is IETF work which I am supposed to do, I would take the Last 
Call comments into consideration.

>The only solution to that sort of time conflict is for the IETF
>to become much less ambitious about how much work can be done in
>parallel, possibly by constraining the number of WGs.  The
>latter has been proposed a few times, but has gone nowhere, I
>think in part because even its advocates want whatever work they
>want to do next to be treated exceptionally.

Isn't the issue about the volume of WG discussions which an Area 
Director has to manage instead of the number of WGs?

>I also note that a Last Call complaint (or appeal, or suggestion
>of intent to appeal) on the grounds that a document on which an
>IETF Last Call has been initiated exceeds the scope of the
>relevant WG Charter has ever gone anywhere.  It isn't clear to
>me how cases like that should be handled because the work has
>typically been completed and there is no obvious basis for
>sending the document back to the WG for technical corrections.
>The community should probably fire ADs who let that sort of
>thing happen, but (without guessing at what discussions occur
>within the Nomcom) there is little evidence of community
>willingness to do that either.

It is up to the Working Group Chair and Responsible Area Director to 
assess whether the WG output falls within the WG Charter.

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg101332.html
2. https://www.ietf.org/mail-archive/web/ietf/current/msg101335.html 


From nobody Sat Feb 18 16:41:36 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C06B1296AC for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J8ib8QMj2E2I for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::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 1E61B1296AF for <ietf@ietf.org>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id k15so65426134qtg.3 for <ietf@ietf.org>; Sat, 18 Feb 2017 16:41:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FGIK1K2IbMDUnCG2xDAFHShAXvi1ftj8qDpbbd+4kJk=; b=QOiU5K2996n7DcqglTmwv7wLzpQ1FR5rFoNFMp4hm/sn/WvY35K2Pd7C+/pWSLtGsh z1DN5etJWF35xM4CEXELG+XxuhDR3OVDS6CKqmOrBPu7Oljq8yRgHe2D4i10yx+iCdue mx0TMnrt0kzia8FtoPv7/qOwAbZHiPFDtRr54Zl7HTBmIChBuylmdNU4vxfXS0MYQT4/ sJfFc8RQzBuwWu7UWyPvIE5MuKmO0FC4vWyrRQuzEaaamNJ9EIdgo1W41WQaCZSQ3Yg4 uYsR0pHdB5+AP6bGLL8UIxO1hs1KJpaVd0hJGWt94ew2He60K+5mmaPFBxUYU2sRa4rY 2eqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FGIK1K2IbMDUnCG2xDAFHShAXvi1ftj8qDpbbd+4kJk=; b=oUrF9CH6o4xdOQ6M2QUmUkmcatgZztlvX4nxbw7JmjS+h0RTs7Zw7Petxicj3MIUqr 7Og14KdOdgbT4KifI2ocZH8bd8jgcZe4Zd6O/4vROoFuRZH6GAxUyokj8DRloA+4p0/q mylJJ+U5509QiGZaV8NY/EfATc4FXKtPPSF4T7gSyQrOLeyzr/K2gfWp+aJtLstxue0e JV61CbgTRLNsvvIUOOVb+eeuLOAg5atU9x0nRQhh/7fraWE606Ov4t/obUFcrfUzvydC /SGAcfQ93hbFWfttILRWmH0DZ4Y/etMhYyMrag7PwGHOWsqn/mpRVle3F+98DCcHXCfR /UOQ==
X-Gm-Message-State: AMke39m0jl64qoUxjMB2yBpfNo74Pd/yyDGmpFrpzFcvlfjIL07oV1DN+OkGoPM87RhIiQ==
X-Received: by 10.237.55.196 with SMTP id j62mr13315461qtb.36.1487464892219; Sat, 18 Feb 2017 16:41:32 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id x13sm9353580qtc.51.2017.02.18.16.41.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Feb 2017 16:41:30 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_76357102-0246-4D44-A253-9BF6B83FDC16"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Sat, 18 Feb 2017 19:41:20 -0500
In-Reply-To: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CgEVevUIekzDoT3e8kY_AwOm4UE>
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 00:41:34 -0000

--Apple-Mail=_76357102-0246-4D44-A253-9BF6B83FDC16
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 18, 2017, at 6:59 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> It is up to the Working Group Chair and Responsible Area Director to =
assess whether the WG output falls within the WG Charter.

This is technically true, but it's worth pointing out that working group =
charters are approved first by the IETF, and only _then_ by the IESG.   =
If the IESG decides that the working group charter is much broader than =
the IETF agreed it is, then that is a process failure.=20

In practice the IETF often leaves these issues entirely to the IESG, so =
in practice this isn't necessarily a problem, but in principle it is, =
and you can't know whether the IETF said nothing about a charter because =
we agreed with the scope, or because we didn't look at it; in the former =
case, the IETF actually does have a position on the scope of the =
charter=E2=80=94it's just unstated, because it agrees with what was =
proposed.   Going beyond that scope would definitely be a process =
failure.


--Apple-Mail=_76357102-0246-4D44-A253-9BF6B83FDC16
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"">On Feb 18, 2017, at 6:59 PM, S Moonesamy &lt;<a =
href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">It is up to the =
Working Group Chair and Responsible Area Director to assess whether the =
WG output falls within the WG Charter.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""></div></blockquote></div><br class=3D""><div =
class=3D"">This is technically true, but it's worth pointing out that =
working group charters are approved first by the IETF, and only _then_ =
by the IESG. &nbsp; If the IESG decides that the working group charter =
is much broader than the IETF agreed it is, then that is a process =
failure.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">In practice the IETF often leaves these issues entirely to =
the IESG, so in practice this isn't necessarily a problem, but in =
principle it is, and you can't know whether the IETF said nothing about =
a charter because we agreed with the scope, or because we didn't look at =
it; in the former case, the IETF actually does have a position on the =
scope of the charter=E2=80=94it's just unstated, because it agrees with =
what was proposed. &nbsp; Going beyond that scope would definitely be a =
process failure.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_76357102-0246-4D44-A253-9BF6B83FDC16--


From nobody Sat Feb 18 19:10:17 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59187129435 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGxcgaxyZ28B for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:10:14 -0800 (PST)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::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 E6AB9128BA2 for <ietf@ietf.org>; Sat, 18 Feb 2017 19:10:13 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id u25so72644222qki.2 for <ietf@ietf.org>; Sat, 18 Feb 2017 19:10:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=gObOTSShrrw+6KYLN4zl5h/ICRQalWdOmQiY0TxCYwA=; b=Vhl21HsppcTDLleMmbR8hf8ZILflwI522h68+D1fJfd6VHry3Yem0NolXXmXqyVlWh JUbxhzTNiaTwBwC7HQXvYCFyTyj+5FgACqOTD9PeAf8NRY8TotPJkXNsn4LoE/2jRdd+ GexTycl8t3MeKPI4C2ZSf6ma64bzF3/7vW7ow88x262eYLSTS3lUpR6ulQVVNJE46ioJ aJJV3fZxfmJxBJUTgTRSL/FVChkK/OQ2F2NHkXRAUzJl46soi3e8qgdTxgdN103vhjDV TTMGjJs7kwLCYENHmE3qAJ8E82oGfjFJ0Hpu3QLpTjNbU26Qba7M11vi1YQNamuYyEb1 eVvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=gObOTSShrrw+6KYLN4zl5h/ICRQalWdOmQiY0TxCYwA=; b=mE0yoV3sBXF1Y2eD+w1iqrc0R+b9CzAN/eKXUhR4VthHSznUEJakxqLPl2mMdJ5/E/ z8lhEjfwFg2Wp/xoTi9RVTJ9Bn8B1AKS+ik5FSZu3hkiDmEgV1fXf12AsmxxpyUh3tDw GsFqKmHJtpZ+NQxsdXszhDK7NeLwkJHJRvgdpUoRkU8PbsNyv8QIa2eGWgsvhb8SagB4 +t777joioyBmaSpwfTm0IHp+PorLM4eceEZy+eJWBpGb/uuNZADBADH99XWZyatlbjl6 kkC5ucW8IvGmgaM3eYwvGWUIxI12I7JrJUVfieXG7s0fQPuj3SRLToFJZgDsa5MCxGqY B0FQ==
X-Gm-Message-State: AMke39l5dmEUSUUzmcmeLpGJmKPPyt1H4W6qB7sCU0eRJxy0rXD1GvRrdZGr7tOcnU03eA==
X-Received: by 10.55.64.73 with SMTP id n70mr13593011qka.186.1487473813035; Sat, 18 Feb 2017 19:10:13 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id l53sm9579945qtl.41.2017.02.18.19.10.11 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Feb 2017 19:10:11 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <D8B7C051-53A1-4EEC-A639-88767C5B3BC4@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9B0D3302-1357-410F-864A-8B5421411823"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: To "lose the argument in the WG"
Date: Sat, 18 Feb 2017 22:10:02 -0500
In-Reply-To: <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com> <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WZjGFeOPmG01nDZR8VKnqRdeAvM>
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 03:10:15 -0000

--Apple-Mail=_9B0D3302-1357-410F-864A-8B5421411823
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 18, 2017, at 7:41 PM, Ted Lemon <mellon@fugue.com> wrote:
>=20
> This is technically true, but it's worth pointing out that working =
group charters are approved first by the IETF, and only _then_ by the =
IESG.   If the IESG decides that the working group charter is much =
broader than the IETF agreed it is, then that is a process failure.=20
>=20
> In practice the IETF often leaves these issues entirely to the IESG, =
so in practice this isn't necessarily a problem, but in principle it is, =
and you can't know whether the IETF said nothing about a charter because =
we agreed with the scope, or because we didn't look at it; in the former =
case, the IETF actually does have a position on the scope of the =
charter=E2=80=94it's just unstated, because it agrees with what was =
proposed.   Going beyond that scope would definitely be a process =
failure.

Joel Halpern pointed out privately that I somewhat misrepresented the =
process here.   The IETF review process for working group charters does =
not require that there be IETF consensus to approve the charter.    This =
is true, butdoesn't actually refute my claim that it is a process =
failure if the IESG approves a charter and then allows a working group =
to do work that exceeds the bounds of the charter.   That _is_ a process =
failure, in the simple literal sense that the process did not produce =
the right outcome: the IETF community was not given an opportunity to =
review the charter that would have included the work that was done.   If =
we think that's okay, why do we have working group charters at all?

The way the process _should_ have gone in this case is that when the =
IESG noticed that new work needed to be done by a particular working =
group, they updated the charter to reflect that, and got IETF review of =
the updated charter.   In this case, you are right that if the IETF =
community was clearly opposed to the new work, the IESG could still =
approve the charter.   But this would be extraordinary.

And this is why the IETF community shouldn't treat charter updates as =
pro forma.   Charter review is an important part of the feedback =
mechanism that keeps the IETF a consensus-driven organization.   Doing =
out-of-charter work, or lawyering the charter to say that work that =
really isn't part of the intent of the charter nevertheless conforms to =
the letter of the charter, bypasses this important step.


--Apple-Mail=_9B0D3302-1357-410F-864A-8B5421411823
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"">On Feb 18, 2017, at 7:41 PM, Ted Lemon &lt;<a =
href=3D"mailto:mellon@fugue.com" class=3D"">mellon@fugue.com</a>&gt; =
wrote:<br class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"" =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">This is technically true, but it's =
worth pointing out that working group charters are approved first by the =
IETF, and only _then_ by the IESG. &nbsp; If the IESG decides that the =
working group charter is much broader than the IETF agreed it is, then =
that is a process failure.&nbsp;</div><div class=3D"" =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><br class=3D""></div><div class=3D"" =
style=3D"font-family: Helvetica; font-size: 14px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">In practice the IETF often leaves these =
issues entirely to the IESG, so in practice this isn't necessarily a =
problem, but in principle it is, and you can't know whether the IETF =
said nothing about a charter because we agreed with the scope, or =
because we didn't look at it; in the former case, the IETF actually does =
have a position on the scope of the charter=E2=80=94it's just unstated, =
because it agrees with what was proposed. &nbsp; Going beyond that scope =
would definitely be a process failure.</div></div></blockquote></div><br =
class=3D""><div class=3D"">Joel Halpern pointed out privately that I =
somewhat misrepresented the process here. &nbsp; The IETF review process =
for working group charters does not require that there be IETF consensus =
to approve the charter. &nbsp; &nbsp;This is true, butdoesn't actually =
refute my claim that it is a process failure if the IESG approves a =
charter and then allows a working group to do work that exceeds the =
bounds of the charter. &nbsp; That _is_ a process failure, in the simple =
literal sense that the process did not produce the right outcome: the =
IETF community was not given an opportunity to review the charter that =
would have included the work that was done. &nbsp; If we think that's =
okay, why do we have working group charters at all?</div><div =
class=3D""><div class=3D""><br class=3D""></div><div class=3D"">The way =
the process _should_ have gone in this case is that when the IESG =
noticed that new work needed to be done by a particular working group, =
they updated the charter to reflect that, and got IETF review of the =
updated charter. &nbsp; In this case, you are right that if the IETF =
community was clearly opposed to the new work, the IESG could still =
approve the charter. &nbsp; But this would be extraordinary.</div><div =
class=3D""><br class=3D""></div><div class=3D"">And this is why the IETF =
community shouldn't treat charter updates as pro forma. &nbsp; Charter =
review is an important part of the feedback mechanism that keeps the =
IETF a consensus-driven organization. &nbsp; Doing out-of-charter work, =
or lawyering the charter to say that work that really isn't part of the =
intent of the charter nevertheless conforms to the letter of the =
charter, bypasses this important step.</div></div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_9B0D3302-1357-410F-864A-8B5421411823--


From nobody Sat Feb 18 19:44:26 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FB7212949F for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:44:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qckHawKzCt1R for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:44:22 -0800 (PST)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 1759012948A for <ietf@ietf.org>; Sat, 18 Feb 2017 19:44:22 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id 90220C6B for <ietf@ietf.org>; Sun, 19 Feb 2017 03:44:21 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o3rB9TdqNo0v for <ietf@ietf.org>; Sat, 18 Feb 2017 21:44:21 -0600 (CST)
Received: from mail-ua0-f198.google.com (mail-ua0-f198.google.com [209.85.217.198]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 41E96BB8 for <ietf@ietf.org>; Sat, 18 Feb 2017 21:44:20 -0600 (CST)
Received: by mail-ua0-f198.google.com with SMTP id j56so32684511uaa.0 for <ietf@ietf.org>; Sat, 18 Feb 2017 19:44:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vENPJ7tsC7rcxJIyAfbBV1PPtjAJy6a7qI2hLSRJlzQ=; b=mALdzE/EkWfS1IqaA9IcEwVqyYvsYXQMBlLs9GaT9jy3RcgAiBBZJyOxXS+LqNNURV xo7blYuAAydqui63Xt3pBc1/ZrAjGYNdMRyhyGiyTlYVAGK1NhFZpC/RKzFICxUb7Fkc 0uWJWcGrW/FEYuVVnvE2bsbxJLfjrgLj35fkzsVYUNyah/iPgb/NuzfYNptZFmwdBCJL T5VMkiYOQqhaAhEhbtlmFjfd8j+38MJNUM0BIHQx8Goe6a/gi7B4V4RSRCWv3IDpZ9tz l3RQDYIxEtxsAKelAT7Vk4+M+09nYN4XYGno5y0zg53S/t0ZBPWIkOuyTSqZ+kF/U1TY oxSA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vENPJ7tsC7rcxJIyAfbBV1PPtjAJy6a7qI2hLSRJlzQ=; b=QAqCMJ3N4nXWVBRGkHDFx9yfP8wRwnk0WIdATUIJeKTwKMSfLAUjcwBolQxo7sArdk CPQ1srQxVdCOjF/+gRriSoZn8GXJLsseSB9dUiKoTA7PNisOi8u9ot63yh6r1xT388+A p86BbBTGIFFwAmJ7Prc/sN0Bfg9+rCnWtWjkaDDs11LxaETXEjLTPfolo2ItDR31bzAv k6Y5fsYaCOLrDf76IOsgpFbfn/LUhQRRXqtQ+QmtGPzWJs9w2la/VBAnihIrnlffENP5 28NCpxCjwepOQFuyDJXDYjweASapkt0KfV+pHgvssZstxgPbTwOLJSlkBF3aT+Jjgfyx NR8g==
X-Gm-Message-State: AMke39nfirmjoM2+7CKBDXQvg6fZqlpwHhjWzpi3vl9zt70Mm7ofVA4yKxEju5+bqK47YJhX1o5F1UVwMrPagV2d/65zRThyjpYrxJjPuyv8Iod+upN2AHYTR3vL6leT53POhwNlCI77IHlzqtM=
X-Received: by 10.159.32.38 with SMTP id 35mr7759806uam.12.1487475860253; Sat, 18 Feb 2017 19:44:20 -0800 (PST)
X-Received: by 10.159.32.38 with SMTP id 35mr7759797uam.12.1487475860052; Sat, 18 Feb 2017 19:44:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.13 with HTTP; Sat, 18 Feb 2017 19:44:18 -0800 (PST)
In-Reply-To: <031601d2891b$eec55dc0$4001a8c0@gateway.2wire.net>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <031601d2891b$eec55dc0$4001a8c0@gateway.2wire.net>
From: David Farmer <farmer@umn.edu>
Date: Sat, 18 Feb 2017 21:44:18 -0600
Message-ID: <CAN-Dau3wo2puS0Yz+n8Drjwp1875+aHYBGFc+rqmv-eZ2iJ52A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: "tom p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=94eb2c04cac2402b050548d9f63d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jKkpclW7zEvLLcxbrCvCSmbSAqs>
Cc: james woodyatt <jhw@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 03:44:25 -0000

--94eb2c04cac2402b050548d9f63d
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 17, 2017 at 6:46 AM, tom p. <daedulus@btconnect.com> wrote:

> From: <otroan@employees.org>
> To: "james woodyatt" <jhw@google.com>
> Cc: <draft-ietf-6man-rfc4291bis@ietf.org>; "6man WG" <ipv6@ietf.org>;
> "IETF-Discussion Discussion" <ietf@ietf.org>; <6man-chairs@ietf.org>
> Sent: Friday, February 17, 2017 7:44 AM
>
> > James,
> >
> > 4291:
> >    For all unicast addresses, except those that start with the binary
> >    value 000, Interface IDs are required to be 64 bits long and to be
> >    constructed in Modified EUI-64 format.
> >
> > 4291bis:
> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
> >    on inter-router point-to-point links.  However, the Interface ID of
> >    all unicast addresses, except those that start with the binary
> value
> >    000, is required to be 64 bits long.  The rationale for the 64 bit
> >    boundary in IPv6 addresses can be found in [RFC7421]
> >
> > Proposal:
> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >   128 bits [BCP198]. However, as explained in [RFC7421], the Interface
> ID
> >    of unicast addresses is generally required to be 64 bits in length,
> with
> >    exceptions only provided in special cases where expressly
> recognised
> >    in IETF standards track documents.
> >
> > I think that's a good proposal.
> > Perhaps with s/is generally required to be/are/
>
> Ole
>
> I would go further on the grounds that this is still somewhat woolly.  I
> would say
>
> Proposal':
>   IPv6 unicast routing is based on prefixes of any valid length up to
>  128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
>   of unicast addresses is required to be 64 bits in length; any
> exceptions
>   must be specified in IETF standards track documents.
>
>
> It would be nice to have something IANA-like with different categories
> of what can update what, with this being at the higher level, the bar
> set higher for an Interface ID that is not 64 bits in length, but when
> we say 'standards track' we are calling for IETF consensus and IESG
> approval and it is hard to see what more could be called for, unless we
> say that this is architectural and so the IAB must approve it!
>

I don't think the intent of that language is to define or constrain our
processes.  As I see it, the purpose of that text is to make it clear the
IID length is and has always been a parameter, which operators are
constrained by this text to to set at 64 bits, but this value cannot be
embedded as a magic value in code, because there are cases where its not 64
bits, even beyond addresses that start with 000.

I'll conceded, whether 64 bit boundary is a requirement, or more
appropriately a recommendation, is probably beyond the scope of a bis
document. However, clarifying who the requirement is directed at, is most
certainly within scope and I think imperative.  I have never heard anyone
claim this requirement is to be put in code, in fact quite the contrary,
everyone seem to agree it should NOT be put in code, and therefore by
reduction it is intended to be an operational constraint.  Or in other
word, the requirement is primarily directed at operators of IPv6 networks,
and not implementers of IPv6.

The following takes the essential text from from RFC4291, rearranges it a
little and wraps it with clarifying language, which is what we should be
doing in a BIS document.  Now those of us that want more significant
changes, it's incumbent on us to write standards track documents, and get
consensus for them, like it has always been.  But in the mean time
implementations are put on notice that 64 bit boundary is primarily an
operational constraint and not something that can safely be embedded in
code.

So I suggest the following;

   IPv6 unicast routing is based on prefixes of any valid length up to 128
   [BCP198].  However, as discussed more thoroughly in [RFC7421], the length
   of the Interface ID is a parameter, that is required to be 64 bits for
   all unicast addresses, except those that start with the binary value 000,
   with additional exceptions provided in other standards track documents.
   Other than it's implications to Stateless Address
Autoconfiguration(SLAAC)
   [RFC4862], this requirement's primary effect is operational, as
   implementations of IPv6 must not ignore or override the local
   configuration of this parameter, even if it conflicts with this
   requirement. The rationale for the 64 bit boundary in IPv6 addresses
   can be found in [RFC7421].

However, the text we have been discussing is the second paragraph of
section 2.4 of the draft, but if preferred these last two, sentences could
be broken out and integrated in section 2.4.1

Leaving the second paragraph of 2.4 something like this;

   IPv6 unicast routing is based on prefixes of any valid length up to 128
   [BCP198].  However, as discussed more thoroughly in [RFC7421], the length
   of the Interface ID is a parameter, that is required to be 64 bits for
   all unicast addresses, except those that start with the binary value 000,
   with additional exceptions provided in other standards track documents.

With the forth paragraph of 2.4.1 something like this;

   As noted in Section 2.4, the length of the Interface ID is a parameter,
   that is required to be 64 bits for all unicast addresses, except those
   that start with the binary value 000, with additional exceptions
   provided in other standards track documents. Other than it's
   implications for Stateless Address Autoconfiguration(SLAAC)[RFC4862],
   this requirement's primary effect is operational, as implementations
   of IPv6 must not ignore or override the local configuration of this
   parameter, even if it conflicts with this requirement. The rationale
   for the 64 bit boundary in IPv6 addresses can be found in [RFC7421].

Thanks


> Tom Petch
>
> > Best regards,
> > Ole
> >
> >
>
>
-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 17, 2017 at 6:46 AM, tom p. <span dir=3D"ltr">&lt;<a href=
=3D"mailto:daedulus@btconnect.com" target=3D"_blank">daedulus@btconnect.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>From: &lt;<a href=3D"mailto:otroan@employees.org" target=3D"_blank">otroan=
@employees.org</a>&gt;<br>
To: &quot;james woodyatt&quot; &lt;<a href=3D"mailto:jhw@google.com" target=
=3D"_blank">jhw@google.com</a>&gt;<br>
Cc: &lt;<a href=3D"mailto:draft-ietf-6man-rfc4291bis@ietf.org" target=3D"_b=
lank">draft-ietf-6man-rfc4291bis@ie<wbr>tf.org</a>&gt;; &quot;6man WG&quot;=
 &lt;<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.org</a>&g=
t;;<br>
&quot;IETF-Discussion Discussion&quot; &lt;<a href=3D"mailto:ietf@ietf.org"=
 target=3D"_blank">ietf@ietf.org</a>&gt;; &lt;<a href=3D"mailto:6man-chairs=
@ietf.org" target=3D"_blank">6man-chairs@ietf.org</a>&gt;<br>
Sent: Friday, February 17, 2017 7:44 AM<br>
<br>
&gt; James,<br>
&gt;<br>
&gt; 4291:<br>
&gt;=C2=A0 =C2=A0 For all unicast addresses, except those that start with t=
he binary<br>
&gt;=C2=A0 =C2=A0 value 000, Interface IDs are required to be 64 bits long =
and to be<br>
&gt;=C2=A0 =C2=A0 constructed in Modified EUI-64 format.<br>
&gt;<br>
&gt; 4291bis:<br>
&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid le=
ngth up to<br>
&gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For example, [RFC6164] standardises 1=
27 bit prefixes<br>
&gt;=C2=A0 =C2=A0 on inter-router point-to-point links.=C2=A0 However, the =
Interface ID of<br>
&gt;=C2=A0 =C2=A0 all unicast addresses, except those that start with the b=
inary<br>
value<br>
&gt;=C2=A0 =C2=A0 000, is required to be 64 bits long.=C2=A0 The rationale =
for the 64 bit<br>
&gt;=C2=A0 =C2=A0 boundary in IPv6 addresses can be found in [RFC7421]<br>
&gt;<br>
&gt; Proposal:<br>
&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid le=
ngth up to<br>
&gt;=C2=A0 =C2=A0128 bits [BCP198]. However, as explained in [RFC7421], the=
 Interface<br>
ID<br>
&gt;=C2=A0 =C2=A0 of unicast addresses is generally required to be 64 bits =
in length,<br>
with<br>
&gt;=C2=A0 =C2=A0 exceptions only provided in special cases where expressly=
<br>
recognised<br>
&gt;=C2=A0 =C2=A0 in IETF standards track documents.<br>
&gt;<br>
&gt; I think that&#39;s a good proposal.<br>
&gt; Perhaps with s/is generally required to be/are/<br>
<br>
Ole<br>
<br>
I would go further on the grounds that this is still somewhat woolly.=C2=A0=
 I<br>
would say<br>
<br>
Proposal&#39;:<br>
=C2=A0 IPv6 unicast routing is based on prefixes of any valid length up to<=
br>
=C2=A0128 bits [BCP198]. However, as explained in [RFC7421], the Interface =
ID<br>
=C2=A0 of unicast addresses is required to be 64 bits in length; any<br>
exceptions<br>
=C2=A0 must be specified in IETF standards track documents.<br>
<br>
<br>
It would be nice to have something IANA-like with different categories<br>
of what can update what, with this being at the higher level, the bar<br>
set higher for an Interface ID that is not 64 bits in length, but when<br>
we say &#39;standards track&#39; we are calling for IETF consensus and IESG=
<br>
approval and it is hard to see what more could be called for, unless we<br>
say that this is architectural and so the IAB must approve it!<br></blockqu=
ote><div><br></div><div>I don&#39;t think the intent of that language is to=
 define or constrain our processes.=C2=A0 As I see it, the purpose of that =
text is to make it clear the IID length is and has always been a parameter,=
 which operators are constrained by this text to to set at 64 bits, but thi=
s value cannot be embedded as a magic value in code, because there are case=
s where its not 64 bits, even beyond addresses that start with 000. =C2=A0<=
/div><div><br></div><div><div>I&#39;ll conceded, whether 64 bit boundary is=
 a requirement, or more appropriately a recommendation, is probably beyond =
the scope of a bis document. However, clarifying who the requirement is dir=
ected at, is most certainly within scope and I think imperative.=C2=A0 I ha=
ve never heard anyone claim this requirement is to be put in code, in fact =
quite the contrary, everyone seem to agree it should NOT be put in code, an=
d therefore by reduction it is intended to be an operational constraint.=C2=
=A0 Or in other word, the requirement is primarily directed at operators of=
 IPv6 networks, and not implementers of IPv6. =C2=A0 =C2=A0=C2=A0</div></di=
v><div><br></div><div>The following takes the essential text from from RFC4=
291, rearranges it a little and wraps it with clarifying language, which is=
 what we should be doing in a BIS document.=C2=A0 Now those of us that want=
 more significant changes, it&#39;s incumbent on us to write standards trac=
k documents, and get consensus for them, like it has always been.=C2=A0 But=
 in the mean time implementations are put on notice that 64 bit boundary is=
 primarily an operational constraint and not something that can safely be e=
mbedded in code.=C2=A0<br></div></div><div class=3D"gmail_extra"><br></div>=
</div><div><div class=3D"gmail_extra">So I suggest the following;<br><br>=
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to 128<br>=C2=A0 =C2=A0[BCP198].=C2=A0 However, as discussed more thorou=
ghly in [RFC7421], the length<br>=C2=A0 =C2=A0of the Interface ID is a para=
meter, that is required to be 64 bits for<br>=C2=A0 =C2=A0all unicast addre=
sses, except those that start with the binary value 000,<br>=C2=A0 =C2=A0wi=
th additional exceptions provided in other standards track documents.<br>=
=C2=A0 =C2=A0Other than it&#39;s implications to Stateless Address Autoconf=
iguration(SLAAC)<br>=C2=A0 =C2=A0[RFC4862], this requirement&#39;s primary =
effect is operational, as<br>=C2=A0 =C2=A0implementations of IPv6 must not =
ignore or override the local<br>=C2=A0 =C2=A0configuration of this paramete=
r, even if it conflicts with this<br>=C2=A0 =C2=A0requirement. The rational=
e for the 64 bit boundary in IPv6 addresses<br>=C2=A0 =C2=A0can be found in=
 [RFC7421].<br><br>However, the text we have been discussing is the second =
paragraph of section 2.4 of the draft, but if preferred these last two, sen=
tences could be broken out and integrated in section 2.4.1 <br><br>Leaving =
the second paragraph of 2.4 something like this;<br><br>=C2=A0 =C2=A0IPv6 u=
nicast routing is based on prefixes of any valid length up to 128<br>=C2=A0=
 =C2=A0[BCP198].=C2=A0 However, as discussed more thoroughly in [RFC7421], =
the length<br>=C2=A0 =C2=A0of the Interface ID is a parameter, that is requ=
ired to be 64 bits for<br>=C2=A0 =C2=A0all unicast addresses, except those =
that start with the binary value 000,<br>=C2=A0 =C2=A0with additional excep=
tions provided in other standards track documents.<br><br>With the forth pa=
ragraph of 2.4.1 something like this;<br><br>=C2=A0 =C2=A0As noted in Secti=
on 2.4, the length of the Interface ID is a parameter,</div><div class=3D"g=
mail_extra">=C2=A0 =C2=A0that is required to be 64 bits for all unicast add=
resses, except those</div><div class=3D"gmail_extra">=C2=A0 =C2=A0that star=
t with the binary value 000, with additional exceptions</div><div class=3D"=
gmail_extra">=C2=A0 =C2=A0provided in other standards track documents. Othe=
r than it&#39;s</div><div class=3D"gmail_extra">=C2=A0 =C2=A0implications f=
or Stateless Address Autoconfiguration(SLAAC)[RFC4862], <br>=C2=A0 =C2=A0th=
is requirement&#39;s primary effect is operational, as implementations<br>=
=C2=A0 =C2=A0of IPv6 must not ignore or override the local configuration of=
 this<br>=C2=A0 =C2=A0parameter, even if it conflicts with this requirement=
. The rationale<br>=C2=A0 =C2=A0for the 64 bit boundary in IPv6 addresses c=
an be found in [RFC7421].</div><div class=3D"gmail_extra"><br>Thanks<br>=C2=
=A0<br></div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex">
Tom Petch<br>
<br>
&gt; Best regards,<br>
&gt; Ole<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><div><br></div>-- <br><div class=3D"gmail-m_-38792838797=
709309m_-5462801538659932156gmail-m_4791314674415143348m_776552765749839257=
0gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Em=
ail:farmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Of=
fice of Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2=
218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612=
)%20626-0815" value=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>=
Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-995=
2" value=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div></div>

--94eb2c04cac2402b050548d9f63d--


From nobody Sat Feb 18 19:56:54 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2510128B44 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:56:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 D_W-knLX70B4 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 19:56:52 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A698129407 for <ietf@ietf.org>; Sat, 18 Feb 2017 19:56:52 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cfIc7-0009TJ-Ox; Sat, 18 Feb 2017 22:56:43 -0500
Date: Sat, 18 Feb 2017 22:56:38 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, ietf@ietf.org
Subject: Re: To "lose the argument in the WG"
Message-ID: <55E03EE38894AF3FBC97DE8F@JcK-HP5.jck.com>
In-Reply-To: <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BE5L2MIfqgiFfotFIW1Ul8YxHKo>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 03:56:54 -0000

--On Saturday, February 18, 2017 3:59 PM -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

>...
>> The only solution to that sort of time conflict is for the
>> IETF to become much less ambitious about how much work can be
>> done in parallel, possibly by constraining the number of WGs.
>> The latter has been proposed a few times, but has gone
>> nowhere, I think in part because even its advocates want
>> whatever work they want to do next to be treated
>> exceptionally.
> 
> Isn't the issue about the volume of WG discussions which an
> Area Director has to manage instead of the number of WGs?

There are a number of dimensions of the problem.  One could
debate their ranking by importance, but I'm not sure the
exercise would be productive.  I would encourage you to find the
earlier I-Ds (there were at least two different models) and
discussions before starting over again.

>> I also note that a Last Call complaint (or appeal, or
>> suggestion of intent to appeal) on the grounds that a
>> document on which an IETF Last Call has been initiated
>> exceeds the scope of the relevant WG Charter has ever gone
>> anywhere.  It isn't clear to me how cases like that should be
>> handled because the work has typically been completed and
>> there is no obvious basis for sending the document back to
>> the WG for technical corrections. The community should
>> probably fire ADs who let that sort of thing happen, but
>> (without guessing at what discussions occur within the
>> Nomcom) there is little evidence of community willingness to
>> do that either.
> 
> It is up to the Working Group Chair and Responsible Area
> Director to assess whether the WG output falls within the WG
> Charter.

Yes, as long as you remember that they are supposed to be
representing the will of the community and accountable to it.
Neither WG Chairs nor ADs have any other source of authority.
The difficulty with your statement above is that it can be read
to imply that there are no constraints one, or appeals from, the
decisions.  That is not true or, more specifically, if one wants
a healthy IETF that produces credible work, it better not be.

best,
   john


From nobody Sat Feb 18 23:08:21 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84EBA1288B8 for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 23:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=XgK9mAUp; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=AjRsdG+H
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I4afebGe_Eer for <ietf@ietfa.amsl.com>; Sat, 18 Feb 2017 23:08:18 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A60B4127058 for <ietf@ietf.org>; Sat, 18 Feb 2017 23:08:18 -0800 (PST)
Received: from sm-THINK.elandsys.com ([197.226.55.251]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1J77x1V007635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 18 Feb 2017 23:08:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1487488092; x=1487574492; bh=5fWUf5fJk8TnXKEuH+DHzjYfZhkH/GI9puAMbTLP/J4=; h=Date:To:From:Subject:In-Reply-To:References; b=XgK9mAUpx7R4axjvIkP4XHKt+u4k3WUWCmrXuVTlC75iZeAei8d+YSSdk9rjsuL3Q 0XUDZwCmiYm+FYzVuoaj6HPs8isZT+eor9F9NrJjNHSkWVwuYF+VH3zGq3BIPiFtn9 4I6EhIB/Gb0cpcBCQj3IxTNrKlBwwp6lfFdjTfBo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1487488092; x=1487574492; i=@elandsys.com; bh=5fWUf5fJk8TnXKEuH+DHzjYfZhkH/GI9puAMbTLP/J4=; h=Date:To:From:Subject:In-Reply-To:References; b=AjRsdG+HL/1mDrIhPs5/IXGWGB/tyrUFfIS4siSsftGxmHJSefBe6vczQlQgGxrB1 9WLlBqKCOnuQrhvhnm1qbbAtZ9fkEFQ72qLb3LgQrokGBa1PPnmNwuFyaubRl0mUfS xhLxaU6PAZeh0OLWGLbFsA4FDB6gUsgbLTN4t79E=
Message-Id: <6.2.5.6.2.20170218205437.09c36548@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 18 Feb 2017 23:07:16 -0800
To: Ted Lemon <mellon@fugue.com>, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Why do we have working group charters (was: To "lose the argument in the WG")
In-Reply-To: <D8B7C051-53A1-4EEC-A639-88767C5B3BC4@fugue.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com> <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com> <D8B7C051-53A1-4EEC-A639-88767C5B3BC4@fugue.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AUPJvowjtE7j2TnZ9r7s1guBeac>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 07:08:19 -0000

Hi Ted, John,

[I changed the subject line]

At 07:10 PM 2/18/2017, Ted Lemon wrote:
>Joel Halpern pointed out privately that I somewhat misrepresented 
>the process here.   The IETF review process for working group 
>charters does not require that there be IETF consensus to approve 
>the charter.    This is true, butdoesn't actually refute my claim 
>that it is a process failure if the IESG approves a charter and then 
>allows a working group to do work that exceeds the bounds of the 
>charter.   That _is_ a process failure, in the simple literal sense 
>that the process did not produce the right outcome: the IETF 
>community was not given an opportunity to review the charter that 
>would have included the work that was done.   If we think that's 
>okay, why do we have working group charters at all?

A Working Group charter is approved by the IESG and the IAB [1].  The 
working group charter would be a theoretical exercise if the charter 
which was published diverges significantly from what was actually 
done.  I agree that it is a process failure.

>The way the process _should_ have gone in this case is that when the 
>IESG noticed that new work needed to be done by a particular working 
>group, they updated the charter to reflect that, and got IETF review 
>of the updated charter.   In this case, you are right that if the 
>IETF community was clearly opposed to the new work, the IESG could 
>still approve the charter.   But this would be extraordinary.

It does not seem that difficult to ask for a recharter.  The relevant 
AD(s) could bring the matter to the attention of the IESG instead of 
having to ignore or to deal with a process failure.

>And this is why the IETF community shouldn't treat charter updates 
>as pro forma.   Charter review is an important part of the feedback 
>mechanism that keeps the IETF a consensus-driven 
>organization.   Doing out-of-charter work, or lawyering the charter 
>to say that work that really isn't part of the intent of the charter 
>nevertheless conforms to the letter of the charter, bypasses this 
>important step.

Describing the process issue as "lawyering" conveys the idea that it 
is unreasonable to complain about such issues.  I agree with what you 
wrote about the feedback mechanism.

At 07:56 PM 2/18/2017, John C Klensin wrote:
>There are a number of dimensions of the problem.  One could
>debate their ranking by importance, but I'm not sure the
>exercise would be productive.  I would encourage you to find the

Agreed.

>Yes, as long as you remember that they are supposed to be
>representing the will of the community and accountable to it.
>Neither WG Chairs nor ADs have any other source of authority.
>The difficulty with your statement above is that it can be read
>to imply that there are no constraints one, or appeals from, the
>decisions.  That is not true or, more specifically, if one wants
>a healthy IETF that produces credible work, it better not be.

It is possible to appeal the decision of the WG Chair, and if that 
fails, to file an appeal with the Responsible AD.  There is still an 
option to file an appeal if the issue is noticed later in the process.

There are constraints.  At the WG level, the WG Chair is accountable 
to the Area Director.  A competent Area Director would probably ask 
for an explanation if the document exceeds the scope of the WG 
Charter.  I don't know the details of the case [2] to form an opinion 
about the matter.

Regards,
S. Moonesamy

1. The wording which I used is imprecise.
2. https://www.ietf.org/mail-archive/web/ietf/current/msg101489.html 


From nobody Sun Feb 19 01:36:43 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72F5612943E; Sun, 19 Feb 2017 01:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ih_QUwbTRdhR; Sun, 19 Feb 2017 01:36:35 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (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 A67FD129434; Sun, 19 Feb 2017 01:36:34 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id AFB9B49; Sun, 19 Feb 2017 10:36:31 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1487496989; bh=FKoTW0TBLI6aD66xGwz IQv489jA7jOFmWNQVZLaTkX0=; b=eB33Wa12p2rLcIxyxgZGJfueko6fbZve6DG zp6yzv/wfvAoiBRtexF09uOnOpbkZzgaUx7Qr1f5Yi+H461+Xe5ijDI7Fqd2NI/N KU7+u0WALz/SwyStJz2Rmg/3y4mR+6Ejy68zQHQww1qu4JlkZEiAPwfazqt+jdGC qL0lRBos=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id G6UhU9HVhLQf; Sun, 19 Feb 2017 10:36:29 +0100 (CET)
Received: from [172.20.10.4] (unknown [89.200.2.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id B773848; Sun, 19 Feb 2017 10:36:27 +0100 (CET)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <567281BF-DD55-4E46-9977-4575561A83C9@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_2B330AC0-48BF-42F1-99A3-1EF72EB2E8D0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Sun, 19 Feb 2017 10:36:54 +0100
In-Reply-To: <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
To: james woodyatt <jhw@google.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8E7Hea4TfsXiI29tOP0FeLxo4gE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 09:36:36 -0000

--Apple-Mail=_2B330AC0-48BF-42F1-99A3-1EF72EB2E8D0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi,

> In response to various comments to this message, I=E2=80=99d like to =
propose a refinement:
>=20
>> IPv6 unicast routing is based on prefixes of any valid length up to =
128 bits [BCP198]. However, in accordance with the reasoning explained =
in [RFC7421], the Interface ID part of host interface addresses is =
generally 64 bits, with exceptions only provided in special cases =
expressly recognized in IETF standards track documents.

Sounds good to me. It's clear on routing, it's clear on IIDs being 64 =
bits long except in special standards-track cases without trying to =
enumerate them and it provides an informational reference to explain why =
it should be 64 bits.

> For my personal part, I=E2=80=99d prefer to see a clear statement here =
using RFC 2119 requirements language keywords, but I recognize that =
consensus probably requires compromise on that point. Hence, the =
proposed refinement above, which does not use RFC 2119 keywords. (Here =
is how I would write this with keywords: =E2=80=9CIPv6 unicast routing =
is based on network prefixes that MAY have any valid length up to 128 =
bits [BCP198]. However, in accordance with the reasoning explained in =
[RFC7421], the Interface ID part of host interface addresses SHOULD be =
64 bits with exceptions only provided in special cases expressly =
recognized in IETF standards track documents.=E2=80=9D)

I'm a bit worried that the "MAY have any valid length up to 128 bits" =
definition is too loose when read by router vendors, but otherwise that =
version sounds good as well. I like to see explicit clear guidance in =
standards documents.

One question: don't the texts conflict with things like policy based =
routing? Do we need to take that into account here?

Cheers,
Sander


--Apple-Mail=_2B330AC0-48BF-42F1-99A3-1EF72EB2E8D0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYqWc2AAoJEB7hi8LTyHy2lSIH/3BJ5RFQunF8g7JAn+hBiqsU
2UOwbsF/fB0rtYtgDvQma+cRhngoEYIDFcVRrP+sghUq2JYkHAqtIcKqthAQbrra
fhG/dyJgReeMRYLebSt8bmBLsdANIprEXDvhwr7oQGBq69yePrV3f1uTcbGz63yl
J5gvIvgKaaQrklPzlxnzDNpIc0igwxnDg7LBgejgO77UwR2ujoF+D+4CDdXij89A
0k4VY2TdIBdVJ+lWYdl2WzLxyvimHVS88jESoxoYHqS4CsQLbNd5SNmGV6WMBKrI
vwHxlLv9q20T8htfC8RSbGdawICYnL5GJn0DtcNqlArlxovgvTVIQmomJr2t4yk=
=rM3P
-----END PGP SIGNATURE-----

--Apple-Mail=_2B330AC0-48BF-42F1-99A3-1EF72EB2E8D0--


From nobody Sun Feb 19 05:02:29 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E2401294AA for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 05:02:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EytU3uzCUZLm for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 05:02:24 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 E74AD1294A6 for <ietf@ietf.org>; Sun, 19 Feb 2017 05:02:23 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id n21so2631702qta.1 for <ietf@ietf.org>; Sun, 19 Feb 2017 05:02:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yVNPnrqfpvvzU0xmO7qRZ3jnn7VXx/YSP5M4ogF1uT0=; b=cW+rcIlbGh5rmzf6AHBcUuQreMPcCZDiFIZoUffDFeXGS9H539QR39atCYsR5Aa8sh c5A2xE2bxtmlv8LQgFNTwOIXOvQRSgZJP1RxfB/EqaN17Zx13M+1xMDwNrJPTkSaf8QW Tnti1rdLYJz1Nin0mhqqiIWHEOYRv+OpEevtSqAb1sFqAgo+U/79WtzAt9nlSVu2jvKh ZeeIZcFqrvP5mDCnx8r3s+IJ/obeTdE6y9zRS3a33r2BYnYBIy22fUb7ubDZT2lsIVMk hUOxRbtZeWGLuc8jEplm2Z9eKINjpMcqZpZQHN9xZIBa0dauBRxNkGYLlOoPcozsTxt0 kTLQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yVNPnrqfpvvzU0xmO7qRZ3jnn7VXx/YSP5M4ogF1uT0=; b=RhDg9+YZA+PNv5qEkUQw6ITtTzT44fj5IJI2+2cRT8fbIPSSnBEJ4kA+hYGwTUXVKh D+FCpSF1GYCxR3f7pENR6ZSlRzRTrp0dVNCZHl2Xa3iXyuvpYbscBqZ5nqzR6k+s2Qu5 q5TbmemYreC4Uno2O6+Wtj4uHp1bldtZHykyQDsXZYAihqhZHfBV9gT28qUhtZbOEOfi JnJURWOzGCd1lxbaKn7RtwNQjgcrMwR/eI7ODFiA8ACAmvGOzb4u45fWap3Zsze3NIY0 wAzMXMN4wauiPTu6sC+frvmCnZvc/ePv64IDHyUdjJcwkGubX9QT6GT3CxUsm5wGDEGO Okaw==
X-Gm-Message-State: AMke39n7nYwrmi4br75bQz1HesEH/ylg3lWd+63OC7CI1HdYTtPjzmF0Ldb5ENhKlEiXJQ==
X-Received: by 10.200.36.81 with SMTP id d17mr14587673qtd.99.1487509342954; Sun, 19 Feb 2017 05:02:22 -0800 (PST)
Received: from [192.168.1.228] (c-73-167-64-188.hsd1.ma.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id y23sm10254978qtc.38.2017.02.19.05.02.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 19 Feb 2017 05:02:21 -0800 (PST)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <F4558EC8-87BB-4FA5-A55E-7FA6C9605CA6@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0F6A5130-8569-4983-B6A1-933EF7807305"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Why do we have working group charters (was: To "lose the argument in the WG")
Date: Sun, 19 Feb 2017 08:02:16 -0500
In-Reply-To: <6.2.5.6.2.20170218205437.09c36548@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com> <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com> <D8B7C051-53A1-4EEC-A639-88767C5B3BC4@fugue.com> <6.2.5.6.2.20170218205437.09c36548@elandnews.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/e9jCaeO9T1kHJvZc_m7mqXu0AaA>
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 13:02:25 -0000

--Apple-Mail=_0F6A5130-8569-4983-B6A1-933EF7807305
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Feb 19, 2017, at 2:07 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
>> And this is why the IETF community shouldn't treat charter updates as =
pro forma.   Charter review is an important part of the feedback =
mechanism that keeps the IETF a consensus-driven organization.   Doing =
out-of-charter work, or lawyering the charter to say that work that =
really isn't part of the intent of the charter nevertheless conforms to =
the letter of the charter, bypasses this important step.
>=20
> Describing the process issue as "lawyering" conveys the idea that it =
is unreasonable to complain about such issues.  I agree with what you =
wrote about the feedback mechanism.

By lawyering, I mean the practice of trying to fit more in the charter =
than those who participated in writing that charter intended for it to =
cover.   This is a very fine line: there are definitely cases where one =
can legitimately debate what the actual intention expressed in the =
charter is.   For this reason I think it's best for ADs to err on the =
side of caution and update the charter if an AD thinks they might be at =
the edge.


--Apple-Mail=_0F6A5130-8569-4983-B6A1-933EF7807305
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Feb 19, 2017, at 2:07 AM, S Moonesamy &lt;<a =
href=3D"mailto:sm+ietf@elandsys.com" =
class=3D"">sm+ietf@elandsys.com</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div =
class=3D"Singleton"><blockquote type=3D"cite" style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">And this is why the IETF =
community shouldn't treat charter updates as pro forma. =
&nbsp;&nbsp;Charter review is an important part of the feedback =
mechanism that keeps the IETF a consensus-driven organization. =
&nbsp;&nbsp;Doing out-of-charter work, or lawyering the charter to say =
that work that really isn't part of the intent of the charter =
nevertheless conforms to the letter of the charter, bypasses this =
important step.<br class=3D""></blockquote><br style=3D"font-family: =
Menlo-Regular; font-size: 14px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;" class=3D""><span style=3D"font-family: Menlo-Regular; font-size: =
14px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; =
display: inline !important;" class=3D"">Describing the process issue as =
"lawyering" conveys the idea that it is unreasonable to complain about =
such issues. &nbsp;I agree with what you wrote about the feedback =
mechanism.</span></div></div></blockquote></div><br class=3D""><div =
class=3D"">By lawyering, I mean the practice of trying to fit more in =
the charter than those who participated in writing that charter intended =
for it to cover. &nbsp; This is a very fine line: there are definitely =
cases where one can legitimately debate what the actual intention =
expressed in the charter is. &nbsp; For this reason I think it's best =
for ADs to err on the side of caution and update the charter if an AD =
thinks they might be at the edge.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_0F6A5130-8569-4983-B6A1-933EF7807305--


From nobody Sun Feb 19 09:34:07 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9998312944D for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 09:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.201
X-Spam-Level: 
X-Spam-Status: No, score=-2.201 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_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xmE4nkX3rvh for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 09:34:04 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A7BE129442 for <ietf@ietf.org>; Sun, 19 Feb 2017 09:34:03 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 8A425696C0 for <ietf@ietf.org>; Sun, 19 Feb 2017 12:34:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:content-type :content-transfer-encoding; s=sasl; bh=br01aGKBq1Y7MStCI+rDwbDlx 6M=; b=JeFs3kIyLZB41mtiJxEIWo8Dahp5JvEHRlcc5QNbX+ZeAKf8lO898Y5X/ u2JfYQbPOC9r7bw9ky8HyTO74Q0fBpnIrQoKSNuvnAsSXSoJXh+s0VikWt6H3OmB kVDGIpwwCM1oaluYD1bhHGiHnhsL2hrvwbv0oNcBvsSt3Vyfxg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:content-type :content-transfer-encoding; q=dns; s=sasl; b=VQOVdqnxuhhdkan3ntm zbJu0QbJsR9qCjM2BBeGpD11BQG3IDNeB5+zGByJqWAOckPFhc/vPvqdYcKs57hY Xry1tIHeVCDSxPktC2wTh8wye+GtgFBxUxlL8qIZDZbJ0+JF4oN9ZgwoVtoI4Gde vtJd5F9RFvH9TGMgXfYm6G5g=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 78E9C696BE for <ietf@ietf.org>; Sun, 19 Feb 2017 12:34:02 -0500 (EST)
Received: from mail-qt0-f169.google.com (unknown [209.85.216.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 9BDBD696BC for <ietf@ietf.org>; Sun, 19 Feb 2017 12:34:01 -0500 (EST)
Received: by mail-qt0-f169.google.com with SMTP id x49so72120662qtc.2 for <ietf@ietf.org>; Sun, 19 Feb 2017 09:34:01 -0800 (PST)
X-Gm-Message-State: AMke39lLsvvLSTHrinliwdFwvkR2cq6Dx+v/0ydt9Fk08CFg9AgatT5sOD45xoxfJ9CI2MgjYZshHVPdwr/EBA==
X-Received: by 10.200.40.113 with SMTP id 46mr15532045qtr.167.1487525640963; Sun, 19 Feb 2017 09:34:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sun, 19 Feb 2017 09:33:40 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 19 Feb 2017 09:33:40 -0800
X-Gmail-Original-Message-ID: <CACL_3VEykmViHpT=X3XC9wiBU+wDSbHjzrj-JrkJTqtO3v4cSw@mail.gmail.com>
Message-ID: <CACL_3VEykmViHpT=X3XC9wiBU+wDSbHjzrj-JrkJTqtO3v4cSw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Pobox-Relay-ID: 9A2815AC-F6C9-11E6-8C68-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FVA5zEhpoq1GFozEufx9RZQAN5U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 17:34:05 -0000

On 2017-02-18 Brian E Carpenter wrote:
> On 18/02/2017 07:00, Stewart Bryant wrote:
> > Ole
> >
> > Are you saying:
> >
> > A correct implementation of RFC2460 MUST NOT insert an EH at any point
> > along the path other than at the packet source.
> >
> Or
> >
> > A correct implementation of RFC2460 MAY insert an EH at any point along
> > the path.
>
> Ole doesn't, apparently, want to say either of those things.
>
> I want to say the first *as part of the promotion to Internet Standard*
> because it was the clear and documented intent of the authors and WG
> of RFC 1883, which became RFC 2460. (Documented in the ancient email I du=
g
> out a while back.) And it has been assumed by subsequent work such
> as PMTUD and IPsec/AH.

For the benefit of those who find it inconvenient to dig into the 6man WG
email archives, I've pasted the relevant part of that ancient email below.
See https://mailarchive.ietf.org/arch/msg/ipv6/poEU0yz7m2qpx3EACsszktrOlpk
for the full text of Brian's message.

-------- Forwarded Message --------
Subject: (IPng 609) changes to Last Call'ed specs
Date: Sun, 27 Aug 1995 20:59:26 PDT
From: Steve Deering <deering@parc.xerox.com>
To: ipng@sunroof.eng.sun.com
CC: deering@parc.xerox.com

At the request of our ADs, I prepared the following list of agreed-upon
changes and outstanding issues with the set of specs that underwent
IETF-wide Last Call in June and July.  Please let me know of any errors
or omissions.

Steve
[ =E2=80=A6 ]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
The following suggestions in Charlie Lynn's formal response to the Last Cal=
l
were rejected at the Stockholm meeting:

  - Add a bit to the Routing Header indicating whether or not it was
    inserted into the packet en-route, i.e., by a node other than the
    packet's originator.

      reasons for rejection: insertion of extension headers en-route breaks
      PMTU-discovery and can result in ICMP error messages being sent to
      non-guilty parties.  The desired effect can be achieved, and those
      problems avoided, by using en-route encapsulation (with optional
      Routing Header) rather than header insertion.
[ =E2=80=A6 ]


From nobody Sun Feb 19 13:48:22 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A419129583; Sun, 19 Feb 2017 13:48:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJoqHFadRcMS; Sun, 19 Feb 2017 13:48:15 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 4C1A2129588; Sun, 19 Feb 2017 13:48:15 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 016CA49; Sun, 19 Feb 2017 22:48:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= references:message-id:content-transfer-encoding:date:date :in-reply-to:x-mailer:from:from:subject:subject:mime-version :content-type:content-type:received:received; s=mail; t= 1487540890; bh=ItBSaxfSfVf0V6QNF3tKmFPppPgfON7KfvhjaWdtCmA=; b=F f1zhbbzZajoM7K0U9+WFTx5bAy1SIBxVafuXNgvQ0tqcqhC7qq7LnBUNwYX3ygRJ ElSi/mdbzWTRW869w67VNLoAM4SJxX+43MZ9K7NEhLIhfkdtDlpCxrUaaDgPKU9u Og8+cZdiMUsy9a88ZlpSfZxoUC1R1zaKH91qButOVE=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dxuzO2FdqJuQ; Sun, 19 Feb 2017 22:48:10 +0100 (CET)
Received: from [100.69.60.127] (unknown [188.206.77.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 652BB48; Sun, 19 Feb 2017 22:48:10 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <567281BF-DD55-4E46-9977-4575561A83C9@steffann.nl>
Date: Sun, 19 Feb 2017 22:48:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F4868F7E-C970-4342-8A89-8087B9D33911@steffann.nl>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com> <567281BF-DD55-4E46-9977-4575561A83C9@steffann.nl>
To: james woodyatt <jhw@google.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5j22OzlMEDkpssf0kQlQSBUwAnU>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 21:48:17 -0000

Hi,

Sorry, replying to myself. An off-list discussion made me realise I made an e=
rror.

>>> IPv6 unicast routing is based on prefixes of any valid length up to 128 b=
its [BCP198]. However, in accordance with the reasoning explained in [RFC742=
1], the Interface ID part of host interface addresses is generally 64 bits, w=
ith exceptions only provided in special cases expressly recognized in IETF s=
tandards track documents.
>=20
> Sounds good to me. It's clear on routing, it's clear on IIDs being 64 bits=
 long except in special standards-track cases without trying to enumerate th=
em and it provides an informational reference to explain why it should be 64=
 bits.

I have to clarify this a little bit. When reading it I was focusing on the "=
is generally 64 bits" part. In hindsight the exceptions clause is too strict=
 though. See below for the rest.

>> For my personal part, I=E2=80=99d prefer to see a clear statement here us=
ing RFC 2119 requirements language keywords, but I recognize that consensus p=
robably requires compromise on that point. Hence, the proposed refinement ab=
ove, which does not use RFC 2119 keywords. (Here is how I would write this w=
ith keywords: =E2=80=9CIPv6 unicast routing is based on network prefixes tha=
t MAY have any valid length up to 128 bits [BCP198]. However, in accordance w=
ith the reasoning explained in [RFC7421], the Interface ID part of host inte=
rface addresses SHOULD be 64 bits with exceptions only provided in special c=
ases expressly recognized in IETF standards track documents.=E2=80=9D)
>=20
> I'm a bit worried that the "MAY have any valid length up to 128 bits" defi=
nition is too loose when read by router vendors, but otherwise that version s=
ounds good as well. I like to see explicit clear guidance in standards docum=
ents.

I like the SHOULD. It allows for exceptions. Such special case are recognise=
d by the IETF and documents in standards track. Still good. There should be a=
 clear guidelines to network operators. I have seen too many beginners mess u=
p their addressing plans because they think they know better.

But on the other hand the text above limits exceptions to ONLY the IETF stan=
dards track, and that is too strong. Operators who know what they are doing m=
ust not be limited.

When writing my previous email I was focusing on giving guidance to operator=
s, and thinking about inexperienced operators. When I saw that exceptions we=
re taken into account I thought that that was good, but in hindsight the exc=
eptions as written are too limited.

So to summarise I think we need to state that in general the IID SHOULD be 6=
4 bits, exceptions MAY be defined, preferably in IETF standards track docume=
nts, equipment MUST allow operators to use any prefix length up to 128, and r=
outing MUST support those prefix lengths.

Sorry if my series of messages were confusing. I'm trying to strike a balanc=
e between giving good guidance while allowing well-informed deviations, maki=
ng sure that the text doesn't unnecessarily limit network operators while al=
so protecting users so that ISPs don't start delegating them /96s "because i=
t's more than enough and the RFC allows it" etc. (if you think that last arg=
ument is farfetched, sorry, I've seen too many ISPs start from there and onl=
y make a more reasonable addressing plan because the "/64 is the standard", s=
o we shouldn't be too loose about that)

When reading the different arguments on this list I often find myself agreei=
ng to most of them, even the conflicting ones, because I understand where th=
e different viewpoints are coming from. And they are all important. It's dif=
ficult enough to try to fit everything together in my head, and I hope that t=
his time I did a better job of writing it down in this email :)

Cheers,
Sander



From nobody Sun Feb 19 13:51:07 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A37E512958D for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 13:51:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.202
X-Spam-Level: 
X-Spam-Status: No, score=-2.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mcZJEdfqFmqw for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 13:51:04 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp1.pobox.com [64.147.108.70]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A961B12955B for <ietf@ietf.org>; Sun, 19 Feb 2017 13:51:04 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 9365E6A6FE for <ietf@ietf.org>; Sun, 19 Feb 2017 16:51:03 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; s=sasl; bh=BnUGVg2kv/MxTSu/T3A7BrOJRKo=; b=DcWGlm +MiWV2hrb5IH33YRNi/axJLqNcBsJHXEPXs6pbfruPGiMtNIWVzX+RNhvdIh18vU 9cztjUJX/Z0/VXw9sOKYm+IvxJNQkDT7Sw85ax27sM2ImNOd5zV6ochCUxKmhQzQ nfuLfCLrtqlcmo7algtYW+o6+gNEDbBkKAqmg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :in-reply-to:references:from:date:message-id:subject:to:cc :content-type; q=dns; s=sasl; b=CkZDow/1ICy/ZCy3xOoZfIpZ3dwMf9iY NKibtLXb+o7iAcrIRVEc4fjGayzlZ9FUUp89i6/r2ZjnvRyrzWr60ZFYDdkdc2Ir Y7WnDAx1k1uXBpqYjyI36LXIYZOpEn9TGjkDe/POqGmXFu6w6felfkibRa/Kuxkj pHAf4K5pfgM=
Received: from pb-smtp1.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp1.pobox.com (Postfix) with ESMTP id 835CB6A6FD for <ietf@ietf.org>; Sun, 19 Feb 2017 16:51:03 -0500 (EST)
Received: from mail-qk0-f182.google.com (unknown [209.85.220.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp1.pobox.com (Postfix) with ESMTPSA id CB91D6A6FC for <ietf@ietf.org>; Sun, 19 Feb 2017 16:51:02 -0500 (EST)
Received: by mail-qk0-f182.google.com with SMTP id s186so81890691qkb.1 for <ietf@ietf.org>; Sun, 19 Feb 2017 13:51:02 -0800 (PST)
X-Gm-Message-State: AMke39m+gPU21qPXaQPRy16WZ7+plWGSXxoeIMvSW9b/8dqfVwD79aCJR7QhGLogAxiFY0eTWyqdqF6YEjTjgA==
X-Received: by 10.55.119.1 with SMTP id s1mr18939918qkc.81.1487541062439; Sun, 19 Feb 2017 13:51:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sun, 19 Feb 2017 13:50:42 -0800 (PST)
In-Reply-To: <CACL_3VEykmViHpT=X3XC9wiBU+wDSbHjzrj-JrkJTqtO3v4cSw@mail.gmail.com>
References: <CACL_3VEykmViHpT=X3XC9wiBU+wDSbHjzrj-JrkJTqtO3v4cSw@mail.gmail.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 19 Feb 2017 13:50:42 -0800
X-Gmail-Original-Message-ID: <CACL_3VEKRD+2sFchdfoPWLcXi1m=oiFCb=mtO4arqOPgP5cM9A@mail.gmail.com>
Message-ID: <CACL_3VEKRD+2sFchdfoPWLcXi1m=oiFCb=mtO4arqOPgP5cM9A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: 81E76C4E-F6ED-11E6-BCE3-FE3F13518317-06080547!pb-smtp1.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9XUsxR_jRIoJUJnC7icEgzxN0lU>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 21:51:05 -0000

On 2017-02-18 Philip Homburg wrote:
> So the only purpose of a stronger text against inserting extension headers
> would be to prevent IETF working groups from publishing RFCs that use
> that technique.

That is not the only purpose -- some of us, at least, would like to believe
that stronger text will help to discourage practices that can have
demonstrably harmful effects -- but it is definitely an important purpose.

> Then the question becomes, why would we need to pre-emptively constrain
> ourselves?

To prevent IETF working groups from publishing RFCs that are inconsistent
with  existing standards track specifications and cause them not to work, or
more precisely, to prevent them from doing so without proper consideration
of negative side effects and how to deal with them (which may include
explicitly updating or obsoleting existing specifications).

//cmh


From nobody Sun Feb 19 14:36:28 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7FF312941A for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 14:36:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ScrtnbCeYInD for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 14:36:25 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (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 9BBAD1293E0 for <ietf@ietf.org>; Sun, 19 Feb 2017 14:36:25 -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)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id AC7F334930F; Sun, 19 Feb 2017 22:36:21 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 96B0016003F; Sun, 19 Feb 2017 22:36:21 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 73A46160047; Sun, 19 Feb 2017 22:36: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 61eXAYhF9lMc; Sun, 19 Feb 2017 22:36:21 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id DA98E16003F; Sun, 19 Feb 2017 22:36:20 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 8E4E46427E17; Mon, 20 Feb 2017 09:36:27 +1100 (EST)
To: Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
From: Mark Andrews <marka@isc.org>
References: <m1cf4bw-0000FfC@stereo.hq.phicoh.net>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard 
In-reply-to: Your message of "Sat, 18 Feb 2017 13:59:35 +0100." <m1cf4bw-0000FfC@stereo.hq.phicoh.net>
Date: Mon, 20 Feb 2017 09:36:27 +1100
Message-Id: <20170219223627.8E4E46427E17@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xxLoqK70LjIo13f54TXO31xRCwE>
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 22:36:27 -0000

In message <m1cf4bw-0000FfC@stereo.hq.phicoh.net>, Philip Homburg writes:
> >> Are you saying:
> >> 
> >> A correct implementation of RFC2460 MUST NOT insert an EH at any point 
> >> along the path other than at the packet source.
> >> 
> >> Or
> >> 
> >> A correct implementation of RFC2460 MAY insert an EH at any point along 
> >> the path.
> >
> >Ole doesn't, apparently, want to say either of those things.
> >
> >I want to say the first *as part of the promotion to Internet Standard*
> >because it was the clear and documented intent of the authors and WG
> >of RFC 1883, which became RFC 2460. (Documented in the ancient email I dug
> >out a while back.) And it has been assumed by subsequent work such
> >as PMTUD and IPsec/AH.
> >
> >If we want to *change* it, that's a separate discussion from promoting
> >the current standard. We can do it afterwards.
> >
> >(And in answer to some other comments, I'll note that RFC 791 does not
> >forbid NAT, but I bet the authors would have done so if they'd thought
> >of it. When did forbidding something in an RFC ever prevent people from
> >implementing it in a limited domain?)
> 
> I agree.
> 
> Personally, I wish we could allow routers to insert fragmentation headers.
> There is some crazy interaction between DNS and fragmentation that doesn't
> happen in IPv4.

With IPv4 DF is 0 unless you are running a out of RFC compliance
stack (Yes I'm talking about Linux) so fragmentation is done when
required. Add to that very few paths that actually require PMTUD
even with DF=1 you don't see issues.  As IPv4 as a service becomes
more common you will start to see more issues.

For IPv6 you have to play games with DNS.  We tried just fragmenting
at 1280 but the idiots with firewalls that drop all fragments made
that not viable.  At the moment named is forcing fragmentation at
1280 on DNS/UDP message sizes > 1432 (IPv6 in IPv4 + UDP header).
This removes most of the PMTUD issues without getting DNS/UDP
messages between 1252 and 1432 bytes dropped just because they were
fragmented.

> But in any case, a stronger text doesn't have much impact on parties outside
> the IETF. If, as a random example, I came to the conclusion that I can
> reduce PMTU problems by having one of my routers fragment IPv6 packets, then
> that may violate the spec, but it is possible that the gains are worth it.
> 
> So the only purpose of a stronger text against inserting extension headers
> would be to prevent IETF working groups from publishing RFCs that use
> that technique. 
> 
> Then the question becomes, why would we need to pre-emptively constrain
> ourselves? 
> 
> If we expect that there is some real world use case where insering
> extension headers along the way brings a lot of benefit, then it is much
> better to prepare for that situation then writing text to disallow it.
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sun Feb 19 15:15:09 2017
Return-Path: <heard@pobox.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4125E128B44; Sun, 19 Feb 2017 15:15:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 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_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=heard@pobox.com header.d=pobox.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96TXHBaLS1Kx; Sun, 19 Feb 2017 15:15:06 -0800 (PST)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6309120725; Sun, 19 Feb 2017 15:15:06 -0800 (PST)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 6852368F72; Sun, 19 Feb 2017 18:15:05 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=mime-version :from:date:message-id:subject:to:content-type; s=sasl; bh=WZNtPe Mk19atnmzU+i4degN1Nqg=; b=S90Hhm5kNEzcUesL3Aehp2/ODLViZMEJzmL6jT fpke35eNsSWIwGxqEGuIs3hJVc+9J2dsq3kctThmTLPPEW3aLj0qmfyAMk53i2zF AAN0qWO8iYgZGllvx+DmONhuVV2XqHe5nIr3ox4XIAkwl30Vd0jRNlEgcs8gSr3w VS67w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=mime-version :from:date:message-id:subject:to:content-type; q=dns; s=sasl; b= v5hbMIGT++i5uubapdpHY/xIer7JuVYY/fQMwQITa6SXYjDmFtbORqK7Wmz7aZD7 Tr7zQCZuICbD/0Kk0U61We1NToHeX6jnyn5uSwMIfHthl9mDjjdgfjSjiGZr5feK g/+kOXqzZdqRTcLYaPKa/Q7N2PJujQptvDw+AaRBs1g=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 5FC1568F70; Sun, 19 Feb 2017 18:15:05 -0500 (EST)
Received: from mail-qk0-f176.google.com (unknown [209.85.220.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 1DA4068F6D; Sun, 19 Feb 2017 18:15:02 -0500 (EST)
Received: by mail-qk0-f176.google.com with SMTP id x71so16658627qkb.3; Sun, 19 Feb 2017 15:15:02 -0800 (PST)
X-Gm-Message-State: AMke39m8Mwn1RsqdxG+S98nzBsNfMQYw5QukHPxRgl+MbnZJ/4tuBY8mGCPncVM4mhv6fFR41Qkog7LAqqyiIg==
X-Received: by 10.55.153.130 with SMTP id b124mr13627704qke.82.1487546101252;  Sun, 19 Feb 2017 15:15:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.18.106 with HTTP; Sun, 19 Feb 2017 15:14:40 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
Date: Sun, 19 Feb 2017 15:14:40 -0800
X-Gmail-Original-Message-ID: <CACL_3VHC3sx5=E4uk3+6-LR-JqXXMwF4cmMuJH-goipBUDX7fw@mail.gmail.com>
Message-ID: <CACL_3VHC3sx5=E4uk3+6-LR-JqXXMwF4cmMuJH-goipBUDX7fw@mail.gmail.com>
Subject: Possible ambiguity of Hop-by-Hop Options header processing text in draft-ietf-6man-rfc2460bis-08
To: IETF <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset=UTF-8
X-Pobox-Relay-ID: 3E35770A-F6F9-11E6-A9E7-A7617B1B28F4-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VKJWqpFe1LjKN067rk3R-x4fdkk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 23:15:08 -0000

Greetings,

While looking at something else, it occurred to me that there is a
possible ambiguity in the following text on Hop-by-Hop Options
header processing in draft-ietf-6man-rfc2460bis-08:

   The exception referred to in the preceding paragraph is the Hop-by-
   Hop Options header, which carries information that may be examined
   and processed by every node along a packet's delivery path, including
   the source and destination nodes.  The Hop-by-Hop Options header,
   when present, must immediately follow the IPv6 header.  Its presence
   is indicated by the value zero in the Next Header field of the IPv6
   header.

   NOTE: While [RFC2460] required that all nodes must examine and
   process the Hop-by-Hop Options header, it is now expected that nodes
   along a packet's delivery path only examine and process the Hop-by-
   Hop Options header if explicitly configured to do so.

The ambiguity: was the note intended to apply to every node along a
packet's delivery path, *including* the source and destination nodes?
Or was it intended to apply *only* to intermediate nodes?  It seemed
clear to me from the discussions in 6man that the issues that motivated
the note applied to forwarding nodes, not to end nodes, which are
expected to process every extension header present in a packet,
discarding it if they cannot do so.  It would seem odd not to expect
the HBH Options header to be processed given that we expect all other
headers to be processed, including the Destination Options header.

On that basis I would like to suggest changing the note as follows:

   NOTE: While [RFC2460] required that all nodes must examine and
   process the Hop-by-Hop Options header, it is now expected that nodes
   along a packet's delivery path, other than the source and destination
   nodes, will examine and process the Hop-by-Hop Options header only if
   explicitly configured to do so.

Apologies for not catching this during the WG discussion.

Regards,

Mike Heard


From nobody Sun Feb 19 15:49:50 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6DFD129542 for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 15:49:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 wAvPdXSvvHzs for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 15:49:46 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C7BE120725 for <ietf@ietf.org>; Sun, 19 Feb 2017 15:49:46 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cfbEZ-000E32-Gr; Sun, 19 Feb 2017 18:49:39 -0500
Date: Sun, 19 Feb 2017 18:49:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, Ted Lemon <mellon@fugue.com>, ietf@ietf.org
Subject: Re: Why do we have working group charters (was: To "lose the  argument in the WG")
Message-ID: <558153DF1D57D2059971A162@JcK-HP5.jck.com>
In-Reply-To: <6.2.5.6.2.20170218205437.09c36548@elandnews.com>
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB> <6.2.5.6.2.20170218152825.0c4d7d68@elandnews.com> <EF9DE86E-C964-4E92-BA48-B1555786C19B@fugue.com> <D8B7C051-53A1-4EEC-A639-88767C5B3BC4@fugue.com> <6.2.5.6.2.20170218205437.09c36548@elandnews.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SpE3qFlQoW8e2NQBQgDgRw3TqS4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 19 Feb 2017 23:49:48 -0000

SM,

--On Saturday, February 18, 2017 11:07 PM -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

>> Yes, as long as you remember that they are supposed to be
>> representing the will of the community and accountable to it.
>> Neither WG Chairs nor ADs have any other source of authority.
>> The difficulty with your statement above is that it can be
>> read to imply that there are no constraints one, or appeals
>> from, the decisions.  That is not true or, more specifically,
>> if one wants a healthy IETF that produces credible work, it
>> better not be.
> 
> It is possible to appeal the decision of the WG Chair, and if
> that fails, to file an appeal with the Responsible AD.  There
> is still an option to file an appeal if the issue is noticed
> later in the process.

I think we are in danger of having two separate conversations
here and not quite realizing it.  I think Ted and I have been
discussing what happens, or could happen, in practice.  Your
response has been to tell us what the procedures are and allow.
I've confident that I understand those procedures and almost as
confident that Ted does too.  It is probably helpful to remind
us, but let's not get them confused with what happens in reality
(the difference between the procedures and reality may also be a
useful conversation but it is, again, a different one).

The most extreme example of the difference is, of course, that
the written procedures specify a remedy for an AD who has gone
off in the weeds, seriously underformed, or otherwise lost the
confidence of the community in the form of a recall procedure.
That procedure has never been used up to the point that a recall
committee is appointed, much less beyond that point.  One could
infer from that that we've never had a serious problem with an
AD.  I don't think that is true, YMMD.  One could also infer
that informal discussions and interactions, including
encouraging people to resign rather than face the actual recall
procedure, have worked well, making that actual procedure
unnecessary, but the procedures do not call for those actions.

In the charter case, unless someone is following the work of a
WG very closely (for which see the "I don't have time"
discussion that spawned this thread), the first warning that the
WG has produced work that drifted away from the charter involves
a document showing up for IETF Last Call.  That poses a very
difficult problem for the AD for two reasons.  First,
inconsistency between a draft document and charter provisions
can be the result of differing interpretations of the charter or
a discovery that completing the chartered work required some
excursions into directions not anticipated when the charter was
written.  Deviations from the charter are rarely a
black-and-white matter: what is more typical is "some" or "a
bit" and a judgment call as whether or not the issue is actually
significant. In principle, we probably all agree that it would
be best to revise the charter as soon as such situations are
discovered.  In practice, there are lots of reasons why that
often doesn't happen, many of them rather good reasons.   If the
deviations are significant, one of the not-so-good reasons is
the it requires ADs to admit that they let the WG get out of
control.

And, yes, a decision to not put the document on hold while the
charter is revised can be appealed.  But holding work up,
especially work that appears to be finished, is a big deal and
there is, appropriately, a lot of reluctance to do that.  So the
appeals don't happen and, when they do, they often don't go
anywhere.

> There are constraints.  At the WG level, the WG Chair is
> accountable to the Area Director.  A competent Area Director
> would probably ask for an explanation if the document exceeds
> the scope of the WG Charter.

Again, "exceeds" is a judgment call.  Asking is one thing,
getting a useful answer is another.  And telling a WG that
thinks it has finished a document and may be waiting to close
down that they have to start fussing with charter revisions
and/or completely redesign the specification is very hard and
not always a good idea.

best,
   john


From nobody Sun Feb 19 17:14:03 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECC80129457 for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 17:13:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZQ1f0Zl_lcP1 for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 17:13:57 -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 BD836129603 for <ietf@ietf.org>; Sun, 19 Feb 2017 17:13:55 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id t8so54176664vke.3 for <ietf@ietf.org>; Sun, 19 Feb 2017 17:13:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=OyMeamIKrV/Xss1qvVXFpV3uiDax6e1EwinxQlXBe3U=; b=gNxIPnlArvyCCrEZW9v5/rsP0vpJcokAchAIHxCkQP1uIRgksYy4JQpv3+6fW6Cyaq Kh1/JEpXnbrbTfMQcViO/G1strYWyZSu0a9H6cwMFSGXMVrMzuddJj/q/tn8K/FnCeNP A0IKXg9OuJfpIEWhFs/jQlMRSVUoGtdf3zwFlKZYGVE3dmva6Y3BQK/zI+OpPxjn+lrx Lj55duTlOf5yuEvPDuqNmPkYnmZOWYCoth50evzi5cnKW7DMe49hCuAq00suhtpuV5lh CV8cQV8O93sDPTDEZ87xm5sMBg+6B0axDgiqKl7e7p4D3Bl46Gbt0nGgNtztJTBz5749 fZPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=OyMeamIKrV/Xss1qvVXFpV3uiDax6e1EwinxQlXBe3U=; b=Xt1vH1oGbI9D7RoHovxfwCIxWMPAzSn8Znw0//L2Ol103X0DLElDxrvvn2Dg3jquSe QxL819q5EuEokGqxo6gBnRBfhgO7p4o9atsDk/ZnDff97rasVdFJGary4DuD50K+gNeA xP7oOrNrloZjwUhCM4O1uULzRZMKXNQrmvC7FQqLr1t45giuKDu52eGaaUZgUkLp4tH/ bEJnSrjzeYcKLq/6gZBrvlrOLPqljkhjNwQjgcI46rtp9q0IN4eVShqUETfJAVepdXBu 4Y7YjW4S/tsJ/zPNdh0JtI/ZRJFm/uoUPL2p2HsBJTlW9N6DsdLUz4EOQZ/h2V+n4h3X 7low==
X-Gm-Message-State: AMke39nuW4foFcHHUCFm+wK0m8onSlwp+8R1qFGdQIEXPrbrieYYw+C+TCHLSg2LL/BHt7grw0xvWytCWS7aiLCL
X-Received: by 10.31.248.193 with SMTP id w184mr9511580vkh.10.1487553234534; Sun, 19 Feb 2017 17:13:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Sun, 19 Feb 2017 17:13:33 -0800 (PST)
In-Reply-To: <CAN-Dau3gXG8O2Fx_rdBJD8cokKMDJFN7D_MDsmzORmpgDUfVPQ@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <CAN-Dau3gXG8O2Fx_rdBJD8cokKMDJFN7D_MDsmzORmpgDUfVPQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Feb 2017 10:13:33 +0900
Message-ID: <CAKD1Yr2bSc6yDmOh=mJ-Z3YvemNfUEbPKGzLs-MxP7RQzqBgZA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=94eb2c14bd2a2158cb0548ebfa11
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/guC6IYI90CKHvIAME3HZgz2ndao>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 01:13:58 -0000

--94eb2c14bd2a2158cb0548ebfa11
Content-Type: text/plain; charset=UTF-8

On Sat, Feb 18, 2017 at 2:32 AM, David Farmer <farmer@umn.edu> wrote:

> The proposed text appears to make the Interface-ID length an operational
>> choice.
>> How is that _not_ changing the 64 bit boundary?
>>
>
> This has always been an operational choice.  You are mis-interrupting the
> intent of the 64 bit boundary, you seem to be saying it intends to specify
> the IID length for every interface on the Internet. If that was the intent,
> then RA's would never have needed a prefix length, nor would you need to
> specify a prefix length when manually configuring an interface.  If this
> requirement intended to specify the IID length of every interface on the
> Internet, then the requirement would have been sufficient by itself, we
> would have been done at that point. However, the fact that RAs have prefix
> lengths, and we specify a prefix length when manually configuring an
> interface, belies the argument that this was not intended to be an
> operational choice from the beginning.
>
> So, for other than SLAAC, the 64 bit boundary has only ever been in
> operational guidance, there are serious consequences to not following the
> IETF's operational guidance in this regard, this is discussed in
> [RFC7421].  However, it is an operational choice to follow that guidance or
> not. Interpreting this requirement as ever taking away that operational
> choice, shows this as a false imperative.
>

The fact that (most) glonal unicast IIDs are 64 bits is not an operational
choice, it is defined by the standards. The reason that it is a parameter
in various parts of the protocol is *not* that it is an operational choice;
the reason is to leave open the protocol to a future change in the
standards and future address allocations where IIDs are not required to be
64 bits long.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Feb 18, 2017 at 2:32 AM, David Farmer <span dir=3D"ltr">&lt;<a href=3D"=
mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wrot=
e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">The proposed text appears to make the Interface-ID=
 length an operational choice.<br>
How is that _not_ changing the 64 bit boundary?<br></blockquote><div><br></=
div></span><div>This has always been an operational choice.=C2=A0 You are m=
is-interrupting the intent of the 64 bit boundary, you seem to be saying it=
 intends to specify the IID length for every interface on the Internet. If =
that was the intent, then RA&#39;s would never have needed a prefix length,=
 nor would you need to specify a prefix length when manually configuring an=
 interface.=C2=A0 If this requirement intended to specify the IID length of=
 every interface on the Internet, then the requirement would have been suff=
icient by itself, we would have been done at that point. However, the fact =
that RAs have prefix lengths, and we specify a prefix length when manually =
configuring an interface, belies the argument that this was not intended to=
 be an operational choice from the beginning.</div><div>=C2=A0<br></div><di=
v>So, for other than SLAAC, the 64 bit boundary has only ever been in opera=
tional guidance, there are serious consequences to not following the IETF&#=
39;s operational guidance in this regard, this is discussed in [RFC7421].=
=C2=A0 However, it is an operational choice to follow that guidance or not.=
 Interpreting this requirement as ever taking away that operational choice,=
 shows this as a false imperative. =C2=A0=C2=A0</div></div></div></div></bl=
ockquote><div><br></div><div>The fact that (most) glonal unicast IIDs are 6=
4 bits is not an operational choice, it is defined by the standards. The re=
ason that it is a parameter in various parts of the protocol is *not* that =
it is an operational choice; the reason is to leave open the protocol to a =
future change in the standards and future address allocations where IIDs ar=
e not required to be 64 bits long.</div></div></div></div>

--94eb2c14bd2a2158cb0548ebfa11--


From nobody Sun Feb 19 17:22:19 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CB3C129401 for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 17:22:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yM5p_iV0hYuK for <ietf@ietfa.amsl.com>; Sun, 19 Feb 2017 17:22:13 -0800 (PST)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::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 ED01312960D for <ietf@ietf.org>; Sun, 19 Feb 2017 17:22:11 -0800 (PST)
Received: by mail-ua0-x236.google.com with SMTP id t17so48624552uae.3 for <ietf@ietf.org>; Sun, 19 Feb 2017 17:22:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gG+8YBMuc4d/vfzhm7YvpusTk7wRr+tSJLkvrunYeLA=; b=T/KVv1rV1wgRx0Fbowqelt65BrnNI/WDqsHv+CLDVsPAUG+iajVhh7qOzpHq3Y9pRD N/8EtbM9LihXSVjGFB8Z0SwkZ7QDH6wNSlCFGLTVE7iqGqBZKzQytMHBuqtNu0dO57Hr YG1lQ9JzA9QJRLpLqQCQbsY7m0I4i7cy5XQr0BjzAHREh8NIQdpVAtdzrBDMZV14V2K2 LOm2TfbYouff0shfXSRUeNG/sj5VQeSAMwOJQgaa6lasOtuiA2D+SNlqe2AK2fbu07tb hQhLXSRzddB5Kn7tOyC/48rcMuyYdJD34q8qiPo6xyggF5nT3KpIAQdnq3W7cd2c/04l c2Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gG+8YBMuc4d/vfzhm7YvpusTk7wRr+tSJLkvrunYeLA=; b=GBsqFpVCzq0Uu0+HexJwCvnl0tNL6LAcGc9h9dOZvDheqwISU1BaDCBycgIIrjOpT5 npxeF1P4FDqElk7zYiRefNm+g9mJCh4MEEWxlwfTBWrAMpb5QnT0ROKg0C4KB3HXnNVC paqIuj5J+Q65kgZhD79vilwfcD6zJDexAxSTHP0yfCfVM6KtECK7ySmaI+D/bQwELyzn 8uvnoUJHISpJVE0E3n020LVfpEq63H0Dcf41W4celEyAEdXkcnNmZm5Q4Zlc4mB+SoAQ WWT2yMn88MIWsTk7bSpxslOByjkZ65cvG6L9QtMoTcQA16Q9gmZa3HwJsp3+hzdD9ogH 53bA==
X-Gm-Message-State: AMke39lORsfV62gk6wryPAlnLiA1EI3MIWUG4INKn0VOBsyr4KEC9M9vFIZQw/RoIFimRZjxchGygRQLD0aK6mrv
X-Received: by 10.176.8.19 with SMTP id a19mr8780674uaf.30.1487553730849; Sun, 19 Feb 2017 17:22:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Sun, 19 Feb 2017 17:21:49 -0800 (PST)
In-Reply-To: <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 20 Feb 2017 10:21:49 +0900
Message-ID: <CAKD1Yr0m1mP4gmGF12NVLDyoo0+QFSRUmetjnPWbv5dU5nEtsg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: james woodyatt <jhw@google.com>
Content-Type: multipart/alternative; boundary=f403045f84a6b6932f0548ec17a4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tms9iWp_3psG0pObRvaYn0g5VAE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 01:22:14 -0000

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

On Sat, Feb 18, 2017 at 5:20 AM, james woodyatt <jhw@google.com> wrote:

> In response to various comments to this message, I=E2=80=99d like to prop=
ose a
> refinement:
>
> IPv6 unicast routing is based on prefixes of any valid length up to 128
> bits [BCP198]. However, in accordance with the reasoning explained in
> [RFC7421],
>
> Do you think it makes sense to cite RFC 7934 as well? There is text in
there that also justifies the 64 bit boundary.

> the Interface ID part of host interface addresses is generally 64 bits,
>
> Note that this is also a change to the standard, because the previous
standard explicitly excluded global addresses starting with binary 000.

> with exceptions only provided in special cases expressly recognized in
> IETF standards track documents.
>
> Can we require that said documents formally update this document?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Feb 18, 2017 at 5:20 AM, james woodyatt <span dir=3D"ltr">&lt;<a href=
=3D"mailto:jhw@google.com" target=3D"_blank">jhw@google.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"w=
ord-wrap:break-word"><div>In response to various comments to this message, =
I=E2=80=99d like to propose a refinement:</div><div><br></div><div><blockqu=
ote type=3D"cite">IPv6 unicast routing is based on prefixes of any valid le=
ngth up to 128 bits [BCP198]. However, in accordance with the reasoning exp=
lained in [RFC7421],</blockquote></div></div></blockquote><div>Do you think=
 it makes sense to cite RFC 7934 as well? There is text in there that also =
justifies the 64 bit boundary.</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div style=3D"word-wrap:break-word"><div><blockquote type=3D"cit=
e">the Interface ID part of host interface addresses is generally 64 bits,<=
/blockquote></div></div></blockquote><div>Note that this is also a change t=
o the standard, because the previous standard explicitly excluded global ad=
dresses starting with binary 000.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div style=3D"word-wrap:break-word"><div><blockquote type=3D"=
cite"> with exceptions only provided in special cases expressly recognized =
in IETF standards track documents.</blockquote></div></div></blockquote><di=
v>Can we require that said documents formally update this document?</div></=
div></div></div>

--f403045f84a6b6932f0548ec17a4--


From nobody Mon Feb 20 00:31:02 2017
Return-Path: <dannyniu@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55EC9129998 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 00:31:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yB4wvbGHojc8 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 00:30:59 -0800 (PST)
Received: from COL004-OMC4S1.hotmail.com (col004-omc4s1.hotmail.com [65.55.34.203]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD7F01298A5 for <ietf@ietf.org>; Mon, 20 Feb 2017 00:30:59 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com ([65.55.34.200]) by COL004-OMC4S1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 20 Feb 2017 00:30:59 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=G/PsliJ4ljplE7vYCRSNTYDQBdKHsrae87uf6PG9MeM=; b=M8frcgkSbySoB7OTfHllVjM/P232e0HtSHV0MLm8uZn0Sfqk3BU4sd2CuEvDxFevlW2PVZcdQJUYP38o7lHNwtOW62SHMMmuRoNmRaCul6JmqYHTYBUjHYv+h9EAXYsFEutMxmkul/WCZMSvZBgZ3j8VxwVpJgb1vbPZ4aHN7Cw87moWiNmkJ32Y8HxaF18C2BMwHKFAj5veInmCR42/t/hIp0HGdYhkr1q9zqXKuB30liHt1mh4pyOo1vpx19DZKs13HSnnL71NQz/GN68Ze/wwyL80dxz0Q8hm684JAEEnqfd3gfg+46Mt3DmRbNygVaKU7RGnTpvQWRyYvrmAyA==
Received: from PU1APC01FT115.eop-APC01.prod.protection.outlook.com (10.152.252.58) by PU1APC01HT008.eop-APC01.prod.protection.outlook.com (10.152.252.211) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16; Mon, 20 Feb 2017 08:30:46 +0000
Received: from SG2PR06MB0710.apcprd06.prod.outlook.com (10.152.252.54) by PU1APC01FT115.mail.protection.outlook.com (10.152.252.208) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16 via Frontend Transport; Mon, 20 Feb 2017 08:30:45 +0000
Received: from SG2PR06MB0710.apcprd06.prod.outlook.com ([10.162.197.144]) by SG2PR06MB0710.apcprd06.prod.outlook.com ([10.162.197.144]) with mapi id 15.01.0888.035; Mon, 20 Feb 2017 08:30:45 +0000
From: Danny Niu <dannyniu@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Purpose of Port 0. 
Thread-Topic: Purpose of Port 0. 
Thread-Index: AQHSi1DxuO1ub++PNkO0Iy9S1VhCGQ==
Date: Mon, 20 Feb 2017 08:30:45 +0000
Message-ID: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:6576CCD788312B64989F87781514AA46C572D1CDE516EBFF23264070BE2CC2E1; UpperCasedChecksum:DA0839D4BBDF7777C954BF10F5D0AFDD5B180AEC4FA5C0997F6E0C2257C7A44E; SizeAsReceived:7555; Count:37
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [P//jLSCzmSRz6rLQae9tgpH29fZ9GGON]
x-incomingheadercount: 37
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; PU1APC01HT008; 5:VR7KIusxq866PThsESGK+KzHTBIpiorzzANBhjFJLr36cK4rUpD94LL+559s5EBLOQbm/PzcyPEM4LndFItRXmIzyi61r3mEa6macVd0YSzbXdDUaNhmndyuWydf0sV9xP2L/0+Cfufn99hGKW/3yEeyT3v2jcg5qGBjq77RxAU=; 24:PkLwUfYzV8y1SAKfW8CjuFHRN1qGEg69eGX6JQpLu71o97aYq+e8pnJXcrQpIVlrTF5rn1yPUo6RkK7XIUzQxXZOj/cAINiIE/tqRKrgS/0=; 7:mqhxuhwZY3BpOHPl940zVPlFwRcmCDI2TkRGiEFk+ioP8zn0d9O+KbnY3klPVH3yn8eCnjPFcd2/KclAdkTYwAzNqA3pXq2SHcyDyIuEtP9Ts7336v31PSK1hoCVLIc3pbHSQV0i4sveILfIEzXN82OIStqn1fN3Cy/dPEiBd8hIo2+omWJh2s3xH9/Gz/uJDpV8DOmMPHhTJALtXW/xw9Haz8DmyEnEo0IIEZsl2PCBsfzrnfcJuzPbtXXgLvGv72O+FSIUz0iDibTu7VpBRAv+AH1wHxYJPhQ6rLGJuJCIYBhXI/DVrViJRfvGqbv4
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:PU1APC01HT008; H:SG2PR06MB0710.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 1a7550dc-2e64-484d-1218-08d4596ac3ca
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506556)(5061507331)(1603103135)(1603101406)(1601125237)(1701031045); SRVR:PU1APC01HT008; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:PU1APC01HT008; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT008; 
x-forefront-prvs: 02243C58C6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2017 08:30:45.0881 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT008
X-OriginalArrivalTime: 20 Feb 2017 08:30:59.0326 (UTC) FILETIME=[A9BA21E0:01D28B53]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LbyPVSAPJ9VSzYkWJMD8-faDoL4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 08:31:01 -0000

Hi, all.=20

Recently on the POSIX mailing list, there's a discussion on the correct way=
 to bind to (or listen on) an ephemeral port. While I referenced the "UNIX =
Network Programming", we're not quite satisfied because even though it's co=
-written by someone involved in IETF, it's still JUST a textbook.=20

The canonical way to do this, according to some (from stackoverflow.com, an=
d other places), is to bind to port 0, which I assume had been reserved for=
 this purpose, but I haven't find anything to back this up yet.=20

On the POSIX list, they suggested that IETF should, (or should have already=
) state(d) that port 0 be reserved for binding to ephemeral ports. So can w=
e find any reference for this? Or should we draft an RFC?=20

Thanks. =


From nobody Mon Feb 20 00:53:54 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DC16129605 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 00:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 7DWkDuesHtiJ for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 00:53:51 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CB1A128BA2 for <ietf@ietf.org>; Mon, 20 Feb 2017 00:53:51 -0800 (PST)
Received: from mb.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v1K8rm0Y092779 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 20 Feb 2017 08:53:49 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be mb.local
Subject: Re: Purpose of Port 0.
To: Danny Niu <dannyniu@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com>
Date: Mon, 20 Feb 2017 00:53:42 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xRTKTWDBeS36bCWE0DXILNwKBRDHT7CsK"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RG7lkqadmIwd8drfK8FZWj7K7uw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 08:53:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xRTKTWDBeS36bCWE0DXILNwKBRDHT7CsK
Content-Type: multipart/mixed; boundary="Sc4TNOMeOTtX2bLTH42P9lxQdkhQ9Mx2J";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Danny Niu <dannyniu@hotmail.com>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com>
Subject: Re: Purpose of Port 0.
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
In-Reply-To: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>

--Sc4TNOMeOTtX2bLTH42P9lxQdkhQ9Mx2J
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2/20/17 12:30 AM, Danny Niu wrote:
> Hi, all.
>=20
> Recently on the POSIX mailing list, there's a discussion on the
> correct way to bind to (or listen on) an ephemeral port. While I
> referenced the "UNIX Network Programming", we're not quite satisfied
> because even though it's co-written by someone involved in IETF, it's
> still JUST a textbook.
>=20
> The canonical way to do this, according to some (from
> stackoverflow.com, and other places), is to bind to port 0, which I
> assume had been reserved for this purpose, but I haven't find
> anything to back this up yet.
>=20
> On the POSIX list, they suggested that IETF should, (or should have
> already) state(d) that port 0 be reserved for binding to ephemeral
> ports. So can we find any reference for this? Or should we draft an
> RFC?

The original convention is from berkeley sockets api, so it's been that
way since 1983 or so. it would predate therefore ieee 1003 by some
years. I would. suspect that Postel et al were well aware that it was
employed by that convention when it was noted as reserved in rfc 1340/170=
0.

> Thanks.
>=20



--Sc4TNOMeOTtX2bLTH42P9lxQdkhQ9Mx2J--

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

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

iEYEARECAAYFAliqrpcACgkQ8AA1q7Z/VrLykACdHz4Mu6ncGDvogWkUI2MFu0V5
N2kAnRs25S5inUkq0BSyhlkXoaXACzGj
=flwH
-----END PGP SIGNATURE-----

--xRTKTWDBeS36bCWE0DXILNwKBRDHT7CsK--


From nobody Mon Feb 20 01:05:35 2017
Return-Path: <dannyniu@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C47A12706D for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 01:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hMIhKqyXQ8St for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 01:05:33 -0800 (PST)
Received: from COL004-OMC3S16.hotmail.com (col004-omc3s16.hotmail.com [65.55.34.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC435126D74 for <ietf@ietf.org>; Mon, 20 Feb 2017 01:05:32 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com ([65.55.34.137]) by COL004-OMC3S16.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 20 Feb 2017 01:05:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=VDGRf9orT1mzyyE6DCqm0DW3RDSz3UqOiKuW+n8LxYQ=; b=VhRHSWInRwaAeU1JqrMsng1OlCXDUUeGqHtMdxKx0fGNkS/NUOHMdNMn2JY/icALtHjbGcOA9lgmZOH+feBmxPBIgSIYD2XZGJPVIb0S06q9zyL4Rmdbnf+lbkX8ZLKHXjjU0jpg8ta7sDe3zpdnCtu+wgGA3XlscxVrYz33Z7lYIo53uwZmtMihcKJ3hFt+0Jet4ohPosdHJAULj6ttF2gHFDiEWk5OVgT8mKLQZS3NNlMMm9KuNETZI0ADS90ttzMeqrTrMyHxSmkLJds3FsRIq7jd1BMD8RCQzeoKZR0ZfVWd/FoTJuX2QqWDqppJi24Y4HK4C82Ze5Cfd9gHag==
Received: from PU1APC01FT049.eop-APC01.prod.protection.outlook.com (10.152.252.55) by PU1APC01HT003.eop-APC01.prod.protection.outlook.com (10.152.252.117) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16; Mon, 20 Feb 2017 09:05:30 +0000
Received: from SG2PR06MB0710.apcprd06.prod.outlook.com (10.152.252.51) by PU1APC01FT049.mail.protection.outlook.com (10.152.253.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16 via Frontend Transport; Mon, 20 Feb 2017 09:05:29 +0000
Received: from SG2PR06MB0710.apcprd06.prod.outlook.com ([10.162.197.144]) by SG2PR06MB0710.apcprd06.prod.outlook.com ([10.162.197.144]) with mapi id 15.01.0888.035; Mon, 20 Feb 2017 09:05:29 +0000
From: Danny Niu <dannyniu@hotmail.com>
To: joel jaeggli <joelja@bogus.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Purpose of Port 0.
Thread-Topic: Purpose of Port 0.
Thread-Index: AQHSi1DxuO1ub++PNkO0Iy9S1VhCGaFxlwoAgAABdcY=
Date: Mon, 20 Feb 2017 09:05:29 +0000
Message-ID: <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>, <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com>
In-Reply-To: <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: bogus.com; dkim=none (message not signed) header.d=none;bogus.com; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:C44A173A335FED9BA7C6BC1D74410363D515B904F81A48A78D26BF4CC32D57C2; UpperCasedChecksum:747BFC310C858C89B9E8079AD9BD533655141336C7F5B917241C1A245E8438F3; SizeAsReceived:7803; Count:39
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [qvBz+ER9O6xXwftupxIqEprlyjWm0VFS]
x-incomingheadercount: 39
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; PU1APC01HT003; 7:BOnwYVJRHGvVH2U7r7yJrLjNTmnDBiZE5uwqhasGQtwxsJx6FiqN/wOxPtogljbLqSSyUsIF1aSDjHnqH8HYAgy7Yq6R1OktrnS/zHf+GrRnXSkXwrrav9R5gq6YDqqaIbVSVUv9IwF5ZD8Wfa4d12TRXBAWWm0j2TUM0BimJnt58veTI0J3+XhjBaZGn5MIZkh64H0shlLxTRJLEpcXtyEYcuCM5PGX8qg8fz1nlOF7cYtXMmJW7lB8Qe7OxZAcCQWeERPfDOh+AfjoirFrabVuS5Fa1Qtk/4WMjxtR8nkdocFuLum7Au4brYxdF1RvaTxk1QBCbzU7Wsb/eCjAYg==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:PU1APC01HT003; H:SG2PR06MB0710.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 19efc3ca-3050-453b-e0c7-08d4596f9e15
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506556)(5061507331)(1603103135)(1601125237)(1603101373)(1701031045); SRVR:PU1APC01HT003; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:PU1APC01HT003; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT003; 
x-forefront-prvs: 02243C58C6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2017 09:05:29.3777 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT003
X-OriginalArrivalTime: 20 Feb 2017 09:05:32.0459 (UTC) FILETIME=[7D691FB0:01D28B58]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yYc8rSwr4bgIQWZUha9-YoesZvU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 09:05:34 -0000

Questions:=20
Is "Berkerly Sockets API"  defined seperately from the BSD manpages? Or is =
it just sections of the BSD manpages? What happened to "Berkerly Sockets AP=
I"?=20

Proposal:=20
Folks at POSIX are a bit unwilling to dis-certify some allegedly existing s=
ystems, and think it'd be better IETF note the purpose of port 0, so that e=
xisting app/sys woudn't break.=20
So is it too soon to start drafting?=20

________________________________________
From: joel jaeggli <joelja@bogus.com>
Sent: Monday, February 20, 2017 16:53
To: Danny Niu; ietf@ietf.org
Subject: Re: Purpose of Port 0.

On 2/20/17 12:30 AM, Danny Niu wrote:
> Hi, all.
>
> Recently on the POSIX mailing list, there's a discussion on the
> correct way to bind to (or listen on) an ephemeral port. While I
> referenced the "UNIX Network Programming", we're not quite satisfied
> because even though it's co-written by someone involved in IETF, it's
> still JUST a textbook.
>
> The canonical way to do this, according to some (from
> stackoverflow.com, and other places), is to bind to port 0, which I
> assume had been reserved for this purpose, but I haven't find
> anything to back this up yet.
>
> On the POSIX list, they suggested that IETF should, (or should have
> already) state(d) that port 0 be reserved for binding to ephemeral
> ports. So can we find any reference for this? Or should we draft an
> RFC?

The original convention is from berkeley sockets api, so it's been that
way since 1983 or so. it would predate therefore ieee 1003 by some
years. I would. suspect that Postel et al were well aware that it was
employed by that convention when it was noted as reserved in rfc 1340/1700.

> Thanks.
>



From nobody Mon Feb 20 03:07:30 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC6C11295D3 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 03:07:29 -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 autolearn_force=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 bf2mrTqvM6Xe for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 03:07:28 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (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 A8FAF128B38 for <ietf@ietf.org>; Mon, 20 Feb 2017 03:07:28 -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)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id 4D22D3493E0; Mon, 20 Feb 2017 11:07:26 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 3DE60160043; Mon, 20 Feb 2017 11:07:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 219C8160055; Mon, 20 Feb 2017 11:07:26 +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 BT8AZwcwxNda; Mon, 20 Feb 2017 11:07:26 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id A1268160043; Mon, 20 Feb 2017 11:07:25 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 5D144643B8DF; Mon, 20 Feb 2017 22:07:33 +1100 (EST)
To: Danny Niu <dannyniu@hotmail.com>
From: Mark Andrews <marka@isc.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>, <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
Subject: Re: Purpose of Port 0.
In-reply-to: Your message of "Mon, 20 Feb 2017 09:05:29 -0000." <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com>
Date: Mon, 20 Feb 2017 22:07:33 +1100
Message-Id: <20170220110733.5D144643B8DF@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZOiU7D8K1uOwPMMksMgOc73CcKU>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 11:07:29 -0000

In message <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.
outlook.com>, Danny Niu writes:
> Questions:
> Is "Berkerly Sockets API"  defined seperately from the BSD manpages? Or
> is it just sections of the BSD manpages? What happened to "Berkerly
> Sockets API"?
>
> Proposal:
> Folks at POSIX are a bit unwilling to dis-certify some allegedly existing
> systems, and think it'd be better IETF note the purpose of port 0, so
> that existing app/sys woudn't break.
> So is it too soon to start drafting?

Well UDP source port 0 means don't reply (RFC 768).   It's for uni
directional streams.

As for 0 to select a ephemeral port that is a BSD sockets convention.
That isn't something the IETF should specify.

Mark


> ________________________________________
> From: joel jaeggli <joelja@bogus.com>
> Sent: Monday, February 20, 2017 16:53
> To: Danny Niu; ietf@ietf.org
> Subject: Re: Purpose of Port 0.
> 
> On 2/20/17 12:30 AM, Danny Niu wrote:
> > Hi, all.
> >
> > Recently on the POSIX mailing list, there's a discussion on the
> > correct way to bind to (or listen on) an ephemeral port. While I
> > referenced the "UNIX Network Programming", we're not quite satisfied
> > because even though it's co-written by someone involved in IETF, it's
> > still JUST a textbook.
> >
> > The canonical way to do this, according to some (from
> > stackoverflow.com, and other places), is to bind to port 0, which I
> > assume had been reserved for this purpose, but I haven't find
> > anything to back this up yet.
> >
> > On the POSIX list, they suggested that IETF should, (or should have
> > already) state(d) that port 0 be reserved for binding to ephemeral
> > ports. So can we find any reference for this? Or should we draft an
> > RFC?
> 
> The original convention is from berkeley sockets api, so it's been that
> way since 1983 or so. it would predate therefore ieee 1003 by some
> years. I would. suspect that Postel et al were well aware that it was
> employed by that convention when it was noted as reserved in rfc 1340/1700.
> 
> > Thanks.
> >
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Mon Feb 20 03:49:58 2017
Return-Path: <lhotka@nic.cz>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7EEA1299B9; Mon, 20 Feb 2017 03:49:56 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "Ladislav Lhotka" <lhotka@nic.cz>
To: <yang-doctors@ietf.org>
Subject: Review of draft-ietf-rtgwg-yang-key-chain-13
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148759139687.25976.6374643432126541498.idtracker@ietfa.amsl.com>
Date: Mon, 20 Feb 2017 03:49:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i_7ZzUcnarblVugbdiT1nW9G7NA>
Cc: draft-ietf-rtgwg-yang-key-chain.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 11:49:57 -0000

Reviewer: Ladislav Lhotka
Review result: Almost Ready

# General Comments

## Cryptographic algorithm types

What is the reason for representing these as a YANG choice with empty
leaves? I think it would be more natural to use a single leaf, either
an enumeration or (if extensibility is important) identityref.

## Reusability

The module defines key-chain as a grouping with the aim of making it
reusable in other modules. However, this approach has known problems
that are discussed in draft-ietf-netmod-schema-mount. I am not sure
how relevant they are in this case but, for one, the "key-chain-ref"
type is not applicable if the "key-chain" grouping is used in another
module. An alternative is not to use the grouping and rely on schema
mount.

## Key string style

The difference between ASCII and hexadecimal formats of key strings
should be explained. I understand that the latter is a hash of the key
and, if so, I'd suggest to include "hexadecimal-string" also in state
data.

Also, I believe that storing clear-text key in configuration is
insecure and Security Considerations should warn against it.

## Example

It might be useful to include an appendix with example instance data.

# Specific comments
  
## Sec. 2

-   paragraph 2: s/where ever/wherever/

## Sec. 3

-   paragraph 1: replace both Key-Id a Key-ID with Key ID (the latter
is used in other places of the 
    text).
-   paragraph 2: the suggested way of supporting asymmetric keys looks
like a hack, I would suggest 
    a more explicit representation, e.g. using a choice.

## Sec. 4

-   The module has inconsistent indentation: up to "grouping
crypto-algorithm-types", top-level      
    statements are indented with four spaces, the subsequent ones with
five spaces.

## Sec. 6

-   The statement "Given that the key chains themselves are sensitive
data, it is RECOMMENDED    
    that the NETCONF communication channel be encrypted." is
misleading because RFC 6241 
    requires that transport protocols for NETCONF guarantee
confidentiality (and RFC 8040 does the 
    same for RESTCONF).



From nobody Mon Feb 20 04:34:11 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E0812946C for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 ToyJuumC7quu for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:34:09 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71CE1129462 for <ietf@ietf.org>; Mon, 20 Feb 2017 04:34:09 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cfnAJ-000HF6-Kg; Mon, 20 Feb 2017 07:34:03 -0500
Date: Mon, 20 Feb 2017 07:33:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <marka@isc.org>, Danny Niu <dannyniu@hotmail.com>
Subject: Re: Purpose of Port 0.
Message-ID: <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
In-Reply-To: <20170220110733.5D144643B8DF@rock.dv.isc.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> , <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m8zO7_e3V1_LLTSOWwvO8qtrnNQ>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:34:10 -0000

--On Monday, February 20, 2017 10:07 PM +1100 Mark Andrews
<marka@isc.org> wrote:

> 
> In message
> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06
> .prod. outlook.com>, Danny Niu writes:
>> Questions:
>> Is "Berkerly Sockets API"  defined seperately from the BSD
>> manpages? Or is it just sections of the BSD manpages? What
>> happened to "Berkerly Sockets API"?
>> 
>> Proposal:
>> Folks at POSIX are a bit unwilling to dis-certify some
>> allegedly existing systems, and think it'd be better IETF
>> note the purpose of port 0, so that existing app/sys woudn't
>> break.
>> So is it too soon to start drafting?
> 
> Well UDP source port 0 means don't reply (RFC 768).   It's for
> uni directional streams.
> 
> As for 0 to select a ephemeral port that is a BSD sockets
> convention. That isn't something the IETF should specify.

While _assignment_ of a por is an IETF matter and I mostly agree
with Mark, recognition of how one is being used is is a little
different.

It seems to me that this is rather more an IANA registry matter
than a standardization one and that, given practices today, it
would be reasonable to annotate the registry by adding "used
for" or "known to be used for" to "reserved".  

That should be mostly a housekeeping matter: could one of the
relevant ADs speak up and indicate whether they want an I-D, a
note (perhaps just this thread), a formal liaison request from
POSIX, or something else?

    john


From nobody Mon Feb 20 04:40:53 2017
Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A00451299C3 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:40:51 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RXMbb5VPQUMf for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:40:50 -0800 (PST)
Received: from statler.isode.com (Statler.isode.com [62.232.206.189]) by ietfa.amsl.com (Postfix) with ESMTP id A76D01299C2 for <ietf@ietf.org>; Mon, 20 Feb 2017 04:40:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1487594449; d=isode.com; s=june2016; i=@isode.com; bh=pu8v9s5eRyINFxzK+ewJTFkTPeJrs3SqLmngub1YwcQ=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=h39kBexxFtaoQhu8rS+ODzU4Sr62Re/gEhoaMDy8Y0SmVG6AYj0hQosRKayJ2oYn2OHYc4 vHxpDqosHnYco3WkbEHihjDRUjOcOslxJ+HVVQT+MKlbM/RsdicMfgWDw20BUzyO48n7RO B2XR6DpsqWPaFaxoFCbWnhJ2Wmygvmo=;
Received: from [172.20.1.215] (dhcp-215.isode.net [172.20.1.215])  by statler.isode.com (submission channel) via TCP with ESMTPSA  id <WKrj0AAY17Ev@statler.isode.com>; Mon, 20 Feb 2017 12:40:49 +0000
Subject: Re: Purpose of Port 0.
To: John C Klensin <john-ietf@jck.com>, Mark Andrews <marka@isc.org>, Danny Niu <dannyniu@hotmail.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
Message-ID: <c69c7d15-d601-756c-c0d0-ff16b68d0744@isode.com>
Date: Mon, 20 Feb 2017 12:40:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
In-Reply-To: <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qPmYgeYv7uyHnZcqHvEW8qRiljc>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:40:51 -0000

Hi John,

On 20/02/2017 12:33, John C Klensin wrote:
> --On Monday, February 20, 2017 10:07 PM +1100 Mark Andrews
> <marka@isc.org> wrote:
>
>> In message
>> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06
>> .prod. outlook.com>, Danny Niu writes:
>>> Questions:
>>> Is "Berkerly Sockets API"  defined seperately from the BSD
>>> manpages? Or is it just sections of the BSD manpages? What
>>> happened to "Berkerly Sockets API"?
>>>
>>> Proposal:
>>> Folks at POSIX are a bit unwilling to dis-certify some
>>> allegedly existing systems, and think it'd be better IETF
>>> note the purpose of port 0, so that existing app/sys woudn't
>>> break.
>>> So is it too soon to start drafting?
>> Well UDP source port 0 means don't reply (RFC 768).   It's for
>> uni directional streams.
>>
>> As for 0 to select a ephemeral port that is a BSD sockets
>> convention. That isn't something the IETF should specify.
> While _assignment_ of a por is an IETF matter and I mostly agree
> with Mark, recognition of how one is being used is is a little
> different.
>
> It seems to me that this is rather more an IANA registry matter
> than a standardization one and that, given practices today, it
> would be reasonable to annotate the registry by adding "used
> for" or "known to be used for" to "reserved".
Agreed.
> That should be mostly a housekeeping matter: could one of the
> relevant ADs speak up and indicate whether they want an I-D, a
> note (perhaps just this thread), a formal liaison request from
> POSIX, or something else?
I will ask IESG.


From nobody Mon Feb 20 04:46:32 2017
Return-Path: <dannyniu@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D92A1299C0 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:46:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0w3dv315WAPD for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:46:28 -0800 (PST)
Received: from COL004-OMC4S11.hotmail.com (col004-omc4s11.hotmail.com [65.55.34.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA2A0129434 for <ietf@ietf.org>; Mon, 20 Feb 2017 04:46:28 -0800 (PST)
Received: from APC01-PU1-obe.outbound.protection.outlook.com ([65.55.34.201]) by COL004-OMC4S11.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 20 Feb 2017 04:46:28 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=T46thVTINgfsDhR3J2IjY87xHH3DantQ5mlPns0rZGk=; b=nbCO/iza8ncwI0INJhjlFZG4XmThgt7B8eFjgOJBNzfHc7QtmAgX4GnQxhr86Ng/V32yody/73z6qQzjOoPDu4y0VqPBfDUu4hgvJXM9p3DDvyZb9ne51GHb6sx/py/ui6YelFM7y/T3vpjX6y5H9+lncGuv63IV+FYP31z24sN3qDhADnHgKzUA5qZ0uTK/bk25a0Jze1roYOHacOd76cT8zv5rshr+ZtYpZ2ZK/JRw2M8E00Nm4KHp3vMi7IpBJwTttkRrNxaLMoZYsYtdkOoBHWKbAnonOT0sVc5XMYqXAsrfb7twtEysDuMLc6ey0hYcqEX3v0lN2V3PRwnYYQ==
Received: from SG2APC01FT009.eop-APC01.prod.protection.outlook.com (10.152.250.53) by SG2APC01HT097.eop-APC01.prod.protection.outlook.com (10.152.251.200) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16; Mon, 20 Feb 2017 12:46:25 +0000
Received: from TY1PR06MB0718.apcprd06.prod.outlook.com (10.152.250.51) by SG2APC01FT009.mail.protection.outlook.com (10.152.250.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16 via Frontend Transport; Mon, 20 Feb 2017 12:46:25 +0000
Received: from TY1PR06MB0718.apcprd06.prod.outlook.com ([10.163.245.140]) by TY1PR06MB0718.apcprd06.prod.outlook.com ([10.163.245.140]) with mapi id 15.01.0919.015; Mon, 20 Feb 2017 12:46:25 +0000
From: Danny Niu <dannyniu@hotmail.com>
To: John C Klensin <john-ietf@jck.com>, Mark Andrews <marka@isc.org>
Subject: Re: Purpose of Port 0.
Thread-Topic: Purpose of Port 0.
Thread-Index: AQHSi1DxuO1ub++PNkO0Iy9S1VhCGaFxlwoAgAABdcaAACPyTYAAGCMAgAADIII=
Date: Mon, 20 Feb 2017 12:46:25 +0000
Message-ID: <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> , <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org>, <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
In-Reply-To: <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:D7EE975F70EFC92ED37483BE7E26301CFA24A763FF8430B0545654C5C0382164; UpperCasedChecksum:3DEE72B1FA3534A964667AAE2107A71F206E590E4BA0009D53218DE72EA4AB32; SizeAsReceived:8033; Count:40
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [RWmNU1qUwEJytgamQZCVbmD5a62vthdm]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; SG2APC01HT097; 7:ahB1t774Ta3Anj8RiB5MqWAGry19XJc0JfGN0BGvE3Sz6oNItaXWAlM4JuGXdaJP4vUI0asbSc8WlrkRHOE83C9Qpn7oi4rRmc2mN0YQ24FJDUI9uZW0F1ymCAcEDDzJzdJkgcuBSp1H8rCgt7Pdl3vT3s9To30bXIkNvVRkTEZzigO5FyrcXgF53y/suQs7nn5StvdIXCJxmXd2mIXEciX7nuhX0nZlWv0PtcxJ82VAV58EWeROwBBn3HmYu604HU847I6kYgr22ZztegOO3z53X7F9bGba2Fq5Z3R89jUu2Rg08hmyTbvuXHVCNRv9hOAIMZGyMwZbU+WQufy0Mg==
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:SG2APC01HT097; H:TY1PR06MB0718.apcprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: c6cef446-e14b-42e3-6285-08d4598e7b24
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506556)(5061507331)(1603103135)(1601125237)(1603101373)(1701031045); SRVR:SG2APC01HT097; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:SG2APC01HT097; BCL:0; PCL:0; RULEID:; SRVR:SG2APC01HT097; 
x-forefront-prvs: 02243C58C6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Feb 2017 12:46:25.0551 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT097
X-OriginalArrivalTime: 20 Feb 2017 12:46:28.0429 (UTC) FILETIME=[5A959FD0:01D28B77]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-48ek_mdRa10SvsZUTtziZTpxsQ>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:46:31 -0000

That's what I'd expected, thanks.=20

BTW, https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers did the=
 same,=20
except of the two references it cited, one is broken and one is not reliabl=
e enough.=20

________________________________________
From: John C Klensin <john-ietf@jck.com>
Sent: Monday, February 20, 2017 20:33
To: Mark Andrews; Danny Niu
Cc: ietf@ietf.org
Subject: Re: Purpose of Port 0.

--On Monday, February 20, 2017 10:07 PM +1100 Mark Andrews
<marka@isc.org> wrote:

>
> In message
> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06
> .prod. outlook.com>, Danny Niu writes:
>> Questions:
>> Is "Berkerly Sockets API"  defined seperately from the BSD
>> manpages? Or is it just sections of the BSD manpages? What
>> happened to "Berkerly Sockets API"?
>>
>> Proposal:
>> Folks at POSIX are a bit unwilling to dis-certify some
>> allegedly existing systems, and think it'd be better IETF
>> note the purpose of port 0, so that existing app/sys woudn't
>> break.
>> So is it too soon to start drafting?
>
> Well UDP source port 0 means don't reply (RFC 768).   It's for
> uni directional streams.
>
> As for 0 to select a ephemeral port that is a BSD sockets
> convention. That isn't something the IETF should specify.

While _assignment_ of a por is an IETF matter and I mostly agree
with Mark, recognition of how one is being used is is a little
different.

It seems to me that this is rather more an IANA registry matter
than a standardization one and that, given practices today, it
would be reasonable to annotate the registry by adding "used
for" or "known to be used for" to "reserved".

That should be mostly a housekeeping matter: could one of the
relevant ADs speak up and indicate whether they want an I-D, a
note (perhaps just this thread), a formal liaison request from
POSIX, or something else?

    john


From nobody Mon Feb 20 04:53:35 2017
Return-Path: <acee@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1946012947D; Mon, 20 Feb 2017 04:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level: 
X-Spam-Status: No, score=-14.523 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LYlj9QTuBxNn; Mon, 20 Feb 2017 04:53:28 -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 5E6A5129434; Mon, 20 Feb 2017 04:53:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2526; q=dns/txt; s=iport; t=1487595208; x=1488804808; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Oq0hHheM5PUHmVCUR4tfnud0Ti+JEvgE2uWPbGioGLs=; b=PpZCnobijN9McvK3VGFngCsy30iDK3E/w0DBpgTwj+c65jsN5XOnegcf pvo9HMQ1lMp27F6Nuxp86E1a51lDUX9ADaFNg+cZaCs1hMiyHmjXd+/Ni LDTiKs85/8tfnTrSW6ikRCuOZP2CZoxdBdBhVfIfEq5vCzVzwMOcgO6VA k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BwAQCU5qpY/4UNJK1eGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1FhgQkHjVynSIIMKoV4AoI4PxgBAgEBAQEBAQFiKIRxBnkQAgEIRjI?= =?us-ascii?q?lAgQBDQWJbw6vaotOAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWLO4o5BZAIi3wBk?= =?us-ascii?q?hyRCpMhAR84gQBTFT6ESR6BYXUBigOBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.35,186,1484006400"; d="scan'208";a="210648156"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Feb 2017 12:53:05 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v1KCr5ct015004 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 20 Feb 2017 12:53:05 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 20 Feb 2017 07:53:05 -0500
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 20 Feb 2017 07:53:05 -0500
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Ladislav Lhotka <lhotka@nic.cz>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Subject: Re: Review of draft-ietf-rtgwg-yang-key-chain-13
Thread-Topic: Review of draft-ietf-rtgwg-yang-key-chain-13
Thread-Index: AQHSi293pFk9o9mEqEaW7SaUvTwXFqFx2aOA
Date: Mon, 20 Feb 2017 12:53:04 +0000
Message-ID: <D4D04FCC.9CD7D%acee@cisco.com>
References: <148759139687.25976.6374643432126541498.idtracker@ietfa.amsl.com>
In-Reply-To: <148759139687.25976.6374643432126541498.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <DA05100CE288CB45A75960E847CE98A7@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nZMb-PRStkCNAr6JwN_CBANuP2s>
Cc: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:53:30 -0000

Hi Lada,=20
I believe we=B9ve addressed all of these other than adding an explicit leaf
for key direction (which was discussed on the RTGWG list). The current
version is https://www.ietf.org/id/draft-ietf-rtgwg-yang-key-chain-15.txt

Thanks,
Acee=20

On 2/20/17, 6:49 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:

>Reviewer: Ladislav Lhotka
>Review result: Almost Ready
>
># General Comments
>
>## Cryptographic algorithm types
>
>What is the reason for representing these as a YANG choice with empty
>leaves? I think it would be more natural to use a single leaf, either
>an enumeration or (if extensibility is important) identityref.
>
>## Reusability
>
>The module defines key-chain as a grouping with the aim of making it
>reusable in other modules. However, this approach has known problems
>that are discussed in draft-ietf-netmod-schema-mount. I am not sure
>how relevant they are in this case but, for one, the "key-chain-ref"
>type is not applicable if the "key-chain" grouping is used in another
>module. An alternative is not to use the grouping and rely on schema
>mount.
>
>## Key string style
>
>The difference between ASCII and hexadecimal formats of key strings
>should be explained. I understand that the latter is a hash of the key
>and, if so, I'd suggest to include "hexadecimal-string" also in state
>data.
>
>Also, I believe that storing clear-text key in configuration is
>insecure and Security Considerations should warn against it.
>
>## Example
>
>It might be useful to include an appendix with example instance data.
>
># Specific comments
> =20
>## Sec. 2
>
>-   paragraph 2: s/where ever/wherever/
>
>## Sec. 3
>
>-   paragraph 1: replace both Key-Id a Key-ID with Key ID (the latter
>is used in other places of the
>    text).
>-   paragraph 2: the suggested way of supporting asymmetric keys looks
>like a hack, I would suggest
>    a more explicit representation, e.g. using a choice.
>
>## Sec. 4
>
>-   The module has inconsistent indentation: up to "grouping
>crypto-algorithm-types", top-level
>    statements are indented with four spaces, the subsequent ones with
>five spaces.
>
>## Sec. 6
>
>-   The statement "Given that the key chains themselves are sensitive
>data, it is RECOMMENDED
>    that the NETCONF communication channel be encrypted." is
>misleading because RFC 6241
>    requires that transport protocols for NETCONF guarantee
>confidentiality (and RFC 8040 does the
>    same for RESTCONF).
>
>


From nobody Mon Feb 20 04:54:53 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1025B1298BD for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:54:52 -0800 (PST)
X-Quarantine-ID: <OuQAklV3-Y5T>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace: References: ...cprd06.prod.outlook.com>\n  \n <201702201107[...]
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 OuQAklV3-Y5T for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 04:54:51 -0800 (PST)
Received: from bsa3.jck.com (static-65-175-133-137.cpe.metrocast.net [65.175.133.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 166EB129464 for <ietf@ietf.org>; Mon, 20 Feb 2017 04:54:51 -0800 (PST)
Received: from hp5.int.jck.com ([198.252.137.153] helo=JcK-HP5.jck.com) by bsa3.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cfnUO-000HId-SY; Mon, 20 Feb 2017 07:54:48 -0500
Date: Mon, 20 Feb 2017 07:54:43 -0500
From: John C Klensin <john-ietf@jck.com>
To: Danny Niu <dannyniu@hotmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>
Subject: Re: Purpose of Port 0.
Message-ID: <C53A7803713BD60E3A05057C@JcK-HP5.jck.com>
In-Reply-To: <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> , <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> ,<71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ChmEOTpvOV33FaMprP2-_3LUbmc>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:54:52 -0000

--On Monday, February 20, 2017 12:46 PM +0000 Danny Niu
<dannyniu@hotmail.com> wrote:

> That's what I'd expected, thanks. 
> 
> BTW,
> https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
> did the same,  except of the two references it cited, one is
> broken and one is not reliable enough. 

Avoiding that sort of problem is part of what IANA registries
are supposed to be for.

Alexey, thanks,

   john





From nobody Mon Feb 20 04:57:57 2017
Return-Path: <lhotka@nic.cz>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CFF812946E; Mon, 20 Feb 2017 04:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nic.cz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ygnOykqTEZ5z; Mon, 20 Feb 2017 04:57:48 -0800 (PST)
Received: from mail.nic.cz (mail.nic.cz [217.31.204.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F276B12941D; Mon, 20 Feb 2017 04:57:47 -0800 (PST)
Received: from [IPv6:2001:718:1a02:1:fd80:c4c7:82a3:3655] (unknown [IPv6:2001:718:1a02:1:fd80:c4c7:82a3:3655]) by mail.nic.cz (Postfix) with ESMTPSA id 834FA61E45; Mon, 20 Feb 2017 13:57:46 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1487595466; bh=dwxVewM09ncLgYi5sSMWOCU+MP21JjAv1zh4yZP1gWI=; h=From:Date:To; b=qXrR4J66xG6vmSq5MfgonXHxctfIEPu2UjcWxRnWYS2hlv+1gybJnNS0JRE8SlLdj Xua7Xg+9B4P2JKub5L4GLBTVwRJ0REXpyCNigLDoim8wD4V+eerbf9TSqtYfU6l7U0 6UBRkP1BMls2VXe0Hrc2ByqFc+3t4nMfw7xE65RM=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Review of draft-ietf-rtgwg-yang-key-chain-13
From: Ladislav Lhotka <lhotka@nic.cz>
In-Reply-To: <D4D04FCC.9CD7D%acee@cisco.com>
Date: Mon, 20 Feb 2017 13:58:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <04FB4163-BBA3-44ED-8B9F-E1F2A5F49205@nic.cz>
References: <148759139687.25976.6374643432126541498.idtracker@ietfa.amsl.com> <D4D04FCC.9CD7D%acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>
X-Mailer: Apple Mail (2.3259)
X-Virus-Scanned: clamav-milter 0.99.2 at mail
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iZ6xbT6NEnQB7SziDWAMRy3iv0I>
Cc: Benoit Claise <yang-doctors@ietf.org>, "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 12:57:50 -0000

> On 20 Feb 2017, at 13:53, Acee Lindem (acee) <acee@cisco.com> wrote:
>=20
> Hi Lada,=20
> I believe we=C2=B9ve addressed all of these other than adding an =
explicit leaf
> for key direction (which was discussed on the RTGWG list). The current
> version is =
https://www.ietf.org/id/draft-ietf-rtgwg-yang-key-chain-15.txt

Yes, I saw it, looks good.

Thanks, Lada

>=20
> Thanks,
> Acee=20
>=20
> On 2/20/17, 6:49 AM, "Ladislav Lhotka" <lhotka@nic.cz> wrote:
>=20
>> Reviewer: Ladislav Lhotka
>> Review result: Almost Ready
>>=20
>> # General Comments
>>=20
>> ## Cryptographic algorithm types
>>=20
>> What is the reason for representing these as a YANG choice with empty
>> leaves? I think it would be more natural to use a single leaf, either
>> an enumeration or (if extensibility is important) identityref.
>>=20
>> ## Reusability
>>=20
>> The module defines key-chain as a grouping with the aim of making it
>> reusable in other modules. However, this approach has known problems
>> that are discussed in draft-ietf-netmod-schema-mount. I am not sure
>> how relevant they are in this case but, for one, the "key-chain-ref"
>> type is not applicable if the "key-chain" grouping is used in another
>> module. An alternative is not to use the grouping and rely on schema
>> mount.
>>=20
>> ## Key string style
>>=20
>> The difference between ASCII and hexadecimal formats of key strings
>> should be explained. I understand that the latter is a hash of the =
key
>> and, if so, I'd suggest to include "hexadecimal-string" also in state
>> data.
>>=20
>> Also, I believe that storing clear-text key in configuration is
>> insecure and Security Considerations should warn against it.
>>=20
>> ## Example
>>=20
>> It might be useful to include an appendix with example instance data.
>>=20
>> # Specific comments
>>=20
>> ## Sec. 2
>>=20
>> -   paragraph 2: s/where ever/wherever/
>>=20
>> ## Sec. 3
>>=20
>> -   paragraph 1: replace both Key-Id a Key-ID with Key ID (the latter
>> is used in other places of the
>>   text).
>> -   paragraph 2: the suggested way of supporting asymmetric keys =
looks
>> like a hack, I would suggest
>>   a more explicit representation, e.g. using a choice.
>>=20
>> ## Sec. 4
>>=20
>> -   The module has inconsistent indentation: up to "grouping
>> crypto-algorithm-types", top-level
>>   statements are indented with four spaces, the subsequent ones with
>> five spaces.
>>=20
>> ## Sec. 6
>>=20
>> -   The statement "Given that the key chains themselves are sensitive
>> data, it is RECOMMENDED
>>   that the NETCONF communication channel be encrypted." is
>> misleading because RFC 6241
>>   requires that transport protocols for NETCONF guarantee
>> confidentiality (and RFC 8040 does the
>>   same for RESTCONF).
>>=20
>>=20
>=20

--
Ladislav Lhotka, CZ.NIC Labs
PGP Key ID: 0xB8F92B08A9F76C67






From nobody Mon Feb 20 07:47:15 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD2D5129410 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 07:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 1b9ap7GctHy0 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 07:47:12 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 3542E129467 for <ietf@ietf.org>; Mon, 20 Feb 2017 07:47:12 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1KFkif7029614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Feb 2017 07:46:45 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: John C Klensin <john-ietf@jck.com>, Danny Niu <dannyniu@hotmail.com>, Alexey Melnikov <alexey.melnikov@isode.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com> <C53A7803713BD60E3A05057C@JcK-HP5.jck.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <3115a5b3-4b86-6968-f251-ed7aceb29441@isi.edu>
Date: Mon, 20 Feb 2017 07:46:42 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <C53A7803713BD60E3A05057C@JcK-HP5.jck.com>
Content-Type: multipart/alternative; boundary="------------0EA690A8B1706FF97762668D"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tzgtNqen4RP_V0g6eLrWQeuOymM>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 15:47:14 -0000

This is a multi-part message in MIME format.
--------------0EA690A8B1706FF97762668D
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit



On 2/20/2017 4:54 AM, John C Klensin wrote:
>> That's what I'd expected, thanks. 
>>
>> BTW,
>> https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
>> did the same,  except of the two references it cited, one is
>> broken and one is not reliable enough. 
> Avoiding that sort of problem is part of what IANA registries
> are supposed to be for.
I would agree IF Wikipedia didn't insist on replicating the content of
the registry.

The best solution is to edit the Wikipedia page, but that's a Sisyphian
task.

Joe

--------------0EA690A8B1706FF97762668D
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/20/2017 4:54 AM, John C Klensin
      wrote:<br>
    </div>
    <blockquote cite="mid:C53A7803713BD60E3A05057C@JcK-HP5.jck.com"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">That's what I'd expected, thanks. 

BTW,
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers">https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers</a>
did the same,  except of the two references it cited, one is
broken and one is not reliable enough. 
</pre>
      </blockquote>
      <pre wrap="">Avoiding that sort of problem is part of what IANA registries
are supposed to be for.</pre>
    </blockquote>
    I would agree IF Wikipedia didn't insist on replicating the content
    of the registry.<br>
    <br>
    The best solution is to edit the Wikipedia page, but that's a
    Sisyphian task.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------0EA690A8B1706FF97762668D--


From nobody Mon Feb 20 08:10:53 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359B1129466 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 08:10:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 MzEykrmubqdB for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 08:10:49 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 DBEBC1296C8 for <ietf@ietf.org>; Mon, 20 Feb 2017 08:10:49 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1KGA5AR002853 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Feb 2017 08:10:07 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: Danny Niu <dannyniu@hotmail.com>, John C Klensin <john-ietf@jck.com>, Mark Andrews <marka@isc.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu>
Date: Mon, 20 Feb 2017 08:10:03 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------4212750A867AA8DA635757F5"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_2vh2qccuNF-51X83Ihbad3QXhs>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 16:10:51 -0000

This is a multi-part message in MIME format.
--------------4212750A867AA8DA635757F5
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit

Hi, Danny (et al.),


On 2/20/2017 4:46 AM, Danny Niu wrote:
>> ell UDP source port 0 means don't reply (RFC 768).   It's for
>> uni directional streams.
>>
>> As for 0 to select a ephemeral port that is a BSD sockets
>> convention. That isn't something the IETF should specify.
> While _assignment_ of a port is an IETF matter and I mostly agree
> with Mark, recognition of how one is being used is is a little
> different.
+1
> It seems to me that this is rather more an IANA registry matter
> than a standardization one and that, given practices today, it
> would be reasonable to annotate the registry by adding "used
> for" or "known to be used for" to "reserved".
The IANA port registries indicate default service interpretation for
ports used as a destination for first-contact (TCP SYN, UDP 'request'
messages intending a reply).

There is no IANA registry for source ports, nor should there be. Ports
in the incoming first-contact are swapped, as indicated in RFCs 768 and
793. Source ports indicate "who to call back", and "0" is indicated in
UDP (RFC768) as "nobody" and TCP (RFC793)

As to the Berkeley socket convention, "0" has special meaning when used
in that API which follows mostly that already documented in RFC793. The
special meaning is for passive OPEN when indicating the foreign socket.
The other Berkeley conventions are specific to its API - if/when IANA
decided to assign 0 for active OPEN foreign sockets or other uses, then
presumably any API that could support that use would need a different
way to indicate "don't care" or "to be selected by the OS". There's no
*protocol* reason to exclude it, though, except that 793 makes it
difficult to do a passive OPEN to that port.

Finally, nearly all assigned ranges have RESERVED first and last values,
to allow for future changes. RFC820 (Jan 1983) is the first to list 0 as
RESERVED. The lists in RFC739 (Nov 1971) and 758 (Aug 1979)  starts at
1, though 0 not yet flagged as RESERVED, it is not assigned as early as
that. So, IMO, I would infer that the "not assignable" convention seems
to predate the Berkeley socket convention.

Joe

--------------4212750A867AA8DA635757F5
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi, Danny (et al.),</p>
    <br>
    <div class="moz-cite-prefix">On 2/20/2017 4:46 AM, Danny Niu wrote:<br>
    </div>
    <blockquote
cite="mid:TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com"
      type="cite">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">ell UDP source port 0 means don't reply (RFC 768).   It's for
uni directional streams.

As for 0 to select a ephemeral port that is a BSD sockets
convention. That isn't something the IETF should specify.
</pre>
      </blockquote>
      <pre wrap="">While <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>assignment<span class="moz-txt-tag">_</span></span> of a port is an IETF matter and I mostly agree
with Mark, recognition of how one is being used is is a little
different.</pre>
    </blockquote>
    +1<br>
    <blockquote
cite="mid:TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com"
      type="cite">
      <pre wrap="">It seems to me that this is rather more an IANA registry matter
than a standardization one and that, given practices today, it
would be reasonable to annotate the registry by adding "used
for" or "known to be used for" to "reserved".</pre>
    </blockquote>
    The IANA port registries indicate default service interpretation for
    ports used as a destination for first-contact (TCP SYN, UDP
    'request' messages intending a reply).<br>
    <br>
    There is no IANA registry for source ports, nor should there be.
    Ports in the incoming first-contact are swapped, as indicated in
    RFCs 768 and 793. Source ports indicate "who to call back", and "0"
    is indicated in UDP (RFC768) as "nobody" and TCP (RFC793)<br>
    <br>
    As to the Berkeley socket convention, "0" has special meaning when
    used in that API which follows mostly that already documented in
    RFC793. The special meaning is for passive OPEN when indicating the
    foreign socket. The other Berkeley conventions are specific to its
    API - if/when IANA decided to assign 0 for active OPEN foreign
    sockets or other uses, then presumably any API that could support
    that use would need a different way to indicate "don't care" or "to
    be selected by the OS". There's no *protocol* reason to exclude it,
    though, except that 793 makes it difficult to do a passive OPEN to
    that port.<br>
    <br>
    Finally, nearly all assigned ranges have RESERVED first and last
    values, to allow for future changes. RFC820 (Jan 1983) is the first
    to list 0 as RESERVED. The lists in RFC739 (Nov 1971) and 758 (Aug
    1979)  starts at 1, though 0 not yet flagged as RESERVED, it is not
    assigned as early as that. So, IMO, I would infer that the "not
    assignable" convention seems to predate the Berkeley socket
    convention.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------4212750A867AA8DA635757F5--


From nobody Mon Feb 20 08:15:13 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F7E1296CF for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 08:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 pQEfytbc7mvL for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 08:15:04 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 EF3BB1296DB for <ietf@ietf.org>; Mon, 20 Feb 2017 08:15:00 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1KGEPrX003146 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Feb 2017 08:14:27 -0800 (PST)
Subject: Re: To "lose the argument in the WG"
To: John C Klensin <john-ietf@jck.com>, S Moonesamy <sm+ietf@elandsys.com>, John Leslie <john@jlc.net>, dcrocker@bbiw.net, ietf@ietf.org
References: <66A86016-0382-4B2C-B9E8-30638237CB68@qti.qualcomm.com> <00e13499-7cea-a79a-7de1-dd9bad4bc530@dcrocker.net> <20170214060156.73B32639AEDF@rock.dv.isc.org> <0A3B2FF0-8F1C-430E-B4ED-DFA4CDB1FDB3@gmail.com> <0FB75520-E0BA-453C-8CF6-9F2D05B95FD6@fugue.com> <76d4aff3-760c-b258-a4e5-426ba69923f7@dcrocker.net> <84E813AE-6BD6-4EC3-A8CD-8AB24C9857D2@qti.qualcomm.com> <20170215025055.GW10525@verdi> <6.2.5.6.2.20170218010720.0b845c18@elandnews.com> <AB7BB4019CE95D16CA7B0B8D@PSB>
From: Joe Touch <touch@isi.edu>
Message-ID: <eb804059-710f-0336-8a1d-0e97f768a8e6@isi.edu>
Date: Mon, 20 Feb 2017 08:14:24 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <AB7BB4019CE95D16CA7B0B8D@PSB>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sfReiVBKt4P8kFfKg-oiT_o5cZY>
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 16:15:09 -0000

On 2/18/2017 7:26 AM, John C Klensin wrote:
> any attempt to dismiss the concerns on the
> grounds of "you should have participated more and earlier" are
> not only abusive but pose a danger to the IETF.
+1

It's very easy for large organizations to perform DDOS attacks to push
through ideas that the rest of us have insufficient resources to address.

We need to not prevent that later feedback, even when it's raised early
inside the WG. IMO, an RFC is a result of *community* consensus, and WG
consensus should never supercede that.

Joe


From nobody Mon Feb 20 08:34:52 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E7B1F1296CA; Mon, 20 Feb 2017 08:34:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: ART AD II Community Feedback Due: 2/24/17
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148760848790.26021.13861393110949198073.idtracker@ietfa.amsl.com>
Date: Mon, 20 Feb 2017 08:34:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gL7gwb_ufr4QaV6o8t-1m7s131o>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 16:34:48 -0000

The 2016-17 Nominating Committee has collected a list of willing
Nominees for the 1 year position of ART AD II (Vacancy 2017):

Adam Roach
Barry Leiba
Roni Even
S Moonesamy

We are soliciting feedback until Friday, February 24, 2017. You may provide 
feedback using the web form found here:

https://datatracker.ietf.org/nomcom/2016/feedback/

All web feedback goes into the datatracker using asymmetric encryption,
which is then decrypted by the NomCom members as they read it.  Your 
feedback can not be seen by the secretariat, the tools people, or any of 
the management.

Your feedback through the web form is not anonymous when shown to NomCom 
members as you need an IETF login to provide it.

If you want to give truly anonymous feedback, please contact one of the 
NomCom members that you trust directly, and ask him/her to relay the 
feedback anonymously to the NomCom.

You can also submit feedback via email to nomcom-chair-2016@ietf.org and I 
will enter it in the datatracker. One email per candidate, please. Please 
indicate if I should share your identity with the full NomCom.

To reach the full NomCom directly send mail to: nomcom-2016@ietf.org

If sending feedback via email please include a Feedback: tag in the subject
line.

Thanks -

Lucy Lynch
NomCom Chair 2016-2017


From nobody Mon Feb 20 08:48:48 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFEAA129559; Mon, 20 Feb 2017 08:48:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 6cOOFYNomMe0; Mon, 20 Feb 2017 08:48:41 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 800D5129465; Mon, 20 Feb 2017 08:48:41 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1KGmL64008687 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Feb 2017 08:48:22 -0800 (PST)
Subject: Re: Possible ambiguity of Hop-by-Hop Options header processing text in draft-ietf-6man-rfc2460bis-08
To: "C. M. Heard" <heard@pobox.com>, IETF <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
References: <CACL_3VHC3sx5=E4uk3+6-LR-JqXXMwF4cmMuJH-goipBUDX7fw@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <5f1201fa-cfb1-9ea0-0fbf-21cacc5bf224@isi.edu>
Date: Mon, 20 Feb 2017 08:48:19 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CACL_3VHC3sx5=E4uk3+6-LR-JqXXMwF4cmMuJH-goipBUDX7fw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/smtbXfnNHMaeOi1_Te9HFKv_HcY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 16:48:42 -0000

On 2/19/2017 3:14 PM, C. M. Heard wrote:
> ...
> On that basis I would like to suggest changing the note as follows:
>
>    NOTE: While [RFC2460] required that all nodes must examine and
>    process the Hop-by-Hop Options header, it is now expected that nodes
>    along a packet's delivery path, other than the source and destination
>    nodes, will examine and process the Hop-by-Hop Options header only if
>    explicitly configured to do so.
>
It would be useful to be more clear about destination - e.g., as
indicated up the destination IP address.

I.e., AFAICT an intermediate stop of a "loose source route" (using the
routing header) should be able to alter the HBH headers at will.

Joe


From nobody Mon Feb 20 10:33:01 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D208D1294CD for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 10:32:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AptAdaOSrSmc for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 10:32:57 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 93E74129416 for <ietf@ietf.org>; Mon, 20 Feb 2017 10:32:57 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 03B56A7B for <ietf@ietf.org>; Mon, 20 Feb 2017 18:32:57 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3jjItyPsF251 for <ietf@ietf.org>; Mon, 20 Feb 2017 12:32:56 -0600 (CST)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id CBE45A69 for <ietf@ietf.org>; Mon, 20 Feb 2017 12:32:56 -0600 (CST)
Received: by mail-ua0-f197.google.com with SMTP id 92so58010739uad.1 for <ietf@ietf.org>; Mon, 20 Feb 2017 10:32:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Zw1tI3viui897uQTr+wBybLdqDLtICmugNE6xG2RO8E=; b=W/3K16slsykWAixUciq70TJjze91SzA7rVhaoXM5nRjCvFnM7f9Utph5TUdJTwG5H1 pK0r6ok42iLWOvBbl+aJr4WokXmAF8OKs+1ukgsoLqRqu2XlsUmQfmruOJjKv+udXoAU i1bbZUNVn8eMqJYTVUYg1iZN8L0DMr3c7od1jSA00qvgtVGJE5JmpAl9MC8/NjgKv642 hU5iUaj/S8WyY8/p4kp5q4tR7AKSNExtLp9WCNPsofxbcF2dFBwHVlZDBsctiwirUhZV Zk53nxrkll3qwkVrMvQEuFVFCZtuCjWxej7GVwyuPtuE0ssbc+R2lNk4XGyU2oHcAfVr eEoQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Zw1tI3viui897uQTr+wBybLdqDLtICmugNE6xG2RO8E=; b=Aq7s2wlgMZ1aKf7EV/WmuYz6qql/8E+Wy9qcTSxFBneJiwo1NlN0IrBkJCnB+Iw5lx whtuCN92LVhIqJ5bNUykG+zVJYbJDpnFC3el37a+gB8sdD6BlCxX1zw60+VFznQeyqKy Uoq3OiZp/SmaGCQv7JXc3B325x43o5KI1PtXWd4Mr0Mg/6jfGar4i9Q1qK2HBhp+N25I /ao2ZQfHF+EhVj7UYFopHlIsp5LCevz326x0ywJb7MHJ8x75NekkZ6UdJ125M/lvukVA tXsB7fXA+gmnTPYxnHsyGbsLY/FtjTR8KlNoKXSjs5zcAPVuHFKOa7FDw8CAys8syIbp zleA==
X-Gm-Message-State: AMke39lytFI0CUMv7GXQFyezqFKuJcRzGn8tH//d+sadAjwcF+y2gOtz9d8+lzp0Y3/Dic20P5wCoEv9stbql9F8vg/QNSqikdc2ZU6tLpBEY4/O4vS1SaAT7KbS51iFOp3MmEBGBwXLHA9SDnk=
X-Received: by 10.31.192.204 with SMTP id q195mr11096880vkf.155.1487615576305;  Mon, 20 Feb 2017 10:32:56 -0800 (PST)
X-Received: by 10.31.192.204 with SMTP id q195mr11096871vkf.155.1487615576126;  Mon, 20 Feb 2017 10:32:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.13 with HTTP; Mon, 20 Feb 2017 10:32:54 -0800 (PST)
In-Reply-To: <CAKD1Yr0m1mP4gmGF12NVLDyoo0+QFSRUmetjnPWbv5dU5nEtsg@mail.gmail.com>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com> <CAKD1Yr0m1mP4gmGF12NVLDyoo0+QFSRUmetjnPWbv5dU5nEtsg@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Mon, 20 Feb 2017 12:32:54 -0600
Message-ID: <CAN-Dau1FvJFU+_MyL1UkFkkaJ9x5dPfiMDkCRfdjNcB1Vb1JFA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114388ccfa525f0548fa7d80
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LiUEtw_iWOGnIx9AXXS5NkcvP4w>
Cc: james woodyatt <jhw@google.com>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 18:32:59 -0000

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

On Sun, Feb 19, 2017 at 7:21 PM, Lorenzo Colitti <lorenzo@google.com> wrote:

>
> Do you think it makes sense to cite RFC 7934 as well? There is text in
> there that also justifies the 64 bit boundary.
>

I think a reference to RFC 7934 absolutely belong in the IPv6 Addressing
Architecture, but it seems more appropriate in section 2.1, maybe the
second paragraph or even a new paragraph in that section.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Sun, Feb 19, 2017 at 7:21 PM, Lorenzo Colitti <span dir=3D"ltr">&lt;=
<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><br>=
<div>Do you think it makes sense to cite RFC 7934 as well? There is text in=
 there that also justifies the 64 bit boundary.</div></div></div></div></bl=
ockquote><div><br></div><div>I think a reference to RFC 7934 absolutely bel=
ong in the IPv6 Addressing Architecture, but it seems more appropriate in s=
ection 2.1, maybe the second paragraph or even a new paragraph in that sect=
ion. =C2=A0=C2=A0</div></div><div><br></div>-- <br><div class=3D"gmail_sign=
ature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a h=
ref=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.ed=
u</a><br>Networking &amp; Telecommunication Services<br>Office of Informati=
on Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Av=
e SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 5541=
4-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--001a114388ccfa525f0548fa7d80--


From nobody Mon Feb 20 11:34:55 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE62C1294A2 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 11:34:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6lLrvlNaUaUK for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 11:34:52 -0800 (PST)
Received: from mail-pg0-x22f.google.com (mail-pg0-x22f.google.com [IPv6:2607:f8b0:400e: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 6240D1270B4 for <ietf@ietf.org>; Mon, 20 Feb 2017 11:34:52 -0800 (PST)
Received: by mail-pg0-x22f.google.com with SMTP id 1so4502779pgi.1 for <ietf@ietf.org>; Mon, 20 Feb 2017 11:34:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=s+72OiuKZ/wdvus/0/argajhDbtSMey4LThOwgCcXZQ=; b=B3FeY+NpIvkG6NAgon9B2acs515ZOc5p9A9UlCtvKtD0mnfGCK9dMeXFZCmndn/skm 5GCJK9VMy7/HvCiBqKLN69fWtmlgvLlPqo3knwN1SZ8WSBBmQ1x3wlYHKz+i1bRQH+pg rwkX16veCt7ut0FzQVzp7GDiHBV1ezuYM74PHDF+5ilZZq2yIafGygKfiSPV2EFitq4I RCj7khlfCSEZJgzkFDJcytnd4j9y5MZG6QYpnojbantrtNdqHwHYUSSKIcM/sTOlGQoe +7/8nFCLZOpjl0KaapysXz77/ShP0zfaG7H4a+gLfHEKdFyyj0KA8g7ArWzkW4cXfsAO rklw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=s+72OiuKZ/wdvus/0/argajhDbtSMey4LThOwgCcXZQ=; b=fIS8793nNgPKrwF//0tMYNI68pDHFbzmfQNvUDURsFsfJeM6s3eqE7A9QBAdAYhHMl gj/SeBj0MgHoaXfn/A7IWmStMmASe+JuYjPWqxM+C4EKFekZnBPkhU7sEVID8PRKuGT7 ldh5qQfSCeufUNMTmUWk3PJUcgvoghFSsHxyLcvbXowpV4f1+dQN0YfpfBNGfecCOYSB NJeKubsH0zGnjH9G/KugH79blFRWAqayjV+opJrOptYNxPKVw40Z396nTkOviNJyFed2 vxFZkdKjznehY1UUvaS54lLcrc4OSYi8gUZEI6/xmGKCyHz+E/wW7PW5KDaR5dTlpJK9 eHbQ==
X-Gm-Message-State: AMke39nR2n+uRdRT86Ir3fPYFfBa4x/UGz7GTEegHHi1VtPfJWoQAN6AMef8pB8R+xhNtg==
X-Received: by 10.84.192.137 with SMTP id c9mr5575536pld.17.1487619291794; Mon, 20 Feb 2017 11:34:51 -0800 (PST)
Received: from [192.168.178.21] ([118.149.107.106]) by smtp.gmail.com with ESMTPSA id w25sm36836499pge.27.2017.02.20.11.34.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Feb 2017 11:34:51 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: John C Klensin <john-ietf@jck.com>, Mark Andrews <marka@isc.org>, Danny Niu <dannyniu@hotmail.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1e5a335c-18e0-d9f9-60a3-dc8038d35200@gmail.com>
Date: Tue, 21 Feb 2017 08:34:50 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <71C934EA2783BD38959023DD@JcK-HP5.jck.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PzQqKTsPuVlLTal4QDg6_pWQnXY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 19:34:54 -0000

On 21/02/2017 01:33, John C Klensin wrote:
> 
> 
> --On Monday, February 20, 2017 10:07 PM +1100 Mark Andrews
> <marka@isc.org> wrote:
> 
>>
>> In message
>> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06
>> .prod. outlook.com>, Danny Niu writes:
>>> Questions:
>>> Is "Berkerly Sockets API"  defined seperately from the BSD
>>> manpages? Or is it just sections of the BSD manpages? What
>>> happened to "Berkerly Sockets API"?
>>>
>>> Proposal:
>>> Folks at POSIX are a bit unwilling to dis-certify some
>>> allegedly existing systems, and think it'd be better IETF
>>> note the purpose of port 0, so that existing app/sys woudn't
>>> break.
>>> So is it too soon to start drafting?
>>
>> Well UDP source port 0 means don't reply (RFC 768).   It's for
>> uni directional streams.
>>
>> As for 0 to select a ephemeral port that is a BSD sockets
>> convention. That isn't something the IETF should specify.
> 
> While _assignment_ of a por is an IETF matter and I mostly agree
> with Mark, recognition of how one is being used is is a little
> different.
> 
> It seems to me that this is rather more an IANA registry matter
> than a standardization one

Not quite though. Noting the RFC 768 usage as a source port, aren't
all these uses equivalent to saying 'Not valid on the wire as a
destination port'? That sounds like something the IETF should say,
as a protocol matter, and it leaves the value open for use by APIs
or other software.

This rings bells for me. Only yesterday I had to fix an unassigned
variable bug in my code for draft-ietf-anima-grasp by adding this:
    else:
        listen_port = 0

  Brian

> and that, given practices today, it
> would be reasonable to annotate the registry by adding "used
> for" or "known to be used for" to "reserved".  
> 
> That should be mostly a housekeeping matter: could one of the
> relevant ADs speak up and indicate whether they want an I-D, a
> note (perhaps just this thread), a formal liaison request from
> POSIX, or something else?
> 
>     john
> 
> .
> 


From nobody Mon Feb 20 13:32:00 2017
Return-Path: <nomcom-chair-2016@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 870EC129406; Mon, 20 Feb 2017 13:31:55 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2016 <nomcom-chair-2016@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: NomCom 2016- 2017: Announcement of IAB selections
X-Test-IDTracker: no
X-IETF-IDTracker: 6.44.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148762631551.26105.8289595240484979208.idtracker@ietfa.amsl.com>
Date: Mon, 20 Feb 2017 13:31:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kBDIzN7rQD9XlYlkWNFwfoBCqrM>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 21:31:55 -0000

As chair of the 2015-2016 NomCom, it is my pleasure to announce the selection 
of IAB members to serve in the 2017-2019 cycle.

The selected candidates are:

Gabriel Montenegro, Microsoft
Jari Arkko, Ericsson
Jeff Tantsura, Futurewei
Mark Nottingham, Akamai Technologies
Robert Sparks, Oracle
Suzanne Woolf, Independant

The resulting IAB will consist of:

Alissa Cooper, IETF Chair, Cisco
Brian Trammell, ETH
Erik Nordmark, Arista
Gabriel Montenegro, Microsoft
Jari Arkko, Ericsson
Jeff Tantsura, Futurewei
Joe Hildebrand, Cisco
Lee Howard, Time Warner Cable
Mark Nottingham, Akamai Technologies
Martin Thomson, Mozilla
Robert Sparks, Oracle
Suzanne Woolf, Independant
Ted Hardie, Google

With this confirmation, the regular work of the Nomcom 2016-2017 is at an end.
We are working on filling the ART AD vacancy now and expect to make an
announcement before IETF 98.

The NomCom wishes to thank everyone who volunteered, everyone who nominated,
and everyone who provided feedback to the process. Your input was vital
in coming to this set of decisions.

Lucy Lynch
NomCom chair 2016-2017
nomCom-chair-2016@ietf.org


From nobody Mon Feb 20 14:08:36 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E21C12706D for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 14:08:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=unavailable autolearn_force=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 8zL9V7L_bTRb for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 14:08:29 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EDBB128E19 for <ietf@ietf.org>; Mon, 20 Feb 2017 14:08:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 3C5CC30042E for <ietf@ietf.org>; Mon, 20 Feb 2017 17:08:28 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id yj0LJtoD-9mI for <ietf@ietf.org>; Mon, 20 Feb 2017 17:08:27 -0500 (EST)
Received: from russhousleymbp.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 1E63C3002B9; Mon, 20 Feb 2017 17:08:27 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <C8F3EDBB-8D78-4C22-AA12-4751AA7EBDA8@vigilsec.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_F480C90B-B149-4041-AD77-D53539ED048C"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-dane-smime-15.txt> (Using Secure DNS to Associate Certificates with Domain Names For S/MIME) to Experimental RFC
Date: Mon, 20 Feb 2017 17:08:26 -0500
In-Reply-To: <148735135694.19996.10639905917399706253.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
References: <148735135694.19996.10639905917399706253.idtracker@ietfa.amsl.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GeBcNKbVLpSRici-Eaxjwmn-qMY>
Cc: dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 22:08:31 -0000

--Apple-Mail=_F480C90B-B149-4041-AD77-D53539ED048C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I just took a look at this document, and I think it is ready for =
publication as an Experimental RFC.

Russ


> On Feb 17, 2017, at 12:09 PM, The IESG <iesg-secretary@ietf.org> =
wrote:
>=20
>=20
> The IESG has received a request from the DNS-based Authentication of
> Named Entities WG (dane) to consider the following document:
> - 'Using Secure DNS to Associate Certificates with Domain Names For
>   S/MIME'
>  <draft-ietf-dane-smime-15.txt> as Experimental RFC
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-03. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document describes how to use secure DNS to associate an S/MIME
>   user's certificate with the intended domain name, similar to the way
>   that DNS-Based Authentication of Named Entities (DANE), RFC 6698,
>   does for TLS.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dane-smime/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-dane-smime/ballot/
>=20
> The following IPR Declarations may be related to this I-D:
>=20
>   https://datatracker.ietf.org/ipr/2468/
>   https://datatracker.ietf.org/ipr/2446/
>=20
>=20
>=20
>=20
>=20


--Apple-Mail=_F480C90B-B149-4041-AD77-D53539ED048C
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJ9zCCBK8w
ggOXoAMCAQICEQDgI8sVEoNTia1hbnpUZ2shMA0GCSqGSIb3DQEBCwUAMG8xCzAJBgNVBAYTAlNF
MRQwEgYDVQQKEwtBZGRUcnVzdCBBQjEmMCQGA1UECxMdQWRkVHJ1c3QgRXh0ZXJuYWwgVFRQIE5l
dHdvcmsxIjAgBgNVBAMTGUFkZFRydXN0IEV4dGVybmFsIENBIFJvb3QwHhcNMTQxMjIyMDAwMDAw
WhcNMjAwNTMwMTA0ODM4WjCBmzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNV
BAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAibEN2npTGU5wUh28VqYGJre4SeCW
51Gr8fBaE0kVo7SMG2C8elFCp3mMpCLfF2FOkdV2IwoU00oCf7YdCYBupQQ92bq7Fv6hh6kuQ1JD
FnyvMlDIpk9a6QjYz5MlnHuI6DBk5qT4VoD9KiQUMxeZrETlaYujRgZLwjPU6UCfBrCxrJNAubUI
kzqcKlOjENs9IGE8VQOO2U52JQIhKfqjfHF2T+7hX4Hp+1SA28N7NVK3hN4iPSwwLTF/Wb1SN7Az
aS1D6/rWpfGXd2dRjNnuJ+u8pQc4doykqTj/34z1A6xJvsr3c5k6DzKrnJU6Ez0ORjpXdGFQvsZA
P8vk4p+iIQIDAQABo4IBFzCCARMwHwYDVR0jBBgwFoAUrb2YejS0Jvf6xCZU7wO94CTLVBowHQYD
VR0OBBYEFJJha4LhoqCqT+xn8cKj97SAAMHsMA4GA1UdDwEB/wQEAwIBhjASBgNVHRMBAf8ECDAG
AQH/AgEAMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDARBgNVHSAECjAIMAYGBFUdIAAw
RAYDVR0fBD0wOzA5oDegNYYzaHR0cDovL2NybC51c2VydHJ1c3QuY29tL0FkZFRydXN0RXh0ZXJu
YWxDQVJvb3QuY3JsMDUGCCsGAQUFBwEBBCkwJzAlBggrBgEFBQcwAYYZaHR0cDovL29jc3AudXNl
cnRydXN0LmNvbTANBgkqhkiG9w0BAQsFAAOCAQEAGypurFXBOquIxdjtzVXzqmthK8AJECOZD8Vm
am+x9bS1d14PAmEA330F/hKzpICAAPz7HVtqcgIKQbwFusFY1SbC6tVNhPv+gpjPWBvjImOcUvi7
BTarfVil3qs7Y+Xa1XPv7OD7e+Kj//BCI5zKto1NPuRLGAOyqC3U2LtCS5BphRDbpjc06HvgARCl
nMo6x59PiDRuimXQGoq7qdzKyjbR9PzCZCk1r9axp3ER0gNDsY8+muyeMlP0dpLKhjQHuSzK5hxK
2JkNwYbikJL7WkJqIyEQ6WXH9dW7fuqMhSACYurROgcsWcWZM/I4ieW26RZ6H3kU9koQGib6fIr7
mzCCBUAwggQooAMCAQICEQCzIsUuKpsHVq2Oiy2wXwvCMA0GCSqGSIb3DQEBCwUAMIGbMQswCQYD
VQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRow
GAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UEAxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50
IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwgQ0EwHhcNMTYwMzMxMDAwMDAwWhcNMTcw
MzMxMjM1OTU5WjAlMSMwIQYJKoZIhvcNAQkBFhRob3VzbGV5QHZpZ2lsc2VjLmNvbTCCASIwDQYJ
KoZIhvcNAQEBBQADggEPADCCAQoCggEBAOQwBbNVXhmLbyClWrRBX0GdNQFhVHEpbzM4tr5pdd0q
rPp8i+6qqNa4dAbJT6kodJ/LgsBi5EN3li4MJOIlf3rCsK1/VXepRwqUoc1cZfLRGdEj/4zgwrNZ
ULvOFiDIvYkAYDWRlYnEXulWr3KriOApHpfzbQvHStU1YsV762AIHVbZUW5tlTC9LfI8r+PIBFzv
Y5ujoUnSAgKgeE8gDK9yAxemrQ6wzDpwaf5PxEVnw0gOC2jtDojdzhoQfz57MFrL9pA1QyMbnItV
zCYfc5J7EfeCGupcFqwXytbJHSYPfLfM1/3omGgCGD/DZk4z4SUVC19k02iGxAIVDsWJ5oMCAwEA
AaOCAfIwggHuMB8GA1UdIwQYMBaAFJJha4LhoqCqT+xn8cKj97SAAMHsMB0GA1UdDgQWBBTrsV85
Y7qY6oVPF5xRd+wqIu3VJTAOBgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAX
BggrBgEFBQcDBAYLKwYBBAGyMQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYM
KwYBBAGyMQECAQEBMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BT
MF0GA1UdHwRWMFQwUqBQoE6GTGh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1NIQTI1NkNs
aWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgZAGCCsGAQUFBwEBBIGDMIGA
MFgGCCsGAQUFBzAChkxodHRwOi8vY3J0LmNvbW9kb2NhLmNvbS9DT01PRE9TSEEyNTZDbGllbnRB
dXRoZW50aWNhdGlvbmFuZFNlY3VyZUVtYWlsQ0EuY3J0MCQGCCsGAQUFBzABhhhodHRwOi8vb2Nz
cC5jb21vZG9jYS5jb20wHwYDVR0RBBgwFoEUaG91c2xleUB2aWdpbHNlYy5jb20wDQYJKoZIhvcN
AQELBQADggEBACgHw+/VeC7LgLJs19KZ6Ds2cW+jLSPjA3AIqSxiQ+uyDFwe6FujBUqRCXfla0qg
MzbhJ+1uSxcaktsS5idpB5Dfp8SVEGLcjtSJwWVlEofjaRrx6pi2mzazQwfKklY/epvsgnCoY8KW
FeSGkpbQXu5WrIL18EFqMCHqDiu5/P49PcZnJRv2xHTi5CkIsI7XgOw4FazS3xuJMVQ5TVtIUeMW
OqRlNJaeTiBsOVauS3FE/zRejsAYhHp3EV1PZFhV6hdcK/8qKrqRBtZtsEIm2FNWNsk8p/3RmUQl
4n4qN/NvapmXyYqfHZiuxf2g8H/WHF8IlVDzljLy90Uy0X7Qp0gxggPGMIIDwgIBATCBsTCBmzEL
MAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9y
ZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENs
aWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhEAsyLFLiqbB1atjostsF8L
wjAJBgUrDgMCGgUAoIIB6TAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMjAyMjA4MjZaMCMGCSqGSIb3DQEJBDEWBBRsZtaYQUsp2afd3Q+P2K1wLaH96zCBwgYJ
KwYBBAGCNxAEMYG0MIGxMIGbMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVz
dGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDFBMD8GA1UE
AxM4Q09NT0RPIFNIQS0yNTYgQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBTZWN1cmUgRW1haWwg
Q0ECEQCzIsUuKpsHVq2Oiy2wXwvCMIHEBgsqhkiG9w0BCRACCzGBtKCBsTCBmzELMAkGA1UEBhMC
R0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UE
ChMRQ09NT0RPIENBIExpbWl0ZWQxQTA/BgNVBAMTOENPTU9ETyBTSEEtMjU2IENsaWVudCBBdXRo
ZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhEAsyLFLiqbB1atjostsF8LwjANBgkqhkiG
9w0BAQEFAASCAQAbS20DETc4esaiJaDMRA33jpg1Lc9cYoKxmgKAd1A17tGDBZQana3Q2boje7j7
0JpSb9h1+aUPRQC23S4HmD7F7QRK0HHkakh98P5Lhk3zM/eIFB+PLd5xLSHxpE3HEjQiT1HuPcpM
6i8lBGLfgJJn+ohKDCEbv05rxWue1gMLYH33xfeXgqpExTEBc0tiq1XUJX27MqJJRe+beGu6joq1
dtca8Q4a3LyHG1xuTu+PmLbzj0PS77Y1FIwDFWNs8BJEGJmEKVx2XlDaBQTPDrLcC4UgON/kHG1j
XwOc8H+bQu+BcXNPBS8CShX+9/MiUiyCMg3E6OuIYzakBgXbE6DGAAAAAAAA
--Apple-Mail=_F480C90B-B149-4041-AD77-D53539ED048C--


From nobody Mon Feb 20 14:49:54 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAE4E128E19 for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 14:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 fLskwwZF0N1o for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 14:49:51 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 E72A7128874 for <ietf@ietf.org>; Mon, 20 Feb 2017 14:49:51 -0800 (PST)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1KMnVsv000918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Feb 2017 14:49:32 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John C Klensin <john-ietf@jck.com>, Mark Andrews <marka@isc.org>, Danny Niu <dannyniu@hotmail.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <1e5a335c-18e0-d9f9-60a3-dc8038d35200@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <4b7f4780-2bb6-2fc6-0081-735ced52f495@isi.edu>
Date: Mon, 20 Feb 2017 14:49:30 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <1e5a335c-18e0-d9f9-60a3-dc8038d35200@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zeUdtJtGeoLg76FKGWFuiwquLmo>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 22:49:53 -0000

Hi, Brian,


On 2/20/2017 11:34 AM, Brian E Carpenter wrote:
> On 21/02/2017 01:33, John C Klensin wrote:
>> ...
>>> Well UDP source port 0 means don't reply (RFC 768).   It's for
>>> uni directional streams.
>>>
>>> As for 0 to select a ephemeral port that is a BSD sockets
>>> convention. That isn't something the IETF should specify.
>> While _assignment_ of a por is an IETF matter and I mostly agree
>> with Mark, recognition of how one is being used is is a little
>> different.
>>
>> It seems to me that this is rather more an IANA registry matter
>> than a standardization one
> Not quite though. Noting the RFC 768 usage as a source port, aren't
> all these uses equivalent to saying 'Not valid on the wire as a
> destination port'?

I don't think so.

768 says that if you receive 0 as source, do not reply.

That doesn't mean you can't *initiate* to port 0, if it is ever assigned.

Joe


From nobody Mon Feb 20 15:58:12 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E379F129435; Mon, 20 Feb 2017 15:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 nZCck42Ap_If; Mon, 20 Feb 2017 15:58:05 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 10FEB129413; Mon, 20 Feb 2017 15:58:05 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cfxpy-00032s-PR (job@us.ntt.net); Mon, 20 Feb 2017 23:58:04 +0000
Date: Tue, 21 Feb 2017 00:57:34 +0100
From: Job Snijders <job@ntt.net>
To: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170220235734.GA84656@Vurt.local>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F3y64cGPRtSDX_6zDYYZrVetF90>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Feb 2017 23:58:06 -0000

On Fri, Feb 17, 2017 at 08:44:20AM +0100, otroan@employees.org wrote:
> 4291:
>    For all unicast addresses, except those that start with the binary
>    value 000, Interface IDs are required to be 64 bits long and to be
>    constructed in Modified EUI-64 format.
> 
> 4291bis:
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>    on inter-router point-to-point links.  However, the Interface ID of
>    all unicast addresses, except those that start with the binary
>    value 000, is required to be 64 bits long.  The rationale for the
>    64 bit boundary in IPv6 addresses can be found in [RFC7421]
> 
> Proposal:
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 bits [BCP198]. However, as explained in [RFC7421], the
>    Interface ID of unicast addresses is generally required to be 64
>    bits in length, with exceptions only provided in special cases
>    where expressly recognised in IETF standards track documents.

wow, the last sentence of that proposal is overreaching! The text in
4291bis -07 is not ideal either. At this point, I do not believe
rfc4291bis can advance with such text. The contention around unicast
addresses not starting with a binary value 000 must be resolved.

Let's look at the following:

    job@tardis:~$ sudo ip -6 addr show dev eth1
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
        inet6 2001:728:1808:1::21/126 scope global
           valid_lft forever preferred_lft forever
        inet6 fe80::20d:b9ff:fe41:d4f5/64 scope link
           valid_lft forever preferred_lft forever
    job@tardis:~$ echo HERESY\! a /126\!

Is the IPv6 Addressing Architecture Police (IAAP) gonna come to crack
down on this? What's IETF going to do about this? Nothing! Is this bad?
No. Should there be any tolerance for "IPv6 capable" hw/sw which can't
cope with a /126, /120 or whatever? No.

The main issue for me on this point is that from a pragmatic point of
view, a architecture policy specification should strive to match the
expected deployment reality. I think we can argue that there now is
sufficient deployment experience to admit that all possible IPv6 prefix
lengths are configured.

Referencing RFC7421 is fine, but please realise that in doing so we're
(by proxy) referencing FDDI, ATM, Token Ring and other fascinating
standards from the good ole' days - imho a 7421 ref is just scrambling
for arguments.

Persisting with a 64-bit boundry fixation is actually making the IPv6
address architecture _less_ expressive. When expressiveness is limited
through an arbitrary rule... that's just shortsighted. 

Nobody can claim that we know all use cases (with their respective up
and downsides). However, the few use cases we _do_ know about arrived at
different prefix lengths. Why continue to document exceptions? That is
just busywork. There is no 'one true subnet size'.

Mandating something arbitrary like 'address ID must be 64 bits' when
there is no technical requirement for such rule would be nothing short
of arrogant.

The ND/SLAAC attack vector was real problem, can still be real, why
pretend that that issue doesn't exist by mandating 64-bit IIDs? Any sane
deployment will take steps to cover that risk surface. A valid
mitigation strategy remains to just configure something longer then a
/64 ... like /120

We must accept that we cannot see into the future. Let operators choose.

Kind regards,

Job

ps. The "Write a draft" argument is weak at best, since we are already
are discussing a draft (called 'draft-ietf-6man-rfc4291bis-07.txt'),
which is in IETF Last call, which means it is in a place to discuss the
contents of that draft. No reason to kick the can down the road.


From nobody Mon Feb 20 16:06:45 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D8512946A; Mon, 20 Feb 2017 16:06: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xSVy8NZxLNs1; Mon, 20 Feb 2017 16:06:37 -0800 (PST)
Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 669A2129479; Mon, 20 Feb 2017 16:06:36 -0800 (PST)
Received: by mail-pg0-x244.google.com with SMTP id a123so12227663pgc.3; Mon, 20 Feb 2017 16:06:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kUk/0JsIsMzQPKIzAyK5tjau7EaJyJ8AynOh97AtNRY=; b=FlPgJT8bcdPDSIGTn5y0py5vA4WWap2rgMBD2fugKZEFck1v+bf8wHzRbsveyA1GsZ G0zj0mtjZBlUKU+O06IHqxeIphXZDNLnDwKDJpMEHL9dP8ybUmnR3kjqpdp8w4fKS/hu 1g41G0gbY20q/WO9Qpq1DfwJkclwHkeCghzOa982RccrXKilsrUlS1Zgkh5GCOojWaGQ Xp4S/1Eof/pkFTqrNdI5WM5ExWEaAlRWc7UIEPT4L9vO0ovq1zZM8AST7W0MlOyMaFE+ 6rt/HKGd0/nhGakd0F0Z7E9Wt4H7nnDC8Fnv62Pf8G6EKb963OTw8iMxaelkPZiJDvXs buTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kUk/0JsIsMzQPKIzAyK5tjau7EaJyJ8AynOh97AtNRY=; b=E5WUmD18iHBzMeT255p1jVcSY9i99Q2UDW5R3Kd94j9KQkvGSsOipQ9O1qs77OPMnr LpaE0io6gbYw9jd+SBbXA8gUgkDdra6Z1P5h/T2NgUlOkK9vPsdS4bfsvlnoFUuDD1IJ wADArX0uUKXiASMzSn8Ci2xzZaECyxaARVM9P9XrLysKmewJF2bvaukIq7OeGoKzZQFH 3Uwm/v+H+8RLhVSZ7e66QfTjHyWy/1Sco9eo5Sh23ee24ulA6xNWRTsxYawmIKa31pQi BbvvGmIHChtVcc+/mRHjKdpEI+59NsIE3CcQz6t2W++N0DlugT8aUC/kaxWyEh5yCY7k qeEw==
X-Gm-Message-State: AMke39kd+idZGUrJUS+MM/KfD1zPD/dDtPQAfJcZODM3FEFwqavOfYI8NmtrpVSiOZ/awg==
X-Received: by 10.84.231.205 with SMTP id g13mr35865151pln.30.1487635596085; Mon, 20 Feb 2017 16:06:36 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id y201sm26881882pfb.16.2017.02.20.16.06.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Feb 2017 16:06:34 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <20170220235734.GA84656@Vurt.local>
Date: Mon, 20 Feb 2017 16:06:33 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <77A662EB-1466-4F73-8105-E33F152D4824@gmail.com>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local>
To: Job Snijders <job@ntt.net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y_n9h8N3xt1AGUB5NUcXRgMXgW4>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 00:06:39 -0000

On Feb 20, 2017, at 3:57 PM, Job Snijders <job@ntt.net> wrote:
> We must accept that we cannot see into the future. Let operators choose.

That, of course, was the point of RFC 7608.


From nobody Mon Feb 20 16:20:23 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6D5412943B; Mon, 20 Feb 2017 16:20:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 1WS6wQSHxOlo; Mon, 20 Feb 2017 16:20:21 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 5923D12945D; Mon, 20 Feb 2017 16:20:21 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cfyBW-0008e8-UE (job@us.ntt.net); Tue, 21 Feb 2017 00:20:20 +0000
Date: Tue, 21 Feb 2017 01:19:40 +0100
From: Job Snijders <job@ntt.net>
To: otroan@employees.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221001940.GB84656@Vurt.local>
References: <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jXU8we2iptCE2bw_25jevU2HtxU>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 00:20:22 -0000

On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:
> There are many reasons for the 64 bit boundary.
> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and NPT66

Irrelevant.

> - Simplicity in addressing (no more subnet masks)

That seems an overly optimistic statement.

> - A fair balance between the users and the providers of networks.
>   Ensure that users get a fair share of addresses and try to avoid
>   operators charging per address.

IETF is not a product management committee. Regardless of what is fair
or just or reasonable, vendors will charge for the strangest things.
While I sympathize with the objective, I do not think this is the
appropiate forum to achieve such a goal.

Also, I think we here touching upon the very heart of the issue: some
would like to force every link on this planet to have a routable /64
(for perhaps ideological reasons), and some don't (for perhaps
operational reasons).

I'm from the school of thought where unenforceable rules have no place
in society. There already is precedent to abandon a classful addressing
paradigm in favor of classless inter-domain routing. This implies that a
the fixed 64 bit boundary is unattainable, as such, getting classless
IPv6 is merely a matter of expending sufficient energy.

> The 64 bit boundary is so embedded in the set of IPv6 specifications
> that it would be very hard to unravel at this point. It certainly
> cannot be a single paragraph put in during the advancement of 4291.
> Write a draft. Or write a book on protocol politics and the
> underlaying values reflected in the specifications...

If this is the case, why proceed 4291bis while its content is contested?
What purpose does that serve?  By publishing 4291bis, one would add yet
another referenceable source to legitimize the 64 bit boundary, which
adds to the pile of things that need to be 'unraveled'. Perhaps the buck
should stop here?

> PS: With an implementor hat on, I write code that can deal with any prefix length.

Excellent! Keep it up.

Kind regards,

Job


From nobody Mon Feb 20 16:49:58 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 598391294ED for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 16:49:56 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FIeuWjO0QmcT for <ietf@ietfa.amsl.com>; Mon, 20 Feb 2017 16:49:55 -0800 (PST)
Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::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 934F212954A for <ietf@ietf.org>; Mon, 20 Feb 2017 16:49:54 -0800 (PST)
Received: by mail-ua0-x22a.google.com with SMTP id k1so16276054uab.0 for <ietf@ietf.org>; Mon, 20 Feb 2017 16:49:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=7b9aqjo3MsX/TQiOWrsVbvyMoN2jU/Tx9X4DGDM5wTM=; b=GXvcvODbqRlRojPalOHR115ww6wwmRxGskIsz92A3v8A20Mrf4V6WmG9JtSHQv6sgD /EBeXJCE4C33SmYqCn84ZKL29m+wlnvnPY93QUBVGsYvCQcovHcN2krjNgNc2YCwUeOi V2IgwJvQ10LZLH+lAjzktSUFGKlKXaW26XD/G/aTAhEVLK2n7ro3Lr2rOEDw+jRUXzfP jTl21aW/q454hQm0DQQ17RosxGx6PhKMh02fcJJszpGCClWNF1Vac/MwPis/l+fwhcu0 9VXc8hDPQIjUd3PhE8PKTUGr9U5UM66C8CCoh+v4gFHpjYB9A6UK8mYQJFfdZKOJW7p8 GEKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=7b9aqjo3MsX/TQiOWrsVbvyMoN2jU/Tx9X4DGDM5wTM=; b=o1DuIzTHkQc4W+u+LSKrm/44vcx2IjMtxBIGLgPspZs9Xh23Ayetm8DlA+/YNUZ8yb W7EqVugbIZcgjS91xUVmf+A0fNhhsxBefARJxjXbMGlJQeZAMNGyLQ8VItF6/paFOQgU ep0sJPwoHWopJBQ8UsMOk72I3FTDe7IF+JHRN19lpj5vIxxuj3Kh+x0Nn2oeT+wUpVPW qWrFBmlOJMuVOOgNVUoYLiyBwWvW4UAQJrNBmxSmutW3DJc1RwA54mgsSPVzG+JB7TUq PV//R/oXM/bMhhlIovd1x4RoRARqzAranTXXbx6ARdaeyxCnaFqc1PDgzvrS1r4eFGO2 5n2A==
X-Gm-Message-State: AMke39mLgbqFPxCk2ThQyB8k54x9LCGXnygeoeWrL4jHPeZGXNm+lrU6navkwYdLsMooPtp6bfJk7QhHNlESkP4P
X-Received: by 10.176.82.93 with SMTP id j29mr13003532uaa.57.1487638193466; Mon, 20 Feb 2017 16:49:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Mon, 20 Feb 2017 16:49:32 -0800 (PST)
In-Reply-To: <20170220235734.GA84656@Vurt.local>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 21 Feb 2017 09:49:32 +0900
Message-ID: <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=94eb2c1916a41449400548ffc23c
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bi6JBlRyW8iITn71SqHZuj_rToc>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 00:49:56 -0000

--94eb2c1916a41449400548ffc23c
Content-Type: text/plain; charset=UTF-8

On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:

> ps. The "Write a draft" argument is weak at best, since we are already
> are discussing a draft (called 'draft-ietf-6man-rfc4291bis-07.txt'),
> which is in IETF Last call, which means it is in a place to discuss the
> contents of that draft. No reason to kick the can down the road.


I'm sorry, but that's really how it is. The text you dislike has been the
standard for almost 20 years, and is it inappropriate to change it in the
context of reclassifying this document from draft standard to Internet
standard.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Feb 21, 2017 at 8:57 AM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"=
mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">ps. The &quot;Write a draft&quot; argument i=
s weak at best, since we are already<br>
are discussing a draft (called &#39;draft-ietf-6man-rfc4291bis-<wbr>07.txt&=
#39;),<br>
which is in IETF Last call, which means it is in a place to discuss the<br>
contents of that draft. No reason to kick the can down the road.</blockquot=
e><div><br></div><div>I&#39;m sorry, but that&#39;s really how it is. The t=
ext you dislike has been the standard for almost 20 years, and is it inappr=
opriate to change it in the context of reclassifying this document from dra=
ft standard to Internet standard.</div></div></div></div>

--94eb2c1916a41449400548ffc23c--


From nobody Mon Feb 20 17:11:24 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF3BD12954F; Mon, 20 Feb 2017 17:11:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DP1Unlfudhz7; Mon, 20 Feb 2017 17:11:16 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 C18E6129530; Mon, 20 Feb 2017 17:11:16 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id s67so4654887pgb.1; Mon, 20 Feb 2017 17:11:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=jQRy8RdhaONXJngEmPdJTNYmkMUKFg4dVeJu/IC2s9s=; b=gD4UAYG7uvw0SGfGoM6BwqdcIpXtd0CHINBauk25DwGRnpXOa/KNOAyvrYKcSlkBUk Kf2XoL9qc0NG0AUW0tgCCaVj3mttZj0PekjEuoCVD6KaZKcwQHT03uD42BV9OXz/1wnq 9cr1VBMK7wTwSLZyeHSfHVa4T8VyrbJoRECCTLJCxV1kzzdWa+gzK7gyljrIPAjhLqFE N3Or6UjPMROOLKQjlexCxp7894xNuOyd1YA3WpJWPhL+eTW9sOBZvZnjo0VM7X8tfa1V GBPj+PmgAAPEAwG5tLhfT/zYt+bmeXeyE/H9DInxdhf7IAdTWWikhzTf0K0C5R8TjnPO H7RA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=jQRy8RdhaONXJngEmPdJTNYmkMUKFg4dVeJu/IC2s9s=; b=JjB7A/UdN9uEhKQBB3NnQ7/Tsn7B/ARfgpABiofmJ5ZKS7H3A6m/tl4JXutnuPxK2s kOLsNjhh0ocZ8xAmA3XOfRHQF5tRVMmNUs+V0WNcKVF1MbkwtxGs1d4M+JFGE6rh4pH9 xHwT64uQJogElZnVwlbWW/CJzjM6pDH10z6/AArS/dRjYOr9b9lyNfWFrxpYceNHxHKv 2atwGMy6L/EszeFr9ZsGNUd8xU+J5GIuWln3YLNRmSoZXfjYob3VP+UCXYsJD3gyomE5 XiHBcWkBG1QTKrqflezgYeym+UA/bsKXdPdN7FUKSyxvMtSm1BtM4i05K1M2BpRHdFLL Nf2g==
X-Gm-Message-State: AMke39ldPgh2+RRYQFlI0QrOi090svL8ccY+lBVOcEPd7pVFK6qEhkuSyuDsajEPeNkNhQ==
X-Received: by 10.84.174.4 with SMTP id q4mr26886432plb.35.1487639476378; Mon, 20 Feb 2017 17:11:16 -0800 (PST)
Received: from [192.168.178.21] ([118.149.107.106]) by smtp.gmail.com with ESMTPSA id 202sm4619456pfa.6.2017.02.20.17.11.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Feb 2017 17:11:15 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>, otroan@employees.org
References: <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com>
Date: Tue, 21 Feb 2017 14:11:15 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170221001940.GB84656@Vurt.local>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j3AiGAvV7c25orZvJ2HuyMV8pZM>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 01:11:18 -0000

Hi Job,

On 21/02/2017 13:19, Job Snijders wrote:
> On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:
>> There are many reasons for the 64 bit boundary.
>> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and NPT66
> 
> Irrelevant.

Not really. They are both running code. You may not want them in
*your* network but that isn't the point. Some people want them.

And there is a lot of other running code too, not just SLAAC which is
mandatory to implement in every IPv6 host. So this actually trumps all
the other arguments: it's 64 bits because it's 64 bits.

...
> Also, I think we here touching upon the very heart of the issue: some
> would like to force every link on this planet to have a routable /64
> (for perhaps ideological reasons),

No. For running code and interoperability reasons. We could have settled
on 48 bits, but we didn't. But, because of interoperability, we had to
pick something.

> and some don't (for perhaps
> operational reasons).

In practice, there isn't much choice except for point to point links.
All the same, we definitely needed RFC7608 (=BCP198).
 
> I'm from the school of thought where unenforceable rules have no place
> in society. There already is precedent to abandon a classful addressing
> paradigm in favor of classless inter-domain routing. This implies that a
> the fixed 64 bit boundary is unattainable, as such, getting classless
> IPv6 is merely a matter of expending sufficient energy.

No. IPv6 routing is classless and always has been. RFC7608 simply re-states
it. But automatic address assignment, which is an equally important property
of IPv6, needs a default setting for portable code, and it is /64. That isn't
a matter of opinion. It's a (possibly inconvenient) truth.

...
> If this is the case, why proceed 4291bis while its content is contested?

What we're discussing is the exact text to describe the inconvenient
truth. I'm not aware of any generally available running code that will
be changed in even one instruction by the final text - that is indeed
a requirement for advancement to Internet Standard.

   Brian


From nobody Tue Feb 21 01:47:17 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 88EE712959A for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 01:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.332
X-Spam-Level: 
X-Spam-Status: No, score=-5.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 RU8nzQUYq_br for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 01:47:15 -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 0BF0812940B for <ietf@ietf.org>; Tue, 21 Feb 2017 01:47:14 -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 v1L9lD4W016506 for <ietf@ietf.org>; Tue, 21 Feb 2017 10:47:13 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F3C96202B05 for <ietf@ietf.org>; Tue, 21 Feb 2017 10:47:12 +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 E9C152015D0 for <ietf@ietf.org>; Tue, 21 Feb 2017 10:47:12 +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 v1L9lCeh027951 for <ietf@ietf.org>; Tue, 21 Feb 2017 10:47:12 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com> <CAKD1Yr0m1mP4gmGF12NVLDyoo0+QFSRUmetjnPWbv5dU5nEtsg@mail.gmail.com> <CAN-Dau1FvJFU+_MyL1UkFkkaJ9x5dPfiMDkCRfdjNcB1Vb1JFA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1e5d9486-ea94-f1ca-ad6f-05e9bc0c2c5e@gmail.com>
Date: Tue, 21 Feb 2017 10:47:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau1FvJFU+_MyL1UkFkkaJ9x5dPfiMDkCRfdjNcB1Vb1JFA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gtK1PWb1-TnZit51k6HHy1B1A6Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 09:47:16 -0000

Le 20/02/2017 à 19:32, David Farmer a écrit :
>
>
> On Sun, Feb 19, 2017 at 7:21 PM, Lorenzo Colitti <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
>
>
> Do you think it makes sense to cite RFC 7934 as well? There is text
> in there that also justifies the 64 bit boundary.
>
>
> I think a reference to RFC 7934 absolutely belong in the IPv6
> Addressing Architecture,

I agree.

I read that RFC7934 again because a new errata points to an earlier
RFC1681 mentioning additional reasons for needing multiple IP addresses
per Host: e.g. a ppp Router.

I would appreciate if RFC4291bis considered the /64 limit too in light
of today's IoT Routers connecting to cellular operators.  How would such
cellular IoT Router live with /64-everywhere of current cellular operators?

> but it seems more appropriate in section 2.1, maybe the second
> paragraph or even a new paragraph in that section.

Section 2.1 looks good to receive a reference for RFC7934.

Alex

>
> -- =============================================== David Farmer
> Email:farmer@umn.edu <mailto:Email%3Afarmer@umn.edu> Networking &
> Telecommunication Services Office of Information Technology
> University of Minnesota 2218 University Ave SE        Phone:
> 612-626-0815 Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================


From nobody Tue Feb 21 02:14:08 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558511298AB; Tue, 21 Feb 2017 02:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 tVA5gkI2b65G; Tue, 21 Feb 2017 02:14:06 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 D317612940B; Tue, 21 Feb 2017 02:14:06 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cg7SH-000CpA-IN (job@us.ntt.net); Tue, 21 Feb 2017 10:14:06 +0000
Date: Tue, 21 Feb 2017 11:13:39 +0100
From: Job Snijders <job@ntt.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221101339.GC84656@Vurt.local>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nW5HlLJ3edFqAF9JCJ-BmMKNv-A>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 10:14:07 -0000

On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:
> On 21/02/2017 13:19, Job Snijders wrote:
> > On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:
> >> There are many reasons for the 64 bit boundary.
> >> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and NPT66
> > 
> > Irrelevant.
> 
> Not really. They are both running code. You may not want them in
> *your* network but that isn't the point. Some people want them.
> 
> And there is a lot of other running code too, not just SLAAC which is
> mandatory to implement in every IPv6 host. So this actually trumps all
> the other arguments: it's 64 bits because it's 64 bits.

When someone utters the phrase "it is X because it is X", the rhetorical
imperative seems to be to dismiss further conversation (perhaps any
internal dialogue as well, which may be the primary purpose). "It is
what it is" therefore, there’s nothing more to be said about it...

Except when it's not 64 bits?

> > If this is the case, why proceed 4291bis while its content is
> > contested?
> 
> What we're discussing is the exact text to describe the inconvenient
> truth. I'm not aware of any generally available running code that will
> be changed in even one instruction by the final text - that is indeed
> a requirement for advancement to Internet Standard.

The below is truth.

AS 2914 is one of the larger Internet backbones. If the Internet
Archives are to believed they started deployment of IPv6 15+ years ago.

I've looked at all configured IPv6 addresses on AS 2914 equipment.
Interestingly enough, the below table is a reflection of not only NTT's
own addressing, and (since AS2914's core function is to connect networks
to each other) also of its peers and customers. In the end, whatever
makes the thing work is the thing that will be configured.

	/127 - 22%
	/126 - 52%
	/125 - 0,9%
	/124 - 0,5%
	/120 - 0,04%
	/112 - 0,02%
	/64  - 23%

The above percentages come from grepping through configurations of
thousands of interconnections. I'm confident that other networks will
show similar prefix length distributions.

I'd be interested to see an accomodation for staticly configured
environments in the text.

Kind regards,

Job


From nobody Tue Feb 21 02:24:17 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28CB51298AA; Tue, 21 Feb 2017 02:24:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i04PLR4oewmB; Tue, 21 Feb 2017 02:24:13 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0106.outbound.protection.outlook.com [104.47.1.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD45B12959A; Tue, 21 Feb 2017 02:24:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Zd/F5TBrYT6sl+teDOGoxmQ8kFlDs1lftew+47WALUM=; b=G3M9hrEvG46HdW9J8FwokV7xhC4UwHlxs5c7MDa1mikSYrT2R+nyTPtS8PMOjFA/z1R2yjvqKVTpN56b9wrcoZYyM+fV+uTjZHi5srvCaSEBxZWzhQgR5StBC5Y5PhkgaEhHncQyI3hYtYXHK8PtrsMtXcVYDDduwIKLNAY+v5w=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by HE1PR07MB1564.eurprd07.prod.outlook.com (10.169.123.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Tue, 21 Feb 2017 10:24:09 +0000
Message-ID: <01cc01d28c2c$42aab8a0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Sander Steffann <sander@steffann.nl>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <BA018A61-1390-4775-ACB9-61C66D7A34FB@google.com> <567281BF-DD55-4E46-9977-4575561A83C9@steffann.nl> <F4868F7E-C970-4342-8A89-8087B9D33911@steffann.nl>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Tue, 21 Feb 2017 09:49:20 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB6P195CA0005.EURP195.PROD.OUTLOOK.COM (10.171.120.143) To HE1PR07MB1564.eurprd07.prod.outlook.com (10.169.123.14)
X-MS-Office365-Filtering-Correlation-Id: cda30b3f-d3ad-472c-1a04-08d45a43c602
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR07MB1564;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 3:mRIdUZrcGf3GOvS2Be5nAm58qI0tBAx61Y9eo2rqaX2dY+AodQmlYGji2TlZT9Dm9HrKqhOYpyQ3CaDfZum/TKQmbP1FXua9yrs/OVh7moiodDBdp/K0jauDVX7CAYN5QDn8u57zYfkF3VGTXF4DHAHg+fY3JwTU9jTEnjDMU2/vUYa4ojG9AmLhINejFzajkQlpTxh7ezZvKYqF6kFHw+G2YN9tj+PAvdZVd/i6YCxx1XE+UOn7vJeQvlm+7EWLdGTBY3fijfMdPurVNQBfQQ==; 25:hVkuvyWCg/QOAJb1j6AP+vQChJ2MsaNr/5e06GE83Gn/D8uC3YvnHSTMuqQHP/XoUcIcHSIFOeu9+TsM16RMUOdgU8Pw9fiMfjQ3JzWpYV8rlYhfsyWlwRcwAPAGiHJvoy/qqMdB49UPiAw5P8dCE0SFsNjIu/udSHtmENPtHqaR0avB+GWVicDczA9Pk4+5rbuME6RHC5zgNjZwldihmocpcPJ4sNfPrx+b/P3Y1ovr7jR0jDEuwL/tdqhEPOA9f/6r15yjpLDxuX7jzEV4sfZREKaBX+5M/4sTaAdMrw5LbXALO5P8gSajig8AvUpzwi9l68oVXu19YpXxoXDB4pHgHCEZSI9QcFEnMAneBOBQ33V0Cd0bidIUyhDgLSExU1qZuEiD89zs5NhNeTaEr8yQ4SgOOjkAcLlmlGHzfr5vd1PTHOR/O4M/TXJssZ+tBuIsx5/6/0CcPSkUZpfz6A==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 31:B5bOR/wD2Pe6hkga2ucQxvD0ro+VNvPBHO036DlLhfYy93XpOehj28Yx9RQ6GM8QJ96pRbaExO7ww2+9JgxxKioCoY17NeActNDiAPLmCd15dc1UfiSMYRejapwiWIwvPlJXrJWd/F7lKmAnuEPO7pNYFZOh0N3At/vGobAuoT5QP33oc9dUVXo/EWCTOevfgcsolLh7nyTWJz67K3X8PntYJzBcLDk5uA/YBC/Ull2x4PC36Rcd248Yzs3nU1Fx7L9f4Hx9a0vVfTFb9VZ42w==; 4:RYQrrM9/hH+1Hvne2IEZYBPbxKiUhlBNCxsUmBviSFz1oQpfW48oxqVxCaJ7+ac3r9le1oKaJ8jdWDig64Mq/4OXvl8cQDw8UDThpSqZKzWTDyeQCwEvFbKYLcUbbpRu7aQIQEFBXYm7HIDfvKSLpGmB/Mq1iKPWnliPexQb1FevQDld2g+V/Qh4WoTrRcgQvP7Whd9y3WmSiUC4Wyakl58friPILq5V2IPCmSRHyafY0u1npzTE0Kqd1//shpquE6jda+i9U7Hn3xKP7BzNHLlnOHBTFs9cRqHiWyixkNiDfRk97tdVqH/UFMmqGVxr6JRm7z+6S5vmmsX2Hlv4r5hUxcM0G5JWcZpU0IM0X4/WjibIL6X0ihOUgOySdMitTJWQHAeAbp8Mte19rVUC+GkLqeTKy+YHanJXMM+0E+md2M6yyMfGtwzq/vd1l8BIMfHU4Yt5WW+ZnbHEHfYHVGnko6Tk9s3YOLsa6CVaX8bIzW99CDXOk7VCkcRZc55CEQQD+rzIALxAjhjJB3lnj79HWv1UlIsYKn9C8H0jJuYvoJvBINovaNSbwhYm7gbxYbkKcn7lSSe+tK3qWSIW9VpYv/b34DNty9XjWLnOtUmsy5lvEMYjzz7ZrUrg+4/Xm2m+RB7L1sTXe+AbHr9zlw==
X-Microsoft-Antispam-PRVS: <HE1PR07MB15642A043D1DD28545144198C6510@HE1PR07MB1564.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(100405760836317);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123555025)(20161123560025)(20161123562025)(20161123564025)(20161123558025)(6072148); SRVR:HE1PR07MB1564; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1564; 
X-Forefront-PRVS: 0225B0D5BC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(199003)(189002)(377454003)(13464003)(97736004)(106356001)(62236002)(189998001)(4720700003)(44716002)(105586002)(50466002)(66066001)(9686003)(42186005)(25786008)(54906002)(47776003)(61296003)(76176999)(50986999)(81816999)(81686999)(101416001)(68736007)(6486002)(44736005)(93886004)(23676002)(305945005)(1456003)(2870700001)(84392002)(7736002)(4326007)(1556002)(53936002)(229853002)(6246003)(2906002)(86362001)(5660300001)(6496005)(38730400002)(8676002)(6916009)(6666003)(81156014)(33646002)(81166006)(92566002)(14496001)(50226002)(5820100001)(116806002)(230783001)(6116002)(3846002)(110136004)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1564; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTY0OzIzOnMrTXlFTW56TUtsbEVZUTcvV0M0SHZDM0RX?= =?utf-8?B?b3o2dEVIWVcyUjh5ejZEMC90YjJDRXh3VDExczlFc1VqMjNvbHVxamZOanNk?= =?utf-8?B?eEE3c3d5Qjd5MFBPckJiWndBUzJjeVpjdnVsOGJmaGF1ZnlCc2hoRTlEeUEr?= =?utf-8?B?cURZOGNENE1BdXJzMXRaM2poeTB2bmtLd0JIT1FqNXBZU2oybVBkTlVqZXZE?= =?utf-8?B?VkJYNklBNk1nalV1elpOWXZsbUkrYTRLSWZKZkVGY25zMWh1aGVDV1lnbnMv?= =?utf-8?B?dkN6RDFnY0Y5RjMxQzRzM1RROVFYcEVMQ0QwM2V3SzNscmlpUzI0MlAxOHp5?= =?utf-8?B?MTRCT1BIQkF2ejdwbnZGczFkR2MxbEVjT3lrUncxZm5MM2dqTDZmcTdBdm5F?= =?utf-8?B?SHVUSU55Mjk3RzlRbGEvWUhkMFpxZUcrQldOUGVJN01MbnBKN3lVWHRlNFp5?= =?utf-8?B?c3k5bXRlcGRiWkhNNmFKcU42cWkxWWtGa1ZlYXZTWEEvVEdscFduYjFHMXBK?= =?utf-8?B?eEUyck1rVnkrb0ZqU201NjhndXZ0Z3p0QVNsQjlWVU9va3ViQWhhcUk1bWV0?= =?utf-8?B?bklnNGdvaXBvSngxK0NzWGNjNldOc2tDZyt3MGpCY0NWSFZWdTFsN0V2WGpH?= =?utf-8?B?dDJWNVJZOHF6clE1SE5JekE0TjJ2a1RsQ096QStEamRLekh4V3Ruem92SGRW?= =?utf-8?B?dkVaWFF6eXhmSmgrWmpFRDFxNnVBSTZObU5CeFNNbU5YYjE3em41T3NWZFpx?= =?utf-8?B?RGhwNWFjWFZpUUU2alNoQndTOXRPdktTeDFESkNLZGM0N2llekpiNWxPYXN6?= =?utf-8?B?Rld2SEJuSWVadFUvWVBIaHZRcnlEak9ZN2dndXdHdmRZWk5MemtDQXlqYnpS?= =?utf-8?B?aG5HR3lWaFE0TUlraGZpaGxFWDRNRjdrSVdWb2FHU2FFcGdacHlMQ2t3cWJ2?= =?utf-8?B?TTBLcXN6V0ZBTCtyVUNqbS9PeGFSMzhUSGtXWDhRMUJyOGNjL0hBYkxqRFd0?= =?utf-8?B?NWhxQjdKQ2RiZmNmZVFkNlVPcm9qNUllOTBLanlrTjVPVjRoTUFhSGl5QzN6?= =?utf-8?B?bGJrV0x1L25VSXV3SHlWdVNoYXpxUDhuNm4zSjlIY09IN2ROdXNKUnlrRjZ2?= =?utf-8?B?a1cvNVhMV1RkSlNEYUg1K0FCWk0wdXlSQ0NhN0x6L3lXODNhVXM0S0FnRVN6?= =?utf-8?B?NkVpRC9rdGNtY1hVbG9CN0NFR2xZSTFyZGhpRUxNTnpFelVMZE9xNEZFQzJU?= =?utf-8?B?ZFduNVU5Y1lUVTFDU3grR2hQbk9QUFIvbFl1MGUwS2grMDJ1MXA5NVI4TFUy?= =?utf-8?B?UGR5WHJXdDRWanhmSjFwM2R4cm9JL0JydC91YUR6ZVFOZEttNlh3bEpyMmI4?= =?utf-8?B?dDVOK2FGTXh3Qm0rcTZlOHViRElHY2JFOEFyUzBDcVRJQUIzdTZJQVRWdGpE?= =?utf-8?B?NDkzTi9RcGZNdTYwamtxdkY5MzhoYlc4b1V1U3lUTUozdmVmeXhOMVp3eEp1?= =?utf-8?B?bVM1M0llVFEyWEpDUHlxd1EyWGpCOE12TTgzQzZINkFNRTNyRnZqYklUSEVU?= =?utf-8?B?WCtJSFpvdXN5blc4WGhkdkxWaVFWK1ZNVVdSY0N1ZGZaWUpmcGJEbCtpTkJB?= =?utf-8?B?cXZMRkpza1E4VkdpYndmUVE2eXFOKzZmLysvRnY3VGlhZnJjSWVDQlV6Y21R?= =?utf-8?B?WTJ3c1k3eXl1TmhKcXhPWHBsYkNiNm1zT0FEb3ZTTlRxcTY2Y01PUmE3SitY?= =?utf-8?B?bEY5Q3FGbXBPdGVnYVdpZVRSNitHUHNmcCtMdjN6cFBVNW9XN2lzRDBueGkz?= =?utf-8?B?UzVGVzdzd01qMG11YXAzS3lCVFV0UFYwaGoydnBqSVp0anZKa1FpQ2Y4MUxT?= =?utf-8?B?b2tsOWdCY2lWMTNnTzYrTWkrRGJJeSt3ZFBRbnp1ZVdFYWxTR20xNVRKSllC?= =?utf-8?B?NVFxbUhNT2dJcFFoTzNGQ25qUFNlQVNXanRWRXJtN0JEbEd2VDJvVjluNWd2?= =?utf-8?B?SHlVUzd1U1ljc2Q3UXlrZHlDclY0NyswdnJmTjQwWDdjKzUwMXpEeHZaa0gv?= =?utf-8?Q?i5hw=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 6:mOPwE7sAYWSAlLnPAw+RCN2FR+EjuleBHWRKLSMh3c+93I02GDQeqC5YyUrK9FzHyNgj9Vvs7kan44lT6KmjAM3MKzd+s4mYaFH5JSoujYA9aVbNxNlkYMZcvLOczY85nI1+qmZSC/tPDJNePTvJtpZkhPVadmeUYSfUGN3LOB0MLcqSghfkO5D1vSbcjvadcmYMlHuOysVctYOT/TQgkwYSBEUeq00VNSvxRBf12gUlp6YSt7dTWYIpSV+OPTbYfsD6rxyMNnGm7IDBV8YTootoj13yVpF4NR4/FM8wQdZxvlOAAzHP7XwxPo+dRQQ2WeDcJxb+3CzVe0uy/20d0nUqpMDdkMyQiygiC0jt4PkHVQk5KGjpUUlSF/PzJOWHbnfTGCcEgc7UgfEV2nMevQ==; 5:l2o8HGaZUEYDaQGnTCG/h9YwIXTdu3Aga7Ewbcp/Kzo4oegGlWnBm1XoLZ/We05y0j6H4/Pm8RPcvNo2p+nyQtcraBWYqekah57C9XjrF53vKpYqby59aKr61TOXn2hIKlMsUMHVtYp+Z9gUvgKbxEurX5FsiDh04ltwROaxlro=; 24:KytJcV9dh22mu5sS31SUnreVHQiG6PUfN/tcLGV8hfVPT8OPRYXUCQiGh4BJHnwAB5bThw4JSFacB2N2yK012v4eJerY7gUzP84e9v/Bkoc=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 7:ZqoqLmwqUXy+mOllLukjPQQB+HwtmdISrQzqvBMEni8oumtv+jJXbcfQZ2VOtCnlvUWn+OIdSKVUdY7S5aYFpXRmOMLHvShxFJfbxZBQ8P0iAscpq4kqvoHyT75zGZ6JEjcrH981fOiicfJO0+g/M4NCGd66tltwIZsJtGDr6Do3K0imFZWV5jyJDAUZN83rUDF6QL1ROxOYLT5Sa70gT5aPzN6lKPJWEUKjiekWEHo6cNpHIfDfWlflP1AyBjzzO2Eqc2mq2suQcciRfOLlcB/qW7XnQuasox7UzWt1arLsDHh+Ddhwx5Qp/79Z5OrnoFDWmrARlZ9wopQXvUQ+TA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Feb 2017 10:24:09.0632 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1564
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_tbGeKcemaG9dZHqiX3BCqzy4No>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 10:24:15 -0000

----- Original Message -----
From: "Sander Steffann" <sander@steffann.nl>
Sent: Sunday, February 19, 2017 9:48 PM

Sorry, replying to myself. An off-list discussion made me realise I made
an error.

>>> IPv6 unicast routing is based on prefixes of any valid length up to
128 bits [BCP198]. However, in accordance with the reasoning explained
in [RFC7421], the Interface ID part of host interface addresses is
generally 64 bits, with exceptions only provided in special cases
expressly recognized in IETF standards track documents.
>
> Sounds good to me. It's clear on routing, it's clear on IIDs being 64
bits long except in special standards-track cases without trying to
enumerate them and it provides an informational reference to explain why
it should be 64 bits.

I have to clarify this a little bit. When reading it I was focusing on
the "is generally 64 bits" part. In hindsight the exceptions clause is
too strict though. See below for the rest.

>> For my personal part, I’d prefer to see a clear statement here using
RFC 2119 requirements language keywords, but I recognize that consensus
probably requires compromise on that point. Hence, the proposed
refinement above, which does not use RFC 2119 keywords. (Here is how I
would write this with keywords: “IPv6 unicast routing is based on
network prefixes that MAY have any valid length up to 128 bits [BCP198].
However, in accordance with the reasoning explained in [RFC7421], the
Interface ID part of host interface addresses SHOULD be 64 bits with
exceptions only provided in special cases expressly recognized in IETF
standards track documents.”)
>
> I'm a bit worried that the "MAY have any valid length up to 128 bits"
definition is too loose when read by router vendors, but otherwise that
version sounds good as well. I like to see explicit clear guidance in
standards documents.

I like the SHOULD. It allows for exceptions.

<tp>

Sander

Note that 4291bis does not use the language of RFC2119 and does not even
include a reference to it.

This reflects the consensus of the WG; to introduce such language now
would, IMHO, open up another can of worms, of which we already have
quite a few.

Tom Petch

           Such special case are recognised by the IETF and documents in
standards track. Still good. There should be a clear guidelines to
network operators. I have seen too many beginners mess up their
addressing plans because they think they know better.

But on the other hand the text above limits exceptions to ONLY the IETF
standards track, and that is too strong. Operators who know what they
are doing must not be limited.

When writing my previous email I was focusing on giving guidance to
operators, and thinking about inexperienced operators. When I saw that
exceptions were taken into account I thought that that was good, but in
hindsight the exceptions as written are too limited.

So to summarise I think we need to state that in general the IID SHOULD
be 64 bits, exceptions MAY be defined, preferably in IETF standards
track documents, equipment MUST allow operators to use any prefix length
up to 128, and routing MUST support those prefix lengths.

Sorry if my series of messages were confusing. I'm trying to strike a
balance between giving good guidance while allowing well-informed
deviations, making sure that the text doesn't unnecessarily limit
network operators while also protecting users so that ISPs don't start
delegating them /96s "because it's more than enough and the RFC allows
it" etc. (if you think that last argument is farfetched, sorry, I've
seen too many ISPs start from there and only make a more reasonable
addressing plan because the "/64 is the standard", so we shouldn't be
too loose about that)

When reading the different arguments on this list I often find myself
agreeing to most of them, even the conflicting ones, because I
understand where the different viewpoints are coming from. And they are
all important. It's difficult enough to try to fit everything together
in my head, and I hope that this time I did a better job of writing it
down in this email :)

Cheers,
Sander



From nobody Tue Feb 21 04:29:42 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4059129959; Tue, 21 Feb 2017 04:29:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jmOZL532VPwW; Tue, 21 Feb 2017 04:29:39 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00108.outbound.protection.outlook.com [40.107.0.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76493129976; Tue, 21 Feb 2017 04:29:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=9y9lFrbWf+WgicwKiPbNxCuChc4i9sFW4MLECnC8+5M=; b=Ie7aEfHE3rtMzg2J0CAOrIbLgxoboO8zedEr7B1awsFPnPsFM6lemIhtmoHIHYaz31rEWmRC/9sfdhO7w4F0p17PSzXZaV2r+I9pEAeb3MvjEBrg+EXB1Cpw27z/4Ai+Lpy9uslXUFccUPngttO8JuMXxkLV71HpYIs8eQ6AXs4=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Tue, 21 Feb 2017 12:29:34 +0000
Message-ID: <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Date: Tue, 21 Feb 2017 12:25:51 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB6P195CA0024.EURP195.PROD.OUTLOOK.COM (10.171.120.162) To HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13)
X-MS-Office365-Filtering-Correlation-Id: bb80eeac-91b6-450f-e65c-08d45a554b91
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR07MB1563;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 3:M683gHeBMe8GNcgu75zGBEBLBkzZUMC7W+IaryxlxRv/CsJkeoAQlF2RkOrw+mQLzM/QKuBUq6ZQ6VmmIjkNVaJqqx8N6hh0bRXKugTvpSrj15MNWAxHTNdG0Jf2t7veYYlFeqwVPqGQQo36w4xWWSon1X4E2axgTYkeGke4T550LjYdfFrtziWjGl9O6c7y+Wfh6npqZhWMQaZD+36Ne0p7v7RhG9FEeNYV9k3QkbPErB/9XAabaO65vrDHSdGz8+fkUMxZlr8q3NRzHKCqwA==; 25:WoK92t036O541qYRXVN5UVf9IDVoB+8nxJnNyUi7YmY1IwGg7OE4qeouxpLY5GtrdpHL0rM5L37u8giS7EzJmIN39g7bzWMPM66wWC/p9H76LP4rQFnGhU0Z5dxQmjopkRbnjr6Zdz/4xu8rKaxCl8eeYifU36E0lFq1gVyFMFgJX/YShMR3dczRpfiOxiP95/pasF0Lnjwu57JCG1OCGgILfCYegFXs4meulpHTSQ2X4SXZqFoApd+pMApzET8kZq00qmCzzcbee8MUNwvmD6NWnVFhgYNBQjjfiMspzbbDc7VIsePXJo/BlE3IAwV9cGLOXAD6FCXyBKZxeFAaTLhnH5Ij1XE4IEy+FavyOWnro2zyIIC8lSPtaAbvEZvIJB1RitpzI4ZRN5NeaRtbroUhWukd2pfHTOhTdtPlqPGT6vOia7iipYeOQ+SUHF2qd/SoikyBfQQiElw1T+Fhxw==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 31:vZ4qNK0K7uWcYgN5V7CW4XUmwlCV1jsPS4HkgFZSVRPBugMhk25i851z3Vkhgd6tGXorbDUBklnBonkbxgFUevXVMWiZ7ep6lgI2wdWvdiMXrNozpd43lfDcVxtuujo04Rs5fY+zZdaPL1tQ7QomzLc4/o6ScKYaJWySPP9/Gmub3jBR7INf3YmElnsEhZPZn9Bjb8uI1SOWKFX8ZlO/W0aV5+62USAjKAgoapHEM5Ea+uDg24GL9RwbXFxXoxpQQucht7/F4a5o4j8nfOuP+w==; 4:X/WmWxxnz483w6aF9Gms/F+Ck/xx6s6Vv3v7dErzhqmfuYY9w9CNMzixH8upCsa/rqaQ0eurcej8Ml4+9XGlVRVUwve2XpAlcxcXjvlFN7xolAnp55LbsYchnc8LG6ifgXQnwPY8N5of93/viXR4F00j4ohBEZ2IejE3lBBDwTVk7KWOsHp4KbZn9BZJnFm7x0leD4ecwrRiv83Dzj5sdrFX1Ds2LfPGZ7WlPNQg/9mFE3gRAwnv2ARUuK14Exj0Mungcr7BAzGtuLg0peD3NqkNex3XBhlzWYoWi6GodhV5sXWwi/wCO//eADiEns/xvIpdZrwzz6FlE5nXV5sSkeXI7P6CR/5el4l417jF7t6GSk//JmNCPgeDAarcxIdu3cIXInW3H5zWeAhwidaO1/Wkc1bbDjtJaXxlwbKZPIrL2Ct6VMfvvsqkhSozwvz5u4RsszRwyjBNopd+0qKtqWHHxMnJ/niX+CWqxqH+ntwwC+7oGoeKXF/tihIWpuALSW66XOG/j/xbmeSplX+imJN7Q80FHh7vn1P7CF0a7kpRqrcwSlgCczdzL63/Sb+pcNTZ+5/NyjTHeNMX0rrxMZ7dnL/ff3YpFT51gyFvxlfvKbfXC1W6xBSJ5NG6RGW2y4FbP0jC1H0yRG1YHL4GpA==
X-Microsoft-Antispam-PRVS: <HE1PR07MB156397EC8364DBAE9F1A0B2EC6510@HE1PR07MB1563.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(120809045254105);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123558025)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:HE1PR07MB1563; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1563; 
X-Forefront-PRVS: 0225B0D5BC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(13464003)(377454003)(199003)(189002)(53936002)(38730400002)(6666003)(4720700003)(110136004)(50466002)(1556002)(92566002)(68736007)(23756003)(189998001)(229853002)(6916009)(1456003)(6486002)(62236002)(44716002)(44736005)(5660300001)(25786008)(14496001)(66066001)(47776003)(6116002)(3846002)(6306002)(50226002)(230700001)(8676002)(97736004)(54906002)(81156014)(81166006)(2351001)(33646002)(84392002)(4326007)(7736002)(42186005)(6246003)(61296003)(6496005)(86362001)(305945005)(2906002)(116806002)(81686999)(81816999)(105586002)(106356001)(9686003)(50986999)(230783001)(76176999)(101416001)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1563; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; HE1PR07MB1563; 23:BiS2ud09//xaTsDwE299D3OnTyt/rutpCYDN18H?= =?iso-8859-1?Q?5zWH1ZlFXkSvoca7NPmGCG1qdPKamDwHjxT47ZLlcd1/UIZ3V7V55yP7L+?= =?iso-8859-1?Q?eSqpaaxsOdr2RVIk+a3XbpVNkysBPIWNGpp+XOlBLlvnJeYRsEScIMH28W?= =?iso-8859-1?Q?tzfU8AxTxfsfD6iI9oqbftcPTHDpiNDHTQH6f4dOT78+gi0THuirsQl0EG?= =?iso-8859-1?Q?m3pNcGi2uZE4kFO0mH4Ol3lg5ve1JCdgw+o7YZaboyd+tFNfGvqccO/cLe?= =?iso-8859-1?Q?14zDhnhyeCJpdUlkQLQ4iOyunk3qA8R/zQ/sVzvNIV38HBl296ti7Vv5o4?= =?iso-8859-1?Q?+A/YVzvFTX7/TKsOWWnGlt0DLu/7iBs2mkPuN8b7fjkHq/2Aw3+SOts7Cb?= =?iso-8859-1?Q?9F2xL/9E6QwA/45NZLw0ttoW7lsH0OAirw0NJygeNMyQCNI2FrH66rv+9M?= =?iso-8859-1?Q?E1Qp/sh2n6y3VpAxyTTZ2zZAJq/bcYVkX2Fw+bZGHnc6i/bWfw3FbHFQPx?= =?iso-8859-1?Q?newTRiFTu2PpMEUoKceyySF6EOD9885nVeyJGMbCRh44yjfnxoew47XvZx?= =?iso-8859-1?Q?AO8aemmNOsVQ9gEdS1TZUODHTM7HMo5OZEhKygTU6L3Uv/mCTntSZftIPS?= =?iso-8859-1?Q?zPpn5j9YfcnarcZh+2t4et6W3CTNgMrgI4Cc3lO4ztj/ZT5VteuO8XPkr9?= =?iso-8859-1?Q?NccJakQHXja6cN3+arh1UVqRn8yW4JS4w/94CAauIqIIFKgvbkbAuRgyG7?= =?iso-8859-1?Q?ycF1vUcA1whwlqh17H/NJGPArRy2nLE3nc3cifNEdecLxzxRG5FjGiOn49?= =?iso-8859-1?Q?GjGeQNAja5uQwgOI4lCP5Padb7fFqjIHvjiGNnnozFNLTUYaPneuI/QnKZ?= =?iso-8859-1?Q?DvjOrarzP3JYGQ14NNEe5x/OQdx9apqUotlhkMc/LnjHT80Gzn3HNJo6kq?= =?iso-8859-1?Q?efs3vxz1AA25qdKx6pt9CBnA4wIKDfrNKibAkNbW2ltvEAL98xDXdQwC+I?= =?iso-8859-1?Q?o97kZSfEDf6siJLWBRSkMGFqX8t8NfByd9nqa+n7rBGEAb0VHZo5R9HeEq?= =?iso-8859-1?Q?QrOADukUwq/dksqcYaRdc2k61wFxxR7guGm1W8sbSYFIYYToqx6COlIr4l?= =?iso-8859-1?Q?IOjAJBXRXVd8Zft6StiDo4waWCo5N8TZsRVypQlL90tQt+zNWE3vLq9ws3?= =?iso-8859-1?Q?SeKCCmshlnZE3+iwd2HL/jPBRUmf8NWbXswqUoznWOwXK8Xq0CxE4jQmwo?= =?iso-8859-1?Q?NGT3IvL/H9LRomR+Iv2KtG6ozp7/fbrXfo2PuHKcpVXsgGkqj3ABnlJq+X?= =?iso-8859-1?Q?TI+uOhZGeozGhPOy1D5T9WZRj9zcIN45GnolcuHShvuE5VpZkM5qvZqINn?= =?iso-8859-1?Q?+4WTZ8s8BAU4+4cMe1hq/DLarpvm4tOmKuw9u0Gq5ugFDguZ6dh4jzbEhA?= =?iso-8859-1?Q?q7hylQzbWuFIsRp8jrOpHnBhmGdhCB8C/f/2XXJEgt5xJp8UbKn+1fzsJA?= =?iso-8859-1?Q?dIb3XkfZALJORg7Qa88H30Tx2lY2RsUh3LuUPBsSt3WQdYiyBJPhDu+wUg?= =?iso-8859-1?Q?l+wR+he6zpNyt+bMIir+aZkLYQ=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 6:QusCsN/lIEWuwGbaqsbJ+elAYuZCgr3NyRjbcJusgAr+8NARK5M/qbtalc1Omu9zJWBKYiqaxT4jJVKfLwKLmj+/n27H+Z3ubCqRQbB6DqmS3YUbU/OpraOSEECitldUT7xvxp9DFJiAEdWZJJIYeVu74Lyl/3OQp9EhNrRaW66ldxOiFC1HSJUkDzOE7w1bJ0XJigo48+Eo5Bn2ZbYPWHxOfOQOjOdO+rZqdRpGvGEAPn9XKuPVI/TN5ZM4qy148AAC6lvEAOMVbxnI2Gw5ABm/g7leMccOLGCRRCv0PAhFkbBKNFZ6H7IdL0eTd9HTrt6fA9o5QqJrrC6+MU2U39AWdRIetdcmpG6wEh5LrSiHhWk2kuc29/zAojQMhVQnKH3o9ht8AnWkSpY4lcMWmA==; 5:rp0VsBxwgsrWBJ4+TyVRaRNQ3AX7jiGU8T/MM/U6Rtle+MVadu02v5PomRE45np5qHUnMAZxaquQkEv7HAvq8wNJZwZPvNYnxnToFvIlNVvsqgbpjqiq/eUQ6fAaeuKgH/XWH2F+KmrCJJNDyEzJOQ==; 24:72zlLC0ToYRN3CPibCAnG/a/uEKDkauiS3p4HAfO3+6iJ3LSmYauitqehHH41S5PlhmcxPxmmd95rFVFlY0nURqe6MUBwcHjO9CksLB28qc=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 7:tntCthIXIC5WNZb6cbvXwD0/fz7Ud3zl6xPoSerPrAPnvuSB0S9O7WLBAeW9PWIL6wSNx6xDbe0Qnq25ow/ZLxuoAVHalMMa7xR1rsgDukZF8jHs1glXpm4wyZG0wPaoXPVmObrTCe2jcsUhnBVbvwZFe+2QlUvMWJ3bvSUYeLsxLGBWVH7li5mKbwKFJ94jLWdT88kfa1YtlD55uFoyL51kY+FhAHSvsgbE2xHpQyHuKTSON+ftY59oQkt2bjcN9/71/ilTGwhNxTHWN4WOOvhmOJDWIlsC9Ni5lzF9EecZRBk2sCgRM0891PkvhS/PoWngoWyLBcFKZeVYVZDewQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Feb 2017 12:29:34.5559 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1563
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3t55IfxrRFGzMmh0P3dpFTRIqis>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 12:29:40 -0000

I would like to see

Updates RFC3986

on this.

It says
"   discussions of URNs and URN namespaces should be interpreted
   according to this document and not by extrapolation from RFC 3986.
"
which to me says that RFC3986 may not be authoritative for URN and so is
de facto updated.

Tom Petch

----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <urn@ietf.org>; <alexey.melnikov@isode.com>;
<barryleiba@computer.org>; <draft-ietf-urnbis-rfc2141bis-urn@ietf.org>;
<urnbis-chairs@ietf.org>
Sent: Monday, February 13, 2017 3:08 PM
Subject: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform
Resource Names (URNs)) to Proposed Standard


>
> The IESG has received a request from the Uniform Resource Names,
Revised
> WG (urnbis) to consider the following document:
> - 'Uniform Resource Names (URNs)'
>   <draft-ietf-urnbis-rfc2141bis-urn-20.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-02-27. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    A Uniform Resource Name (URN) is a Uniform Resource Identifier
(URI)
>    that is assigned under the "urn" URI scheme and a particular URN
>    namespace, with the intent that the URN will be a persistent,
>    location-independent resource identifier.  With regard to URN
syntax,
>    this document defines the canonical syntax for URNs (in a way that
is
>    consistent with URI syntax), specifies methods for determining URN-
>    equivalence, and discusses URI conformance.  With regard to URN
>    namespaces, this document specifies a method for defining a URN
>    namespace and associating it with a namespace identifier, and
>    describes procedures for registering namespace identifiers with the
>    Internet Assigned Numbers Authority (IANA).  This document
obsoletes
>    both RFC 2141 and RFC 3406.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/
>
> IESG discussion can be tracked via
>
https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/ballot
/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>


From nobody Tue Feb 21 07:12:59 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54C76129C02; Tue, 21 Feb 2017 07:12:58 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7hm0hb8xVaLy; Tue, 21 Feb 2017 07:12:56 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2A701294DC; Tue, 21 Feb 2017 07:12:55 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cgC7Z-000BRj-M9; Tue, 21 Feb 2017 10:12:53 -0500
Date: Tue, 21 Feb 2017 10:12:47 -0500
From: John C Klensin <john-ietf@jck.com>
To: "tom p." <daedulus@btconnect.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Message-ID: <092474D20D151EB6C7C0E280@PSB>
In-Reply-To: <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7dT40TWM2PIaW3PuI2fjZa60uzM>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 15:12:58 -0000

-On Tuesday, February 21, 2017 12:25 +0000 "tom p."
<daedulus@btconnect.com> wrote:

> I would like to see
> 
> Updates RFC3986
> 
> on this.
> 
> It says
> "   discussions of URNs and URN namespaces should be
> interpreted    according to this document and not by
> extrapolation from RFC 3986. "
> which to me says that RFC3986 may not be authoritative for URN
> and so is de facto updated.

Tom,

Speaking as a WG participate, with no particular authority...

I'm afraid my response to this is going to be a lot longer than
"yeah, we forgot that".  We definitely didn't and I hope you and
any others with this concern will take the time to understand
the explanation below (and, if needed, the two expired I-Ds it
mentions) before pursuing it further.

The question of the exact relationship to 3986 has been
discussed extensively and repeatedly in the WG.  One way of
looking at the problem is that it is impossible to define URNs
the way the WG has concluded they need to be defined to meet the
needs of important user communities without pushing a bit on the
boundaries of 3986.  That is complicated by the observation that
3986 asserts that it covers UNRs, makes the distinction between
URNs (of both the "urn:" scheme covered by 2141 and some unnamed
other varieties) and URLs, but then proceeds to talk almost
exclusively about things that look like URLs to at least some of
use, and effectively modifying some things specified by 2141
without updating RFC 2141 (or even mentioning it in the context
of a statement about the "urn:" scheme.

The situation is further confused by disagreement in the
community about whether 3986 is basically a syntax document with
a lot of explanation and examples about what the syntax means,
whether all of it is normative and prescriptive (even though
there are many alternatives for some of the cases), or somewhere
in between.

The WG considered a series of options, including 

 (1) explicitly updating 3986 to point out some of the
	issues
	
 (2) Modifying the scope of 3986 to remove URNs from it.
	
 (3) Taking the position that, since 3986 claims to be
	about syntax and says almost nothing about name-type
	URIs (as distinct from locator-type ones), it was
	reasonable to have URNs conform to the syntax but ignore
	3986 semantics, especially when they appear to be
	specific to the needs of locators.

Of these the first was quickly rejected as out of scope and
possibly out of the core competence of the WG.  There are
definitely people who have participated in the WG (myself
included) who believe it would be desirable to open 3986, clean
up a lot of text, make it actually conform to the ABNF specs,
etc., but who see that as a very different project from the URN
update represented by this document.  The second was considered,
including a draft document (see
https://datatracker.ietf.org/doc/draft-ietf-urnbis-urns-are-not-uris/
) but rejected, I think because it was felt to be too radical
and likely to cause interoperability problems with generic URI
parsers (another issue but off topic for this note).  The WG
adopted a variation on the third.  That model is explained in
more detail in
https://datatracker.ietf.org/doc/draft-ietf-urnbis-semantics-clarif/.


The latter document was allowed to expire after the WG concluded
that it had been useful in facilitating discussions within the
WG and developing the current document but that little or no
purpose would be served by publishing it in the RFC Series.
That I-D, fwiw, did propose to update 3986, but it is not clear
to me that there was ever consensus in the WG for that provision.

So...  While I understand your position, I don't think 2141
alters 3986.  It just uses some terminology and other aspects of
3986 slightly differently than some (but definitely not all)
readers of 3986 have interpreted it.  Some of the language in
2141bis is intended to simply avoid further arguments and lost
time about whether it is completely consistent with 3986 or not.
The sentence before the one from which you quote tries to be
quite explicit about that:

	"... may lead to some interpretations of RFC 3986 and
	this specification that appear (or perhaps actually are)
	not completely consistent,"

In other words, maybe there is a difference, maybe there isn't
(and different people have reached different conclusions) but,
if you think there is, use these definitions.

That would call for "some people think this updates 3968, some
think it is consistent with it" and "Updates: 3986 (maybe)".
There is no provision for the latter in RFCS and the former
seems more abrasive or critical of 3986 than is appropriate.

I hope we can avoid reopening this topic.  Discussions of it
tend to be very painful and to expose what appear to be a lot of
raw nerves.  If there does need to be an "updates" statement, I
think the reasonable way to do it would be to put
draft-ietf-urnbis-semantics-clarif back on the table because it
actually explains the relationship while simply adding an
"updates" line to 2141bis might actually add to the confusion
because it would not provide that clarity.   Speaking very
personally as an overextended editor, I hope that isn't
necessary either.

best,
    john


From nobody Tue Feb 21 07:38:21 2017
Return-Path: <barryleiba@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8026E129C34; Tue, 21 Feb 2017 07:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sNeVd-lLgSsQ; Tue, 21 Feb 2017 07:38:14 -0800 (PST)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::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 97B03129C2A; Tue, 21 Feb 2017 07:37:50 -0800 (PST)
Received: by mail-it0-x236.google.com with SMTP id 203so113109138ith.0; Tue, 21 Feb 2017 07:37:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r3mvQ5X8vaQx8dcjwFwTXZdC2p0i1jkPa8hv3djfSyE=; b=YM4YdnohUX2yOtY151d0hFj55PEa3r5ECbJGgFfPHVgt0agNh1p0oeIQob9Ij0fINH fOUiTQNU+cABEnR0KVQZE+dMBok5HhH3zJjMOkzo/nhixs24nAdSu2n3T+DpGD5GjZaS cYu06mRiuxS33TIYhX49Rkn9cc+tYN+/ivMZsUJJhIYuvdkSv+mpeMNtPeCQt62D9YKD SYFh8iTipdsgQ25JygVPpcJce0v6q4mbnGAx1XhBN3ctcQ6zdpgQTYlsjy6vuivLhhDv KhyK8K3hk8lbsEG0z4+EE829u1QhwZF8Ivg0QqjRlNKQgROda4lE3dkcoyRQpsfwkcYd 0I/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r3mvQ5X8vaQx8dcjwFwTXZdC2p0i1jkPa8hv3djfSyE=; b=IphpVzUNZTqT+WqTm75jYbTPVi3My9LcvE7b2cKXeoQH19SoE/RHCjXh0NYq9CNJF6 Tf5nY/u/l9pR+u3RlOxCLIThwImhahPYjLhMuwpL9M4OQxxb62ca1PXpZXMVWNXzW0kV Y0yOkczrmJo+dTGVMG2jG/ThKtmd20Ub5nsPT25ECP8DIR223Q8hX/eMQgQn28NlNa/G +pmNL/lAX3CYPO76Q6aw/13VnFhHkZSeAuMUK3kyg+JuE08qgXvbK+qbyXggn+5Mmd9l ts25I3O+oO5RKWFD7a+q2Lijv05DatxKxzoY5P/xGaNs07kI7xDeLziiNULulBGScGGt ygng==
X-Gm-Message-State: AMke39kf3ZXRC3y4N1wPHxgVp58RN08N9WojDlRTan0aapOuO0ywUrDPvb79BJlUgX8+nqfBQVpIhCmf0Gmnug==
X-Received: by 10.107.20.84 with SMTP id 81mr20285239iou.145.1487691431117; Tue, 21 Feb 2017 07:37:11 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba@gmail.com
Received: by 10.107.34.14 with HTTP; Tue, 21 Feb 2017 07:37:10 -0800 (PST)
In-Reply-To: <092474D20D151EB6C7C0E280@PSB>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 21 Feb 2017 10:37:10 -0500
X-Google-Sender-Auth: 1S20_AGtO3az_QYFLXMDqlysyAU
Message-ID: <CALaySJLdDAC86FTu26QtBpAeJUhcoDcV000y_73B7_3B3WAOnA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Jp08SL8MQ-Rz1-R7mLc3aMVxd0k>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, URNBIS Chairs <urnbis-chairs@ietf.org>, IETF discussion list <ietf@ietf.org>, draft-ietf-urnbis-rfc2141bis-urn@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 15:38:16 -0000

Adding to what John said, and also narrowing to a key point...

Narrowing:
This point was discussed in the working group, and I believe we do not
have consensus to use "updates" here with respect to 3986.

Adding:
That said, I think it's important for readers of 3986 who are
interested in URNs to come here.  The "updates" metadata would do
that.  Happily, we have even more targeted metadata that will do it
better.  3986 says this in Section 1.1.3:

   The term "Uniform Resource Name"
   (URN) has been used historically to refer to both URIs under the
   "urn" scheme [RFC2141], which are required to remain globally unique
   and persistent even when the resource ceases to exist or becomes
   unavailable, and to any other URI with the properties of a name.

Anyone interested in URN is already told that 2141 is the place to go
to read about those, and the metadata for 2141 will clearly say that
this document obsoletes that one.

So I think we're covered just fine here.

Barry, WG chair

On Tue, Feb 21, 2017 at 10:12 AM, John C Klensin <john-ietf@jck.com> wrote:
> -On Tuesday, February 21, 2017 12:25 +0000 "tom p."
> <daedulus@btconnect.com> wrote:
>
>> I would like to see
>>
>> Updates RFC3986
>>
>> on this.
>>
>> It says
>> "   discussions of URNs and URN namespaces should be
>> interpreted    according to this document and not by
>> extrapolation from RFC 3986. "
>> which to me says that RFC3986 may not be authoritative for URN
>> and so is de facto updated.
>
> Tom,
>
> Speaking as a WG participate, with no particular authority...
>
> I'm afraid my response to this is going to be a lot longer than
> "yeah, we forgot that".  We definitely didn't and I hope you and
> any others with this concern will take the time to understand
> the explanation below (and, if needed, the two expired I-Ds it
> mentions) before pursuing it further.
>
> The question of the exact relationship to 3986 has been
> discussed extensively and repeatedly in the WG.  One way of
> looking at the problem is that it is impossible to define URNs
> the way the WG has concluded they need to be defined to meet the
> needs of important user communities without pushing a bit on the
> boundaries of 3986.  That is complicated by the observation that
> 3986 asserts that it covers UNRs, makes the distinction between
> URNs (of both the "urn:" scheme covered by 2141 and some unnamed
> other varieties) and URLs, but then proceeds to talk almost
> exclusively about things that look like URLs to at least some of
> use, and effectively modifying some things specified by 2141
> without updating RFC 2141 (or even mentioning it in the context
> of a statement about the "urn:" scheme.
>
> The situation is further confused by disagreement in the
> community about whether 3986 is basically a syntax document with
> a lot of explanation and examples about what the syntax means,
> whether all of it is normative and prescriptive (even though
> there are many alternatives for some of the cases), or somewhere
> in between.
>
> The WG considered a series of options, including
>
>  (1) explicitly updating 3986 to point out some of the
>         issues
>
>  (2) Modifying the scope of 3986 to remove URNs from it.
>
>  (3) Taking the position that, since 3986 claims to be
>         about syntax and says almost nothing about name-type
>         URIs (as distinct from locator-type ones), it was
>         reasonable to have URNs conform to the syntax but ignore
>         3986 semantics, especially when they appear to be
>         specific to the needs of locators.
>
> Of these the first was quickly rejected as out of scope and
> possibly out of the core competence of the WG.  There are
> definitely people who have participated in the WG (myself
> included) who believe it would be desirable to open 3986, clean
> up a lot of text, make it actually conform to the ABNF specs,
> etc., but who see that as a very different project from the URN
> update represented by this document.  The second was considered,
> including a draft document (see
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-urns-are-not-uris/
> ) but rejected, I think because it was felt to be too radical
> and likely to cause interoperability problems with generic URI
> parsers (another issue but off topic for this note).  The WG
> adopted a variation on the third.  That model is explained in
> more detail in
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-semantics-clarif/.
>
>
> The latter document was allowed to expire after the WG concluded
> that it had been useful in facilitating discussions within the
> WG and developing the current document but that little or no
> purpose would be served by publishing it in the RFC Series.
> That I-D, fwiw, did propose to update 3986, but it is not clear
> to me that there was ever consensus in the WG for that provision.
>
> So...  While I understand your position, I don't think 2141
> alters 3986.  It just uses some terminology and other aspects of
> 3986 slightly differently than some (but definitely not all)
> readers of 3986 have interpreted it.  Some of the language in
> 2141bis is intended to simply avoid further arguments and lost
> time about whether it is completely consistent with 3986 or not.
> The sentence before the one from which you quote tries to be
> quite explicit about that:
>
>         "... may lead to some interpretations of RFC 3986 and
>         this specification that appear (or perhaps actually are)
>         not completely consistent,"
>
> In other words, maybe there is a difference, maybe there isn't
> (and different people have reached different conclusions) but,
> if you think there is, use these definitions.
>
> That would call for "some people think this updates 3968, some
> think it is consistent with it" and "Updates: 3986 (maybe)".
> There is no provision for the latter in RFCS and the former
> seems more abrasive or critical of 3986 than is appropriate.
>
> I hope we can avoid reopening this topic.  Discussions of it
> tend to be very painful and to expose what appear to be a lot of
> raw nerves.  If there does need to be an "updates" statement, I
> think the reasonable way to do it would be to put
> draft-ietf-urnbis-semantics-clarif back on the table because it
> actually explains the relationship while simply adding an
> "updates" line to 2141bis might actually add to the confusion
> because it would not provide that clarity.   Speaking very
> personally as an overextended editor, I hope that isn't
> necessary either.
>
> best,
>     john
>


From nobody Tue Feb 21 08:27:21 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82B5D1294C4; Tue, 21 Feb 2017 08:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level: 
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bHq25gM6UkWQ; Tue, 21 Feb 2017 08:27:18 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0134.outbound.protection.outlook.com [104.47.1.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4834129512; Tue, 21 Feb 2017 08:27:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eZb68QxhhnGIabASFQ0etjZf01avobMMh08ZaXWEzhA=; b=XRgmPgc1i6EaYrZ1hdGIaAHNlhg8c7d2kxZk6rZjLHAdlZxPJ6J9uAUQJNY4ng9UtP4E6yQ6Dwy5O33EVKQOj9NGyubTICVdFeGw1Sk06NqjDdgFrflGvXfQldKLGsPf1Uk+MpXQVgT409yGDlPcu64CI9DvtYzwAXh0G47jYU8=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Tue, 21 Feb 2017 16:27:13 +0000
Message-ID: <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: John C Klensin <john-ietf@jck.com>, <ietf@ietf.org>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB>
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Date: Tue, 21 Feb 2017 16:04:31 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB6PR0701CA0041.eurprd07.prod.outlook.com (10.168.7.179) To HE1PR07MB1563.eurprd07.prod.outlook.com (10.169.123.13)
X-MS-Office365-Filtering-Correlation-Id: 011b512c-e6ff-4931-22fc-08d45a767ee7
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR07MB1563;
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 3:j0W0FaMSYaQz2z+3WCmCIRyQtuulDoP8oWmX35cjJOyg+B8u4L2e4y1qFFaFA2pT/PbsJ/3xC5N7YuPV9OeZoDppU2SIm0FJDWdovWS8/g3c/YXAquMVVijmSTxCEjNo5+qfjoo4EGUI9ZBKyS7+gTKUepnVqeMWXXqbnzD7UuxfcefgOXxl1SgmPT6CKLKodkaYqYB3O8c6ukTPa+zSbToHbgdC42+RrhlESOPNWRww0xup6WSw0pDnO8e5FVvMFnPXI1zpx9L63TTtkI/oEQ==; 25:CSBtrEW510c1f8kv505YbBhGP2g6E9rNLHuCgu9cUHLhxDq6UPzWxXau1pQOZ8365AUfbR4aX19EsVatsz+NMguv57GnsGqUDsuTwub2mJCvnFWZkgDDbF9hU3s0JjXeTI1It2xK58+559vJkyACgx5EQ6GZUsaJp7VWkuzgZYArFF+VMf3hGBcKUERfSurT5cU6cdkXSzue70EAiFzI32USq/IuCgJdstYfCu1Loc+q2ggtFd0seQDHJ5YJmYAkvBitXIDp1h+74K7Bg1diWVacrMEO66oXKbYTIa+XZDBd5nPAR9T9h//bvKOWVDyd9ObooqnroPtRLSAYuDNtTbMdB/NwYfeNqCmwRfcxOWAemCKV2UIHJRAEIQsl3WEOktPhS+0koWZSLobep6W5II0U8B2yCn7vdSVssE2L8UJhFBDJiL19qNl7HwswuLgJN4EWPm87JQ6ucGlCjSKQkg==
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 31:PDHa1KYU2Z8urwPOwONiuwlF9EEYk/D/6tV1VsPmakbOgnyflWSVwKmvkhs+VWMBn3tUFxXSV5IjNHkoKuaZCHxIZJKdlf8s/GWAymCbCR7bnoyeTqyKkAfsk5/ybkkXgQaYNO0LKtimaCqlZxUsgIP55KfVDyEKh5IWX94/o+zWkS+e/7TYPetSt6Yi/EogFBz7jYk/d/3TT+T9wR3tAeF64NKAeOIe8Cajv+1RV2ayL0ww5BUPxWiPC+39JZtA2c2inoclKgAwl6TTzxKq6g==
X-Microsoft-Antispam-PRVS: <HE1PR07MB1563A2424FC7580ED1891B5AC6510@HE1PR07MB1563.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(178726229863574)(120809045254105)(100405760836317); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6041248)(20161123558025)(20161123555025)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:HE1PR07MB1563; BCL:0; PCL:0; RULEID:; SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 4:e7yvK2lCeKB+/CMfZwSBGqkt6ErL/UxhX20SyDn56dm4zo8XgC4z/VqSHihR3nTI1l6FFhzHdj+cYtfwD2yU7f23fyQWFytSFl0nb4ypY5RYENnZzHDVXkZFE8A2lNJv6jS+Qc00oSvsk+mcBQt+FY1dLeceq7fsNEfrI3EsPCsPQP6Z1muCnbc6Q1yaf2ytTE2Y4tHj05AL1UpwTE4iAuB+d839MkAGzM+4rjzFfe8opmJ+v5wllDOAzcFjzkLBN015IdYdmVoWup+yuDf+0Mje9EZ3nRtJrwH/FZDqCO5Pi7skJE5DQwXgALvW6RiHcmXeiCoTFX504dw9C0XH/wqawMoyHFq4MSSExxCXBJ8axuXLDGJHTCbn20kskdOIvjNnVA+VAZEsY7H9+geUOO0JshWi8ZfFWDcpH4UY5gRUj5Ps4mpxFVmFqYh/bl8odcZ9w6E71Uq0bTjhXsUyJGuNaWyygWJoFF27UxY6OfNmd7t2yllPbQItSTd4CRKf3tjwadZCBn4Is2yP2REUndE7NpPzy6P0Zl40EzcmUtP+AT7Wk20vTjKwhceCXuXm8IRFoHKhYYA6CRznEq17iXPqs91rrg+0ZOsselvYrY2xLMBe5POUheeg/9akAfu02oG+9XyLFLuOb00x0LG5RZ4O/8CdpoBnOu7X2hfyWiYmeJITRRM4uNYH/fJiykzUL5szo5eZCHhs/nND7wytRXm6eWEfjkO6o+Z3D08CxMo=
X-Forefront-PRVS: 0225B0D5BC
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(979002)(6009001)(7916002)(39450400003)(24454002)(13464003)(377454003)(199003)(189002)(53936002)(4720700003)(6666003)(38730400002)(50466002)(229853002)(1556002)(68736007)(92566002)(23756003)(189998001)(6486002)(44716002)(62236002)(5660300001)(25786008)(44736005)(66066001)(14496001)(1456003)(47776003)(6116002)(3846002)(6306002)(50226002)(97736004)(8676002)(230700001)(54906002)(81156014)(81166006)(33646002)(6246003)(61296003)(6496005)(305945005)(7736002)(86362001)(42186005)(2906002)(4326007)(84392002)(81686999)(116806002)(81816999)(105586002)(106356001)(50986999)(9686003)(76176999)(230783001)(101416001)(74416001)(7726001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1563; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; HE1PR07MB1563; 23:APX4lTx/1a/nFirQhTNHvV7QhUuhG1pn2Tbfvx+?= =?iso-8859-1?Q?N2VDFM4Pltttg4CTFqWjfFelTqKiSl7JLBm/ayqVEw13Ymq1cop3Qi5Nvj?= =?iso-8859-1?Q?+hxhu4WKPSfpedULZ+P+oXNlcBUiDryDoD+osI8vSYK4wpToocX41d6lHo?= =?iso-8859-1?Q?BhiFI+f7vUuPEEjdxU8BnmljQu5du9eQz63/51vfCL7bxy0Ow9Fe+9FxoE?= =?iso-8859-1?Q?Zq4Yak932hXonSs3W/s+WmekoAXhbVsYp3RqKI7vjJQgXy/by0x29j2u57?= =?iso-8859-1?Q?w5RQ78B2q40IHsYYy1UhTPWB1THnBFmjWmcId0B7sNdohziF/JtdBpEcE1?= =?iso-8859-1?Q?0JwFNsBLjpRVwAYmpw9U5RH/4VhrSeOytjUii/PmFvNLenBKhrdygGdyDC?= =?iso-8859-1?Q?eOm+NFPL7oYWJkKsc22zrtlvSmzEG6RbcxIrWTAfJKQyuzQaPdZZC7wN7m?= =?iso-8859-1?Q?KvDKheYWaHtuh0Z4BKcODbGOFJiCU4cBZDwEonCNQvPskMW+gdg86KJALk?= =?iso-8859-1?Q?7UEGc7Cas+/sgRbEJWwqn4e4rj73Qzxjam6KyJpWCKq8TneHRaS3f01W8+?= =?iso-8859-1?Q?no/WD3d/i3s5OeYw5yd+WBVI5idJ292WvMdmJS6jJLBYJkP5e91YUGeGGA?= =?iso-8859-1?Q?riyqmuyKjqlmZANrRmzNPIhV4ZTU7y6GIid7Px9xMD9MiwTYkcTPMuwfro?= =?iso-8859-1?Q?FlrgIqCG2+gCpnLWqgwoo7hJOytO3/IcDfeC/oK4DsfR5joEgd9z7akZws?= =?iso-8859-1?Q?gyDpmJUUgApxdekRIferesd5I9xhsl/wjGCTagPz/KplsXdCDUdI38gGAd?= =?iso-8859-1?Q?rkCrbpaJ5XMtQHQR6M9MoWB9/JbwpfgrMH4xX3wqL3hgJ5P7sk51i2Cf/T?= =?iso-8859-1?Q?4Q8DkYldjGZu6slLsnJtdncmzGJlS0/RXpJtag//YatmldW7Uc6cDSfGBn?= =?iso-8859-1?Q?2NdGd1DYqlQk0xNQCfg4vNKH7AsBkhAFwqxttxXMfD87wFAiYm+MA9k8Qc?= =?iso-8859-1?Q?rZ9vWMxJqpcHk1r5OLLyh9XFnciMepbA890zDb5Hx3Bei4kAsgwFCvtL9w?= =?iso-8859-1?Q?T4OgYsCemR6QW9roNL6pMb2+3zOk8ASAETHtAQvG2Y1EG1lZDw7kR3sPgc?= =?iso-8859-1?Q?Fjc39bF1n8DZnOQlq+qaolGvqw3oguo6G8wd9y/IHFsYu6RYVH7VM9xb+A?= =?iso-8859-1?Q?g9AnurujdTz87VYGEyrGB53kN3R7Uwija2k+w48qWAQypF22VGiNPF2LPN?= =?iso-8859-1?Q?EXPkTe+4D4CwujmrI5738+BKt+YiaI4ZVosqqmmu3e642I1ZXNPqcTngG7?= =?iso-8859-1?Q?Tu9BXBzwDvaSIUi9b+uvn3SLL9WJBoGumPHmveWvpcGR1XlEd8Mg7ndZv3?= =?iso-8859-1?Q?Vj5ZKUmATt76MT2so6eAJsW1keYrVcoanQPmBrmqqQBqCio/DYVyP1rApN?= =?iso-8859-1?Q?/8h0RAreGdj/kj/LjjJW+SPCL960IOb2qwJP1WYpStqGXcg8JwcXdPvMDY?= =?iso-8859-1?Q?xAsud4umksf36cvoEDPHoM+IC/aNhxBSl1RmRJ0+GOv8b77lZJRZ/moc+H?= =?iso-8859-1?Q?OWyBWUUNtcc22tTg3KoZzftiILzAQW/gXx1fK+YVxwDhO4NPgi0ujVCPSK?= =?iso-8859-1?Q?lv+DCRNygSg=3D=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 6:DNUvaxAbQv2fVZHFVFMkVhRZMvgldV93oel8131IviIbLKiCldwtzzc0wUM/RqdnejX8jBDC9jxGQoNl12ColXue+BCf94Tw+d0bSi3QqeTmhIfhrPGuXyFpInzZbydF7QlOlU4EicWdipsUgserJ5rL/gbDSAtjZPc6r4+VR8nLnV+z1nhHpnbpKQaEpBKZKosigUpizs+qcy2ytmGlk2JSZedTABMNhFrQOhlAV+dksfLoM93CRrRieWhq9B36VFyM8DTER3wKWkxoJNQ8X27sr0yQEZRlqoj9p5ob8rhr6EOkdd8xx3/AEBuRFzRdHogFiozP2Kw8dxvsoGo8eMtxiIm8l7GDgM+vl65CKQUd4RtFo8VdeLdw1XAdUFj8AlHl50O5XW/PIjtd+QugPg==; 5:5vn1bAWnM3KvYYeQ3Gw5ZFt+MJvzOxmDWp9EhjcVC05ddHuC3/up6LNxwekIwt7+7HAdJ7B8bpFEl1MEZcF9hPrkIvCg7Lq1sJ4QiSzz6wh9yY+BO8JNvU4B+/4CJmsVZgPqAhj2iDKKCjhvLrEfyPwDoDnGKqEUsr94MfrfEXU=; 24:HXYKpADkRZuxjC69H3WUVaTVSqjY9BqRXKswQqIE78rnPvITlAYS55I5G4wXzp+FsKPSE7EENCTPAYmE5pfi8Pr14mW/TcH3H4kLykNX680=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 7:f7RFPWtuDK4qVQ3bmtSA7EYmqjJdyk2qgWU8JPZp5sWOkAqVAUNqWkbreYFkJsbbwQJ4TnCMa8cCmpozdk/6Mc2cze+Co4g9F2Ij438RYK5r+e750nw+aMPeKfFjhnHZV0v3S7+hS24AkNeslB6GK9MSHFy5IzWkDTX6KgXqxdFAQRJobqVSH5WIrQCCMHKtXqsKKOGwGy1FL211t73ywGALWyx4PDYeciHFhJpEAOR3xeb4DVwsTboNdTEgRRCytn94kt365Ih4NXfXt99ct1X5egaiswEmEoWxB7dK7McoNWtfK4I18hQbR9Aodt3Ue3DsdnRCnulKffnboWVxEA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Feb 2017 16:27:13.9013 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1563
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0n7dvdJogK66AAmS0j01eTwfUSA>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 16:27:20 -0000

OK on 'Updates'

Meanwhile,
s.2.2 'the basic Latin repertoire [RFC20] '
I don't know what you mean - RFC20 does not use the term 'Latin
repertoire' and, being European, I tend to think of the Latin repertoire
as being the 160 or so characters of the Belgian language.

I think you need to specify the code points here.

Tom Petch

----- Original Message -----
From: "John C Klensin" <john-ietf@jck.com>
Sent: Tuesday, February 21, 2017 3:12 PM


> -On Tuesday, February 21, 2017 12:25 +0000 "tom p."
> <daedulus@btconnect.com> wrote:
>
> > I would like to see
> >
> > Updates RFC3986
> >
> > on this.
> >
> > It says
> > "   discussions of URNs and URN namespaces should be
> > interpreted    according to this document and not by
> > extrapolation from RFC 3986. "
> > which to me says that RFC3986 may not be authoritative for URN
> > and so is de facto updated.
>
> Tom,
>
> Speaking as a WG participate, with no particular authority...
>
> I'm afraid my response to this is going to be a lot longer than
> "yeah, we forgot that".  We definitely didn't and I hope you and
> any others with this concern will take the time to understand
> the explanation below (and, if needed, the two expired I-Ds it
> mentions) before pursuing it further.
>
> The question of the exact relationship to 3986 has been
> discussed extensively and repeatedly in the WG.  One way of
> looking at the problem is that it is impossible to define URNs
> the way the WG has concluded they need to be defined to meet the
> needs of important user communities without pushing a bit on the
> boundaries of 3986.  That is complicated by the observation that
> 3986 asserts that it covers UNRs, makes the distinction between
> URNs (of both the "urn:" scheme covered by 2141 and some unnamed
> other varieties) and URLs, but then proceeds to talk almost
> exclusively about things that look like URLs to at least some of
> use, and effectively modifying some things specified by 2141
> without updating RFC 2141 (or even mentioning it in the context
> of a statement about the "urn:" scheme.
>
> The situation is further confused by disagreement in the
> community about whether 3986 is basically a syntax document with
> a lot of explanation and examples about what the syntax means,
> whether all of it is normative and prescriptive (even though
> there are many alternatives for some of the cases), or somewhere
> in between.
>
> The WG considered a series of options, including
>
>  (1) explicitly updating 3986 to point out some of the
> issues
>
>  (2) Modifying the scope of 3986 to remove URNs from it.
>
>  (3) Taking the position that, since 3986 claims to be
> about syntax and says almost nothing about name-type
> URIs (as distinct from locator-type ones), it was
> reasonable to have URNs conform to the syntax but ignore
> 3986 semantics, especially when they appear to be
> specific to the needs of locators.
>
> Of these the first was quickly rejected as out of scope and
> possibly out of the core competence of the WG.  There are
> definitely people who have participated in the WG (myself
> included) who believe it would be desirable to open 3986, clean
> up a lot of text, make it actually conform to the ABNF specs,
> etc., but who see that as a very different project from the URN
> update represented by this document.  The second was considered,
> including a draft document (see
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-urns-are-not-uris/
> ) but rejected, I think because it was felt to be too radical
> and likely to cause interoperability problems with generic URI
> parsers (another issue but off topic for this note).  The WG
> adopted a variation on the third.  That model is explained in
> more detail in
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-semantics-clarif/.
>
>
> The latter document was allowed to expire after the WG concluded
> that it had been useful in facilitating discussions within the
> WG and developing the current document but that little or no
> purpose would be served by publishing it in the RFC Series.
> That I-D, fwiw, did propose to update 3986, but it is not clear
> to me that there was ever consensus in the WG for that provision.
>
> So...  While I understand your position, I don't think 2141
> alters 3986.  It just uses some terminology and other aspects of
> 3986 slightly differently than some (but definitely not all)
> readers of 3986 have interpreted it.  Some of the language in
> 2141bis is intended to simply avoid further arguments and lost
> time about whether it is completely consistent with 3986 or not.
> The sentence before the one from which you quote tries to be
> quite explicit about that:
>
> "... may lead to some interpretations of RFC 3986 and
> this specification that appear (or perhaps actually are)
> not completely consistent,"
>
> In other words, maybe there is a difference, maybe there isn't
> (and different people have reached different conclusions) but,
> if you think there is, use these definitions.
>
> That would call for "some people think this updates 3968, some
> think it is consistent with it" and "Updates: 3986 (maybe)".
> There is no provision for the latter in RFCS and the former
> seems more abrasive or critical of 3986 than is appropriate.
>
> I hope we can avoid reopening this topic.  Discussions of it
> tend to be very painful and to expose what appear to be a lot of
> raw nerves.  If there does need to be an "updates" statement, I
> think the reasonable way to do it would be to put
> draft-ietf-urnbis-semantics-clarif back on the table because it
> actually explains the relationship while simply adding an
> "updates" line to 2141bis might actually add to the confusion
> because it would not provide that clarity.   Speaking very
> personally as an overextended editor, I hope that isn't
> necessary either.
>
> best,
>     john
>


From nobody Tue Feb 21 09:28:16 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B62C129533; Tue, 21 Feb 2017 09:28:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 2mR3FlzCgdkZ; Tue, 21 Feb 2017 09:28:10 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 7FDF212952D; Tue, 21 Feb 2017 09:28:10 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgEEL-000EPp-IQ (job@us.ntt.net); Tue, 21 Feb 2017 17:28:10 +0000
Date: Tue, 21 Feb 2017 18:27:39 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221172739.GT84656@Vurt.local>
References: <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HsNDGHXCULXZh2c-p1U0xvGYseI>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 17:28:11 -0000

On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
> On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
> > ps. The "Write a draft" argument is weak at best, since we are
> > already are discussing a draft (called
> > 'draft-ietf-6man-rfc4291bis-07.txt'), which is in IETF Last call,
> > which means it is in a place to discuss the contents of that draft.
> > No reason to kick the can down the road.
> 
> I'm sorry, but that's really how it is. The text you dislike has been
> the standard for almost 20 years, and is it inappropriate to change it
> in the context of reclassifying this document from draft standard to
> Internet standard.

Or, perhaps it is inappropiate for the -bis document to target "Internet
Standard" classification at this moment? ¯\_(ツ)_/¯

Especially when solidifying recommendations in an architecture Internet
Standard-to-be, the utmost care should be taken to verify whether the
paper reality (RFCs) and operational reality (what people do, for
$reasons) are aligned.

In those years sufficient data has been collected to conclude that /64
is not the "be all and end all". The current paragraph does not account
for staticly configured environments in which SLAAC plays no role.

Perhaps the following suggestion bridges the gap.

-------

OLD:
   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
   on inter-router point-to-point links.  However, the Interface ID of
   all unicast addresses, except those that start with the binary value
   000, is required to be 64 bits long.  The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421]

NEW:
   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface ID
   of unicast addresses is required to be 64 bits long. In other use
   cases different prefix sizes may be required. For example [RFC6164]
   standardises 127 bit prefixes on inter-router point-to-point links.
   For most use cases, prefix lengths of 64 bits is RECOMMENDED, unless
   there are operational reasons not to do so.

OLD:
   As noted in Section 2.4, all unicast addresses, except those that
   with the binary value 000, Interface IDs are required to be 64 bits
   long.

NEW:
    *delete, its superfluous*

-------

Kind regards,

Job


From nobody Tue Feb 21 09:40:59 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9415B129485; Tue, 21 Feb 2017 09:40:57 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 RjjJLe77u0Xc; Tue, 21 Feb 2017 09:40:56 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5CCAD12943D; Tue, 21 Feb 2017 09:40:56 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cgEQo-000Bdw-OD; Tue, 21 Feb 2017 12:40:54 -0500
Date: Tue, 21 Feb 2017 12:40:48 -0500
From: John C Klensin <john-ietf@jck.com>
To: "tom p." <daedulus@btconnect.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Message-ID: <00068EB71CB3F63F36092E69@PSB>
In-Reply-To: <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB> <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WXTDI0X_B-MLtmsGiD_HgdgzBzg>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 17:40:57 -0000

--On Tuesday, February 21, 2017 16:04 +0000 "tom p."
<daedulus@btconnect.com> wrote:

> OK on 'Updates'
> 
> Meanwhile,
> s.2.2 'the basic Latin repertoire [RFC20] '
> I don't know what you mean - RFC20 does not use the term 'Latin
> repertoire' and, being European, I tend to think of the Latin
> repertoire as being the 160 or so characters of the Belgian
> language.

Mea cupla.  I knew that unqualified reference was going to get
us into trouble and let it go.  Whether you (and future readers
of 2141bis) should have known this (European or not) is
debatable,  but "Basic Latin" is a term of art in
internationalization work and "repertoire" keeps us away from
debates about particular coded character sets, encodings, etc.,
and, in particular, avoids confusion with %-encoded arbitrary
Unicode characters (see the introduction to Section 2) which are
certainly still ASCII characters.  The definition of "basic
Latin repertoire"  is more or less equivalent to "undecorated
Latin characters", but that terminology raises other issues...
to the point that I'm tempted to say "can't win no matter what
one does".    

Personally, I've always objected to "Basic Latin" because
several characters we consider to be part of the repertoire
today (e.g., "w" and distinct "j" and "u") were late additions
and would not have been part of the writing system as distinct
characters for writers of Latin in the time or, e.g., Virgil.
But that argument was lost long ago and "basic Latin" is the
prevailing terminology today.

> I think you need to specify the code points here.

I think that would cause confusion with syntax rules that
specify what is possible.   The paragraph in which the phrase
you picked up simply imposes a "SHOULD NOT" restriction and
explains why it should be adhered to when possible and what the
exceptions should be. It really clarifies and is perhaps
partially redundant with the previous paragraph.  How would you
feel about making the phrase something closer to "the basic
Latin repertoire, i.e., the letters and digits of ASCII as
described above" and moving the RFC 20 citation to the first use
of "ASCII" in that previous paragraph?

Other textual suggestions welcome but, again, I think listing
code points would cause confusion with the formal syntax for
<namestring> and some of the carefully-constructed language
around it.

     john

p.s. personal note: 2141bis has either the advantage of, or
suffers from, the fact that Peter and I have been immersed in
internationalization (i18n) issues for the last several years
with various involvements in PEECIS, IDNA, SMTPUTF8 ("EAI"), and
other efforts.   That has probably resulted in our trying to be
a little more precise in this draft than many IETF documents
about URI schemes and naming and perhaps, as in this case,
having slightly higher expectations about community
understanding of those issues than might be the case.  I think
that precision is an advantage and hope that community knowledge
and understanding will gradually improve.   YMMD, but I hope
than anyone who is actually inclined to advocate for less
precision (you have not) be careful about any advocacy, even on
a diversity basis, for IETF consideration of writing systems
that cannot be expressed in ASCII and/or any language other than
English.
 


From nobody Tue Feb 21 10:08:42 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 478F212951E for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 10:08:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 V7l5mI8n373A for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 10:08:40 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 518D412949B for <ietf@ietf.org>; Tue, 21 Feb 2017 10:08:40 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 4359544107; Tue, 21 Feb 2017 18:08:39 +0000 (UTC)
Date: Tue, 21 Feb 2017 18:08:39 +0000
From: heasley <heas@shrubbery.net>
To: "C. M. Heard" <heard@pobox.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
Message-ID: <20170221180839.GM6787@shrubbery.net>
References: <CACL_3VEykmViHpT=X3XC9wiBU+wDSbHjzrj-JrkJTqtO3v4cSw@mail.gmail.com> <CACL_3VEKRD+2sFchdfoPWLcXi1m=oiFCb=mtO4arqOPgP5cM9A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACL_3VEKRD+2sFchdfoPWLcXi1m=oiFCb=mtO4arqOPgP5cM9A@mail.gmail.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Yh8dRYEHqiyVXWIGJVv_fsoQnX8>
Cc: IETF <ietf@ietf.org>, Philip Homburg <pch-ipv6-ietf-3@u-1.phicoh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 18:08:41 -0000

Sun, Feb 19, 2017 at 01:50:42PM -0800, C. M. Heard:
> On 2017-02-18 Philip Homburg wrote:
> > So the only purpose of a stronger text against inserting extension headers
> > would be to prevent IETF working groups from publishing RFCs that use
> > that technique.
> 
> That is not the only purpose -- some of us, at least, would like to believe
> that stronger text will help to discourage practices that can have
> demonstrably harmful effects -- but it is definitely an important purpose.

Stronger text is also amunition for operators and users to push vendors to
fix bugs (no matter the proto in question).  we prefer the text to be
precise.  if it breaks ptmud and ptmud is essentially mandatory ....

[ps thanks for digging in the ml archive]


From nobody Tue Feb 21 11:04:33 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFD6129C7B for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 11:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEL-EoHynruA for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 11:04:28 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::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 B8F09129C76 for <ietf@ietf.org>; Tue, 21 Feb 2017 11:04:28 -0800 (PST)
Received: by mail-oi0-x22e.google.com with SMTP id s205so7602833oif.3 for <ietf@ietf.org>; Tue, 21 Feb 2017 11:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=UNIE74v8oMSclZvW7zObYDmAXeMqWZjQ4/LLg5Eh1a4=; b=vztaTYkIWsP9yHvnFygvfdrGr4dGgX+3ucS0fxgfGiQITKTGo/vO1Q+upTYobtlS9A n23UyYQy+/00rJ6H03aHCuMd406fIdFTU2tqfEvreCAi5Pu1HstUsUo6s0RI/MHwYVcx 8EX8YwWlDSqCy34dOPnEXWWQCq/Rf0suPRxCuZQWj1ndyUCI1TFpFi0xW7wXpUD439tY qhgX53ru/4m5SvsXpzQzTZxHs5IyNME6g+tl/b6ChtPIhc68wm4RQbVdVc8eEDHu0WlW tMc4m/ndPALiGtZy4L6XsEDJcGopV06oukWvnfZFnJrGNuLg9Na241oYqHsEXe7gA2IK LIVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=UNIE74v8oMSclZvW7zObYDmAXeMqWZjQ4/LLg5Eh1a4=; b=l7RHpvODyK4/I2fRqbAwEEwog4Eby/lGLRhOsnA4XcnZod6TZldU+CjVLTePZMJwyt lc1b5b3udvd0ZAcUTFtGOYb7fW3peahyCHMeYnhkrrHlDeEZ2pL+8FC8p+FdWWqYQk35 O6kDkXqq31BV1jLc2UoFzu+ZRw0LOH2wf3pSLyXG17IWsLl5va45+fyuNbmaActgMFYj NV2cRExx1QSiVM0NOp+7H0Ouv4rjLYuohF6hgvxWsm1vNNNkirooaaHi+X4gRebyxi/M 7xCG2Y1qnFKtseLhfOtY+qZJZQRNyqcKORsKQNOFQGmKs0JvKLZPlESHKmtVma2uBy61 /0yA==
X-Gm-Message-State: AMke39kNQoxq8Y/m+0eBGhQcyGEJ1+F7jpk5iV//RC44gYOiDT4p7CmI7vp2tYlybpW0sw==
X-Received: by 10.202.114.70 with SMTP id p67mr11902984oic.212.1487703868128;  Tue, 21 Feb 2017 11:04:28 -0800 (PST)
Received: from aither.local (c-98-245-40-52.hsd1.co.comcast.net. [98.245.40.52]) by smtp.gmail.com with ESMTPSA id v14sm9601734otv.0.2017.02.21.11.04.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 11:04:27 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
To: John C Klensin <john-ietf@jck.com>, "tom p." <daedulus@btconnect.com>, ietf@ietf.org
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB> <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net> <00068EB71CB3F63F36092E69@PSB>
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <89b5c4b3-4772-be57-8b5d-b6d63521801b@filament.com>
Date: Tue, 21 Feb 2017 12:04:26 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <00068EB71CB3F63F36092E69@PSB>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YToi8G6T6bEjWHpu5wR3BeIEjhI>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:04:31 -0000

On 2/21/17 10:40 AM, John C Klensin wrote:

> How would you
> feel about making the phrase something closer to "the basic
> Latin repertoire, i.e., the letters and digits of ASCII as
> described above" and moving the RFC 20 citation to the first use
> of "ASCII" in that previous paragraph?

OLD

   In order to make URNs as stable and persistent as possible when
   protocols evolve and the environment around them changes, URN
   namespaces SHOULD NOT allow characters outside the basic Latin
   repertoire [RFC20] unless the nature of the particular URN namespace
   makes such characters necessary.

NEW

   In order to make URNs as stable and persistent as possible when
   protocols evolve and the environment around them changes, URN
   namespaces SHOULD NOT allow non-ASCII characters [RFC6365] unless
   the nature of the particular URN namespace makes such characters
   necessary.

The term "non-ASCII" is defined in RFC 6365 and seems perfectly
appropriate here.

Peter


From nobody Tue Feb 21 11:14:54 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 880981296C1; Tue, 21 Feb 2017 11:14:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <ops-dir@ietf.org>
Subject: Partial review of draft-ietf-httpbis-rfc5987bis-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com>
Date: Tue, 21 Feb 2017 11:14:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yIxKzv-LLHsZTifBieKP2E6fGwQ>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:14:48 -0000

Review is partially done. Another review request has been registered
for completing it.

Reviewer: Jouni Korhonen
Review result: Ready

Sorry for being one day late (..but I had to honor presidents here and
take a day off.. ;)

The document was clear and I spotted no issues (bearing in mind my
limited HTTP proficiency). I did also check the ext-value ABNF with a
tool that it is correct (which it was).

The IDnits complains about non-ascii characters (pound, euro, etc). I
am not sure whether that will turn out to an "editorial" issue in the
final RFC text.


From nobody Tue Feb 21 11:17:16 2017
Return-Path: <julian.reschke@greenbytes.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 984EF129564; Tue, 21 Feb 2017 11:17:14 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=greenbytes.de header.b=YBHrm1yD; dkim=pass (1024-bit key) header.d=greenbytes.de header.b=YBHrm1yD
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSElfwolxsLg; Tue, 21 Feb 2017 11:17:13 -0800 (PST)
Received: from mail.greenbytes.de (mail.greenbytes.de [5.10.171.186]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0724129448; Tue, 21 Feb 2017 11:17:09 -0800 (PST)
Received: by mail.greenbytes.de (Postfix, from userid 117) id 455F015A1125; Tue, 21 Feb 2017 20:17:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1487704628; bh=zV7KCdKAmGKbQjSR4O0dTjmLGvDKNBw92LQcLcFfGgY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YBHrm1yDuKI26HjADbV+4cN62RhOgO4VXU3UcvZsXhpwuAOTWKglfxtmcPbapBK+Z sXjtYqtB84FSP/fh8V6IseWAG3z0Wvp6vhhSVZVMHBxaP9C3xx/bOWoZ56dsURChSW pgZLIxis6uI7XwGxSobO5lWCJ1J+BaWPkX2C3OS0=
Received: from [192.168.178.20] (unknown [93.217.71.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id 5460D15A05F8; Tue, 21 Feb 2017 20:17:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=greenbytes.de; s=mail; t=1487704628; bh=zV7KCdKAmGKbQjSR4O0dTjmLGvDKNBw92LQcLcFfGgY=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YBHrm1yDuKI26HjADbV+4cN62RhOgO4VXU3UcvZsXhpwuAOTWKglfxtmcPbapBK+Z sXjtYqtB84FSP/fh8V6IseWAG3z0Wvp6vhhSVZVMHBxaP9C3xx/bOWoZ56dsURChSW pgZLIxis6uI7XwGxSobO5lWCJ1J+BaWPkX2C3OS0=
Subject: Re: Partial review of draft-ietf-httpbis-rfc5987bis-04
To: Jouni Korhonen <jounikor@gmail.com>, ops-dir@ietf.org
References: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@greenbytes.de>
Message-ID: <b08d4591-437c-f65f-8a51-c4f807261c7e@greenbytes.de>
Date: Tue, 21 Feb 2017 20:17:07 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bMMqAqRKffSfDp6PFovU4Zja2Fs>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:17:14 -0000

On 2017-02-21 20:14, Jouni Korhonen wrote:
> ...
> The IDnits complains about non-ascii characters (pound, euro, etc). I
> am not sure whether that will turn out to an "editorial" issue in the
> final RFC text.
> ...

Right. That's because the tool chain doesn't yet support that properly. 
That shouldn't stop us from pushing.

(I'm ok with the spec spending some quality time in the RFC Editor queue 
until they are ready)

Best regards, Julian


From nobody Tue Feb 21 11:20:45 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1D8B129C83; Tue, 21 Feb 2017 11:20:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Hwj7EhW_9PQe; Tue, 21 Feb 2017 11:20:30 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1EB7F129C7D; Tue, 21 Feb 2017 11:20:30 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1cgFz9-000Bnm-Op; Tue, 21 Feb 2017 14:20:27 -0500
Date: Tue, 21 Feb 2017 14:20:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre - Filament <peter@filament.com>, "tom p." <daedulus@btconnect.com>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Message-ID: <A82A31111E5E5A6B4EDE9D12@PSB>
In-Reply-To: <89b5c4b3-4772-be57-8b5d-b6d63521801b@filament.com>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB> <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net> <00068EB71CB3F63F36092E69@PSB> <89b5c4b3-4772-be57-8b5d-b6d63521801b@filament.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Bd-TPhm2nHItqG5-TuFWRbwumBI>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:20:40 -0000

--On Tuesday, February 21, 2017 12:04 -0700 Peter Saint-Andre -
Filament <peter@filament.com> wrote:

> On 2/21/17 10:40 AM, John C Klensin wrote:
> 
>> How would you
>> feel about making the phrase something closer to "the basic
>> Latin repertoire, i.e., the letters and digits of ASCII as
>> described above" and moving the RFC 20 citation to the first
>> use of "ASCII" in that previous paragraph?
> 
> OLD
> 
>    In order to make URNs as stable and persistent as possible
> when    protocols evolve and the environment around them
> changes, URN    namespaces SHOULD NOT allow characters outside
> the basic Latin    repertoire [RFC20] unless the nature of the
> particular URN namespace    makes such characters necessary.
> 
> NEW
> 
>    In order to make URNs as stable and persistent as possible
> when    protocols evolve and the environment around them
> changes, URN    namespaces SHOULD NOT allow non-ASCII
> characters [RFC6365] unless    the nature of the particular
> URN namespace makes such characters    necessary.
> 
> The term "non-ASCII" is defined in RFC 6365 and seems perfectly
> appropriate here.

Wfm.  Tom?

    john




From nobody Tue Feb 21 11:21:40 2017
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C381A12711D; Tue, 21 Feb 2017 11:21:34 -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_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 77qf8OXyWSd1; Tue, 21 Feb 2017 11:21:33 -0800 (PST)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D9B7129525; Tue, 21 Feb 2017 11:21:33 -0800 (PST)
Received: from linne.localnet (85.16.19.79) by linfreserv (Axigen) with (ECDHE-RSA-AES256-SHA encrypted) ESMTPSA id 28C0FB; Tue, 21 Feb 2017 20:21:22 +0100
From: Karsten Thomann <karsten_thomann@linfre.de>
To: ipv6@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <2683353.FOTFeJBnXE@linne>
User-Agent: KMail/4.13.0.22 (Windows/6.1; KDE/4.14.3; i686; git-c97962a; 2016-07-14)
In-Reply-To: <20170221172739.GT84656@Vurt.local>
References: <m2y3x6eutl.wl-randy@psg.com> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 7
Date: Tue, 21 Feb 2017 11:21:33 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bN4A4IyykXCyiz6BNi_x2nWNUOk>
Cc: 6man-chairs@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:21:35 -0000

Am Dienstag, 21. Februar 2017, 18:27:39 schrieb Job Snijders:
> On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
> > On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
> > > ps. The "Write a draft" argument is weak at best, since we are
> > > already are discussing a draft (called
> > > 'draft-ietf-6man-rfc4291bis-07.txt'), which is in IETF Last call,=

> > > which means it is in a place to discuss the contents of that draf=
t.
> > > No reason to kick the can down the road.
> >=20
> > I'm sorry, but that's really how it is. The text you dislike has be=
en
> > the standard for almost 20 years, and is it inappropriate to change=
 it
> > in the context of reclassifying this document from draft standard t=
o
> > Internet standard.
>=20
> Or, perhaps it is inappropiate for the -bis document to target "Inter=
net
> Standard" classification at this moment? =AF\_(?)_/=AF
>=20
> Especially when solidifying recommendations in an architecture Intern=
et
> Standard-to-be, the utmost care should be taken to verify whether the=

> paper reality (RFCs) and operational reality (what people do, for
> $reasons) are aligned.
>=20
> In those years sufficient data has been collected to conclude that /6=
4
> is not the "be all and end all". The current paragraph does not accou=
nt
> for staticly configured environments in which SLAAC plays no role.
>=20
> Perhaps the following suggestion bridges the gap.
>=20
> -------
>=20
> OLD:
>    IPv6 unicast routing is based on prefixes of any valid length up t=
o
>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixe=
s
>    on inter-router point-to-point links.  However, the Interface ID o=
f
>    all unicast addresses, except those that start with the binary val=
ue
>    000, is required to be 64 bits long.  The rationale for the 64 bit=

>    boundary in IPv6 addresses can be found in [RFC7421]
>=20
> NEW:
>    IPv6 unicast routing is based on prefixes of any valid length up t=
o
>    128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface=
 ID
>    of unicast addresses is required to be 64 bits long. In other use
>    cases different prefix sizes may be required. For example [RFC6164=
]
>    standardises 127 bit prefixes on inter-router point-to-point links=
.
>    For most use cases, prefix lengths of 64 bits is RECOMMENDED, unle=
ss
>    there are operational reasons not to do so.

Satisfies my desired outcome of the text, but I would like to modify it=
:
    IPv6 unicast routing is based on prefixes of any valid length up to=

    128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface =
ID
    of unicast addresses is required to be 64 bits long. An exception i=
s for
    example [RFC6164] which standardises 127 bit prefixes on point-to-p=
oint
    links. The RECOMMENDED prefix length is 64 bit, but prefix lengths =
up to
   128 bit can be possible on explicit configuration.


> OLD:
>    As noted in Section 2.4, all unicast addresses, except those that
>    with the binary value 000, Interface IDs are required to be 64 bit=
s
>    long.
>=20
> NEW:
>     *delete, its superfluous*
Ok for me.


From nobody Tue Feb 21 11:33:54 2017
Return-Path: <jounikor@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D88131294BF; Tue, 21 Feb 2017 11:33:43 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jouni Korhonen <jounikor@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-ccamp-ospf-availability-extension-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148770562388.19070.16770867288080366155.idtracker@ietfa.amsl.com>
Date: Tue, 21 Feb 2017 11:33:43 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZhJQWSYtTxBHzLa9N90Pkguz_xs>
Cc: draft-ietf-ccamp-ospf-availability-extension.all@ietf.org, ccamp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:33:44 -0000

Reviewer: Jouni Korhonen
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-ccamp-ospf-availability-extension-??
Reviewer: Jouni Korhonen
Review Date: 2017-02-21
IETF LC End Date: 2016-10-24
IESG Telechat date: 2017-03-16

Summary:

I have reviewed two earlier versions of this document. All my comments
have been addressed. I am also happy to see my earlier comments
generated (I believe) a draft addressing the generalized SCSI TLV
specification work in TEAS, and this draft referencing to that work.

Major issues:

none.

Minor issues:

none.

Nits/editorial comments: 

There are minor editorials here and there, but those will be picked up
by the RFC editor in any case.


From nobody Tue Feb 21 11:44:31 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67187129C95; Tue, 21 Feb 2017 11:44:29 -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, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QroFR528ZvU; Tue, 21 Feb 2017 11:44:28 -0800 (PST)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 2A4CE129C8B; Tue, 21 Feb 2017 11:44:28 -0800 (PST)
Received: by mail-vk0-x235.google.com with SMTP id k127so85717232vke.0; Tue, 21 Feb 2017 11:44:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=KEtq3N51UwbEddTR3DiW3d26tEkSw5QK89XvhvZM8hA=; b=G0eKiMsgNCwkVJe2O2G0D9/AonVynBWVckibgK28ZbMZfs2g2WyW1kwsQq4k1W1WM9 CZOtUMwSzcXzikLmkD9sJ5Y28e04lREJ5JPPHbgJNtyLId6u9kUBxjK/ct8Q7a56zPRu NzsubkThsKYiTKAdXmm+E7m81e/Y+jMAbRgMfheS0nsDx+0niGZkbLKZR6GXFA4Sr+UR f0kBphZoPTUhEACJ+GIWse03fRqvR2l4pzPOSFb9HJokeaKFbxv5q67bWo0Nq+/TJAs8 h1SOlct5IcNuSTWTdUn407NCTboyKCzW6SdvFwzXjpufFvuhs331jK0xYv3aFBBwUPUi A/Iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=KEtq3N51UwbEddTR3DiW3d26tEkSw5QK89XvhvZM8hA=; b=N/PBGcAj9rIHsMuVXU5sMOKlodiwQTUCUlat0SNEla3JJikXFNRUeVGufM/FLJo5M8 /Htjf3ZYYWZzA4xyysy0NXmFkbXJkrw68woIA3xWI3BJTrtQO05wlqwmfbG9D9BylcoO eE3ObfO4XVyNlE9VaIOf18p1DuAvKSqoUJQq1zKftlH/lJRWN0oXOo3Uvfhc01qYBF1m X6o4W9TjoRgnPEjtLkQBgUA+TewvXEsFwWmSY/KfsgBlSRUdAlS8/S8g/dxdLsI6m70S ZYVKO9UU+3HX9hCjeQFny3uUcTXdOXgP09ixLL+h5FLeUdFif+0pklKz8kA2sjo0PDhz OLAg==
X-Gm-Message-State: AMke39lEqzZVGVwEdj8ATGscTki6g3xkJx8m7XRXio+7yfHLyN8S6VB3ieIkB6cZus4Yxam/X3uFjwmbm9PAIg==
X-Received: by 10.31.52.193 with SMTP id b184mr12841726vka.156.1487706267231;  Tue, 21 Feb 2017 11:44:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Tue, 21 Feb 2017 11:43:56 -0800 (PST)
In-Reply-To: <20170221172739.GT84656@Vurt.local>
References: <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 22 Feb 2017 06:43:56 +1100
Message-ID: <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oKNP1CP5oXco6Za16qilBjS9ekE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:44:29 -0000

On 22 February 2017 at 04:27, Job Snijders <job@ntt.net> wrote:
> On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
>> On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
>> > ps. The "Write a draft" argument is weak at best, since we are
>> > already are discussing a draft (called
>> > 'draft-ietf-6man-rfc4291bis-07.txt'), which is in IETF Last call,
>> > which means it is in a place to discuss the contents of that draft.
>> > No reason to kick the can down the road.
>>
>> I'm sorry, but that's really how it is. The text you dislike has been
>> the standard for almost 20 years, and is it inappropriate to change it
>> in the context of reclassifying this document from draft standard to
>> Internet standard.
>
> Or, perhaps it is inappropiate for the -bis document to target "Internet
> Standard" classification at this moment? =C2=AF\_(=E3=83=84)_/=C2=AF
>
> Especially when solidifying recommendations in an architecture Internet
> Standard-to-be, the utmost care should be taken to verify whether the
> paper reality (RFCs) and operational reality (what people do, for
> $reasons) are aligned.
>

Flexibility isn't cheaper, it is more operationally expensive, because
it creates opportunity for complexity and errors.

A very simple example to demonstrate the additional cost of flexibility.

You showed the the distribution of prefix lengths in an AS. That may
have taken say 5 minutes to assemble and calculate? If all your prefix
lengths were /64s, you could have saved 5 minutes because you would
know the single value.

Multiply that sort of example 5 minutes over the many times you deal
with the complexity and errors that will occur when having a range of
prefix lengths, and that will add up to a significant amount of time.
It was an unavoidable cost in IPv4 because it was necessary to stretch
the usable life of IPv4's 32 bits of address space. It is an avoidable
cost in IPv6.

IPv4 too started out with a fixed or well known boundary between the
network portion and the host portion.

RFC760:

"   Addresses are fixed length of four octets (32 bits).  An address
    begins with a one octet network number, followed by a three octet
    local address.  This three octet field is called the "rest" field."


I advocate for /48s for all customers over a mix of /56s and /48s for
the same reason. The cost of managing the different prefix lengths and
resolving errors when the incorrect size prefix is assigned to a
customer are significant compared to the savings in RIR fees, and
perhaps may eliminate all those savings. When there is a single value
or size, there is no ambiguity and no opportunity for error.

I think many network engineers (and many technical people in general)
consider flexibility to be a a desirable property because they think
it means they'll be able to adapt to any future requirement without
any significant constraints. It's an understandable view (which I used
to have), however, I don't think they often consider the cost that
flexibility creates. I've also haven't seen that flexibility pay off
as much as it is supposed to.

> In those years sufficient data has been collected to conclude that /64
> is not the "be all and end all".

Alternatively, it could show that people are applying IPv4 practices
they're familiar with to IPv6, even when it isn't necessary. They're
missing out on operational savings from simplicity.

Regards,
Mark.


From nobody Tue Feb 21 11:51:06 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9B701294E7; Tue, 21 Feb 2017 11:50:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 v_HvDP8vWOeL; Tue, 21 Feb 2017 11:50:58 -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 AECF912944D; Tue, 21 Feb 2017 11:50: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 v1LJowW6006351; Tue, 21 Feb 2017 12:50:58 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1LJopr8006312 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 21 Feb 2017 12:50:51 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Tue, 21 Feb 2017 11:50:50 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Tue, 21 Feb 2017 11:50:51 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Job Snijders <job@ntt.net>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSjGfMgtRG27MIc0yfTQ6D9ojxU6Fz2xKw
Date: Tue, 21 Feb 2017 19:50:50 +0000
Message-ID: <76f6e70880d34632a334181df2fba637@XCH15-06-11.nw.nos.boeing.com>
References: <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local>
In-Reply-To: <20170221172739.GT84656@Vurt.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dEYQgP_GuP-afsbQUbm81vce9l8>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:51:00 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9iIFNuaWpkZXJzDQoNCj4gTkVXOg0KPiAg
ICBJUHY2IHVuaWNhc3Qgcm91dGluZyBpcyBiYXNlZCBvbiBwcmVmaXhlcyBvZiBhbnkgdmFsaWQg
bGVuZ3RoIHVwIHRvDQo+ICAgIDEyOCBbQkNQMTk4XS4gV2hlbiB1c2luZyBbU0xBQUNdLCBbSUxO
UF0sIG9yIFtOUFQ2Nl0gdGhlIEludGVyZmFjZSBJRA0KPiAgICBvZiB1bmljYXN0IGFkZHJlc3Nl
cyBpcyByZXF1aXJlZCB0byBiZSA2NCBiaXRzIGxvbmcuIEluIG90aGVyIHVzZQ0KPiAgICBjYXNl
cyBkaWZmZXJlbnQgcHJlZml4IHNpemVzIG1heSBiZSByZXF1aXJlZC4gRm9yIGV4YW1wbGUgW1JG
QzYxNjRdDQo+ICAgIHN0YW5kYXJkaXNlcyAxMjcgYml0IHByZWZpeGVzIG9uIGludGVyLXJvdXRl
ciBwb2ludC10by1wb2ludCBsaW5rcy4NCj4gICAgRm9yIG1vc3QgdXNlIGNhc2VzLCBwcmVmaXgg
bGVuZ3RocyBvZiA2NCBiaXRzIGlzIFJFQ09NTUVOREVELCB1bmxlc3MNCj4gICAgdGhlcmUgYXJl
IG9wZXJhdGlvbmFsIHJlYXNvbnMgbm90IHRvIGRvIHNvLg0KDQpTb3VuZHMgYWJvdXQgcmlnaHQg
dG8gbWUuIEFub3RoZXIgZXhjZXB0aW9uIHRoYXQgcmVxdWlyZXMgLzY0IHdvdWxkIGJlIFVMQXMu
DQoNCkkgdGhpbmsgdGhhdCBhZnRlciBSRkMgMjQ2MC1iaXMgYmVjb21lcyB0aGUgc3RhbmRhcmQs
IHRoaXMgLzY0IGRlYmF0ZSB3aWxsIGJlIHJldmlzaXRlZC4gV2h5PyBUbyBtYWtlIGl0IHN1cGVy
IGNsZWFyIHRoYXQgZm9yIHVuaWNhc3QsIGluIGdlbmVyYWwsIC82NCBhcmUgZ29pbmcgdG8gYmUg
dGhlIGV4Y2VwdGlvbiwgbm90IHRoZSBydWxlIChhcyBzbyBtdWNoIHRleHQgbm93IHN1Z2dlc3Rz
KS4gVGhlIDY0IGJpdCBwcmVmaXggYXBwbGllcyB0byB0aGUgMjAwMDo6LzMgYWRkcmVzcyBzcGFj
ZSwgYW5kIHRob3NlIGZldyBleGNlcHRpb25zLg0KDQpGb3IgZXhhbXBsZSwgdGhpcyBpcyBhbGwg
dXAgaW4gdGhlIGFpciBzdGlsbCwgYnV0IHdlIGNhbiBhc3N1bWUgdGhhdCBqdXN0IGFzIGhvdXNl
aG9sZHMgYXJlIGJlaW5nIGFzc2lnbmVkIG9uZSAvNjQgcHJlZml4IGZyZXF1ZW50bHksIHNvIHdp
bGwgY2Fycz8gRWFjaCBjYXIgZ2V0cyBhIC82NC4gRG9lcyBhbnlvbmUgdGhpbmsgdGhhdCBjYXJz
IHdpbGwgb25seSBpbmNsdWRlIG9uZSBJUHY2IHN1Ym5ldD8gTm90IG1lLiBTbyB3ZSB3aWxsIG5l
ZWQgQ0lEUi4NCg0KQmVydA0KDQo=


From nobody Tue Feb 21 11:57:34 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1F481294C7; Tue, 21 Feb 2017 11:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, HK_RANDOM_FROM=0.999, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LudjZxFQkXRO; Tue, 21 Feb 2017 11:57:25 -0800 (PST)
Received: from mail-ua0-x229.google.com (mail-ua0-x229.google.com [IPv6:2607:f8b0:400c:c08::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 9FF7012946F; Tue, 21 Feb 2017 11:57:25 -0800 (PST)
Received: by mail-ua0-x229.google.com with SMTP id 35so90823886uak.1; Tue, 21 Feb 2017 11:57:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TtnyU7enZlorlmTYBxgfZ5Kxq2fLcjMKvtoVCQ0I+og=; b=gdavoqUO1TR2jzQZeHb7nTLAk0T5YkmaLrp22CUbFTOWzN4kwc4A2mo8ditfs1zXng g7cZKhoNDy+WEtewZ34vZRzVcQfxVxLE9yj1YVgn2w2k+N/Wpg8Na9z8E47Lvn6S/dhM dfo4ZGgQ1b+feNGlM0NktOpuAWF3NkUx85OKg2tVwyvKWk2nD287g9IgT8ww5Nvv333m 5NPKopvzlwpa5J0T0ZqJ4RY3eaDvl4fmVRAOv1LWmeQcuK7WtkeIylrWBZAP/2gKAjGr uY/StNPTP/aRUv3o+YXIzHH86Uxb+DaMgw8iQWar7tH29S4iRytc1ZZg2/ABbwaWJqHl BxOg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TtnyU7enZlorlmTYBxgfZ5Kxq2fLcjMKvtoVCQ0I+og=; b=p+mTDS9vUaJs4PNDemMRkcOxMz9QWEca1ae2vu9qcUUsNzGyvIJJvRQZP9Av2Js4TF E30vHGn7gJq6BFvb20G9xOVSb4KVlb2sLvwlSiIiyaRR9J3KLlfGYK/Xx83sHR3/HK/q FgINPCWiGhfTkl/dgGN9x1IXLn/h1YQaYilxIbwSUV9p3HFVYhfAAuEb0KtSbH7Id5ZC k/2L0feve1cnopVEhe+RDDvTdGKbf2DGM49nPHRST+I/OJN+BnWRYe8M0pkvuDhLan8x Jj9p+IOgBlk+8qZR+LL4sdUKTX1+nfKfxxVH0NCFIjJjNpBoD3FTr2xpY6Al9vk14ifj z+AQ==
X-Gm-Message-State: AMke39ni0KVClAX+dac4ZG/6L8GBM8KVFh4Aoj+gpLuQwtQgreS1mUZClazrU8gJ7cSy8QGmwfTC9p8zH0c2Wg==
X-Received: by 10.176.71.234 with SMTP id w42mr5423813uac.141.1487707044712; Tue, 21 Feb 2017 11:57:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Tue, 21 Feb 2017 11:56:53 -0800 (PST)
In-Reply-To: <2683353.FOTFeJBnXE@linne>
References: <m2y3x6eutl.wl-randy@psg.com> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <2683353.FOTFeJBnXE@linne>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 22 Feb 2017 06:56:53 +1100
Message-ID: <CAO42Z2z6K9tzYCekbyROXR7J1nB9FW53ncTRrW3p3N2P_6WyRQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Karsten Thomann <karsten_thomann@linfre.de>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ej6IQs_2LW8AZftselWwbiN4m8E>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 19:57:27 -0000

On 22 February 2017 at 06:21, Karsten Thomann <karsten_thomann@linfre.de> wrote:
> Am Dienstag, 21. Februar 2017, 18:27:39 schrieb Job Snijders:
>> On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
>> > On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
<snip>
>>
>> -------
>>
>> OLD:
>>    IPv6 unicast routing is based on prefixes of any valid length up to
>>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
>>    on inter-router point-to-point links.  However, the Interface ID of
>>    all unicast addresses, except those that start with the binary value
>>    000, is required to be 64 bits long.  The rationale for the 64 bit
>>    boundary in IPv6 addresses can be found in [RFC7421]
>>
>> NEW:
>>    IPv6 unicast routing is based on prefixes of any valid length up to
>>    128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface ID
>>    of unicast addresses is required to be 64 bits long. In other use
>>    cases different prefix sizes may be required. For example [RFC6164]
>>    standardises 127 bit prefixes on inter-router point-to-point links.
>>    For most use cases, prefix lengths of 64 bits is RECOMMENDED, unless
>>    there are operational reasons not to do so.
>
> Satisfies my desired outcome of the text, but I would like to modify it:
>     IPv6 unicast routing is based on prefixes of any valid length up to
>     128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface ID
>     of unicast addresses is required to be 64 bits long. An exception is for
>     example [RFC6164] which standardises 127 bit prefixes on point-to-point
>     links. The RECOMMENDED prefix length is 64 bit,

It has to be stronger than a RECOMMENDED, because that implies it is
an arbitrary choice that won't have any protocol operational and
privacy or security impacts. That is not the case.

Have you and Job read,

"Analysis of the 64-bit Boundary in IPv6 Addressing
https://tools.ietf.org/html/rfc7421


?

(It has been referenced at some point in a version of this text
proposed I think.)

Regards,
Mark.


From nobody Tue Feb 21 12:05:25 2017
Return-Path: <jhw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F581296E9 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:05: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dIfV0Xz8r5Mp for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:05:22 -0800 (PST)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e: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 E861D1296ED for <ietf@ietf.org>; Tue, 21 Feb 2017 12:05:21 -0800 (PST)
Received: by mail-pg0-x22c.google.com with SMTP id 1so22041248pgi.1 for <ietf@ietf.org>; Tue, 21 Feb 2017 12:05:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VcWQVWD7KiQ6HYDTnyBFirlXjVhXLQtoODFaaousa7g=; b=L6HoD21+74JGMykgUTRBdOV9dmqsfbh+kbGGyT8kv0o0ssDc/0+cclWbZYfOPByUNY oO+YOZWPnJqdcpZnhILmxH3UBxXgpjK+YfZMFzcoK2qZuHnsaXn3m2qxvJwx2K9en0LA AcKHEOOjN5AwoBNYp4g9F1nncMgL0yElGSyEGYD4B2CXNlVMKNhV5Q88IqhDoufmhneO qD1KsYpiI6CtmVE3xPAP/UCk1FZF+6zk/mfpjbW8SlEfQ5Xo/Rx49iYRBOcciFP2AC9v l/qAa1ifWpZqNI+BNszNt1o9AYQaH7B4CU0/GOf8scVVSm2s7Q0g3ZZylVsiXHJkGPFy s4EA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VcWQVWD7KiQ6HYDTnyBFirlXjVhXLQtoODFaaousa7g=; b=q2sE0exhMdaTPJQ6g6kqO8xKP0cfipqpGEBIBDQSJ6aKvKDhfNS6PDuM2GJ9QcnF4f WrQnihYirWLsvxneBeuZG/wl8JoDmBx1kHwoNa9V51FU0fOdQkzuGoGuFKSjCR3j3tQz XSlyUvk01J5+pJarg6jZbA1A7w67HKHCR5/ONvTXUgF2GwOlgqeXpzJZl9Ab/AIGr93n O1Wx0r2oInHEBEjGr4KbWZO36G+0H5Bxd7x9c6ou85tyQzaAubpW5f7bPUiFk9N4SxZE hyXmG7o5MIlJjQHr37kkn7JedebmZX34IycsKOo4Pifw0yLp/oePDvPUS5unYRrcOop5 8fTg==
X-Gm-Message-State: AMke39kFiBVDFqMGWQX9qPYVfO5WUlX0xcQYqE/+DoWhvLrAagVeO7vcT/DCVmZpqnKN2Ocu
X-Received: by 10.99.116.9 with SMTP id p9mr7077237pgc.74.1487707521350; Tue, 21 Feb 2017 12:05:21 -0800 (PST)
Received: from dhcp-100-99-230-134.pao.corp.google.com ([100.99.230.134]) by smtp.gmail.com with ESMTPSA id p73sm2475068pfj.47.2017.02.21.12.05.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 12:05:20 -0800 (PST)
From: james woodyatt <jhw@google.com>
Message-Id: <5F3FA243-F141-4508-9F99-282E05D4DC85@google.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C9D3BB78-E93E-4FF3-A9AB-7FAA3F2AF777"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Purpose of Port 0.
Date: Tue, 21 Feb 2017 12:05:19 -0800
In-Reply-To: <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu>
To: Joe Touch <touch@isi.edu>, Danny Niu <dannyniu@hotmail.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com> <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lwa7PbdJ0ZP3yliRtd0M1xx59XM>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 20:05:23 -0000

--Apple-Mail=_C9D3BB78-E93E-4FF3-A9AB-7FAA3F2AF777
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Feb 20, 2017, at 08:10, Joe Touch <touch@isi.edu> wrote:
>=20
> There is no IANA registry for source ports, nor should there be. Ports =
in the incoming first-contact are swapped, as indicated in RFCs 768 and =
793. Source ports indicate "who to call back", and "0" is indicated in =
UDP (RFC768) as "nobody" and TCP (RFC793)


p1. Port zero is currently Unassigned for the SCTP and DCCP standard =
transports and all the other non-standard transports listed in the =
Protocol Numbers registry.

  =
<https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml =
<https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml>=
>

p2. Port zero is a System Port, so the process for assigning its IANA =
registration is RFC 6335, section 8.1.2, which says:

>>   o  Ports in the System Ports range (0-1023) are also available for
>>       assignment through IANA.  Because the System Ports range is =
both
>>       the smallest and the most densely assigned, the requirements =
for
>>       new assignments are more strict than those for the User Ports
>>       range, and will only be granted under the "IETF Review" or =
"IESG
>>       Approval" procedures [RFC5226 =
<https://tools.ietf.org/html/rfc5226>].  A request for a System Port
>>       number MUST document *both* why using a port number from the
>>       Dynamic Ports range is unsuitable *and* why using a port number
>>       from the User Ports range is unsuitable for that application.

p3. Port zero is already reserved for SCTP by RFC 4960. IANA just needs =
to correct its registry to show that port zero is Assigned.

p4. Port zero is not reserved for DCCP by RFC 4340, so port zero remains =
Unassigned there at this point.

p5. Port zero is already reserved in their respective RFCs for a few of =
the non-standard transports listed in the Protocol Numbers registry, but =
being non-standard transports, there=E2=80=99s no way to assign them for =
those protocols under the procedure in RFC 6335.

I=E2=80=99m guessing the POSIX community could attempt to write an =
Internet Draft that expressly assigned port zero across all known and =
unknown transport protocols to the =E2=80=9Cunspecified service =
number=E2=80=9D semantic that it uses, but my hunch is the need for that =
draft isn=E2=80=99t very strong (considering the intent declared in RFC =
2553 to keep POSIX as the standard API for IPv6 applications) and that =
getting the language right would not be worth the hassle.


--james woodyatt <jhw@google.com <mailto:jhw@google.com>>




--Apple-Mail=_C9D3BB78-E93E-4FF3-A9AB-7FAA3F2AF777
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"">On Feb 20, 2017, at 08:10, Joe Touch &lt;<a =
href=3D"mailto:touch@isi.edu" class=3D"">touch@isi.edu</a>&gt; wrote:<br =
class=3D""><div><blockquote type=3D"cite" class=3D""><br =
class=3D"Apple-interchange-newline"><div class=3D""><span =
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); =
float: none; display: inline !important;" class=3D"">There is no IANA =
registry for source ports, nor should there be. Ports in the incoming =
first-contact are swapped, as indicated in RFCs 768 and 793. Source =
ports indicate "who to call back", and "0" is indicated in UDP (RFC768) =
as "nobody" and TCP (RFC793)</span></div></blockquote></div><div =
class=3D""><br class=3D""></div><div class=3D"">p1. Port zero is =
currently Unassigned for the SCTP and DCCP standard transports and all =
the other non-standard transports listed in the Protocol Numbers =
registry.</div><div class=3D""><br class=3D""></div><div class=3D"">&nbsp;=
 &lt;<a =
href=3D"https://www.iana.org/assignments/protocol-numbers/protocol-numbers=
.xhtml" =
class=3D"">https://www.iana.org/assignments/protocol-numbers/protocol-numb=
ers.xhtml</a>&gt;</div><div class=3D""><br class=3D""></div><div =
class=3D"">p2. Port zero is a System Port, so the process for assigning =
its IANA registration is RFC 6335, section 8.1.2, which says:</div><div =
class=3D""><br class=3D""></div><div class=3D""><pre class=3D"newpage" =
style=3D"font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; =
break-before: page; font-variant-ligatures: normal; orphans: 2; widows: =
2;"></pre><blockquote type=3D"cite" class=3D""><pre class=3D"newpage" =
style=3D"font-size: 13.3333px; margin-top: 0px; margin-bottom: 0px; =
break-before: page; font-variant-ligatures: normal; orphans: 2; widows: =
2;"></pre></blockquote><blockquote type=3D"cite" class=3D""><blockquote =
type=3D"cite" class=3D""><pre class=3D"newpage" style=3D"font-size: =
13.3333px; margin-top: 0px; margin-bottom: 0px; break-before: page; =
font-variant-ligatures: normal; orphans: 2; widows: 2;">  o  Ports in =
the System Ports range (0-1023) are also available for
      assignment through IANA.  Because the System Ports range is both
      the smallest and the most densely assigned, the requirements for
      new assignments are more strict than those for the User Ports
      range, and will only be granted under the "IETF Review" or "IESG
      Approval" procedures [<a =
href=3D"https://tools.ietf.org/html/rfc5226" title=3D"&quot;Guidelines =
for Writing an IANA Considerations Section in RFCs&quot;" =
class=3D"">RFC5226</a>].  A request for a System Port
      number MUST document *both* why using a port number from the
      Dynamic Ports range is unsuitable *and* why using a port number
      from the User Ports range is unsuitable for that =
application.</pre></blockquote></blockquote><div class=3D""><br =
class=3D""></div></div><div class=3D"">p3. Port zero is already reserved =
for SCTP by RFC 4960. IANA just needs to correct its registry to show =
that port zero is Assigned.</div><div class=3D""><br class=3D""></div><div=
 class=3D"">p4. Port zero is not reserved for DCCP by RFC 4340, so port =
zero remains Unassigned there at this point.</div><div class=3D""><br =
class=3D""></div><div class=3D""><div class=3D"">p5. Port zero is =
already reserved in their respective RFCs for a few of the non-standard =
transports listed in the Protocol Numbers registry, but being =
non-standard transports, there=E2=80=99s no way to assign them for those =
protocols under the procedure in RFC 6335.</div></div><div class=3D""><br =
class=3D""></div><div class=3D"">I=E2=80=99m guessing the POSIX =
community could attempt to write an Internet Draft that expressly =
assigned port zero across all known and unknown transport protocols to =
the =E2=80=9Cunspecified service number=E2=80=9D semantic that it uses, =
but my hunch is the need for that draft isn=E2=80=99t very strong =
(considering the intent declared in RFC 2553 to keep POSIX as the =
standard API for IPv6 applications) and that getting the language right =
would not be worth the hassle.</div><div class=3D""><br =
class=3D""></div><br class=3D""><div class=3D"">
<div class=3D"">--james woodyatt &lt;<a href=3D"mailto:jhw@google.com" =
class=3D"">jhw@google.com</a>&gt;</div><div class=3D""><br =
class=3D""></div><br class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_C9D3BB78-E93E-4FF3-A9AB-7FAA3F2AF777--


From nobody Tue Feb 21 12:08:32 2017
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08AE11296F8; Tue, 21 Feb 2017 12:08:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nzcF9AoQw5AI; Tue, 21 Feb 2017 12:08:30 -0800 (PST)
Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (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 872BD1296F7; Tue, 21 Feb 2017 12:08:30 -0800 (PST)
Received: by mail-pg0-x242.google.com with SMTP id z128so1042585pgb.3; Tue, 21 Feb 2017 12:08:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tdWulHAfzBxZijNyoX/pCDe/5ROZNtg9UGVcQx1YEMw=; b=At13GJUMWF/ouvQQk03dCK4kEjesTz32It2Cgr+H7EbI8FGj+LR9EhLSYwdjG2PWaf L9okUoOpUQwxGWf5ZicDf3SBChUIEO+jOU8HDee0u3LwiFB804p9eUlxy/iib5Glh0k5 9wHxQFhMFesSuIsSyYQJ7KLDQ0JQIrX4gUBe4n+fSn0aBm6agbhfN8ejP5HsB72WV74M 3uqX6i9S2etJW4EtXoHmknVxjumugs6F3nBvbIpoTdWH8++l3tDSbjEJ4hnB7vpdKo98 y5doyp4bp64/+Mt3Eu78F8DOp3jhd+BnC9IQNPFFMZoXy5BsisYq7mrDFJtuF4C7ZG6+ c65g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=tdWulHAfzBxZijNyoX/pCDe/5ROZNtg9UGVcQx1YEMw=; b=qWNYgRBnvqdcV3JKvyr3p9+a/Z5mpcSzWCJdO0OfSN6Grk8D7UIdjJAwEhfjoryyQp kq5GfPgfYiEMIo4csb7noBDn36d5rVMXRhz4K15ApxSlZ5Ti3ordypMB2y01HV/fLn3b dDD+TmQGVRwNJEH0McmAozGK0fDYTcaKZKcmi9E0kR2/YXtuey2gMqCkVJKSDNGQxOt2 unL7Xh0kfRI66v/5/I5LZdV03pGQvpOQuE4hIpnsQT5wsAA0IeEwvwo5PSAiwE04UZ/F u+5+ZUPt4yJ1fdvC/bA9i26pAP5Znnwof4dM1CI4Zj9GmcKol8DT4Dk3RbKqnpZhADe/ g4jw==
X-Gm-Message-State: AMke39kq9c6Hu48EsmTw1wATAwZTE68Swqxs85wd1T28mb8hqPvbm5b1OKF2QyVBRyjrEA==
X-Received: by 10.84.232.129 with SMTP id i1mr42374585plk.129.1487707710069; Tue, 21 Feb 2017 12:08:30 -0800 (PST)
Received: from [192.168.89.94] ([216.31.219.19]) by smtp.gmail.com with ESMTPSA id l3sm42845337pgn.10.2017.02.21.12.08.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 12:08:28 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [OPS-DIR] Partial review of draft-ietf-httpbis-rfc5987bis-04
From: "jouni.nospam" <jouni.nospam@gmail.com>
In-Reply-To: <b08d4591-437c-f65f-8a51-c4f807261c7e@greenbytes.de>
Date: Tue, 21 Feb 2017 12:08:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <14AF10FC-7B86-4838-9EF6-19F02446D8C1@gmail.com>
References: <148770448855.19178.9845548060581119883.idtracker@ietfa.amsl.com> <b08d4591-437c-f65f-8a51-c4f807261c7e@greenbytes.de>
To: Julian Reschke <julian.reschke@greenbytes.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BLr4S2hNTS0H87G8ctUlUFUS7NA>
Cc: ops-dir@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org, Jouni Korhonen <jounikor@gmail.com>, draft-ietf-httpbis-rfc5987bis.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 20:08:32 -0000

> On Feb 21, 2017, at 11:17 AM, Julian Reschke =
<julian.reschke@greenbytes.de> wrote:
>=20
> On 2017-02-21 20:14, Jouni Korhonen wrote:
>> ...
>> The IDnits complains about non-ascii characters (pound, euro, etc). I
>> am not sure whether that will turn out to an "editorial" issue in the
>> final RFC text.
>> ...
>=20
> Right. That's because the tool chain doesn't yet support that =
properly. That shouldn=E2=80=99t stop us from pushing.

Yep. That should not be any kind of blocking factor/issue.

> (I=E2=80=99m ok with the spec spending some quality time in the RFC =
Editor queue until they are ready)

Whatever works for you/Editor.

- Jouni

>=20
> Best regards, Julian
>=20
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir


From nobody Tue Feb 21 12:25:58 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E11261294B5 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:25:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 dGa2kh0q6BFs for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:25:55 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 8621A12944C for <ietf@ietf.org>; Tue, 21 Feb 2017 12:25:55 -0800 (PST)
Received: from [128.9.184.189] ([128.9.184.189]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1LKPMFU000329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Feb 2017 12:25:23 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: james woodyatt <jhw@google.com>, Danny Niu <dannyniu@hotmail.com>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com> <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu> <5F3FA243-F141-4508-9F99-282E05D4DC85@google.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu>
Date: Tue, 21 Feb 2017 12:25:20 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <5F3FA243-F141-4508-9F99-282E05D4DC85@google.com>
Content-Type: multipart/alternative; boundary="------------A3F7A0FAB8EBC7A3DAF19DAA"
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bGUz0ddc6-RJPSzJtPK30UVWmp4>
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 20:25:57 -0000

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

Hi James,


On 2/21/2017 12:05 PM, james woodyatt wrote:
> On Feb 20, 2017, at 08:10, Joe Touch <touch@isi.edu
> <mailto:touch@isi.edu>> wrote:
>>
>> There is no IANA registry for source ports, nor should there be.
>> Ports in the incoming first-contact are swapped, as indicated in RFCs
>> 768 and 793. Source ports indicate "who to call back", and "0" is
>> indicated in UDP (RFC768) as "nobody" and TCP (RFC793)
>
> p1. Port zero is currently Unassigned for the SCTP and DCCP standard
> transports and all the other non-standard transports listed in the
> Protocol Numbers registry.

Per RFC6335, there is one registry for all transport port numbers.
"RESERVED" in that registry applies to all transports.

> p2. Port zero is a System Port, so the process for assigning its IANA
> registration is RFC 6335, section 8.1.2, which says:
Agreed.

> p3. Port zero is already reserved for SCTP by RFC 4960. IANA just
> needs to correct its registry to show that port zero is Assigned.
Per section 14.5, SCTP uses the existing transport port registry. It
lists a set of assignments starting at port 9, but does not request
assignment of 0.

Section 3.1 prohibits the use of 0 as either source or destination port,
but that's not an assignment. That's a prohibition, and not indicated as
a reservation in the IANA Considerations (Sec 14).

> p4. Port zero is not reserved for DCCP by RFC 4340, so port zero
> remains Unassigned there at this point.

It remains RESERVED (as per the ports registry) but potentially
assignable to DCCP.

> p5. Port zero is already reserved in their respective RFCs for a few
> of the non-standard transports listed in the Protocol Numbers
> registry, but being non-standard transports, there’s no way to assign
> them for those protocols under the procedure in RFC 6335.

"RESERVED" would involve IANA Considerations, and that act would have
resulted in their being recorded in the IANA registry.

Prohibitions within the protocol do not result in IANA actions.

> I’m guessing the POSIX community could attempt to write an Internet
> Draft that expressly assigned port zero across all known and unknown
> transport protocols to the “unspecified service number” semantic that
> it uses,

IMO, an RFC that needs an API to pass the value "unspecified" should
indicate just that. It would be far out of scope for an RFC to indicate
the *value* passed in an API to indicate that parameter.

Joe

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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Hi James,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/21/2017 12:05 PM, james woodyatt
      wrote:<br>
    </div>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      On Feb 20, 2017, at 08:10, Joe Touch &lt;<a moz-do-not-send="true"
        href="mailto:touch@isi.edu" class="">touch@isi.edu</a>&gt;
      wrote:<br class="">
      <div>
        <blockquote type="cite" class=""><br
            class="Apple-interchange-newline">
          <div class=""><span style="font-family: Helvetica; font-size:
              12px; font-style: normal; font-variant-caps: normal;
              font-weight: normal; letter-spacing: normal; orphans:
              auto; text-align: start; text-indent: 0px; text-transform:
              none; white-space: normal; widows: auto; word-spacing:
              0px; -webkit-text-stroke-width: 0px; background-color:
              rgb(255, 255, 255); float: none; display: inline
              !important;" class="">There is no IANA registry for source
              ports, nor should there be. Ports in the incoming
              first-contact are swapped, as indicated in RFCs 768 and
              793. Source ports indicate "who to call back", and "0" is
              indicated in UDP (RFC768) as "nobody" and TCP (RFC793)</span></div>
        </blockquote>
      </div>
      <div class=""><br class="">
      </div>
      <div class="">p1. Port zero is currently Unassigned for the SCTP
        and DCCP standard transports and all the other non-standard
        transports listed in the Protocol Numbers registry.</div>
    </blockquote>
    <br>
    Per RFC6335, there is one registry for all transport port numbers.
    "RESERVED" in that registry applies to all transports.<br>
    <br>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">
      <div class="">p2. Port zero is a System Port, so the process for
        assigning its IANA registration is RFC 6335, section 8.1.2,
        which says:</div>
    </blockquote>
    Agreed.<br>
    <br>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">p3. Port zero is already reserved for SCTP by RFC
      4960. IANA just needs to correct its registry to show that port
      zero is Assigned.</blockquote>
    Per section 14.5, SCTP uses the existing transport port registry. It
    lists a set of assignments starting at port 9, but does not request
    assignment of 0.<br>
    <br>
    Section 3.1 prohibits the use of 0 as either source or destination
    port, but that's not an assignment. That's a prohibition, and not
    indicated as a reservation in the IANA Considerations (Sec 14).<br>
    <br>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">
      <div class="">p4. Port zero is not reserved for DCCP by RFC 4340,
        so port zero remains Unassigned there at this point.</div>
    </blockquote>
    <br>
    It remains RESERVED (as per the ports registry) but potentially
    assignable to DCCP.<br>
    <br>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">
      <div class="">
        <div class="">p5. Port zero is already reserved in their
          respective RFCs for a few of the non-standard transports
          listed in the Protocol Numbers registry, but being
          non-standard transports, there’s no way to assign them for
          those protocols under the procedure in RFC 6335.</div>
      </div>
    </blockquote>
    <br>
    "RESERVED" would involve IANA Considerations, and that act would
    have resulted in their being recorded in the IANA registry.<br>
    <br>
    Prohibitions within the protocol do not result in IANA actions.<br>
    <br>
    <blockquote
      cite="mid:5F3FA243-F141-4508-9F99-282E05D4DC85@google.com"
      type="cite">
      <div class="">I’m guessing the POSIX community could attempt to
        write an Internet Draft that expressly assigned port zero across
        all known and unknown transport protocols to the “unspecified
        service number” semantic that it uses, </div>
    </blockquote>
    <br>
    IMO, an RFC that needs an API to pass the value "unspecified" should
    indicate just that. It would be far out of scope for an RFC to
    indicate the *value* passed in an API to indicate that parameter.<br>
    <br>
    Joe<br>
  </body>
</html>

--------------A3F7A0FAB8EBC7A3DAF19DAA--


From nobody Tue Feb 21 12:29:04 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECB71296EE; Tue, 21 Feb 2017 12:28:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 rWoz1hpdSNQ5; Tue, 21 Feb 2017 12:28:56 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 7CF0812944C; Tue, 21 Feb 2017 12:28:56 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgH3F-00095y-CC (job@us.ntt.net); Tue, 21 Feb 2017 20:28:55 +0000
Date: Tue, 21 Feb 2017 21:28:21 +0100
From: Job Snijders <job@ntt.net>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221202821.GB32367@Vurt.local>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yKJZvncNTQBjaH_7GcPowU1_aZY>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 20:28:57 -0000

On Wed, Feb 22, 2017 at 06:43:56AM +1100, Mark Smith wrote:
> On 22 February 2017 at 04:27, Job Snijders <job@ntt.net> wrote:
> > On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
> >> On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
> >> > ps. The "Write a draft" argument is weak at best, since we are
> >> > already are discussing a draft (called
> >> > 'draft-ietf-6man-rfc4291bis-07.txt'), which is in IETF Last call,
> >> > which means it is in a place to discuss the contents of that draft.
> >> > No reason to kick the can down the road.
> >>
> >> I'm sorry, but that's really how it is. The text you dislike has been
> >> the standard for almost 20 years, and is it inappropriate to change it
> >> in the context of reclassifying this document from draft standard to
> >> Internet standard.
> >
> > Or, perhaps it is inappropiate for the -bis document to target "Internet
> > Standard" classification at this moment? ¯\_(ツ)_/¯
> >
> > Especially when solidifying recommendations in an architecture Internet
> > Standard-to-be, the utmost care should be taken to verify whether the
> > paper reality (RFCs) and operational reality (what people do, for
> > $reasons) are aligned.
> >
> 
> Flexibility isn't cheaper, it is more operationally expensive, because
> it creates opportunity for complexity and errors.
> 
> A very simple example to demonstrate the additional cost of flexibility.
> 
> You showed the the distribution of prefix lengths in an AS. That may
> have taken say 5 minutes to assemble and calculate? If all your prefix
> lengths were /64s, you could have saved 5 minutes because you would
> know the single value.
> 
> Multiply that sort of example 5 minutes over the many times you deal
> with the complexity and errors that will occur when having a range of
> prefix lengths, and that will add up to a significant amount of time.
> It was an unavoidable cost in IPv4 because it was necessary to stretch
> the usable life of IPv4's 32 bits of address space. It is an avoidable
> cost in IPv6.
> 
> IPv4 too started out with a fixed or well known boundary between the
> network portion and the host portion.
> 
> RFC760:
> 
> "   Addresses are fixed length of four octets (32 bits).  An address
>     begins with a one octet network number, followed by a three octet
>     local address.  This three octet field is called the "rest" field."
> 
> I advocate for /48s for all customers over a mix of /56s and /48s for
> the same reason. The cost of managing the different prefix lengths and
> resolving errors when the incorrect size prefix is assigned to a
> customer are significant compared to the savings in RIR fees, and
> perhaps may eliminate all those savings. When there is a single value
> or size, there is no ambiguity and no opportunity for error.
> 
> I think many network engineers (and many technical people in general)
> consider flexibility to be a a desirable property because they think
> it means they'll be able to adapt to any future requirement without
> any significant constraints. It's an understandable view (which I used
> to have), however, I don't think they often consider the cost that
> flexibility creates. I've also haven't seen that flexibility pay off
> as much as it is supposed to.
> 
> > In those years sufficient data has been collected to conclude that
> > /64 is not the "be all and end all".
> 
> Alternatively, it could show that people are applying IPv4 practices
> they're familiar with to IPv6, even when it isn't necessary. They're
> missing out on operational savings from simplicity.

Have you read rfc1925 section 2.4?

You are grossly overstating these 'operational savings'. Also, for the
sake of this dialogue I'll apply Hanlon's razor and operate under the
assumption that you are not familiar with my work environment. 

I am amazed your reaction to my sharing of real-world data is the
equivalent of "well, i think you are doing it wrong". A lack of empathy
is exhibited in that you do not wonder _why_ things are what they are.

Kind regards,

Job


From nobody Tue Feb 21 12:57:20 2017
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BC39129CB9 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VOpKU4fe6OGm for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 12:57:17 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (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 330601297C2 for <ietf@ietf.org>; Tue, 21 Feb 2017 12:57:17 -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)) (No client certificate requested) by mx.ams1.isc.org (Postfix) with ESMTPS id A53ED24AE08; Tue, 21 Feb 2017 20:55:58 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 89AD316006B; Tue, 21 Feb 2017 20:55:57 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 71EBB16005B; Tue, 21 Feb 2017 20:55:57 +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 7WX_Dr0tl-Qk; Tue, 21 Feb 2017 20:55:57 +0000 (UTC)
Received: from rock.dv.isc.org (c27-253-115-14.carlnfd2.nsw.optusnet.com.au [27.253.115.14]) by zmx1.isc.org (Postfix) with ESMTPSA id 82DE016004C; Tue, 21 Feb 2017 20:55:56 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D8FC96447A57; Wed, 22 Feb 2017 07:55:50 +1100 (EST)
To: Joe Touch <touch@isi.edu>
From: Mark Andrews <marka@isc.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com> <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu> <5F3FA243-F141-4508-9F99-282E05D4DC85@google.com> <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu>
Subject: Re: Purpose of Port 0.
In-reply-to: Your message of "Tue, 21 Feb 2017 12:25:20 -0800." <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu>
Date: Wed, 22 Feb 2017 07:55:50 +1100
Message-Id: <20170221205550.D8FC96447A57@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-L_wg9_5jd__35P0Pg6Ylu1IWrM>
Cc: james woodyatt <jhw@google.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 20:57:18 -0000

In message <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu>, Joe Touch writes:
> Hi James,
> 
> 
> On 2/21/2017 12:05 PM, james woodyatt wrote:
> > On Feb 20, 2017, at 08:10, Joe Touch <touch@isi.edu
> > <mailto:touch@isi.edu>> wrote:
> >>
> >> There is no IANA registry for source ports, nor should there be.
> >> Ports in the incoming first-contact are swapped, as indicated in RFCs
> >> 768 and 793. Source ports indicate "who to call back", and "0" is
> >> indicated in UDP (RFC768) as "nobody" and TCP (RFC793)
> >
> > p1. Port zero is currently Unassigned for the SCTP and DCCP standard
> > transports and all the other non-standard transports listed in the
> > Protocol Numbers registry.
> 
> Per RFC6335, there is one registry for all transport port numbers.
> "RESERVED" in that registry applies to all transports.
> 
> > p2. Port zero is a System Port, so the process for assigning its IANA
> > registration is RFC 6335, section 8.1.2, which says:
> Agreed.
> 
> > p3. Port zero is already reserved for SCTP by RFC 4960. IANA just
> > needs to correct its registry to show that port zero is Assigned.
> Per section 14.5, SCTP uses the existing transport port registry. It
> lists a set of assignments starting at port 9, but does not request
> assignment of 0.
> 
> Section 3.1 prohibits the use of 0 as either source or destination port,
> but that's not an assignment. That's a prohibition, and not indicated as
> a reservation in the IANA Considerations (Sec 14).
> 
> > p4. Port zero is not reserved for DCCP by RFC 4340, so port zero
> > remains Unassigned there at this point.
> 
> It remains RESERVED (as per the ports registry) but potentially
> assignable to DCCP.
> 
> > p5. Port zero is already reserved in their respective RFCs for a few
> > of the non-standard transports listed in the Protocol Numbers
> > registry, but being non-standard transports, there’s no way to assign
> > them for those protocols under the procedure in RFC 6335.
> 
> "RESERVED" would involve IANA Considerations, and that act would have
> resulted in their being recorded in the IANA registry.
> 
> Prohibitions within the protocol do not result in IANA actions.
> 
> > I’m guessing the POSIX community could attempt to write an Internet
> > Draft that expressly assigned port zero across all known and unknown
> > transport protocols to the “unspecified service number” semantic that
> > it uses,
> 
> IMO, an RFC that needs an API to pass the value "unspecified" should
> indicate just that. It would be far out of scope for an RFC to indicate
> the *value* passed in an API to indicate that parameter.
> 
> Joe

Indeed.  0 is just overloaded in the BSD socket API.  You need to
use raw sockets to send from port 0 when it shouldn't even be a
reserved source port as you are not expecting return traffic.

We actually need a mechanism to allow 0 to be used as a source port.
setsockopts saying to assign source 0 or a bind0() system call would
be better than using a raw socket.  But these are API issues.

What's really annoying for developers is the when the IETF did
actually specfiy parts of the socket API for IPv6, POSIX only pulled
over half of it.  If developers need to use the advanced half of
the API they need to do all sorts of different tricks per platform
to get them.

Basic Socket Interface Extensions for IPv6 and Advanced Sockets API
for IPv6 are designed to be used together but POSIX has only pulled
in Basic Socket Interface Extensions for IPv6.  That like only
taking the left shoe and throwing the right shoe in the bin when
you buy a pair of shoes.

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


From nobody Tue Feb 21 13:29:59 2017
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 631A9129CFC for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 13:29:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 LrdS9WN7_Oy8 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 13:29:57 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 22FEA129CEF for <ietf@ietf.org>; Tue, 21 Feb 2017 13:29:53 -0800 (PST)
Received: from [128.9.184.189] ([128.9.184.189]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1LLTCGD023442 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Feb 2017 13:29:13 -0800 (PST)
Subject: Re: Purpose of Port 0.
To: Mark Andrews <marka@isc.org>
References: <SG2PR06MB07108AF14AC5444D60CDBD36C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <15033982-70a3-0aa2-01a5-570528b36eeb@bogus.com> <SG2PR06MB071061291C3DC252AA62FCB2C15E0@SG2PR06MB0710.apcprd06.prod.outlook.com> <20170220110733.5D144643B8DF@rock.dv.isc.org> <71C934EA2783BD38959023DD@JcK-HP5.jck.com> <TY1PR06MB0718077BC600CC9B2E5A261AC15E0@TY1PR06MB0718.apcprd06.prod.outlook.com> <378f2cb7-66cc-0d3f-c864-6719b177c053@isi.edu> <5F3FA243-F141-4508-9F99-282E05D4DC85@google.com> <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu> <20170221205550.D8FC96447A57@rock.dv.isc.org>
From: Joe Touch <touch@isi.edu>
Message-ID: <ff339adb-5d79-00f4-0039-46de1a6dedcc@isi.edu>
Date: Tue, 21 Feb 2017 13:29:10 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170221205550.D8FC96447A57@rock.dv.isc.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XBjbDEbG45Mh5yToLiFSRtdWWgw>
Cc: james woodyatt <jhw@google.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 21:29:58 -0000

On 2/21/2017 12:55 PM, Mark Andrews wrote:
> In message <8bfcba26-22b6-4258-47dd-872a2d288169@isi.edu>, Joe Touch writes:
>> ...
>> IMO, an RFC that needs an API to pass the value "unspecified" should
>> indicate just that. It would be far out of scope for an RFC to indicate
>> the *value* passed in an API to indicate that parameter.
>>
>> Joe
> Indeed.  0 is just overloaded in the BSD socket API.  You need to
> use raw sockets to send from port 0 when it shouldn't even be a
> reserved source port as you are not expecting return traffic.
FYI, that's required only for UDP traffic (and SCTP prohibits it as
either source or dest). Others allow it.

> We actually need a mechanism to allow 0 to be used as a source port.
> setsockopts saying to assign source 0 or a bind0() system call would
> be better than using a raw socket.  But these are API issues.
>
> What's really annoying for developers is the when the IETF did
> actually specfiy parts of the socket API for IPv6, POSIX only pulled
> over half of it.  If developers need to use the advanced half of
> the API they need to do all sorts of different tricks per platform
> to get them.
>
> Basic Socket Interface Extensions for IPv6 and Advanced Sockets API
> for IPv6 are designed to be used together but POSIX has only pulled
> in Basic Socket Interface Extensions for IPv6.  That like only
> taking the left shoe and throwing the right shoe in the bin when
> you buy a pair of shoes.
Yup. APIs are as difficult to get right as the "packet on the wire" or
state machine parts of a protocol.

Joe


From nobody Tue Feb 21 13:52:47 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CA28129D1A; Tue, 21 Feb 2017 13:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHPJLzKtnW_2; Tue, 21 Feb 2017 13:52:44 -0800 (PST)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::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 191D5129D16; Tue, 21 Feb 2017 13:52:44 -0800 (PST)
Received: by mail-qk0-x233.google.com with SMTP id s186so135636152qkb.1; Tue, 21 Feb 2017 13:52:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qQjaaQvrQNo65QPc+j8RymYtN3nl5Z5EQjeZiPSXONc=; b=f12Rkl/Z9iRBSGcN77ZY8J3UbBcC+Ivd3RJllYOxahW8sLtr+s4c5TrAV/o+znu18+ T7FMtxFoMLUbHu7TowjwApPqcpHfw1YiJgLAdfoKPIqQ5UL1id9En7hIgn4pxQkOxv1s 6HCY3IALDisYR4wmPxHTf+xeNr7N/EvuKjJ12YgiP6Ee2CF2mzC4lOMYIf+98MSVelUT /V1/7+PCA0Dn0ztsXO4acpWQNAOAY+ZoXi5OSMjjkwPLUHZkPEaBJg0XxjIWxBQPrMUn fPIIlMyCCx6WdEBMJ9kOaAOWBZ7xy2giC+iYgdtRAJ6GUhFhONFJJKcnTifcgsqKiPEg 37rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qQjaaQvrQNo65QPc+j8RymYtN3nl5Z5EQjeZiPSXONc=; b=bZKEEp5FcksnWqqOJc9rnUgMo35FdnjY6LrXAaH9nErB34stOUWO/OOZXj5RRyOaV6 nsNbJ4y3fj+gZIRBisEEw6ERrc+QL9w1JNPEc2X4jWBTu+ROLkogj37A00yj4hpvBjlM pPJpwOH83f3bs4Cr2t8T3L9luUSgTkXjg9zCHb/MmuUdcwjBJfAMBrkuPbk7Z3AHwf8/ +6bkhWcX74Zk+MB/ThlVWsfLUf1EXOVGvxTLFmzAJfCpkQX9ggZRCLbSUGe5XVfrMDuc p0eS+K24XcLVPQgw2i0katEkunG6IS/fJvTxdXX2e9hoB7pg4AUH0TnksML+IHH/z8B+ fDcg==
X-Gm-Message-State: AMke39kMV2+MO+gzJRR2TyphvQN09ffoWseMos0lD2522eCOZ561SOBR0ueej5irFLKm+KhOquQFfAQyrhQPKA==
X-Received: by 10.55.200.217 with SMTP id t86mr28482950qkl.5.1487713963154; Tue, 21 Feb 2017 13:52:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.91.71 with HTTP; Tue, 21 Feb 2017 13:52:42 -0800 (PST)
In-Reply-To: <CAO42Z2z6K9tzYCekbyROXR7J1nB9FW53ncTRrW3p3N2P_6WyRQ@mail.gmail.com>
References: <m2y3x6eutl.wl-randy@psg.com> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <2683353.FOTFeJBnXE@linne> <CAO42Z2z6K9tzYCekbyROXR7J1nB9FW53ncTRrW3p3N2P_6WyRQ@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 21 Feb 2017 16:52:42 -0500
Message-ID: <CAL9jLaZMbQaViLm6jms5chDMMYRZym7hN5w_6amACoLx5FqQ4w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a113aa8e84d32d40549116616
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OngDX3jwOgJWNoyGD3Ur5PUs0c0>
Cc: 6man WG <ipv6@ietf.org>, Karsten Thomann <karsten_thomann@linfre.de>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 21:52:46 -0000

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

On Tue, Feb 21, 2017 at 2:56 PM, Mark Smith <markzzzsmith@gmail.com> wrote:

> On 22 February 2017 at 06:21, Karsten Thomann <karsten_thomann@linfre.de>
> wrote:
> > Am Dienstag, 21. Februar 2017, 18:27:39 schrieb Job Snijders:
> >> On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:
> >> > On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders <job@ntt.net> wrote:
> <snip>
> >>
> >> -------
> >>
> >> OLD:
> >>    IPv6 unicast routing is based on prefixes of any valid length up to
> >>    128 [BCP198].  For example, [RFC6164] standardises 127 bit prefixes
> >>    on inter-router point-to-point links.  However, the Interface ID of
> >>    all unicast addresses, except those that start with the binary value
> >>    000, is required to be 64 bits long.  The rationale for the 64 bit
> >>    boundary in IPv6 addresses can be found in [RFC7421]
> >>
> >> NEW:
> >>    IPv6 unicast routing is based on prefixes of any valid length up to
> >>    128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface ID
> >>    of unicast addresses is required to be 64 bits long. In other use
> >>    cases different prefix sizes may be required. For example [RFC6164]
> >>    standardises 127 bit prefixes on inter-router point-to-point links.
> >>    For most use cases, prefix lengths of 64 bits is RECOMMENDED, unless
> >>    there are operational reasons not to do so.
> >
> > Satisfies my desired outcome of the text, but I would like to modify it:
> >     IPv6 unicast routing is based on prefixes of any valid length up to
> >     128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface ID
> >     of unicast addresses is required to be 64 bits long. An exception is
> for
> >     example [RFC6164] which standardises 127 bit prefixes on
> point-to-point
> >     links. The RECOMMENDED prefix length is 64 bit,
>
>
Firstly, the last update to the suggested text seems great to me. As I see
it, operating a reasonably large mixed-mode network... and some smaller
networks around the place... There are operational reasons why /64 makes
sense, for instance: "I just want all these things to get a v6 address, I
don't really care which one" and SLAAC fits that bill.

For my network interfaces I may (for my own reasons) decide that /127 is
perfect for me, and roll out all NNI type interfaces as /127's (hey, I even
helped with the rfc about this) ... for 'operational reasons' I don't care
about SLAAC, so I don't care about /64... and having to 'break the
standard' seems silly. Yes, this case is already taken care of by
RFC6164... but i have servers on which I don't need SLAAC to manage
addressing and simply assign addresses according to some other
systems-management automation... I even limit the number of devices per
subnet for internal reasons, so I don't need a /64 there, I just need a
/124.

I think the idea that some 'applications' need /64 is fine... but making
'all the things must be /64' just silly, in light of the actual deployment
and use-cases today. Therefore, the text as proposed above seems on target.

There have certainly been plenty of baked-in (to asics and/or software)
assumptions about /64 over the years, we shouldn't want that to happen
longer term and wording like:

  "However, the Interface ID of
   all unicast addresses, except those that start with the binary value
   000, is required to be 64 bits long"

ends up letting people make assumptions again, which get baked into
code/asics :(

It has to be stronger than a RECOMMENDED, because that implies it is
> an arbitrary choice that won't have any protocol operational and
> privacy or security impacts. That is not the case.
>

Someone else pointed out that the 2119 language isn't used/referenced in
4291, looking quickly:
  $ grep MUST rfc4291.txt

  $

seems to agree with that assertion... so I don't think "RECOMMENDED" is
right here, I think: "recommended" is correct.. and that since 2119 isn't
used you can't expect anything in the document to actually be binding :(
whoops! Also, /64 really was an 'arbitrary choice' ... more or less anyway.
Trusting in people to follow without MUST/SHOULD/RECOMMENDED seems a bit
crazy, but :)

thanks job@ for making a suggested fix here, I too am troubled by the
'classful' ideas in the ipv6 space, those didn't seem useful long-term in
ipv4 so I can't see how they would be useful in the short-term here in
v6-land.

I'm really not a fan of the: "But this makes subnetting easy!" arguments...
i don't think those hold water since we have tooling to do subnetting, it's
just not a problem looking for a solution anymore.

-chris

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 21, 2017 at 2:56 PM, Mark Smith <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><span class=3D"gmail-">On 22 February 2017 at 06:21, Karsten Thomann &lt=
;<a href=3D"mailto:karsten_thomann@linfre.de">karsten_thomann@linfre.de</a>=
&gt; wrote:<br>
&gt; Am Dienstag, 21. Februar 2017, 18:27:39 schrieb Job Snijders:<br>
&gt;&gt; On Tue, Feb 21, 2017 at 09:49:32AM +0900, Lorenzo Colitti wrote:<b=
r>
&gt;&gt; &gt; On Tue, Feb 21, 2017 at 8:57 AM, Job Snijders &lt;<a href=3D"=
mailto:job@ntt.net">job@ntt.net</a>&gt; wrote:<br>
</span>&lt;snip&gt;<br>
<span class=3D"gmail-">&gt;&gt;<br>
&gt;&gt; -------<br>
&gt;&gt;<br>
&gt;&gt; OLD:<br>
&gt;&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any vali=
d length up to<br>
&gt;&gt;=C2=A0 =C2=A0 128 [BCP198].=C2=A0 For example, [RFC6164] standardis=
es 127 bit prefixes<br>
&gt;&gt;=C2=A0 =C2=A0 on inter-router point-to-point links.=C2=A0 However, =
the Interface ID of<br>
&gt;&gt;=C2=A0 =C2=A0 all unicast addresses, except those that start with t=
he binary value<br>
&gt;&gt;=C2=A0 =C2=A0 000, is required to be 64 bits long.=C2=A0 The ration=
ale for the 64 bit<br>
&gt;&gt;=C2=A0 =C2=A0 boundary in IPv6 addresses can be found in [RFC7421]<=
br>
&gt;&gt;<br>
&gt;&gt; NEW:<br>
&gt;&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any vali=
d length up to<br>
&gt;&gt;=C2=A0 =C2=A0 128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] =
the Interface ID<br>
&gt;&gt;=C2=A0 =C2=A0 of unicast addresses is required to be 64 bits long. =
In other use<br>
&gt;&gt;=C2=A0 =C2=A0 cases different prefix sizes may be required. For exa=
mple [RFC6164]<br>
&gt;&gt;=C2=A0 =C2=A0 standardises 127 bit prefixes on inter-router point-t=
o-point links.<br>
&gt;&gt;=C2=A0 =C2=A0 For most use cases, prefix lengths of 64 bits is RECO=
MMENDED, unless<br>
&gt;&gt;=C2=A0 =C2=A0 there are operational reasons not to do so.<br>
&gt;<br>
&gt; Satisfies my desired outcome of the text, but I would like to modify i=
t:<br>
&gt;=C2=A0 =C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any va=
lid length up to<br>
&gt;=C2=A0 =C2=A0 =C2=A0128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66=
] the Interface ID<br>
&gt;=C2=A0 =C2=A0 =C2=A0of unicast addresses is required to be 64 bits long=
. An exception is for<br>
&gt;=C2=A0 =C2=A0 =C2=A0example [RFC6164] which standardises 127 bit prefix=
es on point-to-point<br>
&gt;=C2=A0 =C2=A0 =C2=A0links. The RECOMMENDED prefix length is 64 bit,<br>
<br></span></blockquote><div><br></div><div>Firstly, the last update to the=
 suggested text seems great to me. As I see it, operating a reasonably larg=
e mixed-mode network... and some smaller networks around the place... There=
 are operational reasons why /64 makes sense, for instance: &quot;I just wa=
nt all these things to get a v6 address, I don&#39;t really care which one&=
quot; and SLAAC fits that bill.</div><div><br></div><div>For my network int=
erfaces I may (for my own reasons) decide that /127 is perfect for me, and =
roll out all NNI type interfaces as /127&#39;s (hey, I even helped with the=
 rfc about this) ... for &#39;operational reasons&#39; I don&#39;t care abo=
ut SLAAC, so I don&#39;t care about /64... and having to &#39;break the sta=
ndard&#39; seems silly. Yes, this case is already taken care of by RFC6164.=
.. but i have servers on which I don&#39;t need SLAAC to manage addressing =
and simply assign addresses according to some other systems-management auto=
mation... I even limit the number of devices per subnet for internal reason=
s, so I don&#39;t need a /64 there, I just need a /124.</div><div><br></div=
><div>I think the idea that some &#39;applications&#39; need /64 is fine...=
 but making &#39;all the things must be /64&#39; just silly, in light of th=
e actual deployment and use-cases today. Therefore, the text as proposed ab=
ove seems on target.</div><div>=C2=A0</div><div>There have certainly been p=
lenty of baked-in (to asics and/or software) assumptions about /64 over the=
 years, we shouldn&#39;t want that to happen longer term and wording like:<=
br><br>=C2=A0 &quot;However, the Interface ID of</div><div>=C2=A0 =C2=A0all=
 unicast addresses, except those that start with the binary value</div><div=
>=C2=A0 =C2=A0000, is required to be 64 bits long&quot;</div><div><br></div=
><div>ends up letting people make assumptions again, which get baked into c=
ode/asics :(</div><div><br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><span class=3D"gmail-">
</span>It has to be stronger than a RECOMMENDED, because that implies it is=
<br>
an arbitrary choice that won&#39;t have any protocol operational and<br>
privacy or security impacts. That is not the case.<br></blockquote><div><br=
></div><div>Someone else pointed out that the 2119 language isn&#39;t used/=
referenced in 4291, looking quickly:<br><div>=C2=A0 $ grep MUST rfc4291.txt=
</div><div><br></div></div><div>=C2=A0 $</div><div><br></div><div>seems to =
agree with that assertion... so I don&#39;t think &quot;RECOMMENDED&quot; i=
s right here, I think: &quot;recommended&quot; is correct.. and that since =
2119 isn&#39;t used you can&#39;t expect anything in the document to actual=
ly be binding :( whoops! Also, /64 really was an &#39;arbitrary choice&#39;=
 ... more or less anyway. Trusting in people to follow without MUST/SHOULD/=
RECOMMENDED seems a bit crazy, but :)</div><div><br></div><div>thanks job@ =
for making a suggested fix here, I too am troubled by the &#39;classful&#39=
; ideas in the ipv6 space, those didn&#39;t seem useful long-term in ipv4 s=
o I can&#39;t see how they would be useful in the short-term here in v6-lan=
d.</div><div><br></div><div>I&#39;m really not a fan of the: &quot;But this=
 makes subnetting easy!&quot; arguments... i don&#39;t think those hold wat=
er since we have tooling to do subnetting, it&#39;s just not a problem look=
ing for a solution anymore.</div><div></div></div><br>-chris</div></div>

--001a113aa8e84d32d40549116616--


From nobody Tue Feb 21 14:02:03 2017
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC980129D27; Tue, 21 Feb 2017 14:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1ybju2Fxr21p; Tue, 21 Feb 2017 14:01:56 -0800 (PST)
Received: from mail-io0-x244.google.com (mail-io0-x244.google.com [IPv6:2607:f8b0:4001:c06::244]) (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 33F53129D22; Tue, 21 Feb 2017 14:01:56 -0800 (PST)
Received: by mail-io0-x244.google.com with SMTP id m98so5420549iod.2; Tue, 21 Feb 2017 14:01:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=r9jXsT3eq4b79zQO6MiuAStNnQaa9ubvBPrRZ2Q0BvI=; b=QL6UYRed5VUpD3Wkjz9P8fZP7pZ4iFFrbTgD8SnkNytXFm3w8KFySsaQKqoW/dsWkp f5GKmhAUVykY6M508Q9P2Yxja54vuM7Q3B7bHF058IajC/f8VKoWyiEl5EKCp1I8MPyp rPIZ/uKIbXnPt8jCzI06SAl0xvF1k4Yj5ptmTb9yKoMztN5GkUuLerR67Xga1dnp4xdb QITk7r5mZ7A9gfgvaHgYrqZVesQO1P+zSLfbIiGvTuwOuncMH0HB4uStYLSPhgfDY/Mi y+wAi5yS9cKw3fS38zpB1GMF59ByBnkm5AsYn7A2htXW0pPiHDJsJLWDtWCIOtP2XaYx NSlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=r9jXsT3eq4b79zQO6MiuAStNnQaa9ubvBPrRZ2Q0BvI=; b=CSGbVvddWYbJOvEdJOmWvcJ7RzDQvvMw+s3OOe1c8s4L2coII8Eiw+ezcxjWilLLNO Dv1Lri24PUS6EqItj1qYl7z1CzRxVzc8nDjB3QJwDrxLNyItdrkbuNGdm61eTQMTf/zo yO5WxMAF+5jES7ktcU4OzKnXZd5a9REDMi38XTTpx8gp9RWSR7hdT0B4X8Y6nUsL5lNu yRTFoFvyCW8GitmlJdV5w4RozhEZjzzpK3yfJk7OEWUS1vwmD8MFuDz/wwIIu/JKqFa3 G65jvsRSNjGiOkr82WjVBafehFR+kEkYsEhmsJEPcBRA1T+KBjumxkQtsXJ+6Uzly6NV 4VBA==
X-Gm-Message-State: AMke39lJkIoStGphogDCfYoJRj6DzBiw7MI9y0h8aI2532fDxwF28XIF/gW2nxKBSnAuB9oMBQXQ5X/FOk+K+g==
X-Received: by 10.107.187.133 with SMTP id l127mr21185733iof.1.1487714515299;  Tue, 21 Feb 2017 14:01:55 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.55.134 with HTTP; Tue, 21 Feb 2017 14:01:54 -0800 (PST)
In-Reply-To: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com>
References: <148768893008.19098.12067836059813292525.idtracker@ietfa.amsl.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 21 Feb 2017 17:01:54 -0500
X-Google-Sender-Auth: 2ddsPmpdDPeB8hWiJFCNTmSjEeQ
Message-ID: <CAC4RtVDuoKFoCckrDYLPKxC2Oj_Ctr9vZSAALBMBk=foW2MdzA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-jsonbis-rfc7159bis-03.txt> (The JavaScript Object Notation (JSON) Data Interchange Format) to Internet Standard
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1XbY0xEcK2PWjDqFHn19o5wn3M4>
Cc: "json@ietf.org" <json@ietf.org>, Alexey Melnikov <alexey.melnikov@isode.com>, draft-ietf-jsonbis-rfc7159bis@ietf.org, jsonbis-chairs@ietf.org, Matt Miller <mamille2@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 22:01:58 -0000

The primary reasons for this document are (1) to advance the
specification to Internet Standard and (2) to normatively align the
IETF and ECMA specifications for JSON.  I support both of those
points, and think this document is ready for approval.

Barry

On Tue, Feb 21, 2017 at 9:55 AM, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Javascript Object Notation
> Update WG (jsonbis) to consider the following document:
> - 'The JavaScript Object Notation (JSON) Data Interchange Format'
>   <draft-ietf-jsonbis-rfc7159bis-03.txt> as Internet Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-07. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    JavaScript Object Notation (JSON) is a lightweight, text-based,
>    language-independent data interchange format.  It was derived from
>    the ECMAScript Programming Language Standard.  JSON defines a small
>    set of formatting rules for the portable representation of structured
>    data.
>
>    This document removes inconsistencies with other specifications of
>    JSON, repairs specification errors, and offers experience-based
>    interoperability guidance.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-jsonbis-rfc7159bis/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>


From nobody Tue Feb 21 14:31:57 2017
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC47129D5E; Tue, 21 Feb 2017 14:31:48 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: David Black <david.black@emc.com>
To: <tsv-art@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com>
Date: Tue, 21 Feb 2017 14:31:48 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eCZgR1OVsKKQ5LEzTnrlNt7Cej0>
Cc: idr@ietf.org, draft-ietf-idr-sla-exchange.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 22:31:48 -0000

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets. 
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.

[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

The following should be done instead:
	- Define TSpecs for two token buckets, a primary/committed token
bucket
		and a secondary/peak token bucket that MUST be nested, i.e.,
traffic
		that is in-profile for the secondary/peak token bucket is always
		in-profile for the primary/committed token bucket.  Some of the
details
		of how to specify this are subtle, see RFC 2698 for a worked
example.
		Use of a secondary/peak token bucket requires use of the primary/
		committed token bucket, but a primary/committed token bucket can be
used
		without a secondary/peak token bucket.
	- For a single token bucket, define two handling TLVs, Committed (in
profile) and
		Excess (out of profile).
	- For two token buckets, define three handling TLVs, Committed (in
profile for both
		token buckets), Peak (out of profile for primary/committed token
bucket, but in
		profile for secondary/peak token bucket) and Excess (out of profile
for both
		token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.

[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.

[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse; it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

      If an advertised SLA ID is different from earlier advertised
one,
      for the same prefix and from the same Source AS, indicates
Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
	- The first three parameters (DSCP, MPLS EXP field in top label,
802.1q priority) can
		and do vary on a link-by-link or LSP-by-LSP basis along a traffic's
network path.
	- The IP address parameters are rather likely to be VPN-specific when
there's more
		than one BGP/MPLS VPN that spans or transits the ASs involved.
	- The transport port parameters need specification of which transport
header and where it
		is located (e.g., for TCP traffic carried by in VXLAN, is this the
inner TCP header
		or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

	- Discussion of possible abuse of this BGP option for
denial-of-service and theft-of-service,
		needs to be added, including possible countermeasures and
mitigations.

	- This sentence at the end of the second paragraph in Section 10 is
content-free:

		   It is NOT RECOMMENDED to enable this attribute at the
		   scale of the Internet unless if means to prevent leaking
sensitive
		   information are enforced.

		What exactly is an implementer or admin supposed to do?  How does
one
		figure out whether an implementation or deployment is  "at the
scale
		of the Internet" ??

	- The next to last paragraph in section 10 is almost content-free, as
it leaves
		decisions on implementation and deployment of key security
functionality as
		"an exercise for the reader" - that's not acceptable.

	- Last, but not least, the final paragraph in Section 10 is a joke
that will
		be lost on a security directorate reviewer - to understand why, see
		Section 2 of RFC 6919, and take note of the publication date of RFC
6919.

------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com  <=== NEW ===
--------------------------------------------------------




From nobody Tue Feb 21 14:44:45 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83767129D78; Tue, 21 Feb 2017 14:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X7Vv_K7L4_RF; Tue, 21 Feb 2017 14:44:43 -0800 (PST)
Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 4EFB7129D22; Tue, 21 Feb 2017 14:44:43 -0800 (PST)
Received: by mail-pg0-x244.google.com with SMTP id 5so20323204pgj.0; Tue, 21 Feb 2017 14:44:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=AlleWqpN8V6foGUBjB8TmWglutzejIgtTpJQwXnkmIY=; b=s2zIyKBeK4URb+A4SSH9GyLULdhWjhTMIN8YUgsfKRPKkTWwEUFPw7tckvNx5sUn67 +Fhv0V/lnStV51G6oJyRmMw+lqZsaOUq20m8/qaLqLDse9G6Re+3CM6wV3QST5v7SSKA L8xT+3EstDdbJpmGi0NzXjFqicPO4+G2jDz9fzKjzKeYy8PtPKYvP5mtXhbP4o6HpL20 AFVhNVi2Nge3wAT0poerlFunaWVkbzRmWQ6bukkD7BMK2Px8/PTSzJUrwFdUbHueYYU7 Ci6wEZLq0LyStR3pzy2qtVELs3rOTUF7NBnJq0VFOzOGnsdWUgIKfQdQsyhsMUVhJVGd 6Jgw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=AlleWqpN8V6foGUBjB8TmWglutzejIgtTpJQwXnkmIY=; b=hMHSOcs2svl6lMafENp+kG1WXzQblIEWwnfomRuObHH7xPiGE6zAmjXFkIzUZjuGn6 X2lW0623g4Z4RKn9EpIYc8k7PJGYagybC7/+21yPlu8fMsg/OXYBrSKPKybZxhbiSClV ZfJiW7O8lmMTvlMbSjaZF8/o9UAq1RuYtZO6KG3eN6IDKJdij6it1/6m8AAxWCRg7OM7 nEKQg45Tf9sVq0pGwdOsmbn68iN+whj2pk1aw7Oazl45P/vHKZw3XNPNDZokHwqODAy9 gtA5NU6yKc+syTGTMw9iK7dinWm4dkoIHHGkfhNRq+1+2itfk/fwIxMaAKoRKFx5GG8J v6jA==
X-Gm-Message-State: AMke39ldevm/c7MygYVJtN2HpmFLB0mjaWb6OCucXCRWXa9ZpV+RRb8wPi3V8/qq8+/ExA==
X-Received: by 10.84.241.138 with SMTP id b10mr43367561pll.32.1487717082654; Tue, 21 Feb 2017 14:44:42 -0800 (PST)
Received: from [130.216.38.132] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.132]) by smtp.gmail.com with ESMTPSA id p15sm42869552pfk.58.2017.02.21.14.44.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 14:44:41 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com>
Date: Wed, 22 Feb 2017 11:44:42 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170221101339.GC84656@Vurt.local>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C3AIMAnkUGDb1XJVMSGnc6o9-78>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 22:44:44 -0000

On 21/02/2017 23:13, Job Snijders wrote:
> On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:
>> On 21/02/2017 13:19, Job Snijders wrote:
>>> On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:=

>>>> There are many reasons for the 64 bit boundary.
>>>> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and =
NPT66
>>>
>>> Irrelevant.
>>
>> Not really. They are both running code. You may not want them in
>> *your* network but that isn't the point. Some people want them.
>>
>> And there is a lot of other running code too, not just SLAAC which is
>> mandatory to implement in every IPv6 host. So this actually trumps all=

>> the other arguments: it's 64 bits because it's 64 bits.
>=20
> When someone utters the phrase "it is X because it is X", the rhetorica=
l
> imperative seems to be to dismiss further conversation (perhaps any
> internal dialogue as well, which may be the primary purpose). "It is
> what it is" therefore, there=E2=80=99s nothing more to be said about it=
=2E..
>=20
> Except when it's not 64 bits?

That wasn't quite my intention. I just wanted to underline that
(like it or not) it was set at 64 bits many years ago and a lot
has been built on that.

=2E..
> I've looked at all configured IPv6 addresses on AS 2914 equipment.
> Interestingly enough, the below table is a reflection of not only NTT's=

> own addressing, and (since AS2914's core function is to connect network=
s
> to each other) also of its peers and customers. In the end, whatever
> makes the thing work is the thing that will be configured.
>=20
> 	/127 - 22%
> 	/126 - 52%
> 	/125 - 0,9%
> 	/124 - 0,5%
> 	/120 - 0,04%
> 	/112 - 0,02%
> 	/64  - 23%

Thanks, that's interesting. So 23% of the devices might have=20
RFC4291-compliant IIDs. The others are configured with 128 bit
IPv6 addresses. Is that correct?

That being so, perhaps the words that are missing are
"The IID length requirement does not apply to interfaces that
are explicitly configured with 128 bit addresses." Because the
requirement is meaningless for such interfaces.

   Brian


From nobody Tue Feb 21 14:57:08 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59619120725; Tue, 21 Feb 2017 14:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8eKkDOvYa6_S; Tue, 21 Feb 2017 14:56:54 -0800 (PST)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::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 87E26120724; Tue, 21 Feb 2017 14:56:54 -0800 (PST)
Received: by mail-qt0-x230.google.com with SMTP id k15so124723508qtg.3; Tue, 21 Feb 2017 14:56:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=EKtdDgo2o0kv4Os+X5jbPEXHxUYL91L64+Ty6j8nrPQ=; b=TEw1Mo4+8N1Gb/1u929dFpKIJbjcM+wpzB4LaIew30b/byU5LgioTUWTK4xxKTLbI7 uNyIVdSSgq4JnOu93xCDXAA87Ieb02Pp9M1fGsWYCh2niWuJXKn9goPu78W45txfQgDB 83d8u3oOtZfpLmJdaPE+KMBnelilygvReqzduncQNHkJ8xq38seK1dpAsROj9zVwJiEP B410gQPBfhge4Wvk6sf458QGow3GjpDkXtHmO+sWbfSm8Dhnm/IOkxPpvxbCk4hDhyI2 rnj/lpMlsztxrJBklgoE6euGgk1bpHm7BzqJip1PxkhiV1IV3izQIM1eWnt4eJEGZ7dX m5SQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=EKtdDgo2o0kv4Os+X5jbPEXHxUYL91L64+Ty6j8nrPQ=; b=DyrYv6gMcXMGSjMAPFZCFcLFRrRNEHCVISGPYJ+PvQaRwlvAGcV0htZBx67ppo5Cxj lwPZ1FOw407yf1mnKk0R3RHzns4RzvQBbiaAI8vrYd2bGinm6OCya7gvOF1csaZreq+F DIV73he01l8q7nSO8uSo4J7dcZCvemXAD+2OGahE/yA/Eff/gspBfHSIynsjPb/F3D3q SL34m7HDMHgMZ1b+ekBfzsvilZvF371uKDw86AsAaiEZHYVh0oQFv57RGNjp8GCvsNyJ 0fk+AcGlPBr5irGMe8RCTo4SmJdbOX/VqGJ88A7Bl8wAsq5zwviEwVjSuvTLojnGVtda XuSQ==
X-Gm-Message-State: AMke39mswCWXUqAqxqHVcgtaXLnN8OwXdq6iBfb/UxYltIdzuP2RMpwZ/RktDnSIa0CIbjw8gT7x4pRLGZsj3w==
X-Received: by 10.237.44.7 with SMTP id f7mr20969767qtd.214.1487717813699; Tue, 21 Feb 2017 14:56:53 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Tue, 21 Feb 2017 14:56:52 -0800 (PST)
In-Reply-To: <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Tue, 21 Feb 2017 17:56:52 -0500
X-Google-Sender-Auth: 9AzFSFbWrniimgFb8v8Nlw4Kwic
Message-ID: <CAL9jLaYy_=d+MePOpL4bfnENTuos-QD07Teme+TUVo3RghzMXA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c05df90cfcd490549124ba3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LyGSdD_eRUSmfi_jv87tNY1p1EU>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 22:57:03 -0000

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

On Tue, Feb 21, 2017 at 5:44 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 21/02/2017 23:13, Job Snijders wrote:
> > On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:
> >> On 21/02/2017 13:19, Job Snijders wrote:
> >>> On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:
> >>>> There are many reasons for the 64 bit boundary.
> >>>> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and
> NPT66
> >>>
> >>> Irrelevant.
> >>
> >> Not really. They are both running code. You may not want them in
> >> *your* network but that isn't the point. Some people want them.
> >>
> >> And there is a lot of other running code too, not just SLAAC which is
> >> mandatory to implement in every IPv6 host. So this actually trumps all
> >> the other arguments: it's 64 bits because it's 64 bits.
> >
> > When someone utters the phrase "it is X because it is X", the rhetorica=
l
> > imperative seems to be to dismiss further conversation (perhaps any
> > internal dialogue as well, which may be the primary purpose). "It is
> > what it is" therefore, there=E2=80=99s nothing more to be said about it=
...
> >
> > Except when it's not 64 bits?
>
> That wasn't quite my intention. I just wanted to underline that
> (like it or not) it was set at 64 bits many years ago and a lot
> has been built on that.
>
>
I think one of the points the thread has brought out is that: "just because
we have always been at war with elbonia, does not mean we have to keep
being at war with elbonia"

We don't have to keep promulgating advice that we don't actually use in
practice... If we set the "Internet Standard" today we can move forward to
a better world in the time it takes to age out old 'broken'
gear/software... (yes, that's a while but eventually :) )


> ...
> > I've looked at all configured IPv6 addresses on AS 2914 equipment.
> > Interestingly enough, the below table is a reflection of not only NTT's
> > own addressing, and (since AS2914's core function is to connect network=
s
> > to each other) also of its peers and customers. In the end, whatever
> > makes the thing work is the thing that will be configured.
> >
> >       /127 - 22%
> >       /126 - 52%
> >       /125 - 0,9%
> >       /124 - 0,5%
> >       /120 - 0,04%
> >       /112 - 0,02%
> >       /64  - 23%
>
> Thanks, that's interesting. So 23% of the devices might have
> RFC4291-compliant IIDs. The others are configured with 128 bit
> IPv6 addresses. Is that correct?
>
> That being so, perhaps the words that are missing are
> "The IID length requirement does not apply to interfaces that
> are explicitly configured with 128 bit addresses." Because the
> requirement is meaningless for such interfaces.
>
>
specifying the 128 here seems wrong... or I'm using it wrong in my
interpretation :)
I would have said:
  "The IID length requirement does not apply to interfaces that are
explicitly configured."

all ipv6 interfaces have 128 addresses, they may have a subnet
configuration which is shorter though. right?

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 21, 2017 at 5:44 PM, Brian E Carpenter <span dir=3D"ltr">&l=
t;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.=
carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><span class=3D"">On 21/02/2017 23:13, Job Snijders wrote:<br>
&gt; On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:<br>
&gt;&gt; On 21/02/2017 13:19, Job Snijders wrote:<br>
&gt;&gt;&gt; On Thu, Feb 16, 2017 at 09:40:01AM +0100, <a href=3D"mailto:ot=
roan@employees.org">otroan@employees.org</a> wrote:<br>
&gt;&gt;&gt;&gt; There are many reasons for the 64 bit boundary.<br>
&gt;&gt;&gt;&gt; - Allowing identifier locator split: 8+8 / GSE that led to=
 ILNP and NPT66<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Irrelevant.<br>
&gt;&gt;<br>
&gt;&gt; Not really. They are both running code. You may not want them in<b=
r>
&gt;&gt; *your* network but that isn&#39;t the point. Some people want them=
.<br>
&gt;&gt;<br>
&gt;&gt; And there is a lot of other running code too, not just SLAAC which=
 is<br>
&gt;&gt; mandatory to implement in every IPv6 host. So this actually trumps=
 all<br>
&gt;&gt; the other arguments: it&#39;s 64 bits because it&#39;s 64 bits.<br=
>
&gt;<br>
&gt; When someone utters the phrase &quot;it is X because it is X&quot;, th=
e rhetorical<br>
&gt; imperative seems to be to dismiss further conversation (perhaps any<br=
>
&gt; internal dialogue as well, which may be the primary purpose). &quot;It=
 is<br>
&gt; what it is&quot; therefore, there=E2=80=99s nothing more to be said ab=
out it...<br>
&gt;<br>
&gt; Except when it&#39;s not 64 bits?<br>
<br>
</span>That wasn&#39;t quite my intention. I just wanted to underline that<=
br>
(like it or not) it was set at 64 bits many years ago and a lot<br>
has been built on that.<br>
<br></blockquote><div><br></div><div>I think one of the points the thread h=
as brought out is that: &quot;just because we have always been at war with =
elbonia, does not mean we have to keep being at war with elbonia&quot;</div=
><div><br></div><div>We don&#39;t have to keep promulgating advice that we =
don&#39;t actually use in practice... If we set the &quot;Internet Standard=
&quot; today we can move forward to a better world in the time it takes to =
age out old &#39;broken&#39; gear/software... (yes, that&#39;s a while but =
eventually :) )</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
...<br>
<span class=3D"">&gt; I&#39;ve looked at all configured IPv6 addresses on A=
S 2914 equipment.<br>
&gt; Interestingly enough, the below table is a reflection of not only NTT&=
#39;s<br>
&gt; own addressing, and (since AS2914&#39;s core function is to connect ne=
tworks<br>
&gt; to each other) also of its peers and customers. In the end, whatever<b=
r>
&gt; makes the thing work is the thing that will be configured.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/127 - 22%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/126 - 52%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/125 - 0,9%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/124 - 0,5%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/120 - 0,04%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/112 - 0,02%<br>
&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0/64=C2=A0 - 23%<br>
<br>
</span>Thanks, that&#39;s interesting. So 23% of the devices might have<br>
RFC4291-compliant IIDs. The others are configured with 128 bit<br>
IPv6 addresses. Is that correct?<br>
<br>
That being so, perhaps the words that are missing are<br>
&quot;The IID length requirement does not apply to interfaces that<br>
are explicitly configured with 128 bit addresses.&quot; Because the<br>
requirement is meaningless for such interfaces.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>specifying the 128 here seems wrong... or I&#39;m us=
ing it wrong in my interpretation :)</div><div>I would have said:<br>=C2=A0=
 &quot;The IID length requirement does not apply to interfaces that are exp=
licitly configured.&quot;</div><div><br></div><div>all ipv6 interfaces have=
 128 addresses, they may have a subnet configuration which is shorter thoug=
h. right?</div></div></div></div>

--94eb2c05df90cfcd490549124ba3--


From nobody Tue Feb 21 14:59:33 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0792F126579; Tue, 21 Feb 2017 14:59:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 zu9lmWHqXqaW; Tue, 21 Feb 2017 14:59:28 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 1291E120724; Tue, 21 Feb 2017 14:59:28 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgJOu-0007iy-BH (job@us.ntt.net); Tue, 21 Feb 2017 22:59:27 +0000
Date: Tue, 21 Feb 2017 23:58:57 +0100
From: Job Snijders <job@ntt.net>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170221225857.GE32367@Vurt.local>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vQLlUrFkJutMAVxRK6HtokJms9U>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 22:59:29 -0000

On Wed, Feb 22, 2017 at 11:44:42AM +1300, Brian E Carpenter wrote:
> On 21/02/2017 23:13, Job Snijders wrote:
> > On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:
> >> On 21/02/2017 13:19, Job Snijders wrote:
> >>> On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrote:
> >>>> There are many reasons for the 64 bit boundary.
> >>>> - Allowing identifier locator split: 8+8 / GSE that led to ILNP and NPT66
> >>>
> >>> Irrelevant.
> >>
> >> Not really. They are both running code. You may not want them in
> >> *your* network but that isn't the point. Some people want them.
> >>
> >> And there is a lot of other running code too, not just SLAAC which is
> >> mandatory to implement in every IPv6 host. So this actually trumps all
> >> the other arguments: it's 64 bits because it's 64 bits.
> > 
> > When someone utters the phrase "it is X because it is X", the rhetorical
> > imperative seems to be to dismiss further conversation (perhaps any
> > internal dialogue as well, which may be the primary purpose). "It is
> > what it is" therefore, there’s nothing more to be said about it...
> > 
> > Except when it's not 64 bits?
> 
> That wasn't quite my intention. I just wanted to underline that
> (like it or not) it was set at 64 bits many years ago and a lot
> has been built on that.
> 
> ...
> > I've looked at all configured IPv6 addresses on AS 2914 equipment.
> > Interestingly enough, the below table is a reflection of not only NTT's
> > own addressing, and (since AS2914's core function is to connect networks
> > to each other) also of its peers and customers. In the end, whatever
> > makes the thing work is the thing that will be configured.
> > 
> > 	/127 - 22%
> > 	/126 - 52%
> > 	/125 - 0,9%
> > 	/124 - 0,5%
> > 	/120 - 0,04%
> > 	/112 - 0,02%
> > 	/64  - 23%
> 
> Thanks, that's interesting. So 23% of the devices might have 
> RFC4291-compliant IIDs. The others are configured with 128 bit
> IPv6 addresses. Is that correct?

The percentage is not the percentage of devices, but the percentage of
interconnections. In all instances the addresses are staticly
configured.

Back to my example from earlier, to make sure we are on the same page,
this is output from a standard Linux machine:

    job@tardis:~$ sudo ip -6 addr add 2001:728:1808:1::21/126 dev eth1
    job@tardis:~$ sudo ip -6 addr show dev eth1
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
        inet6 2001:728:1808:1::21/126 scope global
           valid_lft forever preferred_lft forever
        inet6 fe80::20d:b9ff:fe41:d4f5/64 scope link
           valid_lft forever preferred_lft forever
    job@tardis:~$ 

Most network engineers would call the above example "configuring a /126
on an interface" - but am I understanding correctly that in your
taxonomy you would call this "configuring a 128 bit IPv6 address"?

> That being so, perhaps the words that are missing are
> "The IID length requirement does not apply to interfaces that
> are explicitly configured with 128 bit addresses." Because the
> requirement is meaningless for such interfaces.

The terminology might confuse some people, as in common language when
one configures "a /128", or 'a 128 bit address', it usually means you
are configuring something like a loopback address.

Perhaps:

    "The IID length requirement does not apply to interfaces that are
    explicitly configured without autoconfiguration."

(perhaps even remove the word 'explicitly')

    "The IID length requirement does not apply to interfaces that are
    configured without autoconfiguration."

Kind regards,

Job


From nobody Tue Feb 21 15:24:01 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7611D1293DB; Tue, 21 Feb 2017 15:24:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yVS3q6VQ5g1D; Tue, 21 Feb 2017 15:23:59 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 36490126D73; Tue, 21 Feb 2017 15:23:59 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 5so20453931pgj.0; Tue, 21 Feb 2017 15:23:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=xx9Z2zRGlsJCdszOpYV7sNZIUZ6y5TYLSlhUNs/HNcE=; b=VwI51e1W3ibf2PoDEYI0uXsmu1KcTYSv8STNz7nSTUAlzVIEnU6Xp3hgebgkX30v52 HNhtzXrrWb3nuvxhSPu5PQdyzFUWd326oq2KNtsCkH0qZuPboB+MsZkf/H34eGqOFRtY ANA96aEhIZKumpp/BT7PtVOgw7UGbeYflk9kSlwys/TseSlvZmu9jXpfEaykuzh9Scwt 5YyyIYMZPbK8HFwXq7CKbcfVZqFCGsywwk4TwCMzkN/ZiY8XCVoNagYWc1hCbhvqt4sy KxlO21zdGtWNLF6asBQkHrJO9LRruBsXaTf++DhNz9+ENMI5j6mVBj+BfRJMZSUmIKpb Q6hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=xx9Z2zRGlsJCdszOpYV7sNZIUZ6y5TYLSlhUNs/HNcE=; b=XHm0uvw4V8I4kug+C7ZdOPy5mw1Y2L1FFXvu2xcE82/qyJVqC943hunWUCghFxtnH1 OjcbCH32aUQn5N//ozjSGma1ko+oHgFrbLF2LxwoA9PwK5d16YQyaa0e7bfR2ttrouif 2X7ut6fMCaJkda4mkg4vkJChVt1y/2p/xLS3EmrBSM6WxDlTSL8XOB5a8qcWP7hiHY8N LsQmzdLR5xzpSpxAD19LfI6GrkWRLS/5zld15QNqk8EX3vGWPLsto/0MlhWi92G7g1VT cgVLzz38NcUOhbh9nXxmAxpz58+iQ9MLdqZSo3YfTBPYx/nH0fHU8Cr+uT3ld9hjGzWI 49mg==
X-Gm-Message-State: AMke39n/3Ci8xhOLrRk51u2RmVHuQqKExgS4CC5FOn3MtnM+d0q+LJwicOKEmLMR/Zt/pg==
X-Received: by 10.98.223.214 with SMTP id d83mr1856868pfl.147.1487719438560; Tue, 21 Feb 2017 15:23:58 -0800 (PST)
Received: from [130.216.38.132] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.38.132]) by smtp.gmail.com with ESMTPSA id 128sm21148593pfe.23.2017.02.21.15.23.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 15:23:57 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com>
Date: Wed, 22 Feb 2017 12:23:17 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170221225857.GE32367@Vurt.local>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0APlpiSPdlT2SZPoKbBRJxNfWaY>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 23:24:00 -0000

On 22/02/2017 11:58, Job Snijders wrote:
> On Wed, Feb 22, 2017 at 11:44:42AM +1300, Brian E Carpenter wrote:
>> On 21/02/2017 23:13, Job Snijders wrote:
>>> On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter wrote:
>>>> On 21/02/2017 13:19, Job Snijders wrote:
>>>>> On Thu, Feb 16, 2017 at 09:40:01AM +0100, otroan@employees.org wrot=
e:
>>>>>> There are many reasons for the 64 bit boundary.
>>>>>> - Allowing identifier locator split: 8+8 / GSE that led to ILNP an=
d NPT66
>>>>>
>>>>> Irrelevant.
>>>>
>>>> Not really. They are both running code. You may not want them in
>>>> *your* network but that isn't the point. Some people want them.
>>>>
>>>> And there is a lot of other running code too, not just SLAAC which i=
s
>>>> mandatory to implement in every IPv6 host. So this actually trumps a=
ll
>>>> the other arguments: it's 64 bits because it's 64 bits.
>>>
>>> When someone utters the phrase "it is X because it is X", the rhetori=
cal
>>> imperative seems to be to dismiss further conversation (perhaps any
>>> internal dialogue as well, which may be the primary purpose). "It is
>>> what it is" therefore, there=E2=80=99s nothing more to be said about =
it...
>>>
>>> Except when it's not 64 bits?
>>
>> That wasn't quite my intention. I just wanted to underline that
>> (like it or not) it was set at 64 bits many years ago and a lot
>> has been built on that.
>>
>> ...
>>> I've looked at all configured IPv6 addresses on AS 2914 equipment.
>>> Interestingly enough, the below table is a reflection of not only NTT=
's
>>> own addressing, and (since AS2914's core function is to connect netwo=
rks
>>> to each other) also of its peers and customers. In the end, whatever
>>> makes the thing work is the thing that will be configured.
>>>
>>> 	/127 - 22%
>>> 	/126 - 52%
>>> 	/125 - 0,9%
>>> 	/124 - 0,5%
>>> 	/120 - 0,04%
>>> 	/112 - 0,02%
>>> 	/64  - 23%
>>
>> Thanks, that's interesting. So 23% of the devices might have=20
>> RFC4291-compliant IIDs. The others are configured with 128 bit
>> IPv6 addresses. Is that correct?
>=20
> The percentage is not the percentage of devices, but the percentage of
> interconnections. In all instances the addresses are staticly
> configured.

OK, but from the outside I can't know that for the /64 subnets.

> Back to my example from earlier, to make sure we are on the same page,
> this is output from a standard Linux machine:
>=20
>     job@tardis:~$ sudo ip -6 addr add 2001:728:1808:1::21/126 dev eth1
>     job@tardis:~$ sudo ip -6 addr show dev eth1
>     3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000
>         inet6 2001:728:1808:1::21/126 scope global
>            valid_lft forever preferred_lft forever
>         inet6 fe80::20d:b9ff:fe41:d4f5/64 scope link
>            valid_lft forever preferred_lft forever
>     job@tardis:~$=20
>=20
> Most network engineers would call the above example "configuring a /126=

> on an interface" - but am I understanding correctly that in your
> taxonomy you would call this "configuring a 128 bit IPv6 address"?

Well that does two things: configures a 128 bit address (as Chris points
out, *all* addresses are 128 bits, duh) and associates a prefix length
with it, which afaik is optional. But the interface has already
auto-configured a link-local address, with a 64 bit IID. So yes, that's
exactly what I mean.

>=20
>> That being so, perhaps the words that are missing are
>> "The IID length requirement does not apply to interfaces that
>> are explicitly configured with 128 bit addresses." Because the
>> requirement is meaningless for such interfaces.
>=20
> The terminology might confuse some people, as in common language when
> one configures "a /128", or 'a 128 bit address', it usually means you
> are configuring something like a loopback address.
>=20
> Perhaps:
>=20
>     "The IID length requirement does not apply to interfaces that are
>     explicitly configured without autoconfiguration."
>=20
> (perhaps even remove the word 'explicitly')
>=20
>     "The IID length requirement does not apply to interfaces that are
>     configured without autoconfiguration."

Personally I think that's right. (However, if you manually configure
an address that matches a pre-existing prefix announced by an RA,
it will be assumed to belong to that prefix. I've done that by
hand on Windows, not sure I've done it in Linux.)

   Brian


From nobody Tue Feb 21 15:29:04 2017
Return-Path: <nrooney@gsma.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885701293DF; Tue, 21 Feb 2017 15:28:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gsmasso.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8c4av7skV_0; Tue, 21 Feb 2017 15:28:55 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-db5eur01on0066.outbound.protection.outlook.com [104.47.2.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71DF21204D9; Tue, 21 Feb 2017 15:28:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=GSMASSO.onmicrosoft.com; s=selector1-gsma-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=6gYsPkN2X4IWhAAmUHZhoKkTQ3QWAJTPSl4GK0E9/dA=; b=iXgGDNAoP7dsubF5/cLUyvW89P9uNSTwtNikM3rWx0pbiGaRlVMFsJNX3esjv7I1B28pWAQ+R8VjYBlHu0DoEiZnNU5AZ7aRZpiY2C3ZpuV7AmlU6glaKFgXONvnmWxwekqRGZMqD7zTQhym6xij7C+48eSthfeY9NqkSTUU4H0=
Received: from HE1PR04MB3113.eurprd04.prod.outlook.com (10.171.196.31) by HE1PR04MB3116.eurprd04.prod.outlook.com (10.171.196.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.13; Tue, 21 Feb 2017 23:28:51 +0000
Received: from HE1PR04MB3113.eurprd04.prod.outlook.com ([10.171.196.31]) by HE1PR04MB3113.eurprd04.prod.outlook.com ([10.171.196.31]) with mapi id 15.01.0919.018; Tue, 21 Feb 2017 23:28:51 +0000
From: Natasha Rooney <nrooney@gsma.com>
To: Dale Worley <worley@ariadne.com>, "slim@ietf.org" <slim@ietf.org>
Subject: Re: Review of draft-ietf-slim-negotiating-human-language-06
Thread-Topic: Review of draft-ietf-slim-negotiating-human-language-06
Thread-Index: AQHSiY9AG5SIuWMvTkWvq4pl7gSV96F0IWOA
Date: Tue, 21 Feb 2017 23:28:50 +0000
Message-ID: <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
In-Reply-To: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nrooney@gsma.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.39.120.58]
x-ms-office365-filtering-correlation-id: b1762689-c66c-48c4-64f5-08d45ab164ab
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR04MB3116;
x-microsoft-exchange-diagnostics: 1; HE1PR04MB3116; 7:qs5+nnuX0DtYS8RoxUf1I18DpTDPshEzm+uo1/rvUyBm4byHHnWwza8a2l2Qv+p61CRqGXim7FxRw7XIzz4p+qgAEqWcCHo4S1BYT8Kjg4Wqf4vJE9RSqVjwB17D7qKHg+91gfgW1JfRszpq51UH94Y/9W2L3lJO4LDsnCgBS6Uv9kyVUjGcFucOToah0NatAdZ5Pbubvfv0ATkufh3YJ6MASJxz1N8WpB5VKdiGMJwxwZ5JDK/b4SGH+0zy1EK56TQGznWaVP/5jNXTlf1w78tO8vM+VGpIvgpEaP1/ALeiyu8UBTG7TOKbvMoh+Gn2zWtK8p1aJohmhdCrgqg/zw==
x-microsoft-antispam-prvs: <HE1PR04MB311636487A0B8ACC21D3F164C3510@HE1PR04MB3116.eurprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123558025)(20161123560025)(6072148); SRVR:HE1PR04MB3116; BCL:0; PCL:0; RULEID:; SRVR:HE1PR04MB3116; 
x-forefront-prvs: 0225B0D5BC
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(7916002)(39450400003)(51914003)(189002)(377424004)(199003)(66654002)(24454002)(50986999)(5660300001)(76176999)(36756003)(122556002)(2950100002)(38730400002)(6246003)(53936002)(2906002)(77096006)(606005)(83716003)(5890100001)(6506006)(57306001)(66066001)(102836003)(6486002)(229853002)(6116002)(2501003)(3846002)(6306002)(25786008)(6436002)(82746002)(6512007)(54896002)(99286003)(236005)(54906002)(92566002)(97736004)(189998001)(4326007)(3280700002)(86362001)(3660700001)(68736007)(33656002)(2900100001)(53546006)(50226002)(105586002)(7906003)(106116001)(81166006)(81156014)(7736002)(106356001)(8676002)(8936002)(101416001)(561944003)(230783001)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:HE1PR04MB3116; H:HE1PR04MB3113.eurprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: gsma.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_"
MIME-Version: 1.0
X-OriginatorOrg: gsma.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Feb 2017 23:28:50.8396 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72a4ff82-fec3-469d-aafb-ac8276216699
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR04MB3116
X-MS-Exchange-CrossPremises-AuthAs: Internal
X-MS-Exchange-CrossPremises-AuthMechanism: 04
X-MS-Exchange-CrossPremises-AuthSource: HE1PR04MB3113.eurprd04.prod.outlook.com
X-MS-Exchange-CrossPremises-SCL: 1
X-MS-Exchange-CrossPremises-messagesource: StoreDriver
X-MS-Exchange-CrossPremises-BCC: 
X-MS-Exchange-CrossPremises-originalclientipaddress: 217.39.120.58
X-MS-Exchange-CrossPremises-avstamp-service: 1.0
X-MS-Exchange-CrossPremises-disclaimer-hash: 78ca8040c6722e32c2f5b0a45bf37e74b9409d645a53be96aa19958e0cee0f00
X-MS-Exchange-CrossPremises-antispam-scancontext: DIR:Originating; SFV:NSPM; SKIP:0; 
X-MS-Exchange-CrossPremises-processed-by-journaling: Journal Agent
X-OrganizationHeadersPreserved: HE1PR04MB3116.eurprd04.prod.outlook.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UU26GK_QfmPP_DrJLdOFzG1yopg>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-slim-negotiating-human-language.all@ietf.org" <draft-ietf-slim-negotiating-human-language.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Feb 2017 23:28:59 -0000

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgRGFsZSEgTWFueSB0aGFua3MgZm9yIHRoZXNlIGNvbW1lbnRzLCBhcyBvbmUgb2YgdGhlIFNM
SU0gY2hhaXJzIEnigJlsbCB3b3JrIG9uIGdldHRpbmcgc29tZSBhbnN3ZXJzIHRvIHlvdSBvciBJ
4oCZbGwgcmVxdWVzdCB0aGUgYXV0aG9yIG9yIG9uZSBvZiB0aGUgU0xJTSBhY3RpdmUgcGFydGlj
aXBhbnRzIHRvIHJlc3BvbmQuDQoNCkJlcm5hcmQsIFJhbmRhbGwgYW5kIFNMSU0gLSBzZWUgYmVs
b3cgcmUgRGFsZeKAmXMgcG9pbnRzLg0KDQoqKioqIEEuIENhbGwgZmFpbHVyZSAqKioqDQpSYW5k
YWxsIG9yIEJlcm5hcmQgY2FuIHlvdSByZXNwb25kIHRvIHRoaXM/IEkgaW1hZ2luZSB0aGUgVUEg
Y2FsbCBmYWlsdXJlIG1ldGhvZCBpcyBVQSBzcGVjaWZpYywgYnV0IGlmIHRoZXJlIGlzIGEgY2xh
c2ggd2l0aCBTSVAgbGV2ZWwgY2FsbCBmYWlsIHRoZW4gdGhpcyBzaG91bGQgYmUgYWRkcmVzc2Vk
Lg0KDQoqKioqIEIuIEF1ZGlvL1ZpZGVvIGNvb3JkaW5hdGlvbiAqKioqDQpJIGJlbGlldmUgdGhl
IHRoZW9yeSBiZWhpbmQgdGhlIGN1cnJlbnQgZHJhZnQgaXMgdGhhdCB0aGUgc3Bva2VuIGFuZCB2
aWRlbyBzdHJlYW1zIHdpbGwgYmUgZGlmZmVyZW50IGluIHRoZSBjYXNlcyBvZiBzdWNoIHRoaW5n
cyBhcyBzaWduIGxhbmd1YWdlLiBWaWRlbyBjb3VsZCB0aGVyZWZvcmUgYmUgc2lnbiBhbmQgYXVk
aW8gd291bGQgYmUgYSBzcG9rZW4gbGFuZ3VhZ2UuIEnigJltIG5vdCBzdXJlIGlmIHRoZSBzdWdn
ZXN0aW9uIGhlIHNhdGlzZmllcyB0aGlzIGNhc2U/DQoNCioqKiogQy4gImh1bWludGxhbmciIHNl
ZW1zIGxvbmcgdG8gbWUgKioqKg0KQmVybmFyZCAtIEkgZG9u4oCZdCBzZWUgdGhlIGlzc3VlIHdp
dGggc2hvcnRlbmluZyBodW1pbnRsYW5nLCBidXQgdGhlIGdyb3VwIG1pZ2h0LiBJIHN1Z2dlc3Qg
d2UgdGhyb3cgdGhpcyB0byB0aGUgZ3JvdXAgZm9yIGRpc2N1c3Npb24uDQoNCioqKiogRC4gVXNl
IHRoZSBBY2NlcHQtTGFuZ3VhZ2Ugc3ludGF4ICoqKioNClJhbmRhbGwgYW5kIEJlcm5hcmQgLSBp
cyB0aGlzIGFuIGFjY2VwdGFibGUgY2hhbmdlPyBPciBvbmUgd2UgbmVlZCB0byBkaXNjdXNzIGZ1
cnRoZXIuIFNlZW1zIGxpa2UgYSByZWFzb25hYmxlIHJlcXVlc3QsIGJ1dCBhbHNvIGEgbGFyZ2Vy
IGNoYW5nZSwgd2hpY2ggaXMgd2h5IEkgYXNrIQ0KDQoqKioqIEUuIEhhdmUgYW4gYXR0cmlidXRl
IHRvIGFiYnJldmlhdGUgdGhlIGJpZGlyZWN0aW9uYWxseS1zeW1tZXRyaWMgY2FzZSAqKioqDQpJ
IGRvIG5vdCByZW1lbWJlciB1cyBoYXZpbmcgdGhpcyBkaXNjdXNzaW9uIHdpdGhpbiB0aGUgZ3Jv
dXAsIGFsdGhvdWdoIGl0IG1heSBoYXZlIG9jY3VycmVkIGJlZm9yZSBJIGJlY2FtZSBjaGFpci4N
ClJhbmRhbGwsIEJyaWFuIG9yIEJlcm5hcmQgLSBoYXMgdGhpcyBpZGVhIGJlZW4gZGlzY3Vzc2Vk
IGJlZm9yZT8gSWYgc28sIGNhbiBvbmUgb2YgeW91IHJlc3BvbmQgd2l0aCBhbiBleHBsYW5hdGlv
biBhcyB0byB3aHkgd2UgaGF2ZW7igJl0IGRvbmUgdGhpcz8NCg0KKioqKiBFZGl0b3JpYWwgY29t
bWVudHMgYW5kIG5pdHMgKioqKioNClJhbmRhbGwgLSBjYW4geW91IHRha2UgYSBsb29rIHRocm91
Z2ggRGFsZeKAmXMgZWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBzaG91dCBpZiB0aGVyZSBpcyBhbnkg
cHJvYmxlbXMgd2l0aCB0aGVzZSBzdWdnZXN0aW9uczsgaWYgZXZlcnl0aGluZyBpcyBvayBwbGVh
c2UgbWFrZSB0aGUgY2hhbmdlcy4NCg0KVGhhbmtzIGFsbCENCg0KTmF0YXNoYSBSb29uZXkgfCBJ
bnRlcm5ldCBFbmdpbmVlcmluZyBEaXJlY3RvciB8IEludGVybmV0IGFuZCBXZWIgVGVhbSB8IFRl
Y2hub2xvZ3kgfCBHU01BIHwgbnJvb25leUBnc21hLmNvbTxtYWlsdG86bnJvb25leUBnc21hLmNv
bT4gfCArNDQgKDApIDc3MzAgMjE5IDc2NSB8IEB0aGlzTmF0YXNoYSB8IFNreXBlOiBucm9vbmV5
QGdzbS5vcmc8bWFpbHRvOm5yb29uZXlAZ3NtLm9yZz4NCg0KT24gMTggRmViIDIwMTcsIGF0IDAy
OjMyLCBEYWxlIFdvcmxleSA8d29ybGV5QGFyaWFkbmUuY29tPG1haWx0bzp3b3JsZXlAYXJpYWRu
ZS5jb20+PiB3cm90ZToNCg0KUmV2aWV3ZXI6IERhbGUgV29ybGV5DQpSZXZpZXcgcmVzdWx0OiBS
ZWFkeSB3aXRoIE5pdHMNCg0KSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3Ig
dGhpcyBkcmFmdC4gIFRoZSBHZW5lcmFsIEFyZWENClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZp
ZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQNCmJ5IHRoZSBJRVNHIGZvciB0
aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0DQpsaWtlIGFu
eSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVh
c2Ugc2VlIHRoZSBGQVEgYXQNCjxodHRwOi8vd2lraS50b29scy5pZXRmLm9yZy9hcmVhL2dlbi90
cmFjL3dpa2kvR2VuQXJ0ZmFxPi4NCg0KRG9jdW1lbnQ6ICBkcmFmdC1pZXRmLXNsaW0tbmVnb3Rp
YXRpbmctaHVtYW4tbGFuZ3VhZ2UtMDYNClJldmlld2VyOiAgRGFsZSBSLiBXb3JsZXkNClJldmll
dyBEYXRlOiAgMjAxNy0wMi0xNw0KSUVURiBMQyBFbmQgRGF0ZTogIDIwMTctMDItMjANCklFU0cg
VGVsZWNoYXQgZGF0ZTogIFt1bmtub3duXQ0KDQpTdW1tYXJ5Og0KICAgICAgVGhpcyBkcmFmdCBp
cyBiYXNpY2FsbHkgcmVhZHkgZm9yIHB1YmxpY2F0aW9uLCBidXQgaGFzIG5pdHMNCiAgICAgIHRo
YXQgc2hvdWxkIGJlIGZpeGVkIGJlZm9yZSBwdWJsaWNhdGlvbi4NCg0KKiBUZWNobmljYWwgY29t
bWVudHMNCg0KQS4gQ2FsbCBmYWlsdXJlDQoNCklmIGEgY2FsbCBmYWlscyBkdWUgdG8gbm8gYXZh
aWxhYmxlIGxhbmd1YWdlIG1hdGNoLCBpbiB3aGF0IHdheShzKQ0KZG9lcyBpdCBmYWlsPyAgU2Vj
dGlvbiA1LjMgc2F5cw0KDQogIElmIHN1Y2ggYW4gb2ZmZXIgaXMgcmVjZWl2ZWQsIHRoZSByZWNl
aXZlciBNQVkNCiAgcmVqZWN0IHRoZSBtZWRpYSwgaWdub3JlIHRoZSBsYW5ndWFnZSBzcGVjaWZp
ZWQsIG9yIGF0dGVtcHQgdG8NCiAgaW50ZXJwcmV0IHRoZSBpbnRlbnQNCg0KQnV0IEkgc3VzcGVj
dCBpdCdzIGFsc28gYWxsb3dlZCBmb3IgdGhlIFVBUyB0byBmYWlsIHRoZSBjYWxsIGF0IHRoZQ0K
U0lQIGxldmVsLiAgV2hldGhlciBvciBub3QgdGhhdCBpcyBhbGxvd2VkIChvciBhdCBsZWFzdCBl
bnZpc2lvbmVkKQ0Kc2hvdWxkIGJlIGRlc2NyaWJlZC4gIEFuZCB3aGF0IHJlc3BvbnNlIGNvZGUo
cykvd2Fybi1jb2RlKHMpIHNob3VsZA0KYmUNCnVzZWQgZm9yIHRoYXQ/DQoNCkIuIEF1ZGlvL1Zp
ZGVvIGNvb3JkaW5hdGlvbg0KDQogIDUuMi4gIE5ldyAnaHVtaW50bGFuZy1zZW5kJyBhbmQgJ2h1
bWludGxhbmctcmVjdicgYXR0cmlidXRlcw0KDQogIE5vdGUgdGhhdCB3aGlsZSBzaWduZWQgbGFu
Z3VhZ2UgdGFncyBhcmUgdXNlZCB3aXRoIGEgdmlkZW8gc3RyZWFtDQp0bw0KICBpbmRpY2F0ZSBz
aWduIGxhbmd1YWdlLCBhIHNwb2tlbiBsYW5ndWFnZSB0YWcgZm9yIGEgdmlkZW8gc3RyZWFtDQpp
bg0KICBwYXJhbGxlbCB3aXRoIGFuIGF1ZGlvIHN0cmVhbSB3aXRoIHRoZSBzYW1lIHNwb2tlbiBs
YW5ndWFnZSB0YWcNCiAgaW5kaWNhdGVzIGEgcmVxdWVzdCBmb3IgYSBzdXBwbGVtZW50YWwgdmlk
ZW8gc3RyZWFtIHRvIHNlZSB0aGUNCiAgc3BlYWtlci4NCg0KQW5kIHRoZXJlJ3MgYSBzaW1pbGFy
IHBhcmFncmFwaCBpbiA1LjQ6DQoNCiAgQSBzcG9rZW4gbGFuZ3VhZ2UgdGFnIGZvciBhIHZpZGVv
IHN0cmVhbSBpbiBjb25qdW5jdGlvbiB3aXRoIGFuDQphdWRpbw0KICBzdHJlYW0gd2l0aCB0aGUg
c2FtZSBsYW5ndWFnZSBtaWdodCBpbmRpY2F0ZSBhIHJlcXVlc3QgZm9yDQogIHN1cHBsZW1lbnRh
bCB2aWRlbyB0byBzZWUgdGhlIHNwZWFrZXIuDQoNCkkgdGhpbmsgdGhpcyBtZWNoYW5pc20gbmVl
ZHMgdG8gYmUgZGVzY3JpYmVkIG1vcmUgZXhhY3RseSwgYW5kIGluDQpwYXJ0aWN1bGFyLCBpdCBz
aG91bGQgbm90IGRlcGVuZCBvbiB0aGUgVUEgdW5kZXJzdGFuZGluZyB3aGljaA0KbGFuZ3VhZ2Ug
dGFncyBhcmUgc3Bva2VuIGxhbmd1YWdlIHRhZ3MuICBJdCBzZWVtcyB0byBtZSB0aGF0IGENCndv
cmthYmxlIHJ1bGUgaXMgdGhhdCB0aGVyZSBpcyBhbiBhdWRpbyBzdHJlYW0gYW5kIGEgdmlkZW8g
c3RyZWFtIGFuZA0KdGhleSBzcGVjaWZ5IGV4YWN0bHkgdGhlIHNhbWUgbGFuZ3VhZ2UgdGFnIGlu
IHRoZWlyIHJlc3BlY3RpdmUNCmh1bWludGxhbmcgYXR0cmlidXRlcy4gIEluIHRoYXQgY2FzZSwg
aXQgaXMgYSByZXF1ZXN0IGZvciBhIHNwb2tlbg0KbGFuZ3VhZ2Ugd2l0aCBzaW11bHRhbmVvdXMg
dmlkZW8gb2YgdGhlIHNwZWFrZXIsIGFuZCB0aG9zZSByZXF1ZXN0cw0Kc2hvdWxkIGJlIGNvbnNp
ZGVyZWQgc2F0aXNmaWVkIG9ubHkgaWYgYm90aCBzdHJlYW1zIGNhbiBiZQ0KZXN0YWJsaXNoZWQu
DQoNCiogVGhlIGZvbGxvd2luZyB0aHJlZSBpdGVtcyBhcmUgYWRqdXN0bWVudHMgdG8gdGhlIGRl
c2lnbiB3aGljaCBJJ2QNCmxpa2UgdG8ga25vdyBoYXZlIGJlZW4gY29uc2lkZXJlZC4NCg0KQy4g
Imh1bWludGxhbmciIHNlZW1zIGxvbmcgdG8gbWUNCg0KR2l2ZW4gdGhlIGV4Y2Vzc2l2ZSBsZW5n
dGggb2YgU0RQIGluIHByYWN0aWNlLCBpdCBzZWVtcyB0byBtZSB0aGF0IGENCnNob3J0ZXIgYXR0
cmlidXRlIG5hbWUgd291bGQgYmUgZGVzaXJhYmxlLiAgRS5nLiwgImh1bWxhbmciIGFzIHdhcw0K
dXNlZCBpbiBzb21lIHByZXZpb3VzIHZlcnNpb25zLiAgT3IgaXMgdGhlcmUgYSBjb29yZGluYXRl
ZCB1c2FnZSB3aXRoDQpvdGhlciBuYW1lcyBpbiB0aGUgImh1bSpsYW5nIiBwYXR0ZXJuPw0KDQpE
LiBVc2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXgNCg0KSXQgc2VlbXMgdG8gbWUgdGhhdCBp
dCB3b3VsZCBiZXR0ZXIgdG8gdXNlIHRoZSBBY2NlcHQtTGFuZ3VhZ2Ugc3ludGF4DQpmb3IgdGhl
IGF0dHJpYnV0ZSB2YWx1ZXMuICBUaGlzIGFsbG93cyAoMSkgc3BlY2lmaXlpbmcgdGhlIHF1YWxp
dHkgb2YNCmxhbmd1YWdlIGV4cGVyaWVuY2UsIGFsbG93aW5nIGNsZWFyIGRlc2NyaXB0aW9uIG9m
IGJpbGluZ3VhbGlzbSwgKDIpDQphDQp1bmlmaWVkIG1ldGhvZCBvZiBzcGVjaWZ5aW5nIHdoZXRo
ZXIgb3Igbm90IGFyYml0cmFyeSBsYW5ndWFnZXMgYXJlDQphY2NlcHRhYmxlLCBhbmQgKDMpIGFi
YnJldmlhdGluZyBTRFAgZGVzY3JpcHRpb25zLg0KDQpJbiBhIHdheSwgdGhlIGZhY3QgdGhhdCB0
aGUgY3VycmVudCBwcm9wb3NhbCBzZWVtcyB0byByZXF1aXJlIChidXQNCmRvZXMgbm90IGRpcmVj
dGx5IHNwZWNpZnkpIHRoZSBjb29yZGluYXRlZCBhYnNlbmNlL3ByZXNlbmNlIG9mIGFuDQphc3Rl
cmlzayBvbiBhbGwgb2YgdGhlIHJlcGV0aXRpb25zIG9mIGh1bWludGxhbmctc2VuZCBvcg0KaHVt
aW50bGFuZy1yZWN2IGlzIGEgd2FybmluZyB0aGF0IHRoZSBzeW50YXggZG9lc24ndCByZXByZXNl
bnQgdGhlDQpzZW1hbnRpY3MgYXMgd2VsbCBhcyBpdCBtaWdodC4NCg0KRS4gSGF2ZSBhbiBhdHRy
aWJ1dGUgdG8gYWJicmV2aWF0ZSB0aGUgYmlkaXJlY3Rpb25hbGx5LXN5bW1ldHJpYyBjYXNlDQoN
Ck5vdGUgdGhhdCBhbGwgZXhhbXBsZXMgYXJlIGJpZGlyZWN0aW9uYWxseSBzeW1tZXRyaWMsIGFu
ZCB0aGUgdGV4dA0Kc2F5cyB0aGF0IHJlcXVlc3RzIGFuZCByZXNwb25zZXMgU0hPVUxEIGJlIGJp
ZGlyZWN0aW9uYWxseSBzeW1tZXRyaWMuDQpTbyBpdCB3b3VsZCBiZSBhIHZlcnkgdXNlZnVsIGFi
YnJldmlhdGlvbiB0byBkZWZpbmUNCiJodW1pbnRsYW5nPTx2YWx1ZT4iIHRvIGJlIGVxdWl2YWxl
bnQgdG8gdGhlIGNvbWJpbmF0aW9uIG9mDQoiaHVtaW50bGFuZy1zZW5kPTx2YWx1ZT4iIGFuZCAi
aHVtaW50bGFuZy1yZWN2PTx2YWx1ZT4iLg0KDQpDb21iaW5pbmcgcHJvcG9zYWxzIEMsIEQsIGFu
ZCBFLCB0aGUgZXhhbXBsZXMgYmVjb21lDQoNCiAgICAgbT1hdWRpbyA0OTE3MCBSVFAvQVZQIDAN
CiAgICAgYT1odW1sYW5nOmVuDQoNCiAgICAgbT12aWRlbyA1MTM3MiBSVFAvQVZQIDMxIDMyDQog
ICAgIGE9aHVtbGFuZzphc2UsKjtxPTAuMQ0KDQogICAgIG09YXVkaW8gNDkyNTAgUlRQL0FWUCAy
MA0KICAgICBhPWh1bWxhbmc6ZXMsZXU7cT0wLjksZW47cT0wLjgsKjtxPTAuMQ0KDQogICAgIG09
dGV4dCA0NTAyMCBSVFAvQVZQIDEwMyAxMDQNCiAgICAgYT1odW1sYW5nOmdyDQoNCndoaWNoIHJl
cXVpcmVzIGFib3V0IGhhbGYgYXMgbWFueSBjaGFyYWN0ZXJzIGFzIHRoZXkgaGF2ZSBub3cuDQoN
CiogRWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBuaXRzDQoNCkFic3RyYWN0DQoNCiAgVGhpcyBkb2N1
bWVudCBkZXNjcmliZXMgdGhlIG5lZWQgYW5kIGEgc29sdXRpb24gdXNpbmcgbmV3IFNEUA0Kc3Ry
ZWFtDQogIGF0dHJpYnV0ZXMuDQoNCkkgZG9uJ3QgdGhpbmsgdGhlIHRlcm0gInN0cmVhbSBhdHRy
aWJ1dGUiIGlzIHVzZWQgaW4gUkZDIDQ1NjYuDQpJbnN0ZWFkLCBpdCB1c2VzICJtZWRpYSBhdHRy
aWJ1dGUiLg0KDQoxLiAgSW50cm9kdWN0aW9uDQoNCiAgY2FsbGVyIGFuZCBjYWxsZWUga25vdyBl
YWNoIG90aGVyIG9yIHRoZXJlIGlzIGNvbnRleHR1YWwgb3Igb3V0IG9mDQogIGJhbmQgaW5mb3Jt
YXRpb24gZnJvbSB3aGljaCB0aGUgbGFuZ3VhZ2UocykgYW5kIG1lZGlhIG1vZGFsaXRpZXMNCmNh
bg0KDQpJIHRoaW5rIHRoaXMgY29udGV4dCwgaXQncyBwcmVmZXJyZWQgdG8gaHlwaGVuYXRlICJv
dXQtb2YtYmFuZCIgdG8NCm1ha2UgaXQgY2xlYXJseSBiZSBhbiBhZGplY3RpdmUuDQoNCiAgVGhp
cyBhcHByb2FjaCBoYXMgYSBudW1iZXIgb2YgYmVuZWZpdHMsIGluY2x1ZGluZyB0aGF0IGl0IGlz
DQpnZW5lcmljDQogIChhcHBsaWVzIHRvIGFsbCBpbnRlcmFjdGl2ZSBjb21tdW5pY2F0aW9ucyBu
ZWdvdGlhdGVkIHVzaW5nIFNEUCkNCmFuZA0KICBub3QgbGltaXRlZCB0byBlbWVyZ2VuY3kgY2Fs
bHMuDQoNCkkgdGhpbmsgcy9hbmQgbm90IGxpbWl0ZWQgdG8vYW5kIGlzIG5vdCBsaW1pdGVkIHRv
LyByZWFkcyBtb3JlDQpzbW9vdGhseS4NCg0KICBCdXQgaXQgaXMgY2xlYXJseSB1c2VmdWwgaW4g
bWFueSBvdGhlciBjYXNlcy4gIEZvcg0KICBleGFtcGxlLCBzb21lb25lIGNhbGxpbmcgYSBjb21w
YW55IGNhbGwgY2VudGVyIG9yIGEgUHVibGljIFNhZmV0eQ0KICBBbnN3ZXJpbmcgUG9pbnQgKFBT
QVApIHNob3VsZCBiZSBhYmxlIHRvIGluZGljYXRlIGlmIG9uZSBvciBtb3JlDQogIHNwZWNpZmlj
IHNpZ25lZCwgd3JpdHRlbiwgYW5kL29yIHNwb2tlbiBsYW5ndWFnZXMgYXJlIHByZWZlcnJlZCwN
CnRoZQ0KICBjYWxsZWUgc2hvdWxkIGJlIGFibGUgdG8gaW5kaWNhdGUgaXRzIGNhcGFiaWxpdGll
cyBpbiB0aGlzIGFyZWEsDQphbmQNCiAgdGhlIGNhbGwgcHJvY2VlZCB1c2luZyBpbi1jb21tb24g
bGFuZ3VhZ2UocykgYW5kIG1lZGlhIGZvcm1zLg0KDQpJIHRoaW5rIHMvcHJlZmVycmVkLCB0aGUg
Y2FsbGVlL3ByZWZlcnJlZDsgdGhlIGNhbGxlZS8gYmVjYXVzZSB0aGUNCnNlbnRlbmNlIGlzIHRo
ZSBjb25jYXRlbmF0aW9uIG9mIHR3byBzZW50ZW5jZXMuDQoNClBlcmhhcHMgcy9pbi1jb21tb24v
c2hhcmVkLy4NCg0KICBJbmNsdWRpbmcgdGhlIHVzZXIncyBodW1hbiAobmF0dXJhbCkgbGFuZ3Vh
Z2UgcHJlZmVyZW5jZXMgaW4gdGhlDQogIHNlc3Npb24gZXN0YWJsaXNobWVudCBuZWdvdGlhdGlv
biBpcyBpbmRlcGVuZGVudCBvZiB0aGUgdXNlIG9mIGENCiAgcmVsYXkgc2VydmljZSBhbmQgaXMg
dHJhbnNwYXJlbnQgdG8gYSB2b2ljZSBzZXJ2aWNlIHByb3ZpZGVyLg0KDQpJIHRoaW5rIGl0J3Mg
ZXZlbiBicm9hZGVyIHRoYW4gInRyYW5zcGFyZW50IHRvIGEgdm9pY2Ugc2VydmljZQ0KcHJvdmlk
ZXIiIC0tIGl0J3MgdHJhbnNwYXJlbnQgdG8gYW55IHNlcml2aWNlIHByb3ZpZGVyLCBhc3N1bWlu
ZyB0aGF0DQp0aGUgbWVkaWEgYXJlIGxhbmd1YWdlLW5ldXRyYWwuDQoNCiAgSW4gdGhlIGNhc2Ug
b2YgYSBjYWxsIHRvIGUuZy4sIGFuIGFpcmxpbmUsIHRoZSBjYWxsIGNvdWxkIGJlDQogIGF1dG9t
YXRpY2FsbHkgaGFuZGxlZCBieSBhIFNwYW5pc2gtc3BlYWtpbmcgYWdlbnQuDQoNCkkgdGhpbmsg
cy9oYW5kbGVkIGJ5L3JvdXRlZCB0by8gaXMgdGhlIHVzdWFsIHVzYWdlLg0KDQozLiAgRGVzaXJl
ZCBTZW1hbnRpY3MNCg0KICBUaGUgZGVzaXJlZCBzb2x1dGlvbiBpcyBhIG1lZGlhIGF0dHJpYnV0
ZSAocHJlZmVyYWJseSBwZXINCmRpcmVjdGlvbikNCiAgdGhhdCBtYXkgYmUgdXNlZCB3aXRoaW4g
YW4gb2ZmZXIgdG8gaW5kaWNhdGUgdGhlIHByZWZlcnJlZA0KbGFuZ3VhZ2UNCiAgb2YgZWFjaCAo
ZGlyZWN0aW9uIG9mIGEpIG1lZGlhIHN0cmVhbSwgYW5kIHdpdGhpbiBhbiBhbnN3ZXIgdG8NCiAg
aW5kaWNhdGUgdGhlIGFjY2VwdGVkIGxhbmd1YWdlLg0KDQpJbiB0aGlzIG9uZSBpbnN0YW5jZSwg
SSB0aGluayB5b3Ugd2FudCB0byB1c2UgImxhbmd1YWdlKHMpIiB0byBkcml2ZQ0KaG9tZSB0aGF0
IHRoYXQgbXVsdGlwbGUgbGFuZ3VhZ2VzIGNhbiBiZSBzcGVjaWZpZWQ6ICAid2l0aGluIGFuIG9m
ZmVyDQp0byBpbmRpY2F0ZSB0aGUgcHJlZmVycmVkIGxhbmd1YWdlKHMpIi4NCg0KICAoTmVnb3Rp
YXRpbmcgbXVsdGlwbGUgc2ltdWx0YW5lb3VzIGxhbmd1YWdlcyB3aXRoaW4gYSBtZWRpYSBzdHJl
YW0NCmlzDQogIG91dCBvZiBzY29wZSwgYXMgdGhlIGNvbXBsZXhpdHkgb2YgZG9pbmcgc28gb3V0
d2VpZ2hzIHRoZQ0KICB1c2VmdWxuZXNzLikNCg0KWW91IG1pZ2h0IHdhbnQgdG8gc2F5IGluc3Rl
YWQgIihOZWdvdGlhdGluZyBtdWx0aXBsZSBzaW11bHRhbmVvdXMNCmxhbmd1YWdlcyB3aXRoaW4g
YSBtZWRpYSBzdHJlYW0gaXMgb3V0IG9mIHNjb3BlIGZvciB0aGlzIGRvY3VtZW50LikiDQp0byBl
bnN1cmUgdGhhdCBub2JvZHkgZGVjaWRlcyB0byBhcmd1ZSB3aGV0aGVyICJ0aGUgY29tcGxleGl0
eSBvZg0KZG9pbmcgc28gb3V0d2VpZ2hzIHRoZSB1c2VmdWxuZXNzIi4NCg0KNC4gIFRoZSBleGlz
dGluZyAnbGFuZycgYXR0cmlidXRlDQoNCiAgUkZDIDQ1NjYgW1JGQzQ1NjZdIHNwZWNpZmllcyBh
biBhdHRyaWJ1dGUgJ2xhbmcnIHdoaWNoIGFwcGVhcnMNCiAgc2ltaWxhciB0byB3aGF0IGlzIG5l
ZWRlZCBoZXJlLCBidXQgaXMgbm90IHN1ZmZpY2llbnRseSBkZXRhaWxlZA0KZm9yDQogIHVzZSBo
ZXJlLg0KDQoiZm9yIHVzZSBoZXJlIiBpc24ndCBxdWl0ZSByaWdodC4gIE1heWJlICJpcyBub3Qg
c3VmZmljaWVudGx5DQpzcGVjaWZpYw0Kb3IgZmxleGlibGUgdG8gc2F0aXNmeSB0aGUgcmVxdWly
ZW1lbnRzIi4NCg0KICBJbiBhZGRpdGlvbiwgaXQgaXMgbm90IG1lbnRpb25lZCBpbiBbUkZDMzI2
NF0NCg0KIml0IiBpcyBzb21ld2hhdCBhbWJpZ3VvdXMgaGVyZSwgcGVyaGFwcyBjaGFuZ2UgdG8g
InRoZSAnbGFuZycNCmF0dHJpYnV0ZSIuDQoNCjUuICBQcm9wb3NlZCBTb2x1dGlvbg0KDQpQZXJo
YXBzIC9Qcm9wb3NlZCBTb2x1dGlvbi9Tb2x1dGlvbi8sIHNpbmNlIG9uY2UgdGhpcyBkcmFmdCBp
cw0KYXBwcm92ZWQsIGl0IGJlY29tZXMgdGhlIHNvbHV0aW9uLg0KDQo1LjIuICBOZXcgJ2h1bWlu
dGxhbmctc2VuZCcgYW5kICdodW1pbnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXMNCg0KICAgICBhPWh1
bWludGxhbmctc2VuZDo8bGFuZ3VhZ2UgdGFnPg0KICAgICBhPWh1bWludGxhbmctcmVjdjo8bGFu
Z3VhZ2UgdGFnPg0KDQpUaGlzIGlzIHByZXNlbnRlZCBhcyB0aGUgZ2VuZXJpYyBmb3JtIG9mIHRo
ZSBhdHRyaWJ1dGVzLCBidXQgdGhlcmUgaXMNCm5vIGluZGljYXRpb24gb2YgdGhlIHBvc2libGUg
YXN0ZXJpc2suDQoNCiAgVGhlIHZhbHVlcyBjb25zdGl0dXRlIGEgbGlzdCBvZiBsYW5ndWFnZXMN
CiAgaW4gcHJlZmVyZW5jZSBvcmRlciAoZmlyc3QgaXMgbW9zdCBwcmVmZXJyZWQpLg0KDQoiVGhl
IHZhbHVlcyIgaXNuJ3QgdmVyeSBjbGVhciwgYmVjYXVzZSB0aGUgdmFsdWVzIGFyZSBpbiBzdWNj
ZXNzaXZlDQphdHRyaWJ1dGVzLiAgWW91IHdhbnQgdG8gc2F5IHNvbWV0aGluZyBsaWtlICJUaGUg
c2VxdWVuY2Ugb2YgdmFsdWVzDQppbg0KdGhlIG9jY3VycmVuY2VzIG9mIG9uZSBvZiB0aGVzZSBh
dHRyaWJ1dGVzIGNvbnN0aXR1dGVzIC4uLiIuDQpIb3dldmVyLA0Kc2VlIHRoZSB0ZWNobmljYWwg
Y29tbWVudHMgYWJvdmUuDQoNCiAgV2hlbiBwbGFjaW5nIGFuIGVtZXJnZW5jeSBjYWxsLCBhbmQg
aW4gYW55IG90aGVyIGNhc2Ugd2hlcmUgdGhlDQogIGxhbmd1YWdlIGNhbm5vdCBiZSBhc3N1bWVk
IGZyb20gY29udGV4dCwgZWFjaCBtZWRpYSBzdHJlYW0gaW4gYW4NCiAgb2ZmZXIgcHJpbWFyaWx5
IGludGVuZGVkIGZvciBodW1hbiBsYW5ndWFnZSBjb21tdW5pY2F0aW9uIFNIT1VMRA0KICBzcGVj
aWZ5IGJvdGggKG9yIGluIHNvbWUgY2FzZXMsIG9uZSBvZikgdGhlICdodW1pbnRsYW5nLXNlbmQn
IGFuZA0KICAnaHVtaW50bGFuZy1yZWN2JyBhdHRyaWJ1dGVzLg0KDQpQcm9iYWJseSBzL2Fzc3Vt
ZWQvaW5mZXJyZWQvLg0KDQpDb3VsZCB5b3UgYmUgbW9yZSBhY2N1cmF0ZSBieQ0Kcy9vciBpbiBz
b21lIGNhc2VzL29yIGZvciB1bmlkaXJlY3Rpb25hbCBzdHJlYW1zLz8NCg0KNS4zLiAgQWR2aXNv
cnkgdnMgUmVxdWlyZWQNCg0KICBUaGUgbWVjaGFuaXNtIGZvciBpbmRpY2F0aW5nIHRoaXMgcHJl
ZmVyZW5jZSBpcyB0aGF0LCBpbiBhbiBvZmZlciwNCmlmDQogIHRoZSBsYXN0IGNoYXJhY3RlciBv
ZiBhbnkgb2YgdGhlICdodW1pbnRsYW5nLXJlY3YnIG9yICdodW1pbnRsYW5nLQ0KICBzZW5kJyB2
YWx1ZXMgaXMgYW4gYXN0ZXJpc2ssIHRoaXMgaW5kaWNhdGVzIGEgcmVxdWVzdCB0byBub3QgZmFp
bA0KdGhlDQogIGNhbGwgKHNpbWlsYXIgdG8gU0lQIEFjY2VwdC1MYW5ndWFnZSBzeW50YXgpLiAg
RWl0aGVyIHdheSwgdGhlDQpjYWxsZWQNCiAgcGFydHkgTUFZIGlnbm9yZSB0aGlzLCBlLmcuLCBm
b3IgdGhlIGVtZXJnZW5jeSBzZXJ2aWNlcyB1c2UgY2FzZSwNCmENCiAgUFNBUCB3aWxsIGxpa2Vs
eSBub3QgZmFpbCB0aGUgY2FsbC4NCg0KVGhlIGNvbnN0cnVjdGlvbiBvZiB0aGlzIHBhcmFncmFw
aCBpc24ndCBxdWl0ZSBjb21wbGV0ZS4gIEl0IHNheXMNCnRoYXQNCmlmIGFuIGFzdGVyaXNrIGlz
IHByZXNlbnQsIGEgcmVxdWVzdCBzaG91bGRuJ3QgZmFpbCwgYnV0IGl0IGRvZXNuJ3QNCnNheSB0
aGF0IGlmIG5vIGFzdGVyaXNrIGlzIHByZXNlbnQsIGEgcmVxdWVzdCBzaG91bGQgZmFpbCBpZiB0
aGVyZSBpcw0Kbm8gbGFuZ3VhZ2UgbWF0Y2guICBBbmQgaXQncyB0aGUgbGF0dGVyIGNvbmRpdGlv
biB0aGF0IG1ha2VzIHRoZQ0Kc2Vjb25kIHNlbnRlbmNlIG1lYW5pbmdmdWwuICBTbyBJIHRoaW5r
IHlvdSB3YW50IHRvIGluc2VydCBiZXR3ZWVuDQp0aGUNCnR3byBzZW50ZW5jZXMgb25lIHJlZ2Fy
ZGluZyB0aGUgYWJzZW5jZSBvZiBhbiBhc3Rlcmlzay4NCg0KNS41LiAgRXhhbXBsZXMNCg0KR2l2
ZW4gdGhhdCB0aGUgY29tYmluZWQgYXVkaW8vdmlkZW8gbWVjaGFuaXNtIGlzIHRoZSBvbmx5DQpp
cnJlZ3VsYXJpdHkNCmluIHRoaXMgc3lzdGVtLCB0aGVyZSBvdWdodCB0byBiZSBhbiBleGFtcGxl
IG9mIGl0LiAgRS5nLiwNCg0KICBBbiBleGFtcGxlIG9mIGEgc3VwcGxlbWVudGFsIHZpZGVvIHN0
cmVhbSB3aXRoIGEgc3Bva2VuIGxhbmd1YWdlDQogIGF1ZGlvIHN0cmVhbToNCg0KICAgICBtPXZp
ZGVvIDUxMzcyIFJUUC9BVlAgMzEgMzINCiAgICAgYT1odW1pbnRsYW5nLXNlbmQ6ZW4NCiAgICAg
YT1odW1pbnRsYW5nLXJlY3Y6ZW4NCg0KICAgICBtPWF1ZGlvIDQ5MjUwIFJUUC9BVlAgMjANCiAg
ICAgYT1odW1pbnRsYW5nLXNlbmQ6ZW4NCiAgICAgYT1odW1pbnRsYW5nLXJlY3Y6ZW4NCg0KNi4g
IElBTkEgQ29uc2lkZXJhdGlvbnMNCg0KICAgICBodW1pbnRsYW5nLXZhbHVlID0gIExhbmd1YWdl
LVRhZyBbIGFzdGVyaXNrIF0NCiAgICAgICAgICAgICAgICAgICAgICAgICA7IExhbmd1YWdlLVRh
ZyBkZWZpbmVkIGluIFJGQyA1NjQ2DQogICAgIGFzdGVyaXNrICAgICAgICAgPSAgIioiDQoNCnMv
TGFuZ3VhZ2UtVGFnIGRlZmluZWQgaW4gUkZDIDU2NDYvTGFuZ3VhZ2UtVGFnIGFzIGRlZmluZWQg
aW4gUkZDDQo1NjQ2Lw0KDQpCdXQgcGVyaGFwcyBhbHNvIHMvUkZDIDU2NDYvQkNQIDQ3Lywgd2hp
Y2ggZW5zdXJlcyB0aGF0ICJodW1pbnRsYW5nIg0KdHJhY2tzIHRoZSBjdXJyZW50IHZlcnNpb24g
b2YgbGFuZ3VhZ2UgdGFncy4NCg0KQXBwZW5kaXggQS4gIEhpc3RvcmljIEFsdGVybmF0aXZlIFBy
b3Bvc2FsOiBDYWxsZXItcHJlZnMNCg0KICBUaGlzDQogIHJlc3VsdHMgaW4gYSBtb3JlIGZyYWdp
bGUgc29sdXRpb24gc2luY2UgdGhlIG1lZGlhIG1vZGFsaXR5IGFuZA0KICBsYW5ndWFnZSB3b3Vs
ZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNpZmljDQptZWRpYQ0K
ICBmb3JtYXRzICh3aGljaCBpbmhlcmVudGx5IGluY2x1ZGUgdGhlIG1vZGFsaXR5KSB3b3VsZCBi
ZQ0KbmVnb3RpYXRlZA0KICBhdCBhIGRpZmZlcmVudCBsZXZlbCAodHlwaWNhbGx5IFNEUCwgZXNw
ZWNpYWxseSBpbiB0aGUgZW1lcmdlbmN5DQogIGNhbGxpbmcgY2FzZXMpLCBtYWtpbmcgaXQgZWFz
aWVyIHRvIGhhdmUgbWlzbWF0Y2hlcyAoc3VjaCBhcyB3aGVyZQ0KICB0aGUgbWVkaWEgbW9kYWxp
dHkgbmVnb3RpYXRlZCBpbiBTSVAgZG9uJ3QgbWF0Y2ggd2hhdCB3YXMNCm5lZ290aWF0ZWQNCiAg
dXNpbmcgU0RQKS4NCg0KInRoZSBtZWRpYSBtb2RhbGl0eSBhbmQgbGFuZ3VhZ2Ugd291bGQgYmUg
bmVnb3RpYXRlZCB1c2luZyBTSVAiIGlzbid0DQpxdWl0ZSB0aGUgcmlnaHQgd2F5IHRvIHNheSBp
dCBiZWNhdXNlIFNJUCBpc24ndCBleHBsaWNpdGx5DQpuZWdvdGlhdGluZw0KdGhlIG1vZGFsaXR5
LiAgQmV0dGVyIHdvdWxkIGJlDQoNCiAgLi4uIHRoZSBsYW5ndWFnZSAoYW5kIGJ5IGltcGxpY2F0
aW9uIHRoZSBtZWRpYSBtb2RhbGl0eSkgd291bGQgYmUNCiAgbmVnb3RpYXRlZCB1c2luZyBTSVAs
IGFuZCB0aGVuIHRoZSBzcGVjaWZpYyBtZWRpYSAod2hpY2gNCmluaGVyZW50bHkNCiAgaW5jbHVk
ZSB0aGUgbW9kYWxpdGllcyBhbmQgZm9ybWF0cykgd291bGQgYmUgbmVnb3RpYXRlZCBhdCBhDQog
IGRpZmZlcmVudCBsZXZlbCAuLi4NCg0KW0VORF0NCg0KDQoNCg0KVGhpcyBlbWFpbCBhbmQgaXRz
IGF0dGFjaG1lbnRzIGFyZSBpbnRlbmRlZCBmb3IgdGhlIGFib3ZlIG5hbWVkIG9ubHkgYW5kIG1h
eSBiZSBjb25maWRlbnRpYWwuIElmIHRoZXkgaGF2ZSBjb21lIHRvIHlvdSBpbiBlcnJvciB5b3Ug
bXVzdCB0YWtlIG5vIGFjdGlvbiBiYXNlZCBvbiB0aGVtLCBub3IgbXVzdCB5b3UgY29weSBvciBz
aG93IHRoZW0gdG8gYW55b25lOyBwbGVhc2UgcmVwbHkgdG8gdGhpcyBlbWFpbCBvciBjYWxsICs0
NCAyMDcgMzU2IDA2MDAgYW5kIGhpZ2hsaWdodCB0aGUgZXJyb3IuDQo=

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_
Content-Type: text/html; charset="utf-8"
Content-ID: <1F5EA51BAA990E4EBDCD38D9D0B94897@eurprd04.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIiPg0KSGkgRGFsZSEgTWFueSB0aGFua3Mg
Zm9yIHRoZXNlIGNvbW1lbnRzLCBhcyBvbmUgb2YgdGhlIFNMSU0gY2hhaXJzIEnigJlsbCB3b3Jr
IG9uIGdldHRpbmcgc29tZSBhbnN3ZXJzIHRvIHlvdSBvciBJ4oCZbGwgcmVxdWVzdCB0aGUgYXV0
aG9yIG9yIG9uZSBvZiB0aGUgU0xJTSBhY3RpdmUgcGFydGljaXBhbnRzIHRvIHJlc3BvbmQuJm5i
c3A7DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5C
ZXJuYXJkLCBSYW5kYWxsIGFuZCBTTElNIC0gc2VlIGJlbG93IHJlIERhbGXigJlzIHBvaW50cy4m
bmJzcDs8YnIgY2xhc3M9IiI+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0K
PGRpdiBjbGFzcz0iIj4qKioqIEEuIENhbGwgZmFpbHVyZSAqKioqPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPlJhbmRhbGwgb3IgQmVybmFyZCBjYW4geW91IHJlc3BvbmQgdG8gdGhpcz8gSSBpbWFnaW5l
IHRoZSBVQSBjYWxsIGZhaWx1cmUgbWV0aG9kIGlzIFVBIHNwZWNpZmljLCBidXQgaWYgdGhlcmUg
aXMgYSBjbGFzaCB3aXRoIFNJUCBsZXZlbCBjYWxsIGZhaWwgdGhlbiB0aGlzIHNob3VsZCBiZSBh
ZGRyZXNzZWQuPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj4qKioqJm5ic3A7Qi4gQXVkaW8vVmlkZW8gY29vcmRpbmF0aW9uICoqKio8L2Rp
dj4NCjxkaXYgY2xhc3M9IiI+SSBiZWxpZXZlIHRoZSB0aGVvcnkgYmVoaW5kIHRoZSBjdXJyZW50
IGRyYWZ0IGlzIHRoYXQgdGhlIHNwb2tlbiBhbmQgdmlkZW8gc3RyZWFtcyB3aWxsIGJlIGRpZmZl
cmVudCBpbiB0aGUgY2FzZXMgb2Ygc3VjaCB0aGluZ3MgYXMgc2lnbiBsYW5ndWFnZS4gVmlkZW8g
Y291bGQgdGhlcmVmb3JlIGJlIHNpZ24gYW5kIGF1ZGlvIHdvdWxkIGJlIGEgc3Bva2VuIGxhbmd1
YWdlLiBJ4oCZbSBub3Qgc3VyZSBpZiB0aGUgc3VnZ2VzdGlvbg0KIGhlIHNhdGlzZmllcyB0aGlz
IGNhc2U/PC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBj
bGFzcz0iIj4qKioqIEMuICZxdW90O2h1bWludGxhbmcmcXVvdDsgc2VlbXMgbG9uZyB0byBtZSAq
KioqPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPkJlcm5hcmQgLSBJIGRvbuKAmXQgc2VlIHRoZSBpc3N1
ZSB3aXRoIHNob3J0ZW5pbmcgaHVtaW50bGFuZywgYnV0IHRoZSBncm91cCBtaWdodC4gSSBzdWdn
ZXN0IHdlIHRocm93IHRoaXMgdG8gdGhlIGdyb3VwIGZvciBkaXNjdXNzaW9uLjwvZGl2Pg0KPGRp
diBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+KioqKiBELiBV
c2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXggKioqKjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5S
YW5kYWxsIGFuZCBCZXJuYXJkIC0gaXMgdGhpcyBhbiBhY2NlcHRhYmxlIGNoYW5nZT8gT3Igb25l
IHdlIG5lZWQgdG8gZGlzY3VzcyBmdXJ0aGVyLiBTZWVtcyBsaWtlIGEgcmVhc29uYWJsZSByZXF1
ZXN0LCBidXQgYWxzbyBhIGxhcmdlciBjaGFuZ2UsIHdoaWNoIGlzIHdoeSBJIGFzayE8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPioqKiog
RS4gSGF2ZSBhbiBhdHRyaWJ1dGUgdG8gYWJicmV2aWF0ZSB0aGUgYmlkaXJlY3Rpb25hbGx5LXN5
bW1ldHJpYyBjYXNlICoqKio8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+SSBkbyBub3QgcmVtZW1iZXIg
dXMgaGF2aW5nIHRoaXMgZGlzY3Vzc2lvbiB3aXRoaW4gdGhlIGdyb3VwLCBhbHRob3VnaCBpdCBt
YXkgaGF2ZSBvY2N1cnJlZCBiZWZvcmUgSSBiZWNhbWUgY2hhaXIuPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPlJhbmRhbGwsIEJyaWFuIG9yIEJlcm5hcmQgLSBoYXMgdGhpcyBpZGVhIGJlZW4gZGlzY3Vz
c2VkIGJlZm9yZT8gSWYgc28sIGNhbiBvbmUgb2YgeW91IHJlc3BvbmQgd2l0aCBhbiBleHBsYW5h
dGlvbiBhcyB0byB3aHkgd2UgaGF2ZW7igJl0IGRvbmUgdGhpcz88L2Rpdj4NCjxkaXYgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KPGRpdiBjbGFzcz0iIj4qKioqJm5ic3A7RWRpdG9yaWFsIGNvbW1l
bnRzIGFuZCBuaXRzICoqKioqPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlJhbmRhbGwgLSBjYW4geW91
IHRha2UgYSBsb29rIHRocm91Z2ggRGFsZeKAmXMgZWRpdG9yaWFsIGNvbW1lbnRzIGFuZCBzaG91
dCBpZiB0aGVyZSBpcyBhbnkgcHJvYmxlbXMgd2l0aCB0aGVzZSBzdWdnZXN0aW9uczsgaWYgZXZl
cnl0aGluZyBpcyBvayBwbGVhc2UgbWFrZSB0aGUgY2hhbmdlcy48L2Rpdj4NCjxkaXYgY2xhc3M9
IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPlRoYW5rcyBhbGwhPC9kaXY+
DQo8ZGl2IGNsYXNzPSIiPg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1m
YW1pbHk6IEhlbHZldGljYTsgZm9udC1zaXplOiAxMnB4OyBmb250LXN0eWxlOiBub3JtYWw7IGZv
bnQtdmFyaWFudC1jYXBzOiBub3JtYWw7IGZvbnQtd2VpZ2h0OiBub3JtYWw7IGxldHRlci1zcGFj
aW5nOiBub3JtYWw7IG9ycGhhbnM6IGF1dG87IHRleHQtYWxpZ246IHN0YXJ0OyB0ZXh0LWluZGVu
dDogMHB4OyB0ZXh0LXRyYW5zZm9ybTogbm9uZTsgd2hpdGUtc3BhY2U6IG5vcm1hbDsgd2lkb3dz
OiBhdXRvOyB3b3JkLXNwYWNpbmc6IDBweDsgLXdlYmtpdC10ZXh0LXNpemUtYWRqdXN0OiBhdXRv
OyAtd2Via2l0LXRleHQtc3Ryb2tlLXdpZHRoOiAwcHg7Ij4NCjxiciBjbGFzcz0iIj4NCk5hdGFz
aGEgUm9vbmV5IHwgSW50ZXJuZXQgRW5naW5lZXJpbmcmbmJzcDtEaXJlY3RvciB8IEludGVybmV0
IGFuZCBXZWIgVGVhbSB8Jm5ic3A7VGVjaG5vbG9neSB8IEdTTUEgfCZuYnNwOzxhIGhyZWY9Im1h
aWx0bzpucm9vbmV5QGdzbWEuY29tIiBjbGFzcz0iIj5ucm9vbmV5QGdzbWEuY29tPC9hPiZuYnNw
O3wgJiM0Mzs0NCAoMCkgNzczMCAyMTkmbmJzcDs3NjUgfCBAdGhpc05hdGFzaGEgfCBTa3lwZTom
bmJzcDs8YSBocmVmPSJtYWlsdG86bnJvb25leUBnc20ub3JnIiBjbGFzcz0iIj5ucm9vbmV5QGdz
bS5vcmc8L2E+PC9kaXY+DQo8L2Rpdj4NCjxiciBjbGFzcz0iIj4NCjxkaXY+DQo8YmxvY2txdW90
ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gMTggRmViIDIwMTcsIGF0
IDAyOjMyLCBEYWxlIFdvcmxleSAmbHQ7PGEgaHJlZj0ibWFpbHRvOndvcmxleUBhcmlhZG5lLmNv
bSIgY2xhc3M9IiI+d29ybGV5QGFyaWFkbmUuY29tPC9hPiZndDsgd3JvdGU6PC9kaXY+DQo8YnIg
Y2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRpdiBjbGFzcz0iIj4NCjxkaXYg
Y2xhc3M9IiI+UmV2aWV3ZXI6IERhbGUgV29ybGV5PGJyIGNsYXNzPSIiPg0KUmV2aWV3IHJlc3Vs
dDogUmVhZHkgd2l0aCBOaXRzPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KSSBhbSB0aGUg
YXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gJm5ic3A7VGhlIEdlbmVy
YWwgQXJlYTxiciBjbGFzcz0iIj4NClJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJ
RVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQ8YnIgY2xhc3M9IiI+DQpieSB0aGUgSUVTRyBm
b3IgdGhlIElFVEYgQ2hhaXIuICZuYnNwO1BsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50cyBqdXN0
PGJyIGNsYXNzPSIiPg0KbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLjxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCkZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRo
ZSBGQVEgYXQ8YnIgY2xhc3M9IiI+DQombHQ7PGEgaHJlZj0iaHR0cDovL3dpa2kudG9vbHMuaWV0
Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcSIgY2xhc3M9IiI+aHR0cDovL3dpa2ku
dG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtpL0dlbkFydGZhcTwvYT4mZ3Q7LjxiciBj
bGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkRvY3VtZW50OiAmbmJzcDtkcmFmdC1pZXRmLXNsaW0t
bmVnb3RpYXRpbmctaHVtYW4tbGFuZ3VhZ2UtMDY8YnIgY2xhc3M9IiI+DQpSZXZpZXdlcjogJm5i
c3A7RGFsZSBSLiBXb3JsZXk8YnIgY2xhc3M9IiI+DQpSZXZpZXcgRGF0ZTogJm5ic3A7MjAxNy0w
Mi0xNzxiciBjbGFzcz0iIj4NCklFVEYgTEMgRW5kIERhdGU6ICZuYnNwOzIwMTctMDItMjA8YnIg
Y2xhc3M9IiI+DQpJRVNHIFRlbGVjaGF0IGRhdGU6ICZuYnNwO1t1bmtub3duXTxiciBjbGFzcz0i
Ij4NCjxiciBjbGFzcz0iIj4NClN1bW1hcnk6PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhpcyBkcmFmdCBpcyBiYXNpY2FsbHkgcmVhZHkgZm9yIHB1
YmxpY2F0aW9uLCBidXQgaGFzIG5pdHM8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDt0aGF0IHNob3VsZCBiZSBmaXhlZCBiZWZvcmUgcHVibGljYXRpb24u
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KKiBUZWNobmljYWwgY29tbWVudHM8YnIgY2xh
c3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpBLiBDYWxsIGZhaWx1cmU8YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpJZiBhIGNhbGwgZmFpbHMgZHVlIHRvIG5vIGF2YWlsYWJsZSBsYW5ndWFnZSBt
YXRjaCwgaW4gd2hhdCB3YXkocyk8YnIgY2xhc3M9IiI+DQpkb2VzIGl0IGZhaWw/ICZuYnNwO1Nl
Y3Rpb24gNS4zIHNheXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtJ
ZiBzdWNoIGFuIG9mZmVyIGlzIHJlY2VpdmVkLCB0aGUgcmVjZWl2ZXIgTUFZPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7cmVqZWN0IHRoZSBtZWRpYSwgaWdub3JlIHRoZSBsYW5ndWFnZSBzcGVj
aWZpZWQsIG9yIGF0dGVtcHQgdG88YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtpbnRlcnByZXQg
dGhlIGludGVudDxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkJ1dCBJIHN1c3BlY3QgaXQn
cyBhbHNvIGFsbG93ZWQgZm9yIHRoZSBVQVMgdG8gZmFpbCB0aGUgY2FsbCBhdCB0aGU8YnIgY2xh
c3M9IiI+DQpTSVAgbGV2ZWwuICZuYnNwO1doZXRoZXIgb3Igbm90IHRoYXQgaXMgYWxsb3dlZCAo
b3IgYXQgbGVhc3QgZW52aXNpb25lZCk8YnIgY2xhc3M9IiI+DQpzaG91bGQgYmUgZGVzY3JpYmVk
LiAmbmJzcDtBbmQgd2hhdCByZXNwb25zZSBjb2RlKHMpL3dhcm4tY29kZShzKSBzaG91bGQ8YnIg
Y2xhc3M9IiI+DQpiZTxiciBjbGFzcz0iIj4NCnVzZWQgZm9yIHRoYXQ/PGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KQi4gQXVkaW8vVmlkZW8gY29vcmRpbmF0aW9uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7NS4yLiAmbmJzcDtOZXcgJ2h1bWludGxhbmctc2Vu
ZCcgYW5kICdodW1pbnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQombmJzcDsmbmJzcDtOb3RlIHRoYXQgd2hpbGUgc2lnbmVkIGxhbmd1YWdlIHRhZ3Mg
YXJlIHVzZWQgd2l0aCBhIHZpZGVvIHN0cmVhbTxiciBjbGFzcz0iIj4NCnRvPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7aW5kaWNhdGUgc2lnbiBsYW5ndWFnZSwgYSBzcG9rZW4gbGFuZ3VhZ2Ug
dGFnIGZvciBhIHZpZGVvIHN0cmVhbTxiciBjbGFzcz0iIj4NCmluPGJyIGNsYXNzPSIiPg0KJm5i
c3A7Jm5ic3A7cGFyYWxsZWwgd2l0aCBhbiBhdWRpbyBzdHJlYW0gd2l0aCB0aGUgc2FtZSBzcG9r
ZW4gbGFuZ3VhZ2UgdGFnPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7aW5kaWNhdGVzIGEgcmVx
dWVzdCBmb3IgYSBzdXBwbGVtZW50YWwgdmlkZW8gc3RyZWFtIHRvIHNlZSB0aGU8YnIgY2xhc3M9
IiI+DQombmJzcDsmbmJzcDtzcGVha2VyLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkFu
ZCB0aGVyZSdzIGEgc2ltaWxhciBwYXJhZ3JhcGggaW4gNS40OjxiciBjbGFzcz0iIj4NCjxiciBj
bGFzcz0iIj4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiIGNsYXNzPSIiPiZuYnNwOyZuYnNwO0Eg
c3Bva2VuIGxhbmd1YWdlIHRhZyBmb3IgYSB2aWRlbyBzdHJlYW0gaW4gY29uanVuY3Rpb24gd2l0
aCBhbjxiciBjbGFzcz0iIj4NCjwvYmxvY2txdW90ZT4NCmF1ZGlvPGJyIGNsYXNzPSIiPg0KPGJs
b2NrcXVvdGUgdHlwZT0iY2l0ZSIgY2xhc3M9IiI+Jm5ic3A7Jm5ic3A7c3RyZWFtIHdpdGggdGhl
IHNhbWUgbGFuZ3VhZ2UgbWlnaHQgaW5kaWNhdGUgYSByZXF1ZXN0IGZvcjxiciBjbGFzcz0iIj4N
CiZuYnNwOyZuYnNwO3N1cHBsZW1lbnRhbCB2aWRlbyB0byBzZWUgdGhlIHNwZWFrZXIuPGJyIGNs
YXNzPSIiPg0KPC9ibG9ja3F1b3RlPg0KPGJyIGNsYXNzPSIiPg0KSSB0aGluayB0aGlzIG1lY2hh
bmlzbSBuZWVkcyB0byBiZSBkZXNjcmliZWQgbW9yZSBleGFjdGx5LCBhbmQgaW48YnIgY2xhc3M9
IiI+DQpwYXJ0aWN1bGFyLCBpdCBzaG91bGQgbm90IGRlcGVuZCBvbiB0aGUgVUEgdW5kZXJzdGFu
ZGluZyB3aGljaDxiciBjbGFzcz0iIj4NCmxhbmd1YWdlIHRhZ3MgYXJlIHNwb2tlbiBsYW5ndWFn
ZSB0YWdzLiAmbmJzcDtJdCBzZWVtcyB0byBtZSB0aGF0IGE8YnIgY2xhc3M9IiI+DQp3b3JrYWJs
ZSBydWxlIGlzIHRoYXQgdGhlcmUgaXMgYW4gYXVkaW8gc3RyZWFtIGFuZCBhIHZpZGVvIHN0cmVh
bSBhbmQ8YnIgY2xhc3M9IiI+DQp0aGV5IHNwZWNpZnkgZXhhY3RseSB0aGUgc2FtZSBsYW5ndWFn
ZSB0YWcgaW4gdGhlaXIgcmVzcGVjdGl2ZTxiciBjbGFzcz0iIj4NCmh1bWludGxhbmcgYXR0cmli
dXRlcy4gJm5ic3A7SW4gdGhhdCBjYXNlLCBpdCBpcyBhIHJlcXVlc3QgZm9yIGEgc3Bva2VuPGJy
IGNsYXNzPSIiPg0KbGFuZ3VhZ2Ugd2l0aCBzaW11bHRhbmVvdXMgdmlkZW8gb2YgdGhlIHNwZWFr
ZXIsIGFuZCB0aG9zZSByZXF1ZXN0czxiciBjbGFzcz0iIj4NCnNob3VsZCBiZSBjb25zaWRlcmVk
IHNhdGlzZmllZCBvbmx5IGlmIGJvdGggc3RyZWFtcyBjYW4gYmU8YnIgY2xhc3M9IiI+DQplc3Rh
Ymxpc2hlZC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQoqIFRoZSBmb2xsb3dpbmcgdGhy
ZWUgaXRlbXMgYXJlIGFkanVzdG1lbnRzIHRvIHRoZSBkZXNpZ24gd2hpY2ggSSdkPGJyIGNsYXNz
PSIiPg0KbGlrZSB0byBrbm93IGhhdmUgYmVlbiBjb25zaWRlcmVkLjxiciBjbGFzcz0iIj4NCjxi
ciBjbGFzcz0iIj4NCkMuICZxdW90O2h1bWludGxhbmcmcXVvdDsgc2VlbXMgbG9uZyB0byBtZTxi
ciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkdpdmVuIHRoZSBleGNlc3NpdmUgbGVuZ3RoIG9m
IFNEUCBpbiBwcmFjdGljZSwgaXQgc2VlbXMgdG8gbWUgdGhhdCBhPGJyIGNsYXNzPSIiPg0Kc2hv
cnRlciBhdHRyaWJ1dGUgbmFtZSB3b3VsZCBiZSBkZXNpcmFibGUuICZuYnNwO0UuZy4sICZxdW90
O2h1bWxhbmcmcXVvdDsgYXMgd2FzPGJyIGNsYXNzPSIiPg0KdXNlZCBpbiBzb21lIHByZXZpb3Vz
IHZlcnNpb25zLiAmbmJzcDtPciBpcyB0aGVyZSBhIGNvb3JkaW5hdGVkIHVzYWdlIHdpdGg8YnIg
Y2xhc3M9IiI+DQpvdGhlciBuYW1lcyBpbiB0aGUgJnF1b3Q7aHVtKmxhbmcmcXVvdDsgcGF0dGVy
bj88YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpELiBVc2UgdGhlIEFjY2VwdC1MYW5ndWFn
ZSBzeW50YXg8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJdCBzZWVtcyB0byBtZSB0aGF0
IGl0IHdvdWxkIGJldHRlciB0byB1c2UgdGhlIEFjY2VwdC1MYW5ndWFnZSBzeW50YXg8YnIgY2xh
c3M9IiI+DQpmb3IgdGhlIGF0dHJpYnV0ZSB2YWx1ZXMuICZuYnNwO1RoaXMgYWxsb3dzICgxKSBz
cGVjaWZpeWluZyB0aGUgcXVhbGl0eSBvZjxiciBjbGFzcz0iIj4NCmxhbmd1YWdlIGV4cGVyaWVu
Y2UsIGFsbG93aW5nIGNsZWFyIGRlc2NyaXB0aW9uIG9mIGJpbGluZ3VhbGlzbSwgKDIpPGJyIGNs
YXNzPSIiPg0KYTxiciBjbGFzcz0iIj4NCnVuaWZpZWQgbWV0aG9kIG9mIHNwZWNpZnlpbmcgd2hl
dGhlciBvciBub3QgYXJiaXRyYXJ5IGxhbmd1YWdlcyBhcmU8YnIgY2xhc3M9IiI+DQphY2NlcHRh
YmxlLCBhbmQgKDMpIGFiYnJldmlhdGluZyBTRFAgZGVzY3JpcHRpb25zLjxiciBjbGFzcz0iIj4N
CjxiciBjbGFzcz0iIj4NCkluIGEgd2F5LCB0aGUgZmFjdCB0aGF0IHRoZSBjdXJyZW50IHByb3Bv
c2FsIHNlZW1zIHRvIHJlcXVpcmUgKGJ1dDxiciBjbGFzcz0iIj4NCmRvZXMgbm90IGRpcmVjdGx5
IHNwZWNpZnkpIHRoZSBjb29yZGluYXRlZCBhYnNlbmNlL3ByZXNlbmNlIG9mIGFuPGJyIGNsYXNz
PSIiPg0KYXN0ZXJpc2sgb24gYWxsIG9mIHRoZSByZXBldGl0aW9ucyBvZiBodW1pbnRsYW5nLXNl
bmQgb3I8YnIgY2xhc3M9IiI+DQpodW1pbnRsYW5nLXJlY3YgaXMgYSB3YXJuaW5nIHRoYXQgdGhl
IHN5bnRheCBkb2Vzbid0IHJlcHJlc2VudCB0aGU8YnIgY2xhc3M9IiI+DQpzZW1hbnRpY3MgYXMg
d2VsbCBhcyBpdCBtaWdodC48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpFLiBIYXZlIGFu
IGF0dHJpYnV0ZSB0byBhYmJyZXZpYXRlIHRoZSBiaWRpcmVjdGlvbmFsbHktc3ltbWV0cmljIGNh
c2U8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpOb3RlIHRoYXQgYWxsIGV4YW1wbGVzIGFy
ZSBiaWRpcmVjdGlvbmFsbHkgc3ltbWV0cmljLCBhbmQgdGhlIHRleHQ8YnIgY2xhc3M9IiI+DQpz
YXlzIHRoYXQgcmVxdWVzdHMgYW5kIHJlc3BvbnNlcyBTSE9VTEQgYmUgYmlkaXJlY3Rpb25hbGx5
IHN5bW1ldHJpYy48YnIgY2xhc3M9IiI+DQpTbyBpdCB3b3VsZCBiZSBhIHZlcnkgdXNlZnVsIGFi
YnJldmlhdGlvbiB0byBkZWZpbmU8YnIgY2xhc3M9IiI+DQomcXVvdDtodW1pbnRsYW5nPSZsdDt2
YWx1ZSZndDsmcXVvdDsgdG8gYmUgZXF1aXZhbGVudCB0byB0aGUgY29tYmluYXRpb24gb2Y8YnIg
Y2xhc3M9IiI+DQomcXVvdDtodW1pbnRsYW5nLXNlbmQ9Jmx0O3ZhbHVlJmd0OyZxdW90OyBhbmQg
JnF1b3Q7aHVtaW50bGFuZy1yZWN2PSZsdDt2YWx1ZSZndDsmcXVvdDsuPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KQ29tYmluaW5nIHByb3Bvc2FscyBDLCBELCBhbmQgRSwgdGhlIGV4YW1w
bGVzIGJlY29tZTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwO209YXVkaW8gNDkxNzAgUlRQL0FWUCAwPGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmVuPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT12aWRlbyA1MTM3MiBSVFAv
QVZQIDMxIDMyPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1o
dW1sYW5nOmFzZSwqO3E9MC4xPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT1hdWRpbyA0OTI1MCBSVFAvQVZQIDIwPGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmVzLGV1O3E9MC45LGVu
O3E9MC44LCo7cT0wLjE8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDttPXRleHQgNDUwMjAgUlRQL0FWUCAxMDMgMTA0PGJyIGNsYXNzPSIi
Pg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1sYW5nOmdyPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0Kd2hpY2ggcmVxdWlyZXMgYWJvdXQgaGFsZiBhcyBtYW55IGNoYXJh
Y3RlcnMgYXMgdGhleSBoYXZlIG5vdy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQoqIEVk
aXRvcmlhbCBjb21tZW50cyBhbmQgbml0czxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkFi
c3RyYWN0PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7VGhpcyBkb2N1
bWVudCBkZXNjcmliZXMgdGhlIG5lZWQgYW5kIGEgc29sdXRpb24gdXNpbmcgbmV3IFNEUDxiciBj
bGFzcz0iIj4NCnN0cmVhbTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2F0dHJpYnV0ZXMuPGJy
IGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KSSBkb24ndCB0aGluayB0aGUgdGVybSAmcXVvdDtz
dHJlYW0gYXR0cmlidXRlJnF1b3Q7IGlzIHVzZWQgaW4gUkZDIDQ1NjYuPGJyIGNsYXNzPSIiPg0K
SW5zdGVhZCwgaXQgdXNlcyAmcXVvdDttZWRpYSBhdHRyaWJ1dGUmcXVvdDsuPGJyIGNsYXNzPSIi
Pg0KPGJyIGNsYXNzPSIiPg0KMS4gJm5ic3A7SW50cm9kdWN0aW9uPGJyIGNsYXNzPSIiPg0KPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbGVyIGFuZCBjYWxsZWUga25vdyBlYWNoIG90aGVy
IG9yIHRoZXJlIGlzIGNvbnRleHR1YWwgb3Igb3V0IG9mPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7YmFuZCBpbmZvcm1hdGlvbiBmcm9tIHdoaWNoIHRoZSBsYW5ndWFnZShzKSBhbmQgbWVkaWEg
bW9kYWxpdGllczxiciBjbGFzcz0iIj4NCmNhbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CkkgdGhpbmsgdGhpcyBjb250ZXh0LCBpdCdzIHByZWZlcnJlZCB0byBoeXBoZW5hdGUgJnF1b3Q7
b3V0LW9mLWJhbmQmcXVvdDsgdG88YnIgY2xhc3M9IiI+DQptYWtlIGl0IGNsZWFybHkgYmUgYW4g
YWRqZWN0aXZlLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoaXMg
YXBwcm9hY2ggaGFzIGEgbnVtYmVyIG9mIGJlbmVmaXRzLCBpbmNsdWRpbmcgdGhhdCBpdCBpczxi
ciBjbGFzcz0iIj4NCmdlbmVyaWM8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsoYXBwbGllcyB0
byBhbGwgaW50ZXJhY3RpdmUgY29tbXVuaWNhdGlvbnMgbmVnb3RpYXRlZCB1c2luZyBTRFApPGJy
IGNsYXNzPSIiPg0KYW5kPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7bm90IGxpbWl0ZWQgdG8g
ZW1lcmdlbmN5IGNhbGxzLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCkkgdGhpbmsgcy9h
bmQgbm90IGxpbWl0ZWQgdG8vYW5kIGlzIG5vdCBsaW1pdGVkIHRvLyByZWFkcyBtb3JlPGJyIGNs
YXNzPSIiPg0Kc21vb3RobHkuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5i
c3A7QnV0IGl0IGlzIGNsZWFybHkgdXNlZnVsIGluIG1hbnkgb3RoZXIgY2FzZXMuICZuYnNwO0Zv
cjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2V4YW1wbGUsIHNvbWVvbmUgY2FsbGluZyBhIGNv
bXBhbnkgY2FsbCBjZW50ZXIgb3IgYSBQdWJsaWMgU2FmZXR5PGJyIGNsYXNzPSIiPg0KJm5ic3A7
Jm5ic3A7QW5zd2VyaW5nIFBvaW50IChQU0FQKSBzaG91bGQgYmUgYWJsZSB0byBpbmRpY2F0ZSBp
ZiBvbmUgb3IgbW9yZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3NwZWNpZmljIHNpZ25lZCwg
d3JpdHRlbiwgYW5kL29yIHNwb2tlbiBsYW5ndWFnZXMgYXJlIHByZWZlcnJlZCw8YnIgY2xhc3M9
IiI+DQp0aGU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtjYWxsZWUgc2hvdWxkIGJlIGFibGUg
dG8gaW5kaWNhdGUgaXRzIGNhcGFiaWxpdGllcyBpbiB0aGlzIGFyZWEsPGJyIGNsYXNzPSIiPg0K
YW5kPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7dGhlIGNhbGwgcHJvY2VlZCB1c2luZyBpbi1j
b21tb24gbGFuZ3VhZ2UocykgYW5kIG1lZGlhIGZvcm1zLjxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCkkgdGhpbmsgcy9wcmVmZXJyZWQsIHRoZSBjYWxsZWUvcHJlZmVycmVkOyB0aGUgY2Fs
bGVlLyBiZWNhdXNlIHRoZTxiciBjbGFzcz0iIj4NCnNlbnRlbmNlIGlzIHRoZSBjb25jYXRlbmF0
aW9uIG9mIHR3byBzZW50ZW5jZXMuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KUGVyaGFw
cyBzL2luLWNvbW1vbi9zaGFyZWQvLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNw
OyZuYnNwO0luY2x1ZGluZyB0aGUgdXNlcidzIGh1bWFuIChuYXR1cmFsKSBsYW5ndWFnZSBwcmVm
ZXJlbmNlcyBpbiB0aGU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtzZXNzaW9uIGVzdGFibGlz
aG1lbnQgbmVnb3RpYXRpb24gaXMgaW5kZXBlbmRlbnQgb2YgdGhlIHVzZSBvZiBhPGJyIGNsYXNz
PSIiPg0KJm5ic3A7Jm5ic3A7cmVsYXkgc2VydmljZSBhbmQgaXMgdHJhbnNwYXJlbnQgdG8gYSB2
b2ljZSBzZXJ2aWNlIHByb3ZpZGVyLiA8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQpJIHRo
aW5rIGl0J3MgZXZlbiBicm9hZGVyIHRoYW4gJnF1b3Q7dHJhbnNwYXJlbnQgdG8gYSB2b2ljZSBz
ZXJ2aWNlPGJyIGNsYXNzPSIiPg0KcHJvdmlkZXImcXVvdDsgLS0gaXQncyB0cmFuc3BhcmVudCB0
byBhbnkgc2VyaXZpY2UgcHJvdmlkZXIsIGFzc3VtaW5nIHRoYXQ8YnIgY2xhc3M9IiI+DQp0aGUg
bWVkaWEgYXJlIGxhbmd1YWdlLW5ldXRyYWwuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0K
Jm5ic3A7Jm5ic3A7SW4gdGhlIGNhc2Ugb2YgYSBjYWxsIHRvIGUuZy4sIGFuIGFpcmxpbmUsIHRo
ZSBjYWxsIGNvdWxkIGJlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7YXV0b21hdGljYWxseSBo
YW5kbGVkIGJ5IGEgU3BhbmlzaC1zcGVha2luZyBhZ2VudC48YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQpJIHRoaW5rIHMvaGFuZGxlZCBieS9yb3V0ZWQgdG8vIGlzIHRoZSB1c3VhbCB1c2Fn
ZS48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQozLiAmbmJzcDtEZXNpcmVkIFNlbWFudGlj
czxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoZSBkZXNpcmVkIHNv
bHV0aW9uIGlzIGEgbWVkaWEgYXR0cmlidXRlIChwcmVmZXJhYmx5IHBlcjxiciBjbGFzcz0iIj4N
CmRpcmVjdGlvbik8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDt0aGF0IG1heSBiZSB1c2VkIHdp
dGhpbiBhbiBvZmZlciB0byBpbmRpY2F0ZSB0aGUgcHJlZmVycmVkPGJyIGNsYXNzPSIiPg0KbGFu
Z3VhZ2U8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtvZiBlYWNoIChkaXJlY3Rpb24gb2YgYSkg
bWVkaWEgc3RyZWFtLCBhbmQgd2l0aGluIGFuIGFuc3dlciB0bzxiciBjbGFzcz0iIj4NCiZuYnNw
OyZuYnNwO2luZGljYXRlIHRoZSBhY2NlcHRlZCBsYW5ndWFnZS48YnIgY2xhc3M9IiI+DQo8YnIg
Y2xhc3M9IiI+DQpJbiB0aGlzIG9uZSBpbnN0YW5jZSwgSSB0aGluayB5b3Ugd2FudCB0byB1c2Ug
JnF1b3Q7bGFuZ3VhZ2UocykmcXVvdDsgdG8gZHJpdmU8YnIgY2xhc3M9IiI+DQpob21lIHRoYXQg
dGhhdCBtdWx0aXBsZSBsYW5ndWFnZXMgY2FuIGJlIHNwZWNpZmllZDogJm5ic3A7JnF1b3Q7d2l0
aGluIGFuIG9mZmVyPGJyIGNsYXNzPSIiPg0KdG8gaW5kaWNhdGUgdGhlIHByZWZlcnJlZCBsYW5n
dWFnZShzKSZxdW90Oy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDso
TmVnb3RpYXRpbmcgbXVsdGlwbGUgc2ltdWx0YW5lb3VzIGxhbmd1YWdlcyB3aXRoaW4gYSBtZWRp
YSBzdHJlYW08YnIgY2xhc3M9IiI+DQppczxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO291dCBv
ZiBzY29wZSwgYXMgdGhlIGNvbXBsZXhpdHkgb2YgZG9pbmcgc28gb3V0d2VpZ2hzIHRoZTxiciBj
bGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzZWZ1bG5lc3MuKTxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCllvdSBtaWdodCB3YW50IHRvIHNheSBpbnN0ZWFkICZxdW90OyhOZWdvdGlhdGluZyBt
dWx0aXBsZSBzaW11bHRhbmVvdXM8YnIgY2xhc3M9IiI+DQpsYW5ndWFnZXMgd2l0aGluIGEgbWVk
aWEgc3RyZWFtIGlzIG91dCBvZiBzY29wZSBmb3IgdGhpcyBkb2N1bWVudC4pJnF1b3Q7PGJyIGNs
YXNzPSIiPg0KdG8gZW5zdXJlIHRoYXQgbm9ib2R5IGRlY2lkZXMgdG8gYXJndWUgd2hldGhlciAm
cXVvdDt0aGUgY29tcGxleGl0eSBvZjxiciBjbGFzcz0iIj4NCmRvaW5nIHNvIG91dHdlaWdocyB0
aGUgdXNlZnVsbmVzcyZxdW90Oy48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo0LiAmbmJz
cDtUaGUgZXhpc3RpbmcgJ2xhbmcnIGF0dHJpYnV0ZTxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0i
Ij4NCiZuYnNwOyZuYnNwO1JGQyA0NTY2IFtSRkM0NTY2XSBzcGVjaWZpZXMgYW4gYXR0cmlidXRl
ICdsYW5nJyB3aGljaCBhcHBlYXJzPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7c2ltaWxhciB0
byB3aGF0IGlzIG5lZWRlZCBoZXJlLCBidXQgaXMgbm90IHN1ZmZpY2llbnRseSBkZXRhaWxlZDxi
ciBjbGFzcz0iIj4NCmZvcjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzZSBoZXJlLjxiciBj
bGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZxdW90O2ZvciB1c2UgaGVyZSZxdW90OyBpc24ndCBx
dWl0ZSByaWdodC4gJm5ic3A7TWF5YmUgJnF1b3Q7aXMgbm90IHN1ZmZpY2llbnRseTxiciBjbGFz
cz0iIj4NCnNwZWNpZmljPGJyIGNsYXNzPSIiPg0Kb3IgZmxleGlibGUgdG8gc2F0aXNmeSB0aGUg
cmVxdWlyZW1lbnRzJnF1b3Q7LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZu
YnNwO0luIGFkZGl0aW9uLCBpdCBpcyBub3QgbWVudGlvbmVkIGluIFtSRkMzMjY0XTxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCiZxdW90O2l0JnF1b3Q7IGlzIHNvbWV3aGF0IGFtYmlndW91
cyBoZXJlLCBwZXJoYXBzIGNoYW5nZSB0byAmcXVvdDt0aGUgJ2xhbmcnPGJyIGNsYXNzPSIiPg0K
YXR0cmlidXRlJnF1b3Q7LjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjUuICZuYnNwO1By
b3Bvc2VkIFNvbHV0aW9uPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KUGVyaGFwcyAvUHJv
cG9zZWQgU29sdXRpb24vU29sdXRpb24vLCBzaW5jZSBvbmNlIHRoaXMgZHJhZnQgaXM8YnIgY2xh
c3M9IiI+DQphcHByb3ZlZCwgaXQgYmVjb21lcyB0aGUgc29sdXRpb24uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KNS4yLiAmbmJzcDtOZXcgJ2h1bWludGxhbmctc2VuZCcgYW5kICdodW1p
bnRsYW5nLXJlY3YnIGF0dHJpYnV0ZXM8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDthPWh1bWludGxhbmctc2VuZDombHQ7bGFuZ3VhZ2Ug
dGFnJmd0OzxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2E9aHVt
aW50bGFuZy1yZWN2OiZsdDtsYW5ndWFnZSB0YWcmZ3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0KVGhpcyBpcyBwcmVzZW50ZWQgYXMgdGhlIGdlbmVyaWMgZm9ybSBvZiB0aGUgYXR0cmli
dXRlcywgYnV0IHRoZXJlIGlzPGJyIGNsYXNzPSIiPg0Kbm8gaW5kaWNhdGlvbiBvZiB0aGUgcG9z
aWJsZSBhc3Rlcmlzay48YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtU
aGUgdmFsdWVzIGNvbnN0aXR1dGUgYSBsaXN0IG9mIGxhbmd1YWdlczxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwO2luIHByZWZlcmVuY2Ugb3JkZXIgKGZpcnN0IGlzIG1vc3QgcHJlZmVycmVkKS48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQomcXVvdDtUaGUgdmFsdWVzJnF1b3Q7IGlzbid0
IHZlcnkgY2xlYXIsIGJlY2F1c2UgdGhlIHZhbHVlcyBhcmUgaW4gc3VjY2Vzc2l2ZTxiciBjbGFz
cz0iIj4NCmF0dHJpYnV0ZXMuICZuYnNwO1lvdSB3YW50IHRvIHNheSBzb21ldGhpbmcgbGlrZSAm
cXVvdDtUaGUgc2VxdWVuY2Ugb2YgdmFsdWVzPGJyIGNsYXNzPSIiPg0KaW48YnIgY2xhc3M9IiI+
DQp0aGUgb2NjdXJyZW5jZXMgb2Ygb25lIG9mIHRoZXNlIGF0dHJpYnV0ZXMgY29uc3RpdHV0ZXMg
Li4uJnF1b3Q7LiA8YnIgY2xhc3M9IiI+DQpIb3dldmVyLDxiciBjbGFzcz0iIj4NCnNlZSB0aGUg
dGVjaG5pY2FsIGNvbW1lbnRzIGFib3ZlLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwO1doZW4gcGxhY2luZyBhbiBlbWVyZ2VuY3kgY2FsbCwgYW5kIGluIGFueSBvdGhl
ciBjYXNlIHdoZXJlIHRoZTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO2xhbmd1YWdlIGNhbm5v
dCBiZSBhc3N1bWVkIGZyb20gY29udGV4dCwgZWFjaCBtZWRpYSBzdHJlYW0gaW4gYW48YnIgY2xh
c3M9IiI+DQombmJzcDsmbmJzcDtvZmZlciBwcmltYXJpbHkgaW50ZW5kZWQgZm9yIGh1bWFuIGxh
bmd1YWdlIGNvbW11bmljYXRpb24gU0hPVUxEPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7c3Bl
Y2lmeSBib3RoIChvciBpbiBzb21lIGNhc2VzLCBvbmUgb2YpIHRoZSAnaHVtaW50bGFuZy1zZW5k
JyBhbmQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsnaHVtaW50bGFuZy1yZWN2JyBhdHRyaWJ1
dGVzLjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NClByb2JhYmx5IHMvYXNzdW1lZC9pbmZl
cnJlZC8uPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KQ291bGQgeW91IGJlIG1vcmUgYWNj
dXJhdGUgYnk8YnIgY2xhc3M9IiI+DQpzL29yIGluIHNvbWUgY2FzZXMvb3IgZm9yIHVuaWRpcmVj
dGlvbmFsIHN0cmVhbXMvPzxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCjUuMy4gJm5ic3A7
QWR2aXNvcnkgdnMgUmVxdWlyZWQ8YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQombmJzcDsm
bmJzcDtUaGUgbWVjaGFuaXNtIGZvciBpbmRpY2F0aW5nIHRoaXMgcHJlZmVyZW5jZSBpcyB0aGF0
LCBpbiBhbiBvZmZlciw8YnIgY2xhc3M9IiI+DQppZjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNw
O3RoZSBsYXN0IGNoYXJhY3RlciBvZiBhbnkgb2YgdGhlICdodW1pbnRsYW5nLXJlY3YnIG9yICdo
dW1pbnRsYW5nLTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3NlbmQnIHZhbHVlcyBpcyBhbiBh
c3RlcmlzaywgdGhpcyBpbmRpY2F0ZXMgYSByZXF1ZXN0IHRvIG5vdCBmYWlsPGJyIGNsYXNzPSIi
Pg0KdGhlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbCAoc2ltaWxhciB0byBTSVAgQWNj
ZXB0LUxhbmd1YWdlIHN5bnRheCkuICZuYnNwO0VpdGhlciB3YXksIHRoZTxiciBjbGFzcz0iIj4N
CmNhbGxlZDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3BhcnR5IE1BWSBpZ25vcmUgdGhpcywg
ZS5nLiwgZm9yIHRoZSBlbWVyZ2VuY3kgc2VydmljZXMgdXNlIGNhc2UsPGJyIGNsYXNzPSIiPg0K
YTxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1BTQVAgd2lsbCBsaWtlbHkgbm90IGZhaWwgdGhl
IGNhbGwuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KVGhlIGNvbnN0cnVjdGlvbiBvZiB0
aGlzIHBhcmFncmFwaCBpc24ndCBxdWl0ZSBjb21wbGV0ZS4gJm5ic3A7SXQgc2F5czxiciBjbGFz
cz0iIj4NCnRoYXQ8YnIgY2xhc3M9IiI+DQppZiBhbiBhc3RlcmlzayBpcyBwcmVzZW50LCBhIHJl
cXVlc3Qgc2hvdWxkbid0IGZhaWwsIGJ1dCBpdCBkb2Vzbid0PGJyIGNsYXNzPSIiPg0Kc2F5IHRo
YXQgaWYgbm8gYXN0ZXJpc2sgaXMgcHJlc2VudCwgYSByZXF1ZXN0IHNob3VsZCBmYWlsIGlmIHRo
ZXJlIGlzPGJyIGNsYXNzPSIiPg0Kbm8gbGFuZ3VhZ2UgbWF0Y2guICZuYnNwO0FuZCBpdCdzIHRo
ZSBsYXR0ZXIgY29uZGl0aW9uIHRoYXQgbWFrZXMgdGhlPGJyIGNsYXNzPSIiPg0Kc2Vjb25kIHNl
bnRlbmNlIG1lYW5pbmdmdWwuICZuYnNwO1NvIEkgdGhpbmsgeW91IHdhbnQgdG8gaW5zZXJ0IGJl
dHdlZW48YnIgY2xhc3M9IiI+DQp0aGU8YnIgY2xhc3M9IiI+DQp0d28gc2VudGVuY2VzIG9uZSBy
ZWdhcmRpbmcgdGhlIGFic2VuY2Ugb2YgYW4gYXN0ZXJpc2suPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KNS41LiAmbmJzcDtFeGFtcGxlczxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4N
CkdpdmVuIHRoYXQgdGhlIGNvbWJpbmVkIGF1ZGlvL3ZpZGVvIG1lY2hhbmlzbSBpcyB0aGUgb25s
eTxiciBjbGFzcz0iIj4NCmlycmVndWxhcml0eTxiciBjbGFzcz0iIj4NCmluIHRoaXMgc3lzdGVt
LCB0aGVyZSBvdWdodCB0byBiZSBhbiBleGFtcGxlIG9mIGl0LiAmbmJzcDtFLmcuLDxiciBjbGFz
cz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO0FuIGV4YW1wbGUgb2YgYSBzdXBwbGVt
ZW50YWwgdmlkZW8gc3RyZWFtIHdpdGggYSBzcG9rZW4gbGFuZ3VhZ2U8YnIgY2xhc3M9IiI+DQom
bmJzcDsmbmJzcDthdWRpbyBzdHJlYW06PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7bT12aWRlbyA1MTM3MiBSVFAvQVZQIDMxIDMyPGJy
IGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1pbnRsYW5nLXNl
bmQ6ZW48YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDthPWh1bWlu
dGxhbmctcmVjdjplbjxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwO209YXVkaW8gNDkyNTAgUlRQL0FWUCAyMDxiciBjbGFzcz0iIj4NCiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO2E9aHVtaW50bGFuZy1zZW5kOmVuPGJyIGNsYXNz
PSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7YT1odW1pbnRsYW5nLXJlY3Y6ZW48
YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo2LiAmbmJzcDtJQU5BIENvbnNpZGVyYXRpb25z
PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7aHVtaW50bGFuZy12YWx1ZSA9ICZuYnNwO0xhbmd1YWdlLVRhZyBbIGFzdGVyaXNrIF08YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs7IExhbmd1YWdl
LVRhZyBkZWZpbmVkIGluIFJGQyA1NjQ2PGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7YXN0ZXJpc2sgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7PSAmbmJzcDsmcXVvdDsqJnF1b3Q7PGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNz
PSIiPg0Kcy9MYW5ndWFnZS1UYWcgZGVmaW5lZCBpbiBSRkMgNTY0Ni9MYW5ndWFnZS1UYWcgYXMg
ZGVmaW5lZCBpbiBSRkM8YnIgY2xhc3M9IiI+DQo1NjQ2LzxiciBjbGFzcz0iIj4NCjxiciBjbGFz
cz0iIj4NCkJ1dCBwZXJoYXBzIGFsc28gcy9SRkMgNTY0Ni9CQ1AgNDcvLCB3aGljaCBlbnN1cmVz
IHRoYXQgJnF1b3Q7aHVtaW50bGFuZyZxdW90OzxiciBjbGFzcz0iIj4NCnRyYWNrcyB0aGUgY3Vy
cmVudCB2ZXJzaW9uIG9mIGxhbmd1YWdlIHRhZ3MuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIi
Pg0KQXBwZW5kaXggQS4gJm5ic3A7SGlzdG9yaWMgQWx0ZXJuYXRpdmUgUHJvcG9zYWw6IENhbGxl
ci1wcmVmczxiciBjbGFzcz0iIj4NCjxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO1RoaXM8YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDtyZXN1bHRzIGluIGEgbW9yZSBmcmFnaWxlIHNvbHV0aW9u
IHNpbmNlIHRoZSBtZWRpYSBtb2RhbGl0eSBhbmQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDts
YW5ndWFnZSB3b3VsZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNp
ZmljPGJyIGNsYXNzPSIiPg0KbWVkaWE8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtmb3JtYXRz
ICh3aGljaCBpbmhlcmVudGx5IGluY2x1ZGUgdGhlIG1vZGFsaXR5KSB3b3VsZCBiZTxiciBjbGFz
cz0iIj4NCm5lZ290aWF0ZWQ8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDthdCBhIGRpZmZlcmVu
dCBsZXZlbCAodHlwaWNhbGx5IFNEUCwgZXNwZWNpYWxseSBpbiB0aGUgZW1lcmdlbmN5PGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Y2FsbGluZyBjYXNlcyksIG1ha2luZyBpdCBlYXNpZXIgdG8g
aGF2ZSBtaXNtYXRjaGVzIChzdWNoIGFzIHdoZXJlPGJyIGNsYXNzPSIiPg0KJm5ic3A7Jm5ic3A7
dGhlIG1lZGlhIG1vZGFsaXR5IG5lZ290aWF0ZWQgaW4gU0lQIGRvbid0IG1hdGNoIHdoYXQgd2Fz
PGJyIGNsYXNzPSIiPg0KbmVnb3RpYXRlZDxiciBjbGFzcz0iIj4NCiZuYnNwOyZuYnNwO3VzaW5n
IFNEUCkuPGJyIGNsYXNzPSIiPg0KPGJyIGNsYXNzPSIiPg0KJnF1b3Q7dGhlIG1lZGlhIG1vZGFs
aXR5IGFuZCBsYW5ndWFnZSB3b3VsZCBiZSBuZWdvdGlhdGVkIHVzaW5nIFNJUCZxdW90OyBpc24n
dDxiciBjbGFzcz0iIj4NCnF1aXRlIHRoZSByaWdodCB3YXkgdG8gc2F5IGl0IGJlY2F1c2UgU0lQ
IGlzbid0IGV4cGxpY2l0bHk8YnIgY2xhc3M9IiI+DQpuZWdvdGlhdGluZzxiciBjbGFzcz0iIj4N
CnRoZSBtb2RhbGl0eS4gJm5ic3A7QmV0dGVyIHdvdWxkIGJlPGJyIGNsYXNzPSIiPg0KPGJyIGNs
YXNzPSIiPg0KJm5ic3A7Jm5ic3A7Li4uIHRoZSBsYW5ndWFnZSAoYW5kIGJ5IGltcGxpY2F0aW9u
IHRoZSBtZWRpYSBtb2RhbGl0eSkgd291bGQgYmU8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtu
ZWdvdGlhdGVkIHVzaW5nIFNJUCwgYW5kIHRoZW4gdGhlIHNwZWNpZmljIG1lZGlhICh3aGljaDxi
ciBjbGFzcz0iIj4NCmluaGVyZW50bHk8YnIgY2xhc3M9IiI+DQombmJzcDsmbmJzcDtpbmNsdWRl
IHRoZSBtb2RhbGl0aWVzIGFuZCBmb3JtYXRzKSB3b3VsZCBiZSBuZWdvdGlhdGVkIGF0IGE8YnIg
Y2xhc3M9IiI+DQombmJzcDsmbmJzcDtkaWZmZXJlbnQgbGV2ZWwgLi4uPGJyIGNsYXNzPSIiPg0K
PGJyIGNsYXNzPSIiPg0KW0VORF08YnIgY2xhc3M9IiI+DQo8YnIgY2xhc3M9IiI+DQo8YnIgY2xh
c3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9
IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgc3R5bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCxzYW5zLXNl
cmlmO2ZvbnQtc2l6ZToxMXB4O2NvbG9yOiM5OTk5OTk7Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtZmFtaWx5OiBBcmlhbCxzYW5zLXNlcmlmO2NvbG9yOiM5OTk5OTk7IG1zby1mYXJl
YXN0LWZvbnQtZmFtaWx5OiBBcmlhbDsgbXNvLWZhcmVhc3QtdGhlbWUtZm9udDogbWlub3ItbGF0
aW47IG1zby1iaWRpLWZvbnQtZmFtaWx5OiAmcXVvdDtBcmlhbCZxdW90OzsgbXNvLWFuc2ktbGFu
Z3VhZ2U6IEVOLVVTOyBtc28tZmFyZWFzdC1sYW5ndWFnZTogRU4tR0I7IG1zby1iaWRpLWxhbmd1
YWdlOiBBUi1TQSI+VGhpcw0KIGVtYWlsIGFuZCBpdHMgYXR0YWNobWVudHMgYXJlIGludGVuZGVk
IGZvciB0aGUgYWJvdmUgbmFtZWQgb25seSBhbmQgbWF5IGJlIGNvbmZpZGVudGlhbC4gSWYgdGhl
eSBoYXZlIGNvbWUgdG8geW91IGluIGVycm9yIHlvdSBtdXN0IHRha2Ugbm8gYWN0aW9uIGJhc2Vk
IG9uIHRoZW0sIG5vciBtdXN0IHlvdSBjb3B5IG9yIHNob3cgdGhlbSB0byBhbnlvbmU7IHBsZWFz
ZSByZXBseSB0byB0aGlzIGVtYWlsIG9yIGNhbGwgJiM0Mzs0NCAyMDcgMzU2IDA2MDANCiBhbmQg
aGlnaGxpZ2h0IHRoZSBlcnJvci4gPC9zcGFuPjwvcD4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_D80EB5AC8E94475683D02F6FB721A883gsmacom_--


From nobody Tue Feb 21 16:20:23 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A4D5129474 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 16:20: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RWdxr8DwDx0L for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 16:20:20 -0800 (PST)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::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 AE4B1129479 for <ietf@ietf.org>; Tue, 21 Feb 2017 16:20:20 -0800 (PST)
Received: by mail-ua0-x232.google.com with SMTP id x24so23683892uae.3 for <ietf@ietf.org>; Tue, 21 Feb 2017 16:20:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=EZMLsG7zEzSL4HSmzLH+fSVlCXDRUXkABqmSw6Fw0A4=; b=arQGeaGsjSKtfXQjZJsrECBSkuPTDalc1WGGRP/z8sekaeKnxfkvOssWAM729CRcQN tr1OiSupeB0FZ5HFg+3k5crCXSn8Cp8dT12fa3wAYmKYmpYd9V8RH/wbR/y+F7QNs8n/ 9IgSLr8uRhtcN1L4zOYDdet6Hgqvkebxii4IDtXMMOAiRlX3KDBbxJzZnu13B6J3Q8bl 4SN3O5BMcFdPm/bMV740TAVumytjkzS17Frw7wYuUbSaOwqcS77rsVn86ueyj1igkttW nWcOLSA4m1oF2nXREa6bHLZnaR8LBHiLXpKxru0jNaSVs3hLNgXOktpYbaBXDRV9CQf8 ePag==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=EZMLsG7zEzSL4HSmzLH+fSVlCXDRUXkABqmSw6Fw0A4=; b=ks8Wv94v6FB327x0oPCOARXyzFRZJilZ7tQdFf3vk14h8Ju9+aHNkS8qaytem/fZrj NRg/abH6gT80IOJnfnppI5De/gfM0Q58dqsJbBXutziQIc7dqlunc8sLEHZeyQ7y/pJq OJdZpNLeHQ4PWHSxAdZrvgHLR9l6d82AbWrjHbU5eWLWgpTOOt4lb9gdXcZJ5/gfAv1X ZjDdiwrtxbSjKiGZCFmLepv7z2w9GXTQqtEo5VJOLaBIYOvFdk45/ImIQZzRrAqh+KyN ie4MaXbNKAIoMbDNToELa22QYfKgJQL9JggSoAtm7jn/Ijfj1gvUXki1YCTYUzYU01EU +T3w==
X-Gm-Message-State: AMke39kOd+wQc4G3JUrexbhcPxXBVf1I8Pvvdl0ZDbYbVUkC/pIZhG3UMSium/r7O8vPq8XwZAdJKjUCvq0Z5KZo
X-Received: by 10.176.7.204 with SMTP id d12mr8863842uaf.171.1487722819607; Tue, 21 Feb 2017 16:20:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Tue, 21 Feb 2017 16:19:58 -0800 (PST)
In-Reply-To: <20170221101339.GC84656@Vurt.local>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 09:19:58 +0900
Message-ID: <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=f403045f7ea030a2310549137682
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/taiz9WXqaeeTlCjqkLtHkkQTyYc>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 00:20:22 -0000

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

On Tue, Feb 21, 2017 at 7:13 PM, Job Snijders <job@ntt.net> wrote:

> I've looked at all configured IPv6 addresses on AS 2914 equipment.
> The above percentages come from grepping through configurations of
> thousands of interconnections. I'm confident that other networks will
> show similar prefix length distributions.
>

"Thousands of interconnections" are not really relevant given that we're
well into the hundreds of millions of IPv6 hosts on residential or mobile
connections that provide one or more /64s.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Feb 21, 2017 at 7:13 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"=
mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I&#39;ve looked at all configured IPv6 addre=
sses on AS 2914 equipment.<br>
The above percentages come from grepping through configurations of<br>
thousands of interconnections. I&#39;m confident that other networks will<b=
r>
show similar prefix length distributions.<br></blockquote><div><br></div><d=
iv>&quot;Thousands of interconnections&quot; are not really relevant given =
that we&#39;re well into the hundreds of millions of IPv6 hosts on resident=
ial or mobile connections that provide one or more /64s.</div></div></div><=
/div>

--f403045f7ea030a2310549137682--


From nobody Tue Feb 21 17:07:19 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF7F1294BB for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 17:07:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z5lA4sjJql-1 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 17:07:11 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 A4C741294BC for <ietf@ietf.org>; Tue, 21 Feb 2017 17:07:11 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 0D44AB53 for <ietf@ietf.org>; Wed, 22 Feb 2017 01:07:11 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UHCFOehObP4n for <ietf@ietf.org>; Tue, 21 Feb 2017 19:07:10 -0600 (CST)
Received: from mail-it0-f72.google.com (mail-it0-f72.google.com [209.85.214.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id DA2F3B4A for <ietf@ietf.org>; Tue, 21 Feb 2017 19:07:10 -0600 (CST)
Received: by mail-it0-f72.google.com with SMTP id w185so207482171ita.5 for <ietf@ietf.org>; Tue, 21 Feb 2017 17:07:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YHMs3F2li03QhYYaYtSXODGJGlEfHKIEbhC/e5ixB/E=; b=IKMwY8Jf+4MJJlB4hcozVEhFwi+ubgBFgbHKw6Fnd0BYxAMXP4AdAZZQNnO2aACZoD snRY3zsvLfOAEJLzg2dLL2jJpuv+QxcjpIHnwPM40sbDed/EkurOOaXR84Ic5g8P6ynm jcXFZd7wZQQz+/YjxxdNbtFMK+q0swieTivB4YzE4hrpJoqUyovwfB652UWgH7Pfex1Z 18hbc/A94T9okIh1uxEscv1O3F/B9r2F303hwqMG0mA6H+LNtf1S8KUro5XpELlASiD2 tTx/OydPWGSgujsoU1orZTS3RL7SBrDdhezUKJ5WpNwvIE4F9WT06wlddydRc8bdVE6Y F6gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YHMs3F2li03QhYYaYtSXODGJGlEfHKIEbhC/e5ixB/E=; b=a+BZZODU0Aw19HYe/2sTPlKqYSTdQb0LBbCDIf57IV0Rr2K3/wRTKVJxXZN3gYZB0Z EYh1g2kmHlULbP7w9IvL0E+GgBrzW6ouKKlA4nVZJXSnvOVhBcnK5LV4WNil2rfPPJlQ PnJoeS6QFuCwrxp/QlgH3jc9qeksqHfsHa3ZLyAkemE7uPNABt0KJxPutpmuQvSnFCKd qd/vgpeG7YDIlYssMWcX7ifSK1/t5gXzorR8x0rGwtPDz5cAjhHUM1zqC5n/ltr9vF6d qdm8y+u9vRnppk8hmhsP9+OfPI/zJ6Ch6DToZySARLwp6ADT5vUlBKWyBlKjX1s2wOOO 5M5w==
X-Gm-Message-State: AMke39kzPMSWkXdox5ufCs5VamxYPLdzRmpANvw8VYwbBj9hqFKBrRd4chIU4pVwHZHcP/0y+9qzDMvO+npVX/FLIGO14TsSCKaENlJ+04HUNS8wprPetOxkXPsWJtjOvFQ=
X-Received: by 10.107.9.96 with SMTP id j93mr22004663ioi.149.1487725630333; Tue, 21 Feb 2017 17:07:10 -0800 (PST)
X-Received: by 10.107.9.96 with SMTP id j93mr22004640ioi.149.1487725630099; Tue, 21 Feb 2017 17:07:10 -0800 (PST)
Received: from [10.38.148.97] ([166.175.58.155]) by smtp.gmail.com with ESMTPSA id e11sm179283ita.10.2017.02.21.17.07.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 17:07:05 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-49AD28CC-A0ED-4A40-AF00-FA5644496A0D
Mime-Version: 1.0 (1.0)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: David Farmer <farmer@umn.edu>
X-Mailer: iPhone Mail (14D27)
In-Reply-To: <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
Date: Tue, 21 Feb 2017 19:07:03 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <55B2855A-5E96-4A6A-BAE0-CAC24191E792@umn.edu>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IKzO2cUrXENoVHmhjSteIAH8JAU>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:07:14 -0000

--Apple-Mail-49AD28CC-A0ED-4A40-AF00-FA5644496A0D
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable



Sent from my iPhone

> On Feb 21, 2017, at 18:19, Lorenzo Colitti <lorenzo@google.com> wrote:
>=20
>> On Tue, Feb 21, 2017 at 7:13 PM, Job Snijders <job@ntt.net> wrote:
>> I've looked at all configured IPv6 addresses on AS 2914 equipment.
>> The above percentages come from grepping through configurations of
>> thousands of interconnections. I'm confident that other networks will
>> show similar prefix length distributions.
>=20
> "Thousands of interconnections" are not really relevant given that we're w=
ell into the hundreds of millions of IPv6 hosts on residential or mobile con=
nections that provide one or more /64s.

It can equally be said that the millions of IPv6 hosts don't matter either, b=
ecause without those thousands of interconnections the millions of hosts are=
n't connected to each other or the Internet.  But both perspectives are equa=
lly correct, its not one or the other, it's both, they are interdependent on=
 each other.  Without hosts there is no need for the interconnections, and w=
ithout the interconnections there wouldn't be millions of hosts in the first=
 place.=

--Apple-Mail-49AD28CC-A0ED-4A40-AF00-FA5644496A0D
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: 7bit

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Sent from my iPhone</div><div><br>On Feb 21, 2017, at 18:19, Lorenzo Colitti &lt;<a href="mailto:lorenzo@google.com">lorenzo@google.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Feb 21, 2017 at 7:13 PM, Job Snijders <span dir="ltr">&lt;<a href="mailto:job@ntt.net" target="_blank">job@ntt.net</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've looked at all configured IPv6 addresses on AS 2914 equipment.<br>
The above percentages come from grepping through configurations of<br>
thousands of interconnections. I'm confident that other networks will<br>
show similar prefix length distributions.<br></blockquote><div><br></div><div>"Thousands of interconnections" are not really relevant given that we're well into the hundreds of millions of IPv6 hosts on residential or mobile connections that provide one or more /64s.</div></div></div></div>
</div></blockquote><div><br></div><div>It can equally be said that the millions of IPv6 hosts don't matter either, because without those thousands of interconnections the millions of hosts aren't connected to each other or the Internet. &nbsp;But both perspectives are equally correct, its not one or the other, it's both, they are interdependent on each other. &nbsp;Without hosts there is no need for the interconnections, and without the interconnections there wouldn't be millions of hosts in the first place.</div></body></html>
--Apple-Mail-49AD28CC-A0ED-4A40-AF00-FA5644496A0D--


From nobody Tue Feb 21 17:13:45 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 297D11294A9; Tue, 21 Feb 2017 17:13:44 -0800 (PST)
X-Quarantine-ID: <UaO1YlHoDi94>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 UaO1YlHoDi94; Tue, 21 Feb 2017 17:13:41 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5FF129443; Tue, 21 Feb 2017 17:13:41 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 21 Feb 2017 17:04:27 -0800
Mime-Version: 1.0
Message-Id: <p06240608d4d2961c0304@[99.111.97.136]>
In-Reply-To: <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <D80EB5AC-8E94-4756-83D0-2F6FB721A883@gsma.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 21 Feb 2017 17:13:33 -0800
To: Natasha Rooney <nrooney@gsma.com>, Dale Worley <worley@ariadne.com>, "slim@ietf.org" <slim@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: Review of draft-ietf-slim-negotiating-human-language-06
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H1K3UHbcMst6k3Fy4PfUPtQajvA>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-slim-negotiating-human-language.all@ietf.org" <draft-ietf-slim-negotiating-human-language.all@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:13:44 -0000

I am almost done with my reply.  I wasn't ignoring Dale, I've been 
working on his comments.

At 11:28 PM +0000 2/21/17, Natasha Rooney wrote:

>  Hi Dale! Many thanks for these comments, as one of the SLIM chairs 
> I'll work on getting some answers to you or I'll request the author 
> or one of the SLIM active participants to respond.
>
>  Bernard, Randall and SLIM - see below re Dale's points. 
>
>
>  **** A. Call failure ****
>  Randall or Bernard can you respond to this? I imagine the UA call 
> failure method is UA specific, but if there is a clash with SIP 
> level call fail then this should be addressed.
>
>  **** B. Audio/Video coordination ****
>  I believe the theory behind the current draft is that the spoken 
> and video streams will be different in the cases of such things as 
> sign language. Video could therefore be sign and audio would be a 
> spoken language. I'm not sure if the suggestion he satisfies this 
> case?
>
>  **** C. "humintlang" seems long to me ****
>  Bernard - I don't see the issue with shortening humintlang, but the 
> group might. I suggest we throw this to the group for discussion.
>
>  **** D. Use the Accept-Language syntax ****
>  Randall and Bernard - is this an acceptable change? Or one we need 
> to discuss further. Seems like a reasonable request, but also a 
> larger change, which is why I ask!
>
>  **** E. Have an attribute to abbreviate the 
> bidirectionally-symmetric case ****
>  I do not remember us having this discussion within the group, 
> although it may have occurred before I became chair.
>  Randall, Brian or Bernard - has this idea been discussed before? If 
> so, can one of you respond with an explanation as to why we haven't 
> done this?
>
>  **** Editorial comments and nits *****
>  Randall - can you take a look through Dale's editorial comments and 
> shout if there is any problems with these suggestions; if 
> everything is ok please make the changes.
>
>  Thanks all!
>
>  Natasha Rooney | Internet Engineering Director | Internet and Web 
> Team | Technology | GSMA 
> | <mailto:nrooney@gsma.com>nrooney@gsma.com | +44 (0) 7730 219 765 
> | @thisNatasha | Skype: <mailto:nrooney@gsm.org>nrooney@gsm.org
>
>>  On 18 Feb 2017, at 02:32, Dale Worley 
>> <<mailto:worley@ariadne.com>worley@ariadne.com> wrote:
>>
>>  Reviewer: Dale Worley
>>  Review result: Ready with Nits
>>
>>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>>  Review Team (Gen-ART) reviews all IETF documents being processed
>>  by the IESG for the IETF Chair.  Please treat these comments just
>>  like any other last call comments.
>>
>>  For more information, please see the FAQ at
>> 
>> <<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>  Document:  draft-ietf-slim-negotiating-human-language-06
>>  Reviewer:  Dale R. Worley
>>  Review Date:  2017-02-17
>>  IETF LC End Date:  2017-02-20
>>  IESG Telechat date:  [unknown]
>>
>>  Summary:
>>        This draft is basically ready for publication, but has nits
>>        that should be fixed before publication.
>>
>>  * Technical comments
>>
>>  A. Call failure
>>
>>  If a call fails due to no available language match, in what way(s)
>>  does it fail?  Section 5.3 says
>>
>>    If such an offer is received, the receiver MAY
>>    reject the media, ignore the language specified, or attempt to
>>    interpret the intent
>>
>>  But I suspect it's also allowed for the UAS to fail the call at the
>>  SIP level.  Whether or not that is allowed (or at least envisioned)
>>  should be described.  And what response code(s)/warn-code(s) should
>>  be
>>  used for that?
>>
>>  B. Audio/Video coordination
>>
>>    5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>    Note that while signed language tags are used with a video stream
>>  to
>>    indicate sign language, a spoken language tag for a video stream
>>  in
>>    parallel with an audio stream with the same spoken language tag
>>    indicates a request for a supplemental video stream to see the
>>    speaker.
>>
>>  And there's a similar paragraph in 5.4:
>>
>>>    A spoken language tag for a video stream in conjunction with an
>>>
>>  audio
>>
>>>    stream with the same language might indicate a request for
>>>    supplemental video to see the speaker.
>>>
>>
>>  I think this mechanism needs to be described more exactly, and in
>>  particular, it should not depend on the UA understanding which
>>  language tags are spoken language tags.  It seems to me that a
>>  workable rule is that there is an audio stream and a video stream and
>>  they specify exactly the same language tag in their respective
>>  humintlang attributes.  In that case, it is a request for a spoken
>>  language with simultaneous video of the speaker, and those requests
>>  should be considered satisfied only if both streams can be
>>  established.
>>
>>  * The following three items are adjustments to the design which I'd
>>  like to know have been considered.
>>
>>  C. "humintlang" seems long to me
>>
>>  Given the excessive length of SDP in practice, it seems to me that a
>>  shorter attribute name would be desirable.  E.g., "humlang" as was
>>  used in some previous versions.  Or is there a coordinated usage with
>>  other names in the "hum*lang" pattern?
>>
>>  D. Use the Accept-Language syntax
>>
>>  It seems to me that it would better to use the Accept-Language syntax
>>  for the attribute values.  This allows (1) specifiying the quality of
>>  language experience, allowing clear description of bilingualism, (2)
>>  a
>>  unified method of specifying whether or not arbitrary languages are
>>  acceptable, and (3) abbreviating SDP descriptions.
>>
>>  In a way, the fact that the current proposal seems to require (but
>>  does not directly specify) the coordinated absence/presence of an
>>  asterisk on all of the repetitions of humintlang-send or
>>  humintlang-recv is a warning that the syntax doesn't represent the
>>  semantics as well as it might.
>>
>>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>
>>  Note that all examples are bidirectionally symmetric, and the text
>>  says that requests and responses SHOULD be bidirectionally symmetric.
>>  So it would be a very useful abbreviation to define
>>  "humintlang=<value>" to be equivalent to the combination of
>>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>>
>>  Combining proposals C, D, and E, the examples become
>>
>>       m=audio 49170 RTP/AVP 0
>>       a=humlang:en
>>
>>       m=video 51372 RTP/AVP 31 32
>>       a=humlang:ase,*;q=0.1
>>
>>       m=audio 49250 RTP/AVP 20
>>       a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>>
>>       m=text 45020 RTP/AVP 103 104
>>       a=humlang:gr
>>
>>  which requires about half as many characters as they have now.
>>
>>  * Editorial comments and nits
>>
>>  Abstract
>>
>>    This document describes the need and a solution using new SDP
>>  stream
>>    attributes.
>>
>>  I don't think the term "stream attribute" is used in RFC 4566.
>>  Instead, it uses "media attribute".
>>
>>  1.  Introduction
>>
>>    caller and callee know each other or there is contextual or out of
>>    band information from which the language(s) and media modalities
>>  can
>>
>>  I think this context, it's preferred to hyphenate "out-of-band" to
>>  make it clearly be an adjective.
>>
>>    This approach has a number of benefits, including that it is
>>  generic
>>    (applies to all interactive communications negotiated using SDP)
>>  and
>>    not limited to emergency calls.
>>
>>  I think s/and not limited to/and is not limited to/ reads more
>>  smoothly.
>>
>>    But it is clearly useful in many other cases.  For
>>    example, someone calling a company call center or a Public Safety
>>    Answering Point (PSAP) should be able to indicate if one or more
>>    specific signed, written, and/or spoken languages are preferred,
>>  the
>>    callee should be able to indicate its capabilities in this area,
>>  and
>>    the call proceed using in-common language(s) and media forms.
>>
>>  I think s/preferred, the callee/preferred; the callee/ because the
>>  sentence is the concatenation of two sentences.
>>
>>  Perhaps s/in-common/shared/.
>>
>>    Including the user's human (natural) language preferences in the
>>    session establishment negotiation is independent of the use of a
>>    relay service and is transparent to a voice service provider.
>>
>>  I think it's even broader than "transparent to a voice service
>>  provider" -- it's transparent to any serivice provider, assuming that
>>  the media are language-neutral.
>>
>>    In the case of a call to e.g., an airline, the call could be
>>    automatically handled by a Spanish-speaking agent.
>>
>>  I think s/handled by/routed to/ is the usual usage.
>>
>>  3.  Desired Semantics
>>
>>    The desired solution is a media attribute (preferably per
>>  direction)
>>    that may be used within an offer to indicate the preferred
>>  language
>>    of each (direction of a) media stream, and within an answer to
>>    indicate the accepted language.
>>
>>  In this one instance, I think you want to use "language(s)" to drive
>>  home that that multiple languages can be specified:  "within an offer
>>  to indicate the preferred language(s)".
>>
>>    (Negotiating multiple simultaneous languages within a media stream
>>  is
>>    out of scope, as the complexity of doing so outweighs the
>>    usefulness.)
>>
>>  You might want to say instead "(Negotiating multiple simultaneous
>>  languages within a media stream is out of scope for this document.)"
>>  to ensure that nobody decides to argue whether "the complexity of
>>  doing so outweighs the usefulness".
>>
>>  4.  The existing 'lang' attribute
>>
>>    RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>    similar to what is needed here, but is not sufficiently detailed
>>  for
>>    use here.
>>
>>  "for use here" isn't quite right.  Maybe "is not sufficiently
>>  specific
>>  or flexible to satisfy the requirements".
>>
>>    In addition, it is not mentioned in [RFC3264]
>>
>>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>  attribute".
>>
>>  5.  Proposed Solution
>>
>>  Perhaps /Proposed Solution/Solution/, since once this draft is
>>  approved, it becomes the solution.
>>
>>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>       a=humintlang-send:<language tag>
>>       a=humintlang-recv:<language tag>
>>
>>  This is presented as the generic form of the attributes, but there is
>>  no indication of the posible asterisk.
>>
>>    The values constitute a list of languages
>>    in preference order (first is most preferred).
>>
>>  "The values" isn't very clear, because the values are in successive
>>  attributes.  You want to say something like "The sequence of values
>>  in
>>  the occurrences of one of these attributes constitutes ...".
>>  However,
>>  see the technical comments above.
>>
>>    When placing an emergency call, and in any other case where the
>>    language cannot be assumed from context, each media stream in an
>>    offer primarily intended for human language communication SHOULD
>>    specify both (or in some cases, one of) the 'humintlang-send' and
>>    'humintlang-recv' attributes.
>>
>>  Probably s/assumed/inferred/.
>>
>>  Could you be more accurate by
>>  s/or in some cases/or for unidirectional streams/?
>>
>>  5.3.  Advisory vs Required
>>
>>    The mechanism for indicating this preference is that, in an offer,
>>  if
>>    the last character of any of the 'humintlang-recv' or 'humintlang-
>>    send' values is an asterisk, this indicates a request to not fail
>>  the
>>    call (similar to SIP Accept-Language syntax).  Either way, the
>>  called
>>    party MAY ignore this, e.g., for the emergency services use case,
>>  a
>>    PSAP will likely not fail the call.
>>
>>  The construction of this paragraph isn't quite complete.  It says
>>  that
>>  if an asterisk is present, a request shouldn't fail, but it doesn't
>>  say that if no asterisk is present, a request should fail if there is
>>  no language match.  And it's the latter condition that makes the
>>  second sentence meaningful.  So I think you want to insert between
>>  the
>>  two sentences one regarding the absence of an asterisk.
>>
>>  5.5.  Examples
>>
>>  Given that the combined audio/video mechanism is the only
>>  irregularity
>>  in this system, there ought to be an example of it.  E.g.,
>>
>>    An example of a supplemental video stream with a spoken language
>>    audio stream:
>>
>>       m=video 51372 RTP/AVP 31 32
>>       a=humintlang-send:en
>>       a=humintlang-recv:en
>>
>>       m=audio 49250 RTP/AVP 20
>>       a=humintlang-send:en
>>       a=humintlang-recv:en
>>
>>  6.  IANA Considerations
>>
>>       humintlang-value =  Language-Tag [ asterisk ]
>>                           ; Language-Tag defined in RFC 5646
>>       asterisk         =  "*"
>>
>>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>  5646/
>>
>>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>  tracks the current version of language tags.
>>
>>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>>
>>    This
>>    results in a more fragile solution since the media modality and
>>    language would be negotiated using SIP, and then the specific
>>  media
>>    formats (which inherently include the modality) would be
>>  negotiated
>>    at a different level (typically SDP, especially in the emergency
>>    calling cases), making it easier to have mismatches (such as where
>>    the media modality negotiated in SIP don't match what was
>>  negotiated
>>    using SDP).
>>
>>  "the media modality and language would be negotiated using SIP" isn't
>>  quite the right way to say it because SIP isn't explicitly
>>  negotiating
>>  the modality.  Better would be
>>
>>    ... the language (and by implication the media modality) would be
>>    negotiated using SIP, and then the specific media (which
>>  inherently
>>    include the modalities and formats) would be negotiated at a
>>    different level ...
>>
>>  [END]
>>
>
>  This email and its attachments are intended for the above named 
> only and may be confidential. If they have come to you in error you 
> must take no action based on them, nor must you copy or show them 
> to anyone; please reply to this email or call +44 207 356 0600 and 
> highlight the error.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
There's nothing wrong with me.  Maybe there's something wrong with
the universe.       --'Dr. Beverly Crusher' in ST:TNG _Remember Me_.


From nobody Tue Feb 21 17:45:09 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 127401294D2; Tue, 21 Feb 2017 17:45:00 -0800 (PST)
X-Quarantine-ID: <1vzWfK52Lwnm>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 1vzWfK52Lwnm; Tue, 21 Feb 2017 17:44:58 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEBF1294E4; Tue, 21 Feb 2017 17:44:58 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Tue, 21 Feb 2017 17:35:44 -0800
Mime-Version: 1.0
Message-Id: <p06240602d4d236a5a2dd@[99.111.97.136]>
In-Reply-To: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com>
X-Mailer: Eudora for Mac OS X
Date: Tue, 21 Feb 2017 17:44:42 -0800
To: "Dale Worley" <worley@ariadne.com>, <gen-art@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: Review of draft-ietf-slim-negotiating-human-language-06
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kqtac4HbSrApwQZtAy82b8PdEJA>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:45:00 -0000

Hi Dale,

Thank you for your review, I appreciate it.  Please see inline.

At 6:32 PM -0800 2/17/17, Dale Worley wrote:

>  Reviewer: Dale Worley
>  Review result: Ready with Nits
>
>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>  Review Team (Gen-ART) reviews all IETF documents being processed
>  by the IESG for the IETF Chair.  Please treat these comments just
>  like any other last call comments.
>
>  For more information, please see the FAQ at
>  <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
>  Document:  draft-ietf-slim-negotiating-human-language-06
>  Reviewer:  Dale R. Worley
>  Review Date:  2017-02-17
>  IETF LC End Date:  2017-02-20
>  IESG Telechat date:  [unknown]
>
>  Summary:
>         This draft is basically ready for publication, but has nits
>         that should be fixed before publication.
>
>  * Technical comments
>
>  A. Call failure
>
>  If a call fails due to no available language match, in what way(s)
>  does it fail?  Section 5.3 says
>
>     If such an offer is received, the receiver MAY
>     reject the media, ignore the language specified, or attempt to
>     interpret the intent
>
>  But I suspect it's also allowed for the UAS to fail the call at the
>  SIP level.  Whether or not that is allowed (or at least envisioned)
>  should be described.  And what response code(s)/warn-code(s) should
>  be
>  used for that?

The text you quote has been deleted.  The draft does not mandate if 
the call should proceed or fail if there is no language match 
possible, although the draft does provide an optional mechanism to 
indicate the caller's preference that the call not fail, and the 
draft does mention that in the emergency services case, the call will 
likely proceed, but that's a matter of policy not protocol.

>
>  B. Audio/Video coordination
>
>     5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>
>     Note that while signed language tags are used with a video stream
>  to
>     indicate sign language, a spoken language tag for a video stream
>  in
>     parallel with an audio stream with the same spoken language tag
>     indicates a request for a supplemental video stream to see the
>     speaker.
>
>  And there's a similar paragraph in 5.4:
>
>>     A spoken language tag for a video stream in conjunction with an
>  audio
>>     stream with the same language might indicate a request for
>>     supplemental video to see the speaker.
>
>  I think this mechanism needs to be described more exactly, and in
>  particular, it should not depend on the UA understanding which
>  language tags are spoken language tags.  It seems to me that a
>  workable rule is that there is an audio stream and a video stream and
>  they specify exactly the same language tag in their respective
>  humintlang attributes.  In that case, it is a request for a spoken
>  language with simultaneous video of the speaker, and those requests
>  should be considered satisfied only if both streams can be
>  established.

The text you quote has been deleted.  A media stream for supplemental 
purposes can be negotiated without a language tag, as normal.

>
>  * The following three items are adjustments to the design which I'd
>  like to know have been considered.
>
>  C. "humintlang" seems long to me
>
>  Given the excessive length of SDP in practice, it seems to me that a
>  shorter attribute name would be desirable.  E.g., "humlang" as was
>  used in some previous versions.  Or is there a coordinated usage with
>  other names in the "hum*lang" pattern?

There is no intent for a coordinated pattern.  The name was chosen 
years ago to avoid potential confusion with the 'lang' attribute.  Is 
it worth reopening the issue to potentially save three characters per 
SDP line with a language?

>
>  D. Use the Accept-Language syntax
>
>  It seems to me that it would better to use the Accept-Language syntax
>  for the attribute values.  This allows (1) specifiying the quality of
>  language experience, allowing clear description of bilingualism, (2)
>  a
>  unified method of specifying whether or not arbitrary languages are
>  acceptable, and (3) abbreviating SDP descriptions.
>
>  In a way, the fact that the current proposal seems to require (but
>  does not directly specify) the coordinated absence/presence of an
>  asterisk on all of the repetitions of humintlang-send or
>  humintlang-recv is a warning that the syntax doesn't represent the
>  semantics as well as it might.

The group considered multiple proposals to permit specifying quality, 
preference, q-values, etc. but decided to keep things simple for this 
draft.  There is no intent to require the use of an asterisk (to 
indicate a preference by the caller to not fail the call).  The 
asterisk is a very mild mechanism with no normative effects.  It 
merely conveys the preference of the caller, and is not binding on 
the answerer.

>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>
>  Note that all examples are bidirectionally symmetric, and the text
>  says that requests and responses SHOULD be bidirectionally symmetric.
>  So it would be a very useful abbreviation to define
>  "humintlang=<value>" to be equivalent to the combination of
>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>
>  Combining proposals C, D, and E, the examples become
>
>        m=audio 49170 RTP/AVP 0
>        a=humlang:en
>
>        m=video 51372 RTP/AVP 31 32
>        a=humlang:ase,*;q=0.1
>
>        m=audio 49250 RTP/AVP 20
>        a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>
>        m=text 45020 RTP/AVP 103 104
>        a=humlang:gr
>
>  which requires about half as many characters as they have now.

A third attribute without the "-send" or "-recv" to indicate 
bidirectionality would reduce the characters in the SDP block, at the 
cost of some added complexity (e.g., what if all three appear).  I 
don't believe this has been discussed in the group.

>  * Editorial comments and nits
>
>  Abstract
>
>     This document describes the need and a solution using new SDP
>  stream
>     attributes.
>
>  I don't think the term "stream attribute" is used in RFC 4566.
>  Instead, it uses "media attribute".

Fixed.

>  1.  Introduction
>
>     caller and callee know each other or there is contextual or out of
>     band information from which the language(s) and media modalities
>  can
>
>  I think this context, it's preferred to hyphenate "out-of-band" to
>  make it clearly be an adjective.

>  OK.


>     This approach has a number of benefits, including that it is
>  generic
>     (applies to all interactive communications negotiated using SDP)
>  and
>     not limited to emergency calls.
>
>  I think s/and not limited to/and is not limited to/ reads more
>  smoothly.

There's no harm in the extra "is" so I'm happy to add it.

>     But it is clearly useful in many other cases.  For
>     example, someone calling a company call center or a Public Safety
>     Answering Point (PSAP) should be able to indicate if one or more
>     specific signed, written, and/or spoken languages are preferred,
>  the
>     callee should be able to indicate its capabilities in this area,
>  and
>     the call proceed using in-common language(s) and media forms.
>
>  I think s/preferred, the callee/preferred; the callee/ because the
>  sentence is the concatenation of two sentences.

I reworded the sentence to flow better:

    For example, it is helpful that someone calling a company call center
    or a Public Safety Answering Point (PSAP) be able to indicate
    preferred signed, written, and/or spoken languages, the callee be
    able to indicate its capabilities in this area, and the call proceed
    using the language(s) and media forms supported by both.

>  Perhaps s/in-common/shared/.

Fixed in the rewording above.

>
>     Including the user's human (natural) language preferences in the
>     session establishment negotiation is independent of the use of a
>     relay service and is transparent to a voice service provider.
>
>  I think it's even broader than "transparent to a voice service
>  provider" -- it's transparent to any serivice provider, assuming that
>  the media are language-neutral.

I changed it to read "voice or other service provider".

>
>     In the case of a call to e.g., an airline, the call could be
>     automatically handled by a Spanish-speaking agent.
>
>  I think s/handled by/routed to/ is the usual usage.

We are trying to be careful in the draft to not imply that it is 
discussing call routing.  I'd rather keep the more generic "handled 
by".

>
>  3.  Desired Semantics
>
>     The desired solution is a media attribute (preferably per
>  direction)
>     that may be used within an offer to indicate the preferred
>  language
>     of each (direction of a) media stream, and within an answer to
>     indicate the accepted language.
>
>  In this one instance, I think you want to use "language(s)" to drive
>  home that that multiple languages can be specified:  "within an offer
>  to indicate the preferred language(s)".
>
>     (Negotiating multiple simultaneous languages within a media stream
>  is
>     out of scope, as the complexity of doing so outweighs the
>     usefulness.)
>
>  You might want to say instead "(Negotiating multiple simultaneous
>  languages within a media stream is out of scope for this document.)"
>  to ensure that nobody decides to argue whether "the complexity of
>  doing so outweighs the usefulness".

I agree and deleted "the complexity of doing so outweighs the usefulness".

>
>  4.  The existing 'lang' attribute
>
>     RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>     similar to what is needed here, but is not sufficiently detailed
>  for
>     use here.
>
>  "for use here" isn't quite right.  Maybe "is not sufficiently
>  specific
>  or flexible to satisfy the requirements".
>
>     In addition, it is not mentioned in [RFC3264]
>
>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>  attribute".

OK, accepted both changes.

>
>  5.  Proposed Solution
>
>  Perhaps /Proposed Solution/Solution/, since once this draft is
>  approved, it becomes the solution.

OK.

>
>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>
>        a=humintlang-send:<language tag>
>        a=humintlang-recv:<language tag>
>
>  This is presented as the generic form of the attributes, but there is
>  no indication of the posible asterisk.

The syntax has been deleted from 5.2 since it's now in 6.

>
>     The values constitute a list of languages
>     in preference order (first is most preferred).
>
>  "The values" isn't very clear, because the values are in successive
>  attributes.  You want to say something like "The sequence of values
>  in
>  the occurrences of one of these attributes constitutes ...".
>  However,
>  see the technical comments above.

The text was reworded to read:

    The values from all
    instances of the attribute constitute a list of languages in
    preference order (first is most preferred).


>
>     When placing an emergency call, and in any other case where the
>     language cannot be assumed from context, each media stream in an
>     offer primarily intended for human language communication SHOULD
>     specify both (or in some cases, one of) the 'humintlang-send' and
>     'humintlang-recv' attributes.
>
>  Probably s/assumed/inferred/.

I agree.

>
>  Could you be more accurate by
>  s/or in some cases/or for unidirectional streams/?

I agree.

>
>  5.3.  Advisory vs Required
>
>     The mechanism for indicating this preference is that, in an offer,
>  if
>     the last character of any of the 'humintlang-recv' or 'humintlang-
>     send' values is an asterisk, this indicates a request to not fail
>  the
>     call (similar to SIP Accept-Language syntax).  Either way, the
>  called
>     party MAY ignore this, e.g., for the emergency services use case,
>  a
>     PSAP will likely not fail the call.
>
>  The construction of this paragraph isn't quite complete.  It says
>  that
>  if an asterisk is present, a request shouldn't fail, but it doesn't
>  say that if no asterisk is present, a request should fail if there is
>  no language match.  And it's the latter condition that makes the
>  second sentence meaningful.  So I think you want to insert between
>  the
>  two sentences one regarding the absence of an asterisk.

I've reworded the section to read:

    A consideration with the ability to negotiate language is if the call
    proceeds or fails if the callee does not support any of the languages
    requested by the caller.  This document does not mandate either
    behavior, although it does provide a way for the caller to indicate a
    preference for the call succeeding when there is no language in
    common.  It is OPTIONAL for the callee to honor this preference.  For
    example, a PSAP is likely to attempt the call even without an
    indicated preference when there is no language in common, while a
    call center might choose to fail the call.

    The mechanism for indicating this preference is that, in an offer, if
    the last character of any of the 'humintlang-recv' or 'humintlang-
    send' values is an asterisk, this indicates a request to not fail the
    call.  The called party MAY ignore the indication, e.g., for the
    emergency services use case, regardless of the absence of an
    asterisk, a PSAP will likely not fail the call; some call centers
    might reject a call even with an asterisk.

>  5.5.  Examples
>
>  Given that the combined audio/video mechanism is the only
>  irregularity
>  in this system, there ought to be an example of it.  E.g.,
>
>     An example of a supplemental video stream with a spoken language
>     audio stream:
>
>        m=video 51372 RTP/AVP 31 32
>        a=humintlang-send:en
>        a=humintlang-recv:en
>
>        m=audio 49250 RTP/AVP 20
>        a=humintlang-send:en
>        a=humintlang-recv:en

If the video stream is supplemental then it doesn't have a language 
(the text that suggested otherwise has been deleted).  But I am 
considering adding more examples.

>
>  6.  IANA Considerations
>
>        humintlang-value =  Language-Tag [ asterisk ]
>                            ; Language-Tag defined in RFC 5646
>        asterisk         =  "*"
>
>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>  5646/
>
>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>  tracks the current version of language tags.

Ok.

>
>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>
>     This
>     results in a more fragile solution since the media modality and
>     language would be negotiated using SIP, and then the specific
>  media
>     formats (which inherently include the modality) would be
>  negotiated
>     at a different level (typically SDP, especially in the emergency
>     calling cases), making it easier to have mismatches (such as where
>     the media modality negotiated in SIP don't match what was
>  negotiated
>     using SDP).
>
>  "the media modality and language would be negotiated using SIP" isn't
>  quite the right way to say it because SIP isn't explicitly
>  negotiating
>  the modality.  Better would be
>
>     ... the language (and by implication the media modality) would be
>     negotiated using SIP, and then the specific media (which
>  inherently
>     include the modalities and formats) would be negotiated at a
>     different level ...

This section has been deleted.

>
>  [END]


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
I make a fortune from criticizing the policy of the government, and
then hand it over to the government in taxes to keep it going.
                                              --George Bernard Shaw


From nobody Tue Feb 21 17:51:49 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C02621294E0; Tue, 21 Feb 2017 17:51:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 z84eaqKlTuiK; Tue, 21 Feb 2017 17:51:42 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 225461294EE; Tue, 21 Feb 2017 17:51:41 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgM5Y-0008Xb-K0 (job@us.ntt.net); Wed, 22 Feb 2017 01:51:40 +0000
Date: Wed, 22 Feb 2017 02:50:41 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Message-ID: <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark>
In-Reply-To: <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
X-Readdle-Message-ID: 54c81141-e4f5-4436-9479-9c02be6c09bb@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="58acee89_109cf92e_1cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LiPutV9V0sv4AXuZszogInR_CSg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 01:51:44 -0000

--58acee89_109cf92e_1cf
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Perhaps you are jesting, but I'll bite.

Those "thousands of interconnections" facilitate the communication between millions of those hosts. Have you considered that not all interconnections are equal? The type of interconnection I am mainly (but not exclusively) referring to is the interconnection between Autonomous Systems to facilitate the exchange of routing information using BGP-4. Autoconfiguration plays no role here, everything is configured explicitly. I'd argue that the use case is hardly comparable with a residential or mobile connection.

Surely you don't mean to say that the Internet's backbone routers are irrelevant because they are the minority from a device count perspective? It's fine if you do, it'll help me put your comments in perspective.

In the last 15 years we've been through all kinds of phases, the observant reader might perceive an intricate tension between two schools of thought blossom, a dance even:

RFC 3513 "only /64 is valid"
RFC 3627 "don't use /127, use /126 if you must"
RFC 4291 "reaffirming: only /64 is valid"
RFC 6164 "a /127 is OK to use too"
RFC 6583 "there are problems with /64"
RFC 7421 "/64 is the best!"
RFC 7608 "every prefix length must be forward-able"
RFC 4291bis-07 "fine, /64 and /127 are valid, but nothing else!"

As pointed out in this thread, real networks use all kinds of prefix lengths. Also, one doesn't renumber everything every time a new document comes out - you stick to things that work for you.

Some vendors in this thread have admitted to strive to make things work with any prefix length, why is there then still a discussion that people must use /64 - when both vendors and users are not always doing so, for good reasons?

I'm confident this discussion will eventually resolve itself and conclude that /64 is not the only valid prefix length, rigid positions rarely are attainable. Water can flow or it can crash.

Kind regards,

Job

On 22 Feb 2017, 01:20 +0100, Lorenzo Colitti <lorenzo@google.com>, wrote:
> On Tue, Feb 21, 2017 at 7:13 PM, Job Snijders <job@ntt.net (mailto:job@ntt.net)> wrote:
> > I've looked at all configured IPv6 addresses on AS 2914 equipment.
> > The above percentages come from grepping through configurations of
> > thousands of interconnections. I'm confident that other networks will
> > show similar prefix length distributions.
>
> "Thousands of interconnections" are not really relevant given that we're well into the hundreds of millions of IPv6 hosts on residential or mobile connections that provide one or more /64s.
--58acee89_109cf92e_1cf
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>Perhaps you are jesting, but I'll bi=
te.<br />
<br />
Those =22thousands of interconnections=22 facilitate the communication be=
tween millions of those hosts. Have you considered that not all interconn=
ections are equal=3F The type of interconnection I am mainly (but not exc=
lusively) referring to is the interconnection between Autonomous Systems =
to facilitate the exchange of routing information using BGP-4. Autoconfig=
uration plays no role here, everything is configured explicitly. I'd argu=
e that the use case is hardly comparable with a residential or mobile con=
nection.<br />
<br />
Surely you don't mean to say that the Internet's backbone routers are irr=
elevant because they are the minority from a device count perspective=3F =
It's fine if you do, it'll help me put your comments in perspective.<br /=
>
<br />
In the last 15 years we've been through all kinds of phases, the observan=
t reader might perceive an intricate tension between two schools of thoug=
ht blossom, a dance even:<br />
<br />
R=46C 3513 =22only /64 is valid=22<br />
R=46C 3627 =22don't use /127, use /126 if you must=22<br />
R=46C 4291 =22reaffirming: only /64 is valid=22<br />
R=46C 6164 =22a /127 is OK to use too=22<br />
R=46C 6583 =22there are problems with /64=22<br />
R=46C 7421 =22/64 is the best=21=22<br />
R=46C 7608 =22every prefix length must be forward-able=22<br />
R=46C 4291bis-07 =22fine, /64 and /127 are valid, but nothing else=21=22<=
br />
<br />
As pointed out in this thread, real networks use all kinds of prefix leng=
ths. Also, one doesn't renumber everything every time a new document come=
s out - you stick to things that work for you.<br />
<br />
Some vendors in this thread have admitted to strive to make things work w=
ith any prefix length, why is there then still a discussion that people m=
ust use /64 - when both vendors and users are not always doing so, for go=
od reasons=3F<br />
<br />
I'm confident this discussion will eventually resolve itself and conclude=
 that /64 is not the only valid prefix length, rigid positions rarely are=
 attainable. Water can flow or it can crash.</div>
<div name=3D=22messageSignatureSection=22><br />
Kind regards,<br />
<br />
Job</div>
<div name=3D=22messageReplySection=22><br />
On 22 =46eb 2017, 01:20 +0100, Lorenzo Colitti &lt;lorenzo=40google.com&g=
t;, wrote:<br />
<blockquote type=3D=22cite=22>
<div dir=3D=22ltr=22>
<div class=3D=22gmail=5Fextra=22>
<div class=3D=22gmail=5Fquote=22>On Tue, =46eb 21, 2017 at 7:13 PM, Job S=
nijders <span dir=3D=22ltr=22>&lt;<a href=3D=22mailto:job=40ntt.net=22 ta=
rget=3D=22=5Fblank=22>job=40ntt.net</a>&gt;</span> wrote:<br />
<blockquote class=3D=22gmail=5Fquote=22 style=3D=22margin:0 0 0 .8ex;bord=
er-left:1px =23ccc solid;padding-left:1ex=22>I've looked at all configure=
d IPv6 addresses on AS 2914 equipment.<br />
The above percentages come from grepping through configurations of<br />
thousands of interconnections. I'm confident that other networks will<br =
/>
show similar prefix length distributions.<br /></blockquote>
<div><br /></div>
<div>=22Thousands of interconnections=22 are not really relevant given th=
at we're well into the hundreds of millions of IPv6 hosts on residential =
or mobile connections that provide one or more /64s.</div>
</div>
</div>
</div>
</blockquote>
</div>
</body>
</html>

--58acee89_109cf92e_1cf--


From nobody Tue Feb 21 19:00:47 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3147B129518 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 19:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f9iPgthxsGtw for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 19:00:43 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c: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 24541129530 for <ietf@ietf.org>; Tue, 21 Feb 2017 19:00:41 -0800 (PST)
Received: by mail-vk0-x22c.google.com with SMTP id k127so90867202vke.0 for <ietf@ietf.org>; Tue, 21 Feb 2017 19:00:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vaJdM2IoGtbKS1URHOZYaWinu9P3MfvfUFXo5gvu4IE=; b=EgasqFjiVkJgGH+EOLh70Rav44yhJvwNV/vjQFgdRXNdRhWV8CkV7ZlZuoqjDPyrey CYRtdK18dPSQMT5gVXdkT8Gc+Hg5aj5mPump9y+LhTEx8A30FdsBPIJOkD9Q0lcV5f/O ZiWWZZwiABBYHV7trcT+qJk7nAbTPuawovEsl1X8WNzt4CCTAy3osxl60hurGHluT9ac or0lyCZX1Ris5jc2E02IBJxgxx36wKnkI8XwHrY3WxrbRR6FNRHGQrTPQIETn1WfKQM5 j6UWJbSQwfNf/yDYRMkDrLly31cF8SpVpKoUsYwzMTtEhIA9swMDSx9MXD7cgHsd3Nly jSmg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vaJdM2IoGtbKS1URHOZYaWinu9P3MfvfUFXo5gvu4IE=; b=WvMXWOzNLYzbMvUdjU6llPJavbmBFZDiW+D/TZ/drnVKwqliqsRbgbv2CbGs/w2pHd prbpK521RdUALZugYWEX1gbmTlElFwk0YBNTx7rtdWEB0VSOtIdBoMMpFtDdDpxkGakR FBPPPH2Gql9DlxUfVCYJHFDYgoamZz+WJvABJOfTIJjQVj8hivT0Zm3YKAyS4KIo9fCc tCis4dZmqHaORYKe16Dnbdw3QSnnmocyd2C6C0YraPmnToIzDeS8rZS31n9y7dhxUF4H j6IC4gSqmifh9AECjT6SdChalZAFaPzhNFv2AfahgdFCS6bb4q/UvkjywaQrGmkHN/+0 /Hdg==
X-Gm-Message-State: AMke39l2eMDOzu7SxrYzzz/6Gz77apZC/mpqrCkcWKRqGEjK9noRPiLsJRvQECTqb3OSUL6GE3yYUlibH6dPPbgn
X-Received: by 10.31.170.15 with SMTP id t15mr12832578vke.6.1487732439988; Tue, 21 Feb 2017 19:00:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Tue, 21 Feb 2017 19:00:18 -0800 (PST)
In-Reply-To: <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 12:00:18 +0900
Message-ID: <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=001a114322509ba963054915b3a9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vsoSpTF3Buj6WY3Wfh5-P66M7AI>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 03:00:44 -0000

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

On Wed, Feb 22, 2017 at 10:50 AM, Job Snijders <job@ntt.net> wrote:

> Those "thousands of interconnections" facilitate the communication between
> millions of those hosts.
>

But the configuration cost and management overhead is not proportional to
the hosts that are served by those interconnections, it is proportional to
the number of interconnections. A 10x100G peering interconnection that
serves X million hosts is one interface that has to be managed.

Have you considered that not all interconnections are equal? The type of
> interconnection I am mainly (but not exclusively) referring to is the
> interconnection between Autonomous Systems to facilitate the exchange of
> routing information using BGP-4. Autoconfiguration plays no role here,
> everything is configured explicitly. I'd argue that the use case is hardly
> comparable with a residential or mobile connection.
>

Those use cases are very well served by /127 for PNIs and /64s for Internet
exchanges. What's left?

As pointed out in this thread, real networks use all kinds of prefix
> lengths. Also, one doesn't renumber everything every time a new document
> comes out - you stick to things that work for you.
>

As discussed above, most links use /64.

Some vendors in this thread have admitted to strive to make things work
> with any prefix length, why is there then still a discussion that people
> must use /64 - when both vendors and users are not always doing so, for
> good reasons?
>

You're forgetting about host operating system developers and host users,
both of which benefit substantially to having a subnet size that is always
the same and never runs out of addresses.

I'm confident this discussion will eventually resolve itself and conclude
> that /64 is not the only valid prefix length, rigid positions rarely are
> attainable. Water can flow or it can crash.
>

Even if you're right, the place to have that discussion is not on this
document.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Feb 22, 2017 at 10:50 AM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D=
"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">



<div>
<div name=3D"messageBodySection">Those &quot;thousands of interconnections&=
quot; facilitate the communication between millions of those hosts.</div></=
div></blockquote><div><br></div><div>But the configuration cost and managem=
ent overhead is not proportional to the hosts that are served by those inte=
rconnections, it is proportional to the number of interconnections. A 10x10=
0G peering interconnection that serves X million hosts is one interface tha=
t has to be managed.</div><div><br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v><div name=3D"messageBodySection">Have you considered that not all interco=
nnections are equal? The type of interconnection I am mainly (but not exclu=
sively) referring to is the interconnection between Autonomous Systems to f=
acilitate the exchange of routing information using BGP-4. Autoconfiguratio=
n plays no role here, everything is configured explicitly. I&#39;d argue th=
at the use case is hardly comparable with a residential or mobile connectio=
n.<br></div></div></blockquote><div><br></div><div>Those use cases are very=
 well served by /127 for PNIs and /64s for Internet exchanges. What&#39;s l=
eft?</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div name=3D"m=
essageBodySection">
As pointed out in this thread, real networks use all kinds of prefix length=
s. Also, one doesn&#39;t renumber everything every time a new document come=
s out - you stick to things that work for you.<br></div></div></blockquote>=
<div><br></div><div>As discussed above, most links use /64.</div><div><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div><div name=3D"messageBodySection">S=
ome vendors in this thread have admitted to strive to make things work with=
 any prefix length, why is there then still a discussion that people must u=
se /64 - when both vendors and users are not always doing so, for good reas=
ons?<br></div></div></blockquote><div><br></div><div>You&#39;re forgetting =
about host operating system developers and host users, both of which benefi=
t substantially to having a subnet size that is always the same and never r=
uns out of addresses.</div><div><br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv><div name=3D"messageBodySection">I&#39;m confident this discussion will =
eventually resolve itself and conclude that /64 is not the only valid prefi=
x length, rigid positions rarely are attainable. Water can flow or it can c=
rash.</div></div></blockquote><div><br></div><div>Even if you&#39;re right,=
 the place to have that discussion is not on this document.</div></div></di=
v></div>

--001a114322509ba963054915b3a9--


From nobody Tue Feb 21 19:12:28 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A6F129518; Tue, 21 Feb 2017 19:12:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R8WsTus0N72j; Tue, 21 Feb 2017 19:12:20 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::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 93664129411; Tue, 21 Feb 2017 19:12:20 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id x71so74747790qkb.3; Tue, 21 Feb 2017 19:12:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+LFQzzrxrOYXLGqHhvrxFBNQ2Z2FA4ixhw5A6Nw1sXM=; b=f8O9oT5opSjKtQD9SC7Ni+wFQdXtWx/+AjeeZ+wvdVhKMYXGZ6u2B9zOI5qOQeaBnp YkcUYAFAySTOnRu06DGHYwZ0ptZeXxyyL//IgpObAUG/ElAZUx2mNaMGnERz/4mwcD0l UWeEoGG0/5czKlWGyKEuX9Hp0MNymMVv3ZCG/Uhafpz+bnKcb7o+DGZVE10+nnlvfi63 HMYsuT48KTeYolZTJ669IBIZgn6VCiE4bM351A869FGRQkWjIkytCUH34FRJDbLZ5Y0F cvrZNO4wvs2zg7b7aaLanHxNR9x6Fo4J46gVEUQaSZaHJepaIvuaipoa6uDBIpQ0103Y Y92g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+LFQzzrxrOYXLGqHhvrxFBNQ2Z2FA4ixhw5A6Nw1sXM=; b=PUd55iwNa1AA7r6HfGB7uDH0+kQem6Sx6iWq5mU2iDLl5rViTNl9kzfc3mRz7+tgwM +P976YF/2oT+dWPkBmSSswak1BtpPD2vpbjlWeIydslxRZp60hvJslXkT1pqgzzuj5NV dEHCVJ5DjC6Ny0TTZZOZFZN8dRjWmM+Vv8Hn62yhH9CNsoO42Iar4ePYceDGxjOQywcQ YceqL0szU/gToJAbnA2TQ2nfxgs69PoAl8n4JV1dqzLPNIo57ycDVOVGFHicTYDBPC/4 nPGiCYhv4xFnRlwbmTpVOgIE5GSBZEyHVNcQf6ya0fm3h3zM+PlCb07VhfY6zG+ohGuM F2zA==
X-Gm-Message-State: AMke39nA9ztlBM/X++LGZ61deFHf8/KgJ8weZ0d7g6/tWNLrxjjfUfWKIzCtpBHMQ1oJKiRMQj1a6dUG1tjiQw==
X-Received: by 10.55.94.198 with SMTP id s189mr26573730qkb.236.1487733139675;  Tue, 21 Feb 2017 19:12:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.91.71 with HTTP; Tue, 21 Feb 2017 19:12:18 -0800 (PST)
In-Reply-To: <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 21 Feb 2017 22:12:18 -0500
Message-ID: <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114e2e204fa48a054915ddd3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eQVYEJGlfvuGcMuK7G_ddBn6OA4>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 03:12:22 -0000

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

On Tue, Feb 21, 2017 at 10:00 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Wed, Feb 22, 2017 at 10:50 AM, Job Snijders <job@ntt.net> wrote:
>
>> Those "thousands of interconnections" facilitate the communication
>> between millions of those hosts.
>>
>
> But the configuration cost and management overhead is not proportional to
> the hosts that are served by those interconnections, it is proportional to
> the number of interconnections. A 10x100G peering interconnection that
> serves X million hosts is one interface that has to be managed.
>
>
isn't the dicsussion here really:
  "If you want to use /64 go ahead, if you want to use /121 go for it, if
you want to use SLAAC you'll get a /64 and like it"

which fits both the interconnect problem space and the home-consumer
problem space. The change outlined ~6 messages back seemed to be a more
officious way to say what my quoted bit above says, and seemed just fine
for both use cases.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 21, 2017 at 10:00 PM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D"">On We=
d, Feb 22, 2017 at 10:50 AM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"=
mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div>
<div name=3D"messageBodySection">Those &quot;thousands of interconnections&=
quot; facilitate the communication between millions of those hosts.</div></=
div></blockquote><div><br></div></span><div>But the configuration cost and =
management overhead is not proportional to the hosts that are served by tho=
se interconnections, it is proportional to the number of interconnections. =
A 10x100G peering interconnection that serves X million hosts is one interf=
ace that has to be managed.</div><span class=3D""><div><br></div></span></d=
iv></div></div></blockquote><div><br></div><div>isn&#39;t the dicsussion he=
re really:<br>=C2=A0 &quot;If you want to use /64 go ahead, if you want to =
use /121 go for it, if you want to use SLAAC you&#39;ll get a /64 and like =
it&quot;</div><div><br></div><div>which fits both the interconnect problem =
space and the home-consumer problem space. The change outlined ~6 messages =
back seemed to be a more officious way to say what my quoted bit above says=
, and seemed just fine for both use cases.=C2=A0</div></div></div></div>

--001a114e2e204fa48a054915ddd3--


From nobody Tue Feb 21 19:52:20 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C420129578 for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 19:52:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LWq9YjKJeQhR for <ietf@ietfa.amsl.com>; Tue, 21 Feb 2017 19:52:15 -0800 (PST)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 EC57A12957C for <ietf@ietf.org>; Tue, 21 Feb 2017 19:52:13 -0800 (PST)
Received: by mail-vk0-x235.google.com with SMTP id r136so91438340vke.1 for <ietf@ietf.org>; Tue, 21 Feb 2017 19:52:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=M8LFO7WLJj0UD0JgIDhcDsBpxRM6Ta9NrS+WItsPg+I=; b=mEutR/Hhr1e3Ts/9uPW1k09cLS7f2cgHO70RIJ/AGL1BlIuabb0/3RPrKZK6BLv4ld c6AxiiG/A2H+fbduTKZxKoDmxcPw8C3MlAPzNEDdjxdXy4Upjhr0pmDcgHuJKkCx4ZcV uke7t7Rhx7WTCwbg0WmJyQfjNJ38RVGjg7UOSLVk8fnT4JwIu9157u1zrHWSLhw5LmFx +n5/jecKX5ZPYWUVQjZ9V0hE+Lw5fbwdkr7o3NZ5/Qr3cyhzxSyQiN8LY2tzcv38srlx PE46lPd/k/OJS/XLIq5SHy5SSQ+F+6lY7QBxyMfLb0CCt/mqslmNpqgNBXzipUwZ+rL5 XgYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=M8LFO7WLJj0UD0JgIDhcDsBpxRM6Ta9NrS+WItsPg+I=; b=aYW0DmXP4fXYll5YIaPhUFNpfRlHbt0U4pums5SakdAHkZH0DFZZ4QUkDGk0CmGOZU Pmfs38U8JLFSijFkElDOs5VhVISlkS5nKmG6uqvJhZfH6Fdaxph6hRJ5tNyRfhyLOMso 8UVlH5TXDI1kWKxJlXvkmoqZOn9VKuHxzDMXu4jMNuSUbfmftlLgzXyS91tgtZRazwWf R8uJmKHqsvkykco2ak7kL7ewR3uUdXvJN7fhvOaVla2hjDJ01SrLi4FriWBjqFUBSL6w kDZtBIgQMEnvEhfJTHVU6t9PnQvWM2rMoU047P46Vrk3yWgASwv+gbuYkluQne7QJEtR samg==
X-Gm-Message-State: AMke39kN5xykDE4f7uyCFvEDbcYSJlioYSGkmv+g16MPl3J41UIsi36KfUbkBMQBm1RFl9TI4F7gZSm5wgTpwQmh
X-Received: by 10.31.192.204 with SMTP id q195mr14921289vkf.155.1487735532777;  Tue, 21 Feb 2017 19:52:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Tue, 21 Feb 2017 19:51:51 -0800 (PST)
In-Reply-To: <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 12:51:51 +0900
Message-ID: <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: multipart/alternative; boundary=001a114388ccf3d54f0549166b69
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UTTsFZN50u8_CjsQIkkpa6FnNf4>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 03:52:16 -0000

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

On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <
christopher.morrow@gmail.com> wrote:

> But the configuration cost and management overhead is not proportional to
>> the hosts that are served by those interconnections, it is proportional to
>> the number of interconnections. A 10x100G peering interconnection that
>> serves X million hosts is one interface that has to be managed.
>>
>
> isn't the dicsussion here really:
>   "If you want to use /64 go ahead, if you want to use /121 go for it, if
> you want to use SLAAC you'll get a /64 and like it"
>

Not sure. I for one wouldn't agree with that position, because I don't see
that /121 has enough advantages over /127 and /64 - and few enough
downsides for general-purpose hosts - to make it a good idea in general.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:christopher.morrow@gmail.com" target=3D"_blank">christopher.m=
orrow@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span c=
lass=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_extra"><div class=3D"gmail_quote"><div>But the configuration cost and ma=
nagement overhead is not proportional to the hosts that are served by those=
 interconnections, it is proportional to the number of interconnections. A =
10x100G peering interconnection that serves X million hosts is one interfac=
e that has to be managed.</div></div></div></div></blockquote><div><br></di=
v></span><div>isn&#39;t the dicsussion here really:<br>=C2=A0 &quot;If you =
want to use /64 go ahead, if you want to use /121 go for it, if you want to=
 use SLAAC you&#39;ll get a /64 and like it&quot;</div></div></div></div></=
blockquote><div><br></div><div>Not sure. I for one wouldn&#39;t agree with =
that position, because I don&#39;t see that /121 has enough advantages over=
 /127 and /64 - and few enough downsides for general-purpose hosts - to mak=
e it a good idea in general.</div></div></div></div>

--001a114388ccf3d54f0549166b69--


From nobody Tue Feb 21 20:44:22 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 307281295AE; Tue, 21 Feb 2017 20:44:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ctpqUv0cmkjE; Tue, 21 Feb 2017 20:44:20 -0800 (PST)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::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 F28A112959E; Tue, 21 Feb 2017 20:44:19 -0800 (PST)
Received: by mail-qk0-x22d.google.com with SMTP id x71so230048qkb.3; Tue, 21 Feb 2017 20:44:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=3T+Ck6hb1vRglALBng4l2dQMovAuxR5M7Zzvgucm7pM=; b=YppFuGWNqsmHLkoasxhhozK3WDOMmdJBUD9NmV0GMQfohedHpDs40gxvtxMZCB61TW 4vkW7CboIH0ES9Po4gfIR/0hkW0fJFV/KYh5Os+naZYWYHVbPtqcYFHXolvWD6txHxd4 wkNrtHqajmvCyYXEaD6vUxqJTrl6XrOVbhI0xCT0xWQDczo8eBy27J0kgRdHcO25QWyr j2LoIleKswD5zZy8juR3G1UPVIA60qqIBC6kihqGSYIK2hflsdoCz1BAdKgqcc8vv1tu C78iI70CJ0yvV9OYT1t2BKWrxmIkzQMPRyqPGfJWKM+GQu0Ta5vaZt1kOKwaeQgkWbzk kh1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=3T+Ck6hb1vRglALBng4l2dQMovAuxR5M7Zzvgucm7pM=; b=LZBWi6ER5+zBkztwPYKTEJd0Z1kVnR8b24htE408mCJKv5UVsnzvYP3mj/rW1RNbDu mVTSbpmt9ay5pTAa50LA8z9nFZNBFNU1qJMUc/KsQoQSnct+AihcM6QhDGdHo0IA3tw+ Xpnx1rQ7A65OL62anwb9QhXXBgdzOYvBwvBaq+8pRF9o9QXMyAemimBSQAUOcna9IvNi ihenHHn6GXg/vYzg9YzBws746gdi7ycTYkqu8T1BTCfPjsZfX0x04J0T3De5ddURK5EZ bVbm3APXLKEZBY6wlLb8nk2a6yc0vBw+OEQjrfk69gYhDSBwcTJbf/UV/IWCej1uSIL+ cEFw==
X-Gm-Message-State: AMke39k9Iak/f6fdtmpp3KClm0uUBwYMcsKmUP2bhFD5dXRLrTZKDTe1zvWK14xP0yYfiz2578qUvrrkQJrESQ==
X-Received: by 10.55.200.217 with SMTP id t86mr29841947qkl.5.1487738659141; Tue, 21 Feb 2017 20:44:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.91.71 with HTTP; Tue, 21 Feb 2017 20:44:18 -0800 (PST)
In-Reply-To: <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Tue, 21 Feb 2017 23:44:18 -0500
Message-ID: <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a113aa8e84c066405491726d7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YC_VaZjSPt2EGaSPEtqGRYUNbjQ>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 04:44:21 -0000

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

On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <
> christopher.morrow@gmail.com> wrote:
>
>> But the configuration cost and management overhead is not proportional to
>>> the hosts that are served by those interconnections, it is proportional to
>>> the number of interconnections. A 10x100G peering interconnection that
>>> serves X million hosts is one interface that has to be managed.
>>>
>>
>> isn't the dicsussion here really:
>>   "If you want to use /64 go ahead, if you want to use /121 go for it, if
>> you want to use SLAAC you'll get a /64 and like it"
>>
>
> Not sure. I for one wouldn't agree with that position, because I don't see
> that /121 has enough advantages over /127 and /64 - and few enough
> downsides for general-purpose hosts - to make it a good idea in general.
>

I don't think /121 is anymore special than /127... or /64. My point was we
don't care what prefix people use, generally, that there are cases where a
/64 is required and that's fine, there are cases where /64 isn't and people
can do what they want there.  It's simple enough to do SLAAC/64 on lans and
other places.

Requiring /64 or /127 and nothing else means when you do have to do a /120
or something else you MAY end up fighting vendor problems because they made
assumptions about: "only ever 64 or 127".

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D"">On We=
d, Feb 22, 2017 at 12:12 PM, Christopher Morrow <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:christopher.morrow@gmail.com" target=3D"_blank">christopher.mo=
rrow@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div=
 dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote"><div>But the configuration cost and management ove=
rhead is not proportional to the hosts that are served by those interconnec=
tions, it is proportional to the number of interconnections. A 10x100G peer=
ing interconnection that serves X million hosts is one interface that has t=
o be managed.</div></div></div></div></blockquote><div><br></div></span><di=
v>isn&#39;t the dicsussion here really:<br>=C2=A0 &quot;If you want to use =
/64 go ahead, if you want to use /121 go for it, if you want to use SLAAC y=
ou&#39;ll get a /64 and like it&quot;</div></div></div></div></blockquote><=
div><br></div></span><div>Not sure. I for one wouldn&#39;t agree with that =
position, because I don&#39;t see that /121 has enough advantages over /127=
 and /64 - and few enough downsides for general-purpose hosts - to make it =
a good idea in general.</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">I don&#39;t think /=
121 is anymore special than /127... or /64. My point was we don&#39;t care =
what prefix people use, generally, that there are cases where a /64 is requ=
ired and that&#39;s fine, there are cases where /64 isn&#39;t and people ca=
n do what they want there.=C2=A0 It&#39;s simple enough to do SLAAC/64 on l=
ans and other places.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Requiring /64 or /127 and nothing else means when you do h=
ave to do a /120 or something else you MAY end up fighting vendor problems =
because they made assumptions about: &quot;only ever 64 or 127&quot;.</div>=
</div>

--001a113aa8e84c066405491726d7--


From nobody Wed Feb 22 00:09:02 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B89F61294ED; Wed, 22 Feb 2017 00:09:00 -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 autolearn_force=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 79aUxVaL_dGY; Wed, 22 Feb 2017 00:08:59 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 B8366129457; Wed, 22 Feb 2017 00:08:59 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cgRyq-0000sV-9z; Wed, 22 Feb 2017 08:08:56 +0000
Date: Wed, 22 Feb 2017 15:08:51 +0700
Message-ID: <m21suqwsto.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v8vM7luwsU2jXftxekuR1m4hV7I>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 08:09:01 -0000

> isn't the dicsussion here really:
>   "If you want to use /64 go ahead, if you want to use /121 go for it,
> if you want to use SLAAC you'll get a /64 and like it"

with which i do not have a probem.

and i even use slaac at home where things such as address control,
reverse dns, etc. do not matter and are not worth the effort.

randy


From nobody Wed Feb 22 01:09:21 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C362129457; Wed, 22 Feb 2017 01:09:15 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 7xibN_aVW40m; Wed, 22 Feb 2017 01:09:13 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 F2C231293DF; Wed, 22 Feb 2017 01:09:12 -0800 (PST)
Received: from unescapeable.local (2.204-14-84.ripe.coltfrance.com [84.14.204.2]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v1M997Y9022800 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 22 Feb 2017 03:09:09 -0600 (CST) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 2.204-14-84.ripe.coltfrance.com [84.14.204.2] claimed to be unescapeable.local
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Greg Mirsky <gregimirsky@gmail.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com> <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
Date: Wed, 22 Feb 2017 10:09:01 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------4BA9FE9488D2E8686F0044F9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RXmYX_YtSQhjYS28P40HlMe5jMo>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 09:09:15 -0000

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

I would simply delete "To ensure precise accuracy in time determination" 
and start the sentence at "These actions"

RjS


On 2/15/17 9:40 PM, Greg Mirsky wrote:
> Hi Robert,
> safe travel and here's another version for your consideration. The 
> point I'm trying to convey is that the jitter is real but must be 
> accounted not as part of propagation delay but as residence time. Hope 
> I'm getting close.
>     Each RTM-capable
>     node on the explicit path receives an RTM packet and records the time
>     at which it receives that packet at its ingress interface as well as
>     the time at which it transmits that packet from its egress interface.
>     To ensure precise accuracy in time determination these actions should
>     be done as close to the physical layer as possible at the same point
>     of packet processing striving to avoid introducing the appearance of
>     jitter in propogation delay whereas it should be accounted as
>     residence time.
> Regards,
> Greg
>
> On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com 
> <mailto:rjsparks@nostrum.com>> wrote:
>
>
>
>     On 2/15/17 11:20 AM, Greg Mirsky wrote:
>>     Hi Robert,
>>     yes, you've absolutely correct in your example. The importance of
>>     RTM is to exclude and quantify, as much as possible, jitter from
>>     propagation delay. I've updated the wording to reflect that.
>>     Below is new text I propose, please let me know if it makes it
>>     clearer.
>>         Each RTM-capable
>>         node on the explicit path receives an RTM packet and records the time
>>         at which it receives that packet at its ingress interface as well as
>>         the time at which it transmits that packet from its egress interface.
>>         These actions should be done as close to the physical layer as
>>         possible at the same point of packet processing striving to avoid
>>         introduction of jitter in propogation delay to ensure precise
>>         accuracy in time determination.
>     perhaps change "avoid introduction of jitter" to "avoid
>     introducing the appearance of jitter that's not really there"?
>
>     (I'm about to board a plane, so further responses will be very
>     delayed).
>>     Regards,
>>     Greg
>>
>>     On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks
>>     <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>
>>
>>
>>         On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>>         Hi Robert,
>>>         Section 5 Data Plane Theory of Operation has the following
>>>         recommendation on reading time value at ingress and egress:
>>>             Each RTM-capable
>>>             node on the explicit path receives an RTM packet and records the time
>>>             at which it receives that packet at its ingress interface as well as
>>>             the time at which it transmits that packet from its egress interface;
>>>             this should be done as close to the physical layer as possible to
>>>             ensure precise accuracy in time determination.
>>>         Do you find the text sufficient in providing guidance to an implementer of RTM?
>>         Well, no - that was point in the text from my review of -12
>>         that caused me to make comment in the first place.
>>
>>         What does "precise accuracy" even _MEAN_? You're waving your
>>         hands with words that don't help the reader guess what you
>>         mean at the moment. The subsequent email exchange said the
>>         important part was that you measure _precisely_ (in that the
>>         measurements are always taken the same way), but accuracy
>>         isn't that important (you've (and here by "you" I mean the
>>         set of people that have responded to the review") told me
>>         it's not important whether the reading is taken at the
>>         beginning of the bit-stream, the end, or several 1000
>>         nanoseconds after the last bit came off the physical media as
>>         long as it's done the same way for each packet). The fact
>>         that you're carrying a measurement that can talk about times
>>         smaller than the interarrival time for individual bits for
>>         some real world line speeds says that different
>>         implementations taking the measurement different ways is
>>         going to result in different residence time measurements,
>>         even if the residence time was really identical. You've told
>>         me that's not important to the protocol using the measurement
>>         as long as the an individual implementation doesn't introduce
>>         something that will look to the using protocol like jitter
>>         that's not really there.
>>
>>         The text does not say that to an implementer right now.
>>
>>         To restate that long paragraph with maybe a longer one, 
>>         assume a simplified world where everything is perfectly
>>         constant. Packets are all flowing at the same size and same
>>         rate. For reference, I assert that the time between the first
>>         bit of a packet entering the system taking the measurement
>>         and the first bit of that packet leaving the system is
>>         exactly T (every time). You are telling me that if the system
>>         returns cT for some constant T other than 1 (and not
>>         necessarily  close to 1), everything is fine. You're also
>>         telling me that if you replace the system with another that
>>         preserves T, but measures differently so that it returns c'T
>>         where c' != c, everything is fine. The important part to you
>>         is that c and c' don't change for their respective systems.
>>         (That surprises me, I can see how the way the clocks are
>>         going to use this will do the right thing, but I can't help
>>         but think someone later will look at the difference between
>>         the two systems and say something is wrong with one of them).
>>         What you've told me is not fine is that if you drop i a third
>>         system that also preserves T but reports aT where a _varies_
>>         over some range.
>>
>>         Have I heard you correctly?
>>>         Regards,
>>>         Greg
>>>
>>>         On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks
>>>         <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
>>>
>>>             Reviewer: Robert Sparks
>>>             Review result: Ready
>>>
>>>             I am the assigned Gen-ART reviewer for this draft. The
>>>             General Area
>>>             Review Team (Gen-ART) reviews all IETF documents being
>>>             processed
>>>             by the IESG for the IETF Chair. Please wait for
>>>             direction from your
>>>             document shepherd or AD before posting a new version of
>>>             the draft.
>>>
>>>             For more information, please see the FAQ at
>>>
>>>             <https://trac.ietf.org/trac/gen/wiki/GenArtfaq
>>>             <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>>>
>>>             Document: draft-ietf-mpls-residence-time-13
>>>             Reviewer: Robert Sparks
>>>             Review Date: 2017-02-13
>>>             IETF LC End Date: 2017-01-17
>>>             IESG Telechat date: 2017-03-02
>>>
>>>             Summary: Ready for publication as PS
>>>
>>>             Thanks for addressing my comments.
>>>             (I still think some discussion about taking arrival and
>>>             departure time
>>>             measurements would be helpful, even if it only said "do it
>>>             consistently so you don't indicate jitter that's not
>>>             really there".)
>>>
>>>
>>
>>
>
>


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>I would simply delete "To ensure precise accuracy in time
      determination" and start the sentence at "These actions"</p>
    <p>RjS<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 2/15/17 9:40 PM, Greg Mirsky wrote:<br>
    </div>
    <blockquote
cite="mid:CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Robert,
        <div>safe travel and here's another version for your
          consideration. The point I'm trying to convey is that the
          jitter is real but must be accounted not as part of
          propagation delay but as residence time. Hope I'm getting
          close.</div>
        <div>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
          <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,
          Robert Sparks <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:rjsparks@nostrum.com" target="_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"><span class="">
                <p><br>
                </p>
                <br>
                <div class="m_2800513769154960288moz-cite-prefix">On
                  2/15/17 11:20 AM, Greg Mirsky wrote:<br>
                </div>
              </span>
              <blockquote type="cite">
                <div dir="ltr">Hi Robert, <span class="">
                    <div>yes, you've absolutely correct in your example.
                      The importance of RTM is to exclude and quantify,
                      as much as possible, jitter from propagation
                      delay. I've updated the wording to reflect that.
                      Below is new text I propose, please let me know if
                      it makes it clearer.</div>
                    <div>
                      <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
                    </div>
                  </span></div>
              </blockquote>
              perhaps change "avoid introduction of jitter" to "avoid
              introducing the appearance of jitter that's not really
              there"?<br>
              <br>
              (I'm about to board a plane, so further responses will be
              very delayed). <br>
              <div>
                <div class="h5">
                  <blockquote type="cite">
                    <div dir="ltr">
                      <div>
                        <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Regards,</pre>
                        <pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap">Greg</pre>
                      </div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">On Wed, Feb 15, 2017 at
                        7:43 AM, Robert Sparks <span dir="ltr">&lt;<a
                            moz-do-not-send="true"
                            href="mailto:rjsparks@nostrum.com"
                            target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                        wrote:<br>
                        <blockquote class="gmail_quote" style="margin:0
                          0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex">
                          <div bgcolor="#FFFFFF" text="#000000"><span>
                              <p><br>
                              </p>
                              <br>
                              <div
                                class="m_2800513769154960288m_3072934530585377958moz-cite-prefix">On
                                2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                              </div>
                              <blockquote type="cite">
                                <div dir="ltr">Hi Robert,
                                  <div>Section 5 Data Plane Theory of
                                    Operation has the following
                                    recommendation on reading time value
                                    at ingress and egress:</div>
                                  <div>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the text sufficient in providing guidance to an implementer of RTM?</pre>
                                  </div>
                                </div>
                              </blockquote>
                            </span> Well, no - that was point in the
                            text from my review of -12 that caused me to
                            make comment in the first place.<br>
                            <br>
                            What does "precise accuracy" even _MEAN_?
                            You're waving your hands with words that
                            don't help the reader guess what you mean at
                            the moment. The subsequent email exchange
                            said the important part was that you measure
                            _precisely_ (in that the measurements are
                            always taken the same way), but accuracy
                            isn't that important (you've (and here by
                            "you" I mean the set of people that have
                            responded to the review") told me it's not
                            important whether the reading is taken at
                            the beginning of the bit-stream, the end, or
                            several 1000 nanoseconds after the last bit
                            came off the physical media as long as it's
                            done the same way for each packet). The fact
                            that you're carrying a measurement that can
                            talk about times smaller than the
                            interarrival time for individual bits for
                            some real world line speeds says that
                            different implementations taking the
                            measurement different ways is going to
                            result in different residence time
                            measurements, even if the residence time was
                            really identical. You've told me that's not
                            important to the protocol using the
                            measurement as long as the an individual
                            implementation doesn't introduce something
                            that will look to the using protocol like
                            jitter that's not really there.<br>
                            <br>
                            The text does not say that to an implementer
                            right now.<br>
                            <br>
                            To restate that long paragraph with maybe a
                            longer one,  assume a simplified world where
                            everything is perfectly constant. Packets
                            are all flowing at the same size and same
                            rate. For reference, I assert that the time
                            between the first bit of a packet entering
                            the system taking the measurement and the
                            first bit of that packet leaving the system
                            is exactly T (every time). You are telling
                            me that if the system returns cT for some
                            constant T other than 1 (and not
                            necessarily  close to 1), everything is
                            fine. You're also telling me that if you
                            replace the system with another that
                            preserves T, but measures differently so
                            that it returns c'T where c' != c,
                            everything is fine. The important part to
                            you is that c and c' don't change for their
                            respective systems. (That surprises me, I
                            can see how the way the clocks are going to
                            use this will do the right thing, but I
                            can't help but think someone later will look
                            at the difference between the two systems
                            and say something is wrong with one of
                            them). What you've told me is not fine is
                            that if you drop i a third system that also
                            preserves T but reports aT where a _varies_
                            over some range.<br>
                            <br>
                            Have I heard you correctly?<span><br>
                              <blockquote type="cite">
                                <div dir="ltr">
                                  <div>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                                    <pre class="m_2800513769154960288m_3072934530585377958gmail-newpage" style="font-size:13.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                                  </div>
                                </div>
                                <div class="gmail_extra"><br>
                                  <div class="gmail_quote">On Mon, Feb
                                    13, 2017 at 1:51 PM, Robert Sparks <span
                                      dir="ltr">&lt;<a
                                        moz-do-not-send="true"
                                        href="mailto:rjsparks@nostrum.com"
                                        target="_blank">rjsparks@nostrum.com</a>&gt;</span>
                                    wrote:<br>
                                    <blockquote class="gmail_quote"
                                      style="margin:0 0 0
                                      .8ex;border-left:1px #ccc
                                      solid;padding-left:1ex">Reviewer:
                                      Robert Sparks<br>
                                      Review result: Ready<br>
                                      <br>
                                      I am the assigned Gen-ART reviewer
                                      for this draft. The General Area<br>
                                      Review Team (Gen-ART) reviews all
                                      IETF documents being processed<br>
                                      by the IESG for the IETF Chair.
                                      Please wait for direction from
                                      your<br>
                                      document shepherd or AD before
                                      posting a new version of the
                                      draft.<br>
                                      <br>
                                      For more information, please see
                                      the FAQ at<br>
                                      <br>
                                      &lt;<a moz-do-not-send="true"
                                        href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq"
                                        rel="noreferrer" target="_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                                      <br>
                                      Document:
                                      draft-ietf-mpls-residence-time<wbr>-13<br>
                                      Reviewer: Robert Sparks<br>
                                      Review Date: 2017-02-13<br>
                                      IETF LC End Date: 2017-01-17<br>
                                      IESG Telechat date: 2017-03-02<br>
                                      <br>
                                      Summary: Ready for publication as
                                      PS<br>
                                      <br>
                                      Thanks for addressing my comments.<br>
                                      (I still think some discussion
                                      about taking arrival and departure
                                      time<br>
                                      measurements would be helpful,
                                      even if it only said "do it<br>
                                      consistently so you don't indicate
                                      jitter that's not really there".)<br>
                                      <br>
                                    </blockquote>
                                  </div>
                                  <br>
                                </div>
                              </blockquote>
                              <br>
                            </span></div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------4BA9FE9488D2E8686F0044F9--


From nobody Wed Feb 22 01:41:43 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 859EA1296AE for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 01:41:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 G4Dy1lb_NBrx for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 01:41:40 -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 A586E1296A2 for <ietf@ietf.org>; Wed, 22 Feb 2017 01:41:39 -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 v1M9fbo3014238 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:41:37 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A70CC2045E8 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:41:37 +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 9D94C202B0E for <ietf@ietf.org>; Wed, 22 Feb 2017 10:41:37 +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 v1M9fbDf031845 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:41:37 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com>
Date: Wed, 22 Feb 2017 10:41:28 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1_obu6RGJNDr5wMMTwGUyQVfXsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 09:41:41 -0000

Le 22/02/2017 à 00:23, Brian E Carpenter a écrit :
> On 22/02/2017 11:58, Job Snijders wrote:
>> On Wed, Feb 22, 2017 at 11:44:42AM +1300, Brian E Carpenter wrote:
>>> On 21/02/2017 23:13, Job Snijders wrote:
>>>> On Tue, Feb 21, 2017 at 02:11:15PM +1300, Brian E Carpenter
>>>> wrote:
>>>>> On 21/02/2017 13:19, Job Snijders wrote:
>>>>>> On Thu, Feb 16, 2017 at 09:40:01AM +0100,
>>>>>> otroan@employees.org wrote:
>>>>>>> There are many reasons for the 64 bit boundary. -
>>>>>>> Allowing identifier locator split: 8+8 / GSE that led to
>>>>>>> ILNP and NPT66
>>>>>>
>>>>>> Irrelevant.
>>>>>
>>>>> Not really. They are both running code. You may not want them
>>>>> in *your* network but that isn't the point. Some people want
>>>>> them.
>>>>>
>>>>> And there is a lot of other running code too, not just SLAAC
>>>>> which is mandatory to implement in every IPv6 host. So this
>>>>> actually trumps all the other arguments: it's 64 bits because
>>>>> it's 64 bits.
>>>>
>>>> When someone utters the phrase "it is X because it is X", the
>>>> rhetorical imperative seems to be to dismiss further
>>>> conversation (perhaps any internal dialogue as well, which may
>>>> be the primary purpose). "It is what it is" therefore, there’s
>>>> nothing more to be said about it...
>>>>
>>>> Except when it's not 64 bits?
>>>
>>> That wasn't quite my intention. I just wanted to underline that
>>> (like it or not) it was set at 64 bits many years ago and a lot
>>> has been built on that.
>>>
>>> ...
>>>> I've looked at all configured IPv6 addresses on AS 2914
>>>> equipment. Interestingly enough, the below table is a
>>>> reflection of not only NTT's own addressing, and (since
>>>> AS2914's core function is to connect networks to each other)
>>>> also of its peers and customers. In the end, whatever makes the
>>>> thing work is the thing that will be configured.
>>>>
>>>> /127 - 22% /126 - 52% /125 - 0,9% /124 - 0,5% /120 - 0,04% /112
>>>> - 0,02% /64  - 23%
>>>
>>> Thanks, that's interesting. So 23% of the devices might have
>>> RFC4291-compliant IIDs. The others are configured with 128 bit
>>> IPv6 addresses. Is that correct?
>>
>> The percentage is not the percentage of devices, but the percentage
>> of interconnections. In all instances the addresses are staticly
>> configured.
>
> OK, but from the outside I can't know that for the /64 subnets.
>
>> Back to my example from earlier, to make sure we are on the same
>> page, this is output from a standard Linux machine:
>>
>> job@tardis:~$ sudo ip -6 addr add 2001:728:1808:1::21/126 dev eth1
>> job@tardis:~$ sudo ip -6 addr show dev eth1 3: eth1:
>> <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qlen 1000 inet6
>> 2001:728:1808:1::21/126 scope global valid_lft forever
>> preferred_lft forever inet6 fe80::20d:b9ff:fe41:d4f5/64 scope link
>> valid_lft forever preferred_lft forever job@tardis:~$
>>
>> Most network engineers would call the above example "configuring a
>> /126 on an interface" - but am I understanding correctly that in
>> your taxonomy you would call this "configuring a 128 bit IPv6
>> address"?
>
> Well that does two things: configures a 128 bit address (as Chris
> points out, *all* addresses are 128 bits, duh) and associates a
> prefix length with it, which afaik is optional.

The prefix length is not optional.  There is no system out there on
which one could configure a 128bit address without explicitely telling
'/128' or '/64' or '/something-else'.

By specifications, I think only DHCPv6 specs say that the address
assigned to a Client has no prefix length.  In practice though, the
address assigned by DHCPv6 w/o  prefix length gets a 'by default' prefix
length often hardcoded as '/64'.

> But the interface has already auto-configured a link-local address,
> with a 64 bit IID. So yes, that's exactly what I mean.

Which brings back: the LL address should have a prefix length or no?  If 
yes should it be /64 (2464bis) or /10 (4291bis)?

Linux sets it at /64 by default... and I disagree with it, 4291bis 
disagrees too.

Alex

>>> That being so, perhaps the words that are missing are "The IID
>>> length requirement does not apply to interfaces that are
>>> explicitly configured with 128 bit addresses." Because the
>>> requirement is meaningless for such interfaces.
>>
>> The terminology might confuse some people, as in common language
>> when one configures "a /128", or 'a 128 bit address', it usually
>> means you are configuring something like a loopback address.
>>
>> Perhaps:
>>
>> "The IID length requirement does not apply to interfaces that are
>> explicitly configured without autoconfiguration."
>>
>> (perhaps even remove the word 'explicitly')
>>
>> "The IID length requirement does not apply to interfaces that are
>> configured without autoconfiguration."
>
> Personally I think that's right. (However, if you manually configure
> an address that matches a pre-existing prefix announced by an RA, it
> will be assumed to belong to that prefix. I've done that by hand on
> Windows, not sure I've done it in Linux.)
>
> Brian
>
>


From nobody Wed Feb 22 01:44:02 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15548129689 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 01:43:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 FjZPNTNqzYF4 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 01:43:57 -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 4BFEE129669 for <ietf@ietf.org>; Wed, 22 Feb 2017 01:43:57 -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 v1M9hsrm026206 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:43:54 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A199A204A1F for <ietf@ietf.org>; Wed, 22 Feb 2017 10:43:54 +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 8E26E2046D5 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:43:54 +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 v1M9hsgv001281 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:43:54 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <1074143e-0ca1-0427-ddcb-61a5aa678a4c@gmail.com>
Date: Wed, 22 Feb 2017 10:43:47 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EI1lsry4C9ibtevTQJ0BEisjZyk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 09:43:59 -0000

Le 22/02/2017 à 01:19, Lorenzo Colitti a écrit :
> On Tue, Feb 21, 2017 at 7:13 PM, Job Snijders <job@ntt.net
> <mailto:job@ntt.net>> wrote:
>
>     I've looked at all configured IPv6 addresses on AS 2914 equipment.
>     The above percentages come from grepping through configurations of
>     thousands of interconnections. I'm confident that other networks will
>     show similar prefix length distributions.
>
>
> "Thousands of interconnections" are not really relevant given that we're
> well into the hundreds of millions of IPv6 hosts on residential or
> mobile connections that provide one or more /64s.

Maybe if he said 'permanent' connections, which mobile or residential 
are less.

One could have one trillion connections on/off during 10years, but only 
1 connection up all that time.

Alex


From nobody Wed Feb 22 02:47:05 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A647A1296D0; Wed, 22 Feb 2017 02:47:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 fAGdXK4ElrHK; Wed, 22 Feb 2017 02:47:03 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 869401296BD; Wed, 22 Feb 2017 02:47:03 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgURm-0007nn-53 (job@us.ntt.net); Wed, 22 Feb 2017 10:46:59 +0000
Date: Wed, 22 Feb 2017 11:46:25 +0100
From: Job Snijders <job@ntt.net>
To: Christopher Morrow <christopher.morrow@gmail.com>, Lorenzo Colitti <lorenzo@google.com>
Message-ID: <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark>
In-Reply-To: <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
X-Readdle-Message-ID: 4936e96b-fc82-4de0-9188-ced9547deb2f@Spark
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="58ad6c08_2ae8944a_d3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yrc1zd_6XtbIlBTfcEpc_07DpFM>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 10:47:05 -0000

--58ad6c08_2ae8944a_d3
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

One of the immediate benefits of using a /126, is that it's not a /64! Also, a /126 is the smallest non-64 size with the highest likeliness to get the job done from an interoperability perspective (not the /127). Another example: when you use a /120, the advantage again is that it is not a /64, and you can make a bunch of routers talk BGP with each other on a layer-2 segment. This is why /126, /125, /124 etc end up being used.

An Addressing Architecture that does not admit this has been common practice for 15+ years, is disassociated from reality and thus inconsequential and no good. It does not follow that because you don't see enough advantages, the idea and practice are bad.

Kind regards,

Job

On 22 Feb 2017, 04:52 +0100, Lorenzo Colitti <lorenzo@google.com>, wrote:
> On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <christopher.morrow@gmail.com (mailto:christopher.morrow@gmail.com)> wrote:
> > > But the configuration cost and management overhead is not proportional to the hosts that are served by those interconnections, it is proportional to the number of interconnections. A 10x100G peering interconnection that serves X million hosts is one interface that has to be managed.
> >
> > isn't the dicsussion here really:
> > "If you want to use /64 go ahead, if you want to use /121 go for it, if you want to use SLAAC you'll get a /64 and like it"
>
> Not sure. I for one wouldn't agree with that position, because I don't see that /121 has enough advantages over /127 and /64 - and few enough downsides for general-purpose hosts - to make it a good idea in general.
--58ad6c08_2ae8944a_d3
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<html xmlns=3D=22http://www.w3.org/1999/xhtml=22>
<head>
<title></title>
</head>
<body>
<div name=3D=22messageBodySection=22>One of the immediate benefits of usi=
ng a /126, is that it's not a /64=21 Also, a /126 is the smallest non-64 =
size with the highest likeliness to get the job done from an interoperabi=
lity perspective (not the /127). Another example: when you use a /120, th=
e advantage again is that it is not a /64, and you can make a bunch of ro=
uters talk BGP with each other on a layer-2 segment. This is why /126, /1=
25, /124 etc end up being used.<br />
<br />
An Addressing Architecture that does not admit this has been common pract=
ice for 15+ years, is disassociated from reality and thus inconsequential=
 and no good. It does not follow that because you don't see enough advant=
ages, the idea and practice are bad.</div>
<div name=3D=22messageSignatureSection=22><br />
Kind regards,<br />
<br />
Job</div>
<div name=3D=22messageReplySection=22><br />
<div name=3D=22messageReplySection=22><br />
On 22 =46eb 2017, 04:52 +0100, Lorenzo Colitti &lt;lorenzo=40google.com&g=
t;, wrote:<br />
<blockquote type=3D=22cite=22>
<div dir=3D=22ltr=22>
<div class=3D=22gmail=5Fextra=22>
<div class=3D=22gmail=5Fquote=22>On Wed, =46eb 22, 2017 at 12:12 PM, Chri=
stopher Morrow <span dir=3D=22ltr=22>&lt;<a href=3D=22mailto:christopher.=
morrow=40gmail.com=22 target=3D=22=5Fblank=22>christopher.morrow=40gmail.=
com</a>&gt;</span> wrote:<br />
<blockquote class=3D=22gmail=5Fquote=22 style=3D=22margin:0 0 0 .8ex;bord=
er-left:1px =23ccc solid;padding-left:1ex=22>
<div dir=3D=22ltr=22>
<div class=3D=22gmail=5Fextra=22>
<div class=3D=22gmail=5Fquote=22><span class=3D=22=22></span>
<blockquote class=3D=22gmail=5Fquote=22 style=3D=22margin:0 0 0 .8ex;bord=
er-left:1px =23ccc solid;padding-left:1ex=22><span class=3D=22=22><span c=
lass=3D=22=22></span></span>
<div dir=3D=22ltr=22><span class=3D=22=22><span class=3D=22=22></span></s=
pan>
<div class=3D=22gmail=5Fextra=22><span class=3D=22=22><span class=3D=22=22=
></span></span>
<div class=3D=22gmail=5Fquote=22><span class=3D=22=22><span class=3D=22=22=
></span></span>
<div><span class=3D=22=22><span class=3D=22=22>But the configuration cost=
 and management overhead is not proportional to the hosts that are served=
 by those interconnections, it is proportional to the number of interconn=
ections. A 10x100G peering interconnection that serves X million hosts is=
 one interface that has to be managed.</span></span></div>
</div>
</div>
</div>
</blockquote>
<div><span class=3D=22=22><br /></span></div>
<div>isn't the dicsussion here really:<br />
&=23160; =22If you want to use /64 go ahead, if you want to use /121 go f=
or it, if you want to use SLAAC you'll get a /64 and like it=22</div>
</div>
</div>
</div>
</blockquote>
<div><br /></div>
<div>Not sure. I for one wouldn't agree with that position, because I don=
't see that /121 has enough advantages over /127 and /64 - and few enough=
 downsides for general-purpose hosts - to make it a good idea in general.=
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--58ad6c08_2ae8944a_d3--


From nobody Wed Feb 22 02:57:59 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2F401296E8 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 02:57:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 COEbwwGuti8P for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 02:57:49 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (vsp-unauthed02.binero.net [195.74.38.227]) (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 3DBCC1296DF for <ietf@ietf.org>; Wed, 22 Feb 2017 02:57:45 -0800 (PST)
X-Halon-ID: b8c0bedd-f8ed-11e6-af90-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Wed, 22 Feb 2017 11:57:35 +0100 (CET)
Subject: Re: [Slim] Review of draft-ietf-slim-negotiating-human-language-06
To: Randall Gellens <rg+ietf@randy.pensive.org>, Dale Worley <worley@ariadne.com>, gen-art@ietf.org
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <p06240602d4d236a5a2dd@[99.111.97.136]>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
Date: Wed, 22 Feb 2017 11:57:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240602d4d236a5a2dd@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MlXWI9uv3Dz1EXEKp_oO34gdSFA>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 10:57:52 -0000

A few comments inline,


Den 2017-02-22 kl. 02:44, skrev Randall Gellens:
> Hi Dale,
>
> Thank you for your review, I appreciate it.  Please see inline.
>
> At 6:32 PM -0800 2/17/17, Dale Worley wrote:
>
>>  Reviewer: Dale Worley
>>  Review result: Ready with Nits
>>
>>  I am the assigned Gen-ART reviewer for this draft.  The General Area
>>  Review Team (Gen-ART) reviews all IETF documents being processed
>>  by the IESG for the IETF Chair.  Please treat these comments just
>>  like any other last call comments.
>>
>>  For more information, please see the FAQ at
>>  <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>
>>  Document:  draft-ietf-slim-negotiating-human-language-06
>>  Reviewer:  Dale R. Worley
>>  Review Date:  2017-02-17
>>  IETF LC End Date:  2017-02-20
>>  IESG Telechat date:  [unknown]
>>
>>  Summary:
>>         This draft is basically ready for publication, but has nits
>>         that should be fixed before publication.
>>
>>  * Technical comments
>>
>>  A. Call failure
>>
>>  If a call fails due to no available language match, in what way(s)
>>  does it fail?  Section 5.3 says
>>
>>     If such an offer is received, the receiver MAY
>>     reject the media, ignore the language specified, or attempt to
>>     interpret the intent
>>
>>  But I suspect it's also allowed for the UAS to fail the call at the
>>  SIP level.  Whether or not that is allowed (or at least envisioned)
>>  should be described.  And what response code(s)/warn-code(s) should
>>  be
>>  used for that?
>
> The text you quote has been deleted.  The draft does not mandate if 
> the call should proceed or fail if there is no language match 
> possible, although the draft does provide an optional mechanism to 
> indicate the caller's preference that the call not fail, and the draft 
> does mention that in the emergency services case, the call will likely 
> proceed, but that's a matter of policy not protocol.
You may have a version where it is proposed that the text is deleted. We 
need to see that new text and agree if it was good to delete it.

There are more places in the draft where failing the call is mentioned, 
so the question about how it is failed is relevant anyway. A 603 Decline 
from the proxy would likely be the natural way to fail the call when it 
is because of lack of matching languages. But I do not see any natural 
way for an addressed UA to signal this.

>
>>
>>  B. Audio/Video coordination
>>
>>     5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>     Note that while signed language tags are used with a video stream
>>  to
>>     indicate sign language, a spoken language tag for a video stream
>>  in
>>     parallel with an audio stream with the same spoken language tag
>>     indicates a request for a supplemental video stream to see the
>>     speaker.
>>
>>  And there's a similar paragraph in 5.4:
>>
>>>     A spoken language tag for a video stream in conjunction with an
>>  audio
>>>     stream with the same language might indicate a request for
>>>     supplemental video to see the speaker.
>>
>>  I think this mechanism needs to be described more exactly, and in
>>  particular, it should not depend on the UA understanding which
>>  language tags are spoken language tags.  It seems to me that a
>>  workable rule is that there is an audio stream and a video stream and
>>  they specify exactly the same language tag in their respective
>>  humintlang attributes.  In that case, it is a request for a spoken
>>  language with simultaneous video of the speaker, and those requests
>>  should be considered satisfied only if both streams can be
>>  established.
>
> The text you quote has been deleted.  A media stream for supplemental 
> purposes can be negotiated without a language tag, as normal.
>
The text should not be deleted just because it is under discussion.
It is a valid and valuable alternative. At the moment we lack ways to 
indicate if languages are wanted together or seen as separate 
alternatives, and we have said that such detailing can be added in 
future versions or additional specifications if not done now. Therefore 
we had better allow this combination and let the negotiating parties 
sort out what it currently means. The specification just indicates that 
the indicated languages are alternatives, and any number may be selected 
for matching and usage in the session.
I do not think we should require very exactly matching language tags 
between spoken language in audio and corresponding view of the speaker 
in video.
>>
>>  * The following three items are adjustments to the design which I'd
>>  like to know have been considered.
>>
>>  C. "humintlang" seems long to me
>>
>>  Given the excessive length of SDP in practice, it seems to me that a
>>  shorter attribute name would be desirable.  E.g., "humlang" as was
>>  used in some previous versions.  Or is there a coordinated usage with
>>  other names in the "hum*lang" pattern?
>
> There is no intent for a coordinated pattern.  The name was chosen 
> years ago to avoid potential confusion with the 'lang' attribute. Is 
> it worth reopening the issue to potentially save three characters per 
> SDP line with a language?
>
>>
>>  D. Use the Accept-Language syntax
>>
>>  It seems to me that it would better to use the Accept-Language syntax
>>  for the attribute values.  This allows (1) specifiying the quality of
>>  language experience, allowing clear description of bilingualism, (2)
>>  a
>>  unified method of specifying whether or not arbitrary languages are
>>  acceptable, and (3) abbreviating SDP descriptions.
>>
>>  In a way, the fact that the current proposal seems to require (but
>>  does not directly specify) the coordinated absence/presence of an
>>  asterisk on all of the repetitions of humintlang-send or
>>  humintlang-recv is a warning that the syntax doesn't represent the
>>  semantics as well as it might.
>
> The group considered multiple proposals to permit specifying quality, 
> preference, q-values, etc. but decided to keep things simple for this 
> draft.  There is no intent to require the use of an asterisk (to 
> indicate a preference by the caller to not fail the call).  The 
> asterisk is a very mild mechanism with no normative effects.  It 
> merely conveys the preference of the caller, and is not binding on the 
> answerer.
I would never dare to use an sdp without an asterisk. Language matching 
is a tricky thing and human capabilities much wider than the language 
tags can express. If I get a call from a Norwegian user talking 
Norwegian and indicating Norwegian in the humintlang attributes, I want 
to get the call accepted by my device with setting for spoken Swedish, 
because Swedes and Norwegians usually can communicate quite well 
speaking their own languages. I would anyway not have imagined making a 
setting for Norwegian language as a preference in my device.
It will however be an excellent help for me to see the indication of the 
Norwegian, when I get the call, so I can tune my listening.
By setting the asterisk somewhere among the Humintlang attributes, I 
will make sure that I do not lose calls that I could handle.

>
>>  E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>
>>  Note that all examples are bidirectionally symmetric, and the text
>>  says that requests and responses SHOULD be bidirectionally symmetric.
>>  So it would be a very useful abbreviation to define
>>  "humintlang=<value>" to be equivalent to the combination of
>>  "humintlang-send=<value>" and "humintlang-recv=<value>".
>>
>>  Combining proposals C, D, and E, the examples become
>>
>>        m=audio 49170 RTP/AVP 0
>>        a=humlang:en
>>
>>        m=video 51372 RTP/AVP 31 32
>>        a=humlang:ase,*;q=0.1
>>
>>        m=audio 49250 RTP/AVP 20
>>        a=humlang:es,eu;q=0.9,en;q=0.8,*;q=0.1
>>
>>        m=text 45020 RTP/AVP 103 104
>>        a=humlang:gr
>>
>>  which requires about half as many characters as they have now.
>
> A third attribute without the "-send" or "-recv" to indicate 
> bidirectionality would reduce the characters in the SDP block, at the 
> cost of some added complexity (e.g., what if all three appear).  I 
> don't believe this has been discussed in the group.
>
>>  * Editorial comments and nits
>>
>>  Abstract
>>
>>     This document describes the need and a solution using new SDP
>>  stream
>>     attributes.
>>
>>  I don't think the term "stream attribute" is used in RFC 4566.
>>  Instead, it uses "media attribute".
>
> Fixed.
>
>>  1.  Introduction
>>
>>     caller and callee know each other or there is contextual or out of
>>     band information from which the language(s) and media modalities
>>  can
>>
>>  I think this context, it's preferred to hyphenate "out-of-band" to
>>  make it clearly be an adjective.
>
>>  OK.
>
>
>>     This approach has a number of benefits, including that it is
>>  generic
>>     (applies to all interactive communications negotiated using SDP)
>>  and
>>     not limited to emergency calls.
>>
>>  I think s/and not limited to/and is not limited to/ reads more
>>  smoothly.
>
> There's no harm in the extra "is" so I'm happy to add it.
>
>>     But it is clearly useful in many other cases.  For
>>     example, someone calling a company call center or a Public Safety
>>     Answering Point (PSAP) should be able to indicate if one or more
>>     specific signed, written, and/or spoken languages are preferred,
>>  the
>>     callee should be able to indicate its capabilities in this area,
>>  and
>>     the call proceed using in-common language(s) and media forms.
>>
>>  I think s/preferred, the callee/preferred; the callee/ because the
>>  sentence is the concatenation of two sentences.
>
> I reworded the sentence to flow better:
>
>    For example, it is helpful that someone calling a company call center
>    or a Public Safety Answering Point (PSAP) be able to indicate
>    preferred signed, written, and/or spoken languages, the callee be
>    able to indicate its capabilities in this area, and the call proceed
>    using the language(s) and media forms supported by both.
>
>>  Perhaps s/in-common/shared/.
>
> Fixed in the rewording above.
>
>>
>>     Including the user's human (natural) language preferences in the
>>     session establishment negotiation is independent of the use of a
>>     relay service and is transparent to a voice service provider.
>>
>>  I think it's even broader than "transparent to a voice service
>>  provider" -- it's transparent to any serivice provider, assuming that
>>  the media are language-neutral.
>
> I changed it to read "voice or other service provider".
>
>>
>>     In the case of a call to e.g., an airline, the call could be
>>     automatically handled by a Spanish-speaking agent.
>>
>>  I think s/handled by/routed to/ is the usual usage.
>
> We are trying to be careful in the draft to not imply that it is 
> discussing call routing.  I'd rather keep the more generic "handled by".
>
>>
>>  3.  Desired Semantics
>>
>>     The desired solution is a media attribute (preferably per
>>  direction)
>>     that may be used within an offer to indicate the preferred
>>  language
>>     of each (direction of a) media stream, and within an answer to
>>     indicate the accepted language.
>>
>>  In this one instance, I think you want to use "language(s)" to drive
>>  home that that multiple languages can be specified:  "within an offer
>>  to indicate the preferred language(s)".
>>
>>     (Negotiating multiple simultaneous languages within a media stream
>>  is
>>     out of scope, as the complexity of doing so outweighs the
>>     usefulness.)
>>
>>  You might want to say instead "(Negotiating multiple simultaneous
>>  languages within a media stream is out of scope for this document.)"
>>  to ensure that nobody decides to argue whether "the complexity of
>>  doing so outweighs the usefulness".
>
> I agree and deleted "the complexity of doing so outweighs the 
> usefulness".
>
>>
>>  4.  The existing 'lang' attribute
>>
>>     RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>     similar to what is needed here, but is not sufficiently detailed
>>  for
>>     use here.
>>
>>  "for use here" isn't quite right.  Maybe "is not sufficiently
>>  specific
>>  or flexible to satisfy the requirements".
>>
>>     In addition, it is not mentioned in [RFC3264]
>>
>>  "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>  attribute".
>
> OK, accepted both changes.
>
>>
>>  5.  Proposed Solution
>>
>>  Perhaps /Proposed Solution/Solution/, since once this draft is
>>  approved, it becomes the solution.
>
> OK.
>
>>
>>  5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>
>>        a=humintlang-send:<language tag>
>>        a=humintlang-recv:<language tag>
>>
>>  This is presented as the generic form of the attributes, but there is
>>  no indication of the posible asterisk.
>
> The syntax has been deleted from 5.2 since it's now in 6.
I think it should not be deleted, but instead Dale's comment satisfied.  
That would be more in line with the stye of rfc4566bis.
5.2 shows the complete attributes, and that is good. Chapter 6 only 
shows the syntax of the value.
>
>>
>>     The values constitute a list of languages
>>     in preference order (first is most preferred).
>>
>>  "The values" isn't very clear, because the values are in successive
>>  attributes.  You want to say something like "The sequence of values
>>  in
>>  the occurrences of one of these attributes constitutes ...".
>>  However,
>>  see the technical comments above.
>
> The text was reworded to read:
>
>    The values from all
>    instances of the attribute constitute a list of languages in
>    preference order (first is most preferred).
>
>
>>
>>     When placing an emergency call, and in any other case where the
>>     language cannot be assumed from context, each media stream in an
>>     offer primarily intended for human language communication SHOULD
>>     specify both (or in some cases, one of) the 'humintlang-send' and
>>     'humintlang-recv' attributes.
>>
>>  Probably s/assumed/inferred/.
>
> I agree.
>
>>
>>  Could you be more accurate by
>>  s/or in some cases/or for unidirectional streams/?
>
> I agree.
>
>>
>>  5.3.  Advisory vs Required
>>
>>     The mechanism for indicating this preference is that, in an offer,
>>  if
>>     the last character of any of the 'humintlang-recv' or 'humintlang-
>>     send' values is an asterisk, this indicates a request to not fail
>>  the
>>     call (similar to SIP Accept-Language syntax).  Either way, the
>>  called
>>     party MAY ignore this, e.g., for the emergency services use case,
>>  a
>>     PSAP will likely not fail the call.
>>
>>  The construction of this paragraph isn't quite complete.  It says
>>  that
>>  if an asterisk is present, a request shouldn't fail, but it doesn't
>>  say that if no asterisk is present, a request should fail if there is
>>  no language match.  And it's the latter condition that makes the
>>  second sentence meaningful.  So I think you want to insert between
>>  the
>>  two sentences one regarding the absence of an asterisk.
>
> I've reworded the section to read:
>
>    A consideration with the ability to negotiate language is if the call
>    proceeds or fails if the callee does not support any of the languages
>    requested by the caller.  This document does not mandate either
>    behavior, although it does provide a way for the caller to indicate a
>    preference for the call succeeding when there is no language in
>    common.  It is OPTIONAL for the callee to honor this preference.  For
>    example, a PSAP is likely to attempt the call even without an
>    indicated preference when there is no language in common, while a
>    call center might choose to fail the call.
>
>    The mechanism for indicating this preference is that, in an offer, if
>    the last character of any of the 'humintlang-recv' or 'humintlang-
>    send' values is an asterisk, this indicates a request to not fail the
>    call.  The called party MAY ignore the indication, e.g., for the
>    emergency services use case, regardless of the absence of an
>    asterisk, a PSAP will likely not fail the call; some call centers
>    might reject a call even with an asterisk.
This still does not meet Dale's comment.
Insert a sentence saying:
"A preference for getting the call denied in case of no language match 
SHOULD be indicated by no asterisk appended on any humintlang attribute 
value in the whole SDP."
>
>>  5.5.  Examples
>>
>>  Given that the combined audio/video mechanism is the only
>>  irregularity
>>  in this system, there ought to be an example of it.  E.g.,
>>
>>     An example of a supplemental video stream with a spoken language
>>     audio stream:
>>
>>        m=video 51372 RTP/AVP 31 32
>>        a=humintlang-send:en
>>        a=humintlang-recv:en
>>
>>        m=audio 49250 RTP/AVP 20
>>        a=humintlang-send:en
>>        a=humintlang-recv:en
>
> If the video stream is supplemental then it doesn't have a language 
> (the text that suggested otherwise has been deleted). But I am 
> considering adding more examples.
I provided a rich set of examples in my LC comments of Feb 13. Please 
consider them as a base even if some need revision if the proposed 
extended meaning of the asterisk is not accepted.
>
>>
>>  6.  IANA Considerations
>>
>>        humintlang-value =  Language-Tag [ asterisk ]
>>                            ; Language-Tag defined in RFC 5646
>>        asterisk         =  "*"
>>
>>  s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>  5646/
>>
>>  But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>  tracks the current version of language tags.
>
> Ok.
>
>>
>>  Appendix A.  Historic Alternative Proposal: Caller-prefs
>>
>>     This
>>     results in a more fragile solution since the media modality and
>>     language would be negotiated using SIP, and then the specific
>>  media
>>     formats (which inherently include the modality) would be
>>  negotiated
>>     at a different level (typically SDP, especially in the emergency
>>     calling cases), making it easier to have mismatches (such as where
>>     the media modality negotiated in SIP don't match what was
>>  negotiated
>>     using SDP).
>>
>>  "the media modality and language would be negotiated using SIP" isn't
>>  quite the right way to say it because SIP isn't explicitly
>>  negotiating
>>  the modality.  Better would be
>>
>>     ... the language (and by implication the media modality) would be
>>     negotiated using SIP, and then the specific media (which
>>  inherently
>>     include the modalities and formats) would be negotiated at a
>>     different level ...
>
> This section has been deleted.
Did we agree on that?
>
>>
>>  [END]
>
>
Regards
Gunnar

-- 
-----------------------------------------
Gunnar Hellström
Omnitor
gunnar.hellstrom@omnitor.se
+46 708 204 288


From nobody Wed Feb 22 05:38:34 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94191298AA; Wed, 22 Feb 2017 05:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=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 u-l6z4NU_WF3; Wed, 22 Feb 2017 05:38:30 -0800 (PST)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (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 7734B129895; Wed, 22 Feb 2017 05:38:30 -0800 (PST)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.124.243.128; 
From: "Susan Hares" <shares@ndzh.com>
To: "'David Black'" <david.black@emc.com>, <tsv-art@ietf.org>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com>
In-Reply-To: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com>
Subject: RE: [Idr] Review of draft-ietf-idr-sla-exchange-10
Date: Wed, 22 Feb 2017 08:34:08 -0500
Message-ID: <00bc01d28d10$58be37e0$0a3aa7a0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKDUuAoPuK0lQdnfnc2fTnq9qa/26ATetSg
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EC4JVInqWp2Q6fpPf5lZHKZOcT4>
Cc: idr@ietf.org, draft-ietf-idr-sla-exchange.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 13:38:33 -0000

David: 

Thank you for the review.  The authors will respond to you on these issues. 

Sue 

-----Original Message-----
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of David Black
Sent: Tuesday, February 21, 2017 5:32 PM
To: tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: [Idr] Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors for their information and to allow them to address any issues
raised. When done at the time of IETF Last Call, the authors should consider
this review together with any other last-call comments they receive. Please
always CC tsv-art@ietf.org if you reply to or forward this review.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by the
IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic handling
parameters (e.g., configured rates, burst sizes, drop thresholds).  While
this is a useful area of technology to standardize across network operators,
this draft has significant problems, and parts of it could use some serious
rethought.

This reviewer has discussed small portions of this draft with some of the
authors in the past, but this is his first comprehensive reading and review
of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft - see
the definition of TCA in RFC 2475.  This draft should start from that
definition and generalize the applicability of TCA beyond Diffserv.  Large
areas of SLA content are not covered by this draft - for more details, see
the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to specify
a token bucket is a good idea, but it's not a good idea to respecify that
construct in terms of L2 (link-layer, e.g., Ethernet) octets, as the RFC
2115 TSpec is specified in terms of IP octets. 
This change to specification in terms of L2 octets results in needing the
L2_OVERHEAD TLV to cope with the possible differences in L2 (link) framing
overhead at sender and receiver of this information.  The TSpec should be
respecified at the IP layer, with L2 framing overhead left to the Producer
and Consumer to factor into their calculations based on each's direct
knowledge of L2 functionality and configuration in the local AS.  That ought
to enable elimination of the L2_OVERHEAD TLV, thereby reducing complexity.

[3] A token bucket should have two rate-related marking parameters based on
its token fill rate, i.e., min-rate, not the four rate-related marking
parameters in this draft.  The max-rate parameters in sections 3.3.2.5-6
ought to be specified against a second token bucket.  In addition, the
handling precedence algorithm in section 3.3.2.7 is an overly complex way to
specify the relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only applicable to
bursting - that max-rate for bursting often turns out to be an interface
line rate, which is not generally useful for the traffic provisioning
purposes of this draft.

The following should be done instead:
	- Define TSpecs for two token buckets, a primary/committed token
bucket
		and a secondary/peak token bucket that MUST be nested, i.e.,
traffic
		that is in-profile for the secondary/peak token bucket is
always
		in-profile for the primary/committed token bucket.  Some of
the details
		of how to specify this are subtle, see RFC 2698 for a worked
example.
		Use of a secondary/peak token bucket requires use of the
primary/
		committed token bucket, but a primary/committed token bucket
can be used
		without a secondary/peak token bucket.
	- For a single token bucket, define two handling TLVs, Committed (in
profile) and
		Excess (out of profile).
	- For two token buckets, define three handling TLVs, Committed (in
profile for both
		token buckets), Peak (out of profile for primary/committed
token bucket, but in
		profile for secondary/peak token bucket) and Excess (out of
profile for both
		token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified sufficiently
to be implemented interoperably.  For example, I don't understand what an
implementation is supposed to do when it receives 3 drop thresholds.

[5] The relative priority TLV in section 3.3.2.9 has the same insufficient
specification problem as the drop threshold TLV, compounded by a functional
incompleteness problem - if the recipient is using a weighted packet
transmission scheduler (e.g., WRR), priorities cannot be used to configure
that scheduler.  Hence, some specification of weights and scheduling
algorithms that use weights needs to be added.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic Class
TLVs" which is an undefined term in this draft (e.g., that term is not used
outside of section 3.3.2.10.

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some assurance that
that this draft is implementable for actual network switch/router data
paths.  The current acknowledgement of the existence of YANG, NETCONF and
RESTConf at the end of Section 1 does not suffice.

[8] There are significant complexity and correctness problems caused by the
option to not specify the Source AS - e.g., Section 3.2 defines an SLA ID as
an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

[9] In section 3.2, the "intended for the peer receiver of the BGP UPDATE
message" text in the specification of bit 0 of the SLA Subtype flags is
unclear.  I suspect that this is intended to differentiate the two usages
described in sections 4.1.1 (Point-to-Point) and 4.1.2 (Multiple Hops), in
which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two sections.

[10] There needs to be a coherent discussion in one place about how SLA
advertisement, update and withdrawal work.  A single ADVERTISE method may
suffice on the wire, but the details on how initial advertisement,
subsequent advertisement (update) and withdrawal work need to be specified
in one place.  The third paragraph of Section 4 is a start on this material,
but it's too terse; it should be expanded into its own subsection, and moved
earlier to come before the ADVERTISE method in Section 3.2.  This text from
Section 3.2 should be moved into that new subsection and likewise expanded:

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that was
not part of the original design.

[11] Notions of context for interpretation of all the IPFIX parameters in
3.3.1 need to be added, e.g.:
	- The first three parameters (DSCP, MPLS EXP field in top label,
802.1q priority) can
		and do vary on a link-by-link or LSP-by-LSP basis along a
traffic's network path.
	- The IP address parameters are rather likely to be VPN-specific
when there's more
		than one BGP/MPLS VPN that spans or transits the ASs
involved.
	- The transport port parameters need specification of which
transport header and where it
		is located (e.g., for TCP traffic carried by in VXLAN, is
this the inner TCP header
		or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all cases, but
that context does need to be specified ... in all cases.

[12] The security considerations (section 10) are severely incomplete and
insufficient:

	- Discussion of possible abuse of this BGP option for
denial-of-service and theft-of-service,
		needs to be added, including possible countermeasures and
mitigations.

	- This sentence at the end of the second paragraph in Section 10 is
content-free:

		   It is NOT RECOMMENDED to enable this attribute at the
		   scale of the Internet unless if means to prevent leaking
sensitive
		   information are enforced.

		What exactly is an implementer or admin supposed to do?  How
does one
		figure out whether an implementation or deployment is  "at
the scale
		of the Internet" ??

	- The next to last paragraph in section 10 is almost content-free,
as it leaves
		decisions on implementation and deployment of key security
functionality as
		"an exercise for the reader" - that's not acceptable.

	- Last, but not least, the final paragraph in Section 10 is a joke
that will
		be lost on a security directorate reviewer - to understand
why, see
		Section 2 of RFC 6919, and take note of the publication date
of RFC 6919.

------------------------

Having noted a dozen major issues, I'll end the review here for now, as I
believe a serious revision of the draft is called for, which would be a
better starting point to review for minor issues and editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com  <=== NEW ===
--------------------------------------------------------



_______________________________________________
Idr mailing list
Idr@ietf.org
https://www.ietf.org/mailman/listinfo/idr


From nobody Wed Feb 22 06:17:35 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01ED129961 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:17:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zHjnwSYqTVFk for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:17:32 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c: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 067BA12996C for <ietf@ietf.org>; Wed, 22 Feb 2017 06:17:32 -0800 (PST)
Received: by mail-vk0-x22c.google.com with SMTP id r136so2265761vke.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:17:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=fJbShjzwAajr/xL5MEq/GUDSXh6xW4h+W6Yd/O51O6I=; b=ici1Do7ereyVVLU++2M3rEDXtlgCTm6AmxA7WHA2zqxtd0SrCNEZTojL7mvxUum/rN C9W7AjZaXmtwNohFz8OD7EqVcIDj1Ap9myaJy/NpQCePDjJ05qnEebfGTKU8jDn6EzvI W9xedEWRFORlsmEoOXWx5tgVqNFPd/l0UGDX0JrmL+bqPaz9ZMvJW17H4EUuyeWc5pRu 77FtJZFbRGnN6WMUlTHCjTkwu8/SR5qMa6eZgLiAeYD2WufFq91qLM0Sxe8m9tfBvR+F 4PAtpy7KQw+Ixw+MkBCuoRrwULi2FCVYCypFpE276yQ7jWKicr1ggo4iZMCGl8tC8Pks H5XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=fJbShjzwAajr/xL5MEq/GUDSXh6xW4h+W6Yd/O51O6I=; b=sxmWubnOy9rF0stzxPajRs0P46V//Etr/520TFmQgnm3NWs/PCScT0ikoWLIckOV95 WD/oHghIIwwodIy/e5sAcyCy57PQNQXx7m4hSm/8cLUSBvc/WFOvQtvUaCQ21VLJbg8z TJmg361rBiwCv9nzNQidU/3fku0aKbInYnzdCVh70LpQKtu0rlg76YosSa3kgQvf6/Cg x8+Y7b2qshuzP6a7VfkReex6/o4Jc4ezgd01oDs0iNDACp48PDPcOaxZOh20UypbUawT xvdI+S70haXXG4VRCIDh+K+kVJa1EHN8V45UYRzmP7XkawAeZByULfhNB/yHet21mtUd T5Vw==
X-Gm-Message-State: AMke39mcvVRFe34saa8SaNpQaFHGT1L2IWHFWulxTdtq02J7tOKlR3trk+DbRCdeetolOCuK9xSLl/v8Cfhdl+Qq
X-Received: by 10.31.59.197 with SMTP id i188mr12227960vka.45.1487773050823; Wed, 22 Feb 2017 06:17:30 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 06:17:09 -0800 (PST)
In-Reply-To: <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 23:17:09 +0900
Message-ID: <CAKD1Yr2yjH9SGtBv2pJPEtceBWo=4+vobAV1o1JBjVpcNLXmcA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: multipart/alternative; boundary=001a1142f17833d3d305491f28bc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/AdMR0ZYTbf1z-3kcjhz-I9GCo_k>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:17:34 -0000

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

Host developers and users do care what the prefix length is.

There are lots of things you can do if you know that the network will never
run out of addresses. For example, you can form new addresses at will and
use them for anything you want (privacy; per-application addresses, or
whatever else you can think of). Read RFC 7934 for a list of the things
we've thought of so far, and bear in mind that if this IPv6 thing even only
lasts as long as IPv4, that's still several decades, and I'm sure we'll
have lots of bright ideas during that time if we don't shortsightedly carry
over IPv4 practices motivated by address scarcity.

A fixed prefix length is also very beneficial because it allows hosts to
extend the network indefinitely at layer 2 without giving up the benefits
provided by autoconfiguration and end to end connectivity. It means that
ill-informed or ill-intentioned network administrators cannot use
addressing to constrain apps in a way that leads to suboptimal user
experience. That sort of thing obviously does not happen in the 2914 or
15169 backbone. It does happen in lots of other places.

On Wed, Feb 22, 2017 at 1:44 PM, Christopher Morrow <
christopher.morrow@gmail.com> wrote:

>
>
> On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <lorenzo@google.com>
> wrote:
>
>> On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <
>> christopher.morrow@gmail.com> wrote:
>>
>>> But the configuration cost and management overhead is not proportional
>>>> to the hosts that are served by those interconnections, it is proportional
>>>> to the number of interconnections. A 10x100G peering interconnection that
>>>> serves X million hosts is one interface that has to be managed.
>>>>
>>>
>>> isn't the dicsussion here really:
>>>   "If you want to use /64 go ahead, if you want to use /121 go for it,
>>> if you want to use SLAAC you'll get a /64 and like it"
>>>
>>
>> Not sure. I for one wouldn't agree with that position, because I don't
>> see that /121 has enough advantages over /127 and /64 - and few enough
>> downsides for general-purpose hosts - to make it a good idea in general.
>>
>
> I don't think /121 is anymore special than /127... or /64. My point was we
> don't care what prefix people use, generally, that there are cases where a
> /64 is required and that's fine, there are cases where /64 isn't and people
> can do what they want there.  It's simple enough to do SLAAC/64 on lans and
> other places.
>
> Requiring /64 or /127 and nothing else means when you do have to do a /120
> or something else you MAY end up fighting vendor problems because they made
> assumptions about: "only ever 64 or 127".
>

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

<div dir=3D"ltr">Host developers and users do care what the prefix length i=
s.<div><br></div><div>There are lots of things you can do if you know that =
the network will never run out of addresses. For example, you can form new =
addresses at will and use them for anything you want (privacy; per-applicat=
ion addresses, or whatever else you can think of). Read RFC 7934 for a list=
 of the things we&#39;ve thought of so far, and bear in mind that if this I=
Pv6 thing even only lasts as long as IPv4, that&#39;s still several decades=
, and I&#39;m sure we&#39;ll have lots of bright ideas during that time if =
we don&#39;t shortsightedly carry over IPv4 practices motivated by address =
scarcity.<div><br></div><div>A fixed prefix length is also very beneficial =
because it allows hosts to extend the network indefinitely at layer 2 witho=
ut giving up the benefits provided by autoconfiguration and end to end conn=
ectivity. It means that ill-informed or ill-intentioned network administrat=
ors cannot use addressing to constrain apps in a way that leads to suboptim=
al user experience. That sort of thing obviously does not happen in the 291=
4 or 15169 backbone. It does happen in lots of other places.</div></div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 22=
, 2017 at 1:44 PM, Christopher Morrow <span dir=3D"ltr">&lt;<a href=3D"mail=
to:christopher.morrow@gmail.com" target=3D"_blank">christopher.morrow@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r"><div><div class=3D"h5"><br><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <span dir=3D=
"ltr">&lt;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@g=
oogle.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span>On Wed=
, Feb 22, 2017 at 12:12 PM, Christopher Morrow <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:christopher.morrow@gmail.com" target=3D"_blank">christopher.mor=
row@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><span><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><di=
v class=3D"gmail_quote"><div>But the configuration cost and management over=
head is not proportional to the hosts that are served by those interconnect=
ions, it is proportional to the number of interconnections. A 10x100G peeri=
ng interconnection that serves X million hosts is one interface that has to=
 be managed.</div></div></div></div></blockquote><div><br></div></span><div=
>isn&#39;t the dicsussion here really:<br>=C2=A0 &quot;If you want to use /=
64 go ahead, if you want to use /121 go for it, if you want to use SLAAC yo=
u&#39;ll get a /64 and like it&quot;</div></div></div></div></blockquote><d=
iv><br></div></span><div>Not sure. I for one wouldn&#39;t agree with that p=
osition, because I don&#39;t see that /121 has enough advantages over /127 =
and /64 - and few enough downsides for general-purpose hosts - to make it a=
 good idea in general.</div></div></div></div>
</blockquote></div><br></div></div></div><div class=3D"gmail_extra">I don&#=
39;t think /121 is anymore special than /127... or /64. My point was we don=
&#39;t care what prefix people use, generally, that there are cases where a=
 /64 is required and that&#39;s fine, there are cases where /64 isn&#39;t a=
nd people can do what they want there.=C2=A0 It&#39;s simple enough to do S=
LAAC/64 on lans and other places.</div><div class=3D"gmail_extra"><br></div=
><div class=3D"gmail_extra">Requiring /64 or /127 and nothing else means wh=
en you do have to do a /120 or something else you MAY end up fighting vendo=
r problems because they made assumptions about: &quot;only ever 64 or 127&q=
uot;.</div></div>
</blockquote></div><br></div>

--001a1142f17833d3d305491f28bc--


From nobody Wed Feb 22 06:21:04 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B52012996B for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewRJdQrlNger for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:20:57 -0800 (PST)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::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 3888C129977 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:20:56 -0800 (PST)
Received: by mail-ua0-x231.google.com with SMTP id g30so2532538uac.3 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jZ2fdpfX/cx11QcavB/eYV0y/4uFYZglqhi2S1Xsqfc=; b=sDl41hJ19+0hQsavprYeZ3l40gX1NbNMn2B9wJ9HS98FiwNLBg486yNgh02bqzYtsE EsrLgX9aN/n6d4nqcaUH8biHwbbmGOmxgTtAIudYjYNAbYB3+EJh42qFD2EBix5m09L/ kWDHmfn5sT2GFTvM06VFBLqhObZrv/tf307vkhoXDMZ4zOWfXe60ZB1tQB53+orHcMxX Qum/PhOi+4AN3JdX91XAdy9oKDVIb6PUtNkxFTVKpEXDzoAruKeCmQsCMGniKnHgiTR3 hrZKl1f/xvy8BSLjI9nyzJ343hJ+DN34hiiQqUXI0/6fLu0ZVYM/pp3cF9B8eDE76a24 xdGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jZ2fdpfX/cx11QcavB/eYV0y/4uFYZglqhi2S1Xsqfc=; b=JPYUzeX1TBGLsqjtJHYrqYPgW86iv7a5b4WIt65JAscMObG+ArP60XwS2KhIzGxKFn IgaOADpRXw9x1r6rw1YzHZxGJlqyb3XXCJMx109FBAklclKzTYXtEPd/almiMf7wOjbz /NJSZgm8uqRShunw1gT/aZlbXHBOzL7z7nRimmo+n7+cjlGYFBFYdNmCJVdzPXU9SMbF 7YZLTVYOR3385lptSmzl9FMxRA2RRZ8cNx5KSwUslB+qDJXp1oqJlwL3LhkV7SzzMAFv iiwPudFUVznqqZoMo5U8nUdMhCmPOQWojX08zpsP33ggoXeW6+RnzFvaxDigsz5GD0XS +95A==
X-Gm-Message-State: AMke39mUeXFeqb6ruSctSlLSsUBRjx84v5JwJK8OW1GKeXKqtLyajHdfCI2ILjmOEMeJOXN5HGJ0+vhRl19wLged
X-Received: by 10.176.17.108 with SMTP id g44mr1124864uac.30.1487773254923; Wed, 22 Feb 2017 06:20:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 06:20:33 -0800 (PST)
In-Reply-To: <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 23:20:33 +0900
Message-ID: <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=f4030435b5705e1c3b05491f347f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EJKpYB1NzA9SPo98qof7R9h6zlM>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:20:58 -0000

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

On Wed, Feb 22, 2017 at 7:46 PM, Job Snijders <job@ntt.net> wrote:

> One of the immediate benefits of using a /126, is that it's not a /64!
>

That argument is nonsensical. You can't prove that A is better than B only
by saying that A is not the same as B.


> Also, a /126 is the smallest non-64 size with the highest likeliness to
> get the job done from an interoperability perspective (not the /127).
>

I don't see how you can simultaneously argue that /126 is good because
vendors don't implement the RFC 6164 and allow /127 AND that you want to
change the standard. If vendors don't implement the standard, then what
good does changing the standard do you?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Feb 22, 2017 at 7:46 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"=
mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div>
<div name=3D"messageBodySection">One of the immediate benefits of using a /=
126, is that it&#39;s not a /64!</div></div></blockquote><div><br></div><di=
v>That argument is nonsensical. You can&#39;t prove that A is better than B=
 only by saying that A is not the same as B.</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex"><div><div name=3D"messageBodySection">Also, a /126 i=
s the smallest non-64 size with the highest likeliness to get the job done =
from an interoperability perspective (not the /127).</div></div></blockquot=
e><div><br></div><div>I don&#39;t see how you can simultaneously argue that=
 /126 is good because vendors don&#39;t implement the RFC 6164 and allow /1=
27 AND that you want to change the standard. If vendors don&#39;t implement=
 the standard, then what good does changing the standard do you?</div></div=
></div></div>

--f4030435b5705e1c3b05491f347f--


From nobody Wed Feb 22 06:23:01 2017
Return-Path: <gregimirsky@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D997B129986; Wed, 22 Feb 2017 06:22:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xCYO-71jBVXs; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003: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 5959F12997F; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id s205so2135208oif.3; Wed, 22 Feb 2017 06:22:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XIgIgtg1qtkUPB8TWXfevsexZSXdwxv+QPqALa22ZRg=; b=eUy4JN3IxHRuelgIFTxIzJzyaNAkOrUwfCe15sY0VLrSmgpt7Z+OD/iEakyuVfbzyY GMXGw+U7saDsFmLsbC79pFRRXlBQBEfDvtX5UErsVwcjIOacmN2r1tOQbH1xniyjFWxH ZcelRg6/09GfUxgf25zgIVK72LHGHPjino2FdZpuUbn/TlU0/fwC95pOLjI2J3Vmgl7T nDDI+Hx1uwIDlMl+5yj0WDIj0HiDcl9L8e2HBXBh+DOxbrDJ6xyPBrhPrfFLGd9rexXk Huf74rw8KMMm4TlMNNNCSabfNdGWIvFnNXggzbUWg5uGDdyBqIIFx/jCEvpgbgz5YpJg cTKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XIgIgtg1qtkUPB8TWXfevsexZSXdwxv+QPqALa22ZRg=; b=r+LYy1CggyaM+G+TZ036N38AEpVcM5Ql5QBq7ldVHTXjRbe1Y36CacxBpDn2tUumY2 7i/coWwO6etH8k9DzLlUSg6hQ3bw3D/f0KTyyjawxRiadVMEnNNcuArAGs2aNuWx/ZIs cPotmM6j+ZdE37IAox6VRN5gOD6Qs/TCf75oVqkV0JtTFHKicnlvavVH5CYnHLu10XxL X2O9R55epHdpaV6zdDPyjZersW+UQyuUa64kT/bEOgzrG8nOO/HfED7JXtHoNj4opMI6 KcpUzTrgU1SjSgXuDXIKRzrfuzh8YzjFWJRBk/KNTz0eTSHnMHPSmzIY0ych/i5y7e+2 7sVg==
X-Gm-Message-State: AMke39lnd+Pr2gg7apyjvGBRy7BVDKb570RHYKWfFRWIwDSsZl/vV+7eAKycZ94WmklQIe5an1SdQ4pOhZvfNA==
X-Received: by 10.202.239.2 with SMTP id n2mr18668278oih.157.1487773368653; Wed, 22 Feb 2017 06:22:48 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.38.211 with HTTP; Wed, 22 Feb 2017 06:22:48 -0800 (PST)
In-Reply-To: <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
References: <148702270016.25055.10297552659599192833.idtracker@ietfa.amsl.com> <CA+RyBmWaTBNzycSyEu8BLCZA3jF2t-_vy3chosvrmurkamNEfQ@mail.gmail.com> <a812b604-89b0-b741-4ea8-e518259dbb17@nostrum.com> <CA+RyBmW8NcThCJt4WscccfTMr29JWa-7oPVaptvOdT1dgi+Q_A@mail.gmail.com> <e28d238c-f27f-6dd9-41a9-b0ff6e2fe272@nostrum.com> <CA+RyBmUzP9rDdq9un08GnY0Dzcq+0w-ty1_Fg=kGGHZ3af8JJQ@mail.gmail.com> <ca75efb7-d1ba-c9c7-593b-486dd41a7171@nostrum.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Wed, 22 Feb 2017 06:22:48 -0800
Message-ID: <CA+RyBmV=fCrv7NfbAXZ7VPj2ngX0h-6eO6EwY7h4CiWV8PgrAQ@mail.gmail.com>
Subject: Re: Review of draft-ietf-mpls-residence-time-13
To: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=94eb2c0931da251a7b05491f3b6d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uXr-BgzXSzdNxYwx7M3IaxCU3Zs>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-mpls-residence-time.all@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:22:52 -0000

--94eb2c0931da251a7b05491f3b6d
Content-Type: text/plain; charset=UTF-8

Hi Robert,
agreed. Thank you for your thorough review and the most helpful comments.
I'll upload the update shortly.

Regards,
Greg

On Wed, Feb 22, 2017 at 1:09 AM, Robert Sparks <rjsparks@nostrum.com> wrote:

> I would simply delete "To ensure precise accuracy in time determination"
> and start the sentence at "These actions"
>
> RjS
>
> On 2/15/17 9:40 PM, Greg Mirsky wrote:
>
> Hi Robert,
> safe travel and here's another version for your consideration. The point
> I'm trying to convey is that the jitter is real but must be accounted not
> as part of propagation delay but as residence time. Hope I'm getting close.
>
>    Each RTM-capable
>    node on the explicit path receives an RTM packet and records the time
>    at which it receives that packet at its ingress interface as well as
>    the time at which it transmits that packet from its egress interface.
>    To ensure precise accuracy in time determination these actions should
>    be done as close to the physical layer as possible at the same point
>    of packet processing striving to avoid introducing the appearance of
>    jitter in propogation delay whereas it should be accounted as
>    residence time.
>
> Regards,
>
> Greg
>
>
> On Wed, Feb 15, 2017 at 11:15 AM, Robert Sparks <rjsparks@nostrum.com>
> wrote:
>
>>
>>
>> On 2/15/17 11:20 AM, Greg Mirsky wrote:
>>
>> Hi Robert,
>> yes, you've absolutely correct in your example. The importance of RTM is
>> to exclude and quantify, as much as possible, jitter from propagation
>> delay. I've updated the wording to reflect that. Below is new text I
>> propose, please let me know if it makes it clearer.
>>
>>    Each RTM-capable
>>    node on the explicit path receives an RTM packet and records the time
>>    at which it receives that packet at its ingress interface as well as
>>    the time at which it transmits that packet from its egress interface.
>>    These actions should be done as close to the physical layer as
>>    possible at the same point of packet processing striving to avoid
>>    introduction of jitter in propogation delay to ensure precise
>>    accuracy in time determination.
>>
>> perhaps change "avoid introduction of jitter" to "avoid introducing the
>> appearance of jitter that's not really there"?
>>
>> (I'm about to board a plane, so further responses will be very delayed).
>>
>> Regards,
>>
>> Greg
>>
>>
>> On Wed, Feb 15, 2017 at 7:43 AM, Robert Sparks <rjsparks@nostrum.com>
>> wrote:
>>
>>>
>>>
>>> On 2/14/17 10:06 PM, Greg Mirsky wrote:
>>>
>>> Hi Robert,
>>> Section 5 Data Plane Theory of Operation has the following
>>> recommendation on reading time value at ingress and egress:
>>>
>>>    Each RTM-capable
>>>    node on the explicit path receives an RTM packet and records the time
>>>    at which it receives that packet at its ingress interface as well as
>>>    the time at which it transmits that packet from its egress interface;
>>>    this should be done as close to the physical layer as possible to
>>>    ensure precise accuracy in time determination.
>>>
>>> Do you find the text sufficient in providing guidance to an implementer of RTM?
>>>
>>> Well, no - that was point in the text from my review of -12 that caused
>>> me to make comment in the first place.
>>>
>>> What does "precise accuracy" even _MEAN_? You're waving your hands with
>>> words that don't help the reader guess what you mean at the moment. The
>>> subsequent email exchange said the important part was that you measure
>>> _precisely_ (in that the measurements are always taken the same way), but
>>> accuracy isn't that important (you've (and here by "you" I mean the set of
>>> people that have responded to the review") told me it's not important
>>> whether the reading is taken at the beginning of the bit-stream, the end,
>>> or several 1000 nanoseconds after the last bit came off the physical media
>>> as long as it's done the same way for each packet). The fact that you're
>>> carrying a measurement that can talk about times smaller than the
>>> interarrival time for individual bits for some real world line speeds says
>>> that different implementations taking the measurement different ways is
>>> going to result in different residence time measurements, even if the
>>> residence time was really identical. You've told me that's not important to
>>> the protocol using the measurement as long as the an individual
>>> implementation doesn't introduce something that will look to the using
>>> protocol like jitter that's not really there.
>>>
>>> The text does not say that to an implementer right now.
>>>
>>> To restate that long paragraph with maybe a longer one,  assume a
>>> simplified world where everything is perfectly constant. Packets are all
>>> flowing at the same size and same rate. For reference, I assert that the
>>> time between the first bit of a packet entering the system taking the
>>> measurement and the first bit of that packet leaving the system is exactly
>>> T (every time). You are telling me that if the system returns cT for some
>>> constant T other than 1 (and not necessarily  close to 1), everything is
>>> fine. You're also telling me that if you replace the system with another
>>> that preserves T, but measures differently so that it returns c'T where c'
>>> != c, everything is fine. The important part to you is that c and c' don't
>>> change for their respective systems. (That surprises me, I can see how the
>>> way the clocks are going to use this will do the right thing, but I can't
>>> help but think someone later will look at the difference between the two
>>> systems and say something is wrong with one of them). What you've told me
>>> is not fine is that if you drop i a third system that also preserves T but
>>> reports aT where a _varies_ over some range.
>>>
>>> Have I heard you correctly?
>>>
>>> Regards,
>>>
>>> Greg
>>>
>>>
>>> On Mon, Feb 13, 2017 at 1:51 PM, Robert Sparks <rjsparks@nostrum.com>
>>> wrote:
>>>
>>>> Reviewer: Robert Sparks
>>>> Review result: Ready
>>>>
>>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>>> by the IESG for the IETF Chair. Please wait for direction from your
>>>> document shepherd or AD before posting a new version of the draft.
>>>>
>>>> For more information, please see the FAQ at
>>>>
>>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>>
>>>> Document: draft-ietf-mpls-residence-time-13
>>>> Reviewer: Robert Sparks
>>>> Review Date: 2017-02-13
>>>> IETF LC End Date: 2017-01-17
>>>> IESG Telechat date: 2017-03-02
>>>>
>>>> Summary: Ready for publication as PS
>>>>
>>>> Thanks for addressing my comments.
>>>> (I still think some discussion about taking arrival and departure time
>>>> measurements would be helpful, even if it only said "do it
>>>> consistently so you don't indicate jitter that's not really there".)
>>>>
>>>>
>>>
>>>
>>
>>
>
>

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

<div dir=3D"ltr">Hi Robert,<div>agreed. Thank you for your thorough review =
and the most helpful comments. I&#39;ll upload the update shortly.</div><di=
v><br></div><div>Regards,</div><div>Greg</div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, Feb 22, 2017 at 1:09 AM, Robert =
Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=
=3D"_blank">rjsparks@nostrum.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <p>I would simply delete &quot;To ensure precise accuracy in time
      determination&quot; and start the sentence at &quot;These actions&quo=
t;</p>
    <p>RjS<br>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_-8072473529522433651moz-cite-prefix">On 2/15/17 9:40 PM=
, Greg Mirsky wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">Hi Robert,
        <div>safe travel and here&#39;s another version for your
          consideration. The point I&#39;m trying to convey is that the
          jitter is real but must be accounted not as part of
          propagation delay but as residence time. Hope I&#39;m getting
          close.</div>
        <div>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   To ensure precise accuracy in time determination these actions should
   be done as close to the physical layer as possible at the same point
   of packet processing striving to avoid introducing the appearance of
   jitter in propogation delay whereas it should be accounted as
   residence time. </pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Regards,</pre>
          <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;white-space:p=
re-wrap">Greg</pre>
        </div>
      </div>
      <div class=3D"gmail_extra"><br>
        <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at 11:15 AM,
          Robert Sparks <span dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@no=
strum.com" target=3D"_blank">rjsparks@nostrum.com</a>&gt;</span>
          wrote:<br>
          <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                <p><br>
                </p>
                <br>
                <div class=3D"m_-8072473529522433651m_2800513769154960288mo=
z-cite-prefix">On
                  2/15/17 11:20 AM, Greg Mirsky wrote:<br>
                </div>
              </span>
              <blockquote type=3D"cite">
                <div dir=3D"ltr">Hi Robert, <span>
                    <div>yes, you&#39;ve absolutely correct in your example=
.
                      The importance of RTM is to exclude and quantify,
                      as much as possible, jitter from propagation
                      delay. I&#39;ve updated the wording to reflect that.
                      Below is new text I propose, please let me know if
                      it makes it clearer.</div>
                    <div>
                      <pre style=3D"color:rgb(0,0,0);word-wrap:break-word;w=
hite-space:pre-wrap">   Each RTM-capable
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface.
   These actions should be done as close to the physical layer as
   possible at the same point of packet processing striving to avoid
   introduction of jitter in propogation delay to ensure precise
   accuracy in time determination.</pre>
                    </div>
                  </span></div>
              </blockquote>
              perhaps change &quot;avoid introduction of jitter&quot; to &q=
uot;avoid
              introducing the appearance of jitter that&#39;s not really
              there&quot;?<br>
              <br>
              (I&#39;m about to board a plane, so further responses will be
              very delayed). <br>
              <div>
                <div class=3D"m_-8072473529522433651h5">
                  <blockquote type=3D"cite">
                    <div dir=3D"ltr">
                      <div>
                        <pre style=3D"color:rgb(0,0,0);word-wrap:break-word=
;white-space:pre-wrap">Regards,</pre>
                        <pre style=3D"color:rgb(0,0,0);word-wrap:break-word=
;white-space:pre-wrap">Greg</pre>
                      </div>
                    </div>
                    <div class=3D"gmail_extra"><br>
                      <div class=3D"gmail_quote">On Wed, Feb 15, 2017 at
                        7:43 AM, Robert Sparks <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:rjsparks@nostrum.com" target=3D"_blank">rjsparks@nostrum.com</a=
>&gt;</span>
                        wrote:<br>
                        <blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
                          <div bgcolor=3D"#FFFFFF" text=3D"#000000"><span>
                              <p><br>
                              </p>
                              <br>
                              <div class=3D"m_-8072473529522433651m_2800513=
769154960288m_3072934530585377958moz-cite-prefix">On
                                2/14/17 10:06 PM, Greg Mirsky wrote:<br>
                              </div>
                              <blockquote type=3D"cite">
                                <div dir=3D"ltr">Hi Robert,
                                  <div>Section 5 Data Plane Theory of
                                    Operation has the following
                                    recommendation on reading time value
                                    at ingress and egress:</div>
                                  <div>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">   Each RTM-capa=
ble
   node on the explicit path receives an RTM packet and records the time
   at which it receives that packet at its ingress interface as well as
   the time at which it transmits that packet from its egress interface;
   this should be done as close to the physical layer as possible to
   ensure precise accuracy in time determination.  </pre>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Do you find the =
text sufficient in providing guidance to an implementer of RTM?</pre>
                                  </div>
                                </div>
                              </blockquote>
                            </span> Well, no - that was point in the
                            text from my review of -12 that caused me to
                            make comment in the first place.<br>
                            <br>
                            What does &quot;precise accuracy&quot; even _ME=
AN_?
                            You&#39;re waving your hands with words that
                            don&#39;t help the reader guess what you mean a=
t
                            the moment. The subsequent email exchange
                            said the important part was that you measure
                            _precisely_ (in that the measurements are
                            always taken the same way), but accuracy
                            isn&#39;t that important (you&#39;ve (and here =
by
                            &quot;you&quot; I mean the set of people that h=
ave
                            responded to the review&quot;) told me it&#39;s=
 not
                            important whether the reading is taken at
                            the beginning of the bit-stream, the end, or
                            several 1000 nanoseconds after the last bit
                            came off the physical media as long as it&#39;s
                            done the same way for each packet). The fact
                            that you&#39;re carrying a measurement that can
                            talk about times smaller than the
                            interarrival time for individual bits for
                            some real world line speeds says that
                            different implementations taking the
                            measurement different ways is going to
                            result in different residence time
                            measurements, even if the residence time was
                            really identical. You&#39;ve told me that&#39;s=
 not
                            important to the protocol using the
                            measurement as long as the an individual
                            implementation doesn&#39;t introduce something
                            that will look to the using protocol like
                            jitter that&#39;s not really there.<br>
                            <br>
                            The text does not say that to an implementer
                            right now.<br>
                            <br>
                            To restate that long paragraph with maybe a
                            longer one,=C2=A0 assume a simplified world whe=
re
                            everything is perfectly constant. Packets
                            are all flowing at the same size and same
                            rate. For reference, I assert that the time
                            between the first bit of a packet entering
                            the system taking the measurement and the
                            first bit of that packet leaving the system
                            is exactly T (every time). You are telling
                            me that if the system returns cT for some
                            constant T other than 1 (and not
                            necessarily=C2=A0 close to 1), everything is
                            fine. You&#39;re also telling me that if you
                            replace the system with another that
                            preserves T, but measures differently so
                            that it returns c&#39;T where c&#39; !=3D c,
                            everything is fine. The important part to
                            you is that c and c&#39; don&#39;t change for t=
heir
                            respective systems. (That surprises me, I
                            can see how the way the clocks are going to
                            use this will do the right thing, but I
                            can&#39;t help but think someone later will loo=
k
                            at the difference between the two systems
                            and say something is wrong with one of
                            them). What you&#39;ve told me is not fine is
                            that if you drop i a third system that also
                            preserves T but reports aT where a _varies_
                            over some range.<br>
                            <br>
                            Have I heard you correctly?<span><br>
                              <blockquote type=3D"cite">
                                <div dir=3D"ltr">
                                  <div>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Regards,</pre>
                                    <pre class=3D"m_-8072473529522433651m_2=
800513769154960288m_3072934530585377958gmail-newpage" style=3D"font-size:13=
.3333px;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)">Greg</pre>
                                  </div>
                                </div>
                                <div class=3D"gmail_extra"><br>
                                  <div class=3D"gmail_quote">On Mon, Feb
                                    13, 2017 at 1:51 PM, Robert Sparks <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:rjsparks@nostrum.com" target=3D"_blank"=
>rjsparks@nostrum.com</a>&gt;</span>
                                    wrote:<br>
                                    <blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer=
:
                                      Robert Sparks<br>
                                      Review result: Ready<br>
                                      <br>
                                      I am the assigned Gen-ART reviewer
                                      for this draft. The General Area<br>
                                      Review Team (Gen-ART) reviews all
                                      IETF documents being processed<br>
                                      by the IESG for the IETF Chair.
                                      Please wait for direction from
                                      your<br>
                                      document shepherd or AD before
                                      posting a new version of the
                                      draft.<br>
                                      <br>
                                      For more information, please see
                                      the FAQ at<br>
                                      <br>
                                      &lt;<a href=3D"https://trac.ietf.org/=
trac/gen/wiki/GenArtfaq" rel=3D"noreferrer" target=3D"_blank">https://trac.=
ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&gt;.<br>
                                      <br>
                                      Document:
                                      draft-ietf-mpls-residence-time<wbr>-1=
3<br>
                                      Reviewer: Robert Sparks<br>
                                      Review Date: 2017-02-13<br>
                                      IETF LC End Date: 2017-01-17<br>
                                      IESG Telechat date: 2017-03-02<br>
                                      <br>
                                      Summary: Ready for publication as
                                      PS<br>
                                      <br>
                                      Thanks for addressing my comments.<br=
>
                                      (I still think some discussion
                                      about taking arrival and departure
                                      time<br>
                                      measurements would be helpful,
                                      even if it only said &quot;do it<br>
                                      consistently so you don&#39;t indicat=
e
                                      jitter that&#39;s not really there&qu=
ot;.)<br>
                                      <br>
                                    </blockquote>
                                  </div>
                                  <br>
                                </div>
                              </blockquote>
                              <br>
                            </span></div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                  </blockquote>
                  <br>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div>

--94eb2c0931da251a7b05491f3b6d--


From nobody Wed Feb 22 06:42:43 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280741299AD; Wed, 22 Feb 2017 06:42:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 DLe53W_jbgP9; Wed, 22 Feb 2017 06:42:40 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 4EFA11299AC; Wed, 22 Feb 2017 06:42:40 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgY7c-0000ru-WA (job@us.ntt.net); Wed, 22 Feb 2017 14:42:39 +0000
Date: Wed, 22 Feb 2017 15:41:47 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170222144147.GC89584@hanna.meerval.net>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XLfi9Jwi1_2vbwNFyKwvSUX2deI>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:42:41 -0000

On Wed, Feb 22, 2017 at 11:20:33PM +0900, Lorenzo Colitti wrote:
> On Wed, Feb 22, 2017 at 7:46 PM, Job Snijders <job@ntt.net> wrote:
> > One of the immediate benefits of using a /126, is that it's not a /64!
> 
> That argument is nonsensical. You can't prove that A is better than B only
> by saying that A is not the same as B.

Since you are unwilling to accept that there could be downsides to using
a /64, i understand the argument makes no sense to you. Reasonable
people can disagree with each other.

> > Also, a /126 is the smallest non-64 size with the highest likeliness
> > to get the job done from an interoperability perspective (not the
> > /127).
> 
> I don't see how you can simultaneously argue that /126 is good because
> vendors don't implement the RFC 6164 and allow /127 AND that you want
> to change the standard. If vendors don't implement the standard, then
> what good does changing the standard do you?

Don't you see the common theme here? The "standard" is a red thread.

I'm advocating to align the Addressing Architecture documentation with
operational reality and operational expectations. If vendors support
/64-/127, and if operators use /64-/127 - then you should not insist
that anything non-/64 is invalid. Its not.

The 64-bit boundry is useful in some contexts [SLAAC], nobody is
disputing that. The boundry is not useful in every context, especially
in the case of explicit configuration, and the documentation should
reflect and acknowledge that fact. 

Why publish a document that conflicts with (almost) every deployed
global IPv6 backbone? This would be a farce.

Kind regards,

Job


From nobody Wed Feb 22 06:51:16 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2DE01299AF for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:51:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W_HWr96960IR for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:51:10 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 E2E161299C0 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:51:08 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 6E94ABC0 for <ietf@ietf.org>; Wed, 22 Feb 2017 14:51:08 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id crHfSdPOJD_M for <ietf@ietf.org>; Wed, 22 Feb 2017 08:51:08 -0600 (CST)
Received: from mail-ua0-f199.google.com (mail-ua0-f199.google.com [209.85.217.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 17767B60 for <ietf@ietf.org>; Wed, 22 Feb 2017 08:51:07 -0600 (CST)
Received: by mail-ua0-f199.google.com with SMTP id j56so2647442uaa.0 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:51:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ZAaBAQwVCfJCocCodAcABV30+P1KfJHhYQHIpwc5PYc=; b=j6qZ8ydyDBD6RU2VUTWmtKod6qagzLkBLdehEQCW8GwCKHusEaQztJPdisykBXU90r Xh6CaPeYMeOIk36JSO8PYWLl2nHYclml5bx95W+Q+4v0skP0Kec9P+LRJAJj2SRulqqW pVyD9EnpD7R1yM5Lxj/Rx8AGt2LrH/ro0pQKSDwVnlBZ1AYC2wlhTpMfC/VvnlI83tW+ 4uS7h879RKDveyJWpqMzZCyloUIZsk78kbz+2zh0Dyb9ys4ih95+lLxPvAjg3WYC1ryg HJTn8X61MSFYiZzOETtKcYVx4R1nNAz9teIA+SFQZcFoL55UdcJXTFF+x2KkcvhEq/Rh GQNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ZAaBAQwVCfJCocCodAcABV30+P1KfJHhYQHIpwc5PYc=; b=DBC94IuDOFYcCqESct4ku/CHpTgR6DmChZ7O9OLtpd4DeP0BVIYyepF1RcXMmMxE+i IiRSIU9nyNCUPD9N1p2UJyuOtPYQ3i5+qVXgETqVU3Qvyj500WW5jQ/uke30Q2ygQLmM DDFYr4LpuRwHYT03ChQ64hxYztu8OFWc9L+AP5Nksm8cvrY3wx/AcOsKFiw8kamqP4Od +suEPKeWsQIghjKi6ehtkA21rZWvXQdSFsJ14HU9AhfoFCHrJyFWv6Vbj5t+JUBZn0Mj /cPSxwmLaxmeRd7gEJCtlBNt75NFUDQAPn6CHBTMcq2q4SdgZ/Ld1lFhVg+iyy8DDi1z Diag==
X-Gm-Message-State: AMke39mRtG3sUaVZiSsBlAeQuc6Eco8c1RhwtCyZVK6l5HJuKLaWfpIVhaAwDjCZQieUP/jLAlSkDQdrGdWxPYNJSaesN9IakS6jSjfvQEFzc7CvlQRJymddMc/YeKCpjhb/rQmLj/vRPcVOb6s=
X-Received: by 10.31.204.197 with SMTP id c188mr16441295vkg.31.1487775067434;  Wed, 22 Feb 2017 06:51:07 -0800 (PST)
X-Received: by 10.31.204.197 with SMTP id c188mr16441280vkg.31.1487775067183;  Wed, 22 Feb 2017 06:51:07 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Wed, 22 Feb 2017 06:51:06 -0800 (PST)
In-Reply-To: <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 22 Feb 2017 08:51:06 -0600
Message-ID: <CAN-Dau2K9nOF_NnxEX1uLkjWuNJtcM-x4xwWm=1WAoY6QAjzXg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Christopher Morrow <christopher.morrow@gmail.com>
Content-Type: multipart/alternative; boundary=001a114dd5d062b21505491fa07e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XJoQH96nmO4f65E5J4r8FUmWiFk>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:51:12 -0000

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

On Tue, Feb 21, 2017 at 10:44 PM, Christopher Morrow <
christopher.morrow@gmail.com> wrote:
>
>
> On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <lorenzo@google.com>
> wrote:
>
>> On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <
>> christopher.morrow@gmail.com> wrote:
>>
>>> But the configuration cost and management overhead is not proportional
>>>> to the hosts that are served by those interconnections, it is proportional
>>>> to the number of interconnections. A 10x100G peering interconnection that
>>>> serves X million hosts is one interface that has to be managed.
>>>>
>>>
>>> isn't the dicsussion here really:
>>>   "If you want to use /64 go ahead, if you want to use /121 go for it,
>>> if you want to use SLAAC you'll get a /64 and like it"
>>>
>>
>> Not sure. I for one wouldn't agree with that position, because I don't
>> see that /121 has enough advantages over /127 and /64 - and few enough
>> downsides for general-purpose hosts - to make it a good idea in general.
>>
>
> I don't think /121 is anymore special than /127... or /64. My point was we
> don't care what prefix people use, generally, that there are cases where a
> /64 is required and that's fine, there are cases where /64 isn't and people
> can do what they want there.  It's simple enough to do SLAAC/64 on lans and
> other places.
>
> Requiring /64 or /127 and nothing else means when you do have to do a /120
> or something else you MAY end up fighting vendor problems because they made
> assumptions about: "only ever 64 or 127".
>

I have to disagree with Chis slightly, /127 and /64 are slightly special,
in that they are clearly RECOMMENDED and the others (/126 through /65)
are NOT RECOMMENDED.  The problem we have is that some people think it
isn't enough to say /64 is only RECOMMENDED and want something stronger,
the stronger option is REQUIRED, and the current and historic text says
"required".  On the other hand we have people saying REQUIRED is too
strong, because it implies that /126 through /65 are not possible to use,
which is demonstrably false.

There is no universal (Internet wide) requirement, to make the Internet
work, that all interfaces have /64 as their as their prefix.  In fact as a
host on the other side of the Internet from me, you are forbidden from
making that very assumption, you must treat my 128 IPv6 address as opaque.

Their is a local requirement that all interfaces on the same link have the
same prefix.  The easies way to achieve this is to assume a fixed prefix
everywhere, and we picked /64 for that, and built it into SLAAC.  Once we
picked it, we have also built a whole bunch of other things that depend on
that pick, many of those other things are discussed in RFC7421.

Is the operational effort to utilize other prefix lengths (/126 through
/65) justified, including the issues discussed in RFC7421?  Most of the
time, probably NO, but some times, YES it is.  Here is the crux of this
issue, some of you think it is never justified.  But tough, this simply is
not your call, and again on the other side of the Internet you are not
supposed to care anyway.

Furthermore, as currently written it is easy to misinterpret the text as
implying that a configuration of something other than /64 MUST be ignored
or overridden.  My preferred solution is to simply change "required" to
"recommended" in the current text. I'd also be ok with saying /64 is
required for SLAAC, and recommended for everything else. But, If current
"required" is kept for everything, then it needs to be clarified who the
requirement is directed at, and that there are other exceptions than just
addresses that begin with 000. I think something like the following would
would deal with the first part;

   Other than the implications for Stateless Address
Autoconfiguration(SLAAC)[RFC4862],
   this requirement primarily constrains operators of IPv6 networks and
does not imply
   implementations of IPv6 are to ignore or override a configuration that
is in conflict with
   this requirement.

And as has been talked about, for the second part we can enumerate the
exceptions or say that there are other standards track exceptions beyond
just the addresses that begin with 000.

Thanks.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Tue, Feb 21, 2017 at 10:44 PM, Christopher Morrow <span dir=3D"ltr">=
&lt;<a href=3D"mailto:christopher.morrow@gmail.com" target=3D"_blank">chris=
topher.morrow@gmail.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><br><div cl=
ass=3D"gmail_quote">On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lo=
renzo@google.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"=
gmail_quote"><span>On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:christopher.morrow@gmail.com" target=
=3D"_blank">christopher.morrow@gmail.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_extra"><div class=3D"gmail_quote"><span><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D=
"gmail_quote"><div>But the configuration cost and management overhead is no=
t proportional to the hosts that are served by those interconnections, it i=
s proportional to the number of interconnections. A 10x100G peering interco=
nnection that serves X million hosts is one interface that has to be manage=
d.</div></div></div></div></blockquote><div><br></div></span><div>isn&#39;t=
 the dicsussion here really:<br>=C2=A0 &quot;If you want to use /64 go ahea=
d, if you want to use /121 go for it, if you want to use SLAAC you&#39;ll g=
et a /64 and like it&quot;</div></div></div></div></blockquote><div><br></d=
iv></span><div>Not sure. I for one wouldn&#39;t agree with that position, b=
ecause I don&#39;t see that /121 has enough advantages over /127 and /64 - =
and few enough downsides for general-purpose hosts - to make it a good idea=
 in general.</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">I don&#39;t think /=
121 is anymore special than /127... or /64. My point was we don&#39;t care =
what prefix people use, generally, that there are cases where a /64 is requ=
ired and that&#39;s fine, there are cases where /64 isn&#39;t and people ca=
n do what they want there.=C2=A0 It&#39;s simple enough to do SLAAC/64 on l=
ans and other places.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Requiring /64 or /127 and nothing else means when you do h=
ave to do a /120 or something else you MAY end up fighting vendor problems =
because they made assumptions about: &quot;only ever 64 or 127&quot;.</div>=
</div>
</blockquote></div><br>I have to disagree with Chis slightly, /127 and /64 =
are slightly special, in that they are clearly RECOMMENDED and the others (=
/126 through /65) are=C2=A0NOT RECOMMENDED.=C2=A0 The problem we have is th=
at some people think it isn&#39;t enough to say /64 is only RECOMMENDED and=
 want something stronger, the stronger option is REQUIRED, and the current =
and historic text says &quot;required&quot;.=C2=A0 On the other hand we hav=
e people saying REQUIRED is too strong, because it implies that /126 throug=
h /65 are not possible to use, which is demonstrably false.</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">There is no universal=
 (Internet wide) requirement,=C2=A0to make the Internet work,=C2=A0that all=
 interfaces have /64 as their as their prefix.=C2=A0 In fact as a host on t=
he other side of the Internet from me, you are forbidden from making that v=
ery assumption, you must treat my 128 IPv6 address as opaque. =C2=A0</div><=
div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Their is a l=
ocal requirement that all interfaces on the same link have the same prefix.=
=C2=A0 The easies way to achieve this is to assume a fixed prefix everywher=
e, and we picked /64 for that, and built it into SLAAC.=C2=A0 Once we picke=
d it, we have also built a whole bunch of other things that depend on that =
pick, many of those other things are discussed in RFC7421. =C2=A0=C2=A0</di=
v><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Is the op=
erational effort to utilize other prefix lengths (/126 through /65) justifi=
ed, including the issues discussed in RFC7421?=C2=A0 Most of the time, prob=
ably=C2=A0NO, but some times, YES it is.=C2=A0 Here is the crux of this iss=
ue, some of you think it is never justified.=C2=A0 But tough, this simply i=
s not your call, and again on the other side of the Internet you are not su=
pposed to care anyway.</div><div class=3D"gmail_extra"><br></div><div class=
=3D"gmail_extra">Furthermore, as currently written it is easy to misinterpr=
et the text as implying that a configuration of something other than /64 MU=
ST be ignored or overridden.=C2=A0 My preferred solution is to simply chang=
e &quot;required&quot; to &quot;recommended&quot; in the current text. I&#3=
9;d also be ok with saying /64 is required for SLAAC, and recommended for e=
verything else. But, If current &quot;required&quot; is kept for everything=
, then it needs to be clarified who the requirement is directed at, and tha=
t there are other exceptions than just addresses that begin with 000. I thi=
nk something like the following would would deal with the first part;</div>=
<div class=3D"gmail_extra"><div><br></div><div>=C2=A0 =C2=A0Other than the =
implications for Stateless Address Autoconfiguration(SLAAC)[RFC48<wbr>62],=
=C2=A0</div><div>=C2=A0 =C2=A0this requirement primarily constrains operato=
rs of IPv6 networks and does not imply</div><div>=C2=A0 =C2=A0implementatio=
ns of IPv6 are to ignore or override a configuration that is in conflict wi=
th</div><div>=C2=A0 =C2=A0this requirement. =C2=A0<br></div><div><br></div>=
<div>And as has been talked about, for the second part we can enumerate the=
 exceptions or say that there are other standards track exceptions beyond j=
ust the addresses that begin with 000. =C2=A0</div><div><br></div><div>Than=
ks.</div><div><br></div>-- <br><div class=3D"gmail-m_5462672776644529676m_5=
975801330111488836gmail-m_5148934756150405796gmail-m_1102256779016955324gma=
il-m_8427343652719326708gmail_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu=
" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; Telecommun=
ication Services<br>Office of Information Technology<br>University of Minne=
sota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phon=
e: <a href=3D"tel:(612)%20626-0815" value=3D"+16126260815" target=3D"_blank=
">612-626-0815</a><br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=
=3D"tel:(612)%20812-9952" value=3D"+16128129952" target=3D"_blank">612-812-=
9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D </div>
</div></div>

--001a114dd5d062b21505491fa07e--


From nobody Wed Feb 22 06:54:07 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9411D1299CA for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HdTONg4mKd3f for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 06:53:54 -0800 (PST)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 4F2751299DC for <ietf@ietf.org>; Wed, 22 Feb 2017 06:53:51 -0800 (PST)
Received: by mail-vk0-x230.google.com with SMTP id t8so2884343vke.3 for <ietf@ietf.org>; Wed, 22 Feb 2017 06:53:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hhN7oueNyaqvwLGrRskeJ04PTOPHQK6LbfEdbVzsgcI=; b=ST7zq83T9jlDOv3kmThimDDrG7kQ/UK+pygB7nDI7yZdzI7K0tyRJgV91osya6xIRs VBM/DCgbGdUZKnFxaqcrR3kqq7qiVaV1a/1NrlgXlUe6qcXsRSgke9oEMGejPKInCE9+ 0TCMp8NplQsjR1Jb97P7vf3u+9y4R2E19nfejt9dM07IEKMcVlumE1xhFmJPj4atIlfh E6aDtRGwV2PN4vpT7uc87ebWkiyaT9HR0Rm5QNphAesTdFJYRkK6o7EGvJnqarmiQWJ5 0dMeM67Qe9mGeTW8AkZzXYe+M/IXisIPl79zE4w+LFmj4AUAIp7Eknn7suHbMJxz30nj i3Bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hhN7oueNyaqvwLGrRskeJ04PTOPHQK6LbfEdbVzsgcI=; b=EAamsnA++XIkJD5GN0ZdL14ZAAU6rHpIbavk5nrzkhiOFcBBkTIcJm2CGTF9E/RGac VOvp0EDlfS49w0ifx3BqGUL12fnWfmUQ2DVP1DxV9ZIFIETXFoKXPw475AlH7A+1ol2x ASWt6YUCsUk8197IJsoy7iqYBmfx6oaUcV3EzQHmh8Wdp5SdEjspEbLyHgEP1RIOz9FN wftHFpHSUxm6dp7CXZHBuRG6uLuDRxTWaOrKynSki+OaNGv3oRUQjSzp6ZnyBraXljZd 8CQHrqOp8zZnmxMmj80Imxt7fjUnqojqqZ2yzjdxmICs3V6Her4kY5AB3wlfWpWR4tUX 7Qnw==
X-Gm-Message-State: AMke39kRerEMopharCrObfFsqEyy3Uokwkzy7LHY3Dt9DN0dCg9JiyeLmG0uM2rSG+oeChSaqYyxhpcaRsfurm6M
X-Received: by 10.31.59.197 with SMTP id i188mr12296425vka.45.1487775230170; Wed, 22 Feb 2017 06:53:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 06:53:29 -0800 (PST)
In-Reply-To: <20170222144147.GC89584@hanna.meerval.net>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 22 Feb 2017 23:53:29 +0900
Message-ID: <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=001a1142f1781a0c0905491faa52
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZuIw2y68BUiqVcUr3GUUl4qmKbs>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 14:53:55 -0000

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

On Wed, Feb 22, 2017 at 11:41 PM, Job Snijders <job@ntt.net> wrote:

> > That argument is nonsensical. You can't prove that A is better than B
> only
> > by saying that A is not the same as B.
>
> Since you are unwilling to accept that there could be downsides to using
> a /64, i understand the argument makes no sense to you. Reasonable
> people can disagree with each other.
>

I stand by the position that "/126 is better than /64 because /126 is not
/64" is a nonsensical argument. Saying "/126 is better than /64 due to
reasons A, B, C, ..." will likely be more effective - well, depending on
what A, B and C are. But I haven't heard much in the way of supporting
evidence from you other than "my network uses lots of prefix lengths thus
/64 is bad". That in itself is not convincing to me. Perhaps I am missing
something else you said?



> Why publish a document that conflicts with (almost) every deployed
> global IPv6 backbone? This would be a farce.
>

"Conflicts with the NTT backbone" != "conficts with almost every deployed
backbone". The backbone I am familiar with uses a combination of /127, /64,
and link-local point to point interfaces, or at least it did last time I
checked.

Also, backbone networks are a tiny percentage of the links on the planet.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Feb 22, 2017 at 11:41 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D=
"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><span>&gt; That argument is nonsensical. Yo=
u can&#39;t prove that A is better than B only<br>
&gt; by saying that A is not the same as B.<br>
<br>
</span>Since you are unwilling to accept that there could be downsides to u=
sing<br>
a /64, i understand the argument makes no sense to you. Reasonable<br>
people can disagree with each other.<br></blockquote><div><br></div><div>I =
stand by the position that &quot;/126 is better than /64 because /126 is no=
t /64&quot; is a nonsensical argument. Saying &quot;/126 is better than /64=
 due to reasons A, B, C, ...&quot; will likely be more effective - well, de=
pending on what A, B and C are. But I haven&#39;t heard much in the way of =
supporting evidence from you other than &quot;my network uses lots of prefi=
x lengths thus /64 is bad&quot;. That in itself is not convincing to me. Pe=
rhaps I am missing something else you said?</div><div><br></div><div>=C2=A0=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex">Why publish a document that confli=
cts with (almost) every deployed<br>
global IPv6 backbone? This would be a farce.<br></blockquote><div><br></div=
><div>&quot;Conflicts with the NTT backbone&quot; !=3D &quot;conficts with =
almost every deployed backbone&quot;. The backbone I am familiar with uses =
a combination of /127, /64, and link-local point to point interfaces, or at=
 least it did last time I checked.</div><div><br></div><div>Also, backbone =
networks are a tiny percentage of the links on the planet.</div></div></div=
></div>

--001a1142f1781a0c0905491faa52--


From nobody Wed Feb 22 07:17:12 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2E9C129970 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:17:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.333
X-Spam-Level: 
X-Spam-Status: No, score=-4.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 U_3HWRCpX9g6 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:17:10 -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 C73831299F3 for <ietf@ietf.org>; Wed, 22 Feb 2017 07:17: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 v1MFH7qF026229 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:17:07 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E90BA206F4A for <ietf@ietf.org>; Wed, 22 Feb 2017 16:17:07 +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 DFEBF2033B5 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:17:07 +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 v1MFH7c0032080 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:17:07 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com> <CAKD1Yr2yjH9SGtBv2pJPEtceBWo=4+vobAV1o1JBjVpcNLXmcA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <bd63b751-6243-d5b6-93b0-afbed70a3ecd@gmail.com>
Date: Wed, 22 Feb 2017 16:17:00 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr2yjH9SGtBv2pJPEtceBWo=4+vobAV1o1JBjVpcNLXmcA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zDS_Di_tZ6v6yhUS09Li979jFRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 15:17:12 -0000

Le 22/02/2017 à 15:17, Lorenzo Colitti a écrit :
[...]
> A fixed prefix length is also very beneficial because it allows hosts
> to extend the network indefinitely at layer 2 without giving up the
> benefits provided by autoconfiguration and end to end connectivity.

I would agree bridging can extend to some extent.  But not indefinitely.

I would argue routing extends beyond what bridging can extend.

> It means that ill-informed or ill-intentioned network administrators
>  cannot use addressing to constrain apps in a way that leads to
> suboptimal user experience.

Maybe well-intentioned admins consider DHCP too, because it does not
have that /64 limit.

I have seen DHCPv6 running fast on smartphones on cellular links.

> That sort of thing obviously does not happen in the 2914 or 15169
> backbone. It does happen in lots of other places.

2914, 15169?

Alex

>
> On Wed, Feb 22, 2017 at 1:44 PM, Christopher Morrow
> <christopher.morrow@gmail.com <mailto:christopher.morrow@gmail.com>>
>  wrote:
>
>
>
> On Tue, Feb 21, 2017 at 10:51 PM, Lorenzo Colitti <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
>
> On Wed, Feb 22, 2017 at 12:12 PM, Christopher Morrow
> <christopher.morrow@gmail.com <mailto:christopher.morrow@gmail.com>>
>  wrote:
>
> But the configuration cost and management overhead is not
> proportional to the hosts that are served by those interconnections,
>  it is proportional to the number of interconnections. A 10x100G
> peering interconnection that serves X million hosts is one interface
>  that has to be managed.
>
>
> isn't the dicsussion here really: "If you want to use /64 go ahead,
> if you want to use /121 go for it, if you want to use SLAAC you'll
> get a /64 and like it"
>
>
> Not sure. I for one wouldn't agree with that position, because I
> don't see that /121 has enough advantages over /127 and /64 - and few
> enough downsides for general-purpose hosts - to make it a good idea
> in general.
>
>
> I don't think /121 is anymore special than /127... or /64. My point
> was we don't care what prefix people use, generally, that there are
> cases where a /64 is required and that's fine, there are cases where
> /64 isn't and people can do what they want there.  It's simple enough
> to do SLAAC/64 on lans and other places.
>
> Requiring /64 or /127 and nothing else means when you do have to do a
> /120 or something else you MAY end up fighting vendor problems
> because they made assumptions about: "only ever 64 or 127".
>
>


From nobody Wed Feb 22 07:22:23 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17052129A0F for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:22:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m9evqxOl2OJ7 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:22:21 -0800 (PST)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 419FE129A0B for <ietf@ietf.org>; Wed, 22 Feb 2017 07:22:19 -0800 (PST)
Received: by mail-vk0-x22a.google.com with SMTP id k127so3477904vke.0 for <ietf@ietf.org>; Wed, 22 Feb 2017 07:22:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=ovAjBDctGwVM5OPLtQxwT6xz4KPyD5uLzTYROzlqzec=; b=bV6kZpsQmc1F9MYOepCpHUli2awSRwQlTsxFHdUvYfvynO4iVCIUGH9X2+6crrAxqn GOQUvdMNAt/obLq464iXvGys2FsXAQ7BocRoMaVU/H6oWNY/U01g91W/jsV+tAyJ5y3t zK3e4dih+sYznnALIFZnaSVnH59ow4X+gkHtLX8j3bR4kiefZ8dy2BLysJZZQAy4bmE6 yZnot2bUrP2n/8GChwmqu71s9CTaVC89l31aN0RU7pm4eqJeBJtrO5EkwZJ+A2fQU1L7 j7xW6/E0QJXJQDQoI/eH/Y2qvO0h18fi7KEaF+ZVOZjuCP3HIGj9C9CXshPw2aISb4df mG0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=ovAjBDctGwVM5OPLtQxwT6xz4KPyD5uLzTYROzlqzec=; b=F8kKZkNyMQ1U9lyLOTFmGyB15iE9c0++BMOZRqS8vKu0hj6alRDrGdNfcx4ZOqs4K3 JcnyqA1oAGDO31V1mx5TvEU9mT6aRK5nsTlsn6E7jRYXME1cuoWISBWouCAjTUXj8Tjm X9Wz50SnzZvfdUW/TOCfu6ZJbPexC9wipjwI9C5SODV6OMqQrBIXvEZh+DOJ+aetLCkC /HyQwLCcS1aEX3NXLK9b8OapI0jX366zRoh95p/qYzfQFR5h6l4ea3YMgIxqbSL3Kozu wjEvAb4STALxIRcUoJBn969KtLJE78Pg/UBPW4v0D4g61GosO+Uf81OpdvF4wNub/jXh tusQ==
X-Gm-Message-State: AMke39n0xF9Sle8GVhDppXRtg5U6TZtSh4Nm4Kr94Abnz9AYYTAUXh9VY5uvY9B6goRZx0Ji6/Ae7j6dgK23+Vb2
X-Received: by 10.31.142.68 with SMTP id q65mr16161253vkd.83.1487776937955; Wed, 22 Feb 2017 07:22:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 07:21:56 -0800 (PST)
In-Reply-To: <CAN-Dau2K9nOF_NnxEX1uLkjWuNJtcM-x4xwWm=1WAoY6QAjzXg@mail.gmail.com>
References: <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <CAL9jLaY-7JqeNqotWsrQZ6JqNJ9NdzQT8Jt7Pd_YZwCpNgk6VQ@mail.gmail.com> <CAN-Dau2K9nOF_NnxEX1uLkjWuNJtcM-x4xwWm=1WAoY6QAjzXg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 00:21:56 +0900
Message-ID: <CAKD1Yr3LTYQjbMofphBi7Z_2zHMuK2T_YcQ7S73JSKGfSu3Zhg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=001a1143703ae4b0d40549200f60
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R2ncVnjEcRCe7lc0oLFah2lUQVg>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 15:22:22 -0000

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

On Wed, Feb 22, 2017 at 11:51 PM, David Farmer <farmer@umn.edu> wrote:

> There is no universal (Internet wide) requirement, to make the Internet
> work, that all interfaces have /64 as their as their prefix.
>

Where "make the Internet work" means what, exactly? I assume you don't mean
"experiences no loss in functionality" - all it takes is one implementation
that breaks when configured with a non-/64 prefix to make the statement
false.

That might seem like a specious distinction, but if you think about it more
broadly, then I think you'll agree that "work" is not black and white, and
also covers degraded functionality. In which case it's absolutely true that
moving away from /64 everywhere is going to cause some amount of loss of
functionality. The question is how much, and whether that's acceptable.


> Their is a local requirement that all interfaces on the same link have the
> same prefix.
>

Actually, there isn't. The requirement for working communication is that
all hosts are configured with a prefix length that covers all hosts on the
link (or, more narrowly, all hosts they want to talk to). It IS a
requirement in IPv4 because of the broadcast address, but it's not in IPv6.
Again, this might seem like nitpicking, but if you think about it some
more, I think you might realize that some of what is being written on this
thread is based on unstated assumptions that are not necessarily correct,
and in many cases based only on IPv4 practices where they were actually
necessary for reasons that are no longer applicable in IPv6.


> Is the operational effort to utilize other prefix lengths (/126 through
> /65) justified, including the issues discussed in RFC7421?  Most of the
> time, probably NO, but some times, YES it is.  Here is the crux of this
> issue, some of you think it is never justified.
>

I think this is where the disconnect lies. As a host OS developer and app
developer, my work is not impacted by what you, Job, or Chris, individually
do in your networks. My work is impacted by the minimum common denominator,
because that is what constrains the code I need to write.

If we don't have a fixed subnet size, that minimum common denominator
quickly ends up being /128-to-the-host. I don't want to end up at /128
because it makes my code more complex and brittle and my users' experience
much more battery intensive and less reliable. (Again, see RFC 7934.)

If we do have a fixed subnet size, and the only loss is that that backbone
operators cannot use RFC 4291bis to complain if host vendors refuse to
implement configuring /117 prefixes on their links, then I truly believe
that that is a better outcome for the Internet as a whole. As you point
out, /117 already "works", anyway - at least in your definition of "works".

When I was still involved in writing its addressing plans, the backbone I
am familiar with ran on a mix of /127, link-local point to point, and
/64-to-the-rack with some operational measures to defend against ND cache
exhaustion attacks. I never found the lack of /117 prefix lengths to be a
limitation.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On W=
ed, Feb 22, 2017 at 11:51 PM, David Farmer <span dir=3D"ltr">&lt;<a href=3D=
"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_=
extra">There is no universal (Internet wide) requirement,=C2=A0to make the =
Internet work,=C2=A0that all interfaces have /64 as their as their prefix.<=
/div></div></blockquote><div><br></div><div>Where &quot;make the Internet w=
ork&quot; means what, exactly? I assume you don&#39;t mean &quot;experience=
s no loss in functionality&quot; - all it takes is one implementation that =
breaks when configured with a non-/64 prefix to make the statement false.</=
div><div><br></div><div>That might seem like a specious distinction, but if=
 you think about it more broadly, then I think you&#39;ll agree that &quot;=
work&quot; is not black and white, and also covers degraded functionality. =
In which case it&#39;s absolutely true that moving away from /64 everywhere=
 is going to cause some amount of loss of functionality. The question is ho=
w much, and whether that&#39;s acceptable.</div><div>=C2=A0<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">Their =
is a local requirement that all interfaces on the same link have the same p=
refix.</div></div></blockquote><div><br></div><div>Actually, there isn&#39;=
t. The requirement for working communication is that all hosts are configur=
ed with a prefix length that covers all hosts on the link (or, more narrowl=
y, all hosts they want to talk to). It IS a requirement in IPv4 because of =
the broadcast address, but it&#39;s not in IPv6. Again, this might seem lik=
e nitpicking, but if you think about it some more, I think you might realiz=
e that some of what is being written on this thread is based on unstated as=
sumptions that are not necessarily correct, and in many cases based only on=
 IPv4 practices where they were actually necessary for reasons that are no =
longer applicable in IPv6.</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">Is the operational effort =
to utilize other prefix lengths (/126 through /65) justified, including the=
 issues discussed in RFC7421?=C2=A0 Most of the time, probably=C2=A0NO, but=
 some times, YES it is.=C2=A0 Here is the crux of this issue, some of you t=
hink it is never justified.</div></div></blockquote><div><br></div><div>I t=
hink this is where the disconnect lies. As a host OS developer and app deve=
loper, my work is not impacted by what you, Job, or Chris, individually do =
in your networks. My work is impacted by the minimum common denominator, be=
cause that is what constrains the code I need to write.</div><div><br></div=
><div>If we don&#39;t have a fixed subnet size, that minimum common denomin=
ator quickly ends up being /128-to-the-host. I don&#39;t want to end up at =
/128 because it makes my code more complex and brittle and my users&#39; ex=
perience much more battery intensive and less reliable. (Again, see RFC 793=
4.)</div><div><br></div><div>If we do have a fixed subnet size, and the onl=
y loss is that that backbone operators cannot use RFC 4291bis to complain i=
f host vendors refuse to implement configuring /117 prefixes on their links=
, then I truly believe that that is a better outcome for the Internet as a =
whole. As you point out, /117 already &quot;works&quot;, anyway - at least =
in your definition of &quot;works&quot;.</div><div><br></div><div>When I wa=
s still involved in writing its addressing plans, the backbone I am familia=
r with ran on a mix of /127, link-local point to point, and /64-to-the-rack=
 with some operational measures to defend against ND cache exhaustion attac=
ks. I never found the lack of /117 prefix lengths to be a limitation.</div>=
</div></div></div>

--001a1143703ae4b0d40549200f60--


From nobody Wed Feb 22 07:32:22 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776F1129A1E; Wed, 22 Feb 2017 07:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 aEBcqH_Jd3iE; Wed, 22 Feb 2017 07:32:19 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 8E8AE129A1C; Wed, 22 Feb 2017 07:32:19 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgYtk-0005xc-4W (job@us.ntt.net); Wed, 22 Feb 2017 15:32:18 +0000
Date: Wed, 22 Feb 2017 16:31:29 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170222153129.GE89584@hanna.meerval.net>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bJs79R_u4-Q1WSPJIBEVTtvWQQM>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 15:32:20 -0000

On Wed, Feb 22, 2017 at 11:53:29PM +0900, Lorenzo Colitti wrote:
> On Wed, Feb 22, 2017 at 11:41 PM, Job Snijders <job@ntt.net> wrote:
> > > That argument is nonsensical. You can't prove that A is better
> > > than B only by saying that A is not the same as B.
> >
> > Since you are unwilling to accept that there could be downsides to
> > using a /64, i understand the argument makes no sense to you.
> > Reasonable people can disagree with each other.
> 
> I stand by the position that "/126 is better than /64 because /126 is
> not /64" is a nonsensical argument. Saying "/126 is better than /64
> due to reasons A, B, C, ..." will likely be more effective - well,
> depending on what A, B and C are. But I haven't heard much in the way
> of supporting evidence from you other than "my network uses lots of
> prefix lengths thus /64 is bad". That in itself is not convincing to
> me. Perhaps I am missing something else you said?

Apologies to the working group for having to repeat these refences
again.

rfc6164 and rfc6583 are great examples that document considerations
regarding not using a /64, it simply is not always the best fit. Their
very existence show me that one can legitimately state "i want to use
something other then a /64".

The tandem of RFC 3627 and RFC 6164 is what caused both /126 and /127 to
become popular in operational circles. While /126 does not enjoy the
same recognised status as /127 from an IETF paperwork perspective, that
doesn't invalidate its use and existence.

Of course it is possible that two people look at the same data and
arrive at different conclusions.

> > Why publish a document that conflicts with (almost) every deployed
> > global IPv6 backbone? This would be a farce.
> >
> 
> "Conflicts with the NTT backbone" != "conficts with almost every
> deployed backbone".

You gross over the fact that NTT connects with many other backbones, and
that the data I shared is a reflection on both NTT's own addressing
structure as well as peering partner's or customer's addressing. When
NTT interconnects with another network, both parties have to agree on a
prefix and prefix length, and which party will use what IP address.
Thus, if the other party proposes and configures a /126, NTT will also
configure a /126.

As such, I am confident to state that almost every deployed backbone
uses a mixture of /64, /127, /126 and perhaps other lengths. This
information can also be gleaned from public resources such as PeeringDB,
public BGP Looking Glasses and hallway conversations at IETF.

> The backbone I am familiar with uses a combination of /127, /64, and
> link-local point to point interfaces, or at least it did last time I
> checked.

There is public data that suggests that the backbone you are familiar
with might be connected to a public internet exchange which uses a /112
as peering lan prefix. I hope this won't cause an existential crisis!

Of course one such anecdotal datapoint is worthless, and perhaps it is
childish of me to bring it up. I hope you'll share my amazement at all
the curious things that together form the internet. :-)

The key point here is that there is a larger pattern of '/64 avoidance'
amongst internet backbone operators, and that needs to be acknowledged
in the Addressing Architecture document. There have been numerous
suggestions to improve the text.

> Also, backbone networks are a tiny percentage of the links on the planet.

I certainly will not deny that fact. Are you familiar with the concept
of the McNamara fallacy?

Kind regards,

Job


From nobody Wed Feb 22 07:53:22 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BF28129A37; Wed, 22 Feb 2017 07:53:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9] autolearn=ham autolearn_force=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 sSCYbfwp9Gyx; Wed, 22 Feb 2017 07:53:17 -0800 (PST)
Received: from m67.nomadiclab.com (gw.nomadiclab.com [193.234.218.122]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id C9ECD12996B; Wed, 22 Feb 2017 07:53:15 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Agenda and connection details for the IASA 2.0 workshops
From: IETF Chair <chair@ietf.org>
In-Reply-To: <148701676326.25013.13898050851695958169.idtracker@ietfa.amsl.com>
Date: Wed, 22 Feb 2017 17:53:10 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F30556FA-0F6C-4B6C-A824-32682C0435B5@ietf.org>
References: <148701676326.25013.13898050851695958169.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EfcE0FXGxU96KG_CQp6buo_WPsg>
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 15:53:21 -0000

This is the promised update on the workshop arrangements. The two
workshops are both on Tuesday February 28. The first one is at 11:00 UTC
(6:00AM ET / 12:00 noon CET) and chaired by Gonzalo Camarillo. The
second one is at 16:00 UTC (11:00AM ET / 17:00 CET) and chaired
by Leslie Daigle.=20

The workshops run for 90 minutes. We have reserved most of the time for =
input
from you all, under specific topics, and this is the planned agenda:

1. Introduction (10m)
2. Staff and volunteer resource issues (20m)
3. Structural issues between the IETF, the IAOC, ISOC, the IESG,
    and contractors (15m)
4. Internal IAOC organizational issues (15m)
5. Funding issues (20m)
6. Parking lot / AOB (10m)

Meeting notes and an Internet Draft  summarising the input will be
produced afterwards.

The connection details are as follows:

> IASA 2.0: Challenges and Opportunities Workshop 1
> Tuesday, February 28, 2017
> 3:00 am  |  Pacific Standard Time (San Francisco, GMT-08:00)  |  1 hr =
30 mins
> Meeting number (access code): 649 641 309
> Meeting password: r3Kp3YK2
>=20
> When it's time, join the meeting: =
https://ietf.webex.com/ietf/j.php?MTID=3Dm1687ad2470da2686c579d370065e32e0=

>=20
> Join by phone
> 1-877-668-4493 Call-in toll free number (US/Canada)
> 1-650-479-3208 Call-in toll number (US/Canada)
> Toll-free calling restrictions

> IASA 2.0: Challenges and Opportunities Workshop 2
> Tuesday, February 28, 2017
> 8:00 am  |  Pacific Standard Time (San Francisco, GMT-08:00)  |  1 hr =
30 mins
> Meeting number (access code): 643 841 805
> Meeting password: QhbTb6Xy
>=20
> When it's time, join the meeting: =
https://ietf.webex.com/ietf/j.php?MTID=3Dmd2b82b329c773944216f99c3aa2ba9fa=

>=20
> Join by phone
> 1-877-668-4493 Call-in toll free number (US/Canada)
> 1-650-479-3208 Call-in toll number (US/Canada)
> Toll-free calling restrictions


We=92ve also set up a mailing list for discussions related to this topic =
at
https://www.ietf.org/mailman/listinfo/iasa20

Jari Arkko, IETF Chair


From nobody Wed Feb 22 07:57:11 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 658CB129A47 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NFgiolWBdXO4 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 07:57:07 -0800 (PST)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::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 6CEFF129A3B for <ietf@ietf.org>; Wed, 22 Feb 2017 07:57:07 -0800 (PST)
Received: by mail-ua0-x231.google.com with SMTP id c32so4504315uac.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 07:57:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2/tnWnIvuYT4QcpDrle9xMCLJ646fRHxwpe1Ty8TAJA=; b=vezZeEIlBZ5bXXgi7DO8MUH9u1+Pednu76w6jeFrNYnyEj/Sn026rRHStmlDYKJq6t Ku5n5hx26CgoaBr9xKk8kX2k3sy/fWlk2VETJWAknoFmWZw3DrrVeSEOu7UYvi9GBewR fGz6qWs6h2bd7c6pyjkykxI6UNFCv+f5YNpV8J2jb3vbtmll8s1zuYg2mVKcPHOtbL6v 5rcTeF/5umjfKoZhiaJzMEnMOrJpJjzN3LYgsFJDx5v6NF4LLBUls0IxddUAd3bOOfZH xHMHuuY7vFiU3pUjQHHLRjlS2dGgAunllxxqLou5HSYwOuXODtOkhRackovBcdb6Hh3g Gpzg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2/tnWnIvuYT4QcpDrle9xMCLJ646fRHxwpe1Ty8TAJA=; b=E9n4ljBnpxJT8BtNJ0PQhibsjA8wZyMbQ/Yh28cA1yoIgokKle7COcdLtNTQVW5+1j TtcfyLRcpIrON8qO7IeTjnuW+GL1dZuQKiIS2HTj3u+uLJvP3HfVWz4mu2fH0dF0bIaO CY0ZQDNKmK3c0O77rO2j8dDJHbmpy3kvcTz5qXb18HyjzXDVyCv4ouMs+2i8etr7zAG5 GyfzdPNL2ytBwEG7tk9H+szW9xQ5op125G2Gqsl3k9uqUKEIa+civtCr52DY5LEiQxPa hI07o0mdKisKBbQtMIbskvASUrQF3B8NFjtcdpiyWZeFu4tcCVKQwheec0y0s/QWWVC8 7wnQ==
X-Gm-Message-State: AMke39lU83J3hSV6IenDfH1bP/VRPR4LeV5L7c1xu+O4/9zaBoKYRXbN2VFGJUqeBEioECHZ2k1h45irkW2ztN2n
X-Received: by 10.176.8.4 with SMTP id a4mr255664uaf.171.1487779026289; Wed, 22 Feb 2017 07:57:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 07:56:45 -0800 (PST)
In-Reply-To: <20170222153129.GE89584@hanna.meerval.net>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 00:56:45 +0900
Message-ID: <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=f403045ee7785e73b70549208cc5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N1ONGmeDebsRKmU6WPwF22DjCLA>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 15:57:09 -0000

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

On Thu, Feb 23, 2017 at 12:31 AM, Job Snijders <job@ntt.net> wrote:

> rfc6164 and rfc6583 are great examples that document considerations
> regarding not using a /64, it simply is not always the best fit.
>

RFC6583-style attacks (of which the class addressed by RFC6164 is a subset)
are low payoff and pretty easy to mitigate using very small changes to ND
implementations. You can solve most or all of the problem by using
per-interface ND queues and prioritizing existing and gleaned ND entries
over incomplete ones. You can do even better by pushing the filtering away
from the host so that you don't have to carry the packets.

Also, bear in mind that the interface ID length is *not* the same as the
prefix you route to the link. Given that you're talking about static
configuration, you can perfectly well configure all the hosts with /64
prefixes, but give them addresses that are all in a given /120 and then
route only the /120 to that link. That will also avoid all the attacks.

It also makes configuration much simpler, because you don't have to touch
any of the hosts when you run out of the /120: just increase the /120 to a
/119 on the router and move up from ::ff to ::100. That is 100% supported
by the current text of RFC4291bis, which requires that the router forward
packets to the /120.

This trick doesn't work in IPv4, so it will take a bit of getting used to
for people who only know IPv4, but I doubt that's the common case in NTT.

As such, I am confident to state that almost every deployed backbone
> uses a mixture of /64, /127, /126 and perhaps other lengths.

...

> There is public data that suggests that the backbone you are familiar
> with might be connected to a public internet exchange which uses a /112
> as peering lan prefix.
>

For the record, I don't dispute either of those.

> Also, backbone networks are a tiny percentage of the links on the planet.
>
> I certainly will not deny that fact. Are you familiar with the concept
> of the McNamara fallacy?
>

I wasn't. But that fallacy would apply to your arguments just as well as to
mine. You're the one that brought numbers to the thread first.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 12:31 AM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D=
"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">rfc6164 and rfc6583 are =
great examples that document considerations<br>
regarding not using a /64, it simply is not always the best fit.<br></block=
quote><div><br></div><div>RFC6583-style attacks (of which the class address=
ed by RFC6164 is a subset) are low payoff and pretty easy to mitigate using=
 very small changes to ND implementations. You can solve most or all of the=
 problem by using per-interface ND queues and prioritizing existing and gle=
aned ND entries over incomplete ones. You can do even better by pushing the=
 filtering away from the host so that you don&#39;t have to carry the packe=
ts.</div><div><br></div><div>Also, bear in mind that the interface ID lengt=
h is *not* the same as the prefix you route to the link. Given that you&#39=
;re talking about static configuration, you can perfectly well configure al=
l the hosts with /64 prefixes, but give them addresses that are all in a gi=
ven /120 and then route only the /120 to that link. That will also avoid al=
l the attacks.</div><div><br></div><div>It also makes configuration much si=
mpler, because you don&#39;t have to touch any of the hosts when you run ou=
t of the /120: just increase the /120 to a /119 on the router and move up f=
rom ::ff to ::100. That is 100% supported by the current text of RFC4291bis=
, which requires that the router forward packets to the /120.</div><div><br=
></div><div>This trick doesn&#39;t work in IPv4, so it will take a bit of g=
etting used to for people who only know IPv4, but I doubt that&#39;s the co=
mmon case in NTT.</div><div><br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">As such, I am confident to state that almost every deployed ba=
ckbone<br>
uses a mixture of /64, /127, /126 and perhaps other lengths.</blockquote><d=
iv>...=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">There i=
s public data that suggests that the backbone you are familiar<br>
with might be connected to a public internet exchange which uses a /112<br>
as peering lan prefix.<br></blockquote><div><br></div><div>For the record, =
I don&#39;t dispute either of those.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><span class=3D"gmail-">&gt; Also, backbone=
 networks are a tiny percentage of the links on the planet.<br>
<br>
</span>I certainly will not deny that fact. Are you familiar with the conce=
pt<br>
of the McNamara fallacy?<br></blockquote><div><br></div><div>I wasn&#39;t. =
But that fallacy would apply to your arguments just as well as to mine. You=
&#39;re the one that brought numbers to the thread first.</div></div></div>=
</div>

--f403045ee7785e73b70549208cc5--


From nobody Wed Feb 22 09:42:59 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E211129695; Wed, 22 Feb 2017 09:42:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PTqfmoz4QPJM; Wed, 22 Feb 2017 09:42:55 -0800 (PST)
Received: from mail-ua0-x236.google.com (mail-ua0-x236.google.com [IPv6:2607:f8b0:400c:c08::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 A056212968B; Wed, 22 Feb 2017 09:42:55 -0800 (PST)
Received: by mail-ua0-x236.google.com with SMTP id c32so6576963uac.1; Wed, 22 Feb 2017 09:42:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=M53hEkOhNWc6dHH4UW4Xu10ECbV1XYaW5W8seA1JB7w=; b=A+0bupadL71zcckzl98fbnLcpbFemXmeCpVOhT9NW+Ortpuv5ArVpEubVGkS1gplMH /je3z7BOJdD0LRO8k5zFMVaaImBVGCz4el8NrofLeSMHEoIJdhVFMVnYCrgmefmLhsuG oYlcMRUFnaLO0jK0ikEEg4vXF2MGPQOxysisExwNwDu2pjZA6v4vwVOdDxlFvGXkLLWx agDReqiJIMMjYPSQQ2rJTfoVg92qFal+BqPw9uEmkiVHw3nNg3HkXucUZfC2WW/r985z d/77EbLrymwNKROVV2RMroNtQVu8XpRG3fk1nLMgT6sGUneep8XbtsrWkvp6q6H71R9y EA8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=M53hEkOhNWc6dHH4UW4Xu10ECbV1XYaW5W8seA1JB7w=; b=r8DHZplVu0vujgCYwp56tG7ZpDStAJgBMW7JQKAjOr8/dTtU1Z1/eFFC0fjhFqSPJl HECEaKOY02cQ+Dt9Tp5rA5hMlG7TWZZRb3PUR6nBYrnmQTd3m0L0PNLedeq2fxp5TfEN h6LJBdxwFKYzVH2P/bNipTsuXfuHPR8WtcW+epipeP/d7OyGhwgQF0t3NJWnaNdrvPsp KsjSs/ZEe1OawlSW/v9mS/hkcuKW7fZifAkD4sOIFC34yHW6/kEOCGXQZ1wjHkwt8BLV 5XxhNesFiIU1vdk5yTqUgqtik/sONwWBeXpNoHhrsBJiNq7AAKkMtOPFAGJMiweuYq6q DBqg==
X-Gm-Message-State: AMke39l7p3Al9Bf14/m7peLo+P5yE+OOOswpi5ytW+O+f51KqO/sqWigcF5xpVGY+gFivJdMtuhKY8pScCOfTQ==
X-Received: by 10.176.23.89 with SMTP id k25mr14588205uaf.49.1487785374771; Wed, 22 Feb 2017 09:42:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Wed, 22 Feb 2017 09:42:24 -0800 (PST)
In-Reply-To: <20170221202821.GB32367@Vurt.local>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Thu, 23 Feb 2017 04:42:24 +1100
Message-ID: <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wtJ7goiLpmkDS0nDBVhC4sGoIjo>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 17:42:57 -0000

<snip>
> > In those years sufficient data has been collected to conclude that
> > /64 is not the "be all and end all".
>
> Alternatively, it could show that people are applying IPv4 practices
> they're familiar with to IPv6, even when it isn't necessary. They're
> missing out on operational savings from simplicity.

>Have you read rfc1925 section 2.4?


My operational experience is why I value simplicity, consistency and
less variation, as I've worked on and troubleshooted networks that
have been unnecessarily complex.

I think RFC1925 2.12 is more important.


> You are grossly overstating these 'operational savings'.


I've seen 4x/24s on a router interface because renumbering hosts into
a single /22 was operationally too expensive. Those hosts also were
being left with default "class B" subnet masks because that was
allowing their broadcast based discovery to work. Fortunately their
router was performing proxy ARP which then allowed them to access
other off-link destinations within the Class B address space.

I've seen a router with 25 subnets on its interface because they were
collapsed down from many PCs acting as routers, and renumbering the
hosts into a single large enough prefix was too operationally
expensive. That also meant the router was sending two RIP packets for
each update because the limit is 25 routes in a RIP packet.

If you see those sorts of things, and have experience with other
protocols like IPX where subnets are always large enough for any
number of devices the layer 2 technology can support, you value the
simplicity of /64s everywhere, even on links with two addresses.


>Also, for the
>sake of this dialogue I'll apply Hanlon's razor and operate under the
>assumption that you are not familiar with my work environment.

>I am amazed your reaction to my sharing of real-world data is the
>equivalent of "well, i think you are doing it wrong".
>A lack of empathy
>is exhibited in that you do not wonder _why_ things are what they are.


I know quite well why IPv4 has been operated the way it has.

Your data doesn't measure motivation.

If I see a set of prefix lengths in IPv6 that vary like IPv4 ones
would, which is what your data set showed, then I think the motivation
is that IPv4 addressing methods and thinking have been applied to
IPv6.

If your mix of prefix lengths was only /64s, or only /64s and /127s,
then I think that shows an understanding of IPv6 addressing models and
intents.

A lot of IPv4's addressing models and methods are a consequence of
IPv4 never being designed to be used to build the Internet we have
today.

Here's what Vint Cerf has said about IPv4's address size and design context.

http://mailman.nanog.org/pipermail/nanog/2010-April/020488.html

IPv4 was designed for a research network that escaped and became a
global network. IPv6 is really the first protocol designed by the IETF
to solve a global internetwork problem. Let's leave behind unnecessary
practices that have been used to extend IPv4's life, and that make
things unnecessarily complicated and more costly to operate and
troubleshoot.


Regards,
Mark.


From nobody Wed Feb 22 09:46:50 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB415129503 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:46:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JBXYnyMqvkfd for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:46:47 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 797C8129958 for <ietf@ietf.org>; Wed, 22 Feb 2017 09:46:47 -0800 (PST)
Received: by mail-vk0-x234.google.com with SMTP id x75so6095743vke.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 09:46:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=MsMeQRoSZvZ8ehhWYm+iVc4g4H7f93yeIXgcnk2XPlc=; b=fH7tc3SdOcbcY5qiRyBAKJ/aUGusEXHM2aUADHLThVGXLM12eBbcuAoe+EU7UF8yIq VLhK5WXK8abd1DCbBHM0x/9OjhoMOjZXLFFQPBR2pFVXoiJ3UP7EK9J426GyF18WGSxt WTsN0JFM8YEJaZpLmXstyRGW8ahGQzLuVyQ5+uSsImdxLxQVWBVaLyugmGXgbG3OPtJO qdkG6+TPXsd0eP50PFQKO8jiverDjDyifuM+byn0VxMIpUOdUnl/W1UpCM1JKh9QjvG5 ZUzHXuawGUgcnzjOs0sWJLKm964dBHjUALMimVDJ1naWm0a6XraJX6Y1zDdxaoNJNxpx 82XA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=MsMeQRoSZvZ8ehhWYm+iVc4g4H7f93yeIXgcnk2XPlc=; b=XDlTUTHRCpYh9qzmuWfK+DDcvJGR5epvuaZFWZJJ4aqMgyvBOzSQX0brmMQPwogPbb R5uEeEiQR3KAXXgzg27wuNjlWAl+F/QhK9Ciw9EbMRyEzRpB622KIldKPGY29r8wobwL nrxrdvb6Zrj2rWrKfuJ3EkVzHVaIlxN/grHllpKTscBm8CUezkqoV8wtGYxPvVIikGFq P5/ZVQOaRcK5j+PTgQkBv0YdjWGJEZAwp/LWJKCcuilj1BVuftHf9cy8AfgUscR8kYEQ Mkn1MnH4V1qkP705T3OfDmW9hLgcjlUDqx0VShDbF05+a2PuKXAhwm/gqDz0FzoM2mqS hg0g==
X-Gm-Message-State: AMke39ljGLwq7UgVa8Iqnq50hLh2bZFhPQi3YSkJzyLuxcA3DZRssET2ro1TdkDkThNEJT+qd5tAAfCUymgL/S/M
X-Received: by 10.31.170.15 with SMTP id t15mr14310465vke.6.1487785606365; Wed, 22 Feb 2017 09:46:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 09:46:25 -0800 (PST)
In-Reply-To: <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 02:46:25 +0900
Message-ID: <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Mark Smith <markzzzsmith@gmail.com>
Content-Type: multipart/alternative; boundary=001a1143225092201d0549221482
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iHA71wvm68bUTivfH-imzNu4k4E>
Cc: 6man WG <ipv6@ietf.org>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, IETF <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 17:46:49 -0000

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

On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com> wrote:

> Let's leave behind unnecessary practices that have been used to extend
> IPv4's life, and that make things unnecessarily complicated and more costly
> to operate and troubleshoot.
>

What he said.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 2:42 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Let&#39;s leave behind u=
nnecessary practices that have been used to extend IPv4&#39;s life, and tha=
t make things unnecessarily complicated and more costly to operate and=C2=
=A0troubleshoot.<br></blockquote><div><br></div><div>What he said.=C2=A0</d=
iv></div></div></div>

--001a1143225092201d0549221482--


From nobody Wed Feb 22 09:47:17 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44FCA129A75 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 Uv6VguRYjKpu for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:47:15 -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 B6648129A7A for <ietf@ietf.org>; Wed, 22 Feb 2017 09:47:14 -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 v1MHlC9I012908 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:47:12 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D029920ACC6 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:47:12 +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 C961F20ACC2 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:47:12 +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 v1MHlCYK009011 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:47:12 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
Message-ID: <d72bb63f-04c3-f72b-08f9-787a324afe1c@gmail.com>
Date: Wed, 22 Feb 2017 18:47:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oGCdkmFvY35sUtjQK10_P9lXabs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 17:47:17 -0000

Sorry for interfering Lorenzo, but I think there is an error here.

Le 22/02/2017 à 16:56, Lorenzo Colitti a écrit :
[...]
> Also, bear in mind that the interface ID length is *not* the same as
> the prefix you route to the link.

I guess you mean the plen1 of a prefix routed to a link is not the same
as a plen2 (128-IIDlen) advertised by RA on that link.

If plen1 is /63 and the IIDlen is 64 then RFC4862 (SLAAC) text says the
prefix in the RA must be discarded.  For this reason people make a /64
out of that /63 by putting a 0 in there.  Should it be 0 or 1?  Silence
in specs about this.

If plen1 is /120 and the plen in the RA is /64 then there is a big
problem, below.

If on another hand you mean that that /64 is not in an RA but manually
configured in the interface: then why put 64 when all the subnet has is
a 120?  Who asks for this?  The 4291bis spec?  That's an error too.

> Given that you're talking about static configuration, you can
> perfectly well configure all the hosts with /64 prefixes, but give
> them addresses that are all in a given /120

I guess you mean to manually assign 2001:db8::1/120 on a machine, and
2001:db8::2/120 on another.  I dont see why setting a /64 there at all.

> and then route only the /120 to that link.

YEs.  One could route the /120 to that link, and have each Host on that
link statically configure an IP address with that /120 prefix length.
That works.

ND and NUD also work ok with /120.

But,

If one puts a /64 in a RA in a subnet where only a /120 is routed to
then things may break.  Some Hosts may self-configure SLAAC/Ethernet
some addresses with an IID of length 64 which are routed elsewhere, not
to them.  Outgoing packets may go, but incoming packets go to some other
place.

> That will also avoid all the attacks.

YEs, some ND attacks will be avoided if using a /120.  One does not need
to put /64 anywhere in order to avoid ND attacks.

> It also makes configuration much simpler, because you don't have to
> touch any of the hosts when you run out of the /120: just increase
> the /120 to a /119 on the router and move up from ::ff to ::100. That
> is 100% supported by the current text of RFC4291bis, which requires
> that the router forward packets to the /120.

YEs, I agree.  It can be extended that way.  But in this case, again,
why the need to put /64 there?

> This trick doesn't work in IPv4,

I agree: in IPv4 it amounts to forwarding a /24 to a subnet and set /16
as subnet mask on the addresses of Hosts in that subnet.  That can
create problems.  They are more visible in IPv4.

Same in IPv6: if one forwards a /120 to a subnet then set /120 as that
prefix length (aka subnet mask).  Otherwise problems.

One can do such trick equally well in IPv4 and in IPv6 and one is
equally conscious of the problems created.

Alex

>
> ...
>
> There is public data that suggests that the backbone you are
> familiar with might be connected to a public internet exchange which
> uses a /112 as peering lan prefix.
>
>
> For the record, I don't dispute either of those.
>
>> Also, backbone networks are a tiny percentage of the links on the
>> planet.
>
> I certainly will not deny that fact. Are you familiar with the
> concept of the McNamara fallacy?
>
>
> I wasn't. But that fallacy would apply to your arguments just as well
> as to mine. You're the one that brought numbers to the thread first.


From nobody Wed Feb 22 09:56:29 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9780E12985F for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:56:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level: 
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 S18rVwomu2YN for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 09:56:25 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 7D9A5129503 for <ietf@ietf.org>; Wed, 22 Feb 2017 09:56:25 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1MHuN7O039139 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:56:23 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 579DC207106 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:56:23 +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 44C4A207063 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:56:23 +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 v1MHuNUw011515 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:56:23 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <cb235822-f45a-5ccd-9493-07e2f560fddd@gmail.com>
Date: Wed, 22 Feb 2017 18:56:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a9xjr6wVYbPpwWS3Z6ibCPwARKU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 17:56:27 -0000

Le 22/02/2017 à 18:46, Lorenzo Colitti a écrit :
> On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com
> <mailto:markzzzsmith@gmail.com>> wrote:
>
>     Let's leave behind unnecessary practices that have been used to
>     extend IPv4's life, and that make things unnecessarily complicated
>     and more costly to operate and troubleshoot.
>
>
> What he said.

I think this comparison to IPv4 is non-sense.

I think IPv6 should benefit from IPv4 experience of no-fixed-length
Interface ID and DHCP.

I think you should try the experience of trying to persuade ISPs to
involve DHCPv6 PD before you can claim networks can grow in the presence
of this /64 limit. Or otherwise tell when the smartphones 'tether' by
using a Standards Track protocol.

Until then there is no reason to have a /64 recommendation.

Alex


From nobody Wed Feb 22 10:02:05 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5BC129503 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 10:02:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ESR-IJFYb9y0 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 10:02:01 -0800 (PST)
Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) (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 9B0141296EE for <ietf@ietf.org>; Wed, 22 Feb 2017 10:02:00 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id 37FA3B44 for <ietf@ietf.org>; Wed, 22 Feb 2017 18:02:00 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07OuH1eij8Aq for <ietf@ietf.org>; Wed, 22 Feb 2017 12:02:00 -0600 (CST)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 009BD6B9 for <ietf@ietf.org>; Wed, 22 Feb 2017 12:01:59 -0600 (CST)
Received: by mail-ua0-f197.google.com with SMTP id 72so6617788ual.6 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:01:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0urM+5cYuChWCIZfibMHsHKtzTmzUp13fQZKIz2q/GA=; b=QsuNtWAPMWeAfWBh3vBMKtVd/rNKIk78zMM5giId8hIr7VQORNnW5dXzFWoUwQ70bN qlWiXRYFJEb04T75fpeE68TRiaaQbqNfuNS/izsyaURu84QuJtyHkbncRKPiTN7DIDUG TFLm6m8YlaruSZ9rIKnrUCHtbhEJHjfOw3y2qYK7rLhqNWBp8xlaRL/jx80lWT1V3xHU ZPC2Ryi9RKUM0o2lVbsHNSsVXbqIqkyWsM0eJs3M4Fi9XNpG7V/qXQDQ5QzVuzkuPJzB FWzgbVLEx6zmC9TiHYv1cxJR0kXCHPMs48yLEDP1qRBEGRsfYLaz6ndx1lkrUJUDBwX9 q0BA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0urM+5cYuChWCIZfibMHsHKtzTmzUp13fQZKIz2q/GA=; b=ln4Z7iOnEVlGAeUCQPPfBOggF61GCsXDj6z5ER6j1AwHQVSiTW2etk6SBcCt3lBOTL ms+ZcJ1owVCRbchfywiIznYLWJSyvtKID/XYj+1OpTJHNUAiYWVLL9MgDes3+YOfYiFr FJCM3GhBYIiGG49IPI43lwMwtoChzjwdimd2TZAANX3msVoHcxI+2XVFW0uRocuNSkEW 7jeyqn4Py/dJUW0z1wBcazf9PobkKl1YB3WPvt6CQlXmkeBo2MgtWQCnvUduXQUnhCbn P1f+pmKTFA9vvO8v+ukKo8CxdKpRhWZyXUWTdvWGzmGKBFvukltbLbdZkEFCXoQDyNc7 d2aw==
X-Gm-Message-State: AMke39nX4pTf7FK86Zokl8NAeiqDIQYQGXa/86ilf4+VzT93vkJf/dZGps5RPzbtIXzVzqTDxcS9b0FQaYIdPcJML1DZLAbEib1MOWBMnWeM+uiXFpTgewWawmGmGz5ierUGTVBWDM4CavThAhE=
X-Received: by 10.176.5.200 with SMTP id e66mr8830428uae.108.1487786519478; Wed, 22 Feb 2017 10:01:59 -0800 (PST)
X-Received: by 10.176.5.200 with SMTP id e66mr8830414uae.108.1487786519259; Wed, 22 Feb 2017 10:01:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Wed, 22 Feb 2017 10:01:58 -0800 (PST)
In-Reply-To: <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 22 Feb 2017 12:01:58 -0600
Message-ID: <CAN-Dau1e0uac2qkxW-6xk-ToYROw6ipkQV3RjtMqFm6RuWq0EQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=94eb2c1239a0fbdd0e0549224ac2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vBpjOk2Junm8WjJb1qCUrEl6axM>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 18:02:03 -0000

--94eb2c1239a0fbdd0e0549224ac2
Content-Type: text/plain; charset=UTF-8

On Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com>
> wrote:
>
>> Let's leave behind unnecessary practices that have been used to extend
>> IPv4's life, and that make things unnecessarily complicated and more costly
>> to operate and troubleshoot.
>>
>
> What he said.
>

Yes, what he said is a very compelling argument to use /64 in most places,
the default. However, you cannot extrapolate there exists no places were
something other than /64 make sense.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, Feb 23, 2017 a=
t 2:42 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmith@=
gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">Let&#39;s leave behind unnecessary practic=
es that have been used to extend IPv4&#39;s life, and that make things unne=
cessarily complicated and more costly to operate and=C2=A0troubleshoot.<br>=
</blockquote><div><br></div><div>What he said.=C2=A0</div></div></div></div=
>
</blockquote></div><br>Yes, what he said is a very compelling argument to u=
se /64 in most places, the default. However, you cannot extrapolate there e=
xists no places were something other than /64 make sense.<br clear=3D"all">=
<div><br></div>-- <br><div class=3D"gmail_signature" data-smartmail=3D"gmai=
l_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=
=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farme=
r@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Office of I=
nformation Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 Unive=
rsity Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis,=
 MN 55414-3029=C2=A0=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c1239a0fbdd0e0549224ac2--


From nobody Wed Feb 22 10:05:47 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BFD3129A4D for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 10:05:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dvo-AYCqBYNR for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 10:05:43 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c: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 35BC3129A9B for <ietf@ietf.org>; Wed, 22 Feb 2017 10:05:08 -0800 (PST)
Received: by mail-vk0-x22c.google.com with SMTP id x75so6408598vke.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 10:05:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QBkJHMTRcMF1X/R4GYgwFFVGH7d/JgaB4yfGyaNPlDg=; b=Ody9HkYmfhj+p2pCt9L/9GWRawa2q4YFPoGvANauSkSPaG7VaJTk0KUs78WFJHChTO u46Vl/CWZhfQzTo+MPa9Z/Dc2Ucjht9hsxjylHVQYQIqkYxgF6ntEpe8zdu0pebtOaSb frhd3ZPek1DmCZBT3UMa+VCgkqnPdoYm3QELsUlavh6T34gtyZd7Qxzrc128zp8mDMtM QNtHVSOiXUcgXi6K/gba0XypgTIoOI0J0P3zN9hhWhpAduQq8umkqRhCjQTkMXjk0Kwz nvQIV3U55EMonw89+M1blxriOwu2Yl/zECLuSeTRdwEGxqhOlCOQUWkW9qs2zLlqjKrJ jVbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QBkJHMTRcMF1X/R4GYgwFFVGH7d/JgaB4yfGyaNPlDg=; b=tD8qlmmsxtAtI6J5q/+RXit2nCW6+y7rwoYjriLAHUDTi9hb5zCHDJuY8WNUli9Gqp vQmOwKrJ1/qtuf0SbstCiyUpuNnFl+ICvpb9jmWLtYC6LmqpvOafDHWn1JWbPY+xgI3r jJr/F4mR3t4ZRrL/Fw2MiCppI193qYEkmcaAhk8XwABn+SNceXDLbdFLXNF/zp3dOzvj ggb7dlCCvOHiuTLfqMuUX9lSm6r8awEoX7nos1vJTB0cAXLH8scANhcAKmsz5BtFsofM Z5q4EuM7XwgjqHU+uUB6LgGGFhbRIeqq+zjXVBZz/z+xUKJYti+oiKUCBJv2isHJ2RHg lRbQ==
X-Gm-Message-State: AMke39lSENOSFqC3PIZcJqdPLNGgLoMm18849FhsxDtT9jqdwOo+XzJrL0MHqT6IlK3dVP+U378qpR+Uh0FsY4LJ
X-Received: by 10.31.52.193 with SMTP id b184mr15393409vka.156.1487786706845;  Wed, 22 Feb 2017 10:05:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 10:04:46 -0800 (PST)
In-Reply-To: <CAN-Dau1e0uac2qkxW-6xk-ToYROw6ipkQV3RjtMqFm6RuWq0EQ@mail.gmail.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com> <CAN-Dau1e0uac2qkxW-6xk-ToYROw6ipkQV3RjtMqFm6RuWq0EQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 03:04:46 +0900
Message-ID: <CAKD1Yr0F0e7CbieLr4+7mMJ7xZXponPS+5-nbcDWh_dRP7wR9w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: multipart/alternative; boundary=001a114402c02a67e40549225686
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a8L_Kg9N6lOQ3q1RzeoKZMLo__k>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 18:05:44 -0000

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

>From a complexity, reliability, and cost point of view, it is likely better
to say that everything should be /64 rather than say that 99.9% of links
will be /64 or /128 but we still need to support other prefix lengths for
0.1% of cases.

On Thu, Feb 23, 2017 at 3:01 AM, David Farmer <farmer@umn.edu> wrote:

>
>
> On Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitti <lorenzo@google.com>
> wrote:
>
>> On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com>
>> wrote:
>>
>>> Let's leave behind unnecessary practices that have been used to extend
>>> IPv4's life, and that make things unnecessarily complicated and more costly
>>> to operate and troubleshoot.
>>>
>>
>> What he said.
>>
>
> Yes, what he said is a very compelling argument to use /64 in most places,
> the default. However, you cannot extrapolate there exists no places were
> something other than /64 make sense.
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================
>

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

<div dir=3D"ltr">From a complexity, reliability, and cost point of view, it=
 is likely better to say that everything should be /64 rather than say that=
 99.9% of links will be /64 or /128 but we still need to support other pref=
ix lengths for 0.1% of cases.<div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Thu, Feb 23, 2017 at 3:01 AM, David Farmer <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><=
div class=3D"gmail_extra"><div><div class=3D"m_-7411168634962528019h5"><br>=
<div class=3D"gmail_quote">On Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitt=
i <span dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo@google.com" target=3D"_bl=
ank">lorenzo@google.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"=
>On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=
=3D"mailto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Let&#39;s leave be=
hind unnecessary practices that have been used to extend IPv4&#39;s life, a=
nd that make things unnecessarily complicated and more costly to operate an=
d=C2=A0troubleshoot.<br></blockquote><div><br></div><div>What he said.=C2=
=A0</div></div></div></div>
</blockquote></div><br></div></div>Yes, what he said is a very compelling a=
rgument to use /64 in most places, the default. However, you cannot extrapo=
late there exists no places were something other than /64 make sense.<span =
class=3D"m_-7411168634962528019HOEnZb"><font color=3D"#888888"><br clear=3D=
"all"><div><br></div>-- <br><div class=3D"m_-7411168634962528019m_-51208193=
51676245916gmail_signature" data-smartmail=3D"gmail_signature">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Em=
ail%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Network=
ing &amp; Telecommunication Services<br>Office of Information Technology<br=
>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=
=C2=A0 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</font></span></div></div>
</blockquote></div><br></div></div>

--001a114402c02a67e40549225686--


From nobody Wed Feb 22 11:24:59 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D9E129A8B for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 11:24:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IeHzhXVHU3iz for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 11:24:56 -0800 (PST)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 99CD81297B8 for <ietf@ietf.org>; Wed, 22 Feb 2017 11:24:56 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id 2B97F209 for <ietf@ietf.org>; Wed, 22 Feb 2017 19:24:56 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5rTrcLgo0fT0 for <ietf@ietf.org>; Wed, 22 Feb 2017 13:24:56 -0600 (CST)
Received: from mail-qk0-f197.google.com (mail-qk0-f197.google.com [209.85.220.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id EB1B19B0 for <ietf@ietf.org>; Wed, 22 Feb 2017 13:24:55 -0600 (CST)
Received: by mail-qk0-f197.google.com with SMTP id q4so9269308qkh.4 for <ietf@ietf.org>; Wed, 22 Feb 2017 11:24:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=N5i+ZN2KMqrnBpL5uHZ+34m+vXA4ndQDZKBRFtoMIi0=; b=o3Qqz7asdhjRbMi8FVR0q9uNHesWCPpgvk0DlmU3x+Es8Lhte5cilNla3WViwjgDm8 714doPCu+p86x1bPLYuIcHUk4Dlv6iTFPcq8L6wMBvgCWxRYxEzlNKnKrot4mNZOTfsp mYeBS/i6iLuOWKXQR1u2cVO3hvdOfHaOjx/ymJ0fTKnLxeAFEtQat/DDZW4A21AomZiJ U+mGS7iqfjg97tSbDrpOiP4Q6kLMzI2fDcz8XtSQaPP1qPczREIZEqpm2c4/0U1S0NIK jastn3swweaNqfigeR6m2JV8dqeI4DsrvtRGK3InMolMrOO9MjWibAR33w4Fm54NRdS5 +xCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=N5i+ZN2KMqrnBpL5uHZ+34m+vXA4ndQDZKBRFtoMIi0=; b=nzfUO9DmZsVlCq22WINz+fTLV8mQGAX3lUNz1kyDYxKRRsLNBUEeLBUD9HLAB/gYKl sT5e9wzQpJ73sstU2WAQLbWXd5FZjMIttdMkJDCQhbdCk5qAAQm8q2QOlLzrq1ZPC7Wg 0yfKQ/sWqPhFgX7x/M/B5SDiA7Vcw3wY4y/64e/7v6hswtRLDtZbMyRE+2xMkrTn6I1O ZeTYA0GFr4pIvSBa3prB/FNwTT//zvUuSTJm37kriU2XKTzZnbGgV/ky9Oovo6P7Z49V 7lLMhnpvRygD7NvcH+08dPTViNBOPqJCGWzVcigx6tESObH78EUPD6ks9T+ykkwcp9Kz dt+Q==
X-Gm-Message-State: AMke39kOex2ruMNJ0LbH+VpEsMc4h7lDcdW+QZNueHnm7urtKNkngDISiCHNlDsntI1htoPQcCk21rqGk+4yugMt4FjRm8+kjsxM9ZjwsTprnayfxjxKkLxlyboaiiLEHYd+Hgx7Nv9aDsEEVzA=
X-Received: by 10.55.39.147 with SMTP id n141mr17222658qkn.103.1487791495456;  Wed, 22 Feb 2017 11:24:55 -0800 (PST)
X-Received: by 10.55.39.147 with SMTP id n141mr17222638qkn.103.1487791495255;  Wed, 22 Feb 2017 11:24:55 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.41.83 with HTTP; Wed, 22 Feb 2017 11:24:54 -0800 (PST)
In-Reply-To: <CAKD1Yr0F0e7CbieLr4+7mMJ7xZXponPS+5-nbcDWh_dRP7wR9w@mail.gmail.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com> <CAN-Dau1e0uac2qkxW-6xk-ToYROw6ipkQV3RjtMqFm6RuWq0EQ@mail.gmail.com> <CAKD1Yr0F0e7CbieLr4+7mMJ7xZXponPS+5-nbcDWh_dRP7wR9w@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Wed, 22 Feb 2017 13:24:54 -0600
Message-ID: <CAN-Dau0iYOD-WLq7J_23M3oZKiBTTKV-jbsG+WTZ7GYNABwD-A@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=94eb2c095c7e93437305492373e2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6GERCp91K89DQP16N7QXOCeYbWc>
Cc: 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 19:24:58 -0000

--94eb2c095c7e93437305492373e2
Content-Type: text/plain; charset=UTF-8

I'm perfectly fine with "should be" or even "almost alway", but that's not
"required", "must be", or "always", just like 5 - 9s uptime isn't never
have an outage.  And yes you still need to deal with that 0.1% or 0.0001%
in the case of 5 - 9s, there is no way off that hook.

On Wed, Feb 22, 2017 at 12:04 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> From a complexity, reliability, and cost point of view, it is likely
> better to say that everything should be /64 rather than say that 99.9% of
> links will be /64 or /128 but we still need to support other prefix lengths
> for 0.1% of cases.
>
> On Thu, Feb 23, 2017 at 3:01 AM, David Farmer <farmer@umn.edu> wrote:
>
>>
>>
>> On Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitti <lorenzo@google.com>
>> wrote:
>>
>>> On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com>
>>> wrote:
>>>
>>>> Let's leave behind unnecessary practices that have been used to extend
>>>> IPv4's life, and that make things unnecessarily complicated and more costly
>>>> to operate and troubleshoot.
>>>>
>>>
>>> What he said.
>>>
>>
>> Yes, what he said is a very compelling argument to use /64 in most
>> places, the default. However, you cannot extrapolate there exists no places
>> were something other than /64 make sense.
>>
>> --
>> ===============================================
>> David Farmer               Email:farmer@umn.edu
>> Networking & Telecommunication Services
>> Office of Information Technology
>> University of Minnesota
>> 2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
>> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
>> ===============================================
>>
>
>


-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr">I&#39;m perfectly fine with &quot;should be&quot; or even =
&quot;almost alway&quot;, but that&#39;s not &quot;required&quot;, &quot;mu=
st be&quot;, or &quot;always&quot;, just like 5 - 9s uptime isn&#39;t never=
 have an outage.=C2=A0 And yes you still need to deal with that 0.1% or 0.0=
001% in the case of 5 - 9s, there is no way off that hook.</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Feb 22, 2017 at 12:=
04 PM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo@goog=
le.com" target=3D"_blank">lorenzo@google.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div dir=3D"ltr">From a complexity, reliability, =
and cost point of view, it is likely better to say that everything should b=
e /64 rather than say that 99.9% of links will be /64 or /128 but we still =
need to support other prefix lengths for 0.1% of cases.<div class=3D"gmail_=
extra"><br><div class=3D"gmail_quote">On Thu, Feb 23, 2017 at 3:01 AM, Davi=
d Farmer <span dir=3D"ltr">&lt;<a href=3D"mailto:farmer@umn.edu" target=3D"=
_blank">farmer@umn.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><div><div class=3D"m_11=
77044719528010047m_-7411168634962528019h5"><br><div class=3D"gmail_quote">O=
n Wed, Feb 22, 2017 at 11:46 AM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div c=
lass=3D"gmail_extra"><div class=3D"gmail_quote">On Thu, Feb 23, 2017 at 2:4=
2 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mailto:markzzzsmith@gmail=
.com" target=3D"_blank">markzzzsmith@gmail.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Let&#39;s leave behind unnecessary practices th=
at have been used to extend IPv4&#39;s life, and that make things unnecessa=
rily complicated and more costly to operate and=C2=A0troubleshoot.<br></blo=
ckquote><div><br></div><div>What he said.=C2=A0</div></div></div></div>
</blockquote></div><br></div></div>Yes, what he said is a very compelling a=
rgument to use /64 in most places, the default. However, you cannot extrapo=
late there exists no places were something other than /64 make sense.<span =
class=3D"HOEnZb"><font color=3D"#888888"><span class=3D"m_11770447195280100=
47m_-7411168634962528019HOEnZb"><font color=3D"#888888"><br clear=3D"all"><=
div><br></div>-- <br><div class=3D"m_1177044719528010047m_-7411168634962528=
019m_-5120819351676245916gmail_signature" data-smartmail=3D"gmail_signature=
">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a hr=
ef=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu=
</a><br>Networking &amp; Telecommunication Services<br>Office of Informatio=
n Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave=
 SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612)%20626-0815" valu=
e=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>Minneapolis, MN 55=
414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-9952" value=3D"+16128=
129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</font></span></font></span></div></div>
</blockquote></div><br></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarm=
er@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; =
Telecommunication Services<br>Office of Information Technology<br>Universit=
y of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: =
612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D </div>
</div>

--94eb2c095c7e93437305492373e2--


From nobody Wed Feb 22 11:46:43 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DD0129AAB; Wed, 22 Feb 2017 11:46:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level: 
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 MNmp_t2NpeqV; Wed, 22 Feb 2017 11:46:36 -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 74400129A9C; Wed, 22 Feb 2017 11:46:36 -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 v1MJkZEf049554; Wed, 22 Feb 2017 12:46:35 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1MJkTtx049507 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 22 Feb 2017 12:46:29 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 22 Feb 2017 11:46:28 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Wed, 22 Feb 2017 11:46:28 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>, Mark Smith <markzzzsmith@gmail.com>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSjGfMgtRG27MIc0yfTQ6D9ojxU6F0YvkAgAAMaYCAAWP3AIAAASCA//+YrVA=
Date: Wed, 22 Feb 2017 19:46:28 +0000
Message-ID: <16967d27e6c042eab133826457c45e5a@XCH15-06-11.nw.nos.boeing.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_16967d27e6c042eab133826457c45e5aXCH150611nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CDiYxDxeZk5AfvMDqe0cBj5K9wI>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, IETF <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 19:46:37 -0000

--_000_16967d27e6c042eab133826457c45e5aXCH150611nwnosboeingcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

T2JzZXJ2aW5nIHRoaXMgdGhyZWFkLCB0aGlzIHNlZW1zIHRvIGJlIHRoZSBtaW5vcml0eSBvcGlu
aW9uLiBBbmQgSSBzdXBwb3NlIGl04oCZcyBub3JtYWwgdGhhdCBwZW9wbGUgd291bGQgZ2VuZXJh
bGl6ZWQgYmFzZWQgb24gdGhlaXIgcGVyc29uYWwgZXhwZXJpZW5jZXMuDQoNCk15IGV4cGVyaWVu
Y2UgaXMgb25lIG9mIGJlaW5nIGFsbG9jYXRlZCBhZGRyZXNzIGJsb2NrcyBwZXIgcGxhdGZvcm0s
IGFuZCBoYXZpbmcgYSB2ZXJ5IHN0cm9uZyBpbmNlbnRpdmUgdG8gbWFrZSB0aGVzZSB3b3JrIG92
ZXIgdGhlIGxvbmcgaGF1bC4gQXMgc3VjaCwgYXJiaXRyYXJ5IGNvbnN0cmFpbnRzLCBzdWNoIGFz
IC82NCwgZG9u4oCZdCBzZWVtIGxpa2UgYSBmbGV4aWJsZSBkZXNpZ24gYXQgYWxsLg0KDQpQbHVz
LCBmb3IgdGhvc2Ugd2hvIG9waW5lIHRoYXQg4oCcZXZlcnlvbmXigJ0gc2hvdWxkIGJlIGFsbG9j
YXRlZCBhIC80OCwgSeKAmWQgc3VnZ2VzdCB0d28gcHJvYmxlbXMgd2l0aCB0aGF0IG5vdGlvbi4g
Rmlyc3QsIGl0IGRvZXMgbm90IHJlZmxlY3QgdG9kYXnigJlzIHJlYWxpdHkuIEFuZCBzZWNvbmRs
eSwgaXQgc2VlbXMgcXVpdGUgbGltaXRpbmcuIE5vIGJldHRlciB0aGFuIE1BQyBhZGRyZXNzZXMs
IHdoaWNoIGJ5IG5vdyB3ZSBrbm93IGFyZSBoYXJkbHkg4oCcZ3VhcmFudGVlZOKAnSB0byBiZSBn
bG9iYWxseSB1bmlxdWUuDQoNCklvVCBjaGFuZ2VzIGFsbCBvZiBvdXIgcHJlY29uY2VpdmVkIG5v
dGlvbnMgYWJvdXQgd2hhdCBpcyDigJxhbXBsZS7igJ0NCg0KDQpGcm9tOiBpcHY2IFttYWlsdG86
aXB2Ni1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgTG9yZW56byBDb2xpdHRpDQpTZW50
OiBXZWRuZXNkYXksIEZlYnJ1YXJ5IDIyLCAyMDE3IDEyOjQ2DQpUbzogTWFyayBTbWl0aCA8bWFy
a3p6enNtaXRoQGdtYWlsLmNvbT4NCkNjOiA2bWFuIFdHIDxpcHY2QGlldGYub3JnPjsgNm1hbi1j
aGFpcnNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtNm1hbi1yZmM0MjkxYmlzQGlldGYub3JnOyBJRVRG
IDxpZXRmQGlldGYub3JnPg0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWlldGYtNm1h
bi1yZmM0MjkxYmlzLTA3LnR4dD4gKElQIFZlcnNpb24gNiBBZGRyZXNzaW5nIEFyY2hpdGVjdHVy
ZSkgdG8gSW50ZXJuZXQgU3RhbmRhcmQNCg0KT24gVGh1LCBGZWIgMjMsIDIwMTcgYXQgMjo0MiBB
TSwgTWFyayBTbWl0aCA8bWFya3p6enNtaXRoQGdtYWlsLmNvbTxtYWlsdG86bWFya3p6enNtaXRo
QGdtYWlsLmNvbT4+IHdyb3RlOg0KTGV0J3MgbGVhdmUgYmVoaW5kIHVubmVjZXNzYXJ5IHByYWN0
aWNlcyB0aGF0IGhhdmUgYmVlbiB1c2VkIHRvIGV4dGVuZCBJUHY0J3MgbGlmZSwgYW5kIHRoYXQg
bWFrZSB0aGluZ3MgdW5uZWNlc3NhcmlseSBjb21wbGljYXRlZCBhbmQgbW9yZSBjb3N0bHkgdG8g
b3BlcmF0ZSBhbmQgdHJvdWJsZXNob290Lg0KDQpXaGF0IGhlIHNhaWQuDQo=

--_000_16967d27e6c042eab133826457c45e5aXCH150611nwnosboeingcom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpw
dXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiVGltZXMgTmV3
IFJvbWFuIixzZXJpZjsNCgljb2xvcjojMEUyNUQwOw0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglm
b250LXN0eWxlOm5vcm1hbDsNCgl0ZXh0LWRlY29yYXRpb246bm9uZSBub25lO30NCi5Nc29DaHBE
ZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBp
bjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0K
CXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1s
PjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpl
eHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVs
YXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGlu
az0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBF
MjVEMCI+T2JzZXJ2aW5nIHRoaXMgdGhyZWFkLCB0aGlzIHNlZW1zIHRvIGJlIHRoZSBtaW5vcml0
eSBvcGluaW9uLiBBbmQgSSBzdXBwb3NlIGl04oCZcyBub3JtYWwgdGhhdCBwZW9wbGUgd291bGQg
Z2VuZXJhbGl6ZWQgYmFzZWQgb24gdGhlaXIgcGVyc29uYWwgZXhwZXJpZW5jZXMuPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Y29sb3I6IzBFMjVEMCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBF
MjVEMCI+TXkgZXhwZXJpZW5jZSBpcyBvbmUgb2YgYmVpbmcgYWxsb2NhdGVkIGFkZHJlc3MgYmxv
Y2tzIHBlciBwbGF0Zm9ybSwgYW5kIGhhdmluZyBhIHZlcnkgc3Ryb25nIGluY2VudGl2ZSB0byBt
YWtlIHRoZXNlIHdvcmsgb3ZlciB0aGUgbG9uZyBoYXVsLiBBcyBzdWNoLCBhcmJpdHJhcnkgY29u
c3RyYWludHMsIHN1Y2ggYXMgLzY0LCBkb27igJl0DQogc2VlbSBsaWtlIGEgZmxleGlibGUgZGVz
aWduIGF0IGFsbC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMEUyNUQwIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtjb2xvcjojMEUyNUQwIj5QbHVzLCBmb3IgdGhvc2Ugd2hvIG9waW5lIHRoYXQg
4oCcZXZlcnlvbmXigJ0gc2hvdWxkIGJlIGFsbG9jYXRlZCBhIC80OCwgSeKAmWQgc3VnZ2VzdCB0
d28gcHJvYmxlbXMgd2l0aCB0aGF0IG5vdGlvbi4gRmlyc3QsIGl0IGRvZXMgbm90IHJlZmxlY3Qg
dG9kYXnigJlzIHJlYWxpdHkuIEFuZCBzZWNvbmRseSwgaXQgc2VlbXMgcXVpdGUgbGltaXRpbmcu
DQogTm8gYmV0dGVyIHRoYW4gTUFDIGFkZHJlc3Nlcywgd2hpY2ggYnkgbm93IHdlIGtub3cgYXJl
IGhhcmRseSDigJxndWFyYW50ZWVk4oCdIHRvIGJlIGdsb2JhbGx5IHVuaXF1ZS48bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjExLjBwdDtjb2xvcjojMEUyNUQwIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtjb2xvcjojMEUy
NUQwIj5Jb1QgY2hhbmdlcyBhbGwgb2Ygb3VyIHByZWNvbmNlaXZlZCBub3Rpb25zIGFib3V0IHdo
YXQgaXMg4oCcYW1wbGUu4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBFMjVEMCI+PG86cD4m
bmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMS4wcHQ7Y29sb3I6IzBFMjVEMCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVw
dDtwYWRkaW5nOjBpbiAwaW4gMGluIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGlu
IDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiBpcHY2IFttYWlsdG86aXB2Ni1ib3VuY2VzQGlldGYu
b3JnXQ0KPGI+T24gQmVoYWxmIE9mIDwvYj5Mb3JlbnpvIENvbGl0dGk8YnI+DQo8Yj5TZW50Ojwv
Yj4gV2VkbmVzZGF5LCBGZWJydWFyeSAyMiwgMjAxNyAxMjo0Njxicj4NCjxiPlRvOjwvYj4gTWFy
ayBTbWl0aCAmbHQ7bWFya3p6enNtaXRoQGdtYWlsLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IDZt
YW4gV0cgJmx0O2lwdjZAaWV0Zi5vcmcmZ3Q7OyA2bWFuLWNoYWlyc0BpZXRmLm9yZzsgZHJhZnQt
aWV0Zi02bWFuLXJmYzQyOTFiaXNAaWV0Zi5vcmc7IElFVEYgJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBMYXN0IENhbGw6ICZsdDtkcmFmdC1pZXRmLTZtYW4t
cmZjNDI5MWJpcy0wNy50eHQmZ3Q7IChJUCBWZXJzaW9uIDYgQWRkcmVzc2luZyBBcmNoaXRlY3R1
cmUpIHRvIEludGVybmV0IFN0YW5kYXJkPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVGh1LCBGZWIgMjMsIDIwMTcg
YXQgMjo0MiBBTSwgTWFyayBTbWl0aCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcmt6enpzbWl0aEBn
bWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5tYXJrenp6c21pdGhAZ21haWwuY29tPC9hPiZndDsg
d3JvdGU6PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21h
cmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
TGV0J3MgbGVhdmUgYmVoaW5kIHVubmVjZXNzYXJ5IHByYWN0aWNlcyB0aGF0IGhhdmUgYmVlbiB1
c2VkIHRvIGV4dGVuZCBJUHY0J3MgbGlmZSwgYW5kIHRoYXQgbWFrZSB0aGluZ3MgdW5uZWNlc3Nh
cmlseSBjb21wbGljYXRlZCBhbmQgbW9yZSBjb3N0bHkgdG8gb3BlcmF0ZSBhbmQmbmJzcDt0cm91
Ymxlc2hvb3QuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5XaGF0IGhlIHNhaWQuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+
DQo=

--_000_16967d27e6c042eab133826457c45e5aXCH150611nwnosboeingcom_--


From nobody Wed Feb 22 12:00:16 2017
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 618D7129AD4 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 12:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BJcfYk6NfZU4 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 12:00:12 -0800 (PST)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::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 B6BA7129AE0 for <ietf@ietf.org>; Wed, 22 Feb 2017 12:00:10 -0800 (PST)
Received: by mail-wm0-x22c.google.com with SMTP id v77so8640385wmv.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 12:00:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=w+8XspVDXq9F6z3LpTlHjMFplXTmh7VQHB1jYiKlVbg=; b=HgOvHc1tXGSpzkiVOXHON2a/2Hal55YBc7CBYI7F34SmXUt8b6Pu6zml0sH5ewWP2w M6WO/pezk3tEONH7mJUmIhxe+FUvHJp1hVdzKwhBXYGH7gsGmCcZKtY8YnAUlUAlM9JC MOWg1wAD88Fy1f4vYtINKN5neW/NlktvYHPFWRO1eHSEXpvST9Z67W9yuhCgmMlrA+fb HI1psBjqQET2peCyHdF9urvN8D8Ms3ZVUKeuhgtqCl7LwgBVLKv6pN4+pATPTXrFepCC R3Tz1P4XnnRUQlPFX0w5Yej29DU3cR0aSdXfflWBNLYLS7U4F/rryRAvFWNBJL5qgGLf FtWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=w+8XspVDXq9F6z3LpTlHjMFplXTmh7VQHB1jYiKlVbg=; b=fNuOq2DDIOwi/HUkPUEr74G/KyXujqcfe1V2lbuiZch4TehceCU7/icC4nJx6AIPG0 CPgKPK2tbHe+8wrITy0FC0IWMeLRmJHaXKKATcU0g3TP8uY3h9dF7iMBtOwZD4VpR0FO 77gGaw3QoEJJylXK7eQ7TWP0G/IYJJGib+UkVg9A7BW2RX8/mRI9FsQ04TGQXBZaxRO+ Ix6PLg1f/e2ckEwtpdU4E45Jj3tPTVgLH+XRKlvgFq6tNbkxqqCJsue6zhh2KafbhsAZ n3vwF+VsNfYA/OKJxm6adXgyY5a06rgdtK3/Q+895eWoGFgsvwC4EbC2EflIs/GsOA3x oJqA==
X-Gm-Message-State: AMke39lbUumyjfPXSQXZNzbGhUaKCA6qKWNMaAQbDJI3RHDuAskPMuh0e1/nno1FLOxVHVBRWQlUaSH42jhjZw==
X-Received: by 10.28.207.7 with SMTP id f7mr57079wmg.112.1487793608618; Wed, 22 Feb 2017 12:00:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.223.150.93 with HTTP; Wed, 22 Feb 2017 12:00:08 -0800 (PST)
From: Alia Atlas <akatlas@gmail.com>
Date: Wed, 22 Feb 2017 15:00:08 -0500
Message-ID: <CAG4d1reo9PD0vsRm1nLiDyOqqtrCcu+k2kz1y2PzGuiTxYHWcA@mail.gmail.com>
Subject: Looking for more Discussion on IETF Hubs: draft-atlas-community-hubs-00.txt
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=94eb2c0d79cc8a8f4b054923f137
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RbqTJko5RGGvzvUrNim0CEC2cJk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:00:14 -0000

--94eb2c0d79cc8a8f4b054923f137
Content-Type: text/plain; charset=UTF-8

After some discussions, I realized that it would be useful to write up in
more detail the motivations and ideas around IETF Community Hubs - as well
as what we've been doing experimentally in Boston.

If you're interested in discussing the idea of geographically based IETF
groups with some outreach aspects, please do take a look.   I sent the
initial pointer to the draft to vmeet@ietf.org - but realized that may not
have reached everyone interested.

Regards,
Alia

P.S.  Rich Salz organized the last Boston meeting that was yesterday; we
had almost 40 people with 3 talks focused on aspects of privacy and
security.


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Thu, Feb 16, 2017 at 12:49 PM
Subject: I-D Action: draft-atlas-community-hubs-00.txt
To: i-d-announce@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.


        Title           : IETF Community Hubs
        Author          : Alia Atlas
        Filename        : draft-atlas-community-hubs-00.txt
        Pages           : 9
        Date            : 2017-02-16

Abstract:
   IETF Community Hubs are geographically-focused groups that facilitate
   participation in IETF activities.  An IETF Community Hub may have
   different focuses, depending upon the interests of those
   participating, such as cross-area learning, outreach, mentoring,
   problem refinement, implementation and interop testing, and social.
   An IETF Community Hub's focuses and the energy of its coordinators
   will determine what types of activities are organized.  Sample
   activities may include sessions of technical talks, social get-
   togethers, remote hubs during some IETF WG meetings, hackathons, etc.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-atlas-community-hubs/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-atlas-community-hubs-00


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

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

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

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

<div dir=3D"ltr"><div>After some discussions, I realized that it would be u=
seful to write up in more detail the motivations and ideas around IETF Comm=
unity Hubs - as well as what we&#39;ve been doing experimentally in Boston.=
 =C2=A0=C2=A0</div><div><br></div><div>If you&#39;re interested in discussi=
ng the idea of geographically based IETF groups with some outreach aspects,=
 please do take a look. =C2=A0 I sent the initial pointer to the draft to <=
a href=3D"mailto:vmeet@ietf.org">vmeet@ietf.org</a> - but realized that may=
 not have reached everyone interested.</div><div><br></div><div>Regards,</d=
iv><div>Alia</div><div><br></div><div>P.S.=C2=A0 Rich Salz organized the la=
st Boston meeting that was yesterday; we had almost 40 people with 3 talks =
focused on aspects of privacy and security.</div><div><br></div><br><div cl=
ass=3D"gmail_quote">---------- Forwarded message ----------<br>From: <b cla=
ss=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=3D"mailto:intern=
et-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: Thu, F=
eb 16, 2017 at 12:49 PM<br>Subject: I-D Action: draft-atlas-community-hubs-=
00.txt<br>To: <a href=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.or=
g</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 IETF Community Hubs<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Alia=
 Atlas<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-atl=
as-community-hubs-00.<wbr>txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 9<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2017-02-16<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0IETF Community Hubs are geographically-focused groups that fac=
ilitate<br>
=C2=A0 =C2=A0participation in IETF activities.=C2=A0 An IETF Community Hub =
may have<br>
=C2=A0 =C2=A0different focuses, depending upon the interests of those<br>
=C2=A0 =C2=A0participating, such as cross-area learning, outreach, mentorin=
g,<br>
=C2=A0 =C2=A0problem refinement, implementation and interop testing, and so=
cial.<br>
=C2=A0 =C2=A0An IETF Community Hub&#39;s focuses and the energy of its coor=
dinators<br>
=C2=A0 =C2=A0will determine what types of activities are organized.=C2=A0 S=
ample<br>
=C2=A0 =C2=A0activities may include sessions of technical talks, social get=
-<br>
=C2=A0 =C2=A0togethers, remote hubs during some IETF WG meetings, hackathon=
s, etc.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-atlas-community-hubs/" re=
l=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/dr=
aft-atlas-community-<wbr>hubs/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"https://tools.ietf.org/html/draft-atlas-community-hubs-00" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/<wbr>draft-at=
las-community-hubs-00</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" rel=3D"noreferrer" target=
=3D"_blank">ftp://ftp.ietf.org/internet-<wbr>drafts/</a><br>
<br>
______________________________<wbr>_________________<br>
I-D-Announce mailing list<br>
<a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/m=
ailman/<wbr>listinfo/i-d-announce<br>
Internet-Draft</a> directories: <a href=3D"http://www.ietf.org/shadow.html"=
 rel=3D"noreferrer" target=3D"_blank">http://www.ietf.org/shadow.<wbr>html<=
/a><br>
or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" rel=3D"noreferrer"=
 target=3D"_blank">ftp://ftp.ietf.org/ietf/<wbr>1shadow-sites.txt</a><br>
</div><br></div>

--94eb2c0d79cc8a8f4b054923f137--


From nobody Wed Feb 22 12:04:32 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E89C8129ADE for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 12:04: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ap-KPr6Ky-T0 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 12:04:17 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::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 9B96E129ABB for <ietf@ietf.org>; Wed, 22 Feb 2017 12:04:17 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id b129so4940884pgc.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 12:04:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=B29VjHqv3a1wCjkKm7yWelJ4KwDOk1L7wKFNh+Yy0M0=; b=GmkJL3DWLdwXyuSxky1TYjWHmmDGMZzXDgLjpofMqnSD79ptWaD6STKutFthxVZJbr AEu4RtLK405e7FdfELJ0KiI/6+yUXipmx1jCdUBpB1+Lm81Z1kX3TrFKW0PQEtCC3ReM 0ZstQc2ox4UuKJa1Loyp/sUBqIzmYwMKkJHyN1ch04c04c6Fvge+0bVQcL8fae/Fz1P+ pUyFD8WelTev0qARduZdTa+wBLoVurI6exDnnjKfMTbjN0DHTqr1IqDhf/TngUeFOq3l ANPOmf5LakNWrWsE6MVue5aQ0De6bIHDKiBLWsUeK9TRDK3EntBE1x7InidW62y0irQX hNsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=B29VjHqv3a1wCjkKm7yWelJ4KwDOk1L7wKFNh+Yy0M0=; b=c1xlj5rOefau2CAZuKXFeaFK231Zat9stcBAJiQxt5ykUZlWjc0vW2r4c3cBP/EDez cnqBPHcoVBpOurI9vWIHXkzYCIMunHez4WG120eo6OWGVbAil/ggY98YIMaJsJRMycOP G2PXvrzL0Rn+kfU/fSfYO7Il7lgyWQxU1cieqIaFywRnUBR5N+tLB6SiGfeiqnqmnLc9 UGrioZUagP82T6ePZILUzCwHjGCvjO8iIepuSdByN2MH8wYKOtFlH+GYRbrefZyX8/I4 PcVhdpcUu3k5KFmIks1QNeyJ4enblL+4xDUvw8KBQN1eMVCUgaxmyPNt8aQRQxTdVIjU rA3w==
X-Gm-Message-State: AMke39mrO9I3KcLIZ7PqMrZs7NSAAo7mygKFGTB3ZKiRq0AXpHM2NXtjQ77DBC6YuDbVcg==
X-Received: by 10.98.84.193 with SMTP id i184mr41776261pfb.27.1487793857037; Wed, 22 Feb 2017 12:04:17 -0800 (PST)
Received: from [192.168.178.21] ([118.149.111.84]) by smtp.gmail.com with ESMTPSA id h14sm5241836pgn.41.2017.02.22.12.04.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2017 12:04:16 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ietf@ietf.org
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com> <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com>
Date: Thu, 23 Feb 2017 09:04:21 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WLWaSnM9GegVghU8-o9sOLK2wBQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:04:23 -0000

On 22/02/2017 22:41, Alexandre Petrescu wrote:
<snip>

>> Well that does two things: configures a 128 bit address (as Chris
>> points out, *all* addresses are 128 bits, duh) and associates a
>> prefix length with it, which afaik is optional.
> 
> The prefix length is not optional.  There is no system out there on
> which one could configure a 128bit address without explicitely telling
> '/128' or '/64' or '/something-else'.

Wrong. Sorry to get all technical, but on Windows:

C:\windows\system32>netsh interface ipv6 add address ?

Usage: add address [interface=]<string> [address=]<IPv6 address>[/<integer>]
             [[type=]unicast|anycast]
             [[validlifetime=]<integer>|infinite]
             [[preferredlifetime=]<integer>|infinite]
             [[store=]active|persistent]
             [[skipassource=]true|false]

The [/<integer>] looks pretty optional to me. I just tried
   netsh interface ipv6 add address 12 2001:db8:dead::beef
and now I have three addresses:

C:\windows\system32>netsh interface ipv6 show addresses

Interface 12: Wireless Network Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:db8:dead::beef
Public     Preferred      1h54m9s      54m9s fd63:45eb:dc14:0:28cc:dc4c:9703:6781
Other      Preferred     infinite   infinite fe80::28cc:dc4c:9703:6781%12

When I try to ping 2001:db8:dead::cafe, I see what I expected in Wireshark:
neighbour solicitations from 2001:db8:dead::beef to ff02::1:ff00:cafe.
In other words, the new address is treated as on-link. I can't find any trace
of an associated prefix entry.

Maybe Linux is different.

     Brian


From nobody Wed Feb 22 12:05:22 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABB44129AD9; Wed, 22 Feb 2017 12:05:15 -0800 (PST)
X-Quarantine-ID: <CF_QuydnYirC>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 CF_QuydnYirC; Wed, 22 Feb 2017 12:05:13 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id BFD0A129A70; Wed, 22 Feb 2017 12:05:12 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 22 Feb 2017 11:55:50 -0800
Mime-Version: 1.0
Message-Id: <p06240603d4d39d70bb08@[99.111.97.136]>
In-Reply-To: <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
References: <148738514545.19944.11486737065416495302.idtracker@ietfa.amsl.com> <p06240602d4d236a5a2dd@[99.111.97.136]> <db1b0b75-f8bd-b582-92e5-e6c5bdb6b2b8@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Wed, 22 Feb 2017 12:05:09 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Dale Worley <worley@ariadne.com>, gen-art@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] Review of draft-ietf-slim-negotiating-human-language-06
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7rmxcBCZjP-q1WWCNEA_hfBF5Hw>
Cc: slim@ietf.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:05:15 -0000

At 11:57 AM +0100 2/22/17, Gunnar Hellstr=F6m wrote:

>  A few comments inline,
>
>
>  Den 2017-02-22 kl. 02:44, skrev Randall Gellens:
>>  Hi Dale,
>>
>>  Thank you for your review, I appreciate it.  Please see inline.
>>
>>  At 6:32 PM -0800 2/17/17, Dale Worley wrote:
>>
>>>   Reviewer: Dale Worley
>>>   Review result: Ready with Nits
>>>
>>>   I am the assigned Gen-ART reviewer for this draft.  The General Area
>>>   Review Team (Gen-ART) reviews all IETF documents being processed
>>>   by the IESG for the IETF Chair.  Please treat these comments just
>>>   like any other last call comments.
>>>
>>>   For more information, please see the FAQ at
>>>   <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>>>
>>>   Document:  draft-ietf-slim-negotiating-human-language-06
>>>   Reviewer:  Dale R. Worley
>>>   Review Date:  2017-02-17
>>>   IETF LC End Date:  2017-02-20
>>>   IESG Telechat date:  [unknown]
>>>
>>>   Summary:
>>>          This draft is basically ready for publication, but has nits
>>>          that should be fixed before publication.
>>>
>>>   * Technical comments
>>>
>>>   A. Call failure
>>>
>>>   If a call fails due to no available language match, in what way(s)
>>>   does it fail?  Section 5.3 says
>>>
>>>      If such an offer is received, the receiver MAY
>>>      reject the media, ignore the language specified, or attempt to
>>>      interpret the intent
>>>
>>>   But I suspect it's also allowed for the UAS to fail the call at the
>>>   SIP level.  Whether or not that is allowed (or at least envisioned)
>>>   should be described.  And what response code(s)/warn-code(s) should
>>>   be
>>>   used for that?
>>
>>  The text you quote has been deleted.  The=20
>> draft does not mandate if the call should=20
>> proceed or fail if there is no language match=20
>> possible, although the draft does provide an=20
>> optional mechanism to indicate the caller's=20
>> preference that the call not fail, and the=20
>> draft does mention that in the emergency=20
>> services case, the call will likely proceed,=20
>> but that's a matter of policy not protocol.
>  You may have a version where it is proposed=20
> that the text is deleted. We need to see that=20
> new text and agree if it was good to delete it.

I will be uploading the updated draft shortly.=20
The only question is if I upload it before or=20
after adding any extra examples.

>
>  There are more places in the draft where=20
> failing the call is mentioned, so the question=20
> about how it is failed is relevant anyway. A=20
> 603 Decline from the proxy would likely be the=20
> natural way to fail the call when it is because=20
> of lack of matching languages. But I do not see=20
> any natural way for an addressed UA to signal=20
> this.

I do not believe the draft needs to mandate how a call is rejected.

>
>>
>>>
>>>   B. Audio/Video coordination
>>>
>>>      5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>>
>>>      Note that while signed language tags are used with a video stream
>>>   to
>>>      indicate sign language, a spoken language tag for a video stream
>>>   in
>>>      parallel with an audio stream with the same spoken language tag
>>>      indicates a request for a supplemental video stream to see the
>>>      speaker.
>>>
>>>   And there's a similar paragraph in 5.4:
>>>
>>>>      A spoken language tag for a video stream in conjunction with an
>>>   audio
>>>>      stream with the same language might indicate a request for
>>>>      supplemental video to see the speaker.
>>>
>>>   I think this mechanism needs to be described more exactly, and in
>>>   particular, it should not depend on the UA understanding which
>>>   language tags are spoken language tags.  It seems to me that a
>>>   workable rule is that there is an audio stream and a video stream and
>>>   they specify exactly the same language tag in their respective
>>>   humintlang attributes.  In that case, it is a request for a spoken
>>>   language with simultaneous video of the speaker, and those requests
>>>   should be considered satisfied only if both streams can be
>>>   established.
>>
>>  The text you quote has been deleted.  A media=20
>> stream for supplemental purposes can be=20
>> negotiated without a language tag, as normal.
>>
>  The text should not be deleted just because it is under discussion.

It was controversial and not needed, hence it was=20
deleted.  The WG expressed a goal of publishing a=20
simple document to have something that can be=20
deployed.

>  It is a valid and valuable alternative. At the=20
> moment we lack ways to indicate if languages=20
> are wanted together or seen as separate=20
> alternatives, and we have said that such=20
> detailing can be added in future versions or=20
> additional specifications if not done now.=20
> Therefore we had better allow this combination=20
> and let the negotiating parties sort out what=20
> it currently means. The specification just=20
> indicates that the indicated languages are=20
> alternatives, and any number may be selected=20
> for matching and usage in the session.
>  I do not think we should require very exactly=20
> matching language tags between spoken language=20
> in audio and corresponding view of the speaker=20
> in video.

We are not requiring this.  On the contrary, a=20
video stream without a language attribute=20
indicates it is used for supplemental purposes,=20
not interactive language.  If we need more=20
capabilities, this can be done in the future.

>>>
>>>   * The following three items are adjustments to the design which I'd
>>>   like to know have been considered.
>>>
>>>   C. "humintlang" seems long to me
>>>
>>>   Given the excessive length of SDP in practice, it seems to me that a
>>>   shorter attribute name would be desirable.  E.g., "humlang" as was
>>>   used in some previous versions.  Or is there a coordinated usage with
>>>   other names in the "hum*lang" pattern?
>>
>>  There is no intent for a coordinated pattern.=20
>> The name was chosen years ago to avoid=20
>> potential confusion with the 'lang' attribute.=20
>> Is it worth reopening the issue to potentially=20
>> save three characters per SDP line with a=20
>> language?
>>
>>>
>>>   D. Use the Accept-Language syntax
>>>
>>>   It seems to me that it would better to use the Accept-Language syntax
>>>   for the attribute values.  This allows (1) specifiying the quality of
>>>   language experience, allowing clear description of bilingualism, (2)
>>>   a
>>>   unified method of specifying whether or not arbitrary languages are
>>>   acceptable, and (3) abbreviating SDP descriptions.
>>>
>>>   In a way, the fact that the current proposal seems to require (but
>>>   does not directly specify) the coordinated absence/presence of an
>>>   asterisk on all of the repetitions of humintlang-send or
>>>   humintlang-recv is a warning that the syntax doesn't represent the
>>>   semantics as well as it might.
>>
>>  The group considered multiple proposals to=20
>> permit specifying quality, preference,=20
>> q-values, etc. but decided to keep things=20
>> simple for this draft.  There is no intent to=20
>> require the use of an asterisk (to indicate a=20
>> preference by the caller to not fail the=20
>> call).  The asterisk is a very mild mechanism=20
>> with no normative effects.  It merely conveys=20
>> the preference of the caller, and is not=20
>> binding on the answerer.
>  I would never dare to use an sdp without an=20
> asterisk. Language matching is a tricky thing=20
> and human capabilities much wider than the=20
> language tags can express. If I get a call from=20
> a Norwegian user talking Norwegian and=20
> indicating Norwegian in the humintlang=20
> attributes, I want to get the call accepted by=20
> my device with setting for spoken Swedish,=20
> because Swedes and Norwegians usually can=20
> communicate quite well speaking their own=20
> languages. I would anyway not have imagined=20
> making a setting for Norwegian language as a=20
> preference in my device.
>  It will however be an excellent help for me to=20
> see the indication of the Norwegian, when I get=20
> the call, so I can tune my listening.
>  By setting the asterisk somewhere among the=20
> Humintlang attributes, I will make sure that I=20
> do not lose calls that I could handle.
>
>>
>>>   E. Have an attribute to abbreviate the bidirectionally-symmetric case
>>>
>>>   Note that all examples are bidirectionally symmetric, and the text
>>>   says that requests and responses SHOULD be bidirectionally symmetric.
>>>   So it would be a very useful abbreviation to define
>>>   "humintlang=3D<value>" to be equivalent to the combination of
>>>   "humintlang-send=3D<value>" and "humintlang-recv=3D<value>".
>>>
>>>   Combining proposals C, D, and E, the examples become
>>>
>>>         m=3Daudio 49170 RTP/AVP 0
>>>         a=3Dhumlang:en
>>>
>>>         m=3Dvideo 51372 RTP/AVP 31 32
>>>         a=3Dhumlang:ase,*;q=3D0.1
>>>
>>>         m=3Daudio 49250 RTP/AVP 20
>>>         a=3Dhumlang:es,eu;q=3D0.9,en;q=3D0.8,*;q=3D0.1
>>>
>>>         m=3Dtext 45020 RTP/AVP 103 104
>>>         a=3Dhumlang:gr
>>>
>>>   which requires about half as many characters as they have now.
>>
>>  A third attribute without the "-send" or=20
>> "-recv" to indicate bidirectionality would=20
>> reduce the characters in the SDP block, at the=20
>> cost of some added complexity (e.g., what if=20
>> all three appear).  I don't believe this has=20
>> been discussed in the group.
>>
>>>   * Editorial comments and nits
>>>
>>>   Abstract
>>>
>>>      This document describes the need and a solution using new SDP
>>>   stream
>>>      attributes.
>>>
>>>   I don't think the term "stream attribute" is used in RFC 4566.
>>>   Instead, it uses "media attribute".
>>
>>  Fixed.
>>
>>>   1.  Introduction
>>>
>>>      caller and callee know each other or there is contextual or out of
>>>      band information from which the language(s) and media modalities
>>>   can
>>>
>>>   I think this context, it's preferred to hyphenate "out-of-band" to
>>>   make it clearly be an adjective.
>>
>>>   OK.
>>
>>
>>>      This approach has a number of benefits, including that it is
>>>   generic
>>>      (applies to all interactive communications negotiated using SDP)
>>>   and
>>>      not limited to emergency calls.
>>>
>>>   I think s/and not limited to/and is not limited to/ reads more
>>>   smoothly.
>>
>>  There's no harm in the extra "is" so I'm happy to add it.
>>
>>>      But it is clearly useful in many other cases.  For
>>>      example, someone calling a company call center or a Public Safety
>>>      Answering Point (PSAP) should be able to indicate if one or more
>>>      specific signed, written, and/or spoken languages are preferred,
>>>   the
>>>      callee should be able to indicate its capabilities in this area,
>>>   and
>>>      the call proceed using in-common language(s) and media forms.
>>>
>>>   I think s/preferred, the callee/preferred; the callee/ because the
>>>   sentence is the concatenation of two sentences.
>>
>>  I reworded the sentence to flow better:
>>
>>     For example, it is helpful that someone calling a company call center
>>     or a Public Safety Answering Point (PSAP) be able to indicate
>>     preferred signed, written, and/or spoken languages, the callee be
>>     able to indicate its capabilities in this area, and the call proceed
>>     using the language(s) and media forms supported by both.
>>
>>>   Perhaps s/in-common/shared/.
>>
>>  Fixed in the rewording above.
>>
>>>
>>>      Including the user's human (natural) language preferences in the
>>>      session establishment negotiation is independent of the use of a
>>>      relay service and is transparent to a voice service provider.
>>>
>>>   I think it's even broader than "transparent to a voice service
>>>   provider" -- it's transparent to any serivice provider, assuming that
>>>   the media are language-neutral.
>>
>>  I changed it to read "voice or other service provider".
>>
>>>
>>>      In the case of a call to e.g., an airline, the call could be
>>>      automatically handled by a Spanish-speaking agent.
>>>
>>>   I think s/handled by/routed to/ is the usual usage.
>>
>>  We are trying to be careful in the draft to=20
>> not imply that it is discussing call routing.=20
>> I'd rather keep the more generic "handled by".
>>
>>>
>>>   3.  Desired Semantics
>>>
>>>      The desired solution is a media attribute (preferably per
>>>   direction)
>>>      that may be used within an offer to indicate the preferred
>>>   language
>>>      of each (direction of a) media stream, and within an answer to
>>>      indicate the accepted language.
>>>
>>>   In this one instance, I think you want to use "language(s)" to drive
>>>   home that that multiple languages can be specified:  "within an offer
>>>   to indicate the preferred language(s)".
>>>
>>>      (Negotiating multiple simultaneous languages within a media stream
>>>   is
>>>      out of scope, as the complexity of doing so outweighs the
>>>      usefulness.)
>>>
>>>   You might want to say instead "(Negotiating multiple simultaneous
>>>   languages within a media stream is out of scope for this document.)"
>>>   to ensure that nobody decides to argue whether "the complexity of
>>>   doing so outweighs the usefulness".
>>
>>  I agree and deleted "the complexity of doing so outweighs the usefulness=
".
>>
>>>
>>>   4.  The existing 'lang' attribute
>>>
>>>      RFC 4566 [RFC4566] specifies an attribute 'lang' which appears
>>>      similar to what is needed here, but is not sufficiently detailed
>>>   for
>>>      use here.
>>>
>>>   "for use here" isn't quite right.  Maybe "is not sufficiently
>>>   specific
>>>   or flexible to satisfy the requirements".
>>>
>>>      In addition, it is not mentioned in [RFC3264]
>>>
>>>   "it" is somewhat ambiguous here, perhaps change to "the 'lang'
>>>   attribute".
>>
>>  OK, accepted both changes.
>>
>>>
>>>   5.  Proposed Solution
>>>
>>>   Perhaps /Proposed Solution/Solution/, since once this draft is
>>>   approved, it becomes the solution.
>>
>>  OK.
>>
>>>
>>>   5.2.  New 'humintlang-send' and 'humintlang-recv' attributes
>>>
>>>         a=3Dhumintlang-send:<language tag>
>>>         a=3Dhumintlang-recv:<language tag>
>>>
>>>   This is presented as the generic form of the attributes, but there is
>>>   no indication of the posible asterisk.
>>
>>  The syntax has been deleted from 5.2 since it's now in 6.
>  I think it should not be deleted, but instead=20
> Dale's comment satisfied.  That would be more=20
> in line with the stye of rfc4566bis.
>  5.2 shows the complete attributes, and that is=20
> good. Chapter 6 only shows the syntax of the=20
> value.

Having the syntax in two places is a stylistic matter.

>>
>>>
>>>      The values constitute a list of languages
>>>      in preference order (first is most preferred).
>>>
>>>   "The values" isn't very clear, because the values are in successive
>>>   attributes.  You want to say something like "The sequence of values
>>>   in
>>>   the occurrences of one of these attributes constitutes ...".
>>>   However,
>>>   see the technical comments above.
>>
>>  The text was reworded to read:
>>
>>     The values from all
>>     instances of the attribute constitute a list of languages in
>>     preference order (first is most preferred).
>>
>>>
>>>      When placing an emergency call, and in any other case where the
>>>      language cannot be assumed from context, each media stream in an
>>>      offer primarily intended for human language communication SHOULD
>>>      specify both (or in some cases, one of) the 'humintlang-send' and
>>>      'humintlang-recv' attributes.
>>>
>>>   Probably s/assumed/inferred/.
>>
>>  I agree.
>>
>>>
>>>   Could you be more accurate by
>>>   s/or in some cases/or for unidirectional streams/?
>>
>>  I agree.
>>
>>>
>>>   5.3.  Advisory vs Required
>>>
>>>      The mechanism for indicating this preference is that, in an offer,
>>>   if
>>>      the last character of any of the 'humintlang-recv' or 'humintlang-
>>>      send' values is an asterisk, this indicates a request to not fail
>>>   the
>>>      call (similar to SIP Accept-Language syntax).  Either way, the
>>>   called
>>>      party MAY ignore this, e.g., for the emergency services use case,
>>>   a
>>>      PSAP will likely not fail the call.
>>>
>>>   The construction of this paragraph isn't quite complete.  It says
>>>   that
>>>   if an asterisk is present, a request shouldn't fail, but it doesn't
>>>   say that if no asterisk is present, a request should fail if there is
>>>   no language match.  And it's the latter condition that makes the
>>>   second sentence meaningful.  So I think you want to insert between
>>>   the
>>>   two sentences one regarding the absence of an asterisk.
>>
>>  I've reworded the section to read:
>>
>>     A consideration with the ability to negotiate language is if the call
>>     proceeds or fails if the callee does not support any of the languages
>>     requested by the caller.  This document does not mandate either
>>     behavior, although it does provide a way for the caller to indicate a
>>     preference for the call succeeding when there is no language in
>>     common.  It is OPTIONAL for the callee to honor this preference.  For
>>     example, a PSAP is likely to attempt the call even without an
>>     indicated preference when there is no language in common, while a
>>     call center might choose to fail the call.
>>
>>     The mechanism for indicating this preference is that, in an offer, if
>>     the last character of any of the 'humintlang-recv' or 'humintlang-
>>     send' values is an asterisk, this indicates a request to not fail the
>>     call.  The called party MAY ignore the indication, e.g., for the
>>     emergency services use case, regardless of the absence of an
>>     asterisk, a PSAP will likely not fail the call; some call centers
>>     might reject a call even with an asterisk.
>  This still does not meet Dale's comment.
>  Insert a sentence saying:
>  "A preference for getting the call denied in=20
> case of no language match SHOULD be indicated=20
> by no asterisk appended on any humintlang=20
> attribute value in the whole SDP."

I don't think that's needed, and it's a strangely=20
constructed normative directive.  How can a=20
preference have a SHOULD?

>>
>>>   5.5.  Examples
>>>
>>>   Given that the combined audio/video mechanism is the only
>>>   irregularity
>>>   in this system, there ought to be an example of it.  E.g.,
>>>
>>>      An example of a supplemental video stream with a spoken language
>>>      audio stream:
>>>
>>>         m=3Dvideo 51372 RTP/AVP 31 32
>>>         a=3Dhumintlang-send:en
>>>         a=3Dhumintlang-recv:en
>>>
>>>         m=3Daudio 49250 RTP/AVP 20
>>>         a=3Dhumintlang-send:en
>>>         a=3Dhumintlang-recv:en
>>
>>  If the video stream is supplemental then it=20
>> doesn't have a language (the text that=20
>> suggested otherwise has been deleted). But I=20
>> am considering adding more examples.
>  I provided a rich set of examples in my LC=20
> comments of Feb 13. Please consider them as a=20
> base even if some need revision if the proposed=20
> extended meaning of the asterisk is not=20
> accepted.

Thank you for submitting them; I am considering them.

>>
>>>
>>>   6.  IANA Considerations
>>>
>>>         humintlang-value =3D  Language-Tag [ asterisk ]
>>>                             ; Language-Tag defined in RFC 5646
>>>         asterisk         =3D  "*"
>>>
>>>   s/Language-Tag defined in RFC 5646/Language-Tag as defined in RFC
>>>   5646/
>>>
>>>   But perhaps also s/RFC 5646/BCP 47/, which ensures that "humintlang"
>>>   tracks the current version of language tags.
>>
>>  Ok.
>>
>>>
>>>   Appendix A.  Historic Alternative Proposal: Caller-prefs
>>>
>>>      This
>>>      results in a more fragile solution since the media modality and
>>>      language would be negotiated using SIP, and then the specific
>>>   media
>>>      formats (which inherently include the modality) would be
>>>   negotiated
>>>      at a different level (typically SDP, especially in the emergency
>>>      calling cases), making it easier to have mismatches (such as where
>>>      the media modality negotiated in SIP don't match what was
>>>   negotiated
>>>      using SDP).
>>>
>>>   "the media modality and language would be negotiated using SIP" isn't
>>>   quite the right way to say it because SIP isn't explicitly
>>>   negotiating
>>>   the modality.  Better would be
>>>
>>>      ... the language (and by implication the media modality) would be
>>>      negotiated using SIP, and then the specific media (which
>>>   inherently
>>>      include the modalities and formats) would be negotiated at a
>>>      different level ...
>>
>>  This section has been deleted.
>  Did we agree on that?

It was suggested in earlier comments to delete it=20
as it is clearly not needed (it's an informative=20
appendix detailing a historical alternative that=20
was not pursued).


>>
>>>
>>>   [END]
>>
>>
>  Regards
>  Gunnar
>
>  --
>  -----------------------------------------
>  Gunnar Hellstr=F6m
>  Omnitor
>  gunnar.hellstrom@omnitor.se
>  +46 708 204 288


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
    The highlight of the annual Computer Bowl occurred when Bill Gates,
who was a judge, posed the following question to the contestants:
    "What contest, held via Usenet, is dedicated to examples of weird,
obscure, bizarre, and really bad programming?"
    After a moment of silence, Jean-Louis Gassee (ex-honcho at Apple)
hit his buzzer and answered "Windows."
                                          --Recounted by Adam C. Engst


From nobody Wed Feb 22 12:10:48 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1393B129ABE; Wed, 22 Feb 2017 12:10:43 -0800 (PST)
X-Quarantine-ID: <1YyZcYODmjIa>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 1YyZcYODmjIa; Wed, 22 Feb 2017 12:10:41 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id C5F9D129A98; Wed, 22 Feb 2017 12:10:41 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Wed, 22 Feb 2017 12:01:20 -0800
Mime-Version: 1.0
Message-Id: <p06240604d4d3a0175a34@[99.111.97.136]>
In-Reply-To: <87h93mut8q.fsf@hobgoblin.ariadne.com>
References: <87h93mut8q.fsf@hobgoblin.ariadne.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 22 Feb 2017 12:10:38 -0800
To: worley@ariadne.com (Dale R. Worley), Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, slim@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] Review of draft-ietf-slim-negotiating-human-language-06
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/crX1Y7GbFUjIiQqXYLTODb5sS0M>
Cc: gen-art@ietf.org, rg+ietf@randy.pensive.org, ietf@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:10:43 -0000

At 10:42 AM -0500 2/22/17, Dale R. Worley wrote:

>  Gunnar Hellstr=F6m <gunnar.hellstrom@omnitor.se> writes:
>>>>   A. Call failure
>>>>
>>>>   If a call fails due to no available language match, in what way(s)
>>>>   does it fail?  Section 5.3 says
>>>>
>>>>      If such an offer is received, the receiver MAY
>>>>      reject the media, ignore the language specified, or attempt to
>>>>      interpret the intent
>>>>
>>>>   But I suspect it's also allowed for the UAS to fail the call at the
>>>>   SIP level.  Whether or not that is allowed (or at least envisioned)
>>>>   should be described.  And what response code(s)/warn-code(s) should
>>>>   be used for that?
>>>
>>>  The text you quote has been deleted.  The draft does not mandate if
>>>  the call should proceed or fail if there is no language match
>>>  possible, although the draft does provide an optional mechanism to
>>>  indicate the caller's preference that the call not fail, and the draft
>>>  does mention that in the emergency services case, the call will likely
>>>  proceed, but that's a matter of policy not protocol.
>>
>>  You may have a version where it is proposed that the text is deleted. We
>>  need to see that new text and agree if it was good to delete it.
>>
>>  There are more places in the draft where failing the call is mentioned,
>>  so the question about how it is failed is relevant anyway. A 603 Decline
>>  from the proxy would likely be the natural way to fail the call when it
>>  is because of lack of matching languages. But I do not see any natural
>>  way for an addressed UA to signal this.
>
>  I would argue strongly against using a 6xx response, as the defined
>  effect of those is to make the call fail all the way back to the
>  caller, rather than allowing alternative forks of the call to possibly
>  succeed.  The way to handle a call that *this* proxy can't route due to
>  language incompatibility is a 4xx response.
>
>  My question wasn't for the draft to be prescriptive on this issue (and
>  that seems to align with what the WG/authors intend), but to provide
>  implementation advice, best practices as it were -- There are a lot 4xx
>  responses available, and if you don't read their descriptions carefully,
>  it can be easy to choose one with the wrong semantics.  E.g., a 415
>  response is "Unsupported Media Type", but it's not for unsupported media
>  in the *session* (i.e., the SDP), it's for unsupported media in the
>  *INVITE body* (i.e., you can't process application/sdp).
>
>  OK, here it is:  RFC 3261 section 13.3.1.3:
>
>     A UAS rejecting an offer contained in an INVITE SHOULD return a 488
>     (Not Acceptable Here) response.  Such a response SHOULD include a
>     Warning header field value explaining why the offer was rejected.
>
>  section 21.4.26:
>
>  21.4.26 488 Not Acceptable Here
>
>     The response has the same meaning as 606 (Not Acceptable), but only
>     applies to the specific resource addressed by the Request-URI and the
>     request may succeed elsewhere.
>
>     A message body containing a description of media capabilities MAY be
>     present in the response, which is formatted according to the Accept
>     header field in the INVITE (or application/sdp if not present), the
>     same as a message body in a 200 (OK) response to an OPTIONS request.
>
>  and section 21.6.4:
>
>  21.6.4 606 Not Acceptable
>
>     The user's agent was contacted successfully but some aspects of the
>     session description such as the requested media, bandwidth, or
>     addressing style were not acceptable.
>
>     A 606 (Not Acceptable) response means that the user wishes to
>     communicate, but cannot adequately support the session described.
>     The 606 (Not Acceptable) response MAY contain a list of reasons in a
>     Warning header field describing why the session described cannot be
>     supported.  Warning reason codes are listed in Section 20.43.
>
>  And my memory was correct; a Warning header is appropriate in a 488
>  response.  Section 20.43 gives the details; it looks like a warn-code in
>  the range 390-398 is appropriate, or perhaps 300-329.  It seems like the
>  choice should be either 308 or 390, the first available codes in those
>  ranges.  And the ideal message text would contain the list of compatible
>  languages:
>
>      Warning: 308 proxy.example.com "Supported languages are: es, en"
>
>  The registration would be something like:
>
>      308 Incompatible language specification:  No requested      [this RFC=
]
>          language is supported and offerer requested failure.
>          The text should include the list of supported languages.

Thanks, Dale.  It seems that it would be useful=20
for the draft to suggest (not require) that a=20
session rejected due to lack of=20
mutually-supported languages use 488 or 606, and=20
also include a Warning header field with the=20
suggested 308 code that the draft would register.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
We are what we repeatedly do. Excellence, then, is not an act but a habit.
                                --Aristotle


From nobody Wed Feb 22 12:20:37 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5F2129AD8; Wed, 22 Feb 2017 12:20:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P-7VTuMP9V12; Wed, 22 Feb 2017 12:20:30 -0800 (PST)
Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (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 4368A129AB6; Wed, 22 Feb 2017 12:20:30 -0800 (PST)
Received: by mail-pf0-x244.google.com with SMTP id 68so205676pfx.2; Wed, 22 Feb 2017 12:20:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=lCArjO2eVrxE7WpzLvSL3oKJLPblC2Hqa3J86RM6z04=; b=VS5y/p6OgSqGjW6cEGSiPP1m5VaFzm/nujebl900b7CARn/ZYbv3pyqiWdoPqQL1bl CF/YaqheThTfUbJCmGAMEePKAtCM7ePRtjNHnf8P628dFsd2Yf0HRwO1R1AxncazXO5N Q+vvxDiVGBq24yrFW9SGLtwPpt4M9YmT55PNlSEO2FC2NyNVJxl9fiy3ogqVHL3ihhbH jbOen/G2Whh3J3dCL4iNnfUwfdehsw7nnQgtGIWrcWAJ8Nw9E8E9+n/v45/uJ2+PLxah Y5tO9NfUq6oGsnIs7e3swNrxpazeV8KN3XO0DhXFkyNdyw0sp2pxynMJSYUtzKNUUhJ3 aYvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=lCArjO2eVrxE7WpzLvSL3oKJLPblC2Hqa3J86RM6z04=; b=qYHNySPFV6yencdeUeVzHsKTcg2BrIyz3AmTxpgy+jwbDowuFTPB3754yLxAnv2w7w 3OUwg9enNrB6MawclwNYeaKeW4Y4w4iWPAtFYLWOgDTLINLl9szQeD0jnghH7WV/kPDU mGKYWyG3F76+FTMi2RYWPmqtfN3EStQW6/DHTfsPR77LmvXE9W4Y6m4wgOB+t99mWofu +J1LLx1IDzB+MiryNJxhyv9lwHXRgeeuh9UFhl2uE7L7ueJqpbJSFHfD5M7jDiYs2RQu BpK9tXwRbmAq7tjYSP2tQEyGzHeBgtIISa1OfhHufk0+9IQXIbINzgkoxKZ1HKLEL9TX f/Sg==
X-Gm-Message-State: AMke39kHPhO9TKNDy1XL82ZJov2i3z3hHWwWH7eTIPNEAhlHiMn/d7Gv2Wka2rr0gsElbg==
X-Received: by 10.84.241.76 with SMTP id u12mr50509127plm.107.1487794829790; Wed, 22 Feb 2017 12:20:29 -0800 (PST)
Received: from [192.168.178.21] ([118.149.111.84]) by smtp.gmail.com with ESMTPSA id 128sm5278309pfe.23.2017.02.22.12.20.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2017 12:20:29 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>, Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com>
Date: Thu, 23 Feb 2017 09:20:32 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <20170222144147.GC89584@hanna.meerval.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KOiXj1LcMIQMmj5unUyPg0vOZ34>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, Christopher Morrow <christopher.morrow@gmail.com>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:20:31 -0000

On 23/02/2017 03:41, Job Snijders wrote:
...
> Why publish a document that conflicts with (almost) every deployed
> global IPv6 backbone? This would be a farce.

Job is correct, and I think the document editor can find one of the
various proposed formulations that avoids the farce.

Nobody is saying that /64 isn't extremely widely used where it's
appropriate to have a portable fixed length IID. Set the default
at 64 and trust operators to change it where they need to.
That's realistic.

     Brian


From nobody Wed Feb 22 12:26:00 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF561299DC; Wed, 22 Feb 2017 12:25:52 -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 autolearn_force=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 rOInyH_Y8UhV; Wed, 22 Feb 2017 12:25:51 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 B543612999C; Wed, 22 Feb 2017 12:25:51 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cgdTw-0004dH-8i; Wed, 22 Feb 2017 20:25:48 +0000
Date: Thu, 23 Feb 2017 03:25:43 +0700
Message-ID: <m2poiaug54.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Job Snijders <job@ntt.net>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <20170222153129.GE89584@hanna.meerval.net>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FAFEtD9GhNVb5IhfmxZJcfCyw_w>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 20:25:53 -0000

>> "Conflicts with the NTT backbone" != "conficts with almost every
>> deployed backbone".
> 
> You gross over the fact that NTT connects with many other backbones, and
> that the data I shared is a reflection on both NTT's own addressing
> structure as well as peering partner's or customer's addressing.

face it job.  what we have here is non-ops telling us what we should do
and denying what we actually do and intend to keep doing.  welcome to
the ietf; we want ops here but that does not mean we want to listen to
them.

this is not new.  this is the last classful sickness needing expunging
from ipv6.  it has been a long trail.  you would have loved the insanity
of NLA/TLA; and it took some years of bloodshed to get rid of them.

randy


From nobody Wed Feb 22 13:41:16 2017
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03D50129B92; Wed, 22 Feb 2017 13:41:15 -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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 h5FN3V9sZzIj; Wed, 22 Feb 2017 13:41:10 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2a00:1d50:2::130]) by ietfa.amsl.com (Postfix) with ESMTP id CD7D6129B91; Wed, 22 Feb 2017 13:41:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 98A662CCBA; Wed, 22 Feb 2017 23:41:08 +0200 (EET) (envelope-from jari.arkko@piuha.net)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yv7PkMY3h6oQ; Wed, 22 Feb 2017 23:41:04 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 595DA2CC9C; Wed, 22 Feb 2017 23:40:59 +0200 (EET) (envelope-from jari.arkko@piuha.net)
Subject: Last Call Summary on <draft-bradner-rfc3979bis-10.txt> (Intellectual Property Rights in IETF Technology) to Best Current Practice
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_5AD199DA-1830-4715-8158-0F4525B717D5"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <148474911031.2261.11881119527780959351.idtracker@ietfa.amsl.com>
Date: Wed, 22 Feb 2017 23:40:56 +0200
Message-Id: <7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net>
References: <148474911031.2261.11881119527780959351.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v_rrBpyq32rtHVGXXOayPsUDuy0>
Cc: draft-bradner-rfc3979bis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 21:41:15 -0000

--Apple-Mail=_5AD199DA-1830-4715-8158-0F4525B717D5
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_34073D2D-2042-42AB-8990-8DC5E22D1F5E"


--Apple-Mail=_34073D2D-2042-42AB-8990-8DC5E22D1F5E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

All,

I have gone through the discussion. Here=92s what I=92d like to =
conclude,
and have told the editors to take these into account in a new version.
I have asked a version to  be published, and see if we can get that
approved in the next IESG telechat(s).

SUBSTANTIAL

* Comment from Russ Housley on Jan 19, regarding design
  teams and when the IETF work starts.


>> * Russ Housley=92s concern re: =93IETF sanctioned=94 was resolved

>> per Brian=92s and Harald's suggestions (Brian's mail on March 26).

>=20

> I do not think that the change here is sufficient based on my reading =
of the thread that followed my comments.  I think my comment is =
addressed, but not all of the points that are made in that thread.  In =
particular, the output of the design team is the contribution, not every =
alternative that is discarded before being written down or presented.  =
Also, the reference to BCP 25 seems to scope this the design teams in =
working groups, not all design teams.


Further discussion in the thread resulted in this suggested change:

Perhaps: =93=85 WG design teams [see BCP 25] and other design teams that
intend to deliver an output to the IETF =85=94

* Comment from Stewart Bryant on Jan 24, regarding item j in
  Section 1:

>   j. "Internet-Draft": a temporary document used in the IETF and RFC

>      Editor processes, as described in [RFC2026].

>=20

> SB> IDs are no longer temporary documents. There was a myth that

> SB> were temporary long after they were unofficially archived, but =
they

> SB> are now formally archived by the tools system. This is important

> SB> because they have a potential influence that stretches beyond

> SB> the notional six months.


Stewart is factually right here. I=92d propose deleting the word and
saying nothing about the documents=92 permanence or lack thereof.
The deletion was also supported by Brian Carpenter on IETF
list discussion. This RFC-to-be is not the place that discusses
IETF I-D storage practices so I don=92t think we need to explain
what the situation is, just not incorrectly refer to it :-)

* Comment from Stewart Bryant on Jan 24:

>   5.2.3      Timing of Disclosure by ADs

>=20

>   By the nature of their office, IETF area directors may become aware

>   of Contributions late in the process (for example at IETF Last Call

>   or during IESG review) and, therefor and in such cases, cannot

>   reasonably be expected to disclose IPR Covering those Contributions

>   until they become aware of them.

>=20

> SB> I made the following point as an input via another route.

> SB>

> SB> There are a number of people that would not ordinarily be expected

> SB> to see a document until the very late stages of the process.

> SB> The Gen-art reviewers, and the directorates doing cross are

> SB> reviews. It would seem reasonable to give dispensation to all

> SB> of the groups assisting the ADs in late stage reviews where

> SB> the reviewer took no part in the development of the document.

> SB>

> SB> Either the above or strike the section.


Stewart has a point here as well. Brian Carpenter suggested:

  By the nature of their office, IETF area directors or persons =
assisting
  them may become aware of Contributions late in the process =85

so lets do that.


* Comment from Stewart Bryant on Jan 24 on Section 5.4.1:

> 5.4.1. Content of IPR Disclosures

>=20

>   The IPR disclosure must

>   also list the name(s) of the inventor(s) (with respect to issued

>   patents and published patent applications) and the specific IETF

>   Document(s) or activity affected.

>=20

> SB> It is new to require the names of inventors. Given that the names

> SB> of inventors are in the published patent it would seem reasonable

> SB> to follow the principle of minimizing the actions required by

> SB> organizations outside the IETF and not add this requirement.


There has been considerable discussion on including the names
supporting the addition, and there=92s a rationale for this addition,
relating to for instance, the easy ability to identify IETF =
participants.
There are also translation concerns when patent filings incl.
inventor names are not easily readable.

I=92d suggest no changes here.

* Comment from Stewart Bryant on Jan 24 on Section 5.4.1:

>   If the IETF Document is an

>   Internet-Draft, it must be referenced by specific version number.

>=20

> SB> That is presumably the version number in which the IPR was

> SB> first observed by the IPR owner. You cover updates later

> SB> but it may be useful to clarify upfront that you do not expect

> SB> per version IPR refresh.


You are right, but I think we are already covered for this in the
draft. The text later says:

      An IPR disclosure must be updated or a new disclosure made
      promptly after any of the following has occurred =85  (4) a =
material
      change to the IETF Document covered by the Disclosure that
      causes the Disclosure to be covered by additional IPR

In other words, no need to update unless there was a material change.

* Comment from Stewart Bryant on Jan 25 on Section 5.4.1:

>>>   An IPR disclosure must list the numbers of any issued patents or

>>>   published patent applications or indicate that the disclosure is

>>>   based on unpublished patent applications.  The IPR disclosure must

>>>   also list the name(s) of the inventor(s) (with respect to issued

>>>   patents and published patent applications) and the specific IETF

>>>   Document(s) or activity affected.

>>>=20

>>> In some cases that is simply impractical. For example one might

>>> know that IPR was filed at a previous employer, for example

>>> because you were on the patent review panel, but of course

>>> would no longer have access to the documents to tease out the

>>> exact identity of the patent. All that we can expect by the first

>>> stage discloser, perhaps filing a third party disclosure, is as

>>> much information as they still have available.

>> Right. Is there a possibility to have a different rule for 3rd party =
and

>> =93regular=94 declarations?

>=20

> The text has a must, whereas the discloser can only provide that =
information

> as far as practical and with regard to the access to records they have =
available

> to them at the time they identify the need to disclose.


Perhaps the right thing to do here is to add a constraint
on information available to the person making the disclosure.

How about this:

Add to the end of Section 5.4.1 a new paragraph:

Note that there may be cases =97 such as third party declarations =97
where person making the declaration may not have all the
information. The requirements of this section only apply to
the information that is available to the person(s) making the
declaration.


* Pete Resnick=92s review noted the following about Section 2:

>> * Pete Resnick suggested to put back in the three principles to

>> Section 2 that were deleted from the previous RFC (April 11).

>> We=92ve done so; we should only make substantive changes

>> to the original RFC when there=92s clear consensus to do so.

>=20

> I can't find these in -10. I suggested that they go in at the second =
paragraph of section 2:

>=20

> OLD

>=20

> Section 1 defines...

> NEW

>=20

> RFC 2026, Section 10 established three basic principles regarding

> the IETF dealing with claims of Intellectual Property Rights:

>=20

> (a) the IETF will make no determination about the validity of any

>     particular IPR claim

> (b) the IETF following normal processes can decide to use technology

>     for which IPR disclosures have been made if it decides that such

>     a use is warranted

> (c) in order for the working group and the rest of the IETF to have

>     the information needed to make an informed decision about the

>     use of a particular technology, all those contributing to the

>     working group's discussions must disclose the existence of any

>     IPR the Contributor or other IETF participant believes Covers or

>     may ultimately Cover the technology under discussion.  This

>     applies to both Contributors and other participants, and applies

>     whether they contribute in person, via email or by other means.

>     The requirement applies to all IPR of the participant, the

>     participant's employer, sponsor, or others represented by the

>     participants, that is reasonably and personally known to the

>     participant.  No patent search is required.

>=20

> Section 1 defines...

> END


These should be adopted, as previously discussed.


* Pete Renisck=92s review noted the following on January 26:

>> In Sec. 6, put back list of penalties since it was pointed out that

>> RFC 6701 is informational only.

> Ugh. This undid a change that was (correctly) done back in -07. The =
new text in -07 was definitely ungrammatical and needed fixing. However, =
I do not believe that putting back the -06 text is appropriate in light =
of the discussion on the list regarding -08. RFC 6701 was Informational =
for a reason: It is not introducing any new sanctions. All of the =
sanctions are available under already existing IETF processes. A primary =
reason 6701 was written was because folks at the time didn't understand =
that they could be used for this purpose, just like you would use such =
remedies for any other disruption of IETF work. But we wanted to be =
clear that we weren't making new policy, which is why it's not a BCP. =
This document (which is going to be a BCP) shouldn't do anything that =
might be interpreted as a new sanctions policy. It reads as if it's =
trying to do exactly that, particularly given that the text in this =
document lists suspension of posting/participation first in the list, =
which is quite contrary to the spirit of 6701. (And let's be honest: The =
real penalties in not disclosing lie in those "available under law".) As =
was proposed back in March, please change the last paragraph of 6:

>=20

> OLD

>=20

> In addition to any remedies or defenses that may be available to

> implementers and others under the law with respect to such a

> violation (e.g., rendering the relevant IPR unenforceable), the IESG

> may, when it in good faith concludes that such a violation has

> occurred, impose penalties including, but not limited to, suspending

> the posting/participation rights of the offending individual,

> suspending the posting/participation rights of other individuals

> employed by the same company as the offending individual, amending,

> withdrawing or superseding the relevant IETF Documents, and publicly

> announcing the facts surrounding such violation, including the name

> of the offending individual and his or her employer or sponsor. See

> [RFC6701] for details.

> NEW

>=20

> In addition to any remedies available outside the IETF, actions may

> be taken inside the IETF to address violations of IPR disclosure

> policies; see [RFC6701] for details of the sanctions defined in

> various existing Best Current Practice documents.

> END

>=20

> That appeared to be the conclusion of the discussion then, and I =
didn't see anything on the list to indicate otherwise. If someone likes =
the stuff at the beginning (which I don't particularly think is =
necessary, but I won't object to if someone insists), here's an =
alternative:

>=20

> NEW

>=20

> In addition to any remedies or defenses that may be available to

> implementers and others under the law with respect to such a

> violation (e.g., rendering the relevant IPR unenforceable), sanctions

> are available through the normal IETF processes for handling

> disruptions to IETF work. See [RFC6701] for details of the sanctions

> defined in various existing Best Current Practice documents.

> END


He seems right. Please use the text (the first =93NEW=94 block above).


* Russ Housley=92s suggestions from Feb 7:

> In Section 1, definition j, please be more specific in the reference.  =
I think the intention is to reference Section 2.2 of [RFC2026].

>=20

> In Section 5.5, paragraph D, I suggest a different wording:

>=20

>      D. Licensing declarations must be made by people with appropriate

>          authorization as discussed in Section 5.6 of this document.


These should be adopted.


OTHER OBSERVATIONS AND QUESTIONS

* Observation from Stewart Bryant on Jan 24, regarding item e in
  Section 1:

>   e. "IETF": In the context of this document, the IETF includes all

>      individuals who participate in meetings, working groups, mailing

>      lists, functions and other activities which are organized or

>      initiated by ISOC, the IESG or the IAB under the general

>      designation of the Internet Engineering Task Force or IETF, but

>      solely to the extent of such participation.
> SB> I think this is a definition of so called "members of the IETF"
> SB> Certainly the term "IETF" on its own means a multitude of things
> SB> to different people and is easily confused.

This definition style is unchanged since the previous RFC. I see
no reason to make changes in this regard.

* Question from Stewart Bryant on Jan 24, regarding item B in
  Section 3.3:

>   B. Such Contributor represents that there are no limits to the
>      Contributor's ability to make the grants, acknowledgments and
>      agreements herein that are reasonably and personally known to the
>      Contributor.
>=20
> SB> I do not understand what point B above means.

It means that if you (for instance) make an IPR declaration
and say something about the license conditions, you or whoever
is helping you to make that statement, can actually make those
statements.

I don=92t think a document change is needed.

* Suggestion from Stewart Bryant on Jan 24, regarding Section
  5.4.2

>   A. An IPR disclosure must be updated or a new disclosure made

>      promptly after any of the following has occurred unless =
sufficient

>      information to identify the issued patent was disclosed when the

>      patent application was disclosed: (1) the publication of a

>      previously unpublished patent application, (2) the abandonment of

>      a patent application (3) the issuance of a patent on a previously

>      disclosed patent application ), (4) a material change to the IETF

>      Document covered by the Disclosure that causes the Disclosure to

>      be covered by additional IPR. If the patent application was

>      abandoned, then the new IPR disclosure must explicitly withdraw

>      any earlier IPR disclosures based on the application.  IPR

>      disclosures against a particular Contribution are assumed to be

>      inherited by revisions of the Contribution and by any RFCs that

>      are published from the Contribution unless the disclosure has =
been

>      updated or withdrawn.

>=20

> SB> The above is ideal, but I seriously wonder if a busy IPR group

> SB> will provide update (2) and (3). Given the application number

> SB> anyone interested can find the (2)and (3) for themselves.

> SB> Again the principle of minimizing the work of third parties

> SB> applies.


I think I mostly agree personally. But without further input from =
others,
I don=92t think a change is warranted.

* Question from Stewart Bryant on Jan 24, regarding Section
  5.7:

> 5.7. Disclosures for Oral Contributions.

>=20

>   .... then the Contributor must accompany

>   such oral Contribution with an oral declaration that he/she is aware

>   of relevant IPR in as much detail as reasonably possible

>=20

> SB> I do not recall ever seeing a purely verbal disclosure, and wonder

> SB> what the process is, how this is archived and how it is =
discovered?


Sometimes it happens that a presenter makes a statement,
e.g. that the audience should note that some IPRs may apply
and that a written declaration is forthcoming.

* Question from Stewart Bryant on Jan 24, regarding Section
  6:

> 6. Failure to Disclose

>=20

>   There may be cases in which individuals are not permitted by their

>   employers or by other factors to disclose the existence or substance

>   of patent applications or other IPR.  Since disclosure is required

>   for anyone making a Contribution or participating in IETF =
activities,

>   a person who is not willing or able to disclose IPR for this reason,

>   or any other reason, must not contribute to or participate in IETF

>   activities with respect to technologies that he or she reasonably =
and

>   personally knows to be Covered by IPR which he or she will not

>   disclose, unless that person knows that his or her employer or

>   sponsor will make the required disclosures on his or her behalf.

>=20

> SB> Doesn't this have implications for those that work or have

> SB> previously worked in the defence sector? Do we really wish

> SB> to potentially exclude such individuals? I am not sure how

> SB> we deal with the situation, but I am concerned about unintended

> SB> consequences here.


I think this is a choice that the community has wished to make,
and I personally believe it is also the only thing we can actually
do. It is not about excluding anyone, but the IETF=92s IPR rules
are actually very easy to satisfy for most participants (cf. SDOs
that would require granting RF license to other members of the
SDO, for instance). If this fundamental basis cannot be complied
to, then maybe it is best that one stays away from that topic. Do
note that it is indeed just that topic, not the whole IETF.

* Observation from Stewart Bryant on Jan 24, regarding Section
  7:

> 7. Evaluating Alternative Technologies in IETF Working Groups

>=20

>   In general, IETF working groups prefer technologies with no known =
IPR

>   claims or, for technologies with claims against them, an offer of

>   royalty-free licensing.  However, to solve a given technical =
problem,

>   IETF working groups have the discretion to adopt a technology as to

>   which IPR claims have been made if they feel that this technology is

>   superior enough to alternatives with fewer IPR claims or free

>   licensing to outweigh the potential cost of the licenses. To assist

>   these working groups, it is helpful for the IPR claimants to =
declare,

>   in their IPR Declarations, the terms, if any, on which they are

>   willing to license their IPR Covering the relevant IETF Documents.

>=20

> SB> I really do not see how a WG can properly apply the above =
considerations

> SB> given that it is not permitted to discuss the financial terms

> SB> of the licence.

> SB>

> SB> Historically this may have been less important, but with IoT this =
changes.

> SB> what would be a reasonable cost in a core router can be a =
showstopper

> SB> in a $1 device.


Perhaps, but I don=92t see another alternative. Standards organisations
cannot really become the negotiation platform for IPR costs, for
a myriad of reasons starting from competition law.

* Question from Stewart Bryant on Jan 24, regarding Section
  12:

> 12. Security Considerations

>=20

>   This memo relates to IETF process, not any particular technology.

>   There are security considerations when adopting any technology,

>   whether IPR-protected or not.  A working group should take those

>   security considerations into account as one part of evaluating the

>   technology, just as IPR is one part, but there are no known issues =
of

>   security with IPR procedures.

>=20

> SB> I wonder if this is entirely correct. How about someone who owns

> SB> IPR silently waiting until deployment and then getting an IPR

> SB> based shutdown order? With nations and quasi nations applying =
unconventional

> SB> warfare, I suspect that there is a potential IPR attack vector.


I think we are already covered for that. You have to declare if
you are a participant, or else you are breaking the rules. Once
you break the rules, but still attempt to use the court system
to collect license fees, your actions will be picked out and
potentially used against you. And if you are not a participant,
no rules that IETF can employ apply to you.

There is no question IPR claims cannot have economical and
other impacts, and the behaviour of the players certainly
affects this. I don=92t think we need to write this in the RFC,
however.

* David Rudin asked the following about two implementations on
  January 26:

> "If the two unrelated implementations of the specification that are =
required to advance from Proposed Standard to Standard have been =
produced by different organizations or individuals, or if the =
"significant implementation and successful operational experience" =
required to advance from Proposed Standard to Standard has been =
achieved, the IESG will presume that the terms are reasonable and to =
some degree non-discriminatory. Note that this also applies to the case =
where multiple implementers have concluded that no licensing is =
required."

>=20

> It's not clear to me what IETF gains by making this presumption, =
especially given that the availability of two or more implementations =
does not mean that the implementers did any patent due diligence or =
licensing around the implementation.  It does, however, potentially =
expose IESG to risks in the event of patent litigation if implementers =
are basing their decisions on IESG's presumption.


As noted by Scott, these requirements are not new. Scott also argued =
that the
time for changing this assumption is not now. And I agree. And Brian =
Carpenter
opposed changing the assumption, on the basis of practical evidence =
rather
than getting into the business of validating claims or assessing license =
conditions.

I made some additional questions to a few participants in the =
discussion,
and found out that changes in text would cause indigestion for several
participants. Hence I recommend no changes.


EDITORIAL

* Suggestions from Brian Carpenter in private e-mail on Jan 15:


>> [1]Eggert [2]Resnick
>=20
> These citations are a bit mysterious=85

Remove. That was an oversight.

* Question from Stewart Bryant on Jan 24, regarding the list in
  Section 1 item b.

> SB> It is interesting that you exclude WG Chairs from the list of

> SB> officials that you call out, and yet they can be a key player in

> SB> in deciding whether an encumbered technology progresses or not.

> SB>

> SB> Would it not be cleaner to express this in terms of "officials=94?


I will leave this to the editors to adopt or not, but I personally
would be OK adding =93A working group chair(s), on behalf of their
work working group=94.

* Suggestions from Pete Resnick in private e-mail on Feb 2:

> 16 1.m: s/features/permanence


Adopt

> 16 5.6: s/n/In


Adopt

> 16 8: Got the section number and title wrong here. It should say, "9. =
- Licensing Requirements (was 10) - Wording updated to reflect RFC 6410=94=



Adopt

> The first sentence of 5.4.2(A) is really hard to read because there's =
a long subordinate clause. I think it would read better if you used the =
same words and just reversed the order:

>=20

> OLD

> A. An IPR disclosure must be updated or a new disclosure made

> promptly after any of the following has occurred unless sufficient

> information to identify the issued patent was disclosed when the

> patent application was disclosed:

> NEW

> A. Unless sufficient information to identify the issued patent was

> disclosed when the patent application was disclosed, an IPR

> disclosure must be updated or a new disclosure made promptly after

> any of the following has occurred:

> END


Adopt.

* Suggestion from Stewart Bryant on Jan 24, regarding Section
  5.5:

> 5.5. Licensing Information in an IPR Disclosure

>=20

>   A. Since IPR disclosures will be used by IETF working groups during

>      their evaluation of alternative technical solutions, it is =
helpful

>      if an IPR disclosure includes information about licensing of the

>      IPR in case Implementing Technologies require a license.

>      Specifically, it is helpful to indicate whether, upon approval by

>      the IESG for publication as an RFC of the relevant IETF

>      specification(s), all persons will be able to obtain the right to

>      implement, use, distribute and exercise other rights with respect

>      to an Implementing Technology a) under a royalty-free and

>      otherwise reasonable and non- discriminatory license, or b) under

>      a license that contains reasonable and non-discriminatory terms

>      and conditions, including a reasonable royalty or other payment,

>      or c) without the need to obtain a license from the IPR holder

>      (e.g., a covenant not to sue).

>=20

> SB> One of the most popular IPR terms is so called MAD. It is =
surprising

> SB> that you do not call this out.

> =85

>   Some common

>   conditions include 1) terms that are fair, reasonable and non-

>   discriminatory, and which may bear royalties or other financial

>   obligations (FRAND or RAND); 2) royalty-free terms that are =
otherwise

>   fair, reasonable and non-discriminatory (RAND-z); and 3) commitments

>   not to assert declared IPR.

>=20

> SB> One of the most common (at least in the Routing area) is =
non-assert

> SB> unless the other party asserts (so called MAD)


Personally, I don=92t view MAD as a term quite in the same style
and technical specificity as, say, RAND or RF. I would suggest
not adopting this.

(Non-assert on the other hand is a more
technical term, but I also have not seen calls for adding that
from others.)

* Editorial suggestions from Brian Carpenter in his Gen-ART review
   on January 26:

>> 7. Evaluating Alternative Technologies in IETF Working Groups

> ...

>> technology in violation if this principle if there is a very good

>=20

> s/if this principle/of this principle/


Adopt

>> 13. Changes Since RFC 3979 and RFC 4879

>> 16. Changes Since RFC 3979

>=20

> Should the preamble to these sections state that they are provided

> for informational purposes only and that in case of doubt the text

> of sections 1-12 prevails?

>=20

> Should these two sections be merged?


Yes. Adopt both suggestions.


* Pete Resnick=92s review suggested the following edits
  to Section 4.1:

>> * Pete Resnick suggested to put back the material from

>> RFC 3979 Section 4.1 that were deleted from the

>> previous RFC (April 11), which we=92ve also done.

>=20

> 4(D) in the new version. Thanks for that. I see that the section title =
and first sentence of 4(D) are the text from -08 instead of the original =
text from 3979. That's OK, but personally, I think the section title has =
gotten unwieldy and the changes to the first sentence make it somewhat =
less clear. I'd suggest just eliminating the title (so it matches the =
form of A, B, and C) and putting the example into the first sentence:

>=20

> OLD

>=20

> D. Determination of Provision of Reasonable and Non-discriminatory

>   Terms

>   The IESG will not make any determination that any terms for the

>   use of an Implementing Technology has been fulfilled in practice.

>   It will instead...

> NEW

>=20

> D. The IESG will not make any determination that any terms for the

>   use of an Implementing Technology (e.g., the assurance of

>   reasonable and non-discriminatory terms) has been fulfilled in

>   practice. It will instead...

> END


These should be adopted.


* Pete Resnick=92s review said:

>> * Pete Resnick had a concern on adding the word =93all=94 to Section =
7

>> (April 11). This was an oversight, and has been corrected.

>=20

> Thanks for that. Personally, I don't think the extra text at the end =
of that paragraph that went in as of -09 really adds anything. 3979 =
already said that there is a consensus that MTI security must be =
royalty-free, so of course there would need to be a consensus to do =
otherwise. I'm in favor of sticking to the language of 3979 unless =
something really changed or clarification is truly necessary, so I'd ask =
to remove the new stuff. That said, I won't go to the mat about this =
change if folks want it in there, but if we go with the new text, please =
fix the typo: s/in violation if this principle/in violation of this =
principle


I think we are OK either way, and I will leave the choice to the =
editors.


* Pete Resnick notes about the change notes:

>> update abstract to make it clear that this document replaces RFC 2026

>> section 10

> If we're going to do that, we should probably do it the same way that =
3979 did:

>=20

> OLD

>=20

>                                                    This memo

> replaces section 10 of RFC 2026 and obsoletes RFC 3979 and RFC 4879.

> NEW

>=20

>                                                    This memo

> updates RFC 2026 and, with RFC 5378, replaces Section 10 of

> RFC 2026.  This memo also obsoletes RFC 3979 and RFC 4879.

> END

>=20

> BTW: Whichever text is used should probably also be used in the last =
sentence of the first paragraph of section 2. It still uses the previous =
language there.

>=20

>> In Sec. 3.1, added sentence about WGs that summarizes ideas from Sec.

>> 7.

> That's fine, but in that sentence, please change "possible" to =
"reasonably possible". In other places in the document it's used =
informally, but 3.1 is a statement of the "General Policy", so we should =
be a bit more precise.


These should be adopted.


* Pete Resnick=92s minor editorial suggestions from January 26:

> In section 1, in the definition of "Contribution", "this definition" =
changed to "this specification". I think I see why that was done (to =
avoid confusing whether "this definition" is referring to the definition =
of "Contribution" or the definition of entire document.) But calling =
either of those a "specification" is a bit weird, especially considering =
that in context, every other use of "specification" in this document is =
about a technical specification. I'd suggest either changing "this =
definition" to "this policy" if the intention is the entire document, or =
"this definition of Contribution" if that's what's meant.


Please adopt =93this policy=94.

* Pete Resnick=92s minor editorial suggestions from January 26:
> Also, there were a couple of minor changes in 5.2.2. In both =
instances, please change "Covers" to "may Cover". I actually think that =
makes it stronger and leaves less ambiguity: What triggers the =
disclosure is that you simply realize that IPR may cover the =
contribution; you don't have to come to some sort of grand final =
determination that it does surely cover (and how could you know that for =
sure anyway?).
>=20

Right. Adopt this.

* Russ Housley=92s suggestions from Feb 7:

> In Section 7, please provide pointers for FRAND, RAND, and RAND-z.

>=20

> In Section 11, please drop =93legal=94 from the first sentence in the =
second paragraph:

>=20

>   The rules that apply =85


These should be adopted.

* Russ Housley=92s editorial nits from Feb 7:

> Nits =85

>=20

> I see =93this memo=94 and =93this document=94.  Either one is fine =
with me, but please pick one and use it throughout.

>=20

> Section 2: s/IETF and its Participants/IETF and IETF Participants/

>=20

> Section 5.2.3:  s/IETF area directors/IETF Area Directors/

>=20

> Section 5.3: s/RFC-Editor/RFC Editor/

>=20

> Please remove the period at the end of the heading for Section 5.4.2.

>=20

> Section 5.4.2: s/drafts/Internet-Drafts/

>=20

> Section 5.4.2, paragraph A:

>   s/application (3)/application, (3)/

>   s/application ), (4)/application, (4)/

>=20

> Section 5.4.2, paragraph D:

>   s/submit to IETF an update/submit an update/

>   s/Secretariat/IETF Secretariat/ (several places)

>=20

> Section 5.5, paragraph A: s/non- discriminatory/non-discriminatory/

>=20

> Section 5.6:

>   s/IPR that is (a) owned/IPR that (a) is owned/

>   s/ or (b) that such persons/; or (b) persons/

>   s/ or (c) that such persons/; or (c) persons/

>   s/, or (d) in the case of an individual, the individual/; or (d) an =
individual/

>=20

> Section 6: s/violation of IETF process/violation of the IETF Standards =
Process/

>=20

> Section 7: s/Working groups and areas may/IETF Areas and IETF working =
groups/


These should be adopted.

Jari

--Apple-Mail=_34073D2D-2042-42AB-8990-8DC5E22D1F5E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;">All,<div><br></div><div>I have =
gone through the discussion. Here=92s what I=92d like to =
conclude,<div>and have told the editors to take these into account in a =
new version.</div><div>I have asked a version to &nbsp;be published, and =
see if we can get that</div><div>approved in the next IESG =
telechat(s).<div><div><br></div><div><b>SUBSTANTIAL</b></div><div><br></di=
v><div>* Comment from Russ Housley on Jan 19, regarding =
design</div><div>&nbsp; teams and when the IETF work =
starts.</div><div><br></div><div><blockquote =
type=3D"cite"></blockquote></div></div><blockquote style=3D"margin: 0px =
0px 0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">* Russ Housley=92s concern re: =
=93IETF sanctioned=94 was =
resolved</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">per Brian=92s and Harald's =
suggestions (Brian's mail on March =
26).</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">I do =
not think that the change here is sufficient based on my reading of the =
thread that followed my comments. &nbsp;I think my comment is addressed, =
but not all of the points that are made in that thread. &nbsp;In =
particular, the output of the design team is the contribution, not every =
alternative that is discarded before being written down or presented. =
&nbsp;Also, the reference to BCP 25 seems to scope this the design teams =
in working groups, not all design =
teams.</blockquote></div><div><br></div><div>Further discussion in the =
thread resulted in this suggested =
change:</div><div><br></div><div>Perhaps: =93=85 WG design teams [see =
BCP 25] and other design teams that</div><div>intend to deliver an =
output to the IETF =85=94</div></blockquote><div><div><br></div><div>* =
Comment from Stewart Bryant on Jan 24, regarding item j in<br>&nbsp; =
Section 1:</div><div><br></div><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><blockquote type=3D"cite">&nbsp; =
j. "Internet-Draft": a temporary document used in the IETF and =
RFC</blockquote></div><div><blockquote type=3D"cite">&nbsp; &nbsp; =
&nbsp;Editor processes, as described in =
[RFC2026].</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 IDs are no longer temporary documents. There was a myth =
that</blockquote></div><div><blockquote type=3D"cite">SB&gt; were =
temporary long after they were unofficially archived, but =
they</blockquote></div><div><blockquote type=3D"cite">SB&gt; are now =
formally archived by the tools system. This is =
important</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
because they have a potential influence that stretches =
beyond</blockquote></div><div><blockquote type=3D"cite">SB&gt; the =
notional six months.</blockquote></div><div><br></div><div>Stewart is =
factually right here. I=92d propose deleting the word =
and</div><div>saying nothing about the documents=92 permanence or lack =
thereof.</div><div>The deletion was also supported by Brian Carpenter on =
IETF</div><div>list discussion. This RFC-to-be is not the place that =
discusses</div><div>IETF I-D storage practices so I don=92t think we =
need to explain</div><div>what the situation is, just not incorrectly =
refer to it :-)</div><div><br></div></blockquote><div>* Comment from =
Stewart Bryant on Jan 24:</div><div><br></div><blockquote style=3D"margin:=
 0px 0px 0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite">&nbsp; 5.2.3 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Timing of =
Disclosure by ADs</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;By the nature of their office, IETF area =
directors may become aware</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;of Contributions late in the process (for =
example at IETF Last Call</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;or during IESG review) and, therefor and in =
such cases, cannot</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;reasonably be expected to disclose IPR =
Covering those Contributions</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;until they become aware of =
them.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 I made the following point as an input via another =
route.</blockquote></div><div><blockquote =
type=3D"cite">SB&gt;</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; There are a number of people that would not =
ordinarily be expected</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; to see a document until the very late stages of the =
process.</blockquote></div><div><blockquote type=3D"cite">SB&gt; The =
Gen-art reviewers, and the directorates doing cross =
are</blockquote></div><div><blockquote type=3D"cite">SB&gt; reviews. It =
would seem reasonable to give dispensation to =
all</blockquote></div><div><blockquote type=3D"cite">SB&gt; of the =
groups assisting the ADs in late stage reviews =
where</blockquote></div><div><blockquote type=3D"cite">SB&gt; the =
reviewer took no part in the development of the =
document.</blockquote></div><div><blockquote =
type=3D"cite">SB&gt;</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; Either the above or strike the =
section.</blockquote></div><div><br></div><div>Stewart has a point here =
as well. Brian Carpenter suggested:</div><div><br></div>&nbsp; By the =
nature of their office, IETF area directors or persons =
assisting<br>&nbsp;&nbsp;them may become aware of Contributions late in =
the process =85</blockquote><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><br></blockquote><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: 0px;">so lets =
do that.</blockquote><div><blockquote =
type=3D"cite"></blockquote></div><div><br></div><div>* Comment from =
Stewart Bryant on Jan 24 on Section =
5.4.1:</div><div><br></div></div><blockquote style=3D"margin: 0px 0px =
0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite">5.4.1. Content of IPR =
Disclosures</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;The IPR disclosure =
must</blockquote></div><div><blockquote type=3D"cite">&nbsp;&nbsp;also =
list the name(s) of the inventor(s) (with respect to =
issued</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;patents and published patent applications) and =
the specific IETF</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;Document(s) or activity =
affected.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 It is new to require the names of inventors. Given that the =
names</blockquote></div><div><blockquote type=3D"cite">SB&gt; of =
inventors are in the published patent it would seem =
reasonable</blockquote></div><div><blockquote type=3D"cite">SB&gt; to =
follow the principle of minimizing the actions required =
by</blockquote></div><div><blockquote type=3D"cite">SB&gt; organizations =
outside the IETF and not add this =
requirement.</blockquote></div><div><br></div><div>There has been =
considerable discussion on including the names</div><div>supporting the =
addition, and there=92s a rationale for this =
addition,</div><div>relating to for instance, the easy ability to =
identify IETF participants.</div><div>There are also translation =
concerns when patent filings incl.</div><div>inventor names are not =
easily readable.</div><div><br></div><div>I=92d suggest no changes =
here.</div></blockquote><div><div><br></div><div>* Comment from Stewart =
Bryant on Jan 24 on Section 5.4.1:</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite">&nbsp; If the IETF Document is =
an</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;Internet-Draft, it must be referenced by =
specific version number.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 That is presumably the version number in which the IPR =
was</blockquote></div><div><blockquote type=3D"cite">SB&gt; first =
observed by the IPR owner. You cover updates =
later</blockquote></div><div><blockquote type=3D"cite">SB&gt; but it may =
be useful to clarify upfront that you do not =
expect</blockquote></div><div><blockquote type=3D"cite">SB&gt; per =
version IPR refresh.</blockquote></div><div><br></div><div>You are =
right, but I think we are already covered for this in =
the</div><div>draft. The text later =
says:</div><div><br></div><div>&nbsp; &nbsp; &nbsp; An IPR disclosure =
must be updated or a new disclosure made</div><div>&nbsp; &nbsp; &nbsp; =
promptly after any of the following has occurred =85 &nbsp;(4) a =
material</div><div>&nbsp; &nbsp; &nbsp; change to the IETF Document =
covered by the Disclosure that</div><div>&nbsp; &nbsp; &nbsp; causes the =
Disclosure to be covered by additional IPR</div><div><br></div><div>In =
other words, no need to update unless there was a material =
change.</div></blockquote><div><div><br></div><div>* Comment from =
Stewart Bryant on Jan 25 on Section =
5.4.1:</div><div><br></div></div><blockquote style=3D"margin: 0px 0px =
0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;An IPR disclosure must list the numbers of any =
issued patents =
or</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;published patent applications or indicate that =
the disclosure =
is</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;based on unpublished patent applications. =
&nbsp;The IPR disclosure =
must</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;also list the name(s) of the inventor(s) (with =
respect to =
issued</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;patents and published patent applications) and =
the specific =
IETF</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite">&nbsp;&nbsp;Document(s) or activity =
affected.</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote =
type=3D"cite"><br></blockquote></blockquote></blockquote></div><div><block=
quote type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">In=
 some cases that is simply impractical. For example one =
might</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">know =
that IPR was filed at a previous employer, for =
example</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">because =
you were on the patent review panel, but of =
course</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">would =
no longer have access to the documents to tease out =
the</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">exact =
identity of the patent. All that we can expect by the =
first</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">stage =
discloser, perhaps filing a third party disclosure, is =
as</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><blockquote type=3D"cite">much =
information as they still have =
available.</blockquote></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">Right. Is there a possibility to =
have a different rule for 3rd party =
and</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">=93regular=94 =
declarations?</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">The =
text has a must, whereas the discloser can only provide that =
information</blockquote></div><div><blockquote type=3D"cite">as far as =
practical and with regard to the access to records they have =
available</blockquote></div><div><blockquote type=3D"cite">to them at =
the time they identify the need to =
disclose.</blockquote></div><div><br></div><div>Perhaps the right thing =
to do here is to add a constraint</div><div>on information available to =
the person making the disclosure.</div><div><br></div><div>How about =
this:</div><div><br></div><div>Add to the end of Section 5.4.1 a new =
paragraph:</div><div><br></div><div>Note that there may be cases =97 =
such as third party declarations =97</div><div>where person making the =
declaration may not have all the</div><div>information. The requirements =
of this section only apply to</div><div>the information that is =
available to the person(s) making =
the</div><div>declaration.</div></blockquote><div><div><blockquote =
type=3D"cite"><blockquote =
type=3D"cite"></blockquote></blockquote></div><div><br></div><div>* Pete =
Resnick=92s review noted the following about Section =
2:</div></div><div><br></div><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">* Pete =
Resnick suggested to put back in the three principles =
to</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">Section =
2 that were deleted from the previous RFC (April =
11).</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">We=92ve =
done so; we should only make substantive =
changes</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">to the =
original RFC when there=92s clear consensus to do =
so.</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">I can't find these in -10. I =
suggested that they go in at the second paragraph of section =
2:</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif">OLD</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">Section 1 =
defines...</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">NEW</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">RFC 2026, Section 10 established =
three basic principles =
regarding</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">the IETF dealing with claims of Intellectual =
Property Rights:</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">(a) the IETF will make no =
determination about the validity of =
any</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; particular IPR =
claim</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">(b) the IETF following normal processes can decide =
to use technology</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; for which IPR =
disclosures have been made if it decides that =
such</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; a use is =
warranted</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">(c) in order for the working group and the rest of =
the IETF to have</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; the information =
needed to make an informed decision about =
the</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; use of a particular technology, all =
those contributing to the</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; working group's =
discussions must disclose the existence of =
any</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; IPR the Contributor or other IETF =
participant believes Covers or</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; may ultimately =
Cover the technology under discussion. =
&nbsp;This</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; applies to both Contributors and other =
participants, and applies</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; whether they =
contribute in person, via email or by other =
means.</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; The requirement applies to all IPR of =
the participant, the</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; participant's =
employer, sponsor, or others represented by =
the</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">&nbsp; &nbsp; participants, that is reasonably and =
personally known to the</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">&nbsp; &nbsp; participant. =
&nbsp;No patent search is =
required.</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">Section 1 =
defines...</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">END</font></blockquote></div><div><div =
style=3D"font-family: sans-serif;"><br></div></div><div><div =
style=3D"font-family: sans-serif;">These should be adopted, as =
previously discussed.</div></div><div style=3D"font-family: =
sans-serif;"><br></div></blockquote><div><div><div><div></div><blockquote =
type=3D"cite"><div></div></blockquote></div></div><div =
style=3D"font-family: sans-serif;">* Pete Renisck=92s review noted the =
following on January 26:</div><div style=3D"font-family: =
sans-serif;"><br></div></div><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">In =
Sec. 6, put back list of penalties since it was pointed out =
that</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><font face=3D"sans-serif">RFC =
6701 is informational only. &nbsp; =
&nbsp;</font></blockquote></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">Ugh. This undid a change that =
was (correctly) done back in -07. The new text in -07 was definitely =
ungrammatical and needed fixing. However, I do not believe that putting =
back the -06 text is appropriate in light of the discussion on the list =
regarding -08. RFC 6701 was Informational for a reason: It is not =
introducing any new sanctions. All of the sanctions are available under =
already existing IETF processes. A primary reason 6701 was written was =
because folks at the time didn't understand that they could be used for =
this purpose, just like you would use such remedies for any other =
disruption of IETF work. But we wanted to be clear that we weren't =
making new policy, which is why it's not a BCP. This document (which is =
going to be a BCP) shouldn't do anything that might be interpreted as a =
new sanctions policy. It reads as if it's trying to do exactly that, =
particularly given that the text in this document lists suspension of =
posting/participation first in the list, which is quite contrary to the =
spirit of 6701. (And let's be honest: The real penalties in not =
disclosing lie in those "available under law".) As was proposed back in =
March, please change the last paragraph of =
6:</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif">OLD</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">In addition to any remedies or =
defenses that may be available =
to</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">implementers and others under the law with respect =
to such a</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">violation (e.g., rendering the relevant IPR =
unenforceable), the IESG</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">may, when it in good faith =
concludes that such a violation =
has</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">occurred, impose penalties including, but not =
limited to, suspending</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">the posting/participation rights =
of the offending individual,</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">suspending the =
posting/participation rights of other =
individuals</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">employed by the same company as the offending =
individual, amending,</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">withdrawing or superseding the =
relevant IETF Documents, and =
publicly</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">announcing the facts surrounding such violation, =
including the name</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">of the offending individual and =
his or her employer or sponsor. =
See</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">[RFC6701] for =
details.</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">NEW</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">In addition to any remedies =
available outside the IETF, actions =
may</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">be taken inside the IETF to address violations of =
IPR disclosure</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">policies; see [RFC6701] for =
details of the sanctions defined =
in</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">various existing Best Current Practice =
documents.</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">END</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">That appeared to be the =
conclusion of the discussion then, and I didn't see anything on the list =
to indicate otherwise. If someone likes the stuff at the beginning =
(which I don't particularly think is necessary, but I won't object to if =
someone insists), here's an =
alternative:</font></blockquote></div><div><blockquote type=3D"cite"><font=
 face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif">NEW</font></blockquote></div><div><blockquote =
type=3D"cite"><font =
face=3D"sans-serif"><br></font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">In addition to any remedies or =
defenses that may be available =
to</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">implementers and others under the law with respect =
to such a</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">violation (e.g., rendering the relevant IPR =
unenforceable), sanctions</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">are available through the normal =
IETF processes for handling</font></blockquote></div><div><blockquote =
type=3D"cite"><font face=3D"sans-serif">disruptions to IETF work. See =
[RFC6701] for details of the =
sanctions</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">defined in various existing Best Current Practice =
documents.</font></blockquote></div><div><blockquote type=3D"cite"><font =
face=3D"sans-serif">END</font></blockquote></div><div><div =
style=3D"font-family: sans-serif;"><br></div></div><div><div =
style=3D"font-family: sans-serif;">He seems right. Please use the text =
(the first =93NEW=94 block =
above).</div></div></blockquote><div><div><blockquote =
type=3D"cite"><div></div></blockquote></div><div style=3D"font-family: =
sans-serif;"><br></div><div style=3D"font-family: =
sans-serif;"><div><div>* Russ Housley=92s suggestions from Feb =
7:</div><div><br></div><div></div></div><blockquote style=3D"margin: 0px =
0px 0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite">In Section 1, definition j, please be more =
specific&nbsp;in the reference. &nbsp;I think the intention is to =
reference Section 2.2 of [RFC2026].</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">In =
Section 5.5, paragraph D, I suggest a different =
wording:</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;D. Licensing declarations =
must be made by people with =
appropriate</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;author=
ization as discussed in Section 5.6 of this =
document.</blockquote></div><div><blockquote style=3D"font-family: =
Helvetica; margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><br></blockquote><span style=3D"font-family: Helvetica;">These =
should be adopted.</span></div><div><span style=3D"font-family: =
Helvetica;"><br></span></div><div><span style=3D"font-family: =
Helvetica;"><br></span></div></blockquote></div><div><b>OTHER =
OBSERVATIONS AND QUESTIONS</b></div><div><br></div><div>* Observation =
from Stewart Bryant on Jan 24, regarding item e in</div><div>&nbsp; =
Section 1:</div><div><blockquote style=3D"margin: 0px 0px 0px 40px; =
border: none; padding: 0px;"><div><br></div><div><blockquote =
type=3D"cite">&nbsp; e. "IETF": In the context of this document, the =
IETF includes all</blockquote></div><div><blockquote type=3D"cite">&nbsp; =
&nbsp; &nbsp;individuals who participate in meetings, working groups, =
mailing</blockquote></div><div><blockquote type=3D"cite">&nbsp; &nbsp; =
&nbsp;lists, functions and other activities which are organized =
or</blockquote></div><div><blockquote type=3D"cite">&nbsp; &nbsp; =
&nbsp;initiated by ISOC, the IESG or the IAB under the =
general</blockquote></div><div><blockquote type=3D"cite">&nbsp; &nbsp; =
&nbsp;designation of the Internet Engineering Task Force or IETF, =
but</blockquote></div><div><blockquote type=3D"cite">&nbsp; &nbsp; =
&nbsp;solely to the extent of such =
participation.</blockquote></div><blockquote type=3D"cite">SB&gt; I =
think this is a definition of so called "members of the =
IETF"</blockquote><blockquote type=3D"cite">SB&gt; Certainly the term =
"IETF" on its own means a multitude of things</blockquote><blockquote =
type=3D"cite">SB&gt; to different people and is easily =
confused.</blockquote><div><br></div><div>This definition style is =
unchanged since the previous RFC. I see</div><div>no reason to make =
changes in this =
regard.</div></blockquote></div><div></div><div><br></div><div><div>* =
Question from Stewart Bryant on Jan 24, regarding item B =
in</div><div>&nbsp; Section =
3.3:</div></div><div><br></div><div></div><blockquote style=3D"margin: =
0px 0px 0px 40px; border: none; padding: 0px;"><blockquote =
type=3D"cite">&nbsp; B. Such Contributor represents that there are no =
limits to the</blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Contributor's ability to =
make the grants, acknowledgments and</blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;agreements herein that are =
reasonably and personally known to the</blockquote><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Contributor.</blockquote><bloc=
kquote type=3D"cite"><br></blockquote><blockquote type=3D"cite">SB&gt; I =
do not understand what point B above =
means.</blockquote><div><br></div><div>It means that if you (for =
instance) make an IPR declaration</div><div>and say something about the =
license conditions, you or whoever</div><div>is helping you to make that =
statement, can actually make =
those</div><div>statements.</div><div><br></div><div>I don=92t think a =
document change is needed.</div></blockquote><div><br></div><div>* =
Suggestion from Stewart Bryant on Jan 24, regarding =
Section</div><div>&nbsp; 5.4.2</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite">&nbsp; A. An IPR disclosure must be =
updated or a new disclosure made</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;promptly after any of the =
following has occurred unless =
sufficient</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;information to identify the =
issued patent was disclosed when the</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;patent application was =
disclosed: (1) the publication of a</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;previously unpublished =
patent application, (2) the abandonment =
of</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a patent application (3) the =
issuance of a patent on a previously</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;disclosed patent application =
), (4) a material change to the IETF</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Document covered by the =
Disclosure that causes the Disclosure =
to</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;be covered by additional =
IPR. If the patent application was</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;abandoned, then the new IPR =
disclosure must explicitly withdraw</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;any earlier IPR disclosures =
based on the application. &nbsp;IPR</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;disclosures against a =
particular Contribution are assumed to =
be</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;inherited by revisions of =
the Contribution and by any RFCs that</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;are published from the =
Contribution unless the disclosure has =
been</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;updated or =
withdrawn.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 The above is ideal, but I seriously wonder if a busy IPR =
group</blockquote></div><div><blockquote type=3D"cite">SB&gt; will =
provide update (2) and (3). Given the application =
number</blockquote></div><div><blockquote type=3D"cite">SB&gt; anyone =
interested can find the (2)and (3) for =
themselves.</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
Again the principle of minimizing the work of third =
parties</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
applies.</blockquote></div><div><br></div><div>I think I mostly agree =
personally. But without further input from others,</div><div>I don=92t =
think a change is =
warranted.</div></blockquote><div><div><br></div><div><div>* Question =
from Stewart Bryant on Jan 24, regarding Section</div><div>&nbsp; =
5.7:</div></div><div><br></div></div><blockquote style=3D"margin: 0px =
0px 0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite">5.7. Disclosures for Oral =
Contributions.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;.... then the Contributor must =
accompany</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;such oral Contribution with an oral =
declaration that he/she is aware</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;of relevant IPR in as much detail as =
reasonably possible</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 I do not recall ever seeing a purely verbal disclosure, and =
wonder</blockquote></div><div><blockquote type=3D"cite">SB&gt; what the =
process is, how this is archived and how it is =
discovered?</blockquote></div><div><br></div><div>Sometimes it happens =
that a presenter makes a statement,</div><div>e.g. that the audience =
should note that some IPRs may apply</div><div>and that a written =
declaration is =
forthcoming.</div></blockquote><div><div><br></div><div><div>* Question =
from Stewart Bryant on Jan 24, regarding Section</div><div>&nbsp; =
6:</div></div><div><br></div></div><blockquote style=3D"margin: 0px 0px =
0px 40px; border: none; padding: 0px;"><div><blockquote type=3D"cite">6. =
Failure to Disclose</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;There may be cases in which individuals are =
not permitted by their</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;employers or by other factors to disclose the =
existence or substance</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;of patent applications or other IPR. =
&nbsp;Since disclosure is required</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;for anyone making a Contribution or =
participating in IETF activities,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;a person who is not willing or able to =
disclose IPR for this reason,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;or any other reason, must not contribute to or =
participate in IETF</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;activities with respect to technologies that =
he or she reasonably and</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;personally knows to be Covered by IPR which he =
or she will not</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;disclose, unless that person knows that his or =
her employer or</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;sponsor will make the required disclosures on =
his or her behalf.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 Doesn't this have implications for those that work or =
have</blockquote></div><div><blockquote type=3D"cite">SB&gt; previously =
worked in the defence sector? Do we really =
wish</blockquote></div><div><blockquote type=3D"cite">SB&gt; to =
potentially exclude such individuals? I am not sure =
how</blockquote></div><div><blockquote type=3D"cite">SB&gt; we deal with =
the situation, but I am concerned about =
unintended</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
consequences here.</blockquote></div><div><br></div><div>I think this is =
a choice that the community has wished to make,</div><div>and I =
personally believe it is also the only thing we can =
actually</div><div>do. It is not about excluding anyone, but the IETF=92s =
IPR rules</div><div>are actually very easy to satisfy for most =
participants (cf. SDOs</div><div>that would require granting RF license =
to other members of the</div><div>SDO, for instance). If this =
fundamental basis cannot be complied</div><div>to, then maybe it is best =
that one stays away from that topic. Do</div><div>note that it is indeed =
just that topic, not the whole =
IETF.</div></blockquote><div><div><br></div><div><div>* Observation from =
Stewart Bryant on Jan 24, regarding Section</div><div>&nbsp; =
7:</div></div><div><br></div></div><blockquote style=3D"margin: 0px 0px =
0px 40px; border: none; padding: 0px;"><div><blockquote type=3D"cite">7. =
Evaluating Alternative Technologies in IETF Working =
Groups</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;In general, IETF working groups prefer =
technologies with no known IPR</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;claims or, for technologies with claims =
against them, an offer of</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;royalty-free licensing. &nbsp;However, to =
solve a given technical problem,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;IETF working groups have the discretion to =
adopt a technology as to</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;which IPR claims have been made if they feel =
that this technology is</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;superior enough to alternatives with fewer IPR =
claims or free</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;licensing to outweigh the potential cost of =
the licenses. To assist</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;these working groups, it is helpful for the =
IPR claimants to declare,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;in their IPR Declarations, the terms, if any, =
on which they are</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;willing to license their IPR Covering the =
relevant IETF Documents.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 I really do not see how a WG can properly apply the above =
considerations</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
given that it is not permitted to discuss the financial =
terms</blockquote></div><div><blockquote type=3D"cite">SB&gt; of the =
licence.</blockquote></div><div><blockquote =
type=3D"cite">SB&gt;</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; Historically this may have been less important, but =
with IoT this changes.</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; what would be a reasonable cost in a core router =
can be a showstopper</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; in a $1 =
device.</blockquote></div><div><br></div><div>Perhaps, but I don=92t see =
another alternative. Standards organisations</div><div>cannot really =
become the negotiation platform for IPR costs, for</div><div>a myriad of =
reasons starting from competition =
law.</div></blockquote><div><div><br></div><div><div>* Question from =
Stewart Bryant on Jan 24, regarding Section</div><div>&nbsp; =
12:</div></div><div><br></div><div></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite">12. Security =
Considerations</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;This memo relates to IETF process, not any =
particular technology.</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;There are security considerations when =
adopting any technology,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;whether IPR-protected or not. &nbsp;A working =
group should take those</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;security considerations into account as one =
part of evaluating the</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;technology, just as IPR is one part, but there =
are no known issues of</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;security with IPR =
procedures.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 I wonder if this is entirely correct. How about someone who =
owns</blockquote></div><div><blockquote type=3D"cite">SB&gt; IPR =
silently waiting until deployment and then getting an =
IPR</blockquote></div><div><blockquote type=3D"cite">SB&gt; based =
shutdown order? With nations and quasi nations applying =
unconventional</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
warfare, I suspect that there is a potential IPR attack =
vector.</blockquote></div><div><br></div><div>I think we are already =
covered for that. You have to declare if</div><div>you are a =
participant, or else you are breaking the rules. Once</div><div>you =
break the rules, but still attempt to use the court system</div><div>to =
collect license fees, your actions will be picked out =
and</div><div>potentially used against you. And if you are not a =
participant,</div><div>no rules that IETF can employ apply to =
you.</div><div><br></div><div>There is no question IPR claims cannot =
have economical and</div><div>other impacts, and the behaviour of the =
players certainly</div><div>affects this. I don=92t think we need to =
write this in the =
RFC,</div><div>however.</div></blockquote><div><div><br></div><div>* =
David Rudin asked the following about two implementations =
on</div><div>&nbsp; January 26:</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite">"If the two unrelated =
implementations of the specification that are required to advance from =
Proposed Standard to Standard have been produced by different =
organizations or individuals, or if the "significant implementation and =
successful operational experience" required to advance from Proposed =
Standard to Standard has been achieved, the IESG will presume that the =
terms are reasonable and to some degree non-discriminatory. Note that =
this also applies to the case where multiple implementers have concluded =
that no licensing is required."</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">It's =
not clear to me what IETF gains by making this presumption, especially =
given that the availability of two or more implementations does not mean =
that the implementers did any patent due diligence or licensing around =
the implementation. &nbsp;It does, however, potentially expose IESG to =
risks in the event of patent litigation if implementers are basing their =
decisions on IESG's =
presumption.</blockquote></div><div><br></div><div>As noted by Scott, =
these requirements are not new. Scott also argued that =
the</div><div><div>time for changing this assumption is not now. And I =
agree. And Brian Carpenter</div><div>opposed changing the assumption, on =
the basis of practical evidence rather</div><div>than getting into the =
business of validating claims or assessing license =
conditions.</div><div><br></div><div>I made some additional questions to =
a few participants in the discussion,</div></div><div>and found out that =
changes in text would cause indigestion for =
several</div><div>participants. Hence I recommend no =
changes.</div></blockquote><div><div><br></div><div><br></div><div><b>EDIT=
ORIAL</b></div><div><br></div><div>* Suggestions from Brian Carpenter in =
private e-mail on Jan 15:</div><div><br></div><div><blockquote =
type=3D"cite"></blockquote></div><blockquote style=3D"margin: 0px 0px =
0px 40px; border: none; padding: 0px;"><blockquote =
type=3D"cite"><blockquote type=3D"cite">[1]Eggert =
[2]Resnick</blockquote></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">These citations =
are a bit mysterious=85</blockquote><div><br></div><div>Remove. That was =
an oversight.</div></blockquote><div><br></div><div>* Question from =
Stewart Bryant on Jan 24, regarding the list in</div><div>&nbsp; Section =
1 item b.</div><div><br></div><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><blockquote type=3D"cite">SB&gt; =
It is interesting that you exclude WG Chairs from the list =
of</blockquote></div><div><blockquote type=3D"cite">SB&gt; officials =
that you call out, and yet they can be a key player =
in</blockquote></div><div><blockquote type=3D"cite">SB&gt; in deciding =
whether an encumbered technology progresses or =
not.</blockquote></div><div><blockquote =
type=3D"cite">SB&gt;</blockquote></div><div><blockquote =
type=3D"cite">SB&gt; Would it not be cleaner to express this in terms of =
"officials=94?</blockquote></div><div><br></div><div>I will leave this =
to the editors to adopt or not, but I personally</div><div>would be OK =
adding =93A working group chair(s), on behalf of their</div><div>work =
working group=94.</div></blockquote><div><br></div><div>* Suggestions =
from Pete Resnick in private e-mail on Feb =
2:</div><div><br></div><blockquote style=3D"margin: 0px 0px 0px 40px; =
border: none; padding: 0px;"><div><blockquote type=3D"cite">16 1.m: =
s/features/permanence</blockquote></div><div><br></div><div>Adopt</div><di=
v><br></div><div><blockquote type=3D"cite">16 5.6: =
s/n/In</blockquote></div><div><br></div><div>Adopt</div><div><br></div><di=
v><blockquote type=3D"cite">16 8: Got the section number and title wrong =
here. It should say, "9. - Licensing Requirements (was 10) - Wording =
updated to reflect RFC =
6410=94</blockquote></div><div><br></div><div>Adopt</div><div><br></div><d=
iv><blockquote type=3D"cite">The first sentence of 5.4.2(A) is really =
hard to read&nbsp;because there's a long subordinate clause. I think it =
would read better if you used the same words and just reversed the =
order:</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">OLD</blockquote></div><div><blockquote type=3D"cite">A. An =
IPR disclosure must be updated or a new disclosure =
made</blockquote></div><div><blockquote type=3D"cite">promptly after any =
of the following has occurred unless =
sufficient</blockquote></div><div><blockquote type=3D"cite">information =
to identify the issued patent was disclosed when =
the</blockquote></div><div><blockquote type=3D"cite">patent application =
was disclosed:</blockquote></div><div><blockquote =
type=3D"cite">NEW</blockquote></div><div><blockquote type=3D"cite">A. =
Unless sufficient information to identify the issued patent =
was</blockquote></div><div><blockquote type=3D"cite">disclosed when the =
patent application was disclosed, an =
IPR</blockquote></div><div><blockquote type=3D"cite">disclosure must be =
updated or a new disclosure made promptly =
after</blockquote></div><div><blockquote type=3D"cite">any of the =
following has occurred:</blockquote></div><div><blockquote =
type=3D"cite">END</blockquote></div><div><br></div><div>Adopt.</div></bloc=
kquote><div><br></div><div><div>* Suggestion from Stewart Bryant on Jan =
24, regarding Section</div><div>&nbsp; =
5.5:</div></div><div><br></div></div><blockquote style=3D"margin: 0px =
0px 0px 40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite">5.5. Licensing Information in an IPR =
Disclosure</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;A. Since IPR disclosures will be used by IETF =
working groups during</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;their evaluation of =
alternative technical solutions, it is =
helpful</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if an IPR disclosure =
includes information about licensing of =
the</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;IPR in case Implementing =
Technologies require a license.</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Specifically, it is helpful =
to indicate whether, upon approval by</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;the IESG for publication as =
an RFC of the relevant IETF</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;specification(s), all =
persons will be able to obtain the right =
to</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;implement, use, distribute =
and exercise other rights with =
respect</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;to an Implementing =
Technology a) under a royalty-free =
and</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;otherwise reasonable and =
non- discriminatory license, or b) =
under</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;a license that contains =
reasonable and non-discriminatory =
terms</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;and conditions, including a =
reasonable royalty or other payment,</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;or c) without the need to =
obtain a license from the IPR holder</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(e.g., a covenant not to =
sue).</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 One of the most popular IPR terms is so called MAD. It is =
surprising</blockquote></div><div><blockquote type=3D"cite">SB&gt; that =
you do not call this out.</blockquote></div><div><blockquote =
type=3D"cite">=85</blockquote></div><div><blockquote type=3D"cite">&nbsp; =
Some common</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;conditions include 1) terms that are fair, =
reasonable and non-</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;discriminatory, and which may bear royalties =
or other financial</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;obligations (FRAND or RAND); 2) royalty-free =
terms that are otherwise</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;fair, reasonable and non-discriminatory =
(RAND-z); and 3) commitments</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;not to assert declared =
IPR.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">SB&gt;=
 One of the most common (at least in the Routing area) is =
non-assert</blockquote></div><div><blockquote type=3D"cite">SB&gt; =
unless the other party asserts (so called =
MAD)</blockquote></div><div><br></div><div>Personally, I don=92t view =
MAD as a term quite in the same style</div><div>and technical =
specificity as, say, RAND or RF. I would suggest</div><div><div>not =
adopting this.</div><div><br></div><div>(Non-assert on the other hand is =
a more</div></div><div>technical term, but I also have not seen calls =
for adding that</div><div>from =
others.)</div><div><br></div></blockquote><div><div>* Editorial =
suggestions from Brian Carpenter in his Gen-ART review</div><div>&nbsp; =
&nbsp;on January 26:</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite"><blockquote type=3D"cite">7. =
Evaluating Alternative Technologies in IETF Working =
Groups</blockquote></blockquote></div><div><blockquote =
type=3D"cite">...</blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">technology in violation if this =
principle if there is a very =
good</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">s/if =
this principle/of this =
principle/</blockquote></div><div><br></div><div>Adopt</div><div><br></div=
><div><blockquote type=3D"cite"><blockquote type=3D"cite">13. Changes =
Since RFC 3979 and RFC =
4879</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">16. Changes Since RFC =
3979</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">Should=
 the preamble to these sections state that they are =
provided</blockquote></div><div><blockquote type=3D"cite">for =
informational purposes only and that in case of doubt the =
text&nbsp;</blockquote></div><div><blockquote type=3D"cite">of sections =
1-12 prevails?</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">Should=
 these two sections be =
merged?</blockquote></div><div><br></div><div>Yes. Adopt both =
suggestions.</div></blockquote><div><div><blockquote =
type=3D"cite"></blockquote></div><div><br></div><div>* Pete Resnick=92s =
review suggested the following edits</div><div>&nbsp; to Section =
4.1:</div></div><div><br></div><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">* Pete Resnick suggested to put =
back the material from</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">RFC 3979 Section 4.1 that were =
deleted from the</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">previous RFC (April 11), which =
we=92ve also done.</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">4(D) =
in the new version. Thanks for that. I see that the section title and =
first sentence of 4(D) are the text from -08 instead of the original =
text from 3979. That's OK, but personally, I think the section title has =
gotten unwieldy and the changes to the first sentence make it somewhat =
less clear. I'd suggest just eliminating the title (so it matches the =
form of A, B, and C) and putting the example into the first =
sentence:</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">OLD</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">D. =
Determination of Provision of Reasonable and =
Non-discriminatory</blockquote></div><div><blockquote type=3D"cite">&nbsp;=
 Terms</blockquote></div><div><blockquote type=3D"cite">&nbsp; The IESG =
will not make any determination that any terms for =
the</blockquote></div><div><blockquote type=3D"cite">&nbsp; use of an =
Implementing Technology has been fulfilled in =
practice.</blockquote></div><div><blockquote type=3D"cite">&nbsp; It =
will instead...</blockquote></div><div><blockquote =
type=3D"cite">NEW</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">D. =
The IESG will not make any determination that any terms for =
the</blockquote></div><div><blockquote type=3D"cite">&nbsp; use of an =
Implementing Technology (e.g., the assurance =
of</blockquote></div><div><blockquote type=3D"cite">&nbsp; reasonable =
and non-discriminatory terms) has been fulfilled =
in</blockquote></div><div><blockquote type=3D"cite">&nbsp; practice. It =
will instead...</blockquote></div><div><blockquote =
type=3D"cite">END</blockquote></div><div><br></div><div>These should be =
adopted.</div></blockquote><div><div><div></div><blockquote =
type=3D"cite"><div></div></blockquote></div><div><br></div><div>* Pete =
Resnick=92s review said:</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite"><blockquote type=3D"cite">* Pete =
Resnick had a concern on adding the word =93all=94 to Section =
7</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite">(April 11). This was an =
oversight, and has been =
corrected.</blockquote></blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">Thanks=
 for that. Personally, I don't think the extra text at the end of that =
paragraph that went in as of -09 really adds anything. 3979 already said =
that there is a consensus that MTI security must be royalty-free, so of =
course there would need to be a consensus to do otherwise. I'm in favor =
of sticking to the language of 3979 unless something really changed or =
clarification is truly necessary, so I'd ask to remove the new stuff. =
That said, I won't go to the mat about this change if folks want it in =
there, but if we go with the new text, please fix the typo: s/in =
violation if this principle/in violation of this =
principle</blockquote></div><div><br></div><div>I think we are OK either =
way, and I will leave the choice to the =
editors.</div></blockquote><div><div><div></div><blockquote =
type=3D"cite"><div></div></blockquote></div><div><br></div><div>* Pete =
Resnick notes about the change =
notes:</div><div><br></div></div></div><blockquote style=3D"margin: 0 0 =
0 40px; border: none; padding: 0px;"><div><div><div><blockquote =
type=3D"cite"><blockquote type=3D"cite"><div>update abstract to make it =
clear that this document replaces RFC =
2026</div></blockquote></blockquote></div></div></div><div><div><div><bloc=
kquote type=3D"cite"><blockquote type=3D"cite"><div>section =
10</div></blockquote></blockquote></div></div></div><div><div><div><blockq=
uote type=3D"cite"><div>If we're going to do that, we should probably do =
it the same way that 3979 =
did:</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div><br></div></blockquote></div></div></div><div><div><div=
><blockquote =
type=3D"cite"><div>OLD</div></blockquote></div></div></div><div><div><div>=
<blockquote =
type=3D"cite"><div><br></div></blockquote></div></div></div><div><div><div=
><blockquote type=3D"cite"><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;This =
memo</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div>replaces section 10 of RFC 2026 and obsoletes RFC =
3979 and RFC =
4879.</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div>NEW</div></blockquote></div></div></div><div><div><div>=
<blockquote =
type=3D"cite"><div><br></div></blockquote></div></div></div><div><div><div=
><blockquote type=3D"cite"><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;This =
memo</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div>updates RFC 2026 and, with RFC 5378, replaces Section =
10 of</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div>RFC 2026. &nbsp;This memo also obsoletes RFC 3979 and =
RFC 4879.</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div>END</div></blockquote></div></div></div><div><div><div>=
<blockquote =
type=3D"cite"><div><br></div></blockquote></div></div></div><div><div><div=
><blockquote type=3D"cite"><div>BTW: Whichever text is used should =
probably also be used in the last sentence of the first paragraph of =
section 2. It still uses the previous language =
there.</div></blockquote></div></div></div><div><div><div><blockquote =
type=3D"cite"><div><br></div></blockquote></div></div></div><div><div><div=
><blockquote type=3D"cite"><blockquote type=3D"cite"><div>In Sec. 3.1, =
added sentence about WGs that summarizes ideas from =
Sec.</div></blockquote></blockquote></div></div></div><div><div><div><bloc=
kquote type=3D"cite"><blockquote =
type=3D"cite"><div>7.</div></blockquote></blockquote></div></div></div><di=
v><div><div><blockquote type=3D"cite">That's fine, but in that sentence, =
please change "possible" to "reasonably possible". In other places in =
the document it's used informally, but 3.1 is a statement of the =
"General Policy", so we should be a bit more =
precise.</blockquote></div></div></div><div><div><div><div><br></div></div=
></div></div><div><div><div><div>These should be =
adopted.</div></div></div></div></blockquote><div><div><div><div></div><bl=
ockquote type=3D"cite"><div></div></blockquote></div><div><br></div><div>*=
 Pete Resnick=92s minor editorial suggestions from January =
26:</div><div><span style=3D"font-family: =
sans-serif;"><br></span></div><div></div><div></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite"><span style=3D"font-family: =
sans-serif;">In section 1, in the definition of "Contribution", "this =
definition" changed to "this specification". I think I see why that was =
done (to avoid confusing whether "this definition" is referring to the =
definition of "Contribution" or the definition of entire document.) But =
calling either of those a "specification" is a bit weird, especially =
considering that in context, every other use of "specification" in this =
document is about a technical specification. I'd suggest either changing =
"this definition" to "this policy" if the intention is the entire =
document, or "this definition of Contribution" if that's what's =
meant.</span></blockquote></div><div><br></div><div>Please adopt =93this =
policy=94.</div></blockquote><div><br></div><div>* Pete Resnick=92s =
minor editorial suggestions from January 26:</div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite"><p dir=3D"auto" style=3D"font-family:=
 sans-serif;">Also, there were a couple of minor changes in 5.2.2. In =
both instances, please change "Covers" to "may Cover". I actually think =
that makes it stronger and leaves less ambiguity: What triggers the =
disclosure is that you simply realize that =
IPR&nbsp;<em>may</em>&nbsp;cover the contribution; you don't have to =
come to some sort of grand final determination that it does surely cover =
(and how could you know that for sure =
anyway?).</p></blockquote></div><div>Right. Adopt =
this.</div></blockquote><blockquote style=3D"margin: 0px 0px 0px 40px; =
border: none; padding: 0px;"><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: =
0px;"><br></blockquote><div></div></blockquote>* Russ Housley=92s =
suggestions from Feb 7:<br><blockquote style=3D"margin: 0px 0px 0px =
40px; border: none; padding: 0px;"><div><br></div><div><blockquote =
type=3D"cite">In Section 7, please provide pointers for FRAND, RAND, and =
RAND-z.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">In =
Section 11, please drop =93legal=94 from the first sentence in the =
second paragraph:</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;The rules that apply =
=85</blockquote></div><div><br></div><div>These should be =
adopted.</div></blockquote><div><div><br></div><div>* Russ Housley=92s =
editorial nits from Feb 7:</div><div><br></div></div><blockquote =
style=3D"margin: 0px 0px 0px 40px; border: none; padding: =
0px;"><div><blockquote type=3D"cite">Nits =
=85</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">I =
see =93this memo=94 and =93this document=94. &nbsp;Either one is fine =
with me, but please pick one and use it =
throughout.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 2: s/IETF and its Participants/IETF and IETF =
Participants/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.2.3: &nbsp;s/IETF area directors/IETF Area =
Directors/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.3: s/RFC-Editor/RFC =
Editor/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote type=3D"cite">Please=
 remove the period at the end of the heading for Section =
5.4.2.</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.4.2: =
s/drafts/Internet-Drafts/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.4.2, paragraph =
A:</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;s/application (3)/application, =
(3)/</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;s/application ), (4)/application, =
(4)/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.4.2, paragraph =
D:</blockquote></div><div><blockquote type=3D"cite">&nbsp;&nbsp;s/submit =
to IETF an update/submit an update/</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;s/Secretariat/IETF Secretariat/ (several =
places)</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.5, paragraph A: s/non- =
discriminatory/non-discriminatory/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 5.6:</blockquote></div><div><blockquote =
type=3D"cite">&nbsp;&nbsp;s/IPR that is (a) owned/IPR that (a) is =
owned/</blockquote></div><div><blockquote type=3D"cite">&nbsp;&nbsp;s/ =
or (b) that such persons/; or (b) =
persons/</blockquote></div><div><blockquote type=3D"cite">&nbsp;&nbsp;s/ =
or (c) that such persons/; or (c) =
persons/</blockquote></div><div><blockquote type=3D"cite">&nbsp;&nbsp;s/, =
or (d) in the case of an individual, the individual/; or (d) an =
individual/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 6: s/violation of IETF process/violation of the =
IETF Standards Process/</blockquote></div><div><blockquote =
type=3D"cite"><br></blockquote></div><div><blockquote =
type=3D"cite">Section 7: s/Working groups and areas may/IETF Areas and =
IETF working groups/</blockquote></div><div><br></div><div>These should =
be =
adopted.</div></blockquote><div><div><br></div><div>Jari</div></div></div>=
</div></body></html>=

--Apple-Mail=_34073D2D-2042-42AB-8990-8DC5E22D1F5E--

--Apple-Mail=_5AD199DA-1830-4715-8158-0F4525B717D5
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

iQIcBAEBCgAGBQJYrgVpAAoJEM80gCTQU46qgIIP/3hmWFdvwZqBDQjgg5G7TYLH
gj3/EOdVeXuaZmOI8ddFmG8bTHgH7Ocb0cihyjTOZdd637LD4LBDku2uW07XL0rq
zHDUuO91tm5B98vVYkSgQZKENJ4Aey77rsAN8ZV/8tuntDjSkXIIHYvUUf8Y1FDA
FjI27A8UJ1Hiagdy8h5dxDu/zv9aDuAw+Xpka2kcoh+SKteA/AAJBO1APei+ALF2
cjmZvewFuQj0hL54tO2pzdjuP6/QMq0W2GcyP/zm2nh+b/RPabTNTMTdFZLEAbc6
dYt5goTKuu8C8+iklYMlsjBAorzZK6/iy76mjcibWZK4UPsak6RAdbgnHenpxm8E
4+hymBCZw5ERvLEs7LoEdBwi/uOZk7YoCFPM0Tjvj3DY/Z304NOdnMqAz4oUgaB7
ElZxCtakarErvIjfgDxX5W5AgsTFPCU+48PLlT7eFqxA/QkUePN7Fr42u3/fQNHZ
kugdWD5JXCkOj10f1YSJvE6V8f71u2a78mxKcUghFLQXck0xMMKaGYOGrAvIwJ6p
j8sZmF3MSKKMVciI0exOmRxTKF4ZQ53kOIl01fxkmHvXnQXt/hDvi+7omqis35GO
GXZqJWV5NZ7sJR7cg/oBFJHfAiXmprEJrR5m2XBBwpAIlVv6yL80jvY93RonIKFd
xlLPa813OTHdOl9vfQhZ
=1QjZ
-----END PGP SIGNATURE-----

--Apple-Mail=_5AD199DA-1830-4715-8158-0F4525B717D5--


From nobody Wed Feb 22 13:54:04 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF87129BA1; Wed, 22 Feb 2017 13:54:02 -0800 (PST)
X-Quarantine-ID: <55l4gMNmWrox>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Non-encoded 8-bit data (char C3 hex): To: <"Michael T\303\274xen <tuexen@fh[...]
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55l4gMNmWrox; Wed, 22 Feb 2017 13:53:58 -0800 (PST)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::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 15DA1129BCE; Wed, 22 Feb 2017 13:53:58 -0800 (PST)
Received: by mail-ot0-x229.google.com with SMTP id j38so11962873otb.3; Wed, 22 Feb 2017 13:53:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TGWDL/ThysEIi0XoBGtC6kXUFsa2Oq6SugkVeg2hIBw=; b=ALnWd8KDSSOr6RHqUQmg4OVbIFSary5JIMExSXw1tgOobHtamGIPxXiVTZkrlSKQSq nPNpwqNXy2jpxLxYrPhd4SkpkE5LpH2BzaER2qjfR0cazslXnJ5y07ODthJRc2EEBfZN 0A3jlfq5/uq6FDRnuEG5WTuYW8SNroAE3fN4j3Ikm0P4BmyLjUElOj+tVMmwvZXvCnN+ nqOkx7o9gBSPnHcb298DEfYW4LSAHWOsCaUe1cZxmhlnEairWgCmhp3QNIYKBta4bLlC hR2mpVecL9lvoSi5xvajOVjIv1e3xQXSB+wQQlNM1/M7h6JOdA9hed82erNnzCO3kmRZ qLQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TGWDL/ThysEIi0XoBGtC6kXUFsa2Oq6SugkVeg2hIBw=; b=Ka635I6ZiS1gThyXPMnqqvkZe1Upzgh4m6t2pvsq9DqpYWWnBrqT38HTyVtb2sfj+0 qu8wOhaQq3R18ICu5pIsdi/3I/3ZlBoRWpetLmMDjncdApGiXKDyEI71FejARcQdzBa6 tpXV0etTbWhbl8j8PDWY58nSSZd9xG4YFKp364ktapWO2wYFyEoRyo+uApVJgDAQihAY ME11psTDE9YVnFzvS8U15TMLPHq9YP1F6hxelaIHpN/Q6GdiGU70tIG2IvyP9nzL4W+m Ah7x2gleqtcErHTUHM2xS4ctXinXt+0HWDgCD5YHPokJ38m/CseoacXkG6ISM7OD9eq+ vwJQ==
X-Gm-Message-State: AMke39l0UYC3Lwct6vdNdK3T4HZR+dSMfrSJn0EBbb6uxcYBLezDlU7ggilyvh+AT619UjV4Juzhj3mxgTBXyg==
X-Received: by 10.157.47.209 with SMTP id b17mr5026487otd.47.1487800437003; Wed, 22 Feb 2017 13:53:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Wed, 22 Feb 2017 13:53:26 -0800 (PST)
In-Reply-To: <148726910816.1075.17105591789960030239.idtracker@ietfa.amsl.com>
References: <148726910816.1075.17105591789960030239.idtracker@ietfa.amsl.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 22 Feb 2017 13:53:26 -0800
Message-ID: <CA+9kkMAmG2P=g1k7w3YOh1udjDB_MOjn0=+hnUXap1zq-VtwHQ@mail.gmail.com>
Subject: Re: Review of draft-hardie-privsec-metadata-insertion-05
To: <"Michael Tüxen <tuexen@fh-muenster.de>"@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary=001a113dec1c8b5b9c05492588dc
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tAM1ZhLmmvBybQlp3PC3JlYxuJM>
Cc: tsv-art@ietf.org, IETF <ietf@ietf.org>, draft-hardie-privsec-metadata-insertion.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 21:54:02 -0000

--001a113dec1c8b5b9c05492588dc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi Michael,

Thanks for the review; I've uploaded a -06 now which updates the abstract,
adds the reference to RFC 6891 and clarifies the language around the
purpose of the EDNS0 options.

regards,

Ted

On Thu, Feb 16, 2017 at 10:18 AM, <"Michael Tüxen
<tuexen@fh-muenster.de>"@ietfa.amsl.com> wrote:

> Reviewer: Michael Tüxen
> Review result: Ready with Nits
>
> I've reviewed this document as part of the transport area
> directorate's ongoing
> effort to review key IETF documents.
> These comments were written primarily for the transport area
> directors,
> but are copied to the document's authors for their information and to
> allow
> them to address any issues raised. When done at the time of IETF Last
> Call,
> the authors should consider this review together with any other
> last-call
> comments they receive.
> Please always CC tsv-art@ietf.org if you reply to or forward this
> review.
>
> This draft is basically ready for publication, but has nits that
> should be
> fixed before publication.
>
> Running https://tools.ietf.org/tools/idnits/idnits.pyht reports
> * The abstract seems to contain references ([RFC7624]), which it
> shouldn't.
> * Unused Reference: 'RFC4301'
>
> The discussion of RFC 7871 in section 4 could be improved to allow
> readers
> not knowing the EDNS0 option to get the point. Either provide an
> abstract
> description or refer to RFC 6891.
>
>
>

--001a113dec1c8b5b9c05492588dc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><div>Hi Michael,<br><br></div>Thanks for the review; I&#39;ve uploaded a -06 now which updates the abstract, adds the reference to RFC 6891 and clarifies the language around the purpose of the EDNS0 options.<br><div><div><div class="gmail_extra"><br></div><div class="gmail_extra">regards,<br><br></div><div class="gmail_extra">Ted<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 16, 2017 at 10:18 AM,  <span dir="ltr">&lt;<a href="mailto:&quot;Michael Tüxen &lt;tuexen@fh-muenster.de&gt;&quot;@ietfa.amsl.com" target="_blank">&quot;Michael Tüxen &lt;tuexen@fh-muenster.de&gt;&quot;@ietfa.amsl.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Michael Tüxen<br>
Review result: Ready with Nits<br>
<br>
I&#39;ve reviewed this document as part of the transport area<br>
directorate&#39;s ongoing<br>
effort to review key IETF documents.<br>
These comments were written primarily for the transport area<br>
directors,<br>
but are copied to the document&#39;s authors for their information and to<br>
allow<br>
them to address any issues raised. When done at the time of IETF Last<br>
Call,<br>
the authors should consider this review together with any other<br>
last-call<br>
comments they receive.<br>
Please always CC <a href="mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or forward this<br>
review.<br>
<br>
This draft is basically ready for publication, but has nits that<br>
should be<br>
fixed before publication.<br>
<br>
Running <a href="https://tools.ietf.org/tools/idnits/idnits.pyht" rel="noreferrer" target="_blank">https://tools.ietf.org/tools/<wbr>idnits/idnits.pyht</a> reports<br>
* The abstract seems to contain references ([RFC7624]), which it<br>
shouldn&#39;t.<br>
* Unused Reference: &#39;RFC4301&#39;<br>
<br>
The discussion of RFC 7871 in section 4 could be improved to allow<br>
readers<br>
not knowing the EDNS0 option to get the point. Either provide an<br>
abstract<br>
description or refer to RFC 6891.<br>
<br>
<br>
</blockquote></div><br></div></div></div></div>

--001a113dec1c8b5b9c05492588dc--


From nobody Wed Feb 22 13:59:15 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3EC129BF3; Wed, 22 Feb 2017 13:59:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43JhWEWaeT9q; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::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 3DF54129BF0; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
Received: by mail-oi0-x22f.google.com with SMTP id s205so8813569oif.3; Wed, 22 Feb 2017 13:59:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mOOUYf2NZ+i3gfMTVySGw6jYt0lmGd0UZsTpLt6kPqE=; b=OQZePFmv4mwlEyhtwWti7GbyAct/XZzQGp23Yofoypvd6AHmPibb6nSHvWiypxK7Bk G0xftgqCqNXey5l9VIvXuyD/f4i15YOCiIJNvmQ8hHF0QFINZCI6eJXZktaaWfXzBBeR 4NpvJAVqL/8ChJv+HicPZWQmjtNLTDSd7kUVds9kKuihgO7v5BzDFzKt8DZJU8ZF7F33 8kMAc0hatW8GhFYuqVH2Sa9/hzf6ssvOHC8T8pzHCfuyYi7NRXwma72Gd7jNRs47zZLL U93U69uDN9WnGEhBCj32mOLJoukdIPIaTsULZU34pcPae9XF4vakCWqY4gmLJCPT3uFd 57Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=mOOUYf2NZ+i3gfMTVySGw6jYt0lmGd0UZsTpLt6kPqE=; b=OPNUi56NbD4fu2RLRG7LwwkFIpndmN4vjhM6phsByETKSZLQxxsi61TMc7UK9fN0lL LiKQeDpDpsv/VR2ZmECCy/iWaZhINZc1rtrBV9yTFVM7hhTT/LwxJv1TJUXGFMveoVRI dyFvlAykPRbEmtiGlHU3OsJ+SFgumIpdIlneoTprucLJxUahJ3Cx4Rf9D+9Q4xLEwbkd MclHBHODHB8goDP27AZNbTcTXn5fNxx6z4ocoOJm738Vap5kMtfKr4OinwJIAhr4pskQ 0aPoRHS8lBXinbgl0mBEZKnMOeMbPJoQlQIa3n3m5VrYBxjsXdBRatlNfw9mkjjmiGz0 PghA==
X-Gm-Message-State: AMke39kczSwPxPrGs3Y8KUzO6UaYjonPXhkvj7blj4DSBdmjKlE+31FHpY7aTwK3Fwor7K+VSYelHG6ynVEl8g==
X-Received: by 10.202.72.2 with SMTP id v2mr5435370oia.179.1487800752356; Wed, 22 Feb 2017 13:59:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Wed, 22 Feb 2017 13:58:42 -0800 (PST)
In-Reply-To: <148559843419.17936.4314684504467085961.idtracker@ietfa.amsl.com>
References: <148559843419.17936.4314684504467085961.idtracker@ietfa.amsl.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 22 Feb 2017 13:58:42 -0800
Message-ID: <CA+9kkMBb93qg9NccNkNpn2=sJdfgqE8=MccVz6zWf4MNccGfvQ@mail.gmail.com>
Subject: Re: Review of draft-hardie-privsec-metadata-insertion-05
To: Stewart Bryant <stewart@g3ysx.org.uk>
Content-Type: multipart/alternative; boundary=001a113e4eac57444a0549259b84
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QtlwLJwX4GWvzBdJwFogBRrZFj4>
Cc: gen-art@ietf.org, IETF <ietf@ietf.org>, draft-hardie-privsec-metadata-insertion.all@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 21:59:15 -0000

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

Hi Stewart,

Thanks for the review.  I've updated the abstract, removed the vestigial
reference, added a reference for EDNS0 and clarified how it is used in the
design I describe.

Thanks again for your attention to it,

Ted

On Sat, Jan 28, 2017 at 2:13 AM, Stewart Bryant <stewart@g3ysx.org.uk>
wrote:

> Reviewer: Stewart Bryant
> Review result: Ready with Nits
>
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>
> For more information, please see the FAQ at
>
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-hardie-privsec-metadata-insertion-??
> Reviewer: Stewart Bryant
> Review Date: 2017-01-28
> IETF LC End Date: 2017-02-21
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: This is a well written document with a couple of nits. It
> would be helpful to the reader interested in the concept, but
> unfamiliar with DNS if there was some minor additional clarification
> regarding  EDNS0.
>
> Major issues: None
>
> Minor issues:
>
> RFC4301 is an unused reference. Is it missing from the text?
>
> =====
>
>    By negotiating an EDNS0
>    option which allowed them to self-populate this data,.....
>
> SB> Calling up EDNS0 (which really needs expanding) comes out of the
> SB> blue and could use a reference and sentence of explanation
> SB> at least for those not familiar with the detail of DNS.
>
> Nits/editorial comments:
>
> [RFC7624] in the Abstract should be changed to RFC7624
>
> =========
>
> 1.  Introduction
> ....
>    exploited in the attacks document in [RFC7258] and the threats
> s/document/documented/
>
>
>

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

<div dir=3D"ltr"><div><div><div>Hi Stewart,<br><br></div>Thanks for the rev=
iew.=C2=A0 I&#39;ve updated the abstract, removed the vestigial reference, =
added a reference for EDNS0 and clarified how it is used in the design I de=
scribe.=C2=A0 <br><br></div>Thanks again for your attention to it,<br><br><=
/div>Ted<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"=
>On Sat, Jan 28, 2017 at 2:13 AM, Stewart Bryant <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:stewart@g3ysx.org.uk" target=3D"_blank">stewart@g3ysx.org.uk<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reviewer: Stewart B=
ryant<br>
Review result: Ready with Nits<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.=C2=A0 Please treat these comments just<br>
like any other last call comments.<br>
<br>
For more information, please see the FAQ at<br>
<br>
&lt;<a href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" rel=3D"norefe=
rrer" target=3D"_blank">https://trac.ietf.org/trac/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-hardie-privsec-metadata-<wbr>insertion-??<br>
Reviewer: Stewart Bryant<br>
Review Date: 2017-01-28<br>
IETF LC End Date: 2017-02-21<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary: This is a well written document with a couple of nits. It<br>
would be helpful to the reader interested in the concept, but<br>
unfamiliar with DNS if there was some minor additional clarification<br>
regarding=C2=A0 EDNS0.<br>
<br>
Major issues: None<br>
<br>
Minor issues:<br>
<br>
RFC4301 is an unused reference. Is it missing from the text?<br>
<br>
=3D=3D=3D=3D=3D<br>
<br>
=C2=A0 =C2=A0By negotiating an EDNS0<br>
=C2=A0 =C2=A0option which allowed them to self-populate this data,.....<br>
<br>
SB&gt; Calling up EDNS0 (which really needs expanding) comes out of the<br>
SB&gt; blue and could use a reference and sentence of explanation<br>
SB&gt; at least for those not familiar with the detail of DNS.<br>
<br>
Nits/editorial comments:<br>
<br>
[RFC7624] in the Abstract should be changed to RFC7624<br>
<br>
=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>
<br>
1.=C2=A0 Introduction<br>
....<br>
=C2=A0 =C2=A0exploited in the attacks document in [RFC7258] and the threats=
<br>
s/document/documented/<br>
<br>
<br>
</blockquote></div><br></div>

--001a113e4eac57444a0549259b84--


From nobody Wed Feb 22 14:09:32 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 079C5129C25; Wed, 22 Feb 2017 14:09:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rMBiG_sJJ6Uz; Wed, 22 Feb 2017 14:09:29 -0800 (PST)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003: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 6EE21129C23; Wed, 22 Feb 2017 14:09:29 -0800 (PST)
Received: by mail-oi0-x229.google.com with SMTP id 62so8953287oih.2; Wed, 22 Feb 2017 14:09:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+bUMm1mB6yqP75AKrs4wcyH7dRxuKZlA9nxn3OwmlO8=; b=cXowtS//dJF89RgR8gEe+C8sP7zisluwsGdqYZDBIZSlQQ+wdPWc5mCapRb0L9YSdN X1nqVyl1ovZIHD+nP37EUe72l8hIzMBDkHSdpK+wy816mlRYdYugo3usGUu1Wx56T2O9 PrjQgYFFPIYsxsg6hLwxVrI1AaUtyZDxgnd+1nmBHLpTKQTs+QH9P0KK/UB+JRZIsWty JKq7eBquFLGKER0yzTKrpaNlW7gyXEpejEnEk66ZD1c5GfNXzGCBum0k2jRSQxw366Lf WSlnnSiwYUObCL9K9dAVs+88hYDjqCmfqEHLV1U8IjrPvDjKEHzoyrvyvQE7GDHJeWiD Thww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+bUMm1mB6yqP75AKrs4wcyH7dRxuKZlA9nxn3OwmlO8=; b=s0mtfqaPxYfWUghEagre23FeXukts+frYwkyyEPqXsP8B3kWDwi26fgPF+GVsv5OZi Ioo66YK8ieuLdXri5WBhD4jQ9bz4ird59Q0yFI0Owy3ldi9W2QVgO1AXp0yqENNZRmJV hBk3dKvkjlpn6DWwqM6wY2dIxg1aUJh5jsmI285gmTqyNGZWU1+GUKbEnnLCR7oCsgAL /uv63l3OuAUtNGfU3NNunC8K88u2V5CF0WFQDx9xwTS+EOA6J5zeOLT99nnW7HTqkcii C7ck14t1Lw95N/CV7EI6F90mt0otj1Lsyoaw+Up1Gdea77MY9BumL3TplUMSJW/5vhVk eE+g==
X-Gm-Message-State: AMke39nSrJJaGbMxJhF1IySZ8DyvfvOW99nNzgFyhfcAcTIGNSypTQSRRrU59hwrCfZpfPE4PE9fBIj7+9fTjw==
X-Received: by 10.202.5.4 with SMTP id 4mr18930789oif.132.1487801368539; Wed, 22 Feb 2017 14:09:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Wed, 22 Feb 2017 14:08:58 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 22 Feb 2017 14:08:58 -0800
Message-ID: <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=94eb2c18d092117c8d054925c025
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/h-6jUOxpUxji4xX9WhYdRi_HyZg>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2017 22:09:31 -0000

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

Hi Mohamed,

Thanks for your review.  I've uploaded a draft -06 with updates from your
and other reviews.  Some notes in-line.

On Tue, Jan 31, 2017 at 1:49 AM, <mohamed.boucadair@orange.com> wrote:

> Dear Ted,
>
> Please find below my general review of the document and also my detailed
> comments.
>
> * Overall:
> - I don't think the document is ready to be published as it is. It does
> not discuss the usability and implications of the advice. Further, it may
> be interpreted that a client/end system/user can always by itself populat=
e
> data that is supplied by on-path nodes (in current deployments). That's
> assumption is not true for some protocols.
> - The purpose of publishing this advice is not clear. For example, how
> this advice will be implemented in practice? What is its scope?
> - I would personally prefer an updated version of RFC7258 with more stric=
t
> language on the privacy-related considerations. This is more actionable
> with concrete effects in documents that will required to include a
> discussion on privacy related matters.
>
> Detailed comments are provided below:
>
> * The abstract says the following:
>
>    The IAB has published [RFC7624] in response to several revelations of
>    pervasive attack on Internet communications.  This document considers
>    the implications of protocol designs which associate metadata with
>    encrypted flows.  In particular, it asserts that designs which do so
>    by explicit actions of the end system are preferable to designs in
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    which middleboxes insert them.
>
> I suggest you explicit what is meant by "the end system".


I have updated this to clarify that this is the host/end system not the
user.


> If you mean the owner/user, then the text should say so. If you mean a
> client software instance, then bugs/inappropriate default values may lead
> to (privacy leak) surprises too. It was reported in the past that some
> browsers inject the MSISDN too.
>
> * Introduction: "To ensure that the Internet can be trusted by users"
>
> Rather =C2=AB To minimize the risk of Internet-originated attacks targete=
d at
> users =C2=BB.


I've adopted this language.


> It's reasonable to claim the Internet can be trusted by users; see how th=
e
> usage of social networks has become severely twisted for example


I've also considered your point that an updated version of RFC7258 might be
a better outlet for advice like this. We did consider several approaches,
including incorporating the text in an update to  RFC 3552 or as part of a
document describing the full set of companion mitigations to the threats in
RFC 7624 (draft-iab-privsec-confidentiality-mitigations would be one
approach).  Those are all valid approaches, but it seemed that short,
easily read documents tackling a single point might be easier to produce
and consume.

Thanks again for your review,

Ted Hardie

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

<div dir=3D"ltr"><div>Hi Mohamed,<br><br></div>Thanks for your review.=C2=
=A0 I&#39;ve uploaded a draft -06 with updates from your and other reviews.=
=C2=A0 Some notes in-line.<br><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Tue, Jan 31, 2017 at 1:49 AM,  <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.boucada=
ir@orange.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">Dear Ted,<br>
<br>
Please find below my general review of the document and also my detailed co=
mments.<br>
<br>
* Overall:<br>
- I don&#39;t think the document is ready to be published as it is. It does=
 not discuss the usability and implications of the advice. Further, it may =
be interpreted that a client/end system/user can always by itself populate =
data that is supplied by on-path nodes (in current deployments). That&#39;s=
 assumption is not true for some protocols.<br>
- The purpose of publishing this advice is not clear. For example, how this=
 advice will be implemented in practice? What is its scope?<br>
- I would personally prefer an updated version of RFC7258 with more strict =
language on the privacy-related considerations. This is more actionable wit=
h concrete effects in documents that will required to include a discussion =
on privacy related matters.<br>
<br>
Detailed comments are provided below:<br>
<br>
* The abstract says the following:<br>
<span class=3D"gmail-"><br>
=C2=A0 =C2=A0The IAB has published [RFC7624] in response to several revelat=
ions of<br>
=C2=A0 =C2=A0pervasive attack on Internet communications.=C2=A0 This docume=
nt considers<br>
=C2=A0 =C2=A0the implications of protocol designs which associate metadata =
with<br>
=C2=A0 =C2=A0encrypted flows.=C2=A0 In particular, it asserts that designs =
which do so<br>
=C2=A0 =C2=A0by explicit actions of the end system are preferable to design=
s in<br>
</span>=C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<wbr>^^^^<br>
=C2=A0 =C2=A0which middleboxes insert them.<br>
<br>
I suggest you explicit what is meant by &quot;the end system&quot;. </block=
quote><div><br></div><div>I have updated this to clarify that this is the h=
ost/end system not the user.=C2=A0 <br>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex">If you mean the owner/user, then the text should =
say so. If you mean a client software instance, then bugs/inappropriate def=
ault values may lead to (privacy leak) surprises too. It was reported in th=
e past that some browsers inject the MSISDN too.<br>
<br>
* Introduction: &quot;To ensure that the Internet can be trusted by users&q=
uot;<br>
<br>
Rather =C2=AB To minimize the risk of Internet-originated attacks targeted =
at users =C2=BB. </blockquote><div><br></div><div>I&#39;ve adopted this lan=
guage.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">It&#39;s reasonable to claim the Internet can be trusted by users; =
see how the usage of social networks has become severely twisted for exampl=
e</blockquote></div><br></div><div class=3D"gmail_extra">I&#39;ve also cons=
idered your point that an updated version of RFC7258 might be a better outl=
et for advice like this. We did consider several approaches, including inco=
rporating the text in an update to=C2=A0 RFC 3552 or as part of a document =
describing the full set of companion mitigations to the threats in RFC 7624=
 (draft-iab-privsec-confidentiality-mitigations would be one approach).=C2=
=A0 Those are all valid approaches, but it seemed that short, easily read d=
ocuments tackling a single point might be easier to produce and consume.=C2=
=A0 <br><br></div><div class=3D"gmail_extra">Thanks again for your review,<=
br><br></div><div class=3D"gmail_extra">Ted Hardie<br></div><div class=3D"g=
mail_extra"><br></div></div>

--94eb2c18d092117c8d054925c025--


From nobody Wed Feb 22 16:42:08 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA3C129430 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 16:42:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wq1FrgefSDp1 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 16:42:06 -0800 (PST)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 274B11293FF for <ietf@ietf.org>; Wed, 22 Feb 2017 16:42:05 -0800 (PST)
Received: by mail-vk0-x22a.google.com with SMTP id t8so11810697vke.3 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:42:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1gwJV3wFAwWG2XT+xrNr30yt0CI1c5xYYGXNwjHPZ0M=; b=JWuC+Dsz6mFPwrLvdBb/H/NIz5lV3MVYTLbcGd6YfASvFWt6chopKpN46QydfB+aPa Tr9T3Tz9X1zAqcJoJL8SDF5Qnt/ZY23j26ZRK48ATbavsYU+BzXj2Ac1nJGMbBOib9yo RK31Z+0WvO1j4AwLv6+fWN4WnLzOJ5bRnaKyVGKFFOi564gP/ufvBP01Ua+g+pHf8CtY ES9UnwxIPi4prWVLhv7QD8EEvxtRQ46Ywb8eX3mPVFEbUl16TAKto0WDT88VX3EXmigz Kw+iZlfeIeAV0HBWvSivT93BTQK9t7+PY4+vNyf3LR61IOvFZHGfkVmaH5ELg+ebU4DB 5hdg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1gwJV3wFAwWG2XT+xrNr30yt0CI1c5xYYGXNwjHPZ0M=; b=raeZQQZ8vYhSmSONsEiV+jbgCFB5l3Co7synLjo6h2Cb3E/YZHVQwq4iOgV2xuskIc 0q97i7i5k75b9MoHvv8Lu4dUN4WC8aJw0VQOVC6E7dPz+qSUVAWM8XPqAH/5b+Y9aB4w Un+jvYg9dSfKq8fnC92VArS8XbCb6S44ypdZ1bZmx6gNMQPEha6fSRv9qSPXoAZcEe/q Ej6kTj427WwYeeb/0ktkzc2z1z7TG+eDLiJ6+LLTktj2QZCIFDzLdqHE7lgiQGIIilLd eJUPcQ2Sa7tsuWAzFA8Q+trgq5RataSZqdkEP4PwoMfBIJpyN37OGSylLD0jA9K5LQnL MHJQ==
X-Gm-Message-State: AMke39mdAaPI0DcTtu0NFzGNf9LPIOCwzQQ+KCSgYlXWRVH68x8lFZ7AcVgxAKgB7MRKZ0Zyrh22zn5f1J8kGWPf
X-Received: by 10.31.150.134 with SMTP id y128mr15570987vkd.102.1487810523992;  Wed, 22 Feb 2017 16:42:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 16:41:43 -0800 (PST)
In-Reply-To: <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 09:41:43 +0900
Message-ID: <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141d600c75155054927e144
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mIZygX6zzBl01KCShrph9iRCMmg>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 00:42:07 -0000

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

On Thu, Feb 23, 2017 at 5:20 AM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Nobody is saying that /64 isn't extremely widely used where it's
> appropriate to have a portable fixed length IID. Set the default
> at 64 and trust operators to change it where they need to.
> That's realistic.


As a host developer I strongly oppose that. It will make life easier for
network operators but make life harder for host OS developers, host
operators, and host users.

And it is absolutely inappropriate to change this now in given that the /64
boundary has been the standard for the last 20 years. It will break
deployed code that relies on the current standard. (That includes concrete
code I can point to that I know runs on tens of millions of devices.)
That's not acceptable to do in a standard reclassification.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 5:20 AM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpente=
r@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Nobody =
is saying that /64 isn&#39;t extremely widely used where it&#39;s<br>
appropriate to have a portable fixed length IID. Set the default<br>
at 64 and trust operators to change it where they need to.<br>
That&#39;s realistic.</blockquote><div><br></div><div>As a host developer I=
 strongly oppose that. It will make life easier for network operators but m=
ake life harder for host OS developers, host operators, and host users.</di=
v><div><br></div><div>And it is absolutely inappropriate to change this now=
 in given that the /64 boundary has been the standard for the last 20 years=
. It will break deployed code that relies on the current standard. (That in=
cludes concrete code I can point to that I know runs on tens of millions of=
 devices.) That&#39;s not acceptable to do in a standard reclassification.<=
/div></div></div></div>

--001a1141d600c75155054927e144--


From nobody Wed Feb 22 16:50:24 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C0FF129462 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 16:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZhXow7SdaNb for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 16:50:22 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 19C9B129455 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:50:22 -0800 (PST)
Received: by mail-vk0-x234.google.com with SMTP id r136so11907399vke.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 16:50:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Ui5zqvSVS2C40TAioNJdAj9nN2Vy3v2s8dwoK8vb8TQ=; b=P5qJ/5aZF6tpP5tt9veSx6pTlV9D1tdRMJkFUkXb64z/ddwmMjkozQwcwVnN2w8YH+ 3aDYnJ2XD6WOlX9Zm46akVuPwydN3CW1aDe9+R0cpDCrxZN5uBrPsItvFzQgmtyYnwzz X9hu92NK/rLHF3n1JI2RAoNGrLtX7jE/FIrOB2+FmEQl07ZRTs+K5DeRbCClg6TYl0Uf jJ6jcLNPBKAbXetRxCo/Wl4tE75SOPyuWC7x81CpCIkPTNviJuZ9JyhsCUIwzMhKc1FY BG6sj7Kw49iLXOGAAHJwRmgOowSBJOBEE9BHVsslaKEJYcuBJS7DsqAmFXpqbAUqxJrc +bLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Ui5zqvSVS2C40TAioNJdAj9nN2Vy3v2s8dwoK8vb8TQ=; b=ijes5zsyKQrRyVMWhiRIM0c5WhAEMSsn1+2vB7wW5daRNZaB3zqrf2SeIEL3y4nkJK NQNd01OdiZA+j5PU08Z4kY6yTw3e6MyfH9gLtrpJM8BHsNCWVwwwrVO/pFLvKyIKqOeR jdL9FiZXUqzXPabyMAd/2d1XzASAAHYRw0f2oUhtLhiTOx5drWWPCg+QaraN26Bv+G5E 1YXvIZWO1V96Y6ma3EXZGYDPBHLlk7j2ZO22XtBOGLwAzBnEuLN3hd2OMCyI2K5kR2xH frniw2u20yUUpbS4twtRHzJbdAOb3uXCTB9NZV3zSKm6X4So1HE5ATbOFgli3L4PxfaJ LokQ==
X-Gm-Message-State: AMke39mxy8uVgjATjLvqOfcx9WKjxxOpet8ojqtuKMAgPAYgKQuluILdVEEDoxILZYjJE0Ak8BZg8D6eSUPSjFhG
X-Received: by 10.31.150.134 with SMTP id y128mr15585297vkd.102.1487811021010;  Wed, 22 Feb 2017 16:50:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 16:50:00 -0800 (PST)
In-Reply-To: <m2poiaug54.wl-randy@psg.com>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <m2poiaug54.wl-randy@psg.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 09:50:00 +0900
Message-ID: <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a1141d60066e62b054927ff89
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VopCJ7BmDiUxmV6QI47fncJjVfs>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 00:50:23 -0000

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

On Thu, Feb 23, 2017 at 5:25 AM, Randy Bush <randy@psg.com> wrote:

> face it job.  what we have here is non-ops telling us what we should do
> and denying what we actually do and intend to keep doing.  welcome to
> the ietf; we want ops here but that does not mean we want to listen to
> them.
>

Host developers could just as well claim "this is just network ops telling
us what we should do do and denying what we actually do and intend to keep
on doing".

With the difference that the standards clearly specify what the current
state of affairs is.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 5:25 AM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">face it job.=C2=A0 what we have here is no=
n-ops telling us what we should do<br>
and denying what we actually do and intend to keep doing.=C2=A0 welcome to<=
br>
the ietf; we want ops here but that does not mean we want to listen to<br>
them.<br></blockquote><div><br></div><div>Host developers could just as wel=
l claim &quot;this is just network ops telling us what we should do do and =
denying what we actually do and intend to keep on doing&quot;.</div><div><b=
r></div><div>With the difference that the standards clearly specify what th=
e current state of affairs is.</div></div></div></div>

--001a1141d60066e62b054927ff89--


From nobody Wed Feb 22 16:56:31 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EAED129472; Wed, 22 Feb 2017 16:56:24 -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 autolearn_force=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 QHxzPBZQY4vm; Wed, 22 Feb 2017 16:56:23 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 382D012946B; Wed, 22 Feb 2017 16:56:22 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cghhi-0006Cp-Lo; Thu, 23 Feb 2017 00:56:19 +0000
Date: Thu, 23 Feb 2017 07:56:15 +0700
Message-ID: <m2efypvi6o.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <m2poiaug54.wl-randy@psg.com> <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uDyVmfv6tH3I6KmAXEwbx9vNizc>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 00:56:24 -0000

> Host developers could just as well claim "this is just network ops telling
> us what we should do do and denying what we actually do and intend to keep
> on doing".

how is that working out for dual-stack and dhcp android users?

> With the difference that the standards clearly specify what the current
> state of affairs is.

and now we need to make the wannabe document match what the state of
affairs is in networking.

randy


From nobody Wed Feb 22 17:51:19 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDAD129D9F for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 17:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id loRkcv3FvKnI for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 17:51:16 -0800 (PST)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 4C4A9129DA7 for <ietf@ietf.org>; Wed, 22 Feb 2017 17:51:11 -0800 (PST)
Received: by mail-vk0-x22a.google.com with SMTP id x75so12447677vke.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 17:51:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JShC4nDxORjZTUrFDVOSSLFRKjGesq5on501tTKEzeE=; b=NENXnbF2HHd0P4O06snYIb3Bwgmr8a2jMqbznnDbcou81eT7d3vforo9D2cBVEtTM1 6FITRbih1uF0p5DJykK75ft4LwnlDsn/EGITtLt5/3drICHueq46Zx1SuJX5f5qWzGit qc42q7HCUYzHIH6wrNYdyDTSslZV2rA90obDij61ztwIueO1V9m6SGdYTcX8KMv70nQG uw9qSwfJcEJZxm3tlUV3lw1JcYfTlEbRMd9Hz0Csofh07WILrxuWbzl49r71z/jPDaKS ItvBMkIyiwDEBISFs1x390eqDi7fsQL94BrtJ4TI6vQHj8BQ88grryilOC0ByiJp43cm rrEA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JShC4nDxORjZTUrFDVOSSLFRKjGesq5on501tTKEzeE=; b=I9kqpecoxIhqmLwhHKX//SAOkJJQekl5sA9Q1UfOLx/1t/WWnRR6f8PVWx0z83Fkam jtD879pwrdUbsstPP/fGYf7+oj1IYNZHMQMyRTQAF8cEsLEi7vDoqCAgxYxy9LbEclmz 31mf3yJZCOqhwxSzmW4vjJG5u4sxTr0COZRa/b29d0hGWtFu50WmJLWhKveshPovwXp/ fDfudamjOmXva78BMYMVTiLwW+/6cWrNMHE30nv1bAzq1VqSY1Wkwu18DqLxZMYGaOca h/HlxLjqbBByqE8i9dEfZEGeNxktH978Vg0KVl8I6Nls0QlL3ZNEEpwAy+AqX/bbryoX 2WEg==
X-Gm-Message-State: AMke39nvd76hQyOAR0TeqGqpXtTXh8HwNoos02pcj+2jipSeoK/Vfit0RV9V+jGfhp/VSXCeRroTsCwiwWr1kP/X
X-Received: by 10.31.142.68 with SMTP id q65mr17611397vkd.83.1487814670177; Wed, 22 Feb 2017 17:51:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 17:50:49 -0800 (PST)
In-Reply-To: <m2efypvi6o.wl-randy@psg.com>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <m2poiaug54.wl-randy@psg.com> <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com> <m2efypvi6o.wl-randy@psg.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 10:50:49 +0900
Message-ID: <CAKD1Yr0bUTT+NSjO=9GFeDU1UnsFjxneS5kqQw2U5UgQp7RnSg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a1143703ae8b0d7054928d86d
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SvQ7WN1UVFVjPwctmn5yU-MSXbY>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 01:51:17 -0000

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

On Thu, Feb 23, 2017 at 9:56 AM, Randy Bush <randy@psg.com> wrote:

> > Host developers could just as well claim "this is just network ops
> telling
> > us what we should do do and denying what we actually do and intend to
> keep
> > on doing".
>
> how is that working out for dual-stack and dhcp android users?
>

What do you mean? Are you saying that host developers don't always and
automatically do what network operators want them to do? If that's
motivated by the fact that they are acting in their users' interests, it
seems to me that they are justified in doing so, and in fact, would be
remiss not to.

> With the difference that the standards clearly specify what the current
> > state of affairs is.
>
> and now we need to make the wannabe document match what the state of
> affairs is in networking.
>

That doesn't mean "we've been violating the standards, so now the standards
have to change to match what we've been doing, even if other parties are
depending on the standards", does it? :-)

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 9:56 AM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">=
&gt; Host developers could just as well claim &quot;this is just network op=
s telling<br>
&gt; us what we should do do and denying what we actually do and intend to =
keep<br>
&gt; on doing&quot;.<br>
<br>
</span>how is that working out for dual-stack and dhcp android users?<br></=
blockquote><div><br></div><div>What do you mean? Are you saying that host d=
evelopers don&#39;t always and automatically do what network operators want=
 them to do? If that&#39;s motivated by the fact that they are acting in th=
eir users&#39; interests, it seems to me that they are justified in doing s=
o, and in fact, would be remiss not to.</div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">
&gt; With the difference that the standards clearly specify what the curren=
t<br>
&gt; state of affairs is.<br>
<br>
</span>and now we need to make the wannabe document match what the state of=
<br>
affairs is in networking.<br></blockquote><div><br></div><div>That doesn&#3=
9;t mean &quot;we&#39;ve been violating the standards, so now the standards=
 have to change to match what we&#39;ve been doing, even if other parties a=
re depending on the standards&quot;, does it? :-)</div></div></div></div>

--001a1143703ae8b0d7054928d86d--


From nobody Wed Feb 22 17:51:48 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0F66129D8E; Wed, 22 Feb 2017 17:51:41 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VKgCKUDEAArz; Wed, 22 Feb 2017 17:51:38 -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 23887129DAB; Wed, 22 Feb 2017 17:51:37 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 9249A80F20; Thu, 23 Feb 2017 02:51:30 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <9a3bf7fe-e482-3796-5973-21db9ebcb055@si6networks.com>
Date: Wed, 22 Feb 2017 22:48:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YotlwohOmUNnh4jUzZztrWslhh4>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, "ops-dir@ietf.org" <ops-dir@ietf.org>, ipv6@ietf.org, "ops-ads@tools.ietf.org" <ops-ads@tools.ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 01:51:42 -0000

Folks,

One thing that is missing in this document is a reality-check of the use
of Extension Headers in the public Internet.

No matter whether one likes it or not, published studies regarding the
drop rate of IPv6 packets with extension headers should signal an alarm
in at least the operational world.

RFC7872 ("Observations on the Dropping of Packets with IPv6 Extension
Headers in the Real World") might be of use here.

Thanks,
Fernando




On 02/01/2017 08:49 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Internet Protocol, Version 6 (IPv6) Specification'
>   <draft-ietf-6man-rfc2460bis-08.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies version 6 of the Internet Protocol (IPv6).
>    It obsoletes RFC2460
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information: 
>     rfc4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard - IETF stream)
>     rfc3168: The Addition of Explicit Congestion Notification (ECN) to IP (Proposed Standard - IETF stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
> 
> 
> --------------------------------------------------------------------
> 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 22 18:12:05 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B56D129E1E; Wed, 22 Feb 2017 18:11:58 -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 autolearn_force=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 0kjm4kYNC1Os; Wed, 22 Feb 2017 18:11:56 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 C5D83129E13; Wed, 22 Feb 2017 18:11:56 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cgiss-0007Pd-1R; Thu, 23 Feb 2017 02:11:54 +0000
Date: Thu, 23 Feb 2017 09:11:50 +0700
Message-ID: <m2a89dveop.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hmiMr-xXWFGGkwuM2ZmX-C0xvwg>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 02:11:58 -0000

> As a host developer I strongly oppose that. 

as a network operator, i strongly opposed classfulness and will hold my
breath and have a tantrum.

> It will make life easier for network operators but make life harder
> for host OS developers, host operators, and host users.

users do not notice, except when device programmers break things.  i am
a host operator, and i do not need classfulness.  slaac is nice in small
lans, and the /64 id is fine for the slaac niche.

> And it is absolutely inappropriate to change this nowin given that the /64
> boundary has been the standard for the last 20 years. 

the other week you were saying i should be patient and we could change
it in another decade from now.  now you say forever, it's cast in
concrete.

well, we are breaking that concrete, have broken it for years, and it's
time 6man wakes up, smells the coffee, and gets with reality.

randy


From nobody Wed Feb 22 19:44:05 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 634BF12952E; Wed, 22 Feb 2017 19:44:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e02v_gz9WgNI; Wed, 22 Feb 2017 19:44:02 -0800 (PST)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::243]) (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 D67A51294CC; Wed, 22 Feb 2017 19:43:58 -0800 (PST)
Received: by mail-pf0-x243.google.com with SMTP id p185so732746pfb.0; Wed, 22 Feb 2017 19:43:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=wQjEzg+XkiRrkw21WP273ikYruqMe/OQ2xV0TvFcTXk=; b=Sg02CUh4Nf+z+JLi+rKmFg3tTzQxOfes9Jj+j4LcwSwOuz1aL/pOlndQiYzN3HddXi bwB6APPghwxQq+ZyI+3uO8J/tQ02+pC0dqQ/yME5uraZP++yoKVpRVQA/yU2/tWWD066 aiNcVvlFiJ51j5XrNKdefCGs+hDzU5m7UuUxLzA3lPx1+TSZYVBk4XTMo2MOchrUeQLn V0Lu3MW/7ylLKvlE4JGRRCtggRyugfJ1APZ5F2q7g2u3ECr382WF9m/tA0OHs66EG8Ga IYTn3at1nbO18klbk+7qQB0WG3Mn3IEWrm4vKB18nOX3W1wmcjEeGgBG4xA/Jphp2laU RfIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=wQjEzg+XkiRrkw21WP273ikYruqMe/OQ2xV0TvFcTXk=; b=csOMxudL2WFEfHMUh8tceF5HvWxZTBR84JZqjlA/T5oQgNjSNlMHswJAIiJSBe5v7/ PFrXH/4T1S/G+XSvTeDn3fI0vbuTaFTWmIswiz84BAPsN6OkjkqIfpvvAyms0g1JiISu dahNbRFVUBKyAGySCMskF3VsKYPn3dNp+20BosttOn3M2kSaMSCghJdkGBjGU+rA/j2a ZPOs//RNxQFxvv1rnkKs+Tn0i2cRxSnZYwVApnilUY2O+U+Xv0Pi7tpoJZs11Hva27iS P3AiNxhENlCsKzhOLldxXu6IGBmkCmhVFZzpDr7r+9KmFGMfi7VvTIYfz0bEzG71UXi2 i1mQ==
X-Gm-Message-State: AMke39mRHZotpFVONKcjA5WjOeIH0cLofcA2XirFYrzGw0NtplgtOVOt7Pt1Z0TsO2O79A==
X-Received: by 10.84.210.46 with SMTP id z43mr52598839plh.11.1487821438300; Wed, 22 Feb 2017 19:43:58 -0800 (PST)
Received: from [192.168.178.21] ([118.149.111.84]) by smtp.gmail.com with ESMTPSA id t184sm6199993pgb.11.2017.02.22.19.43.54 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Feb 2017 19:43:57 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com>
Date: Thu, 23 Feb 2017 16:44:01 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/150Xujo41LAPK4bH6DGEgnJYoJk>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 03:44:03 -0000

On 23/02/2017 13:41, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 5:20 AM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> Nobody is saying that /64 isn't extremely widely used where it's
>> appropriate to have a portable fixed length IID. Set the default
>> at 64 and trust operators to change it where they need to.
>> That's realistic.
> 
> 
> As a host developer I strongly oppose that. It will make life easier for
> network operators but make life harder for host OS developers, host
> operators, and host users.

I'm sorry, I'm wondering which word in my recent message that said
"I'm not aware of any generally available running code that will
be changed in even one instruction by the final text - that is indeed
a requirement for advancement to Internet Standard."
is hard to understand.

We are not suggesting to change the /64 usage in all the hosts that need to
use it. We are simply pointing out other nodes do and will behave differently.
/64 is an interop requirement on links that use /64. It is not an interop
requirement on links that don't use /64. RFC4291 is mistaken about this.

   Brian


> 
> And it is absolutely inappropriate to change this now in given that the /64
> boundary has been the standard for the last 20 years. It will break
> deployed code that relies on the current standard. (That includes concrete
> code I can point to that I know runs on tens of millions of devices.)
> That's not acceptable to do in a standard reclassification.
> 


From nobody Wed Feb 22 20:13:58 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704A8129567 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 20:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCPtKZAkn8xP for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 20:13:53 -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 0A9B8129568 for <ietf@ietf.org>; Wed, 22 Feb 2017 20:13:51 -0800 (PST)
Received: by mail-vk0-x22b.google.com with SMTP id x75so13669706vke.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 20:13:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h18CdDaMcraCcH0aW8ri4yiFf1OvNdYENLqKcMXz1bA=; b=P0WRW41p3bdzbMfsS1RWEf3nM3xceFLY3Bjld6Z0WEYMXn+r6/bDemEHlo58kI0+zx G1z3xENxcA1/S4FemdCzQyqdixFLCfoFxzGqxb2qKTT0UzqZyEJ/isqZcltYwWK0zjgd bweUOumAfsdg0ODQE3BWP7Q/7uE8Fu0C9HcXg09aX95nwQvmFpvJBFQZTw0SLliA7gwq ORyIqzdVkdid46C8HLuNv9lMEF3/620ZuKE9DEq24Jl/HdFXDBQCL16fq1StGfn8phJF nbBbNHQGwpi5ZryYPcIhNJV32kX9wKLf+xTJpuyygT8y4V7TAN7osSpyiDrBuADdNuaw KW9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h18CdDaMcraCcH0aW8ri4yiFf1OvNdYENLqKcMXz1bA=; b=GyerHwqlH1qUIR6DuzimBfzVFHJaAxMz1MqYQsk6mOcFAkiMp5LwfE6xJtIOOLa0lI K9xN919g3BvBfbVVddop21OOPjqVte4NslQb3B36QbHLVDbRmA7pEAx0RXjKWPehj79X s65u0bN773nBA0NxgI98ZW1MeFFRLJ9VeC91zExDB+TKyeCBf16eNjQ88YF4Q1fL3asZ 4uhQLFNfOWSqY8FItIp3WPS0l3UhGYAbXg1AffbnrEoZ/xrbFKdUqG/+giKGDJyly/FT alxA1TcKaQGIbk6XxTUDPo7qQf9sH9DDu3cF/GFBNRYVT3cqRr410IsnOOeDQdEpFARk zHsA==
X-Gm-Message-State: AMke39ll5AytF+WsORaAgjEN+gg4ph7yOimPNM3NFEzE+CTa1NG+dqfm8ef9MRD6w2hHiVqecKq0kMqMAk/GeYec
X-Received: by 10.31.142.68 with SMTP id q65mr17842228vkd.83.1487823229859; Wed, 22 Feb 2017 20:13:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 20:13:29 -0800 (PST)
In-Reply-To: <m2a89dveop.wl-randy@psg.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 13:13:29 +0900
Message-ID: <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a1143703a1b124d05492ad7bd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c0-JCJt9j62zbvM9E_qC_jRhSoQ>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:13:54 -0000

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

On Thu, Feb 23, 2017 at 11:11 AM, Randy Bush <randy@psg.com> wrote:

> users do not notice, except when device programmers break things.  i am
> a host operator, and i do not need classfulness.  slaac is nice in small
> lans, and the /64 id is fine for the slaac niche.
>

Please think about the arguments in RFC 7934. If some misguided operator
assigns your device exactly one IPv6 address, that hugely constrains what
the device can do and how well it does it. And I do think that users notice
when their network is flaky.


> > And it is absolutely inappropriate to change this nowin given that the
> /64
> > boundary has been the standard for the last 20 years.
>
> the other week you were saying i should be patient and we could change
> it in another decade from now.  now you say forever, it's cast in
> concrete.
>

Sorry, let me clarify: it is inappropriate to change that now *in this
document*. As I said elsewhere, the IETF and 6man absolutely have the
ability to change the standard, but it should follow the proper process:
write a draft, get consensus, update whatever RFC RFC 4291bis eventually
becomes. I'm not saying we need to wait a decade.

(I do also happen to think that it would be better if we waited a decade
before changing this, because we're only 5 or so years into large-scale
deployment that will hopefully last at least 3 or 4 decades. However, I
don't expect many people to agree with me on that, so I'm not trying to
make that argument here.)


> well, we are breaking that concrete, have broken it for years, and it's
> time 6man wakes up, smells the coffee, and gets with reality.
>

What you do in your network is your business. If it works for you - which
we know it does - I have no problem with that. What I have a problem with
is when someone tells me that OS code needs to change because some operator
thinks that "we give this network a /120 subnet makes sense because that
matches the /24 we use IPv4, and we should be free to do that".

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 11:11 AM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">users do not notice, e=
xcept when device programmers break things.=C2=A0 i am<br>
a host operator, and i do not need classfulness.=C2=A0 slaac is nice in sma=
ll<br>
lans, and the /64 id is fine for the slaac niche.<br></blockquote><div><br>=
</div><div>Please think about the arguments in RFC 7934. If some misguided =
operator assigns your device exactly one IPv6 address, that hugely constrai=
ns what the device can do and how well it does it. And I do think that user=
s notice when their network is flaky.</div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">&gt; And it is absolutely inappropriate =
to change this nowin given that the /64<br>
<span class=3D"gmail-">&gt; boundary has been the standard for the last 20 =
years.<br>
<br>
</span>the other week you were saying i should be patient and we could chan=
ge<br>
it in another decade from now.=C2=A0 now you say forever, it&#39;s cast in<=
br>
concrete.<br></blockquote><div><br></div><div>Sorry, let me clarify: it is =
inappropriate to change that now *in this document*. As I said elsewhere, t=
he IETF and 6man absolutely have the ability to change the standard, but it=
 should follow the proper process: write a draft, get consensus, update wha=
tever RFC RFC 4291bis eventually becomes. I&#39;m not saying we need to wai=
t a decade.</div><div><br></div><div>(I do also happen to think that it wou=
ld be better if we waited a decade before changing this, because we&#39;re =
only 5 or so years into large-scale deployment that will hopefully last at =
least 3 or 4 decades. However, I don&#39;t expect many people to agree with=
 me on that, so I&#39;m not trying to make that argument here.)</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">well, we are =
breaking that concrete, have broken it for years, and it&#39;s<br>
time 6man wakes up, smells the coffee, and gets with reality.<br></blockquo=
te><div><br>What you do in your network is your business. If it works for y=
ou - which we know it does - I have no problem with that. What I have a pro=
blem with is when someone tells me that OS code needs to change because som=
e operator thinks that &quot;we give this network a /120 subnet makes sense=
 because that matches the /24 we use IPv4, and we should be free to do that=
&quot;.</div></div></div></div>

--001a1143703a1b124d05492ad7bd--


From nobody Wed Feb 22 20:17:11 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9711912A032 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 20:17:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q55bqSOBmIej for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 20:17:09 -0800 (PST)
Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::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 E494212A02F for <ietf@ietf.org>; Wed, 22 Feb 2017 20:17:07 -0800 (PST)
Received: by mail-ua0-x234.google.com with SMTP id 40so14955145uau.2 for <ietf@ietf.org>; Wed, 22 Feb 2017 20:17:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d6xogAejicwj6EhYbqXusEwUqwxFQgnhWn7pmGth/eY=; b=TWiXaaAoxzy7tRUsL6YBlFTcHocR+B9WaGOQYmepbtIIkCyCDH6T7hm8JzGI+sZE0p rRE/yVopzELWQe52YoXtUPjZcvf/T8Idaoa48DnSsL+qIyRwgoQviV2PaSfo1Iip2Op4 Eiwu/cfCtJnFUItXM0wvur5aGdbHQ+qcOLGmsDbEHraauMP+sRsnWquFt5PMjiNW2ead Je3ZkrVT3+zNFDlMGYmwUpGSYxqgkmxqnK/9/ECUdM9+EzfRQznjfsAfUU7PCKGv8kx5 jCwAlvGkOrvdyxOKkOUpjPyXyxamA2xS6GZF7CLCQtKvnY5Kfx9gtW56mo3wZi9zCG/u szxA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d6xogAejicwj6EhYbqXusEwUqwxFQgnhWn7pmGth/eY=; b=jZApmsmFYg4cv47FFczy3EgW4zo9pQBtNfuGRkP3I9XfZtwnJuoiLIzvU1z5xc4nsO 6sRS0pfBi9Ly7HCPpB22HIB9Sr+kBVoqIfCuVPI3V91hqK9epbQdO4gH1GfBOiw4VELo asFuCeaOCLiCbzfl36z1DtH0DHEUAPOh44M/jHnmXY9EXcKRzioIFSsamYSvQ4I/K0yK m+ut4c+fX9Cc69Laq3cHwrf+mGUAFsvjeuElOzmHNcuonmhGq7MOkkiALKjujB7fJyep mj2+UPV4A0GXRaUVTrZvf1pJuxBhD8CcusQ59Q1lEVSuu1tTpnuZa225CkRyJ+o3W4NU LZ+w==
X-Gm-Message-State: AMke39nWzO0pzTVTWOWhP8ngbbJbe57L94HR0fT0RK5j/N9IGpC5M5rkH8a/tCtSL/pUsgD0eIE++pO9o3yR6Rt7
X-Received: by 10.159.36.56 with SMTP id 53mr11979037uaq.124.1487823426797; Wed, 22 Feb 2017 20:17:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 20:16:46 -0800 (PST)
In-Reply-To: <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 13:16:46 +0900
Message-ID: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a113e1ca0d82ae705492ae2d3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NlgPfH3UQd3kerhWjwR3H9u9D6A>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:17:09 -0000

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

On Thu, Feb 23, 2017 at 12:44 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> I'm sorry, I'm wondering which word in my recent message that said
> "I'm not aware of any generally available running code that will
> be changed in even one instruction by the final text - that is indeed
> a requirement for advancement to Internet Standard."
> is hard to understand.
>

Help he understand, then. There is widely-deployed code that assumes that
the interface ID is 64 and does not work on anything other than 64 bit
prefix lengths. Currently that code is correct on all unicast space. If you
change RFC 4291, won't that code be incorrect?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 12:44 PM, Brian E Carpenter <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpent=
er@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I&#39;=
m sorry, I&#39;m wondering which word in my recent message that said<br>
&quot;I&#39;m not aware of any generally available running code that will<b=
r>
be changed in even one instruction by the final text - that is indeed<br>
a requirement for advancement to Internet Standard.&quot;<br>
is hard to understand.<br></blockquote><div><br></div><div>Help he understa=
nd, then. There is widely-deployed code that assumes that the interface ID =
is 64 and does not work on anything other than 64 bit prefix lengths. Curre=
ntly that code is correct on all unicast space. If you change RFC 4291, won=
&#39;t that code be incorrect?</div></div></div></div>

--001a113e1ca0d82ae705492ae2d3--


From nobody Wed Feb 22 20:25:46 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA1C129574; Wed, 22 Feb 2017 20:25:41 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 SPzRl06JTKk4; Wed, 22 Feb 2017 20:25:39 -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 43D6F12956E; Wed, 22 Feb 2017 20:25:39 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 3DA4780F12; Thu, 23 Feb 2017 05:25:34 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>, Randy Bush <randy@psg.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com>
Date: Thu, 23 Feb 2017 01:25:30 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BcrQWcN-1vNpXJjeX4A1CT8S9ks>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:25:41 -0000

On 02/23/2017 01:13 AM, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 11:11 AM, Randy Bush <randy@psg.com
> <mailto:randy@psg.com>> wrote:
[...]
>     > And it is absolutely inappropriate to change this nowin given that
>     the /64
>     > boundary has been the standard for the last 20 years.
> 
>     the other week you were saying i should be patient and we could change
>     it in another decade from now.  now you say forever, it's cast in
>     concrete.
> 
> 
> Sorry, let me clarify: it is inappropriate to change that now *in this
> document*. As I said elsewhere, the IETF and 6man absolutely have the
> ability to change the standard, but it should follow the proper process:
> write a draft, get consensus, update whatever RFC RFC 4291bis eventually
> becomes. I'm not saying we need to wait a decade.
> 
> (I do also happen to think that it would be better if we waited a decade
> before changing this, because we're only 5 or so years into large-scale
> deployment that will hopefully last at least 3 or 4 decades. However, I
> don't expect many people to agree with me on that, so I'm not trying to
> make that argument here.)

Isn't that actually an argument for waiting before moving rfc4291bis to
full standard?

If you'd wait to change it, why would you want to cast this into stone
now? So that, later you can argue that "it's a full standard document...
so we shouldn't change it"?


-- 
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 22 20:28:37 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A04129560; Wed, 22 Feb 2017 20:28:36 -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 autolearn_force=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 Vmxeoao4CPx8; Wed, 22 Feb 2017 20:28:35 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 4F5EC129577; Wed, 22 Feb 2017 20:28:35 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cgl16-0008HZ-5U; Thu, 23 Feb 2017 04:28:32 +0000
Date: Thu, 23 Feb 2017 11:28:28 +0700
Message-ID: <m2vas1ttsj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mx_9IflFsIxAhXtWOhnWjiUlzo8>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:28:36 -0000

> the IETF and 6man absolutely have the ability to change the standard,
> but it should follow the proper process: write a draft, get consensus,

that is the process we are currently in.  but there seems to be serious
disagreement over the draft.

randy


From nobody Wed Feb 22 20:34:24 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBA0812A06F; Wed, 22 Feb 2017 20:34:22 -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 autolearn_force=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 lNJLcp9OKUDS; Wed, 22 Feb 2017 20:34:21 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 7498912A060; Wed, 22 Feb 2017 20:34:14 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1cgl6a-0008Ig-7r; Thu, 23 Feb 2017 04:34:12 +0000
Date: Thu, 23 Feb 2017 11:34:08 +0700
Message-ID: <m2r32pttj3.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jd6ExNtA8dh5lsJ5Us8gHuyCguw>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:34:23 -0000

> Help he understand, then. There is widely-deployed code that assumes that
> the interface ID is 64 and does not work on anything other than 64 bit
> prefix lengths.

if you have code which is hard coded to want to be on a network with a
17.5 bit netmask, then put it on networks with 17.5 bit masks.  enjoy.

unless it is doing something useful with that restriction, such as
slaac, you're severly restricting the usability of your product.  your
choice.

randy


From nobody Wed Feb 22 20:39:47 2017
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F5312A096; Wed, 22 Feb 2017 20:39:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 3y8lgdwveT2H; Wed, 22 Feb 2017 20:39:43 -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 38AA512A08C; Wed, 22 Feb 2017 20:39:29 -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 v1N4dSSu047391; Wed, 22 Feb 2017 21:39:28 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v1N4dJ6c047147 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 22 Feb 2017 21:39:19 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 22 Feb 2017 20:39:18 -0800
Received: from XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) by XCH15-06-11.nw.nos.boeing.com ([137.136.239.220]) with mapi id 15.00.1263.000; Wed, 22 Feb 2017 20:39:18 -0800
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: RE: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Topic: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Thread-Index: AQHSi9gxgtRG27MIc0yfTQ6D9ojxU6FzLTeAgACXjICAAOx1AIAAGViAgAATdACAAANaAIAACw2AgABz1ICAADvUgIAABe+AgABepQCAAEj5gIAAMu+AgAAJJwD//3qsQA==
Date: Thu, 23 Feb 2017 04:39:18 +0000
Message-ID: <0f3db3bd87eb4a9ba51360d9b73751e3@XCH15-06-11.nw.nos.boeing.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dzt6ox-82LisNtsqV5F4NhAQSnA>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 04:39:45 -0000

RnJvbTogaXB2NiBbbWFpbHRvOmlwdjYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIExv
cmVuem8gQ29saXR0aQ0KDQo+IEhlbHAgaGUgdW5kZXJzdGFuZCwgdGhlbi4gVGhlcmUgaXMgd2lk
ZWx5LWRlcGxveWVkIGNvZGUgdGhhdCBhc3N1bWVzDQo+IHRoYXQgdGhlIGludGVyZmFjZSBJRCBp
cyA2NCBhbmQgZG9lcyBub3Qgd29yayBvbiBhbnl0aGluZyBvdGhlciB0aGFuDQo+IDY0IGJpdCBw
cmVmaXggbGVuZ3Rocy4gQ3VycmVudGx5IHRoYXQgY29kZSBpcyBjb3JyZWN0IG9uIGFsbCB1bmlj
YXN0DQo+IHNwYWNlLiBJZiB5b3UgY2hhbmdlIFJGQyA0MjkxLCB3b24ndCB0aGF0IGNvZGUgYmUg
aW5jb3JyZWN0Pw0KDQpUaGlzIHNob3dzIHByZWNpc2VseSB3aHkgaXQgaXMgdXJnZW50IHRvIHVw
ZGF0ZSBSRkMgNDI5MSwgdG8gY29ycmVjdCB0aGF0IG5vdGlvbiBvZiBhIGZpeGVkIElJRCwgYmVm
b3JlIGl0J3MgdG9vIGxhdGUgdG8gc2V0IHRoaW5ncyBzdHJhaWdodCBhZ2Fpbi4NCg0KUkZDIDQy
OTEgZGVzY3JpYmVzIGFueSBudW1iZXIgb2YgYWRkcmVzcyBwcmVmaXhlcyB0aGF0IGFyZSBub3Qg
LzY0LiBGb3IgZXhhbXBsZToNCg0KICAgSVB2NiB1bmljYXN0IGFkZHJlc3NlcyBhcmUgYWdncmVn
YXRhYmxlIHdpdGggcHJlZml4ZXMgb2YgYXJiaXRyYXJ5DQogICBiaXQtbGVuZ3RoLCBzaW1pbGFy
IHRvIElQdjQgYWRkcmVzc2VzIHVuZGVyIENsYXNzbGVzcyBJbnRlci1Eb21haW4NCiAgIFJvdXRp
bmcuDQoNCkltcG9ydGFudCBwb2ludC4gQXJiaXRyYXJ5IGxlbmd0aC4gVGhhdCBkb2VzIG5vdCBt
ZWFuIDY0IGJpdHMuDQoNCkFuZA0KDQogICB8ICAgICAgICAgIG4gYml0cyAgICAgICAgICAgICAg
IHwgICAgICAgICAgIDEyOC1uIGJpdHMgICAgICAgICAgICB8DQogICArLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQogICB8
ICAgICAgIHN1Ym5ldCBwcmVmaXggICAgICAgICAgIHwgICAgICAgICAgIGludGVyZmFjZSBJRCAg
ICAgICAgICB8DQogICArLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSstLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rDQoNClRoaXMgbmV4dCBuZWVkcyB0byBiZSBjbGFyaWZp
ZWQvY29ycmVjdGVkLCBhcyBpdCBzaG91bGQgb25seSBhcHBseSB0byB0aGUgMjAwMDo6LzMgc3Bh
Y2U6DQoNCiAgIEFsbCBHbG9iYWwgVW5pY2FzdCBhZGRyZXNzZXMgb3RoZXIgdGhhbiB0aG9zZSB0
aGF0IHN0YXJ0IHdpdGggYmluYXJ5DQogICAwMDAgaGF2ZSBhIDY0LWJpdCBpbnRlcmZhY2UgSUQg
ZmllbGQgKGkuZS4sIG4gKyBtID0gNjQpLCBmb3JtYXR0ZWQgYXMNCiAgIGRlc2NyaWJlZCBpbiBT
ZWN0aW9uIDIuNS4xLiAgR2xvYmFsIFVuaWNhc3QgYWRkcmVzc2VzIHRoYXQgc3RhcnQgd2l0aA0K
ICAgYmluYXJ5IDAwMCBoYXZlIG5vIHN1Y2ggY29uc3RyYWludCBvbiB0aGUgc2l6ZSBvciBzdHJ1
Y3R1cmUgb2YgdGhlDQogICBpbnRlcmZhY2UgSUQgZmllbGQuDQoNCkJlcnQNCg0K


From nobody Wed Feb 22 21:58:26 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0A41295EE for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 21:58:25 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBb2U3dIlQUq for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 21:58:23 -0800 (PST)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 9795C1295CA for <ietf@ietf.org>; Wed, 22 Feb 2017 21:58:23 -0800 (PST)
Received: by mail-ua0-x22d.google.com with SMTP id h65so15898607uah.0 for <ietf@ietf.org>; Wed, 22 Feb 2017 21:58:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eU9cSmJt7o57lnu+mnWjOOh4HYbS/28iWPqaOimf9W8=; b=tQiy2MlWhFsrl8vonFFKbCdjDMfi2HBMRPqHuhcf2xAw+j0SY/SGOf2+KtOPuPKolX LHrdoE4LxP10EtlKewk7sYGbK54nRhD2KdqAlnTXA6MtloO4CYIqlnhcnlT9+UqErPya d7FSRP93VpH4D1pxR9HXUUkmI0xqjYg7GXIL1ci/Ler0LEHJzfu4Up6lKLPANFxBEsZs Csj5MwX4Ym1vRx4DOt/wv+vtta+e9wt+qtnDzSv83nC1v27TOsOuG29NRWLzG73y1dhz gXCTmR+9ZqdcseAvi3L90qA5zWRvrgqBW5v+wV1/fCfAPigwPwYh9u68lzUGfk3VBf38 yx+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eU9cSmJt7o57lnu+mnWjOOh4HYbS/28iWPqaOimf9W8=; b=QSIfTmxyuy9aokeQc4ULoL0uM31vK3tvF0WilC2l0dpAhEIBvi2BuhYq7XN5hqhnwm nl3p2IHwO4oSEXGUuqn8DZwWMNQjG97o2H6Va7cqohTdqjOqUnTzg9X/fQ9sTX2tQkgQ fyPxr64zkVFR7ZE9rQqwW02oza79aEasJTCAjWIVVPUIJQqtsdXMMKMVwjImtXLyeEb1 aU8IZDoHA1JBnguAl6kvKiAP4jZ+OC/Q5UkaKfnfr47GUjt5M4AVIVqUkelfUNj7aLpi JzX6QDrfF8s4UB7aKd9FR7T8lh+OwqQXTh0mZ7Qb9f+zcUM+EGcUJPsdSvSs7/nmTYiw p1uw==
X-Gm-Message-State: AMke39kdc2ClIh74J0h6gmH42QhgsuYeFyu7Dx/oz5/zlnEGYSVMQsjsLqqYlTzx+3Ix4n8r3zxn15MTTWdRkgOO
X-Received: by 10.176.8.4 with SMTP id a4mr2247018uaf.171.1487829502501; Wed, 22 Feb 2017 21:58:22 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 21:58:01 -0800 (PST)
In-Reply-To: <0f3db3bd87eb4a9ba51360d9b73751e3@XCH15-06-11.nw.nos.boeing.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <0f3db3bd87eb4a9ba51360d9b73751e3@XCH15-06-11.nw.nos.boeing.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 14:58:01 +0900
Message-ID: <CAKD1Yr2o3eyuhvij4=KjsVMTor=oh5N8AWfjOCJ_jh6nSA0=Gg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Content-Type: multipart/alternative; boundary=f403045ee778fbfa8f05492c4cbd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qt4vgh1k6cqfgkGVLWJyY2xJM30>
Cc: "draft-ietf-6man-rfc4291bis@ietf.org" <draft-ietf-6man-rfc4291bis@ietf.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, "6man-chairs@ietf.org" <6man-chairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 05:58:25 -0000

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

On Thu, Feb 23, 2017 at 1:39 PM, Manfredi, Albert E <
albert.e.manfredi@boeing.com> wrote:

> > Help he understand, then. There is widely-deployed code that assumes
> > that the interface ID is 64 and does not work on anything other than
> > 64 bit prefix lengths. Currently that code is correct on all unicast
> > space. If you change RFC 4291, won't that code be incorrect?
>
> This shows precisely why it is urgent to update RFC 4291, to correct that
> notion of a fixed IID, before it's too late to set things straight again.
>

Ok, so you're suggesting that we drop the attempt to reclassify RFC 4291,
and instead write a new document to update it? That's a possible course of
action. It would only result in your desired outcome if there was rough
consensus to change the boundary, but as I said before, I'm not going to
oppose that course of action.


>    IPv6 unicast addresses are aggregatable with prefixes of arbitrary
>
   bit-length, similar to IPv4 addresses under Classless Inter-Domain
>    Routing.
>
> Important point. Arbitrary length. That does not mean 64 bits.
>

Nobody is disagreeing with that text. Please refer to the earlier
clarifications in this thread and the discussion in 6man that pointed out
that *routing* based on prefix lengths != 64 is independent from *interface
IDs* being required to be 64 bits long or not.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 1:39 PM, Manfredi, Albert E <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:albert.e.manfredi@boeing.com" target=3D"_blank">albert.e.manfr=
edi@boeing.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><span class=3D"gmail-">&gt; Help he understand, then. There =
is widely-deployed code that assumes<br>
&gt; that the interface ID is 64 and does not work on anything other than<b=
r>
&gt; 64 bit prefix lengths. Currently that code is correct on all unicast<b=
r>
&gt; space. If you change RFC 4291, won&#39;t that code be incorrect?<br>
<br>
</span>This shows precisely why it is urgent to update RFC 4291, to correct=
 that notion of a fixed IID, before it&#39;s too late to set things straigh=
t again.<br></blockquote><div><br></div><div>Ok, so you&#39;re suggesting t=
hat we drop the attempt to reclassify RFC 4291, and instead write a new doc=
ument to update it? That&#39;s a possible course of action. It would only r=
esult in your desired outcome if there was rough consensus to change the bo=
undary, but as I said before, I&#39;m not going to oppose that course of ac=
tion.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">=C2=A0 =C2=A0IPv6 unicast addresses are aggregatable with prefixes of ar=
bitrary<br></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=C2=A0 =C2=A0bit-length, similar to IPv4 addresses under Classless Inter-Do=
main<br>
=C2=A0 =C2=A0Routing.<br>
<br>
Important point. Arbitrary length. That does not mean 64 bits.<br></blockqu=
ote><div><br></div><div>Nobody is disagreeing with that text. Please refer =
to the earlier clarifications in this thread and the discussion in 6man tha=
t pointed out that *routing* based on prefix lengths !=3D 64 is independent=
 from *interface IDs* being required to be 64 bits long or not.</div></div>=
</div></div>

--f403045ee778fbfa8f05492c4cbd--


From nobody Wed Feb 22 22:00:07 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8139F1295F6 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:00:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UL6DzIG18dMQ for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:00:02 -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 BFEF5129A41 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:00:00 -0800 (PST)
Received: by mail-vk0-x22e.google.com with SMTP id k127so14516525vke.0 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:00:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lvK9d7IZ/c3VJ8lwMF+gUjWGxiw32s3P5sAdBdTSLeY=; b=k6VNIDxj33Bb1/VxW1AuMnmAtwR/MU89ud+e0UAtLvP7uoJ+wvoPeotEFMY+7KxRG9 SlBshh25GSzt2/DF7ILDiLS5tqlxCZXmnCQfWZ/0gZa6xJmcjGXEQFlec9pLj0jpXxyr N5Z/92flGMc/Yl4zmroYzESDtVGq20I1XiiHBG/fHwIZZJMmP5ZaFyH5zq5vJ7gGsnkl 2ZQrs19AdSH1uuMPdxXjsUbGDkCHy9dKNE1+JI5YtMWtyKTejhcG7/2D9wmXf+mTmKUW vMjZP9LxmDRdm7gplUI8u6x3gRXfelyegww61omYMd1XrMFZkRtqbs0/1qCAI63eCH5s K4yQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lvK9d7IZ/c3VJ8lwMF+gUjWGxiw32s3P5sAdBdTSLeY=; b=MGE3RoHxSYwJ+vH/8mykvqagT/VD3+nqAzfttGW/+gEJOcW5EmlucB9kdfva5C8U3I 70vPVEdwZpYXRgweXHdpJYS29flDihSC6bX3DLEbGy8yPASSOGUqsroG5oz3oSrw3f4K D7+sTaZpLAOFKaE8Q/PGgEuwQvdtsHItuqNIgXix+TpIGeG5BvaeXyVILTvLah3C4ala SKI2IWGJehNPfmM7U2KTGioWSSePKPLNcpA7lsukvZB4eNZ3ey1dMDIg24DrybXS3BO+ w0MGrIKnlo9SiJHHmV225qiNIv9hRQ8dr96vZH2lXNlF6KjcyRanjfgi1ct7BeMxB3I2 /geA==
X-Gm-Message-State: AMke39m2iplsl3dtPq/scBBUtPj2zyfARZfDlpZoFLFj/Lh91xUjBlHEmuJ0sia0ExQJChfQc/cFRoVvl/v6Gpof
X-Received: by 10.31.248.193 with SMTP id w184mr18348163vkh.10.1487829599655;  Wed, 22 Feb 2017 21:59:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 21:59:39 -0800 (PST)
In-Reply-To: <m2r32pttj3.wl-randy@psg.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <m2r32pttj3.wl-randy@psg.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 14:59:39 +0900
Message-ID: <CAKD1Yr2pBJKFiuGV8cxr3ENx5oy7bWm54fK8-Fre0fApRU7hSA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=94eb2c14bd2ac66d8d05492c5212
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f1-dicQSMKQ-2B9_W9u_y6ZO8kU>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 06:00:03 -0000

--94eb2c14bd2ac66d8d05492c5212
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 23, 2017 at 1:34 PM, Randy Bush <randy@psg.com> wrote:

> if you have code which is hard coded to want to be on a network with a
> 17.5 bit netmask, then put it on networks with 17.5 bit masks.  enjoy.


That would be correct behaviour if the standard specified that IIDs are
17.5 bits long.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 1:34 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">if you have code which is hard coded to wa=
nt to be on a network with a<br>
17.5 bit netmask, then put it on networks with 17.5 bit masks.=C2=A0 enjoy.=
</blockquote><div><br></div><div>That would be correct behaviour if the sta=
ndard specified that IIDs are 17.5 bits long.</div></div></div></div>

--94eb2c14bd2ac66d8d05492c5212--


From nobody Wed Feb 22 22:05:34 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A5F51295DF for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:05:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tdl8Eh-X2eMN for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:05:27 -0800 (PST)
Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0:400c:c05::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 535E312A0D5 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:05:25 -0800 (PST)
Received: by mail-vk0-x233.google.com with SMTP id r136so14591682vke.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:05:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=W7PqxlxdOgWwHQumYUsk3WCr9jVy3Caqtw3gIorgkEo=; b=kGgyNeS28XcUXjSXVYcMuNO3PDBQJJXn4DSivoMcnJCACobCCFTDOK5fGidiaV4W/4 MITBXyx6utJvNfpnff0X1FL4VxxWnLL0kNR5BhPNWv/o3eJPk0LR1wdYaSU83/PkNij7 ZmQNWOihQr167bUDQVela23DhTNZmP3dZRJhpvzApEfLGwkgu4IPvSFBCaGAFsOudpuX Q/M3oPjmVEeSePzDlFbGIH1M7AvK/6nJPBmpZRqQhecr3Vy60qQO0m0TILxwaBZeQd7i Z8m2wstFhPWxIxXhCK8nfI1BH7Bkhoypx0Nn4nBPf035ALrA5lKMv1qB6JKAmW17Yw/a D63g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=W7PqxlxdOgWwHQumYUsk3WCr9jVy3Caqtw3gIorgkEo=; b=ttiFz9Z4TFOSbHdKEKg1Z2HGDuF+drOuS3NA2iK/8KJ5AtuayIysAge2iwsrbRSti4 2XiJCtucih7ZjVuI9m4lrzdp+KXnwOm28Yd2jS7pWkEzRXRN8SKYK7jPfWdsK2C/y19b lOrQHy7rkVoNI9pQSwpLkjb//nktOT4rRt76vMeCkdY5IKmVTFUAWcMfxNswZ4vGRNKl 72lcOc414DozOJwRrEtxv8N0l/0qrDrwrm91j4Y0s6arbr7JCIjhkU408xZERqUZTuA3 BLEuRsxfas+e9M93WFbcy+TcQ08uCx39mLzIsO01q29OtRQ4R+x0SazuzZhdG8bdxMFg oQ9Q==
X-Gm-Message-State: AMke39nfAkyix43MMYlVQWgIgcLii6u5p/+hIKNeY3Q3C7FWWB6bSJchkWVpwwINXPjFqLjh6FEEy4hN0phTRsqd
X-Received: by 10.31.59.197 with SMTP id i188mr13826143vka.45.1487829924052; Wed, 22 Feb 2017 22:05:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 22:05:03 -0800 (PST)
In-Reply-To: <m2vas1ttsj.wl-randy@psg.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <m2vas1ttsj.wl-randy@psg.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 15:05:03 +0900
Message-ID: <CAKD1Yr3cZxsFqkLf=obAngCp5W-1EMnn4bsx-JcvaEaHOYTOCw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a1142f1781c6dd905492c669e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rZ4X-xHJHN3dPDN1qJkPIh_GezM>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 06:05:28 -0000

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

On Thu, Feb 23, 2017 at 1:28 PM, Randy Bush <randy@psg.com> wrote:

> > the IETF and 6man absolutely have the ability to change the standard,
> > but it should follow the proper process: write a draft, get consensus,
>
> that is the process we are currently in.  but there seems to be serious
> disagreement over the draft.
>

AIUI the goal of the process is to reclassify the current specification.
That severely restricts the types of changes that are possible. That is the
basis on which this document gained WG consensus and reached IETF last call.

If we want to say that we're no longer reclassifying the current
specification but are instead opening the door to bigger changes, then the
document should go back to the WG for further work because the existing WG
consensus was based on the stated goal of reclassifying the document.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 1:28 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; the IETF and 6man ab=
solutely have the ability to change the standard,<br>
&gt; but it should follow the proper process: write a draft, get consensus,=
<br>
<br>
</span>that is the process we are currently in.=C2=A0 but there seems to be=
 serious<br>
disagreement over the draft.<br></blockquote><div><br></div><div>AIUI the g=
oal of the process is to reclassify the current specification. That severel=
y restricts the types of changes that are possible. That is the basis on wh=
ich this document gained WG consensus and reached IETF last call.</div><div=
><br></div><div>If we want to say that we&#39;re no longer reclassifying th=
e current specification but are instead opening the door to bigger changes,=
 then the document should go back to the WG for further work because the ex=
isting WG consensus was based on the stated goal of reclassifying the docum=
ent.</div></div></div></div>

--001a1142f1781c6dd905492c669e--


From nobody Wed Feb 22 22:25:14 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BCF61295E1 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CM4xdXNtXIC9 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:25:08 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c: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 5F1041295FA for <ietf@ietf.org>; Wed, 22 Feb 2017 22:25:07 -0800 (PST)
Received: by mail-vk0-x22c.google.com with SMTP id k127so14734688vke.0 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:25:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=9VkoS88Y+TN2j70K6EG7+QnynxD8pQsa+BUvbovFeUk=; b=ttd9Z2dD8JUUvvRGhR0yOCEWUMAREgIwjcafo1ZdztQqP55UxwaR4OqJMimdlZT+68 UmS5XP53M7vZmKZSsS9DxrIpfRe+egFzeNGlPtF7RwDmliW0uZSy5YY1WUCPFz+R6rNp TJWIAyVDSf3VCAbsQfjHm4EkNAoIrWOQndRE6KzPQVZ6MRvfVRP9oi8f+jV876Vj7eAv siQvUJ45cdEv/1GQv34OtE8adprMSam81eq8d/iKguECnJeX79aJDg1na6FPmYwBxSp4 hrM2rTAc8hkHy6EsQinidtpKvmJb0SySinUdCMcfU0u92LmSj6d7xJxKIBSLd9OTYDXK KuIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=9VkoS88Y+TN2j70K6EG7+QnynxD8pQsa+BUvbovFeUk=; b=UvnKdtrToH+LifQ6TkKLMBqQlIjxIP/Ui5QAe1wqK6OnFJpbtjuMh4OaxHOjM855Tr 3Apvcn0gyo9AUrQa6j1/ZYTUsAij98bejggLw8qu/7qVTqTuhkdr1llEmqMqDRWnONJA aio4kWcuikB8eo32iNEu2Zd8CzvatymIC0RvCziUXpAzWmxciddwn/bd0lP0vOTIwqrr j2Dp+BRJOlG+tmfAcf2z/mQ5unvEJV0VZmGHItDvfsdIOzbI9A15NqsxSGIQ+JvzmP0o vc/9nXz6lNIKtcmOHb+tgW3KR9ar0UHG+fUaXJxPTERAVLierxyIVKmdyh+kAjOBXG45 KeWQ==
X-Gm-Message-State: AMke39mS/OLtYBZb1Yn6vogKpmtGcIZJHeJ8ZNdVgaLD/K/YUv0SB50xcn1AmhlmiSsKooi+M+SZR2hqlSMqoL4H
X-Received: by 10.31.248.193 with SMTP id w184mr18386750vkh.10.1487831106291;  Wed, 22 Feb 2017 22:25:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Wed, 22 Feb 2017 22:24:45 -0800 (PST)
In-Reply-To: <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 15:24:45 +0900
Message-ID: <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c14bd2a93cdf005492cac98
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r8bkcpau74ELE3ak7mkkSqqf7Ns>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 06:25:09 -0000

--94eb2c14bd2a93cdf005492cac98
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 23, 2017 at 1:25 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> > (I do also happen to think that it would be better if we waited a decade
> > before changing this, because we're only 5 or so years into large-scale
> > deployment that will hopefully last at least 3 or 4 decades. However, I
> > don't expect many people to agree with me on that, so I'm not trying to
> > make that argument here.)
>
> Isn't that actually an argument for waiting before moving rfc4291bis to
> full standard?
>
> If you'd wait to change it, why would you want to cast this into stone
> now? So that, later you can argue that "it's a full standard document...
> so we shouldn't change it"?


I don't see why that argument would carry any weight. Full standards can be
changed and updated, too.

What I most care about is that if we make fundamental changes like this,
then it's not done as part of a reclassification, and the working group has
its say.

Whether the document says "full standard" or "draft standard" is not as
important as whether it says the right thing.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 1:25 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><spa=
n class=3D"gmail-">&gt; (I do also happen to think that it would be better =
if we waited a decade<br>
&gt; before changing this, because we&#39;re only 5 or so years into large-=
scale<br>
&gt; deployment that will hopefully last at least 3 or 4 decades. However, =
I<br>
&gt; don&#39;t expect many people to agree with me on that, so I&#39;m not =
trying to<br>
&gt; make that argument here.)<br>
<br>
</span>Isn&#39;t that actually an argument for waiting before moving rfc429=
1bis to<br>
full standard?<br>
<br>
If you&#39;d wait to change it, why would you want to cast this into stone<=
br>
now? So that, later you can argue that &quot;it&#39;s a full standard docum=
ent...<br>
so we shouldn&#39;t change it&quot;?</blockquote><div><br></div><div>I don&=
#39;t see why that argument would carry any weight. Full standards can be c=
hanged and updated, too.</div><div><br></div><div>What I most care about is=
 that=C2=A0if we make fundamental changes like this, then it&#39;s not done=
 as part of a reclassification, and the working group has its say.</div><di=
v><br></div><div>Whether the document says &quot;full standard&quot; or &qu=
ot;draft standard&quot; is not as important as whether it says the right th=
ing.</div></div></div></div>

--94eb2c14bd2a93cdf005492cac98--


From nobody Wed Feb 22 22:59:22 2017
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD01129639 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:59:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L1lWUbQIfhQC for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 22:59:15 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002: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 C7F53129635 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:59:02 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id v200so12631479ywc.3 for <ietf@ietf.org>; Wed, 22 Feb 2017 22:59:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oZWJP9/WNa6nR6JbW+cm5aSmTsBom70OzFfJlwhRg6A=; b=wPzpYuYkL4tM0udI++X/R4WHps4FeNLcHF5BkTHAE1ZzQjMb6YHzhvnN2vUo7pqlH5 l+RK4UH0kqck7e4wt67tpFfmoE9AfDg6ZYDCUfCqJRPjw/qqSES8aN4zU2CcWDRAqtDx VrErNHrF/jlMxfmBBheb3modL8ymy5ezoO+pDwte6ePlNEfYcLsUxN3GXSdBh4WQq8D0 f4+XWr5302Ua4TY4f3c2gq0jOgpuAuYI8PLOed0vS3N3GKrL2Sl/LKTvefhXBhsJimU5 5+TCp35mcUCrRdrOd4QwY2h19pygwj2FVxGt2yZNQFmrTfLAYJgqs73fQ21ptpWtYwts RdTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oZWJP9/WNa6nR6JbW+cm5aSmTsBom70OzFfJlwhRg6A=; b=KvAGywMrKdCUPlVxfgiIaIcAAv55374F6R0bEt0CGJIULNX6JgU6D4jfLq5SzIhPNo BLFrpJlnA5JnRYQtCr/8ZJMgIZPBx3mrweVro4Y/EyUT3X2BJipgnrzxmJlBBcetB75f C7TkxfU3II9aHGALF6mUDwOppmrDF+auRPwREqtNLI4aA2WFWp5It1lfKCi7tcT5gpah 8vDLDw+ko996pfXRBMbT9+9jwOvtj5QQuZqhf3t63fIBYJ2pRTAGOJa5k4kPNFHn7d4C E9msl+pMmKWa2ZyXK7ztAkLy50baPdbgetS79wf9bN3XzgTu4Gmp2yhVQMVeuzj6HL8Z S2rg==
X-Gm-Message-State: AMke39nmvyoTPeO4goiSpP6jfUUpi8XGTMSELJ+B0Nik53oxkc/PWVr/GJDWS6xVrAlEVNHy/dYOEPJJ4DTDKfSB
X-Received: by 10.129.129.3 with SMTP id r3mr27167259ywf.0.1487833141701; Wed, 22 Feb 2017 22:59:01 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.207.4 with HTTP; Wed, 22 Feb 2017 22:58:41 -0800 (PST)
In-Reply-To: <CAKD1Yr3cZxsFqkLf=obAngCp5W-1EMnn4bsx-JcvaEaHOYTOCw@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <m2vas1ttsj.wl-randy@psg.com> <CAKD1Yr3cZxsFqkLf=obAngCp5W-1EMnn4bsx-JcvaEaHOYTOCw@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Thu, 23 Feb 2017 15:58:41 +0900
Message-ID: <CAAedzxoO5RgkP7cCL+bfUQEitFto6yQ7eGbLLbBU7_FD9PJPmg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="94eb2c07dd3eecd77605492d25b8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pU9cKbi5GkachLaywDalXne8whk>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 06:59:17 -0000

--94eb2c07dd3eecd77605492d25b8
Content-Type: multipart/alternative; boundary=94eb2c07dd3ee5b61905492d25f7

--94eb2c07dd3ee5b61905492d25f7
Content-Type: text/plain; charset=UTF-8

On 23 February 2017 at 15:05, Lorenzo Colitti <lorenzo@google.com> wrote:

> On Thu, Feb 23, 2017 at 1:28 PM, Randy Bush <randy@psg.com> wrote:
>
>> > the IETF and 6man absolutely have the ability to change the standard,
>> > but it should follow the proper process: write a draft, get consensus,
>>
>> that is the process we are currently in.  but there seems to be serious
>> disagreement over the draft.
>>
>
> AIUI the goal of the process is to reclassify the current specification.
> That severely restricts the types of changes that are possible. That is the
> basis on which this document gained WG consensus and reached IETF last call.
>
> If we want to say that we're no longer reclassifying the current
> specification but are instead opening the door to bigger changes, then the
> document should go back to the WG for further work because the existing WG
> consensus was based on the stated goal of reclassifying the document.
>

I agree with the procedural concerns here.  Among other things, if we make
substantial changes it's hard to claim we have experience running the new
thing we've documented.

I tend to think of IID concept's primary use as: if I have the IID
::dead:beef/64 then for every new /64 PIO that's announced *I* can
reasonably expect to lay claim to prefix1::dead:beef/64,
prefix2::dead:beef/64, and so on.  (Support for this mode operations,
SLAAC, is a MUST.)

I don't personally find any major conflict when considering static and
stateful addressing.  For example, if there are 2 prefixes on a link, and
the administrators are using static addressing then prefix1::cafe and
prefix2::cafe do not in any way have to belong to the same interface on the
same host. ... at least as far as I understand it.  If prefix1 and prefix2
are each longer than /64 then each 64bit IID would still be unique--no
problems.  But if each were <=64 then it's just violating a recommendation
in the first paragraph of 2.4.1--not a big deal for the administrator that
wants to run that way.

I'm not sure if this adds anything useful to the discussion, though.
-Erik

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
3 February 2017 at 15:05, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"=
mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D=
"gmail_extra"><div class=3D"gmail_quote"><span class=3D"">On Thu, Feb 23, 2=
017 at 1:28 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"mailto:randy@ps=
g.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><span>&gt; the IETF and 6man absolutely have the abilit=
y to change the standard,<br>
&gt; but it should follow the proper process: write a draft, get consensus,=
<br>
<br>
</span>that is the process we are currently in.=C2=A0 but there seems to be=
 serious<br>
disagreement over the draft.<br></blockquote><div><br></div></span><div>AIU=
I the goal of the process is to reclassify the current specification. That =
severely restricts the types of changes that are possible. That is the basi=
s on which this document gained WG consensus and reached IETF last call.</d=
iv><div><br></div><div>If we want to say that we&#39;re no longer reclassif=
ying the current specification but are instead opening the door to bigger c=
hanges, then the document should go back to the WG for further work because=
 the existing WG consensus was based on the stated goal of reclassifying th=
e document.</div></div></div></div></blockquote><div><br></div><div>I agree=
 with the procedural concerns here.=C2=A0 Among other things, if we make su=
bstantial changes it&#39;s hard to claim we have experience running the new=
 thing we&#39;ve documented.</div><div><br></div><div>I tend to think of II=
D concept&#39;s primary use as: if I have the IID ::dead:beef/64 then for e=
very new /64 PIO that&#39;s announced *I* can reasonably expect to lay clai=
m to prefix1::dead:beef/64, prefix2::dead:beef/64, and so on. =C2=A0(Suppor=
t for this mode operations, SLAAC, is a MUST.)</div><div><br></div><div>I d=
on&#39;t personally find any major conflict when considering static and sta=
teful addressing.=C2=A0 For example, if there are 2 prefixes on a link, and=
 the administrators are using static addressing then prefix1::cafe and pref=
ix2::cafe do not in any way have to belong to the same interface on the sam=
e host. ... at least as far as I understand it.=C2=A0 If prefix1 and prefix=
2 are each longer than /64 then each 64bit IID would still be unique--no pr=
oblems.=C2=A0 But if each were &lt;=3D64 then it&#39;s just violating a rec=
ommendation in the first paragraph of 2.4.1--not a big deal for the adminis=
trator that wants to run that way.</div><div><br></div><div>I&#39;m not sur=
e if this adds anything useful to the discussion, though.</div><div>-Erik</=
div></div></div></div>

--94eb2c07dd3ee5b61905492d25f7--

--94eb2c07dd3eecd77605492d25b8
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMf7MhR+6WMlT9cAZ4MA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTEyMjA2MzcwNloXDTE3MDUy
MTA2MzcwNlowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMFGbCvV+u+in+H0HY3bqCemHVO+gk8MSoSt5cw8MyfvalJUBE+K8i0L
KO7g5Tf0Hwxwin3Y78Fjurdr5ScXC3q2XKlu/KeOcKZ629BIHXR3Bc4P1kbeSBqtdP1hQsXutC3N
LKA6HYfEAKX5La7jHPIPymFuzHi9jqRt1XPLBhUIx/BUgV2RaLkaLlKi1gilVaUzZ/bwKGEBPXd7
oqEa0bmYHg7nnH3c07Ka5FqwYFbFNH2B8N9qhsEvaidSWAYFR3c83MxaNvd0cc9VR+xkg4h9t4j8
kgMqch9g5WsqvEiB8X9avk0RfRrJXnLpGVE9SgWC+9g/4qHF7INLnWGpoGsCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBRSp79TZtpx4DfF6E+LlflJ0/FBvzAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAYNw4ea3dhqz3+6k7eFLEAto3ynoX
iT5jeLl+/a9UeVSG5MQjruVO3LeqKKs3757hNcyfMZSooiOzamgE/W2G7gZMkCoT2NQbD7zSNB+S
toUONsMQ8t6Awv9osq1WWoK/xZkHV8wMGDOun9Ia8vO+hOU5wMOnhvg5mbE1xbst7pK2P9HgFxY2
/5o3VcBn4M6T5omuaz6GVsQ4VssAWfnqVpholf+EQahap+3Fpue24kwL3/pWnDkp0UcvjfItSy9c
UZdf/XOjI7X4DzroB3PFZ+rJSoRUjF2mKCLbHO0TLXtpEpr8ngGu8WwEAwf7eGHI6O5LCxrLYRdw
jqaGMxZnxTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDH+zIUfuljJU/XAGeDAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgKNY4Cih1tsjpYs99++hrgzmeYozyyV20
LjQ6J8h8Q1YwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjIz
MDY1OTAyWjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBACGwyM+BmWxJ7FR6R8JGcNZiWA38lmJrr084f/DADBV3x7qDkjr3
+cbTpWB+TO9cNenLmw3IKd9Rj66ELei34DGcP5Ns1LcPWaiSo8dZQnKNbfmcD0noAL8nvYEJi9fv
05i1venThWNqJObJ81OZ6QWoAM6/ygGlpdFd/w4d059M68Ac77C2J5VUpn6ZgM1ex3gbH8AO2iXx
3PhkVWaRfD8mjNamtwdIsbABeTUxtD8f6EQQFrp56SkbJOM0Diy9gaXqZFPF7HxoKInm0LVjISv3
JfIvRzTPAYT7+LQ2OEjOWNDEteOJnM090gC4G2Nkl0qMbiRUSTpOq6no8CgaSSc=
--94eb2c07dd3eecd77605492d25b8--


From nobody Wed Feb 22 23:21:06 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F98A129577; Wed, 22 Feb 2017 23:21:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.618
X-Spam-Level: 
X-Spam-Status: No, score=-1.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 6HSLQYjwHEnF; Wed, 22 Feb 2017 23:21:04 -0800 (PST)
Received: from relais-inet.orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A5A7129421; Wed, 22 Feb 2017 23:21:04 -0800 (PST)
Received: from opfednr02.francetelecom.fr (unknown [xx.xx.xx.66]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 7BDA320765; Thu, 23 Feb 2017 08:21:02 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.2]) by opfednr02.francetelecom.fr (ESMTP service) with ESMTP id 429BA120079; Thu, 23 Feb 2017 08:21:02 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM21.corporate.adroot.infra.ftgroup ([fe80::e92a:c932:907e:8f06%19]) with mapi id 14.03.0319.002; Thu, 23 Feb 2017 08:21:02 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSjVhXjEUdWUfi/UqmqMjEy8b9xqF2Lclg
Date: Thu, 23 Feb 2017 07:21:01 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com>
In-Reply-To: <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933009E16627OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EzXFiaVCD9pX9rxVFQlttHoMXMA>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 07:21:05 -0000

--_000_787AE7BB302AE849A7480A190F8B933009E16627OPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpUaGFuayB5b3UgZm9yIHRoZSByZXBseSBhbmQgZm9yIGltcGxlbWVudGluZyB0
aGVzZSBjaGFuZ2VzLg0KDQpJIGNoZWNrZWQgdGhlIGRpZmYsIGJ1dCBJ4oCZbSBhZnJhaWQgdGhl
IC0wNiB2ZXJzaW9uIGhhcyB0aGUgc2FtZSBpc3N1ZXMgYXMgdGhlIG9uZXMgSSByZXBvcnRlZCBp
biBKYW51YXJ5IDMxLg0KDQpJ4oCZbSByZWl0ZXJhdGluZyB0aGF0IG1vc3Qgb2YgbXkgY29tbWVu
dHMgYXJlIHN0aWxsIHVuYWRkcmVzc2VkIGluIC0wNi4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDog
VGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCkVudm95w6kgOiBtZXJjcmVk
aSAyMiBmw6l2cmllciAyMDE3IDIzOjA5DQrDgCA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE4N
CkNjIDogaWV0ZkBpZXRmLm9yZzsgZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0
aW9uQGlldGYub3JnDQpPYmpldCA6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1oYXJkaWUtcHJpdnNl
Yy1tZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0PiAoRGVzaWduIGNvbnNpZGVyYXRpb25zIGZvciBN
ZXRhZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkhpIE1vaGFtZWQsDQpU
aGFua3MgZm9yIHlvdXIgcmV2aWV3LiAgSSd2ZSB1cGxvYWRlZCBhIGRyYWZ0IC0wNiB3aXRoIHVw
ZGF0ZXMgZnJvbSB5b3VyIGFuZCBvdGhlciByZXZpZXdzLiAgU29tZSBub3RlcyBpbi1saW5lLg0K
DQpPbiBUdWUsIEphbiAzMSwgMjAxNyBhdCAxOjQ5IEFNLCA8bW9oYW1lZC5ib3VjYWRhaXJAb3Jh
bmdlLmNvbTxtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4+IHdyb3RlOg0KRGVh
ciBUZWQsDQoNClBsZWFzZSBmaW5kIGJlbG93IG15IGdlbmVyYWwgcmV2aWV3IG9mIHRoZSBkb2N1
bWVudCBhbmQgYWxzbyBteSBkZXRhaWxlZCBjb21tZW50cy4NCg0KKiBPdmVyYWxsOg0KLSBJIGRv
bid0IHRoaW5rIHRoZSBkb2N1bWVudCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgaXQgaXMu
IEl0IGRvZXMgbm90IGRpc2N1c3MgdGhlIHVzYWJpbGl0eSBhbmQgaW1wbGljYXRpb25zIG9mIHRo
ZSBhZHZpY2UuIEZ1cnRoZXIsIGl0IG1heSBiZSBpbnRlcnByZXRlZCB0aGF0IGEgY2xpZW50L2Vu
ZCBzeXN0ZW0vdXNlciBjYW4gYWx3YXlzIGJ5IGl0c2VsZiBwb3B1bGF0ZSBkYXRhIHRoYXQgaXMg
c3VwcGxpZWQgYnkgb24tcGF0aCBub2RlcyAoaW4gY3VycmVudCBkZXBsb3ltZW50cykuIFRoYXQn
cyBhc3N1bXB0aW9uIGlzIG5vdCB0cnVlIGZvciBzb21lIHByb3RvY29scy4NCi0gVGhlIHB1cnBv
c2Ugb2YgcHVibGlzaGluZyB0aGlzIGFkdmljZSBpcyBub3QgY2xlYXIuIEZvciBleGFtcGxlLCBo
b3cgdGhpcyBhZHZpY2Ugd2lsbCBiZSBpbXBsZW1lbnRlZCBpbiBwcmFjdGljZT8gV2hhdCBpcyBp
dHMgc2NvcGU/DQotIEkgd291bGQgcGVyc29uYWxseSBwcmVmZXIgYW4gdXBkYXRlZCB2ZXJzaW9u
IG9mIFJGQzcyNTggd2l0aCBtb3JlIHN0cmljdCBsYW5ndWFnZSBvbiB0aGUgcHJpdmFjeS1yZWxh
dGVkIGNvbnNpZGVyYXRpb25zLiBUaGlzIGlzIG1vcmUgYWN0aW9uYWJsZSB3aXRoIGNvbmNyZXRl
IGVmZmVjdHMgaW4gZG9jdW1lbnRzIHRoYXQgd2lsbCByZXF1aXJlZCB0byBpbmNsdWRlIGEgZGlz
Y3Vzc2lvbiBvbiBwcml2YWN5IHJlbGF0ZWQgbWF0dGVycy4NCg0KRGV0YWlsZWQgY29tbWVudHMg
YXJlIHByb3ZpZGVkIGJlbG93Og0KDQoqIFRoZSBhYnN0cmFjdCBzYXlzIHRoZSBmb2xsb3dpbmc6
DQoNCiAgIFRoZSBJQUIgaGFzIHB1Ymxpc2hlZCBbUkZDNzYyNF0gaW4gcmVzcG9uc2UgdG8gc2V2
ZXJhbCByZXZlbGF0aW9ucyBvZg0KICAgcGVydmFzaXZlIGF0dGFjayBvbiBJbnRlcm5ldCBjb21t
dW5pY2F0aW9ucy4gIFRoaXMgZG9jdW1lbnQgY29uc2lkZXJzDQogICB0aGUgaW1wbGljYXRpb25z
IG9mIHByb3RvY29sIGRlc2lnbnMgd2hpY2ggYXNzb2NpYXRlIG1ldGFkYXRhIHdpdGgNCiAgIGVu
Y3J5cHRlZCBmbG93cy4gIEluIHBhcnRpY3VsYXIsIGl0IGFzc2VydHMgdGhhdCBkZXNpZ25zIHdo
aWNoIGRvIHNvDQogICBieSBleHBsaWNpdCBhY3Rpb25zIG9mIHRoZSBlbmQgc3lzdGVtIGFyZSBw
cmVmZXJhYmxlIHRvIGRlc2lnbnMgaW4NCiAgICAgIF5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl4NCiAgIHdoaWNoIG1pZGRsZWJveGVzIGluc2VydCB0aGVtLg0KDQpJIHN1Z2dlc3Qg
eW91IGV4cGxpY2l0IHdoYXQgaXMgbWVhbnQgYnkgInRoZSBlbmQgc3lzdGVtIi4NCg0KSSBoYXZl
IHVwZGF0ZWQgdGhpcyB0byBjbGFyaWZ5IHRoYXQgdGhpcyBpcyB0aGUgaG9zdC9lbmQgc3lzdGVt
IG5vdCB0aGUgdXNlci4NCg0KSWYgeW91IG1lYW4gdGhlIG93bmVyL3VzZXIsIHRoZW4gdGhlIHRl
eHQgc2hvdWxkIHNheSBzby4gSWYgeW91IG1lYW4gYSBjbGllbnQgc29mdHdhcmUgaW5zdGFuY2Us
IHRoZW4gYnVncy9pbmFwcHJvcHJpYXRlIGRlZmF1bHQgdmFsdWVzIG1heSBsZWFkIHRvIChwcml2
YWN5IGxlYWspIHN1cnByaXNlcyB0b28uIEl0IHdhcyByZXBvcnRlZCBpbiB0aGUgcGFzdCB0aGF0
IHNvbWUgYnJvd3NlcnMgaW5qZWN0IHRoZSBNU0lTRE4gdG9vLg0KDQoqIEludHJvZHVjdGlvbjog
IlRvIGVuc3VyZSB0aGF0IHRoZSBJbnRlcm5ldCBjYW4gYmUgdHJ1c3RlZCBieSB1c2VycyINCg0K
UmF0aGVyIMKrIFRvIG1pbmltaXplIHRoZSByaXNrIG9mIEludGVybmV0LW9yaWdpbmF0ZWQgYXR0
YWNrcyB0YXJnZXRlZCBhdCB1c2VycyDCuy4NCg0KSSd2ZSBhZG9wdGVkIHRoaXMgbGFuZ3VhZ2Uu
DQoNCkl0J3MgcmVhc29uYWJsZSB0byBjbGFpbSB0aGUgSW50ZXJuZXQgY2FuIGJlIHRydXN0ZWQg
YnkgdXNlcnM7IHNlZSBob3cgdGhlIHVzYWdlIG9mIHNvY2lhbCBuZXR3b3JrcyBoYXMgYmVjb21l
IHNldmVyZWx5IHR3aXN0ZWQgZm9yIGV4YW1wbGUNCg0KSSd2ZSBhbHNvIGNvbnNpZGVyZWQgeW91
ciBwb2ludCB0aGF0IGFuIHVwZGF0ZWQgdmVyc2lvbiBvZiBSRkM3MjU4IG1pZ2h0IGJlIGEgYmV0
dGVyIG91dGxldCBmb3IgYWR2aWNlIGxpa2UgdGhpcy4gV2UgZGlkIGNvbnNpZGVyIHNldmVyYWwg
YXBwcm9hY2hlcywgaW5jbHVkaW5nIGluY29ycG9yYXRpbmcgdGhlIHRleHQgaW4gYW4gdXBkYXRl
IHRvICBSRkMgMzU1MiBvciBhcyBwYXJ0IG9mIGEgZG9jdW1lbnQgZGVzY3JpYmluZyB0aGUgZnVs
bCBzZXQgb2YgY29tcGFuaW9uIG1pdGlnYXRpb25zIHRvIHRoZSB0aHJlYXRzIGluIFJGQyA3NjI0
IChkcmFmdC1pYWItcHJpdnNlYy1jb25maWRlbnRpYWxpdHktbWl0aWdhdGlvbnMgd291bGQgYmUg
b25lIGFwcHJvYWNoKS4gIFRob3NlIGFyZSBhbGwgdmFsaWQgYXBwcm9hY2hlcywgYnV0IGl0IHNl
ZW1lZCB0aGF0IHNob3J0LCBlYXNpbHkgcmVhZCBkb2N1bWVudHMgdGFja2xpbmcgYSBzaW5nbGUg
cG9pbnQgbWlnaHQgYmUgZWFzaWVyIHRvIHByb2R1Y2UgYW5kIGNvbnN1bWUuDQpUaGFua3MgYWdh
aW4gZm9yIHlvdXIgcmV2aWV3LA0KVGVkIEhhcmRpZQ0KDQo=

--_000_787AE7BB302AE849A7480A190F8B933009E16627OPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5nbWFpbC0NCgl7bXNvLXN0eWxl
LW5hbWU6Z21haWwtO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNv
bmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7DQoJ
Zm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsO30NCi5Nc29DaHBEZWZhdWx0
DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwi
c2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNl
Y3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1cHQg
NzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRlIiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SGkgVGVkLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGFuayB5b3UgZm9yIHRoZSByZXBseSBh
bmQgZm9yIGltcGxlbWVudGluZyB0aGVzZSBjaGFuZ2VzLg0KPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkkgY2hlY2tlZCB0aGUgZGlmZiwgYnV0IEni
gJltIGFmcmFpZCB0aGUgLTA2IHZlcnNpb24gaGFzIHRoZSBzYW1lIGlzc3VlcyBhcyB0aGUgb25l
cyBJIHJlcG9ydGVkIGluIEphbnVhcnkgMzEuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPknigJltIHJlaXRlcmF0aW5nIHRoYXQgbW9zdCBvZiBteSBj
b21tZW50cyBhcmUgc3RpbGwgdW5hZGRyZXNzZWQgaW4gLTA2LjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5DaGVlcnMsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJs
YWNrIj5NZWQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7
cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAw
Y20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7Ij5EZSZuYnNwOzo8L3NwYW4+PC9iPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7
c2Fucy1zZXJpZiZxdW90OyI+IFRlZCBIYXJkaWUgW21haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jbzwv
c3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhv
bWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+bV0NCjxicj4NCjxiPkVudm95w6kmbmJz
cDs6PC9iPiBtZXJjcmVkaSAyMiBmw6l2cmllciAyMDE3IDIzOjA5PGJyPg0KPGI+w4AmbmJzcDs6
PC9iPiBCT1VDQURBSVIgTW9oYW1lZCBJTVQvT0xOPGJyPg0KPGI+Q2MmbmJzcDs6PC9iPiBpZXRm
QGlldGYub3JnOyBkcmFmdC1oYXJkaWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb25AaWV0Zi5v
cmc8YnI+DQo8Yj5PYmpldCZuYnNwOzo8L2I+IFJlOiBMYXN0IENhbGw6ICZsdDtkcmFmdC1oYXJk
aWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0Jmd0OyAoRGVzaWduIGNvbnNpZGVy
YXRpb25zIGZvciBNZXRhZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkhpIE1vaGFtZWQsPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgeW91ciByZXZpZXcuJm5ic3A7
IEkndmUgdXBsb2FkZWQgYSBkcmFmdCAtMDYgd2l0aCB1cGRhdGVzIGZyb20geW91ciBhbmQgb3Ro
ZXIgcmV2aWV3cy4mbmJzcDsgU29tZSBub3RlcyBpbi1saW5lLjxvOnA+PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPk9uIFR1ZSwgSmFuIDMxLCAyMDE3IGF0IDE6NDkgQU0sICZsdDs8
YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbSIgdGFyZ2V0PSJfYmxh
bmsiPm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5nZS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlYXIgVGVkLDxicj4NCjxicj4NClBsZWFzZSBm
aW5kIGJlbG93IG15IGdlbmVyYWwgcmV2aWV3IG9mIHRoZSBkb2N1bWVudCBhbmQgYWxzbyBteSBk
ZXRhaWxlZCBjb21tZW50cy48YnI+DQo8YnI+DQoqIE92ZXJhbGw6PGJyPg0KLSBJIGRvbid0IHRo
aW5rIHRoZSBkb2N1bWVudCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQgYXMgaXQgaXMuIEl0IGRv
ZXMgbm90IGRpc2N1c3MgdGhlIHVzYWJpbGl0eSBhbmQgaW1wbGljYXRpb25zIG9mIHRoZSBhZHZp
Y2UuIEZ1cnRoZXIsIGl0IG1heSBiZSBpbnRlcnByZXRlZCB0aGF0IGEgY2xpZW50L2VuZCBzeXN0
ZW0vdXNlciBjYW4gYWx3YXlzIGJ5IGl0c2VsZiBwb3B1bGF0ZSBkYXRhIHRoYXQgaXMgc3VwcGxp
ZWQgYnkgb24tcGF0aCBub2Rlcw0KIChpbiBjdXJyZW50IGRlcGxveW1lbnRzKS4gVGhhdCdzIGFz
c3VtcHRpb24gaXMgbm90IHRydWUgZm9yIHNvbWUgcHJvdG9jb2xzLjxicj4NCi0gVGhlIHB1cnBv
c2Ugb2YgcHVibGlzaGluZyB0aGlzIGFkdmljZSBpcyBub3QgY2xlYXIuIEZvciBleGFtcGxlLCBo
b3cgdGhpcyBhZHZpY2Ugd2lsbCBiZSBpbXBsZW1lbnRlZCBpbiBwcmFjdGljZT8gV2hhdCBpcyBp
dHMgc2NvcGU/PGJyPg0KLSBJIHdvdWxkIHBlcnNvbmFsbHkgcHJlZmVyIGFuIHVwZGF0ZWQgdmVy
c2lvbiBvZiBSRkM3MjU4IHdpdGggbW9yZSBzdHJpY3QgbGFuZ3VhZ2Ugb24gdGhlIHByaXZhY3kt
cmVsYXRlZCBjb25zaWRlcmF0aW9ucy4gVGhpcyBpcyBtb3JlIGFjdGlvbmFibGUgd2l0aCBjb25j
cmV0ZSBlZmZlY3RzIGluIGRvY3VtZW50cyB0aGF0IHdpbGwgcmVxdWlyZWQgdG8gaW5jbHVkZSBh
IGRpc2N1c3Npb24gb24gcHJpdmFjeSByZWxhdGVkIG1hdHRlcnMuPGJyPg0KPGJyPg0KRGV0YWls
ZWQgY29tbWVudHMgYXJlIHByb3ZpZGVkIGJlbG93Ojxicj4NCjxicj4NCiogVGhlIGFic3RyYWN0
IHNheXMgdGhlIGZvbGxvd2luZzo8YnI+DQo8YnI+DQo8c3BhbiBjbGFzcz0iZ21haWwtIj4mbmJz
cDsgJm5ic3A7VGhlIElBQiBoYXMgcHVibGlzaGVkIFtSRkM3NjI0XSBpbiByZXNwb25zZSB0byBz
ZXZlcmFsIHJldmVsYXRpb25zIG9mPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJnbWFpbC0iPiZu
YnNwOyAmbmJzcDtwZXJ2YXNpdmUgYXR0YWNrIG9uIEludGVybmV0IGNvbW11bmljYXRpb25zLiZu
YnNwOyBUaGlzIGRvY3VtZW50IGNvbnNpZGVyczwvc3Bhbj48YnI+DQo8c3BhbiBjbGFzcz0iZ21h
aWwtIj4mbmJzcDsgJm5ic3A7dGhlIGltcGxpY2F0aW9ucyBvZiBwcm90b2NvbCBkZXNpZ25zIHdo
aWNoIGFzc29jaWF0ZSBtZXRhZGF0YSB3aXRoPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNzPSJnbWFp
bC0iPiZuYnNwOyAmbmJzcDtlbmNyeXB0ZWQgZmxvd3MuJm5ic3A7IEluIHBhcnRpY3VsYXIsIGl0
IGFzc2VydHMgdGhhdCBkZXNpZ25zIHdoaWNoIGRvIHNvPC9zcGFuPjxicj4NCjxzcGFuIGNsYXNz
PSJnbWFpbC0iPiZuYnNwOyAmbmJzcDtieSBleHBsaWNpdCBhY3Rpb25zIG9mIHRoZSBlbmQgc3lz
dGVtIGFyZSBwcmVmZXJhYmxlIHRvIGRlc2lnbnMgaW48L3NwYW4+PGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5eXjxicj4NCiZuYnNwOyAm
bmJzcDt3aGljaCBtaWRkbGVib3hlcyBpbnNlcnQgdGhlbS48YnI+DQo8YnI+DQpJIHN1Z2dlc3Qg
eW91IGV4cGxpY2l0IHdoYXQgaXMgbWVhbnQgYnkgJnF1b3Q7dGhlIGVuZCBzeXN0ZW0mcXVvdDsu
IDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBoYXZlIHVw
ZGF0ZWQgdGhpcyB0byBjbGFyaWZ5IHRoYXQgdGhpcyBpcyB0aGUgaG9zdC9lbmQgc3lzdGVtIG5v
dCB0aGUgdXNlci4mbmJzcDsNCjxicj4NCiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAx
LjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1y
aWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgeW91IG1lYW4gdGhlIG93bmVyL3Vz
ZXIsIHRoZW4gdGhlIHRleHQgc2hvdWxkIHNheSBzby4gSWYgeW91IG1lYW4gYSBjbGllbnQgc29m
dHdhcmUgaW5zdGFuY2UsIHRoZW4gYnVncy9pbmFwcHJvcHJpYXRlIGRlZmF1bHQgdmFsdWVzIG1h
eSBsZWFkIHRvIChwcml2YWN5IGxlYWspIHN1cnByaXNlcyB0b28uIEl0IHdhcyByZXBvcnRlZCBp
biB0aGUgcGFzdCB0aGF0IHNvbWUgYnJvd3NlcnMgaW5qZWN0IHRoZQ0KIE1TSVNETiB0b28uPGJy
Pg0KPGJyPg0KKiBJbnRyb2R1Y3Rpb246ICZxdW90O1RvIGVuc3VyZSB0aGF0IHRoZSBJbnRlcm5l
dCBjYW4gYmUgdHJ1c3RlZCBieSB1c2VycyZxdW90Ozxicj4NCjxicj4NClJhdGhlciDCqyBUbyBt
aW5pbWl6ZSB0aGUgcmlzayBvZiBJbnRlcm5ldC1vcmlnaW5hdGVkIGF0dGFja3MgdGFyZ2V0ZWQg
YXQgdXNlcnMgwrsuDQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkkndmUgYWRvcHRlZCB0aGlzIGxhbmd1YWdlLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JdCdzIHJl
YXNvbmFibGUgdG8gY2xhaW0gdGhlIEludGVybmV0IGNhbiBiZSB0cnVzdGVkIGJ5IHVzZXJzOyBz
ZWUgaG93IHRoZSB1c2FnZSBvZiBzb2NpYWwgbmV0d29ya3MgaGFzIGJlY29tZSBzZXZlcmVseSB0
d2lzdGVkIGZvciBleGFtcGxlPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5JJ3Zl
IGFsc28gY29uc2lkZXJlZCB5b3VyIHBvaW50IHRoYXQgYW4gdXBkYXRlZCB2ZXJzaW9uIG9mIFJG
QzcyNTggbWlnaHQgYmUgYSBiZXR0ZXIgb3V0bGV0IGZvciBhZHZpY2UgbGlrZSB0aGlzLiBXZSBk
aWQgY29uc2lkZXIgc2V2ZXJhbCBhcHByb2FjaGVzLCBpbmNsdWRpbmcgaW5jb3Jwb3JhdGluZyB0
aGUgdGV4dCBpbiBhbiB1cGRhdGUgdG8mbmJzcDsgUkZDIDM1NTINCiBvciBhcyBwYXJ0IG9mIGEg
ZG9jdW1lbnQgZGVzY3JpYmluZyB0aGUgZnVsbCBzZXQgb2YgY29tcGFuaW9uIG1pdGlnYXRpb25z
IHRvIHRoZSB0aHJlYXRzIGluIFJGQyA3NjI0IChkcmFmdC1pYWItcHJpdnNlYy1jb25maWRlbnRp
YWxpdHktbWl0aWdhdGlvbnMgd291bGQgYmUgb25lIGFwcHJvYWNoKS4mbmJzcDsgVGhvc2UgYXJl
IGFsbCB2YWxpZCBhcHByb2FjaGVzLCBidXQgaXQgc2VlbWVkIHRoYXQgc2hvcnQsIGVhc2lseSBy
ZWFkIGRvY3VtZW50cyB0YWNrbGluZw0KIGEgc2luZ2xlIHBvaW50IG1pZ2h0IGJlIGVhc2llciB0
byBwcm9kdWNlIGFuZCBjb25zdW1lLiZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+VGhh
bmtzIGFnYWluIGZvciB5b3VyIHJldmlldyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRlZCBIYXJkaWU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_787AE7BB302AE849A7480A190F8B933009E16627OPEXCLILMA3corp_--


From nobody Wed Feb 22 23:35:16 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D537C12963D; Wed, 22 Feb 2017 23:35: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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 QGa0lWSwloW1; Wed, 22 Feb 2017 23:35:13 -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 B10FD129639; Wed, 22 Feb 2017 23:35:12 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 82ECC828A5; Thu, 23 Feb 2017 08:35:07 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com> <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com>
Date: Thu, 23 Feb 2017 04:33:50 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i7WtX7lPU7ifIcVAO68B79Em-jY>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 07:35:15 -0000

On 02/23/2017 03:24 AM, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 1:25 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
>     > (I do also happen to think that it would be better if we waited a decade
>     > before changing this, because we're only 5 or so years into large-scale
>     > deployment that will hopefully last at least 3 or 4 decades. However, I
>     > don't expect many people to agree with me on that, so I'm not trying to
>     > make that argument here.)
> 
>     Isn't that actually an argument for waiting before moving rfc4291bis to
>     full standard?
> 
>     If you'd wait to change it, why would you want to cast this into stone
>     now? So that, later you can argue that "it's a full standard document...
>     so we shouldn't change it"?
> 
> 
> I don't see why that argument would carry any weight. Full standards can
> be changed and updated, too.
> 
> What I most care about is that if we make fundamental changes like this,
> then it's not done as part of a reclassification, and the working group
> has its say.
> 
> Whether the document says "full standard" or "draft standard" is not as
> important as whether it says the right thing.

Exactly. And if a document does not reflect operational reality, it has
a big problem.

My understanding is that Randy et al are trying to get rfc4291bis to
reflect operational reality, but you want to progress the document with
no changes, essentially meaning that you want to publish a document as
full standard which doesn't agree with how the protocol is being deployed.

If, even at the time of publication our documents already do not reflect
reality, we are not going to be taken seriously.

If you're argument is that we cannot do what is right because moving
rfc4291 to full standard doesn't allow it, then you're implicitly asking
not to move rfc4291bis to full standard (or are just aasking us to do
the wrong thing).

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 22 23:49:33 2017
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3C9B129B00 for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 23:49:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QfkK2ehe_MRW for <ietf@ietfa.amsl.com>; Wed, 22 Feb 2017 23:49:24 -0800 (PST)
Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002: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 532FD129AE6 for <ietf@ietf.org>; Wed, 22 Feb 2017 23:49:24 -0800 (PST)
Received: by mail-yw0-x22b.google.com with SMTP id p77so13094494ywg.1 for <ietf@ietf.org>; Wed, 22 Feb 2017 23:49:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=6c+Zbol68rBiY8wEMEWKI8aHcS5qt2QZsm2uRYZeEKQ=; b=FYMwr+DahoSgISKwnQZz529NSYmFhJALjrjPXerBkKGpquNWTynPGRBRYCl0EkSeWU s+BBoUjofRF8lbk+dwTibGvAjZalCu+vJUOPve8itgqw5sN7w77S5fsYBpXLK5nVNrZZ kWOKRp1kDuUHDXLews63AcKkC+Lvi5EYdRUoDd3J2QsaWLxj9dAoT4/z10jRrndsm5/O HMIOQRHScJ6tLeiIYUrON2zuZXq8hOQXUYErtbOyUIVCHA2kp7SR8lIxyQWO4D+1PJEn o3sV1ouxIb03ezKr7jXJa+j8bezRwySLn+aJOykLt0xDo9scG4mIqsnvvTRH6A7HrGDT VnMA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=6c+Zbol68rBiY8wEMEWKI8aHcS5qt2QZsm2uRYZeEKQ=; b=nQDn+fZoqG1YWGh68CoGqnYs6s9EP9MEiRb0R//ESdjpLjsZ5l+NELkq2z1la7sXmA lfHe4mBlSxxkKG0Lwrslz+zCal5TFlJ76knZ5nvzkxTN/0SysbyJ/LFntEp11s1iomQQ gP1hIHDEfeSTsV6k2Rbp4kO5pYluQOZ54MYWr5ND+XZNULFcwWy20QQ3kOANPCI35siZ D9xAEZcOGTJAy7KV2AOKah5Wy1uY1YruEKHPb/1lSCi+j5vqey7vv/6Za/DsOFrrpffp WpO2fQyxQcDM1MivWphsTHzNiAzi0Wv+24UvdHIgFWxBVrVg1zEjW41umJFIg5i3w0hu qB+g==
X-Gm-Message-State: AMke39kRU/z9vY6G+9gCZ066d/ug6SHhhcPekfGogc/Ki8GRfMmtqFVBHNAPDWIfJBFy58uQgd35MD7siF1bZULF
X-Received: by 10.129.129.3 with SMTP id r3mr27268234ywf.0.1487836163247; Wed, 22 Feb 2017 23:49:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.207.4 with HTTP; Wed, 22 Feb 2017 23:49:02 -0800 (PST)
In-Reply-To: <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com> <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com>
From: Erik Kline <ek@google.com>
Date: Thu, 23 Feb 2017 16:49:02 +0900
Message-ID: <CAAedzxpQ9hoQF4s1CH-3VbsSibOeuocaPsrk0_iZE=1ji9+jUQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="94eb2c07dd3e057ac305492ddaeb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w8w55x90ZhwDpdaoIkUSlh0Ir7M>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 07:49:29 -0000

--94eb2c07dd3e057ac305492ddaeb
Content-Type: multipart/alternative; boundary=94eb2c07dd3efed72c05492dd920

--94eb2c07dd3efed72c05492dd920
Content-Type: text/plain; charset=UTF-8

On 23 February 2017 at 16:33, Fernando Gont <fgont@si6networks.com> wrote:

> On 02/23/2017 03:24 AM, Lorenzo Colitti wrote:
> > On Thu, Feb 23, 2017 at 1:25 PM, Fernando Gont <fgont@si6networks.com
> > <mailto:fgont@si6networks.com>> wrote:
> >
> >     > (I do also happen to think that it would be better if we waited a
> decade
> >     > before changing this, because we're only 5 or so years into
> large-scale
> >     > deployment that will hopefully last at least 3 or 4 decades.
> However, I
> >     > don't expect many people to agree with me on that, so I'm not
> trying to
> >     > make that argument here.)
> >
> >     Isn't that actually an argument for waiting before moving rfc4291bis
> to
> >     full standard?
> >
> >     If you'd wait to change it, why would you want to cast this into
> stone
> >     now? So that, later you can argue that "it's a full standard
> document...
> >     so we shouldn't change it"?
> >
> >
> > I don't see why that argument would carry any weight. Full standards can
> > be changed and updated, too.
> >
> > What I most care about is that if we make fundamental changes like this,
> > then it's not done as part of a reclassification, and the working group
> > has its say.
> >
> > Whether the document says "full standard" or "draft standard" is not as
> > important as whether it says the right thing.
>
> Exactly. And if a document does not reflect operational reality, it has
> a big problem.
>
> My understanding is that Randy et al are trying to get rfc4291bis to
> reflect operational reality, but you want to progress the document with
> no changes, essentially meaning that you want to publish a document as
> full standard which doesn't agree with how the protocol is being deployed.
>
> If, even at the time of publication our documents already do not reflect
> reality, we are not going to be taken seriously.
>
> If you're argument is that we cannot do what is right because moving
> rfc4291 to full standard doesn't allow it, then you're implicitly asking
> not to move rfc4291bis to full standard (or are just aasking us to do
> the wrong thing).
>

Actually, I was saying that I don't see that there's a real problem with
the current text.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 23 February 2017 at 16:33, Fernando Gont <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 02/23/201=
7 03:24 AM, Lorenzo Colitti wrote:<br>
&gt; On Thu, Feb 23, 2017 at 1:25 PM, Fernando Gont &lt;<a href=3D"mailto:f=
gont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a><br>
</span><span>&gt; &lt;mailto:<a href=3D"mailto:fgont@si6networks.com" targe=
t=3D"_blank">fgont@si6networks.com</a>&gt;<wbr>&gt; wrote:<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; (I do also happen to think that it would be be=
tter if we waited a decade<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; before changing this, because we&#39;re only 5=
 or so years into large-scale<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; deployment that will hopefully last at least 3=
 or 4 decades. However, I<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; don&#39;t expect many people to agree with me =
on that, so I&#39;m not trying to<br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; make that argument here.)<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0Isn&#39;t that actually an argument for waiting bef=
ore moving rfc4291bis to<br>
&gt;=C2=A0 =C2=A0 =C2=A0full standard?<br>
&gt;<br>
&gt;=C2=A0 =C2=A0 =C2=A0If you&#39;d wait to change it, why would you want =
to cast this into stone<br>
&gt;=C2=A0 =C2=A0 =C2=A0now? So that, later you can argue that &quot;it&#39=
;s a full standard document...<br>
&gt;=C2=A0 =C2=A0 =C2=A0so we shouldn&#39;t change it&quot;?<br>
&gt;<br>
&gt;<br>
&gt; I don&#39;t see why that argument would carry any weight. Full standar=
ds can<br>
&gt; be changed and updated, too.<br>
&gt;<br>
&gt; What I most care about is that if we make fundamental changes like thi=
s,<br>
&gt; then it&#39;s not done as part of a reclassification, and the working =
group<br>
&gt; has its say.<br>
&gt;<br>
&gt; Whether the document says &quot;full standard&quot; or &quot;draft sta=
ndard&quot; is not as<br>
&gt; important as whether it says the right thing.<br>
<br>
</span>Exactly. And if a document does not reflect operational reality, it =
has<br>
a big problem.<br>
<br>
My understanding is that Randy et al are trying to get rfc4291bis to<br>
reflect operational reality, but you want to progress the document with<br>
no changes, essentially meaning that you want to publish a document as<br>
full standard which doesn&#39;t agree with how the protocol is being deploy=
ed.<br>
<br>
If, even at the time of publication our documents already do not reflect<br=
>
reality, we are not going to be taken seriously.<br>
<br>
If you&#39;re argument is that we cannot do what is right because moving<br=
>
rfc4291 to full standard doesn&#39;t allow it, then you&#39;re implicitly a=
sking<br>
not to move rfc4291bis to full standard (or are just aasking us to do<br>
the wrong thing).<br></blockquote><div><br></div><div>Actually, I was sayin=
g that I don&#39;t see that there&#39;s a real problem with the current tex=
t.<br></div></div></div></div>

--94eb2c07dd3efed72c05492dd920--

--94eb2c07dd3e057ac305492ddaeb
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMf7MhR+6WMlT9cAZ4MA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTEyMjA2MzcwNloXDTE3MDUy
MTA2MzcwNlowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMFGbCvV+u+in+H0HY3bqCemHVO+gk8MSoSt5cw8MyfvalJUBE+K8i0L
KO7g5Tf0Hwxwin3Y78Fjurdr5ScXC3q2XKlu/KeOcKZ629BIHXR3Bc4P1kbeSBqtdP1hQsXutC3N
LKA6HYfEAKX5La7jHPIPymFuzHi9jqRt1XPLBhUIx/BUgV2RaLkaLlKi1gilVaUzZ/bwKGEBPXd7
oqEa0bmYHg7nnH3c07Ka5FqwYFbFNH2B8N9qhsEvaidSWAYFR3c83MxaNvd0cc9VR+xkg4h9t4j8
kgMqch9g5WsqvEiB8X9avk0RfRrJXnLpGVE9SgWC+9g/4qHF7INLnWGpoGsCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBRSp79TZtpx4DfF6E+LlflJ0/FBvzAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAYNw4ea3dhqz3+6k7eFLEAto3ynoX
iT5jeLl+/a9UeVSG5MQjruVO3LeqKKs3757hNcyfMZSooiOzamgE/W2G7gZMkCoT2NQbD7zSNB+S
toUONsMQ8t6Awv9osq1WWoK/xZkHV8wMGDOun9Ia8vO+hOU5wMOnhvg5mbE1xbst7pK2P9HgFxY2
/5o3VcBn4M6T5omuaz6GVsQ4VssAWfnqVpholf+EQahap+3Fpue24kwL3/pWnDkp0UcvjfItSy9c
UZdf/XOjI7X4DzroB3PFZ+rJSoRUjF2mKCLbHO0TLXtpEpr8ngGu8WwEAwf7eGHI6O5LCxrLYRdw
jqaGMxZnxTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDH+zIUfuljJU/XAGeDAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgXysU/Eof8C5XECHyyv1DbRggpwECVqsC
SUKITXrZgHowGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjIz
MDc0OTIzWjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBAGMWXyFldaOWsvaWot+4L/JU8pylDtj3P5TBuPyAThfDbE8QzMr8
hA3i1PcXMBcNxek91YOt2CcwqGEx+COFMm0dFnucxV784ZK+LJ03NMIRlhnTi3loMYqID4SUAuEb
kGQwuzOpibBHA1kcDYwE03J2uLDjYuKXae/43UIYBIOhppExsXli2HxD2TIfIJKlez6cY9qxJi/o
Z9OhfBLO6kNp+e43rNTqN0rpnZbsLx6K3LdR/Sqfn/lhkPOnQU8YSK7xvJaB8hM2r196Z1Re139d
ArOqu9S+0uxVQKRcl7cW4dTz2PNP33X+EMj+sVoGs8moUdXxsFBW7SFZg4gNIDE=
--94eb2c07dd3e057ac305492ddaeb--


From nobody Thu Feb 23 00:13:00 2017
Return-Path: <sthaug@nethelp.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C60312A130; Thu, 23 Feb 2017 00:12:58 -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 autolearn_force=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 dXqJ83-t5Uch; Thu, 23 Feb 2017 00:12:56 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B2712A12D; Thu, 23 Feb 2017 00:12:56 -0800 (PST)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 37B6EE6065; Thu, 23 Feb 2017 09:12:54 +0100 (CET)
Date: Thu, 23 Feb 2017 09:12:54 +0100 (CET)
Message-Id: <20170223.091254.74715533.sthaug@nethelp.no>
To: lorenzo@google.com
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: sthaug@nethelp.no
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
References: <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CouCxcANW0gepnWJGiHdOL8Fzz8>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:12:58 -0000

> > I'm sorry, I'm wondering which word in my recent message that said
> > "I'm not aware of any generally available running code that will
> > be changed in even one instruction by the final text - that is indeed
> > a requirement for advancement to Internet Standard."
> > is hard to understand.
> 
> Help he understand, then. There is widely-deployed code that assumes that
> the interface ID is 64 and does not work on anything other than 64 bit
> prefix lengths. Currently that code is correct on all unicast space. If you
> change RFC 4291, won't that code be incorrect?

Since there are plenty of addresses with non 64bit IIDs in use, isn't
that code by definition *already* broken? I don't see how changing the
4291bis document to reflect operational reality makes the code any
more broken.

Steinar Haug, AS2116


From nobody Thu Feb 23 00:20:56 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC96912A131; Thu, 23 Feb 2017 00:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 rTI305WzMK3Z; Thu, 23 Feb 2017 00:20:53 -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 ADF9C12A12D; Thu, 23 Feb 2017 00:20:53 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 D0CDE80BE2; Thu, 23 Feb 2017 09:20:48 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <ff7ede5d-7451-53df-0124-96a7344b3d96@si6networks.com>
Date: Thu, 23 Feb 2017 05:17:57 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-tEIJ9_2Wtw0NFOE1fZ1Vmf1DWs>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:20:55 -0000

On 02/22/2017 09:41 PM, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 5:20 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
> 
>     Nobody is saying that /64 isn't extremely widely used where it's
>     appropriate to have a portable fixed length IID. Set the default
>     at 64 and trust operators to change it where they need to.
>     That's realistic.
> 
> 
> As a host developer I strongly oppose that. It will make life easier for
> network operators but make life harder for host OS developers, host
> operators, and host users.
> 
> And it is absolutely inappropriate to change this now in given that the
> /64 boundary has been the standard for the last 20 years. It will break
> deployed code that relies on the current standard. (That includes
> concrete code I can point to that I know runs on tens of millions of
> devices.) That's not acceptable to do in a standard reclassification.

If the above will break your code, then your code is already broken. Fix 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 Thu Feb 23 00:21:09 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9696312A140; Thu, 23 Feb 2017 00:21:05 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c_HuGThlsYpp; Thu, 23 Feb 2017 00:21:00 -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 E44ED12A145; Thu, 23 Feb 2017 00:20:59 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 7EB5E80F12; Thu, 23 Feb 2017 09:20:55 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>, Randy Bush <randy@psg.com>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <m2poiaug54.wl-randy@psg.com> <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com> <m2efypvi6o.wl-randy@psg.com> <CAKD1Yr0bUTT+NSjO=9GFeDU1UnsFjxneS5kqQw2U5UgQp7RnSg@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <548c1e17-3d95-2267-6d68-7486af19fe9b@si6networks.com>
Date: Thu, 23 Feb 2017 05:20:43 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr0bUTT+NSjO=9GFeDU1UnsFjxneS5kqQw2U5UgQp7RnSg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_9vRIYI8jmCxrzLYjtkLXBna74I>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:21:06 -0000

On 02/22/2017 10:50 PM, Lorenzo Colitti wrote:
>     > With the difference that the standards clearly specify what the current
>     > state of affairs is.
> 
>     and now we need to make the wannabe document match what the state of
>     affairs is in networking.
> 
> 
> That doesn't mean "we've been violating the standards, so now the
> standards have to change to match what we've been doing, even if other
> parties are depending on the standards", does it? :-)

Oh, well... you said this exact words at the 6man wg meeting in Seoul,
when you were suggesting that we should allow EH insertion because some
folks had implemented and deployed code that was violating RFC2460.

Looks like you like to bend the rules depending on what you want to push
forward.

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 23 00:25:34 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B5312A13B for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:25:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wf-4Kxf6sp0I for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:25:30 -0800 (PST)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 3D76612A138 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:25:30 -0800 (PST)
Received: by mail-vk0-x235.google.com with SMTP id t8so15919084vke.3 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:25:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NLG1PBZS0bjXRCxdQ0Y1uN13s1edUWR/HUMzWFbFGQw=; b=qmuAZWTSxC6H44zSaWfpEU7yNEnnGNLnYFDxVO3ca3NzlPs69STFo/hWpgI/CRDhgz 1+SPzEOgu155bKwE23CftGIPf8LoRGc9fHZa9o5tEFEuzPL7g3uuK9FBzLKr38oTa5XR SD/WkayqiHte5pfHHq+rEeZCJj2Ad49XNFTsfBX9fhEmW5AOCSt2sjNstpCDav+4jTOk +xKv2EAvxl3qBtWUubCBH0Llxoz/nJTF0LviLoYmOzW6/DxZQaHyuoMTC+aNDXxlkQPU EXmfk0Z567H8uWhZ6V501pE4sCYADLt+5i/a6wexAK7UTprVOKkiyAXcsJu+fB7LA3wO Dvrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NLG1PBZS0bjXRCxdQ0Y1uN13s1edUWR/HUMzWFbFGQw=; b=LTvF/Ra9RVnyIwqHSCHCUjUWBc/GzPkBPM0zpdIFDNbUtHsfhkLFN1PT9TwonOywnW L3eHJ1Zqfv6E7aiPYm2ExoUo4dfmfUn22IBRk4QLuclA37HHCy6ItoacWeSvi0UnOPnn CRYEgxomwcNwsK6z57ivOwVKwYY9nme2qgsolm7pPEGP54jOQtG2EpW4ZM/tn4eGTJWb cdcpioCTT2D+RT+cQbrbJj3DQv79CsoKbGkFrfmwBH9HANT1gNq9qD71XKGeIlvI6yVE DJ9FfvnGxBo+vN6QXgmF0HjGGGNAHkWj7crQGxbpzib1u3CnmsXGpevzSzfRKvW3N37b KBZw==
X-Gm-Message-State: AMke39nVH3R6qMwMtF6jB7vPdvra7DLFE1R+nkNZTfbe4I32qVWnp7qw8wNDSBXqmAQ4bjgx4DcIAqBb4T0C5VAz
X-Received: by 10.31.248.193 with SMTP id w184mr18574384vkh.10.1487838329004;  Thu, 23 Feb 2017 00:25:29 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 00:25:08 -0800 (PST)
In-Reply-To: <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com> <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 17:25:08 +0900
Message-ID: <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c14bd2a15f11205492e5b1b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ChVwTcY1kW5OAIFrUCSoBuKyauw>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:25:32 -0000

--94eb2c14bd2a15f11205492e5b1b
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 23, 2017 at 4:33 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> My understanding is that Randy et al are trying to get rfc4291bis to
> reflect operational reality, but you want to progress the document with
> no changes, essentially meaning that you want to publish a document as
> full standard which doesn't agree with how the protocol is being deployed.
>

I think we all agree that the document doesn't agree with what Randy et al
deployed, because the document matches the existing standard and Randy et
al chose to violate the standard. What I'm saying is:

   1. The "operational reality" that Randy et al want to match is not
   widely deployed (in terms of number of links). The overwhelming majority of
   links on the Internet (of which backbone links are just a small number)
   follow the standards.
   2. There are hosts that follow the standards and only support /64 in
   some cases, or rely on /64 to provide useful functionality. Changing the
   standards to match said limited operational reality will render those hosts
   noncompliant.
   3. We should not render compliant hosts noncompliant because a minority
   of links purposely violated the standards.

If, even at the time of publication our documents already do not reflect
> reality, we are not going to be taken seriously.
>

But they do reflect reality. If you look at the whole Internet, think there
are probably 1000 /64 links for every /65-126 link deployed today. Removing
the fixed /64 boundary will cause way more than 0.1% of hosts - which
*correctly* implemented a fixed /64 IID - to become noncompliant. Thus,
changing the document as suggested by Randy et al will actually cause the
document to reflect reality less than it does today.

Repeating a "classful addressing is bad" mantra isn't going to change those
facts.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 4:33 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">My understanding is tha=
t Randy et al are trying to get rfc4291bis to<br>
reflect operational reality, but you want to progress the document with<br>
no changes, essentially meaning that you want to publish a document as<br>
full standard which doesn&#39;t agree with how the protocol is being deploy=
ed.<br></blockquote><div><br></div><div>I think we all agree that the docum=
ent doesn&#39;t agree with what Randy et al deployed, because the document =
matches the existing standard and Randy et al chose to violate the standard=
. What I&#39;m saying is:</div><div><ol><li>The &quot;operational reality&q=
uot; that Randy et al want to match is not widely deployed (in terms of num=
ber of links). The overwhelming majority of links on the Internet (of which=
 backbone links are just a small number) follow the standards.<br></li><li>=
There are hosts that follow the standards and only support /64 in some case=
s, or rely on /64 to provide useful functionality. Changing the standards t=
o match said limited operational reality will render those hosts noncomplia=
nt.</li><li>We should not render compliant hosts noncompliant because a min=
ority of links purposely violated the standards.</li></ol></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">If, even at the time of publication our documents alrea=
dy do not reflect<br>
reality, we are not going to be taken seriously.<br></blockquote><div><br><=
/div><div>But they do reflect reality. If you look at the whole Internet, t=
hink there are probably 1000 /64 links for every /65-126 link deployed toda=
y. Removing the fixed /64 boundary will cause way more than 0.1% of hosts -=
 which *correctly* implemented a fixed /64 IID - to become noncompliant. Th=
us, changing the document as suggested by Randy et al will actually cause t=
he document to reflect reality less than it does today.</div><div><br></div=
><div>Repeating a &quot;classful addressing is bad&quot; mantra isn&#39;t g=
oing to change those facts.</div></div></div></div>

--94eb2c14bd2a15f11205492e5b1b--


From nobody Thu Feb 23 00:27:18 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D4A012A148 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:27:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a03Ec7aOIX00 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:27:12 -0800 (PST)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::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 6080512A14E for <ietf@ietf.org>; Thu, 23 Feb 2017 00:27:09 -0800 (PST)
Received: by mail-vk0-x22a.google.com with SMTP id t8so15936433vke.3 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:27:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P1OzIgojLEY2L8tTL2H9dHglyPA/9NMhq2lHI99sTew=; b=XZ3bLzAS+0084sxsGem1YhXt5FAQ94voA80YISYQZbDwIUPIEjbrJFUu+CjBZuT5PO HjWWSgLvw1NKz0dDFqd4BAfMRmzBpjFM0+Lfr0blWee6GfeQTi5b+2njYikfRstwKfpX XJCp6LKGHDwKUXeKp2VXgsJcB+TGvAmHgNe3RP8fRhnzrQypeaf0bjeuEfdse/LJx149 zAGPcy2UpmtleK0gI7br8gJ1Y8PxCjYZIzKN2SXoGF2wBYyVoAjQ12hMRyXD0JUydUR4 3JVH2ybyUQ/fPNrsjwdy4cnwK6HO3OHv9C4xyEvSKYkK2Gr/27gpOV4i1cpgEMOyRkHn 8hjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=P1OzIgojLEY2L8tTL2H9dHglyPA/9NMhq2lHI99sTew=; b=L7HrKn8NUs3yLcPkFBS20HDxs8VLh5aQvO9xudy9DqAhDYjMuvIJo+aOZt0niR0II1 8ejwqvrg2fvbsfVn8gNNpZnn41mB6qm+S8/8/pSu7qMAeX02yO1kUcD3NexbL0hE4B0t UBxobP6Y+JBHv4GQXnb5DHhugMFQJUWQ0cEz7FI09chh9OQ8ko9Q4WZAUnBL90731dm/ alZ6Eh8g64YZg9S3Hf02CroT7tXjDq94huOmuBEPxjABw/ohs2KG4yow7Al4+DRk0Uz1 HGRsNp7+xEscO+PvWFYqvE0o0B3qJIMh5NHtyf+YQ5UJFOJuo77Ep6uavK/1Q2918tsi oxOA==
X-Gm-Message-State: AMke39nUmWHf2Wr8XiipWAiCChEggCP5UDIZ60l7HxvYZ1dGhwNCbQtg3uN7FxzhwbQSnnZ9Z4V979vrGN+tumSw
X-Received: by 10.31.142.68 with SMTP id q65mr18212633vkd.83.1487838428149; Thu, 23 Feb 2017 00:27:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 00:26:47 -0800 (PST)
In-Reply-To: <ff7ede5d-7451-53df-0124-96a7344b3d96@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <ff7ede5d-7451-53df-0124-96a7344b3d96@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 17:26:47 +0900
Message-ID: <CAKD1Yr2rGujad-ixiktgw5ju=zYxzvaq6WEHTp0q1UyfOb+X-w@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1143703afed0bf05492e60e5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ittfXjczlo5R2rETtSSApIRT6NA>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:27:13 -0000

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

On Thu, Feb 23, 2017 at 5:17 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> > And it is absolutely inappropriate to change this now in given that the
> > /64 boundary has been the standard for the last 20 years. It will break
> > deployed code that relies on the current standard. (That includes
> > concrete code I can point to that I know runs on tens of millions of
> > devices.) That's not acceptable to do in a standard reclassification.
>
> If the above will break your code, then your code is already broken. Fix
> it.


Nope. That code implements the standard, and thus by definition it's not
broken.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 5:17 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; A=
nd it is absolutely inappropriate to change this now in given that the<br>
&gt; /64 boundary has been the standard for the last 20 years. It will brea=
k<br>
&gt; deployed code that relies on the current standard. (That includes<br>
&gt; concrete code I can point to that I know runs on tens of millions of<b=
r>
&gt; devices.) That&#39;s not acceptable to do in a standard reclassificati=
on.<br>
<br>
</span>If the above will break your code, then your code is already broken.=
 Fix it.</blockquote><div><br></div><div>Nope. That code implements the sta=
ndard, and thus by definition it&#39;s not broken.</div></div></div></div>

--001a1143703afed0bf05492e60e5--


From nobody Thu Feb 23 00:28:10 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4A41129C8D for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AKrBX2kh82Mg for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:28:06 -0800 (PST)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::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 65DC312A152 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:28:06 -0800 (PST)
Received: by mail-vk0-x235.google.com with SMTP id r136so15970840vke.1 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:28:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2HmS7hEm/PSUtlednsPTsJXrFO31CidiIq2r3GGF6/c=; b=UMkMcSscgt0N/QKAIkiErizw0nDZEhQ7eNkZIvkE8ne/tUgacXIefyNPUNyvMJgDg3 giVBLnofoDKbjcNVU9sh744xCUwOhuEGbHe8gFOjmXY3HXkOE4QXXh6HS2umvc+p14Ip GxbmG3sSoTRDdU2lwzT5uVOzc+GjJGyq04y3fRDXHiL/Jk+M8kAV5cz7cl6YKWaHm5p2 vr8H9AQ9dW95zIgBl2bb4w0e77Fbb50KpIMNIIaudKarpiSsmyE/PAANWlaNAHxxnWru YMx/Fb3r9T9znNVDuXKfdIX+MjbGSJOS3cfYLd7OwCAkR8qx0268wTL4Grj2oxBNw8H4 KOrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2HmS7hEm/PSUtlednsPTsJXrFO31CidiIq2r3GGF6/c=; b=mgUHTdq3WuR43gPA6I2+A8R8rJpAL9Lnfyz1cEIkeXVCX1ZQmoXEMMG53U2r3WcGxX IO8+EPletNaviqDYG9lm9ODzKZf64aKWWDw1SG1z3C7TRj3IeppiKSMNL2XQASrlVkjw 8E3hRz9gITbadN6d/80HXYaCKf+9rRwOsud+GHmEuNeLE4BYPM73d2s1uGma5AGOxKjI 5hYPTooqYLm+l1z99XaIe2m9jBwZRw4LdDJojyJMU5Gi7nPf4HDmdrTNDqn8/4tdYaCa DEzRG77jNE3EWqzBqsN17hk2QpaSNGm/tbKzwvha39sFvu9TZYszzQiUWOMfOzcMdWi9 lbTw==
X-Gm-Message-State: AMke39m3WVixvoYOATOfdY7rVAEFaJqHgu6G++Spf18Dk0j8SHmd18iQHq1EFSlVsk1DouxN2hzo3dnykiOmUMim
X-Received: by 10.31.170.15 with SMTP id t15mr15751080vke.6.1487838485335; Thu, 23 Feb 2017 00:28:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 00:27:44 -0800 (PST)
In-Reply-To: <548c1e17-3d95-2267-6d68-7486af19fe9b@si6networks.com>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <m2poiaug54.wl-randy@psg.com> <CAKD1Yr04AKpvp81KdSb9zoMfr0ZdNLq8a+Wgk-3KqSYfP=Qn7g@mail.gmail.com> <m2efypvi6o.wl-randy@psg.com> <CAKD1Yr0bUTT+NSjO=9GFeDU1UnsFjxneS5kqQw2U5UgQp7RnSg@mail.gmail.com> <548c1e17-3d95-2267-6d68-7486af19fe9b@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 17:27:44 +0900
Message-ID: <CAKD1Yr3ke6pboPFmaLP_bnXvDH0QKy37U1cJYma+hrzwPy-sNQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a1143225067aa8305492e6436
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z-HahMdjoMjtVOugpvGydpI4Ozw>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:28:08 -0000

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

On Thu, Feb 23, 2017 at 5:20 PM, Fernando Gont <fgont@si6networks.com>
wrote:

> Oh, well... you said this exact words at the 6man wg meeting in Seoul,
> when you were suggesting that we should allow EH insertion because some
> folks had implemented and deployed code that was violating RFC2460.
>

If you want to accuse me of inconsistency, please quote me literally and in
context.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 5:20 PM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Oh, well... you said th=
is exact words at the 6man wg meeting in Seoul,<br>
when you were suggesting that we should allow EH insertion because some<br>
folks had implemented and deployed code that was violating RFC2460.<br></bl=
ockquote><div><br></div><div>If you want to accuse me of inconsistency, ple=
ase quote me literally and in context.=C2=A0</div></div></div></div>

--001a1143225067aa8305492e6436--


From nobody Thu Feb 23 00:38:30 2017
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5591C1294D5; Thu, 23 Feb 2017 00:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.726
X-Spam-Level: 
X-Spam-Status: No, score=-0.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2iVBpmsDjvY; Thu, 23 Feb 2017 00:38:22 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::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 1E28F1293FB; Thu, 23 Feb 2017 00:38:22 -0800 (PST)
Received: by mail-qk0-x229.google.com with SMTP id u188so25574465qkc.2; Thu, 23 Feb 2017 00:38:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=5Q5FkJ4pBiuenmWplBbZcGIhue9LQNn7qRizIsYvPVg=; b=A1f8Biq86Sc/FaHgbmAykPm3Czfzgs//3lkUz7J+SvhIk35a3ZhVi4jPn/8+APyl1c nbXlO8mKw43i60lgazV4lzvtuTooqej+h6MEWRISW4i14jv6O8sM0zieIJXDWPD+Yh/+ PIx1K7e15DSEuXvd+t0Cl/q9zABYlxC5WQiYdxb1VtYiMH6RxbWw5Gmq0nl6InPLTPcO nvgFCKDIm9CL/NSYK+5f7A27JQFoJmLjkjC9DaDKIVyk8sFjgwy2hV/myrIkTvyee0at k6poxAbl5B95KaYyDYg9tG1GFGE0rHfjYFYspwJm4H2gGpnV2he40A1Emyt8MdD6weSs w0ng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=5Q5FkJ4pBiuenmWplBbZcGIhue9LQNn7qRizIsYvPVg=; b=P+RtakteAJ13OMlgAZF8wTqWW8MVkWHoJlMcN2qpXurXhpeMZwI3zFnw8zKwrU/qKm +AOi7UQoSUO0bvZ0NMIhYC0vombkIzpSsqVsZUhlCSs/DyW3Qw1aZvatvdbT+K3nQcRn /5p4PJc0HyZbS3DjUnRxUstcY/BSiG6TVXbq+jAU8sFc+JsJcTXYWDlwHTrV/gfQ/oJh femP0k1gkjdP/AtyJcRZXVf/BJPdT2BndAkQmjQ81OBI2FdXjiDwAvMwPNC1EP7JlbWA gnHjv5qpWkZJ+GdL01hmG56bFM/2Efv0too+beb9CiVxRBngN+MgYhN0Yfc+DP0xehCU 7uVQ==
X-Gm-Message-State: AMke39nc+XJ3wOzXKFz5V3K4ggrSf3NF+Z5S8cPfrTzRksHZmcwrHn2uq9vyC6kOZhxK8zgW8ifvy6PqZHtnlA==
X-Received: by 10.55.66.68 with SMTP id p65mr25195056qka.187.1487839101014; Thu, 23 Feb 2017 00:38:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.99.21 with HTTP; Thu, 23 Feb 2017 00:38:20 -0800 (PST)
In-Reply-To: <148727121108.1035.17932176133304575302.idtracker@ietfa.amsl.com>
References: <148727121108.1035.17932176133304575302.idtracker@ietfa.amsl.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Thu, 23 Feb 2017 10:38:20 +0200
Message-ID: <CADnDZ8_Q3=EHV_1ngnR0kxLtDHWpSL9zEraHnRqMnHLKT1AdSQ@mail.gmail.com>
Subject: Re: Follow up on barriers to entry blog post
To: iesg@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2bw3P9bBlwJVtIzHy8NTT3o3CHE>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:38:23 -0000

Dear Sirs,

Sorry for this long email, but I need to give the respond details.

Thanks for your concerns and support, and I believe that IESG is doing
its best to make IETF the best organisation. However, I have already
send my concerns before years to you about this issue that most
meeting in US is not correct strategy for the best practice of IETF,
the respond I think was that most participants are from US, My
addition thoughts were that most companies participating/hosting are
from US. My reasons of my concerns is that IETF should not follow
others it should lead the participants. Also IETF should not care
about volume of participants (especially old participants), it should
care about varieties/diversity and future participation, the world is
changing very quickly (including US) and hopefully the IETF.

M past suggestions (in many IETF discussions) were to make the
most/best meetings in UK (ex. in London) or Europe, because US
participants get better offers to travel to UK than other offers to
countries in Europe. I also suggested in the past that we need more
work in General Area, but the IETF need to follow interests to such
WG, if no interest the IETF does nothing for its best future.

I studied in the UK and one of the best things I seen from
experts/managers in UK is that they look into unexpected situations to
find solutions. Did we do that so far? I am not sure, please advise
me.

IMO, Your concerns is not enough, you need to change your policy in
General Area, to include diversity and future strategies. May be I am
not familiar with our ADs/IESG decisions in IETF-strategy, but your
email did not mention your past actions/startegies to solve the
unexpected barriers. Old Strategies that include unexpected issues
will help to solve new/future barriers. The WG in General Area your
email referred to is about meeting venues but what about strategies
that this group need to follow. This WG will have majority of
participats from US therefore, it MAY not be fare to work for the IETF
interest, but may support for other companies interests.

Do you have a strategy for the future management issues? please tell
me your procedure as a strategy-plan already defined, or  as WG
charter (or even special group) with milestone. There is no doubt that
any successful organisation needs a strategy to increase opportunities
and decrease threats. My aim for this email is communicate with you
for the best of IETF. Thanks,

Best Regards,

AB

IETF Participant from Libya
University of Tripoli, Tripoli

On 2/16/17, The IESG <iesg@ietf.org> wrote:
> The IESG, IAB and IAOC note the recent US executive order concerning
> entry into the United States and the ongoing discussion of it amongst
> the IETF community. While nations determine who may cross their borders,
> we are very concerned that the resulting uncertainty has damaged our
> ability to host appropriately inclusive meetings and workshops, and may
> result in increased travel restrictions in other locations going
> forward. The present uncertainty affects participants traveling to a
> meeting in the US, or US-based participants returning from a meeting
> held outside the US. We are also concerned that such actions may
> unreasonably limit the ability of engineers the world over to take a
> full part in IETF activities that involve face-to-face meetings.

It is a weakness to follow your participants, because they should not
be your customers, the IETF customers are the users not the
participants. Why you follow your workers, they MUST work for you so
you can continue. IETF should not concern about meeting volumes.

>
> Our primary means of communication (email) does not suffer from such
> restrictions, and we have worked to continually improve remote
> participation for face-to-face meetings. But those who cannot attend
> face-to-face meetings are at a disadvantage compared to those who can,
> and the meetings overall are less effective opportunities for high-
> bandwidth collaboration, cross-pollination of ideas, and focusing on
> running code. We expect the results to be detrimental to our goal of
> making the Internet work better.
>
> The IESG, IAB and IAOC are committed to planning our future meetings in
> locations that do not present an undue risk to our participants and our
> efforts. Our next meeting in Chicago is going ahead as planned, but we
> are working now to investigate any ways in which we can mitigate
> possible disruptions in the near term. Future meetings in the US are
> being reviewed, as we would normally do when we learn of significant
> access issues in any of our planned meeting locations.

Good to know

>
> We encourage the IETF community to raise awareness of travel
> restrictions that make it difficult to attend our meetings in person.

London is the best location for IETF business and future,

> The venue-selection mailing list <=E2=80=8Bhttps://www.ietf.org/mailman/l=
istinfo/
> venue-selection> is available to provide direct input to the IAOC, and
> the IETF Discussion list is available for other awareness-raising. We
> also urge IETF participants to contribute to the MTGVENUE working group
> <=E2=80=8Bhttps://datatracker.ietf.org/wg/mtgvenue/charter/> that is deve=
loping
> criteria and processes for IETF meeting venue selection.
>
>


From nobody Thu Feb 23 00:45:37 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8CA1129668 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:45:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.667
X-Spam-Level: 
X-Spam-Status: No, score=0.667 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 vEbCwVnm09qi for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:45:33 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 BB48B1294F3 for <ietf@ietf.org>; Thu, 23 Feb 2017 00:45:33 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1N8jWBS044455 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:45:32 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 20560203225 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:45:32 +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 18644202516 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:45:32 +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 v1N8jVMW012472 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:45:31 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <54a177d5-a52e-79bb-2613-af6c034b1dd8@gmail.com>
Date: Thu, 23 Feb 2017 09:45:23 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X0xQR9XU4gwY5MM-f8bdtG8ddBQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:45:35 -0000

Le 23/02/2017 à 05:16, Lorenzo Colitti a écrit :
> On Thu, Feb 23, 2017 at 12:44 PM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote:
>
>     I'm sorry, I'm wondering which word in my recent message that said
>     "I'm not aware of any generally available running code that will
>     be changed in even one instruction by the final text - that is indeed
>     a requirement for advancement to Internet Standard."
>     is hard to understand.
>
>
> Help he understand, then. There is widely-deployed code that assumes
> that the interface ID is 64

There is also widely-deployed code that does not make an assumption of 
IID length - it is DHCPv6 which works without any prefix length.

Alex

  and does not work on anything other than 64
> bit prefix lengths. Currently that code is correct on all unicast space.
> If you change RFC 4291, won't that code be incorrect?


From nobody Thu Feb 23 00:47:16 2017
Return-Path: <sthaug@nethelp.no>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAA1F129CF9; Thu, 23 Feb 2017 00:47: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 autolearn_force=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 ZulZzSqE5CxA; Thu, 23 Feb 2017 00:47:13 -0800 (PST)
Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by ietfa.amsl.com (Postfix) with ESMTP id 0B320129668; Thu, 23 Feb 2017 00:47:13 -0800 (PST)
Received: from localhost (bizet.nethelp.no [IPv6:2001:8c0:9e04:500::1]) by bizet.nethelp.no (Postfix) with ESMTP id 87408E6067; Thu, 23 Feb 2017 09:47:11 +0100 (CET)
Date: Thu, 23 Feb 2017 09:47:11 +0100 (CET)
Message-Id: <20170223.094711.41666643.sthaug@nethelp.no>
To: lorenzo@google.com
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: sthaug@nethelp.no
In-Reply-To: <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com>
References: <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com> <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SJH-bUR46Da7fZbItuMUJQ18xuY>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:47:14 -0000

> But they do reflect reality. If you look at the whole Internet, think there
> are probably 1000 /64 links for every /65-126 link deployed today.

1000 /64 links for every /65-126 link may well be the case. However,
plenty of non /64 links exist, and I see no sign of them going
away. Claiming that all IIDs are 64 bit is simply incorrect, and
doesn't reflect operational reality no matter how hard you try to
make that claim.

At least the ISP I work for will make sure (through RFP requirements
etc) that /65-126 links *continue to work*.

Steinar Haug, AS2116


From nobody Thu Feb 23 00:59:09 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 652F8129682 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:59:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 TJ00KyN7AGmB for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 00:59:06 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 8CCEE12966A for <ietf@ietf.org>; Thu, 23 Feb 2017 00:59:06 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1N8x4T6004308 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:59:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 6485E207163 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:59:04 +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 5AE8320716F for <ietf@ietf.org>; Thu, 23 Feb 2017 09:59:04 +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 v1N8x426004995 for <ietf@ietf.org>; Thu, 23 Feb 2017 09:59:04 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <m2vas1ttsj.wl-randy@psg.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c6c13d35-e0b6-4ba3-3246-e90f8e236008@gmail.com>
Date: Thu, 23 Feb 2017 09:58:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <m2vas1ttsj.wl-randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a-xUslfLuZNZ7mOUT10oNGL3v-k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 08:59:07 -0000

Le 23/02/2017 à 05:28, Randy Bush a écrit :
>> the IETF and 6man absolutely have the ability to change the
>> standard, but it should follow the proper process: write a draft,
>> get consensus,
>
> that is the process we are currently in.  but there seems to be
> serious disagreement over the draft.

There was an initiative at a time to write such drafts.

But because of opposition from one single person many other persons
declined such effort.  The wisdom at that time was that it cant get
through.  The result of that effort was deviation into 'why64' RFC
explaining 64 is good, and the 'CIDR routing' RFC which does not oppose
SLAAC/Ethernet/64.

There were suggestions to the new IPv6-over-foo I-Ds derived  from 
RFC2464 to relax the IID length away from 64.  The advice was that it 
could not never get through 6man, better stay with that 64 limit.  As if
everything should be Ethernet in this world.

Given that, what would be the incentives to write yet another draft? 
Only to kill it later?

Alex

>
> randy
>
>


From nobody Thu Feb 23 01:01:42 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21767129CF9; Thu, 23 Feb 2017 01:01:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-dime-load-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148784049413.20240.15876379956092850264.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 01:01:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yI3zH11JMZIzxe8GrKY3SaAsTVQ>
Cc: draft-ietf-dime-load.all@ietf.org, dime@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:01:34 -0000

Reviewer: Roni Even
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dime-load-07
Reviewer: Roni Even
Review Date: 2017-02-23
IETF LC End Date: 2017-02-27
IESG Telechat date: 2017-03-16

Summary: This draft is almost ready for publication as a standard
track RFC

Major issues:

Minor issues:

I understand that each node can calculate the load differently , the
example in figure 8 demonstrate that the agent selection may be
different if the agent aggregates load from the servers to calculate
its load or just conveys his load, possibly even that each one of the
agents will use different method. Why not mandate load calculation
using aggregated weighted loads? 

Nits/editorial comments: 
1. In section 5 paragraph 9 "The load report includes a value
indicating the load of the sending
   node relative load of the sending node, " should be just "The load
report includes a value indicating the relative load of the sending
node,"
2. In section 6.2 "weigth "
3. in the security consideration what about an endpoint in the middle
changing the host load value causing a change in the routing
decisions. 





From nobody Thu Feb 23 01:02:15 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AC6812966A for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 snzod3OSYcbE for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:02:07 -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 02650129682 for <ietf@ietf.org>; Thu, 23 Feb 2017 01:02:06 -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 v1N924Wm002492 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:02:04 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 704A120716F for <ietf@ietf.org>; Thu, 23 Feb 2017 10:02:04 +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 668AB207169 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:02:04 +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 v1N924Ad009515 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:02:04 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <0f3db3bd87eb4a9ba51360d9b73751e3@XCH15-06-11.nw.nos.boeing.com> <CAKD1Yr2o3eyuhvij4=KjsVMTor=oh5N8AWfjOCJ_jh6nSA0=Gg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <eb133099-95ba-430b-1602-efb395307015@gmail.com>
Date: Thu, 23 Feb 2017 10:01:56 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr2o3eyuhvij4=KjsVMTor=oh5N8AWfjOCJ_jh6nSA0=Gg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z6GsGKHAWuyhkrUiCOcZRNBsdAo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:02:13 -0000

Le 23/02/2017 à 06:58, Lorenzo Colitti a écrit :
> On Thu, Feb 23, 2017 at 1:39 PM, Manfredi, Albert E
> <albert.e.manfredi@boeing.com <mailto:albert.e.manfredi@boeing.com>> wrote:
>
>     > Help he understand, then. There is widely-deployed code that assumes
>     > that the interface ID is 64 and does not work on anything other than
>     > 64 bit prefix lengths. Currently that code is correct on all unicast
>     > space. If you change RFC 4291, won't that code be incorrect?
>
>     This shows precisely why it is urgent to update RFC 4291, to correct
>     that notion of a fixed IID, before it's too late to set things
>     straight again.
>
>
> Ok, so you're suggesting that we drop the attempt to reclassify RFC
> 4291, and instead write a new document to update it? That's a possible
> course of action. It would only result in your desired outcome if there
> was rough consensus to change the boundary, but as I said before, I'm
> not going to oppose that course of action.
>
>
>        IPv6 unicast addresses are aggregatable with prefixes of arbitrary
>
>        bit-length, similar to IPv4 addresses under Classless Inter-Domain
>        Routing.
>
>     Important point. Arbitrary length. That does not mean 64 bits.
>
>
> Nobody is disagreeing with that text. Please refer to the earlier
> clarifications in this thread and the discussion in 6man that pointed
> out that *routing* based on prefix lengths != 64 is independent from
> *interface IDs* being required to be 64 bits long or not.

Please understand that routing based on prefix lenghts != 64 is 
dependent on subnets with IIDs precisely of that prefix length.

It is an error to SLAAC/Ethernet/64 on a subnet to which only a /120 is 
routed.

Alex


From nobody Thu Feb 23 01:03:06 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86899129682; Thu, 23 Feb 2017 01:03:02 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 TA_QAAS0AhOg; Thu, 23 Feb 2017 01:03:00 -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 713CF12966A; Thu, 23 Feb 2017 01:03:00 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 E9AC680A1C; Thu, 23 Feb 2017 10:02:55 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <3f6b3814-34ee-e8e4-3746-85b3e7e208d8@si6networks.com> <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com> <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <cf739026-c333-28d0-9c35-ad5b9a8336a0@si6networks.com>
Date: Thu, 23 Feb 2017 06:01:54 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r2J1meIvJIE5WuwnJKDyKED_WP8>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:03:02 -0000

On 02/23/2017 05:25 AM, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 4:33 PM, Fernando Gont <fgont@si6networks.com
> <mailto:fgont@si6networks.com>> wrote:
> 
[...]
> 
> 
> But they do reflect reality. If you look at the whole Internet, think
> there are probably 1000 /64 links for every /65-126 link deployed today.
> Removing the fixed /64 boundary will cause way more than 0.1% of hosts -
> which *correctly* implemented a fixed /64 IID - to become noncompliant.

The proposed fix is to stick to /64 for slaac, and make /64 the default
for other cases (while allowing the operator to override it).

If your comment above was made on the basis that hosts would be
non-compliant because some might not be able to e.g. be configured with
a longer-than-64 prefix, then... that's what usually happens as you
update a spec.

OTOH, if your point is that we cannot do that in the process of moving
this document to full standard, my take is that it's better and more
productive to get the document right, than to cast it into stone "no
matter what".

-- 
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 23 01:04:01 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 778E812A15E for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:04:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pd4RaeZ8YZpP for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:03:58 -0800 (PST)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::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 D2ACE12A148 for <ietf@ietf.org>; Thu, 23 Feb 2017 01:03:57 -0800 (PST)
Received: by mail-vk0-x22d.google.com with SMTP id k127so16329617vke.0 for <ietf@ietf.org>; Thu, 23 Feb 2017 01:03:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=lBxzyCroP73O/WS2lDMyNtU8szlgKWVNr5jfHx5pafM=; b=QMQR61Jej8/kCRtFpdeyuRB+eZoYLKwmfT4yuHO3Lud2sm+SzEho5GkO5vgeU3MjGo VmWhuzPCfkCha5Gf8hTBHRZYkRaFsYrXeOahhOg7W2W23u0V2AbWYzrA7Po9H9YeOOtp 22whhN1tbp7uI1j/orzf/0K7qNbGNCh7XSyGb0uwS7X483O+6+SmahgLs0JKwV7cILqz KxJv+1bdoG4/GzmNmdU1O3tQc1Flt8qiHxyCajq6et906D8bTZFkZvGEjRGCA+JooLBW yGjNHBtw95ps7h2tsHA7lZEmXiO8Pt24RigYeSOUHOB0Amxrk3jXV8cxwvRSxC1t1Tur Ug6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=lBxzyCroP73O/WS2lDMyNtU8szlgKWVNr5jfHx5pafM=; b=GVHcSH+ll7JtkVwp+htV30ZQxpbzTd4AjOaKj7goPnvcScfsqrYOXxoXqoYVhrC+aY GKLlqbjNoM/8JvH2AY9ANvLnejyP9duimbiYY1jL7om/c+EMgggZ2tiEMyMrvX0evHVU MCZTKoVj/KdK99szmxZakI6lmaiWUU7H7s5SRyTMKzA5hyqmiX/GjyZoRx4Rj5yKcb5Z MvKLO6Co5lQZIOWNb264VGia1PZfUEJP6QmomL/+7c0upsLwdMcXJTnWOpjZ0v4AGNru BtxLKy2lZp1orccs5DT+DtcNaAMDWRgzebCxNATTkNX78nNGscp91V/dB7nP35enzwya oLSw==
X-Gm-Message-State: AMke39mwh5YeuMTb47r22JS1JvHw4pQ+3RsXF02BcCFBMl+IwYnZZ7qzhX0k4imT58uxt3nrgvWTqrDaz1M6LViQ
X-Received: by 10.31.150.134 with SMTP id y128mr16261228vkd.102.1487840636793;  Thu, 23 Feb 2017 01:03:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 01:03:35 -0800 (PST)
In-Reply-To: <20170223.094711.41666643.sthaug@nethelp.no>
References: <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com> <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com> <20170223.094711.41666643.sthaug@nethelp.no>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 18:03:35 +0900
Message-ID: <CAKD1Yr2+L2cBMqTmhkwprYbBtTfez70Pv6cx08a+aLPkhhwJqA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: sthaug@nethelp.no
Content-Type: multipart/alternative; boundary=001a1141d600a409c405492ee447
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y-c1paLaBVrkdlAbWlwZK8aiOYU>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:04:00 -0000

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

On Thu, Feb 23, 2017 at 5:47 PM, <sthaug@nethelp.no> wrote:

> 1000 /64 links for every /65-126 link may well be the case. However,
> plenty of non /64 links exist, and I see no sign of them going
> away. Claiming that all IIDs are 64 bit is simply incorrect, and
> doesn't reflect operational reality no matter how hard you try to
> make that claim.
>

I'm not saying that all IIDs are 64 bits. I'm saying that as a percentage
of the Internet, more code is deployed that expects/requires 64 bit IIDs
than links than non-/64 links. So if we want to make the standard reflect
reality, then we should keep it as is.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 5:47 PM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:sthau=
g@nethelp.no" target=3D"_blank">sthaug@nethelp.no</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">1000 /64 links for every /65-126 link may we=
ll be the case. However,<br>
plenty of non /64 links exist, and I see no sign of them going<br>
away. Claiming that all IIDs are 64 bit is simply incorrect, and<br>
doesn&#39;t reflect operational reality no matter how hard you try to<br>
make that claim.<br></blockquote><div><br></div><div>I&#39;m not saying tha=
t all IIDs are 64 bits. I&#39;m saying that as a percentage of the Internet=
, more code is deployed that expects/requires 64 bit IIDs than links than n=
on-/64 links. So if we want to make the standard reflect reality, then we s=
hould keep it as is.</div></div></div></div>

--001a1141d600a409c405492ee447--


From nobody Thu Feb 23 01:08:06 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA2A12956A for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:08:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.333
X-Spam-Level: 
X-Spam-Status: No, score=-4.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 JNVzPtO3v__x for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 01:08:04 -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 427461293FB for <ietf@ietf.org>; Thu, 23 Feb 2017 01:08:04 -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 v1N982Ge026196 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:08:02 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id BFA732071C4 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:08: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 B61362071B3 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:08: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 v1N9824l017392 for <ietf@ietf.org>; Thu, 23 Feb 2017 10:08:02 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <ff7ede5d-7451-53df-0124-96a7344b3d96@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <fcc26901-5375-9786-0353-19050f4497e8@gmail.com>
Date: Thu, 23 Feb 2017 10:07:54 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <ff7ede5d-7451-53df-0124-96a7344b3d96@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MDb35NQ52IlosbniEDmt5tXO6KI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:08:06 -0000

Le 23/02/2017 à 09:17, Fernando Gont a écrit :
> On 02/22/2017 09:41 PM, Lorenzo Colitti wrote:
>> On Thu, Feb 23, 2017 at 5:20 AM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
>> wrote:
>>
>> Nobody is saying that /64 isn't extremely widely used where it's
>> appropriate to have a portable fixed length IID. Set the default at
>> 64 and trust operators to change it where they need to. That's
>> realistic.
>>
>>
>> As a host developer I strongly oppose that. It will make life
>> easier for network operators but make life harder for host OS
>> developers, host operators, and host users.
>>
>> And it is absolutely inappropriate to change this now in given that
>> the /64 boundary has been the standard for the last 20 years. It
>> will break deployed code that relies on the current standard. (That
>> includes concrete code I can point to that I know runs on tens of
>> millions of devices.) That's not acceptable to do in a standard
>> reclassification.
>
> If the above will break your code, then your code is already broken.
> Fix it.

There are a number of precise places that have been identified that
hardcode a 64 value, even places that have nothing to do with
SLAAC/Ethernet.  Especially when it comes to size of a subnet prefix 'by
default'.  Think DHCPv6 code, GUIs, CLIs, and more.

When trying to modify it some times the feedback is better dont, because
the RFCs tell 64 and 64 is a good number.  Some people even say that
IPv6 is different than IPv4 because it has this 64 strong limit.

Alex

>
> Thanks,
>


From nobody Thu Feb 23 01:54:04 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FC891294D3; Thu, 23 Feb 2017 01:54:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.788
X-Spam-Level: 
X-Spam-Status: No, score=-3.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nc3-FZiZX-Gv; Thu, 23 Feb 2017 01:54:01 -0800 (PST)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50097.outbound.protection.outlook.com [40.107.5.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0800D1293FB; Thu, 23 Feb 2017 01:54:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=pAl+tIjE0XkGqdwq9BNNPnbRIWzz+Zl7eHOr1d6+y7s=; b=h3obS1cb6+H9PijJp8nzYl2fIBZyI6Co2S5JTlYMzlrdKB0oPnh+wsTT45XJaEfaeikHDvY4bPIZ09vTFI7fEUJBBA4wRAHVwFOI1wJS48vqt52XObAeJU3Fgga0TSJFhrnYBBxznzgZJki3kUwAMPmSogzkiZwDM2joVmnw028=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.7; Thu, 23 Feb 2017 09:53:58 +0000
Message-ID: <011501d28dba$5ec57cc0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: John C Klensin <john-ietf@jck.com>, Peter Saint-Andre - Filament <peter@filament.com>, <ietf@ietf.org>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <052201d28c3d$c8061060$4001a8c0@gateway.2wire.net> <092474D20D151EB6C7C0E280@PSB> <006c01d28c5e$fbb19760$4001a8c0@gateway.2wire.net> <00068EB71CB3F63F36092E69@PSB> <89b5c4b3-4772-be57-8b5d-b6d63521801b@filament.com> <A82A31111E5E5A6B4EDE9D12@PSB>
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Date: Thu, 23 Feb 2017 09:39:05 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: AM4PR0101CA0054.eurprd01.prod.exchangelabs.com (2603:10a6:200:41::22) To DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10)
X-MS-Office365-Filtering-Correlation-Id: ecf177a2-7c57-447f-2f2f-08d45bd1e351
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR07MB1560;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 3:rZbsX9OhdKfBaOx+D8XLs97do1RnnMAZgpapj0j9yLGa4yCvJQoLIeJFWBnts/7x2AKHwOsbPbmHLoFFhq/xz4wMdVCyrW9Tq110XOtemQ25pvVkDZXNJi0E+1HNjUJM/oM1rk+PBAg099kpeK0AxV+hxUJYJyvs6vXxU2lvt8um/hq90FB7UhIHcSt1XhlFzZJmhl33RXZMf2QSWN6SgakfI93mdhA8/GXRc0xN1W/i0NWIqSwxLXk4Pc4bByj4d3KHwlxY6IyzTRGKmUrDkw==; 25:H7w1grveGaEhLLMFhxC6XbeRXikMR8BKI4OautV3PVz1TGGIu7AF9+tnMBvnnupV5xqEsOYoJ0P9RNsGKs2Er/b2h9JPjgf5d2iigcX6ZcIG5N1N0lBrSlo4aogLc9Vvjqh2CR4VWmGLW2ovkd7hLRFzXylMg7GDXv0yA0fCh/4ks01vC4liuS+wTwe0abqlXMPK+EOJJ2C2E0VcOHgVH0oIK0WkE+4wZMf13EtvvBTOnuUNnk54wvEvIeNTuUXs4rp11basG3T2IEAUB8M6KjvnSHHtZCsz4Ary+7AL2KLgb6Yjqh7+iHVtqvaexLdAPZFr9KEx9ouFjiM8r9g+T8cQ7X5/bff6H3ePQi/biHgjVHdgWOpTTgAsbXxgLT3Ley+ld0o8TD9klCdO3c8gj2tftWzBy8xH8xVRDtj+SPQbIaMOKtJPeXrTy4Q+dMB3+aKdfboLA/MHqWuIZ/zAVQ==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 31:l4CQlTZpxi2odqM6buwDFtH7OR8BR3i3FpElRpHW63dYeULATjnS6q6qtbRde9SLPFhVZzHfp3d47FHrscEuV+JW4XePEDNy+bhK4mSWc3ztNQPqTFeaYVGXmLQxWb54hSR5nsxcfz4bXkwzlUKmVP84jSQTVCAU9gw3AexApiAlaYxvReQnzwWwTRmhzxWQPcOnfrrLm3TDNN9k5vjSKdUHEkVCNqOi2CBwBmpSnC7s2AjD7Zdfd3Mpk37hI0FgKlNBtRJkr9WlLh3Gex5P4BIy7p8v9by4iXjqVlT3ykY=; 4:2ZXKj/kEAuJShwAas3Dv4knxOXlii1sst9O7Lzi6d+HDNTiHDSnudCeI9r/ZcaxRYB/H6OjKsgB0TqUgOdB2L1BzTqkwcqJGxttFmE1ilQ6hR0HyQ0ARakVaUDyqYcS6sIS63k3wYeXGiDWh9iYqZ4IhWEqGG+bFKNNSqCIjsI1/O9toSN6eMsRCj0PgHu1THjoy0Y3H4J5VeOpA4knOhXWVZ05k0eL6US+jDUSJ0BZUFV2ej3dyCbcggg3hzOd22QEy1vUW72PZfU08u4ouj13NQXJru7gE5vzKBCSb6DNc8ggl24ZtXs7Lu0k1nqrapqlgotiQVmaKAIwu1FuyC8fYhZ4qFagKOl/BrU4KW6LK3anmH5U3O7A1NY1tLDoU6yl9DlQJOcMo3qFJ7KeCtqs1BE4GqPzkBAEb+Qkx4DapCRIhFtsJAsj3AU1Kbw5ebA1tK8qNaPx5ddPzU2RzfnI6LQWDbyDRelNVAJttMTFAxqJ/xzxJW81eA4wTPxYw6rnV2M+OVUAwISQhYOpd2OndVO+3KE00QmpSQJwx4zpcxx8YRApchiC3wNPp4Y34V5pfVDhdvso81lwIKcwwX9xhy+VmSgi0LnsFx6QqNi0=
X-Microsoft-Antispam-PRVS: <DB5PR07MB1560274C937D14205C0616B3C6530@DB5PR07MB1560.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123555025)(20161123564025)(20161123558025)(20161123560025)(20161123562025)(6072148); SRVR:DB5PR07MB1560; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1560; 
X-Forefront-PRVS: 02272225C5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(24454002)(189002)(13464003)(199003)(377454003)(5660300001)(230700001)(6496005)(6246003)(50466002)(1456003)(38730400002)(14496001)(1556002)(23756003)(44736005)(6486002)(50986999)(189998001)(116806002)(93886004)(305945005)(101416001)(53936002)(97736004)(7736002)(54906002)(81816999)(9686003)(76176999)(81686999)(33646002)(230783001)(105586002)(42186005)(229853002)(106356001)(61296003)(53546006)(47776003)(3846002)(66066001)(6116002)(92566002)(50226002)(62236002)(68736007)(44716002)(84392002)(2906002)(4326007)(86362001)(81156014)(8676002)(6666003)(81166006)(4720700003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1560; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; DB5PR07MB1560; 23:z1xwjSvgXGVWre2oDUjdlejFr0tnA1LVgQYjoBd?= =?iso-8859-1?Q?WcUX1zT/wwy6jAhCxLgJrZJ5FriEqY9Shrh04rw1mzoyoJQ8cS55cH6Lwm?= =?iso-8859-1?Q?p9jLokDiF2+Cb0lMlkE0E4IMBEIeEDLKUNPrOcP9Szf/FsKE6aCaAFTbDk?= =?iso-8859-1?Q?ooAVGz4iHOY/pNGhaKMUfOn+4+ER9xmiKVwNDTujA3581uu9Tsr6T9zRJs?= =?iso-8859-1?Q?yf4nm2QrF9Be3tU2wVNj3ENP1DMTqUwUj2+FWLQ/YBr/oIyKd6brH3Jlv6?= =?iso-8859-1?Q?CSLCh9AnUh5xCQz7SPsKyUk7O7vQWb+hBpwyinqLO5OLkYSgzNBjdPzxxi?= =?iso-8859-1?Q?0haN1g1R/aflEfYqnvu8365tZzKu/yNUxJKtP1nElA3t/xz26ULPswe7Kp?= =?iso-8859-1?Q?YkPbVFD47BB0i+mNuzBYKcX4/XxK3cnmMXbj5sSEq2IHiyRd5tS6T0XUrM?= =?iso-8859-1?Q?6tiKyi+S4bePp9bKpm/GYyfegp/Zb0bu3Tq0wqs+td1H6hXpPTT8pLNNDu?= =?iso-8859-1?Q?8kosAPUoky6r7mwxohJndMcXAT+J0K+CTvErvghb5aHv3YX1eqA91Cqvf4?= =?iso-8859-1?Q?XgPZZsORVABqURc3TTe/73U27RcgUCu6B+o8k0yXFhgK64EsnWMc4Cq/P4?= =?iso-8859-1?Q?s8x8t8zJjtC9EquBgfXankAU4TkGYxyFjUbiuoOJPLX2Ufh93PnsjB+xTg?= =?iso-8859-1?Q?fumCEe+jw0Is3xmJc9n1MwWA63OR9ceY4YO9ZC021iuRcs99nNBn8WfnQF?= =?iso-8859-1?Q?r2HKEEMngZUwnEPTZferDnjCfaeFskIu9Z8lmHXKAmLvioovRoozToSYsz?= =?iso-8859-1?Q?/JUqiJV7gvklSKv131BcDDMqWeoj4Tg1RVzybPk5hDF4B0/0cNHEXrux0h?= =?iso-8859-1?Q?mVrwndMuwtXdqdz+06Q1z0IvHG0PyXhgSM2+AwMGeQokjwb0Xy8HMkrIj4?= =?iso-8859-1?Q?qmUt5PUq96raOGwEawquDhQfufBp+GOKqdaPEc2sK9DndlEUVK1uSi5kUR?= =?iso-8859-1?Q?NnUy/eiwDt8pHH8c5qutXojDVFkA1nlRNuzmy4hV5m10OJO4tpYMpsM3Dx?= =?iso-8859-1?Q?ZwU8i03TiknihMKfI1lDbxDfioP9HgR17MIt/kxbhX/ibALSFu933alHWR?= =?iso-8859-1?Q?YkylMQcPXTXBXmIcBAHrgDAMWOCHdp2RojGb5xw2Ent4N2YfEgsWkYmnnC?= =?iso-8859-1?Q?i3tx7NyxYVyKQMl8hbRlEvL6MixiNg5kLzeB2ZKcBVZmrMHp+m6g9T7Kae?= =?iso-8859-1?Q?ZZAPHYcKRZNmbk//g60ZdSGagMk8anUY8KZzoW9XOXRm9RtoUvF7jREsy9?= =?iso-8859-1?Q?dh7uQfQ+MgHjxizJ8zF2F0t1wt8r7X7PawhvpNfybyQstgqDtVz9wA/UOO?= =?iso-8859-1?Q?6HemAgeICzV9lQPNN1hWa5uFOtUtGwn/NIQ66bL02tuaF1H75mB20wagpy?= =?iso-8859-1?Q?YtZ6yyz99oKpshLFEYBKMs3tDPCyyVtl4EJ4weL2cwu9jeqs3eaGvf4BSC?= =?iso-8859-1?Q?5b8RaGZ+NXxIiCl8/SIbt9iYCrGypopnc+PfKwNXy?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 6:rI4IigcS8TrZOzdEibq8MbZ2OqbmSquK2Mcur7uvk47VTxFPjbm+JZuHR1DWW+png83ikf3ihReuDsYNFuRR3otuamtWTAUFSU9rydYrAIEBbHMIWWQrRW/9K1pfgVwcKH75oTLCCHPJnEGClsEhwsyQi3IlXkkibJYFoBY+3EXmWcdkYvvFSBKuUURiQd26Wiqs7Y+xtdeHPHeQH55l5BVx06HulKarR9Sz8LBOFehNVlbdtslbRJiL278LC9qnc0vcLlnnMXv+zPjHaaj0jL6sUNTk2aZrMwqrSFDSj1s+VuhfO8qMWTWrm8nKWK+L5R5nxgIbageplEAINf3xTjXb24CeqvAdztWpM0uWnc35OK8Aay5PRejCVak7Olris4sAcKQnuJsgwfgcQJpAyw==; 5:nzCC6RfbciX/adhu2o1Ir3l0EmtfpHstrEw9cJnv0EYtkONbCTJO/v3gJ6ekkJTM62aeoWcjgnISiikafjC4pZ/91gwsHB9HLsqS+uuBABzwt8WfynIu9AzqZO7Cx/wbv2cl2Ho0MD41WP4Y1X+KJw==; 24:H2NQCN9fE1w489WY/xI8Jlv6xbBExE1R5EzjG84I5IHPEP8Lw7EIcy4DjVt3NBbS/XFHI2jNfiwo+oZ9N/nItbYR7BJzLzpFsMRAY7dRPd4=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1560; 7:HCdQfwKs5uNmpK73ta7TrtD4FL8MErYWzPtjnX5n74C5u1g3JDxC0qFHfISjRrNobDYMUalpugDmYSEeteNx2gfrk8tuGDD2SKH28jNSy9hJNGhTBYcRZMrtdcTIpeNtjyXSBfoHjIzcqyq5JMwFvjfxYu2ud8oTB6VtnurIrzdBxh16duTru3Ie4kXy2cs5ybVhBEoIQQGa32I7Q/U1e9kepxvXdLZJ5NuFPGc2hC5CpPCAMhOYyrQeqAFulWoiIR/yreba7cJ6pYQ7WtujycAYofTmz/BSTBuNINAZJ1yMmrDMQ51i2v87iT51pyliaTuZfK10srAR6PyQrtePkQ==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Feb 2017 09:53:58.0185 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1560
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/quXTH0Sklw4KsBd3ZtzmsBox5pU>
Cc: alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 09:54:03 -0000

----- Original Message -----
From: "John C Klensin" <john-ietf@jck.com>
Sent: Tuesday, February 21, 2017 7:20 PM
>
> --On Tuesday, February 21, 2017 12:04 -0700 Peter Saint-Andre -
> Filament <peter@filament.com> wrote:
>
> > On 2/21/17 10:40 AM, John C Klensin wrote:
> >
> >> How would you
> >> feel about making the phrase something closer to "the basic
> >> Latin repertoire, i.e., the letters and digits of ASCII as
> >> described above" and moving the RFC 20 citation to the first
> >> use of "ASCII" in that previous paragraph?
> >
> > OLD
> >
> >    In order to make URNs as stable and persistent as possible
> > when    protocols evolve and the environment around them
> > changes, URN    namespaces SHOULD NOT allow characters outside
> > the basic Latin    repertoire [RFC20] unless the nature of the
> > particular URN namespace    makes such characters necessary.
> >
> > NEW
> >
> >    In order to make URNs as stable and persistent as possible
> > when    protocols evolve and the environment around them
> > changes, URN    namespaces SHOULD NOT allow non-ASCII
> > characters [RFC6365] unless    the nature of the particular
> > URN namespace makes such characters    necessary.
> >
> > The term "non-ASCII" is defined in RFC 6365 and seems perfectly
> > appropriate here.
>
> Wfm.  Tom?

OK (after some thought).

As you surmise, I am not familiar with 'basic Latin' as a term of art
and did wonder if that was intended to exclude digits (since they came
to Europe later, with the Arabs).  The NEW text clarifies that.

Tom Petch




>
>     john
>
>
>


From nobody Thu Feb 23 02:21:01 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4686412969B; Thu, 23 Feb 2017 02:20:59 -0800 (PST)
X-Quarantine-ID: <qT5hQXrgLfqc>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
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 autolearn_force=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 qT5hQXrgLfqc; Thu, 23 Feb 2017 02:20:57 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id 018431294B2; Thu, 23 Feb 2017 02:20:55 -0800 (PST)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1cgqW5-0000MkC; Thu, 23 Feb 2017 11:20:53 +0100
Message-Id: <m1cgqW5-0000MkC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> 
In-reply-to: Your message of "Thu, 23 Feb 2017 09:41:43 +0900 ." <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> 
Date: Thu, 23 Feb 2017 11:20:53 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YSJMNQsIgeZp0JLiiBH1RF-qzgw>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 10:20:59 -0000

>> Nobody is saying that /64 isn't extremely widely used where it's
>> appropriate to have a portable fixed length IID. Set the default
>> at 64 and trust operators to change it where they need to.
>> That's realistic.
>
>As a host developer I strongly oppose that. It will make life easier for
>network operators but make life harder for host OS developers, host
>operators, and host users.
>
>And it is absolutely inappropriate to change this now in given that the /64
>boundary has been the standard for the last 20 years. It will break
>deployed code that relies on the current standard. (That includes concrete
>code I can point to that I know runs on tens of millions of devices.)
>That's not acceptable to do in a standard reclassification.

Lorenzo,

I'm curious about the issues the host developer faces.

It seems to me that there are three basic ways of configuring addresses:
1) SLAAC
2) DHCP IA_NA
3) Manual

There is of course also DHCP IA_PD, but I'll leave that out for the moment
as it is not directly relevant to IIDs.

For DHCP IA_NA, the host should not care about the length of the IID. The
host just configures the address as a whole. Not need to look at the prefix
length.

With manual configuration, again the host doesn't care. If is possible that
manual configuration is done using IIDs. But combining an IID and a prefix is
not magic. There is no reason why manually configured IIDs whould have to be
64 bits.

Then there is SLAAC. I'm fully on board to say that SLAAC should require
64 bit IIDs for ever. 

So it seems to me that there are operators that want to use longer prefixes
with manual configuration and you want to keep SLAAC at 64-bit. That sounds
perfectly consistent.

I can't think of any reason why IA_NA or manually configured IIDs would have
to be 64 bit. 

So a text like 'implementations MUST support 64-bit IIDs for SLAAC.
implementations SHOULD support other lengths for other ways of configuring
addresses (IA_NA, manual).' should work. Or did I miss something?



From SRS0=0eqy=2E=darou.fr=pierre.pfister@bounces.m4x.org  Thu Feb 23 02:24:43 2017
Return-Path: <SRS0=0eqy=2E=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0055129602; Thu, 23 Feb 2017 02:24:43 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 eJ5jmkDRCKpR; Thu, 23 Feb 2017 02:24:41 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EFA0129669; Thu, 23 Feb 2017 02:24:41 -0800 (PST)
Received: from ppfister-m-ja6k.ciscolive.local (unknown [80.157.70.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 73D105647A7; Thu, 23 Feb 2017 11:24:38 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
Date: Thu, 23 Feb 2017 11:24:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <A1F60D51-C39E-45DC-B3D5-960D92C186E4@darou.fr>
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org>
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Feb 23 11:24:38 2017 +0100 (CET))
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nYCBLppPDt3M5GeRvZ72UKCjpIA>
Cc: james woodyatt <jhw@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 10:32:38 -0000

Hello all,

> Proposal:
>  IPv6 unicast routing is based on prefixes of any valid length up to
> 128 bits [BCP198]. However, as explained in [RFC7421], the Interface =
ID
>  of unicast addresses is generally required to be 64 bits in length, =
with
>  exceptions only provided in special cases where expressly recognised
>  in IETF standards track documents.
>=20

The only place in IPv6 standards where the 64 boundary is mandated is on =
the 2000::/3 rule.
There is not a single implementation or deployment of that rule. There =
is no instance where=20
trying to configure a prefix of length different than 64 will work when =
the prefix is within 2000::/3, and fail when it is not.
That is a sufficient reason to not include this rule as part of the =
standard track.

Nevertheless, SLAAC over Ethernet links indeed requires prefix length of =
64.
As documented in the RFC7421, there are a few examples of protocols =
which require 64 bits long interface identifiers.

SLAAC is not the only way to configure IPv6 hosts though.
Manual configuration, automated configuration, and DHCP are all IETF =
approved ways of configuring IPv6 hosts.=20
They all work with prefixes of various lengths.=20
Does 'special cases' in the proposed text covers manual/automated =
configuration or DHCP ? If so, it is far from being clear.

You obviously should use /64s if you want SLAAC to work, as well as =
other protocols which are documented in RFC7421,
but /64 is not the rule, it is an architectural consideration that you =
have to take into account when you design your network depending on the =
protocols that you want to run there.

Therefore, as far as this discussion is concerned, there is no reason to =
mandate 64 bits boundaries as part of the IPv6 specification.

- Pierre=


From nobody Thu Feb 23 03:07:52 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CBD7129480; Thu, 23 Feb 2017 03:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.788
X-Spam-Level: 
X-Spam-Status: No, score=-3.788 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id erRhCLcU7KtW; Thu, 23 Feb 2017 03:07:50 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20108.outbound.protection.outlook.com [40.107.2.108]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83A421296A0; Thu, 23 Feb 2017 03:07:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=5wMUoKURpM9lo5EdXtTZs/en4yjSlpF1tZmpOsC4JtY=; b=dybUkBeQOoB2NHwVVZzpOQY3cF1bfyNkQSiFoYj1Qn/m3luO8h4KpNiDlkH/YkeYwoBD89vOX94+70Ti3yqorNl4P5wvBekAhHivwtT8hgPh3jLja7xDMlBZw47mvuXWF50IQV7t9GuLBp1fSWER2qO1TM/l/mU06US3HnINcZQ=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by AM4PR07MB1553.eurprd07.prod.outlook.com (10.165.249.9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.7; Thu, 23 Feb 2017 11:07:46 +0000
Message-ID: <050901d28dc4$ae385700$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com> <m2vas1ttsj.wl-randy@psg.com> <CAKD1Yr3cZxsFqkLf=obAngCp5W-1EMnn4bsx-JcvaEaHOYTOCw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Thu, 23 Feb 2017 10:44:53 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: AM4PR0101CA0056.eurprd01.prod.exchangelabs.com (10.165.22.152) To AM4PR07MB1553.eurprd07.prod.outlook.com (10.165.249.9)
X-MS-Office365-Filtering-Correlation-Id: ecb899a4-6785-4580-bae2-08d45bdc32f6
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:AM4PR07MB1553;
X-Microsoft-Exchange-Diagnostics: 1; AM4PR07MB1553; 3:zn8zwPFqb+z7Vkn75VLhvcA/pEo83790F69BzsJfdMuFtTviUPaO9hPkMRn/Q7Ri1v/f7bNlGipK4cz82Gml87Swmcy2UvWSKwZjkjvX+1WG2J0RhWDAxqodOM90YYI5SOTk1+Hozb2wqJAGOujSWbfiwVMqM1EmNH6HPzaEbE+CTENkVT0rTks9LMHOaUwsC3YFZD2/hAnkd8eodlvAc10QQqoi7mdebMw2+aN6ssU4hIU4x9rnOS6t6Zt25BNHs2n9wE7HnoImROj3animtQ==; 25:FWjwfNKT8RcE2QM4WnplkgTsoZqydUg8JXJnB7a/24w/29qohL3ZB1PcOKpf0va1p13AoulJOF1riAd485HvoaqaRmGBvMv0E4aj/aknBJK5aVvrly8kVhg+WM2u82P9he9YeLtEH0YfDkLfcJrYv8Pa7/dTL/o5ONFc1/x84sEBLjEZh0z7oZC9SdW+dZwu54gnjNQcB/agibb91opGAi3Icf4hggWXEXLDLHmts7toZrBXIWAvj59EslZUmjXwRQq2Mfwm5rgFEQAexyowg86XRWISQF+lhoPho071ASHyWFdmv/I+D1tjn8yOnEvLj5/HyTefB/P2SAUzrjOfFzlRKJT0X0CqqvuOCiUPARQtUJ9sIDgdRH8v84MOghIvd0sZBhEct/9RQeUBdgHzgOI6ad1+D5sos2dhZ61vVpFCz25pMOaSW4WkuYjgbuuxr4fs7fnps374GUxL1FSCZg==
X-Microsoft-Exchange-Diagnostics: 1; AM4PR07MB1553; 31:Z7kYqCVsnG6xHVT7JqlpAYiNjrHh6BqLMgsN5ztD0EQrLsethrwcY1GnIIbx3dV8hJ5LPMGl8nkUf/1/qmHidxkNzyfFpPCeOp4T9oaXk2eyxPc9GchRDd1zsoyhZ2gIm+En6D9EjLYB+9FhSkjyjfhq6JsP/ExrO0cR1m83edI92ZPIMnvtkxJO8WBbtxD0M/KadI0lFpqCc8n3la7y4MD5BbeabqbOmSM7Wz1ryrOw0fxsvQAWTAeZzQQ3ziKU3cyelp7OLkdPkCoiXzc8AA==
X-Microsoft-Antispam-PRVS: <AM4PR07MB1553FC21BC0A8EF3C8BC7AE3C6530@AM4PR07MB1553.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(211936372134217)(100405760836317);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123562025)(20161123560025)(20161123558025)(20161123564025)(20161123555025)(6072148); SRVR:AM4PR07MB1553; BCL:0; PCL:0; RULEID:; SRVR:AM4PR07MB1553; 
X-Microsoft-Exchange-Diagnostics: 1; AM4PR07MB1553; 4:BpIr6fWj7zoG4wtfrGpuXuWx0kN0Yojyiz288XK6fRW+P1ekambQjTJES9aPHJBKexk9UjDkKGt1dU702NFyt3z+3v0Lv44Y7CAppId3uw6+7vGaE9EZvNTjr9ecPYbsj6/zKNOZW+w0q20qTbwlFonQH+EWhjgzLwsrWCv60k/cDmmsLMdc6RSH9MctxIqVnk/0KYdcehl9owxkFL6Jgj5w8ubOMj8NbHe5prVWzTs8mEsLLVACBXMPp7mlCfW8acNSHHvfmFivSeVh9Umc+PhWJk1MZBNd+bYKwUazJ5yzynqjAzuw3F5jjH6lTY8h8NWdjuoUadAF++EziI1U3z3Q+c2MIMBrsLepgAfAk1q+fb87mCPZ26iath83N5jvctjtZd8aPILDKzmOSBKKkwum0nNnCczn3wlJ092D8zazOVpMrOlCjUfHDcx3MpE61BD1l7D6q3zbmfMic8PDfJwFYDHD/ZCdHWI4jfJ2GUfqPfYj9uKHQVO4zxViCTAyTcyc9Hglvm+x77f4ggaWPFwIOA+GGUzPFTamOZm80S/I6a3wl9YOzXHtk5HqyDbY2LDdfCO54MvO6LrRpx4gKVKfNwezv6ivcKadOWSeUhBy0n2NP0JETA89Q5Lyh2u62+kARJqM+CKI5IVRE/AZYGPc8/F83P+qZpenF7HvILsB86uCpagOqayg5wXo65pG
X-Forefront-PRVS: 02272225C5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(24454002)(54534003)(189002)(199003)(377454003)(305945005)(7736002)(230783001)(68736007)(4720700003)(61296003)(8676002)(5660300001)(53936002)(50466002)(6116002)(6916009)(101416001)(6486002)(86362001)(84392002)(6666003)(42186005)(50986999)(76176999)(25786008)(3846002)(44736005)(4326007)(230700001)(81686999)(2906002)(81816999)(44716002)(14496001)(93886004)(47776003)(6496005)(1456003)(81166006)(92566002)(38730400002)(105586002)(106356001)(81156014)(23676002)(97736004)(62236002)(50226002)(54906002)(116806002)(53546006)(9686003)(189998001)(6246003)(33646002)(110136004)(66066001)(229853002)(1556002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB1553; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtBTTRQUjA3TUIxNTUzOzIzOmFtamp2VW1NNEtibjdPSnI2bUJIaVB4azV3?= =?utf-8?B?ZWxXWkliSUY4WlV0VUxIQk9JeTc0ZHMrNWpBVGdUcGx4dTRhMXBNUjRROG5w?= =?utf-8?B?dzl0eHJLMGFjcVFDb3hiRTlNRU04OUFqVEsxcFVUTlRySStNV2VMY1BtbUlr?= =?utf-8?B?UERCTDduampTLzZjRWdWN2llUzdWQzNVWitJRHBQNnUrNXNxUUhkOFZqNHVC?= =?utf-8?B?aDZqcE1LaXBPa1VxbUJIWEJhUjREdjZ0d3lVUXNvUmtPK3MyWnlvR2NydGNY?= =?utf-8?B?eWNqUFBGek1pWjhDQklGU1FmMmorYW5JODB6N3lkeVJJUUNSR1hRamdXVW4z?= =?utf-8?B?Tm1GVlhIT2MwYWJjZEpvVGFQNHV3T2Z4elRyQzBObmVPTGFlRTdrb3I3dy96?= =?utf-8?B?d2ZtaDRDcitzcloycVhEbUZpdE1uM2V6NC9EZEN5RGhsTUVEemN4S2h0T2tO?= =?utf-8?B?UjRneUpjMmJjcFA1RWJncnpQYktBV1p2N29JZ3pOYm93blBsb1dUYkdGUm9N?= =?utf-8?B?OEw4TjEwRUIzZFM5Z2Y3VG9rQVphdFFQSDJ1VnNHUGRxMzlaMEE0aDNyUDN5?= =?utf-8?B?ZzBPaEFYdGxWb1EvL1l6QzZFWDF3TmI4OFRrZ2cwc3lyTytFUW5QZmo2NW5n?= =?utf-8?B?Q0IycmptRjJpZVRKQTRDODBKYWtMQ0lNZVlNaTRGeHIzRWdPOU1KMkxmdDha?= =?utf-8?B?WTdzbnZDZjJIa01COG8zUWl1dDhydTEwSG12REZaK2o4NjhpYmlDS3RBQUl4?= =?utf-8?B?dWYwRFcyNlpyR2JsWnZ3OHVmOEJFeGFMSDd2Ri93OEZvNDNaTGpqVjlsb0Fn?= =?utf-8?B?TWQwbEx2bFhiZ1IyMTdzQVd1UGZGRmQ0Kyt0RDdyeUloUWc3bUVraXdaZzFG?= =?utf-8?B?bHZJYVV2bFZnQnhaMDVYOUhxR3N1aEp5MkkvY0VtblBna3gvblBzVVpjZzlp?= =?utf-8?B?VWlmUU5aaUtwTkxMc0xtSGNUN3ZDSG40Rkw2R0NZT2tUWnZXZkhReGp6LzNS?= =?utf-8?B?R0M0YTJocGdZdWloOGxVUWpHTWpMYU9xUUlWQkg2YzllMnlaWlAzMVB4NzI5?= =?utf-8?B?dkdXY1h0dGNTamc0L3JyTW93OXpleFVFUFZtRG9GN2VhU2pDblhuWFNFWXcx?= =?utf-8?B?WE5RZjBZdE4xaVVqc1JxZkhrOUlUS3hsckhMOXdySFhaaU1aRUJNaHY0OFhF?= =?utf-8?B?TlpwNVJaZ2VvVHZrMGw1VHBJUFY0REJYS0VEdzhZdnM3WWNJY3Nabk9VOWNY?= =?utf-8?B?YXRQSVMvUldSR0wxMW9PbE53ZmIvRkF6RmVvT1dTYXY0QjF4K2JJeFhQWVFi?= =?utf-8?B?c21Md0VCRjdrTzRaeVRqcjdlTjRwZFQzTDNwL3dYWVlmeDlJRlM5TEx4c1k2?= =?utf-8?B?VWhzWXhvRTloNnJNbUhTTmNnUlp6UERiMEdoak9yZWRLQkUxYW5zOWh1bmM2?= =?utf-8?B?SlVKTVQ3VmhzbjdBdm1IU0lEcjM2TUVBRFk1bTJZaHZrYnFRUkhaRXlwdkR1?= =?utf-8?B?TjAyUHR6dHhyMXRITWJ4c3JReEZLbnozVVhLWnFGalk2aFBqMkZJOG5paFZv?= =?utf-8?B?WWNNdGxCcFZTZXpZMFlFL2xXZ1pIUm01Yi9pNUNudHFhc005cnNKazlEZ253?= =?utf-8?B?Yk9qc1hhbmtUenVPSWpyV1ZoRWVKL3BKSGNrWm9ydVZJOEhDOS9STFBNRm5K?= =?utf-8?B?dmZvOGdLLzZxd2NNQ05GM0hCMVFYbnJjNzlVTHNLYmg0WTI0b2lySTgrdm5Z?= =?utf-8?B?dDQvbVJRU0p6Z014QWx5Q0F3ZHVmcmY1eWJzS2F5NXVwQmdZWGt1N1dEYjRV?= =?utf-8?B?T2xQcjhaeGRzU3lJOVNTWnYzREcwMWVQb21jMnJDdktlWEV0Y3ZBdElSSzRO?= =?utf-8?B?YzUwWUpjZkJxa3A1VkkzbHFyTWVKYlNtZTFEc25KV2lpZ1NUZGU4Qmg5bFk5?= =?utf-8?B?Umk3U2dVbkxmRmYzeTRDZ2pUS0lYWGd5aUV2K0daMTlnanVPdU5FVDZiUEdu?= =?utf-8?B?K0FFNW1JRldXcVVpanMyWUtjMDlOUU9wQi9aRmtrZ2d0RncwMDNPTnpqVVo5?= =?utf-8?Q?KBPd+eGUy3532x9bsYgDCzXCg?=
X-Microsoft-Exchange-Diagnostics: 1; AM4PR07MB1553; 6:xGYuHE9+4hSDaQ/E7f9Ahsby3j36fHei4mNUh/RXMJIbusk455DsScxpQkJ1ra2CnPSp2w9gpHxFafInoQnQ6vaMP4TOJsaJig1CGIQPRrI91n34srjjrCVOJaLkpL0NeJ1fr0N4pUPIKGQPcCykDJDKz04CQvjR0C03QxJStzm12ISNm/j8WE0tplsRCVq26hSrt9tKc5SHERm/xey0v/VIuqPnUzbxnziNyz0+SD3T/uOhFwGeqz5xmA3h3OQk4b0xwx9kBuSN8fKohqFAp8MANwlsP+UK4Mg34GdhebxLU59UA3fKHVA27bOdD4FvPVANSzA0gXe9eJ5affSL3M4q/OJ85vZihU8C02FJgZFrO/phqnHt3+EnRihr1HJ33UOVAj+9WItA51KxKYPSvw==; 5:0tZBt/sya3rKMJhPNCh9MevlmNX0FoFZ8Vv5DGaEKqG8AeNAmZu9PtJbXksfB+lOxqPgzqC186h4jbPL4w5lYjbDomENZYwhYhg2Krh/MARvzwHg8RIw4KisPrlxyOR9rawc4CLhlf5ne18D4QwQmw==; 24:fbHIhyRLXwCXXDo3aM6Bg/oe1Zv2zSMKNJJ3EJ2/h5diToC+TlI+JnBmuiWaZHztEd+dv91y9u7tzc1Iot50Hq5Ae8LIZKUrMVhIP4yVwDo=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; AM4PR07MB1553; 7:xmFErFGcWh9UM2R0ATutyfOXs9+GIQ1N11aDiqYy5VPMFEiSlOhQq48h5WjH9s5Pp3aYftelpPa8I+K2qRXndfCc7wwb0nTgRgGQQDOh3NWkwmWDVE1B2hCURtm04EG+se6656yWKjKoTQzqQQe0SET7etWC1obJ3hCDrPop2crGN94VJZHTEsRbVGhNVym2JsQVGAN08YB+wONuFoGPKPzdXQy49Mb4e2YsrmBv/0wde6YDN9wjFzwApWSL5CgdT71X6s89FBkxT1ueJ/M8Ckm2DO84n3VIbVhnPsRnzxcT9FGGciga2LfVXnSxbSeMh9DD3eu/mcmJFXPo4KHtpw==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Feb 2017 11:07:46.8295 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB1553
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yp7rIIF7JsXFqEk0lRNkseMGQkc>
Cc: Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:07:51 -0000

From: "Lorenzo Colitti" <lorenzo@google.com>
Sent: Thursday, February 23, 2017 6:05 AM


> On Thu, Feb 23, 2017 at 1:28 PM, Randy Bush <randy@psg.com> wrote:
>
> > > the IETF and 6man absolutely have the ability to change the
standard,
> > > but it should follow the proper process: write a draft, get
consensus,
> >
> > that is the process we are currently in.  but there seems to be
serious
> > disagreement over the draft.
> >
>
> AIUI the goal of the process is to reclassify the current
specification.
> That severely restricts the types of changes that are possible. That
is the
> basis on which this document gained WG consensus and reached IETF last
call.

Well yes and no.  Reclassification means that the document has to be
made clear and error-free, erratum-less and I see that as valuable
regardless of the subsequent classification - look at the change log and
you will see the amount of value added.

By now, I sense that the consensus to make this a standard is wanting,
that we need to make a technical change that is inconsistent with
reclassification so we should make that change along with all the other
good things that are there already and recycle it at its current level.

Tom Petch

> If we want to say that we're no longer reclassifying the current
> specification but are instead opening the door to bigger changes, then
the
> document should go back to the WG for further work because the
existing WG
> consensus was based on the stated goal of reclassifying the document.
>


From nobody Thu Feb 23 03:37:54 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC5E12A04E; Thu, 23 Feb 2017 03:37:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 myZ2BIyrN23u; Thu, 23 Feb 2017 03:37:48 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 30830129FD4; Thu, 23 Feb 2017 03:37:48 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgriC-0008wi-SF (job@us.ntt.net); Thu, 23 Feb 2017 11:37:47 +0000
Date: Thu, 23 Feb 2017 12:37:05 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170223113705.GJ89584@hanna.meerval.net>
References: <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dUKCRP6yVffaeLS3Tsp3gz-Wy9s>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:37:49 -0000

On Thu, Feb 23, 2017 at 12:56:45AM +0900, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 12:31 AM, Job Snijders <job@ntt.net> wrote:
> 
> > rfc6164 and rfc6583 are great examples that document considerations
> > regarding not using a /64, it simply is not always the best fit.
> 
> RFC6583-style attacks (of which the class addressed by RFC6164 is a
> subset) are low payoff and pretty easy to mitigate using very small
> changes to ND implementations. You can solve most or all of the
> problem by using per-interface ND queues and prioritizing existing and
> gleaned ND entries over incomplete ones. You can do even better by
> pushing the filtering away from the host so that you don't have to
> carry the packets.

The perfect solution is always just one upgrade away! :-)

> Also, bear in mind that the interface ID length is *not* the same as
> the prefix you route to the link. Given that you're talking about
> static configuration, you can perfectly well configure all the hosts
> with /64 prefixes, but give them addresses that are all in a given
> /120 and then route only the /120 to that link. That will also avoid
> all the attacks.
> 
> It also makes configuration much simpler, because you don't have to
> touch any of the hosts when you run out of the /120: just increase the
> /120 to a /119 on the router and move up from ::ff to ::100. That is
> 100% supported by the current text of RFC4291bis, which requires that
> the router forward packets to the /120.

Thanks for sharing this Lorenzo, it something I did not think of. I
appreciate the cleverness of this trick, just as much as the next person
appreciates this funny photo [2]. :-)

However, while the trick can be made to work on Linux, it does not
appear to work on Cisco IOS XR, JunOS and OpenBSD. As such, its no more
then a party trick, and cannot be considered as a supportive argument
for an Internet Standard.

For the benefit of the working group, what Lorenzo describes is the
following in linux-lingo:

    $ sudo ip -6 address add    2001:67c:208c:4291::1/64 dev eth1
    $ sudo ip -6 route   delete 2001:67c:208c:4291::/64 dev eth1
    $ sudo ip -6 route   add    2001:67c:208c:4291::/126 dev eth1

    $ sudo ip -6 route show dev eth1
    2001:67c:208c:4291::/126  metric 1024

    $ sudo ip -6 addr show dev eth1
    3: eth1: <BROADCAST,MULTICAST> mtu 1500 qlen 1000
        inet6 2001:67c:208c:4291::1/64 scope global tentative
        valid_lft forever preferred_lft forever

I also fear that the moment "disunited addressing & routing" become
commonplace, you'll find your devices on the dirty end of a
'/120 routed + /64 addressed'-link and have a dysfunctional experience.
As far as I know there is no way to signal host "only a /120 out of this
/64 is routed".

Kind regards,

Job

[2]: http://instituut.net/~job/ietf-6man.jpg


From nobody Thu Feb 23 03:43:27 2017
Return-Path: <wilco@baanhofman.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1BB01296FA; Thu, 23 Feb 2017 03:43:21 -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 autolearn_force=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 MY9Ewklz1d9D; Thu, 23 Feb 2017 03:43:13 -0800 (PST)
Received: from vps.baanhofman.nl (vps.baanhofman.nl [92.222.219.102]) by ietfa.amsl.com (Postfix) with ESMTP id 90DA812A164; Thu, 23 Feb 2017 03:43:13 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by vps.baanhofman.nl (Postfix) with ESMTP id 6AFC51041AB5; Thu, 23 Feb 2017 12:43:12 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at vps.baanhofman.nl
Received: from vps.baanhofman.nl ([127.0.0.1]) by localhost (vps.baanhofman.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRFjLQz-RiNP; Thu, 23 Feb 2017 12:43:10 +0100 (CET)
Received: from [IPv6:2001:610:120:3001:5d68:ec82:edc8:5d71] (unknown [IPv6:2001:610:120:3001:5d68:ec82:edc8:5d71]) (Authenticated sender: wilco) by vps.baanhofman.nl (Postfix) with ESMTPSA id BB1B31041AAD; Thu, 23 Feb 2017 12:43:10 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>, ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m1cgqW5-0000MkC@stereo.hq.phicoh.net>
From: Wilco Baan Hofman <wilco@baanhofman.nl>
Message-ID: <fb53226a-f798-5a61-afaa-99456d7e9000@baanhofman.nl>
Date: Thu, 23 Feb 2017 12:43:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Icedove/45.4.0
MIME-Version: 1.0
In-Reply-To: <m1cgqW5-0000MkC@stereo.hq.phicoh.net>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NpA95HFXSvAaBS2tENK7dlrgUFGFAUHIR"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BTESskOlZEw3xwdRWTQwLSMPb5k>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:43:22 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--NpA95HFXSvAaBS2tENK7dlrgUFGFAUHIR
Content-Type: multipart/mixed; boundary="lT9XvsiNbPiU2BhqEfup4kBvt5wnbTHNM"
From: Wilco Baan Hofman <wilco@baanhofman.nl>
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>, ietf@ietf.org
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org,
 6man WG <ipv6@ietf.org>
Message-ID: <fb53226a-f798-5a61-afaa-99456d7e9000@baanhofman.nl>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6
 Addressing Architecture) to Internet Standard
References: <20170221001940.GB84656@Vurt.local>
 <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com>
 <20170221101339.GC84656@Vurt.local>
 <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com>
 <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark>
 <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com>
 <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com>
 <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com>
 <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark>
 <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com>
 <20170222144147.GC89584@hanna.meerval.net>
 <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com>
 <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com>
 <m1cgqW5-0000MkC@stereo.hq.phicoh.net>
In-Reply-To: <m1cgqW5-0000MkC@stereo.hq.phicoh.net>

--lT9XvsiNbPiU2BhqEfup4kBvt5wnbTHNM
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 23/02/17 11:20, Philip Homburg wrote:
>>> Nobody is saying that /64 isn't extremely widely used where it's
>>> appropriate to have a portable fixed length IID. Set the default
>>> at 64 and trust operators to change it where they need to.
>>> That's realistic.
>> As a host developer I strongly oppose that. It will make life easier f=
or
>> network operators but make life harder for host OS developers, host
>> operators, and host users.
>>
>> And it is absolutely inappropriate to change this now in given that th=
e /64
>> boundary has been the standard for the last 20 years. It will break
>> deployed code that relies on the current standard. (That includes conc=
rete
>> code I can point to that I know runs on tens of millions of devices.)
>> That's not acceptable to do in a standard reclassification.
>
> I'm curious about the issues the host developer faces.
>
> For DHCP IA_NA, the host should not care about the length of the IID. T=
he
> host just configures the address as a whole. Not need to look at the pr=
efix
> length.
For stateful DHCPv6 the prefix length should also be /64 and should
allow multiple addresses, at least in my opinion. And I have seen
several devices that only allowed configuration of /64 prefixes
(printers, etc) for even static addresses, which is a perfectly valid
assumption right now.

So we see SLAAC, ILNP and NPT66 requiring 64-bit prefix length. But
these cases all cover edge networks, with hosts, printers and similar
nodes. Keeping the requirement (or moving to SHOULD) for edge networks
seems reasonable to me.

However, this does not make the carrier use case any less relevant. The
main problem with /64 is TCAM exhaustion through ND attacks. Because NDP
follows a multicast discovery model, it simply does not scale up to 2^64
addresses in a subnet when being scanned/attacked. A subscription model
(like WiFi proxyNDP does) would scale a lot better. This is something
that needs to be addressed as well, separately.

Another problem carriers face is that /127 can not be configured on a
lot of routers, because of the subnet router anycast requirement that
was only lifted for /127 with rfc6164 in 2011. That means that
operationally people go out-of-spec, because frankly, going out-of-spec
works more reliably and consistently.

And because /64s don't really work for inter-router-links because of the
attack surface, and /127s don't really work because of older routers,
people will start configuring /126 for inter-router-links and /125 and
(slightly) shorter for VRRP and for BGP sessions with multiple routers.

In my opinion, there should at least be some room in the IPv6 standard
for arbitrary prefix lengths for interconnects.

-- Wilco



--lT9XvsiNbPiU2BhqEfup4kBvt5wnbTHNM--

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

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

iQIcBAEBCgAGBQJYrsrZAAoJENNgJ82k1pS90YkQAIwulQmp62RRDTC43sV2JILF
2SyBi3FVhSh08lc/d10AqIWE1tFsj8QlUlSoazFb/y1vKENJqbQTzcqKWHcMHqvd
SZ4W8Pw2Yj6Q691d9+dOpJuQQTPtinnVY8o62ZKkjLH3RUA+NfTvCrGowPm+q24d
JQBHpo15MA7M4V2YiuNG0AqaXMTMEpFr80sJeSxjAGfUPXpH4GnYkkZ/48QRjEZC
oFM2wDlrAhs1kF1HH68UZFY4zTUJXbYnpzEBwugFJwL7AjWJIeUArPM6vsGA+WUg
9VDSV36x4EWHJZlTlAM6CD6UBT8xbg3rs3E+TsFHCknRmQ1INh7f9gL4C/lqpMsm
3bzhp9WFRxHYRqNefbqwhAIFYgotcf8Lr0/xIUWiwo5d9oJQ0MfngJ1XK4qaHhd3
Q1zMLzreLkyh9sy5bLE4bSkCOb6E4dNWmE6ogcRjzjupYjKaHTJgnvNDiXbLwihf
YoRhQgA87nn4TwVGTl3kuOJDrBNH8zwrviP04iB7Iy6+KHFDtne4E9tQZTnsYOt5
k37I/ahoCe1gU4PPGZ9mjqPHFxuPcRjERP437yvZDp8x/H2P0lUYFPWCYuVo+h89
2PhuYeF/xLOJfWHUP0WvQ46EcYsWem8sTQXAmXXZAwZHkWEQjBMY/gBI8nykyhcy
wbemftrasqGaaXM4bYfc
=KVoK
-----END PGP SIGNATURE-----

--NpA95HFXSvAaBS2tENK7dlrgUFGFAUHIR--


From nobody Thu Feb 23 03:46:44 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A14412A16C; Thu, 23 Feb 2017 03:46:42 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-httpbis-rfc5987bis-04
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 03:46:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9ov8fuZT-zV_BC_6rVu9nHL4lmg>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:46:42 -0000

Reviewer: Stewart Bryant
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-httpbis-rfc5987bis-??
Reviewer: Stewart Bryant
Review Date: 2017-02-23
IETF LC End Date: 2017-02-20
IESG Telechat date: 2017-03-02

Summary: 

Thus is ready for publication. There are two minor nits, but these can
be delegated to the RFC Editor.

Major issues: None

Minor issues: None

Nits/editorial comments: 

Should say

Obsoletes: RFC5987 (if approved) ("RFC" missing)

Extended notation, using the Unicode characters U+00A3 ("£", POUND
SIGN) and U+20AC ("€", EURO SIGN):

My European computer can display £ and €, but not sure if all can or
whether the RFC series supports these symbols. There symbols were not
present in RFC5987, they were just named.

FYI
Nits complains about obsoleting RFC2231 can be ignored
The nits complaint about RFC2616 can be ignored
The nits complaint about RFC2978 cab be ignored



From nobody Thu Feb 23 03:50:58 2017
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEFF812A179; Thu, 23 Feb 2017 03:50:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.986
X-Spam-Level: 
X-Spam-Status: No, score=-3.986 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7Xgwjh097oo9; Thu, 23 Feb 2017 03:50:54 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 3AEF012A167; Thu, 23 Feb 2017 03:50:54 -0800 (PST)
Received: from [192.168.1.34] ([5.10.171.186]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ldspr-1byUpN0Ip1-00j4zC; Thu, 23 Feb 2017 12:50:50 +0100
Subject: Re: Review of draft-ietf-httpbis-rfc5987bis-04
To: Stewart Bryant <stewart@g3ysx.org.uk>, gen-art@ietf.org
References: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <486e7aed-93dc-c942-13c1-d59bbefc6a99@gmx.de>
Date: Thu, 23 Feb 2017 12:50:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <148785040242.20313.16585453406395577753.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:K8mDooFqBPoOH2VhrrdiiMhEXxx3fZdlf/sfb/QswCrbslaX4Dm Rza34bhjN4Ic+92cX92BoW6VX8cq1zP5t6XwUEIiqO92VjF2ak2iLj4RzO9Y8+8XPJjHNR9 4Qn62b8KQTULcRaXKvFNyiWXmSDjQ2drZj/XFOePPKX8d27/KOVLmlBZ4xehMu19B6X0pLt mJE8YdtEBXkSfF2nZKniQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:tiR0wmaq4cA=:/5B6czKWCEqLJetqdcCQrw 6vpKZ/01ZjVr3/mbn8uwEmkKSuRL6B+v1hZTqpyGq7dB71V7+S5XK0WJ/fxEFvHxxKM640uiH URGUcJ56JqCECu+/Wy8l7DXUzeYPZI/m3T94PQ1SuoLpEwe5j8cQziR4+pdpTE2TVnJUibob8 L8vcbdmYc7zjKD5wLbF8uYGgKs4lpk6OyOnbKwYv6jMRh0jyRiCGWWPP3pdj0L6Pe7yesv8W4 gskyj5tilL3qvNYvq0nzNCyHFck7kjA53JOIk7JFX7XDqjL6di2U2Z6H8H+x8nuwi+EawN3EB GnMRCgxQ7S3qqa3u5WzfU5H2SvPSsdcB5QELjKaEWi6fBbv42+NIgoK4bvOVNHALVf6rJLa1k iUzGDjHzcn2ooromm3zrBAVEslYXCBDGcPcoqte6PyVk2bdY4/Pg77KukaaFhAcu9N3RdjGSX FY/gTlkTIgrjjd6X1LYJCcoD9gNsfgiOrKyXw98P81W2rlNKS58rMiJNj6qqHfm6qAvS0keP7 yboEob9Cnquwu9lqVLkNxM/64XynIAV1PLIl5L34Ih0iMz0ljMvJtkaOlWe3x05v7OGIAhZ3u cw/vVJq/lDtbQZ6Y0HMxF48hfpc6uxeidhRrEdyx/ONwkNACW1qe29TLyqw9L71UY8WoGtHMO zsglc6TipCABAm7IJny7YuaMxFcJCzHqFJ0ng1wXSvnIR89a/AiUHNFBhEZ5h2UIHXTMmU9v+ fAV60NdVOtejS1FbMF7ooTeVPu8ue6MFiPVNBxElAEZw+/9Qi7hlBkzmgfDIfmOYKDBiL6fuU Dz3RHgh
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oym5AB41m8buKlOI-N7TFRW9pAg>
Cc: draft-ietf-httpbis-rfc5987bis.all@ietf.org, ietf-http-wg@w3.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:50:56 -0000

Hi Stewart,

thanks a lot.

 > ...
> Nits/editorial comments:
>
> Should say
>
> Obsoletes: RFC5987 (if approved) ("RFC" missing)

No. See <https://tools.ietf.org/html/rfc7322#section-4.1.4>.

> Extended notation, using the Unicode characters U+00A3 ("£", POUND
> SIGN) and U+20AC ("€", EURO SIGN):
>
> My European computer can display £ and €, but not sure if all can or
> whether the RFC series supports these symbols. There symbols were not
> present in RFC5987, they were just named.

Yes, that's intentional.

The new RFC format (see RFC 7990 etc) allows the use of non-ASCII 
characters for things like I18N related examples and contact 
information, and that's exactly how it is used here.

Best regards, Julian


From nobody Thu Feb 23 03:57:40 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54FAF12A187 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 03:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 654PZIXC9Y8r for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 03:57:38 -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 CC2B112A17D for <ietf@ietf.org>; Thu, 23 Feb 2017 03:57:37 -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 v1NBvY50010498; Thu, 23 Feb 2017 12:57:34 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D76272074BE; Thu, 23 Feb 2017 12:57:34 +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 C8C09200B4E; Thu, 23 Feb 2017 12:57:34 +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 v1NBvYDg005927; Thu, 23 Feb 2017 12:57:34 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com> <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com> <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <619d77db-8b4d-704a-4f68-6ca6cf3433e7@gmail.com>
Date: Thu, 23 Feb 2017 12:57:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mkGb4ZpkF8mgFRUOWkPEfWqbmzY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 11:57:39 -0000

Le 22/02/2017 à 21:04, Brian E Carpenter a écrit :
> On 22/02/2017 22:41, Alexandre Petrescu wrote:
> <snip>
>
>>> Well that does two things: configures a 128 bit address (as Chris
>>> points out, *all* addresses are 128 bits, duh) and associates a
>>> prefix length with it, which afaik is optional.
>>
>> The prefix length is not optional.  There is no system out there on
>> which one could configure a 128bit address without explicitely telling
>> '/128' or '/64' or '/something-else'.
>
> Wrong. Sorry to get all technical, but on Windows:

Ok, I didnt know Windows acts that way.

>
> C:\windows\system32>netsh interface ipv6 add address ?
>
> Usage: add address [interface=]<string> [address=]<IPv6 address>[/<integer>]
>              [[type=]unicast|anycast]
>              [[validlifetime=]<integer>|infinite]
>              [[preferredlifetime=]<integer>|infinite]
>              [[store=]active|persistent]
>              [[skipassource=]true|false]
>
> The [/<integer>] looks pretty optional to me.

I agree.

> I just tried
>    netsh interface ipv6 add address 12 2001:db8:dead::beef
> and now I have three addresses:
>
> C:\windows\system32>netsh interface ipv6 show addresses
>
> Interface 12: Wireless Network Connection
>
> Addr Type  DAD State   Valid Life Pref. Life Address
> ---------  ----------- ---------- ---------- ------------------------
> Manual     Preferred     infinite   infinite 2001:db8:dead::beef
> Public     Preferred      1h54m9s      54m9s fd63:45eb:dc14:0:28cc:dc4c:9703:6781
> Other      Preferred     infinite   infinite fe80::28cc:dc4c:9703:6781%12
>
> When I try to ping 2001:db8:dead::cafe, I see what I expected in Wireshark:
> neighbour solicitations from 2001:db8:dead::beef to ff02::1:ff00:cafe.
> In other words, the new address is treated as on-link. I can't find any trace
> of an associated prefix entry.

This looks strange.  The NS for 2001:db8:dead::beef are normal - they 
are DAD.  But to consider it on-link, without having been told the plen 
is /64 and the prefix, is not normal.

I suppose Windows configures an address and a prefix/plen by receiving 
an RA.  And then, when adding manually an address it considers that 
address to be part of that link too.  That is not normal, because the 
prefix 2001:db8 is certainly not the same as the one in the RA.

I suppose Windows programmers made it so because they needed that 
[/integer] to be optional but they also needed the addresses that are 
manually configured to be part of some subnet... which one?

To check this behaviour, one would silence the RAs, netsh restart, and 
then manually configure an address without plen, and add a default gw. 
Can that ping the gw?  Can it ping the Internet?  If yes, then it means 
there is a /64 hidden somewhere that must be removed.  If it does not 
work, then it's good - it misses the plen.

> Maybe Linux is different.

YEs in a sesne.

Alex

>
>      Brian
>


From nobody Thu Feb 23 05:38:24 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CE101296DC for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 05:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hkG-aZJUVFRG for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 05:38:16 -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 AD3C91297F3 for <ietf@ietf.org>; Thu, 23 Feb 2017 05:38:14 -0800 (PST)
Received: by mail-vk0-x236.google.com with SMTP id k127so19719159vke.0 for <ietf@ietf.org>; Thu, 23 Feb 2017 05:38:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Vw1sOjBnMNgKL6JpFDvSoJWq+4AiM1HVFIbhWKuAHcc=; b=XkHPASzOB3p+Lv+iBUGUB98SOEsrI82EfHX3dUpn1pHyzUtJDsL/SBZyLH0qdWzMQB +Umy9rw0rC3wLEpvnqlNv+mI4llb0oilGKi3sBC6YSDAcFSew0iL1TWPhseRXn9T3MB1 bsnyBqYJ104e+0SHSWtJNo6V38mIEUaltcGkWAeFA7EVteCIru2MvdfDG29TJN/rwc3I ZdroffhniqAGPSLJegsYDU27OlttY8r3Ag4GvFo61tc0aeSJ5ZO4YH9fkEoQQ0XJ8Cf3 EI83BKIixz03iW1TfGmZCAkGI761O0DfD0JmkTRx51zwniwGgt4ZgQq/uv729t1QEljP +bDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Vw1sOjBnMNgKL6JpFDvSoJWq+4AiM1HVFIbhWKuAHcc=; b=tGMCAK5236cfG2Fc+JyIppIhA80P68jHtKNTNhqKCiBgTtURhiH2UCm/7jxlh+edCi UwI8ts0GYqaPBFhGyHDWx17TuoU+Wm8sEtRRdOZSmKuRk1IulHyDe2C26cTPINS4UuRi klCGtHhGsHUJ7nBSrWslriBHlzDLpD3io1IKRXqmh22BKsMKKoBDnTooKaEvawEVYcV2 dJJ6fQ9RBpVkaNVmGO+GUcmjQz71BFEfYdCQ26OR0DRTjzpQagpCLMcaOwwlm3W+o7t4 AhHTcgL3NYJiulAvPo/1Gg6qf4DD9stHhFLOMeZ0HPG/1Q9vmwfjFQ2ffE5JFvI0ADwf f8yQ==
X-Gm-Message-State: AMke39laD3RsXhJIjqX1ziXwpsvV4N9lLcKpzmYQkfLQOgYYjGYa5NsF4NCDLmZhHra6e6Aojb/C5uj3sl2pA07t
X-Received: by 10.31.170.15 with SMTP id t15mr16218499vke.6.1487857093513; Thu, 23 Feb 2017 05:38:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 05:37:52 -0800 (PST)
In-Reply-To: <20170223113705.GJ89584@hanna.meerval.net>
References: <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com> <20170223113705.GJ89584@hanna.meerval.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 22:37:52 +0900
Message-ID: <CAKD1Yr2_9vhdGDBVTkpRcBUXBOKqw5nETp40Xc=r1rh3gj4PuA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=001a114322508974cf054932b9e1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lS_VkzEQu4hpXypCRe77mtQLjQA>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 13:38:17 -0000

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

On Thu, Feb 23, 2017 at 8:37 PM, Job Snijders <job@ntt.net> wrote:

> For the benefit of the working group, what Lorenzo describes is the
> following in linux-lingo:
> [...]
>

Actually no, what I was saying was literally to leave the addresses as /64s
and configure the first-hop router to route the /126 to the prefix. The
hosts won't care.


> I also fear that the moment "disunited addressing & routing" become
> commonplace, you'll find your devices on the dirty end of a
> '/120 routed + /64 addressed'-link and have a dysfunctional experience.
> As far as I know there is no way to signal host "only a /120 out of this
> /64 is routed".
>

The host doesn't really need to know.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 8:37 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D"=
mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">For the benefit of the working group, what L=
orenzo describes is the<br>
following in linux-lingo:<br>
[...]<br></blockquote><div><br></div><div>Actually no, what I was saying wa=
s literally to leave the addresses as /64s and configure the first-hop rout=
er to route the /126 to the prefix. The hosts won&#39;t care.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">I also fear that the moment &quot;d=
isunited addressing &amp; routing&quot; become<br>
commonplace, you&#39;ll find your devices on the dirty end of a<br>
&#39;/120 routed + /64 addressed&#39;-link and have a dysfunctional experie=
nce.<br>
As far as I know there is no way to signal host &quot;only a /120 out of th=
is<br>
/64 is routed&quot;.<br></blockquote><div><br></div><div>The host doesn&#39=
;t really need to know.</div></div></div></div>

--001a114322508974cf054932b9e1--


From nobody Thu Feb 23 05:48:29 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB46129C51; Thu, 23 Feb 2017 05:48:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 SbiikIXjax5Z; Thu, 23 Feb 2017 05:48:23 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 BBA2D129851; Thu, 23 Feb 2017 05:48:23 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgtkc-000AaW-B6 (job@us.ntt.net); Thu, 23 Feb 2017 13:48:22 +0000
Date: Thu, 23 Feb 2017 14:47:33 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170223134733.GL89584@hanna.meerval.net>
References: <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com> <20170223113705.GJ89584@hanna.meerval.net> <CAKD1Yr2_9vhdGDBVTkpRcBUXBOKqw5nETp40Xc=r1rh3gj4PuA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr2_9vhdGDBVTkpRcBUXBOKqw5nETp40Xc=r1rh3gj4PuA@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hfvvvnflQZv-GXfUW5FGs7CYOgg>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 13:48:24 -0000

On Thu, Feb 23, 2017 at 10:37:52PM +0900, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 8:37 PM, Job Snijders <job@ntt.net> wrote:
> 
> > For the benefit of the working group, what Lorenzo describes is the
> > following in linux-lingo:
> > [...]
> 
> Actually no, what I was saying was literally to leave the addresses as
> /64s and configure the first-hop router to route the /126 to the
> prefix. The hosts won't care.

And how to protect the interconnection between the first-hop router and
the edge-of-your-network? or the edge of the network itself? I suspect
this idea is still in a theoretical stage.

Can you point me to a RIPE, NANOG or APRICOT talk where this idea is
shared in its entirety?

Kind regards,

Job


From nobody Thu Feb 23 05:52:26 2017
Return-Path: <phessler@theapt.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8201297CA for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 05:52:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.415
X-Spam-Level: 
X-Spam-Status: No, score=-0.415 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 7dSYA_VAYTpB for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 05:52:23 -0800 (PST)
Received: from gir.theapt.org (gir.theapt.org [IPv6:2001:470:1f0b:8b2::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5897F1297EE for <ietf@ietf.org>; Thu, 23 Feb 2017 05:52:23 -0800 (PST)
Received: from gir.theapt.org (unknown [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/0 bits)) (Client did not present a certificate) (Authenticated sender: phessler) by gir.theapt.org (Postfix) with ESMTPSA id 011A878984 for <ietf@ietf.org>; Thu, 23 Feb 2017 14:52:21 +0100 (CET)
Date: Thu, 23 Feb 2017 14:52:20 +0100
From: Peter Hessler <phessler@theapt.org>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Message-ID: <20170223135220.GJ5069@gir.theapt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lt10FR_k17zrm8PPI08XxRRzc04>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 13:52:24 -0000

----- Forwarded message from Peter Hessler <phessler@theapt.org> -----

Date: Thu, 23 Feb 2017 14:40:26 +0100
From: Peter Hessler <phessler@theapt.org>
To: ipv6@ietf.org
Subject: Objection to draft-ietf-6man-rfc4291bis-07.txt
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>

Restricting all subnets to The One True Size(tm) of /64 is utterly
ridiculous.  Sure, that may be an artificial limitation of SLAAC and
various other technologies, but *those* can have limitations.

Limiting it inside the entire specification is even stupider of an idea
than still supporting Classful networks.

As an implementation, OpenBSD will never add such a crazy thing.  And
you know that many other implementations won't do so either.

I strongly oppose this draft.

-- 
Numeric stability is probably not all that important when you're guessing.


From nobody Thu Feb 23 05:58:50 2017
Return-Path: <tuexen@fh-muenster.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4046C12940F; Thu, 23 Feb 2017 05:58:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 kjfsYZcQYwQR; Thu, 23 Feb 2017 05:58:46 -0800 (PST)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D744C1296D2; Thu, 23 Feb 2017 05:58:42 -0800 (PST)
Received: from [IPv6:2003:cd:6be5:a300:487d:7c9d:5944:feda] (p200300CD6BE5A300487D7C9D5944FEDA.dip0.t-ipconnect.de [IPv6:2003:cd:6be5:a300:487d:7c9d:5944:feda]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 5E655721E281A; Thu, 23 Feb 2017 14:58:38 +0100 (CET)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <792C410E-98F1-42E9-84C8-FC71BC8528F9@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_A8E529D9-0FC5-4052-A2AA-928B22F5C8A4"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [Tsv-art] Review of draft-hardie-privsec-metadata-insertion-05
Date: Thu, 23 Feb 2017 14:58:37 +0100
In-Reply-To: <CA+9kkMAmG2P=g1k7w3YOh1udjDB_MOjn0=+hnUXap1zq-VtwHQ@mail.gmail.com>
To: Ted Hardie <ted.ietf@gmail.com>
References: <148726910816.1075.17105591789960030239.idtracker@ietfa.amsl.com> <CA+9kkMAmG2P=g1k7w3YOh1udjDB_MOjn0=+hnUXap1zq-VtwHQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nVdwgEXoafuX9-SDHGgRy3ryio0>
Cc: @ietfa.amsl.com, "Michael TXXxen <tuexen@fh-muenster.de>"@ietfa.amsl.com, IETF <ietf@ietf.org>, draft-hardie-privsec-metadata-insertion.all@ietf.org, tsv-art@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 13:58:48 -0000

--Apple-Mail=_A8E529D9-0FC5-4052-A2AA-928B22F5C8A4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 22 Feb 2017, at 22:53, Ted Hardie <ted.ietf@gmail.com> wrote:
>=20
> Hi Michael,
>=20
> Thanks for the review; I've uploaded a -06 now which updates the =
abstract, adds the reference to RFC 6891 and clarifies the language =
around the purpose of the EDNS0 options.
Thanks for the update. It addresses the issues I found.

Best regards
Michael
>=20
> regards,
>=20
> Ted
>=20
> On Thu, Feb 16, 2017 at 10:18 AM, <"Michael T=C3=BCxen =
<tuexen@fh-muenster.de>"@ietfa.amsl.com> wrote:
> Reviewer: Michael T=C3=BCxen
> Review result: Ready with Nits
>=20
> I've reviewed this document as part of the transport area
> directorate's ongoing
> effort to review key IETF documents.
> These comments were written primarily for the transport area
> directors,
> but are copied to the document's authors for their information and to
> allow
> them to address any issues raised. When done at the time of IETF Last
> Call,
> the authors should consider this review together with any other
> last-call
> comments they receive.
> Please always CC tsv-art@ietf.org if you reply to or forward this
> review.
>=20
> This draft is basically ready for publication, but has nits that
> should be
> fixed before publication.
>=20
> Running https://tools.ietf.org/tools/idnits/idnits.pyht reports
> * The abstract seems to contain references ([RFC7624]), which it
> shouldn't.
> * Unused Reference: 'RFC4301'
>=20
> The discussion of RFC 7871 in section 4 could be improved to allow
> readers
> not knowing the EDNS0 option to get the point. Either provide an
> abstract
> description or refer to RFC 6891.
>=20
>=20
>=20
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art


--Apple-Mail=_A8E529D9-0FC5-4052-A2AA-928B22F5C8A4
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIQkDCCBNUw
ggO9oAMCAQICCFBOxvU9EbRkMA0GCSqGSIb3DQEBCwUAMHExCzAJBgNVBAYTAkRFMRwwGgYDVQQK
ExNEZXV0c2NoZSBUZWxla29tIEFHMR8wHQYDVQQLExZULVRlbGVTZWMgVHJ1c3QgQ2VudGVyMSMw
IQYDVQQDExpEZXV0c2NoZSBUZWxla29tIFJvb3QgQ0EgMjAeFw0xNDA3MjIxMjA4MjZaFw0xOTA3
MDkyMzU5MDBaMFoxCzAJBgNVBAYTAkRFMRMwEQYDVQQKEwpERk4tVmVyZWluMRAwDgYDVQQLEwdE
Rk4tUEtJMSQwIgYDVQQDExtERk4tVmVyZWluIFBDQSBHbG9iYWwgLSBHMDEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDpm8NnhfkNrvWNVMOWUDU9YuluTO2U1wBblSJ01CDrNI/W7MAx
BAuZgeKmFNJSoCgjhIt0iQReW+DieMF4yxbLKDU5ey2QRdDtoAB6fL9KDhsAw4bpXCsxEXsM84Ik
Q4wcOItqaACa7txPeKvSxhObdq3u3ibo7wGvdA/BCaL2a869080UME/15eOkyGKbghoDJzANAmVg
Te3RCSMqljVYJ9N2xnG2kB3E7f81hn1vM7PbD8URwoqDoZRdQWvY0hD1TP3KUazZve+Sg7va64sW
VlZDz+HVEz2mHycwzUlU28kTNJpxdcVs6qcLmPkhnSevPqM5OUhqjK3JmfvDEvK9AgMBAAGjggGG
MIIBgjAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFEm3xs/oPR9/6kR7Eyn38QpwPt5kMB8GA1Ud
IwQYMBaAFDHDeRu69VPXF+CJei0XbAqzK50zMBIGA1UdEwEB/wQIMAYBAf8CAQIwYgYDVR0gBFsw
WTARBg8rBgEEAYGtIYIsAQEEAgIwEQYPKwYBBAGBrSGCLAEBBAMAMBEGDysGAQQBga0hgiwBAQQD
ATAPBg0rBgEEAYGtIYIsAQEEMA0GCysGAQQBga0hgiweMD4GA1UdHwQ3MDUwM6AxoC+GLWh0dHA6
Ly9wa2kwMzM2LnRlbGVzZWMuZGUvcmwvRFRfUk9PVF9DQV8yLmNybDB4BggrBgEFBQcBAQRsMGow
LAYIKwYBBQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMDoGCCsGAQUFBzAC
hi5odHRwOi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9EVF9ST09UX0NBXzIuY2VyMA0GCSqGSIb3
DQEBCwUAA4IBAQBjICj9nCGGcr45Rlk5MiW8qQGbDczKfUGchm0KbiyzE1l1sTOSG2EnFv/DstU1
gvuEKgFJvWa7Zi+ywgZdbj9u4wFaW8pDY1yVtuExpx/VB19N5mWCTjL5w3x6S81NXHTuIfJ1AuxS
PtLJatOQI25JZzW+f01WpOzML8+3oZeocj7JvEDWWqQIPda8gsO3tzKOsSyOam23NQIZz/U5RFhj
pyQAELC7/E6vbi84u6VXST/YblBvLJeW3B1GmmWJz67M8uXZn1OzPqEvkqnYC8aEHwTG6x7on321
e6UC8STFJGMRNMxakyAqeYg6JUKQqWU7fIbTEhUjKfws2sw5W1QXMIIFojCCBIqgAwIBAgIHF6Qk
oQlIMzANBgkqhkiG9w0BAQsFADBaMQswCQYDVQQGEwJERTETMBEGA1UEChMKREZOLVZlcmVpbjEQ
MA4GA1UECxMHREZOLVBLSTEkMCIGA1UEAxMbREZOLVZlcmVpbiBQQ0EgR2xvYmFsIC0gRzAxMB4X
DTE0MDUyNzE0NTQwOVoXDTE5MDcwOTIzNTkwMFowgcYxCzAJBgNVBAYTAkRFMRwwGgYDVQQIExNO
b3JkcmhlaW4tV2VzdGZhbGVuMREwDwYDVQQHEwhNdWVuc3RlcjEgMB4GA1UEChMXRmFjaGhvY2hz
Y2h1bGUgTXVlbnN0ZXIxIzAhBgNVBAsTGkRhdGVudmVyYXJiZWl0dW5nc3plbnRyYWxlMR0wGwYD
VQQDExRGSCBNdWVuc3RlciBDQSAtIEcwMTEgMB4GCSqGSIb3DQEJARYRY2FAZmgtbXVlbnN0ZXIu
ZGUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC4eWyu8GzsIv0iowf2v/9BT0SmCFNX
/eyQe5BncOk1j6XIlY5bnNu1S5uBe3uVgekgTh3gJyVNlaoIfCgAjqCrNJIaNQq5fr/S6L8uFeaU
O8IF/C4RH5P7f9Hn2GUueEjmJhg9CI3LBAhrfAmEEtNmuVfDycN2MjngwDNxUNRfuXbWxuhkgDqJ
0ztJeayHGhFDrGx88eyStx40xy+0c0OFWdWxzBFQlBRHnl+zRftj3c9qy6BY+/fGaA2vV1oKr3h5
X6eyU1T8YlpP1NDe4bylqAteX01sM2Qciu8UAPnNc7Sb93TQjhCFRVDIS3CdN6AOpwz5YWEld6ey
CdmFZ7pvAgMBAAGjggH+MIIB+jASBgNVHRMBAf8ECDAGAQH/AgEBMA4GA1UdDwEB/wQEAwIBBjAR
BgNVHSAECjAIMAYGBFUdIAAwHQYDVR0OBBYEFArzW7zkMYDWNUKJptPDzzfe0d/XMB8GA1UdIwQY
MBaAFEm3xs/oPR9/6kR7Eyn38QpwPt5kMBwGA1UdEQQVMBOBEWNhQGZoLW11ZW5zdGVyLmRlMIGI
BgNVHR8EgYAwfjA9oDugOYY3aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9w
dWIvY3JsL2NhY3JsLmNybDA9oDugOYY3aHR0cDovL2NkcDIucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1jYS9wdWIvY3JsL2NhY3JsLmNybDCB1wYIKwYBBQUHAQEEgcowgccwMwYIKwYBBQUHMAGGJ2h0
dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBHBggrBgEFBQcwAoY7aHR0cDov
L2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwRwYI
KwYBBQUHMAKGO2h0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJvb3QtY2EvcHViL2NhY2Vy
dC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQDeRwM11kpvuRIPuzWXLapr/ZBtB76V3cuF
l45x/Kx0u03yjB4GaBPcxihn4P1z5KhRYkDBMo8HXkOgbL59aF6VdOlCurEgZvghKvUkKOCyWeYx
S9rTGPBkbGiNn2ATVuLXzF8rDf50ynAIu3otstOOv+3Ifqi1pzCva1nO64khQA5Gd5/BNyu+YHbW
f8ERAf9leu5a7yVI7cv1gCZAHpWJpkUKmfawyY4sAJ2hbGZRBvdACOxrfbuMdSOzPneT2rlmvH+D
7M6DmzVabLYk6UtAxQhldd/T/qsHkWvaWXHt0Eb9STs2Fl03Ls7M3NyLQLhaeR3ysNURYcaEfaB+
lxN+MIIGDTCCBPWgAwIBAgIHG5mIdDexozANBgkqhkiG9w0BAQsFADCBxjELMAkGA1UEBhMCREUx
HDAaBgNVBAgTE05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQK
ExdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVu
dHJhbGUxHTAbBgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBm
aC1tdWVuc3Rlci5kZTAeFw0xNjA3MDQwNzA2MTNaFw0xOTA3MDQwNzA2MTNaMHwxCzAJBgNVBAYT
AkRFMSAwHgYDVQQKDBdGYWNoaG9jaHNjaHVsZSBNdWVuc3RlcjEyMDAGA1UECwwpRmFjaGJlcmVp
Y2ggRWxla3Ryb3RlY2huaWsgdW5kIEluZm9ybWF0aWsxFzAVBgNVBAMMDk1pY2hhZWwgVHVleGVu
MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAzJoaUG3Zm24XxA/zNg2sbFcL56w8xqMg
+X6G7UsYec3YEncnlkw3jgE5nDefos7UVoCA7wPjFTj8AQt5xfpXElnbM45IPy5Ng7g6dS7biGSM
VRACPXe1PrjgApRAwwGmCPvALnZXkmKP6Zlf+3VLfz9YWIIaeKu3jFM2Lk6Y3gr5U1l8bjHSawOo
WMlfvSsXXLT38zKW7Uz9jS278j0OqHANBPgsE6/LJoCWFInwlvybxhO3nGU7OteUGaPikqzvjLsL
YgpHDi0WjMZfVx/UtUSzZ4EJvmJTBeuVwyKnCbrawnfwYPTQQ6VE1OkAzmsMByBbEwJ996RtG//T
XCG06QIDAQABo4ICRzCCAkMwQAYDVR0gBDkwNzARBg8rBgEEAYGtIYIsAQEEAwUwEQYPKwYBBAGB
rSGCLAIBBAMBMA8GDSsGAQQBga0hgiwBAQQwCQYDVR0TBAIwADAOBgNVHQ8BAf8EBAMCBeAwHQYD
VR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBTQHa9qhKgSZgCCAPThZkXaEaJ/
dTAfBgNVHSMEGDAWgBQK81u85DGA1jVCiabTw8833tHf1zAgBgNVHREEGTAXgRV0dWV4ZW5AZmgt
bXVlbnN0ZXIuZGUwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2Zo
LW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMD2gO6A5hjdodHRwOi8vY2RwMi5wY2EuZGZu
LmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jcmwvY2FjcmwuY3JsMIHXBggrBgEFBQcBAQSByjCBxzAz
BggrBgEFBQcwAYYnaHR0cDovL29jc3AucGNhLmRmbi5kZS9PQ1NQLVNlcnZlci9PQ1NQMEcGCCsG
AQUFBzAChjtodHRwOi8vY2RwMS5wY2EuZGZuLmRlL2ZoLW11ZW5zdGVyLWNhL3B1Yi9jYWNlcnQv
Y2FjZXJ0LmNydDBHBggrBgEFBQcwAoY7aHR0cDovL2NkcDIucGNhLmRmbi5kZS9maC1tdWVuc3Rl
ci1jYS9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwDQYJKoZIhvcNAQELBQADggEBAEj2/6x4kzoCVIiu
aaminPrOHxACyoYsmSRjYPQpgW5xRj/FlolO1nG+ZZ11sqTb3TdCGD69ko5/zs8eGKnv/i0VLCHF
g1JLfpaxElN5RrR/cqRJrbzKshF9aUkBODF8vlf9BCeimMK3fifjbbWRyxHssfEECffujD7/Yvta
NYMO46Roz39lIK2s37IVFq3V5RWzUeTuwpP9t8lOxirOi9eK2OYI/dh0HjR2S5Dr9nMR1dNulrhz
jlFxGc+opefGScrRR9Ec0eqTXlbt1Q9UzNIYVS+OGZY8/bBbprwXVTmwSp8dygEULkIaMbLsaTaW
6TehuL8ousPJkL52SOENgSkxggQpMIIEJQIBATCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozAJBgUrDgMCGgUAoIICKzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwG
CSqGSIb3DQEJBTEPFw0xNzAyMjMxMzU4MzdaMCMGCSqGSIb3DQEJBDEWBBRO9N5zg6d83awzVxTE
2WDac8YPezCB4wYJKwYBBAGCNxAEMYHVMIHSMIHGMQswCQYDVQQGEwJERTEcMBoGA1UECBMTTm9y
ZHJoZWluLVdlc3RmYWxlbjERMA8GA1UEBxMITXVlbnN0ZXIxIDAeBgNVBAoTF0ZhY2hob2Noc2No
dWxlIE11ZW5zdGVyMSMwIQYDVQQLExpEYXRlbnZlcmFyYmVpdHVuZ3N6ZW50cmFsZTEdMBsGA1UE
AxMURkggTXVlbnN0ZXIgQ0EgLSBHMDExIDAeBgkqhkiG9w0BCQEWEWNhQGZoLW11ZW5zdGVyLmRl
AgcbmYh0N7GjMIHlBgsqhkiG9w0BCRACCzGB1aCB0jCBxjELMAkGA1UEBhMCREUxHDAaBgNVBAgT
E05vcmRyaGVpbi1XZXN0ZmFsZW4xETAPBgNVBAcTCE11ZW5zdGVyMSAwHgYDVQQKExdGYWNoaG9j
aHNjaHVsZSBNdWVuc3RlcjEjMCEGA1UECxMaRGF0ZW52ZXJhcmJlaXR1bmdzemVudHJhbGUxHTAb
BgNVBAMTFEZIIE11ZW5zdGVyIENBIC0gRzAxMSAwHgYJKoZIhvcNAQkBFhFjYUBmaC1tdWVuc3Rl
ci5kZQIHG5mIdDexozANBgkqhkiG9w0BAQEFAASCAQBfD7Wc5QQ826cXDWiavUOpZGNCfPWICHyi
qL9wTypgVGGcyX64x4z7UOhyyJOOVEVd8kWoWJ+EXKN2h8WcrYBbgfM5VLNHNvs7lvXbDLoe5576
ygU+Vd430OtUgbDXTUCIYrVu7HZpG6zkSR3Vd7TSJQxVbyQiNoKK0OuYSpf4Hdv3GuWcmDslBI4b
aWk+30USkZVaEjqT7XEQvKISOgLVns0UWAMVoI/Esi1Mo+E1oCfvdv9H6ACxrZKoD1JwqOjky1sl
KXYMgz5Ss98pQHVs3BcaZFHSGnuVNRQoSUgLiwz+Suh1IX4s51nHufkXFQR4TQ4nN7ZS/bAJkzxm
3LiLAAAAAAAA
--Apple-Mail=_A8E529D9-0FC5-4052-A2AA-928B22F5C8A4--


From nobody Thu Feb 23 06:06:48 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F63A129861 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 06:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gYQnxYb7xO1S for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 06:06:44 -0800 (PST)
Received: from mail-vk0-x230.google.com (mail-vk0-x230.google.com [IPv6:2607:f8b0:400c:c05::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 60D6E129865 for <ietf@ietf.org>; Thu, 23 Feb 2017 06:06:42 -0800 (PST)
Received: by mail-vk0-x230.google.com with SMTP id k127so20183464vke.0 for <ietf@ietf.org>; Thu, 23 Feb 2017 06:06:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=hT/Uu91XPjw7ER0NBpQW7B5T5JYcQMdD5aXKEgirHxI=; b=UBTqc8VDiWC9CuUeTwvA8/0Zb3LnmNyXnsDFJFTaBO5lVqNvxshtuH1K8lSQ/jiKnR hnogcjcjps5gEH4AtUl5WGeuIcKZqAsEjMs5cj/nhXL1vU/d2Wl9WSk4CVPqJP72FF9l zeGByw/P69ZGA8j5kU50sxPcca4B4f5KfvfqWbxVbaBuNPTEdWH9HGKGGNdH14Qm3I1X wJV/CxhAyd89WfTm0VY1W1DA4PIawmsEo1qZJvEL8CNTKLFfNxOeeXr9nDg55G9NxaVV azqNLNTtfWDsxGdSOBkfjyxUCKRqfjWMUGy3+QbHIuv0si4CfmHmeSCJ2BRtsyVYXRIZ xOGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=hT/Uu91XPjw7ER0NBpQW7B5T5JYcQMdD5aXKEgirHxI=; b=kHSEWdZeOUzcoug3ZlOkRE+JuB4WM7MQyAQ8Cltl8BL5yij7641Ryef+SmuqkiYAD9 QoBRZSgrKVkqWtvMLVWsIcMNxQP6YvSsPSCtLUBEvqItPb3nE51Debmh4cLSaU7DFW7I XbBD1uNbKJN6X7chlJaogZYaivy834S4jojF3uk3eFJsm5KGfsO3Ug57xDBQ+u6Cweyx C38n9bKJM1hfmlnJMWQUCZxQK/ihCwZYRyeRtxrUYpKcbZvBG+ng6rUSaU+0rgmeuMzS 4oegbk4iB77Jy4Tfm5f1gYb2aMH+4oRRVz8aiIiA+M7qgtu2Sv/Sb6AMOfzcpn60x29w TwnQ==
X-Gm-Message-State: AMke39mrLaVwqGhV5uWjNcDNzJXPYj7jCZ2cMKNsvnqPhBtNkkZ3+rUA9Nomnu4BbZTS0uFS/P1o8vUWIJArMlWy
X-Received: by 10.31.163.199 with SMTP id m190mr215825vke.10.1487858801179; Thu, 23 Feb 2017 06:06:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 06:06:20 -0800 (PST)
In-Reply-To: <20170223134733.GL89584@hanna.meerval.net>
References: <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com> <20170223113705.GJ89584@hanna.meerval.net> <CAKD1Yr2_9vhdGDBVTkpRcBUXBOKqw5nETp40Xc=r1rh3gj4PuA@mail.gmail.com> <20170223134733.GL89584@hanna.meerval.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 23:06:20 +0900
Message-ID: <CAKD1Yr2+j_mGdDJ6xpSz=WyNuFuucfwX3K8=YwDHbam2=jMHtQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=001a114150dc526ea60549331f81
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p_cAde1YmEqi17jFGGEzTAdkrNs>
Cc: 6man WG <ipv6@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 14:06:45 -0000

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

On Thu, Feb 23, 2017 at 10:47 PM, Job Snijders <job@ntt.net> wrote:

> And how to protect the interconnection between the first-hop router and
> the edge-of-your-network? or the edge of the network itself? I suspect
> this idea is still in a theoretical stage.
>

Not sure what you mean. If you have an edge ACL and you want to ensure that
packets in the machine /64 but not in the arbitrarily small subnet you've
decided to restrict the machines to, just allow the /120 at the edge and
drop the /64. If you're talking about protecting the interconnects between
routers, you can just use /127.


> Can you point me to a RIPE, NANOG or APRICOT talk where this idea is
> shared in its entirety?
>

You don't need a RIPE talk to do some experimentation, do you? If it works
well, you give the talk. :-)

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 10:47 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D=
"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">And how to protect the interconnection betw=
een the first-hop router and<br>
the edge-of-your-network? or the edge of the network itself? I suspect<br>
this idea is still in a theoretical stage.<br></blockquote><div><br></div><=
div>Not sure what you mean. If you have an edge ACL and you want to ensure =
that packets in the machine /64 but not in the arbitrarily small subnet you=
&#39;ve decided to restrict the machines to, just allow the /120 at the edg=
e and drop the /64. If you&#39;re talking about protecting the interconnect=
s between routers, you can just use /127.</div><div>=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Can you point me to a RIPE, NANOG or APRICOT talk where=
 this idea is<br>
shared in its entirety?<br></blockquote><div><br></div><div>You don&#39;t n=
eed a RIPE talk to do some experimentation, do you? If it works well, you g=
ive the talk. :-)</div></div></div></div>

--001a114150dc526ea60549331f81--


From nobody Thu Feb 23 06:36:48 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCFA6129887; Thu, 23 Feb 2017 06:36:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 c4gNBW4rthfM; Thu, 23 Feb 2017 06:36:42 -0800 (PST)
Received: from mail3.dllstx09.us.to.gin.ntt.net (mail3.dllstx09.us.to.gin.ntt.net [IPv6:2001:418:3ff:5::26]) (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 1D8EE129886; Thu, 23 Feb 2017 06:36:42 -0800 (PST)
Received: by mail3.dllstx09.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cguVS-000FY2-A3 (job@us.ntt.net); Thu, 23 Feb 2017 14:36:40 +0000
Date: Thu, 23 Feb 2017 15:36:02 +0100
From: Job Snijders <job@ntt.net>
To: Lorenzo Colitti <lorenzo@google.com>, ietf@ietf.org
Subject: Re: Objection to draft-ietf-6man-rfc4291bis-07.txt
Message-ID: <20170223143602.GN89584@hanna.meerval.net>
References: <20170223134026.GI5069@gir.theapt.org> <CAKD1Yr16PZDUEKQHd3At9GRz23EBKL7dTr5+aQCnzOwaT0bAxw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr16PZDUEKQHd3At9GRz23EBKL7dTr5+aQCnzOwaT0bAxw@mail.gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K_ZU-CnJNvBnlWASwT8_JSl9xsA>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, Peter Hessler <phessler@theapt.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 14:36:43 -0000

On Thu, Feb 23, 2017 at 11:14:35PM +0900, Lorenzo Colitti wrote:
> On Thu, Feb 23, 2017 at 10:40 PM, Peter Hessler <phessler@theapt.org> wrote:
> 
> > As an implementation, OpenBSD will never add such a crazy thing.  And
> > you know that many other implementations won't do so either.
> >
> > I strongly oppose this draft.
> 
> Bit late to object to that text now I'm afraid.

You are overstepping, Peter's message is submitted well within the
proper time window:

	The IESG has received a request from the IPv6 Maintenance WG (6man) to
	consider the following document:
	- 'IP Version 6 Addressing Architecture'
	  <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard

	The IESG plans to make a decision in the next few weeks, and solicits
	final comments on this action. Please send substantive comments to the
	ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
	sent to iesg@ietf.org instead. 

> A good time to object would have been 19 years ago when the text you
> object to became the standard:

You realise that new people are born every day, and not everyone who
participates in IETF is 50+ years old? Even I were not of legal age 19
years ago.

Your comment borders on the verge of discrimation based on age. This
violates the fundamentals on which we work together to standardise
technologies.

Comments which imply "you should've been there" are both demeaning
and derogatory to operators who come to IETF to improve the current
state of affairs.

Kind regards,

Job


From nobody Thu Feb 23 06:47:10 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFB2B129B07 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 06:47:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6xyj1p1-zb8r for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 06:47:07 -0800 (PST)
Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::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 835171298CE for <ietf@ietf.org>; Thu, 23 Feb 2017 06:47:07 -0800 (PST)
Received: by mail-vk0-x22d.google.com with SMTP id x75so20906253vke.2 for <ietf@ietf.org>; Thu, 23 Feb 2017 06:47:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NddmQmOaM/cQ/y1aN7sLR5Vn21qtPHdhEQqai5/aqWM=; b=n04xJMB//JhnozdNMXIi7/UvNjBsnZWe2Z32Bnxh9F/9STYf/tI1WtN9eM9ws7726r pO0DWNF0KN2dUPmlIv8WYk3dIUTvwFaBBVMjFn2ReoNtX+XecnPG+jSlMPU0IroIpCbp 7Y6kck83nRF7/Cr1S3DScghw1r12gI6aoyKqvqhVcAZizDE5a4gm9M25Srq7iPhpMx71 t/7uZzv33H+N92Iun6+gjV2pO43BV/Zk7YfHGxooCRVd8kFPbObmqneOHQRBJcwT5dRl 9uZNlEHDhYGIjC6qSSYN/jzvaGMV2LMnQwAdZRTnfs68XQ5I6FcaTNYhLdxMespCRntT jf4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NddmQmOaM/cQ/y1aN7sLR5Vn21qtPHdhEQqai5/aqWM=; b=c4mcdJzpCul8NJ0QA8vaHtLWVzS15U8Vu1saRp5LHfRSekd39efPZ8K9OQqtzPLph/ 9YDhwcYSlrR6i0YlnzQMzPn3jkexvN7wYtj9Yk23iNArcyYa7Kz0Lp+7RNwb+D94SLv1 +5rvO6SxutoTcdJoqkTV4mD1yT0WOzmBeDdps+Yp5zOKfLFqscIWizjrvHxGc6n4T2sQ xtZ6/H/5pEuIwH4W6RbtNRHm5Iw8egcAbCUNz+0Vt1Xlva/SX2QGl4YN6xo7fOB9XS/X GAakr9dvw+tC7VvknnvLcizW4MtQzR0Bd9RbpQINQXslKmftCUiT7yQnmi2DXSldpgnZ QMxA==
X-Gm-Message-State: AMke39l84ATTrHsGnxdf/juFXZpid5Ud6tlNiyMCOHVXLiQFSSk6b2PIZ0OJUJh7DACRbRUIVnmACQsjSvfJrcNs
X-Received: by 10.31.142.68 with SMTP id q65mr18953309vkd.83.1487861226375; Thu, 23 Feb 2017 06:47:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 06:46:45 -0800 (PST)
In-Reply-To: <20170223143602.GN89584@hanna.meerval.net>
References: <20170223134026.GI5069@gir.theapt.org> <CAKD1Yr16PZDUEKQHd3At9GRz23EBKL7dTr5+aQCnzOwaT0bAxw@mail.gmail.com> <20170223143602.GN89584@hanna.meerval.net>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 23 Feb 2017 23:46:45 +0900
Message-ID: <CAKD1Yr3KAbGAbJbpvNtoqSodX4AwKd1G+YmDpXaTTwbexTGjdw@mail.gmail.com>
Subject: Re: Objection to draft-ietf-6man-rfc4291bis-07.txt
To: Job Snijders <job@ntt.net>
Content-Type: multipart/alternative; boundary=001a1143703ae0134b054933aff1
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iqM8KEUriSUo1a4VP0NURpj4s6Q>
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, Peter Hessler <phessler@theapt.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 14:47:09 -0000

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

On Thu, Feb 23, 2017 at 11:36 PM, Job Snijders <job@ntt.net> wrote:

> Comments which imply "you should've been there" are both demeaning
> and derogatory to operators who come to IETF to improve the current
> state of affairs.
>

My intention was not to imply anything of the sort. I apologize if that was
how it was received. FWIW I wasn't there when the standard was written,
either.

My point was a purely technical one: this is not new text or a new
proposal. It is the current text of the standard, and has been the current
text of the standard for almost 20 years. Opposing this document will
prevent this document from becoming a standard, but it won't prevent that
text from becoming a standard because it is *already* the standard.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 23, 2017 at 11:36 PM, Job Snijders <span dir=3D"ltr">&lt;<a href=3D=
"mailto:job@ntt.net" target=3D"_blank">job@ntt.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">Comments which imply &quot;you should&#39;v=
e been there&quot; are both demeaning<br>
and derogatory to operators who come to IETF to improve the current<br>
state of affairs.<br></blockquote><div><br></div><div>My intention was not =
to imply anything of the sort. I apologize if that was how it was received.=
 FWIW I wasn&#39;t there when the standard was written, either.</div><div><=
br></div><div>My point was a purely technical one: this is not new text or =
a new proposal. It is the current text of the standard, and has been the cu=
rrent text of the standard for almost 20 years. Opposing this document will=
 prevent this document from becoming a standard, but it won&#39;t prevent t=
hat text from becoming a standard because it is *already* the standard.</di=
v></div></div></div>

--001a1143703ae0134b054933aff1--


From nobody Thu Feb 23 09:38:18 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69D1A1294CF; Thu, 23 Feb 2017 09:38:07 -0800 (PST)
X-Quarantine-ID: <86We3dWaumE3>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 86We3dWaumE3; Thu, 23 Feb 2017 09:38:05 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 86AFB12A202; Thu, 23 Feb 2017 09:38:05 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 23 Feb 2017 09:28:32 -0800
Mime-Version: 1.0
Message-Id: <p06240601d4d4cd1fe887@[99.111.97.136]>
In-Reply-To: <87fuj4syy6.fsf@hobgoblin.ariadne.com>
References: <87fuj4syy6.fsf@hobgoblin.ariadne.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 23 Feb 2017 09:35:19 -0800
To: worley@ariadne.com (Dale R. Worley)
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] Review of  draft-ietf-slim-negotiating-human-language-06
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WmrHU1x3Ij9dQRWu3IgIgp6pnWc>
Cc: slim@ietf.org, ietf@ietf.org, gen-art@ietf.org, draft-ietf-slim-negotiating-human-language.all@ietf.org, rg+ietf@randy.pensive.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 17:38:07 -0000

At 10:34 AM -0500 2/23/17, Dale R. Worley wrote:

>  Randall Gellens <rg+ietf@randy.pensive.org> writes:
>>  Thanks, Dale.  It seems that it would be useful
>>  for the draft to suggest (not require) that a
>>  session rejected due to lack of
>>  mutually-supported languages use 488 or 606, and
>>  also include a Warning header field with the
>>  suggested 308 code that the draft would register.
>
>  It seems to me that specifying how to reject the call is one of those
>  "SHOULD" things.  Of course, the document would have to register 308 as
>  a warn-code.

The update I posted yesterday does register a new warn-code.  I'm not 
sure we need to use SHOULD instead of explicit advice for the SIP 
response code.  I doubt implementers would ignore the explicit advice 
yet would honor a SHOULD.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
An elephant is a mouse with an operating system.


From nobody Thu Feb 23 09:39:23 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4537D1299D4; Thu, 23 Feb 2017 09:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UrpF2jbqYWkd; Thu, 23 Feb 2017 09:39:20 -0800 (PST)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::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 3B8E8126B6D; Thu, 23 Feb 2017 09:39:20 -0800 (PST)
Received: by mail-qk0-x229.google.com with SMTP id x71so38295920qkb.3; Thu, 23 Feb 2017 09:39:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uQwvRlxxAtDbdXgxMvk4phudRvZT5LsVm7yEc51IVLI=; b=WZmP3VZJfvMN1lUJWEML/uq5sDbqZkf8VXy8RjkHoeMBwh/9fjks5sD31UkBzaV7+1 5BH6t5HFpul4A8/WxoYI4OKmSqQ+co0sJDRi9IvzmEPZT/msp6eIn4Wr9TovMl5egA6y VMQ/sod0EIbDULg/2FLV5mr9b++8omdByfGLfRK5SPTdKp8hR3+FRvYCKPHsxzQ7kore gMreVJXPkXq59fATW5YJmHEsN4oHCCi9BOXyNwg/jBFe+cJR9K4c5In9RhmbDL3Yvei8 9IifRZYmjYy4rP1A+S6LesfnyxDAEDY7lCaMLgdFmk9ZT6Ky3gOzFPT8eKs5ZzP+rqdV nKeA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uQwvRlxxAtDbdXgxMvk4phudRvZT5LsVm7yEc51IVLI=; b=c7Wl2aq+Hy8cqRH1aVRUzOrzSAxFO4F1+lxUPFMtpguV2pSPLzhxFRvW/eWO0zawr9 JHyoZDGuYABE7BD/j3vn68SFrqSqnocTBSXXBTZcgxGt7NTSdtfPh5KnY4T1XNFCdYrM xWQ0+a9sb9PhbqSm3RLw68uQykVzADrXa8nLuEYVIx6FKeBhmLbnAk2u/5kK2n5j9irp aBm0e/MiJVgIHFAe/79AMWu3guxSE05dndBIozt6vsx1mGhqhi4Cx2hZ23tE3xcbU9ip QQRP3ELMnVsa8PwW+xsVF9zx6ACEQHo66kyMluYYds+lKIVKf81c9MOIrFbvuvdLZ5xs Pvkg==
X-Gm-Message-State: AMke39lkUSB626P/4sgaKEJvw4dyTJRcLIfXvAPkAKVcLAf8lOn4XA4aeueJN+XlKrtpCnNoZko4HfbltQ2SCg==
X-Received: by 10.55.100.71 with SMTP id y68mr30487353qkb.108.1487871559386; Thu, 23 Feb 2017 09:39:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.91.71 with HTTP; Thu, 23 Feb 2017 09:39:18 -0800 (PST)
In-Reply-To: <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
References: <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <20170220235734.GA84656@Vurt.local> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <CAO42Z2xEqnz4=E7JDOA_FCg_RxkMuZgnBc3KuaxwY1oZryed9g@mail.gmail.com> <20170221202821.GB32367@Vurt.local> <CAO42Z2yK_rZksa4xQkuW8Q_hwaitH610m6kVBmFisN7toaSoPw@mail.gmail.com> <CAKD1Yr3pNBCNFRkZiDYoOp7CDDG-4pbuzkLW8UeJB_bbS7QEWw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Thu, 23 Feb 2017 12:39:18 -0500
Message-ID: <CAL9jLaZwruTEnZ9eddkWf0bC3EKW_AN2XbYeo0j4C3=nQC+OcQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a11485d0ec4d26f0549361770
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cRRA7pT39kUB5ilcjOw1PoHygdw>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF <ietf@ietf.org>, 6man WG <ipv6@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 17:39:21 -0000

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

On Wed, Feb 22, 2017 at 12:46 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Thu, Feb 23, 2017 at 2:42 AM, Mark Smith <markzzzsmith@gmail.com>
> wrote:
>
>> Let's leave behind unnecessary practices that have been used to extend
>> IPv4's life, and that make things unnecessarily complicated and more costly
>> to operate and troubleshoot.
>>
>
> What he said.
>
>
I like this as well, I'm not convinced that any of mark's problems won't
show up in v6 networks though, even if the mandate (and hardware/software
fixes the mandate) is /64 only... people do dumb things, we can't really
stop them.

I don't see how the proposed wording makes this more complicated, for MOST
things people will just pick the default /64 and never look back (because
their upstream will be doing SLAAC and they won't even really 'pick').

For cases where people need (or feel the need) another prefix length
'RECOMMENDED'  means they can, they are adults, they can (and will) do what
they want.

-chris

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 22, 2017 at 12:46 PM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D"">On Th=
u, Feb 23, 2017 at 2:42 AM, Mark Smith <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:markzzzsmith@gmail.com" target=3D"_blank">markzzzsmith@gmail.com</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">Let&#39;s leave behind un=
necessary practices that have been used to extend IPv4&#39;s life, and that=
 make things unnecessarily complicated and more costly to operate and=C2=A0=
troubleshoot.<br></blockquote><div><br></div></span><div>What he said.=C2=
=A0</div></div></div></div>
<br></blockquote><div><br></div><div>I like this as well, I&#39;m not convi=
nced that any of mark&#39;s problems won&#39;t show up in v6 networks thoug=
h, even if the mandate (and hardware/software fixes the mandate) is /64 onl=
y... people do dumb things, we can&#39;t really stop them.</div><div><br></=
div><div>I don&#39;t see how the proposed wording makes this more complicat=
ed, for MOST things people will just pick the default /64 and never look ba=
ck (because their upstream will be doing SLAAC and they won&#39;t even real=
ly &#39;pick&#39;).</div><div><br>For cases where people need (or feel the =
need) another prefix length &#39;RECOMMENDED&#39; =C2=A0means they can, the=
y are adults, they can (and will) do what they want.</div><div><br></div><d=
iv>-chris</div></div><br></div></div>

--001a11485d0ec4d26f0549361770--


From nobody Thu Feb 23 10:11:46 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE1A912A233 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 10:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 CYTKJTwy3Gfz for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 10:11:43 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA4EC129A6B for <ietf@ietf.org>; Thu, 23 Feb 2017 10:11:43 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0A995300436 for <ietf@ietf.org>; Thu, 23 Feb 2017 13:11:43 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id NYY5XzchXWVN for <ietf@ietf.org>; Thu, 23 Feb 2017 13:11:41 -0500 (EST)
Received: from [192.168.2.107] (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id A96A2300254; Thu, 23 Feb 2017 13:11:41 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-bchv-rfc6890bis-04.txt> (Special-Purpose IP Address Registries) to Best Current Practice
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <148673973837.29207.1930720405178355242.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 13:11:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <125BB3C0-3D8B-4482-9E5E-1FD81C7AD703@vigilsec.com>
References: <148673973837.29207.1930720405178355242.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xEou5IldmPHai__myyL9f2wYG6A>
Cc: draft-bchv-rfc6890bis@ietf.org, mglt.ietf@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 18:11:46 -0000

In reviewing the document I noticed a small nit.  Otherwise it looks =
okay to me,.

In section 3.1:
s/Sections 4.1 and 4.3 [RFC2860]/Sections 4.1 and 4.3 of [RFC2860]/

Russ


> On Feb 10, 2017, at 10:15 AM, The IESG <iesg-secretary@ietf.org> =
wrote:
>=20
>=20
> The IESG has received a request from an individual submitter to =
consider
> the following document:
> - 'Special-Purpose IP Address Registries'
>  <draft-bchv-rfc6890bis-04.txt> as Best Current Practice
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-10. 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.
>=20
> Abstract
>=20
>=20
>   This memo updates the IANA IPv6 Special-Purpose Address Registries =
to
>   address issues raised by the definition of a global prefix.  For
>   completeness, this memo contains all the assignments made to the =
IANA
>   Special-Purpose Address Registries.
>=20
>   This memo obsoletes RFC 6890.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20
>=20


From nobody Thu Feb 23 10:45:53 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABCBA126D73; Thu, 23 Feb 2017 10:45:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CaDwxmRQnc3y; Thu, 23 Feb 2017 10:45:46 -0800 (PST)
Received: from mail-qt0-x22d.google.com (mail-qt0-x22d.google.com [IPv6:2607:f8b0:400d:c0d::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 3FE951296EE; Thu, 23 Feb 2017 10:45:46 -0800 (PST)
Received: by mail-qt0-x22d.google.com with SMTP id x35so36075705qtc.2; Thu, 23 Feb 2017 10:45:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=3TYZnVcPA64GExTopjankG0v6it3fbIT/QFNXhRuTMo=; b=BrllluSQMXHjiuSa2rronoq63YfhiefjK2c6WjaRtuj47YbuxAVw3EYTHUC4m/o1GK oMqL/ieWudZSs9iq0+BVXoPOEuAKd3w3htXOdDcykhRS2BKCqL7NX2g0uxDxcRmKVyJ0 0glJgE78aDDfn/Mn73oWLS9mo11mLLABG3vPwXI0juYQk+U8UYKdoPL5pBC2GqCZ6h9M lQk+iQH4FXrgLyKxIPLq87invj4kxNL6UbAX4idNQgyW07ijGfaDKd8k4JR4PcTsXKBE +tR2KTKxyPEL4IF4S9zgxLTJXfAifhWztIDznw8HqIz5IVl8dD3H0BkPcpJbAJ7dVzLk 1UJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=3TYZnVcPA64GExTopjankG0v6it3fbIT/QFNXhRuTMo=; b=eBm3O5xA65dsIPIqr3g5lJQKMP56OhkoJ2iiIeEv5ygd0/F5MxeoBptoTCKhl74yxC BxTKmaQ0koSD9hMQXZ4nmDtgk604oMDhWL78bXz2pYEs/GSQHdMYxtUZsP81RiFG4xm5 t0q09rmLfGUw1ejApx4vS3sKdv7UWnr7/FV5J8ejlWzeWMePK5sKd6p72tn182sAgFFm vrTuePK0UEh71bQso+Jt/JIB3PR8cqw3mhzmhGK1wnQfVXcx78TV8F6sSdNBEHX4ShJ3 Z52LxuBn1TfwdekT1G7V1LaVOAsOvHCRNiRaig4vvZoL87Rheg3+W/hqE0Awcue8GBRn xu4Q==
X-Gm-Message-State: AMke39kbbYTZHeA6JxUSFKP4M5YYRaTp/DQKYoaVr1drdIO56MRD5GwbU+FzCER8VPVhZ2WE64g49+cdrUg5lQ==
X-Received: by 10.200.56.48 with SMTP id q45mr2493297qtb.220.1487875545323; Thu, 23 Feb 2017 10:45:45 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.61.204 with HTTP; Thu, 23 Feb 2017 10:45:44 -0800 (PST)
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Thu, 23 Feb 2017 10:45:44 -0800
X-Google-Sender-Auth: _Ec79NoZrxS4TrgNfa7LrHAaV1c
Message-ID: <CAJE_bqe=4KruMwWOnSF7RO7TOQTdx48cG_4uSPkGptkG7R4ckw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gcM_339KxXKjtBW3jH65uwTNPTg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 18:45:48 -0000

At Thu, 23 Feb 2017 13:16:46 +0900,
Lorenzo Colitti <lorenzo@google.com> wrote:

> Help he understand, then. There is widely-deployed code that assumes that
> the interface ID is 64 and does not work on anything other than 64 bit
> prefix lengths.

Out of curiosity: which code is it, and exactly what does its
assumption mean?  Does it mean, for example, it allows manual
configuration of an address but requires its IID length be 64 bits?
(If it means something like this, I'd also wonder how its "IID"
matters in the first place - does that implementation use the lower 64
bits for some specific purpose?)

I thought general-purpose OSes are actually quite flexible about the
length of "IIDs" (in many cases it's actually derived from the length
of on-link prefix corresponding to the address).  I know BSD variants
are intentionally flexible on this.  I also know at least some (if not
all) kernel versions of Linux are flexible.

The only example of "widely-deployed code" with such an assumption
that I know of is ISC DHCPv6 client (though I'm not sure if its latest
version still has that assumption) as described in Section 4.4 of
RFC7421.  But I guess you're referring to something else.

If you can be more specific it might help provide some clarity for the
discussion, although I'm not so optimistic that it will automagically
resolve the conflicting views we are seeing.

--
JINMEI, Tatuya


From nobody Thu Feb 23 11:00:21 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3A812973E; Thu, 23 Feb 2017 11:00:20 -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 autolearn_force=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 1-4EOuf3CMBh; Thu, 23 Feb 2017 11:00:18 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 01B451295B7; Thu, 23 Feb 2017 11:00:17 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.foobar.org (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v1NJ0Ein095260 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Feb 2017 19:00:14 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.foobar.org
Message-ID: <58AF313D.3020905@foobar.org>
Date: Thu, 23 Feb 2017 19:00:13 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.10 (Macintosh/20170123)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KNfxHn3QMVLgWbp4iAKoOuDagc0>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 19:00:20 -0000

as it's currently worded, draft-ietf-6man-rfc4291bis seems to prohibit
the implementation of any interface netmask != /64:

>                                           However, the Interface ID of
>    all unicast addresses, except those that start with the binary value
>    000, is required to be 64 bits long.

This has substantial operational consequences in the ipv6 world because
if it's implemented as stated, it will cause production ipv6 networks to
break.

The ipv6 operational community may have opinions on the wisdom of
mandating new behaviour which would cause their networks to fall over,
so it would probably be a good idea to notify v6ops@ietf about the
existence of this draft so that the folks over there get a look-in
before a consensus call is made. As far as I can tell, this notification
never happened.

Nick


From nobody Thu Feb 23 11:07:42 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD37D1297E7 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 11:07:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=unavailable autolearn_force=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 eP5lWikNIB04 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 11:07:34 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5E6D12987B for <ietf@ietf.org>; Thu, 23 Feb 2017 11:07:33 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0FDA4617B1 for <ietf@ietf.org>; Thu, 23 Feb 2017 20:07:31 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 84BF6602C7; Thu, 23 Feb 2017 20:07:30 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 7780170D93; Thu, 23 Feb 2017 20:07:30 +0100 (CET)
Date: Thu, 23 Feb 2017 20:07:30 +0100
From: Gert Doering <gert@space.net>
To: Nick Hilliard <nick@foobar.org>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170223190730.GL2367@Space.Net>
References: <58AF313D.3020905@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58AF313D.3020905@foobar.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fSaekTarchElvPVJCPsThzwONXU>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 19:07:36 -0000

Hi,

On Thu, Feb 23, 2017 at 07:00:13PM +0000, Nick Hilliard wrote:
> as it's currently worded, draft-ietf-6man-rfc4291bis seems to prohibit
> the implementation of any interface netmask != /64:
> 
> >                                           However, the Interface ID of
> >    all unicast addresses, except those that start with the binary value
> >    000, is required to be 64 bits long.
> 
> This has substantial operational consequences in the ipv6 world because
> if it's implemented as stated, it will cause production ipv6 networks to
> break.

Unless I'm totally mistaken this wording has been in "the appropriate
RFC" (4291?) since the beginning of time.

Well, 4291 only mentions this in passing, and points to 3587 [GLOBAL], 
which points to [ARCH] with this sentence

   [ARCH] also requires that all unicast addresses, except those that
   start with binary value 000, have Interface IDs that are 64 bits long
   and to be constructed in Modified EUI-64 format.

[ARCH] is 3513, and states

   For all unicast addresses, except those that start with binary value
   000, Interface IDs are required to be 64 bits long and to be
   constructed in Modified EUI-64 format.

which very much sounds like the sentence above.


> The ipv6 operational community may have opinions on the wisdom of
> mandating new behaviour which would cause their networks to fall over,
> so it would probably be a good idea to notify v6ops@ietf about the
> existence of this draft so that the folks over there get a look-in
> before a consensus call is made. As far as I can tell, this notification
> never happened.

It's not a new mandate - but doing this document, a discussion might
be in order on whether it should still be worded as strictly.

But since nobody seemed to care for the last 14 years (3513 is 
standard track, published April 2003), why should people or vendors
bother to follow RFC mandates now...?

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

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


From nobody Thu Feb 23 11:09:04 2017
Return-Path: <job@ntt.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7711129967; Thu, 23 Feb 2017 11:09:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 DegD2DTE-m-2; Thu, 23 Feb 2017 11:09:02 -0800 (PST)
Received: from mail3.mlpsca01.us.to.gin.ntt.net (mail3.mlpsca01.us.to.gin.ntt.net [IPv6:2001:418:3ff:3::22]) (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 61B391297DE; Thu, 23 Feb 2017 11:08:59 -0800 (PST)
Received: by mail3.mlpsca01.us.to.gin.ntt.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88) (envelope-from <job@ntt.net>) id 1cgyl4-0004E2-ML (job@us.ntt.net); Thu, 23 Feb 2017 19:08:55 +0000
Date: Thu, 23 Feb 2017 20:08:46 +0100
From: Job Snijders <job@ntt.net>
To: Nick Hilliard <nick@foobar.org>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170223190846.GS89584@hanna.meerval.net>
References: <58AF313D.3020905@foobar.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <58AF313D.3020905@foobar.org>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RbY7oaxWrYi7QPzEaBPnm4FTBkU>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 19:09:03 -0000

On Thu, Feb 23, 2017 at 07:00:13PM +0000, Nick Hilliard wrote:
> as it's currently worded, draft-ietf-6man-rfc4291bis seems to prohibit
> the implementation of any interface netmask != /64:
> 
> >                                           However, the Interface ID of
> >    all unicast addresses, except those that start with the binary value
> >    000, is required to be 64 bits long.
> 
> This has substantial operational consequences in the ipv6 world because
> if it's implemented as stated, it will cause production ipv6 networks to
> break.
> 
> The ipv6 operational community may have opinions on the wisdom of
> mandating new behaviour which would cause their networks to fall over,
> so it would probably be a good idea to notify v6ops@ietf about the
> existence of this draft so that the folks over there get a look-in
> before a consensus call is made. As far as I can tell, this notification
> never happened.

This is not 'new', but it is a re-iteration of (in my opinion) a
specification of a non-optimal addressing architecture.

Aside from the newness, I agree with you. I would've hoped that when a
document like this is revised after 10+ years, people would think to ask
and include in dialogue the actual ipv6 operators whether reality is
aligned with the documented architecture.

rfc4291 (2006) "For all unicast addresses, except those that start with
                the binary value 000, Interface IDs are required to be
                64 bits long and to be constructed in Modified EUI-64
                format."

rfc3513 (2003) "For all unicast addresses, except those that start with
                binary value 000, Interface IDs are required to be 64
                bits long and to be constructed in Modified EUI-64
                format.

rfc2373 (1998) "The format prefixes 001 through 111, except for
               Multicast Addresses (1111 1111), are all required to have
               to have 64-bit interface identifiers in EUI-64 format.
               See section 2.5.1 for definitions."

Kind regards,

Job


From nobody Thu Feb 23 11:57:11 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C3F129A7D for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 11:57:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.799
X-Spam-Level: 
X-Spam-Status: No, score=-3.799 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, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gW4HEMJIIz5q for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 11:57:07 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 36BF71294F0 for <ietf@ietf.org>; Thu, 23 Feb 2017 11:57:07 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id B5DE69C3 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:57:06 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v8o4UO5cSjSD for <ietf@ietf.org>; Thu, 23 Feb 2017 13:57:06 -0600 (CST)
Received: from mail-vk0-f70.google.com (mail-vk0-f70.google.com [209.85.213.70]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 8274928C for <ietf@ietf.org>; Thu, 23 Feb 2017 13:57:06 -0600 (CST)
Received: by mail-vk0-f70.google.com with SMTP id x75so846460vke.5 for <ietf@ietf.org>; Thu, 23 Feb 2017 11:57:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Wi890lpbRgm6wKpYve/ho6YP1IE5kxnT6Iuq1Zm9HSw=; b=FryBvmh8EudnY1FEv6egWIbZgKgFdbuiUaVMMX+t/vd2xJ59RpcZUz+70BuPLWmKai TNSBep94BSD7AhxT78AJx7bpcyg9QGhKlDVUH88UcW+I9+Yh4HN5YpcldHV/lU4uCjuE s6ltHVsYO4KqPCyHRBzUtTKbhAdUSjUc7+/qJOcBCm3Ebyx6mTRCAkN0t4QS9+DJEq0J 2kdgOmCT6xg+IwT4HXN1i258s//nNCGB/8XOA3F50Cm4wZD9z2ZIU0wiou7EmWBYoZ3f bczazYKhFz+dEckr/AmNGw0ibYM0cJ3qsUOH8oEbuogf84yjGT/D25LP9PBQ38cgJtyu ldhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Wi890lpbRgm6wKpYve/ho6YP1IE5kxnT6Iuq1Zm9HSw=; b=UL5/phMP0KluRutJVFShZRta3+dpKaw9jtEpdyZrxRbpzzIK+o82nO9F2G0+PNRf7t x1vWFIBo0T70HpL4qDpb2tBGa8sqafIrXfugCZlUKLy0QzA4fiLyNq2Iq+UqoV+URdnr rnPcE1Ji/cig1UFTrrIyJlrFwiKrGG2kgIp2HW/R5ukpJX1S5sWZdpohI0AUE58b17O1 9tcMcxwplbapBmPP/sKJDMmY238TG/8QywmpHI2vzyEjz21bzPVQTgffTqHOMDombk8M eRJ6EDZUveLchO+l5wzv0Bnx+/zMnZ3DdAFNbQi30ovhk0yYrzJYxlx0kxBy+pPfLpjF 6qIw==
X-Gm-Message-State: AMke39mic1fcA9/rY8T/qvxqhnvVAg4iQKkAW9GE3qUMs0rFDBMyEMPeQvj4KS+1KLAJFqpih1gAmvatY8cC/8AMAjSVXEA7bgVz9bDEZpYTDptvD5CHhIhoT3T6PFdnxnDCU7PJj0ge2IgOJRE=
X-Received: by 10.176.3.72 with SMTP id 66mr5046461uat.163.1487879825975; Thu, 23 Feb 2017 11:57:05 -0800 (PST)
X-Received: by 10.176.3.72 with SMTP id 66mr5046449uat.163.1487879825771; Thu, 23 Feb 2017 11:57:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Thu, 23 Feb 2017 11:57:05 -0800 (PST)
In-Reply-To: <125BB3C0-3D8B-4482-9E5E-1FD81C7AD703@vigilsec.com>
References: <148673973837.29207.1930720405178355242.idtracker@ietfa.amsl.com> <125BB3C0-3D8B-4482-9E5E-1FD81C7AD703@vigilsec.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 23 Feb 2017 13:57:05 -0600
Message-ID: <CAN-Dau2T2TUmz1dU_PQdjsai_LPZhe=h+Yvis5NaL90f=hFU+Q@mail.gmail.com>
Subject: Re: Last Call: <draft-bchv-rfc6890bis-04.txt> (Special-Purpose IP Address Registries) to Best Current Practice
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary=001a113f26947c091d05493804f7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gy3VY8Wc2VkBrD8CKA2aldFFu0k>
Cc: draft-bchv-rfc6890bis@ietf.org, IETF <ietf@ietf.org>, mglt.ietf@gmail.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 19:57:10 -0000

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

I found something else;

In Table 17, 192.175.48.0/24 is incorrectly labeled as "Private-Use" and
should probably be "Direct Delegation AS112 Service"

Thanks.

On Thu, Feb 23, 2017 at 12:11 PM, Russ Housley <housley@vigilsec.com> wrote:

> In reviewing the document I noticed a small nit.  Otherwise it looks okay
> to me,.
>
> In section 3.1:
> s/Sections 4.1 and 4.3 [RFC2860]/Sections 4.1 and 4.3 of [RFC2860]/
>
> Russ
>
>
> > On Feb 10, 2017, at 10:15 AM, The IESG <iesg-secretary@ietf.org> wrote:
> >
> >
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'Special-Purpose IP Address Registries'
> >  <draft-bchv-rfc6890bis-04.txt> as Best Current Practice
> >
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2017-03-10. Exceptionally, comments may
> be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >   This memo updates the IANA IPv6 Special-Purpose Address Registries to
> >   address issues raised by the definition of a global prefix.  For
> >   completeness, this memo contains all the assignments made to the IANA
> >   Special-Purpose Address Registries.
> >
> >   This memo obsoletes RFC 6890.
> >
> >
> >
> >
> > The file can be obtained via
> > https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/
> >
> > IESG discussion can be tracked via
> > https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
> >
> >
>
>


-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr">I found something else;<div><br></div><div>In Table 17, <a=
 href=3D"http://192.175.48.0/24" target=3D"_blank">192.175.48.0/24</a> is i=
ncorrectly labeled as &quot;Private-Use&quot; and should probably be &quot;=
Direct Delegation AS112 Service&quot;</div><div><br></div><div>Thanks.</div=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Fe=
b 23, 2017 at 12:11 PM, Russ Housley <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:housley@vigilsec.com" target=3D"_blank">housley@vigilsec.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">In reviewing the document I not=
iced a small nit.=C2=A0 Otherwise it looks okay to me,.<br>
<br>
In section 3.1:<br>
s/Sections 4.1 and 4.3 [RFC2860]/Sections 4.1 and 4.3 of [RFC2860]/<br>
<br>
Russ<br>
<br>
<br>
&gt; On Feb 10, 2017, at 10:15 AM, The IESG &lt;<a href=3D"mailto:iesg-secr=
etary@ietf.org">iesg-secretary@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; The IESG has received a request from an individual submitter to consid=
er<br>
&gt; the following document:<br>
&gt; - &#39;Special-Purpose IP Address Registries&#39;<br>
&gt;=C2=A0 &lt;draft-bchv-rfc6890bis-04.txt&gt; as Best Current Practice<br=
>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 20=
17-03-10. Exceptionally, comments may be<br>
&gt; sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In=
 either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt;=C2=A0 =C2=A0This memo updates the IANA IPv6 Special-Purpose Address Re=
gistries to<br>
&gt;=C2=A0 =C2=A0address issues raised by the definition of a global prefix=
.=C2=A0 For<br>
&gt;=C2=A0 =C2=A0completeness, this memo contains all the assignments made =
to the IANA<br>
&gt;=C2=A0 =C2=A0Special-Purpose Address Registries.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0This memo obsoletes RFC 6890.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/" re=
l=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/dr=
aft-bchv-rfc6890bis/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-bchv-rfc6890bis/ball=
ot/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr=
>doc/draft-bchv-rfc6890bis/<wbr>ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email%3Afarm=
er@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking &amp; =
Telecommunication Services<br>Office of Information Technology<br>Universit=
y of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0 Cell: =
612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D </div>
</div>

--001a113f26947c091d05493804f7--


From nobody Thu Feb 23 12:16:48 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0259129A9E; Thu, 23 Feb 2017 12:16:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4368ryaAmxra; Thu, 23 Feb 2017 12:16:44 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCAF7129A8B; Thu, 23 Feb 2017 12:16:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 61A19BE3E; Thu, 23 Feb 2017 20:16:42 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tnglWHDyLc9J; Thu, 23 Feb 2017 20:16:41 +0000 (GMT)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id B3157BE38; Thu, 23 Feb 2017 20:16:40 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1487881001; bh=AjFh+hwxoaGT4Bg9EGW7Oh33/RsFfxfBSchIucXBhRw=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=YTm9gZZQH12Nack20ayVV3WpLbzMx3y017ljvkHbxSlH+xks1sU43iztItMbpS+GU 1PjvVIUQraJBnmJpslzQpf61HJBlKZSHp7ErrsSn7ZniALRcUgG4hQ/oOyHdL92d4Y YvcxRjTfV44NCNuBirr+vpA/QD4JnVj/woFIKbgM=
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>
Date: Thu, 23 Feb 2017 20:16:40 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2R6chPAJhdmCeBoGv7Vpuq8RIa5KjpgOq"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y01zhY6hhIasSM28G7y5V8C_JfI>
Cc: "spasm@ietf.org" <spasm@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 20:16:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2R6chPAJhdmCeBoGv7Vpuq8RIa5KjpgOq
Content-Type: multipart/mixed; boundary="m4Oprf2X5omJppHEuE2lgRu79Csoi6dwu";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: IETF general list <ietf@ietf.org>
Cc: "spasm@ietf.org" <spasm@ietf.org>
Message-ID: <841bb724-7403-4682-3d50-f878f63b0346@cs.tcd.ie>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt>
 (Internationalized Email Addresses in X.509 certificates) to Proposed
 Standard
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy>
 <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com>
 <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
In-Reply-To: <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>

--m4Oprf2X5omJppHEuE2lgRu79Csoi6dwu
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Folks,

I've just reviewed the IETF LC for this draft. Thanks all for
the comments and discussion which I think have thrown up some
real issues.

As of now, it is not clear to me that we have finished the
work with this one, at least the issues to do with name
constraints seem to me to call for some more WG consideration.

I think Russ (as lamps WG chair) has a similar opinion
that we're not done yet.

That said, I had put this on the March 16th IESG telechat
for consideration. If we do manage to reach a clear enough
consensus on a published revision to the draft in say the
next week then that schedule should still be fine. So I'd
encourage the authors and others who've commented to try
again and see if, in that timeframe, we can get to where
we're happy that the issues raised have been handled well
enough.

But, if it looks (as it does to me today) as if this'll take
a bit longer to figure out, then I figure the right thing to
do will be to let the lamps WG figure out how to proceed.
(And that'll mean that my successor as the responsible AD
for the lamps WG will handle further actions with the doc.)

Bottom line: if this isn't settled in the next week or so,
I'll take it off the March 16th IESG telechat and let the WG
continue the discussion.

Cheers,
S.

PS: To add to the name constraints discussion, I did wonder
if anyone really wants to use those. So for example, if we
defined the new name form so that certificate chains with
any name constraints at all and one of those names anywhere
are always treated as invalid, then would that cause any
real breakage? (It certainly would cause theoretical breakage,
but if that's all then I'd be ok with that:-)




--m4Oprf2X5omJppHEuE2lgRu79Csoi6dwu--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYr0MoAAoJEC88hzaAX42iSzwH/1yMzfZM6R6n2lSp/CA3UFqx
GiYs0O+mEjMu+u/12zZ0j3FZZok+o1YORo9G+oLq4MpdlMQ0TfB7mmXiHILrvwVq
8IcUFb06FVSeMZInALlQV1X+HlRtHNYMUBqBQXkyoirl4zslKndhno/OlYqtHMaG
yuUjLO02pcEsF8pFzQZ2V1sBh8fzCvBO9zKOYfKxm+HcpvioEhCUl3WWwlNOTPGG
hl7EhKDXcZeH2zOi0iORbdZkSevF1LxUlzvHAx2/2GICxaX9hMFZq07bvp2XutMX
uqreRG6GlfVc9Xz9UHwNc5MzHwXyH8sCIAQjC5h3MV/eagThqjL+apBLzVeb5cs=
=9iCT
-----END PGP SIGNATURE-----

--2R6chPAJhdmCeBoGv7Vpuq8RIa5KjpgOq--


From nobody Thu Feb 23 12:42:55 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B1DE12A2AC; Thu, 23 Feb 2017 12:42:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.499
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, HK_RANDOM_FROM=0.999, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0XIwXazwQVq; Thu, 23 Feb 2017 12:42:53 -0800 (PST)
Received: from mail-ua0-x22d.google.com (mail-ua0-x22d.google.com [IPv6:2607:f8b0:400c:c08::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 C8D4E12A2C3; Thu, 23 Feb 2017 12:42:52 -0800 (PST)
Received: by mail-ua0-x22d.google.com with SMTP id h65so1827523uah.0; Thu, 23 Feb 2017 12:42:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NMcxeJtsHtXvnQzih2JYZheUYftgMUF2Wr7A2ggwIEM=; b=Jk7aeqZdCHhIEGUPTz5gwgSyuZjTXtLa7n4LTutewLeMW+OpZ7KG6CLd1GtAziFauH zWMEC8HN02iwyilEiG43Tm6mPEYbg7spbCUzf0VmTDZtRVz4zKmAi8H0kNENP04wRRg5 WLM6Xb7iQyRJ8A1wbVFU+Ia0Oxq9mlyFXQ46meVstlH/mcIvvgqwIjcLGY5BDj1TPZKz ylP5hhxvlkS+xSSabayV9+T6AK+n4P+wQENCJAVScz9aPoHMIbA5iRlOOukfTwcXiCZR BRLMASBOtzZvUdg4tlsQb1+B3odqEmeFf0VHIFlUL/MvYRKi2e7Try7LlBI3YA4KBTHV Ag0Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NMcxeJtsHtXvnQzih2JYZheUYftgMUF2Wr7A2ggwIEM=; b=Jbj4m9HTaBvvkdZrhejUL3M2QAk2rxKI8NK+yGtNfxxiahnPhZY3ruQkgNlptagAbp KCzWYQ9BjslL5tFUF7crGYOSeBtfSEFowK0odfUtkUdCYFEkd4gBdixaeAMKjNsi3M1P zI0Z7lYx1PRFcoDbmnz8PPkAP4ozIbp5jOTmzqMRfV1GQt92ZbGk0o8AbGy4RFMfolio JrYz98jokPrHRQVRfbh0Epd3ovB/hza7kJB/uEeScHNQonbk1xRqNii/IlEMGmTDb4YR PovH4hgSZ74T/v7BwUeOWHFRHANJlS+oIFG1Ye/x2A0U0pgLQ0AUyp4gZuEtBAVGpdlk 8iSA==
X-Gm-Message-State: AMke39kv2O9Pwj1i9LaNLxQd6tdotsmu9duU48joRTYNeEi9iHQfKeanRaU6GNEXjK9KxlrU+LWYCcgu6CJobQ==
X-Received: by 10.176.74.86 with SMTP id r22mr10848568uae.18.1487882571891; Thu, 23 Feb 2017 12:42:51 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Thu, 23 Feb 2017 12:42:21 -0800 (PST)
In-Reply-To: <58AF313D.3020905@foobar.org>
References: <58AF313D.3020905@foobar.org>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 24 Feb 2017 07:42:21 +1100
Message-ID: <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Nick Hilliard <nick@foobar.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zh-UxT6emkWzL01AvAc-ur9T8I0>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 20:42:54 -0000

On 24 February 2017 at 06:00, Nick Hilliard <nick@foobar.org> wrote:
> as it's currently worded, draft-ietf-6man-rfc4291bis seems to prohibit
> the implementation of any interface netmask != /64:
>
>>                                           However, the Interface ID of
>>    all unicast addresses, except those that start with the binary value
>>    000, is required to be 64 bits long.
>

The thing is this is not new text, it has been in RFC4291 for 11
years. c.f., 2.5.1.

It can't be changed without invalidating all of the other RFCs that
have utilised 64 bit identifiers.

> This has substantial operational consequences in the ipv6 world because
> if it's implemented as stated, it will cause production ipv6 networks to
> break.

Going by the millions of IPv6 deployments now, it has been implemented
as stated.

>
> The ipv6 operational community may have opinions on the wisdom of
> mandating new behaviour which would cause their networks to fall over,

There is and should be no new behaviour in RFC4291bis, it is a tidy up
to advance it along the standard track.


> so it would probably be a good idea to notify v6ops@ietf about the
> existence of this draft so that the folks over there get a look-in
> before a consensus call is made. As far as I can tell, this notification
> never happened.
>
> Nick
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Thu Feb 23 13:46:25 2017
Return-Path: <ietf@augustcellars.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404E412940A; Thu, 23 Feb 2017 13:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=augustcellars.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LV7Za_VGJTP; Thu, 23 Feb 2017 13:46:17 -0800 (PST)
Received: from mail4.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 172B4129997; Thu, 23 Feb 2017 13:46:16 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; d=augustcellars.com; s=winery; c=simple/simple; t=1487886372; h=from:subject:to:date:message-id; bh=u7Vz5MbN7nAQN6W9gBIiMddB31v9jF7HvbVUsqBS3Qs=; b=WhyWd+EU83geu92MZaKj7LK6q9XxdwqkeW7Eb33PFsKTmYSgVKnsq6e7EzRTdiZ5lEhu9SxPwmM v4haIVQpapKhLfRI791bMHRkgE9lavOWo51GBqVfE88T4onvEQX9GcywVYLeUHpEeU1P5rzkIJm0G lpFbdCzkoJHL7y+WnhHdGGjHTuigLPLIfI8ZBunQgI2u7hgrsgNNkB8en7VrQNTCAH16rJQtVC3+L 86KWamYJb/0I1EF8LCStym0wqCDQNNpHkTIm6PKuTNty2SV7kQEPiOVNPK3xBNKgr+NKGUClB8enL GRrxFERlpCaSfNGIsreEZMfojTJwxyZF5chQ==
Received: from mail2.augustcellars.com (192.168.1.201) by mail4.augustcellars.com (192.168.1.153) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 23 Feb 2017 13:46:11 -0800
Received: from hebrews (173.8.216.38) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 23 Feb 2017 13:43:36 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: 'John C Klensin' <klensin@jck.com>, <ietf@ietf.org>
References: <148460673104.22580.543094070599448665.idtracker@ietfa.amsl.com> <E61E7383DDD7A81671C398EC@JcK-HP5.jck.com>
In-Reply-To: <E61E7383DDD7A81671C398EC@JcK-HP5.jck.com>
Subject: RE: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Date: Thu, 23 Feb 2017 13:44:53 -0800
Message-ID: <009201d28e1e$13337c30$399a7490$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLDY2fkRCgzG0ihtoVsZdX9vIbgygGIv4dMn4kvBMA=
X-Originating-IP: [173.8.216.38]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nLrKf301V6lVgTCLHIuftCRkSeQ>
Cc: spasm@ietf.org, lamps-chairs@ietf.org, draft-ietf-lamps-eai-addresses@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 21:46:19 -0000

John,

I have used and have seen used the term of US-ASCII to refer to 7-bit ASCII
as opposed to the full 8-bit ASCII.  I think that this generally makes sense
and therefore am unsure that the term should be removed.

Jim


> -----Original Message-----
> From: Spasm [mailto:spasm-bounces@ietf.org] On Behalf Of John C Klensin
> Sent: Sunday, January 22, 2017 11:47 AM
> To: ietf@ietf.org
> Cc: spasm@ietf.org; lamps-chairs@ietf.org; draft-ietf-lamps-eai-
> addresses@ietf.org
> Subject: Re: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt>
> (Internationalized Email Addresses in X.509 certificates) to Proposed
> Standard
> 
> 
> 
> --On Monday, January 16, 2017 2:45 PM -0800 The IESG <iesg-
> secretary@ietf.org> wrote:
> 
> > The IESG has received a request from the Limited Additional
> >Mechanisms for PKIX and SMIME WG (lamps) to consider the  following
> >document: - 'Internationalized Email Addresses in
> > X.509 certificates'   <draft-ietf-lamps-eai-addresses-05.txt>
> > as Proposed Standard
> >...
> 
> Hi.
> 
> This note is the result of a quick review for email, SMTPUTF8
> and general I18n issues only.   I have some questions about
> general comprehensibility but, in part because I have not carefully
followed
> the work that this extends, I'll leave those questions to others and the
RFC
> Editor.  Most of what follows is nit-picking, but significant parts of it
may
> affect the comprehensibility of the document and hence the ability of
> implementers, working it good faith, to conform and create interoperable
> implementations.
> 
> (1) The term "EAI" was the hastily-chosen short name/ abbreviation for a
> WG.  It is not the name of a protocol, system, technique, etc.  The
relevant
> standards-track RFCs are very clear that, if a reference is made to the
> relevant SMTP extension and associated protocols, the term should be
> "SMTPUTF8".  "Internationalized Email Addresses" in the title is ok, but
there
> should be no IANA registry, subregistry, or module that uses the "EAI"
> terminology.
> 
> (2) The base document [RFC5280] is referenced as depending on RFC 5322
> addresses.  822-addresses (used in message headers,
> etc.) are not the same as 821-addresses (used in the SMTP envelope).  One
> can make a case for either, but neither is a proper subset of the other.
This is
> important in this context because the document then talks about extending
> 5280 to accommodate RFC 6531-style addresses.  Those are envelope-style
> addresses, not message header-style ones.  I think the protocol specifics
may
> be ok due to the language in the third (" This document further
refines..."
> and subsequent paragraphs in Section 3, but the explanation could easily
be
> a source of confusion and may need some clarification.
> 
> Note that, as proposals are kicked around that move information from the
> mailbox name to the descriptive phrase (which does not exist in envelope
> names) during mailing list expansion or some models of post-delivery
> SMTPUTF8 "downgrading", any confusion about this issue may become
> important (again, the I-D explicitly prohibits the phrase, but only after
talking
> a lot about 822-style addresses).
> 
> (3) A MUST NOT requirement on the use of A-labels has often been
> problematic because, as far as a protocol that does not support IDNA is
> concerned, they are ordinary labels conforming to the "preferred syntax"
of
> RFC 1034/1035 (commonly known as "LDH syntax").  As important, it is
easily
> possible to construct strings that look (lexically) like A-labels but are
actually
> not
> A-labels.   If the desire is to prevent the use of anything but
> normal (i.e., not IDNA) LDH labels and U-labels, the restriction that is
> probably needed is either "no label starting in 'xn--'"
> or "no label starting in two letters followed by two hyphen-minus
> characters".  Requiring NR-LDH restrictions probably solves the problem
> (although I'm not sure what "solely ASCII character labels" means -- see
(2)
> above) but requires much more specific knowledge of the IDNA2008 protocol
> set (particularly RFC 5890 in this case) than I predict readers of this
document
> will have.  See RFC 5890 and 5894 for more discussion on this issue and
other
> recent correspondence about confusing and contradictory usage of "IDN"
> and "IDNA" and the associated risks for additional details and risk
> descriptions.
> 
> (4) The second paragraph of Section 4 appears to me to be correct.
> However, for reasons related to those discussed above, these are not
strictly
> "conversion" because the operations may fail (and will fail if the
U-labels or
> A-labels are not strictly valid).  It would probably be useful to be
explicit that
> one of the effects of this definition is to absolutely prohibit domains
that do
> not conform to IDNA2008 from appearing in certificates (IMO, that is A
Good
> Thing).
> 
> (5) It may be worth being explicit that there is no normalization or case-
> folding permitted with the local-part.
> The current text does say that but it may not be obvious to someone not
> thoroughly familiar with other specs.
> 
> (6) I assume the RFC Editor would catch this, but the name of the CCS that
is
> historically most often used for/on the Internet is "ASCII" not "ascii" or
some
> other variation.  "US-ASCII" is common to but, since there isn't any
non-US-
> ASCII", a little redundant unless reference is being made to the relevant
> media type rather than the CCS.  The I-D appears to use "ASCII" and
"ascii"
> inconsistently.
> 
> (7) In part because of the normalization issue mentioned briefly above,
the
> Security Considerations section should probably mention not only "visually
> similar characters" but "visually identical strings".  Note that, at least
modulo
> the non-decomposing character issue, RFC 5890 does not have that problem
> because IDNA requires that all input strings be NFC-conforming.
> 
> (8) Perhaps no one cares, but the notation used in Appendix B for
> "\u8001\u5E2B@example.com" does not appear to be referenced or
> described anywhere in the document, nor is it consistent with the
> recommendations of RFC 5137.
> 
> best,
>    john
> 
> 
> 
> _______________________________________________
> Spasm mailing list
> Spasm@ietf.org
> https://www.ietf.org/mailman/listinfo/spasm


From nobody Thu Feb 23 14:02:59 2017
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 964C4129B4F; Thu, 23 Feb 2017 14:02:51 -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, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5levUU8IIrWa; Thu, 23 Feb 2017 14:02:48 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3A9E1296D5; Thu, 23 Feb 2017 14:02:48 -0800 (PST)
Received: from [198.252.137.70] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1ch1TL-000Hcz-NF; Thu, 23 Feb 2017 17:02:47 -0500
Date: Thu, 23 Feb 2017 17:02:41 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jim Schaad <ietf@augustcellars.com>, ietf@ietf.org
Subject: RE: [Spasm] Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
Message-ID: <70BCBC4290ABB6783F608C84@PSB>
In-Reply-To: <009201d28e1e$13337c30$399a7490$@augustcellars.com>
References: <148460673104.22580.543094070599448665.idtracker@ietfa.amsl.com> <E61E7383DDD7A81671C398EC@JcK-HP5.jck.com> <009201d28e1e$13337c30$399a7490$@augustcellars.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.70
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LJPZ82GapAx0Lbb5vfSNFMf93WE>
Cc: spasm@ietf.org, lamps-chairs@ietf.org, draft-ietf-lamps-eai-addresses@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 22:02:51 -0000

--On Thursday, February 23, 2017 13:44 -0800 Jim Schaad
<ietf@augustcellars.com> wrote:

> I have used and have seen used the term of US-ASCII to refer
> to 7-bit ASCII as opposed to the full 8-bit ASCII.  I think
> that this generally makes sense and therefore am unsure that
> the term should be removed.

Jim,

I don't have time to go through this again, but...

(1) Depending on what you count, there is either no such thing
as "8-bit ASCII" ("full" or otherwise) or it can refer to any of
the following:

 (i) 7-bit ASCII in octets with leading zero bits, as
	described in RFC 20 and other places.
	
 (ii) ISO 8859-1 (aka "Latin-1")
	
 (iii) The entire ISO 8850 family, or at least the subset
	of it that have all or most of ASCII (or at least ISO
	646 IRV) in the low-order seven bits

So it either doesn't mean what you think it means, or it is
hopelessly ambiguous.

"US-ASCII" is a different matter.  It is a term of art in the
IETF, referring to a "charset" that was specified as part of
MIME and is now listed in the IANA charset registry.  It is
essentially equivalent to the first definition above.
Unfortunately, "US ASCII" is used in some other contexts to
refer to other things, in particular to distinguish between the
repertoire of [7 bit) ASCII (i.e., ANSI X3.4) and that of ISO
646 IRV and BV.    I personally think the IETF would be better
off if we retired the term but YMMD (indeed, I'm probably in the
rough), and I'm therefore ok with its use in this context as
long as there is a normative reference pointing to a clear
definition.

My problem is not "remove the term" but being absolutely sure
that whatever terminology you use is completely unambiguous.

best,
    john




From nobody Thu Feb 23 14:05:42 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D2C2129B56 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 14:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 tx_BB6YwsHck for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 14:05:36 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 146CB129B69 for <ietf@ietf.org>; Thu, 23 Feb 2017 14:05:34 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 37820617A7 for <ietf@ietf.org>; Thu, 23 Feb 2017 23:05:32 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id D205A60ED1; Thu, 23 Feb 2017 23:05:31 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id C797D704D8; Thu, 23 Feb 2017 23:05:31 +0100 (CET)
Date: Thu, 23 Feb 2017 23:05:31 +0100
From: Gert Doering <gert@space.net>
To: Mark Smith <markzzzsmith@gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170223220531.GU2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pqOPQJZ490mZFT8MX7Pkm8F9ulg>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 22:05:37 -0000

Hi,

On Fri, Feb 24, 2017 at 07:42:21AM +1100, Mark Smith wrote:
> It can't be changed without invalidating all of the other RFCs that
> have utilised 64 bit identifiers.

Except for the few that explain how to use /126 or /127, right?

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

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


From nobody Thu Feb 23 14:14:56 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F24E0129B0F; Thu, 23 Feb 2017 14:14:54 -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 autolearn_force=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 rwLrawZw8dUh; Thu, 23 Feb 2017 14:14:53 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40A4A1299E3; Thu, 23 Feb 2017 14:14:53 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.foobar.org (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v1NMEovl018459 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Feb 2017 22:14:51 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.foobar.org
Message-ID: <58AF5ED9.7060006@foobar.org>
Date: Thu, 23 Feb 2017 22:14:49 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.10 (Macintosh/20170123)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net>
In-Reply-To: <20170223190730.GL2367@Space.Net>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hBZSikg_8y2kACu59WnHH2YrILk>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 22:14:55 -0000

Gert Doering wrote:
> Unless I'm totally mistaken this wording has been in "the appropriate
> RFC" (4291?) since the beginning of time.

it has, but it was updated over the years by several other drafts which
proposed the use of other appropriate interface netmasks, including e.g.
rfcs 6164 and 7608.  The importance of 7608 is that netmasks longer than
/64 have no relevance unless there are interface netmasks longer than /64.

> But since nobody seemed to care for the last 14 years (3513 is 
> standard track, published April 2003), why should people or vendors
> bother to follow RFC mandates now...?

If the IETF mandates something that's both unenforceable and which will
cause breakage if implemented, this makes the IETF look rather foolish.

Nick


From nobody Thu Feb 23 14:43:58 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CECEE129BC2 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 14:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vF-Nu2phtNt0 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 14:43:54 -0800 (PST)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (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 3BBC4129BBF for <ietf@ietf.org>; Thu, 23 Feb 2017 14:43:54 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id B405E602 for <ietf@ietf.org>; Thu, 23 Feb 2017 22:43:53 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IybojWBwoFl5 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:43:53 -0600 (CST)
Received: from mail-ua0-f198.google.com (mail-ua0-f198.google.com [209.85.217.198]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id 85989A87 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:43:53 -0600 (CST)
Received: by mail-ua0-f198.google.com with SMTP id 72so3408271ual.6 for <ietf@ietf.org>; Thu, 23 Feb 2017 14:43:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xJ/eh1msA8dUkCsdpC9At06kkb5RUxs3jyr6X/lZQ/E=; b=EnYTdOQ/5lcOPYsxa2IlSdAb7MScSaviYY6RqFSVtcJVF9yYiWJnewVPHS17+7hu9Q szUkQ0t2sg1se4mvip9qhfZqn9EkbKRG2Mod8GNdU3+P9THFfc+joEGdP5kTXp6/WV4J pSmH473h2icQo369tluWdFYyz9x0qwcTZvMxqfgzSHjP3FYQMlyXuD+x90mKh3b6cNLb PrbO4EfrhOPttTE/tAl7Iky4y83/9UPeYQIS9WwmSgpmV0YZ5eo1vB7AKvkbKScuAIlD q1Cb1gIp6yDeBwWx5ucwy6NsF/uUa7CzwSZIU11zqyFt1BNMMEvDs0mimpNRh1Ab5G8U RqCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xJ/eh1msA8dUkCsdpC9At06kkb5RUxs3jyr6X/lZQ/E=; b=gTCxizYt3vA/lByGwbsotsWa9CV5Z41ZydjQq4ZbAbuz7FAvZiag/BZIswrMtA/w7f /YU/RbxaPQj+g3apGARqujxU8Q1LyHHw+HOe5MWy19UmYEPgKg2Rwe0h5yzHHMfd5aPj GVdkeX5yS+kNJBNY2oitWHXKuydrO3P8d2CTJEbvzL9JWBQ+3T66YGQVp96CyfsmE3cI ywzWuNyZd2vdJN6Tc/2RLE8tQXUYZF3PdmGUBgLIIbnCJVAhL/6WCH/qhvXhWVcp+3ld jCsGT0EO3w/CZra1q80Nukv1vbQZJdUUQVZjKmtCzHK/31/A4WFcB/BaQrsv14hmxORD pEJQ==
X-Gm-Message-State: AMke39lmGzymTNZipm0Te7TGTMhEJznefUa9gHYpfTPVYh2rLxNV3A5fRF7q9eUyPHpuBxnFnW/z0TGr7XMOCX/FGF063KXpOxF/+AqZFPhXuMKqDP5rkP7XhNjfUdAX0XC+ir3LXC7nptdUXyE=
X-Received: by 10.31.49.81 with SMTP id x78mr19802502vkx.82.1487889833009; Thu, 23 Feb 2017 14:43:53 -0800 (PST)
X-Received: by 10.31.49.81 with SMTP id x78mr19802487vkx.82.1487889832766; Thu, 23 Feb 2017 14:43:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Thu, 23 Feb 2017 14:43:51 -0800 (PST)
In-Reply-To: <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com>
From: David Farmer <farmer@umn.edu>
Date: Thu, 23 Feb 2017 16:43:51 -0600
Message-ID: <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a114388b0f2872f05493a5864
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GqXpOu5dV65aLWb-B81QqQ2asAI>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 22:43:57 -0000

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

On Wed, Feb 22, 2017 at 10:16 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:
>
> Help he understand, then. There is widely-deployed code that assumes that
> the interface ID is 64 and does not work on anything other than 64 bit
> prefix lengths. Currently that code is correct on all unicast space. If you
> change RFC 4291, won't that code be incorrect?
>

OK, what if we said something like this;

   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198]. However, all implementations of IPv6 are REQUIRED to
   support an IID length of 64 bits, other IID lengths are OPTIONAL.
   Subnet prefixes of /64 are RECOMMENDED for general purpose use,
   subnet prefixes of /127 are RECOMMENDED for point-to-point router
   links [RFC6164], other subnet prefix lengths are NOT RECOMMENDED,
   as their use could be incompatible with some implementations of IPv6.
   The rationale for the 64 bit boundary in IPv6 addresses can be found
   in [RFC7421].

I'd prefer other IID lengths to be RECOMMENDED for implementations, but I
can live with OPTIONAL.



-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 22, 2017 at 10:16 PM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>He=
lp he understand, then. There is widely-deployed code that assumes that the=
 interface ID is 64 and does not work on anything other than 64 bit prefix =
lengths. Currently that code is correct on all unicast space. If you change=
 RFC 4291, won&#39;t that code be incorrect?</div></div></div></div>
</blockquote></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail=
_extra">OK, what if we said something like this;</div></div><div class=3D"g=
mail_extra"><br>=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of a=
ny valid length up to<br>=C2=A0 =C2=A0128 [BCP198]. However, all implementa=
tions of IPv6 are REQUIRED to<br>=C2=A0 =C2=A0support an IID length of 64 b=
its, other IID lengths are OPTIONAL.<br>=C2=A0 =C2=A0Subnet prefixes of /64=
 are RECOMMENDED for general purpose use,<br>=C2=A0 =C2=A0subnet prefixes o=
f /127 are RECOMMENDED for point-to-point router<br>=C2=A0 =C2=A0links [RFC=
6164], other subnet prefix lengths are NOT RECOMMENDED,<br>=C2=A0 =C2=A0as =
their use could be incompatible with some implementations of IPv6.<br>=C2=
=A0 =C2=A0The rationale for the 64 bit boundary in IPv6 addresses can be fo=
und<br>=C2=A0 =C2=A0in [RFC7421].</div><div class=3D"gmail_extra"><br>I&#39=
;d prefer other IID lengths to be RECOMMENDED for implementations, but I ca=
n live with OPTIONAL. =C2=A0 =C2=A0 =C2=A0=C2=A0<br></div><div class=3D"gma=
il_extra"><br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmai=
l_extra"><div><br></div>-- <br><div class=3D"gmail_signature">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email=
%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking=
 &amp; Telecommunication Services<br>Office of Information Technology<br>Un=
iversity of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0=
 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D </div>
</div></div>

--001a114388b0f2872f05493a5864--


From nobody Thu Feb 23 14:44:13 2017
Return-Path: <SRS0=0eqy=2E=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEE2129BD8; Thu, 23 Feb 2017 14:44:00 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 rEQYbLj2eVLu; Thu, 23 Feb 2017 14:43:57 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A28BC129BC9; Thu, 23 Feb 2017 14:43:57 -0800 (PST)
Received: from [10.61.217.135] (unknown [173.38.220.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id D46D9564671; Thu, 23 Feb 2017 23:43:53 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com>
Date: Thu, 23 Feb 2017 23:43:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com>
To: Mark Smith <markzzzsmith@gmail.com>
X-Mailer: Apple Mail (2.3259)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Feb 23 23:43:55 2017 +0100 (CET))
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7Oc307grKPOK9lGPTU7sySxdR3Q>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 22:44:00 -0000

> Le 23 f=C3=A9vr. 2017 =C3=A0 21:42, Mark Smith =
<markzzzsmith@gmail.com> a =C3=A9crit :
>=20
> On 24 February 2017 at 06:00, Nick Hilliard <nick@foobar.org> wrote:
>> as it's currently worded, draft-ietf-6man-rfc4291bis seems to =
prohibit
>> the implementation of any interface netmask !=3D /64:
>>=20
>>>                                          However, the Interface ID =
of
>>>   all unicast addresses, except those that start with the binary =
value
>>>   000, is required to be 64 bits long.
>>=20
>=20
> The thing is this is not new text, it has been in RFC4291 for 11
> years. c.f., 2.5.1.

And during those 11 years. Nobody implemented this rule specific to =
::/3.

>=20
> It can't be changed without invalidating all of the other RFCs that
> have utilised 64 bit identifiers.

Those "other RFCs" have nothing to do with being part of ::/3 or not.
They require an interface identifier of 64 bits long.
The fact that a protocol does not work in some conditions does not =
invalidate the protocol.
e.g. the fact that SLAAC over Ethernet doesn't work when IID is not 64 =
doesn't mean
the IID could not be 64 bits long. It just means that under those =
conditions, SLAAC would not work.
And those conditions are perfectly well defined in those "other RFCs".

- Pierre

>=20
>> This has substantial operational consequences in the ipv6 world =
because
>> if it's implemented as stated, it will cause production ipv6 networks =
to
>> break.
>=20
> Going by the millions of IPv6 deployments now, it has been implemented
> as stated.
>=20
>>=20
>> The ipv6 operational community may have opinions on the wisdom of
>> mandating new behaviour which would cause their networks to fall =
over,
>=20
> There is and should be no new behaviour in RFC4291bis, it is a tidy up
> to advance it along the standard track.
>=20
>=20
>> so it would probably be a good idea to notify v6ops@ietf about the
>> existence of this draft so that the folks over there get a look-in
>> before a consensus call is made. As far as I can tell, this =
notification
>> never happened.
>>=20
>> Nick
>>=20
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>=20
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops


From nobody Thu Feb 23 15:04:06 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E089A129B9B; Thu, 23 Feb 2017 15:03:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2yyWslKB_kCD; Thu, 23 Feb 2017 15:03:57 -0800 (PST)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com [IPv6:2607:f8b0:400d:c09::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 B2CE8129B49; Thu, 23 Feb 2017 15:03:57 -0800 (PST)
Received: by mail-qk0-x235.google.com with SMTP id x71so5568327qkb.3; Thu, 23 Feb 2017 15:03:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=WteCHQcqoo5VkyRnW8P8ro88xeVnIiINRVYJmjI8Pwc=; b=uyKnAP2lRUWQxoGYj3IwVmMQa3Mo2+uGRow0ooFvRYomc/Q3aCJ4xagWp6uXDF5dWm CqjHwGtJQLZkFDXpfT9x/VGVWOLMK1sjM79HyqNNrSIi8ZJqnJEmm5fZzSnLZxcwt1de yPp0GjsfFz/xT6/yrYD7fnmYBXYs816RrLSP2KV9zR/ccbsebQlFxcIsb3TpWwAVTmEP DvRZ3R4EMcJFG8zfLSFbuFQt7k4zv89L62gPZhR/N3SLWu4ha1wDn4YKC1nGJCYbQUDK Zw7cTMqdW1aPSZiBFx1HrjoHdnE8wgj4b8MWxdkeB1epDXk1W6fq/hA+y1QvFI6L30u3 vbdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=WteCHQcqoo5VkyRnW8P8ro88xeVnIiINRVYJmjI8Pwc=; b=LkuMppcpGYP4tnehOjCZ66fJ6b7UkkUrts4/bcVo7L3buRRxus0rgBopmlJokEmQ/U GsIFs0DJ+shp6fHlKAcRFo2UgE+tGS7jP7bEiCDork6i1lIpCJgqISPe3mA+AcDiZjoe psbJNHJ4+kM98fwY4fsjpef7NkcPqYRG4fuoUOpKY1eVSvCBvU4H4Vhge0T8o82kf9x2 M/CTgJLzzb8a+OiuYTmkDgvgt6+LbFh+lToxXhqkPRLgq66RPYdyTzG0YQQ4mGMKvk7t 9Kmc1IIPQmtrTQHDZU5x21XbttCmXdOX3jhv9DIydLe9AkkhZQDO29bYeZEMG3JVcO2h 5Ggg==
X-Gm-Message-State: AMke39nYOCRlpsl66TEsCqqkDen+FHvMYIE77kG3DzR9dQx+EeROV2VhCZ24f0qZgctEikZBgJCVPFyYmDJDmQ==
X-Received: by 10.55.140.134 with SMTP id o128mr36894026qkd.58.1487891036952;  Thu, 23 Feb 2017 15:03:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.91.71 with HTTP; Thu, 23 Feb 2017 15:03:56 -0800 (PST)
In-Reply-To: <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <m2a89dveop.wl-randy@psg.com> <CAKD1Yr1igJiL_2BVi=RL_Wkd6V0O6WaPJ5fMS+ggVkTRAOdPXw@mail.gmail.com>
From: Christopher Morrow <christopher.morrow@gmail.com>
Date: Thu, 23 Feb 2017 18:03:56 -0500
Message-ID: <CAL9jLaaJXdqM9mKefr7_NzcVBhDSPPniHUO0VfVMRUhPDUb7Tw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=94eb2c0548d8b8f64705493aa058
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QURELHciibZ6C52l0fp-ZaUjM7Y>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 23:03:59 -0000

--94eb2c0548d8b8f64705493aa058
Content-Type: text/plain; charset=UTF-8

On Wed, Feb 22, 2017 at 11:13 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Thu, Feb 23, 2017 at 11:11 AM, Randy Bush <randy@psg.com> wrote:
>
>> users do not notice, except when device programmers break things.  i am
>> a host operator, and i do not need classfulness.  slaac is nice in small
>> lans, and the /64 id is fine for the slaac niche.
>>
>
> Please think about the arguments in RFC 7934. If some misguided operator
> assigns your device exactly one IPv6 address, that hugely constrains what
> the device can do and how well it does it. And I do think that users notice
> when their network is flaky.
>
>

A bunch of networks do silly things... they aren't going to stop doing
those silly things just because the IETF says something, are they?

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Feb 22, 2017 at 11:13 PM, Lorenzo Colitti <span dir=3D"ltr">&lt=
;<a href=3D"mailto:lorenzo@google.com" target=3D"_blank">lorenzo@google.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
div class=3D"gmail_extra"><div class=3D"gmail_quote"><span class=3D"">On Th=
u, Feb 23, 2017 at 11:11 AM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">users do not notice, ex=
cept when device programmers break things.=C2=A0 i am<br>
a host operator, and i do not need classfulness.=C2=A0 slaac is nice in sma=
ll<br>
lans, and the /64 id is fine for the slaac niche.<br></blockquote><div><br>=
</div></span><div>Please think about the arguments in RFC 7934. If some mis=
guided operator assigns your device exactly one IPv6 address, that hugely c=
onstrains what the device can do and how well it does it. And I do think th=
at users notice when their network is flaky.</div><span class=3D""><div>=C2=
=A0</div></span></div></div></div></blockquote><div><br></div><div>A bunch =
of networks do silly things... they aren&#39;t going to stop doing those si=
lly things just because the IETF says something, are they?=C2=A0</div></div=
></div></div>

--94eb2c0548d8b8f64705493aa058--


From nobody Thu Feb 23 15:40:22 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADEF6129C68; Thu, 23 Feb 2017 15:40:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2rDZWxm9HKlr; Thu, 23 Feb 2017 15:40:19 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003: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 A2E96129C55; Thu, 23 Feb 2017 15:40:19 -0800 (PST)
Received: by mail-oi0-x235.google.com with SMTP id 65so3427820oig.1; Thu, 23 Feb 2017 15:40:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=KJKbH4J6SyxjqPhDPA3Duv0Jl3NUGFcSTLa/Y9N5eEg=; b=a8Rr+VT0SGWStoSnBuuND/EfAcapEudDWjZfcYcZsHEeAewqWEluDFFi7cVO/+Qv5g 5fipM1szzecW2idUneMC0r5coQZC59VgUjEmaWU8vmbrFgUNW7/qh12uXQanq+HKvJP+ Vob+1ehL1QaxwQxXJJmIanYaGkG+1zhJ93c2N2ds73sbfRb1MWhOPKedDkcx12bCSwPS zI+KRNHdy4uojzQ8ohdwugHc9WogW1g0Hw15XHg8d4kRRWi11eHxgEy6M6XHGAnzmmIw BwQU60KlgZIK3MwEm4HVmXuV6soT/SzXEhKUdcEMycvI+/0HWbL2TXk9ul0LuyELaVMW 1beQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=KJKbH4J6SyxjqPhDPA3Duv0Jl3NUGFcSTLa/Y9N5eEg=; b=Bl4KY+nse6VuxfuwrM3NFcH9ShTyM9RfgRN1fBn1NS0MUoq4C/LFfXDtjRgD8o+Ese ajPF0YjLnpNYxZc1INEuxlcawgl7JXjmGRSF0m56fMkC59PLvjvz8UwZIJsi1pyytKIT TzLOdDZdfFSVjfWkzO+r1OAWN64XDeQTshxIxBj4QF8AErc/ZGX0xV4h65pzykn0p3gV JsaD3L4JRMZn0nzTnPNJwZzfGHfKJlFLaYF/oy/ivVIY1jgDoCa/IK0D/TTFD2onih5H Fc7Qq5YWSR3OrZvx9CiLlYdIxv84hYVxT8LejC4cRW/0Eut06nfWrtyF1UNkLL+bwGW2 xmDg==
X-Gm-Message-State: AMke39ncLiW4oRMByOoH6KyLblbV3+VU+9HejcocP1alooRWXoC488JNiDhTWIu5eR3qk5RiLc2MU8nSIVET6A==
X-Received: by 10.202.72.6 with SMTP id v6mr617138oia.177.1487893218761; Thu, 23 Feb 2017 15:40:18 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Thu, 23 Feb 2017 15:39:48 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 23 Feb 2017 15:39:48 -0800
Message-ID: <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=001a113db248c4a3e305493b227f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0JCjvUqy5L7NFyY9g_n8HdEmPIc>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 23:40:21 -0000

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

HI Mohamad,

Thanks for rechecking; some further comments in-line.

On Wed, Feb 22, 2017 at 11:21 PM, <mohamed.boucadair@orange.com> wrote:

> Hi Ted,
>
>
>
> Thank you for the reply and for implementing these changes.
>
>
>
> I checked the diff, but I=E2=80=99m afraid the -06 version has the same i=
ssues as
> the ones I reported in January 31.
>
>
>

I did respond to the particular comments and text proposals, so I assume
this is the more general issue.  If I understand correctly, you would
prefer this document to be structured as a revision to the threat model
document or connected to a larger consideration of the issues.  I
understand that, and it was considered, but I believe that this format is
still the most effective for the narrow issue it addresses.

>From that flow some of your other concerns about audience, at least as I
understand.  As written, this is narrow advice for a broad audience:
basically, anyone who would consider the form of metadata insertion it
describes.  You would, if I understand you, prefer a narrower description
of the audience in a larger context.


> I=E2=80=99m reiterating that most of my comments are still unaddressed in=
 -06.
>
>
>

I realize that the document did not change to address the audience or
document integration you preferred; I think there we simply disagree on how
to make this advice effective.  I'm sorry that first message apparently did
not describe the disagreement effectively.

If I have misunderstood your comments, please accept my apologies. I would
be happy of further clarification and suggested text to illustrate your
preferences would be especially welcome.

thanks,

Ted Hardie



> Cheers,
>
> Med
>
>
>
> *De :* Ted Hardie [mailto:ted.ietf@gmail.com]
> *Envoy=C3=A9 :* mercredi 22 f=C3=A9vrier 2017 23:09
> *=C3=80 :* BOUCADAIR Mohamed IMT/OLN
> *Cc :* ietf@ietf.org; draft-hardie-privsec-metadata-insertion@ietf.org
> *Objet :* Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
> (Design considerations for Metadata Insertion) to Informational RFC
>
>
>
> Hi Mohamed,
>
> Thanks for your review.  I've uploaded a draft -06 with updates from your
> and other reviews.  Some notes in-line.
>
>
>
> On Tue, Jan 31, 2017 at 1:49 AM, <mohamed.boucadair@orange.com> wrote:
>
> Dear Ted,
>
> Please find below my general review of the document and also my detailed
> comments.
>
> * Overall:
> - I don't think the document is ready to be published as it is. It does
> not discuss the usability and implications of the advice. Further, it may
> be interpreted that a client/end system/user can always by itself populat=
e
> data that is supplied by on-path nodes (in current deployments). That's
> assumption is not true for some protocols.
> - The purpose of publishing this advice is not clear. For example, how
> this advice will be implemented in practice? What is its scope?
> - I would personally prefer an updated version of RFC7258 with more stric=
t
> language on the privacy-related considerations. This is more actionable
> with concrete effects in documents that will required to include a
> discussion on privacy related matters.
>
> Detailed comments are provided below:
>
> * The abstract says the following:
>
>    The IAB has published [RFC7624] in response to several revelations of
>    pervasive attack on Internet communications.  This document considers
>    the implications of protocol designs which associate metadata with
>    encrypted flows.  In particular, it asserts that designs which do so
>    by explicit actions of the end system are preferable to designs in
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    which middleboxes insert them.
>
> I suggest you explicit what is meant by "the end system".
>
>
>
> I have updated this to clarify that this is the host/end system not the
> user.
>
>
> If you mean the owner/user, then the text should say so. If you mean a
> client software instance, then bugs/inappropriate default values may lead
> to (privacy leak) surprises too. It was reported in the past that some
> browsers inject the MSISDN too.
>
> * Introduction: "To ensure that the Internet can be trusted by users"
>
> Rather =C2=AB To minimize the risk of Internet-originated attacks targete=
d at
> users =C2=BB.
>
>
>
> I've adopted this language.
>
>
>
> It's reasonable to claim the Internet can be trusted by users; see how th=
e
> usage of social networks has become severely twisted for example
>
>
>
> I've also considered your point that an updated version of RFC7258 might
> be a better outlet for advice like this. We did consider several
> approaches, including incorporating the text in an update to  RFC 3552 or
> as part of a document describing the full set of companion mitigations to
> the threats in RFC 7624 (draft-iab-privsec-confidentiality-mitigations
> would be one approach).  Those are all valid approaches, but it seemed th=
at
> short, easily read documents tackling a single point might be easier to
> produce and consume.
>
> Thanks again for your review,
>
> Ted Hardie
>
>
>

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

<div dir=3D"ltr">HI Mohamad,<br><br>Thanks for rechecking; some further com=
ments in-line.<br><br>On Wed, Feb 22, 2017 at 11:21 PM,  <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mohamed.boucadair@orange.com" target=3D"_blank">moham=
ed.boucadair@orange.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"FR">
<div class=3D"m_-2746598804484943185WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Hi Ted,<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Thank you for the reply and for=
 implementing these changes.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">I checked the diff, but I=E2=80=
=99m afraid the -06 version has the same issues as the ones I reported in J=
anuary 31.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0</span></p></div><=
/div></blockquote><div><br></div><div>I did respond to the particular comme=
nts and text proposals, so I assume this is the more general issue.=C2=A0 I=
f I understand correctly, you would prefer this document to be structured a=
s a revision to the threat model document or connected to a larger consider=
ation of the issues.=C2=A0 I understand that, and it was considered, but I =
believe that this format is still the most effective for the narrow issue i=
t addresses.<br><br></div><div>From that flow some of your other concerns a=
bout audience, at least as I understand.=C2=A0 As written, this is narrow a=
dvice for a broad audience: basically, anyone who would consider the form o=
f metadata insertion it describes.=C2=A0 You would, if I understand you, pr=
efer a narrower description of the audience in a larger context.=C2=A0 <br>=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vl=
ink=3D"purple" lang=3D"FR"><div class=3D"m_-2746598804484943185WordSection1=
"><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;=
Courier New&quot;;color:black" lang=3D"EN-US"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">I=E2=80=99m reiterating that mo=
st of my comments are still unaddressed in -06.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0</span></p></div><=
/div></blockquote><div><br></div><div>I realize that the document did not c=
hange to address the audience or document integration you preferred; I thin=
k there we simply disagree on how to make this advice effective.=C2=A0 I&#3=
9;m sorry that first message apparently did not describe the disagreement e=
ffectively.<br><br></div><div>If I have misunderstood your comments, please=
 accept my apologies. I would be happy of further clarification and suggest=
ed text to illustrate your preferences would be especially welcome.<br><br>=
</div><div>thanks,<br><br></div><div>Ted Hardie<br></div><div><br>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=
=3D"FR"><div class=3D"m_-2746598804484943185WordSection1"><p class=3D"MsoNo=
rmal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:black" lang=3D"EN-US"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Cheers,<u></u><u></u></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Med<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">De=C2=A0:</span></b><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;" lang=3D"EN-US"> Ted Hardie [mailto:<a href=3D"mailto:ted.ietf@gma=
il.co" target=3D"_blank">ted.ietf@gmail.co</a></span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">m]
<br>
<b>Envoy=C3=A9=C2=A0:</b> mercredi 22 f=C3=A9vrier 2017 23:09<br>
<b>=C3=80=C2=A0:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc=C2=A0:</b> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ie=
tf.org</a>; <a href=3D"mailto:draft-hardie-privsec-metadata-insertion@ietf.=
org" target=3D"_blank">draft-hardie-privsec-metadata-<wbr>insertion@ietf.or=
g</a><br>
<b>Objet=C2=A0:</b> Re: Last Call: &lt;draft-hardie-privsec-<wbr>metadata-i=
nsertion-05.txt&gt; (Design considerations for Metadata Insertion) to Infor=
mational RFC<u></u><u></u></span></p>
</div>
</div><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi Mohamed,<u></u><u>=
</u></p>
</div>
<p class=3D"MsoNormal">Thanks for your review.=C2=A0 I&#39;ve uploaded a dr=
aft -06 with updates from your and other reviews.=C2=A0 Some notes in-line.=
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Jan 31, 2017 at 1:49 AM, &lt;<a href=3D"mail=
to:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.boucadair@orange=
.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Dear Ted,<br>
<br>
Please find below my general review of the document and also my detailed co=
mments.<br>
<br>
* Overall:<br>
- I don&#39;t think the document is ready to be published as it is. It does=
 not discuss the usability and implications of the advice. Further, it may =
be interpreted that a client/end system/user can always by itself populate =
data that is supplied by on-path nodes
 (in current deployments). That&#39;s assumption is not true for some proto=
cols.<br>
- The purpose of publishing this advice is not clear. For example, how this=
 advice will be implemented in practice? What is its scope?<br>
- I would personally prefer an updated version of RFC7258 with more strict =
language on the privacy-related considerations. This is more actionable wit=
h concrete effects in documents that will required to include a discussion =
on privacy related matters.<br>
<br>
Detailed comments are provided below:<br>
<br>
* The abstract says the following:<br>
<br>
<span class=3D"m_-2746598804484943185gmail-">=C2=A0 =C2=A0The IAB has publi=
shed [RFC7624] in response to several revelations of</span><br>
<span class=3D"m_-2746598804484943185gmail-">=C2=A0 =C2=A0pervasive attack =
on Internet communications.=C2=A0 This document considers</span><br>
<span class=3D"m_-2746598804484943185gmail-">=C2=A0 =C2=A0the implications =
of protocol designs which associate metadata with</span><br>
<span class=3D"m_-2746598804484943185gmail-">=C2=A0 =C2=A0encrypted flows.=
=C2=A0 In particular, it asserts that designs which do so</span><br>
<span class=3D"m_-2746598804484943185gmail-">=C2=A0 =C2=A0by explicit actio=
ns of the end system are preferable to designs in</span><br>
=C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<wbr>^^^^<br>
=C2=A0 =C2=A0which middleboxes insert them.<br>
<br>
I suggest you explicit what is meant by &quot;the end system&quot;. <u></u>=
<u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have updated this to clarify that this is the host=
/end system not the user.=C2=A0
<br>
=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">If you mean the owner/user, then the text should say=
 so. If you mean a client software instance, then bugs/inappropriate defaul=
t values may lead to (privacy leak) surprises too. It was reported in the p=
ast that some browsers inject the
 MSISDN too.<br>
<br>
* Introduction: &quot;To ensure that the Internet can be trusted by users&q=
uot;<br>
<br>
Rather =C2=AB To minimize the risk of Internet-originated attacks targeted =
at users =C2=BB.
<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;ve adopted this language.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal">It&#39;s reasonable to claim the Internet can be tru=
sted by users; see how the usage of social networks has become severely twi=
sted for example<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I&#39;ve also conside=
red your point that an updated version of RFC7258 might be a better outlet =
for advice like this. We did consider several approaches, including incorpo=
rating the text in an update to=C2=A0 RFC 3552
 or as part of a document describing the full set of companion mitigations =
to the threats in RFC 7624 (draft-iab-privsec-<wbr>confidentiality-mitigati=
ons would be one approach).=C2=A0 Those are all valid approaches, but it se=
emed that short, easily read documents tackling
 a single point might be easier to produce and consume.=C2=A0 <u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Thanks again for your=
 review,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ted Hardie<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div></div>

--001a113db248c4a3e305493b227f--


From nobody Thu Feb 23 16:48:12 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 49A2D1293DA; Thu, 23 Feb 2017 16:48:09 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Ralph Droms <rdroms.ietf@gmail.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-nfsv4-rfc5666bis-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148789728925.21052.5219361429368790695.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 16:48:09 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/l5o6HdynwuEMIBix0sHhTRfBnjM>
Cc: ietf@ietf.org, draft-ietf-nfsv4-rfc5666bis.all@ietf.org, nfsv4@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 00:48:09 -0000

Reviewer: Ralph Droms
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-nfsv4-rfc5666bis-10
Reviewer: Ralph Droms
Review Date: 2017-02-23
IETF LC End Date: 2017-02-07
IESG Telechat date: 2017-03-02

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: None



From nobody Thu Feb 23 16:49:35 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34C0129449 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 16:49:33 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UVQTFLpBQ41n for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 16:49:32 -0800 (PST)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::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 6EF2F129420 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:49:32 -0800 (PST)
Received: by mail-pg0-x235.google.com with SMTP id s67so3343835pgb.3 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:49:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Adz7pKIlHvwvkpoy5bDObO0TSD1gUuJH7RF3Lkdli7M=; b=KCsRH+evApvq0WBEQrrRE2TTn2Z6Uy7kLbpgq8CwCfKu/59dnn6htFj3O7NPT2656P /oO2FJ2C4yCHP5751a2JdM2wp8HSPFJvJRveE7c1Zl8xHEvAbxrJBzNI1+vbmEX4GvM3 TuZn9ce2uQ1Lr1pi5C50hbgOxF0KNtMh+jRO3ZPJMsQG6zqptsSs3g3SiAw0YjfKUPjT MMk5IskV5z0uaLnSb54V2mcwvT9PGEuKhdn2RSLPviZYdJHXGzGjtAQ4J6AXR40tIp4j 3SxRu7+vT7L/vKqpxN+nRAOOeHCm7+DNaBb9GRe2j4yDZl5XVUqKu8vMv51yndNeNsZE KZng==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=Adz7pKIlHvwvkpoy5bDObO0TSD1gUuJH7RF3Lkdli7M=; b=EZcM/oFmHivSW2IQUO73PfbaNTNjdNrbaJnWNnkldSjxEjT0H/Kjk+WC1He2YzRufE 2FGGerbMIfA1T8mH+YTf1boHxTGcem6TL8xfzp2CX3lJMJE+xc/xn5dHLZ4hPwPFwYGf 3gUCdoR+zFMW7pFTHsTFaO0lM67o2e6ItCEX9NyQ2nXF38eA2wZWDXwHpmLiGK0fF3z8 XYrbHrLWTsaHT2A+J5Nl1GJulTSnmU1QhZeP5kbA8CdiQ45FiMPb9vXLBncTM+mrqj4+ ab3Ho2Bu5U3/sNRcRhX1e3l879f2AIlJdrciavcueYIVvVAhbHaXNa6QROOi3guVMxEK t3Dw==
X-Gm-Message-State: AMke39nyhO0AHanIg+RlyiGGL9FpK1+M2yrH/iG5jgiMhdmS/gQKv0WnAFYzSCvuzLl4oQ==
X-Received: by 10.99.158.2 with SMTP id s2mr11267pgd.116.1487897371883; Thu, 23 Feb 2017 16:49:31 -0800 (PST)
Received: from ?IPv6:2406:e007:4b1c:1:28cc:dc4c:9703:6781? ([2406:e007:4b1c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id m12sm11827666pgc.46.2017.02.23.16.49.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Feb 2017 16:49:31 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, ietf@ietf.org
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com> <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com> <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com> <619d77db-8b4d-704a-4f68-6ca6cf3433e7@gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3b9dcc42-8448-a30f-82ad-596c49acdad4@gmail.com>
Date: Fri, 24 Feb 2017 13:49:38 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <619d77db-8b4d-704a-4f68-6ca6cf3433e7@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_wG4YvMzEABFYbZgEs1-xdxOjIY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 00:49:34 -0000

>=20
>> Maybe Linux is different.
>=20
> YEs in a sesne.

I fired up a Linux box and tried ip -6 address add 2001:db8:dead::beef de=
v wlp2s0

It works - the /nn is not required - but the prefix length shown
by ip -6 address show is /128, so that seems to be the Linux default.

(Sorry, can't cut and paste from that screen to this one. Also I can't
mess with the RAs since it is a shared gateway.)

Regards
   Brian

On 24/02/2017 00:57, Alexandre Petrescu wrote:
>=20
>=20
> Le 22/02/2017 =C3=A0 21:04, Brian E Carpenter a =C3=A9crit :
>> On 22/02/2017 22:41, Alexandre Petrescu wrote:
>> <snip>
>>
>>>> Well that does two things: configures a 128 bit address (as Chris
>>>> points out, *all* addresses are 128 bits, duh) and associates a
>>>> prefix length with it, which afaik is optional.
>>>
>>> The prefix length is not optional.  There is no system out there on
>>> which one could configure a 128bit address without explicitely tellin=
g
>>> '/128' or '/64' or '/something-else'.
>>
>> Wrong. Sorry to get all technical, but on Windows:
>=20
> Ok, I didnt know Windows acts that way.
>=20
>>
>> C:\windows\system32>netsh interface ipv6 add address ?
>>
>> Usage: add address [interface=3D]<string> [address=3D]<IPv6 address>[/=
<integer>]
>>              [[type=3D]unicast|anycast]
>>              [[validlifetime=3D]<integer>|infinite]
>>              [[preferredlifetime=3D]<integer>|infinite]
>>              [[store=3D]active|persistent]
>>              [[skipassource=3D]true|false]
>>
>> The [/<integer>] looks pretty optional to me.
>=20
> I agree.
>=20
>> I just tried
>>    netsh interface ipv6 add address 12 2001:db8:dead::beef
>> and now I have three addresses:
>>
>> C:\windows\system32>netsh interface ipv6 show addresses
>>
>> Interface 12: Wireless Network Connection
>>
>> Addr Type  DAD State   Valid Life Pref. Life Address
>> ---------  ----------- ---------- ---------- ------------------------
>> Manual     Preferred     infinite   infinite 2001:db8:dead::beef
>> Public     Preferred      1h54m9s      54m9s fd63:45eb:dc14:0:28cc:dc4=
c:9703:6781
>> Other      Preferred     infinite   infinite fe80::28cc:dc4c:9703:6781=
%12
>>
>> When I try to ping 2001:db8:dead::cafe, I see what I expected in Wires=
hark:
>> neighbour solicitations from 2001:db8:dead::beef to ff02::1:ff00:cafe.=

>> In other words, the new address is treated as on-link. I can't find an=
y trace
>> of an associated prefix entry.
>=20
> This looks strange.  The NS for 2001:db8:dead::beef are normal - they=20
> are DAD.  But to consider it on-link, without having been told the plen=
=20
> is /64 and the prefix, is not normal.
>=20
> I suppose Windows configures an address and a prefix/plen by receiving =

> an RA.  And then, when adding manually an address it considers that=20
> address to be part of that link too.  That is not normal, because the=20
> prefix 2001:db8 is certainly not the same as the one in the RA.
>=20
> I suppose Windows programmers made it so because they needed that=20
> [/integer] to be optional but they also needed the addresses that are=20
> manually configured to be part of some subnet... which one?
>=20
> To check this behaviour, one would silence the RAs, netsh restart, and =

> then manually configure an address without plen, and add a default gw. =

> Can that ping the gw?  Can it ping the Internet?  If yes, then it means=
=20
> there is a /64 hidden somewhere that must be removed.  If it does not=20
> work, then it's good - it misses the plen.
>=20
>> Maybe Linux is different.
>=20
> YEs in a sesne.
>=20
> Alex
>=20
>>
>>      Brian
>>
>=20


From nobody Thu Feb 23 16:55:21 2017
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B452129404 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 16:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4qwxx_FrNcVV for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 16:55:18 -0800 (PST)
Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d:c09::243]) (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 78E13127076 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:55:18 -0800 (PST)
Received: by mail-qk0-x243.google.com with SMTP id x71so1110603qkb.0 for <ietf@ietf.org>; Thu, 23 Feb 2017 16:55:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YSO2jXLIKnXppzmIgbg3zs+Yfa/v7/cH0+/ZZ58eTug=; b=D0gyR9Uqlu+e9Usluy/iCWqOxqJMn10eB6YPhXHg9YNaq6iC5zrMqrjnty0I2NdOCi QIK1Abcm0aRn+cOBURikzMvtTpf/xUkZ2WRDSs2Mayok25lSVXaAqWkaDmny93heGCFr zAa00cBSgavlylB+vho+/8LxFGIdLihQbkhSdZwMbX7aE42TQbCdo1iJyCOkIGvpgRdc CdD7UOmejjML70kmjLvbHJqNV+3ArVVD4MyW9AmqqsszSQmw1P2DrURgP064aaFljoES RtlymzDzJINwWqOfzT2mRtslRAdUmFwzXRafQ131ut61+WunTjX8RufeiYEXtEdtHUbq 8IrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YSO2jXLIKnXppzmIgbg3zs+Yfa/v7/cH0+/ZZ58eTug=; b=A9Kgavc4Z2rhUApIpqnTmaZZbF3hc8QkYZXNZz5vnsrQvRVQKc3L07axiOd7wO7GX3 4jPPQ50WLONPIdhsFr+Wb4FOgdxVWGOplQrhEyHe+azpfBdQ7qiyIOG3bsAN1XOyC1YU iU0rg37VqtzCBRg3ZAcgDjxLByLaSXpmyZQzLh0Ob2J34Ipf7e5OWMqtP/FAaTQ5qCM1 cSrvPawBV2sxa2CZvTUhcqFuOY2Z/YEXjCVT6KomBH5waomBRDPP1DmqExz/Ox4TZKvw ckTSENaqVmOIFzR0qvtj//PqfZt9e/rOcEiiXkQy+qOjXouAZef1UsQ3K34Hy6wxTH4o s7Ig==
X-Gm-Message-State: AMke39lCaVy/z4Li+oJHn+AiUxwn7OWpWQpL39MpUZ+peaOHvpnVn00Qx0QG2yZtlDMd6A==
X-Received: by 10.55.214.209 with SMTP id p78mr3748248qkl.255.1487897717547; Thu, 23 Feb 2017 16:55:17 -0800 (PST)
Received: from ?IPv6:2601:18f:801:600:c922:aa68:a599:d419? ([2601:18f:801:600:c922:aa68:a599:d419]) by smtp.gmail.com with ESMTPSA id m62sm3790130qkf.31.2017.02.23.16.55.16 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Feb 2017 16:55:17 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <3b9dcc42-8448-a30f-82ad-596c49acdad4@gmail.com>
Date: Thu, 23 Feb 2017 19:55:16 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C14767E5-2948-444B-9E8A-7CE5072F9413@gmail.com>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com> <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com> <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com> <619d77db-8b4d-704a-4f68-6ca6cf3433e7@gmail.com> <3b9dcc42-8448-a30f-82ad-596c49acdad4@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7CGlDHQGHq8ExjHsKyeI6hAbl68>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 00:55:20 -0000

> On Feb 23, 2017, at 7:49 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
>>=20
>>> Maybe Linux is different.
>>=20
>> YEs in a sesne.
>=20
> I fired up a Linux box and tried ip -6 address add 2001:db8:dead::beef =
dev wlp2s0
>=20
> It works - the /nn is not required - but the prefix length shown
> by ip -6 address show is /128, so that seems to be the Linux default.

I recall having a related discussion several years ago on an IETF =
mailing list.  There should be, in my opinion, *no* prefix length =
associated with a simple address assigned to an interface - neither when =
the address is assigned nor when the address is shown in response to a =
config query.  It's just an address.  The client's list prefixes is, in =
the abstract, separate from the list of addresses assigned to interfaces =
and populated through other means like RA or manual config, *not* by =
inference from address assignment.

This way of thinking about addresses and prefixes explains why DHCPv6 =
does not include a prefix length with assigned addresses.  DHCPv6 simply =
assigns 128-bit addresses.  Any prefix tables are populated through =
separate mechanisms.

IPv4 has no equivalent to RAs, so the workaround is to infer prefix =
assignment from address assignment.

- Ralph

>=20
> (Sorry, can't cut and paste from that screen to this one. Also I can't
> mess with the RAs since it is a shared gateway.)
>=20
> Regards
>   Brian
>=20
> On 24/02/2017 00:57, Alexandre Petrescu wrote:
>>=20
>>=20
>> Le 22/02/2017 =C3=A0 21:04, Brian E Carpenter a =C3=A9crit :
>>> On 22/02/2017 22:41, Alexandre Petrescu wrote:
>>> <snip>
>>>=20
>>>>> Well that does two things: configures a 128 bit address (as Chris
>>>>> points out, *all* addresses are 128 bits, duh) and associates a
>>>>> prefix length with it, which afaik is optional.
>>>>=20
>>>> The prefix length is not optional.  There is no system out there on
>>>> which one could configure a 128bit address without explicitely =
telling
>>>> '/128' or '/64' or '/something-else'.
>>>=20
>>> Wrong. Sorry to get all technical, but on Windows:
>>=20
>> Ok, I didnt know Windows acts that way.
>>=20
>>>=20
>>> C:\windows\system32>netsh interface ipv6 add address ?
>>>=20
>>> Usage: add address [interface=3D]<string> [address=3D]<IPv6 =
address>[/<integer>]
>>>             [[type=3D]unicast|anycast]
>>>             [[validlifetime=3D]<integer>|infinite]
>>>             [[preferredlifetime=3D]<integer>|infinite]
>>>             [[store=3D]active|persistent]
>>>             [[skipassource=3D]true|false]
>>>=20
>>> The [/<integer>] looks pretty optional to me.
>>=20
>> I agree.
>>=20
>>> I just tried
>>>   netsh interface ipv6 add address 12 2001:db8:dead::beef
>>> and now I have three addresses:
>>>=20
>>> C:\windows\system32>netsh interface ipv6 show addresses
>>>=20
>>> Interface 12: Wireless Network Connection
>>>=20
>>> Addr Type  DAD State   Valid Life Pref. Life Address
>>> ---------  ----------- ---------- ---------- =
------------------------
>>> Manual     Preferred     infinite   infinite 2001:db8:dead::beef
>>> Public     Preferred      1h54m9s      54m9s =
fd63:45eb:dc14:0:28cc:dc4c:9703:6781
>>> Other      Preferred     infinite   infinite =
fe80::28cc:dc4c:9703:6781%12
>>>=20
>>> When I try to ping 2001:db8:dead::cafe, I see what I expected in =
Wireshark:
>>> neighbour solicitations from 2001:db8:dead::beef to =
ff02::1:ff00:cafe.
>>> In other words, the new address is treated as on-link. I can't find =
any trace
>>> of an associated prefix entry.
>>=20
>> This looks strange.  The NS for 2001:db8:dead::beef are normal - they=20=

>> are DAD.  But to consider it on-link, without having been told the =
plen=20
>> is /64 and the prefix, is not normal.
>>=20
>> I suppose Windows configures an address and a prefix/plen by =
receiving=20
>> an RA.  And then, when adding manually an address it considers that=20=

>> address to be part of that link too.  That is not normal, because the=20=

>> prefix 2001:db8 is certainly not the same as the one in the RA.
>>=20
>> I suppose Windows programmers made it so because they needed that=20
>> [/integer] to be optional but they also needed the addresses that are=20=

>> manually configured to be part of some subnet... which one?
>>=20
>> To check this behaviour, one would silence the RAs, netsh restart, =
and=20
>> then manually configure an address without plen, and add a default =
gw.=20
>> Can that ping the gw?  Can it ping the Internet?  If yes, then it =
means=20
>> there is a /64 hidden somewhere that must be removed.  If it does not=20=

>> work, then it's good - it misses the plen.
>>=20
>>> Maybe Linux is different.
>>=20
>> YEs in a sesne.
>>=20
>> Alex
>>=20
>>>=20
>>>     Brian
>>>=20
>>=20
>=20


From nobody Thu Feb 23 17:40:56 2017
Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4FD12941D; Thu, 23 Feb 2017 17:40:50 -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, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nGTFyTOatFgs; Thu, 23 Feb 2017 17:40:48 -0800 (PST)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::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 ED588129442; Thu, 23 Feb 2017 17:40:47 -0800 (PST)
Received: by mail-vk0-x234.google.com with SMTP id r136so4942294vke.1; Thu, 23 Feb 2017 17:40:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=S9I9YVAnPKuidA8zDysqxD1jEvjZqbe7JxhRRZXuC04=; b=XQst6W2DRh13j1dygMU9oOOY3IMMSdftoRPmRky+fe8dMvLfqlbEDri4K1OcpIOOca 2Ypi25MGSAK9ybK7WAVUOoEowJz984IKEZNRsq+nDUTHuOPp0wG5yhrbG1beAu11XQCV v0mFdT/VrMaF8mHvC0gTaOqvui8lfkvtNKIboG1iea2rk/h4f3VUxLDSSOyFEYnECuFu EQ8d2sc4yJsx26aI6adThsjnDxVoo2xA7BF8+8K9XZEBNdpyLkP0y/C0L8BbNEU5KRIc WvMjnpuzP7cHGWT/3RuSDAZwUxcf1WaiomGEBL23pF0dsTBY73mEnlwzcX66Kjz/igya SjEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=S9I9YVAnPKuidA8zDysqxD1jEvjZqbe7JxhRRZXuC04=; b=nmrQen4bSEVstiNyj5Jfr123zU2E3YZ4Of7pMltigYjcrt/rpFW50oZSnhsj9ctdmN osm+pLHtoGieVsMWIW7jyDUPI24m/nX3uiGStjyruaOfM+7ose9qyQRQSaJNAayA807X 2Eu0Ve0CXV2CMnW8qq3aRtXf1KSDXn51W2oQOzI/ltpb595TZP/VXs/sr8C9miEakIZ/ SbirrAczSo1nNNShS2XZkM+IB5kSfGrqerZbds5XDm+WQJ+co7MBi1HiGy990t5JxcXW RKaM1i7PxTnkahQYtrdc3bhpj8o6R9eH5SmLkItfxhdJfa1nem4T0Mm3xF/Wb0S6BMtv cCgw==
X-Gm-Message-State: AMke39kvriBaG7qb6rdsidWf15vJgU7qmKld90JcuiQJGOpj2L2z6ZF4fo+MWxIDpb9GC5TeYwJft6t4LB6k7w==
X-Received: by 10.31.54.85 with SMTP id d82mr65083vka.25.1487900447059; Thu, 23 Feb 2017 17:40:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.159.38.2 with HTTP; Thu, 23 Feb 2017 17:40:46 -0800 (PST)
Received: by 10.159.38.2 with HTTP; Thu, 23 Feb 2017 17:40:46 -0800 (PST)
In-Reply-To: <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 24 Feb 2017 12:40:46 +1100
Message-ID: <CAO42Z2z3aW_eKOTeGGT=Nd-rCF3G0ztkwe+ZLuJqAcuTQbJ=BQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: multipart/alternative; boundary=001a114384ac9bb5d305493cd165
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D_gxCL9Q4WZjeidLjerWVgRnF4g>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 01:40:50 -0000

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

On 24 Feb. 2017 09:43, "Pierre Pfister" <pierre.pfister@darou.fr> wrote:


> Le 23 f=C3=A9vr. 2017 =C3=A0 21:42, Mark Smith <markzzzsmith@gmail.com> a=
 =C3=A9crit :
>
> On 24 February 2017 at 06:00, Nick Hilliard <nick@foobar.org> wrote:
>> as it's currently worded, draft-ietf-6man-rfc4291bis seems to prohibit
>> the implementation of any interface netmask !=3D /64:
>>
>>>                                          However, the Interface ID of
>>>   all unicast addresses, except those that start with the binary value
>>>   000, is required to be 64 bits long.
>>
>
> The thing is this is not new text, it has been in RFC4291 for 11
> years. c.f., 2.5.1.

And during those 11 years. Nobody implemented this rule specific to ::/3.

>
> It can't be changed without invalidating all of the other RFCs that
> have utilised 64 bit identifiers.

Those "other RFCs" have nothing to do with being part of ::/3 or not.
They require an interface identifier of 64 bits long.
The fact that a protocol does not work in some conditions does not
invalidate the protocol.
e.g. the fact that SLAAC over Ethernet doesn't work when IID is not 64
doesn't mean
the IID could not be 64 bits long. It just means that under those
conditions, SLAAC would not work.
And those conditions are perfectly well defined in those "other RFCs".


A non-SLAAC example.

"Unicast-Prefix-based IPv6 Multicast Addresses"

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


That example and many others are described in

"Analysis of the 64-bit Boundary in IPv6 Addressing"

https://tools.ietf.org/rfc/rfc7421

Surely everybody here saying change it or abandon it have read that
RFC so they fully understand the consequences of what they're
suggesting, right? I'm pretty sure it has been referenced in at least
one version of the text I've seen in the discussion.




- Pierre

>
>> This has substantial operational consequences in the ipv6 world because
>> if it's implemented as stated, it will cause production ipv6 networks to
>> break.
>
> Going by the millions of IPv6 deployments now, it has been implemented
> as stated.
>
>>
>> The ipv6 operational community may have opinions on the wisdom of
>> mandating new behaviour which would cause their networks to fall over,
>
> There is and should be no new behaviour in RFC4291bis, it is a tidy up
> to advance it along the standard track.
>
>
>> so it would probably be a good idea to notify v6ops@ietf about the
>> existence of this draft so that the folks over there get a look-in
>> before a consensus call is made. As far as I can tell, this notification
>> never happened.
>>
>> Nick
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 24 Feb. 2017 09:43, &quot;Pierre Pfister&quot; &lt;<a href=3D"=
mailto:pierre.pfister@darou.fr">pierre.pfister@darou.fr</a>&gt; wrote:<br t=
ype=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text"><br=
>
&gt; Le 23 f=C3=A9vr. 2017 =C3=A0 21:42, Mark Smith &lt;<a href=3D"mailto:m=
arkzzzsmith@gmail.com">markzzzsmith@gmail.com</a>&gt; a =C3=A9crit :<br>
&gt;<br>
&gt; On 24 February 2017 at 06:00, Nick Hilliard &lt;<a href=3D"mailto:nick=
@foobar.org">nick@foobar.org</a>&gt; wrote:<br>
&gt;&gt; as it&#39;s currently worded, draft-ietf-6man-rfc4291bis seems to =
prohibit<br>
&gt;&gt; the implementation of any interface netmask !=3D /64:<br>
&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 However, the Interface ID of<br>
&gt;&gt;&gt;=C2=A0 =C2=A0all unicast addresses, except those that start wit=
h the binary value<br>
&gt;&gt;&gt;=C2=A0 =C2=A0000, is required to be 64 bits long.<br>
&gt;&gt;<br>
&gt;<br>
&gt; The thing is this is not new text, it has been in RFC4291 for 11<br>
&gt; years. c.f., 2.5.1.<br>
<br>
</div>And during those 11 years. Nobody implemented this rule specific to :=
:/3.<br>
<div class=3D"quoted-text"><br>
&gt;<br>
&gt; It can&#39;t be changed without invalidating all of the other RFCs tha=
t<br>
&gt; have utilised 64 bit identifiers.<br>
<br>
</div>Those &quot;other RFCs&quot; have nothing to do with being part of ::=
/3 or not.<br>
They require an interface identifier of 64 bits long.<br>
The fact that a protocol does not work in some conditions does not invalida=
te the protocol.<br>
e.g. the fact that SLAAC over Ethernet doesn&#39;t work when IID is not 64 =
doesn&#39;t mean<br>
the IID could not be 64 bits long. It just means that under those condition=
s, SLAAC would not work.<br>
And those conditions are perfectly well defined in those &quot;other RFCs&q=
uot;.<br></blockquote></div></div></div><div dir=3D"auto"><br></div><div di=
r=3D"auto">A non-SLAAC example.</div><div dir=3D"auto"><br></div><div dir=
=3D"auto"><pre style=3D"word-wrap:break-word;white-space:pre-wrap">&quot;Un=
icast-Prefix-based IPv6 Multicast Addresses&quot;
</pre></div><div dir=3D"auto"><a href=3D"https://tools.ietf.org/html/rfc330=
6">https://tools.ietf.org/html/rfc3306</a><br></div><div dir=3D"auto"><br><=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">That example and many ot=
hers are described in</div><div dir=3D"auto"><br></div><div dir=3D"auto"><p=
re style=3D"word-wrap:break-word;white-space:pre-wrap">&quot;Analysis of th=
e 64-bit Boundary in IPv6 Addressing&quot;</pre><pre style=3D"word-wrap:bre=
ak-word"><span style=3D"white-space:pre-wrap"><a href=3D"https://tools.ietf=
.org/rfc/rfc7421">https://tools.ietf.org/rfc/rfc7421</a></span></pre><pre s=
tyle=3D"word-wrap:break-word"><span style=3D"white-space:pre-wrap">Surely e=
verybody here saying change it or abandon it have read that RFC so they ful=
ly understand the consequences of what they&#39;re suggesting, right? I&#39=
;m pretty sure it has been referenced in at least one version of the text I=
&#39;ve seen in the discussion.</span></pre><pre style=3D"word-wrap:break-w=
ord"><span style=3D"white-space:pre-wrap"><br></span></pre></div><div dir=
=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
<font color=3D"#888888"><br>
- Pierre<br>
</font><div class=3D"elided-text"><br>
&gt;<br>
&gt;&gt; This has substantial operational consequences in the ipv6 world be=
cause<br>
&gt;&gt; if it&#39;s implemented as stated, it will cause production ipv6 n=
etworks to<br>
&gt;&gt; break.<br>
&gt;<br>
&gt; Going by the millions of IPv6 deployments now, it has been implemented=
<br>
&gt; as stated.<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; The ipv6 operational community may have opinions on the wisdom of<=
br>
&gt;&gt; mandating new behaviour which would cause their networks to fall o=
ver,<br>
&gt;<br>
&gt; There is and should be no new behaviour in RFC4291bis, it is a tidy up=
<br>
&gt; to advance it along the standard track.<br>
&gt;<br>
&gt;<br>
&gt;&gt; so it would probably be a good idea to notify v6ops@ietf about the=
<br>
&gt;&gt; existence of this draft so that the folks over there get a look-in=
<br>
&gt;&gt; before a consensus call is made. As far as I can tell, this notifi=
cation<br>
&gt;&gt; never happened.<br>
&gt;&gt;<br>
&gt;&gt; Nick<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; v6ops mailing list<br>
&gt;&gt; <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"nor=
eferrer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/v6ops=
</a><br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; v6ops mailing list<br>
&gt; <a href=3D"mailto:v6ops@ietf.org">v6ops@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=3D"norefer=
rer" target=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/v6ops</a>=
<br>
<br>
</div></blockquote></div><br></div></div></div>

--001a114384ac9bb5d305493cd165--


From nobody Thu Feb 23 18:54:10 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75A2112948C; Thu, 23 Feb 2017 18:54:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 g9jh6eJ-ZN5S; Thu, 23 Feb 2017 18:54:03 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 646881294A4; Thu, 23 Feb 2017 18:54:03 -0800 (PST)
Received: from [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f] (unknown [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 3ABA5540A6B; Thu, 23 Feb 2017 21:53:41 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <2683353.FOTFeJBnXE@linne>
Date: Thu, 23 Feb 2017 21:53:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BB8C710-653B-4A0D-940C-98D865F8D9D1@puck.nether.net>
References: <m2y3x6eutl.wl-randy@psg.com> <CAKD1Yr3p=8b9Dmmb9GvGMq1u00xnE2ScmaF_a3FJXiteL=ZhBQ@mail.gmail.com> <20170221172739.GT84656@Vurt.local> <2683353.FOTFeJBnXE@linne>
To: Karsten Thomann <karsten_thomann@linfre.de>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YEjOt8FHlrrBk6reStIZpyRPfC0>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, Job Snijders <job@ntt.net>, ipv6@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 02:54:04 -0000

> On Feb 21, 2017, at 2:21 PM, Karsten Thomann =
<karsten_thomann@linfre.de> wrote:
>=20
> Satisfies my desired outcome of the text, but I would like to modify =
it:
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. When using [SLAAC], [ILNP], or [NPT66] the Interface =
ID
>    of unicast addresses is required to be 64 bits long. An exception =
is for
>    example [RFC6164] which standardises 127 bit prefixes on =
point-to-point
>    links. The RECOMMENDED prefix length is 64 bit, but prefix lengths =
up to
>   128 bit can be possible on explicit configuration.
>=20

I=E2=80=99m reminded of when a vendor decided that /31 on ethernet was =
not a suitable configuration and did not properly disclose in the =
release notes, causing a subsequent series of outages.

I=E2=80=99m therefore cautious about the usage of any normative comment =
on bit mask length.

Nothing quite like your interfaces losing their IP config after upgrade =
because someone decided to more strictly interpret guidance.

- Jared=


From nobody Thu Feb 23 18:59:02 2017
Return-Path: <xing@cernet.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FBC212948C; Thu, 23 Feb 2017 18:59:01 -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_HELO_PASS=-0.001] autolearn=ham autolearn_force=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 CPmtm7snISwa; Thu, 23 Feb 2017 18:58:59 -0800 (PST)
Received: from tsinghua.edu.cn (smtp39.tsinghua.edu.cn [166.111.204.63]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8BD1294C6; Thu, 23 Feb 2017 18:58:57 -0800 (PST)
Received: from [10.235.234.125] (unknown [58.200.235.39]) by app1 (Coremail) with SMTP id CsxvpgAnLUVtoa9YcixcAg--.1596S2; Fri, 24 Feb 2017 10:58:55 +0800 (CST)
Message-ID: <58AF9C78.2000106@cernet.edu.cn>
Date: Fri, 24 Feb 2017 10:37:44 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <20170223220531.GU2367@Space.Net>
In-Reply-To: <20170223220531.GU2367@Space.Net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CM-TRANSID: CsxvpgAnLUVtoa9YcixcAg--.1596S2
X-Coremail-Antispam: 1UD129KBjDUn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7v73 VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjp_UUU5h7k0a2IF6F4UM7kC6x804xWl14x267AK xVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AKwVWUJVWUGw A2ocxC64kIII0Yj41l84ACjcxK6xIIjxv20xvE14v26r1I6r4UM28EF7xvwVC0I7IYx2IY 6xkF7I0E14v26r4j6F4UM28EF7xvwVC2z280aVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2js IEc7CjxVAFwI0_Gr1j6F4UJwAS0I0E0xvYzxvE52x082IY62kv0487Mc02F40EFcxC0VAK zVAqx4xG6I80ewAv7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx 8S6xCaFVCjc4AY6r1j6r4UM4x0Y48IcVAKI48JMxkIecxEwVAFwVW8JwCF04k20xvY0x0E wIxGrwC20s026c02F40E14v26r1j6r18MI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67 kF1VAFwI0_JF0_Jw1lIxkGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY 6xIIjxv20xvEc7CjxVAFwI0_Jr0_Gr1lIxAIcVCF04k26cxKx2IYs7xG6rWUJVWrZr1UMI IF0xvEx4A2jsIE14v26r4j6F4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIdaVF xhVjvjDU0xZFpf9x0UUjRlUUUUUU=
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ICUYRv1r5pqJErbRI4Hkcn-8fC0>
Cc: IPv6 Operations <v6ops@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 02:59:01 -0000

Gert Doering 写道:
> Hi,
>
> On Fri, Feb 24, 2017 at 07:42:21AM +1100, Mark Smith wrote:
>   
>> It can't be changed without invalidating all of the other RFCs that
>> have utilised 64 bit identifiers.
>>     
>
> Except for the few that explain how to use /126 or /127, right?
>   

+1, plus exceptions for the IPv4-translatable IPv6 address defined in 
RFC6052. I suggest just provide pointers to those RFCs in rfc4291bis. xing

> Gert Doering
>         -- NetMaster
>   




From nobody Thu Feb 23 19:05:48 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1927129AF9; Thu, 23 Feb 2017 19:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 kgw40jKK6_oc; Thu, 23 Feb 2017 19:05:40 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id D5D9C129A9A; Thu, 23 Feb 2017 19:05:40 -0800 (PST)
Received: from [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f] (unknown [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id E9221540C70; Thu, 23 Feb 2017 22:05:23 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
Date: Thu, 23 Feb 2017 22:05:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4D8C452B-FC3D-465A-A2CE-9ECD9E4F02F1@puck.nether.net>
References: <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <CAKD1Yr2n=ogFo7LJYgjcraoFxioQQzmo8HYxzNRJ10VA8xMVOg@mail.gmail.com> <20170222153129.GE89584@hanna.meerval.net> <CAKD1Yr2-yS-tX9Pe0Rk_74hnXa9Rc-yTHV0m=Kbi2q0wvYGgPg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DwhaA_N42qF8VbR7N7SY9bad_gg>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Job Snijders <job@ntt.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:05:42 -0000

> On Feb 22, 2017, at 10:56 AM, Lorenzo Colitti <lorenzo@google.com> =
wrote:
>=20
> RFC6583-style attacks (of which the class addressed by RFC6164 is a =
subset) are low payoff and pretty easy to mitigate using very small =
changes to ND implementations

The duration of time it takes to roll out new code is measured in years =
in a backbone.  Some vendors are still missing negative-arp caching for =
v4 in 2017, so I=E2=80=99m having trouble treating this as a low-payoff =
attack.  Even when it=E2=80=99s not intended as an attack, the =
side-effects are well documented, and is something the IETF NOC team has =
experienced first-hand.

Not all vendors, hardware or implementations are equal, and convergence =
here takes some time.  Setting the right standard in the first place =
helps, and when doing a -bis, it=E2=80=99s furthermore important to =
incorporate the operational lessons learned.  If the WG decides to not =
listen, that=E2=80=99s certainly it=E2=80=99s prerogative but does not =
move the standards forward.

For me, this is just one of many things in IPv6 that requires servicing, =
so not the end of the world if this one doesn=E2=80=99t get fixed, but =
being overly prescriptive here is begging for trouble.

- Jared=


From nobody Thu Feb 23 19:15:45 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89D6E129C9E; Thu, 23 Feb 2017 19:15:43 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 uHQUWbRVOOKj; Thu, 23 Feb 2017 19:15: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 71D48129C9C; Thu, 23 Feb 2017 19:15:41 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 9008A809EA; Fri, 24 Feb 2017 04:15:36 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>, Lorenzo Colitti <lorenzo@google.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com>
Date: Fri, 24 Feb 2017 00:13:03 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vzdCE9BRNmFnKRFZHOlQ0N7wSAU>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:15:43 -0000

On 02/23/2017 07:43 PM, David Farmer wrote:
> 
> 
> On Wed, Feb 22, 2017 at 10:16 PM, Lorenzo Colitti <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
> 
>     Help he understand, then. There is widely-deployed code that assumes
>     that the interface ID is 64 and does not work on anything other than
>     64 bit prefix lengths. Currently that code is correct on all unicast
>     space. If you change RFC 4291, won't that code be incorrect?
> 
> 
> OK, what if we said something like this;
> 
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. However, all implementations of IPv6 are REQUIRED to
>    support an IID length of 64 bits, other IID lengths are OPTIONAL.
>    Subnet prefixes of /64 are RECOMMENDED for general purpose use,
>    subnet prefixes of /127 are RECOMMENDED for point-to-point router
>    links [RFC6164], other subnet prefix lengths are NOT RECOMMENDED,
>    as their use could be incompatible with some implementations of IPv6.
>    The rationale for the 64 bit boundary in IPv6 addresses can be found
>    in [RFC7421].

I'd remove a few sentences here, as in:

   IPv6 unicast routing is based on prefixes of any valid length up to
   128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
   purpose use, subnet prefixes of /127 are RECOMMENDED for point-
   to-point router links [RFC6164]. The rationale for the 64 bit
   boundary in IPv6 addresses can be found in [RFC7421].

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 23 19:19:08 2017
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A849E129CC8; Thu, 23 Feb 2017 19:19:07 -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 autolearn_force=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 H5jXleS87i6u; Thu, 23 Feb 2017 19:19:06 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 91D071294F2; Thu, 23 Feb 2017 19:19:06 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1ch6PM-0006BO-Ml; Fri, 24 Feb 2017 03:19:01 +0000
Date: Fri, 24 Feb 2017 10:18:56 +0700
Message-ID: <m2poi8s2cf.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Gert Doering <gert@space.net>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
In-Reply-To: <20170223190730.GL2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/24.5 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g7RNHDjv-aqyLJ-iW-05XNPGbpQ>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:19:07 -0000

> But since nobody seemed to care for the last 14 years

this is false.  some people have been fighting this for 20 years.
though the first years were more concentrated on fighting the TLS/NLA
insanity, which makes this /64 mess look minor.  for those of us trying
to deal with classful ipv6 for the last 20 years, this /64 issue is the
last clean-up.

randy


From nobody Thu Feb 23 19:23:47 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2892F1294F9; Thu, 23 Feb 2017 19:23:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iJZz0tlQUNZm; Thu, 23 Feb 2017 19:23:40 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::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 CC17D1294E6; Thu, 23 Feb 2017 19:23:39 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id b16so8434913qte.0; Thu, 23 Feb 2017 19:23:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=pssrw9zN7R2F8P++BFcEQ5oJLN3jkQhljrBedOh0GSA=; b=gOVcb9RXh2OOuOgLp37K8/Y6gGekpPVPL27DRlRVTdmIiAqg5oazilL8kwqpiZXmPA 1WkqjnpQJVjo3iS42OqGcyn7u4vr1QHcrr0So7BFp9Wse0S7Qe5ejEVMFjqLDNQmYUDx SWVFCUlHFfO19M/yAqgOTkZFZXWtNMmfpd5fVli2332q8mrvIujiWroTqbVN+eKoqLtb KsHbybosJV3mn8jrOvFTOllwfSEi3O/A3FD8jtgYwLWX9XQ2S/p48kl4wV1H+fs7AB6U u39UnxARXI2JXclXGDUL61l5ouSEjq8CNgi40ORbbvFGi6mCBylFS80ErQgn8be9pHNd kiaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=pssrw9zN7R2F8P++BFcEQ5oJLN3jkQhljrBedOh0GSA=; b=oAPYPVV6GqjiqHyD1rGVHEUq2zLdbpbx3Uq6wS2RTV9PdmVEPom3KqQDoqbsYpVlPh 25ph2pOSWYIgDJ6/9TuROOqiYE8R005zMceNIQpaMd9RtQvJxPzRK3vw/5yoLb/XS7h4 nfg3Iy1HUP5wg0Oe2jqys3bTR0RTlIdI+NyxZknm/UU3IwUyVxLFMrwPraX62FdCBUqA ZT8eyzP2NE5wuCjZDyn6vfE7Y3o7uKF+vZHMwG0vmWFemjIcmmYvFnctnN1nGsjpCR9b 5u3JXPBxOO03MKW3Vc3u9RpV5TC/Nrc9nqbXEVXxZiBAkbpwIzzdk9K/UNPQngHTEY/h r/3Q==
X-Gm-Message-State: AMke39kXiW1okBJlcao52oxfaFHEUkUNtiuL52ioV2m2rs2tq6v00yRMRGmEJtsB9PUD4/6efDa5qxeET7SM4A==
X-Received: by 10.237.33.47 with SMTP id 44mr501114qtc.100.1487906618930; Thu, 23 Feb 2017 19:23:38 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Thu, 23 Feb 2017 19:23:38 -0800 (PST)
In-Reply-To: <m2poi8s2cf.wl-randy@psg.com>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 23 Feb 2017 22:23:38 -0500
X-Google-Sender-Auth: 96LWu__n4j4Jrug8wcpC5BcFd4I
Message-ID: <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=94eb2c0c5e527afc3705493e419e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PCXtTVPLENL7AHri2XW7JhB-edI>
Cc: IPv6 Operations <v6ops@ietf.org>, Gert Doering <gert@space.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:23:41 -0000

--94eb2c0c5e527afc3705493e419e
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 23, 2017 at 10:18 PM, Randy Bush <randy@psg.com> wrote:

> > But since nobody seemed to care for the last 14 years
>
> this is false.  some people have been fighting this for 20 years.
> though the first years were more concentrated on fighting the TLS/NLA
> insanity, which makes this /64 mess look minor.  for those of us trying
> to deal with classful ipv6 for the last 20 years, this /64 issue is the
> last clean-up.
>
>
The original message in the thread about this draft:
" > The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'IP Version 6 Addressing Architecture'
>   <draft-ietf-6man-rfc4291bis-07.txt> as Internet Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. 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."

Nothing in the past really matters here, what matters is: "Is the bis draft
all set, did we fix all the things which must be fixed before this draft
becomes a real 'standard'?"

"no, I don't think we did" - randy (as strawman arguer)

Folk's frustrations are coming out, deep breath and think before 'send'
please... we're all really trying to do the right thing, yes?

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Feb 23, 2017 at 10:18 PM, Randy Bush <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.=
8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D=
"gmail-">&gt; But since nobody seemed to care for the last 14 years<br>
<br>
</span>this is false.=C2=A0 some people have been fighting this for 20 year=
s.<br>
though the first years were more concentrated on fighting the TLS/NLA<br>
insanity, which makes this /64 mess look minor.=C2=A0 for those of us tryin=
g<br>
to deal with classful ipv6 for the last 20 years, this /64 issue is the<br>
last clean-up.<br><br></blockquote><div><br></div><div>The original message=
 in the thread about this draft:<br>&quot; &gt; The IESG has received a req=
uest from the IPv6 Maintenance WG (6man) to</div><div>&gt; consider the fol=
lowing document:</div><div>&gt; - &#39;IP Version 6 Addressing Architecture=
&#39;</div><div>&gt; =C2=A0 &lt;draft-ietf-6man-rfc4291bis-07.txt&gt; as In=
ternet Standard</div><div>&gt;=C2=A0</div><div>&gt; The IESG plans to make =
a decision in the next few weeks, and solicits</div><div>&gt; final comment=
s on this action. Please send substantive comments to the</div><div>&gt; <a=
 href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-03-0=
1. Exceptionally, comments may be</div><div>&gt; sent to <a href=3D"mailto:=
iesg@ietf.org">iesg@ietf.org</a> instead. In either case, please retain the=
</div><div>&gt; beginning of the Subject line to allow automated sorting.&q=
uot;</div><div><br></div><div>Nothing in the past really matters here, what=
 matters is: &quot;Is the bis draft all set, did we fix all the things whic=
h must be fixed before this draft becomes a real &#39;standard&#39;?&quot;<=
br><br></div><div>&quot;no, I don&#39;t think we did&quot; - randy (as stra=
wman arguer)</div><div><br></div><div>Folk&#39;s frustrations are coming ou=
t, deep breath and think before &#39;send&#39; please... we&#39;re all real=
ly trying to do the right thing, yes?</div></div><br></div></div>

--94eb2c0c5e527afc3705493e419e--


From nobody Thu Feb 23 19:28:21 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 246481294F7 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qtMgqhpaDoYJ for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:28:17 -0800 (PST)
Received: from mail-ua0-x235.google.com (mail-ua0-x235.google.com [IPv6:2607:f8b0:400c:c08::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 A3C461294C7 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:28:17 -0800 (PST)
Received: by mail-ua0-x235.google.com with SMTP id 60so4259571uah.1 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:28:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s4vyK5ldz5TueiqH3lARdNq3Xp9lOKbsNUOLq78LjVI=; b=GZEjp1DNL/AUkoySM+4jN1Z0xpGIWnXib6S8NJNyM2oaSMf4EG/AAP33RUVreCPBKo hYvhlrzEu68r1lkCsdI8qZ6FFl2H4LxoxvWdAOwiV9bHF9GCtsXl0Gk922BU6NBq19r0 M28dSF/um9tsF3wclTvXFzbGwEK3b9i4Bowacc1VxwJWrI8pvGoHlqnXgKE/NYeViyCm eUqK9kfPp2jWYtI3Hb44phMP2dMjpujHxAQXTx561Qwv9eosZDeXVjNB3PnJi6qVo45Y kFmCkV3hBC4AVVR+33fICmjjSWoAAUFF7B6YBNkruo/2WdHSlhXElZPpinteRqOx7tEJ L05Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s4vyK5ldz5TueiqH3lARdNq3Xp9lOKbsNUOLq78LjVI=; b=W3w5CNA5EZfebjcz1uYLLK1iziOn0UpeMD+TGazurX+T2N3I+Ox2YC4vTAvNJbiiqG JVZQLw/N6Vj8OeWztkYc3iWtAda+1OXuuUSlgW14W2HO9SHxbCX5b29K2lcXOWYtVj+V pTY8e9HlDnLrsrakthW/byR+x74P9ZAKnhW/LZZsMlvYnB1h4mavqtpxUJ73+Vq5n0ym seBZAlfvCKgFGTWPMFasqGsUmpNHT72pqslvqQDuc88vstn+eI7nfbb7zYV7weyuqd8L M8YcOGT6wiODriClYpe+nwHteKNRZHJ+oslQWF6vewVYnS30oi6ttlk3r1JmNVQRzPoM Hn8Q==
X-Gm-Message-State: AMke39nG5Xek4kfA4A/yjpyI6gOLFa7YUuPtxPAaQRDibUXQBsEYu5cLvuYCN4USLWFhB9K/X7uHsBqIQuVCLl3O
X-Received: by 10.159.36.56 with SMTP id 53mr281429uaq.124.1487906896476; Thu, 23 Feb 2017 19:28:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 19:27:55 -0800 (PST)
In-Reply-To: <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 24 Feb 2017 12:27:55 +0900
Message-ID: <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: multipart/alternative; boundary=001a113e1ca006a6d605493e52b0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RBklppMer5htKROJ_yNI165KfyE>
Cc: IPv6 Operations <v6ops@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:28:19 -0000

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

On Fri, Feb 24, 2017 at 7:43 AM, Pierre Pfister <pierre.pfister@darou.fr>
wrote:

> > The thing is this is not new text, it has been in RFC4291 for 11
> > years. c.f., 2.5.1.
>
> And during those 11 years. Nobody implemented this rule specific to ::/3.
>

I can implement it today in some of our code if you like :-). But it seems
unlikely to make a difference, since the rule only applies to unicast
addresses in ::/3, and no such addresses have been released to the RIRs.
That in turn is unlikely to change until we run out of 2000::/3, and even
then we'll likely move on to allocating addresses out of 4000::/3 instead
of from ::/3.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 24, 2017 at 7:43 AM, Pierre Pfister <span dir=3D"ltr">&lt;<a href=
=3D"mailto:pierre.pfister@darou.fr" target=3D"_blank">pierre.pfister@darou.=
fr</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
>&gt; The thing is this is not new text, it has been in RFC4291 for 11<br>
&gt; years. c.f., 2.5.1.<br>
<br>
</span>And during those 11 years. Nobody implemented this rule specific to =
::/3.<br></blockquote><div><br></div><div>I can implement it today in some =
of our code if you like :-). But it seems unlikely to make a difference, si=
nce the rule only applies to unicast addresses in ::/3, and no such address=
es have been released to the RIRs. That in turn is unlikely to change until=
 we run out of 2000::/3, and even then we&#39;ll likely move on to allocati=
ng addresses out of 4000::/3 instead of from ::/3.</div></div></div></div>

--001a113e1ca006a6d605493e52b0--


From nobody Thu Feb 23 19:32:25 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ACF8129D28 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:32:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eljexRkWqQ5i for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:32:17 -0800 (PST)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::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 3BC13129D25 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:32:17 -0800 (PST)
Received: by mail-ua0-x233.google.com with SMTP id 40so6396437uau.2 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:32:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=t4y5wcXECAV7DVhZQcYWJTDXR3jfLJ8vuOjkcvPv+mE=; b=Vmmxb15WSUYP1Q8yKTo6agYLo3xvTdOOAlCMvEKvFMnkJc92qIVX5QS2ENlLyNDQHy pJTleb+0kDFs3AawBtvpCTRp/gEpKalo1ef2O9XMLh/a4nhNrPLQnzDlXwAYP7KpGrOQ N/xgGtSqLSH7y+huIM54v1SuD9Kns8udba+dompwtnuwuA7iHqGzGRdQQ83tGe1k/UL1 ljYdXRdz+BQnbQu5YZP+RVsTPUynY71SU0dGPzY+1P0mzo6n2YgIN1pqBlDqvsuwW1yB 9AMLiKqP9fjgYsKrJwTx3q1AVTS+Epyjy1raRP8fe4W3LwzMX+YjV35ADZ/H7HIbZDyY soBQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t4y5wcXECAV7DVhZQcYWJTDXR3jfLJ8vuOjkcvPv+mE=; b=WWF+zfvyJUBLDRwZn4/LHMra474rHQ4HP+HIwPbsxrxQhIMSh7Umh0uU0uQ3B9YiJ7 IKcL6aRlaQKK6oxQhfuoZM+kHq3i+lEHptXdLtHka1gk72V8ZA6NlvuQF5MTVDaYWAVE sTCeAiIr8XRqAqatrWTgel/E4M24KTWfSDFu9oG9esxXKpHim/hlD7XAvJCZFvNP4s6G 9sESS/CRyyfRUTc0IzqQevMpp1ca9JmT2LiVvoud5pgNYyHFRPSFS0BN/FUc2yjbDp+D 9A7rr32efsw/hhW5CnlaTnubiA16fYDcr9xpASGogqLmy3yaUAA/X/8p5ipSLosVsYbz jNHA==
X-Gm-Message-State: AMke39mTEAy5GglsJKn3JzN3v0jQHU1XdmO1jeu9zzCmikcb4C/re7vCsvsFrnrZdpmrzRcWQaitgYwRJNeP1H+M
X-Received: by 10.176.17.108 with SMTP id g44mr244957uac.30.1487907136135; Thu, 23 Feb 2017 19:32:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 19:31:55 -0800 (PST)
In-Reply-To: <58AF9C78.2000106@cernet.edu.cn>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <20170223220531.GU2367@Space.Net> <58AF9C78.2000106@cernet.edu.cn>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 24 Feb 2017 12:31:55 +0900
Message-ID: <CAKD1Yr2EVhZWjbPfaJ+=LzwMqVwyS8tJeHdBp5beP1vQoXyqXg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Xing Li <xing@cernet.edu.cn>
Content-Type: multipart/alternative; boundary=f4030435b5704f3d1305493e6025
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qj7ShGGQj16gqoKAxBZ8j-QjzSc>
Cc: IPv6 Operations <v6ops@ietf.org>, Gert Doering <gert@space.net>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:32:19 -0000

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

On Fri, Feb 24, 2017 at 11:37 AM, Xing Li <xing@cernet.edu.cn> wrote:

> Except for the few that explain how to use /126 or /127, right?
>>
>>
>
> +1, plus exceptions for the IPv4-translatable IPv6 address defined in
> RFC6052. I suggest just provide pointers to those RFCs in rfc4291bis.
>

Yes, seems like those should be documented too. In fact, perhaps a general
exception for IPv6 addresses where the only non-zero bits in the IID are an
IPv4 address?

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 24, 2017 at 11:37 AM, Xing Li <span dir=3D"ltr">&lt;<a href=3D"mail=
to:xing@cernet.edu.cn" target=3D"_blank">xing@cernet.edu.cn</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><span class=3D""><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">Except for the few that explain how to use /126 or /127, righ=
t?<br>
=C2=A0 <br>
</blockquote>
<br></span>
+1, plus exceptions for the IPv4-translatable IPv6 address defined in RFC60=
52. I suggest just provide pointers to those RFCs in rfc4291bis.<br></block=
quote><div><br></div><div>Yes, seems like those should be documented too. I=
n fact, perhaps a general exception for IPv6 addresses where the only non-z=
ero bits in the IID are an IPv4 address?</div></div></div></div>

--f4030435b5704f3d1305493e6025--


From nobody Thu Feb 23 19:35:00 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 877FE1294FE for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8KL9prDCiu7 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 19:34:53 -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 BD632129A9A for <ietf@ietf.org>; Thu, 23 Feb 2017 19:34:53 -0800 (PST)
Received: by mail-vk0-x231.google.com with SMTP id k127so5911981vke.0 for <ietf@ietf.org>; Thu, 23 Feb 2017 19:34:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s1zq4usS5Z971djrHB8lo+vtcQTbmhSjrDqhENeX4nQ=; b=Ue170Oaz/8sP2fttfe948jFt8LgAPo4OtAEgpLMDBNAotDJsHkZtVRkWFGVo2n/Yz8 Ic3xFhe5aVkY3aMhNxZtigfxMvVthyKC1z73OEsjLwFgGwINnQxtRQXLm9R6pcYtgpzu bRTJucmJSq06mQt883fpPLkgFOqg2H4NfW3iDQyboU6NftaVvcO7vntdaB+LOS+Xa6Hn fud0f9S9PM97TMwpY/XjVulI7iyemBeVupynM3A/wgZSTIQRTP+BZRVxAwPY8CKpuhNg VNkOUWR+wUNlp9h9YnfJzS56DAFboXkRsVWSr50jYlzpJprZr6/sCQMGjKhQe8hd76tf Flcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s1zq4usS5Z971djrHB8lo+vtcQTbmhSjrDqhENeX4nQ=; b=KgHwjcuMGxUcE3lEtajd3HebUPpBJDOrKKcFDRhX17PcxHUw6VZKLckywH7RXNZSAs kI8J+jNwydkMufjjCTTTxxytJ3rR5h8oHAcZYO7XHzIiKFaUJwTsObIJzWd3UQTl8QlQ AmPmuf3EY02mTAdRVneGcDTK/hM0pe/KCaAGvKG9tsr7hExuc2n1b0x9gNo6jUAuvpjA 9t3YNAHQ+rKKXzaXKjaMxdQRmJrma2A3uM7CNfIEzvxCKt5Pk9ZuVya1aYdzSQXl7sGQ JqhLqFkwtLcuL3vJnaXSHe7/wOwoGuGRLdvxD0JAlemzVTGe/0cnyokmncuOs33w4Syi SoFQ==
X-Gm-Message-State: AMke39lRaME5jp2pX/QDkGZiwKdcvocIngqTRJgvy0/HMHSB9dSQIn3Y2bX/45Z8FszPu6Y+by5eIdN4AvKY+vEf
X-Received: by 10.31.150.134 with SMTP id y128mr220761vkd.102.1487907292689; Thu, 23 Feb 2017 19:34:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Thu, 23 Feb 2017 19:34:32 -0800 (PST)
In-Reply-To: <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 24 Feb 2017 12:34:32 +0900
Message-ID: <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
Content-Type: multipart/alternative; boundary=001a1141d600a410a205493e6977
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QI84RSoBxedqcEO3UBD47lrQBAg>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:34:55 -0000

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

On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <
morrowc.lists@gmail.com> wrote:

> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2017-03-01. 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."
>
> Nothing in the past really matters here, what matters is: "Is the bis
> draft all set, did we fix all the things which must be fixed before this
> draft becomes a real 'standard'?"
>

I don't think you can say nothing in the past matters here. We know that
there have been host implementations that relied on this guarantee, and we
have to consider that if we change the standard, those implementations will
become non-compliant.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:morrowc.lists@gmail.com" target=3D"_blank">morrowc.lists@gmai=
l.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"l=
tr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>&gt; The IES=
G plans to make a decision in the next few weeks, and solicits</div><div>&g=
t; final comments on this action. Please send substantive comments to the</=
div><div>&gt; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.=
org</a> mailing lists by 2017-03-01. Exceptionally, comments may be</div><d=
iv>&gt; sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@iet=
f.org</a> instead. In either case, please retain the</div><div>&gt; beginni=
ng of the Subject line to allow automated sorting.&quot;</div><div><br></di=
v><div>Nothing in the past really matters here, what matters is: &quot;Is t=
he bis draft all set, did we fix all the things which must be fixed before =
this draft becomes a real &#39;standard&#39;?&quot;</div></div></div></div>=
</blockquote><div><br></div><div>I don&#39;t think you can say nothing in t=
he past matters here. We know that there have been host implementations tha=
t relied on this guarantee, and we have to consider that if we change the s=
tandard, those implementations will become non-compliant.</div></div></div>=
</div>

--001a1141d600a410a205493e6977--


From nobody Thu Feb 23 19:38:21 2017
Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDE11294DA; Thu, 23 Feb 2017 19:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 o22hmu46kqgP; Thu, 23 Feb 2017 19:38:16 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0E59E1294C7; Thu, 23 Feb 2017 19:38:16 -0800 (PST)
Received: from [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f] (unknown [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 1EB23540BCD; Thu, 23 Feb 2017 22:37:59 -0500 (EST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
Date: Thu, 23 Feb 2017 22:37:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28DBAE9B-1E48-4246-8EB7-2F0723D0BD32@puck.nether.net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gOVLNyff7a5c9LPL12sjVbrWfuo>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:38:17 -0000

> On Feb 23, 2017, at 10:34 PM, Lorenzo Colitti <lorenzo@google.com> =
wrote:
>=20
> On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow =
<morrowc.lists@gmail.com> wrote:
> > The IESG plans to make a decision in the next few weeks, and =
solicits
> > final comments on this action. Please send substantive comments to =
the
> > ietf@ietf.org mailing lists by 2017-03-01. 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."
>=20
> Nothing in the past really matters here, what matters is: "Is the bis =
draft all set, did we fix all the things which must be fixed before this =
draft becomes a real 'standard'?"
>=20
> I don't think you can say nothing in the past matters here. We know =
that there have been host implementations that relied on this guarantee, =
and we have to consider that if we change the standard, those =
implementations will become non-compliant.

This has always been the case and was a big excuse given by Cisco back =
in the 1990s for not fixing the directed-broadcast problem.

For progress to occur sometimes a prior behavior will become invalid, if =
we can=E2=80=99t handle this then there=E2=80=99s no hope.  I don=E2=80=99=
t live in a world without hope.

- Jared=


From nobody Thu Feb 23 19:41:52 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5D2B129D50; Thu, 23 Feb 2017 19:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXyWN4MwBqrA; Thu, 23 Feb 2017 19:41:45 -0800 (PST)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 8C459129D51; Thu, 23 Feb 2017 19:41:44 -0800 (PST)
Received: by mail-qt0-x22f.google.com with SMTP id n21so8609286qta.1; Thu, 23 Feb 2017 19:41:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=iy9/NLfT2inTbMQsVJPcTux3WMus8X+6dLgtbVXSxWE=; b=H+kqfvbr6GDnNUkQZ19rFi9xa8zsRfUshNbR1tyiLZtuI/cCI+qJ95steDULY1dgze KGYFJUp8aIms6ID77V8cSW89lrDZ0fz4vksTxQ4q917yCntm8kIZtQ8jYTsYhO57EmF/ a6QRtdEQdNu4zEieGfUZBNcAjANBHEoI05ND7C9cJICHfbsvGVCkgsAOVfkRQg+6Tir8 fyeSE3I1+wIXvNz22rH4DlqhJs0gH6naZOnzzfaC6M82ehnd9ptpXbVYo32lPEANSZvx uoaSFmlfNoopAp4IXU8DSGxb4so2EMyuSEb/RSEn6s6DQ1Sz6DOQjcgotLw9+2FS1mRq 6wNw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=iy9/NLfT2inTbMQsVJPcTux3WMus8X+6dLgtbVXSxWE=; b=dLgd2fx/I37yl7yEiuKCyUFmq5sj33P/HgLUjXWqQ3KnM60zbAwt8A06GLW366LX7K 3CwW8o/8KXSoekO3EuT4eYF3E1aEARwDxsb5FnE1hT4tWmUSvp2WXyTPh0Aj7Sm8oLgE BHoKG91d9k9aABXUu1kWg5EBTOERnTlybB3lOOY1L23FfYRlzMlB5INJH/fMNNN1ZvFy fPJaxq1elYjcyMkK3h1m6esLHq0ubCsXyLGqmZH2y92+z9xlJvElgoZexARVZNbZthEt B/LBqF4mWPe+o4jmzFgIjbPCz0qUj9XhxK1kKCq5vfOipHxz5an1CVSGV9fYIJcBVuIs b3gA==
X-Gm-Message-State: AMke39njug8+NRhet417fQfWr5tk48/9jfXzfCj7p6kwMMeHRnlFa5Dj9fCzZMEz5+MsGaiFLBvJZNP42S0lXA==
X-Received: by 10.200.54.13 with SMTP id m13mr544368qtb.214.1487907703625; Thu, 23 Feb 2017 19:41:43 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Thu, 23 Feb 2017 19:41:43 -0800 (PST)
In-Reply-To: <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Thu, 23 Feb 2017 22:41:43 -0500
X-Google-Sender-Auth: OLTLickTXSE0eqfxvTFWx0d-Fe8
Message-ID: <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: multipart/alternative; boundary=001a1139f8ea2221b605493e82fe
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3uP-PhBuZigxh91UdkItuENkkSs>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 03:41:47 -0000

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

gosh people are being literal today :)

On Thu, Feb 23, 2017 at 10:34 PM, Lorenzo Colitti <lorenzo@google.com>
wrote:

> On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <
> morrowc.lists@gmail.com> wrote:
>
>> > The IESG plans to make a decision in the next few weeks, and solicits
>> > final comments on this action. Please send substantive comments to the
>> > ietf@ietf.org mailing lists by 2017-03-01. 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."
>>
>> Nothing in the past really matters here, what matters is: "Is the bis
>> draft all set, did we fix all the things which must be fixed before this
>> draft becomes a real 'standard'?"
>>
>
> I don't think you can say nothing in the past matters here. We know that
> there have been host implementations that relied on this guarantee, and we
> have to consider that if we change the standard, those implementations will
> become non-compliant.
>

I don't think the proposed (now 160+ messages back) text really says: "FREE
FOR ALL< NO LIMITS!!! WEEE!" it says: "Hey, if you want to use /64 because
the application you are being placed into requires it (slac, blah and blah
and ilnp and blah - see rfc7k) then do that, else any other prefix length
works"

how's that not 'ok' for host folks? "Hi, my host is going to be in a slaac
world.. so /64 it is!"

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

<div dir=3D"ltr">gosh people are being literal today :)<br><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote">On Thu, Feb 23, 2017 at 10:34 PM,=
 Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo@google.com=
" target=3D"_blank">lorenzo@google.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><span class=3D"">On Fri, Feb 24, 2017 at 12:23 PM, Christo=
pher Morrow <span dir=3D"ltr">&lt;<a href=3D"mailto:morrowc.lists@gmail.com=
" target=3D"_blank">morrowc.lists@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote"><div>&gt; The IESG plans to make a decision in the nex=
t few weeks, and solicits</div><div>&gt; final comments on this action. Ple=
ase send substantive comments to the</div><div>&gt; <a href=3D"mailto:ietf@=
ietf.org" target=3D"_blank">ietf@ietf.org</a> mailing lists by 2017-03-01. =
Exceptionally, comments may be</div><div>&gt; sent to <a href=3D"mailto:ies=
g@ietf.org" target=3D"_blank">iesg@ietf.org</a> instead. In either case, pl=
ease retain the</div><div>&gt; beginning of the Subject line to allow autom=
ated sorting.&quot;</div><div><br></div><div>Nothing in the past really mat=
ters here, what matters is: &quot;Is the bis draft all set, did we fix all =
the things which must be fixed before this draft becomes a real &#39;standa=
rd&#39;?&quot;</div></div></div></div></blockquote><div><br></div></span><d=
iv>I don&#39;t think you can say nothing in the past matters here. We know =
that there have been host implementations that relied on this guarantee, an=
d we have to consider that if we change the standard, those implementations=
 will become non-compliant.</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">I don&#39;t think t=
he proposed (now 160+ messages back) text really says: &quot;FREE FOR ALL&l=
t; NO LIMITS!!! WEEE!&quot; it says: &quot;Hey, if you want to use /64 beca=
use the application you are being placed into requires it (slac, blah and b=
lah and ilnp and blah - see rfc7k) then do that, else any other prefix leng=
th works&quot;</div><div class=3D"gmail_extra"><br></div><div class=3D"gmai=
l_extra">how&#39;s that not &#39;ok&#39; for host folks? &quot;Hi, my host =
is going to be in a slaac world.. so /64 it is!&quot;</div></div>

--001a1139f8ea2221b605493e82fe--


From nobody Thu Feb 23 21:53:30 2017
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0A23129585 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 21:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.488
X-Spam-Level: 
X-Spam-Status: No, score=-4.488 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 XqJPoWXJl7Rn for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 21:53:26 -0800 (PST)
Received: from mx0a-001b2d01.pphosted.com (mx0b-001b2d01.pphosted.com [148.163.158.5]) (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 B6255129584 for <ietf@ietf.org>; Thu, 23 Feb 2017 21:53:26 -0800 (PST)
Received: from pps.filterd (m0098414.ppops.net [127.0.0.1]) by mx0b-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v1O5miKH080675 for <ietf@ietf.org>; Fri, 24 Feb 2017 00:53:25 -0500
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by mx0b-001b2d01.pphosted.com with ESMTP id 28teq18naq-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 24 Feb 2017 00:53:25 -0500
Received: from localhost by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 23 Feb 2017 22:53:24 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 23 Feb 2017 22:53:21 -0700
Received: from b03cxnp07029.gho.boulder.ibm.com (b03cxnp07029.gho.boulder.ibm.com [9.17.130.16]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id CF72219D8026 for <ietf@ietf.org>; Thu, 23 Feb 2017 22:52:32 -0700 (MST)
Received: from b03ledav005.gho.boulder.ibm.com (b03ledav005.gho.boulder.ibm.com [9.17.130.236]) by b03cxnp07029.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v1O5rK7L17301852 for <ietf@ietf.org>; Thu, 23 Feb 2017 22:53:20 -0700
Received: from b03ledav005.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D711ABE042 for <ietf@ietf.org>; Thu, 23 Feb 2017 22:53:20 -0700 (MST)
Received: from rotala.raleigh.ibm.com (unknown [9.27.222.27]) by b03ledav005.gho.boulder.ibm.com (Postfix) with ESMTPS id A67BEBE03A for <ietf@ietf.org>; Thu, 23 Feb 2017 22:53:20 -0700 (MST)
Received: from rotala.raleigh.ibm.com (localhost [127.0.0.1]) by rotala.raleigh.ibm.com (8.15.2/8.12.5) with ESMTP id v1O5rJD9011557 for <ietf@ietf.org>; Fri, 24 Feb 2017 00:53:19 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v1O5rJFC011521 for ietf@ietf.org; Fri, 24 Feb 2017 00:53:19 -0500
From: narten@us.ibm.com
Date: Fri, 24 Feb 2017 00:53:19 -0500
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-GCONF: 00
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 17022405-0008-0000-0000-00000751EAFC
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00006673; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000204; SDB=6.00826309; UDB=6.00404688; IPR=6.00603761;  BA=6.00005168; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014420; XFM=3.00000011; UTC=2017-02-24 05:53:22
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17022405-0009-0000-0000-0000402EB616
Message-Id: <201702240553.v1O5rJFC011521@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-02-24_03:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=89 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702240060
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KADDVFdQ4tV8a7Bwxq50qsB3TzU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 05:53:29 -0000

Total of 246 messages in the last 7 days.
 
script run at: Fri Feb 24 00:53:13 EST 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.82% |   34 | 13.46% |   388174 | lorenzo@google.com
  5.69% |   14 |  4.59% |   132401 | job@ntt.net
  5.28% |   13 |  4.33% |   124742 | alexandre.petrescu@gmail.com
  3.66% |    9 |  5.04% |   145455 | farmer@umn.edu
  3.66% |    9 |  3.47% |   100088 | otroan@employees.org
  2.85% |    7 |  4.23% |   122023 | daedulus@btconnect.com
  3.66% |    9 |  3.27% |    94342 | brian.e.carpenter@gmail.com
  3.66% |    9 |  2.72% |    78340 | john-ietf@jck.com
  3.66% |    9 |  2.65% |    76463 | fgont@si6networks.com
  2.03% |    5 |  3.07% |    88584 | rg+ietf@randy.pensive.org
  2.85% |    7 |  2.20% |    63373 | touch@isi.edu
  2.85% |    7 |  1.73% |    49813 | randy@psg.com
  2.03% |    5 |  2.24% |    64514 | christopher.morrow@gmail.com
  0.41% |    1 |  3.74% |   107919 | jari.arkko@piuha.net
  2.03% |    5 |  1.98% |    57112 | markzzzsmith@gmail.com
  1.63% |    4 |  2.15% |    61968 | ted.ietf@gmail.com
  1.63% |    4 |  1.37% |    39450 | heard@pobox.com
  1.22% |    3 |  1.43% |    41295 | jhw@google.com
  1.22% |    3 |  1.36% |    39350 | mellon@fugue.com
  1.22% |    3 |  1.35% |    38891 | morrowc.lists@gmail.com
  1.22% |    3 |  1.22% |    35272 | albert.e.manfredi@boeing.com
  1.22% |    3 |  1.21% |    34751 | jmh@joelhalpern.com
  0.41% |    1 |  2.01% |    57909 | nrooney@gsma.com
  1.22% |    3 |  1.16% |    33435 | dannyniu@hotmail.com
  1.22% |    3 |  1.06% |    30549 | sm+ietf@elandsys.com
  0.81% |    2 |  1.45% |    41796 | ek@google.com
  1.22% |    3 |  1.02% |    29391 | marka@isc.org
  1.22% |    3 |  0.99% |    28588 | nite@hq.sk
  1.22% |    3 |  0.78% |    22580 | jared@puck.nether.net
  0.81% |    2 |  0.82% |    23579 | barryleiba@computer.org
  0.81% |    2 |  0.76% |    22014 | sander@steffann.nl
  0.81% |    2 |  0.72% |    20836 | housley@vigilsec.com
  0.41% |    1 |  1.08% |    31127 | gregimirsky@gmail.com
  0.81% |    2 |  0.65% |    18675 | sob@sobco.com
  0.41% |    1 |  1.05% |    30363 | rjsparks@nostrum.com
  0.81% |    2 |  0.64% |    18401 | rdroms.ietf@gmail.com
  0.81% |    2 |  0.64% |    18321 | stewart.bryant@gmail.com
  0.81% |    2 |  0.60% |    17313 | pierre.pfister@darou.fr
  0.81% |    2 |  0.56% |    16181 | lhotka@nic.cz
  0.81% |    2 |  0.53% |    15269 | gert@space.net
  0.81% |    2 |  0.47% |    13574 | nick@foobar.org
  0.41% |    1 |  0.88% |    25232 | gunnar.hellstrom@omnitor.se
  0.81% |    2 |  0.46% |    13147 | sthaug@nethelp.no
  0.41% |    1 |  0.85% |    24390 | mohamed.boucadair@orange.com
  0.81% |    2 |  0.41% |    11905 | nomcom-chair-2016@ietf.org
  0.81% |    2 |  0.39% |    11173 | jounikor@gmail.com
  0.41% |    1 |  0.55% |    15964 | shares@ndzh.com
  0.41% |    1 |  0.54% |    15641 | tuexen@fh-muenster.de
  0.41% |    1 |  0.54% |    15604 | worley@ariadne.com
  0.41% |    1 |  0.50% |    14385 | david.black@emc.com
  0.41% |    1 |  0.49% |    14020 | akatlas@gmail.com
  0.41% |    1 |  0.47% |    13561 | narten@us.ibm.com
  0.41% |    1 |  0.46% |    13220 | ietf@augustcellars.com
  0.41% |    1 |  0.44% |    12719 | abdussalambaryun@gmail.com
  0.41% |    1 |  0.43% |    12380 | wilco@baanhofman.nl
  0.41% |    1 |  0.41% |    11963 | alejandroacostaalamo@gmail.com
  0.41% |    1 |  0.41% |    11787 | dhruv.dhody@huawei.com
  0.41% |    1 |  0.41% |    11699 | jordi.palet@consulintel.es
  0.41% |    1 |  0.36% |    10449 | acee@cisco.com
  0.41% |    1 |  0.36% |    10281 | stephen.farrell@cs.tcd.ie
  0.41% |    1 |  0.34% |     9706 | jinmei@wide.ad.jp
  0.41% |    1 |  0.32% |     9233 | karsten_thomann@linfre.de
  0.41% |    1 |  0.31% |     9063 | peter@filament.com
  0.41% |    1 |  0.30% |     8589 | jouni.nospam@gmail.com
  0.41% |    1 |  0.29% |     8495 | joelja@bogus.com
  0.41% |    1 |  0.29% |     8437 | pch-ietf-6@u-1.phicoh.com
  0.41% |    1 |  0.29% |     8326 | fredbaker.ietf@gmail.com
  0.41% |    1 |  0.28% |     8197 | alexey.melnikov@isode.com
  0.41% |    1 |  0.27% |     7853 | julian.reschke@gmx.de
  0.41% |    1 |  0.26% |     7604 | chair@ietf.org
  0.41% |    1 |  0.26% |     7515 | pch-ipv6-ietf-3@u-1.phicoh.com
  0.41% |    1 |  0.26% |     7473 | julian.reschke@greenbytes.de
  0.41% |    1 |  0.25% |     7193 | xing@cernet.edu.cn
  0.41% |    1 |  0.24% |     6859 | heas@shrubbery.net
  0.41% |    1 |  0.23% |     6625 | phessler@theapt.org
  0.41% |    1 |  0.22% |     6235 | paul.hoffman@vpnc.org
  0.41% |    1 |  0.22% |     6203 | roni.even@mail01.huawei.com
  0.41% |    1 |  0.21% |     5995 | stewart@g3ysx.org.uk
--------+------+--------+----------+------------------------
100.00% |  246 |100.00% |  2883342 | Total


From SRS0=3dbs=2F=darou.fr=pierre.pfister@bounces.m4x.org  Thu Feb 23 22:58:54 2017
Return-Path: <SRS0=3dbs=2F=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98DD31295C1; Thu, 23 Feb 2017 22:58:54 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 h2pckoc5-FDg; Thu, 23 Feb 2017 22:58:52 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16E281295BC; Thu, 23 Feb 2017 22:58:51 -0800 (PST)
Received: from [10.61.217.135] (unknown [173.38.220.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 7990656475D; Fri, 24 Feb 2017 07:58:47 +0100 (CET)
From: Pierre Pfister <pierre.pfister@darou.fr>
Message-Id: <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_764C52CD-FD2D-4EAF-BC8D-CD381224AE4B"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Date: Fri, 24 Feb 2017 07:58:46 +0100
In-Reply-To: <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Feb 24 07:58:48 2017 +0100 (CET))
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4J2fCKk1YekS46nql3wCTcUgj_Q>
Cc: IPv6 Operations <v6ops@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 07:00:04 -0000

--Apple-Mail=_764C52CD-FD2D-4EAF-BC8D-CD381224AE4B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> Le 24 f=C3=A9vr. 2017 =C3=A0 04:27, Lorenzo Colitti =
<lorenzo@google.com> a =C3=A9crit :
>=20
> On Fri, Feb 24, 2017 at 7:43 AM, Pierre Pfister =
<pierre.pfister@darou.fr <mailto:pierre.pfister@darou.fr>> wrote:
> > The thing is this is not new text, it has been in RFC4291 for 11
> > years. c.f., 2.5.1.
>=20
> And during those 11 years. Nobody implemented this rule specific to =
::/3.
>=20
> I can implement it today in some of our code if you like :-).

Good luck getting that upstreamed ! ;-)

> But it seems unlikely to make a difference, since the rule only =
applies to unicast addresses in ::/3, and no such addresses have been =
released to the RIRs. That in turn is unlikely to change until we run =
out of 2000::/3, and even then we'll likely move on to allocating =
addresses out of 4000::/3 instead of from ::/3.


So what you are saying is that all currently assigned unicast addresses =
are out of the ::/3 prefix.=20
Meaning that, according to proposed standard, I should not be able to =
configure on-link prefixes of length different than 64 with currently =
assigned unicast addresses.
At least Linux, Windows, Apple, Cisco, and probably all mature IPv6 =
stacks, would let you configure prefixes of length different than 64.

- Pierre


--Apple-Mail=_764C52CD-FD2D-4EAF-BC8D-CD381224AE4B
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""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">Le 24 f=C3=A9vr. 2017 =C3=A0 04:27, Lorenzo Colitti &lt;<a =
href=3D"mailto:lorenzo@google.com" class=3D"">lorenzo@google.com</a>&gt; =
a =C3=A9crit :</div><br class=3D"Apple-interchange-newline"><div =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On Fri, Feb 24, 2017 at 7:43 AM, Pierre Pfister =
<span dir=3D"ltr" class=3D"">&lt;<a =
href=3D"mailto:pierre.pfister@darou.fr" target=3D"_blank" =
class=3D"">pierre.pfister@darou.fr</a>&gt;</span> wrote:<br =
class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt; =
The thing is this is not new text, it has been in RFC4291 for 11<br =
class=3D"">
&gt; years. c.f., 2.5.1.<br class=3D"">
<br class=3D"">
</span>And during those 11 years. Nobody implemented this rule specific =
to ::/3.<br class=3D""></blockquote><div class=3D""><br =
class=3D""></div><div class=3D"">I can implement it today in some of our =
code if you like :-). =
</div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>Good luck getting that upstreamed ! ;-)</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div class=3D"">But it seems unlikely to make a =
difference, since the rule only applies to unicast addresses in ::/3, =
and no such addresses have been released to the RIRs. That in turn is =
unlikely to change until we run out of 2000::/3, and even then we'll =
likely move on to allocating addresses out of 4000::/3 instead of from =
::/3.</div></div></div></div>
</div></blockquote></div><div class=3D""><br class=3D""></div><div =
class=3D"">So what you are saying is that all currently assigned unicast =
addresses are out of the ::/3 prefix.&nbsp;</div><div class=3D"">Meaning =
that, according to proposed standard, I should not be able to configure =
on-link prefixes of length different than 64 with currently assigned =
unicast addresses.</div><div class=3D"">At least Linux, Windows, Apple, =
Cisco, and probably all mature IPv6 stacks, would let you configure =
prefixes of length different than 64.</div><div class=3D""><br =
class=3D""></div><div class=3D"">- Pierre</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_764C52CD-FD2D-4EAF-BC8D-CD381224AE4B--


From nobody Thu Feb 23 23:15:53 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D383F1295C1 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wOuidDBTe8Q9 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:15:51 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 0A0BD1295B8 for <ietf@ietf.org>; Thu, 23 Feb 2017 23:15:51 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 877DEC50 for <ietf@ietf.org>; Fri, 24 Feb 2017 07:15:50 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9pyGx-HsTRWu for <ietf@ietf.org>; Fri, 24 Feb 2017 01:15:50 -0600 (CST)
Received: from mail-vk0-f69.google.com (mail-vk0-f69.google.com [209.85.213.69]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 44401C42 for <ietf@ietf.org>; Fri, 24 Feb 2017 01:15:50 -0600 (CST)
Received: by mail-vk0-f69.google.com with SMTP id s12so7993257vkf.1 for <ietf@ietf.org>; Thu, 23 Feb 2017 23:15:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QXiRWZU3C+aKDj3v20Tqd4EFZX1NoiGKtjGwBulchH0=; b=kfy2xG3fuzf6wtlftCram9l5YT22dQXpsZaoWnXU8hHXsAinuLhHiILFOEojtKz+ag JC9Sh9LHAM2D2E+Y7lw+8Xj8e3dHxj5QvEW45dKrQ/9b+uKIbUHQz7egCSNmjAUEmJ3h PFhfSfwNpwHh7bQ1eul7W8n2UQPZ/5B6Vv7kClQ4Gcl/d+8dIc2yhJ2Q9VbZihpnPsAs HfBasZ5fdCIxTIIA06OWSBk07v+CzxDXNV7IHboZEZYI1ZjBw3NK/CHLjiIrNoQguwN+ zYwyltBhDjfK1F1GxOzBMl4Y9e6bT4dMdUSLAhM3KYTSSIvmTiVwNCLsFwu1UA/EpQ7W ymNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QXiRWZU3C+aKDj3v20Tqd4EFZX1NoiGKtjGwBulchH0=; b=mV6Xrqs3XHF0C0/m5bK65Hi+Vi48Ka7fyWWREKWfCaO2Z7brNsK8x9YGnBPmnGHTjw QkQx2YiRBi00lzAkFxd5jS+NMIoxQ0w7NE1t5HGnN7FVzK95ZTJmmbXIKYFN9yOng15u 4b2WpRF9v/2FelmGthdHvOYdLZndQAVKwtuzIm4xeJiAT2wGAtsjGC9hybCv0eCvPI8K 3cfIKRGrrSvTQ8XhAv52OnfCvmoxicywEI8D57qYAYVDKpU7tEIBYkYpDCf36QRL0YOj Lc3lcCZjAGsLU6L/xkW1rw86c/LuhBEX5xmNBw73pPu1UHR+W17BI3YS7cfVaJfHGv/V EMeQ==
X-Gm-Message-State: AMke39m9C5Wo5TlNcfSeBa6wMOsgawTMMU4RnNL8S9lUvkwEyEv1yLRzzxwZvok4HLanUzEV0pI68lZJh+eGUbHOQ/pnkN6L2/eGesMK1XJrEWl2rRYm+iOqEZ151CZIagdSFMU8q7JS3qPKe1Q=
X-Received: by 10.31.252.77 with SMTP id a74mr520184vki.46.1487920549586; Thu, 23 Feb 2017 23:15:49 -0800 (PST)
X-Received: by 10.31.252.77 with SMTP id a74mr520179vki.46.1487920549349; Thu, 23 Feb 2017 23:15:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Thu, 23 Feb 2017 23:15:48 -0800 (PST)
In-Reply-To: <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com>
From: David Farmer <farmer@umn.edu>
Date: Fri, 24 Feb 2017 01:15:48 -0600
Message-ID: <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=94eb2c149b28cc6b950549417f36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YlEMDVqLMiVecH6YRXZfE20je0w>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, Lorenzo Colitti <lorenzo@google.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 07:15:53 -0000

--94eb2c149b28cc6b950549417f36
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont <fgont@si6networks.com>
wrote:
>
> I'd remove a few sentences here, as in:
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
>    purpose use, subnet prefixes of /127 are RECOMMENDED for point-
>    to-point router links [RFC6164]. The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421].


The problem is you have stripped out all the implementation guidance and
only left operational guidance.  But maybe the the right idea is to
separate the two, putting the operational guidance in Section 2.4 where we
are talking about prefixes and the implementation guidance in section 2.4.1
where we are talking about IIDs.
2nd Paragraph of 2.4;

   IPv6 unicast routing is based on prefixes of any valid length up to
   and including 128 [BCP198].  However, subnet prefixes of 64 bits in
   length are REQUIRED for use with Stateless Address Autoconfiguration
   (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
   use. The rationale for the 64 bit boundary in IPv6 addresses can be
   found in [RFC7421].

4th paragraph of 2.4.1

   For all unicast addresses, except those that start with the binary
   value 000, support for Interface IDs that are 64 bits long is
   REQUIRED, support for other Interface IDs lengths is OPTIONAL. The
   rationale for the 64 bit boundary in IPv6 addresses can be found in
   [RFC7421].

This clearly say that implementations that only support 64 bit IID lengths
are just fine, but also says implementations that allow IID lengths other
than 64 bits are just fine too.  I think the current and historic text
actually implies implementations are not to allow other IID lengths, is
that what we really intended to say?  A lot of implementations seem to
allow other IID lengths, are they wrong?  I don't think so.

This also gives strong operational guidance that 64 bit length subnet
prefixes are expected in most situations.  Reinforcing the 64 bit boundary,
however without outlawing the use of other subnet prefix lengths when
implemented and they could be useful.  This is done without distracting
from the 64 bit boundary, by not directly calling attention to RFC6164 or
the other longer prefix lengths. Since BCP198 and RFC7421 both reference
RFC6164 calling it out here doesn't seem necessary, and would unnecessarily
weaken the focus on the 64 bit boundary that I'm trying to maintain.

I don't see how this text would require changes in any code, nor does it
imply other IID lengths are not allowed operationally, again which a lot of
implementations seem to allow.

Thanks.
-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.=
com</a>&gt;</span> wrote:<blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I&#39;d remove a few sentences here, as in:<br>
<br>
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to<br>
=C2=A0 =C2=A0128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for gener=
al<br>
=C2=A0 =C2=A0purpose use, subnet prefixes of /127 are RECOMMENDED for point=
-<br>
=C2=A0 =C2=A0to-point router links [RFC6164]. The rationale for the 64 bit<=
br>
=C2=A0 =C2=A0boundary in IPv6 addresses can be found in [RFC7421].</blockqu=
ote><div><br></div><div>The problem is you have stripped out all the implem=
entation guidance and only left operational guidance.=C2=A0 But maybe the t=
he right idea is to separate the two, putting the operational guidance in S=
ection 2.4 where we are talking about prefixes and the implementation guida=
nce in section 2.4.1 where we are talking about IIDs.<br>2nd Paragraph of 2=
.4;<br><br>=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any va=
lid length up to<br>=C2=A0 =C2=A0and including 128 [BCP198].=C2=A0 However,=
 subnet prefixes of 64 bits in<br>=C2=A0 =C2=A0length are REQUIRED for use =
with Stateless Address Autoconfiguration<br>=C2=A0 =C2=A0(SLAAC)[RFC4862] a=
nd are RECOMMENDED for all other general purpose<br>=C2=A0 =C2=A0use. The r=
ationale for the 64 bit boundary in IPv6 addresses can be <br>=C2=A0 =C2=A0=
found in [RFC7421].<br><br>4th paragraph of 2.4.1<br><br>=C2=A0 =C2=A0For a=
ll unicast addresses, except those that start with the binary<br>=C2=A0 =C2=
=A0value 000, support for Interface IDs that are 64 bits long is <br>=C2=A0=
 =C2=A0REQUIRED, support for other Interface IDs lengths is OPTIONAL. The <=
br>=C2=A0 =C2=A0rationale for the 64 bit boundary in IPv6 addresses can be =
found in<br>=C2=A0 =C2=A0[RFC7421].<br><br>This clearly say that implementa=
tions that only support 64 bit IID lengths are just fine, but also says imp=
lementations that allow IID lengths other than 64 bits are just fine too.=
=C2=A0 I think the current and historic text actually implies implementatio=
ns are not to allow other IID lengths, is that what we really intended to s=
ay?=C2=A0 A lot of implementations seem to allow other IID lengths, are the=
y wrong?=C2=A0 I don&#39;t think so.</div></div><div class=3D"gmail_quote">=
<div><br></div><div>This also gives strong operational guidance that 64 bit=
 length subnet prefixes are expected in most situations.=C2=A0 Reinforcing =
the 64 bit boundary, however without outlawing the use of other subnet pref=
ix lengths when implemented and they could be useful.=C2=A0 This is done wi=
thout distracting from the 64 bit boundary, by not directly calling attenti=
on to RFC6164 or the other longer prefix lengths. Since BCP198 and RFC7421 =
both reference RFC6164 calling it out here doesn&#39;t seem necessary, and =
would unnecessarily weaken the focus on the 64 bit boundary that I&#39;m tr=
ying to maintain.</div><div><br></div><div>I don&#39;t see how this text wo=
uld require changes in any code, nor does it imply other IID lengths are no=
t allowed operationally, again which a lot of implementations seem to allow=
.=C2=A0</div></div></div><div class=3D"gmail_extra"><br></div><div class=3D=
"gmail_extra">Thanks.</div><div class=3D"gmail_extra">-- <br><div class=3D"=
gmail-m_-3119961681229421519gmail-m_1047141129374575656gmail-m_357877272716=
0228269gmail-m_18748652294737900gmail-m_-766940304165388083gmail_signature"=
>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<=
br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a hr=
ef=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu=
</a><br>Networking &amp; Telecommunication Services<br>Office of Informatio=
n Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 University Ave=
 SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612)%20626-0815" valu=
e=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>Minneapolis, MN 55=
414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-9952" value=3D"+16128=
129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c149b28cc6b950549417f36--


From nobody Thu Feb 23 23:53:37 2017
Return-Path: <SRS0=3dbs=2F=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 462E01295F1; Thu, 23 Feb 2017 23:53:32 -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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 dOc8NDPJildy; Thu, 23 Feb 2017 23:53:30 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1313A129514; Thu, 23 Feb 2017 23:53:30 -0800 (PST)
Received: from [10.61.217.135] (unknown [173.38.220.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 060BA5646FA; Fri, 24 Feb 2017 08:53:25 +0100 (CET)
From: Pierre Pfister <pierre.pfister@darou.fr>
Message-Id: <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr>
Content-Type: multipart/alternative; boundary="Apple-Mail=_357C3F7A-42B0-43C4-B43E-354CD3D5955E"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 24 Feb 2017 08:53:25 +0100
In-Reply-To: <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
To: David Farmer <farmer@umn.edu>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Feb 24 08:53:27 2017 +0100 (CET))
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0vklELzdxVf99wqVBHAnGAhpE4I>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 07:53:32 -0000

--Apple-Mail=_357C3F7A-42B0-43C4-B43E-354CD3D5955E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hello David,


> Le 24 f=C3=A9vr. 2017 =C3=A0 08:15, David Farmer <farmer@umn.edu> a =
=C3=A9crit :
>=20
>=20
>=20
> On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont <fgont@si6networks.com =
<mailto:fgont@si6networks.com>> wrote:
> I'd remove a few sentences here, as in:
>=20
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
>    purpose use, subnet prefixes of /127 are RECOMMENDED for point-
>    to-point router links [RFC6164]. The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421].
>=20
> The problem is you have stripped out all the implementation guidance =
and only left operational guidance.  But maybe the the right idea is to =
separate the two, putting the operational guidance in Section 2.4 where =
we are talking about prefixes and the implementation guidance in section =
2.4.1 where we are talking about IIDs.
> 2nd Paragraph of 2.4;
>=20
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    and including 128 [BCP198].  However, subnet prefixes of 64 bits in
>    length are REQUIRED for use with Stateless Address =
Autoconfiguration
>    (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
>    use. The rationale for the 64 bit boundary in IPv6 addresses can be=20=

>    found in [RFC7421].

Except RFC4862(SLAAC) does not say anywhere that 64 bits long IIDs are =
required.
Only mention I find of 64 is given as an example for EUI-64 for ethernet =
links.

>=20
> 4th paragraph of 2.4.1
>=20
>    For all unicast addresses, except those that start with the binary
>    value 000, support for Interface IDs that are 64 bits long is=20
>    REQUIRED, support for other Interface IDs lengths is OPTIONAL. The=20=

>    rationale for the 64 bit boundary in IPv6 addresses can be found in
>    [RFC7421].

1) The ::/3 rule is blatantly ignored by all implementations that I know =
of.
I don't see how something that has been ignored for years, and has=20
no implementation and deployment experience, could make its way to full =
standard.

2) "support for other Interface IDs lengths is OPTIONAL" -> Wait. What =
!?
This is not a compromise. You are just relaxing the requirement even =
more than it already is.
This is not what is implemented, nor what is deployed.

- Pierre

>=20
> This clearly say that implementations that only support 64 bit IID =
lengths are just fine, but also says implementations that allow IID =
lengths other than 64 bits are just fine too.  I think the current and =
historic text actually implies implementations are not to allow other =
IID lengths, is that what we really intended to say?  A lot of =
implementations seem to allow other IID lengths, are they wrong?  I =
don't think so.
>=20
> This also gives strong operational guidance that 64 bit length subnet =
prefixes are expected in most situations.  Reinforcing the 64 bit =
boundary, however without outlawing the use of other subnet prefix =
lengths when implemented and they could be useful.  This is done without =
distracting from the 64 bit boundary, by not directly calling attention =
to RFC6164 or the other longer prefix lengths. Since BCP198 and RFC7421 =
both reference RFC6164 calling it out here doesn't seem necessary, and =
would unnecessarily weaken the focus on the 64 bit boundary that I'm =
trying to maintain.
>=20
> I don't see how this text would require changes in any code, nor does =
it imply other IID lengths are not allowed operationally, again which a =
lot of implementations seem to allow.=20
>=20
> Thanks.
> --=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> David Farmer               Email:farmer@umn.edu =
<mailto:Email%3Afarmer@umn.edu>
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota  =20
> 2218 University Ave SE        Phone: 612-626-0815 =
<tel:(612)%20626-0815>
> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <tel:(612)%20812-9952>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


--Apple-Mail=_357C3F7A-42B0-43C4-B43E-354CD3D5955E
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 class=3D"">Hello David,</div><div class=3D""><br =
class=3D""></div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">Le 24 f=C3=A9vr. 2017 =C3=A0 08:15, David =
Farmer &lt;<a href=3D"mailto:farmer@umn.edu" =
class=3D"">farmer@umn.edu</a>&gt; a =C3=A9crit :</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><br class=3D""><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont =
<span dir=3D"ltr" class=3D"">&lt;<a href=3D"mailto:fgont@si6networks.com" =
target=3D"_blank" class=3D"">fgont@si6networks.com</a>&gt;</span> =
wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'd remove a few sentences here, as in:<br class=3D"">
<br class=3D"">
&nbsp; &nbsp;IPv6 unicast routing is based on prefixes of any valid =
length up to<br class=3D"">
&nbsp; &nbsp;128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for =
general<br class=3D"">
&nbsp; &nbsp;purpose use, subnet prefixes of /127 are RECOMMENDED for =
point-<br class=3D"">
&nbsp; &nbsp;to-point router links [RFC6164]. The rationale for the 64 =
bit<br class=3D"">
&nbsp; &nbsp;boundary in IPv6 addresses can be found in =
[RFC7421].</blockquote><div class=3D""><br =
class=3D""></div></div></div></div></div></blockquote><blockquote =
type=3D"cite" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"">The =
problem is you have stripped out all the implementation guidance and =
only left operational guidance.&nbsp; But maybe the the right idea is to =
separate the two, putting the operational guidance in Section 2.4 where =
we are talking about prefixes and the implementation guidance in section =
2.4.1 where we are talking about IIDs.<br class=3D"">2nd Paragraph of =
2.4;<br class=3D""><br class=3D"">&nbsp; &nbsp;IPv6 unicast routing is =
based on prefixes of any valid length up to<br class=3D"">&nbsp; =
&nbsp;and including 128 [BCP198].&nbsp; However, subnet prefixes of 64 =
bits in<br class=3D"">&nbsp; &nbsp;length are REQUIRED for use with =
Stateless Address Autoconfiguration<br class=3D"">&nbsp; =
&nbsp;(SLAAC)[RFC4862] and are RECOMMENDED for all other general =
purpose<br class=3D"">&nbsp; &nbsp;use. The rationale for the 64 bit =
boundary in IPv6 addresses can be <br class=3D"">&nbsp; &nbsp;found in =
[RFC7421].<br =
class=3D""></div></div></div></div></div></blockquote><div><br =
class=3D""></div><div><div>Except RFC4862(SLAAC) does not say anywhere =
that 64 bits long IIDs are required.</div><div>Only mention I find of 64 =
is given as an example for EUI-64 for ethernet links.</div></div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div class=3D""><br class=3D"">4th paragraph of =
2.4.1<br class=3D""><br class=3D"">&nbsp; &nbsp;For all unicast =
addresses, except those that start with the binary<br class=3D"">&nbsp; =
&nbsp;value 000, support for Interface IDs that are 64 bits long is <br =
class=3D"">&nbsp; &nbsp;REQUIRED, support for other Interface IDs =
lengths is OPTIONAL. The <br class=3D"">&nbsp; &nbsp;rationale for the =
64 bit boundary in IPv6 addresses can be found in<br class=3D"">&nbsp; =
&nbsp;[RFC7421].<br =
class=3D""></div></div></div></div></div></blockquote><div><br =
class=3D""></div><div>1) The ::/3 rule is blatantly ignored by all =
implementations that I know of.</div><div>I don't see how something that =
has been ignored for years, and has&nbsp;</div><div>no implementation =
and deployment experience, could make its way to full =
standard.</div><div><br class=3D""></div><div>2) "support for other =
Interface IDs lengths is OPTIONAL" -&gt; Wait. What !?</div><div>This is =
not a compromise. You are just relaxing the requirement even more than =
it already is.</div><div>This is not what is implemented, nor what is =
deployed.</div><div><br class=3D""></div><div>- Pierre</div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
dir=3D"ltr" class=3D""><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div class=3D""><br class=3D"">This clearly say =
that implementations that only support 64 bit IID lengths are just fine, =
but also says implementations that allow IID lengths other than 64 bits =
are just fine too.&nbsp; I think the current and historic text actually =
implies implementations are not to allow other IID lengths, is that what =
we really intended to say?&nbsp; A lot of implementations seem to allow =
other IID lengths, are they wrong?&nbsp; I don't think =
so.</div></div><div class=3D"gmail_quote"><div class=3D""><br =
class=3D""></div><div class=3D"">This also gives strong operational =
guidance that 64 bit length subnet prefixes are expected in most =
situations.&nbsp; Reinforcing the 64 bit boundary, however without =
outlawing the use of other subnet prefix lengths when implemented and =
they could be useful.&nbsp; This is done without distracting from the 64 =
bit boundary, by not directly calling attention to RFC6164 or the other =
longer prefix lengths. Since BCP198 and RFC7421 both reference RFC6164 =
calling it out here doesn't seem necessary, and would unnecessarily =
weaken the focus on the 64 bit boundary that I'm trying to =
maintain.</div><div class=3D""><br class=3D""></div><div class=3D"">I =
don't see how this text would require changes in any code, nor does it =
imply other IID lengths are not allowed operationally, again which a lot =
of implementations seem to allow.&nbsp;</div></div></div><div =
class=3D"gmail_extra"><br class=3D""></div><div =
class=3D"gmail_extra">Thanks.</div><div class=3D"gmail_extra">-- <br =
class=3D""><div =
class=3D"gmail-m_-3119961681229421519gmail-m_1047141129374575656gmail-m_35=
78772727160228269gmail-m_18748652294737900gmail-m_-766940304165388083gmail=
_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr class=3D"">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D<br class=3D"">David Farmer&nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;&nbsp; <a href=3D"mailto:Email%3Afarmer@umn.edu" =
target=3D"_blank" class=3D"">Email:farmer@umn.edu</a><br =
class=3D"">Networking &amp; Telecommunication Services<br =
class=3D"">Office of Information Technology<br class=3D"">University of =
Minnesota&nbsp;&nbsp; <br class=3D"">2218 University Ave SE&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: <a href=3D"tel:(612)%20626-0815" =
value=3D"+16126260815" target=3D"_blank" class=3D"">612-626-0815</a><br =
class=3D"">Minneapolis, MN 55414-3029&nbsp;&nbsp; Cell: <a =
href=3D"tel:(612)%20812-9952" value=3D"+16128129952" target=3D"_blank" =
class=3D"">612-812-9952</a><br =
class=3D"">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr class=3D"">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D </div>
</div></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_357C3F7A-42B0-43C4-B43E-354CD3D5955E--


From nobody Thu Feb 23 23:55:47 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACECC1295F4 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:55:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 NP6PBnKvygTt for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:55:44 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF6221295EC for <ietf@ietf.org>; Thu, 23 Feb 2017 23:55:43 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2846860DB2 for <ietf@ietf.org>; Fri, 24 Feb 2017 08:55:42 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id D085F600EA; Fri, 24 Feb 2017 08:55:41 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id C1EC38705; Fri, 24 Feb 2017 08:55:41 +0100 (CET)
Date: Fri, 24 Feb 2017 08:55:41 +0100
From: Gert Doering <gert@space.net>
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170224075541.GV2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RFh_fhfHuQ5q03eBVlKFVLyNXho>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 07:55:46 -0000

Hi,

On Fri, Feb 24, 2017 at 12:34:32PM +0900, Lorenzo Colitti wrote:
> I don't think you can say nothing in the past matters here. We know that
> there have been host implementations that relied on this guarantee, and we
> have to consider that if we change the standard, those implementations will
> become non-compliant.

Details, please.  Besides SLAAC not working (because not defined), which
implementations will not work with non-/64 network length?

You might know, but if you say "we know", it's not including myself (yet).

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

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


From nobody Thu Feb 23 23:59:43 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF17B129622 for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:59:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 FDYkwyX5tFrC for <ietf@ietfa.amsl.com>; Thu, 23 Feb 2017 23:59:42 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0712812960F for <ietf@ietf.org>; Thu, 23 Feb 2017 23:59:42 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 9784760262 for <ietf@ietf.org>; Fri, 24 Feb 2017 08:59:40 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id 628A7600EA; Fri, 24 Feb 2017 08:59:40 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id 53B638762; Fri, 24 Feb 2017 08:59:40 +0100 (CET)
Date: Fri, 24 Feb 2017 08:59:40 +0100
From: Gert Doering <gert@space.net>
To: Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170224075940.GW2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oJjrDnTmBeXe8TTWhDY54YE4Z_Q>
Cc: IPv6 Operations <v6ops@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 07:59:43 -0000

Hi,

On Thu, Feb 23, 2017 at 11:43:52PM +0100, Pierre Pfister wrote:
> >>>                                          However, the Interface ID of
> >>>   all unicast addresses, except those that start with the binary value
> >>>   000, is required to be 64 bits long.
> >> 
> > 
> > The thing is this is not new text, it has been in RFC4291 for 11
> > years. c.f., 2.5.1.
> 
> And during those 11 years. Nobody implemented this rule specific to ::/3.

The point is not "specific rule for ::/3".  The point is that this is a
explicit rule for all that is *not* ::/3, with an exception(!) for ::/3.

... and still there are other RFCs that permit /126 and /127, so this
definitely needs rewording to match current reality.

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

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


From nobody Fri Feb 24 00:07:04 2017
Return-Path: <gunnar.hellstrom@omnitor.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7A58129637 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:06:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 PTTT2_bvz83E for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:06:57 -0800 (PST)
Received: from bin-vsp-out-02.atm.binero.net (bin-mail-out-06.binero.net [195.74.38.229]) (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 D387B12999A for <ietf@ietf.org>; Fri, 24 Feb 2017 00:06:56 -0800 (PST)
X-Halon-ID: 312b51de-fa68-11e6-af92-005056917f90
Authorized-sender: gunnar.hellstrom@omnitor.se
Received: from [192.168.2.136] (unknown [77.53.231.21]) by bin-vsp-out-02.atm.binero.net (Halon Mail Gateway) with ESMTPSA; Fri, 24 Feb 2017 09:06:48 +0100 (CET)
Subject: Re: [Slim] IETF last call for draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA registrations)
To: Randall Gellens <rg+ietf@randy.pensive.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>, slim@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se> <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se> <p06240604d4ca31180a3d@[99.111.97.136]> <ce88e536-7675-b3f9-a999-314e2626056e@alum.mit.edu> <p06240609d4d3c1973459@[99.111.97.136]>
From: =?UTF-8?Q?Gunnar_Hellstr=c3=b6m?= <gunnar.hellstrom@omnitor.se>
Message-ID: <69f9c707-345c-e90f-ba24-54173c311d72@omnitor.se>
Date: Fri, 24 Feb 2017 09:06:49 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <p06240609d4d3c1973459@[99.111.97.136]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KCb00SV--NLolXm1Lwnp92eCqso>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 08:07:00 -0000

Den 2017-02-22 kl. 23:33, skrev Randall Gellens:
>
> After reading through draft-ietf-mmusic-sdp-mux-attributes, I agree 
> and have added "MUX Category:  normal" to both attributes.
NORMAL    with capitals seems to be the form to register.  please change 
in the draft.

Regards
Gunnar

-- 


From nobody Fri Feb 24 00:16:12 2017
Return-Path: <prvs=1228d0687a=jordi.palet@consulintel.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF5C12957E for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:16:11 -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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vg9qqGi7fBpc for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:16:09 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 487EF1293F9 for <ietf@ietf.org>; Fri, 24 Feb 2017 00:16:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1487923967; x=1488528767; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=z6tVewotDTpHumkSMjftf5FjL 4K8e8oMpUJ1pC8/l0E=; b=TGSuBv4iemK42GHaVoSTAAhv3YXJ5ew76+hEQvEr3 LjQUR2w40vZCPnZ59MdiSE9zwsNQ6CJhbwCqa8Y1fGrCGpn6rdrqNc/2esIin0Ca M3ZQKUzwkpFrvVfLSc8k/b5qTTiKQ38YKrch1gQyYhNbXRJ05ITOcgON0dJJDWW1 LA=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=f/RWR1bMrqMJjWUDI/PoaeZ43DOmvn7AA9VoZy+hCBpOsKU0KNQggaxxa0id pplF6avUJZCsi6bFN8PR3623X815vP4QwmOSWInKs70WDX+1SGPZ1ley9 WoZ6mbLzfUQz9Iv1nsa9230efZCi5XozxVUoFKZsOuv9PeVsdNTmYI=;
X-MDAV-Processed: mail.consulintel.es, Fri, 24 Feb 2017 09:12:47 +0100
X-Spam-Processed: mail.consulintel.es, Fri, 24 Feb 2017 09:12:47 +0100
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005373437.msg for <ietf@ietf.org>; Fri, 24 Feb 2017 09:12:46 +0100
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170224:md50005373437::ELeEBc8fXQBnK+Vs:000026QP
X-Return-Path: prvs=1228d0687a=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: ietf@ietf.org
User-Agent: Microsoft-MacOutlook/f.1f.0.170216
Date: Fri, 24 Feb 2017 09:12:45 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
Message-ID: <4BC61E42-0A36-44E9-8FB9-2062547D939F@consulintel.es>
Thread-Topic: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <20170224075940.GW2367@Space.Net>
In-Reply-To: <20170224075940.GW2367@Space.Net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z3lEyC7PMn4kP0GEnRSJQGKEDAI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: jordi.palet@consulintel.es
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 08:16:11 -0000

I wonder if anyone knows (or if there is an easy way to check, I doubt), if=
 other STD documents have similar situations.

I mean, we define STDs, it takes long time to do so and meanwhile is still =
an RFC or even after a document is already an STD, there may be text sectio=
ns that don=E2=80=99t reflect market reality, or some very specific excepti=
ons (such as in this case /126-/127), that make sense (or not), but in any =
case, the STD is not being modified again and again.

I=E2=80=99m sure this happens in any kind of documents in other business an=
d life fields, for example, there may be generic laws, and afterwards, the =
generic law is not modified for many many many years, but =E2=80=9Cexceptio=
n rules=E2=80=9D are created for those laws.

So, are we spending too much time in this and is not really necessary?

Can we live with the actual text with has been in the market, and working w=
ell, for =E2=80=9Cx=E2=80=9D years?

Can we make too many (or few very important) changes in an RFC in the way t=
o STD, or we need first to have those changes in an RFC for =E2=80=9Cx=E2=
=80=9D years and =E2=80=9Cn=E2=80=9D verified implementations, before we mo=
ve to STD? If the answer is no, is the balance between living with the curr=
ent text but moving to STD a better option than waiting for =E2=80=9Cx=E2=
=80=9D years again?

Regards,
Jordi
=20

-----Mensaje original-----
De: ietf <ietf-bounces@ietf.org> en nombre de Gert Doering <gert@space.net>
Responder a: <gert@space.net>
Fecha: viernes, 24 de febrero de 2017, 8:59
Para: Pierre Pfister <pierre.pfister@darou.fr>
CC: IPv6 Operations <v6ops@ietf.org>, Mark Smith <markzzzsmith@gmail.com>, =
IETF <ietf@ietf.org>
Asunto: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets

    Hi,
   =20
    On Thu, Feb 23, 2017 at 11:43:52PM +0100, Pierre Pfister wrote:
    > >>>                                          However, the Interface I=
D of
    > >>>   all unicast addresses, except those that start with the binary =
value
    > >>>   000, is required to be 64 bits long.
    > >>=20
    > >=20
    > > The thing is this is not new text, it has been in RFC4291 for 11
    > > years. c.f., 2.5.1.
    >=20
    > And during those 11 years. Nobody implemented this rule specific to :=
:/3.
   =20
    The point is not "specific rule for ::/3".  The point is that this is a
    explicit rule for all that is *not* ::/3, with an exception(!) for ::/3=
.
   =20
    ... and still there are other RFCs that permit /126 and /127, so this
    definitely needs rewording to match current reality.
   =20
    Gert Doering
            -- NetMaster
    --=20
    have you enabled IPv6 on something today...?
   =20
    SpaceNet AG                        Vorstand: Sebastian v. Bomhard
    Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Cule=
mann
    D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
    Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
   =20
   =20
   =20



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or con=
fidential. The information is intended to be for the use of the individual(=
s) named above. If you are not the intended recipient be aware that any dis=
closure, copying, distribution or use of the contents of this information, =
including attached files, is prohibited.




From nobody Fri Feb 24 00:20:38 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C7B129648 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:20:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.801
X-Spam-Level: 
X-Spam-Status: No, score=-3.801 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cuOZ_S_4bSZS for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 00:20:12 -0800 (PST)
Received: from mta-p7.oit.umn.edu (mta-p7.oit.umn.edu [134.84.196.207]) (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 CA03812963D for <ietf@ietf.org>; Fri, 24 Feb 2017 00:20:12 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p7.oit.umn.edu (Postfix) with ESMTP id 4FF46C59 for <ietf@ietf.org>; Fri, 24 Feb 2017 08:20:12 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p7.oit.umn.edu ([127.0.0.1]) by localhost (mta-p7.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NUFLad4gZZQg for <ietf@ietf.org>; Fri, 24 Feb 2017 02:20:12 -0600 (CST)
Received: from mail-ua0-f197.google.com (mail-ua0-f197.google.com [209.85.217.197]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p7.oit.umn.edu (Postfix) with ESMTPS id 07A00C50 for <ietf@ietf.org>; Fri, 24 Feb 2017 02:20:11 -0600 (CST)
Received: by mail-ua0-f197.google.com with SMTP id 48so8561108uaf.7 for <ietf@ietf.org>; Fri, 24 Feb 2017 00:20:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1TMAmfx/iFF1nFBFM7I4LDSQmO0B3V9NVlTDDK9e0OE=; b=FPrkVTrDYBY2pTMrR2O2HmO2q60MGTANDsRpyYQl+A8PrX6OcaQQ7KPFkMYgpXyNkC cpWWfJrHam6npspPItD4FOvTzOX8NiqI70v5Eh++GAzjFoDDz+SojI7LmjGJ9qifG7X6 KDMvzW9ognMtrXhDbe+mxPvZOB84u8kvvoHCLAuL1wqHGM5Siq5BaOKTYSC35dXHSyyh 7iQy0w32Es7iQpXw09f8/IdXjxeBSOeDZ6fMLZH5GMt1rwaka3fMT3RzYR53ppEJP9aR JjUnnY6oR6axDghpcQTwH+CjS2boVEIq9rJvbj3jBuILcZ/VKvX9a9uAkZ6ZaQwbvrQp u6MA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1TMAmfx/iFF1nFBFM7I4LDSQmO0B3V9NVlTDDK9e0OE=; b=lQee37kC2VtO50P9cm65DmLlWFfcN1cB6bU5xKdKNVe6eXdw4XolrNhrOS6D7K3f/n W1TYXjUNVjh9AYy2SccHyIONTPnFNbZ/Nae/POKXl86OQObqijZSkjkO+fmgXClNNise BrOSybFEJhlx4pG16maBmeEaNl6rwtIb68d+AMV6z3HunsSwmrgsw0kGT4wCwf57E0X+ QzcyMo/yUAwtm9HhyEzDEMkIjm9HTi+1l4YUbwhWOTBri4XaouExPXGEF/6OMwSdGHTz d+JwBedZvSUwT8uz5yrQhOWC6KgxgZ9QNxa+zmXlBpTkCDXQiwsomrMvEevRSMTEybKJ 9A1w==
X-Gm-Message-State: AMke39nefKdIdJNu2b+uki6DwB9Mj2E2o8tVFuqdK2G1HIArQx0X9UNSOc7gCKULefWNaJXOyvb0JQYqrMeS77ZuoO1rd/kl7ubYKmpuvDFBW7RMM7TppmRLvlNawDFYn2rCeSTytkOlBN/M/fs=
X-Received: by 10.31.114.133 with SMTP id n127mr632580vkc.129.1487924411323; Fri, 24 Feb 2017 00:20:11 -0800 (PST)
X-Received: by 10.31.114.133 with SMTP id n127mr632570vkc.129.1487924410984; Fri, 24 Feb 2017 00:20:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Fri, 24 Feb 2017 00:20:09 -0800 (PST)
In-Reply-To: <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com> <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr>
From: David Farmer <farmer@umn.edu>
Date: Fri, 24 Feb 2017 02:20:09 -0600
Message-ID: <CAN-Dau3shR-f9hA0Thnv7caRKQieiaqnA-4MweDikWk4kBqiUg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: multipart/alternative; boundary=94eb2c1497b4f87bbc0549426585
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UZMv5vSK_qc7TuQ3UkwGKiVsHA4>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, Christopher Morrow <christopher.morrow@gmail.com>, Job Snijders <job@ntt.net>, Lorenzo Colitti <lorenzo@google.com>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 08:20:27 -0000

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

On Fri, Feb 24, 2017 at 1:53 AM, Pierre Pfister <pierre.pfister@darou.fr>
wrote:

> Hello David,
>
>
> Le 24 f=C3=A9vr. 2017 =C3=A0 08:15, David Farmer <farmer@umn.edu> a =C3=
=A9crit :
>
>
>
> On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont <fgont@si6networks.com>
> wrote:
>>
>> I'd remove a few sentences here, as in:
>>
>>    IPv6 unicast routing is based on prefixes of any valid length up to
>>    128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
>>    purpose use, subnet prefixes of /127 are RECOMMENDED for point-
>>    to-point router links [RFC6164]. The rationale for the 64 bit
>>    boundary in IPv6 addresses can be found in [RFC7421].
>
>
> The problem is you have stripped out all the implementation guidance and
> only left operational guidance.  But maybe the the right idea is to
> separate the two, putting the operational guidance in Section 2.4 where w=
e
> are talking about prefixes and the implementation guidance in section 2.4=
.1
> where we are talking about IIDs.
> 2nd Paragraph of 2.4;
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    and including 128 [BCP198].  However, subnet prefixes of 64 bits in
>    length are REQUIRED for use with Stateless Address Autoconfiguration
>    (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
>    use. The rationale for the 64 bit boundary in IPv6 addresses can be
>    found in [RFC7421].
>
>
> Except RFC4862(SLAAC) does not say anywhere that 64 bits long IIDs are
> required.
> Only mention I find of 64 is given as an example for EUI-64 for ethernet
> links.
>

I believe most implementations of SLAAC require /64, but I could be wrong.

> 4th paragraph of 2.4.1
>
>    For all unicast addresses, except those that start with the binary
>    value 000, support for Interface IDs that are 64 bits long is
>    REQUIRED, support for other Interface IDs lengths is OPTIONAL. The
>    rationale for the 64 bit boundary in IPv6 addresses can be found in
>    [RFC7421].
>
>
> 1) The ::/3 rule is blatantly ignored by all implementations that I know
> of.
> I don't see how something that has been ignored for years, and has
> no implementation and deployment experience, could make its way to full
> standard.
>

I'm willing to let that go too, but it was there so I left it for now.


> 2) "support for other Interface IDs lengths is OPTIONAL" -> Wait. What !?
> This is not a compromise. You are just relaxing the requirement even more
> than it already is.
> This is not what is implemented, nor what is deployed.
>

Most routers let you specify any subnet length you want they default to /64
usually.  Also, many host OSes when you manually config let you specify any
subnet length too.  By making it OPTIONAL, I'm saying it ok to do that, or
not if the you don't want too.


> - Pierre
>
>
> This clearly say that implementations that only support 64 bit IID length=
s
> are just fine, but also says implementations that allow IID lengths other
> than 64 bits are just fine too.  I think the current and historic text
> actually implies implementations are not to allow other IID lengths, is
> that what we really intended to say?  A lot of implementations seem to
> allow other IID lengths, are they wrong?  I don't think so.
>
> This also gives strong operational guidance that 64 bit length subnet
> prefixes are expected in most situations.  Reinforcing the 64 bit boundar=
y,
> however without outlawing the use of other subnet prefix lengths when
> implemented and they could be useful.  This is done without distracting
> from the 64 bit boundary, by not directly calling attention to RFC6164 or
> the other longer prefix lengths. Since BCP198 and RFC7421 both reference
> RFC6164 calling it out here doesn't seem necessary, and would unnecessari=
ly
> weaken the focus on the 64 bit boundary that I'm trying to maintain.
>
> I don't see how this text would require changes in any code, nor does it
> imply other IID lengths are not allowed operationally, again which a lot =
of
> implementations seem to allow.
>
>


--=20
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 1:53 AM, Pierre Pfister <span dir=3D"ltr">&lt;<=
a href=3D"mailto:pierre.pfister@darou.fr" target=3D"_blank">pierre.pfister@=
darou.fr</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div sty=
le=3D"word-wrap:break-word"><div>Hello David,</div><div><br></div><br><div>=
<blockquote type=3D"cite"><div>Le 24 f=C3=A9vr. 2017 =C3=A0 08:15, David Fa=
rmer &lt;<a href=3D"mailto:farmer@umn.edu" target=3D"_blank">farmer@umn.edu=
</a>&gt; a =C3=A9crit :</div><br class=3D"m_-6792567943045310741Apple-inter=
change-newline"><div><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" target=3D"_blan=
k">fgont@si6networks.com</a>&gt;</span> wrote:<blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">
I&#39;d remove a few sentences here, as in:<br>
<br>
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to<br>
=C2=A0 =C2=A0128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for gener=
al<br>
=C2=A0 =C2=A0purpose use, subnet prefixes of /127 are RECOMMENDED for point=
-<br>
=C2=A0 =C2=A0to-point router links [RFC6164]. The rationale for the 64 bit<=
br>
=C2=A0 =C2=A0boundary in IPv6 addresses can be found in [RFC7421].</blockqu=
ote><div><br></div></div></div></div></div></blockquote><blockquote type=3D=
"cite"><div><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail=
_quote"><div>The problem is you have stripped out all the implementation gu=
idance and only left operational guidance.=C2=A0 But maybe the the right id=
ea is to separate the two, putting the operational guidance in Section 2.4 =
where we are talking about prefixes and the implementation guidance in sect=
ion 2.4.1 where we are talking about IIDs.<br>2nd Paragraph of 2.4;<br><br>=
=C2=A0 =C2=A0IPv6 unicast routing is based on prefixes of any valid length =
up to<br>=C2=A0 =C2=A0and including 128 [BCP198].=C2=A0 However, subnet pre=
fixes of 64 bits in<br>=C2=A0 =C2=A0length are REQUIRED for use with Statel=
ess Address Autoconfiguration<br>=C2=A0 =C2=A0(SLAAC)[RFC4862] and are RECO=
MMENDED for all other general purpose<br>=C2=A0 =C2=A0use. The rationale fo=
r the 64 bit boundary in IPv6 addresses can be <br>=C2=A0 =C2=A0found in [R=
FC7421].<br></div></div></div></div></div></blockquote><div><br></div><div>=
<div>Except RFC4862(SLAAC) does not say anywhere that 64 bits long IIDs are=
 required.</div><div>Only mention I find of 64 is given as an example for E=
UI-64 for ethernet links.</div></div></div></div></blockquote><div><br></di=
v><div>I believe most implementations of SLAAC require /64, but I could be =
wrong.=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:br=
eak-word"><div><blockquote type=3D"cite"><div><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote"><div>4th paragraph of 2.4.1<br>=
<br>=C2=A0 =C2=A0For all unicast addresses, except those that start with th=
e binary<br>=C2=A0 =C2=A0value 000, support for Interface IDs that are 64 b=
its long is <br>=C2=A0 =C2=A0REQUIRED, support for other Interface IDs leng=
ths is OPTIONAL. The <br>=C2=A0 =C2=A0rationale for the 64 bit boundary in =
IPv6 addresses can be found in<br>=C2=A0 =C2=A0[RFC7421].<br></div></div></=
div></div></div></blockquote><div><br></div><div>1) The ::/3 rule is blatan=
tly ignored by all implementations that I know of.</div><div>I don&#39;t se=
e how something that has been ignored for years, and has=C2=A0</div><div>no=
 implementation and deployment experience, could make its way to full stand=
ard.</div></div></div></blockquote><div><br></div><div>I&#39;m willing to l=
et that go too, but it was there so I left it for now.</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><=
div>2) &quot;support for other Interface IDs lengths is OPTIONAL&quot; -&gt=
; Wait. What !?</div><div>This is not a compromise. You are just relaxing t=
he requirement even more than it already is.</div><div>This is not what is =
implemented, nor what is deployed.</div></div></div></blockquote><div><br><=
/div><div>Most routers let you specify any subnet length you want they defa=
ult to /64 usually.=C2=A0 Also, many host OSes when you manually config let=
 you specify any subnet length too.=C2=A0 By making it OPTIONAL, I&#39;m sa=
ying it ok to do that, or not if the you don&#39;t want too.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"=
><div><div>- Pierre</div><br><blockquote type=3D"cite"><div><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br>This clear=
ly say that implementations that only support 64 bit IID lengths are just f=
ine, but also says implementations that allow IID lengths other than 64 bit=
s are just fine too.=C2=A0 I think the current and historic text actually i=
mplies implementations are not to allow other IID lengths, is that what we =
really intended to say?=C2=A0 A lot of implementations seem to allow other =
IID lengths, are they wrong?=C2=A0 I don&#39;t think so.</div></div><div cl=
ass=3D"gmail_quote"><div><br></div><div>This also gives strong operational =
guidance that 64 bit length subnet prefixes are expected in most situations=
.=C2=A0 Reinforcing the 64 bit boundary, however without outlawing the use =
of other subnet prefix lengths when implemented and they could be useful.=
=C2=A0 This is done without distracting from the 64 bit boundary, by not di=
rectly calling attention to RFC6164 or the other longer prefix lengths. Sin=
ce BCP198 and RFC7421 both reference RFC6164 calling it out here doesn&#39;=
t seem necessary, and would unnecessarily weaken the focus on the 64 bit bo=
undary that I&#39;m trying to maintain.</div><div><br></div><div>I don&#39;=
t see how this text would require changes in any code, nor does it imply ot=
her IID lengths are not allowed operationally, again which a lot of impleme=
ntations seem to allow.=C2=A0</div></div></div></div></div></blockquote></d=
iv></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><di=
v class=3D"gmail_signature" data-smartmail=3D"gmail_signature">=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br>David Farmer=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=C2=A0 <a href=3D"mailto:Email=
%3Afarmer@umn.edu" target=3D"_blank">Email:farmer@umn.edu</a><br>Networking=
 &amp; Telecommunication Services<br>Office of Information Technology<br>Un=
iversity of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, MN 55414-3029=C2=A0=C2=A0=
 Cell: 612-812-9952<br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c1497b4f87bbc0549426585--


From nobody Fri Feb 24 00:56:00 2017
Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 211BE129616; Fri, 24 Feb 2017 00:55:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level: 
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=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 pjmQFCMH3kzd; Fri, 24 Feb 2017 00:55:56 -0800 (PST)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1816129545; Fri, 24 Feb 2017 00:55:55 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 32DE51C0335; Fri, 24 Feb 2017 09:55:54 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.58]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 1876CC0062; Fri, 24 Feb 2017 09:55:54 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM33.corporate.adroot.infra.ftgroup ([fe80::3881:fc15:b4b2:9017%19]) with mapi id 14.03.0319.002; Fri, 24 Feb 2017 09:55:53 +0100
From: <mohamed.boucadair@orange.com>
To: Ted Hardie <ted.ietf@gmail.com>
Subject: RE: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Topic: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
Thread-Index: AQHSji4yv8+hFRXjgUOxh4v9Z5bKrKF30bNw
Date: Fri, 24 Feb 2017 08:55:53 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
In-Reply-To: <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.5]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B933009E183CFOPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0BXcqZRnbVPdJpcAV192PoYhDGE>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 08:55:58 -0000

--_000_787AE7BB302AE849A7480A190F8B933009E183CFOPEXCLILMA3corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgVGVkLA0KDQpQbGVhc2Ugc2VlIGlubGluZS4NCg0KQ2hlZXJzLA0KTWVkDQoNCkRlIDogVGVk
IEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NCkVudm95w6kgOiB2ZW5kcmVkaSAy
NCBmw6l2cmllciAyMDE3IDAwOjQwDQrDgCA6IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE4NCkNj
IDogaWV0ZkBpZXRmLm9yZzsgZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9u
QGlldGYub3JnDQpPYmpldCA6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1oYXJkaWUtcHJpdnNlYy1t
ZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0PiAoRGVzaWduIGNvbnNpZGVyYXRpb25zIGZvciBNZXRh
ZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkhJIE1vaGFtYWQsDQoNClRo
YW5rcyBmb3IgcmVjaGVja2luZzsgc29tZSBmdXJ0aGVyIGNvbW1lbnRzIGluLWxpbmUuDQoNCk9u
IFdlZCwgRmViIDIyLCAyMDE3IGF0IDExOjIxIFBNLCA8bW9oYW1lZC5ib3VjYWRhaXJAb3Jhbmdl
LmNvbTxtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4+IHdyb3RlOg0KSGkgVGVk
LA0KDQpUaGFuayB5b3UgZm9yIHRoZSByZXBseSBhbmQgZm9yIGltcGxlbWVudGluZyB0aGVzZSBj
aGFuZ2VzLg0KDQpJIGNoZWNrZWQgdGhlIGRpZmYsIGJ1dCBJ4oCZbSBhZnJhaWQgdGhlIC0wNiB2
ZXJzaW9uIGhhcyB0aGUgc2FtZSBpc3N1ZXMgYXMgdGhlIG9uZXMgSSByZXBvcnRlZCBpbiBKYW51
YXJ5IDMxLg0KDQoNCkkgZGlkIHJlc3BvbmQgdG8gdGhlIHBhcnRpY3VsYXIgY29tbWVudHMgYW5k
IHRleHQgcHJvcG9zYWxzLCBzbyBJIGFzc3VtZSB0aGlzIGlzIHRoZSBtb3JlIGdlbmVyYWwgaXNz
dWUuICBJZiBJIHVuZGVyc3RhbmQgY29ycmVjdGx5LCB5b3Ugd291bGQgcHJlZmVyIHRoaXMgZG9j
dW1lbnQgdG8gYmUgc3RydWN0dXJlZCBhcyBhIHJldmlzaW9uIHRvIHRoZSB0aHJlYXQgbW9kZWwg
ZG9jdW1lbnQgb3IgY29ubmVjdGVkIHRvIGEgbGFyZ2VyIGNvbnNpZGVyYXRpb24gb2YgdGhlIGlz
c3Vlcy4gIEkgdW5kZXJzdGFuZCB0aGF0LCBhbmQgaXQgd2FzIGNvbnNpZGVyZWQsIGJ1dCBJIGJl
bGlldmUgdGhhdCB0aGlzIGZvcm1hdCBpcyBzdGlsbCB0aGUgbW9zdCBlZmZlY3RpdmUgZm9yIHRo
ZSBuYXJyb3cgaXNzdWUgaXQgYWRkcmVzc2VzLg0KW01lZF0gVGhhdCB3YXMgb25lIG9mIG15IGNv
bmNlcm5zOyBub3QgdGhlIG9ubHkgb25lLiBJbiBQYXJ0aWN1bGFyLCBJ4oCZbSB0cnlpbmcgdG8g
dW5kZXJzdGFuZCBob3cgdGhpcyBkb2N1bWVudCB3aWxsIGJlIHVzZWQgaW4gdGhlIGZ1dHVyZSB0
byBiZXR0ZXIgc3RyZW5ndGhlbiBmb3J0aGNvbWluZyBzcGVjaWZpY2F0aW9ucy4gRnVydGhlciwg
dGhlIGV4cGVyaWVuY2UgSSBoYWQgd2hlbiBhZHZhbmNpbmcgc29tZSBSRkNzIGlzIHRoYXQgUkZD
NzI1OCB3b3JkaW5nIGNhbiBiZSBmdXJ0aGVyIGVuaGFuY2VkIHRvIHByb3ZpZGUgY2xlYXIgZ3Vp
ZGFuY2UuIEFsc28sIGNvbnNpZGVyYXRpb25zIHN1Y2ggYXMgdGhlIGZvbGxvd2luZyBhcmUgbWlz
c2luZyBmcm9tIHRoZSBkb2N1bWVudDoNCiogdGhhdCBkYXRhIG1heSBub3QgYmUgYWx3YXlzIGF2
YWlsYWJsZSB0byB0aGUgZW5kaG9zdA0KKiBhIG1pc2JlaGF2aW5nIG5vZGUgbWF5IGJlIHRlbXB0
ZWQgdG8gc3Bvb2YgdGhlIGRhdGEgdG8gYmUgaW5qZWN0ZWQuIEEgcmVtb3RlIGRldmljZSB0aGF0
IHdpbGwgdXNlIHRoYXQgZGF0YSB0byBlbmZvcmNlIHBvbGljaWVzIHdpbGwgYmUgYnJva2VuLg0K
KiBpdCB3YXMgcmVwb3J0ZWQgaW4gdGhlIHBhc3QgdGhhdCBzb21lIGJyb3dzZXJzIGxlYWsgdGhl
IE1TSVNETiBhbmQgb3RoZXIgc2Vuc2l0aXZlIGRhdGEuDQpGcm9tIHRoYXQgZmxvdyBzb21lIG9m
IHlvdXIgb3RoZXIgY29uY2VybnMgYWJvdXQgYXVkaWVuY2UsIGF0IGxlYXN0IGFzIEkgdW5kZXJz
dGFuZC4gIEFzIHdyaXR0ZW4sIHRoaXMgaXMgbmFycm93IGFkdmljZSBmb3IgYSBicm9hZCBhdWRp
ZW5jZTogYmFzaWNhbGx5LCBhbnlvbmUgd2hvIHdvdWxkIGNvbnNpZGVyIHRoZSBmb3JtIG9mIG1l
dGFkYXRhIGluc2VydGlvbiBpdCBkZXNjcmliZXMuICBZb3Ugd291bGQsIGlmIEkgdW5kZXJzdGFu
ZCB5b3UsIHByZWZlciBhIG5hcnJvd2VyIGRlc2NyaXB0aW9uIG9mIHRoZSBhdWRpZW5jZSBpbiBh
IGxhcmdlciBjb250ZXh0Lg0KDQpbTWVkXSBUaGUga2V5IHBvaW50IGhlcmUgaXMgYWJvdXQgdGhl
IHByYWN0aWNhbGl0eSBvZiBpbXBsZW1lbnRpbmcgdGhlIGFkdmljZSBOT1QgY2hhbmdpbmcgdGhl
IHNjb3BlLiBGb3IgZXhhbXBsZSwgdGhlIGRvY3VtZW50IHNheXMgdGhhdCBpdCBpcyBiZXR0ZXIg
dGhhdCBhIGhvc3QgaXMgaW5qZWN0aW5nIHRoZSBkYXRhIGJ1dCB0aGUgZG9jdW1lbnQgZG9lcyBu
b3QgcXVlc3Rpb24gd2hldGhlciB0aGF0IHN1cHBsaWVkIGRhdGEgY2FuIGJlIHRydXN0ZWQgb3Ig
bm90LCBvciBob3cgdGhlIGNvbnNlbnQgd2lsbCBiZSBvYnRhaW5lZCBmcm9tIGEgdXNlci4gRm9y
IGV4YW1wbGUsIHRoZSBkb2N1bWVudCBzdGF0ZXMgdGhhdCB0aGUgaW5mb3JtYXRpb24gaW4gYSBG
b3J3YXJkLUZvciBoZWFkZXIgY2FuIGJlIHN1cHBsaWVkIGJ5IHRoZSBob3N0IGl0c2VsZiBhbmQg
dGhlbiBjb21tdW5pY2F0ZWQgdG8gYSByZW1vdGUgY29uc3VtZXIuIFRoaXMgaXMgaW5kZWVkIHBv
c3NpYmxlLCBidXQgYmVjYXVzZSBvZiBhYnVzaW5nIGhvc3RzIHNvbWUgc2VydmVycyBpbXBsZW1l
bnQgd2hpdGVsaXN0cyB0byB0cnVzdCBwcm94aWVzOyBzZWUgaHR0cHM6Ly9tZXRhLndpa2ltZWRp
YS5vcmcvdy9leHRlbnNpb25zL1RydXN0ZWRYRkYvdHJ1c3RlZC1ob3N0cy50eHQuDQoNCknigJlt
IHJlaXRlcmF0aW5nIHRoYXQgbW9zdCBvZiBteSBjb21tZW50cyBhcmUgc3RpbGwgdW5hZGRyZXNz
ZWQgaW4gLTA2Lg0KDQoNCkkgcmVhbGl6ZSB0aGF0IHRoZSBkb2N1bWVudCBkaWQgbm90IGNoYW5n
ZSB0byBhZGRyZXNzIHRoZSBhdWRpZW5jZSBvciBkb2N1bWVudCBpbnRlZ3JhdGlvbiB5b3UgcHJl
ZmVycmVkOyBJIHRoaW5rIHRoZXJlIHdlIHNpbXBseSBkaXNhZ3JlZSBvbiBob3cgdG8gbWFrZSB0
aGlzIGFkdmljZSBlZmZlY3RpdmUuICBJJ20gc29ycnkgdGhhdCBmaXJzdCBtZXNzYWdlIGFwcGFy
ZW50bHkgZGlkIG5vdCBkZXNjcmliZSB0aGUgZGlzYWdyZWVtZW50IGVmZmVjdGl2ZWx5Lg0KSWYg
SSBoYXZlIG1pc3VuZGVyc3Rvb2QgeW91ciBjb21tZW50cywgcGxlYXNlIGFjY2VwdCBteSBhcG9s
b2dpZXMuIEkgd291bGQgYmUgaGFwcHkgb2YgZnVydGhlciBjbGFyaWZpY2F0aW9uIGFuZCBzdWdn
ZXN0ZWQgdGV4dCB0byBpbGx1c3RyYXRlIHlvdXIgcHJlZmVyZW5jZXMgd291bGQgYmUgZXNwZWNp
YWxseSB3ZWxjb21lLg0KW01lZF0gU3VyZS4gQmVmb3JlIHRoYXQsIGNhbiB5b3UgcGxlYXNlIGNv
bnNpZGVyIHJlY2hlY2tpbmcgdGhlIGRldGFpbGVkIGxpc3Qgb2YgY29tbWVudHMgYXZhaWxhYmxl
IGF0OiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL2lldGYvY3VycmVudC9t
c2cxMDE2MjkuaHRtbC4gVGhhbmsgeW91Lg0KDQp0aGFua3MsDQpUZWQgSGFyZGllDQoNCg0KQ2hl
ZXJzLA0KTWVkDQoNCkRlIDogVGVkIEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvPG1h
aWx0bzp0ZWQuaWV0ZkBnbWFpbC5jbz5tXQ0KRW52b3nDqSA6IG1lcmNyZWRpIDIyIGbDqXZyaWVy
IDIwMTcgMjM6MDkNCsOAIDogQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTg0KQ2MgOiBpZXRmQGll
dGYub3JnPG1haWx0bzppZXRmQGlldGYub3JnPjsgZHJhZnQtaGFyZGllLXByaXZzZWMtbWV0YWRh
dGEtaW5zZXJ0aW9uQGlldGYub3JnPG1haWx0bzpkcmFmdC1oYXJkaWUtcHJpdnNlYy1tZXRhZGF0
YS1pbnNlcnRpb25AaWV0Zi5vcmc+DQpPYmpldCA6IFJlOiBMYXN0IENhbGw6IDxkcmFmdC1oYXJk
aWUtcHJpdnNlYy1tZXRhZGF0YS1pbnNlcnRpb24tMDUudHh0PiAoRGVzaWduIGNvbnNpZGVyYXRp
b25zIGZvciBNZXRhZGF0YSBJbnNlcnRpb24pIHRvIEluZm9ybWF0aW9uYWwgUkZDDQoNCkhpIE1v
aGFtZWQsDQpUaGFua3MgZm9yIHlvdXIgcmV2aWV3LiAgSSd2ZSB1cGxvYWRlZCBhIGRyYWZ0IC0w
NiB3aXRoIHVwZGF0ZXMgZnJvbSB5b3VyIGFuZCBvdGhlciByZXZpZXdzLiAgU29tZSBub3RlcyBp
bi1saW5lLg0KDQpPbiBUdWUsIEphbiAzMSwgMjAxNyBhdCAxOjQ5IEFNLCA8bW9oYW1lZC5ib3Vj
YWRhaXJAb3JhbmdlLmNvbTxtYWlsdG86bW9oYW1lZC5ib3VjYWRhaXJAb3JhbmdlLmNvbT4+IHdy
b3RlOg0KRGVhciBUZWQsDQoNClBsZWFzZSBmaW5kIGJlbG93IG15IGdlbmVyYWwgcmV2aWV3IG9m
IHRoZSBkb2N1bWVudCBhbmQgYWxzbyBteSBkZXRhaWxlZCBjb21tZW50cy4NCg0KKiBPdmVyYWxs
Og0KLSBJIGRvbid0IHRoaW5rIHRoZSBkb2N1bWVudCBpcyByZWFkeSB0byBiZSBwdWJsaXNoZWQg
YXMgaXQgaXMuIEl0IGRvZXMgbm90IGRpc2N1c3MgdGhlIHVzYWJpbGl0eSBhbmQgaW1wbGljYXRp
b25zIG9mIHRoZSBhZHZpY2UuIEZ1cnRoZXIsIGl0IG1heSBiZSBpbnRlcnByZXRlZCB0aGF0IGEg
Y2xpZW50L2VuZCBzeXN0ZW0vdXNlciBjYW4gYWx3YXlzIGJ5IGl0c2VsZiBwb3B1bGF0ZSBkYXRh
IHRoYXQgaXMgc3VwcGxpZWQgYnkgb24tcGF0aCBub2RlcyAoaW4gY3VycmVudCBkZXBsb3ltZW50
cykuIFRoYXQncyBhc3N1bXB0aW9uIGlzIG5vdCB0cnVlIGZvciBzb21lIHByb3RvY29scy4NCi0g
VGhlIHB1cnBvc2Ugb2YgcHVibGlzaGluZyB0aGlzIGFkdmljZSBpcyBub3QgY2xlYXIuIEZvciBl
eGFtcGxlLCBob3cgdGhpcyBhZHZpY2Ugd2lsbCBiZSBpbXBsZW1lbnRlZCBpbiBwcmFjdGljZT8g
V2hhdCBpcyBpdHMgc2NvcGU/DQotIEkgd291bGQgcGVyc29uYWxseSBwcmVmZXIgYW4gdXBkYXRl
ZCB2ZXJzaW9uIG9mIFJGQzcyNTggd2l0aCBtb3JlIHN0cmljdCBsYW5ndWFnZSBvbiB0aGUgcHJp
dmFjeS1yZWxhdGVkIGNvbnNpZGVyYXRpb25zLiBUaGlzIGlzIG1vcmUgYWN0aW9uYWJsZSB3aXRo
IGNvbmNyZXRlIGVmZmVjdHMgaW4gZG9jdW1lbnRzIHRoYXQgd2lsbCByZXF1aXJlZCB0byBpbmNs
dWRlIGEgZGlzY3Vzc2lvbiBvbiBwcml2YWN5IHJlbGF0ZWQgbWF0dGVycy4NCg0KRGV0YWlsZWQg
Y29tbWVudHMgYXJlIHByb3ZpZGVkIGJlbG93Og0KDQoqIFRoZSBhYnN0cmFjdCBzYXlzIHRoZSBm
b2xsb3dpbmc6DQoNCiAgIFRoZSBJQUIgaGFzIHB1Ymxpc2hlZCBbUkZDNzYyNF0gaW4gcmVzcG9u
c2UgdG8gc2V2ZXJhbCByZXZlbGF0aW9ucyBvZg0KICAgcGVydmFzaXZlIGF0dGFjayBvbiBJbnRl
cm5ldCBjb21tdW5pY2F0aW9ucy4gIFRoaXMgZG9jdW1lbnQgY29uc2lkZXJzDQogICB0aGUgaW1w
bGljYXRpb25zIG9mIHByb3RvY29sIGRlc2lnbnMgd2hpY2ggYXNzb2NpYXRlIG1ldGFkYXRhIHdp
dGgNCiAgIGVuY3J5cHRlZCBmbG93cy4gIEluIHBhcnRpY3VsYXIsIGl0IGFzc2VydHMgdGhhdCBk
ZXNpZ25zIHdoaWNoIGRvIHNvDQogICBieSBleHBsaWNpdCBhY3Rpb25zIG9mIHRoZSBlbmQgc3lz
dGVtIGFyZSBwcmVmZXJhYmxlIHRvIGRlc2lnbnMgaW4NCiAgICAgIF5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5eXl5eXl5eXl4NCiAgIHdoaWNoIG1pZGRsZWJveGVzIGluc2VydCB0aGVtLg0KDQpJ
IHN1Z2dlc3QgeW91IGV4cGxpY2l0IHdoYXQgaXMgbWVhbnQgYnkgInRoZSBlbmQgc3lzdGVtIi4N
Cg0KSSBoYXZlIHVwZGF0ZWQgdGhpcyB0byBjbGFyaWZ5IHRoYXQgdGhpcyBpcyB0aGUgaG9zdC9l
bmQgc3lzdGVtIG5vdCB0aGUgdXNlci4NCg0KSWYgeW91IG1lYW4gdGhlIG93bmVyL3VzZXIsIHRo
ZW4gdGhlIHRleHQgc2hvdWxkIHNheSBzby4gSWYgeW91IG1lYW4gYSBjbGllbnQgc29mdHdhcmUg
aW5zdGFuY2UsIHRoZW4gYnVncy9pbmFwcHJvcHJpYXRlIGRlZmF1bHQgdmFsdWVzIG1heSBsZWFk
IHRvIChwcml2YWN5IGxlYWspIHN1cnByaXNlcyB0b28uIEl0IHdhcyByZXBvcnRlZCBpbiB0aGUg
cGFzdCB0aGF0IHNvbWUgYnJvd3NlcnMgaW5qZWN0IHRoZSBNU0lTRE4gdG9vLg0KDQoqIEludHJv
ZHVjdGlvbjogIlRvIGVuc3VyZSB0aGF0IHRoZSBJbnRlcm5ldCBjYW4gYmUgdHJ1c3RlZCBieSB1
c2VycyINCg0KUmF0aGVyIMKrIFRvIG1pbmltaXplIHRoZSByaXNrIG9mIEludGVybmV0LW9yaWdp
bmF0ZWQgYXR0YWNrcyB0YXJnZXRlZCBhdCB1c2VycyDCuy4NCg0KSSd2ZSBhZG9wdGVkIHRoaXMg
bGFuZ3VhZ2UuDQoNCkl0J3MgcmVhc29uYWJsZSB0byBjbGFpbSB0aGUgSW50ZXJuZXQgY2FuIGJl
IHRydXN0ZWQgYnkgdXNlcnM7IHNlZSBob3cgdGhlIHVzYWdlIG9mIHNvY2lhbCBuZXR3b3JrcyBo
YXMgYmVjb21lIHNldmVyZWx5IHR3aXN0ZWQgZm9yIGV4YW1wbGUNCg0KSSd2ZSBhbHNvIGNvbnNp
ZGVyZWQgeW91ciBwb2ludCB0aGF0IGFuIHVwZGF0ZWQgdmVyc2lvbiBvZiBSRkM3MjU4IG1pZ2h0
IGJlIGEgYmV0dGVyIG91dGxldCBmb3IgYWR2aWNlIGxpa2UgdGhpcy4gV2UgZGlkIGNvbnNpZGVy
IHNldmVyYWwgYXBwcm9hY2hlcywgaW5jbHVkaW5nIGluY29ycG9yYXRpbmcgdGhlIHRleHQgaW4g
YW4gdXBkYXRlIHRvICBSRkMgMzU1MiBvciBhcyBwYXJ0IG9mIGEgZG9jdW1lbnQgZGVzY3JpYmlu
ZyB0aGUgZnVsbCBzZXQgb2YgY29tcGFuaW9uIG1pdGlnYXRpb25zIHRvIHRoZSB0aHJlYXRzIGlu
IFJGQyA3NjI0IChkcmFmdC1pYWItcHJpdnNlYy1jb25maWRlbnRpYWxpdHktbWl0aWdhdGlvbnMg
d291bGQgYmUgb25lIGFwcHJvYWNoKS4gIFRob3NlIGFyZSBhbGwgdmFsaWQgYXBwcm9hY2hlcywg
YnV0IGl0IHNlZW1lZCB0aGF0IHNob3J0LCBlYXNpbHkgcmVhZCBkb2N1bWVudHMgdGFja2xpbmcg
YSBzaW5nbGUgcG9pbnQgbWlnaHQgYmUgZWFzaWVyIHRvIHByb2R1Y2UgYW5kIGNvbnN1bWUuDQpU
aGFua3MgYWdhaW4gZm9yIHlvdXIgcmV2aWV3LA0KVGVkIEhhcmRpZQ0KDQoNCg==

--_000_787AE7BB302AE849A7480A190F8B933009E183CFOPEXCLILMA3corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29BY2V0YXRlLCBsaS5Nc29BY2V0
YXRlLCBkaXYuTXNvQWNldGF0ZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxl
LWxpbms6IlRleHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRv
bTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4LjBwdDsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fu
cy1zZXJpZiI7fQ0Kc3Bhbi5tLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0NCgl7bXNvLXN0eWxl
LW5hbWU6bV8tMjc0NjU5ODgwNDQ4NDk0MzE4NWdtYWlsLTt9DQpzcGFuLlRleHRlZGVidWxsZXND
YXINCgl7bXNvLXN0eWxlLW5hbWU6IlRleHRlIGRlIGJ1bGxlcyBDYXIiOw0KCW1zby1zdHlsZS1w
cmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiVGV4dGUgZGUgYnVsbGVzIjsNCglmb250LWZh
bWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RlI7fQ0K
c3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9u
dC1mYW1pbHk6IkNvdXJpZXIgTmV3IjsNCgljb2xvcjpibGFjazsNCglmb250LXdlaWdodDpub3Jt
YWw7DQoJZm9udC1zdHlsZTpub3JtYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCglt
c28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2
MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcwLjg1cHQgNzAuODVwdCA3MC44NXB0IDcwLjg1cHQ7
fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwh
LS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3Bp
ZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1s
Pg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRh
dGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8
Ym9keSBsYW5nPSJGUiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2si
PkhpIFRlZCwNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+UGxlYXNlIHNlZSBpbmxpbmUuDQo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmll
ciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkNoZWVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZh
bWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+TWVkPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzowY20gMGNtIDBjbSA0LjBwdCI+DQo8ZGl2
Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0
O3BhZGRpbmc6My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkRlJm5ic3A7Ojwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDsiPiBUZWQgSGFyZGllIFttYWlsdG86dGVkLmlldGZAZ21haWwuY29tXQ0K
PGJyPg0KPGI+RW52b3nDqSZuYnNwOzo8L2I+IHZlbmRyZWRpIDI0IGbDqXZyaWVyIDIwMTcgMDA6
NDA8YnI+DQo8Yj7DgCZuYnNwOzo8L2I+IEJPVUNBREFJUiBNb2hhbWVkIElNVC9PTE48YnI+DQo8
Yj5DYyZuYnNwOzo8L2I+IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFk
YXRhLWluc2VydGlvbkBpZXRmLm9yZzxicj4NCjxiPk9iamV0Jm5ic3A7OjwvYj4gUmU6IExhc3Qg
Q2FsbDogJmx0O2RyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFkYXRhLWluc2VydGlvbi0wNS50eHQm
Z3Q7IChEZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9yIE1ldGFkYXRhIEluc2VydGlvbikgdG8gSW5m
b3JtYXRpb25hbCBSRkM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+SEkgTW9oYW1hZCw8YnI+DQo8YnI+DQpUaGFua3MgZm9yIHJlY2hlY2tpbmc7
IHNvbWUgZnVydGhlciBjb21tZW50cyBpbi1saW5lLjxicj4NCjxicj4NCk9uIFdlZCwgRmViIDIy
LCAyMDE3IGF0IDExOjIxIFBNLCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1vaGFtZWQuYm91Y2FkYWly
QG9yYW5nZS5jb20iIHRhcmdldD0iX2JsYW5rIj5tb2hhbWVkLmJvdWNhZGFpckBvcmFuZ2UuY29t
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+
DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7O2NvbG9yOmJsYWNrIj5IaSBUZWQsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5UaGFuayB5b3UgZm9yIHRoZSByZXBseSBhbmQgZm9yIGlt
cGxlbWVudGluZyB0aGVzZSBjaGFuZ2VzLg0KPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNw
Ozwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJp
ZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5JIGNoZWNrZWQgdGhlIGRpZmYsIGJ1dCBJ4oCZbSBh
ZnJhaWQgdGhlIC0wNiB2ZXJzaW9uIGhhcyB0aGUgc2FtZSBpc3N1ZXMgYXMgdGhlIG9uZXMgSSBy
ZXBvcnRlZCBpbg0KIEphbnVhcnkgMzEuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkkg
ZGlkIHJlc3BvbmQgdG8gdGhlIHBhcnRpY3VsYXIgY29tbWVudHMgYW5kIHRleHQgcHJvcG9zYWxz
LCBzbyBJIGFzc3VtZSB0aGlzIGlzIHRoZSBtb3JlIGdlbmVyYWwgaXNzdWUuJm5ic3A7IElmIEkg
dW5kZXJzdGFuZCBjb3JyZWN0bHksIHlvdSB3b3VsZCBwcmVmZXIgdGhpcyBkb2N1bWVudCB0byBi
ZSBzdHJ1Y3R1cmVkIGFzIGEgcmV2aXNpb24gdG8gdGhlIHRocmVhdA0KIG1vZGVsIGRvY3VtZW50
IG9yIGNvbm5lY3RlZCB0byBhIGxhcmdlciBjb25zaWRlcmF0aW9uIG9mIHRoZSBpc3N1ZXMuJm5i
c3A7IEkgdW5kZXJzdGFuZCB0aGF0LCBhbmQgaXQgd2FzIGNvbnNpZGVyZWQsIGJ1dCBJIGJlbGll
dmUgdGhhdCB0aGlzIGZvcm1hdCBpcyBzdGlsbCB0aGUgbW9zdCBlZmZlY3RpdmUgZm9yIHRoZSBu
YXJyb3cgaXNzdWUgaXQgYWRkcmVzc2VzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7
Y29sb3I6YmxhY2siPltNZWRdIFRoYXQgd2FzIG9uZSBvZiBteSBjb25jZXJuczsgbm90IHRoZSBv
bmx5IG9uZS4gSW4gUGFydGljdWxhciwgSeKAmW0gdHJ5aW5nIHRvIHVuZGVyc3RhbmQgaG93IHRo
aXMgZG9jdW1lbnQgd2lsbCBiZSB1c2VkIGluDQogdGhlIGZ1dHVyZSB0byBiZXR0ZXIgc3RyZW5n
dGhlbiBmb3J0aGNvbWluZyBzcGVjaWZpY2F0aW9ucy4gRnVydGhlciwgdGhlIGV4cGVyaWVuY2Ug
SSBoYWQgd2hlbiBhZHZhbmNpbmcgc29tZSBSRkNzIGlzIHRoYXQgUkZDNzI1OCB3b3JkaW5nIGNh
biBiZSBmdXJ0aGVyIGVuaGFuY2VkIHRvIHByb3ZpZGUgY2xlYXIgZ3VpZGFuY2UuIEFsc28sIGNv
bnNpZGVyYXRpb25zIHN1Y2ggYXMgdGhlIGZvbGxvd2luZyBhcmUgbWlzc2luZyBmcm9tIHRoZSBk
b2N1bWVudDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1z
aXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFj
ayI+KiB0aGF0IGRhdGEgbWF5IG5vdCBiZSBhbHdheXMgYXZhaWxhYmxlIHRvIHRoZSBlbmRob3N0
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bi1ib3R0b206MTIuMHB0Ij48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPiogYSBt
aXNiZWhhdmluZyBub2RlIG1heSBiZSB0ZW1wdGVkIHRvIHNwb29mIHRoZSBkYXRhIHRvIGJlIGlu
amVjdGVkLiBBIHJlbW90ZSBkZXZpY2UgdGhhdCB3aWxsIHVzZSB0aGF0IGRhdGEgdG8gZW5mb3Jj
ZSBwb2xpY2llcw0KIHdpbGwgYmUgYnJva2VuLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIg
TmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj4qIGl0IHdhcyByZXBvcnRlZCBpbiB0aGUgcGFzdCB0aGF0
IHNvbWUgYnJvd3NlcnMgbGVhayB0aGUgTVNJU0ROIGFuZCBvdGhlciBzZW5zaXRpdmUgZGF0YS48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+RnJvbSB0aGF0IGZsb3cgc29tZSBvZiB5b3VyIG90aGVyIGNv
bmNlcm5zIGFib3V0IGF1ZGllbmNlLCBhdCBsZWFzdCBhcyBJIHVuZGVyc3RhbmQuJm5ic3A7IEFz
IHdyaXR0ZW48L3NwYW4+LCB0aGlzIGlzIG5hcnJvdyBhZHZpY2UgZm9yIGEgYnJvYWQgYXVkaWVu
Y2U6IGJhc2ljYWxseSwgYW55b25lIHdobyB3b3VsZCBjb25zaWRlciB0aGUgZm9ybSBvZiBtZXRh
ZGF0YSBpbnNlcnRpb24NCiBpdCBkZXNjcmliZXMuJm5ic3A7IFlvdSB3b3VsZCwgaWYgSSB1bmRl
cnN0YW5kIHlvdSwgcHJlZmVyIGEgbmFycm93ZXIgZGVzY3JpcHRpb24gb2YgdGhlIGF1ZGllbmNl
IGluIGEgbGFyZ2VyIGNvbnRleHQuJm5ic3A7DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMi
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1
b3Q7O2NvbG9yOmJsYWNrIj5bTWVkXSBUaGUga2V5IHBvaW50IGhlcmUgaXMgYWJvdXQgdGhlIHBy
YWN0aWNhbGl0eSBvZiBpbXBsZW1lbnRpbmcgdGhlIGFkdmljZSBOT1QgY2hhbmdpbmcgdGhlIHNj
b3BlLiBGb3IgZXhhbXBsZSwgdGhlIGRvY3VtZW50IHNheXMgdGhhdCBpdCBpcyBiZXR0ZXIgdGhh
dA0KIGEgaG9zdCBpcyBpbmplY3RpbmcgdGhlIGRhdGEgYnV0IHRoZSBkb2N1bWVudCBkb2VzIG5v
dCBxdWVzdGlvbiB3aGV0aGVyIHRoYXQgc3VwcGxpZWQgZGF0YSBjYW4gYmUgdHJ1c3RlZCBvciBu
b3QsIG9yIGhvdyB0aGUgY29uc2VudCB3aWxsIGJlIG9idGFpbmVkIGZyb20gYSB1c2VyLiBGb3Ig
ZXhhbXBsZSwgdGhlIGRvY3VtZW50IHN0YXRlcyB0aGF0IHRoZSBpbmZvcm1hdGlvbiBpbiBhIEZv
cndhcmQtRm9yIGhlYWRlciBjYW4gYmUgc3VwcGxpZWQNCiBieSB0aGUgaG9zdCBpdHNlbGYgYW5k
IHRoZW4gY29tbXVuaWNhdGVkIHRvIGEgcmVtb3RlIGNvbnN1bWVyLiBUaGlzIGlzIGluZGVlZCBw
b3NzaWJsZSwgYnV0IGJlY2F1c2Ugb2YgYWJ1c2luZyBob3N0cyBzb21lIHNlcnZlcnMgaW1wbGVt
ZW50IHdoaXRlbGlzdHMgdG8gdHJ1c3QgcHJveGllczsgc2VlDQo8YSBocmVmPSJodHRwczovL21l
dGEud2lraW1lZGlhLm9yZy93L2V4dGVuc2lvbnMvVHJ1c3RlZFhGRi90cnVzdGVkLWhvc3RzLnR4
dCI+aHR0cHM6Ly9tZXRhLndpa2ltZWRpYS5vcmcvdy9leHRlbnNpb25zL1RydXN0ZWRYRkYvdHJ1
c3RlZC1ob3N0cy50eHQ8L2E+LiAmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8Ymxv
Y2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBw
dDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdo
dDowY20iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+SeKAmW0gcmVpdGVyYXRpbmcgdGhhdCBtb3N0IG9mIG15
IGNvbW1lbnRzIGFyZSBzdGlsbCB1bmFkZHJlc3NlZCBpbiAtMDYuPC9zcGFuPjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZv
bnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6
YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Js
b2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJv
dHRvbToxMi4wcHQiPkkgcmVhbGl6ZSB0aGF0IHRoZSBkb2N1bWVudCBkaWQgbm90IGNoYW5nZSB0
byBhZGRyZXNzIHRoZSBhdWRpZW5jZSBvciBkb2N1bWVudCBpbnRlZ3JhdGlvbiB5b3UgcHJlZmVy
cmVkOyBJIHRoaW5rIHRoZXJlIHdlIHNpbXBseSBkaXNhZ3JlZSBvbiBob3cgdG8gbWFrZSB0aGlz
IGFkdmljZSBlZmZlY3RpdmUuJm5ic3A7IEknbSBzb3JyeSB0aGF0IGZpcnN0IG1lc3NhZ2UNCiBh
cHBhcmVudGx5IGRpZCBub3QgZGVzY3JpYmUgdGhlIGRpc2FncmVlbWVudCBlZmZlY3RpdmVseS48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SWYgSSBoYXZlIG1pc3VuZGVyc3Rvb2QgeW91ciBjb21t
ZW50cywgcGxlYXNlIGFjY2VwdCBteSBhcG9sb2dpZXMuIEkgd291bGQgYmUgaGFwcHkgb2YgZnVy
dGhlciBjbGFyaWZpY2F0aW9uIGFuZCBzdWdnZXN0ZWQgdGV4dCB0byBpbGx1c3RyYXRlIHlvdXIg
cHJlZmVyZW5jZXMgd291bGQgYmUgZXNwZWNpYWxseSB3ZWxjb21lLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291
cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPltNZWRdIFN1cmUuIEJlZm9yZSB0aGF0LCBjYW4g
eW91IHBsZWFzZSBjb25zaWRlciByZWNoZWNraW5nIHRoZSBkZXRhaWxlZCBsaXN0IG9mIGNvbW1l
bnRzIGF2YWlsYWJsZSBhdDoNCjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWwtYXJj
aGl2ZS93ZWIvaWV0Zi9jdXJyZW50L21zZzEwMTYyOS5odG1sIj5odHRwczovL3d3dy5pZXRmLm9y
Zy9tYWlsLWFyY2hpdmUvd2ViL2lldGYvY3VycmVudC9tc2cxMDE2MjkuaHRtbDwvYT4uIFRoYW5r
IHlvdS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNr
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij50aGFua3MsPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiPlRlZCBIYXJkaWU8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyI+PGJyPg0KJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtw
YWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDow
Y20iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIGxhbmc9IkVO
LVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+Q2hlZXJzLDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBO
ZXcmcXVvdDs7Y29sb3I6YmxhY2siPk1lZDwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDs7Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD48
L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29s
aWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPjxzcGFuIGxhbmc9
IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFo
b21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiBUZWQNCiBIYXJkaWUgW21haWx0bzo8
YSBocmVmPSJtYWlsdG86dGVkLmlldGZAZ21haWwuY28iIHRhcmdldD0iX2JsYW5rIj50ZWQuaWV0
ZkBnbWFpbC5jbzwvYT48L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPm1dDQo8YnI+
DQo8Yj5FbnZvecOpJm5ic3A7OjwvYj4gbWVyY3JlZGkgMjIgZsOpdnJpZXIgMjAxNyAyMzowOTxi
cj4NCjxiPsOAJm5ic3A7OjwvYj4gQk9VQ0FEQUlSIE1vaGFtZWQgSU1UL09MTjxicj4NCjxiPkNj
Jm5ic3A7OjwvYj4gPGEgaHJlZj0ibWFpbHRvOmlldGZAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5r
Ij5pZXRmQGlldGYub3JnPC9hPjsgPGEgaHJlZj0ibWFpbHRvOmRyYWZ0LWhhcmRpZS1wcml2c2Vj
LW1ldGFkYXRhLWluc2VydGlvbkBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0KZHJhZnQtaGFy
ZGllLXByaXZzZWMtbWV0YWRhdGEtaW5zZXJ0aW9uQGlldGYub3JnPC9hPjxicj4NCjxiPk9iamV0
Jm5ic3A7OjwvYj4gUmU6IExhc3QgQ2FsbDogJmx0O2RyYWZ0LWhhcmRpZS1wcml2c2VjLW1ldGFk
YXRhLWluc2VydGlvbi0wNS50eHQmZ3Q7IChEZXNpZ24gY29uc2lkZXJhdGlvbnMgZm9yIE1ldGFk
YXRhIEluc2VydGlvbikgdG8gSW5mb3JtYXRpb25hbCBSRkM8L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPkhpIE1v
aGFtZWQsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VGhh
bmtzIGZvciB5b3VyIHJldmlldy4mbmJzcDsgSSd2ZSB1cGxvYWRlZCBhIGRyYWZ0IC0wNiB3aXRo
IHVwZGF0ZXMgZnJvbSB5b3VyIGFuZCBvdGhlciByZXZpZXdzLiZuYnNwOyBTb21lIG5vdGVzIGlu
LWxpbmUuPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPk9uIFR1ZSwg
SmFuIDMxLCAyMDE3IGF0IDE6NDkgQU0sICZsdDs8YSBocmVmPSJtYWlsdG86bW9oYW1lZC5ib3Vj
YWRhaXJAb3JhbmdlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1vaGFtZWQuYm91Y2FkYWlyQG9yYW5n
ZS5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+RGVhciBUZWQsPGJyPg0KPGJyPg0KUGxlYXNlIGZpbmQgYmVsb3cgbXkgZ2VuZXJhbCByZXZp
ZXcgb2YgdGhlIGRvY3VtZW50IGFuZCBhbHNvIG15IGRldGFpbGVkIGNvbW1lbnRzLjxicj4NCjxi
cj4NCiogT3ZlcmFsbDo8YnI+DQotIEkgZG9uJ3QgdGhpbmsgdGhlIGRvY3VtZW50IGlzIHJlYWR5
IHRvIGJlIHB1Ymxpc2hlZCBhcyBpdCBpcy4gSXQgZG9lcyBub3QgZGlzY3VzcyB0aGUgdXNhYmls
aXR5IGFuZCBpbXBsaWNhdGlvbnMgb2YgdGhlIGFkdmljZS4gRnVydGhlciwgaXQgbWF5IGJlIGlu
dGVycHJldGVkIHRoYXQgYSBjbGllbnQvZW5kIHN5c3RlbS91c2VyIGNhbiBhbHdheXMgYnkgaXRz
ZWxmIHBvcHVsYXRlIGRhdGEgdGhhdCBpcyBzdXBwbGllZCBieSBvbi1wYXRoIG5vZGVzDQogKGlu
IGN1cnJlbnQgZGVwbG95bWVudHMpLiBUaGF0J3MgYXNzdW1wdGlvbiBpcyBub3QgdHJ1ZSBmb3Ig
c29tZSBwcm90b2NvbHMuPGJyPg0KLSBUaGUgcHVycG9zZSBvZiBwdWJsaXNoaW5nIHRoaXMgYWR2
aWNlIGlzIG5vdCBjbGVhci4gRm9yIGV4YW1wbGUsIGhvdyB0aGlzIGFkdmljZSB3aWxsIGJlIGlt
cGxlbWVudGVkIGluIHByYWN0aWNlPyBXaGF0IGlzIGl0cyBzY29wZT88YnI+DQotIEkgd291bGQg
cGVyc29uYWxseSBwcmVmZXIgYW4gdXBkYXRlZCB2ZXJzaW9uIG9mIFJGQzcyNTggd2l0aCBtb3Jl
IHN0cmljdCBsYW5ndWFnZSBvbiB0aGUgcHJpdmFjeS1yZWxhdGVkIGNvbnNpZGVyYXRpb25zLiBU
aGlzIGlzIG1vcmUgYWN0aW9uYWJsZSB3aXRoIGNvbmNyZXRlIGVmZmVjdHMgaW4gZG9jdW1lbnRz
IHRoYXQgd2lsbCByZXF1aXJlZCB0byBpbmNsdWRlIGEgZGlzY3Vzc2lvbiBvbiBwcml2YWN5IHJl
bGF0ZWQgbWF0dGVycy48YnI+DQo8YnI+DQpEZXRhaWxlZCBjb21tZW50cyBhcmUgcHJvdmlkZWQg
YmVsb3c6PGJyPg0KPGJyPg0KKiBUaGUgYWJzdHJhY3Qgc2F5cyB0aGUgZm9sbG93aW5nOjxicj4N
Cjxicj4NCjxzcGFuIGNsYXNzPSJtLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0iPiZuYnNwOyAm
bmJzcDtUaGUgSUFCIGhhcyBwdWJsaXNoZWQgW1JGQzc2MjRdIGluIHJlc3BvbnNlIHRvIHNldmVy
YWwgcmV2ZWxhdGlvbnMgb2Y8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9Im0tMjc0NjU5ODgwNDQ4
NDk0MzE4NWdtYWlsLSI+Jm5ic3A7ICZuYnNwO3BlcnZhc2l2ZSBhdHRhY2sgb24gSW50ZXJuZXQg
Y29tbXVuaWNhdGlvbnMuJm5ic3A7IFRoaXMgZG9jdW1lbnQgY29uc2lkZXJzPC9zcGFuPjxicj4N
CjxzcGFuIGNsYXNzPSJtLTI3NDY1OTg4MDQ0ODQ5NDMxODVnbWFpbC0iPiZuYnNwOyAmbmJzcDt0
aGUgaW1wbGljYXRpb25zIG9mIHByb3RvY29sIGRlc2lnbnMgd2hpY2ggYXNzb2NpYXRlIG1ldGFk
YXRhIHdpdGg8L3NwYW4+PGJyPg0KPHNwYW4gY2xhc3M9Im0tMjc0NjU5ODgwNDQ4NDk0MzE4NWdt
YWlsLSI+Jm5ic3A7ICZuYnNwO2VuY3J5cHRlZCBmbG93cy4mbmJzcDsgSW4gcGFydGljdWxhciwg
aXQgYXNzZXJ0cyB0aGF0IGRlc2lnbnMgd2hpY2ggZG8gc288L3NwYW4+PGJyPg0KPHNwYW4gY2xh
c3M9Im0tMjc0NjU5ODgwNDQ4NDk0MzE4NWdtYWlsLSI+Jm5ic3A7ICZuYnNwO2J5IGV4cGxpY2l0
IGFjdGlvbnMgb2YgdGhlIGVuZCBzeXN0ZW0gYXJlIHByZWZlcmFibGUgdG8gZGVzaWducyBpbjwv
c3Bhbj48YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl5e
Xl5eXl5eXl5ePGJyPg0KJm5ic3A7ICZuYnNwO3doaWNoIG1pZGRsZWJveGVzIGluc2VydCB0aGVt
Ljxicj4NCjxicj4NCkkgc3VnZ2VzdCB5b3UgZXhwbGljaXQgd2hhdCBpcyBtZWFudCBieSAmcXVv
dDt0aGUgZW5kIHN5c3RlbSZxdW90Oy4gPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+SSBoYXZlIHVwZGF0ZWQgdGhpcyB0byBjbGFyaWZ5IHRoYXQgdGhp
cyBpcyB0aGUgaG9zdC9lbmQgc3lzdGVtIG5vdCB0aGUgdXNlci4mbmJzcDsNCjxicj4NCiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SWYgeW91IG1lYW4gdGhl
IG93bmVyL3VzZXIsIHRoZW4gdGhlIHRleHQgc2hvdWxkIHNheSBzby4gSWYgeW91IG1lYW4gYSBj
bGllbnQgc29mdHdhcmUgaW5zdGFuY2UsIHRoZW4gYnVncy9pbmFwcHJvcHJpYXRlIGRlZmF1bHQg
dmFsdWVzIG1heSBsZWFkIHRvIChwcml2YWN5IGxlYWspIHN1cnByaXNlcyB0b28uDQogSXQgd2Fz
IHJlcG9ydGVkIGluIHRoZSBwYXN0IHRoYXQgc29tZSBicm93c2VycyBpbmplY3QgdGhlIE1TSVNE
TiB0b28uPGJyPg0KPGJyPg0KKiBJbnRyb2R1Y3Rpb246ICZxdW90O1RvIGVuc3VyZSB0aGF0IHRo
ZSBJbnRlcm5ldCBjYW4gYmUgdHJ1c3RlZCBieSB1c2VycyZxdW90Ozxicj4NCjxicj4NClJhdGhl
ciDCqyBUbyBtaW5pbWl6ZSB0aGUgcmlzayBvZiBJbnRlcm5ldC1vcmlnaW5hdGVkIGF0dGFja3Mg
dGFyZ2V0ZWQgYXQgdXNlcnMgwrsuDQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JJ3ZlIGFkb3B0ZWQgdGhpcyBsYW5ndWFn
ZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBjbSAwY20g
Ni4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGNt
O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JdCdzIHJlYXNv
bmFibGUgdG8gY2xhaW0gdGhlIEludGVybmV0IGNhbiBiZSB0cnVzdGVkIGJ5IHVzZXJzOyBzZWUg
aG93IHRoZSB1c2FnZSBvZiBzb2NpYWwgbmV0d29ya3MgaGFzIGJlY29tZSBzZXZlcmVseSB0d2lz
dGVkIGZvciBleGFtcGxlPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bWFy
Z2luLWJvdHRvbToxMi4wcHQiPkkndmUgYWxzbyBjb25zaWRlcmVkIHlvdXIgcG9pbnQgdGhhdCBh
biB1cGRhdGVkIHZlcnNpb24gb2YgUkZDNzI1OCBtaWdodCBiZSBhIGJldHRlciBvdXRsZXQgZm9y
IGFkdmljZSBsaWtlIHRoaXMuIFdlIGRpZCBjb25zaWRlciBzZXZlcmFsIGFwcHJvYWNoZXMsIGlu
Y2x1ZGluZyBpbmNvcnBvcmF0aW5nIHRoZSB0ZXh0DQogaW4gYW4gdXBkYXRlIHRvJm5ic3A7IFJG
QyAzNTUyIG9yIGFzIHBhcnQgb2YgYSBkb2N1bWVudCBkZXNjcmliaW5nIHRoZSBmdWxsIHNldCBv
ZiBjb21wYW5pb24gbWl0aWdhdGlvbnMgdG8gdGhlIHRocmVhdHMgaW4gUkZDIDc2MjQgKGRyYWZ0
LWlhYi1wcml2c2VjLWNvbmZpZGVudGlhbGl0eS1taXRpZ2F0aW9ucyB3b3VsZCBiZSBvbmUgYXBw
cm9hY2gpLiZuYnNwOyBUaG9zZSBhcmUgYWxsIHZhbGlkIGFwcHJvYWNoZXMsIGJ1dCBpdCBzZWVt
ZWQgdGhhdCBzaG9ydCwNCiBlYXNpbHkgcmVhZCBkb2N1bWVudHMgdGFja2xpbmcgYSBzaW5nbGUg
cG9pbnQgbWlnaHQgYmUgZWFzaWVyIHRvIHByb2R1Y2UgYW5kIGNvbnN1bWUuJm5ic3A7DQo8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+VGhhbmtzIGFnYWlu
IGZvciB5b3VyIHJldmlldyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+VGVkIEhhcmRpZTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_787AE7BB302AE849A7480A190F8B933009E183CFOPEXCLILMA3corp_--


From nobody Fri Feb 24 01:04:59 2017
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBAFA12962F for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 01:04:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 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_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0Z2vQB2RFQw for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 01:04:52 -0800 (PST)
Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002:c09::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 DC1D91293F8 for <ietf@ietf.org>; Fri, 24 Feb 2017 01:04:51 -0800 (PST)
Received: by mail-yb0-x229.google.com with SMTP id n76so3898783ybg.3 for <ietf@ietf.org>; Fri, 24 Feb 2017 01:04:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=quwmVS0HgN0VlF0M5EAcmLxVQ4XGDvzkpXE+pUK+Yew=; b=wA3XZXEzM8czzMbGjqsFIPgH5RoiJPtTCUhweRZwAqyknGbXunQDDokenK7tyhEbhl 811bxorudcw/AeMmRXi/FJcp06qCPwbBp/tKmfRJv0o3Qw4SHZGmqjFZN93pb6r37SHH iAhfFMYD0mF+43Pnv+OQdUJcPljLnSxRYNRVwaIj78Dpj7Xn+YH9anRdVwu7pru5Etmd AJdwKTP4yHaAsiqBZ2i+t6sscaDXxjEglCvh8rMQR+io0DBIiWNixnRBKf72Eecl6/Ee U/50E3xu/RMdaxEj0ai71kFK5WW6+jtkGaqxdd2y7PVag1zJm9VOxMyOW+tpgylJNgIZ GXgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=quwmVS0HgN0VlF0M5EAcmLxVQ4XGDvzkpXE+pUK+Yew=; b=Xds5TDLRGYS12A5L9co3pY7LDRzAnrLOg2e74fzmnH3+k9z47vCGok40rhhsXhJgM4 AWq7EW052KuvqSk4cQr0cs2s0WMpnMDUs/Hn4OgVFW6VJGa5btUz6UX8Yg1OrwUiJumd bBQzFBRHKFp/e5esLn8tFPM4Pu19N6LC15j4dNDOzqoNdY5yE2HFvn5vNOvorxvhRAir GvBQQbA0Ldwd168At5ZacZZj8ZqSb6pBNAnegc4Y/8jWs5DVmK7YFkol8GBsu6hzGr5R KmH7Z3owNhUWh9M45yGbNRyVz3LopbiO1PvMf3jXnhF45I9gDCJia4xnZpaxdFO+tVsx 6ZdQ==
X-Gm-Message-State: AMke39mZv8x6WxMZ1hVuOqDoEtGga6sP0CW5ZXSMhoC8ZTJh7MwpXTIsNrLnKTi72GILeZP/VofEiucM3HuuQl/V
X-Received: by 10.37.7.5 with SMTP id 5mr898956ybh.8.1487927090807; Fri, 24 Feb 2017 01:04:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.207.4 with HTTP; Fri, 24 Feb 2017 01:04:30 -0800 (PST)
In-Reply-To: <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com>
From: Erik Kline <ek@google.com>
Date: Fri, 24 Feb 2017 18:04:30 +0900
Message-ID: <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="94eb2c069d44bbd28005494305f4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j2WN0kdS-Zfx-5R_CE5QbBv7AZE>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 09:04:55 -0000

--94eb2c069d44bbd28005494305f4
Content-Type: multipart/alternative; boundary=94eb2c069d44b34b39054943051c

--94eb2c069d44b34b39054943051c
Content-Type: text/plain; charset=UTF-8

On 24 February 2017 at 12:41, Christopher Morrow <morrowc.lists@gmail.com>
wrote:

> gosh people are being literal today :)
>
>
> On Thu, Feb 23, 2017 at 10:34 PM, Lorenzo Colitti <lorenzo@google.com>
> wrote:
>
>> On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <
>> morrowc.lists@gmail.com> wrote:
>>
>>> > The IESG plans to make a decision in the next few weeks, and solicits
>>> > final comments on this action. Please send substantive comments to the
>>> > ietf@ietf.org mailing lists by 2017-03-01. 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."
>>>
>>> Nothing in the past really matters here, what matters is: "Is the bis
>>> draft all set, did we fix all the things which must be fixed before this
>>> draft becomes a real 'standard'?"
>>>
>>
>> I don't think you can say nothing in the past matters here. We know that
>> there have been host implementations that relied on this guarantee, and we
>> have to consider that if we change the standard, those implementations will
>> become non-compliant.
>>
>
> I don't think the proposed (now 160+ messages back) text really says:
> "FREE FOR ALL< NO LIMITS!!! WEEE!" it says: "Hey, if you want to use /64
> because the application you are being placed into requires it (slac, blah
> and blah and ilnp and blah - see rfc7k) then do that, else any other prefix
> length works"
>
> how's that not 'ok' for host folks? "Hi, my host is going to be in a slaac
> world.. so /64 it is!"
>

For manual assignment among consenting adults: as you like it.  (For all
prefixes longer than /64, the trailing 64bits would still end up being
unique; there is no real issue here.)

And I gather everyone agrees that at a minimum the /127 RFC and other
working-group-graduated documents should be suitably incorporated and
referenced.

Otherwise, this feels like another round of "why isn't IPv6 just 128bit
IPv4?"  IMHO having /64 as the logical unit of allocation to network leaves
is a very good thing.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 2=
4 February 2017 at 12:41, Christopher Morrow <span dir=3D"ltr">&lt;<a href=
=3D"mailto:morrowc.lists@gmail.com" target=3D"_blank">morrowc.lists@gmail.c=
om</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"=
>gosh people are being literal today :)<div><div class=3D"h5"><br><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Feb 23, 2017 at 10=
:34 PM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"mailto:lorenzo@goo=
gle.com" target=3D"_blank">lorenzo@google.com</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"><div dir=3D"ltr"><div class=3D"gmail_extra"><div=
 class=3D"gmail_quote"><span>On Fri, Feb 24, 2017 at 12:23 PM, Christopher =
Morrow <span dir=3D"ltr">&lt;<a href=3D"mailto:morrowc.lists@gmail.com" tar=
get=3D"_blank">morrowc.lists@gmail.com</a>&gt;</span> wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><div>&gt; The IESG plans to make a decision in the next fe=
w weeks, and solicits</div><div>&gt; final comments on this action. Please =
send substantive comments to the</div><div>&gt; <a href=3D"mailto:ietf@ietf=
.org" target=3D"_blank">ietf@ietf.org</a> mailing lists by 2017-03-01. Exce=
ptionally, comments may be</div><div>&gt; sent to <a href=3D"mailto:iesg@ie=
tf.org" target=3D"_blank">iesg@ietf.org</a> instead. In either case, please=
 retain the</div><div>&gt; beginning of the Subject line to allow automated=
 sorting.&quot;</div><div><br></div><div>Nothing in the past really matters=
 here, what matters is: &quot;Is the bis draft all set, did we fix all the =
things which must be fixed before this draft becomes a real &#39;standard&#=
39;?&quot;</div></div></div></div></blockquote><div><br></div></span><div>I=
 don&#39;t think you can say nothing in the past matters here. We know that=
 there have been host implementations that relied on this guarantee, and we=
 have to consider that if we change the standard, those implementations wil=
l become non-compliant.</div></div></div></div>
</blockquote></div><br></div></div></div><div class=3D"gmail_extra">I don&#=
39;t think the proposed (now 160+ messages back) text really says: &quot;FR=
EE FOR ALL&lt; NO LIMITS!!! WEEE!&quot; it says: &quot;Hey, if you want to =
use /64 because the application you are being placed into requires it (slac=
, blah and blah and ilnp and blah - see rfc7k) then do that, else any other=
 prefix length works&quot;</div><div class=3D"gmail_extra"><br></div><div c=
lass=3D"gmail_extra">how&#39;s that not &#39;ok&#39; for host folks? &quot;=
Hi, my host is going to be in a slaac world.. so /64 it is!&quot;</div></di=
v></blockquote><div><br></div><div>For manual assignment among consenting a=
dults: as you like it. =C2=A0(For all prefixes longer than /64, the trailin=
g 64bits would still end up being unique; there is no real issue here.)</di=
v><div><br></div><div>And I gather everyone agrees that at a minimum the /1=
27 RFC and other working-group-graduated documents should be suitably incor=
porated and referenced.</div><div><br></div><div>Otherwise, this feels like=
 another round of &quot;why isn&#39;t IPv6 just 128bit IPv4?&quot; =C2=A0IM=
HO having /64 as the logical unit of allocation to network leaves is a very=
 good thing.</div></div></div></div>

--94eb2c069d44b34b39054943051c--

--94eb2c069d44bbd28005494305f4
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMf7MhR+6WMlT9cAZ4MA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTEyMjA2MzcwNloXDTE3MDUy
MTA2MzcwNlowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMFGbCvV+u+in+H0HY3bqCemHVO+gk8MSoSt5cw8MyfvalJUBE+K8i0L
KO7g5Tf0Hwxwin3Y78Fjurdr5ScXC3q2XKlu/KeOcKZ629BIHXR3Bc4P1kbeSBqtdP1hQsXutC3N
LKA6HYfEAKX5La7jHPIPymFuzHi9jqRt1XPLBhUIx/BUgV2RaLkaLlKi1gilVaUzZ/bwKGEBPXd7
oqEa0bmYHg7nnH3c07Ka5FqwYFbFNH2B8N9qhsEvaidSWAYFR3c83MxaNvd0cc9VR+xkg4h9t4j8
kgMqch9g5WsqvEiB8X9avk0RfRrJXnLpGVE9SgWC+9g/4qHF7INLnWGpoGsCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBRSp79TZtpx4DfF6E+LlflJ0/FBvzAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAYNw4ea3dhqz3+6k7eFLEAto3ynoX
iT5jeLl+/a9UeVSG5MQjruVO3LeqKKs3757hNcyfMZSooiOzamgE/W2G7gZMkCoT2NQbD7zSNB+S
toUONsMQ8t6Awv9osq1WWoK/xZkHV8wMGDOun9Ia8vO+hOU5wMOnhvg5mbE1xbst7pK2P9HgFxY2
/5o3VcBn4M6T5omuaz6GVsQ4VssAWfnqVpholf+EQahap+3Fpue24kwL3/pWnDkp0UcvjfItSy9c
UZdf/XOjI7X4DzroB3PFZ+rJSoRUjF2mKCLbHO0TLXtpEpr8ngGu8WwEAwf7eGHI6O5LCxrLYRdw
jqaGMxZnxTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDH+zIUfuljJU/XAGeDAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgMJbHtC8TD9gEBCWdYPd7KXgHNPynakex
unaQoeTDyE0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjI0
MDkwNDUxWjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBABCOP27IZPTdX0ksQA85erQvjhpuEjzlClQljCNJYLpWb2HNZvpK
UVx+p5w2XR8RFuAw0uZts7q8L+V41aEQ7clcvTVVzQ3f5u8wGtL3+uiGBcDQI6fmPv+bmf4dNqAf
yNqaTNWFEV/q/DM8AXxorlcAAFn0UDWXw6VNwFXl/lHmaSkArnuL/4yMwXmuMf1xurG7t+blRIqP
nfjm+wKZJ0OlFDYhMkr/6/Ska1A+WtcWJYjIA0FVLBZ3+uvlpc2Bh/u+kqYQgTeItPJcE0qLfQ/3
ZK+am1mAYnwwi2OAQp+S/d/BwSnif4cMFaR6iXOmFAB5cZ5iryVGsn58OfAHRi0=
--94eb2c069d44bbd28005494305f4--


From nobody Fri Feb 24 01:08:57 2017
Return-Path: <shitanshu_shah@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EFAC129653; Fri, 24 Feb 2017 01:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMTTxDPWB_Vk; Fri, 24 Feb 2017 01:08:51 -0800 (PST)
Received: from BLU004-OMC4S35.hotmail.com (blu004-omc4s35.hotmail.com [65.55.111.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2095812964B; Fri, 24 Feb 2017 01:08:51 -0800 (PST)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com ([65.55.111.135]) by BLU004-OMC4S35.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 24 Feb 2017 01:08:50 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=tvPejQ9ueDVz6O8UoCbDyJi2lHS71Z8YmvAQKZqcNUk=; b=J0UdNb5N0kwjKNWTuyrbNPxeH+/0Ekq5riQi0GT1MTJU6xIFkrcEKhyJzZoB7vMeN/vVn8EvM22uBpJHRYodcP/+fwj/shSy8IDIAXYdn6JhDsnPILyntu0eNKvXDKmQRrMBRFoJTGF7z9fe+q6scxCcU/P2/6a2YykxfK+STBz0Da7awG9CCnzHbBHPtsBEBNU/BOP7wxAsnATivj64Yc6LBGtxmBGz9qwrrEKJTlo8AeUmLmAybez68jHQb3CjTm2y/EmBbyeh7/xKqEUYU5OicdJ5uhe2WMbrDuxYetpaIyEYkTiOwtHd7DJF+NvzebIol5ELbEXzmk9OGjcMtg==
Received: from BN3NAM04FT006.eop-NAM04.prod.protection.outlook.com (10.152.92.57) by BN3NAM04HT005.eop-NAM04.prod.protection.outlook.com (10.152.92.94) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.904.16; Fri, 24 Feb 2017 09:08:49 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com (10.152.92.55) by BN3NAM04FT006.mail.protection.outlook.com (10.152.92.96) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10 via Frontend Transport; Fri, 24 Feb 2017 09:08:48 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) by DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) with mapi id 15.01.0933.011; Fri, 24 Feb 2017 09:08:48 +0000
From: Shitanshu Shah <shitanshu_shah@hotmail.com>
To: David Black <david.black@emc.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjJJLT08h8arb7kKXAYa1wCM/2KF32nBg
Date: Fri, 24 Feb 2017 09:08:48 +0000
Message-ID: <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com>
In-Reply-To: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:9A064EEAB07F54851A715F2F74E80C8DA0B4B3A606E74B648E4C47CC0F7FA35E; UpperCasedChecksum:3AFC029FA63F8C251377EF6B4D9961CBDE7906AD010C7AC060E89BA24FC9D54B; SizeAsReceived:7964; Count:40
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [pjjwzSAqV0lvBrTqXOxXZTIutsVq7otw]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; BN3NAM04HT005; 5:pGuyYfRta1iA36U6LbghAaeKU+MnGR4onIExy2CGA+hGw1kIZIOIcgr+jfQA7UcRbmCtNPk0bhCKx5u/PrhMxYHu6HlG6iYI3DMrmLO2SSQ6A1aJOUh1IljomLLrzwvZrdWUqkCma46K394McWsm3DR8nBwUk4b8zelNwkZbIgY=; 24:A1ZXrOeU4daX4Sg/o1inuiZn1iA30pTE/tRZsTgLrBwCrPzCnUzr3+98tOvaFcP/hmKL/Ym8rBbi+2gfG8fP0EFzTCGUkxvI+vCJpvItE5A=; 7:JrJ3qpRhwipUQiJ0KEgjiebM870X4mWembTDcQGLE1Zemt4/EOtvnpfpAouo4KuuOn2vIX+HeUuG+k0HQnXczBsOsGxRwj3M3AuDgxZvNYGKVqtmp6Q7kgi7Q4oG2jgCXIfYt1UEdGsxZXJz1Ioa+3Lj0lWz1um7JkZPSLgeuCxXwuBnt7v43pwwxj6kixZXkq6hYjKq/MKmLEqZdSDDOp1dAEdKpGm2Olaro6xFCQY8xu6YYOXVHLhrLt9GZA+obMjPNtBEvJYwQPdgtc4nMBZ3/zldEK4RQw25G8+PP4TcdSU7RVduKMHzSerk8PuF
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3NAM04HT005; H:DM3PR13MB0604.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: bd0fd79a-0342-4c12-8df1-08d45c94be37
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1601125254)(1603101373)(1701031045); SRVR:BN3NAM04HT005; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:BN3NAM04HT005; BCL:0; PCL:0; RULEID:; SRVR:BN3NAM04HT005; 
x-forefront-prvs: 0228DDDDD7
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM3PR13MB0604160394059613AD0331AFE5520DM3PR13MB0604namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2017 09:08:48.1372 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM04HT005
X-OriginalArrivalTime: 24 Feb 2017 09:08:50.0294 (UTC) FILETIME=[9CFB5960:01D28E7D]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VlQdD_CmuC6UP8prNWXa2hkBNqY>
Cc: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 09:08:55 -0000

--_000_DM3PR13MB0604160394059613AD0331AFE5520DM3PR13MB0604namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Hi David,


Thank you for taking time for the review..


Please find our response inline ##svshah and [Med]


Regards,
Shitanshu

________________________________
From: David Black <david.black@emc.com>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.




[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.

##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?



[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?




The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token
bucket
                and a secondary/peak token bucket that MUST be nested, i.e.=
,
traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the
details
                of how to specify this are subtle, see RFC 2698 for a worke=
d
example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be
used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n
profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in
profile for both
                token buckets), Peak (out of profile for primary/committed =
token
bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile
for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.

##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.



[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.

##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"




[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.

##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.




[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.

##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.





[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.




[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.

##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

      If an advertised SLA ID is different from earlier advertised
one,
      for the same prefix and from the same Source AS, indicates
Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn=92t adopted that design is that we don=92t want to=
 make assumptions on which data the remote peer will be used for enforcing =
local actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.


[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label,
802.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's
network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en
there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt
header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the
inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind=92t include a context field because we thought that the defin=
ition of the IPFIX attributes is sufficient by itself, but if you do think =
it is helpful to have such information, we can update the table.


[12] The security considerations (section 10) are severely incomplete
and insufficient:

        - Discussion of possible abuse of this BGP option for
denial-of-service and theft-of-service,
                needs to be added, including possible countermeasures and
mitigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.


        - This sentence at the end of the second paragraph in Section 10 is
content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking
sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.
How does
one
                figure out whether an implementation or deployment is  "at =
the
scale
                of the Internet" ??

[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

        - The next to last paragraph in section 10 is almost content-free, =
as
it leaves
                decisions on implementation and deployment of key security
functionality as
                "an exercise for the reader" - that's not acceptable.


[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].



        - Last, but not least, the final paragraph in Section 10 is a joke
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC
6919.

------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------




--_000_DM3PR13MB0604160394059613AD0331AFE5520DM3PR13MB0604namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><br>
</p>
<p>Hi David,</p>
<p><br>
</p>
<p>Thank you for taking time for the review..</p>
<p><br>
</p>
<p>Please find our response inline ##svshah and [Med]</p>
<p><br>
</p>
Regards,
<div>Shitanshu<br>
<br>
<div>
<div style=3D"color: rgb(0, 0, 0);">
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> David Black &lt;dav=
id.black@emc.com&gt;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</font>
<div>&nbsp;</div>
</div>
</div>
<font>
<div class=3D"PlainText" style=3D"color: rgb(0, 0, 0); font-size: 10pt;">Re=
viewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
tsv-art@ietf.org if you reply to or forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142" previewremoved=3D"true">https://en.wikipedia.org/wiki/Service-lev=
el_agreement</a> .<br>
<br>
<span style=3D"font-family: Calibri, Arial, Helvetica, sans-serif;">##svsha=
h, sure, we can change the term to TCA (Traffic Conditioning Agreement), wh=
ich fairly represents intention in the draft, if there is no otherwise comm=
ent from the working group.</span></div>
<div class=3D"PlainText" style=3D"color: rgb(0, 0, 0); font-size: 10pt;"><s=
pan style=3D"font-family: Calibri, Arial, Helvetica, sans-serif;"><br>
</span></div>
<div class=3D"PlainText" style=3D"color: rgb(0, 0, 0); font-size: 10pt;"><f=
ont face=3D"Calibri, Arial, Helvetica, sans-serif"><br>
</font><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.<br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer,&nbsp;is to make sure traffic is well conditioned, at the egress =
of the&nbsp;Consumer, to avoid possible indiscriminate drops at the ingress=
 of the Producer. In another words, the&nbsp;Producer
 is telling the&nbsp;Consumer to ignore its own link level overhead, instea=
d use Producer's provided link level overhead while running frames through =
QoS functions (this is&nbsp;relevant in use-cases where l2 overhead of the&=
nbsp;egress link on Consumer and of ingress link
 on the Producer are of different size, e.g., in the&nbsp;vpn/tunnel connec=
tion between two peer&nbsp;nodes which physically may be multiple hops away=
).</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<span style=3D"font-size: 13.3333px;">I understand your comments regarding =
re-using TSpec without any modification.&nbsp;</span><span style=3D"font-si=
ze: 13.3333px;">Do you agree with the use-case of l2 differences? If yes, a=
ny suggestion how to accommodate that?</span><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</div>
<div class=3D"PlainText" style=3D"color: rgb(0, 0, 0); font-size: 10pt;"><b=
r>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate,
 but no in/out profile marking parameters.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
Is your proposal below to define two TSpecs using the same&nbsp;definition =
from RFC2215? Wouldn't in that case we have min/max specified twice? min/ma=
x in each TSpec? and thus confusing to represent one min and one max throug=
h two TSpecs?</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"PlainText"><br>
</div>
<br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token<br>
bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,<br>
traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the<br>
details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d<br>
example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be<br>
used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in<br>
profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in<br>
profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token<br>
bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile<br>
for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.<br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah,&nbsp;It is around the semantics of&nbsp;a single queue with a dif=
ferent threshold for a set of code-points, where packet for a specific code=
-point is to be tail dropped if overall queue-depth hits code-point specifi=
c threshold at the arrival of that packet.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<span style=3D"font-size: 13.3333px;">We will add appropriate clarification=
 for this semantics.</span><br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.<br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
&quot;</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
A higher priority class of traffic&nbsp;to be served without pre-empted by =
lower priority&nbsp;class of traffic&nbsp;for more than a packet time at th=
e configured rate.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a&nbsp;higher priority traffic=
 class where that queue &nbsp;is configured for the full share of the outpu=
t bandwidth.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
&quot;</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.<br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple &nbsp;subset of&nbsp;Traffic Classes, with =
their own Traffic Class Elements and Traffic Class Services.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
Will correct the wording to remove your this specific concern.</div>
<br>
<br>
<br>
<br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.<br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, While&nbsp;eventually &quot;Traffic Conditioning Agreement&quot; =
should be translated to the actual forwarding qos policy on any vendor spec=
ific device, TCA exchange largely carries concepts/semantics that is either=
 standard based or&nbsp;well understood.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
While we are not aware of any working group document of QoS Yang Model, we =
think that &nbsp;concepts of Traffic Conditioning should be easily adaptabl=
e to any QoS Yang Models since they also have to be defined to support thos=
e concepts.</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
<br>
</div>
<br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
<span style=3D"font-family: Calibri, Arial, Helvetica, sans-serif; font-siz=
e: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;">##svs=
hah, okay. Ron Bonica also suggested same in his review earlier. We had cho=
sen a path of optional Source AS to
 simplify implementations in&nbsp;cases. Given specification of Source AS a=
lways is more clearer in multiple feed-back we have gotten so far, we can m=
odify the specification to incorporate that over the simplicity of implemen=
tation for certain cases.</span></div>
<div class=3D"PlainText">
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri, Arial, Helveti=
ca, sans-serif" size=3D"2"><br>
</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri, Arial, Helveti=
ca, sans-serif" size=3D"2"><br>
</font></div>
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Calibri, Arial, Helveti=
ca, sans-serif" size=3D"2"><br>
</font></div>
<span style=3D"color: rgb(0, 0, 0); font-size: 13.3333px; font-family: Cali=
bri, Arial, Helvetica, sans-serif; font-variant-ligatures: normal; orphans:=
 2; widows: 2;"></span><br>
<font size=3D"2">[9] In section 3.2, the &quot;intended for the peer receiv=
er of the BGP</font><br>
<font size=3D"2">UPDATE message&quot; text in the specification of bit 0 of=
 the SLA Subtype</font><br>
<font size=3D"2">flags is unclear.&nbsp; I suspect that this is intended to=
 differentiate</font><br>
<font size=3D"2">the two usages described in sections 4.1.1 (Point-to-Point=
) and 4.1.2</font><br>
<font size=3D"2">(Multiple Hops), in which case the parenthesized terms (or=
 similar</font><br>
<font size=3D"2">terminology) should be used with cross-references to those=
 two</font><br>
<font size=3D"2">sections.</font><br>
<br>
<div class=3D"x_PlainText" style=3D"font-family: Calibri, Arial, Helvetica,=
 sans-serif; font-size: 13.3333px; font-variant-ligatures: normal; orphans:=
 2; widows: 2;">
##svshah, sure will make necessary changes, also in the context of earlier =
comment.</div>
<div><br>
</div>
<br>
<font size=3D"2">[10] There needs to be a coherent discussion in one place =
about how</font><br>
<font size=3D"2">SLA advertisement, update and withdrawal work.&nbsp; A sin=
gle ADVERTISE</font><br>
<font size=3D"2">method may suffice on the wire, but the details on how ini=
tial</font><br>
<font size=3D"2">advertisement, subsequent advertisement (update) and withd=
rawal work</font><br>
<font size=3D"2">need to be specified in one place.&nbsp; The third paragra=
ph of Section 4</font><br>
<font size=3D"2">is a start on this material, but it's too terse;&nbsp;</fo=
nt></div>
<div class=3D"PlainText"><font size=3D"2"><br>
</font></div>
<div class=3D"PlainText"><span style=3D"font-family: 'Courier New'; font-si=
ze: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;">[Med=
] That text is terse because we are reusing the BGP machinery for advertisi=
ng/withdrawing; we only augment it with
 triggers that are linked to the SLA information. A new SLA will lead to an=
 update message with ADVERTISE, an update of an existing SLA will trigger a=
n update message. We do think this information is already present in the do=
cument. &nbsp;</span><br>
</div>
<div class=3D"PlainText"><font size=3D"2"><br>
</font></div>
<div class=3D"PlainText"><font size=3D"2">it should be expanded</font><br>
<font size=3D"2">into its own subsection, and moved earlier to come before =
the</font><br>
<font size=3D"2">ADVERTISE method in Section 3.2.&nbsp; This text from Sect=
ion 3.2 should be</font><br>
<font size=3D"2">moved into that new subsection and likewise expanded:</fon=
t><br>
<br>
<span style=3D"font-family: 'Courier New'; font-size: 13.3333px; font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;">[Med] Another option is to mo=
ve it Section 4. From our standpoint, we do think it is straightforward to =
describe the behavior once the attributes
 format are defined.&nbsp;</span></div>
<div class=3D"PlainText">
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Courier New" size=3D"2"=
><br>
</font></div>
<span style=3D"font-family: 'Courier New'; font-size: 13.3333px; font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;"></span><font size=3D"2">&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp; If an advertised SLA ID is different from earlier=
 advertised</font><br>
<font size=3D"2">one,</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the same prefix and fro=
m the same Source AS, indicates</font><br>
<font size=3D"2">Source</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is advertising new SLA C=
ontent to replace the previous one</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised with the same SL=
A ID.</font><br>
<br>
<font size=3D"2">In addition, I wonder whether functionality should be adde=
d to allow</font><br>
<font size=3D"2">withdrawal of an advertisement by specifying its SLA ID, a=
lthough that</font><br>
<font size=3D"2">was not part of the original design.</font></div>
<div class=3D"PlainText"><font size=3D"2"><br>
</font></div>
<div class=3D"PlainText">
<p class=3D"x_MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 12pt; fo=
nt-family: 'Times New Roman', serif; color: rgb(33, 33, 33); font-variant-l=
igatures: normal; orphans: 2; widows: 2;">
<span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Courier N=
ew&quot;; color: black;">[Med] The reason we didn=92t adopted that design i=
s that we don=92t want to make assumptions on which data the remote peer wi=
ll be used for enforcing local actions and also because
 of this text:</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt=
; font-family: 'Times New Roman', serif; color: rgb(33, 33, 33); font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;">
<span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Courier N=
ew&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The SLA ID applies to aggregate t=
raffic to prefixes for a given</span></p>
<p class=3D"x_MsoNormal" style=3D"margin: 0cm 0cm 0.0001pt; font-size: 12pt=
; font-family: 'Times New Roman', serif; color: rgb(33, 33, 33); font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;">
<span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Courier N=
ew&quot;;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AFI/SAFI that share the same Sour=
ce AS and SLA ID.</span></p>
</div>
<div class=3D"PlainText"><font size=3D"2"><br>
</font><br>
<font size=3D"2">[11] Notions of context for interpretation of all the IPFI=
X parameters</font><br>
<font size=3D"2">in 3.3.1 need to be added, e.g.:</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The first thr=
ee parameters (DSCP, MPLS EXP field in top label,</font><br>
<font size=3D"2">802.1q priority) can</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-link or LSP-by-LS=
P basis along a traffic's</font><br>
<font size=3D"2">network path.</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The IP addres=
s parameters are rather likely to be VPN-specific when</font><br>
<font size=3D"2">there's more</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN that spans or transi=
ts the ASs involved.</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The transport=
 port parameters need specification of which transport</font><br>
<font size=3D"2">header and where it</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP traffic carried =
by in VXLAN, is this the</font><br>
<font size=3D"2">inner TCP header</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header in VXLAN).</font><=
br>
<font size=3D"2">There are probably simple approaches to specifying context=
 in all</font><br>
<font size=3D"2">cases, but that context does need to be specified ... in a=
ll cases.</font><br>
<br>
<span style=3D"font-family: 'Courier New'; font-size: 13.3333px; font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;">[Med] We dind=92t include a c=
ontext field because we thought that the definition of the IPFIX attributes=
 is sufficient by itself, but if you
 do think it is helpful to have such information, we can update the table.<=
/span><br>
<br>
<br>
<font size=3D"2">[12] The security considerations (section 10) are severely=
 incomplete</font><br>
<font size=3D"2">and insufficient:</font><br>
<br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Discussion of=
 possible abuse of this BGP option for</font><br>
<font size=3D"2">denial-of-service and theft-of-service,</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, including possible coun=
termeasures and</font><br>
<font size=3D"2">mitigations.</font><br>
<br>
<span style=3D"font-family: 'Courier New'; font-size: 13.3333px; font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;">[Med] This attack vector is n=
ot specific to this attribute; this is valid for BGP in general.</span></di=
v>
<div class=3D"PlainText">
<div style=3D"orphans: 2; widows: 2;"><font face=3D"Courier New" size=3D"2"=
><br>
</font></div>
<span style=3D"font-family: 'Courier New'; font-size: 13.3333px; font-varia=
nt-ligatures: normal; orphans: 2; widows: 2;"></span><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - This sentence=
 at the end of the second paragraph in Section 10 is</font><br>
<font size=3D"2">content-free:</font><br>
<br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is NOT RECOMMENDED to=
 enable this attribute at the</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale of the Internet un=
less if means to prevent leaking</font><br>
<font size=3D"2">sensitive</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information are enforced=
.</font><br>
<br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implementer or admin su=
pposed to do?&nbsp;</font></div>
<div class=3D"PlainText"><font size=3D"2"><br>
</font></div>
<div class=3D"PlainText"><span style=3D"font-family: 'Courier New'; font-si=
ze: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;">[Med=
] An example of what an admin needs to check if this information can be sen=
t to a given peer or not. Some of the
 content of the attribute contains some sensitive information such as contr=
act Id, classes, etc.</span><br>
</div>
<div class=3D"PlainText"><font size=3D"2">How does</font><br>
<font size=3D"2">one</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an implementation or de=
ployment is&nbsp; &quot;at the</font><br>
<font size=3D"2">scale</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??</font></div>
<div class=3D"PlainText"><span style=3D"font-family: 'Courier New'; font-si=
ze: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><br>
</span></div>
<div class=3D"PlainText"><span style=3D"font-family: 'Courier New'; font-si=
ze: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;">[Med=
] The idea here is to avoid leaking such data in to the global routing tabl=
e. Only entitled peers need receive
 such information with controlled scope.</span><br>
</div>
<div class=3D"PlainText"><span style=3D"font-family: 'Courier New'; font-si=
ze: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;"><br>
</span></div>
<div class=3D"PlainText"><font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp; - The next to last paragraph in section 10 is almost content-free=
, as</font><br>
<font size=3D"2">it leaves</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementation and deployment=
 of key security</font><br>
<font size=3D"2">functionality as</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the reader&quot; - t=
hat's not acceptable.</font><br>
<br>
<p class=3D"x_MsoNormal" style=3D"margin: 0cm 0cm 12pt; font-size: 12pt; fo=
nt-family: 'Times New Roman', serif; color: rgb(33, 33, 33); font-variant-l=
igatures: normal; orphans: 2; widows: 2;">
<span lang=3D"EN-US" style=3D"font-size: 10pt; font-family: &quot;Courier N=
ew&quot;; color: black;">[Med] I guess you are referring to the following t=
ext. Validation checks are really deployment-specific. The text calls out t=
he issue and recommends an action; how to translate
 this action into detailed actions is realty local to a domain</span></p>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; The attribute may be adver=
tised by a misbehaving node to communicate</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; SLA parameters that are no=
t aligned with the SLA agreements.&nbsp; Though</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; the enforcement of SLA par=
ameters is outside the scope of this</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; document, it is RECOMMENDE=
D that the SLA Consumer to enforce a set of</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; validation checks before t=
ranslating the SLA parameters conveyed in</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; the QoS attributes into pr=
ovisioning actions.&nbsp; Such validations MAY</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; rely on SLA parameters lik=
e the origin AS or SLA ID, like generating</span></pre>
<pre style=3D"margin: 0cm 0cm 0.0001pt; font-size: 10pt; font-family: 'Cour=
ier New'; color: rgb(33, 33, 33); font-variant-ligatures: normal; orphans: =
2; widows: 2;"><span lang=3D"EN-US">&nbsp;&nbsp; SLA ID using pseudo-random=
 schemes [</span><a href=3D"https://tools.ietf.org/html/rfc4086" target=3D"=
_blank" title=3D"&quot;Randomness Requirements for Security&quot;"><span la=
ng=3D"EN-US">RFC4086</span></a><span lang=3D"EN-US">].</span></pre>
<div><span lang=3D"EN-US"><br>
</span></div>
<div><span lang=3D"EN-US"><br>
</span></div>
<br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Last, but not=
 least, the final paragraph in Section 10 is a joke</font><br>
<font size=3D"2">that will</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security directorate reviewer=
 - to understand why, see</font><br>
<font size=3D"2">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, and take note of th=
e publication date of RFC</font><br>
<font size=3D"2">6919.</font><br>
<br>
<font size=3D"2">------------------------</font><br>
<br>
<font size=3D"2">Having noted a dozen major issues, I'll end the review her=
e for now,</font><br>
<font size=3D"2">as I believe a serious revision of the draft is called for=
, which</font><br>
<font size=3D"2">would be a better starting point to review for minor issue=
s and</font><br>
<font size=3D"2">editorial items.</font><br>
<br>
<font size=3D"2">--------------------------------------------------------</=
font><br>
<font size=3D"2">David L. Black, Distinguished Engineer</font><br>
<font size=3D"2">Dell EMC, 176 South St., Hopkinton, MA&nbsp; 01748</font><=
br>
<font size=3D"2">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbsp; Cell: &#43;1=
 (978) 394-7754</font><br>
<font size=3D"2">David.Black@dell.com&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</fo=
nt><br>
<font size=3D"2">--------------------------------------------------------</=
font><br>
<br>
<br>
<br>
</div>
</font></div>
</div>
</div>
</body>
</html>

--_000_DM3PR13MB0604160394059613AD0331AFE5520DM3PR13MB0604namp_--


From nobody Fri Feb 24 01:33:14 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F08CD129657 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 01:33:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 6gTCeWwv0EEV for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 01:33:11 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5074126FDC for <ietf@ietf.org>; Fri, 24 Feb 2017 01:33:10 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2B166615B7 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:33:09 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id E4F7A602B6; Fri, 24 Feb 2017 10:33:08 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id D60B5154D3; Fri, 24 Feb 2017 10:33:08 +0100 (CET)
Date: Fri, 24 Feb 2017 10:33:08 +0100
From: Gert Doering <gert@space.net>
To: Erik Kline <ek@google.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170224093308.GA2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha-256; boundary="Vm3jasITniUHaScm"
Content-Disposition: inline
In-Reply-To: <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/g4xGqaPJNWWhCgYuOQ10KsIxjUk>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 09:33:13 -0000

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

Hi,

On Fri, Feb 24, 2017 at 06:04:30PM +0900, Erik Kline wrote:
> IMHO having /64 as the logical unit of allocation to network leaves
> is a very good thing.

Why, exactly, except "because it was decided to be that way, many years
ago"?

(Not that I have any plans to fight that particular windmill, but /64
never made sense to me, after all the more interesting aspects of 8+8
never happened, and thus, effectively, IPv6 today is "IPv4 with longer
addresses" as far as "hosts attaching to networks" and "routing" is
concerned...)=20

Wasting half the address space and then having to start arguments on
the amount of subnets available to home users ("can we give them a=20
/48, or will we run out?", "can we give ISPs enough space so they can
give all their users a /48, or do we need to make this a /56?", "how
much conservation is required by ISPs?") is major silliness - something
like a /96 would have served the aspect "more machines than you can
imagine per subnet" perfectly well.  SLAAC would have been a bit more
challenging, but "use the MAC address" was not *such* a good idea=20
either.

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

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

--Vm3jasITniUHaScm
Content-Type: application/x-pkcs7-signature
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIIODwYJKoZIhvcNAQcCoIIOADCCDfwCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGgggslMIIFcjCCBFqgAwIBAgICAQIwDQYJKoZIhvcNAQEFBQAwgZQxCzAJBgNVBAYTAkRF
MQ8wDQYDVQQHEwZNdW5pY2gxFDASBgNVBAoTC1NwYWNlTmV0IEFHMR4wHAYDVQQLExVaZXJ0
aWZpemllcnVuZ3NzdGVsbGUxGTAXBgNVBAMTEFNwYWNlTmV0IFJvb3QgQ0ExIzAhBgkqhkiG
9w0BCQEWFGRhdGFjZW50ZXJAc3BhY2UubmV0MB4XDTExMTAxOTE2MjAzM1oXDTI2MTAxNTE2
MjAzM1owgZQxCzAJBgNVBAYTAkRFMQwwCgYDVQQIEwNzcDExFDASBgNVBAoTC1NwYWNlTmV0
IEFHMR8wHQYDVQQLExZad2lzY2hlbnplcnRpZml6aWVydW5nMRswGQYDVQQDExJTcGFjZU5l
dCBMZXZlbDIgQ0ExIzAhBgkqhkiG9w0BCQEWFGRhdGFjZW50ZXJAc3BhY2UubmV0MIIBIjAN
BgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0TZfc3M8GIjLwvISEA8/c5DYYOzGk82PdjkK
LzV0KWg5fOL5XN3QZMNjhspIrwNX4KlUfhhlV6XQ0XoYByJ9OS6IeUgK2DeRrCqZ1FC9zxWD
MUy56Uq5cULUH+dGRUTnCYUX55VNpVYG8OSSIHO8wl0AsSArTevBkLySdoDNXxeQjEaNPQFG
BANiDYCyOtjswsFGM7HleGUfEDgkqFbwsXrcroHL6FIfTQoVQWEN3fY2JbbLXN+xcqOEd4Ih
HfDnPCFtiS3ahAJjEOQ42mcfCpwambPX2fHBGhWuQLEropKoy7ba5DVcs/BhsdLxV2Bs/dPx
7ZVEmYLak+hZk1DatwIDAQABo4IByjCCAcYwHQYDVR0OBBYEFI/AuOF8TILZ9MBdi4dYqe5E
gHR2MIHBBgNVHSMEgbkwgbaAFGcpxe17gXP8uKsBPqyov4kcFy7koYGapIGXMIGUMQswCQYD
VQQGEwJERTEPMA0GA1UEBxMGTXVuaWNoMRQwEgYDVQQKEwtTcGFjZU5ldCBBRzEeMBwGA1UE
CxMVWmVydGlmaXppZXJ1bmdzc3RlbGxlMRkwFwYDVQQDExBTcGFjZU5ldCBSb290IENBMSMw
IQYJKoZIhvcNAQkBFhRkYXRhY2VudGVyQHNwYWNlLm5ldIIBZTAPBgNVHRMBAf8EBTADAQH/
MAsGA1UdDwQEAwIBvjBMBggrBgEFBQcBAQRAMD4wPAYIKwYBBQUHMAKGMGh0dHA6Ly9ldWts
aWQuc3BhY2UubmV0L2NlcnQvc3BhY2VfU3BhY2VSb290LmNlcjBBBgNVHR8EOjA4MDagNKAy
hjBodHRwOi8vZXVrbGlkLnNwYWNlLm5ldC9jZXJ0L3NwYWNlX1NwYWNlUm9vdC5jcmwwEQYJ
YIZIAYb4QgEBBAQDAgEGMB8GA1UdEQQYMBaBFGRhdGFjZW50ZXJAc3BhY2UubmV0MA0GCSqG
SIb3DQEBBQUAA4IBAQAJ0v/AgH8QHyr+bWIavj/z7ITuqPGWEloPbcuw/icljb4mLmAsp8d9
q77k7mXxgzqBmxIrwcuEdL3l22ZrTnWikiYrKMQ97UssNubnVd6p3hD+nOmygusHJ+drSie8
siFokUjlo8tv+bQzriKtLNuwNKHAFvSH3lypBiQvDAyS7ylTgkfM7BDuaLYw3xsBPvCPRI+U
/nzh6ACofz+vogWm5VshW+GhqFQBqcL+gMTm1iW8xLNZ0Z542sTdvSK59YgC/Bhp5kXckgFY
IMGI5F2LJ83Iw/izBl5aD5j9Cnv/d341fIUvzSHXoXOIYT7UP/pjvZAk1xD332WWfEahTO4O
MIIFqzCCBJOgAwIBAgICAzEwDQYJKoZIhvcNAQELBQAwgZQxCzAJBgNVBAYTAkRFMQwwCgYD
VQQIEwNzcDExFDASBgNVBAoTC1NwYWNlTmV0IEFHMR8wHQYDVQQLExZad2lzY2hlbnplcnRp
Zml6aWVydW5nMRswGQYDVQQDExJTcGFjZU5ldCBMZXZlbDIgQ0ExIzAhBgkqhkiG9w0BCQEW
FGRhdGFjZW50ZXJAc3BhY2UubmV0MB4XDTE2MTEwMjEwNTAyM1oXDTE3MTExNjEwNTAyM1ow
gZcxCzAJBgNVBAYTAkRFMQwwCgYDVQQIEwNzcDExDzANBgNVBAcTBk11bmljaDEUMBIGA1UE
ChMLU3BhY2VOZXQgQUcxDjAMBgNVBAsTBXVzZXJzMRUwEwYDVQQDEwxHZXJ0IERvZXJpbmcx
HTAbBgkqhkiG9w0BCQEWDmdlcnRAc3BhY2UubmV0MQ0wCwYDVQQrEwRnZXJ0MIIBIjANBgkq
hkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAstQ0lY62WmGZV1NxsT80jMBo1ilFOOo0B2lWYAkK
lr0N5gwZOtu6WvGf7kFboCBqGUu+++ZPi6DdOqfyCwgPttrIVJxUHExSaWon0xjvgCvSgfLr
dmI4mgm/wAwaStY8cxvO+u0LgKxW2SBxCsba9nVIhMlK/848VhUV0kqunpxwdEk71a65K6J6
UMhMLmyjBHN4lvY54GkfJGRVQneh4is1TraTOTBSEMIfKSe6osiwhqrgW9pORQi1p/0eoitn
5Hv92XZ44zSY7uPD8i5DTuO5oT4AUMMbWSW9k8XwlRLezXs2OBtLExn8eLJCFNAOgtL56F/+
ZN6IGhRmW0CC4wIDAQABo4ICADCCAfwwDAYDVR0TAQH/BAIwADAOBgNVHQ8BAf8EBAMCBaAw
JwYDVR0lBCAwHgYIKwYBBQUHAwIGCCsGAQUFBwMEBggrBgEFBQcDAzAdBgNVHQ4EFgQUwLN/
sVI7xvpVzcIu9GdYLQ3eysowgcIGA1UdIwSBujCBt4AUj8C44XxMgtn0wF2Lh1ip7kSAdHah
gZqkgZcwgZQxCzAJBgNVBAYTAkRFMQ8wDQYDVQQHEwZNdW5pY2gxFDASBgNVBAoTC1NwYWNl
TmV0IEFHMR4wHAYDVQQLExVaZXJ0aWZpemllcnVuZ3NzdGVsbGUxGTAXBgNVBAMTEFNwYWNl
TmV0IFJvb3QgQ0ExIzAhBgkqhkiG9w0BCQEWFGRhdGFjZW50ZXJAc3BhY2UubmV0ggIBAjBO
BggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9ldWtsaWQuc3BhY2UubmV0L2Nl
cnQvc3BhY2VfU3BhY2VMZXZlbDIuY2VyMBkGA1UdEQQSMBCBDmdlcnRAc3BhY2UubmV0MB8G
A1UdEgQYMBaBFGRhdGFjZW50ZXJAc3BhY2UubmV0MEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6
Ly9ldWtsaWQuc3BhY2UubmV0L2NlcnQvc3BhY2VfU3BhY2VMZXZlbDIuY3JsMA0GCSqGSIb3
DQEBCwUAA4IBAQCbUZCcxxopU5RD9+BfA9u+uhqEl/C45p/7y8/m4ANphan0GCGlTSl8tWZ0
bU+IIOrqG94W9v0MGOUnVUNgHD5VVt9MPZFxUsGn6Ac5CWbAhqClABxZbcQLROguG9JYfTmX
Zebl19iUN7vbKvv9U1IFQBGDBlpnm1PtypqsuwXQYQHSZD31XsV7ALMIzAaYhkts9xOySFfm
zPlFj3D8pj/vUfbcqaNNOgiZLqEXb71ynXQcA1cEr2iDCLWejfq3BJoxP3fZLjwBY9us7td0
LtRoha/nVvx0HHXFVI1XDwH7tGtN80LzprNTcWltcWEjwk6gD2CNakhew0P2hzIMzEjIMYIC
rjCCAqoCAQEwgZswgZQxCzAJBgNVBAYTAkRFMQwwCgYDVQQIEwNzcDExFDASBgNVBAoTC1Nw
YWNlTmV0IEFHMR8wHQYDVQQLExZad2lzY2hlbnplcnRpZml6aWVydW5nMRswGQYDVQQDExJT
cGFjZU5ldCBMZXZlbDIgQ0ExIzAhBgkqhkiG9w0BCQEWFGRhdGFjZW50ZXJAc3BhY2UubmV0
AgIDMTANBglghkgBZQMEAgEFAKCB5DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqG
SIb3DQEJBTEPFw0xNzAyMjQwOTMzMDhaMC8GCSqGSIb3DQEJBDEiBCCPryq6YSGoFf9Tnf+4
GhmvTmB53d1SHPz20WGjK8hstTB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggq
hkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG9w0BAQEFAASCAQCk
m96+Ec5VC6JQ1N6jTtpJKaa2hqg2ch+JbwUVeIVn9sQa3YZk+0AURAa5R+RmeTZdrmMBsB2U
04sID/BFxmJxrsowfxB01Ygfjl7Wz6qSMweLKgF7gI1lXXYF/kLLiE79s7IuCpWBxGWhsNWK
UY5bWFiQNc18djh+ph6nDSrqBCHj1XuO+LObjxbJuBqFYcWUTxIHBqfgTZxfuXIOxENsApDM
X96ZiBN6Gr8WcX84ZMlLeSeIuViYKP5HSnGsTTharHkh9FRcVdJPAq9IQeUQtN69dbd7XW9D
EkACDI2VLs3cRHwGnxhtnpYAIPYvgMJS00k7yrRyrsLWv4p5oEPb

--Vm3jasITniUHaScm--


From nobody Fri Feb 24 02:14:38 2017
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8AD7129676; Fri, 24 Feb 2017 02:14: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oKz1aVNXZhX; Fri, 24 Feb 2017 02:14:35 -0800 (PST)
Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::242]) (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 56292129673; Fri, 24 Feb 2017 02:14:35 -0800 (PST)
Received: by mail-wr0-x242.google.com with SMTP id o22so807465wro.3; Fri, 24 Feb 2017 02:14:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=FZ0baErIUGCekm4au6TcF8NiTjxl7cwQFZFrCSiS+o0=; b=bLUtSwHCkR/C+pOT0TdkdT88855Ohs1Nc5ba2aVJw/Mxv8ga3p+qhHfUod3i5I91gM a8pWD51f71oF3R+JtfrHLVDhc74WCXuTpyHk8qB1usLFpUINMhH7lMBVRedN9HqiJSdz wT3zmqZdsxU8wgliw/iMLaiU3dTIiGN8RZsEMKufQNfQZFUxL5A5ihQ/F2BOWa4E63+o PJIQka9COtx0Mq6wAXydkzYETZpZmoN28ZpCM4eiwpjyco/kmYM9kwRhSmicS2d7HKo5 Tu8DOnc2TPziOwC2JjWn/lNvRVlIC37peHBbq8WADINICukHsRfhgAebnrPuHHiVKOUf /SwA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=FZ0baErIUGCekm4au6TcF8NiTjxl7cwQFZFrCSiS+o0=; b=VZMaSKDKRShZqogq1pMQMxkDD3WZxbmhygViSCKLZ4/Zg3BCPGPEF+zll+lnntT8y+ IkMzKDBVgTKiAK8gVra5AKaSlUNRSfHezoUfhrPhvhQSH8ECv0ds/232wjOOmxlFQ224 wevxt5806GlhuhP/c/jSKWb6eKA40oZFugY9fivy3ZYj1CjIAQtt2sXww1bt1yeUG1Wc /Opyu4tuyGuMBQejJJRnw+wC22hDzhH/8tycH1RLeMP7nQIK7JWNzhrzkp8l2lxxx8Zl lm1p30rHubnw6iB7r6+fOo7CColTeyxtBnk8dA9FJkyjxERVAx0mCTqIFRmEAiHwQy8k 8Zbg==
X-Gm-Message-State: AMke39muaFkSQWnz2AVM1Sd7Hvjh6eL06Gogze34d3XxAuzOK0gUFtAUkc3705kpGMv9Aw==
X-Received: by 10.223.171.30 with SMTP id q30mr1777170wrc.61.1487931273768; Fri, 24 Feb 2017 02:14:33 -0800 (PST)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id 65sm9703579wri.53.2017.02.24.02.14.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Feb 2017 02:14:33 -0800 (PST)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <9311B0B8-FCB5-4D1B-8107-BB3EB94C0C23@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B3822E44-4025-40A6-840C-59E9AFF766CE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Date: Fri, 24 Feb 2017 12:14:29 +0200
In-Reply-To: <20170224093308.GA2367@Space.Net>
To: Gert Doering <gert@space.net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com> <20170224093308.GA2367@Space.Net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PM8iDO4D6nV6lhJ19Zp8MYFQmeM>
Cc: Erik Kline <ek@google.com>, IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 10:14:37 -0000

--Apple-Mail=_B3822E44-4025-40A6-840C-59E9AFF766CE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


> On 24 Feb 2017, at 11:33, Gert Doering <gert@space.net> wrote:
>=20
> Hi,
>=20
> On Fri, Feb 24, 2017 at 06:04:30PM +0900, Erik Kline wrote:
>> IMHO having /64 as the logical unit of allocation to network leaves
>> is a very good thing.
>=20
> Why, exactly, except "because it was decided to be that way, many =
years
> ago"?
>=20
> (Not that I have any plans to fight that particular windmill, but /64
> never made sense to me, after all the more interesting aspects of 8+8
> never happened, and thus, effectively, IPv6 today is "IPv4 with longer
> addresses" as far as "hosts attaching to networks" and "routing" is
> concerned...)
>=20
> Wasting half the address space and then having to start arguments on
> the amount of subnets available to home users ("can we give them a
> /48, or will we run out?", "can we give ISPs enough space so they can
> give all their users a /48, or do we need to make this a /56?", "how
> much conservation is required by ISPs?") is major silliness - =
something
> like a /96 would have served the aspect "more machines than you can
> imagine per subnet" perfectly well.

And you can see RFC 5739 on how a /64 subnet is required for each road =
warrior connected to a VPN.  You=E2=80=99d need a /56 or /48 to do what =
a /24 does in IPv4.

Yoav


--Apple-Mail=_B3822E44-4025-40A6-840C-59E9AFF766CE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCgAGBQJYsAeGAAoJELhJCxUKWMyZ8aIH/2QhVzkDHEuZivs9EVcB9ntd
LoaQ139TS/PLh97sTYCFi2qEYywQYjh1MFMaC8yhoeUYGwyICJJcgXtWhqXMNTNq
zWyh8dUzbytfq7ObKlvF0SNGTkjHLFDCiVrvEHR7JgpPJhsGfsDvFYx6fdIKF+gX
UC4IKTuNpE4Tcw8nkQK7qEz8i7MPUz5I/601/5wBsYYoC7OSGSJcwIzmFICYxAk2
U0QFPhXF4aBCungQWBOHiX4B/KUbn2kBntwGY8D0cRVGn490180q9CgcQ8PfYn4S
hLqbf/nKjmDrsUAhoPuOMm+mzAnPIqR/N6xrGGPqgxH0OBxkh99jDxUpE09EcB4=
=szsy
-----END PGP SIGNATURE-----

--Apple-Mail=_B3822E44-4025-40A6-840C-59E9AFF766CE--


From nobody Fri Feb 24 02:45:55 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 362E11296B2; Fri, 24 Feb 2017 02:45:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eldzs1ekYGrg; Fri, 24 Feb 2017 02:45:52 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 F2F7A1297B8; Fri, 24 Feb 2017 02:45:51 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id r141so11400749wmg.1; Fri, 24 Feb 2017 02:45:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to; bh=Mt8pESlzDJSD+gJcIBGvErHTJR3K+mjU2hGs7mlg7r0=; b=LljS1YMqLO3j3IDZRnzPYBS0NcbILo9/aY8ESW9WnuYtfdk1k9bscG2BWTFn03M40T BJfov6f+FvfyiLVbFFN/qI5jmU5uDX4pTQ0U5FSBdggNTDzJCv1MdbbCbSTqSOnjSoJh r3MbWBCRaFhQRy/mZDX3G6KkuA0jRs5ZywKrhWQvAys2hV0ScyB7KAeumFbfAv3bBSyA xAR5J4Uo1qAa0wsyYC2cvD4jr1NpK5uVUwdYyAWHw2QANs3rShldiSc0gAmNzNH7ZFGl pH7n8tdAYM3GTnrGs5OVWi6Z8+g3VP1uOpYEFqtcvxuheirns6GuBXB3chvd3kjrWpTJ FzjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to; bh=Mt8pESlzDJSD+gJcIBGvErHTJR3K+mjU2hGs7mlg7r0=; b=baxn/6upGNx6gL4owBuSCSY2Q+WtVolQbGSaugZRIUGRsLHwZCOXk2PnAyuDXWwyza m9e67Zf5feqkK/FH5vMkmS6adSRn2GdN7/LIdQbdDUPDJYbmDBEwUrjs6PO6VknJOqqo XUFc9xz7/Zu/KjEE52KvfxP8BNwU0fgSSTtgpT4or/+btUzyWKKKa1VEcJzd6Xoe6vCk xonZSNqB74fQXqBhnjMWX8VU/3XlD/9werfICuDYcgf926PT/Q0B3wqm0UZroHh4Hp8G xXsTa5q4JJwlUjtEtZNN1C6bgqwXzrjqegirHlvj3IJ7I8raqY0fFjgDyRkpO+HOIU7z KMRA==
X-Gm-Message-State: AMke39n/NmNGPUYlxU41wTyewDfgNSMBoBLhowakXTVT7eIlBDkWU70pERFUu7oTKVqHqQ==
X-Received: by 10.28.93.68 with SMTP id r65mr2240793wmb.133.1487933150145; Fri, 24 Feb 2017 02:45:50 -0800 (PST)
Received: from [192.168.2.126] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id 48sm9833794wrt.54.2017.02.24.02.45.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Feb 2017 02:45:49 -0800 (PST)
Subject: Re: Last Call Summary on <draft-bradner-rfc3979bis-10.txt> (Intellectual Property Rights in IETF Technology) to Best Current Practice
To: Jari Arkko <jari.arkko@piuha.net>, ietf@ietf.org
References: <148474911031.2261.11881119527780959351.idtracker@ietfa.amsl.com> <7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <228bec7a-96c8-8b30-3ba4-e8b9e8ed73a1@gmail.com>
Date: Fri, 24 Feb 2017 10:45:48 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net>
Content-Type: multipart/alternative; boundary="------------AA460A0691A7013D9CC8B466"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KIbhM1j_Hsf43IyTui_HC9-NGdM>
Cc: draft-bradner-rfc3979bis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 10:45:54 -0000

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

Jari

I agree with the proposed resolutions , but would like to reply on three 
points:


On 22/02/2017 21:40, Jari Arkko wrote:
>
>
>
> * Question from Stewart Bryant on Jan 24, regarding item B in
>   Section 3.3:
>
>>       B. Such Contributor represents that there are no limits to the
>>          Contributor's ability to make the grants, acknowledgments and
>>          agreements herein that are reasonably and personally known
>>     to the
>>          Contributor.
>>
>>     SB> I do not understand what point B above means.
>
>     It means that if you (for instance) make an IPR declaration
>     and say something about the license conditions, you or whoever
>     is helping you to make that statement, can actually make those
>     statements.
>
>     I don’t think a document change is needed.
>

I am suspect that I am not alone in finding the original legal language
impenetrable, whilst finding your explanatory text crystal clear. I would
request you take a another look at this point, perhaps adding your text
by way of clarification.

> * Question from Stewart Bryant on Jan 24, regarding Section
>   5.7:
>
>>     5.7. Disclosures for Oral Contributions.
>>
>>       .... then the Contributor must accompany
>>       such oral Contribution with an oral declaration that he/she is
>>     aware
>>       of relevant IPR in as much detail as reasonably possible
>>
>>     SB> I do not recall ever seeing a purely verbal disclosure, and
>>     wonder
>>     SB> what the process is, how this is archived and how it is
>>     discovered?
>
>     Sometimes it happens that a presenter makes a statement,
>     e.g. that the audience should note that some IPRs may apply
>     and that a written declaration is forthcoming.
>

I suppose the requirement would that the WG take particular care to 
minute the IPR
disclosure so it is on record. At least if it is the minutes it is 
searchable and from
the minutes you can get to the recoding to get the exact words.

>
> * Suggestion from Stewart Bryant on Jan 24, regarding Section
>   5.5:
>
>>     5.5. Licensing Information in an IPR Disclosure
>>
>>       A. Since IPR disclosures will be used by IETF working groups during
>>          their evaluation of alternative technical solutions, it is
>>     helpful
>>          if an IPR disclosure includes information about licensing of the
>>          IPR in case Implementing Technologies require a license.
>>          Specifically, it is helpful to indicate whether, upon
>>     approval by
>>          the IESG for publication as an RFC of the relevant IETF
>>          specification(s), all persons will be able to obtain the
>>     right to
>>          implement, use, distribute and exercise other rights with
>>     respect
>>          to an Implementing Technology a) under a royalty-free and
>>          otherwise reasonable and non- discriminatory license, or b)
>>     under
>>          a license that contains reasonable and non-discriminatory terms
>>          and conditions, including a reasonable royalty or other payment,
>>          or c) without the need to obtain a license from the IPR holder
>>          (e.g., a covenant not to sue).
>>
>>     SB> One of the most popular IPR terms is so called MAD. It is
>>     surprising
>>     SB> that you do not call this out.
>>     …
>>       Some common
>>       conditions include 1) terms that are fair, reasonable and non-
>>       discriminatory, and which may bear royalties or other financial
>>       obligations (FRAND or RAND); 2) royalty-free terms that are
>>     otherwise
>>       fair, reasonable and non-discriminatory (RAND-z); and 3)
>>     commitments
>>       not to assert declared IPR.
>>
>>     SB> One of the most common (at least in the Routing area) is
>>     non-assert
>>     SB> unless the other party asserts (so called MAD)
>
>     Personally, I don’t view MAD as a term quite in the same style
>     and technical specificity as, say, RAND or RF. I would suggest
>     not adopting this.
>
>     (Non-assert on the other hand is a more
>     technical term, but I also have not seen calls for adding that
>     from others.)
>
>

The reason I raise this is because it is the most common licensing term 
in the lower layers
being the standard term by at least three of the major vendors. I am 
sure it has a technical
name, presumably mutual-non-assert.

- Stewart

--------------AA460A0691A7013D9CC8B466
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p>Jari</p>
    <p>I agree with the proposed resolutions , but would like to reply
      on three points:<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 22/02/2017 21:40, Jari Arkko wrote:<br>
    </div>
    <blockquote
      cite="mid:7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net"
      type="cite"><br>
      <div>
        <div>
          <div><br>
            <div><br>
            </div>
            <div>
              <div>* Question from Stewart Bryant on Jan 24, regarding
                item B in</div>
              <div>  Section 3.3:</div>
            </div>
            <div><br>
            </div>
            <blockquote style="margin: 0px 0px 0px 40px; border: none;
              padding: 0px;">
              <blockquote type="cite">  B. Such Contributor represents
                that there are no limits to the</blockquote>
              <blockquote type="cite">     Contributor's ability to make
                the grants, acknowledgments and</blockquote>
              <blockquote type="cite">     agreements herein that are
                reasonably and personally known to the</blockquote>
              <blockquote type="cite">     Contributor.</blockquote>
              <blockquote type="cite"><br>
              </blockquote>
              <blockquote type="cite">SB&gt; I do not understand what
                point B above means.</blockquote>
              <div><br>
              </div>
              <div>It means that if you (for instance) make an IPR
                declaration</div>
              <div>and say something about the license conditions, you
                or whoever</div>
              <div>is helping you to make that statement, can actually
                make those</div>
              <div>statements.</div>
              <div><br>
              </div>
              <div>I don’t think a document change is needed.</div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I am suspect that I am not alone in finding the original legal
    language <br>
    impenetrable, whilst finding your explanatory text crystal clear. I
    would <br>
    request you take a another look at this point, perhaps adding your
    text<br>
    by way of clarification.<br>
    <br>
    <blockquote
      cite="mid:7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net"
      type="cite">
      <div>
        <div>
          <div>
            <div>
              <div>* Question from Stewart Bryant on Jan 24, regarding
                Section</div>
              <div>  5.7:</div>
            </div>
            <div><br>
            </div>
          </div>
          <blockquote style="margin: 0px 0px 0px 40px; border: none;
            padding: 0px;">
            <div>
              <blockquote type="cite">5.7. Disclosures for Oral
                Contributions.</blockquote>
            </div>
            <div>
              <blockquote type="cite"><br>
              </blockquote>
            </div>
            <div>
              <blockquote type="cite">  .... then the Contributor must
                accompany</blockquote>
            </div>
            <div>
              <blockquote type="cite">  such oral Contribution with an
                oral declaration that he/she is aware</blockquote>
            </div>
            <div>
              <blockquote type="cite">  of relevant IPR in as much
                detail as reasonably possible</blockquote>
            </div>
            <div>
              <blockquote type="cite"><br>
              </blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; I do not recall ever seeing
                a purely verbal disclosure, and wonder</blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; what the process is, how
                this is archived and how it is discovered?</blockquote>
            </div>
            <div><br>
            </div>
            <div>Sometimes it happens that a presenter makes a
              statement,</div>
            <div>e.g. that the audience should note that some IPRs may
              apply</div>
            <div>and that a written declaration is forthcoming.</div>
          </blockquote>
        </div>
      </div>
    </blockquote>
    <br>
    I suppose the requirement would that the WG take particular care to
    minute the IPR <br>
    disclosure so it is on record. At least if it is the minutes it is
    searchable and from<br>
    the minutes you can get to the recoding to get the exact words.<br>
    <br>
    <blockquote
      cite="mid:7D727C42-59E0-4105-A64E-86B44B4ACF8F@piuha.net"
      type="cite">
      <div>
        <div>
          <div>
            <blockquote style="margin: 0px 0px 0px 40px; border: none;
              padding: 0px;"></blockquote>
            <div><br>
            </div>
            <div>
              <div>* Suggestion from Stewart Bryant on Jan 24, regarding
                Section</div>
              <div>  5.5:</div>
            </div>
            <div><br>
            </div>
          </div>
          <blockquote style="margin: 0px 0px 0px 40px; border: none;
            padding: 0px;">
            <div>
              <blockquote type="cite">5.5. Licensing Information in an
                IPR Disclosure</blockquote>
            </div>
            <div>
              <blockquote type="cite"><br>
              </blockquote>
            </div>
            <div>
              <blockquote type="cite">  A. Since IPR disclosures will be
                used by IETF working groups during</blockquote>
            </div>
            <div>
              <blockquote type="cite">     their evaluation of
                alternative technical solutions, it is helpful</blockquote>
            </div>
            <div>
              <blockquote type="cite">     if an IPR disclosure includes
                information about licensing of the</blockquote>
            </div>
            <div>
              <blockquote type="cite">     IPR in case Implementing
                Technologies require a license.</blockquote>
            </div>
            <div>
              <blockquote type="cite">     Specifically, it is helpful
                to indicate whether, upon approval by</blockquote>
            </div>
            <div>
              <blockquote type="cite">     the IESG for publication as
                an RFC of the relevant IETF</blockquote>
            </div>
            <div>
              <blockquote type="cite">     specification(s), all persons
                will be able to obtain the right to</blockquote>
            </div>
            <div>
              <blockquote type="cite">     implement, use, distribute
                and exercise other rights with respect</blockquote>
            </div>
            <div>
              <blockquote type="cite">     to an Implementing Technology
                a) under a royalty-free and</blockquote>
            </div>
            <div>
              <blockquote type="cite">     otherwise reasonable and non-
                discriminatory license, or b) under</blockquote>
            </div>
            <div>
              <blockquote type="cite">     a license that contains
                reasonable and non-discriminatory terms</blockquote>
            </div>
            <div>
              <blockquote type="cite">     and conditions, including a
                reasonable royalty or other payment,</blockquote>
            </div>
            <div>
              <blockquote type="cite">     or c) without the need to
                obtain a license from the IPR holder</blockquote>
            </div>
            <div>
              <blockquote type="cite">     (e.g., a covenant not to
                sue).</blockquote>
            </div>
            <div>
              <blockquote type="cite"><br>
              </blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; One of the most popular IPR
                terms is so called MAD. It is surprising</blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; that you do not call this
                out.</blockquote>
            </div>
            <div>
              <blockquote type="cite">…</blockquote>
            </div>
            <div>
              <blockquote type="cite">  Some common</blockquote>
            </div>
            <div>
              <blockquote type="cite">  conditions include 1) terms that
                are fair, reasonable and non-</blockquote>
            </div>
            <div>
              <blockquote type="cite">  discriminatory, and which may
                bear royalties or other financial</blockquote>
            </div>
            <div>
              <blockquote type="cite">  obligations (FRAND or RAND); 2)
                royalty-free terms that are otherwise</blockquote>
            </div>
            <div>
              <blockquote type="cite">  fair, reasonable and
                non-discriminatory (RAND-z); and 3) commitments</blockquote>
            </div>
            <div>
              <blockquote type="cite">  not to assert declared IPR.</blockquote>
            </div>
            <div>
              <blockquote type="cite"><br>
              </blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; One of the most common (at
                least in the Routing area) is non-assert</blockquote>
            </div>
            <div>
              <blockquote type="cite">SB&gt; unless the other party
                asserts (so called MAD)</blockquote>
            </div>
            <div><br>
            </div>
            <div>Personally, I don’t view MAD as a term quite in the
              same style</div>
            <div>and technical specificity as, say, RAND or RF. I would
              suggest</div>
            <div>
              <div>not adopting this.</div>
              <div><br>
              </div>
              <div>(Non-assert on the other hand is a more</div>
            </div>
            <div>technical term, but I also have not seen calls for
              adding that</div>
            <div>from others.)</div>
            <div><br>
            </div>
          </blockquote>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
    The reason I raise this is because it is the most common licensing
    term in the lower layers<br>
    being the standard term by at least three of the major vendors. I am
    sure it has a technical <br>
    name, presumably mutual-non-assert.<br>
    <br>
    - Stewart<br>
  </body>
</html>

--------------AA460A0691A7013D9CC8B466--


From nobody Fri Feb 24 02:49:26 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEECF12960E; Fri, 24 Feb 2017 02:49:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cpkf6mX42eb; Fri, 24 Feb 2017 02:49:18 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 854701293EE; Fri, 24 Feb 2017 02:49:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 19E934D; Fri, 24 Feb 2017 11:49:16 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:in-reply-to:date:date:subject:subject :mime-version:content-type:content-type:message-id:from:from :received:received; s=mail; t=1487933354; bh=GmwOp+6KsJIGltn4ugf ocqrJmJJztHGCrt4RUtX6ris=; b=Q+qOv285OSsXAiLXtCYvieG1C4q938HXdPy hQmH116v6Fy8XIYQhqGYUJK4SJt40kdDpND4b+HxiUd9cfy1cmShJ3LEAgiiPTjc iwV38g1LXDbkb6yNpTk8tTQPjS4btB5bhtPTx0aT82IWi+6eJkKp067NkHQ8CGtq JKdkDKt4=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id E0ak9ho2-clV; Fri, 24 Feb 2017 11:49:14 +0100 (CET)
Received: from [IPv6:2003:8:27:8600:9c7c:7f36:b525:f0d8] (unknown [IPv6:2003:8:27:8600:9c7c:7f36:b525:f0d8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id 23F434C; Fri, 24 Feb 2017 11:49:14 +0100 (CET)
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
Message-Id: <5B82833D-FFF8-45C1-A38D-F8CB81766BB7@steffann.nl>
Content-Type: multipart/signed; boundary="Apple-Mail=_709CA215-A7EE-4036-9179-3EB961F089DB"; protocol="application/pkcs7-signature"; micalg=sha1
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Date: Fri, 24 Feb 2017 11:49:13 +0100
In-Reply-To: <20170224093308.GA2367@Space.Net>
To: =?utf-8?Q?Gert_D=C3=B6ring?= <gert@space.net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com> <20170224093308.GA2367@Space.Net>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n3za1KbpZAu_UKfSjMzPPpGF7Gk>
Cc: Erik Kline <ek@google.com>, IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 10:49:20 -0000

--Apple-Mail=_709CA215-A7EE-4036-9179-3EB961F089DB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

> something like a /96 would have served the aspect "more machines than =
you can
> imagine per subnet" perfectly well.

Yeah, I wish we had chose something like that in the past as well :(

Cheers,
Sander


--Apple-Mail=_709CA215-A7EE-4036-9179-3EB961F089DB
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFSDCCBUQw
ggMsoAMCAQICARMwDQYJKoZIhvcNAQEFBQAwdjELMAkGA1UEBhMCTkwxEjAQBgNVBAcTCUFwZWxk
b29ybjEVMBMGA1UEChMMU0pNIFN0ZWZmYW5uMR0wGwYDVQQDExRTSk0gU3RlZmZhbm4gUm9vdCBD
QTEdMBsGCSqGSIb3DQEJARYOY2FAc3RlZmZhbm4ubmwwHhcNMTUwNTExMDg1MjM1WhcNMTgwODIz
MDg1MjM1WjB1MQswCQYDVQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0g
U3RlZmZhbm4xGDAWBgNVBAMTD1NhbmRlciBTdGVmZmFubjEhMB8GCSqGSIb3DQEJARYSc2FuZGVy
QHN0ZWZmYW5uLm5sMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9b7oVFaA35FKgKq2dZXbh
X1kQl2mgPnaI3OurSyefZ6dyv8JFNM6CAA77kb/Gh5FXVDEJujcRPnE93Lmvmx+82J140WSiTpez
7QY8oBYNDCRP0KksXzwfClZjrG2Afw8S1jH14ymK0HufZ9kEkSWD5WzrxEDSqwnQTyFhsGCrbQID
AQABo4IBYDCCAVwwCQYDVR0TBAIwADARBglghkgBhvhCAQEEBAMCBLAwKwYJYIZIAYb4QgENBB4W
HFRpbnlDQSBHZW5lcmF0ZWQgQ2VydGlmaWNhdGUwHQYDVR0OBBYEFMBr5zy4rYkQJ/JeoU3+6lnw
Ebd5MIGoBgNVHSMEgaAwgZ2AFOH79lsAHFEBG+6Vrq192mCYPEg6oXqkeDB2MQswCQYDVQQGEwJO
TDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0gU3RlZmZhbm4xHTAbBgNVBAMTFFNK
TSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcNAQkBFg5jYUBzdGVmZmFubi5ubIIJALBR3gny
oySYMBkGA1UdEgQSMBCBDmNhQHN0ZWZmYW5uLm5sMB0GA1UdEQQWMBSBEnNhbmRlckBzdGVmZmFu
bi5ubDALBgNVHQ8EBAMCBaAwDQYJKoZIhvcNAQEFBQADggIBAFhAYYTBnxV8QzZPT+qs+WLWNRKL
4JQq0dpmSleofioAUrHj8m2BITvJY1pnIY7mdegJXic6+/uCKMAG8FrA6tSNu/hUoTXYMVcUUih5
xZyCWsIFmSBbTuel0nmPvZDayelIwi7GDN0u9IvrmyinSiYJ5jjgiKg3Z1HmMP5t9MR8vpS38bxT
WKef8RlACK9jeynmk2U8PFRT+ZVYDW3Us8z4wje+g+q0aEm8UZzoYE245C6aFBqiXS56AN9VcK2C
9Z4wSBnq+I0wRof0BIYIh7V1cFCtz3uhdcbVbfKPHP2GGv69nz/jqSz9hPbIEhC3/kv11FHvIA2x
t1scHJOw5DPKaogCtp4BEiOayepZRYo8SCILVTUH07QEP+6D/nLQnNavQT2ClQaSq9ufuD689TvC
r5BApB8glktKaPzsiW5gQncIp4GyY593cGkBdh2jPAVpYCyAG96xtY6E0NsjgoghSojeHRfaZOmR
iDfaszo4JlIer+VPTcsIl984275cOE/LJcXLSb3AA9AyffEr+6Eszs6HzkfWlzdTedGbqPFhkSlg
gBCTZAz/MCT//MVZiDq542xAU8nBpfKWfOyL3oK2PPQAGdpGxFNRzCBngi64n0mB+JrNS44j6WyP
qWp2IGSu05o7x6lcUgsjtNmpYvZy4NoyPu4je4+QuzBpFYgCMYICnjCCApoCAQEwezB2MQswCQYD
VQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQKEwxTSk0gU3RlZmZhbm4xHTAbBgNV
BAMTFFNKTSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcNAQkBFg5jYUBzdGVmZmFubi5ubAIB
EzAJBgUrDgMCGgUAoIIBeTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMjQxMDQ5MTRaMCMGCSqGSIb3DQEJBDEWBBTV92Dq4nMex1fovbfiRDLrsU82LjCBigYJ
KwYBBAGCNxAEMX0wezB2MQswCQYDVQQGEwJOTDESMBAGA1UEBxMJQXBlbGRvb3JuMRUwEwYDVQQK
EwxTSk0gU3RlZmZhbm4xHTAbBgNVBAMTFFNKTSBTdGVmZmFubiBSb290IENBMR0wGwYJKoZIhvcN
AQkBFg5jYUBzdGVmZmFubi5ubAIBEzCBjAYLKoZIhvcNAQkQAgsxfaB7MHYxCzAJBgNVBAYTAk5M
MRIwEAYDVQQHEwlBcGVsZG9vcm4xFTATBgNVBAoTDFNKTSBTdGVmZmFubjEdMBsGA1UEAxMUU0pN
IFN0ZWZmYW5uIFJvb3QgQ0ExHTAbBgkqhkiG9w0BCQEWDmNhQHN0ZWZmYW5uLm5sAgETMA0GCSqG
SIb3DQEBAQUABIGAVgvbmNg/VDStJ1ciLsm7Ag+DbDdiVHsx7BhGbFu4SCO5kNt8OMLHIAOpESkd
FwDh/UxO8ne71pHXzqE+FdIbX76IqInuhC9EbLcGJX0ELDlEYfJSNhNRBPrwYWq30wRwDyjTYrso
/Qn94Lpooo83G/uWVJk0Eb85ZZ/eymHFQpEAAAAAAAA=
--Apple-Mail=_709CA215-A7EE-4036-9179-3EB961F089DB--


From nobody Fri Feb 24 03:27:58 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13F2812969D for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 03:27:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 al-ule-7-0kl for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 03:27:54 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 33C4E1293EE for <ietf@ietf.org>; Fri, 24 Feb 2017 03:27:54 -0800 (PST)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1chE2S-0000ETC; Fri, 24 Feb 2017 12:27:52 +0100
Message-Id: <m1chE2S-0000ETC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
In-reply-to: Your message of "Thu, 23 Feb 2017 19:55:16 -0500 ." <C14767E5-2948-444B-9E8A-7CE5072F9413@gmail.com> 
Date: Fri, 24 Feb 2017 12:27:51 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/60XcWUvZlnH2ffv1iz9OCjfd250>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 11:27:56 -0000

>IPv4 has no equivalent to RAs, so the workaround is to infer prefix assignment
> from address assignment.

Technically that's not quite correct:
RFC-950 defines a subnet mask request/reply.
And RFC 1256 defines router advertisements

Subnet mask ICMPs were never popular. I think some popular implementation
tended to give a wrong reply.

Router advertisements were somewhat popular. But got out of fashion when
DHCP became the standard way of obtaining configuration.


From nobody Fri Feb 24 03:39:11 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21F67129A9F; Fri, 24 Feb 2017 03:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level: 
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e8Ky7FQBCpvg; Fri, 24 Feb 2017 03:39:07 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0102.outbound.protection.outlook.com [104.47.1.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 595B8129A9A; Fri, 24 Feb 2017 03:39:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=yug+Uh38uqVnGUEAhYRAde05FZliHhWxUSaTAHXC+l0=; b=dQStKrrHhXgn2MS7oeRqfg4Zy61T2LGqqyETSB2wd1DA6S8aSM1+ZQPXZEVXBtdf2hfr6WTzRqol0onFKdU26flMLHOoARPF2I4fDIfZemVRIUGycjT3WykTBVz4JwE4t1MVRyHX2Y+Bi2YC+2XtdQ6W4xidsFX3l/KEmJHx1q8=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.7; Fri, 24 Feb 2017 11:39:04 +0000
Message-ID: <02da01d28e92$36a4b8e0$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: David Farmer <farmer@umn.edu>, Fernando Gont <fgont@si6networks.com>
References: <20170221001940.GB84656@Vurt.local> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
Date: Fri, 24 Feb 2017 10:51:56 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: HE1PR05CA0025.eurprd05.prod.outlook.com (2a01:111:e400:51f9::35) To DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9)
X-MS-Office365-Filtering-Correlation-Id: fb2929a6-7408-4037-fbdc-08d45ca9bc9b
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:DB5PR07MB1559;
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 3:kCqzqwo4ySJsPWJWmZxIRbk8QLJnSr99+BA3vjIDTxa2GmqyFp/B3GFldGeeo6xH9fO5IJlT51PbyTSaNM7FxVtFQHc1R9mLX2M9x/q3kl4TvHrgRUDMfrSc9lA5ilf8MTM9IeRv9VKZVLBj+xXrKVNA/WKnLU7OtB0mlZoC9H9gEpBaHvFvZjYrJyEZP0WrSVDyyCntYWfZNQU441T0Pvfy16l7bVMjNV4S+sAhoykGfjNYXSfBid1hCKVcm0R/F8eciKxWfeMzh5vELPq6hw==; 25:6JMfG1gLVyfJJXoGIJU8vHyYsvSUcrmIAbgmtaKeHVMeJcV6quq1Ui8meWS8eh9HyYTV3XrbqrFBExY9yOr83KjFOdAQBma1QGTp9J15lmSCvKUyXvNnpiWv7wt8ghWQwUPmQ3ELn7+xCqZnKlBariFe+EkKjWlZ0ijppkM/atdjQud5AtA3rXfYFbla8pp1qSVkTHMROGeEWFHUorLEIobX83RIXA7I/FV9wTV+MHbNEwWb/YoF7yNpli97qAMfq7hKklz5HA0eLTaITtIlHOEQ0i/t9x8KTFLeYdmLVTd464QQFXWO9F2y4+HHvLzhfntCyjSmwlAxk4bOFhdlJTc4QQmITxQKxdRlAqwasMW8+1fmlGjXv8vSiSmGJqbvr6DLeKsmRiXwMyznqgfVpsaCz+gwO1q+ORyNtvOkhElc0qEgOGknq8+nhlqV20xnOjQljA69Iv4avHE4yzEHRw==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 31:CDwKzuULOKGKccNaMtcBuqyIr8LrVChk+z/m5mf+6vjh///T9PpNHs3nj7Mt3gPZCCfHEhssYEcgllygpXmvjM+Oo9vKkt+nClTJyxODhPqVwZG/9+KMXjd35+VWjEcFAGs0AjJes7eQu4/VRcQagM9ag1Q3hKhU5Wlb4aqHBoz/rtSpGBWbdRt3Su+zWEcawBhusNpWqKwCHSj2HUVRIZQAa9srUbqJVyxEvlVOjMyaKLaHI1vGBTg7X6xXR5Zx7eo9K9DYLllvY68jStL8K77Qo7hxMt7F1ivLcoDw4Xg=
X-Microsoft-Antispam-PRVS: <DB5PR07MB15596A76D03CE0D6C9CA0015C6520@DB5PR07MB1559.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(100405760836317)(8104003914727);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6041248)(20161123560025)(20161123558025)(20161123564025)(20161123555025)(20161123562025)(6072148); SRVR:DB5PR07MB1559; BCL:0; PCL:0; RULEID:; SRVR:DB5PR07MB1559; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 4:scLyqiH5kIrBJq9BjmzpM9sHwF/7To8Amhm8nJH8jDJVZ8RZRF1ioNCuSiHbxWDyufSnfkCxb2ioEw34YUZ+7oI9JAqhSQFZdENq/DOrFpjIFnJvflzAu/S6fMuo8XgY0JWzCbV8NhxRt2uVVJ3Vi1e84QdH/LeKrOi+WfApdPw5Pqu2XEpVyXoQChFZl7Pq++zthJxkxa0ZSXTjCXDMPw81XL7ip7JlsxnCAMYcJ133CvHIkIlvY6+SEvWw9ztGKPxBP0m3asIJs77TLABO9grIEfWpKquBB96bKKrL+W3J+OUt6wl2PxAsh4C7Kg01XwSPAS1bnrLPMkbg9ZmAvAzhB2y1r+pAt2YWEqoqLAABxLU0zdSwS4QEgiC2BxTCi9P3qQCWCvw3e9NNx6ZYsy544hIZA93Qw3ZhXadY8lrklKXRWr77gLoM6vKsO6soMTKqQPhPWaVIQrQ8wkyjhkWPGFHyOhNaERRG7efcXjWqY2AELN4BVbIbJMNL5I+eUmEQrH0snEu4JhML73Fx/CehJyXS4wTykPR3BpFXZ8PlzfiyEnGV140SZCqNQLKaIB8oaTaz1oUxEDsUjuwv1SfjuUk+FDKYHkvFnZPofg5bhF+LxhsTNw8CYI3GxQ2TME5/f8TJNUuYsWlU0vNt98R9Boq2sdy3wnK7XpodGAGSAamnOKZ6L91wXHrFQEIz
X-Forefront-PRVS: 0228DDDDD7
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(13464003)(24454002)(377454003)(199003)(189002)(42186005)(81166006)(76176999)(81686999)(53936002)(6496005)(86362001)(92566002)(106356001)(2171002)(8676002)(23676002)(50226002)(97736004)(101416001)(50466002)(38730400002)(81156014)(53546006)(50986999)(81816999)(61296003)(6246003)(1456003)(189998001)(4720700003)(66066001)(105586002)(230783001)(14496001)(2906002)(6666003)(116806002)(93886004)(5660300001)(3846002)(54906002)(84392002)(7736002)(305945005)(230700001)(6116002)(44716002)(4326007)(68736007)(9686003)(33646002)(47776003)(62236002)(1556002)(44736005)(6486002)(229853002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1559; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU5OzIzOnBZczNhaEdYY3hPZk1NMUxiRThKMTNzMnZT?= =?utf-8?B?VEJEbk0xdndSaENUenF3a1N5em1FT05XakNGVHNOT0IydWxPNE5KSVFlVUxV?= =?utf-8?B?aXNvZFNCWGNzT1VGbEVKeEpwb2xNTWlId0RKSnRkK24rS3cyUFB0UW1mbW5P?= =?utf-8?B?UDR0TXlNMWRDY053QzYxQnE4MXNudUFHdERwWlc2VnltRldyelhGUjc2Z0VZ?= =?utf-8?B?SERGZzZJZEJsOGVYcFZIM0oxbDRRZisveDIvdldTRzhLeGxnRytMd3dxTEI1?= =?utf-8?B?THJOc0xhOW15VzRjd0M4VlVTZWZtTFNYSlpRZVloSjhGejB4RVAvQ0d4cDI4?= =?utf-8?B?ZEdmeDV5eDJxejVvUHJGTm54M1I5azYrTjlCa21sQjNYVjl2cUhyZTdhMUhK?= =?utf-8?B?ZVNjOEMyTDhoL2NMQzRvaWxrVldZTWFGY1Z2ZEZ4SEFRbUFKajllckJsaWVl?= =?utf-8?B?MGxhT1FTMDZ6NllmbjFzMzJiTk55MU8zZEpsZkpKWWUvcEdzQkJVcDN5VXhk?= =?utf-8?B?L29YWWxRaFRXK3ZlZTdYVWU2akZXMnZSMXBEZXV3K1RFTVhqQm9BOTNLTXlJ?= =?utf-8?B?UlJaNmxqNnNtZXdwMkVlWVhMNVdFaVhvUmk1RXBaM2tvMDNpdklBL1gzcVBt?= =?utf-8?B?UWJDNWtqL3RRd3JQM3RqUEV3c0tBOGhFOFg0KzhxeklYajFNRUM1MzVDUUdr?= =?utf-8?B?MWhlWVhUWUhkWk14Wm1tS1VlS0dwak1tMEhXZW9mY3RMeVE4bXQ3ak5Ealp4?= =?utf-8?B?cWtjb2pVNHVHcktSQURWZHYyK3BMVEF3L0pEQ3dJVWJEQTh1ZmQ3MVhzYlph?= =?utf-8?B?OVpwYTNRKzY2cHFnQnF3eG5IM0EvZXdiSXd1Qlh4UU5WQUhLVXJZSkNGVEZI?= =?utf-8?B?RFN2aEQ0cEI0dDBRRmV5VVpseDVISFM3SDdPZGwzOEU5TVZkODhYdHpaRW5D?= =?utf-8?B?ZVE1R001OWYvU1U2WFFvS3RvM3hXblFjeXhITXJDQ2RoeXF0eEQ4WnM5d1NL?= =?utf-8?B?RW8zYlZWVWFwT0VTQVp2eWRqQ0NadmdoRStJV1ljcGt4SjlWVk9ralYxQzlj?= =?utf-8?B?TnZWM08vc3AvbUlMVmhCbytaTjBXTTFZandzM2VkWFdEZm5WN2FVb2hNOHI5?= =?utf-8?B?RytFTHlMdFFRNjN3bDgrOVZQWU1SKzIwczRqL0w3Mkc0bUxReVBuMjZ0ODVu?= =?utf-8?B?VUxBd2MvZTI0MEw0YitRVmhka0JhUTk0dWlXVEt5ckhrNVFGZ3lXeWJMWkZh?= =?utf-8?B?UmMzMGd3SDRFNzlwZXdHNk9MbkxIalFqYXRsb1BMSitEUU5zVGVMTit5dTND?= =?utf-8?B?Wk5XRzBsZm9hQXJDMzhsZjJDNUEyVGs1UEordEI4NFFiZXlQOTdqcUJHR2dw?= =?utf-8?B?SGFob3JqTmk4V25UUnBETHFCRmNVVVVwaE81cnc1bEtDOWl6ajEwSnJLZlJT?= =?utf-8?B?SnQydHN0WEhwTWF4VFRQT2lZMnF3TWp3Nk9JTGJtU3U3YjJ1VWd5azVsbENp?= =?utf-8?B?bDBXZzdVY2JoYkpzdktrOWx2ZUxtRkRDMVJ4YW9DaDdyb2U0NkZNUTNDRmdG?= =?utf-8?B?QzNaTGpIMG00Y1I5bUtqNEEvQ1dGZ092cGQyY1ViczJlQURRbkZGRDJ4NmNq?= =?utf-8?B?TWs4VndSVzcwT2lxbkh5ZE9FZEswaklQeDVDSE1YdDVGaVZORktNak03TTdz?= =?utf-8?B?djlHNkk0N08wanFXbE1mbXpteHBGMDNLWW9iOVlFNU4ycndJdkN2alBiN2p2?= =?utf-8?B?MlBNWWhaQVphUXRrWUJlZkw3WTE0WTh4TWFkZFVtaEhET3pPbkd1blduOHB5?= =?utf-8?B?eThkWVNiU1duaWtrMnRCTEU1bGRheXdDeEUzOUg1dW0wZ01adzd4N0FNMFI1?= =?utf-8?B?VnBEdmlFNmNJakV2eUtCcTZ2a0NZQUs3RXlHdUdBSno3Smc1aExQdnhNdDFo?= =?utf-8?B?K1VJdUVxMzc5OVIxNGY5QmxURlM4aFduRWJoOXpKVTE3RWZMTFlDVUlKbW9l?= =?utf-8?B?SThYNDFmS0RlNGk3ZldNeWhURmgzNTYrcVR0dz09?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 6:Gum9nCs0vqVMVyEHJw2gX4ZL2MSryLYM0T/DHTlJLPSeD8aeICHXp8vfTaDOJEuMCiplElf/t8qc8c+RRWo5eRIYoiwuZRPSw2OZoNZyuq9JRRLajw2SuNq1/sqL95YOYPfqWCZ+Ke1lTBttdkn+8Mi8umVExTQ5wBZg/fmC7GcqancXBeBH5w25Je5KN7ena6hpalatpGHIEHBXvJc2tre56/PCjImyrRPF7B+hk2Hp8B/gju+OhjCS6uuvNhRdFzPYWWh6PQ4ZJXriAAkDEd1VN8x2aBEV8IsFHmKoDMaRY740HeFJBZL4R5YS8KEl0poxjq/HDnIhl+Vber8DmkinspDe4gm7SgjF9exbG8wIGP2kCywVF51ZcfmZGzZzHBL/SVncg07EN6Ml3iDF6w==; 5:Fh3tqg9ApcyDSQWch+MXbfl1J2QvAlJMEoLGWFLF4R3rxqYxgCMn86AyFXAQBjBxLmslXHDKpKVJKbY6AYJcY1dtVGLE5raOqOUKwGOZUh9xP46JWO9zCPNHmQOZ2S88XbcfFcNtgeEPgWkWfpvrCJwPpnyyNklUGBJtaath/6M=; 24:ymVeePQoo5Feqcy1f8zTa04y70d6TkAZoM4kOZ7sBzkLIHtWFhbR6YPgpntIdwPOx0Y9ci3vwi8f14Qt7JSAhgnfYez7sYCKx806PY3KcOQ=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 7:w6CtGTzN3PW+wi/WEimuIyjiQMmfr1ayv7cjdbL4IEA9cqGBJMITYgQY9KF8JqmZRJLGxDzN9RGUSuRB3gUuiBkF5qPVUXb473SR3FD6nKHPGq9F1neN8x6/m2mQvZkNHj5GSNjMRmzV/QITfRhnSn19ReCiYCwBWN/UcCzz6qj8fCxUxyp2Bl8AXzPLu2SS+U7cr/wMhf99ch7aLO0OviCdUsOCJkXGmn3tC5vmeRdJ3S5uwQ6rOyeT0OTaFCm9kq3U1NeFarnMlXVP+q0eOE4PEukaFKADSKBLkqrTvZzRs5/ecNT68jIij2ogPkSrzgS6kmuOA34svcU2JCT2Dg==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2017 11:39:04.0275 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1559
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/P11GQEoOwDjh3BiBKyRYjc24rEc>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 11:39:10 -0000

----- Original Message -----
From: "David Farmer" <farmer@umn.edu>
Sent: Friday, February 24, 2017 7:15 AM
> On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont wrote:
> >
> > I'd remove a few sentences here, as in:
> >
> >    IPv6 unicast routing is based on prefixes of any valid length up
to
> >    128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
> >    purpose use, subnet prefixes of /127 are RECOMMENDED for point-
> >    to-point router links [RFC6164]. The rationale for the 64 bit
> >    boundary in IPv6 addresses can be found in [RFC7421].
>
> The problem is you have stripped out all the implementation guidance
and
> only left operational guidance.  But maybe the the right idea is to
> separate the two, putting the operational guidance in Section 2.4
where we
> are talking about prefixes and the implementation guidance in section
2.4.1
> where we are talking about IIDs.
> 2nd Paragraph of 2.4;
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    and including 128 [BCP198].  However, subnet prefixes of 64 bits in
>    length are REQUIRED for use with Stateless Address
Autoconfiguration
>    (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
>    use. The rationale for the 64 bit boundary in IPv6 addresses can be
>    found in [RFC7421].

David

Note that 4291bis does not use the language of RFC2119 and does not even
include a reference to it.

This reflects the consensus of the WG; to introduce such language now
would, IMHO, open up another can of worms.  It would beg the question as
to why this one paragraph, or set of paragraphs, use this language when
all the others do not.  That is, it will cause us to discuss all the
other places where such language might have been used but was not; 10,
20 50 ...   Well, at a quick glance, I reckon there are about 60 such
places, 60 more discussions?

Tom Petch


> 4th paragraph of 2.4.1
>
>    For all unicast addresses, except those that start with the binary
>    value 000, support for Interface IDs that are 64 bits long is
>    REQUIRED, support for other Interface IDs lengths is OPTIONAL. The
>    rationale for the 64 bit boundary in IPv6 addresses can be found in
>    [RFC7421].
>
> This clearly say that implementations that only support 64 bit IID
lengths
> are just fine, but also says implementations that allow IID lengths
other
> than 64 bits are just fine too.  I think the current and historic text
> actually implies implementations are not to allow other IID lengths,
is
> that what we really intended to say?  A lot of implementations seem to
> allow other IID lengths, are they wrong?  I don't think so.
>
> This also gives strong operational guidance that 64 bit length subnet
> prefixes are expected in most situations.  Reinforcing the 64 bit
boundary,
> however without outlawing the use of other subnet prefix lengths when
> implemented and they could be useful.  This is done without
distracting
> from the 64 bit boundary, by not directly calling attention to RFC6164
or
> the other longer prefix lengths. Since BCP198 and RFC7421 both
reference
> RFC6164 calling it out here doesn't seem necessary, and would
unnecessarily
> weaken the focus on the 64 bit boundary that I'm trying to maintain.
>
> I don't see how this text would require changes in any code, nor does
it
> imply other IID lengths are not allowed operationally, again which a
lot of
> implementations seem to allow.
>
> Thanks.
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
> Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
> ===============================================
>


From nobody Fri Feb 24 04:46:42 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CEA6129DB7; Fri, 24 Feb 2017 04:46:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.922
X-Spam-Level: 
X-Spam-Status: No, score=-1.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pb_1ce5LiEpX; Fri, 24 Feb 2017 04:46:39 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0100.outbound.protection.outlook.com [104.47.1.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB97129DB5; Fri, 24 Feb 2017 04:46:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=YDWa8H3GWWka0Z6J8Eva9t5y14wMKfjeDpaH7tlwByo=; b=U9eIIHRC2VhKO7tPPHP27AQQaefiiIgaT5sJ83eZSJ7ZNCR4CFi4Abp2iBpoM5wfaGVcShcbJ4YZZeVE99N1r956Z94aja/G4nuB/6Z8qwJ+Qhe0uJqClfjT+D8okdsWpSM7CSuR8Ow/f2SXKwpzUMwZMcuS0NWM8uNpA7bZyew=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=daedulus@btconnect.com; 
Received: from pc6 (81.135.210.62) by VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.7; Fri, 24 Feb 2017 12:46:35 +0000
Message-ID: <002701d28e9b$a5d5e820$4001a8c0@gateway.2wire.net>
From: tom p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com>
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
Date: Fri, 24 Feb 2017 12:43:26 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [81.135.210.62]
X-ClientProxiedBy: DB6P18901CA0019.EURP189.PROD.OUTLOOK.COM (10.169.208.157) To VI1PR07MB1567.eurprd07.prod.outlook.com (10.165.239.13)
X-MS-Office365-Filtering-Correlation-Id: e3448856-4bd8-4912-71fe-08d45cb32b5f
X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:VI1PR07MB1567;
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 3:XEfJtBHog6ZkFZmYBjHQGDW2wVU3NgCnbEUwjKlTz7g36FLsHHWKa0rZVEWIP4EUC0JdWPM0Cb1XKljjENpjJ6zLCkCBetDIsETgjgSD5PymrCOfVcAsPLllDqShmCuI5EkFa9gZzLW60umyIEMhhvwUb1rF17ibr2BVaY7KMQ7MXdkf4OohTIEO4YJBiWCzt+hMa+7NJMWtDF6Q4NnhX6ySp1OgrhFJYQUSee/zypA29J3J2zrZPolQdsBZ5cE7DdjTNDv9lBYTr0j8vq+x+g==; 25:QT7zU/7s6HCKpfbea7DdGdrHwm6KsmKQQzHhQXoOQ6VBMjopgBYhtZl1XapXHZCz4hGNG0SxkwNlOYJsbWYwpWTjJaGd7SR7xCx1lBFA878HvDSmSLkMs02ZwMBMWNx6EyZbK3v9mPpmN0vjl2okac11G9MnDG0hckndZycnqbrvSCeXuwmyQmt6HDA39kYF7f4GKbnbmyKrrE18O1TE7jBTznhebtMJX3d7JFb+uX0Mn+7kWTCWvKRALWUk6Fut0UQ98eT+KHTqZv2LlSfUR12/Q53/cMO4rZeNe9h7LDFnQc5Apwdi4LYXRWlzVOpc0JQYD06tVwBFSaVM0Q89B0RvjqqhB4Xwhpho0YhaSBvSdBqZ1nvX3bPqYKpTodaKAjsvcz6KWVgHB5GAjq9AOU2Bx+USiyGYYxVhAJb8INOYqrQlGlmBgdUN0sHw6ipEG3LJQRa+LJQykHhznROBGg==
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 31:SGQd+Qzv5RTdzLsSaB0CO2LFMj/oAFKxLmQb8emcyKjQAIn4Dn4DUt6k9ShqIsispolQoOkUaBW4aS2wjy1V5bW+hsuuPEksbi8/I1KLq+7w5YG2oqSbzBu4rdIQkPXJhw4JtEzyzN6JT6G4iY69GIFOHZ3NakqdTe9pUcyGTWYaBxr/Cvk4Ma22Lb7CorjN9vkLeHg5ERxjumUn7ptoSSkEln47UbBkmQ0sZHWNRZNVeFVDXD3Msj2w4rqbExK5LxGyUvhhFboOuYDULmeFgw==; 4:HeHdXQ2DW/QoEJ8MtIn1nY+XfrmlQfq4iQ/e6afAQ+P1JHpCvaohA2mj/QtIhVNFWgxo9d1DbjpYwL5dOYxrgRMrMN6usO/b2KfnlojonRRHq3RCVamII0atZ+xe9vK8DOKecDnKD2DTPg3OXg1qpjDpYn+sxYURkCwUpmH9CyPpXsPM++FxxAlrXobwBEJFqebKuhFPPLnrGwkst7EbDgRCGvQqA529ga7U7Jtq83BA/H4XJvv+BH08PwWXrG3bnyFNue59PCMD9xlo+S9u5PEffKZmd1GXiSMUSME3VX+S7CtXBdIgMvcjQtE5wpUFaQHAYxoeqEw4fVcykdbXHluTDa4gd1IEilG5/E1/jagE6m8e7RxAabuh7lzVH7xvZtr0omBGs7EI8c3ya1Yl/vTViZId62M3YzoRu+gvuTr+3N8SkcOZfQRmUpeN2RCo5EUH3/oeqqmDWw/MM/NNRvXqRC+5IM6Nty5EeikRrfPuVgUmkNlB7ISrpeYZhqNzM8d+kIP+j2Jhv2o5SNxsXxlwf5shuKGHcwBYPxZhWzR65cC7Vfhs3oU25vWBsl2V8eUyTQ8m35hAGoJ6pArw7AT2Cu1pOU6mcg2PApJPUQ3klmnJgOtYvL0IvlCkl/EtVjJaoyGOKAYIJGzd6W0PYA==
X-Microsoft-Antispam-PRVS: <VI1PR07MB1567377D3C4F2EA9D8D59F15C6520@VI1PR07MB1567.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(120809045254105);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123564025)(20161123562025)(20161123560025)(20161123555025)(20161123558025)(6072148); SRVR:VI1PR07MB1567; BCL:0; PCL:0; RULEID:; SRVR:VI1PR07MB1567; 
X-Forefront-PRVS: 0228DDDDD7
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(7916002)(39450400003)(189002)(13464003)(377454003)(199003)(23756003)(47776003)(230700001)(68736007)(50466002)(2351001)(62236002)(44716002)(2906002)(92566002)(66066001)(61296003)(42186005)(1456003)(230783001)(9686003)(106356001)(4326007)(6306002)(3846002)(84392002)(1556002)(50226002)(6116002)(81166006)(54906002)(116806002)(81156014)(8676002)(81686999)(6486002)(25786008)(6246003)(81816999)(50986999)(6916009)(38730400002)(110136004)(5660300001)(6496005)(229853002)(101416001)(53936002)(44736005)(189998001)(105586002)(97736004)(14496001)(33646002)(4720700003)(76176999)(7736002)(305945005)(86362001)(6666003)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1PR07MB1567; H:pc6; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
Received-SPF: None (protection.outlook.com: btconnect.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?iso-8859-1?Q?1; VI1PR07MB1567; 23:ZvPrJsFGEQXYSpDDPWAAGOhHCGz8on2JYgAmNkn?= =?iso-8859-1?Q?To9puwzy6tmKqdA7xmwVFyXI59iV68BxgK+Bs5TuOh+IoZ72sm5rxSoZVy?= =?iso-8859-1?Q?y57Wtm/On4Ia3/nG50yQ/edVoLIMbbgGXbcawZIcAXjslOWmnacYlTHqAK?= =?iso-8859-1?Q?MbvNDtxVh1fovIgdoJxPivaz1tLmZjV+Vdf/kHtk2HCFk296xT9DPe0siJ?= =?iso-8859-1?Q?O5RQVwiwej5qAbjp4g12DuVkg2zymT/emB3L+H3pug3vMykjVJ11TbNMoP?= =?iso-8859-1?Q?Ml/w4Vf8ZEIPehRT+IzO0pwavyWJkknRvrPi2DJ6WQHY+rnIpxVcvZHU72?= =?iso-8859-1?Q?h43iQDXpKTSstDBRmiLrugjuGIzrcwxHDThDRnNZoUw6yQC9+VhSeZZmve?= =?iso-8859-1?Q?xdw++IW2N+AV3mtbcu9KlXHDvq5LhM/i5BfHrU2Azz+8bt8YTVrTinKXlb?= =?iso-8859-1?Q?1Jq/wkOCbjTKBxMmuSg7zcQKLMxNyLvKUbzA88Q8ReHUfhnl2DMYJ6tp9Z?= =?iso-8859-1?Q?CCz0IvVL3GEBNskbsP732kUGnoHd/1oYTAUrAKfeoepLcFLBgRKUfv8Kxb?= =?iso-8859-1?Q?DqUa8wUELdswuU4AOLNCwZcBOtVbvMBPcGxgOZDLadE21Z5/nMSaWeGfpi?= =?iso-8859-1?Q?92u6Yza0+JPtB072BshTPRm/N6T65YAkhOhP1P4DVcsvZbL6STnDpLHShj?= =?iso-8859-1?Q?nd+YVlZHPsycXdUIGDaZAv7LUOrntJjjm64wbph4WY7cxhurpwKrxhLhVE?= =?iso-8859-1?Q?wOz4lWdhXY9uvnFR4h81bZturvxnqo8hJNNagE+Qdt3qbWc/wF12/eKPf1?= =?iso-8859-1?Q?sW7QlY5pq17b11TO4VfhFsUu7kL3XYk9b5FuA5mktcWaeXnA9ZlOIDJsGd?= =?iso-8859-1?Q?DnAtPWyubQTAqPWJ1ztm7VWVVDVjtNNOd7SbmVO9WaGo5Md8c6A/gLT+Yl?= =?iso-8859-1?Q?vcQpcuhdg813sblr0su/MTXLT6NAQEv/caFJTR8t9c7gTYjChtO51QAl/Y?= =?iso-8859-1?Q?B0KFES8trAEcvOpP/pJVlR718BH1QZhsijeLOpar3anZfTD4mPRd+ifDtE?= =?iso-8859-1?Q?u0nxnojW/YiLLKV2uCRhad4oWz732Z6YsmyjMUSakCe/9xcKzRMBnOqtql?= =?iso-8859-1?Q?SIxltIHd4sd5dPJcV9nVYZyFVs1N5KHSKUEs5o6fdx3rtuKOK2RnvX7zHn?= =?iso-8859-1?Q?OnaMzCT3zE+B5w/9TfuruvuGRl7YDK8SBtNcL2yCdDSEpUASUwG2weo+w3?= =?iso-8859-1?Q?4moohsyaOjil72tzYoWEKO5q5kFPbyk3F7v6H+n+S92hHGrIP5vLoRek0l?= =?iso-8859-1?Q?qfbhnYRy+DZIOx4VTXreu5LNTGP6EstV914oD3TyTIRhdA7D7fBQ5zwbO0?= =?iso-8859-1?Q?yHgV6rJfQHnhnemA430zutMb3jpCAF72yIiVQKg0FIhXf6VGwsVekR1I3G?= =?iso-8859-1?Q?ez2dillDjCFLk/+Kq4cOTufb7uvXdRWCpwKnQ9dRJAhzUR/Jk9cEEOYjWk?= =?iso-8859-1?Q?HzI7hRicBAl2irKSW7gFeJf3tSPDq0lY8lpxQEtIUo4ZOqAdw4gi9BJKoI?= =?iso-8859-1?Q?K4fTDsOD6T3woVOnBBpOe2xzbI=3D?=
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 6:Atmqu8e2yiqbr4QJsDK0aABbBiMSMSKnUBovhCZ3GEXmGADpMdI12tyDODAPKCCozESf3UzaxZTesSpiRNnyLU+FtU9WHLoWJng8AqPV5jrDyf5A3fuZ+adszI9ZMWaK2bJcBIDbSefxp9uKJ8Ep0HAXXbgxsh+yD/0m7uYNhIp2TDzAyrfP4xmT1G7MEvQ2OthA9rntkbaUVhwDOSXAkRWGSWXMs9xJ6wtiBeZXHSLB8+AHNssyumW+I2/ygt0kw5DZVkliQUC4XeKMtP/r3tzQ4pI8HBpqf6oJ4fP/9XDguRQPl9Xu38L3D+9fCgW6lCGGLmdYp0AIi7EtKft+GL/Zc2bhYd4ItR3LFE9TpTPi7NhNRNCLvsoKzpQuuCeHgfD0oBXtnJqGS9tNQXJb5w==; 5:o7mmdNpRVYtlXrZiwK5Ba1/Oo0yxFoQgPrhSVPtVTyYAxrU074KsVcIL/pvOVqfv9uEYuXjqJEqJL0HhXkf1FvG5ceyXPVWRpQqWocBDv5XwPfI1CUM2AiIXRJoN1WP3cZWOwLNgspZSkmtrlc2bxg==; 24:DuraecbcD8qgpOoXWzCy10YeF9EhBumImZ1/HdIzZ4Y1SES9xSb2zN82k+mT7+OoeFVwA9UXJ6kkX1LgBMtXsYtxGAltsgNdqpN4BECkb0s=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; VI1PR07MB1567; 7:b8uKloCd2xWdXMXje5UhXRzXXnE/EBP9ysqjZCWLX3KRMqN3421Ab1VL4YHlIB92ABabmBq7xjaIx4iHCuZ3WtMRdVS3u8giobnIPgF8IJfe0YkThwyoHgUh7j2j8yCE+eD/o+JE+Snq1p0BtmVgxU62euh3gawIME18eWX/85ZC/OBlRDmswwpZkgNfNwUYV62ANlBYLZpFOYa54yQoPqTnpYi4Kemc6zploOLfbQgUrzlCiA1VbJvSV96Jq9SUu2gHcuN8cEKc0EyPALUmKTo4J+t3tUkRBa4Pe1xc9rM3jKhSGdXUWh3IZevQxA/HppjOofI5pnvyysC3YUxdPA==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 24 Feb 2017 12:46:35.5315 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB1567
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EPjzlxdtN8SGhzXpTr93Agd2DfU>
Cc: john-ietf@jck.com, alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 12:46:41 -0000

s.5.2
" ...and that it (3) not
   cause the NID to exceed the length limitations defined for the URN
   syntax (see Section 2). "

I struggle to see anything in Section 2 that relates to a length
limitation.

Tom Petch


----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <urn@ietf.org>; <alexey.melnikov@isode.com>;
<barryleiba@computer.org>; <draft-ietf-urnbis-rfc2141bis-urn@ietf.org>;
<urnbis-chairs@ietf.org>
Sent: Monday, February 13, 2017 3:08 PM


>
> The IESG has received a request from the Uniform Resource Names,
Revised
> WG (urnbis) to consider the following document:
> - 'Uniform Resource Names (URNs)'
>   <draft-ietf-urnbis-rfc2141bis-urn-20.txt> as Proposed Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-02-27. Exceptionally, comments may
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    A Uniform Resource Name (URN) is a Uniform Resource Identifier
(URI)
>    that is assigned under the "urn" URI scheme and a particular URN
>    namespace, with the intent that the URN will be a persistent,
>    location-independent resource identifier.  With regard to URN
syntax,
>    this document defines the canonical syntax for URNs (in a way that
is
>    consistent with URI syntax), specifies methods for determining URN-
>    equivalence, and discusses URI conformance.  With regard to URN
>    namespaces, this document specifies a method for defining a URN
>    namespace and associating it with a namespace identifier, and
>    describes procedures for registering namespace identifiers with the
>    Internet Assigned Numbers Authority (IANA).  This document
obsoletes
>    both RFC 2141 and RFC 3406.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/
>
> IESG discussion can be tracked via
>
https://datatracker.ietf.org/doc/draft-ietf-urnbis-rfc2141bis-urn/ballot
/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>


From nobody Fri Feb 24 05:13:19 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AEDB129739; Fri, 24 Feb 2017 05:13:18 -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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wce4dxZqxr6X; Fri, 24 Feb 2017 05:13:16 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 2F88E1296F9; Fri, 24 Feb 2017 05:13:16 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DAEE2AB; Fri, 24 Feb 2017 14:13:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1487941993; bh=0jsdXUHbLZ6uEJzxsNu6KN/Q4ecYEuVN2Ve+Uomh2oc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=sDbx+IxuNqn8hOSjU/MgaEz+mHtTGqR6B8Yku2Rrsvs8TTycU05nQUli6VMmAfpKw z7ZTrU8Q9q7y/afRXgyeuB1JGAfq/iQb92aXYMKxz3ogwC7fw48+Kp/sJqXNHGLhSp mwNNu/uysPT9cjEkP4wp3BREVG0EcpfxbcbKO3q4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D8A6AAA; Fri, 24 Feb 2017 14:13:13 +0100 (CET)
Date: Fri, 24 Feb 2017 14:13:13 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IPv6 Operations <v6ops@ietf.org>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
In-Reply-To: <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr>
Message-ID: <alpine.DEB.2.02.1702241326380.15705@uplift.swm.pp.se>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/drKs5t4fbPxWzdIAiKDzZdYUzYk>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 13:13:18 -0000

On Fri, 24 Feb 2017, Pierre Pfister wrote:

> At least Linux, Windows, Apple, Cisco, and probably all mature IPv6 
> stacks, would let you configure prefixes of length different than 64.

I just came back from PTO not reading IETF email for 5-6 weeks, and read 
up on this thread.

I just want to state my opinion that whatever text we come up with should 
reflect current operational reality, in that SLAAC A=1 only works on /64, 
and that people use all kinds of subnet sizes when manually configuring 
interfaces.

If current code doesn't treat 000::/3 in any special case, then documents 
should reflect this.

Mandating /64 only for any IPv6 use case doesn't reflect reality as I see 
it. I don't want to see A=1 /64 SLAAC requirement relaxed either.

I just want the -bis document to reflect what is currently in the field 
and we know works. Nothing more, nothing less.

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


From nobody Fri Feb 24 05:25:27 2017
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11FC11296E1; Fri, 24 Feb 2017 05:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sfKFz_yduhG1; Fri, 24 Feb 2017 05:25:21 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 E5C5F1293E3; Fri, 24 Feb 2017 05:25:20 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 10171AA; Fri, 24 Feb 2017 14:25:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1487942719; bh=59aba0rlvWNo6J7egXyM1QvRcZ1fEG7kkQ0TPirLLzE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=0wPkWnpHAA7KM7viAfsdosqBDu1wQ6Xkug4Tk4LP8SM2yK4ZP1Mq1JCG+kGYCij/E thBwiQejFSQ5yDjZTSqxkjuhkKNtAfnhzQrqyeK38TgcjpPfiU2GOZa79aDX++Vw2B yKbewg7D8XeiGIkoTe1tjUZnC1ImN4QZS7sKvQnU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0E3B3A8; Fri, 24 Feb 2017 14:25:19 +0100 (CET)
Date: Fri, 24 Feb 2017 14:25:19 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: draft-ietf-6man-rfc4291bis@ietf.org
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
In-Reply-To: <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr>
Message-ID: <alpine.DEB.2.02.1702241423100.15705@uplift.swm.pp.se>
References: <20170221001940.GB84656@Vurt.local> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com> <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f1MLoEklS-_gXGMkHp_w9wYRDpc>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 13:25:22 -0000

(posting this in the last call thread as well)

I just came back from PTO not reading IETF email for 5-6 weeks, and read
up on this thread.

I just want to state my opinion that whatever text we come up with should
reflect current operational reality, in that SLAAC A=1 only works on /64,
and that people use all kinds of subnet sizes when manually configuring
interfaces.

If current code doesn't treat 000::/3 in any special case, then documents
should reflect this.

Mandating /64 only for any IPv6 use case doesn't reflect reality as I see
it. I don't want to see A=1 /64 SLAAC requirement relaxed either.

I just want the -bis document to reflect what is currently in the field
and we know works. Nothing more, nothing less.

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


From nobody Fri Feb 24 06:09:30 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F2F1297AC for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:09:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.352
X-Spam-Level: 
X-Spam-Status: No, score=-5.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 TZ3p0wTpXeS1 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:09:27 -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 748A51294F5 for <ietf@ietf.org>; Fri, 24 Feb 2017 06:09:26 -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 v1OE9NZf031113; Fri, 24 Feb 2017 15:09:23 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AF9E020B774; Fri, 24 Feb 2017 15:09:23 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9F1EE200C3F; Fri, 24 Feb 2017 15:09:23 +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 v1OE9N80002212; Fri, 24 Feb 2017 15:09:23 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <75196cfa-5476-0c7b-7612-ea2e446fc6f1@gmail.com> <B4A4FFFD-A90D-4C26-BDBD-75555840CA22@employees.org> <m2wpcqeuot.wl-randy@psg.com> <44F7BEDA-CF11-4E1E-BA6F-88794DEC1AF7@employees.org> <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <047994c3-9cce-12ce-55bb-bf3ae3369b57@gmail.com> <20170221225857.GE32367@Vurt.local> <f84828c0-7d37-6c56-b1a6-6260227b4f44@gmail.com> <efd19030-6a81-3e14-d294-94e4605f15a1@gmail.com> <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com>
Message-ID: <1c69ff2c-96ba-f672-7e31-8d2a07368f52@gmail.com>
Date: Fri, 24 Feb 2017 15:09:14 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com>
Content-Type: multipart/alternative; boundary="------------C5C854C822D3CE8A87288B50"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T4Qwr9uAWqlXecZ-19iss0kIp9Y>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 14:09:29 -0000

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



Le 22/02/2017 à 21:04, Brian E Carpenter a écrit :
> On 22/02/2017 22:41, Alexandre Petrescu wrote:
> <snip>
>
>>> Well that does two things: configures a 128 bit address (as Chris
>>> points out, *all* addresses are 128 bits, duh) and associates a
>>> prefix length with it, which afaik is optional.
>> The prefix length is not optional.  There is no system out there on
>> which one could configure a 128bit address without explicitely telling
>> '/128' or '/64' or '/something-else'.
> Wrong. Sorry to get all technical, but on Windows:
>
> C:\windows\system32>netsh interface ipv6 add address ?
>
> Usage: add address [interface=]<string> [address=]<IPv6 address>[/<integer>]
>               [[type=]unicast|anycast]
>               [[validlifetime=]<integer>|infinite]
>               [[preferredlifetime=]<integer>|infinite]
>               [[store=]active|persistent]
>               [[skipassource=]true|false]
>
> The [/<integer>] looks pretty optional to me. I just tried
>     netsh interface ipv6 add address 12 2001:db8:dead::beef
> and now I have three addresses:
>
> C:\windows\system32>netsh interface ipv6 show addresses
>
> Interface 12: Wireless Network Connection
>
> Addr Type  DAD State   Valid Life Pref. Life Address
> ---------  ----------- ---------- ---------- ------------------------
> Manual     Preferred     infinite   infinite 2001:db8:dead::beef
> Public     Preferred      1h54m9s      54m9s fd63:45eb:dc14:0:28cc:dc4c:9703:6781
> Other      Preferred     infinite   infinite fe80::28cc:dc4c:9703:6781%12
>
> When I try to ping 2001:db8:dead::cafe, I see what I expected in Wireshark:
> neighbour solicitations from 2001:db8:dead::beef to ff02::1:ff00:cafe.
> In other words, the new address is treated as on-link. I can't find any trace
> of an associated prefix entry.

Brian, I just discovered that one can see the associated prefix entry 
with "netsh interface ipv6 show route".

In this here setting I receive no RA.

When manually adding an address w/o specifying the plen on an interface 
it adds a /64 'connected' route and that's wrong.  The wrongness is in 
that '/64'.  Nobody told it '64' yet it assumed 64.  It's not wrong in 
adding a 'connected' route, but it's wrong in making that 64.

It's wrong because I may not want the entire 1::/64 to be 'connected', 
but maybe much less, especially when I manually configure.

Whereas in IPv6 it adds a /64, in IPv4 it adds a /8.  That '/8' comes 
from the fact that "1.1.1.1" is a class A; but in IPv6 there are no 
classes, right?  So why 64?

netsh
  interface ipv6 add address "Connexion au réseau local" address=1::1
  interface ipv6 show route



(warning: careful on a managed computer as it resists reboots and needs 
manual fixing afterwards).

Alex

> Maybe Linux is different.
>
>       Brian
>


--------------C5C854C822D3CE8A87288B50
Content-Type: multipart/related;
 boundary="------------DFBB74C3EA653420D206ADE3"


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

<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">Le 22/02/2017 à 21:04, Brian E
      Carpenter a écrit :<br>
    </div>
    <blockquote
      cite="mid:252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com"
      type="cite">
      <pre wrap="">On 22/02/2017 22:41, Alexandre Petrescu wrote:
&lt;snip&gt;

</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">Well that does two things: configures a 128 bit address (as Chris
points out, *all* addresses are 128 bits, duh) and associates a
prefix length with it, which afaik is optional.
</pre>
        </blockquote>
        <pre wrap="">The prefix length is not optional.  There is no system out there on
which one could configure a 128bit address without explicitely telling
'/128' or '/64' or '/something-else'.
</pre>
      </blockquote>
      <pre wrap="">Wrong. Sorry to get all technical, but on Windows:

C:\windows\system32&gt;netsh interface ipv6 add address ?

Usage: add address [interface=]&lt;string&gt; [address=]&lt;IPv6 address&gt;[/&lt;integer&gt;]
             [[type=]unicast|anycast]
             [[validlifetime=]&lt;integer&gt;|infinite]
             [[preferredlifetime=]&lt;integer&gt;|infinite]
             [[store=]active|persistent]
             [[skipassource=]true|false]

The [/&lt;integer&gt;] looks pretty optional to me. I just tried
   netsh interface ipv6 add address 12 2001:db8:dead::beef
and now I have three addresses:

C:\windows\system32&gt;netsh interface ipv6 show addresses

Interface 12: Wireless Network Connection

Addr Type  DAD State   Valid Life Pref. Life Address
---------  ----------- ---------- ---------- ------------------------
Manual     Preferred     infinite   infinite 2001:db8:dead::beef
Public     Preferred      1h54m9s      54m9s fd63:45eb:dc14:0:28cc:dc4c:9703:6781
Other      Preferred     infinite   infinite fe80::28cc:dc4c:9703:6781%12

When I try to ping 2001:db8:dead::cafe, I see what I expected in Wireshark:
neighbour solicitations from 2001:db8:dead::beef to ff02::1:ff00:cafe.
In other words, the new address is treated as on-link. I can't find any trace
of an associated prefix entry.</pre>
    </blockquote>
    <br>
    <font face="Courier New, Courier, monospace">Brian, I just
      discovered that one can see the associated prefix entry with
      "netsh interface ipv6 show route". <br>
      <br>
      In this here setting I receive no RA.<br>
      <br>
      When manually adding an address w/o specifying the plen on an
      interface it adds a /64 'connected' route and that's wrong.  The
      wrongness is in that '/64'.  Nobody told it '64' yet it assumed
      64.  It's not wrong in adding a 'connected' route, but it's wrong
      in making that 64.<br>
      <br>
      It's wrong because I may not want the entire 1::/64 to be
      'connected', but maybe much less, especially when I manually
      configure.<br>
      <br>
      Whereas in IPv6 it adds a /64, in IPv4 it adds a /8.  That '/8'
      comes from the fact that "1.1.1.1" is a class A; but in IPv6 there
      are no classes, right?  So why 64?<br>
      <br>
      netsh <br>
       interface ipv6 add address "Connexion au réseau local"
      address=1::1<br>
       interface ipv6 show route<br>
      <br>
      <img src="cid:part1.E285A6C8.4C353844@gmail.com" alt=""><br>
      <br>
      (warning: careful on a managed computer as it resists reboots and
      needs manual fixing afterwards).<br>
      <br>
      Alex<br>
      <br>
    </font>
    <blockquote
      cite="mid:252c3c52-a158-f65a-bc6f-7c4686db7544@gmail.com"
      type="cite">
      <pre wrap="">
Maybe Linux is different.

     Brian

</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------DFBB74C3EA653420D206ADE3
Content-Type: image/png
Content-Transfer-Encoding: base64
Content-ID: <part1.E285A6C8.4C353844@gmail.com>

iVBORw0KGgoAAAANSUhEUgAAAoYAAAByCAIAAABBdIcIAAANyElEQVR4nO2dQXbkvApGvbRe
Wi/Nwx72oPeTN3jnz3EkQCBhmaq6d+TIGD4QllqdpHL8/v37169fBwAAAGzn398/X19f//7+
+ff3z7FnSz7/Y+7BfEGOoPvjHkn5ivpDnh+sAADAR5G2JYeW7A1bcsoW8h3xwX8N3ORhYlde
UbKNV9EJANCTsyVHl+y7l/gs/y+0FfUMxfuze5U6vIpOAAARYUs+f3K1FsfPDtv+iJ8+PXGn
9VxHxFtOPRPjE/k2ghuR2rUdyKnfae+sYe9kwn9/bTziKQgAwIOoW/L/b3uu+y+d9uIqbOBc
mqf1iMLspTxaK3+yorHoyo5l6/f4OZT5cuboSbnx6ffviWXYAwCUIrwli6u8ttJ5xv2rpBHU
vzQb+u2dwHAVMnYmKzoUw2ka/NqMiCtxezM708Z+Ii8x1tlhiwEAeIrJU3KDvdL1d51ubT9z
S7NTodOPJ5HpbcBZN4+eUEGy4vZm/kzn8gqlCQBQjeT/uJ5YOv0rpt/Jih4jou1nom42vbHt
NlRkv3PtlsfemW9KnT3aQvUHANhMYEs+lKW/uSUOik7EECJnx+HbckJ6PMa9815GyJU/3368
f8TwMzTW7EUNTv+elI3i2P7FELb9UAwAwIM88FEhMA2bCgDAG8OW/DJw1AMAeG/YkgEAAErA
lgwAAFACtmQAAIASsCUDAACUgC0ZAACgBGzJAAAAJWBLBgAAKAFbMgAAQAnYkgEAAErAlgwA
AFACtmQAAIASsCUDAACUgC35o6n2Ryyq6QEA2In695L9f3fIMLOdbF5/o3m9OuIfEjYMcuNO
1Fk0rtM/UBbPOpPeKsP363PQ6p+72D5S4f2bhXxKvorwCLJtiiyp58+/eP/278+1mfrGMiYl
K7QdyHikH7TvAswtQYkR6cb0df6UNvi5Z+ew15+beHJLfoRSYm7llPA8khV63efnTBYs8tSW
nNLn70Hullxh3XhkTgNbstF/9rrfD2rG4vh1ZL1GQ4V9LEPS/gnzc0r0twz7xdDNtTGPWlBN
hqHf0FB8vmAFcXKN5rcf9EcUW9roT38rNp41V4akuXEtKcNPI3g4PiyCJ+75E23c70eLq8nz
5zXM98q/v39+/0e7JTdetGv71jAxj5OmZJ7ENMTHPWk2GgxvRbgKPnz6s9L52T6C/+stu+DG
jPfjTp/rCUI1jGbo74p9Mhex79Jh7/lDD1vX0+fR6yP4nopijPENfkK1Osx8ryO2pOi1xq8L
8ik5lJL4bKjEYhX6StlZGYRSE68NnaXQ5mhY5/TQzXgzj9N6jKnsndSfL1ihn9nriHZ3pRnE
BjbiXg1ESUYI8dr/vthviubndL+noei2H6MsRrKeOkTzHWbU+HEaa9l98/0f119fXyW2ZFGl
JxMnodTE60Qxt6KVd0OdnTM+DGrrMbw5+wreBnvZ0e6uNEbvv3+/tAVElOQJYfgXnzLGo+/d
UPBNcT1+PCEm4g79DOfCjivyvR+r30seShkqm5gq/yxGscV4JHmmoQJaLp46L+YV6s7peTc6
TfNZeb5gBaMZ+rspfR59v64GztDa48PeXrnWtA3fIy0jw/nQ54SfI1grv3K//ukcD/GUfF4Q
1TTZNhd9qr1Dz7joxE5myNCVrf8OSfchar5ei/rX89Kce4I6i3x2HLP5whswbLlDWq+uNtNB
xS+Nfg7F7ZvcyEuLGx3XjJ1+ND1DnX0423/vUHxkOl9PHUQZIVc98in5M9FK+YwaAPhsWH8+
EPl7yR9Fyj9tAAASYf35TDglAwAAlIBTMgAAQAk4JQMAAJSAUzIAAEAJOCUDAACUYPB7yf0v
YNUZj1JNf3T8qXw/rc6MPzv+VL89FZfxzxzX4JQMAABQAr6XDAAAUAJOyQAAACXglAwAAFAC
TskAAAAl4JQMAABQAk7JAAAAJVB/L/nbYvh7VK/Cg3k5fyNtT1z7l+Qe0fkdetF+mNR7dDKk
sNgMdzdVlvOoH3t9SGTd/4Pv9X1xhVNyE+ltFrJrER+ZyM0Rr+G0a+ORzXhC223pyfdtmhkW
SemEu9spy3/Uz7ZXZt35RGor4ZqgdxTH+vSuJvyrc0rsF/BIOM+E5srTKtyPO6ejeQ16e0++
b9PMME3i6393O2X5j/rZ9sqsOw95eKqeIdRTcrMCXqU0gs6f3CR0nVOiv6XZN+P9teZHfHAz
hmbRJiti79Aet73N2Xtyh08jpRPsV0lrWm090W7Z4/64tmaP/VxefdBoXk6pfueeuNcRIzUt
9PR4+DOue03adTWuiRyK1GiOoTo8VZwmbj+z9vgjIoe3QvYP5gU1SWmGlDVk7pE5/86sxaXg
2WtRkpiRpw5R+2tcTYnHp+fa+l5yEzjquhrG9IhVnrs2ZuuR4thB68yjFnF9/FX6E3aS0gn9
knJMrZOLS80wo944lJc9fnasJDXMZSjJWeeh/ustp7xhHTxxBz9x7dE0V8r9aNMTzWs69/3F
CUnKncemz5zjnsGo/av0J+wkpRPE1ppYK0KPTLyz4rPOvIZ3NeNoHebe097SWeehfuPW0I8n
F2088BPXuaXcT1Ze03XYXJx0/RPRtSJ4imNrsO3vywveg5ROEFtrog9DjyT69+Q1JzLxOirV
U4eJutlBJ/LSrmO/l3xe8JSgFJ68Dse0afaHUp9mfFuJjKAenRsU2jo1DYZ9NF/4QLJext6P
2IraI4ar6+Dxc7Vp7A/3+ty79eTlvDUc13R69Eel2sn69UeTnchLHOfTuwAAnsS/CcHbw2dc
AwA8RvRoCO8Np2QAAIASzJyS+dccAABAOuFTMv/BAgAAcAeBUzLf8wAAALgPTskAAAAlCH8v
mS0ZAADgDjglAwAAlIBTMgAAQAk4JQMAAJRg8ieu2ZgBAABy4dO7AAAASsBnXAMAAJSAUzIA
ABTik78xGvt7yS/Ng3k99Q14Ma79MwGJOm9N1tb5Nk0L6xhNkuK82s/WlBIzQR39d0+u6F84
JT+4dd3KNfkHN8hHwmnXxiOJ0bPwpHA8NLlQE60TUjrE+Vptpo6SCQqKv1tS4189JRdstUVO
if0CHgnnmdAseXZ5tVvDGfm+6zF7m6aFabROyOqQxgMt967cPbONf/WULK6AYjefP7lP+iKn
RH9Ls2/G+2vNj/jgZgzNok1uxH68v2X3j0f/4d624XO4r9uHfRhaT8T+N+zFLyf8iPZ2ykMB
TidaLk79c/n6dYoP5uoU/Vun5MaRltJ0qpu5JnIoUqM5hurwVHGauP3M2uMpQRNd2frTo8NL
o3XCeod4PN+0nnx/KWpwvhcr78uin0Z/n8tifbJ0isZZerRB63vJ54VFKRUYVvaarGjgue79
aAL2YAe9bx6zku39+OtfthVhG1ob3Nfh62vI9VprZqPDm/FoXANRz4qf6yNGvqLbof26TtF4
wqemU3xw8BPXYu3mZD2OVtloXtO57y9OSFLuPGoe7L5sxg1LT5QJ2fBm3Nchz64n2ntkCJuO
letHMxs+a+R1k85hXI/PoU0zGPiJ6/RUN5OV13QdNhcnXf909H5cK444QYZnjw18Mrd2iNiK
We+d0ediLC21Cf/+ZCf8eGTvvI6qTY/bDMZ+L/m8MJRYDU9e13EjL9H+UOrTjG8rkRHUo/OO
uFE/nhDRu/AhaH2Y+zL6369eg33t8SM+bqc81ONJVovrcSWKsW9Nj6/oPIL1XNFzNeDTuwAA
AErAZ1wDAACUgFMyAABACTglAwAAlIBTMgAAQAk4JQMAAJSAUzIAAEAJOCUDAACUgFMyAABA
CTglAwAAlIBTMgAAQAk4JQMAAJSAUzIAAEAJOCUDAACUgFMyAAAUwvOXE9+V2N9LfmkezEv7
O5qPxNX+CGhzNyX6upMJP739MNn36HAQ0SY3q8mrtVApMRPU0X/35Ir+hVOyuILfIWgz1+Qf
eYs2R7yG066NRxKj3+3HbldPHd6myaFBm9mUGa/ZQnWUTFBQ/N2SGv/qKblgqy1ySuwX8Eg4
z4RmybPLq93qx53T9G2g2Xvq8DZNDt/Y/bA+42K7rjiEmtw9s41/9ZTcrHTXh42ls3JTnhL9
Lc2+Ge+vNT/ig5sxNIs2uRH78f6WPe6P4rf31ARenfu63fBgrBv+cduP+OWEH9HeTnkowOlE
y8Wpfy5fv07xwVydon/rlNw40lKaTnUz10QORWo0x1AdnipOE7efWXs8JegdfqJF7m8l5gs1
0SZ3fdI9nu+4Pn4uZcNXYML/kEU/jf4+l8X6ZOkUjbP0aIPW95LPC4tSKjCs7DVZ0cBz3fvR
BOzBDnrfPGYlq/lZH3+VvoUVon2S6/m+9UQcFIVF4xqIelb8XB8x8hXdDu3XdYrGEz41neKD
g5+4Fms3J+txtMpG85rOfX9xQpJy51HzYPelNu50HrJ/lb6FFew+TPT8/WXWGmIr1N4XQ9h0
rFw/mtnwWSOvm3QO43p8Dm2awcBPXKenupmsvKbrsLk46fqno/fjWnE8RbO12fb35Qs1sfsw
0fn3ddZ7Z/SnGEtLLav/E9+joeyd11G16XGbwdjvJZ8XhhKr4cnrOm7kJdofSn2a8W0lMoJ6
dN4RN8WP5tCwj9YB3oCJfliM4hn0X3v8iI/bKQ/1eJLV4npciWLsW9PjKzqPYD1X9FwN+PQu
AACAEvAZ1wAAACXglAwAAFACTskAAAAl4JQMAABQAk7JAAAAJeCUDAAAUAJOyQAAACW4npL/
B/CEg+qflizpAAAAAElFTkSuQmCC
--------------DFBB74C3EA653420D206ADE3--

--------------C5C854C822D3CE8A87288B50--


From nobody Fri Feb 24 06:09:50 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE411297CF for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 PG3_uVifpqDU for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:09:48 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 3BCBE1297D0 for <ietf@ietf.org>; Fri, 24 Feb 2017 06:09:48 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1OE9kdv038284 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:09:46 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5A72A207F84 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:09:46 +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 50F1220B787 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:09:46 +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 v1OE9k3i002379 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:09:46 +0100
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: ietf@ietf.org
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr>
Message-ID: <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com>
Date: Fri, 24 Feb 2017 15:09:36 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SbJFWjiPIdSqEtmwtZSs8dKouY4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 14:09:49 -0000

Le 24/02/2017 à 07:58, Pierre Pfister a écrit :
>
>> Le 24 févr. 2017 à 04:27, Lorenzo Colitti <lorenzo@google.com
>> <mailto:lorenzo@google.com>> a écrit :
>>
>> On Fri, Feb 24, 2017 at 7:43 AM, Pierre Pfister
>> <pierre.pfister@darou.fr <mailto:pierre.pfister@darou.fr>> wrote:
>>
>>     > The thing is this is not new text, it has been in RFC4291 for 11
>>     > years. c.f., 2.5.1.
>>
>>     And during those 11 years. Nobody implemented this rule specific
>>     to ::/3.
>>
>>
>> I can implement it today in some of our code if you like :-).
>
> Good luck getting that upstreamed ! ;-)
>
>> But it seems unlikely to make a difference, since the rule only
>> applies to unicast addresses in ::/3, and no such addresses have been
>> released to the RIRs. That in turn is unlikely to change until we run
>> out of 2000::/3, and even then we'll likely move on to allocating
>> addresses out of 4000::/3 instead of from ::/3.
>
> So what you are saying is that all currently assigned unicast addresses
> are out of the ::/3 prefix.
> Meaning that, according to proposed standard, I should not be able to
> configure on-link prefixes of length different than 64 with currently
> assigned unicast addresses.
> At least Linux, Windows, Apple, Cisco, and probably all mature IPv6
> stacks, would let you configure prefixes of length different than 64.

A question to Windows is the following: what prefixlen does it set when 
the end user manually assigns an address on an interface without 
specifiying a prefixlen?

Is that 64?  If yes then it's wrong.

Alex

>
> - Pierre
>


From nobody Fri Feb 24 06:21:39 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23EA8129DC3 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:21:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dwPve_jmlTzs for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:21:35 -0800 (PST)
Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::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 65754129DBE for <ietf@ietf.org>; Fri, 24 Feb 2017 06:21:35 -0800 (PST)
Received: by mail-it0-x232.google.com with SMTP id h10so21233358ith.1 for <ietf@ietf.org>; Fri, 24 Feb 2017 06:21:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=VyNuNxaeYKrNJvMa507R3Joi2Fip0191vXyF/X93Drw=; b=SmjG1Zqb423XLTKjA/1aPahupq7HRjNHaq2tApmlWD6g+GMaTrGYSfAfgnpXbXf16j z0IUoq4ZFq8p5eptIdtAojt/KO0tQ7GUKOyaHIhaQO9BIxukukKsJqKTXoXxLWn8y4vn fXVS7wcf4/cZLtPcF/1AoryxbZjd1zGB1rjag10P+qmZRjDMl0IPJKF2rcOt8mFuevuD l+mpaQqYidmMsPM9DkyA8NEBzkByNpCMBNJ860QGH4nwaVmakryDQsX2dtTzrf/ob3Rn 42RtPahcu6fM7ZQtFacgSaNvb/fKy67pUCqgCA7dmTtYO2Nd+zp+E+Ex4dOE4gn1p6Hf s3SA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=VyNuNxaeYKrNJvMa507R3Joi2Fip0191vXyF/X93Drw=; b=g1Pqe4z4mwL8wnHdcggHnwznuH3PYN8pO42V/kB1PJZa5Y0NzAg7/9FJuVdztg6aK0 vP56lUwvjIrrI7ybTfgrxJDntK0k4/2LVhdMGieIiZvXdQhexfqGuWMkjiTrIo3qo4gp 0gxrzzN+ytyPFjlsPNABnfRBfu8aeJgCt+c1igquhGlrIhcjoGMK9gqSGNJDxGGm8L9l iSKgjOSEX2dX9qySpTG5/on8P3DqvSBLQeT8dYDde7Gl6p2VAtsDb0a2csTzlGSr3Owe dPRPbm/7faCRZJpMI7qlNmSkmewjJYDqLylqxG3+7jt51Q0669vG92cIIZgGUIn4f8sj GFZg==
X-Gm-Message-State: AMke39mUcLA62htrwoyYued+IVqmnxUidksF+hC4D5aBxWjz7HulLKTV+tg4ox5RBAAuQA==
X-Received: by 10.36.84.138 with SMTP id t132mr2682377ita.100.1487946094298; Fri, 24 Feb 2017 06:21:34 -0800 (PST)
Received: from aither.local ([2601:282:4202:67d3:415d:7bd7:5f13:c752]) by smtp.gmail.com with ESMTPSA id b88sm743104itd.21.2017.02.24.06.21.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Feb 2017 06:21:33 -0800 (PST)
Subject: Re: Last Call: <draft-ietf-urnbis-rfc2141bis-urn-20.txt> (Uniform Resource Names (URNs)) to Proposed Standard
To: "tom p." <daedulus@btconnect.com>, ietf@ietf.org
References: <148699853178.24969.7610250025952470052.idtracker@ietfa.amsl.com> <002701d28e9b$a5d5e820$4001a8c0@gateway.2wire.net>
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <97af6b70-7f89-1374-7f22-d2e92f435c87@filament.com>
Date: Fri, 24 Feb 2017 07:21:33 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <002701d28e9b$a5d5e820$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CmJgWRTxZCh2AokEqgcehc6T4t8>
Cc: john-ietf@jck.com, alexey.melnikov@isode.com, barryleiba@computer.org, draft-ietf-urnbis-rfc2141bis-urn@ietf.org, urnbis-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 14:21:37 -0000

On 2/24/17 5:43 AM, tom p. wrote:
> s.5.2
> " ...and that it (3) not
>    cause the NID to exceed the length limitations defined for the URN
>    syntax (see Section 2). "
> 
> I struggle to see anything in Section 2 that relates to a length
> limitation.

The ABNF in Section 2 has:

      NID           = (alphanum) 0*30(ldh) (alphanum)

Peter


From nobody Fri Feb 24 06:50:34 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 065D0129697 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:50:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 ka_ndGcX4Mbj for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:50:30 -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 79BCC129DD0 for <ietf@ietf.org>; Fri, 24 Feb 2017 06:50:28 -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 v1OEoQFF024277 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:50:26 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C439420B84A for <ietf@ietf.org>; Fri, 24 Feb 2017 15:50:26 +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 BA7FF20B843 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:50:26 +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 v1OEoQ6j017128 for <ietf@ietf.org>; Fri, 24 Feb 2017 15:50:26 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <a6a203dd-13cf-37c5-e1b6-8ea61a634550@gmail.com>
Date: Fri, 24 Feb 2017 15:50:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Anicrkp6scdPWNfYPBH0ZRvOROo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 14:50:32 -0000

Le 23/02/2017 à 23:43, David Farmer a écrit :
>
>
> On Wed, Feb 22, 2017 at 10:16 PM, Lorenzo Colitti <lorenzo@google.com
> <mailto:lorenzo@google.com>> wrote:
>
>     Help he understand, then. There is widely-deployed code that assumes
>     that the interface ID is 64 and does not work on anything other than
>     64 bit prefix lengths. Currently that code is correct on all unicast
>     space. If you change RFC 4291, won't that code be incorrect?
>
>
> OK, what if we said something like this;
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. However, all implementations of IPv6 are REQUIRED to
>    support an IID length of 64 bits, other IID lengths are OPTIONAL.
>    Subnet prefixes of /64 are RECOMMENDED for general purpose use,
>    subnet prefixes of /127 are RECOMMENDED for point-to-point router
>    links [RFC6164], other subnet prefix lengths are NOT RECOMMENDED,
>    as their use could be incompatible with some implementations of IPv6.
>    The rationale for the 64 bit boundary in IPv6 addresses can be found
>    in [RFC7421].
>
> I'd prefer other IID lengths to be RECOMMENDED for implementations, but
> I can live with OPTIONAL.

But it's already so beautful to say just plen+IID must give 128.  Why 
telling more?  Could that be 'over-specifying'?

Alex

>
>
>
> --
> ===============================================
> David Farmer               Email:farmer@umn.edu
> <mailto:Email%3Afarmer@umn.edu>
> Networking & Telecommunication Services
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> Minneapolis, MN 55414-3029   Cell: 612-812-9952
> ===============================================


From nobody Fri Feb 24 06:59:51 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C15129874 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:59:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aucdRlTbnH5o for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 06:59:48 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::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 717D512986D for <ietf@ietf.org>; Fri, 24 Feb 2017 06:59:48 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id x35so18523131qtc.2 for <ietf@ietf.org>; Fri, 24 Feb 2017 06:59:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=FgtiRKPUP2xWJ0i/tZ1caU4SuBdbt8qpVuW/kwEi7c0=; b=i/xcYXZn0+OnrwO9LtLoq5XR8OYErGXLv8tFb2sxw38AjbwJQPof0Dd+zGlFSLakpo qfIBtLotArzbziJudjC2Q/Z7t3ozLFVqkSdNBgQDY5wnLrwjSf+sTCVxwgLhLGM6IH7k BYJtFA7+TsB1gG0AtjViCui1EnsyUkWC7bNXkRiDMGLcndrqKtmzggmYw0YBR43AzFBA uLIv5lnR7K/cthsIB7mIzQXB5woHstf7za1lfte2GpASXaNo1TNrDUtCVrP0avkAPXDL eCKGB2snm/n5ZrmQCx9ZIsMqkPNn9n4y5f2WBYI1qppT0bHpHSt23o1ysOe/fxPOZ5sI 0sxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=FgtiRKPUP2xWJ0i/tZ1caU4SuBdbt8qpVuW/kwEi7c0=; b=qxr0kX+zekDiPq/qPTBarjJocdmg8PwJcAaMVwETL/oP5gTEfe9ePDq6PQmCFzDdLe 6wPihEFwH7wG0G4JJgMwZmSm6S6WW67VLfUDpQB4SpCb9/UwLuQIMyHP+BnUuFIqw12Z otGE/uTP1Gua1yxKXXdvOkH1fIgZd2HJRAex0MV7B8StaQ0X7uYI1mqmlBZjKuNyebHR 5Gp3qAOr3ZGJz+Qh+tXELk3uDy7i9Ym3+rBlzPHTUfJLygI2uzPRyTG16P2H4unzcyXX Uyh1PncA912UjsgYMmZmObQ43yBmjNhxzQBwmF4+YpHEfkK7ADwjBJs37qmLdpg5pNCs UiPA==
X-Gm-Message-State: AMke39k+uuOXOCzwkbWrW3Ldf17rCSU52PrR96K/mrRCoiHWRI7W/2NW+aoMohR4yvWQiniM3kqXzMzvGFw42g==
X-Received: by 10.200.51.92 with SMTP id u28mr3184849qta.151.1487948387261; Fri, 24 Feb 2017 06:59:47 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Fri, 24 Feb 2017 06:59:46 -0800 (PST)
In-Reply-To: <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 24 Feb 2017 09:59:46 -0500
X-Google-Sender-Auth: hJhfCi9CKrld9KVr2NYXK2N5mzA
Message-ID: <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a113550ec116834054947fb11
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/f88Unaz86P_Xa5X5AJj3N30ZL5I>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 14:59:50 -0000

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

On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
> A question to Windows is the following: what prefixlen does it set when
> the end user manually assigns an address on an interface without
> specifiying a prefixlen?
>
>
I don't think this matters... 'end users' will in almost all cases just
attach and get connectivity. If they are in a place where someone says:
"Hey, you should go if/ipconfig ...." then .. they are 'consenting adults'
and can do whatever they please.

again the proposed text (now 175+ messages back) really covers this
already..

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu <span dir=3D"ltr">&=
lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexan=
dre.petrescu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><br>
A question to Windows is the following: what prefixlen does it set when the=
 end user manually assigns an address on an interface without specifiying a=
 prefixlen?<br>
<br></blockquote><div><br></div><div>I don&#39;t think this matters... &#39=
;end users&#39; will in almost all cases just attach and get connectivity. =
If they are in a place where someone says: &quot;Hey, you should go if/ipco=
nfig ....&quot; then .. they are &#39;consenting adults&#39; and can do wha=
tever they please.</div><div>=C2=A0</div><div>again the proposed text (now =
175+ messages back) really covers this already..<br></div></div></div></div=
>

--001a113550ec116834054947fb11--


From nobody Fri Feb 24 07:04:15 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF5C129DDC; Fri, 24 Feb 2017 07:04:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wlDm0y-IR0BK; Fri, 24 Feb 2017 07:04:13 -0800 (PST)
Received: from mail-qt0-x22e.google.com (mail-qt0-x22e.google.com [IPv6:2607:f8b0:400d:c0d::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 00AC1129C51; Fri, 24 Feb 2017 07:04:12 -0800 (PST)
Received: by mail-qt0-x22e.google.com with SMTP id x35so18641362qtc.2; Fri, 24 Feb 2017 07:04:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=A9+asw9Bmo07PkGbQ7wn/YiAE86xsNYaxCiuOCSvxyc=; b=XI5JNa+ZNgTNE3VVWXQWGhbNV+SYF3HuSqWibhkCmxJ9i1QvGAHQD4AjbdnSrM9X2Q L4N1xKW2IyFUOY0AQVzXkTVszn2cmk8XiWllzD77WuDPK8SND9RToLoEOsjjN4FkZcPJ 6My1kgFj0QGkpQxZv5OiqOmj7PZoNYCUuuBKtH3+hqHKn9y/TNLi75nkKrm80xbFB7dC EIZrw0LQp9dAu/iou4GUs2Kx/LNg4R85kADaUIg09XKHO2APYOmwOwDu2u2Szw+P0tCF tBDwPnftu41nZ3xMOFydPcyq3NUZK2m5Tkk3oGRQnaXGtTKtL/s33tNd7/LcS+gSyjv1 rO1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=A9+asw9Bmo07PkGbQ7wn/YiAE86xsNYaxCiuOCSvxyc=; b=MLUOr3sChjrgJ4sPM3iI6RmRTYFe5RNIbRo5z2hwFfh/no6RGCYd3hSW6N99IVW+TG smyiT+F1adyP7v8f+tlF3idN3NIBEN/fJGgIcmj2YmoBJQ2SQ3aLkMBgfEHRfv7agSbL yJwm0h/SY8nvBuKg8kgKOutbKO5jIfj2UOnmguYNo7uC+RdINwVS30QjB+mTz42UfL/S wivwh6AHiNshNSb3zSlwV5YYvU1i3vwZkyM5beYtKDkrABuZO7Uk0MAP0SqS9NnWy8qJ rOIbEo5pLkFSl6ZUJY3l2+ex+0iDDtWBRXfddDMgd3nvEL5c1zaXHtTOS0uwi4lR1ojs WfyQ==
X-Gm-Message-State: AMke39lmNEGJY85d5W2Pv1Igclo8C0jiCDErzJtmyY5GO8FIf14HbBzXg8blGed2WKJRDldzUnR3jPZ/HKxShQ==
X-Received: by 10.200.53.209 with SMTP id l17mr2903513qtb.281.1487948651902; Fri, 24 Feb 2017 07:04:11 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Fri, 24 Feb 2017 07:04:11 -0800 (PST)
In-Reply-To: <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 24 Feb 2017 10:04:11 -0500
X-Google-Sender-Auth: _JVotMiJb4KUvHpx3vUJPz_KiwU
Message-ID: <CAL9jLaZ86B8EKy9hrJY2mO3GZDurbp4QZohwMZDrkZyj8ayA_g@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Erik Kline <ek@google.com>
Content-Type: multipart/alternative; boundary=001a1143c7b0d774d20549480a54
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JMBIn8xvfz1wBj5fXlyi1XVuWOo>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:04:15 -0000

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

On Fri, Feb 24, 2017 at 4:04 AM, Erik Kline <ek@google.com> wrote:

> On 24 February 2017 at 12:41, Christopher Morrow <morrowc.lists@gmail.com>
> wrote:
>
>> gosh people are being literal today :)
>>
>>
>> On Thu, Feb 23, 2017 at 10:34 PM, Lorenzo Colitti <lorenzo@google.com>
>> wrote:
>>
>>> On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <
>>> morrowc.lists@gmail.com> wrote:
>>>
>>>> > The IESG plans to make a decision in the next few weeks, and solicits
>>>> > final comments on this action. Please send substantive comments to the
>>>> > ietf@ietf.org mailing lists by 2017-03-01. 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."
>>>>
>>>> Nothing in the past really matters here, what matters is: "Is the bis
>>>> draft all set, did we fix all the things which must be fixed before this
>>>> draft becomes a real 'standard'?"
>>>>
>>>
>>> I don't think you can say nothing in the past matters here. We know that
>>> there have been host implementations that relied on this guarantee, and we
>>> have to consider that if we change the standard, those implementations will
>>> become non-compliant.
>>>
>>
>> I don't think the proposed (now 160+ messages back) text really says:
>> "FREE FOR ALL< NO LIMITS!!! WEEE!" it says: "Hey, if you want to use /64
>> because the application you are being placed into requires it (slac, blah
>> and blah and ilnp and blah - see rfc7k) then do that, else any other prefix
>> length works"
>>
>> how's that not 'ok' for host folks? "Hi, my host is going to be in a
>> slaac world.. so /64 it is!"
>>
>
> For manual assignment among consenting adults: as you like it.  (For all
> prefixes longer than /64, the trailing 64bits would still end up being
> unique; there is no real issue here.)
>
>
I agree.


> And I gather everyone agrees that at a minimum the /127 RFC and other
> working-group-graduated documents should be suitably incorporated and
> referenced.
>
>
I think that's in the proposed text, yes... or easily is a list of
[this][that][theother]


> Otherwise, this feels like another round of "why isn't IPv6 just 128bit
> IPv4?"  IMHO having /64 as the logical unit of allocation to network leaves
> is a very good thing.
>

For enduser deployment picking 'something' (/64 is perfectly fine) is
totally sane, and already in the proposed text. The sticking point isn't so
much: "ipv6 is ipv4 with  more bits" (which the network treats it as) but:
"hey, we know we allocate longer prefixes all the time for 'reasons' on
things that have bespoke config, let's not make that harder by letting
vendors/etc take shortcuts... acknowledge the fact that we really do have
interfaces with >/64 deployed.

I don't see how that damages network-ops folks, nor host-ops, nor
developers.

There is certainly a discussion for 'not this list' about networking
providers doing 'short sighted' things on their network with respect to
attached customers, but... that's not this document and not this discussion
and not this list (except as an opionion/editorial piece).

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 4:04 AM, Erik Kline <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:ek@google.com" target=3D"_blank">ek@google.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_extra"><div class=3D"gmail_quote"><div><div class=3D"h5">On 24 February =
2017 at 12:41, Christopher Morrow <span dir=3D"ltr">&lt;<a href=3D"mailto:m=
orrowc.lists@gmail.com" target=3D"_blank">morrowc.lists@gmail.com</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">gosh people=
 are being literal today :)<div><div class=3D"m_8407023543853465988h5"><br>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Feb 23, 2=
017 at 10:34 PM, Lorenzo Colitti <span dir=3D"ltr">&lt;<a href=3D"mailto:lo=
renzo@google.com" target=3D"_blank">lorenzo@google.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_ex=
tra"><div class=3D"gmail_quote"><span>On Fri, Feb 24, 2017 at 12:23 PM, Chr=
istopher Morrow <span dir=3D"ltr">&lt;<a href=3D"mailto:morrowc.lists@gmail=
.com" target=3D"_blank">morrowc.lists@gmail.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><d=
iv class=3D"gmail_quote"><div>&gt; The IESG plans to make a decision in the=
 next few weeks, and solicits</div><div>&gt; final comments on this action.=
 Please send substantive comments to the</div><div>&gt; <a href=3D"mailto:i=
etf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailing lists by 2017-03-=
01. Exceptionally, comments may be</div><div>&gt; sent to <a href=3D"mailto=
:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a> instead. In either case=
, please retain the</div><div>&gt; beginning of the Subject line to allow a=
utomated sorting.&quot;</div><div><br></div><div>Nothing in the past really=
 matters here, what matters is: &quot;Is the bis draft all set, did we fix =
all the things which must be fixed before this draft becomes a real &#39;st=
andard&#39;?&quot;</div></div></div></div></blockquote><div><br></div></spa=
n><div>I don&#39;t think you can say nothing in the past matters here. We k=
now that there have been host implementations that relied on this guarantee=
, and we have to consider that if we change the standard, those implementat=
ions will become non-compliant.</div></div></div></div>
</blockquote></div><br></div></div></div><div class=3D"gmail_extra">I don&#=
39;t think the proposed (now 160+ messages back) text really says: &quot;FR=
EE FOR ALL&lt; NO LIMITS!!! WEEE!&quot; it says: &quot;Hey, if you want to =
use /64 because the application you are being placed into requires it (slac=
, blah and blah and ilnp and blah - see rfc7k) then do that, else any other=
 prefix length works&quot;</div><div class=3D"gmail_extra"><br></div><div c=
lass=3D"gmail_extra">how&#39;s that not &#39;ok&#39; for host folks? &quot;=
Hi, my host is going to be in a slaac world.. so /64 it is!&quot;</div></di=
v></blockquote><div><br></div></div></div><div>For manual assignment among =
consenting adults: as you like it. =C2=A0(For all prefixes longer than /64,=
 the trailing 64bits would still end up being unique; there is no real issu=
e here.)</div><div><br></div></div></div></div></blockquote><div><br></div>=
<div>I agree.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=
=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div></div><=
div>And I gather everyone agrees that at a minimum the /127 RFC and other w=
orking-group-graduated documents should be suitably incorporated and refere=
nced.</div><div><br></div></div></div></div></blockquote><div><br></div><di=
v>I think that&#39;s in the proposed text, yes... or easily is a list of [t=
his][that][theother]</div><div>=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>=
</div><div>Otherwise, this feels like another round of &quot;why isn&#39;t =
IPv6 just 128bit IPv4?&quot; =C2=A0IMHO having /64 as the logical unit of a=
llocation to network leaves is a very good thing.</div></div></div></div>
</blockquote></div><br></div><div class=3D"gmail_extra">For enduser deploym=
ent picking &#39;something&#39; (/64 is perfectly fine) is totally sane, an=
d already in the proposed text. The sticking point isn&#39;t so much: &quot=
;ipv6 is ipv4 with =C2=A0more bits&quot; (which the network treats it as) b=
ut: &quot;hey, we know we allocate longer prefixes all the time for &#39;re=
asons&#39; on things that have bespoke config, let&#39;s not make that hard=
er by letting vendors/etc take shortcuts... acknowledge the fact that we re=
ally do have interfaces with &gt;/64 deployed.</div><div class=3D"gmail_ext=
ra"><br></div><div class=3D"gmail_extra">I don&#39;t see how that damages n=
etwork-ops folks, nor host-ops, nor developers.</div><div class=3D"gmail_ex=
tra"><br></div><div class=3D"gmail_extra">There is certainly a discussion f=
or &#39;not this list&#39; about networking providers doing &#39;short sigh=
ted&#39; things on their network with respect to attached customers, but...=
 that&#39;s not this document and not this discussion and not this list (ex=
cept as an opionion/editorial piece).</div></div>

--001a1143c7b0d774d20549480a54--


From nobody Fri Feb 24 07:04:56 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC037129DE7 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:04:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.333
X-Spam-Level: 
X-Spam-Status: No, score=-0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 yUZffPv-rThD for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:04:52 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 80ED2129DE6 for <ietf@ietf.org>; Fri, 24 Feb 2017 07:04:52 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1OF4pOu018711 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:04:51 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F060720B846 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:04:50 +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 E63ED20B814 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:04:50 +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 v1OF4odX000822 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:04:50 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <aa238941-3d6f-b9bc-3471-e3f6112e4649@gmail.com>
Date: Fri, 24 Feb 2017 16:04:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kc2jKP1kLRRkJDg7ZI1KcQT0-hw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:04:54 -0000

Le 24/02/2017 à 04:13, Fernando Gont a écrit :
> On 02/23/2017 07:43 PM, David Farmer wrote:
>>
>>
>> On Wed, Feb 22, 2017 at 10:16 PM, Lorenzo Colitti <lorenzo@google.com
>> <mailto:lorenzo@google.com>> wrote:
>>
>>     Help he understand, then. There is widely-deployed code that assumes
>>     that the interface ID is 64 and does not work on anything other than
>>     64 bit prefix lengths. Currently that code is correct on all unicast
>>     space. If you change RFC 4291, won't that code be incorrect?
>>
>>
>> OK, what if we said something like this;
>>
>>    IPv6 unicast routing is based on prefixes of any valid length up to
>>    128 [BCP198]. However, all implementations of IPv6 are REQUIRED to
>>    support an IID length of 64 bits, other IID lengths are OPTIONAL.
>>    Subnet prefixes of /64 are RECOMMENDED for general purpose use,
>>    subnet prefixes of /127 are RECOMMENDED for point-to-point router
>>    links [RFC6164], other subnet prefix lengths are NOT RECOMMENDED,
>>    as their use could be incompatible with some implementations of IPv6.
>>    The rationale for the 64 bit boundary in IPv6 addresses can be found
>>    in [RFC7421].
>
> I'd remove a few sentences here, as in:
>
>    IPv6 unicast routing is based on prefixes of any valid length up to
>    128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
>    purpose use, subnet prefixes of /127 are RECOMMENDED for point-
>    to-point router links [RFC6164]. The rationale for the 64 bit
>    boundary in IPv6 addresses can be found in [RFC7421].

For me IMHO that is still too much text.  Who needs her favorite use 
purpose to be called general by an archi doc and why?

Why not the ptp links be general purpose?  For example ptp cellular links?

Alex

>
> Thanks,
>


From nobody Fri Feb 24 07:11:24 2017
Return-Path: <nick@foobar.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29BF2129C51; Fri, 24 Feb 2017 07:11: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 autolearn_force=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 hGQNah6_REZG; Fri, 24 Feb 2017 07:11:21 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F06B1296C1; Fri, 24 Feb 2017 07:11:20 -0800 (PST)
X-Envelope-To: 6man-chairs@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v1OFBHQK043985 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Feb 2017 15:11:18 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <58B04D15.7030506@foobar.org>
Date: Fri, 24 Feb 2017 15:11:17 +0000
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.10 (Macintosh/20170123)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <20170221001940.GB84656@Vurt.local> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com> <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr> <alpine.DEB.2.02.1702241423100.15705@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1702241423100.15705@uplift.swm.pp.se>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cIII-sER-xFUcF9JarMAUrd5Ors>
Cc: 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:11:23 -0000

Mikael Abrahamsson wrote:
> I just want to state my opinion that whatever text we come up with should
> reflect current operational reality, in that SLAAC A=1 only works on /64,
> and that people use all kinds of subnet sizes when manually configuring
> interfaces.
> 
> If current code doesn't treat 000::/3 in any special case, then documents
> should reflect this.
> 
> Mandating /64 only for any IPv6 use case doesn't reflect reality as I see
> it. I don't want to see A=1 /64 SLAAC requirement relaxed either.
> 
> I just want the -bis document to reflect what is currently in the field
> and we know works. Nothing more, nothing less.

I wholly agree with this as it applies to draft-ietf-6man-rfc4291bis.

As a general comment, it should be reiterated that operational feedback
is critical to standards development and that if field deployment issues
are neglected, this damages the standards development process.  It would
be unfortunate if this document fell prey to this folly.

Nick


From nobody Fri Feb 24 07:38:22 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678D51298CC for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 lTDwveeaOqyl for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:38:18 -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 9033B129888 for <ietf@ietf.org>; Fri, 24 Feb 2017 07:38:18 -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 v1OFcGEm011580 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:38:16 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 1775320B848 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:38: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 1224F20B814 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:38: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 v1OFcFhZ014461 for <ietf@ietf.org>; Fri, 24 Feb 2017 16:38:15 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: ietf@ietf.org
References: <20170221001940.GB84656@Vurt.local> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <dbadff4b-cf80-3554-aa9a-8ceae0616ea9@gmail.com>
Date: Fri, 24 Feb 2017 16:38:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C1wFYwNSyjnTsDqhLe8eaHTp6Dw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:38:20 -0000

Le 24/02/2017 à 08:15, David Farmer a écrit :
>
>
> On Thu, Feb 23, 2017 at 9:13 PM, Fernando Gont
> <fgont@si6networks.com <mailto:fgont@si6networks.com>> wrote:
>
> I'd remove a few sentences here, as in:
>
> IPv6 unicast routing is based on prefixes of any valid length up to
> 128 [BCP198]. Subnet prefixes of /64 are RECOMMENDED for general
> purpose use, subnet prefixes of /127 are RECOMMENDED for point-
> to-point router links [RFC6164]. The rationale for the 64 bit
> boundary in IPv6 addresses can be found in [RFC7421].
>
>
> The problem is you have stripped out all the implementation guidance
> and only left operational guidance.  But maybe the the right idea is
> to separate the two, putting the operational guidance in Section 2.4
> where we are talking about prefixes and the implementation guidance
> in section 2.4.1 where we are talking about IIDs.

Well, in a sense yes.

I had an addressing architecture discussion today with a novice
practitioner and she was surprised to hear that
2001:db8:0:cd30::/60 is the same as
2001:db8:0:cd31::/60, as
2001:db8:0:cd32::/60,... yet we can't say
2001:db8:0:cd3::/60

which makes one wonder why dont we say 2001:db8:0:cd3*::/60?

An architecture document would be a good guidance on this.

But an architecture document that starts to qualify deployments as more
important than others, or cellular vs dsl, or ptp vs shared... or give
implementation guidance, it's maybe beyond archi, IMHO.

Alex

> 2nd Paragraph of 2.4;
>
> IPv6 unicast routing is based on prefixes of any valid length up to
> and including 128 [BCP198].  However, subnet prefixes of 64 bits in
> length are REQUIRED for use with Stateless Address Autoconfiguration
> (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
> use. The rationale for the 64 bit boundary in IPv6 addresses can be
> found in [RFC7421].
>
> 4th paragraph of 2.4.1
>
> For all unicast addresses, except those that start with the binary
> value 000, support for Interface IDs that are 64 bits long is
> REQUIRED, support for other Interface IDs lengths is OPTIONAL. The
> rationale for the 64 bit boundary in IPv6 addresses can be found in
> [RFC7421].
>
> This clearly say that implementations that only support 64 bit IID
> lengths are just fine, but also says implementations that allow IID
> lengths other than 64 bits are just fine too.  I think the current
> and historic text actually implies implementations are not to allow
> other IID lengths, is that what we really intended to say?  A lot of
> implementations seem to allow other IID lengths, are they wrong?  I
> don't think so.
>
> This also gives strong operational guidance that 64 bit length
> subnet prefixes are expected in most situations.  Reinforcing the 64
> bit boundary, however without outlawing the use of other subnet
> prefix lengths when implemented and they could be useful.  This is
> done without distracting from the 64 bit boundary, by not directly
> calling attention to RFC6164 or the other longer prefix lengths.
> Since BCP198 and RFC7421 both reference RFC6164 calling it out here
> doesn't seem necessary, and would unnecessarily weaken the focus on
> the 64 bit boundary that I'm trying to maintain.
>
> I don't see how this text would require changes in any code, nor does
> it imply other IID lengths are not allowed operationally, again which
> a lot of implementations seem to allow.
>
> Thanks. -- =============================================== David
> Farmer               Email:farmer@umn.edu
> <mailto:Email%3Afarmer@umn.edu> Networking & Telecommunication
> Services Office of Information Technology University of Minnesota
> 2218 University Ave SE        Phone: 612-626-0815
> <tel:(612)%20626-0815> Minneapolis, MN 55414-3029   Cell:
> 612-812-9952 <tel:(612)%20812-9952>
> ===============================================


From nobody Fri Feb 24 07:48:57 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C360112986B for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:48:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 58AcGwZ3U8v2 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 07:48:55 -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 68A6C12968F for <ietf@ietf.org>; Fri, 24 Feb 2017 07:48:55 -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 v1OFmqle006474; Fri, 24 Feb 2017 16:48:53 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id E319720B848; Fri, 24 Feb 2017 16:48:52 +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 D561B20B830; Fri, 24 Feb 2017 16:48:52 +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 v1OFmqYO012087; Fri, 24 Feb 2017 16:48:52 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com>
Date: Fri, 24 Feb 2017 16:48:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nJu0krT1QAELypSQ0Lub_11nQxU>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:48:56 -0000

Le 24/02/2017 à 15:59, Christopher Morrow a écrit :
>
>
> On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
>  wrote:
>
>
> A question to Windows is the following: what prefixlen does it set
> when the end user manually assigns an address on an interface without
> specifiying a prefixlen?
>
>
> I don't think this matters... 'end users' will in almost all cases
> just attach and get connectivity.

Let me go next in cycle: what does linux do when one ifconfig add an
IPv6 address without telling the plen?  Is it adding an entry in the rt
table?  Which plen?  Is that plen normal?

> If they are in a place where someone says: "Hey, you should go
> if/ipconfig ...." then .. they are 'consenting adults' and can do
> whatever they please.

I assume you assume that ip/ifconfig by consenting adults means the
adults type a plen in the CLI, right?

That makes it mandatory that the CLI _requires_ a plen, right?  That CLI
should not allow silence for a plen parameter.

Because silent plen means 64.  And I dont think it's right to assume a
by-default 64 plen.  Because many people think 64 is right and others
think it's wrong, there does not seem to be a commonly agreed 'by
default' value for plen.

Alex

>
> again the proposed text (now 175+ messages back) really covers this
> already..


From nobody Fri Feb 24 07:54:00 2017
Return-Path: <David.Black@dell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF2A11298C7; Fri, 24 Feb 2017 07:53:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.087
X-Spam-Level: 
X-Spam-Status: No, score=-4.087 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=s2obd2Iw; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=MGpd70zp
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id st_djehYaqLY; Fri, 24 Feb 2017 07:53:44 -0800 (PST)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 B01C9129890; Fri, 24 Feb 2017 07:53:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1487951531; x=1519487531; h=from:cc:to:subject:date:message-id:references: in-reply-to:mime-version; bh=5o9b3waqCwEE0g689d8vnQH6QwC+3jutlTclyuV8QDo=; b=s2obd2IwaHXk1BpTogSAgRWwMAodywsbVkQ2Il/SX+LuSQDlZboj8HHf xefCUoYOUZgpxKGse2IbMF7/8hBOECAy00LBaMM6Q1UgE2/rXmhoA2dRh WB8KX5lxdtn7LJrbjFu/0d0CPyZaTBem5Oenz/rtak+S+eBBFsbOqosOb M=;
Received: from esa5.dell-outbound2.iphmx.com ([68.232.153.203]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Feb 2017 09:52:10 -0600
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwhop.emc.com ([168.159.213.141]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 24 Feb 2017 21:53:25 +0600
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v1OFrWZW013675 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 24 Feb 2017 10:53:34 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com v1OFrWZW013675
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1487951614; bh=/ZNF07InB2ddXdy1s+lDIdLXjMc=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=MGpd70zpF4flAw3sMLX+GyvNJL7AEaCnPNjNKQR6CZrGw54QKkWXzuCdLULlfTHdP X6cGEaGPm7oNa3PIz43zNrs3Gd3RSqrZ4qZlOCx2diAOHfxNEQ02SHJ+n6X+bCpmTn wQtuzUB+U64fnmzpRCav/WYcuEVwadZoz9A7qHIE=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com v1OFrWZW013675
Received: from mailusrhubprd03.lss.emc.com (mailusrhubprd03.lss.emc.com [10.253.24.21]) by maildlpprd01.lss.emc.com (RSA Interceptor); Fri, 24 Feb 2017 10:52:04 -0500
Received: from MXHUB301.corp.emc.com (MXHUB301.corp.emc.com [10.146.3.27]) by mailusrhubprd03.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v1OFrJYp017478 (version=TLSv1.2 cipher=AES128-SHA256 bits=128 verify=FAIL); Fri, 24 Feb 2017 10:53:19 -0500
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB301.corp.emc.com ([10.146.3.27]) with mapi id 14.03.0266.001; Fri, 24 Feb 2017 10:53:18 -0500
To: Shitanshu Shah <shitanshu_shah@hotmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: RE: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjn2hotpFQg8pf0qPmuGxW7GZeaF4QrTw
Date: Fri, 24 Feb 2017 15:53:17 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>
In-Reply-To: <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.109]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F8C4510MX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd03.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8JVca4kCh691hSbe-GUr37U32aw>
Cc: "idr@ietf.org" <idr@ietf.org>, "Black, David" <David.Black@dell.com>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 15:53:53 -0000

--_000_CE03DB3D7B45C245BCA0D243277949362F8C4510MX307CL04corpem_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That's simpler, and a few sentences of discussi=
on about possible L2 framing differences should cover what needs to be done=
 (e.g., if traffic rates are configured in terms of L2 octets, then explain=
 how each entity converts between IP traffic and L2 traffic - the draft alr=
eady effectively contains that explanation).

[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that's an editorial choice - I prefer to explain how something w=
orks before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn't adopted that design is that we don't want to mak=
e assumptions on which data the remote peer will be used for enforcing loca=
l actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That's fine, I wanted to ensure that this had been considered.  The =
discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind't include a context field because we thought that the definit=
ion of the IPFIX attributes is sufficient by itself, but if you do think it=
 is helpful to have such information, we can update the table.

David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it's the link that crosses the re=
levant AS boundary, but that does have to be stated, as it's nowhere to be =
found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??


[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don't see specificatio=
n of what has to be implemented in either the text in the draft or the abov=
e explanations.

        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.



[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the "exercise to the reader"  criticism - one way to be h=
onest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the "outside the scope of this document" statement is wr=
ong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn't catch the reference, RFC 6919 is an April 1 RF=
C ... and the "SHOULD BE considered" language used in the last security con=
siderations paragraph of this draft is accurately characterized as vague in=
 Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------



--_000_CE03DB3D7B45C245BCA0D243277949362F8C4510MX307CL04corpem_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.xmsonormal, li.xmsonormal, div.xmsonormal
	{mso-style-name:x_msonormal;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; Inline ...<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks, --David<o:p></o:p=
></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Shitansh=
u Shah [mailto:shitanshu_shah@hotmail.com]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Thank you for taking time for the review..<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Please find our response inline ##svshah and [Med]<o:p></o:p></s=
pan></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">Regards,
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">Shitanshu<o:p=
></o:p></span></p>
<div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"> David Black &lt;<a href=3D"mailto:david.black@emc.com">da=
vid.black@emc.com</a>&gt;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Reviewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142">https://en.wikipedia.org/wiki/Service-level_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; That would be good, thanks.</sp=
an><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, the purpose for a=
dvertising L2 overhead, from the Producer to the Consumer,&nbsp;is to make =
sure traffic is well conditioned, at the egress of the&nbsp;Consumer,
 to avoid possible indiscriminate drops at the ingress of the Producer. In =
another words, the&nbsp;Producer is telling the&nbsp;Consumer to ignore its=
 own link level overhead, instead use Producer's provided link level overhe=
ad while running frames through QoS functions
 (this is&nbsp;relevant in use-cases where l2 overhead of the&nbsp;egress l=
ink on Consumer and of ingress link on the Producer are of different size, =
e.g., in the&nbsp;vpn/tunnel connection between two peer&nbsp;nodes which p=
hysically may be multiple hops away).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">I understand your comments =
regarding re-using TSpec without any modification.&nbsp;Do you agree with t=
he use-case of l2 differences? If yes, any suggestion how to
 accommodate that?<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; Specifying this=
 in terms of IP octets implies that L2 overhead is to be ignored on both li=
nks.&nbsp; That&#8217;s simpler, and a few sentences of discussion about
 possible L2 framing differences should cover what needs to be done (e.g., =
if traffic rates are configured in terms of L2 octets, then explain how eac=
h entity converts between IP traffic and L2 traffic - the draft already eff=
ectively contains that explanation).</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p></=
o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, what you describe=
 below conceptually very much makes sense and that is what we attempt to ac=
hieve. What is unclear though how to capture that using
 TSpec definition specified in RFC2215. Since that TSpec definition has bot=
h minimum-rate and maximum-rate, but no in/out profile marking parameters.<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Is your proposal below to d=
efine two TSpecs using the same&nbsp;definition from RFC2215? Wouldn't in t=
hat case we have min/max specified twice? min/max in each TSpec?
 and thus confusing to represent one min and one max through two TSpecs?<o:=
p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; See RFC 2698 fo=
r the desired behavior and the parameters needed to specify it.&nbsp; The c=
urrent idr-sla draft is not able to represent the traffic conditioning
 mechanisms specified in both RFC 2698 and RFC 2697, as each mechanism requ=
ires two token buckets (e.g., there are two burst sizes, but the idr-sla dr=
aft TSpec only contains one).&nbsp; This deficiency needs to be dealt with.=
&nbsp; One possibility for simplification
 is to drop the max-rate from the RFC 2115 TSpec and assume that the max-ra=
te for bursting is the effective line rate.</span><span style=3D"font-size:=
10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt;font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah,&nbsp;It is around=
 the semantics of&nbsp;a single queue with a different threshold for a set =
of code-points, where packet for a specific code-point is to be tail
 dropped if overall queue-depth hits code-point specific threshold at the a=
rrival of that packet.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">We will add appropriate cla=
rification for this semantics.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">David&gt; Will look at revision
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, Sure. Is followin=
g clarification okay? (some of the wordings taken from RFC2598)<o:p></o:p><=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&quot;<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">A higher priority class of =
traffic&nbsp;to be served without pre-empted by lower priority&nbsp;class o=
f traffic&nbsp;for more than a packet time at the configured rate.<o:p></o:=
p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">In the system that implemen=
ts WRR, the use of relative priority may get restricted where a single queu=
e may be used for a&nbsp;higher priority traffic class where
 that queue &nbsp;is configured for the full share of the output bandwidth.=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&quot;<o:p></o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">David&gt; Last sentence basically says that WRR weights are out-of-sc=
ope.&nbsp; That seems wrong.&nbsp; Will look at revision.</span><span style=
=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, They are to facil=
itate hierarchy. A specific Traffic Class, can further be divided in a mult=
iple &nbsp;subset of&nbsp;Traffic Classes, with their own Traffic
 Class Elements and Traffic Class Services.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">Will correct the wording to=
 remove your this specific concern.<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; Will look at revision
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, While&nbsp;eventu=
ally &quot;Traffic Conditioning Agreement&quot; should be translated to the=
 actual forwarding qos policy on any vendor specific device, TCA exchange
 largely carries concepts/semantics that is either standard based or&nbsp;w=
ell understood.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">While we are not aware of a=
ny working group document of QoS Yang Model, we think that &nbsp;concepts o=
f Traffic Conditioning should be easily adaptable to any QoS
 Yang Models since they also have to be defined to support those concepts.<=
o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p=
>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; Still want to s=
ee cross-check with implementations here.</span><span style=3D"font-size:10=
.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><b=
r>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; OK, thanks.</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[9] In section 3.2, the &quot;intended for =
the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">UPDATE message&quot; text in the specificat=
ion of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">flags is unclear.&nbsp; I suspect that this=
 is intended to differentiate</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">the two usages described in sections 4.1.1 =
(Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">(Multiple Hops), in which case the parenthe=
sized terms (or similar</span><span style=3D"font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">terminology) should be used with cross-refe=
rences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sections.</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">##svshah, sure will make ne=
cessary changes, also in the context of earlier comment.<o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[10] There needs to be a coherent discussio=
n in one place about how</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">SLA advertisement, update and withdrawal wo=
rk.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">method may suffice on the wire, but the det=
ails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">advertisement, subsequent advertisement (up=
date) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">need to be specified in one place.&nbsp; Th=
e third paragraph of Section 4</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">is a start on this material, but it's too t=
erse;&nbsp;</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">[Med] That text is terse because we are reusin=
g the BGP machinery for advertising/withdrawing; we only augment it with tr=
iggers that are linked to the SLA information.
 A new SLA will lead to an update message with ADVERTISE, an update of an e=
xisting SLA will trigger an update message. We do think this information is=
 already present in the document.
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt;This is hard to =
understand it, as there is no statement that the BGP machinery is being use=
d, and the material on SLA usage is spread in different places.&nbsp;
 I suggest starting section 3 with a discussion of advertisement/update/wit=
hdrawal, and how all three are realized via a single ADVERTISE method via B=
GP UPDATE - this was difficult to figure out in reading the current draft.<=
/span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">&nbsp;</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">it should be expanded</span=
><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;colo=
r:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">into its own subsection, and moved earlier =
to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">ADVERTISE method in Section 3.2.&nbsp; This=
 text from Section 3.2 should be</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">moved into that new subsection and likewise=
 expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] Another option is to move it Section 4. From our standpo=
int, we do think it is straightforward to describe the behavior once the at=
tributes format are defined.&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; Ok, that&#8217;=
s an editorial choice - I prefer to explain how something works before defi=
ning its on-the-wire data format.</span><span style=3D"font-size:11.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o=
:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp; If an advertised SLA ID is different from earlier advertised</span><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one,</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the same=
 prefix and from the same Source AS, indicates</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Source</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is advert=
ising new SLA Content to replace the previous one</span><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised w=
ith the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">In addition, I wonder whether functionality=
 should be added to allow</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">withdrawal of an advertisement by specifyin=
g its SLA ID, although that</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">was not part of the original design.</span>=
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color=
:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt;font-variant-ligature=
s: normal;orphans: 2;widows: 2">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">[Med] The reason we didn&#8217;t adopted that design is that we don&#=
8217;t want to make assumptions on which data the remote peer will be used =
for enforcing local actions and also because of this text:</span><span styl=
e=3D"color:#212121"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"font-variant-ligatures: normal;orphans: 2;=
widows: 2">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#=
212121">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The SLA ID applies to aggregate traf=
fic to prefixes for a given</span><span style=3D"color:#212121"><o:p></o:p>=
</span></p>
<p class=3D"xmsonormal" style=3D"font-variant-ligatures: normal;orphans: 2;=
widows: 2">
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:#=
212121">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AFI/SAFI that share the same Source =
AS and SLA ID.</span><span style=3D"color:#212121"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; That&#8217;s fi=
ne, I wanted to ensure that this had been considered.&nbsp; The discussion =
of BGP mechanism reuse will probably help here.</span><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[11] Notions of context for interpretation =
of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">in 3.3.1 need to be added, e.g.:</span><spa=
n style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The first three parameters (DSCP, MPLS EXP field in top label,</span><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">802.1q priority) can</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">network path.</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The IP address parameters are rather likely to be VPN-specific when</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">there's more</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN that =
spans or transits the ASs involved.</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The transport port parameters need specification of which transport</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">header and where it</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP t=
raffic carried by in VXLAN, is this the</span><span style=3D"font-size:10.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">inner TCP header</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header in =
VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">There are probably simple approaches to spe=
cifying context in all</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">cases, but that context does need to be spe=
cified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] We dind&#8217;t include a context field because we thoug=
ht that the definition of the IPFIX attributes is sufficient by itself, but=
 if you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Really???=
&nbsp; Please reread the first comment above:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; - The first three parameters (DSCP, MPLS EXP field in top l=
abel, 802.1q priority) can</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's network path.</span><span style=3D=
"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Taking ju=
st DSCP, it can change on a per-link basis, so something has to specify whi=
ch link (between the SLA Producer and SLA Consumer?) is involved.&nbsp;
 It probably suffices to say that it&#8217;s the link that crosses the rele=
vant AS boundary, but that does have to be stated, as it&#8217;s nowhere to=
 be found in the far more general IPFIX registry.</span><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[12] The security considerations (section 1=
0) are severely incomplete</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">and insufficient:</span><span style=3D"font=
-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#=
1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; I stand by this=
 statement and recommend a complete rewrite of the security considerations.=
</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Discussion of possible abuse of this BGP option for</span><span style=3D"=
font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">denial-of-service and theft-of-service,</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includin=
g possible countermeasures and</span><span style=3D"font-size:10.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">mitigations.</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] This attack vector is not specific to this attribute; th=
is is valid for BGP in general.</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p=
></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; There are addit=
ional attacks enabled by this attribute.</span><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><=
o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- This sentence at the end of the second paragraph in Section 10 is</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">content-free:</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is NOT=
 RECOMMENDED to enable this attribute at the</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale of =
the Internet unless if means to prevent leaking</span><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sensitive</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informati=
on are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implemen=
ter or admin supposed to do?&nbsp;</span><span style=3D"font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">[Med] An example of what an admin needs to che=
ck if this information can be sent to a given peer or not. Some of the cont=
ent of the attribute contains some sensitive information
 such as contract Id, classes, etc.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt;text-indent:30.75pt"><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black">How does</span><span style=3D"font-size:10.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imple=
mentation or deployment is&nbsp; &quot;at the</span><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F49=
7D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">scale</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;c=
olor:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">[Med] The idea here is to avoid leaking such d=
ata in to the global routing table. Only entitled peers need receive such i=
nformation with controlled scope.</span><span style=3D"font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; I understand th=
e idea - the problem is that I don&#8217;t see specification of what has to=
 be implemented in either the text in the draft or the above explanations.<=
/span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;c=
olor:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; - The next to last paragraph in section 10 is almost conten=
t-free, as</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">it leaves</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementation=
 and deployment of key security</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">functionality as</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the r=
eader&quot; - that's not acceptable.</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
<br>
<o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">[Med] I guess =
you are referring to the following text. Validation checks are really deplo=
yment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"color:#212121"><o:p></o:p><=
/span></p>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; The attribute may be advertised by a mis=
behaving node to communicate<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; SLA parameters that are not aligned with=
 the SLA agreements.&nbsp; Though<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; the enforcement of SLA parameters is out=
side the scope of this<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; document, it is RECOMMENDED that the SLA=
 Consumer to enforce a set of<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; validation checks before translating the=
 SLA parameters conveyed in<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; the QoS attributes into provisioning act=
ions.&nbsp; Such validations MAY<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; rely on SLA parameters like the origin A=
S or SLA ID, like generating<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; SLA ID using pseudo-random schemes [<a h=
ref=3D"https://tools.ietf.org/html/rfc4086" target=3D"_blank" title=3D"&quo=
t;Randomness Requirements for Security&quot;">RFC4086</a>].<o:p></o:p></spa=
n></pre>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">David&gt; I stand by the =
&#8220;exercise to the reader&#8221; &nbsp;criticism - one way to be honest=
 about this would be to change the paragraph to:<o:p></o:p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span style=3D"color:#212121">The attribute may be advertised by a m=
isbehaving node to communicate<o:p></o:p></span></pre>
<pre style=3D"font-variant-ligatures: normal;orphans: 2;widows: 2"><span st=
yle=3D"color:#212121">&nbsp;&nbsp; SLA parameters that are not aligned with=
 the SLA agreements.&nbsp; The<o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.<o:p></o:p></span></pre>
<pre><span style=3D"color:#212121"><o:p>&nbsp;</o:p></span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
color:#1F497D">David&gt; That does not change any normative content of the =
original paragraph.&nbsp; My view is that the &#8220;outside the scope of t=
his document&#8221; statement is wrong because all of these parameters are =
being defined in this draft.</span><span style=3D"font-size:11.0pt;font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></=
span></pre>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Last, but not least, the final paragraph in Section 10 is a joke</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">that will</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security direc=
torate reviewer - to understand why, see</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, and =
take note of the publication date of RFC</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">6919.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><br>
David&gt; For anyone who didn&#8217;t catch the reference, RFC 6919 is an A=
pril 1 RFC ... and the &#8220;SHOULD BE considered&#8221; language used in =
the last security considerations paragraph of this draft is accurately char=
acterized as vague in Section 2 of RFC 6919:<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; The phrase &quo=
t;SHOULD CONSIDER&quot; indicates that the authors of the<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; specification t=
hink that implementations should do something, but<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt;font-family:&quot;Courier New&quot;">&nbsp;&nbsp; they're not su=
re quite what.</span><span style=3D"font-size:11.0pt;font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck">------------------------</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Having noted a dozen major issues, I'll end=
 the review here for now,</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">as I believe a serious revision of the draf=
t is called for, which</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">would be a better starting point to review =
for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">editorial items.</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">David L. Black, Distinguished Engineer</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Dell EMC, 176 South St., Hopkinton, MA&nbsp=
; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbs=
p; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black"><a href=3D"mailto:David.Black@dell.com">Dav=
id.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
<br>
<o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CE03DB3D7B45C245BCA0D243277949362F8C4510MX307CL04corpem_--


From nobody Fri Feb 24 08:21:58 2017
Return-Path: <rg+ietf@randy.pensive.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92BD41299AD; Fri, 24 Feb 2017 08:21:54 -0800 (PST)
X-Quarantine-ID: <LqOrIWPZWg07>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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 autolearn_force=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 LqOrIWPZWg07; Fri, 24 Feb 2017 08:21:53 -0800 (PST)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id AFB75128AC9; Fri, 24 Feb 2017 08:21:53 -0800 (PST)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Fri, 24 Feb 2017 08:12:12 -0800
Mime-Version: 1.0
Message-Id: <p06240601d4d60d34ee17@[99.111.97.136]>
In-Reply-To: <69f9c707-345c-e90f-ba24-54173c311d72@omnitor.se>
References: <20170213161000.665a7a7059d7ee80bb4d670165c8327d.917539e857.wbe@email0 3.godaddy.com> <ddc5af1d-f084-f57e-d6c9-5963e4fe98d3@omnitor.se> <4c4ef65a-a907-cf5e-4b2c-835fb55d0146@omnitor.se> <p06240603d4c8f105055e@[99.111.97.136]> <434a4f06-f034-46ca-9df7-f59059e67e41@alumni.stanford.edu> <843f0cc1-2686-162d-25dc-0075847579bc@omnitor.se> <p06240609d4c937dc9ff8@[99.111.97.136]> <84760193-19e6-1f53-43cc-32b0493a1844@alumni.stanford.edu> <p0624060dd4c9523fcf2a@[99.111.97.136]> <4f1f3a72-d8a9-4f41-4133-0e6d54aadec8@omnitor.se> <a5ce4d13-309c-0bef-4b23-b44bb7c07c1b@omnitor.se> <p06240604d4ca31180a3d@[99.111.97.136]> <ce88e536-7675-b3f9-a999-314e2626056e@alum.mit.edu> <p06240609d4d3c1973459@[99.111.97.136]> <69f9c707-345c-e90f-ba24-54173c311d72@omnitor.se>
X-Mailer: Eudora for Mac OS X
Date: Fri, 24 Feb 2017 08:18:08 -0800
To: Gunnar =?iso-8859-1?Q?Hellstr=F6m?=  <gunnar.hellstrom@omnitor.se>, Paul Kyzivat <pkyzivat@alum.mit.edu>, slim@ietf.org, "ietf@ietf.org" <ietf@ietf.org>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: [Slim] IETF last call for  draft-ietf-slim-negotiating-human-language (Issue 8, section 6, IANA  registrations)
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
X-Random-Sig-Tag: 1.0b28
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/obQwJrnl3FYjYOxbtCcYqrktkKw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 16:21:54 -0000

At 9:06 AM +0100 2/24/17, Gunnar Hellstr=F6m wrote:

>  Den 2017-02-22 kl. 23:33, skrev Randall Gellens:
>>
>>  After reading through=20
>> draft-ietf-mmusic-sdp-mux-attributes, I agree=20
>> and have added "MUX Category:  normal" to both=20
>> attributes.
>  NORMAL    with capitals seems to be the form to=20
> register.  please change in the draft.

OK

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
[P]olitics, as a practice, whatever its professions, has always been
the systematic organization of hatreds.
                                    --American historian Henry Adams


From nobody Fri Feb 24 08:24:13 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A89791299AE; Fri, 24 Feb 2017 08:24:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 VAoWXPWu_RZi; Fri, 24 Feb 2017 08:24:08 -0800 (PST)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90A7212988C; Fri, 24 Feb 2017 08:24:08 -0800 (PST)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 0EBD14D9AD; Fri, 24 Feb 2017 16:24:08 +0000 (UTC)
Date: Fri, 24 Feb 2017 16:24:08 +0000
From: heasley <heas@shrubbery.net>
To: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170224162408.GD93870@shrubbery.net>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <20170224075940.GW2367@Space.Net> <4BC61E42-0A36-44E9-8FB9-2062547D939F@consulintel.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4BC61E42-0A36-44E9-8FB9-2062547D939F@consulintel.es>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BHCTJA9ZNikkK6EwxvGsYNGbuH4>
Cc: IPv6 Operations <v6ops@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 16:24:09 -0000

Fri, Feb 24, 2017 at 09:12:45AM +0100, JORDI PALET MARTINEZ:
> So, are we spending too much time in this and is not really necessary?
> 
> Can we live with the actual text with has been in the market, and working well, for “x” years?
> 
> Can we make too many (or few very important) changes in an RFC in the way to STD, or we need first to have those changes in an RFC for “x” years and “n” verified implementations, before we move to STD? If the answer is no, is the balance between living with the current text but moving to STD a better option than waiting for “x” years again?

I prefer the document is fixed now; start the process of fixing classful
implementations now, rather than in x years - or please save operators from
those x+ years of pain.


From nobody Fri Feb 24 08:27:41 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34AD01299CB for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 08:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-tRzVspxKwz for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 08:27:38 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 2B3111299AD for <ietf@ietf.org>; Fri, 24 Feb 2017 08:27:38 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id n127so22829786qkf.0 for <ietf@ietf.org>; Fri, 24 Feb 2017 08:27:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=6kv/dsJFWd+T48eZJj+6j07mbvd4g2kAWzVxKMjgYIg=; b=WKTEzqeEWat210Xjb+NW3yyiCOuWEXJvgva6hH4ZqGpRl4uxnOYswHTk9ps64N8SRU Pt5QwCRTKeSMI1l4DWXp4MfACTRXP3fLIkejTuMGmhvf6HOVKDd3yeAH86cIqamYjYLi 8BrFMC9b+ARXOn0rQX9SteP04u/7WHVq0+iRGT7fobTDa9Yc7i96K1D0NmB/cdknraw1 cIreemZQ7HxtL59Ie/ggt5zCAowysJj2xoIO2QboCW3ciuypMw+sImLuDx9PJL2OpB9j zE5s8+yjnl4bhT1dJCvAwCW1m8wpK3KkbVWw7Ui/eMdpKM6nDJsLs6eXkubgb/bxpcB4 z3Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=6kv/dsJFWd+T48eZJj+6j07mbvd4g2kAWzVxKMjgYIg=; b=JPGLgrnqFpIPZPhWTp/8vmuqURfO5E0u0ECYh5dd98gNYu5G4FkTF2SlQKaFb/N5iS pO3KkHpvLK28T7Bhy2KpRhfq88WEbGVuViHVP973qxl2fDoTFhMnHGIKt6dBSAihCh7O iZr06Bzt7F9e2/43UQQIXQej6PePT4QBc5uZ+3tEb8dl+rBpOZNJ+nRemX4GmmdMg0x7 ejAeK8wd3AHcclM5FAo077e+mTps3IZKgn4l12PTGa1AeqxjHDCCnxnivEJCPHTYGzrf 0HYCJSKMQJBtNuKILISj7GuyjHPqdXguRhCCVEDdccgTIsJo7WSEIqwkTKIWiKUjmddI ghvg==
X-Gm-Message-State: AMke39kzh6RnAz27d+kQcyEhDtTIQGr79d/gniE2mQSHHjA6XOEroDocf4EG45vd/harhxzh0U5FfgKnL7fBIw==
X-Received: by 10.55.140.134 with SMTP id o128mr3336674qkd.58.1487953657218; Fri, 24 Feb 2017 08:27:37 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Fri, 24 Feb 2017 08:27:36 -0800 (PST)
In-Reply-To: <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 24 Feb 2017 11:27:36 -0500
X-Google-Sender-Auth: LOI5jTc_EiInOcmUR2ZPS8Tqp9Q
Message-ID: <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=94eb2c0548d82e7cbe0549493566
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VkEBEU1EvN0-14W7g-FwuUIOpOU>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 16:27:39 -0000

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

On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 24/02/2017 =C3=A0 15:59, Christopher Morrow a =C3=A9crit :
>
>>
>>
>> On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
>>  wrote:
>>
>>
>> A question to Windows is the following: what prefixlen does it set
>> when the end user manually assigns an address on an interface without
>> specifiying a prefixlen?
>>
>>
>> I don't think this matters... 'end users' will in almost all cases
>> just attach and get connectivity.
>>
>
> Let me go next in cycle: what does linux do when one ifconfig add an
> IPv6 address without telling the plen?  Is it adding an entry in the rt
> table?  Which plen?  Is that plen normal?
>
>
still don't think this matters. If a user messes up what they type, they
messed up.
if the instructions aren't complete, they aren't complete and there will be
mistakes.
An interface configuration requires all proper parameters be set, or
problems will arise. Assumptions about current and future behavior are
proven wrong time and again.

non-deterministic behavior over time is the hallmark of this space...
please do not rely on defaults for hand-managed/bespoke configurations if
you expect things to work reliably and repeatably.

If they are in a place where someone says: "Hey, you should go
>> if/ipconfig ...." then .. they are 'consenting adults' and can do
>> whatever they please.
>>
>
> I assume you assume that ip/ifconfig by consenting adults means the
> adults type a plen in the CLI, right?
>
>
sure, or a script/program/etc does this, it's not important how the
'ifconfig' happens, it's important that when it happens the right
parameters are passed to the 'ifconfig' command.


> That makes it mandatory that the CLI _requires_ a plen, right?  That CLI
> should not allow silence for a plen parameter.
>
>
sure, or you are at the mercy of the implementor of that command:
  Today I like /64!
  It's tomorrow and now I like /62!!

don't rely on defaults.


> Because silent plen means 64.  And I dont think it's right to assume a
> by-default 64 plen.  Because many people think 64 is right and others
> think it's wrong, there does not seem to be a commonly agreed 'by
> default' value for plen.
>
>
correct, so.. be specific in your configuration effort please... which
again, means that the 'what is the default?" conversation is moot.


> Alex
>
>
>
>> again the proposed text (now 175+ messages back) really covers this
>> already..
>>
>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu <span dir=3D"ltr">=
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex"><span class=3D""><br>
<br>
Le 24/02/2017 =C3=A0 15:59, Christopher Morrow a =C3=A9crit :<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><span class=3D"">
<br>
<br>
On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu<br></span>
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a> &lt;mailto:<a href=3D"mailto:alexandre.petrescu=
@gmail.com" target=3D"_blank">alexandre.petrescu@gma<wbr>il.com</a>&gt;&gt;=
<span class=3D""><br>
=C2=A0wrote:<br>
<br>
<br>
A question to Windows is the following: what prefixlen does it set<br>
when the end user manually assigns an address on an interface without<br>
specifiying a prefixlen?<br>
<br>
<br>
I don&#39;t think this matters... &#39;end users&#39; will in almost all ca=
ses<br>
just attach and get connectivity.<br>
</span></blockquote>
<br>
Let me go next in cycle: what does linux do when one ifconfig add an<br>
IPv6 address without telling the plen?=C2=A0 Is it adding an entry in the r=
t<br>
table?=C2=A0 Which plen?=C2=A0 Is that plen normal?<span class=3D""><br>
<br></span></blockquote><div><br></div><div>still don&#39;t think this matt=
ers. If a user messes up what they type, they messed up.</div><div>if the i=
nstructions aren&#39;t complete, they aren&#39;t complete and there will be=
 mistakes.</div><div>An interface configuration requires all proper paramet=
ers be set, or problems will arise. Assumptions about current and future be=
havior are proven wrong time and again.</div><div>=C2=A0</div><div>non-dete=
rministic behavior over time is the hallmark of this space... please do not=
 rely on defaults for hand-managed/bespoke configurations if you expect thi=
ngs to work reliably and repeatably.</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><span class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If they are in a place where someone says: &quot;Hey, you should go<br>
if/ipconfig ....&quot; then .. they are &#39;consenting adults&#39; and can=
 do<br>
whatever they please.<br>
</blockquote>
<br></span>
I assume you assume that ip/ifconfig by consenting adults means the<br>
adults type a plen in the CLI, right?<br>
<br></blockquote><div><br></div><div>sure, or a script/program/etc does thi=
s, it&#39;s not important how the &#39;ifconfig&#39; happens, it&#39;s impo=
rtant that when it happens the right parameters are passed to the &#39;ifco=
nfig&#39; command.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
That makes it mandatory that the CLI _requires_ a plen, right?=C2=A0 That C=
LI<br>
should not allow silence for a plen parameter.<br>
<br></blockquote><div><br></div><div>sure, or you are at the mercy of the i=
mplementor of that command:<br>=C2=A0 Today I like /64!</div><div>=C2=A0 It=
&#39;s tomorrow and now I like /62!!</div><div><br></div><div>don&#39;t rel=
y on defaults.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Because silent plen means 64.=C2=A0 And I dont think it&#39;s right to assu=
me a<br>
by-default 64 plen.=C2=A0 Because many people think 64 is right and others<=
br>
think it&#39;s wrong, there does not seem to be a commonly agreed &#39;by<b=
r>
default&#39; value for plen.<br>
<br></blockquote><div><br></div><div>correct, so.. be specific in your conf=
iguration effort please... which again, means that the &#39;what is the def=
ault?&quot; conversation is moot.</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
Alex<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
again the proposed text (now 175+ messages back) really covers this<br>
already..<br>
</blockquote>
</div></div></blockquote></div><br></div></div>

--94eb2c0548d82e7cbe0549493566--


From nobody Fri Feb 24 09:09:45 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27BAB128B44 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 09:09:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 EGd_Ks248OOw for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 09:09:42 -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 2DF971293FB for <ietf@ietf.org>; Fri, 24 Feb 2017 09:09:42 -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 v1OH9dwi012101; Fri, 24 Feb 2017 18:09:39 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id AF0FA20B9B2; Fri, 24 Feb 2017 18:09:39 +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 A157D20B905; Fri, 24 Feb 2017 18:09:39 +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 v1OH9d9F014116; Fri, 24 Feb 2017 18:09:39 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com>
Date: Fri, 24 Feb 2017 18:09:29 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r7dJHcNAGevEVDiYrO3gASEZD6o>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 17:09:44 -0000

Le 24/02/2017 à 17:27, Christopher Morrow a écrit :
>
>
> On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
> wrote:
>
>
>
> Le 24/02/2017 à 15:59, Christopher Morrow a écrit :
>
>
>
> On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>
> <mailto:alexandre.petrescu@gmail.com
> <mailto:alexandre.petrescu@gmail.com>>> wrote:
>
>
> A question to Windows is the following: what prefixlen does it set
> when the end user manually assigns an address on an interface
> without specifiying a prefixlen?
>
>
> I don't think this matters... 'end users' will in almost all cases
> just attach and get connectivity.
>
>
> Let me go next in cycle: what does linux do when one ifconfig add an
> IPv6 address without telling the plen?  Is it adding an entry in the
> rt table?  Which plen?  Is that plen normal?
>
>
> still don't think this matters. If a user messes up what they type,
> they messed up. if the instructions aren't complete, they aren't
> complete and there will be mistakes. An interface configuration
> requires all proper parameters be set, or problems will arise.
> Assumptions about current and future behavior are proven wrong time
> and again.
>
> non-deterministic behavior over time is the hallmark of this
> space... please do not rely on defaults for hand-managed/bespoke
> configurations if you expect things to work reliably and repeatably.

That means the following: Windows please make the plen parameter
mandatory.  Dont leave it optional only to subversively set it to 64.
That's a software bug because nobody asks you to set the plen to 64 when
the end user does not specify one.

I guess the same bug is is in BSD, linux and what have you.

>
> If they are in a place where someone says: "Hey, you should go
> if/ipconfig ...." then .. they are 'consenting adults' and can do
> whatever they please.
>
>
> I assume you assume that ip/ifconfig by consenting adults means the
> adults type a plen in the CLI, right?
>
>
> sure, or a script/program/etc does this, it's not important how the
> 'ifconfig' happens, it's important that when it happens the right
> parameters are passed to the 'ifconfig' command.

I agree.  If 'ifconfig' silently assumes 64 then that assumption is
wrong.  The ifconfig programmer should take that as a software bug.
It's not an RFC that requires them to put 64 there.

> That makes it mandatory that the CLI _requires_ a plen, right?  That
> CLI should not allow silence for a plen parameter.
>
>
> sure, or you are at the mercy of the implementor of that command:
> Today I like /64! It's tomorrow and now I like /62!!
>
> don't rely on defaults.

I agree.

> Because silent plen means 64.  And I dont think it's right to assume
> a by-default 64 plen.  Because many people think 64 is right and
> others think it's wrong, there does not seem to be a commonly agreed
> 'by default' value for plen.
>
>
> correct, so.. be specific in your configuration effort please...
> which again, means that the 'what is the default?" conversation is
> moot.

I am not asking what is the default.

I am saying that apparently numerous implementations out there consider
the default to be 64.  This consideration is wrong.

A 'default' value is something that everybody agrees with.  For example,
one can leave out '::' from a command line adding a default route and
just say 'default'.  There is an agreed standard that says that
'default' is '::'.

But there is by far no single standard that says the default prefix
length is 64.

That's why it's a bug.

It's like boxes with pre-defined passwords admin/admin.  The local
programmer imagined it a good 'default' but never asked around the
validity of such assumption.  And that creates problems.

Alex

>
>
> Alex
>
>
>
> again the proposed text (now 175+ messages back) really covers this
> already..
>
>


From nobody Fri Feb 24 09:53:10 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB97D12944A for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 09:53:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uOIDT-GCkEfz for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 09:53:08 -0800 (PST)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::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 C4146129444 for <ietf@ietf.org>; Fri, 24 Feb 2017 09:53:07 -0800 (PST)
Received: by mail-qt0-x230.google.com with SMTP id r45so22599249qte.3 for <ietf@ietf.org>; Fri, 24 Feb 2017 09:53:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=OdAtWZQDCTsQyn+vgdFWibFtbDH8//2IfbwuAt3PF6U=; b=oOMKFDt2HjJZtmkvfc0e2B2ED1EvEzMoMAyzpZkvjaTHzE4DkXVPF1EeC6Wo6Lpa/V WrPBrAT8+OqxaiGb84ewUnFfIdIh6wcknRhnD9oMHzFJD57x+OQNobNpdmvYaXAgIJl7 SPBxCcAtlhn6ZSR7oidEskaJMRASkbjMFnWIe0CUkQh5eFMV1FEyTCe+cvWXmfLbT/7n 9KC6TsQu/jKTb5998hXl1m2DdkIn507SNLlOKOa6AISDeryJosffaFzXkQiRtdMQ3Bjo ejxSqMOOxp+oAfPgngfRYdvmz9NhwMHSJNxDhvBpXttI907ffInzwqOxU4wYGNO8vwDs c8Bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=OdAtWZQDCTsQyn+vgdFWibFtbDH8//2IfbwuAt3PF6U=; b=FBHFdMdb9GP5z6zPD+fDnRnqBhzUVDU8UZ5YMa3iwANRlYsi4wGCpbbAArNAKVXm72 lAeR0BQipZ4nPWn7se6jZaa+q1ICgDJBljhvbUKKJR3h/1PPcY+F3JXvJNFuLeZZ6bMq jrNDmt2HMJI60sCmxEkxeE9iJBdgoEvC7H5cbwW9a2hmGUcEGs8cCtwsTFiCzLS6ZiRe dxOpoCiew/8b/n4oCKWAJnBg5aTLc/NulIz1PZb/tmfFWd4esw2zYDyNP0oYhnGMSbu7 fQzHMh3mf2+1Mnzyb+XJsXR0frJTrjmNOucc4coNtxdeWnSpu43RjFtsGhT+m+QVowTN 3jtQ==
X-Gm-Message-State: AMke39n65HemUS8LGiPN6ozU7aBB4+xlbJIGUcIK8Nn5HvyaquVj/eiPqItSEvyg0npfxLSZZk3mziY6RkTB3g==
X-Received: by 10.200.45.137 with SMTP id p9mr3942704qta.201.1487958786828; Fri, 24 Feb 2017 09:53:06 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Fri, 24 Feb 2017 09:53:06 -0800 (PST)
In-Reply-To: <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com> <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 24 Feb 2017 12:53:06 -0500
X-Google-Sender-Auth: hXSdtImlgZUAGkzc6Wu2yaY2gnM
Message-ID: <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a1136fb18edf62405494a66d5
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U1RJBFO2gJDnf1ZiH8W6YadFRMQ>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 17:53:09 -0000

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

On Fri, Feb 24, 2017 at 12:09 PM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 24/02/2017 =C3=A0 17:27, Christopher Morrow a =C3=A9crit :
>
>>
>>
>> On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>
>> wrote:
>>
>>
>>
>> Le 24/02/2017 =C3=A0 15:59, Christopher Morrow a =C3=A9crit :
>>
>>
>>
>> On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>
>> <mailto:alexandre.petrescu@gmail.com
>> <mailto:alexandre.petrescu@gmail.com>>> wrote:
>>
>>
>> A question to Windows is the following: what prefixlen does it set
>> when the end user manually assigns an address on an interface
>> without specifiying a prefixlen?
>>
>>
>> I don't think this matters... 'end users' will in almost all cases
>> just attach and get connectivity.
>>
>>
>> Let me go next in cycle: what does linux do when one ifconfig add an
>> IPv6 address without telling the plen?  Is it adding an entry in the
>> rt table?  Which plen?  Is that plen normal?
>>
>>
>> still don't think this matters. If a user messes up what they type,
>> they messed up. if the instructions aren't complete, they aren't
>> complete and there will be mistakes. An interface configuration
>> requires all proper parameters be set, or problems will arise.
>> Assumptions about current and future behavior are proven wrong time
>> and again.
>>
>> non-deterministic behavior over time is the hallmark of this
>> space... please do not rely on defaults for hand-managed/bespoke
>> configurations if you expect things to work reliably and repeatably.
>>
>
> That means the following: Windows please make the plen parameter
> mandatory.  Dont leave it optional only to subversively set it to 64.
> That's a software bug because nobody asks you to set the plen to 64 when
> the end user does not specify one.
>
> I guess the same bug is is in BSD, linux and what have you.
>
>
yes, I think so.. for linux:
$ sudo ip -6 addr add 2001:700:4::1 dev em1

gets me:
 inet6 2001:700:4::1/128 scope global

so that actually seems correct.


>
>> If they are in a place where someone says: "Hey, you should go
>> if/ipconfig ...." then .. they are 'consenting adults' and can do
>> whatever they please.
>>
>>
>> I assume you assume that ip/ifconfig by consenting adults means the
>> adults type a plen in the CLI, right?
>>
>>
>> sure, or a script/program/etc does this, it's not important how the
>> 'ifconfig' happens, it's important that when it happens the right
>> parameters are passed to the 'ifconfig' command.
>>
>
> I agree.  If 'ifconfig' silently assumes 64 then that assumption is
> wrong.  The ifconfig programmer should take that as a software bug.
> It's not an RFC that requires them to put 64 there.
>
>
ok


> That makes it mandatory that the CLI _requires_ a plen, right?  That
>> CLI should not allow silence for a plen parameter.
>>
>>
>> sure, or you are at the mercy of the implementor of that command:
>> Today I like /64! It's tomorrow and now I like /62!!
>>
>> don't rely on defaults.
>>
>
> I agree.
>
> Because silent plen means 64.  And I dont think it's right to assume
>> a by-default 64 plen.  Because many people think 64 is right and
>> others think it's wrong, there does not seem to be a commonly agreed
>> 'by default' value for plen.
>>
>>
>> correct, so.. be specific in your configuration effort please...
>> which again, means that the 'what is the default?" conversation is
>> moot.
>>
>
> I am not asking what is the default.
>
> I am saying that apparently numerous implementations out there consider
> the default to be 64.  This consideration is wrong.
>
>
yes, I agree with you here.


> A 'default' value is something that everybody agrees with.  For example,
> one can leave out '::' from a command line adding a default route and
> just say 'default'.  There is an agreed standard that says that
> 'default' is '::'.
>
> But there is by far no single standard that says the default prefix
> length is 64.
>
> That's why it's a bug.
>
> It's like boxes with pre-defined passwords admin/admin.  The local
> programmer imagined it a good 'default' but never asked around the
> validity of such assumption.  And that creates problems.


ok, cool, i think we agree on all of this at least :)


>

Alex
>
>
>
>>
>> Alex
>>
>>
>>
>> again the proposed text (now 175+ messages back) really covers this
>> already..
>>
>>
>>

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 12:09 PM, Alexandre Petrescu <span dir=3D"ltr">=
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><span class=3D"gmail-"><br>
<br>
Le 24/02/2017 =C3=A0 17:27, Christopher Morrow a =C3=A9crit :<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gma=
il-">
<br>
<br>
On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu<br></span>
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a> &lt;mailto:<a href=3D"mailto:alexandre.petrescu=
@gmail.com" target=3D"_blank">alexandre.petrescu@gma<wbr>il.com</a>&gt;&gt;=
<span class=3D"gmail-"><br>
wrote:<br>
<br>
<br>
<br>
Le 24/02/2017 =C3=A0 15:59, Christopher Morrow a =C3=A9crit :<br>
<br>
<br>
<br>
On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu<br>
&lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexa=
ndre.petrescu@gmail.com</a> &lt;mailto:<a href=3D"mailto:alexandre.petrescu=
@gmail.com" target=3D"_blank">alexandre.petrescu@gma<wbr>il.com</a>&gt;<br>=
</span>
&lt;mailto:<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank=
">alexandre.petrescu@gma<wbr>il.com</a><span class=3D"gmail-"><br>
&lt;mailto:<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank=
">alexandre.petrescu@gma<wbr>il.com</a>&gt;&gt;&gt; wrote:<br>
<br>
<br>
A question to Windows is the following: what prefixlen does it set<br>
when the end user manually assigns an address on an interface<br>
without specifiying a prefixlen?<br>
<br>
<br>
I don&#39;t think this matters... &#39;end users&#39; will in almost all ca=
ses<br>
just attach and get connectivity.<br>
<br>
<br>
Let me go next in cycle: what does linux do when one ifconfig add an<br>
IPv6 address without telling the plen?=C2=A0 Is it adding an entry in the<b=
r>
rt table?=C2=A0 Which plen?=C2=A0 Is that plen normal?<br>
<br>
<br>
still don&#39;t think this matters. If a user messes up what they type,<br>
they messed up. if the instructions aren&#39;t complete, they aren&#39;t<br=
>
complete and there will be mistakes. An interface configuration<br>
requires all proper parameters be set, or problems will arise.<br>
Assumptions about current and future behavior are proven wrong time<br>
and again.<br>
<br>
non-deterministic behavior over time is the hallmark of this<br>
space... please do not rely on defaults for hand-managed/bespoke<br>
configurations if you expect things to work reliably and repeatably.<br>
</span></blockquote>
<br>
That means the following: Windows please make the plen parameter<br>
mandatory.=C2=A0 Dont leave it optional only to subversively set it to 64.<=
br>
That&#39;s a software bug because nobody asks you to set the plen to 64 whe=
n<br>
the end user does not specify one.<br>
<br>
I guess the same bug is is in BSD, linux and what have you.<span class=3D"g=
mail-"><br>
<br></span></blockquote><div><br></div><div>yes, I think so.. for linux:<br=
>$ sudo ip -6 addr add 2001:700:4::1 dev em1<br></div><div><br></div><div>g=
ets me:<br><div>=C2=A0inet6 2001:700:4::1/128 scope global=C2=A0</div></div=
><div><br></div><div>so that actually seems correct.</div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
If they are in a place where someone says: &quot;Hey, you should go<br>
if/ipconfig ....&quot; then .. they are &#39;consenting adults&#39; and can=
 do<br>
whatever they please.<br>
<br>
<br>
I assume you assume that ip/ifconfig by consenting adults means the<br>
adults type a plen in the CLI, right?<br>
<br>
<br>
sure, or a script/program/etc does this, it&#39;s not important how the<br>
&#39;ifconfig&#39; happens, it&#39;s important that when it happens the rig=
ht<br>
parameters are passed to the &#39;ifconfig&#39; command.<br>
</blockquote>
<br></span>
I agree.=C2=A0 If &#39;ifconfig&#39; silently assumes 64 then that assumpti=
on is<br>
wrong.=C2=A0 The ifconfig programmer should take that as a software bug.<br=
>
It&#39;s not an RFC that requires them to put 64 there.<span class=3D"gmail=
-"><br>
<br></span></blockquote><div><br></div><div>ok</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
That makes it mandatory that the CLI _requires_ a plen, right?=C2=A0 That<b=
r>
CLI should not allow silence for a plen parameter.<br>
<br>
<br>
sure, or you are at the mercy of the implementor of that command:<br>
Today I like /64! It&#39;s tomorrow and now I like /62!!<br>
<br>
don&#39;t rely on defaults.<br>
</blockquote>
<br></span>
I agree.<span class=3D"gmail-"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
Because silent plen means 64.=C2=A0 And I dont think it&#39;s right to assu=
me<br>
a by-default 64 plen.=C2=A0 Because many people think 64 is right and<br>
others think it&#39;s wrong, there does not seem to be a commonly agreed<br=
>
&#39;by default&#39; value for plen.<br>
<br>
<br>
correct, so.. be specific in your configuration effort please...<br>
which again, means that the &#39;what is the default?&quot; conversation is=
<br>
moot.<br>
</blockquote>
<br></span>
I am not asking what is the default.<br>
<br>
I am saying that apparently numerous implementations out there consider<br>
the default to be 64.=C2=A0 This consideration is wrong.<br>
<br></blockquote><div><br></div><div>yes, I agree with you here.</div><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
A &#39;default&#39; value is something that everybody agrees with.=C2=A0 Fo=
r example,<br>
one can leave out &#39;::&#39; from a command line adding a default route a=
nd<br>
just say &#39;default&#39;.=C2=A0 There is an agreed standard that says tha=
t<br>
&#39;default&#39; is &#39;::&#39;.<br>
<br>
But there is by far no single standard that says the default prefix<br>
length is 64.<br>
<br>
That&#39;s why it&#39;s a bug.<br>
<br>
It&#39;s like boxes with pre-defined passwords admin/admin.=C2=A0 The local=
<br>
programmer imagined it a good &#39;default&#39; but never asked around the<=
br>
validity of such assumption.=C2=A0 And that creates problems.</blockquote><=
div><br></div><div>ok, cool, i think we agree on all of this at least :)</d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=C2=
=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Alex<div class=3D"gmail-HOEnZb"><div class=3D"gmail-h5"><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
Alex<br>
<br>
<br>
<br>
again the proposed text (now 175+ messages back) really covers this<br>
already..<br>
<br>
<br>
</blockquote>
</div></div></blockquote></div><br></div></div>

--001a1136fb18edf62405494a66d5--


From nobody Fri Feb 24 10:05:10 2017
Return-Path: <shitanshu_shah@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6693F12944C; Fri, 24 Feb 2017 10:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.02
X-Spam-Level: 
X-Spam-Status: No, score=-2.02 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zwqks5DsVNvA; Fri, 24 Feb 2017 10:05:05 -0800 (PST)
Received: from BAY004-OMC3S15.hotmail.com (bay004-omc3s15.hotmail.com [65.54.190.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531DD12945F; Fri, 24 Feb 2017 10:05:05 -0800 (PST)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com ([65.54.190.189]) by BAY004-OMC3S15.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Fri, 24 Feb 2017 10:05:04 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=k7bc2Mup9gC5iL7apsALptW0M+pFo0OEoDDx83GvS8c=; b=npZcfe+L3s33GOoXy7T1lrIAReCMX30ML0p8rxQu+jrV1NtmqvA8Rs1iuWeocryjD8pdcXoTrO9640k+SGZ7z20Sl+roidFI0Cc76VPpzC4wFKHN+bt+2TXG3oWovjdmnRlSwCAkNu5k7OkggNOnLwJTu3OrrEmmecmXejggnma3F+v6hP3XGIpk5mF3oyUclu6rUMyaYt16bUxKUbrBh6sDCXypnNpsLQfk8QYwnJj3Tj0irITkjfHi2CcMqUuJuhVIx8q0AFbiSHcCQaLPXHsewVvyN6/KCoLr3mCy/6ssKinxDTlISXMh1tTN7Oug+lZA/AF21lCHlkoRCxNFuA==
Received: from SN1NAM02FT033.eop-nam02.prod.protection.outlook.com (10.152.72.59) by SN1NAM02HT115.eop-nam02.prod.protection.outlook.com (10.152.73.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Fri, 24 Feb 2017 18:05:03 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com (10.152.72.60) by SN1NAM02FT033.mail.protection.outlook.com (10.152.72.133) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10 via Frontend Transport; Fri, 24 Feb 2017 18:05:03 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) by DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) with mapi id 15.01.0933.011; Fri, 24 Feb 2017 18:05:03 +0000
From: Shitanshu Shah <shitanshu_shah@hotmail.com>
To: "Black, David" <David.Black@dell.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjJJLT08h8arb7kKXAYa1wCM/2KF32nBggAB4pYCAACEyqw==
Date: Fri, 24 Feb 2017 18:05:02 +0000
Message-ID: <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:B9E947B70435A1E9A89403BB8F68D449ED89013DCE32C30411F1405A643B00AB; UpperCasedChecksum:D36E9CFD16BE57215670AEDB58518ABC2868835187B1A1C2C97B4E0575452C11; SizeAsReceived:8146; Count:40
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [qIfDCqBQ3MQIDxFbQ7cukkNueWqwPaGz]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; SN1NAM02HT115; 5:p2VLU54M1dff+5cq5CzghmTFml8kwuLDzCtTWPQB16j5rNFUB06xuf4u7L2/05lRlO4rrlYfZ/rJ0MT6cPzd4lphNF6CZWDdNHWaeNGK8Ecrhl4nJXEuPuJDwAXqe+Q7G1toVrPN+yXQGRXWx1KBs0a9y8J6fSnLS4BI/bDHuAI=; 24:YGIpWTmEWdAUR1HOhkbg44deElYZ0HGkum21pnqXd7ohThW7leOvGptqdzOM3qVT5KFfSUX0qlJGIXdH4twvTXthR7uLwEeZXq1mKzEJ8d4=; 7:N7ht5VKaKAsTL4FH9ZoPmQ0PKc9IQY3EdR+lyQFdnTIcx+ARfoeMdqL9mJqp3d+R9+enlmuihCqgKH7ctTZ5Ztoywx4jrG+W9/M6KjdZI3fRZYkoHQEVGORg/ofjko74Xe49To/SXeC34lahGTaZZfJ7kHLZyufFINzKkvyOVd9xMP3eQUUPhtLK01J0e0Uvz5g94RGbhSrH4QRODwbQ1Bty51m9gxNTY+daULN6htZiNNuUkQToJDXVmjF7EzEs3sYcn6MDoLqfRTcV4N8lCeMwRdXryl+F0ak9cV93/WbQ4r6J/6BSBrk/ikitKRw2
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1NAM02HT115; H:DM3PR13MB0604.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: c33233cc-3248-4f5b-80af-08d45cdfa7ea
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1603101415)(1601125254)(1701031045); SRVR:SN1NAM02HT115; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:SN1NAM02HT115; BCL:0; PCL:0; RULEID:; SRVR:SN1NAM02HT115; 
x-forefront-prvs: 0228DDDDD7
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM3PR13MB0604865EC77A246609544830E5520DM3PR13MB0604namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Feb 2017 18:05:02.7739 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM02HT115
X-OriginalArrivalTime: 24 Feb 2017 18:05:05.0008 (UTC) FILETIME=[869B1700:01D28EC8]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fgrJ3rrciEFUCc7gMb3pN1vVz-c>
Cc: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:05:08 -0000

--_000_DM3PR13MB0604865EC77A246609544830E5520DM3PR13MB0604namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Hi David,


One response inline ##svshah2


________________________________
From: Black, David <David.Black@dell.com>
Sent: Friday, February 24, 2017 8:53 AM
To: Shitanshu Shah; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org; =
Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That=92s simpler, and a few sentences of discus=
sion about possible L2 framing differences should cover what needs to be do=
ne (e.g., if traffic rates are configured in terms of L2 octets, then expla=
in how each entity converts between IP traffic and L2 traffic - the draft a=
lready effectively contains that explanation).

##svshah2, just to make sure that some of the real use are not left out..

For the traffic conditioning where sla established is for the ip based rate=
s only, it suffices for the Producer to send rates only IP based ignoring a=
ny specific of l2 overheads.

Though for the cases where physical links are not to be over-run, and/or, s=
la defined are based on l2 rates, the Consumer would need to know l2 overhe=
ad from the Producer. Otherwise 10 byes of l2 overhead difference on 64 byt=
es packets can be significant compare to on 1400 bytes packets, and thus th=
e Producer does not have a way to convert rates to ip based (this can cause=
 functional issue), since this has to be per packet consideration.

Regards,
Shitanshu




[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that=92s an editorial choice - I prefer to explain how something=
 works before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn=92t adopted that design is that we don=92t want to=
 make assumptions on which data the remote peer will be used for enforcing =
local actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That=92s fine, I wanted to ensure that this had been considered.  Th=
e discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind=92t include a context field because we thought that the defin=
ition of the IPFIX attributes is sufficient by itself, but if you do think =
it is helpful to have such information, we can update the table.

David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it=92s the link that crosses the =
relevant AS boundary, but that does have to be stated, as it=92s nowhere to=
 be found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??


[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don=92t see specificat=
ion of what has to be implemented in either the text in the draft or the ab=
ove explanations.

        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.



[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the =93exercise to the reader=94  criticism - one way to =
be honest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the =93outside the scope of this document=94 statement i=
s wrong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn=92t catch the reference, RFC 6919 is an April 1 =
RFC ... and the =93SHOULD BE considered=94 language used in the last securi=
ty considerations paragraph of this draft is accurately characterized as va=
gue in Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------



--_000_DM3PR13MB0604865EC77A246609544830E5520DM3PR13MB0604namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><br>
</p>
<p>Hi David,</p>
<p><br>
</p>
<p>One response inline ##svshah2</p>
<br>
<br>
<div>
<hr tabindex=3D"-1" style=3D"color: rgb(0, 0, 0); display: inline-block; wi=
dth: 98%;">
<div id=3D"divRplyFwdMsg" dir=3D"ltr" style=3D"color: rgb(0, 0, 0);"><font =
face=3D"Calibri, sans-serif" color=3D"#000000" style=3D"font-size:11pt"><b>=
From:</b> Black, David &lt;David.Black@dell.com&gt;<br>
<b>Sent:</b> Friday, February 24, 2017 8:53 AM<br>
<b>To:</b> Shitanshu Shah; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</font>
<div>&nbsp;</div>
</div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; Inline ...</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">&nbsp;</span></p>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Thanks, --David</span><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">&nbsp;</span></p>
<div style=3D"border-style: none none none solid; border-left-color: blue; =
border-left-width: 1.5pt; padding: 0in 0in 0in 4pt;">
<div style=3D"color: rgb(0, 0, 0);">
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Shitan=
shu Shah [mailto:shitanshu_shah@hotmail.com]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);">&nbsp;</p>
<div id=3D"divtagdefaultwrapper">
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">Hi David,</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">Thank you for taking time for th=
e review..</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">Please find our response inline =
##svshah and [Med]</span></p>
<p style=3D"color: rgb(0, 0, 0);"><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Regards,
</span></p>
<div>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); margin-bottom: 12pt;">=
<span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; colo=
r:black">Shitanshu</span></p>
<div>
<div style=3D"color: rgb(0, 0, 0);">
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:bla=
ck">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt; font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black">From:</span></b><span =
style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;; color:black"> David Black &lt;<a href=3D"mailto:david.black@emc.com=
">david.black@emc.com</a>&gt;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">
</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
</div>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">Reviewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142" previewremoved=3D"true">https://en.wikipedia.org/wiki/Service-lev=
el_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0); margin-bottom: 12pt;">=
<span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D">David&gt; That would be good, thanks.</=
span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.</span></p>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, the purpose for=
 advertising L2 overhead, from the Producer to the Consumer,&nbsp;is to mak=
e sure traffic is well conditioned, at the egress of the&nbsp;Consumer,
 to avoid possible indiscriminate drops at the ingress of the Producer. In =
another words, the&nbsp;Producer is telling the&nbsp;Consumer to ignore its=
 own link level overhead, instead use Producer's provided link level overhe=
ad while running frames through QoS functions
 (this is&nbsp;relevant in use-cases where l2 overhead of the&nbsp;egress l=
ink on Consumer and of ingress link on the Producer are of different size, =
e.g., in the&nbsp;vpn/tunnel connection between two peer&nbsp;nodes which p=
hysically may be multiple hops away).</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">I understand your comment=
s regarding re-using TSpec without any modification.&nbsp;Do you agree with=
 the use-case of l2 differences? If yes, any suggestion how to
 accommodate that?</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Specifying th=
is in terms of IP octets implies that L2 overhead is to be ignored on both =
links.&nbsp; That=92s simpler, and a few sentences of discussion about
 possible L2 framing differences should cover what needs to be done (e.g., =
if traffic rates are configured in terms of L2 octets, then explain how eac=
h entity converts between IP traffic and L2 traffic - the draft already eff=
ectively contains that explanation).</span><span style=3D"font-size:10.0pt;=
 font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"></spa=
n></p>
</div>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack">##svshah2, just to make sure that some of the real use are not left o=
ut..</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span></p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2">For th=
e traffic conditioning where sla established is for the ip based rates only=
, it suffices for the Producer to&nbsp;send rates only IP based ignoring an=
y specific of l2 overheads.</font></p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2"><br>
</font></p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2">Though=
 for the cases where&nbsp;physical&nbsp;links are not to be&nbsp;over-run, =
and/or,&nbsp;sla defined are based on l2 rates, the&nbsp;Consumer would nee=
d to know l2 overhead from the Producer. Otherwise 10 byes of l2
 overhead difference on 64 bytes packets can be significant compare to on 1=
400 bytes packets, and thus the Producer does not have a way to convert rat=
es to&nbsp;ip based (this can cause functional issue), since this has to be=
 per packet consideration.</font></p>
<p class=3D"MsoNormal"><br>
</p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2">Regard=
s,</font></p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2">Shitan=
shu</font></p>
<p class=3D"MsoNormal"><font face=3D"Calibri, sans-serif" size=3D"2"><br>
</font></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"color: rgb(0, 0, 0);"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, what you descri=
be below conceptually very much makes sense and that is what we attempt to =
achieve. What is unclear though how to capture that using
 TSpec definition specified in RFC2215. Since that TSpec definition has bot=
h minimum-rate and maximum-rate, but no in/out profile marking parameters.<=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">Is your proposal below to=
 define two TSpecs using the same&nbsp;definition from RFC2215? Wouldn't in=
 that case we have min/max specified twice? min/max in each TSpec?
 and thus confusing to represent one min and one max through two TSpecs?</s=
pan></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; See RFC 2698 =
for the desired behavior and the parameters needed to specify it.&nbsp; The=
 current idr-sla draft is not able to represent the traffic conditioning
 mechanisms specified in both RFC 2698 and RFC 2697, as each mechanism requ=
ires two token buckets (e.g., there are two burst sizes, but the idr-sla dr=
aft TSpec only contains one).&nbsp; This deficiency needs to be dealt with.=
&nbsp; One possibility for simplification
 is to drop the max-rate from the RFC 2115 TSpec and assume that the max-ra=
te for bursting is the effective line rate.</span><span style=3D"font-size:=
10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black=
"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt; fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
 font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt; f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah,&nbsp;It is arou=
nd the semantics of&nbsp;a single queue with a different threshold for a se=
t of code-points, where packet for a specific code-point is to be
 tail dropped if overall queue-depth hits code-point specific threshold at =
the arrival of that packet.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">We will add appropriate c=
larification for this semantics.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; Will look at revision
</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, Sure. Is follow=
ing clarification okay? (some of the wordings taken from RFC2598)</span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&quot;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">A higher priority class o=
f traffic&nbsp;to be served without pre-empted by lower priority&nbsp;class=
 of traffic&nbsp;for more than a packet time at the configured rate.</span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">In the system that implem=
ents WRR, the use of relative priority may get restricted where a single qu=
eue may be used for a&nbsp;higher priority traffic class where
 that queue &nbsp;is configured for the full share of the output bandwidth.=
</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&quot;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; Last sentence basically says that WRR weights are out-of-=
scope.&nbsp; That seems wrong.&nbsp; Will look at revision.</span><span sty=
le=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;; color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, They are to fac=
ilitate hierarchy. A specific Traffic Class, can further be divided in a mu=
ltiple &nbsp;subset of&nbsp;Traffic Classes, with their own Traffic
 Class Elements and Traffic Class Services.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">Will correct the wording =
to remove your this specific concern.</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D">David&gt; Will look at revision
</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, While&nbsp;even=
tually &quot;Traffic Conditioning Agreement&quot; should be translated to t=
he actual forwarding qos policy on any vendor specific device, TCA exchange
 largely carries concepts/semantics that is either standard based or&nbsp;w=
ell understood.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">While we are not aware of=
 any working group document of QoS Yang Model, we think that &nbsp;concepts=
 of Traffic Conditioning should be easily adaptable to any QoS
 Yang Models since they also have to be defined to support those concepts.<=
/span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Still want to=
 see cross-check with implementations here.</span><span style=3D"font-size:=
10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black=
"><br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; OK, thanks.</=
span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
 color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[9] In section 3.2, the &quot;intended fo=
r the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">UPDATE message&quot; text in the specific=
ation of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">flags is unclear.&nbsp; I suspect that th=
is is intended to differentiate</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">the two usages described in sections 4.1.=
1 (Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">(Multiple Hops), in which case the parent=
hesized terms (or similar</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">terminology) should be used with cross-re=
ferences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">sections.</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, sure will make =
necessary changes, also in the context of earlier comment.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[10] There needs to be a coherent discuss=
ion in one place about how</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">SLA advertisement, update and withdrawal =
work.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">method may suffice on the wire, but the d=
etails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">advertisement, subsequent advertisement (=
update) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">need to be specified in one place.&nbsp; =
The third paragraph of Section 4</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">is a start on this material, but it's too=
 terse;&nbsp;</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">[Med] That text is terse because we are reus=
ing the BGP machinery for advertising/withdrawing; we only augment it with =
triggers that are linked to the SLA information.
 A new SLA will lead to an update message with ADVERTISE, an update of an e=
xisting SLA will trigger an update message. We do think this information is=
 already present in the document.
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;This is hard t=
o understand it, as there is no statement that the BGP machinery is being u=
sed, and the material on SLA usage is spread in different places.&nbsp;
 I suggest starting section 3 with a discussion of advertisement/update/wit=
hdrawal, and how all three are realized via a single ADVERTISE method via B=
GP UPDATE - this was difficult to figure out in reading the current draft.<=
/span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">&nbsp;</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">it should be expanded</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">into its own subsection, and moved earlie=
r to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">ADVERTISE method in Section 3.2.&nbsp; Th=
is text from Section 3.2 should be</span><span style=3D"font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">moved into that new subsection and likewi=
se expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] Another option is to move it Section 4. From our stand=
point, we do think it is straightforward to describe the behavior once the =
attributes format are defined.&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Ok, that=92s =
an editorial choice - I prefer to explain how something works before defini=
ng its on-the-wire data format.</span><span style=3D"font-size:11.0pt; font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span><=
/p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; If an advertised SLA ID is different from earlier advertised</span><s=
pan style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">one,</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the sa=
me prefix and from the same Source AS, indicates</span><span style=3D"font-=
size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:=
#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Source</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is adve=
rtising new SLA Content to replace the previous one</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised=
 with the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">In addition, I wonder whether functionali=
ty should be added to allow</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">withdrawal of an advertisement by specify=
ing its SLA ID, although that</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">was not part of the original design.</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; co=
lor:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt; orphans:2; widows:2"=
><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;; colo=
r:black">[Med] The reason we didn=92t adopted that design is that we don=92=
t want to make assumptions on which data the remote
 peer will be used for enforcing local actions and also because of this tex=
t:</span><span style=3D"color:#212121"></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2; widows:2"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Courier New&quot;; color:#212121">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; The SLA ID applies to aggregate traffic to prefixes for=
 a given</span><span style=3D"color:#212121"></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2; widows:2"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Courier New&quot;; color:#212121">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; AFI/SAFI that share the same Source AS and SLA ID.</spa=
n><span style=3D"color:#212121"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; That=92s fine=
, I wanted to ensure that this had been considered.&nbsp; The discussion of=
 BGP mechanism reuse will probably help here.</span><span style=3D"font-siz=
e:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:bla=
ck"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[11] Notions of context for interpretatio=
n of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">in 3.3.1 need to be added, e.g.:</span><s=
pan style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:=
black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The first three parameters (DSCP, MPLS EXP field in top label,</span><s=
pan style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">802.1q priority) can</span><span style=3D=
"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-=
link or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:1=
0.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497=
D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">network path.</span><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The IP address parameters are rather likely to be VPN-specific when</sp=
an><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">there's more</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN tha=
t spans or transits the ASs involved.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The transport port parameters need specification of which transport</sp=
an><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">header and where it</span><span style=3D"=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP=
 traffic carried by in VXLAN, is this the</span><span style=3D"font-size:10=
.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D=
">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">inner TCP header</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header i=
n VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">There are probably simple approaches to s=
pecifying context in all</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">cases, but that context does need to be s=
pecified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] We dind=92t include a context field because we thought=
 that the definition of the IPFIX attributes is sufficient by itself, but i=
f you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;&nbsp; Really?=
??&nbsp; Please reread the first comment above:</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; - The first three parameters (DSCP, MPLS EXP field in top=
 label, 802.1q priority) can</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-=
link or LSP-by-LSP basis along a traffic's network path.</span><span style=
=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;&nbsp; Taking =
just DSCP, it can change on a per-link basis, so something has to specify w=
hich link (between the SLA Producer and SLA Consumer?) is involved.&nbsp;
 It probably suffices to say that it=92s the link that crosses the relevant=
 AS boundary, but that does have to be stated, as it=92s nowhere to be foun=
d in the far more general IPFIX registry.</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[12] The security considerations (section=
 10) are severely incomplete</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">and insufficient:</span><span style=3D"fo=
nt-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; col=
or:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; I stand by th=
is statement and recommend a complete rewrite of the security consideration=
s.</span><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - Discussion of possible abuse of this BGP option for</span><span style=
=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">denial-of-service and theft-of-service,</=
span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
 color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includ=
ing possible countermeasures and</span><span style=3D"font-size:10.0pt; fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">mitigations.</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] This attack vector is not specific to this attribute; =
this is valid for BGP in general.</span><span style=3D"font-size:10.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span=
></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; There are add=
itional attacks enabled by this attribute.</span><span style=3D"font-size:1=
1.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497=
D"></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - This sentence at the end of the second paragraph in Section 10 is</span=
><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">content-free:</span><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is N=
OT RECOMMENDED to enable this attribute at the</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale o=
f the Internet unless if means to prevent leaking</span><span style=3D"font=
-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color=
:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">sensitive</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informa=
tion are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implem=
enter or admin supposed to do?&nbsp;</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">[Med] An example of what an admin needs to c=
heck if this information can be sent to a given peer or not. Some of the co=
ntent of the attribute contains some sensitive
 information such as contract Id, classes, etc.</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt; text-indent:30.75pt"><s=
pan style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black">How does</span><span style=3D"font-size:10.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">one</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imp=
lementation or deployment is&nbsp; &quot;at the</span><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">scale</span><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??<=
/span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;=
; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:black">[Med] The idea here is to avoid leaking such=
 data in to the global routing table. Only entitled peers need receive such=
 information with controlled scope.</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
ourier New&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; I understand =
the idea - the problem is that I don=92t see specification of what has to b=
e implemented in either the text in the draft or the above explanations.</s=
pan><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;; c=
olor:black"><br>
<br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:black"></span></p>
</div>
<div style=3D"color: rgb(0, 0, 0);">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp; - The next to last paragraph in section 10 is almost cont=
ent-free, as</span><span style=3D"font-size:10.0pt; font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">it leaves</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementati=
on and deployment of key security</span><span style=3D"font-size:10.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">functionality as</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the=
 reader&quot; - that's not acceptable.</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
<br>
</span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt; font-family:&quot;Courier New&quot;; color:black">[Med] I gues=
s you are referring to the following text. Validation checks are really dep=
loyment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"color:#212121"></span></p>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; The attribute may be advertised by a misbehaving node to communicate</sp=
an></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA parameters that are not aligned with the SLA agreements.&nbsp; Thoug=
h</span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; the enforcement of SLA parameters is outside the scope of this</span></p=
re>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; document, it is RECOMMENDED that the SLA Consumer to enforce a set of</s=
pan></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; validation checks before translating the SLA parameters conveyed in</spa=
n></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; the QoS attributes into provisioning actions.&nbsp; Such validations MAY=
</span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; rely on SLA parameters like the origin AS or SLA ID, like generating</sp=
an></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA ID using pseudo-random schemes [<a href=3D"https://tools.ietf.org/ht=
ml/rfc4086" target=3D"_blank" title=3D"&quot;Randomness Requirements for Se=
curity&quot;">RFC4086</a>].</span></pre>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; I stand by th=
e =93exercise to the reader=94 &nbsp;criticism - one way to be honest about=
 this would be to change the paragraph to:</span></p>
<pre><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;</span></pre>
<pre><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; </span><span style=3D"color:#212121">The attribute may be advertised by a=
 misbehaving node to communicate</span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA parameters that are not aligned with the SLA agreements.&nbsp; The</=
span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.</span></pre>
<pre><span style=3D"color:#212121">&nbsp;</span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
 color:#1F497D">David&gt; That does not change any normative content of the=
 original paragraph.&nbsp; My view is that the =93outside the scope of this=
 document=94 statement is wrong because all of these parameters are being d=
efined in this draft.</span><span style=3D"font-size:11.0pt; font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span></pre>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - Last, but not least, the final paragraph in Section 10 is a joke</span>=
<span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">that will</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security dir=
ectorate reviewer - to understand why, see</span><span style=3D"font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, an=
d take note of the publication date of RFC</span><span style=3D"font-size:1=
0.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497=
D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">6919.</span><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D"><br>
David&gt; For anyone who didn=92t catch the reference, RFC 6919 is an April=
 1 RFC ... and the =93SHOULD BE considered=94 language used in the last sec=
urity considerations paragraph of this draft is accurately characterized as=
 vague in Section 2 of RFC 6919:</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; The phrase &qu=
ot;SHOULD CONSIDER&quot; indicates that the authors of the</span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; specification =
think that implementations should do something, but</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt; font-family:&quot;Courier New&quot;">&nbsp;&nbsp; they're not s=
ure quite what.</span><span style=3D"font-size:11.0pt; font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack">------------------------</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Having noted a dozen major issues, I'll e=
nd the review here for now,</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">as I believe a serious revision of the dr=
aft is called for, which</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">would be a better starting point to revie=
w for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">editorial items.</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">-----------------------------------------=
---------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">David L. Black, Distinguished Engineer</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; =
color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Dell EMC, 176 South St., Hopkinton, MA&nb=
sp; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&n=
bsp; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black"><a href=3D"mailto:David.Black@dell.com">D=
avid.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><b=
r>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">-----------------------------------------=
---------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;; color:black"><br>
<br>
<br>
</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DM3PR13MB0604865EC77A246609544830E5520DM3PR13MB0604namp_--


From nobody Fri Feb 24 10:07:21 2017
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1DCC129464 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:07:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umn.edu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4k-2i-1Bp-Gr for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:07:18 -0800 (PST)
Received: from mta-p5.oit.umn.edu (mta-p5.oit.umn.edu [134.84.196.205]) (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 2F2BB129465 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:07:18 -0800 (PST)
Received: from localhost (unknown [127.0.0.1]) by mta-p5.oit.umn.edu (Postfix) with ESMTP id B00F15D6 for <ietf@ietf.org>; Fri, 24 Feb 2017 18:07:17 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p5.oit.umn.edu ([127.0.0.1]) by localhost (mta-p5.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlzY58LFXiGA for <ietf@ietf.org>; Fri, 24 Feb 2017 12:07:17 -0600 (CST)
Received: from mail-vk0-f72.google.com (mail-vk0-f72.google.com [209.85.213.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p5.oit.umn.edu (Postfix) with ESMTPS id 7D08C78 for <ietf@ietf.org>; Fri, 24 Feb 2017 12:07:16 -0600 (CST)
Received: by mail-vk0-f72.google.com with SMTP id t8so15244725vke.3 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:07:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uPLlADp5127QJWxSEZbQcErxgJ4LwyzreagxLfD1Lcc=; b=Eh5A835IcbRBY2+/LqU/y0YZ3EYWNbW3gwJd/CAmuMaFvujMZVYUwyI+MiBujxByKM YU09KLxJgJC2Oxt9wqajRJvDATUzyoSKwJvytre/D9HT8YhBgZrKU8P+WkVNDuHOcZOc F9LdjXEE/YK1pSqgBIo7kym6XwLOmN7PxuZdQKaIxfZVsE35L5KAZ8Hn9majG0NB/Cbp ZRK5w4jEav15Wgt17kWkkQ+nc2M7+bE03Rfr11voJGDGx/CBg6x00PwuqPUNOVuaLMBV qCOTZTDe2Z+LQwHWvBu/nR0ZxTZ9hsvnjHj0c9tMXF5V1VWrG+r8uOkMW4ND2SDQ5MKY vmMQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uPLlADp5127QJWxSEZbQcErxgJ4LwyzreagxLfD1Lcc=; b=f5tAlxsgmD3HOqSGQkWdrRqZGqBZEIRxdDAL2sybLAGFkLFrvezM/2RSaXV6/OQDsR y8lUWo6bSoxJIQ5tW/Ow2TEOobh36HVH0yAYjrh+4NN/o3t4oY4owDoQ+PH2f0GFvrJh Y5UZ43tj7kJACAroqzJT0H2/2MhNqrfM8Y3gVcQ2Js8dQqAqAGOufhMH0Gng4ePbtqvQ ZexoZyTJPVLb3+JvdpO2uTcFxTLry2z2iGC1YaeP96lTFhQA2nTl4bMXDyDxsmSvOlV7 0FzCWV2WG+PzYE8owLm0J0nEt1aVr82sZGcRZc1K1wO8Q3RShDM3auSIKbS6TLpozR1k UhNQ==
X-Gm-Message-State: AMke39kHV50yLikJ3MlAjp00TqEzu6N8W4YrZVdZJvZ6J8GZT2pkvvRUhXAJAtqk18S8LO2C9TUVPvj4dQsZr+0zonLzPL2CQarJ/1pF3QAB68cWCspx2+/Ugc54E9uy5NgmfjLIVdoSGTXzBj4=
X-Received: by 10.176.5.200 with SMTP id e66mr1879251uae.108.1487959635756; Fri, 24 Feb 2017 10:07:15 -0800 (PST)
X-Received: by 10.176.5.200 with SMTP id e66mr1879239uae.108.1487959635568; Fri, 24 Feb 2017 10:07:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.103.89.71 with HTTP; Fri, 24 Feb 2017 10:07:14 -0800 (PST)
In-Reply-To: <02da01d28e92$36a4b8e0$4001a8c0@gateway.2wire.net>
References: <20170221001940.GB84656@Vurt.local> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <02da01d28e92$36a4b8e0$4001a8c0@gateway.2wire.net>
From: David Farmer <farmer@umn.edu>
Date: Fri, 24 Feb 2017 12:07:14 -0600
Message-ID: <CAN-Dau0G3y4jesGKZiOimAFRwS=zLyLf0gh35a6U0LYs2oV6pg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: "tom p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=94eb2c1239a084e19a05494a99b7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ua20SwwFZPY4jRsz7iCgnisuXlA>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:07:20 -0000

--94eb2c1239a084e19a05494a99b7
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 24, 2017 at 4:51 AM, tom p. <daedulus@btconnect.com> wrote:

> ----- Original Message -----
> From: "David Farmer" <farmer@umn.edu>
> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    and including 128 [BCP198].  However, subnet prefixes of 64 bits in
> >    length are REQUIRED for use with Stateless Address
> Autoconfiguration
> >    (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
> >    use. The rationale for the 64 bit boundary in IPv6 addresses can be
> >    found in [RFC7421].
>
> David
>
> Note that 4291bis does not use the language of RFC2119 and does not even
> include a reference to it.
>
> This reflects the consensus of the WG; to introduce such language now
> would, IMHO, open up another can of worms.  It would beg the question as
> to why this one paragraph, or set of paragraphs, use this language when
> all the others do not.  That is, it will cause us to discuss all the
> other places where such language might have been used but was not; 10,
> 20 50 ...   Well, at a quick glance, I reckon there are about 60 such
> places, 60 more discussions?
>
> Tom Petch
>

Yep, I'm aware.  I would nuance the WG's consensus a little, I think it was
most people thought there were bigger fish to fry than to make all those
changes, but basically it boils down to the same thing.  I'm not trying to
relitigate it either, it's just the style I prefer to use. If the text I'm
proposing makes it into the document, I fully expect and support the
document's editor munging the text into the document's style.

Thanks.

-- 
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: 612-626-0815 <(612)%20626-0815>
Minneapolis, MN 55414-3029   Cell: 612-812-9952 <(612)%20812-9952>
===============================================

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 4:51 AM, tom p. <span dir=3D"ltr">&lt;<a href=
=3D"mailto:daedulus@btconnect.com" target=3D"_blank">daedulus@btconnect.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">----- Original Mes=
sage -----<br>
From: &quot;David Farmer&quot; &lt;<a href=3D"mailto:farmer@umn.edu" target=
=3D"_blank">farmer@umn.edu</a>&gt;<br>
&gt;=C2=A0 =C2=A0 IPv6 unicast routing is based on prefixes of any valid le=
ngth up to<br>
&gt;=C2=A0 =C2=A0 and including 128 [BCP198].=C2=A0 However, subnet prefixe=
s of 64 bits in<br>
&gt;=C2=A0 =C2=A0 length are REQUIRED for use with Stateless Address<br>
Autoconfiguration<br>
&gt;=C2=A0 =C2=A0 (SLAAC)[RFC4862] and are RECOMMENDED for all other genera=
l purpose<br>
&gt;=C2=A0 =C2=A0 use. The rationale for the 64 bit boundary in IPv6 addres=
ses can be<br>
&gt;=C2=A0 =C2=A0 found in [RFC7421].<br>
<br>
David<br>
<br>
Note that 4291bis does not use the language of RFC2119 and does not even<br=
>
include a reference to it.<br>
<br>
This reflects the consensus of the WG; to introduce such language now<br>
would, IMHO, open up another can of worms.=C2=A0 It would beg the question =
as<br>
to why this one paragraph, or set of paragraphs, use this language when<br>
all the others do not.=C2=A0 That is, it will cause us to discuss all the<b=
r>
other places where such language might have been used but was not; 10,<br>
20 50 ...=C2=A0 =C2=A0Well, at a quick glance, I reckon there are about 60 =
such<br>
places, 60 more discussions?<br>
<br>
Tom Petch<br></blockquote></div><div class=3D"gmail_extra"><br></div>Yep, I=
&#39;m aware.=C2=A0 I would nuance the WG&#39;s consensus a little, I think=
 it was most people thought there were bigger fish to fry than to make all =
those changes, but basically it boils down to the same thing.=C2=A0 I&#39;m=
 not trying to relitigate it either, it&#39;s just the style I prefer to us=
e. If the text I&#39;m proposing makes it into the document, I fully expect=
 and support the document&#39;s editor munging the text into the document&#=
39;s style.=C2=A0</div><div class=3D"gmail_extra"><br></div><div class=3D"g=
mail_extra">Thanks.</div><div class=3D"gmail_extra"><div><br></div>-- <br><=
div class=3D"m_-2841231725150918009gmail_signature" data-smartmail=3D"gmail=
_signature">=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D<br>David Farmer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 <a href=3D"mailto:Email%3Afarmer@umn.edu" target=3D"_blank">Email:fa=
rmer@umn.edu</a><br>Networking &amp; Telecommunication Services<br>Office o=
f Information Technology<br>University of Minnesota=C2=A0=C2=A0 <br>2218 Un=
iversity Ave SE=C2=A0 =C2=A0 =C2=A0 =C2=A0 Phone: <a href=3D"tel:(612)%2062=
6-0815" value=3D"+16126260815" target=3D"_blank">612-626-0815</a><br>Minnea=
polis, MN 55414-3029=C2=A0=C2=A0 Cell: <a href=3D"tel:(612)%20812-9952" val=
ue=3D"+16128129952" target=3D"_blank">612-812-9952</a><br>=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<wbr>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D </div>
</div></div>

--94eb2c1239a084e19a05494a99b7--


From nobody Fri Feb 24 10:08:54 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D0D129453 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:08:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level: 
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 dyr_ucTzp3Q5 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:08: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 B1F47129440 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:08:50 -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 v1OI8mpV018508; Fri, 24 Feb 2017 19:08:48 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0C4B920BA47; Fri, 24 Feb 2017 19:08:48 +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 F025E20BA6C; Fri, 24 Feb 2017 19:08:47 +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 v1OI8lTS013905; Fri, 24 Feb 2017 19:08:47 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com> <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com> <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <e9edd389-9b84-21b0-644b-10cfc7ea7d4e@gmail.com>
Date: Fri, 24 Feb 2017 19:08:38 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a9BKOz20zfCTKOW3cDCsXx9KY74>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:08:53 -0000

Le 24/02/2017 à 18:53, Christopher Morrow a écrit :
>
>
> On Fri, Feb 24, 2017 at 12:09 PM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>
>
>
>     Le 24/02/2017 à 17:27, Christopher Morrow a écrit :
>
>
>
>         On Fri, Feb 24, 2017 at 10:48 AM, Alexandre Petrescu
>         <alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>
>         <mailto:alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>>>
>         wrote:
>
>
>
>         Le 24/02/2017 à 15:59, Christopher Morrow a écrit :
>
>
>
>         On Fri, Feb 24, 2017 at 9:09 AM, Alexandre Petrescu
>         <alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>
>         <mailto:alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>>
>         <mailto:alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>
>         <mailto:alexandre.petrescu@gmail.com
>         <mailto:alexandre.petrescu@gmail.com>>>> wrote:
>
>
>         A question to Windows is the following: what prefixlen does it set
>         when the end user manually assigns an address on an interface
>         without specifiying a prefixlen?
>
>
>         I don't think this matters... 'end users' will in almost all cases
>         just attach and get connectivity.
>
>
>         Let me go next in cycle: what does linux do when one ifconfig add an
>         IPv6 address without telling the plen?  Is it adding an entry in the
>         rt table?  Which plen?  Is that plen normal?
>
>
>         still don't think this matters. If a user messes up what they type,
>         they messed up. if the instructions aren't complete, they aren't
>         complete and there will be mistakes. An interface configuration
>         requires all proper parameters be set, or problems will arise.
>         Assumptions about current and future behavior are proven wrong time
>         and again.
>
>         non-deterministic behavior over time is the hallmark of this
>         space... please do not rely on defaults for hand-managed/bespoke
>         configurations if you expect things to work reliably and repeatably.
>
>
>     That means the following: Windows please make the plen parameter
>     mandatory.  Dont leave it optional only to subversively set it to 64.
>     That's a software bug because nobody asks you to set the plen to 64 when
>     the end user does not specify one.
>
>     I guess the same bug is is in BSD, linux and what have you.
>
>
> yes, I think so.. for linux:
> $ sudo ip -6 addr add 2001:700:4::1 dev em1
>
> gets me:
>  inet6 2001:700:4::1/128 scope global

That address is good, but how about the routing table?  Does it get an 
entry like 2001:700:4::/64?

> so that actually seems correct.
>
>
>
>         If they are in a place where someone says: "Hey, you should go
>         if/ipconfig ...." then .. they are 'consenting adults' and can do
>         whatever they please.
>
>
>         I assume you assume that ip/ifconfig by consenting adults means the
>         adults type a plen in the CLI, right?
>
>
>         sure, or a script/program/etc does this, it's not important how the
>         'ifconfig' happens, it's important that when it happens the right
>         parameters are passed to the 'ifconfig' command.
>
>
>     I agree.  If 'ifconfig' silently assumes 64 then that assumption is
>     wrong.  The ifconfig programmer should take that as a software bug.
>     It's not an RFC that requires them to put 64 there.
>
>
> ok
>
>
>         That makes it mandatory that the CLI _requires_ a plen, right?  That
>         CLI should not allow silence for a plen parameter.
>
>
>         sure, or you are at the mercy of the implementor of that command:
>         Today I like /64! It's tomorrow and now I like /62!!
>
>         don't rely on defaults.
>
>
>     I agree.
>
>         Because silent plen means 64.  And I dont think it's right to assume
>         a by-default 64 plen.  Because many people think 64 is right and
>         others think it's wrong, there does not seem to be a commonly agreed
>         'by default' value for plen.
>
>
>         correct, so.. be specific in your configuration effort please...
>         which again, means that the 'what is the default?" conversation is
>         moot.
>
>
>     I am not asking what is the default.
>
>     I am saying that apparently numerous implementations out there consider
>     the default to be 64.  This consideration is wrong.
>
>
> yes, I agree with you here.
>
>
>     A 'default' value is something that everybody agrees with.  For example,
>     one can leave out '::' from a command line adding a default route and
>     just say 'default'.  There is an agreed standard that says that
>     'default' is '::'.
>
>     But there is by far no single standard that says the default prefix
>     length is 64.
>
>     That's why it's a bug.
>
>     It's like boxes with pre-defined passwords admin/admin.  The local
>     programmer imagined it a good 'default' but never asked around the
>     validity of such assumption.  And that creates problems.
>
>
> ok, cool, i think we agree on all of this at least :)

:-)

Alex

>
>
>
>
>     Alex
>
>
>
>
>         Alex
>
>
>
>         again the proposed text (now 175+ messages back) really covers this
>         already..
>
>
>


From nobody Fri Feb 24 10:21:22 2017
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F19BE129481 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:21:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m1Usi4UfDjUr for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:21:18 -0800 (PST)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::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 9FB2712947F for <ietf@ietf.org>; Fri, 24 Feb 2017 10:21:18 -0800 (PST)
Received: by mail-qt0-x229.google.com with SMTP id x35so23329266qtc.2 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:21:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=2yT5M/ALRD+D4tNfSC4AiTAPhnpitQ7iloZD6EtJgok=; b=ROnWnV4mIBs3NG6ch8H8CkOj5/UOfZlS60Azn5TxW4ktcVAi6X+h7v6kXOSAiYwuj/ TTRNn5YU2ztuqsCHUPwgLTc/+bhdYV4wt8HI8/I/iRlHcR+qUhT4fLM4HHFvzO2qhxTx DED6WpWFFkp+NdfWLbFbSOVa7wnSS00ndeagZddSLEBUvOKqnxxl1lurhm/OFdWDsXBL gd8/PWDCA4MbLlK8TRplfLRBkbwcc7Sz0+DM5+6RyhhR69F5JNe5nkQVpMDYnjEkM9Sh +vZ7jmnvy1ZK8+F/dHL91m07kZgknZRMWij84yYcQRgPbloW82aAvohADk/7JbxqpRn/ mIlw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=2yT5M/ALRD+D4tNfSC4AiTAPhnpitQ7iloZD6EtJgok=; b=S8REkc+2rCTIXG4C0dAkDcXJ0HCzpgGPWwXJMG2rb9uCejo8am3bgr4t+xO8jmaDX/ eKuwEJGggX9hHh8/nhYXavCUJ2iQAkBtOW6sHy9WWco1eK/1ShEt+oxvmwvSmZcAECy2 ZwzUyefoYxc/RryXtiYLQL0YF5AGDnauNAy2FGD8E0xVJmt9CZ4q8L2AlJs0D3w1jgkr H/2vp0j7r+nD2k0yvyb/ImwcU04sWETfBTv4L1cFsqezYqBrvfsFK0x0C9/JEMZcsC42 U2+IYraPkmojpjRf1tEkJzy7b5ahBJi4MMx4vaRve6Adj7hREM21INX6TbCq8wJorEcI XBJA==
X-Gm-Message-State: AMke39l4V6ujFemIo5j739HG+lUJKwEDBCNR+5Siwr5VORFQS56DE9yVmsDKqdxjgWbEOo9NQxOwjqfELupVlQ==
X-Received: by 10.200.51.19 with SMTP id t19mr4059171qta.242.1487960477678; Fri, 24 Feb 2017 10:21:17 -0800 (PST)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.91.71 with HTTP; Fri, 24 Feb 2017 10:21:17 -0800 (PST)
In-Reply-To: <e9edd389-9b84-21b0-644b-10cfc7ea7d4e@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com> <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com> <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com> <e9edd389-9b84-21b0-644b-10cfc7ea7d4e@gmail.com>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Fri, 24 Feb 2017 13:21:17 -0500
X-Google-Sender-Auth: 1OSXzUZb-8sFAVSdSJi4jdiluck
Message-ID: <CAL9jLaatbLHVrjwBh345G6F1jv+R+RtgOSvQdAACcRXRZnU1zQ@mail.gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Content-Type: multipart/alternative; boundary=001a11403ccab665c805494acbca
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n48194dlZ-Ot3b0msvZGFZH6Wvg>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:21:20 -0000

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

On Fri, Feb 24, 2017 at 1:08 PM, Alexandre Petrescu <
alexandre.petrescu@gmail.com> wrote:

>
>
> Le 24/02/2017 =C3=A0 18:53, Christopher Morrow a =C3=A9crit :
>
>>
>> yes, I think so.. for linux:
>> $ sudo ip -6 addr add 2001:700:4::1 dev em1
>>
>> gets me:
>>  inet6 2001:700:4::1/128 scope global
>>
>
> That address is good, but how about the routing table?  Does it get an
> entry like 2001:700:4::/64?
>
>
$ ifconfig em1
<snip>
          inet6 addr: 2001:700:4::1/128 Scope:Global
<snip>

and:
$ netstat -rnA inet6
Kernel IPv6 routing table
Destination                    Next Hop                   Flag Met Ref Use
If
2001:700:4::1/128              ::                         U    256 0     0
em1
<snip>
2001:700:4::1/128              ::                         Un   0   1     0
lo

that sure seems like i only got what I paid for.. on:
$ uname -r
3.13.0-92-generic

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, Feb 24, 2017 at 1:08 PM, Alexandre Petrescu <span dir=3D"ltr">&=
lt;<a href=3D"mailto:alexandre.petrescu@gmail.com" target=3D"_blank">alexan=
dre.petrescu@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><span class=3D"gmail-"><br>
<br>
Le 24/02/2017 =C3=A0 18:53, Christopher Morrow a =C3=A9crit :<br>
</span><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class=3D=
"gmail-h5"><br>
yes, I think so.. for linux:<br>
$ sudo ip -6 addr add 2001:700:4::1 dev em1<br>
<br>
gets me:<br>
=C2=A0inet6 2001:700:4::1/128 scope global<br>
</div></div></blockquote>
<br>
That address is good, but how about the routing table?=C2=A0 Does it get an=
 entry like 2001:700:4::/64?<div><div class=3D"gmail-h5"><br></div></div></=
blockquote><div><br></div><div><div>$ ifconfig em1</div></div><div>&lt;snip=
&gt;</div><div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 inet6 addr: 2001:700=
:4::1/128 Scope:Global</div></div><div>&lt;snip&gt;</div><div><br></div><di=
v>and:<br><div>$ netstat -rnA inet6</div></div><div><div>Kernel IPv6 routin=
g table</div><div>Destination =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0Next Hop =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Flag Met Ref Use If</div><div>2001:700:4::1/128 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 U =C2=A0 =C2=A0256 =
0 =C2=A0 =C2=A0 0 em1</div></div><div>&lt;snip&gt;</div><div><div>2001:700:=
4::1/128 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:: =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Un =
=C2=A0 0 =C2=A0 1 =C2=A0 =C2=A0 0 lo</div></div><div><br></div><div>that su=
re seems like i only got what I paid for.. on:<br><div>$ uname -r</div><div=
>3.13.0-92-generic</div></div><div><br></div><div>=C2=A0</div></div></div><=
/div>

--001a11403ccab665c805494acbca--


From nobody Fri Feb 24 10:28:32 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CC212947A; Fri, 24 Feb 2017 10:28: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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 oFD2SBF_TiYB; Fri, 24 Feb 2017 10:28:24 -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 34F1C129479; Fri, 24 Feb 2017 10:28:24 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 AAC0180F49; Fri, 24 Feb 2017 19:28:15 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: Nick Hilliard <nick@foobar.org>, Mikael Abrahamsson <swmike@swm.pp.se>
References: <20170221001940.GB84656@Vurt.local> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com> <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr> <alpine.DEB.2.02.1702241423100.15705@uplift.swm.pp.se> <58B04D15.7030506@foobar.org>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <e05cb1e1-f8c7-6695-a446-2b302cff1010@si6networks.com>
Date: Fri, 24 Feb 2017 15:26:51 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <58B04D15.7030506@foobar.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LeIK0IsNlCTaulTIbiDqIrtQV2k>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:28:26 -0000

On 02/24/2017 12:11 PM, Nick Hilliard wrote:
[....]
>>
>> I just want the -bis document to reflect what is currently in the field
>> and we know works. Nothing more, nothing less.
> 
> I wholly agree with this as it applies to draft-ietf-6man-rfc4291bis.
> 
> As a general comment, it should be reiterated that operational feedback
> is critical to standards development and that if field deployment issues
> are neglected, this damages the standards development process.  It would
> be unfortunate if this document fell prey to this folly.

+1


-- 
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 24 10:36:26 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29D9C12947A for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.333
X-Spam-Level: 
X-Spam-Status: No, score=-5.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=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 Dclepkv7JsC2 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 10:36:23 -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 47014129489 for <ietf@ietf.org>; Fri, 24 Feb 2017 10:36:23 -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 v1OIaL5i003466; Fri, 24 Feb 2017 19:36:21 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 0B36620B9D1; Fri, 24 Feb 2017 19:36:21 +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 F21E220B817; Fri, 24 Feb 2017 19:36:20 +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 v1OIaKQa027063; Fri, 24 Feb 2017 19:36:20 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com> <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com> <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com> <e9edd389-9b84-21b0-644b-10cfc7ea7d4e@gmail.com> <CAL9jLaatbLHVrjwBh345G6F1jv+R+RtgOSvQdAACcRXRZnU1zQ@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b7b7f6b0-4c53-3baf-320b-0f7e443040f0@gmail.com>
Date: Fri, 24 Feb 2017 19:36:11 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <CAL9jLaatbLHVrjwBh345G6F1jv+R+RtgOSvQdAACcRXRZnU1zQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N3pMAhXM-ZQbA_XAlVQAXuA53zI>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 18:36:25 -0000

Le 24/02/2017 à 19:21, Christopher Morrow a écrit :
>
>
> On Fri, Feb 24, 2017 at 1:08 PM, Alexandre Petrescu
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>
>
>
>     Le 24/02/2017 à 18:53, Christopher Morrow a écrit :
>
>
>         yes, I think so.. for linux:
>         $ sudo ip -6 addr add 2001:700:4::1 dev em1
>
>         gets me:
>          inet6 2001:700:4::1/128 scope global
>
>
>     That address is good, but how about the routing table?  Does it get
>     an entry like 2001:700:4::/64?
>
>
> $ ifconfig em1
> <snip>
>           inet6 addr: 2001:700:4::1/128 Scope:Global
> <snip>
>
> and:
> $ netstat -rnA inet6
> Kernel IPv6 routing table
> Destination                    Next Hop                   Flag Met Ref
> Use If
> 2001:700:4::1/128              ::                         U    256 0
> 0 em1
> <snip>
> 2001:700:4::1/128              ::                         Un   0   1
> 0 lo
>
> that sure seems like i only got what I paid for.. on:
> $ uname -r
> 3.13.0-92-generic

Looks good in linux world.

Alex

>
>


From nobody Fri Feb 24 11:26:39 2017
Return-Path: <alexandre.petrescu@cea.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6927F1294DC for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 11:26:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level: 
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 iYBPCLojIBM2 for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 11:26:35 -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 1CD251294DA for <ietf@ietf.org>; Fri, 24 Feb 2017 11:26:34 -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 v1OJQVq4003415; Fri, 24 Feb 2017 20:26:31 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 97B9F20BAF8; Fri, 24 Feb 2017 20:26:31 +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 889D120B9E7; Fri, 24 Feb 2017 20:26:31 +0100 (CET)
Received: from [132.166.84.80] ([132.166.84.80]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v1OJQUIG017800; Fri, 24 Feb 2017 20:26:30 +0100
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
To: Christopher Morrow <morrowc.lists@gmail.com>
References: <58AF313D.3020905@foobar.org> <CAO42Z2ymnLm9dUNL3doU9+vR0eMzGbr71HQybbibXq9rCObP3A@mail.gmail.com> <21A9AEAE-330D-47F3-88CA-FC845C71AED0@darou.fr> <CAKD1Yr2Q-AUEWQSXFPzjn73Q7dJhMpB2_iHb3wJTCGx4-==Bpg@mail.gmail.com> <DADB35F5-3CB6-4396-A99F-ECE13C3EFE44@darou.fr> <e89b23b0-b037-995e-fd66-335505ecee61@gmail.com> <CAL9jLaY6RzX6pGFFMcReADudt+ewVtNw_XUYp07_BAVKAp8+hQ@mail.gmail.com> <bd05771e-1b03-1ee7-2a4c-0a1fe69b8a14@gmail.com> <CAL9jLaZJR9YzkF-R9Gx6MWBoJG4cSvp0rovYQ_9BALLzbQGiPQ@mail.gmail.com> <c3e04aa1-40e1-551f-3821-b62732106e3d@gmail.com> <CAL9jLaZhAp3VWHBJh08XnFoFAHZ_69tQJyUVAXE_YP9ELaDhbA@mail.gmail.com> <e9edd389-9b84-21b0-644b-10cfc7ea7d4e@gmail.com> <CAL9jLaatbLHVrjwBh345G6F1jv+R+RtgOSvQdAACcRXRZnU1zQ@mail.gmail.com> <b7b7f6b0-4c53-3baf-320b-0f7e443040f0@gmail.com>
From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
Organization: CEA
Message-ID: <81bc136f-b209-2a62-850b-a6b6f4745887@cea.fr>
Date: Fri, 24 Feb 2017 20:26:20 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <b7b7f6b0-4c53-3baf-320b-0f7e443040f0@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms060404050807090606000906"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZGAn1ZFYorwO-sbKUdS5imsjGNk>
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 19:26:37 -0000

This is a cryptographically signed message in MIME format.

--------------ms060404050807090606000906
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable


--
Alexandre Petrescu
alexandre.petrescu@cea.fr, t=C3=A9l 0169089223

Le 24/02/2017 =C3=A0 19:36, Alexandre Petrescu a =C3=A9crit :
>
>
> Le 24/02/2017 =C3=A0 19:21, Christopher Morrow a =C3=A9crit :
>>
>>
>> On Fri, Feb 24, 2017 at 1:08 PM, Alexandre Petrescu
>> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>>=20
>> wrote:
>>
>>
>>
>>     Le 24/02/2017 =C3=A0 18:53, Christopher Morrow a =C3=A9crit :
>>
>>
>>         yes, I think so.. for linux:
>>         $ sudo ip -6 addr add 2001:700:4::1 dev em1
>>
>>         gets me:
>>          inet6 2001:700:4::1/128 scope global
>>
>>
>>     That address is good, but how about the routing table?  Does it ge=
t
>>     an entry like 2001:700:4::/64?
>>
>>
>> $ ifconfig em1
>> <snip>
>>           inet6 addr: 2001:700:4::1/128 Scope:Global
>> <snip>
>>
>> and:
>> $ netstat -rnA inet6
>> Kernel IPv6 routing table
>> Destination                    Next Hop                   Flag Met Ref=

>> Use If
>> 2001:700:4::1/128              ::                         U 256 0
>> 0 em1
>> <snip>
>> 2001:700:4::1/128              ::                         Un 0   1
>> 0 lo
>>
>> that sure seems like i only got what I paid for.. on:
>> $ uname -r
>> 3.13.0-92-generic
>
> Looks good in linux world.
>
> Alex

But, I would like to add that last time I checked (january 2015) the=20
linux kernel complained in /var/log/messages  when receiving an RA=20
containing a plen 65.  It called it "illegal" prefix length.
That RA was sent over usbnet.  There is no specification of=20
IPv6-over-USB, there is no IID length requirement to be 64, because=20
there is noo USB IEEE MAC address.

That was wrong at that time (call a 65 in RA "illegal"), I dont know=20
whether it still the case.  I may check in some time in the following=20
weeks, and this is the question I will follow: is the linux kernel=20
complaining when receiving an RA with a plen 65 on usbnet?  If yes, then =

linux stilll has at least one problem with this 64.

What is sure is that there is still no IPv6-over-USB draft, so no IID 64 =

on USB.

It's  a similar situation with cellular links instead of USB - no spec,=20
but hidden assumptions about it being 64.  They are all wrong.

Alex

>
>>
>>



--------------ms060404050807090606000906
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: Signature cryptographique S/MIME

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCC
C6QwggWgMIIEiKADAgECAgI5MDANBgkqhkiG9w0BAQUFADBjMQswCQYDVQQGEwJGUjEMMAoG
A1UECgwDQ0VBMRcwFQYDVQQLDA4wMDAyIDc3NTY4NTAxOTELMAkGA1UECwwCQUMxIDAeBgNV
BAMMF0NFQSBBQyBVdGlsaXNhdGV1ciAyMDIxMB4XDTE1MDExNTEzNDI1MFoXDTE4MDExNTEz
NDI1MFowVTELMAkGA1UEBhMCRlIxDDAKBgNVBAoMA2NlYTEUMBIGA1UECwwLVXRpbGlzYXRl
dXIxIjAgBgNVBAMMGVBFVFJFU0NVIEFsZXhhbmRyZSAyMjIwNDAwggEiMA0GCSqGSIb3DQEB
AQUAA4IBDwAwggEKAoIBAQDAmIx5QVYSXlLNLE/D9SySZPKHBBP0G9NgtMYKQuYWODXAkmI8
b4xp1YniPStCcyPauXfVn+ySgAr4SX/oWwB2kTPISYWt8FQ7eNdXH7AM7cPbLQh0IYwHUWAf
6Mzakx+/oajWhYv8NvLhVnb7qjGmWObdLUcOgJOSYAzHSVPQRnRB9A9Fw7NzNMi/9wqGwmJz
maBhaDL/iMRZEDnllsnGFHZr1h6N8srFER7nEJVS/CDTIlZwBFO6DXScy1mq8ZzcD3hNIOV1
2PmhiW7dPfeE7BDjvDS+Fb0PQB7R4TCQo4J7+Nm4Cca+U4cloclzpznWJZWD1AZw8CdwXqNM
/tYXAgMBAAGjggJqMIICZjAdBgNVHQ4EFgQUonHmXxWzWW2Z52J+svVY7gn56jUwHwYDVR0j
BBgwFoAU+4DifDNZ7hKDQxL+ys+vHYZdUJgwgcgGA1UdIASBwDCBvTCBugYKKwYBBAHgYAEG
AjCBqzAlBggrBgEFBQcCARYZaHR0cDovL3d3dy1pZ2MuY2VhLmZyL3BjLzCBgQYIKwYBBQUH
AgIwdTANFgNDRUEwBgIBAgIBABpkVm91cyBkZXZleiBhY2NlcHRlciBsYSBwb2xpdGlxdWUg
ZGUgY2VydGlmaWNhdGlvbiBhdmFudCBkJ3V0aWxpc2VyIGNlIGNlcnRpZmljYXQsIGNmLiB3
d3ctaWdjLmNlYS5mcjARBglghkgBhvhCAQEEBAMCBaAwDgYDVR0PAQH/BAQDAgSwMCQGA1Ud
EQQdMBuBGWFsZXhhbmRyZS5wZXRyZXNjdUBjZWEuZnIwTQYDVR0fBEYwRDBCoECgPoY8aHR0
cDovL2NybC1hYy11dGlsaXNhdGV1ci5jZWEuZnIvY3JsL2FjLXV0aWxpc2F0ZXVyLTIwMjEu
Y3JsMHMGCWCGSAGG+EIBDQRmFmRWb3VzIGRldmV6IGFjY2VwdGVyIGxhIHBvbGl0aXF1ZSBk
ZSBjZXJ0aWZpY2F0aW9uIGF2YW50IGQndXRpbGlzZXIgY2UgY2VydGlmaWNhdCwgY2YuIHd3
dy1pZ2MuY2VhLmZyMEwGCCsGAQUFBwEBBEAwPjA8BggrBgEFBQcwAoYwaHR0cDovL3d3dy1p
Z2MuY2VhLmZyL2FjL2FjLXV0aWxpc2F0ZXVyLTIwMjEuY2VyMA0GCSqGSIb3DQEBBQUAA4IB
AQB+wFDqbtylGRYrv0BVuBjf9ZHHixvEVOz1SMyR+9671bbqPylE3xAEENJ9Obz+wI/hTsrL
R0R+UQuMutmU4N2y84YbdWirtCneyiLrS4aG8OkOl0cKdQubj+ptcXHWl0WWdB9urwYjBaZ4
A9Z+/VqJQBz1B3ci1u5Kz4P1HpfILJnjxaAdEvt6xepyshPCms8jEcEKz4OggYAQFKzJoIZx
QPB2yBRc8aJZW+Vqb/W5i7Ow+2oaUTw2RQ7Iv84AvBMyqSFFU//tsgTED4QmIL3+bWcqrG4q
rkFNeuDnQr5neJ2sR3s2kPSCZYn2d1W6BjQ67flz/V6jBEgkshD0TttRMIIF/DCCA+SgAwIB
AgIBAjANBgkqhkiG9w0BAQUFADBeMQswCQYDVQQGEwJGUjEMMAoGA1UECgwDQ0VBMRcwFQYD
VQQLDA4wMDAyIDc3NTY4NTAxOTELMAkGA1UECwwCQUMxGzAZBgNVBAMMEkNFQSBBQyBSYWNp
bmUgMjA0MTAeFw0xMTExMjgxMzU0MzVaFw0yMTEyMDExMzU0MzVaMGMxCzAJBgNVBAYTAkZS
MQwwCgYDVQQKDANDRUExFzAVBgNVBAsMDjAwMDIgNzc1Njg1MDE5MQswCQYDVQQLDAJBQzEg
MB4GA1UEAwwXQ0VBIEFDIFV0aWxpc2F0ZXVyIDIwMjEwggEiMA0GCSqGSIb3DQEBAQUAA4IB
DwAwggEKAoIBAQCc/G4Oogc3nYQybY/irx22kJi+TuA6EqkXjtNRcPYfRi619L7ikuZNsVfa
fBWp/1KQD6VdW4cBzNYghKyrUkdPRhGQ0xLNQhTyVFn3QuJIjyWEpl9IESc2ctzme6NIF4lG
axXvlwve+UCt9v4Xuk1pUcSAt2AJ9PdTNNinJQBNprOTh6Twq30i4YcTxH99X94AWfiYZRvm
/tFE38oK6fD7y8S6/xW90QuCmMHpTUtmKt8l7t6PAwNTx8uFayGFCCfeMAbLIcaXvKZzuBpA
XpKXr7zvGTu/OsdNKNyzxvF7kon/2kDA4dxXAp/MTDIjaARBFjVVfs+/esdROUsLTqUDAgMB
AAGjggG+MIIBujAPBgNVHRMBAf8EBTADAQH/MB0GA1UdDgQWBBT7gOJ8M1nuEoNDEv7Kz68d
hl1QmDAfBgNVHSMEGDAWgBSgEYn4mr+mhLEpBzdTQe2XlUJ7HTCByAYDVR0gBIHAMIG9MIG6
BgorBgEEAeBgAQYCMIGrMCUGCCsGAQUFBwIBFhlodHRwOi8vd3d3LWlnYy5jZWEuZnIvcGMv
MIGBBggrBgEFBQcCAjB1MA0WA0NFQTAGAgECAgEAGmRWb3VzIGRldmV6IGFjY2VwdGVyIGxh
IHBvbGl0aXF1ZSBkZSBjZXJ0aWZpY2F0aW9uIGF2YW50IGQndXRpbGlzZXIgY2UgY2VydGlm
aWNhdCwgY2YuIHd3dy1pZ2MuY2VhLmZyMA4GA1UdDwEB/wQEAwIBBjBDBgNVHR8EPDA6MDig
NqA0hjJodHRwOi8vY3JsLWFjLXJhY2luZS5jZWEuZnIvY3JsL2FjLXJhY2luZS0yMDQxLmNy
bDBHBggrBgEFBQcBAQQ7MDkwNwYIKwYBBQUHMAKGK2h0dHA6Ly93d3ctaWdjLmNlYS5mci9h
Yy9hYy1yYWNpbmUtMjA0MS5jZXIwDQYJKoZIhvcNAQEFBQADggIBAMCbWqmZRh1h4klw5m6b
t2okNIorESBuwWQ3woAdLb9PsVUW70mLwwzvmf/++lphdYn6cWVHxXNn707DPz6XG/IsRfBA
UWTshe0QmrGx5xpVvpbrU9gQVWGwLugF6rYgZ9B7ELOxQp/Ac03nheADYevePfbZ/2lbIJGt
sn7/8lF5JKENkhvAb2+bXZZsyvy59W8xc2QsDUddemHKz9ZtggGeToG0LDT78SkSPbE3RwP+
Q0VXt7QYo8vhmV43mp+UrZeI4JUQibWXvIOp6avOf1zfpbm9RhLa501puoKaVaeHkcxi46je
Bv4znpwQEi5I9yS6Hekivh9hofq52lIQJ+UNe2+QYGAzJmuI62Buto1iwWmBm8Qe+uIpZnRU
/O/tFgw2Gm2fbDdtT1tbaZdJgbI40D4DpUGBbf1kkbn1G5i0bkDUZfUk18w1aa5d4sSC1tLU
xAZqhKe1iA7iLeweZhqLzmylFCL5BlJrVh+PNXwUYhOOLkiE7/uC/ncog+K5J2HnzZfX2Ejh
haeBCTxeQBvmm/omrzWerid6FLG/jlBjqkpoALNucTRfDB6YmspYqOY8sU8yiLKt/v6xpxb4
AI3FEheIzTz/bgCNNbQv3Be1TpdKI8cc40HG72jK/s7sbbKMf1SRtTxDZGGmarjaWtxWo6S9
uFc2ZX4lyqYbNnh3MYIDZTCCA2ECAQEwaTBjMQswCQYDVQQGEwJGUjEMMAoGA1UECgwDQ0VB
MRcwFQYDVQQLDA4wMDAyIDc3NTY4NTAxOTELMAkGA1UECwwCQUMxIDAeBgNVBAMMF0NFQSBB
QyBVdGlsaXNhdGV1ciAyMDIxAgI5MDANBglghkgBZQMEAgEFAKCCAc0wGAYJKoZIhvcNAQkD
MQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjI0MTkyNjIwWjAvBgkqhkiG9w0B
CQQxIgQgwtG3we71K8isI0j5zV7XhrgM5aAVmx2bxxh5GL4zoQwwbAYJKoZIhvcNAQkPMV8w
XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDB4BgkrBgEEAYI3EAQx
azBpMGMxCzAJBgNVBAYTAkZSMQwwCgYDVQQKDANDRUExFzAVBgNVBAsMDjAwMDIgNzc1Njg1
MDE5MQswCQYDVQQLDAJBQzEgMB4GA1UEAwwXQ0VBIEFDIFV0aWxpc2F0ZXVyIDIwMjECAjkw
MHoGCyqGSIb3DQEJEAILMWugaTBjMQswCQYDVQQGEwJGUjEMMAoGA1UECgwDQ0VBMRcwFQYD
VQQLDA4wMDAyIDc3NTY4NTAxOTELMAkGA1UECwwCQUMxIDAeBgNVBAMMF0NFQSBBQyBVdGls
aXNhdGV1ciAyMDIxAgI5MDANBgkqhkiG9w0BAQEFAASCAQAIENy4OHi+QXGKLEDeEAYSbeu6
zDfHPQHcYFHW+3NtH8glOqX+4i/TITk2m/gfmNVExvUllkFuRjTaSO54Hf40S6boy5zCDhNs
yGw/gWb5xRfrICS05dSRHyOzaTlbMNtwBkEUtWNkCzN9qpzgSUu+pywnis55ABBb7+UWsfvt
wJJBfI1bvDpCGnAIzo84U4oAAiRshP0OWyb/8+HNcKP/ir0s/vfdnRlzkwtKUgAxy0OLsY6s
h88B8IaxZD8VUGopJmAW4N7aVZfah9jG5tw0JX0KXrF9LejaB/XqG8AlElW+VufCkoF0UGTt
dfZmhMhuJm4+uvTPbWO4a3TADbo5AAAAAAAA
--------------ms060404050807090606000906--


From nobody Fri Feb 24 11:56:54 2017
Return-Path: <gert@space.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D2B1294EF for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 11:56:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=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 aAo8b4Zqyy9u for <ietf@ietfa.amsl.com>; Fri, 24 Feb 2017 11:56:50 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A96B1294ED for <ietf@ietf.org>; Fri, 24 Feb 2017 11:56:49 -0800 (PST)
X-Original-To: ietf@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 0B5CA61381 for <ietf@ietf.org>; Fri, 24 Feb 2017 20:56:47 +0100 (CET)
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
X-SpaceNet-Relay: true
Received: from moebius4.space.net (moebius4.space.net [IPv6:2001:608:2:2::251]) by mobil.space.net (Postfix) with ESMTP id BB104600E4; Fri, 24 Feb 2017 20:56:46 +0100 (CET)
Received: by moebius4.space.net (Postfix, from userid 1007) id AD2DC70A76; Fri, 24 Feb 2017 20:56:46 +0100 (CET)
Date: Fri, 24 Feb 2017 20:56:46 +0100
From: Gert Doering <gert@space.net>
To: Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
Message-ID: <20170224195646.GI2367@Space.Net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com> <CAL9jLaZ86B8EKy9hrJY2mO3GZDurbp4QZohwMZDrkZyj8ayA_g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL9jLaZ86B8EKy9hrJY2mO3GZDurbp4QZohwMZDrkZyj8ayA_g@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.7.2 (2016-11-26)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oepeWtoSHBwqaonGbk5-yE_J5G4>
Cc: Erik Kline <ek@google.com>, IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 19:56:52 -0000

Hi,

On Fri, Feb 24, 2017 at 10:04:11AM -0500, Christopher Morrow wrote:
> For enduser deployment picking 'something' (/64 is perfectly fine) is
> totally sane, and already in the proposed text. The sticking point isn't so
> much: "ipv6 is ipv4 with  more bits" (which the network treats it as) but:
> "hey, we know we allocate longer prefixes all the time for 'reasons' on
> things that have bespoke config, let's not make that harder by letting
> vendors/etc take shortcuts... acknowledge the fact that we really do have
> interfaces with >/64 deployed.

+1

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

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


From nobody Fri Feb 24 12:48:47 2017
Return-Path: <pch-bF054DD66@u-1.phicoh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED42129507; Fri, 24 Feb 2017 12:48:43 -0800 (PST)
X-Quarantine-ID: <DdPXfYSVf2v4>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "Cc"
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 DdPXfYSVf2v4; Fri, 24 Feb 2017 12:48:41 -0800 (PST)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) by ietfa.amsl.com (Postfix) with ESMTP id 61080129502; Fri, 24 Feb 2017 12:48:39 -0800 (PST)
Received: from stereo.hq.phicoh.net ([::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #127) id m1chMn7-0000DhC; Fri, 24 Feb 2017 21:48:37 +0100
Message-Id: <m1chMn7-0000DhC@stereo.hq.phicoh.net>
To: ietf@ietf.org
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets 
From: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com> <CAL9jLaaOWm+iQMOOGg00CXrhHtKZ0PxBswaJTUn6wf-EDq4KgQ@mail.gmail.com> <CAAedzxqPzPweW6RQUfHfUB0ZktofuY8HxKz-LbiBNWg+2ZoBaw@mail.gmail.com> <CAL9jLaZ86B8EKy9hrJY2mO3GZDurbp4QZohwMZDrkZyj8ayA_g@mail.gmail.com> 
In-reply-to: Your message of "Fri, 24 Feb 2017 10:04:11 -0500 ." <CAL9jLaZ86B8EKy9hrJY2mO3GZDurbp4QZohwMZDrkZyj8ayA_g@mail.gmail.com> 
Date: Fri, 24 Feb 2017 21:48:36 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oMi0gyplIQvWY5Mld6pdh9XupU4>
Cc: IPv6 Operations <v6ops@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 20:48:43 -0000

>For enduser deployment picking 'something' (/64 is perfectly fine) is
>totally sane, and already in the proposed text. The sticking point isn't so
>much: "ipv6 is ipv4 with  more bits" (which the network treats it as) but:
>"hey, we know we allocate longer prefixes all the time for 'reasons' on
>things that have bespoke config, let's not make that harder by letting
>vendors/etc take shortcuts... acknowledge the fact that we really do have
>interfaces with >/64 deployed.

I wonder if (in typical IPv4 fashion) we mix address configuration with
onlink prefixes.

There are three generic address configuration mechanisms, SLAAC, DHCP IA_NA,
and manual. Of these only SLAAC cares about the prefix length. And there
are good reasons to keep SLAAC at 64 bits.

(If would strongly suggest to not pick a random 32 bit IID, combine it
with a /96 and then hope that duplicate addresses detection in all cases
will safe the day. So for longer prefixes, use DHCP or manual configuration.)

For DHCP and manual configuration, an address is just that, an address.
So in that case, the prefix length actually refers to the length of the
onlink prefix.

Note that RFC 4861 (Neighbor Discovery) already specifies that an onlink
prefix can have arbitrary length. 

So it safe to assume that hosts can support arbitrary length onlink
prefixes. Otherwise those host implementations are already broken.

DHCP doesn't have a prefix length, so that's not an issue.

So that leaves hosts that mistakenly combine manual address configuration
with implicit onlink prefix configuration and an arbitrary restriction
on the prefix length. It is safe to declare those hosts broken.



From nobody Fri Feb 24 14:24:46 2017
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25823129529; Fri, 24 Feb 2017 14:24:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KuiFEDVPDvSV; Fri, 24 Feb 2017 14:24:43 -0800 (PST)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::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 A7595129525; Fri, 24 Feb 2017 14:24:43 -0800 (PST)
Received: by mail-qt0-x232.google.com with SMTP id b16so28194295qte.0; Fri, 24 Feb 2017 14:24:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=cQMj9L8UtavpiAntJeVZV9DrUh0+PnpvJVLmLDuTtoM=; b=kWvtkfwYJiFSaR5sF0WJPQeuKOpH5bhLPMGrKRTTWkfOY9tgiegmEvJFMyhb7yDOZ8 nuIW6ZJUCULLP5PaivN0yfjrgoHwM/huEsd54j+P1g2NQdsA6kYIBLGW0NnC6qhX+b8z PkNVoUfHsNasBEVH4y5Vj4JwmTAmnYSw+zCTsr8LAh6QV1+/+cRca8y6HIXPHyVTE1NW AQsHZMyE0y0xHHeIqeHQ6YrkjiTwSm+tvHsQ/j6WbYXr5ZrKHEMYcht1br1wpRTLpnbT MRROhdBuEZPkus6t+/dGKQ/YBSjmDkOXJLuUozRLTrN8G0UgxVYa4kTN76YNuXA20hdY QuMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=cQMj9L8UtavpiAntJeVZV9DrUh0+PnpvJVLmLDuTtoM=; b=GXVtDEpDt1+gpDbwE2DYjgx2/BfisEGniZ7gFyVDfHDr/2VM0qeMxwtePtjdCfi3d4 5DOY9K3X2v+Aa85F2FTZpnDEljC4OyRgWiLtRg/YIs0J41LCCb71NfbAmgWaE31M/EKE u9E72exOpYgGtu0wk1hJo4CzxBHhCb6eq/aoPzpKakwQWYvw6iA3Iq0U0IRi05o/4TaT RjVRs1RlEhJdYsxT4F+sFSDJpYpc/DaeQ/7aZum7GrfjCvhxF5brUtcq4FECHEjnMu4F rI1/W4eHNS7La9Zfs8PR4zx+yjHa/NcLJccMwI6yXIiENpXBxm2DOd4MTFCMCoOKXrTu pc+g==
X-Gm-Message-State: AMke39kq/h2pR0cWxDNJVBto5znJEHGbd/jRGYAlCZwHMxNbEi+PyxLpG+UPwTRpEEE0RvtSdAqZB+VJaA88Xg==
X-Received: by 10.200.34.28 with SMTP id o28mr5627443qto.269.1487975082503; Fri, 24 Feb 2017 14:24:42 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.61.204 with HTTP; Fri, 24 Feb 2017 14:24:41 -0800 (PST)
In-Reply-To: <CAN-Dau3shR-f9hA0Thnv7caRKQieiaqnA-4MweDikWk4kBqiUg@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAN-Dau0xpjB4Z8CgSfW0W7y4F_wnXNS+Ws1UNBC-YnBDrPiTjQ@mail.gmail.com> <cf3496dc-47c6-6c6b-a42a-e0402789110a@si6networks.com> <CAN-Dau3bHXOaJGe1UaLdDht9=+WiD4SEu8qw9Sc915tOes5seA@mail.gmail.com> <A0EDE3AA-95AA-418B-A2B3-E9C8A74204A5@darou.fr> <CAN-Dau3shR-f9hA0Thnv7caRKQieiaqnA-4MweDikWk4kBqiUg@mail.gmail.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Fri, 24 Feb 2017 14:24:41 -0800
X-Google-Sender-Auth: B2ZgJMh9L3S-hbU00aeu6n1Xzak
Message-ID: <CAJE_bqc361a8Q9CKNw6yOzDJzew5O_zoAMb37a3rT-OtJW-dyw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: David Farmer <farmer@umn.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/K8XoEshURT1XvGyswrw1Tf5Ybxs>
Cc: 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Feb 2017 22:24:45 -0000

At Fri, 24 Feb 2017 02:20:09 -0600,
David Farmer <farmer@umn.edu> wrote:

> >    IPv6 unicast routing is based on prefixes of any valid length up to
> >    and including 128 [BCP198].  However, subnet prefixes of 64 bits in
> >    length are REQUIRED for use with Stateless Address Autoconfiguration
> >    (SLAAC)[RFC4862] and are RECOMMENDED for all other general purpose
> >    use. The rationale for the 64 bit boundary in IPv6 addresses can be
> >    found in [RFC7421].
> >
> > Except RFC4862(SLAAC) does not say anywhere that 64 bits long IIDs are
> > required.
> > Only mention I find of 64 is given as an example for EUI-64 for ethernet
> > links.
>
> I believe most implementations of SLAAC require /64, but I could be wrong.

I don't know about "most implementations", but at least BSD variants
don't unconditionally require /64 for the IID (and therefore prefix)
length of SLAAC.  It literally implements what RFC4862 states:

   interface identifier -  [...]  The
      exact length of an interface identifier and the way it is created
      is defined in a separate link-type specific document that covers
      issues related to the transmission of IP over a particular link
      type (e.g., [RFC2464]).

That is, for the SLAAC implementation the length of the IID is a
parameter per link-type, not a magic constant value of 64.  And, as
specified in RFC2464, the value for Ethernet links is defined to be
64.  For an external observer it may not be distinguishable from the
magic number is hardcoded as if required for the entire
implementation, but the actual implementation is far from that.

So, aside from whether the above text is good in the main context of
this thread, just to make it more accurate it should be, e.g.:

    IPv6 unicast routing is based on prefixes of any valid length up to
    and including 128 [BCP198].  However, subnet prefixes of 64 bits
    are REQUIRED for use with Stateless Address Autoconfiguration
    (SLAAC)[RFC4862] in some link types such as Ethernet [RFC2464]. [...]

BTW, I think your idea of separating the implementation guidance and
operational guidance can be a compromise.  If I correctly interpret
the interests of main stake holders in this thread, these are:

- some educated adults (aka "operators") want to be allowed to
  configure there IPv6 addresses with an arbitrary IID (and therefore
  arbitrary length of subnet prefix).  and they don't want rfc4291bis
  to explicitly ban such an operation
- some implementers want to be allowed to write code that only allows
  64-bit IIDs for IPv6 addresses (except those that start with the
  binary value 000) to configure for that implementation.  and they
  don't want rfc4291bis to make such an implementation non-compliant.
- maybe some others also want to use the existence of such
  implementations as leverage to refuse ISPs offering very small size
  of subnet.

If I'm correct that these are main concerns, text like your proposal
seems to meet these even if no one is completely satisfied.

--
JINMEI, Tatuya


From nobody Fri Feb 24 16:26:49 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECCB41295EF; Fri, 24 Feb 2017 16:26:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l39Nf-t7RqVW; Fri, 24 Feb 2017 16:26:44 -0800 (PST)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::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 5B09512952F; Fri, 24 Feb 2017 16:26:44 -0800 (PST)
Received: by mail-oi0-x232.google.com with SMTP id 65so18394769oig.1; Fri, 24 Feb 2017 16:26:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pZ2LMT0DnyuRmWcopPFki0lKnhKfLE8lC3n9ErE3KwA=; b=jQS7tNfRCCyJbOB8AtPGM2awN5mv51wokBjWvGAfuQ5QFDeerFzIukUUNMOOegRvZW RjdRoS3ASsc1MxCjAhVp6LomSm+BIxaRGNu+2LjS5FCSEoQEFYeEOV9kxEhcVRKMeM53 X41PUDxVpgHa7cOE0WoH72bokBmZyg/lTE8EATfjpfe4H877rg2+iYpAQkiOXt0Ckudi JWKx7ayVUbcPBdr6MnZHi0wXPwXQ3GPCZ+y8+h38Lp7q8/Uzx/+xVlI5c1IuLXkbGkuL mZwR/cXlj2uUtIsgTjHGUl5O9EzmjbcOInEvyNrMKb9Jwdn6q6ygCUTYsjsNw6KJj4nT BTgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=pZ2LMT0DnyuRmWcopPFki0lKnhKfLE8lC3n9ErE3KwA=; b=AdmPahw8Q6qcbbOm5MPQeaPsaOoe7iHHk0QgiufNx7Ykimwfz3wWyrl1ot8pqlmOuI VaUgvk2tD/Us5xsQbSRlwodESl31X89agrO2bFvLg4NPVEtv4i7S3sn3qvPBofdG9p/N 3xS3WJbAXqYgw3uyjkXg4qWwG4aSwezUNWKt1x7tYd9lmh2XtiEzX9WCfg7WRNwaj5tW 8aDimiflo5DfKizHKtmM8AMn41wX7RzU28B+dARmEcuWq7GrASRwMbm31kMTH+jT/jKW e1oNH4xKr9xhKcnTv+cApuAq/ppz7HxgmWgLanQgCGtUZaTtaqGi30ZczMlPY9inAx6t 4w8w==
X-Gm-Message-State: AMke39mssvqiLUEByiPPlSfjJJ00/XzNIFQidbz9G95wOHmc6E8EE9QOFPWk4Naz0NAVRnCL3GfAguTdfrOV+g==
X-Received: by 10.202.72.6 with SMTP id v6mr3104350oia.177.1487982403303; Fri, 24 Feb 2017 16:26:43 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Fri, 24 Feb 2017 16:26:12 -0800 (PST)
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148527996733.12573.15522530300481191993.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B933009DEB0B5@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMC8d9dRGA0mYm-ALbZOnnq6LTLE=56imUFqK9JZ0wC=pw@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E16627@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <CA+9kkMBw-QbaDzDanWs6sH-z7rEteofCvp8-d-qSf9J31zJykA@mail.gmail.com> <787AE7BB302AE849A7480A190F8B933009E183CF@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 24 Feb 2017 16:26:12 -0800
Message-ID: <CA+9kkMC4-e=HXSa=QX4m1GgKFA1y-PmKsHkwQTg-ckEM2tGUbw@mail.gmail.com>
Subject: Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt> (Design considerations for Metadata Insertion) to Informational RFC
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>
Content-Type: multipart/alternative; boundary=001a113db24894c0f205494fe667
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GZ1SHXl01cH3sIbEAUuoTEfc3v8>
Cc: "draft-hardie-privsec-metadata-insertion@ietf.org" <draft-hardie-privsec-metadata-insertion@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 00:26:48 -0000

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

Hi Mohamed,

Some replies in-line.

On Fri, Feb 24, 2017 at 12:55 AM, <mohamed.boucadair@orange.com> wrote:

> Hi Ted,
>
>
>
> Please see inline.
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Ted Hardie [mailto:ted.ietf@gmail.com]
> *Envoy=C3=A9 :* vendredi 24 f=C3=A9vrier 2017 00:40
> *=C3=80 :* BOUCADAIR Mohamed IMT/OLN
> *Cc :* ietf@ietf.org; draft-hardie-privsec-metadata-insertion@ietf.org
> *Objet :* Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
> (Design considerations for Metadata Insertion) to Informational RFC
>
>
>
> HI Mohamad,
>
> Thanks for rechecking; some further comments in-line.
>
> On Wed, Feb 22, 2017 at 11:21 PM, <mohamed.boucadair@orange.com> wrote:
>
> Hi Ted,
>
>
>
> Thank you for the reply and for implementing these changes.
>
>
>
> I checked the diff, but I=E2=80=99m afraid the -06 version has the same i=
ssues as
> the ones I reported in January 31.
>
>
>
>
>
> I did respond to the particular comments and text proposals, so I assume
> this is the more general issue.  If I understand correctly, you would
> prefer this document to be structured as a revision to the threat model
> document or connected to a larger consideration of the issues.  I
> understand that, and it was considered, but I believe that this format is
> still the most effective for the narrow issue it addresses.
>
> [Med] That was one of my concerns; not the only one. In Particular, I=E2=
=80=99m
> trying to understand how this document will be used in the future to bett=
er
> strengthen forthcoming specifications. Further, the experience I had when
> advancing some RFCs is that RFC7258 wording can be further enhanced to
> provide clear guidance. Also, considerations such as the following are
> missing from the document:
>
It's difficult to say how something will be used in the future.  My intent
(and the understanding of other reviewers) is to highlight that these
mechanisms have a privacy-damaging result and that this should be
considered.  In particularly, I'm concerned that some application functions
in the network (e.g. recursive resolvers or proxies) do not consider the
postive privacy implications of their aggregation and so do not consider
adding this data back as problematic.   Highlighting this enables them to
see this traffic in a different context.

* that data may not be always available to the endhost

Understood, but even in this case, it is better to make the permission to
add the data explicit. It is also often possible for the end system to gain
this data at the cost of other traffic(e.g. the STUN server requests noted
in the document).  If this can be done in parallel with other actions, then
the latency impact can be minimized.

* a misbehaving node may be tempted to spoof the data to be injected. A
> remote device that will use that data to enforce policies will be broken.
>
This point was discussed extensively in the GEOPRIV work and essentially a
single carve-out was made:  for emergency services, where falsely asserted
location data could be used to SWAT individuals or consume safety
resources.    I don't think that falls into this narrow advice, but I would
be willing to add something like this to the security considerations:

"Note that some emergency service recipients, notably PSAPs (Public Safety
Answering Points) may prefer data provided by a network to data provided by
end system, because an end system could use false data to attack others or
consume resources.   While this has the consequence that the data available
to the PSAP is often more coarse than that available to the end system, the
risk of false data being provided involved a risk to the lives of those
targeted."

> * it was reported in the past that some browsers leak the MSISDN and othe=
r
> sensitive data.
>
> This is true, but it seems to me unrelated to the point of the document.


> From that flow some of your other concerns about audience, at least as I
> understand.  As written, this is narrow advice for a broad audience:
> basically, anyone who would consider the form of metadata insertion it
> describes.  You would, if I understand you, prefer a narrower description
> of the audience in a larger context.
>
>
>
> [Med] The key point here is about the practicality of implementing the
> advice NOT changing the scope. For example, the document says that it is
> better that a host is injecting the data but the document does not questi=
on
> whether that supplied data can be trusted or not, or how the consent will
> be obtained from a user.
>

In general, the point of the document is that the host should be able to
omit the data without mid-network devices adding it back.  That's the point
of protecting the traffic in the first place, after all.  I am saying that
if the protocols require the data, then getting it from the end host has
better privacy properties than getting from it from mid-network entities.


> For example, the document states that the information in a Forward-For
> header can be supplied by the host itself and then communicated to a remo=
te
> consumer. This is indeed possible, but because of abusing hosts some
> servers implement whitelists to trust proxies; see
> https://meta.wikimedia.org/w/extensions/TrustedXFF/trusted-hosts.txt.
>
>
>
>

The Wikimedia case is a very interesting one to raise, because it derives
from a set of assumptions about the network that are somewhat flawed and
then attempts to patch those flaws in ways that actually damage the
mechanisms of the system they originally built.

Wikimedia wants to allow folks to edit without login credentials.  This
allows for anonymous users to make corrections or additions; this is a
goal.  The consequence of that goal being achieved is that trolls or
malicious editors can have at anything they want.

Rather than institute credentials and ACLs, Wikimedia attempts to
substitute blocking by IP for blocking by credential.  The property they
are looking for in IPs is not really there, though:  they are not unique to
individuals, especially over time.

This damages those who share IP addresses (due to NATs or proxies).  As far
as I can tell, the NAT problem is simply treated as collateral damage.  For
the proxies, they attempt to work around the damage using XFF.  That's
spoofable, though, so they attempt to limit it to specific proxies whose
XFF they trust--many of which require logins.  That shifts the information
about who is editing Wikipedia out of their hands, but leaves it in the
network and thus not truly anonymous.  I understand the engineering balance
they are trying to strike, but I'm not sure I can recommend their solution.


> I=E2=80=99m reiterating that most of my comments are still unaddressed in=
 -06.
>
>
>
>
>
> I realize that the document did not change to address the audience or
> document integration you preferred; I think there we simply disagree on h=
ow
> to make this advice effective.  I'm sorry that first message apparently d=
id
> not describe the disagreement effectively.
>
> If I have misunderstood your comments, please accept my apologies. I woul=
d
> be happy of further clarification and suggested text to illustrate your
> preferences would be especially welcome.
>
> [Med] Sure. Before that, can you please consider rechecking the detailed
> list of comments available at: https://www.ietf.org/mail-
> archive/web/ietf/current/msg101629.html. Thank you.
>
>
>
Thanks again for your engagement on this,

regards,

Ted



> thanks,
>
> Ted Hardie
>
>
>
>
> Cheers,
>
> Med
>
>
>
> *De :* Ted Hardie [mailto:ted.ietf@gmail.com]
> *Envoy=C3=A9 :* mercredi 22 f=C3=A9vrier 2017 23:09
> *=C3=80 :* BOUCADAIR Mohamed IMT/OLN
> *Cc :* ietf@ietf.org; draft-hardie-privsec-metadata-insertion@ietf.org
> *Objet :* Re: Last Call: <draft-hardie-privsec-metadata-insertion-05.txt>
> (Design considerations for Metadata Insertion) to Informational RFC
>
>
>
> Hi Mohamed,
>
> Thanks for your review.  I've uploaded a draft -06 with updates from your
> and other reviews.  Some notes in-line.
>
>
>
> On Tue, Jan 31, 2017 at 1:49 AM, <mohamed.boucadair@orange.com> wrote:
>
> Dear Ted,
>
> Please find below my general review of the document and also my detailed
> comments.
>
> * Overall:
> - I don't think the document is ready to be published as it is. It does
> not discuss the usability and implications of the advice. Further, it may
> be interpreted that a client/end system/user can always by itself populat=
e
> data that is supplied by on-path nodes (in current deployments). That's
> assumption is not true for some protocols.
> - The purpose of publishing this advice is not clear. For example, how
> this advice will be implemented in practice? What is its scope?
> - I would personally prefer an updated version of RFC7258 with more stric=
t
> language on the privacy-related considerations. This is more actionable
> with concrete effects in documents that will required to include a
> discussion on privacy related matters.
>
> Detailed comments are provided below:
>
> * The abstract says the following:
>
>    The IAB has published [RFC7624] in response to several revelations of
>    pervasive attack on Internet communications.  This document considers
>    the implications of protocol designs which associate metadata with
>    encrypted flows.  In particular, it asserts that designs which do so
>    by explicit actions of the end system are preferable to designs in
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    which middleboxes insert them.
>
> I suggest you explicit what is meant by "the end system".
>
>
>
> I have updated this to clarify that this is the host/end system not the
> user.
>
>
> If you mean the owner/user, then the text should say so. If you mean a
> client software instance, then bugs/inappropriate default values may lead
> to (privacy leak) surprises too. It was reported in the past that some
> browsers inject the MSISDN too.
>
> * Introduction: "To ensure that the Internet can be trusted by users"
>
> Rather =C2=AB To minimize the risk of Internet-originated attacks targete=
d at
> users =C2=BB.
>
>
>
> I've adopted this language.
>
>
>
> It's reasonable to claim the Internet can be trusted by users; see how th=
e
> usage of social networks has become severely twisted for example
>
>
>
> I've also considered your point that an updated version of RFC7258 might
> be a better outlet for advice like this. We did consider several
> approaches, including incorporating the text in an update to  RFC 3552 or
> as part of a document describing the full set of companion mitigations to
> the threats in RFC 7624 (draft-iab-privsec-confidentiality-mitigations
> would be one approach).  Those are all valid approaches, but it seemed th=
at
> short, easily read documents tackling a single point might be easier to
> produce and consume.
>
> Thanks again for your review,
>
> Ted Hardie
>
>
>
>
>

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

<div dir=3D"ltr"><div>Hi Mohamed,<br><br></div>Some replies in-line.<br><di=
v><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Fe=
b 24, 2017 at 12:55 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:mohamed.bo=
ucadair@orange.com" target=3D"_blank">mohamed.boucadair@orange.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">





<div link=3D"blue" vlink=3D"purple" lang=3D"FR">
<div class=3D"m_-8372899661075484543WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Hi Ted,
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Please see inline.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Cheers,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black">Med<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">De=C2=A0:</span></b><span style=3D"fo=
nt-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Ted =
Hardie [mailto:<a href=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.=
ietf@gmail.com</a>]
<br>
<b>Envoy=C3=A9=C2=A0:</b> vendredi 24 f=C3=A9vrier 2017 00:40<span class=3D=
""><br>
<b>=C3=80=C2=A0:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc=C2=A0:</b> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ie=
tf.org</a>; <a href=3D"mailto:draft-hardie-privsec-metadata-insertion@ietf.=
org" target=3D"_blank">draft-hardie-privsec-metadata-<wbr>insertion@ietf.or=
g</a><br>
<b>Objet=C2=A0:</b> Re: Last Call: &lt;draft-hardie-privsec-<wbr>metadata-i=
nsertion-05.txt&gt; (Design considerations for Metadata Insertion) to Infor=
mational RFC<u></u><u></u></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">HI Mohamad,<span class=3D""><br>
<br>
Thanks for rechecking; some further comments in-line.<br>
<br>
On Wed, Feb 22, 2017 at 11:21 PM, &lt;<a href=3D"mailto:mohamed.boucadair@o=
range.com" target=3D"_blank">mohamed.boucadair@orange.com</a>&gt; wrote:<u>=
</u><u></u></span></p>
<div>
<div><span class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Hi Ted,</span><u></u><u></u></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Thank you for the reply and for=
 implementing these changes.
</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">I checked the diff, but I=E2=80=
=99m afraid the -06 version has the same issues as the ones I reported in
 January 31.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I did respond to the =
particular comments and text proposals, so I assume this is the more genera=
l issue.=C2=A0 If I understand correctly, you would prefer this document to=
 be structured as a revision to the threat
 model document or connected to a larger consideration of the issues.=C2=A0=
 I understand that, and it was considered, but I believe that this format i=
s still the most effective for the narrow issue it addresses.<u></u><u></u>=
</p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"=
EN-US">[Med] That was one of my concerns; not the only one. In Particular, =
I=E2=80=99m trying to understand how this document will be used in
 the future to better strengthen forthcoming specifications. Further, the e=
xperience I had when advancing some RFCs is that RFC7258 wording can be fur=
ther enhanced to provide clear guidance. Also, considerations such as the f=
ollowing are missing from the document:</span></p></div></div></div></div><=
/div></div></div></blockquote><div>It&#39;s difficult to say how something =
will be used in the future.=C2=A0 My intent (and the understanding of other=
 reviewers) is to highlight that these mechanisms have a privacy-damaging r=
esult and that this should be considered.=C2=A0 In particularly, I&#39;m co=
ncerned that some application functions in the network (e.g. recursive reso=
lvers or proxies) do not consider the postive privacy implications of their=
 aggregation and so do not consider adding this data back as problematic.=
=C2=A0=C2=A0 Highlighting this enables them to see this traffic in a differ=
ent context.<br><br><span style=3D"font-size:10.0pt;font-family:&quot;Couri=
er New&quot;;color:black" lang=3D"EN-US">* that data may not be always avai=
lable to the endhost<br><br></span></div><div><span style=3D"font-family:ar=
ial,helvetica,sans-serif"><span style=3D"font-size:10pt;color:black" lang=
=3D"EN-US">Understood, but even in this case, it is better to make the perm=
ission to add the data explicit. It is also often possible for the end syst=
em to gain this data at the cost of other traffic(e.g. the STUN server requ=
ests noted in the document).=C2=A0 If this can be done in parallel with oth=
er actions, then the latency impact can be minimized.<br></span></span></di=
v><div><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black" lang=3D"EN-US"><br></span></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_-837289966=
1075484543WordSection1"><div style=3D"border:none;border-left:solid blue 1.=
5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">=
* a misbehaving node may be tempted to spoof the data to be injected. A rem=
ote device that will use that data to enforce policies
 will be broken.</span></p></div></div></div></div></div></div></div></bloc=
kquote><div>This point was discussed extensively in the GEOPRIV work and es=
sentially a single carve-out was made:=C2=A0 for emergency services, where =
falsely asserted location data could be used to SWAT individuals or consume=
 safety resources.=C2=A0=C2=A0=C2=A0 I don&#39;t think that falls into this=
 narrow advice, but I would be willing to add something like this to the se=
curity considerations:<br><br></div><div>&quot;Note that some emergency ser=
vice recipients, notably PSAPs (Public Safety Answering Points) may prefer =
data provided by a network to data provided by end system, because an end s=
ystem could use false data to attack others or consume resources.=C2=A0=C2=
=A0 While this has the consequence that the data available to the PSAP is o=
ften more coarse than that available to the end system, the risk of false d=
ata being provided involved a risk to the lives of those targeted.&quot;</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=
=3D"FR"><div class=3D"m_-8372899661075484543WordSection1"><div style=3D"bor=
der:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div>=
<div><div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=
=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=
=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">=
* it was reported in the past that some browsers leak the MSISDN and other =
sensitive data.<u></u><u></u></span></p>
</div>
<div><span class=3D"">
<p class=3D"MsoNormal"><span lang=3D"EN-US"></span></p></span></div></div><=
/div></div></div></div></div></blockquote><div>This is true, but it seems t=
o me unrelated to the point of the document.<br></div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR">=
<div class=3D"m_-8372899661075484543WordSection1"><div style=3D"border:none=
;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><di=
v><span class=3D""><p class=3D"MsoNormal"><span lang=3D"EN-US">From that fl=
ow some of your other concerns about audience, at least as I understand.=C2=
=A0 As written</span>, this is narrow advice for a broad audience: basicall=
y, anyone who would consider the form of metadata insertion
 it describes.=C2=A0 You would, if I understand you, prefer a narrower desc=
ription of the audience in a larger context.=C2=A0
<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
</span><p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&=
quot;Courier New&quot;;color:black" lang=3D"EN-US">[Med] The key point here=
 is about the practicality of implementing the advice NOT changing the scop=
e. For example, the document says that it is better that
 a host is injecting the data but the document does not question whether th=
at supplied data can be trusted or not, or how the consent will be obtained=
 from a user.</span></p></div></div></div></div></div></div></div></blockqu=
ote><div><br></div><div>In general, the point of the document is that the h=
ost should be able to omit the data without mid-network devices adding it b=
ack.=C2=A0 That&#39;s the point of protecting the traffic in the first plac=
e, after all.=C2=A0 I am saying that if the protocols require the data, the=
n getting it from the end host has better privacy properties than getting f=
rom it from mid-network entities.<br></div><div>=C2=A0</div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=
=3D"m_-8372899661075484543WordSection1"><div style=3D"border:none;border-le=
ft:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=
=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Courier Ne=
w&quot;;color:black" lang=3D"EN-US"> For example, the document states that =
the information in a Forward-For header can be supplied
 by the host itself and then communicated to a remote consumer. This is ind=
eed possible, but because of abusing hosts some servers implement whitelist=
s to trust proxies; see
<a href=3D"https://meta.wikimedia.org/w/extensions/TrustedXFF/trusted-hosts=
.txt" target=3D"_blank">https://meta.wikimedia.org/w/<wbr>extensions/Truste=
dXFF/trusted-<wbr>hosts.txt</a>. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<u></u><u></=
u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=C2=A0</span></p></div></span><=
/div></div></div></div></div></div></blockquote><div><br></div><div>The Wik=
imedia case is a very interesting one to raise, because it derives from a s=
et of assumptions about the network that are somewhat flawed and then attem=
pts to patch those flaws in ways that actually damage the mechanisms of the=
 system they originally built.<br><br></div><div>Wikimedia wants to allow f=
olks to edit without login credentials.=C2=A0 This allows for anonymous use=
rs to make corrections or additions; this is a goal.=C2=A0 The consequence =
of that goal being achieved is that trolls or malicious editors can have at=
 anything they want.<br><br></div><div>Rather than institute credentials an=
d ACLs, Wikimedia attempts to substitute blocking by IP for blocking by cre=
dential.=C2=A0 The property they are looking for in IPs is not really there=
, though:=C2=A0 they are not unique to individuals, especially over time.=
=C2=A0 <br><br>This damages those who share IP addresses (due to NATs or pr=
oxies).=C2=A0 As far as I can tell, the NAT problem is simply treated as co=
llateral damage.=C2=A0 For the proxies, they attempt to work around the dam=
age using XFF.=C2=A0 That&#39;s spoofable, though, so they attempt to limit=
 it to specific proxies whose XFF they trust--many of which require logins.=
=C2=A0 That shifts the information about who is editing Wikipedia out of th=
eir hands, but leaves it in the network and thus not truly anonymous.=C2=A0=
 I understand the engineering balance they are trying to strike, but I&#39;=
m not sure I can recommend their solution.<br></div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><d=
iv class=3D"m_-8372899661075484543WordSection1"><div style=3D"border:none;b=
order-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><span=
 class=3D""><div><p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u><u></u>=
</span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">I=E2=80=99m reiterating that mo=
st of my comments are still unaddressed in -06.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I realize that the do=
cument did not change to address the audience or document integration you p=
referred; I think there we simply disagree on how to make this advice effec=
tive.=C2=A0 I&#39;m sorry that first message
 apparently did not describe the disagreement effectively.<u></u><u></u></p=
>
</div>
</span><div><span class=3D"">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">If I have misundersto=
od your comments, please accept my apologies. I would be happy of further c=
larification and suggested text to illustrate your preferences would be esp=
ecially welcome.<u></u><u></u></p>
</span><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D=
"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"=
EN-US">[Med] Sure. Before that, can you please consider rechecking the deta=
iled list of comments available at:
<a href=3D"https://www.ietf.org/mail-archive/web/ietf/current/msg101629.htm=
l" target=3D"_blank">https://www.ietf.org/mail-<wbr>archive/web/ietf/curren=
t/<wbr>msg101629.html</a>. Thank you.
<u></u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US">=
<u></u>=C2=A0</span></p></div></div></div></div></div></div></div></blockqu=
ote><div>Thanks again for your engagement on this,<br><br></div><div>regard=
s,<br><br></div><div>Ted<br></div><div><br>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex"><div link=3D"blue" vlink=3D"purple" lang=3D"FR"><div class=3D"m_=
-8372899661075484543WordSection1"><div style=3D"border:none;border-left:sol=
id blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div><div><div><p class=3D"Ms=
oNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Courier New&quot;;color:black" lang=3D"EN-US"><u></u></span>=
</p>
</div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span lang=3D"EN-US">=
thanks,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Ted Hardie<u></u><u></u></span>=
</p>
</div>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
=C2=A0<u></u><u></u></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Cheers,</span><span lang=3D"EN-=
US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">Med</span><span lang=3D"EN-US">=
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Co=
urier New&quot;;color:black" lang=3D"EN-US">=C2=A0</span><span lang=3D"EN-U=
S"><u></u><u></u></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;" lang=3D"EN-US">De=C2=A0:</span></b><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-ser=
if&quot;" lang=3D"EN-US"> Ted
 Hardie [mailto:<a href=3D"mailto:ted.ietf@gmail.co" target=3D"_blank">ted.=
ietf@gmail.co</a></span><span style=3D"font-size:10.0pt;font-family:&quot;T=
ahoma&quot;,&quot;sans-serif&quot;">m]
<br>
<b>Envoy=C3=A9=C2=A0:</b> mercredi 22 f=C3=A9vrier 2017 23:09<br>
<b>=C3=80=C2=A0:</b> BOUCADAIR Mohamed IMT/OLN<br>
<b>Cc=C2=A0:</b> <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ie=
tf.org</a>; <a href=3D"mailto:draft-hardie-privsec-metadata-insertion@ietf.=
org" target=3D"_blank">
draft-hardie-privsec-metadata-<wbr>insertion@ietf.org</a><br>
<b>Objet=C2=A0:</b> Re: Last Call: &lt;draft-hardie-privsec-<wbr>metadata-i=
nsertion-05.txt&gt; (Design considerations for Metadata Insertion) to Infor=
mational RFC</span><u></u><u></u></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Hi Mohamed,<u></u><u>=
</u></p>
</div>
<p class=3D"MsoNormal">Thanks for your review.=C2=A0 I&#39;ve uploaded a dr=
aft -06 with updates from your and other reviews.=C2=A0 Some notes in-line.=
<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Jan 31, 2017 at 1:49 AM, &lt;<a href=3D"mail=
to:mohamed.boucadair@orange.com" target=3D"_blank">mohamed.boucadair@orange=
.com</a>&gt; wrote:<u></u><u></u></p>
<p class=3D"MsoNormal">Dear Ted,<br>
<br>
Please find below my general review of the document and also my detailed co=
mments.<br>
<br>
* Overall:<br>
- I don&#39;t think the document is ready to be published as it is. It does=
 not discuss the usability and implications of the advice. Further, it may =
be interpreted that a client/end system/user can always by itself populate =
data that is supplied by on-path nodes
 (in current deployments). That&#39;s assumption is not true for some proto=
cols.<br>
- The purpose of publishing this advice is not clear. For example, how this=
 advice will be implemented in practice? What is its scope?<br>
- I would personally prefer an updated version of RFC7258 with more strict =
language on the privacy-related considerations. This is more actionable wit=
h concrete effects in documents that will required to include a discussion =
on privacy related matters.<br>
<br>
Detailed comments are provided below:<br>
<br>
* The abstract says the following:<br>
<br>
<span class=3D"m_-8372899661075484543m-2746598804484943185gmail-">=C2=A0 =
=C2=A0The IAB has published [RFC7624] in response to several revelations of=
</span><br>
<span class=3D"m_-8372899661075484543m-2746598804484943185gmail-">=C2=A0 =
=C2=A0pervasive attack on Internet communications.=C2=A0 This document cons=
iders</span><br>
<span class=3D"m_-8372899661075484543m-2746598804484943185gmail-">=C2=A0 =
=C2=A0the implications of protocol designs which associate metadata with</s=
pan><br>
<span class=3D"m_-8372899661075484543m-2746598804484943185gmail-">=C2=A0 =
=C2=A0encrypted flows.=C2=A0 In particular, it asserts that designs which d=
o so</span><br>
<span class=3D"m_-8372899661075484543m-2746598804484943185gmail-">=C2=A0 =
=C2=A0by explicit actions of the end system are preferable to designs in</s=
pan><br>
=C2=A0 =C2=A0 =C2=A0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<wbr>^^^^<br>
=C2=A0 =C2=A0which middleboxes insert them.<br>
<br>
I suggest you explicit what is meant by &quot;the end system&quot;. <u></u>=
<u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I have updated this to clarify that this is the host=
/end system not the user.=C2=A0
<br>
=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<p class=3D"MsoNormal">If you mean the owner/user, then the text should say=
 so. If you mean a client software instance, then bugs/inappropriate defaul=
t values may lead to (privacy leak) surprises too.
 It was reported in the past that some browsers inject the MSISDN too.<br>
<br>
* Introduction: &quot;To ensure that the Internet can be trusted by users&q=
uot;<br>
<br>
Rather =C2=AB To minimize the risk of Internet-originated attacks targeted =
at users =C2=BB.
<u></u><u></u></p>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;ve adopted this language.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0cm;margin-=
bottom:5.0pt">
<p class=3D"MsoNormal">It&#39;s reasonable to claim the Internet can be tru=
sted by users; see how the usage of social networks has become severely twi=
sted for example<u></u><u></u></p>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">I&#39;ve also conside=
red your point that an updated version of RFC7258 might be a better outlet =
for advice like this. We did consider several approaches, including incorpo=
rating the text
 in an update to=C2=A0 RFC 3552 or as part of a document describing the ful=
l set of companion mitigations to the threats in RFC 7624 (draft-iab-privse=
c-<wbr>confidentiality-mitigations would be one approach).=C2=A0 Those are =
all valid approaches, but it seemed that short,
 easily read documents tackling a single point might be easier to produce a=
nd consume.=C2=A0
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Thanks again for your=
 review,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ted Hardie<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div></div></div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div></div></div>

--001a113db24894c0f205494fe667--


From nobody Sat Feb 25 08:01:44 2017
Return-Path: <mersue@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C6A12A12A; Sat, 25 Feb 2017 08:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HKvo98TDf_i7; Sat, 25 Feb 2017 08:01:42 -0800 (PST)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::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 B0DA612A126; Sat, 25 Feb 2017 08:01:41 -0800 (PST)
Received: by mail-wm0-x22e.google.com with SMTP id v77so33972453wmv.1; Sat, 25 Feb 2017 08:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language:disposition-notification-to; bh=0lbkYk7jPAXyODVDIVCzB0DInFPu0xxLd2gHptUlS3o=; b=QvBjjMpRktAa8ksQAQnSW11NEpfbpAFApjoVsEjL/VIuygjLzP/yGmSE73P9i5y80U ArWLzZIVuRkJw404g83twXPpqqERgBW5Y/Pd+SGYyEt6kxL52gzsQt9wCJCicEMOPhlp W8kdT+WbPp3BYveTSkjfyoNyGYeP1VKLHT1ZAPW01YodFRyDuvqaZlaTgCErrB2GmSzQ iCE+bR1lbbpmyxaIyr1AwcfkfgrC4IhtDhCI0x1F170wzy9EHUoQryOFKYpeuKoyEw9X TblRZEkEel6Vb47ffEdklM1pCkBWkkdvQt9Ht7imeCoUEcYD7801H1UQaY/kt9xTIGaC ggrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language:disposition-notification-to; bh=0lbkYk7jPAXyODVDIVCzB0DInFPu0xxLd2gHptUlS3o=; b=j3A1xpUTYMwV5Fezxu2KXuMU29j08J+du/D71lwMmOpiJe3IFHc4LVVQRWMl8HUgwi LV9cYo+zVoPCcpwsm//i7B0jz6A74FoDLa2tIBfRb6AYiB1mN28Bh/kcTq/hV0f0GY7U OvGNCmg68Pneu6XIHPcm3St8knh8u2z9EM1VHFFsMHxbSvf3Hw6hYjKOm3pDEEJOlRQa TSs7upj1XDge7fhVmY0zQks0NEwWAf0j+YOYBzl/Cq5cSw0Q2tJJ6UcuJlBp7I1hDj1h nPtilsN7M1Pbp8Ev3Bbg/6P8Wbt5V3GXUkXNrRDEp+nHJjGwPq3aEPSifDU1Vr6Yyj+u ZtFQ==
X-Gm-Message-State: AMke39mhE4/xYdnLcuJ9r6SLHYJ9HsB6FpsCUU1SKpAjWiwJWhPJbbqCtMiMnSM4e70HqQ==
X-Received: by 10.28.165.196 with SMTP id o187mr6752030wme.6.1488038499965; Sat, 25 Feb 2017 08:01:39 -0800 (PST)
Received: from DESKTOPFLHJVQJ (p5DCC6FAD.dip0.t-ipconnect.de. [93.204.111.173]) by smtp.gmail.com with ESMTPSA id a35sm14877788wra.21.2017.02.25.08.01.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Feb 2017 08:01:39 -0800 (PST)
From: "Mehmet Ersue" <mersue@gmail.com>
To: "'IETF Agenda'" <agenda@ietf.org>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com>
In-Reply-To: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com>
Subject: RE: IETF 98 Preliminary Agenda
Date: Sat, 25 Feb 2017 17:01:43 +0100
Message-ID: <005301d28f80$758d5c30$60a81490$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQLvBlHc5cYfAkTApDxLlwOHz1YA3p9A8+Aw
Content-Language: de
X-AVK-Virus-Check: AVA 25.10096;BF82DA0
X-AVK-Spam-Check: 1; str=0001.0A0C0204.58B1AA63.0068,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0; AE713
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/o3GcCkas6Gns8fdVF2llZN8RIG0>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 16:01:43 -0000

Dear Agenda Experts,

I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
Thank you for your consideration.

Regards,
Mehmet

> -----Original Message-----
> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of
> IETF Agenda
> Sent: Saturday, February 25, 2017 12:00 AM
> To: IETF Announcement List <ietf-announce@ietf.org>
> Cc: 98all@ietf.org
> Subject: IETF 98 Preliminary Agenda
> 
> The IETF 98 Preliminary Agenda has been posted. The final agenda will be
> published on Friday, March 3, 2017.
> 
> https://datatracker.ietf.org/meeting/98/agenda.html
> https://datatracker.ietf.org/meeting/98/agenda.txt
> 
> 
> More information regarding IETF 98 in Chicago is located here:
> https://www.ietf.org/meeting/98/index.html
> 
> Thank you!
> 
> IETF Secretariat



From nobody Sat Feb 25 09:29:24 2017
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4C1C128824; Sat, 25 Feb 2017 09:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ETjhsSpst_n0; Sat, 25 Feb 2017 09:29:22 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82A5C1270B4; Sat, 25 Feb 2017 09:29:22 -0800 (PST)
Received: from mbp-4.local (c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209]) (authenticated bits=0) by nagasaki.bogus.com (8.15.2/8.15.2) with ESMTPSA id v1PHTK6f055813 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 25 Feb 2017 17:29:21 GMT (envelope-from joelja@bogus.com)
X-Authentication-Warning: nagasaki.bogus.com: Host c-73-202-177-209.hsd1.ca.comcast.net [73.202.177.209] claimed to be mbp-4.local
Subject: Re: IETF 98 Preliminary Agenda
To: Mehmet Ersue <mersue@gmail.com>, "'IETF Agenda'" <agenda@ietf.org>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <005301d28f80$758d5c30$60a81490$@gmail.com>
From: joel jaeggli <joelja@bogus.com>
Message-ID: <a7852494-5cd0-1777-176b-399acd6ceecd@bogus.com>
Date: Sat, 25 Feb 2017 09:29:15 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <005301d28f80$758d5c30$60a81490$@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AQeT96oijDX3pLgx7oJ6hU7i5bSvBTJkM"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NEm10tzCjOmK4HPMGNyBYW0m0eY>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 17:29:24 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AQeT96oijDX3pLgx7oJ6hU7i5bSvBTJkM
Content-Type: multipart/mixed; boundary="1L8o8NXbLLu8NQCM8EJK0H4w0eBjwGuH9";
 protected-headers="v1"
From: joel jaeggli <joelja@bogus.com>
To: Mehmet Ersue <mersue@gmail.com>, 'IETF Agenda' <agenda@ietf.org>
Cc: ietf@ietf.org
Message-ID: <a7852494-5cd0-1777-176b-399acd6ceecd@bogus.com>
Subject: Re: IETF 98 Preliminary Agenda
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com>
 <005301d28f80$758d5c30$60a81490$@gmail.com>
In-Reply-To: <005301d28f80$758d5c30$60a81490$@gmail.com>

--1L8o8NXbLLu8NQCM8EJK0H4w0eBjwGuH9
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2/25/17 8:01 AM, Mehmet Ersue wrote:
> Dear Agenda Experts,
>
> I would like to ask to avoid an overlapping of nmrg with OPS area WGs.
> Thank you for your consideration.
I go to rather a lot of ops area working groups and I'm dubious the NMRG
colliades will all of them.

excessive collision lists just make scheduling harder.

joel
> Regards,
> Mehmet
>
>> -----Original Message-----
>> From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf =
Of
>> IETF Agenda
>> Sent: Saturday, February 25, 2017 12:00 AM
>> To: IETF Announcement List <ietf-announce@ietf.org>
>> Cc: 98all@ietf.org
>> Subject: IETF 98 Preliminary Agenda
>>
>> The IETF 98 Preliminary Agenda has been posted. The final agenda will =
be
>> published on Friday, March 3, 2017.
>>
>> https://datatracker.ietf.org/meeting/98/agenda.html
>> https://datatracker.ietf.org/meeting/98/agenda.txt
>>
>>
>> More information regarding IETF 98 in Chicago is located here:
>> https://www.ietf.org/meeting/98/index.html
>>
>> Thank you!
>>
>> IETF Secretariat
>



--1L8o8NXbLLu8NQCM8EJK0H4w0eBjwGuH9--

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

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

iEYEARECAAYFAlixvusACgkQ8AA1q7Z/VrIaVACcD8xCMneHkwC6dMhznKzsJOMt
LKsAmgNKvbNZwS0JI8NlC04bBy4ptI+x
=7dPC
-----END PGP SIGNATURE-----

--AQeT96oijDX3pLgx7oJ6hU7i5bSvBTJkM--


From nobody Sat Feb 25 11:41:16 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 506DF1294A6; Sat, 25 Feb 2017 11:41:15 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-anima-grasp-09
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
Date: Sat, 25 Feb 2017 11:41:15 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-zMMuJlGPkB8-3zBnuSZ_OU1BH8>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 19:41:15 -0000

Reviewer: Joel Halpern
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-anima-grasp-??
Reviewer: Joel Halpern
Review Date: 2017-02-25
IETF LC End Date: 2017-03-02
IESG Telechat date: Not scheduled for a telechat

Summary:

Major issues:

Minor issues:
     Section 2.2 states that routing protocols mainly consider link
up/down and that "all nodes need a consistent view of the network
topology".  the first seems an over-generalization, since all routing
protocols have metrics, and almost all modern routing protocols carry
significant additional information about the links and nodes.  The
second statement about consistency is true for some protocols, but is
not true for external use of BGP nor, as I understand it, for Babel. 
So it seems again too strong a characterization.  The following
sentence about information not normally used also seems to be at odds
with current practice.

    Bullet 1 under SN7 in section 2.2  talks about the potential for
circular dependence, and then says that this protocol will not provide
any assistance for that.  given that such dependence may be complex. 
In particular, given that these dependencies result in separate
negotiations, the chain of efforts would continue even if the initial
impetus has timed out.  If a single negotiation causes two dependent
negotiations, this would seem to have the potential to cause a work
explosion.

    It is probably considered obvious, but I did not see text
indicating that GRASP messages with unknown MESSAGE_TYPE should be
silently ignored.  Or any other definition of the expected behavior
(should be logged?)

Nits/editorial comments: 
    In section 3.1 in the definition of Technical Objective the text
starts by saying that it is a configurable parameter or set of
parameters.   Most further text refers to a single value, with
indications that the value may be a complex structure.  Hence, in the
first part of the definition, the same construction should be used,
rather than referring to a set of values.  This gets slightly confused
when section 3.10.4 goes back to talking about multiple parameters for
an objective.  Consistency please?

    The first paragraph of 3.5.4.1 states that upon receiving a
discovery request, a recipient will respond, either with the data or
with a divert.  While this is eventually true, it is misleading.  As
3.5.4.2 states, the recipient, if it does not have an answer, will
relay the request in order to get an answer.  Some mention of this in
3.5.4.1 would seem helpful.

    Should the first line of 3.5.5 on negotiation include "(using
M_REQ_NEG)"?



From nobody Sat Feb 25 12:43:58 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2481129535; Sat, 25 Feb 2017 12:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 DN29YI1KJMO6; Sat, 25 Feb 2017 12:43:55 -0800 (PST)
Received: from [10.132.216.20] (unknown [194.157.96.226]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id A89321294DB; Sat, 25 Feb 2017 12:43:54 -0800 (PST)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Impact of the "CloudBleed" bug on www.ietf.org
Date: Sat, 25 Feb 2017 22:43:50 +0200
Message-Id: <EBDE9228-B232-47B0-BFE1-3AC524ADBED8@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zbOxFIeEYj9dH6DQyUuzSEZx00s>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2017 20:43:56 -0000

As you may have seen, there was a recent and widely publicised bug
in the Cloudfare service. You can read more about the bug here:

=
https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloud=
flare-parser-bug/
https://github.com/pirate/sites-using-cloudflare

Since the IETF uses Cloudfare for our public-facing website, you may
be wondering whether there are IETF effects.

I wanted to let people know that we performed an initial analysis
of the possible impacts on Friday. The site www.ietf.org is primarily
static and the more interesting content is at datatracker.ietf.org
and various wikis that are not hosted at Cloudfare. However,
we we realised that there are a few groups of users (such as
the ADs) who use IETF credentials on www.ietf.org.

Consequently, it is possible that some of these credentials were
compromised. We=92ve taken the precaution of changing the
potentially affected passwords. As the analysis continues in
the starting week, if we identify further groups that may be
affected, we may be asking you to reset your passwords;
if you get such a request, please take action as soon as
possible.

For your information, datatracker passwords can always
be changed here:

https://datatracker.ietf.org/accounts/password/

Jari Arkko, IETF Chair


From nobody Sat Feb 25 16:08:04 2017
Return-Path: <xing@cernet.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2563512A425; Sat, 25 Feb 2017 16:07:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 NVHQ4ivnNms1; Sat, 25 Feb 2017 16:07:56 -0800 (PST)
Received: from tsinghua.edu.cn (smtp38.tsinghua.edu.cn [166.111.204.62]) by ietfa.amsl.com (Postfix) with ESMTP id 9E71012954D; Sat, 25 Feb 2017 16:07:55 -0800 (PST)
Received: from [192.168.1.100] (unknown [114.254.44.112]) by app6 (Coremail) with SMTP id D8xvpgDn7QU0HLJYtInFAA--.1567S2; Sun, 26 Feb 2017 08:07:17 +0800 (CST)
Message-ID: <58B21C34.1000409@cernet.edu.cn>
Date: Sun, 26 Feb 2017 08:07:16 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: sthaug@nethelp.no
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <CAKD1Yr0LHCT9_3QzaDY=XKWwSsA5CtE-4EqaQsp_Fp_3-Y56GA@mail.gmail.com> <30dda6a9-2683-8157-1b75-9aa154b8deb7@si6networks.com> <CAKD1Yr1hSj0VQQ4vkxnnATxbW3eM2G3WK57OR-fNffydHz5BTw@mail.gmail.com> <20170223.094711.41666643.sthaug@nethelp.no>
In-Reply-To: <20170223.094711.41666643.sthaug@nethelp.no>
Content-Type: multipart/alternative; boundary="------------080806070809030000050205"
X-CM-TRANSID: D8xvpgDn7QU0HLJYtInFAA--.1567S2
X-Coremail-Antispam: 1UD129KBjvdXoWrKry5AF4fuFy5Zw4xAr1rCrg_yoWfWrb_GF y5JF17Jw1UAF4UXw4jqr15Jr90yrW0qr1UJw18JrWfJr17Jrn8Jr18Gr43ZF9rXw15JryD JrWDGr18Jr1UXjkaLaAFLSUrUUUUUb8apTn2vfkv8UJUUUU8Yxn0WfASr-VFAUDa7-sFnT 9fnUUIcSsGvfJTRUUUbOAYjsxI4VW3JwAYFVCjjxCrM7AC8VAFwI0_Gr0_Xr1l1xkIjI8I 6I8E6xAIw20EY4v20xvaj40_Wr0E3s1l1IIY67AEw4v_Jr0_Jr4l8cAvFVAK0II2c7xJM2 8EF7xvwVC0I7IYx2IY67AKxVWUJVWUCwA2z4x0Y4vE2Ix0cI8IcVCY1x0267AKxVW8JVWx JwA2z4x0Y4vEx4A2jsIE14v26r4j6F4UM28EF7xvwVC2z280aVCY1x0267AKxVW8JVW8Jr 1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG6c804VAFz4xC04v7Mc02F40ExcI2r2IE 04Ijxs4lYx0E2Ix0cI8IcVAFwI0_Jr0_Jr4lYx0Ex4A2jsIE14v26r1j6r4UMcvjeVCFs4 IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCjr7xvwVCIw2I0I7xG6c02F41l42xK82IYc2Ij 64vIr41lx2IqxVAqx4xG67AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1V AY17CE14v26r1q6r43MIIYrxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAI cVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMI IF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2 KfnxnUUI43ZEXa7xUUeRBUUUUUU==
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/unnkBWgMUXFRZLAIIUG-yl-_fM0>
Cc: ipv6@ietf.org, ietf@ietf.org, 6man-chairs@ietf.org, draft-ietf-6man-rfc4291bis@ietf.org, lorenzo@google.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 00:07:58 -0000

This is a multi-part message in MIME format.
--------------080806070809030000050205
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

sthaug@nethelp.no ??:
>> But they do reflect reality. If you look at the whole Internet, think there
>> are probably 1000 /64 links for every /65-126 link deployed today.
>>     
>
> 1000 /64 links for every /65-126 link may well be the case. However,
> plenty of non /64 links exist, and I see no sign of them going
> away. Claiming that all IIDs are 64 bit is simply incorrect, and
> doesn't reflect operational reality no matter how hard you try to
> make that claim.
>
> At least the ISP I work for will make sure (through RFP requirements
> etc) that /65-126 links *continue to work*.
>   

+1, xing

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


--------------080806070809030000050205
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<a class="moz-txt-link-abbreviated" href="mailto:sthaug@nethelp.no">sthaug@nethelp.no</a> &#20889;&#36947;:
<blockquote cite="mid:20170223.094711.41666643.sthaug@nethelp.no"
 type="cite">
  <blockquote type="cite">
    <pre wrap="">But they do reflect reality. If you look at the whole Internet, think there
are probably 1000 /64 links for every /65-126 link deployed today.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
1000 /64 links for every /65-126 link may well be the case. However,
plenty of non /64 links exist, and I see no sign of them going
away. Claiming that all IIDs are 64 bit is simply incorrect, and
doesn't reflect operational reality no matter how hard you try to
make that claim.

At least the ISP I work for will make sure (through RFP requirements
etc) that /65-126 links *continue to work*.
  </pre>
</blockquote>
<br>
+1, xing<br>
<br>
<blockquote cite="mid:20170223.094711.41666643.sthaug@nethelp.no"
 type="cite">
  <pre wrap="">
Steinar Haug, AS2116

--------------------------------------------------------------------
IETF IPv6 working group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>
Administrative Requests: <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a>
--------------------------------------------------------------------

  </pre>
</blockquote>
<br>
</body>
</html>

--------------080806070809030000050205--


From nobody Sat Feb 25 16:14:53 2017
Return-Path: <xing@cernet.edu.cn>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AE1129541; Sat, 25 Feb 2017 16:14:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 5oy4uL6PEg4Z; Sat, 25 Feb 2017 16:14:50 -0800 (PST)
Received: from tsinghua.edu.cn (smtp36.tsinghua.edu.cn [166.111.204.60]) by ietfa.amsl.com (Postfix) with ESMTP id DB0BE129488; Sat, 25 Feb 2017 16:14:49 -0800 (PST)
Received: from [192.168.1.100] (unknown [114.254.44.112]) by app3 (Coremail) with SMTP id DMxvpgCXn4fdHbJYIgLqAQ--.5942S2; Sun, 26 Feb 2017 08:14:21 +0800 (CST)
Message-ID: <58B21DDD.7070201@cernet.edu.cn>
Date: Sun, 26 Feb 2017 08:14:21 +0800
From: Xing Li <xing@cernet.edu.cn>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
References: <148599306190.18700.14784486605754128729.idtracker@ietfa.amsl.com> <CAN-Dau0kDiSNXsyq9-xEdS5mzLt-K+MYHqoV8aC8jDVREw8OPQ@mail.gmail.com> <8e5c950a-0957-4323-670f-f3d07f40b4df@gmail.com> <05FD5283-9A15-4819-8362-5E6B2416D617@employees.org> <CAKD1Yr3B+dw83B0+26oUqdVJE==wHUBwoWzfWBJep8f+=uM8xQ@mail.gmail.com> <d9dc153a-61a8-5976-7697-ce1ecc9c8f3f@gmail.com> <4AF83EE6-6109-491F-BE66-114724BB197B@employees.org> <m2y3x6eutl.wl-randy@psg.com> <B76B6864-5827-4AC1-9BF7-8FFF069C10F1@employees.org> <m2lgt6ed7j.wl-randy@psg.com> <4514E052-25C1-4C85-AB1D-0B53FD9DA0E1@employees.org> <CAN-Dau3VriYNUf96yZEFMMV+-4WCxBz94Lkqfg3OsCUAbVYhaw@mail.gmail.com> <660929B4-158B-453F-9B5F-6C029F9699FA@employees.org> <E093E86F-41F5-4485-A8D3-761831F9AAF8@google.com> <ECF27195-4A6B-4AFC-8950-83876F333BD4@employees.org> <A1F60D51-C39E-45DC-B3D5-960D92C186E4@darou.fr>
In-Reply-To: <A1F60D51-C39E-45DC-B3D5-960D92C186E4@darou.fr>
Content-Type: multipart/alternative; boundary="------------010505070608010702010302"
X-CM-TRANSID: DMxvpgCXn4fdHbJYIgLqAQ--.5942S2
X-Coremail-Antispam: 1UD129KBjvJXoW7Ww13tFW5AF1xXF47urWUXFb_yoW8Zw48pa 13tr47ZF4DJF18Ars7G3y8ur15A3ykGw45W3Wrtry8Jr1qkF18Gr1qkr18ZayxJr97JF17 XrW8KryfGF1kZ3DanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUqGb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r4j6ryUM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_Jr0_JF4l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVW8JVWxJwA2z4x0Y4vEx4A2jsIEc7CjxVAFwI0_Gr0_Gr 1UM2AIxVAIcxkEcVAq07x20xvEncxIr21l5I8CrVAqjxCE14ACF2xKxwAv7VC0I7IYx2IY 67AKxVWUXVWUAwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y4 8IcVAKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCF04k20xvY0x0EwIxGrwC20s026c02F40E 14v26r106r1rMI8I3I0E7480Y4vE14v26r106r1rMI8E67AF67kF1VAFwI0_JF0_Jw1lIx kGc2Ij64vIr41lIxAIcVC0I7IYx2IY67AKxVWUJVWUCwCI42IY6xIIjxv20xvEc7CjxVAF wI0_Gr0_Cr1lIxAIcVCF04k26cxKx2IYs7xG6rWUJVWrZr1UMIIF0xvEx4A2jsIE14v26r 1j6r4UMIIF0xvEx4A2jsIEc7CjxVAFwI0_Gr0_Gr1UYxBIdaVFxhVjvjDU0xZFpf9x0UUj RaDUUUUU=
X-CM-SenderInfo: p0lqwqxfhu0vvwohv3gofq/
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IwT-yEDuDgNAPq_4qWXAktrIySk>
Cc: james woodyatt <jhw@google.com>, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 00:14:52 -0000

This is a multi-part message in MIME format.
--------------010505070608010702010302
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Pierre Pfister ??:
> Hello all,
>
>   
>> Proposal:
>>  IPv6 unicast routing is based on prefixes of any valid length up to
>> 128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
>>  of unicast addresses is generally required to be 64 bits in length, with
>>  exceptions only provided in special cases where expressly recognised
>>  in IETF standards track documents.
>>
>>     
>
> The only place in IPv6 standards where the 64 boundary is mandated is on the 2000::/3 rule.
> There is not a single implementation or deployment of that rule. There is no instance where 
> trying to configure a prefix of length different than 64 will work when the prefix is within 2000::/3, and fail when it is not.
> That is a sufficient reason to not include this rule as part of the standard track.
>
> Nevertheless, SLAAC over Ethernet links indeed requires prefix length of 64.
> As documented in the RFC7421, there are a few examples of protocols which require 64 bits long interface identifiers.
>
> SLAAC is not the only way to configure IPv6 hosts though.
> Manual configuration, automated configuration, and DHCP are all IETF approved ways of configuring IPv6 hosts. 
> They all work with prefixes of various lengths. 
> Does 'special cases' in the proposed text covers manual/automated configuration or DHCP ? If so, it is far from being clear.
>
> You obviously should use /64s if you want SLAAC to work, as well as other protocols which are documented in RFC7421,
> but /64 is not the rule, it is an architectural consideration that you have to take into account when you design your network depending on the protocols that you want to run there.
>
> Therefore, as far as this discussion is concerned, there is no reason to mandate 64 bits boundaries as part of the IPv6 specification.
>   

+1, xing

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


--------------010505070608010702010302
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Pierre Pfister &#20889;&#36947;:
<blockquote cite="mid:A1F60D51-C39E-45DC-B3D5-960D92C186E4@darou.fr"
 type="cite">
  <pre wrap="">Hello all,

  </pre>
  <blockquote type="cite">
    <pre wrap="">Proposal:
 IPv6 unicast routing is based on prefixes of any valid length up to
128 bits [BCP198]. However, as explained in [RFC7421], the Interface ID
 of unicast addresses is generally required to be 64 bits in length, with
 exceptions only provided in special cases where expressly recognised
 in IETF standards track documents.

    </pre>
  </blockquote>
  <pre wrap=""><!---->
The only place in IPv6 standards where the 64 boundary is mandated is on the 2000::/3 rule.
There is not a single implementation or deployment of that rule. There is no instance where 
trying to configure a prefix of length different than 64 will work when the prefix is within 2000::/3, and fail when it is not.
That is a sufficient reason to not include this rule as part of the standard track.

Nevertheless, SLAAC over Ethernet links indeed requires prefix length of 64.
As documented in the RFC7421, there are a few examples of protocols which require 64 bits long interface identifiers.

SLAAC is not the only way to configure IPv6 hosts though.
Manual configuration, automated configuration, and DHCP are all IETF approved ways of configuring IPv6 hosts. 
They all work with prefixes of various lengths. 
Does 'special cases' in the proposed text covers manual/automated configuration or DHCP ? If so, it is far from being clear.

You obviously should use /64s if you want SLAAC to work, as well as other protocols which are documented in RFC7421,
but /64 is not the rule, it is an architectural consideration that you have to take into account when you design your network depending on the protocols that you want to run there.

Therefore, as far as this discussion is concerned, there is no reason to mandate 64 bits boundaries as part of the IPv6 specification.
  </pre>
</blockquote>
<br>
+1, xing<br>
<br>
<blockquote cite="mid:A1F60D51-C39E-45DC-B3D5-960D92C186E4@darou.fr"
 type="cite">
  <pre wrap="">
- Pierre
--------------------------------------------------------------------
IETF IPv6 working group mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ipv6@ietf.org">ipv6@ietf.org</a>
Administrative Requests: <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/ipv6">https://www.ietf.org/mailman/listinfo/ipv6</a>
--------------------------------------------------------------------

  </pre>
</blockquote>
<br>
</body>
</html>

--------------010505070608010702010302--


From nobody Sat Feb 25 16:58:02 2017
Return-Path: <chopps@chopps.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1D941295AC; Sat, 25 Feb 2017 16:58:00 -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 autolearn_force=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 EGOUeaQUNaAB; Sat, 25 Feb 2017 16:57:59 -0800 (PST)
Received: from smtp.chopps.org (smtp.chopps.org [54.88.81.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2986F12959B; Sat, 25 Feb 2017 16:57:59 -0800 (PST)
Received: from tops.chopps.org (97-83-46-222.dhcp.trcy.mi.charter.com [97.83.46.222]) (using TLSv1.2 with cipher AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by smtp.chopps.org (Postfix) with ESMTPSA id 48E75617DA; Sun, 26 Feb 2017 00:57:58 +0000 (UTC)
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com>
User-agent: mu4e 0.9.19; emacs 25.1.1
From: Christian Hopps <chopps@chopps.org>
To: ietf@ietf.org, IETF Agenda <agenda@ietf.org>
Subject: Re: IETF 98 Preliminary Agenda
In-reply-to: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com>
Date: Sat, 25 Feb 2017 19:57:56 -0500
Message-ID: <87wpcd4vl7.fsf@chopps.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sMTyW3eC4qI39YwxkEltTqR4uoI>
Cc: Hannes Gredler <hannes@gredler.at>, Routing ADs <rtg-ads@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 00:58:01 -0000

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


Hello agenda folks,

Would it be possible to move isis-wg to Wednesday during the 13:00-15:00
slot? That slot appears to have room and we do not have any conflict
there.

Thanks,
Chris.

IETF Agenda <agenda@ietf.org> writes:

> The IETF 98 Preliminary Agenda has been posted. The final agenda will be published on Friday, March 3, 2017.
>
> https://datatracker.ietf.org/meeting/98/agenda.html
> https://datatracker.ietf.org/meeting/98/agenda.txt
>
>
> More information regarding IETF 98 in Chicago is located here: https://www.ietf.org/meeting/98/index.html
>
> Thank you!
>
> IETF Secretariat

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

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

iQIzBAEBCgAdFiEEm56yH/NF+m1FHa6lLh2DDte4MCUFAliyKBQACgkQLh2DDte4
MCX6oA//ZGBYT7HHDKoEDXB3vIpoHZAz0Xxf/WTD0xUD1C29hcnIatLHZJUPllqp
7lV9IXiF3jAKwn1QAL/xGPaCaSJoKwnMXrBQI+8dFVIeAOB2uCuMzB/q7+IRzt7m
ZkgR7HFV3Clm5ciu+oFbs0CRXf9OX1GEPkeEVntGpIwYtz0hsnRZGqo50hJIW0aZ
PQxaNXjYjiTSgQ93dRt9dqcWbm0xZLt7WU+0tsIbMRovyFLLA6IKZzlnVKHjgGCR
5UmBFsNWA37JkEfkapWJDRN0IHxRTmx+w5UQuWgYgJLTTwBGtoBPyKwL8+xMgZuq
fQEzpwKo1SaNrhsXM54MRq16guJNMgZBlBOFe/2FwCHGera0kwKj4HydA+0Bi1MU
omaEMYBJYMU7quRhhBf4Bw2b7ANSlfukxt4MDUoZyBuaU5vTlXatG7WWVxUkRnDN
Jx562Lrd4EgO/WqNut3O+DBaS1lAQeLSO4hdwFec4FPOb/QwVGgcdyKZ7toF7cm0
umBlVrk0/LdnOfI7VSdRVRuGMN+JuVXnhv+W1pCT4ptm3KA9sIZH/CMFsxgzq7Ss
ZvD67Olu8f7RSoNlVfbZ+XMXYOkTNgrDXFTV3wfektN/++TNVzRsfh+SREtatmcD
2o9ljAWOKIAyXnQfPzX3r2kyRH0tmkycteXfCBaH9kjFuvDe3Gk=
=LJh1
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Feb 25 20:33:15 2017
Return-Path: <barryleiba.mailing.lists@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 132F6129891; Sat, 25 Feb 2017 20:33:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zn1t5J7yyVt8; Sat, 25 Feb 2017 20:33:13 -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 D4DE3129890; Sat, 25 Feb 2017 20:33:12 -0800 (PST)
Received: by mail-io0-x233.google.com with SMTP id l7so1784514ioe.3; Sat, 25 Feb 2017 20:33:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=O6V6xcKRe0vVMJyInV3ntFd+Vtthwlr6exJrC35vsTw=; b=ZW1fOnjoGlYx4bZi4BdCKpxqDvgh+e9MinVwZEsmGyUJkyblomkUaQ/VApUoZzj0D3 dSTTknC4CWZlq9b16AjanZDgWe8WogM7Twcl6lHAnc+YBmPBvnoL2cFLFLjSPVA5+T5S VTGB06swlcZXVD81JdlTuA528SckZsssFsA6txlImRWCrHHBGwdLMsY5+2DnruoZUVul iYKG3zaY1mBUrOF0x6PRLZaK70aCh8ITEzMAXv+E/CKknkB+iTACIXT6j0uL1i1RlRkU GgBAITnbW1Pl1lUurVyT/u16AA3Dl7Zz6cogT83PlA68HiziznXoEfqAoqriGPVY1uTL ZRWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=O6V6xcKRe0vVMJyInV3ntFd+Vtthwlr6exJrC35vsTw=; b=LFGEyNb1JCTd/gXigTIkgM0MgXmvsnBCeI/4PORi2ctRULKLwlP+j5x+Ms3aDiN5ml tY3alqRypP4Ns4kJeCpsBXghuyR78gLtBFH96cCVtOdKBwLezcwdhMYDFPyj/ZvmL3PG HU0qOZEpBEJ//15Yba/Rqlo6cRCZgVqRjpNFiOgAk7W50DXagt39bNp7kPw/dpt62owA 3wd84ISGz1cGPs2OE08LERxJe2V8H4ZkvIDO3hlYWOIhr/aHoAyKZpVbGKHEEhLbmqux t3FucLWf01r8nqByYG+bc77qg8JBR1NpFdFQjLNKHoX6NS2AOZXzPojdjFEzSE6lSjoW OVNw==
X-Gm-Message-State: AMke39klLFH5QsRZ7auJegQLNEX+3NhkwGdUvNkquZTdOGN/OmvhOmPx1OguNM7t9tXbTmc0xBGHTqHkhL/abw==
X-Received: by 10.107.187.133 with SMTP id l127mr9115207iof.1.1488083592192; Sat, 25 Feb 2017 20:33:12 -0800 (PST)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.107.55.134 with HTTP; Sat, 25 Feb 2017 20:33:11 -0800 (PST)
In-Reply-To: <87wpcd4vl7.fsf@chopps.org>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <87wpcd4vl7.fsf@chopps.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Sat, 25 Feb 2017 20:33:11 -0800
X-Google-Sender-Auth: ZQ4qN-N3nyZ8StwL-rKpBzzR05A
Message-ID: <CAC4RtVDLbYAqrjgLO4GY=W1JMXj9WSZNejtaAtbd0fKprkBRxg@mail.gmail.com>
Subject: Re: IETF 98 Preliminary Agenda
To: Christian Hopps <chopps@chopps.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xfwjg9eDB8QLzcW03mdbQCiKh2g>
Cc: Hannes Gredler <hannes@gredler.at>, IETF Agenda <agenda@ietf.org>, IETF discussion list <ietf@ietf.org>, Routing ADs <rtg-ads@tools.ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 04:33:14 -0000

> Would it be possible to move isis-wg to Wednesday during the 13:00-15:00
> slot? That slot appears to have room and we do not have any conflict
> there.

But the slot does not have room: Zurich D, E, F, and G will be under
reconfiguration for the plenary.

Barry


From nobody Sat Feb 25 23:01:16 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B8212989D; Sat, 25 Feb 2017 23:01:15 -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 autolearn_force=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 kJp7d9ot9M-v; Sat, 25 Feb 2017 23:01: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 31502129630; Sat, 25 Feb 2017 23:01:13 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 BC5FA809EA; Sun, 26 Feb 2017 08:01:07 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <b81b4558-48d5-f8df-1a4d-6f4708b1bdfa@si6networks.com>
Date: Sun, 26 Feb 2017 03:42:08 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zW2Bh413vVJWgMGSZDOHwM9BZ2I>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, ipv6@ietf.org, "secdir@ietf.org" <secdir@ietf.org>, =?UTF-8?Q?Iv=c3=a1n_Arce?= <iarce@fundacionsadosky.org.ar>, "sec-ads@ietf.org" <sec-ads@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 07:01:15 -0000

Folks,

Page 15 of the document says:

    For every packet that is to be fragmented, the source node generates
    an Identification value.  The Identification must be different than
    that of any other fragmented packet sent recently* with the same
    Source Address and Destination Address.  If a Routing header is
    present, the Destination Address of concern is that of the final
    destination.



      *  "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.  Examples of
          algorithms that can meet this requirement are described in
          [RFC7739].


This is certainly an improvement over RFC2460, which suggested the use
of a simple counter to achieve this requirement. While the algorithms in
RFC7739 are meant to result in non-predictable (by off-path attackers)
Identification values, I believe that this spec should clarify that
Identification values should not be predictable by off-path attackers.

The survey in Appendix B of RFC7739
(<https://tools.ietf.org/html/rfc7739#appendix-B>) shows some sample
popular implementations that, unfortunately, still employ predictable
Identification values.

Given too-frequent pattern of protocol implementations employing
improper numeric-identifier generators (see
<https://tools.ietf.org/html/draft-gont-predictable-numeric-ids>) and
<https://tools.ietf.org/html/draft-gont-numeric-ids-history>), I think
an explicit requirement is warranted.

Thanks,
Fernando




On 02/01/2017 08:49 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Internet Protocol, Version 6 (IPv6) Specification'
>   <draft-ietf-6man-rfc2460bis-08.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies version 6 of the Internet Protocol (IPv6).
>    It obsoletes RFC2460
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information: 
>     rfc4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard - IETF stream)
>     rfc3168: The Addition of Explicit Congestion Notification (ECN) to IP (Proposed Standard - IETF stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
> 
> 
> --------------------------------------------------------------------
> 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 Sun Feb 26 01:49:13 2017
Return-Path: <roni.even@mail01.huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D548129464; Sun, 26 Feb 2017 01:49:03 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <roni.even@mail01.huawei.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-pce-inter-layer-ext-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148810254318.12511.13035845809455980126.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 01:49:03 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/M4ywwkkT2HyCpoiSViaLiz95Rag>
Cc: draft-ietf-pce-inter-layer-ext.all@ietf.org, pce@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 09:49:03 -0000

Reviewer: Roni Even
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-pce-inter-layer-ext-12
Reviewer: Roni Even
Review Date: 2017-02-26
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-03-16

Summary: This draft is  ready for publication as a standard track
RFC.

Major issues:

Minor issues:

Nits/editorial comments: 

In section 2 "Those TE links exist at the layer/region boarder
normally" should be "border"




From nobody Sun Feb 26 04:40:43 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D39129881; Sun, 26 Feb 2017 04:40:42 -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 autolearn_force=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 zXq8EH0F_XQD; Sun, 26 Feb 2017 04:40:40 -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 3BEC9129528; Sun, 26 Feb 2017 04:40:39 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 9D98E80F6A; Sun, 26 Feb 2017 13:40:33 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com>
Date: Sun, 26 Feb 2017 04:30:02 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vowRij98FOX3Vhok_5cLOLSsKtU>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 12:40:42 -0000

Folks,

Page 9 of the document says:

2.3.  Address Type Identification

   The type of an IPv6 address is identified by the high-order bits of
   the address, as follows:

      Address type         Binary prefix        IPv6 notation   Section
      ------------         -------------        -------------   -------
      Unspecified          00...0  (128 bits)   ::/128          2.4.2
      Loopback             00...1  (128 bits)   ::1/128         2.4.3
      Multicast            11111111             ff00::/8        2.6
      Link-Local unicast   1111111010           fe80::/10       2.4.6
      Global Unicast       (everything else)


I wonder if this table should explicitly call out ULAs, and provide a
reference to the corresponding section.

(Question came up while looking at a slide I use in an IPv6 course I
teach, in which I use a modified version of this table, which calls out
ULAs).

Thanks,
Fernando




On 02/01/2017 08:49 PM, The IESG wrote:
> 
> The IESG has received a request from the IPv6 Maintenance WG (6man) to
> consider the following document:
> - 'Internet Protocol, Version 6 (IPv6) Specification'
>   <draft-ietf-6man-rfc2460bis-08.txt> as Internet Standard
> 
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> 
> Abstract
> 
> 
>    This document specifies version 6 of the Internet Protocol (IPv6).
>    It obsoletes RFC2460
> 
> 
> 
> 
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/
> 
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/ballot/
> 
> 
> No IPR declarations have been submitted directly on this I-D.
> 
> 
> The document contains these normative downward references.
> See RFC 3967 for additional information: 
>     rfc4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification (Draft Standard - IETF stream)
>     rfc3168: The Addition of Explicit Congestion Notification (ECN) to IP (Proposed Standard - IETF stream)
> Note that some of these references may already be listed in the acceptable Downref Registry.
> 
> 
> --------------------------------------------------------------------
> 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 Sun Feb 26 04:56:19 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FF431298BC; Sun, 26 Feb 2017 04:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level: 
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5JxFUkSg6oTL; Sun, 26 Feb 2017 04:56:11 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [83.247.10.6]) (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 B5D2B1298B9; Sun, 26 Feb 2017 04:56:10 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 6DB194A; Sun, 26 Feb 2017 13:56:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :subject:subject:mime-version:content-type:content-type:received :received; s=mail; t=1488113766; bh=FbxCZEydciCfn1Eg/MCqKRzrwxAx Zlgh9/BvMtembtg=; b=SR02Rj85ZRHi4w0Vdy7NlYLWB1CDd5Py8vz2WJi8IpVt wfSjxDtklTMeWrhIw++nR2SyEG2CPaK2LT8PKWWmStXNfxGAhFH8khSziu8DS3S7 OyfXlrLsjE7Xxd+F+VUwFl54pSacy1XnzzbS4G/QAAMbwkgzIFp8677ltieDX6E=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id V0LYWXaQuySR; Sun, 26 Feb 2017 13:56:06 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:9300:1185:211f:5b63:5677] (unknown [IPv6:2a02:a213:a300:9300:1185:211f:5b63:5677]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id AC12649; Sun, 26 Feb 2017 13:56:05 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_4E787FBE-D0AE-4CEB-B20E-2163B515E48D"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com>
Date: Sun, 26 Feb 2017 13:55:59 +0100
Message-Id: <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9P0U7UOrbeQNLFG_-U01_JuBS2U>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, ipv6@ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 12:56:12 -0000

--Apple-Mail=_4E787FBE-D0AE-4CEB-B20E-2163B515E48D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

> 2.3.  Address Type Identification
>=20
>   The type of an IPv6 address is identified by the high-order bits of
>   the address, as follows:
>=20
>      Address type         Binary prefix        IPv6 notation   Section
>      ------------         -------------        -------------   -------
>      Unspecified          00...0  (128 bits)   ::/128          2.4.2
>      Loopback             00...1  (128 bits)   ::1/128         2.4.3
>      Multicast            11111111             ff00::/8        2.6
>      Link-Local unicast   1111111010           fe80::/10       2.4.6
>      Global Unicast       (everything else)
>=20
>=20
> I wonder if this table should explicitly call out ULAs, and provide a
> reference to the corresponding section.

ULAs are not an address type, they are Global Unicast. Adding them here =
might confuse people. And if we include ULAs then there is lots more =
that we should include as well. So while I understand your question, I =
think it would be better not to.

Cheers,
Sander


--Apple-Mail=_4E787FBE-D0AE-4CEB-B20E-2163B515E48D
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-----

iQEcBAEBCAAGBQJYstBfAAoJEKAtA7D+JBO58+AIAJd20PTR+4Wal/b08WD83E6X
0kwO4g5KhXD7kbs0Oa48CgV7JMwNpm0ZWnJwL+QIl7CVOzSYzi+G98zNfLGxqEVu
eyWw4dmQBzSCjPjXZ6DWOoeHXUdWOGFo9es4zeySqiNfFG7Eyh8KtSstneKWtiak
CZNyTLMw6bLg+XoySEKSrRo+qsb44ePuaChee9iYtLX1UdNuvhfK2p/ws4QTb7Sg
FuPjP88OOZuEmRyXdO/m0QUMSHZQWfaj2UxjnPN0LqsuiNoUGQ0ZUqwWKTL5KXVt
PKZXyag2nbZLicbVfycGXU6dF6C6XTS3eZ5/vSvtk6hzpSBamw6HGhO4pjgO+tU=
=6joG
-----END PGP SIGNATURE-----

--Apple-Mail=_4E787FBE-D0AE-4CEB-B20E-2163B515E48D--


From nobody Sun Feb 26 05:15:59 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1479D1298C7; Sun, 26 Feb 2017 05:15:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001] autolearn=ham autolearn_force=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 L2iLdAj5o7VQ; Sun, 26 Feb 2017 05:15:56 -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 51BCE1298C4; Sun, 26 Feb 2017 05:15:55 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 5C51E805E5; Sun, 26 Feb 2017 14:15:50 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Sander Steffann <sander@steffann.nl>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
Date: Sun, 26 Feb 2017 10:05:59 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fcsarnCCDRKfktxRsUXtIw-a6Aw>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, ipv6@ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 13:15:58 -0000

On 02/26/2017 09:55 AM, Sander Steffann wrote:
> Hi,
> 
>> 2.3.  Address Type Identification
>>
>>   The type of an IPv6 address is identified by the high-order bits of
>>   the address, as follows:
>>
>>      Address type         Binary prefix        IPv6 notation   Section
>>      ------------         -------------        -------------   -------
>>      Unspecified          00...0  (128 bits)   ::/128          2.4.2
>>      Loopback             00...1  (128 bits)   ::1/128         2.4.3
>>      Multicast            11111111             ff00::/8        2.6
>>      Link-Local unicast   1111111010           fe80::/10       2.4.6
>>      Global Unicast       (everything else)
>>
>>
>> I wonder if this table should explicitly call out ULAs, and provide a
>> reference to the corresponding section.
> 
> ULAs are not an address type, they are Global Unicast. Adding them here might confuse people. And if we include ULAs then there is lots more that we should include as well. So while I understand your question, I think it would be better not to.

The "confusing" part is that, while globally unique, their scope is not
really global -- i.e., they are not meant to be globally routable.

Wasn't there at some point an I-D aiming to clarify what "global" meant?
-- IIRC, authored by Brian et al.

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





From nobody Sun Feb 26 05:24:44 2017
Return-Path: <sander@steffann.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27B721298A6; Sun, 26 Feb 2017 05:24:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=steffann.nl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEJ4rMcw8-sY; Sun, 26 Feb 2017 05:24:41 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (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 A0E8F1297C6; Sun, 26 Feb 2017 05:24:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 5397A4A; Sun, 26 Feb 2017 14:24:39 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:date:date:in-reply-to:from:from :subject:subject:mime-version:content-type:content-type:received :received; s=mail; t=1488115476; bh=Ta7z8J1Vrp2oJ1lJlScM2UFJL4wa IP83Cj9fHmvdiV0=; b=pggjwRX+Nr49tFlppdUSl3ea1Pn3fBD5lNYad67eIg0c 5CcBPFX0WVZCbefGolI8Dj3bUp3/zBi3KjJk/GuhyrMqb1eK9ZyaE3J7mEICHY/H JS/LJO+FJlpqghQCp7peWAx0uf7QjAoO+w2QbL/zG3Bk65VeHd/W2b0TIpDeh8E=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GDTSkzhrSuZm; Sun, 26 Feb 2017 14:24:36 +0100 (CET)
Received: from [IPv6:2a02:a213:a300:9300:1185:211f:5b63:5677] (unknown [IPv6:2a02:a213:a300:9300:1185:211f:5b63:5677]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.sintact.nl (Postfix) with ESMTPSA id D02EE49; Sun, 26 Feb 2017 14:24:35 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_47669190-2FD0-4B0B-B635-FBACDCB6232E"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol,  Version 6 (IPv6) Specification) to Internet Standard
X-Clacks-Overhead: GNU Terry Pratchett
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
Date: Sun, 26 Feb 2017 14:24:35 +0100
Message-Id: <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-OHEeINMKtVaIcWm17J66Ja532k>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, 6man WG <ipv6@ietf.org>, ietf <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 13:24:43 -0000

--Apple-Mail=_47669190-2FD0-4B0B-B635-FBACDCB6232E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


> Op 26 feb. 2017, om 14:05 heeft Fernando Gont <fgont@si6networks.com> =
het volgende geschreven:
>=20
> On 02/26/2017 09:55 AM, Sander Steffann wrote:
>> Hi,
>>=20
>>> 2.3.  Address Type Identification
>>>=20
>>>  The type of an IPv6 address is identified by the high-order bits of
>>>  the address, as follows:
>>>=20
>>>     Address type         Binary prefix        IPv6 notation   =
Section
>>>     ------------         -------------        -------------   =
-------
>>>     Unspecified          00...0  (128 bits)   ::/128          2.4.2
>>>     Loopback             00...1  (128 bits)   ::1/128         2.4.3
>>>     Multicast            11111111             ff00::/8        2.6
>>>     Link-Local unicast   1111111010           fe80::/10       2.4.6
>>>     Global Unicast       (everything else)
>>>=20
>>>=20
>>> I wonder if this table should explicitly call out ULAs, and provide =
a
>>> reference to the corresponding section.
>>=20
>> ULAs are not an address type, they are Global Unicast. Adding them =
here might confuse people. And if we include ULAs then there is lots =
more that we should include as well. So while I understand your =
question, I think it would be better not to.
>=20
> The "confusing" part is that, while globally unique, their scope is =
not
> really global -- i.e., they are not meant to be globally routable.

Indeed, globally unique vs globally routable. But if you go into this =
then it's more complicated than it seems. Whether something is routable =
and where are an operational choice. Companies choosing to interconnect =
might route each other's ULA space, while some of my RIPE NCC allocated =
space is not routed anywhere public. It's difficult to give a fixed =
definition that doesn't take operational stuff into account.

Of course the intention of how to use ULA should be mentioned somewhere, =
but probably not in this table.

> Wasn't there at some point an I-D aiming to clarify what "global" =
meant?
> -- IIRC, authored by Brian et al.

Sorry, I don't remember.

Cheers,
Sander


--Apple-Mail=_47669190-2FD0-4B0B-B635-FBACDCB6232E
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-----

iQEcBAEBCAAGBQJYstcTAAoJEKAtA7D+JBO5vr0H/RzNZpJqWtwf2/2aqqwwaLZO
EM33eW0Wxbd0AvHVjhyr6mvsCHaojy4VGiR73rEBCBps4Xo9C7uUWZfmG+AJ5q3W
Z0/o8/31q9VzSB7UtlhwDo7lMfECaJKC4HSyKlitLTA5cSOnK/ArhqQ1BlctD9Qr
J4N2lLt63Igda95lRNry5mg13cKfc8T/5cydAK8JrOBdrbUpXu/LGQBs/j+laDKq
7I6LmPHjRAEx3jVMZpRLM2ZibdepefrMad75t9n6qC3K8hZY+/yKn3KuFS67Hr1M
+rS19orff1LelGoXgdtglvqMPct4fBwZHDETN+mli5eXB8QVUV7SLRn1Ag4CecM=
=+Q5P
-----END PGP SIGNATURE-----

--Apple-Mail=_47669190-2FD0-4B0B-B635-FBACDCB6232E--


From nobody Sun Feb 26 06:04:28 2017
Return-Path: <fgont@si6networks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D55CD1298C7; Sun, 26 Feb 2017 06:04:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 lCoiEo7dyAXh; Sun, 26 Feb 2017 06:04:21 -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 BA9BB1298BB; Sun, 26 Feb 2017 06:04:21 -0800 (PST)
Received: from [192.168.3.83] (unknown [181.165.116.69]) (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 394ED8026B; Sun, 26 Feb 2017 15:04:16 +0100 (CET)
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Sander Steffann <sander@steffann.nl>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com> <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
From: Fernando Gont <fgont@si6networks.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <6a49aae9-8971-3ae6-c14f-d18c140aa654@si6networks.com>
Date: Sun, 26 Feb 2017 11:03:54 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JPPJJK7MR4vHn_Uv7hyHteEfNhY>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, 6man WG <ipv6@ietf.org>, ietf <ietf@ietf.org>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 14:04:23 -0000

On 02/26/2017 10:24 AM, Sander Steffann wrote:
>>>> 2.3.  Address Type Identification
>>>> 
>>>> The type of an IPv6 address is identified by the high-order
>>>> bits of the address, as follows:
>>>> 
>>>> Address type         Binary prefix        IPv6 notation
>>>> Section ------------         -------------        -------------
>>>> ------- Unspecified          00...0  (128 bits)   ::/128
>>>> 2.4.2 Loopback             00...1  (128 bits)   ::1/128
>>>> 2.4.3 Multicast            11111111             ff00::/8
>>>> 2.6 Link-Local unicast   1111111010           fe80::/10
>>>> 2.4.6 Global Unicast       (everything else)
>>>> 
>>>> 
>>>> I wonder if this table should explicitly call out ULAs, and
>>>> provide a reference to the corresponding section.
>>> 
>>> ULAs are not an address type, they are Global Unicast. Adding
>>> them here might confuse people. And if we include ULAs then there
>>> is lots more that we should include as well. So while I
>>> understand your question, I think it would be better not to.
>> 
>> The "confusing" part is that, while globally unique, their scope is
>> not really global -- i.e., they are not meant to be globally
>> routable.
> 
> Indeed, globally unique vs globally routable. But if you go into this
> then it's more complicated than it seems. Whether something is
> routable and where are an operational choice. Companies choosing to
> interconnect might route each other's ULA space, while some of my
> RIPE NCC allocated space is not routed anywhere public. It's
> difficult to give a fixed definition that doesn't take operational
> stuff into account.

According to the definition of global scope in RFC4291, ULAs are not
really global. If they were, an ULA address should be able to uniquely
identify an interface in the whole (global) network. If anything, this
only happens "statistically".

In practice, sine 2001:db8::/16 is not routable, if your teaching a
course you'll probably use ULAs for a virtual lab. And since you copy
the same VMs to all attendees, they all end up using the same ULA
addresses. Hence their scope (within which an interface is uniquely
identified) will certainly not be global (multiple different interfaces
employ the same address at the same timeframe). :-)

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





From nobody Sun Feb 26 06:10:55 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DDBFC129960; Sun, 26 Feb 2017 06:10:47 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Dale Worley <worley@ariadne.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-dane-smime-15
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 06:10:47 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p0BSikThJjfRRip485wAAbbyEB4>
Cc: draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 14:10:48 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document:  draft-ietf-dane-smime-15
Reviewer:  Dale R. Worley
Review Date:  2017-02-26
IETF LC End Date:  2017-03-03
IESG Telechat date: 2017-03-16

Summary:  This draft is basically ready for publication, but has nits
that should be fixed before publication.

* Technical points

1. I assume that in parallel with RFC 6698, DNAME records must be
followed during SMIMEA resolution.  It's not clear to me whether
CNAME
records must also be followed or how, given that SNAMEA records are
not for host names, but their grandparent node is a host name.

2. Presumably it was deliberate not to have the first label for an
SNAMEA record be the canonical UTF-8 string for the local-part, even
though the DNS architecture (RFC 1035) seems to admit binary labels.

3. Presumably it was deliberate to hash using SHA2-256 truncated to
224
bits rather than use SHA-224.

4. Is it worth suggesting that some mechanism might be devised for
annotating an e-mail message with the canonical form of the sender's
local-part that is intended to be used to authenticate the message?
The last sentence of the 1st paragraph of section 1 suggests that
this
is deliberately out of scope for this document, but it might be worth
suggesting experimentation regarding this in section 4, which seems
to
be entirely about further experimentation.

* Editorial/Nits

Should there be an explicit statement that the resolver must follow
CNAME and DNAME records?  That seems to be required by RFC 6698
section A.2.1, but that requirement is buried rather deeply.  Also,
is
CNAME following required?  My vague understanding is that CNAME can
only be used to alias host names, and SMIMEA records are not for host
names (contrasting with the DANE records for TLS) -- though the
grandparent node of any SNAMEA is a host name.

Also, some adjustments of the resolution process of RFC 6698 re CNAME
records were made in RFC 7671, but this draft only mentions 7671 in
passing, in the introduction.  It seems that it should be noted that
7671 contains a lot of operational information about DANE.

1.  Introduction

   There are other requirements on the MUA, such as
   associating the identity in the certificate with that of the
message,
   that are out of scope for this document.

"that of the message" isn't quite right, as "that" is parallel to
"the
identity", and the message doesn't itself have an identity.  More
accurate would be "the purported sender of the message", as was used
in 3rd sentence of the paragraph.

2.  The SMIMEA Resource Record

   ... the semantics are also the same except
   where RFC 6698 talks about TLS at the target protocol for the
   certificate information.

s/TLS at/TLS as/

3.  Location of the SMIMEA Record

   The DNS does not allow the use of all characters that are
supported
   in the "local-part" of email addresses as defined in [RFC5322] and
   [RFC6530].

I don't have the full background on this.  My memory ends at RFC
1035:

    Although labels can contain any 8 bit values in octets that make
up a
    label, it is strongly recommended that labels follow the
preferred
    syntax described elsewhere in this memo, which is compatible with
    existing host naming conventions.

I suspect there is by now a defined way to have "UTF-8 labels". 
Given
that this draft doesn't use such a mechanism, there's probably a
discussion out there why just using a UTF-8 string as a label doesn't
work.  It would be helpful to put a reference to that discussion
here,
because the mechanism in the draft is doing a lot of work to avoid
the
seemingly obvious mechanism.

   2.  The local-part is first canonicalized using the following
rules.
       If the local-part is unquoted, any whitespace (CFWS) around
dots
       (".") is removed.  Any enclosing double quotes are removed. 
Any
       literal quoting is removed.

I think this could be more exactly expressed along the following
lines.  Given the costs of not having this implemented exactly the
same way in all implementations, it's probably worth the extra words.

   2.  The local-part is first canonicalized using the following
       rules.  If the local-part is unquoted, any whitespace (CFWS)
       around dots (".") is removed.  If the local-part is quoted,
the
       enclosing double quotes, contained FWS, and the initial
       backslashes of quoted-pairs are removed.  (The obsolete
       local-part format obs-local-part is canonicalized similarly:
       CFWS around dots is removed and any word component that is a
       quoted-string is canonicalized as if it was a separate
       local-part.)

--

   4.  The local-part is hashed using the SHA2-256 [RFC5754]
algorithm,
       with the hash truncated to 28 octets and represented in its
       hexadecimal representation, to become the left-most label in
the
       prepared domain name.

Why use "SHA2-256 [RFC5754] algorithm, with the hash truncated to 28
octets" rather than "SHA2-224 [RFC5754]"?  (The two aren't the same,
because SHA-224 has a different IV than SHA2-256, but they seem to
have the same security properties.)  Is this because implementations
will already implement SHA2-256 (for matching type 1)?

You probably want to specify hexadecimal case here.  DNS is
considered
to be case-insensitive, but it's probably unwise to depend on that
fact.  (Or is this known not to be a problem in DNS?)

7.  Certificate Size and DNS

   The algorithm type and key
   size of certificates should not be modified to accommodate this
   section.

The term "algorithm type" is not defined; what is meant here?  Also,
"of certificates" seems awkward; the encryption/signing algorithms
and
keys exist prior to the certificate which vouches for them.  Perhaps:

   A user's S/MIME encryption/signing algorithms and keys should not
   be changed solely to reduce DNS RR sizes.

9.  Security Considerations

   If an obtained S/MIME certificate is revoked or expired, that
   certificate MUST NOT be used, even if that would result in sending
a
   message in plaintext.

Shouldn't this be moved to section 6?  This seems to be a
specification, but it is not contained in the definition of the
semantics.  The "security considerations" section is where you would
see the explanation of the reason for this specification.

[END]



From nobody Sun Feb 26 10:40:26 2017
Return-Path: <eng.khaled.omar@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D06126CD8 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 10:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.12
X-Spam-Level: 
X-Spam-Status: No, score=-0.12 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yQ8uiWQQkuu for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 10:40:22 -0800 (PST)
Received: from BLU004-OMC1S33.hotmail.com (blu004-omc1s33.hotmail.com [65.55.116.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40A0C120725 for <ietf@ietf.org>; Sun, 26 Feb 2017 10:40:22 -0800 (PST)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com ([65.55.116.7]) by BLU004-OMC1S33.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sun, 26 Feb 2017 10:40:17 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=oZPF5GP1cR1N+9d8bWFX4QHHWx9aXhZgyWpaUybLVhw=; b=Yl1QSUGGpqGw4AnqbWH3NHMPBm1F1cocneY8wGW033eEDL0S2ACgfj2pCoxEc47x7RexNNi1QfBwge+/55/VZpv19xII1bc5g66IFxIeHnp/WYllVXmxuMllJOooHMMakHVxocOISsRLfmaVu9Bq716Fn5UyW/f5SB4Ab8CsUv9VRCHstUjaljT0fe3Egq6lm2QZpdmoFG7WRxW1cx1T/oT5r6uVKKqoV0aOytFq7aA/4jV+5W9INF+oATadIaThL1lszzIpJsxs6qgsTOkob0isGz28c6Yg6Qo3ha+NLsp+xEDxXL3/6NAIxcD0KFQ6W98b6FlbAOeFX74P/a2S5g==
Received: from HE1EUR02FT027.eop-EUR02.prod.protection.outlook.com (10.152.10.51) by HE1EUR02HT074.eop-EUR02.prod.protection.outlook.com (10.152.11.253) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Sun, 26 Feb 2017 18:40:11 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com (10.152.10.53) by HE1EUR02FT027.mail.protection.outlook.com (10.152.10.72) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10 via Frontend Transport; Sun, 26 Feb 2017 18:40:11 +0000
Received: from HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) by HE1PR04MB1449.eurprd04.prod.outlook.com ([10.163.176.11]) with mapi id 15.01.0933.016; Sun, 26 Feb 2017 18:40:11 +0000
From: Khaled Omar <eng.khaled.omar@hotmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Mailing list membership.
Thread-Topic: Mailing list membership.
Thread-Index: AdKQXnXLy5KZnE4ASDKBJyU8UdPqlQ==
Date: Sun, 26 Feb 2017 18:40:11 +0000
Message-ID: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:AEBC6DF9714A42DF635EE3E5FA052862C90BA5B7A6AB3923AB6A95D94021AE1D; UpperCasedChecksum:8A33ADC16BF9555AB610254C14F2A87B9F1AA970D3C61A4E4ACFF7CA292B8E10; SizeAsReceived:7509; Count:36
x-tmn: [A7VArLrmmcZqhKkWqBlBTumWCRFeWu8N]
x-incomingheadercount: 36
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; HE1EUR02HT074; 5:mid7I6u4ocm8dXJlJoGfXuBOWaAj20jwpkPQtxZpH5QJyEE3FAXq6qWKc3RCYIwYh1dp3/kqR0+trFIjbCA7gfwnKsB9QUFmc6LuPI+LJZD/fysWK5UclFeJC8ZppDBCy9LoGbyXjzEioNjVuP43iw==; 24:9Sx9nikYH5f8liD2Qmp7FQQ2tnLoutiou6PLC4vZ1gsV3tjVBZKXeaRJ+idhoq7NEPq92RZX5HzH41F0gQksHBAD2NLIWuGILFDkUdJquCg=; 7:zD7UuCb7OR5pEWYWwWZyXNT2Rt83cnbI6BWWFKg0+AgD7aHehrSiSASzzCrpBJDPadYPgxkOv5fEvSQ8M/mjNAXyYFSMgyzKnZe5hnLecDcUvdGuH1wBLRC7o1dAz48JOKMS0hsQcJ0s0vE3AnRgDy7f/BRezOBCPIufzn8GUB8KVtm+FAuUoP3Yb8kXeX0A4/rF2Kcw0+9erhfKJnaQktDs88ZyOE74gfPGWTaN3wX5d8wNXMV2/uOqo3HIilVXr7e3MxJ1P53fUyA/QaSFStL7c6Ac10Hf3FC5nYDo+R5qpPGBPH8aC/XmKXro2e6x
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1EUR02HT074; H:HE1PR04MB1449.eurprd04.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: f816cabf-0b90-4ee8-a22e-08d45e76e54e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1603101447)(1601125254)(1701031045); SRVR:HE1EUR02HT074; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:HE1EUR02HT074; BCL:0; PCL:0; RULEID:; SRVR:HE1EUR02HT074; 
x-forefront-prvs: 0230B09AC4
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_HE1PR04MB1449F89BC245494298906D06BD540HE1PR04MB1449eurp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Feb 2017 18:40:11.2057 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1EUR02HT074
X-OriginalArrivalTime: 26 Feb 2017 18:40:17.0410 (UTC) FILETIME=[C6858E20:01D2905F]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ld8CvxITnNlHINux4WD23YXG47g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 18:40:24 -0000

--_000_HE1PR04MB1449F89BC245494298906D06BD540HE1PR04MB1449eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

This is the second time to receive an e-mail containing the following :

"Your membership in the mailing list ietf has been disabled due to excessiv=
e bounces The last bounce received from you was dated 23-Feb-2017.  You wil=
l not get any more messages from this list until you re-enable your members=
hip.  You will receive 2 more reminders like this before your membership in=
 the list is deleted."

I don't know whom should I contact for this issue, but I want to be a membe=
r on the mailing list even if my first draft is not discussed anymore but m=
aybe I will find some interesting topics in the future.

Also, where can I find the list of topics that will be discussed at the IET=
F 98 so I can be prepared for it to participate as much as I can, such conv=
ersations will be useful for all.

Best Regards,

Khaled Omar


--_000_HE1PR04MB1449F89BC245494298906D06BD540HE1PR04MB1449eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is the second time to receive an e-mail contain=
ing the following :<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;Your membership in the mailing list ietf has =
been disabled due to excessive bounces The last bounce received from you wa=
s dated 23-Feb-2017.&nbsp; You will not get any more messages from this lis=
t until you re-enable your membership.&nbsp; You will
 receive 2 more reminders like this before your membership in the list is d=
eleted.&#8221;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I don&#8217;t know whom should I contact for this is=
sue, but I want to be a member on the mailing list even if my first draft i=
s not discussed anymore but maybe I will find some interesting topics in th=
e future.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also, where can I find the list of topics that will =
be discussed at the IETF 98 so I can be prepared for it to participate as m=
uch as I can, such conversations will be useful for all.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Khaled Omar<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
</div>
</body>
</html>

--_000_HE1PR04MB1449F89BC245494298906D06BD540HE1PR04MB1449eurp_--


From nobody Sun Feb 26 11:16:02 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A839124281; Sun, 26 Feb 2017 11:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3j-LGaZCZOsz; Sun, 26 Feb 2017 11:15:54 -0800 (PST)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 68D1D120725; Sun, 26 Feb 2017 11:15:54 -0800 (PST)
Received: by mail-pg0-x243.google.com with SMTP id 5so10206365pgj.0; Sun, 26 Feb 2017 11:15:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=4jUOx8ga8IGWJDi3AvFPXKmS21po+d2+AhtNinU7qUQ=; b=KZwXRd8Hetl6v5/y9F6pwG7Uw4/KhMrYmjAlXHGqCUn4MbIF8u+ktKdHPRH04y4Qcj PdoKTjkRXtJ8tya+EEULITmUSFnRXttU+aJC3JJUCJ8Y96fiKy+StoNgsceI7lCUlbfT +kyA1OFwQhfFDVNpmUwENAZBcC1ATCYEjNOpnUDbJJZzv7bfgSurD2GCfSGN0bX7ek+4 L52WlmL90oYjll8gNuQzsu2QqT7v1pnM/FbFeBNBh4fbsvM8L5wo5oZxcCj9gLJXwjsp mwM48kdlfmkcu2HJkf/oU59kPNgSYyeM+VhAuWivU4AiG4AWH1QhunEUfZkrcxZePmV4 Pp2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=4jUOx8ga8IGWJDi3AvFPXKmS21po+d2+AhtNinU7qUQ=; b=JSMkplRtQ41+9HtWKlaBlXBl0nahSskZNujxBdm0Z9xlecgJX4Ok4GB7bDFLrbVpvg GZm/XxozeYP0mMAe80xcHENrLneHH8OiIsVnA1ZuE90pZQkmkVANljCsfJAe2MxwZk6h UHEv/KufN1pvUyFpahxC+ypfurGl18t0swfw8TsrAojc9telNelWajJbd1TYiuPsuUQr f+sezLmY9eiSreFmJLeedaNQCn9eaAFW3bLxGkDMHSfSgaa8S4DGuMn8ejHKcJRE5Qoi yEmao+TNiBuD7Afc9srXHjb5bSd6U7bIh2u1ybFTfI8ZG2T0IEntT+ClES9zXHQt14os A84g==
X-Gm-Message-State: AMke39mxiAhH2FTyiSDCP8cuWTBDJrdaqmDv0vh6kTpOq6Fr6taMXn/jhnEvqH4ZXRTxTQ==
X-Received: by 10.99.53.200 with SMTP id c191mr16478263pga.24.1488136553803; Sun, 26 Feb 2017 11:15:53 -0800 (PST)
Received: from [192.168.178.21] ([118.149.100.134]) by smtp.gmail.com with ESMTPSA id t15sm26097026pgn.62.2017.02.26.11.15.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 26 Feb 2017 11:15:53 -0800 (PST)
Subject: Address types [was: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard]
To: Fernando Gont <fgont@si6networks.com>, Sander Steffann <sander@steffann.nl>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <1fcc3e09-7ba0-0908-ef50-bc2bdd3c3efa@gmail.com>
Date: Mon, 27 Feb 2017 08:15:47 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/B5qYraEKOMeNqmiSorUhGaAaC9Q>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, ipv6@ietf.org, ietf@ietf.org, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 19:15:55 -0000

Hi Fernando,
On 27/02/2017 02:05, Fernando Gont wrote:
> On 02/26/2017 09:55 AM, Sander Steffann wrote:
>> Hi,
>>
>>> 2.3.  Address Type Identification
>>>
>>>   The type of an IPv6 address is identified by the high-order bits of
>>>   the address, as follows:
>>>
>>>      Address type         Binary prefix        IPv6 notation   Section
>>>      ------------         -------------        -------------   -------
>>>      Unspecified          00...0  (128 bits)   ::/128          2.4.2
>>>      Loopback             00...1  (128 bits)   ::1/128         2.4.3
>>>      Multicast            11111111             ff00::/8        2.6
>>>      Link-Local unicast   1111111010           fe80::/10       2.4.6
>>>      Global Unicast       (everything else)
>>>
>>>
>>> I wonder if this table should explicitly call out ULAs, and provide a
>>> reference to the corresponding section.
>>
>> ULAs are not an address type, they are Global Unicast. Adding them here might confuse people. And if we include ULAs then there is lots more that we should include as well. So while I understand your question, I think it would be better not to.
> 
> The "confusing" part is that, while globally unique, their scope is not
> really global -- i.e., they are not meant to be globally routable.
> 
> Wasn't there at some point an I-D aiming to clarify what "global" meant?
> -- IIRC, authored by Brian et al.

Not me, but you are thinking of draft-bchv-rfc6890bis

However I think this is totally out of scope for 2460bis, where the above summary
is necessary & sufficient. It's covered in 4291bis (section 2.4.7).

    Brian


From nobody Sun Feb 26 12:49:41 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D845128B44 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 12:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.109
X-Spam-Level: 
X-Spam-Status: No, score=0.109 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=OuAVVfvc; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=1WEm5O3O
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHRnNxho6Zty for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 12:49:38 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 87888126B6D for <ietf@ietf.org>; Sun, 26 Feb 2017 12:49:38 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.54.40]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1QKnO99012018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Feb 2017 12:49:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1488142175; x=1488228575; bh=R5kaino8EDRFlr507/K7VXpuv6NzQfCxiB/Xpy+z3a8=; h=Date:To:From:Subject:In-Reply-To:References; b=OuAVVfvcSzSypYl1qkHXMLtztCO7EvXplbVqJSD6e+7kk6eEnBkSc+KyQpnHVGz7e Tp1jrBjE36bsWvFTlGSByKYV8bvuCk1/0geV/abBMsKP8MCH1jics9CKfiDv/EJgHp 2NTroAOZltQZ6NJt1GyXojw7MNAWQo1jc7z3SMmQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1488142175; x=1488228575; i=@elandsys.com; bh=R5kaino8EDRFlr507/K7VXpuv6NzQfCxiB/Xpy+z3a8=; h=Date:To:From:Subject:In-Reply-To:References; b=1WEm5O3OVFvo7PisMZFcTKUYPRz0ugHGdNNMZ5ZhQtob7ZqmVUvBAyKIJeusFveC+ UjR7ir/O4gZa3VCTULvMNHEK2W3DcYCG2MflhJNW8a8SVxaAfI+MdwpiZDsUH5Xken ytWkIjZJY0cxSMYkwAuF7X6iQxhGlNJmNg77Jb88=
Message-Id: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 Feb 2017 12:48:57 -0800
To: Khaled Omar <eng.khaled.omar@hotmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Mailing list membership.
In-Reply-To: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurpr d04.prod.outlook.com>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DBmDVDwcS8sNlv9H1DCq0lDBdY0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 20:49:40 -0000

Hi Khaled,
At 10:40 26-02-2017, Khaled Omar wrote:
>This is the second time to receive an e-mail containing the following :
>
>"Your membership in the mailing list ietf has been disabled due to 
>excessive bounces The last bounce received from you was dated 
>23-Feb-2017.  You will not get any more messages from this list 
>until you re-enable your membership.  You will receive 2 more 
>reminders like this before your membership in the list is deleted."
>
>I don't know whom should I contact for this issue, but I want to be 
>a member on the mailing list even if my first draft is not discussed 
>anymore but maybe I will find some interesting topics in the future.

Your email service provider is rejecting mail from the IETF mail 
server.  I suggest contacting your email service provider to find out 
whether its service can be used to receive emails from IETF mailing lists.

>Also, where can I find the list of topics that will be discussed at 
>the IETF 98 so I can be prepared for it to participate as much as I 
>can, such conversations will be useful for all.

There is a meeting agenda at https://datatracker.ietf.org/meeting/agenda/

Regards,
S. Moonesamy 


From nobody Sun Feb 26 13:09:51 2017
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B64B812940D; Sun, 26 Feb 2017 13:09:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Russ Housley <housley@vigilsec.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-lmap-information-model-17
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148814339074.2901.10793232146724828053.idtracker@ietfa.amsl.com>
Date: Sun, 26 Feb 2017 13:09:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qD3dyvgdBbNbwWlVus4FsbG7JC8>
Cc: draft-ietf-lmap-information-model.all@ietf.org, ietf@ietf.org, lmap@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 21:09:51 -0000

Reviewer: Russ Housley
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Document: draft-ietf-lmap-information-model-17
Reviewer: Russ Housley
Review Date: 2017-02-26
IETF LC End Date: 2017-03-08
IESG Telechat date: Unknown

Summary: Ready

Major Concerns:

Section 3.1 says that the pre-configuration information contains
the certificate of the Controller or the certificate of the CA
which issued the certificate for the Controller.  Section 3.1.1
includes ma-preconfig-credentials.  Are these the same?

Section 6 says that secure communication channels are needed.  This
means
that some components of this system (at least the Controller) must
have
secret keys or private keys.  I think that Section 6 should talk
about
which components of this system have keys and the consequences if the
keys are not well protected.

Minor Concerns:

The Introduction in RFC 7594 says: "There is a desire to be able
to coordinate the execution of broadband measurements and the
collection of measurement results across a large scale set of
Measurement Agents (MAs)."  The Fact that LMAP is about broadband
measurements should be stated in the first paragraph of the
Introduction of this document.

Nits:

In Section 3, the reason for the 6 categories should probably be
placed before the list instead of several paragraphs later.

In 3.1: s/If the MA ID is not provided at this stage then/
         /If the MA ID is not provided at this stage, then/



From nobody Sun Feb 26 14:19:33 2017
Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE8161294C5 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 14:19:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihdD5UFn3tgp for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 14:19:30 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 AD32F1294C4 for <ietf@ietf.org>; Sun, 26 Feb 2017 14:19:30 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 2D17E1A26CC for <ietf@ietf.org>; Sun, 26 Feb 2017 22:19:30 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488147570; bh=Rfzg5xDblZZUfCkMnE5lfBGVv9Ers1YruXGk3pXVPQA=; h=Subject:To:References:From:Date:In-Reply-To:From; b=FYbDjFq6JQW8xrWg8dxNeKNoYkMZqVvba7ztXpGcOrb9sAXmgjPZAb4BRJTvk03cD FjEEOYCQqr+h0NZXDkAwywLQAtu4anXfQjHkLVbC/i45AhVkN8RYk5S1/OLscHlTVA tuSwGUYDBa05cD3p9WQ+n5jMHA+OlE2EPyGO+2Oc=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 6776C401EF
Subject: Re: Mailing list membership.
To: IETF discussion <ietf@ietf.org>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net>
Date: Sun, 26 Feb 2017 19:19:13 -0300
MIME-Version: 1.0
In-Reply-To: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eqWO1cM0F5ZyYCwt9KPwFOt2UpA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Feb 2017 22:19:32 -0000

Dear S Moonesamy,

the first action have to come from the ietf-discuss admin group and not 
from Khalid. The admin group have to analyse the bounce-counter for all 
list members.

Khalid use hotmail. A big MS shit. But this is the second task.

many greetings, willi


On 26/02/2017 17:48, S Moonesamy wrote:
> Hi Khaled,
> At 10:40 26-02-2017, Khaled Omar wrote:
>> This is the second time to receive an e-mail containing the following :
>>
>> "Your membership in the mailing list ietf has been disabled due to
>> excessive bounces The last bounce received from you was dated
>> 23-Feb-2017.  You will not get any more messages from this list until
>> you re-enable your membership.  You will receive 2 more reminders like
>> this before your membership in the list is deleted."
>>
>> I don't know whom should I contact for this issue, but I want to be a
>> member on the mailing list even if my first draft is not discussed
>> anymore but maybe I will find some interesting topics in the future.
>
> Your email service provider is rejecting mail from the IETF mail
> server.  I suggest contacting your email service provider to find out
> whether its service can be used to receive emails from IETF mailing lists.
>
>> Also, where can I find the list of topics that will be discussed at
>> the IETF 98 so I can be prepared for it to participate as much as I
>> can, such conversations will be useful for all.
>
> There is a meeting agenda at https://datatracker.ietf.org/meeting/agenda/
>
> Regards,
> S. Moonesamy
>


From nobody Sun Feb 26 19:47:47 2017
Return-Path: <ek@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F86E129AD2 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 19:47:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a0HJhQHwa-UO for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 19:47:39 -0800 (PST)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002: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 62D2412966B for <ietf@ietf.org>; Sun, 26 Feb 2017 19:47:38 -0800 (PST)
Received: by mail-yw0-x22c.google.com with SMTP id l138so5739522ywc.0 for <ietf@ietf.org>; Sun, 26 Feb 2017 19:47:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=yoKy9mvjYezOJIwJszkd/UYr3852CuYQ9VC+24aMiPo=; b=fTqoDZUjB0F9mpETbO0J0Rbx387lvEPdnXANnbW+nUTV9JPVV8w8a/h6Xul1YOAago W0yRPXOmkd6uyR0BWyqkk1osBa7KGr3vuOgHfMpqj3ybPKbbVV4xZIYufqV0GC2vHoSh L7/BAfbf5L1b6SsJcQjX1Ro/3wcjawYuYebGd+Lt7rKgyTDHxlNBu7ytyOpycUyYcZjg G+CqBlihJlYodOge0zqf/9R/BEYiUfEQ8IvRYuiRdpcY0qpN7gRVOMPMNOQNqCkFV2Bg F49BQ+ejxjzHsGsFIlZV42K0w6p1yCTGwKKlIcP5EoAI6e5mrVWN7deHE+sZefbq5u8+ a4vg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=yoKy9mvjYezOJIwJszkd/UYr3852CuYQ9VC+24aMiPo=; b=GVgy6IWtuhnIWVCFxUwZGvNVzb6AXpxGKQiIpbg1GNNLQGDKJlEO7s9YuFb7jNk+Q7 HVjqadFONrBKyabsXwnKDeUmBwO5mgmfr8D89XK4ZaqAnit6wUFMJ4YI9BkkJkjMmpfH 1qy+cICnMiSL1aJxR0GwSfBpY7FwC0lQwNS/Zng/G03/sISrVSW0NoQYy2LXyBT8Ka+R oV6YXYY9Yjs+ZCFBoUIxeAwWZC763DzP6iXqzgv+5JIJuIH9t2e6L6msIsGYKXeQC3ig ZrXvAHztFHf8wZibgeBpQcxmR42t3btWjWe+W+dbDE0HsZzzcRG/SSmq6iLJeBWf+G9A B9Bw==
X-Gm-Message-State: AMke39kP+1RCiXTSyrIEILzsfkAaC6Cz/HaQt2AP/ROEB/GggyU/uP3MhD1BFMg3CshtBHtqxI2PWIziXuU6b82Y
X-Received: by 10.129.93.66 with SMTP id r63mr11349892ywb.211.1488167257206; Sun, 26 Feb 2017 19:47:37 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.207.4 with HTTP; Sun, 26 Feb 2017 19:47:16 -0800 (PST)
In-Reply-To: <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com>
From: Erik Kline <ek@google.com>
Date: Mon, 27 Feb 2017 12:47:16 +0900
Message-ID: <CAAedzxqp06F6HNsr9_-pmWknUGZZy0exhTHc75pd2n4LG4Y2ww@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a114d70b8c3c77605497af091"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1zczK_9ZlIXCvD1SsdioxPsxqQw>
Cc: draft-ietf-6man-rfc2460bis@ietf.org, IETF IPv6 Mailing List <ipv6@ietf.org>, IETF Discussion <ietf@ietf.org>, Sander Steffann <sander@steffann.nl>, 6man-chairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 03:47:42 -0000

--001a114d70b8c3c77605497af091
Content-Type: multipart/alternative; boundary=001a114d70b8bbe98505497af029

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

On 26 February 2017 at 22:05, Fernando Gont <fgont@si6networks.com> wrote:

> On 02/26/2017 09:55 AM, Sander Steffann wrote:
> > Hi,
> >
> >> 2.3.  Address Type Identification
> >>
> >>   The type of an IPv6 address is identified by the high-order bits of
> >>   the address, as follows:
> >>
> >>      Address type         Binary prefix        IPv6 notation   Section
> >>      ------------         -------------        -------------   -------
> >>      Unspecified          00...0  (128 bits)   ::/128          2.4.2
> >>      Loopback             00...1  (128 bits)   ::1/128         2.4.3
> >>      Multicast            11111111             ff00::/8        2.6
> >>      Link-Local unicast   1111111010           fe80::/10       2.4.6
> >>      Global Unicast       (everything else)
> >>
> >>
> >> I wonder if this table should explicitly call out ULAs, and provide a
> >> reference to the corresponding section.
> >
> > ULAs are not an address type, they are Global Unicast. Adding them here
> might confuse people. And if we include ULAs then there is lots more that
> we should include as well. So while I understand your question, I think it
> would be better not to.
>
> The "confusing" part is that, while globally unique, their scope is not
> really global -- i.e., they are not meant to be globally routable.
>
> Wasn't there at some point an I-D aiming to clarify what "global" meant?
> -- IIRC, authored by Brian et al.
>

https://tools.ietf.org/html/draft-carpenter-6man-whats-global

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On 26 February 2017 at 22:05, Fernando Gont <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><span class=3D"gmail-">On 02/26/2017 09:55 AM, Sander Steffann wrote:<br>
&gt; Hi,<br>
&gt;<br>
&gt;&gt; 2.3.=C2=A0 Address Type Identification<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0The type of an IPv6 address is identified by the high-=
order bits of<br>
&gt;&gt;=C2=A0 =C2=A0the address, as follows:<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Address type=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
Binary prefix=C2=A0 =C2=A0 =C2=A0 =C2=A0 IPv6 notation=C2=A0 =C2=A0Section<=
br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 ------------=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
-------------=C2=A0 =C2=A0 =C2=A0 =C2=A0 -------------=C2=A0 =C2=A0-------<=
br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Unspecified=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
00...0=C2=A0 (128 bits)=C2=A0 =C2=A0::/128=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 2.4.2<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Loopback=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A000...1=C2=A0 (128 bits)=C2=A0 =C2=A0::1/128=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A02.4.3<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Multicast=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 11111111=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ff00::/8=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 2.6<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Link-Local unicast=C2=A0 =C2=A01111111010=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0fe80::/10=C2=A0 =C2=A0 =C2=A0 =C2=A02=
.4.6<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0 Global Unicast=C2=A0 =C2=A0 =C2=A0 =C2=A0(ever=
ything else)<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; I wonder if this table should explicitly call out ULAs, and provid=
e a<br>
&gt;&gt; reference to the corresponding section.<br>
&gt;<br>
&gt; ULAs are not an address type, they are Global Unicast. Adding them her=
e might confuse people. And if we include ULAs then there is lots more that=
 we should include as well. So while I understand your question, I think it=
 would be better not to.<br>
<br>
</span>The &quot;confusing&quot; part is that, while globally unique, their=
 scope is not<br>
really global -- i.e., they are not meant to be globally routable.<br>
<br>
Wasn&#39;t there at some point an I-D aiming to clarify what &quot;global&q=
uot; meant?<br>
-- IIRC, authored by Brian et al.<br></blockquote><div><br></div><div><a hr=
ef=3D"https://tools.ietf.org/html/draft-carpenter-6man-whats-global">https:=
//tools.ietf.org/html/draft-carpenter-6man-whats-global</a><br></div></div>=
</div></div>

--001a114d70b8bbe98505497af029--

--001a114d70b8c3c77605497af091
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS3wYJKoZIhvcNAQcCoIIS0DCCEswCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBFMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEXDCCA0SgAwIBAgIMf7MhR+6WMlT9cAZ4MA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTEyMjA2MzcwNloXDTE3MDUy
MTA2MzcwNlowHjEcMBoGCSqGSIb3DQEJAQwNZWtAZ29vZ2xlLmNvbTCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAMFGbCvV+u+in+H0HY3bqCemHVO+gk8MSoSt5cw8MyfvalJUBE+K8i0L
KO7g5Tf0Hwxwin3Y78Fjurdr5ScXC3q2XKlu/KeOcKZ629BIHXR3Bc4P1kbeSBqtdP1hQsXutC3N
LKA6HYfEAKX5La7jHPIPymFuzHi9jqRt1XPLBhUIx/BUgV2RaLkaLlKi1gilVaUzZ/bwKGEBPXd7
oqEa0bmYHg7nnH3c07Ka5FqwYFbFNH2B8N9qhsEvaidSWAYFR3c83MxaNvd0cc9VR+xkg4h9t4j8
kgMqch9g5WsqvEiB8X9avk0RfRrJXnLpGVE9SgWC+9g/4qHF7INLnWGpoGsCAwEAAaOCAWowggFm
MBgGA1UdEQQRMA+BDWVrQGdvb2dsZS5jb20wUAYIKwYBBQUHAQEERDBCMEAGCCsGAQUFBzAChjRo
dHRwOi8vc2VjdXJlLmdsb2JhbHNpZ24uY29tL2NhY2VydC9nc2h2c21pbWVjYTEuY3J0MB0GA1Ud
DgQWBBRSp79TZtpx4DfF6E+LlflJ0/FBvzAfBgNVHSMEGDAWgBTLOBKwx5nAeJKMsyGV5vQmYsDg
PzBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIGCCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9i
YWxzaWduLmNvbS9yZXBvc2l0b3J5LzA7BgNVHR8ENDAyMDCgLqAshipodHRwOi8vY3JsLmdsb2Jh
bHNpZ24uY29tL2dzaHZzbWltZWNhMS5jcmwwDgYDVR0PAQH/BAQDAgWgMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDANBgkqhkiG9w0BAQsFAAOCAQEAYNw4ea3dhqz3+6k7eFLEAto3ynoX
iT5jeLl+/a9UeVSG5MQjruVO3LeqKKs3757hNcyfMZSooiOzamgE/W2G7gZMkCoT2NQbD7zSNB+S
toUONsMQ8t6Awv9osq1WWoK/xZkHV8wMGDOun9Ia8vO+hOU5wMOnhvg5mbE1xbst7pK2P9HgFxY2
/5o3VcBn4M6T5omuaz6GVsQ4VssAWfnqVpholf+EQahap+3Fpue24kwL3/pWnDkp0UcvjfItSy9c
UZdf/XOjI7X4DzroB3PFZ+rJSoRUjF2mKCLbHO0TLXtpEpr8ngGu8WwEAwf7eGHI6O5LCxrLYRdw
jqaGMxZnxTGCAl4wggJaAgEBMFwwTDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExIjAgBgNVBAMTGUdsb2JhbFNpZ24gSFYgUy9NSU1FIENBIDECDH+zIUfuljJU/XAGeDAN
BglghkgBZQMEAgEFAKCB1DAvBgkqhkiG9w0BCQQxIgQgvfX92aOpn/RgphgHCdXsuQIgGI14+ohC
O71eKsxCLqQwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTcwMjI3
MDM0NzM3WjBpBgkqhkiG9w0BCQ8xXDBaMAsGCWCGSAFlAwQBKjALBglghkgBZQMEARYwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMAsGCSqGSIb3DQEBCjALBgkqhkiG9w0BAQcwCwYJYIZIAWUDBAIB
MA0GCSqGSIb3DQEBAQUABIIBAGmmnk11Z0buqvsS/IPXRJuaOzDs8f9BSV0n8vN9CAqxVUvor2mz
/R5b0Lp9PsHcjGrUyjEJp3M7i7/lJn8f6GDl/Hb6nax08GrWFXxqozgmWwlVwG/wLDNEhciNGvAr
OGq5MFNPcmyEppt+tY8Xr3T1IZNi84BS8+zlocwHFmF2ia+G3du8relfUfRBl3uAPsUNdR7qqUDU
OGnRHYPaI/23AVqTGsm52mOVuOZThIvKehvNZhRl1v1sVKtvGgV6i+kBnT+1A2wXmA47U0xXBsqr
2lf3mL2Ny/42XR6lmL4JuRFOn5liBzfUcTKxHyac5819ezggJMx2CiQuiOfdYxE=
--001a114d70b8c3c77605497af091--


From nobody Sun Feb 26 20:39:20 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECA5C1296FF for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 20:39:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.82
X-Spam-Level: 
X-Spam-Status: No, score=-0.82 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 6rOVM5bNnvVy for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 20:39:18 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56AC21296F2 for <ietf@ietf.org>; Sun, 26 Feb 2017 20:39:18 -0800 (PST)
Received: (qmail 79839 invoked from network); 27 Feb 2017 04:39:17 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 27 Feb 2017 04:39:17 -0000
Date: 27 Feb 2017 04:38:55 -0000
Message-ID: <20170227043855.1053.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Mailing list membership.
In-Reply-To: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gpmWaOc9zszFFyPjnFmRXUddy-c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 04:39:19 -0000

In article <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> you write:
>"Your membership in the mailing list ietf has been disabled due to excessive
>bounces

This is the DMARC problem that has been discussed at length here.

It's a pain, it stinks, we're working on it.

R's,
John


From nobody Sun Feb 26 21:12:48 2017
Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F11F7129B03 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 21:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAwrDndQzz8G for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 21:12:46 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 31810129B00 for <ietf@ietf.org>; Sun, 26 Feb 2017 21:12:46 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 7D4601A2560; Mon, 27 Feb 2017 05:12:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488172365; bh=UHJunrnrFZDxSzf/mHy+wRs9ryiFSIwfBysi183fw0s=; h=Subject:To:References:From:Cc:Date:In-Reply-To:From; b=G5iiQAMBrWGINy8QcNF173Mv7aTC/c1OGkvCFXBZes2CFkQ+LCuBk1FHcRnP0Cc/z 6N7XTtHvYSWhAX4dFo2ukApnOgbhqvcRrocR/ATG1lK6gjNPyVS5YTWE5jdJjITz0O IyIBS/+gtHwt7yl5nqG+lIfa/0hv2CUn2A/KxGRQ=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 0F4144059C
Subject: Re: Mailing list membership.
To: IETF discussion <ietf@ietf.org>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net>
Date: Mon, 27 Feb 2017 02:11:46 -0300
MIME-Version: 1.0
In-Reply-To: <20170227011852.GA5403@mx4.yitter.info>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jg8VITQLcNgR_xhhjsG7BLYIyZY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 05:12:47 -0000

Dear Andrew,

John Levine told us another story. And i know it from some other maillist.

For Khalid it will be immpossible to analyse, what is going on with some 
emails in some specific situation. Only in the log file of the MTA you 
can see it. But this is not possible for Khalid, or?

I don't know, if you are member in the admin group. And i don't know, if 
John is member in the admin group. Independent, this group have to start 
the process of analyse.

But John wrote, they work long time for that. And it is absolutly true, 
"It's a pain, it stinks,...". I wish you to find the real bug.

many greetings, willi


On 27/02/2017 01:38, John Levine wrote:
 >
 > This is the DMARC problem that has been discussed at length here.
 > It's a pain, it stinks, we're working on it.
 > R's,
 > John

On 26/02/2017 22:18, Andrew Sullivan wrote:
> On Sun, Feb 26, 2017 at 07:19:13PM -0300, willi uebelherr wrote:
>>
>> the first action have to come from the ietf-discuss admin group and not from
>> Khalid. The admin group have to analyse the bounce-counter for all list
>> members.
>
> No.  Khalid's mail bounced something that came from the ietf mail
> list, and it came to his mail because he was subscribed to that mail
> list.  And therefore, the question is why his configuration is
> bouncing things from the ietf mail server.  And that determination can
> only be made at his end.
>
> A
>


From nobody Mon Feb 27 01:12:20 2017
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41F03128B38; Mon, 27 Feb 2017 01:12:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.922
X-Spam-Level: 
X-Spam-Status: No, score=-6.922 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y1Z589IVnpJh; Mon, 27 Feb 2017 01:12:18 -0800 (PST)
Received: from mx141.netapp.com (mx141.netapp.com [216.240.21.12]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3DE4D128824; Mon, 27 Feb 2017 01:12:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.35,213,1484035200";  d="asc'?scan'208";a="186124460"
Received: from hioexcmbx06-prd.hq.netapp.com ([10.122.105.39]) by mx141-out.netapp.com with ESMTP; 27 Feb 2017 00:58:56 -0800
Received: from VMWEXCCAS03-PRD.hq.netapp.com (10.122.105.19) by hioexcmbx06-prd.hq.netapp.com (10.122.105.39) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 27 Feb 2017 01:07:13 -0800
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS03-PRD.hq.netapp.com (10.122.105.19) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Mon, 27 Feb 2017 01:07:13 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=bmL3gn6Y2CD1OHhBYvJWmY8005oofQxAxHkpDGS8/oc=; b=ejzP6JVy680g+HUbciB1omcfXiu0RfMRF2Q58rBZgQP+T9N7FJ4bTXSZM281Mt/3Vvi8edS5wkQLe3TptHH5TPPE3wUCRi0jtoJmiD766myqq7PuvlSEXSARgx/Oc0vlQ96VO7OLw+dK3ic0k5yOPrxA22cxDatKHdeCGswJVc0=
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com (10.160.157.18) by BN3PR0601MB1154.namprd06.prod.outlook.com (10.160.157.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.888.16; Mon, 27 Feb 2017 09:07:15 +0000
Received: from BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) by BN3PR0601MB1153.namprd06.prod.outlook.com ([10.160.157.18]) with mapi id 15.01.0933.016; Mon, 27 Feb 2017 09:07:14 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Mehmet Ersue <mersue@gmail.com>
Subject: Re: IETF 98 Preliminary Agenda
Thread-Topic: IETF 98 Preliminary Agenda
Thread-Index: AQHSjvHBJsc055sKHUmhapV+ttC3LaF54waAgAKw2oA=
Date: Mon, 27 Feb 2017 09:07:14 +0000
Message-ID: <3C6DF8C5-0F2F-4F81-8478-2451EDD5603C@netapp.com>
References: <148797717180.3179.4164525676122298302.idtracker@ietfa.amsl.com> <005301d28f80$758d5c30$60a81490$@gmail.com>
In-Reply-To: <005301d28f80$758d5c30$60a81490$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3259)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [217.70.211.15]
x-ms-office365-filtering-correlation-id: 247c528e-ce58-4a4c-bbfc-08d45ef005d3
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001); SRVR:BN3PR0601MB1154; 
x-microsoft-exchange-diagnostics: 1; BN3PR0601MB1154; 7:Gxm2UPrH/R0kGQIswb8uqJ2uqWm7mVPxrzhmzP3UgyRP1UjpYdz9d7W9N4BN48WYgduCqiaJZeX3rkUWtXspk3+dRHq5Ig6uiAFzrmO2Or/Ew2AjUrse5Jj8mkREGSbBy+THr3J6hb7QrRVw3fomKjPd1Ggt3DKb+KrcJRG+A9B98T/MaRhR/lw/r00cvHHl+yr5Y9zD2dXxGcryPqswERogsxxGpB9Pvra2Hyy3eAgMNGSf9HlNvFm454/JK6vEsT/3lFnReZa2UrbGGWiP9uZgfzIQyj3bXc+Ynysir9L1suKb9o5S3B2xqq2opdHkQjfpN8JAT7qwxJlIjI5s0A==
x-microsoft-antispam-prvs: <BN3PR0601MB11548493757E09342594CCC6A7570@BN3PR0601MB1154.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(102415395)(6040375)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(6055026)(6041248)(20161123558025)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(6072148); SRVR:BN3PR0601MB1154; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0601MB1154; 
x-forefront-prvs: 02318D10FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(7916002)(39450400003)(24454002)(189002)(377424004)(199003)(305945005)(76176999)(50986999)(7736002)(33656002)(92566002)(86362001)(99936001)(101416001)(4326007)(229853002)(2906002)(2950100002)(6916009)(77096006)(105586002)(6486002)(36756003)(6116002)(102836003)(3846002)(66066001)(8676002)(6512007)(81166006)(81156014)(5660300001)(99286003)(50226002)(3660700001)(3280700002)(7116003)(54906002)(6436002)(106116001)(106356001)(1411001)(6506006)(25786008)(2900100001)(8936002)(68736007)(53936002)(110136004)(122556002)(82746002)(6246003)(83716003)(97736004)(39060400002)(189998001)(53546006)(4001150100001)(57306001)(38730400002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BN3PR0601MB1154; H:BN3PR0601MB1153.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_2BC51559-8B17-4A73-9FCD-92E9C5F501F7"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Feb 2017 09:07:14.5725 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0601MB1154
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8nGYVVuI3TY8MTcJuwkLpBKnhDE>
Cc: IETF Agenda <agenda@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 09:12:19 -0000

--Apple-Mail=_2BC51559-8B17-4A73-9FCD-92E9C5F501F7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2017-2-25, at 17:01, Mehmet Ersue <mersue@gmail.com> wrote:
> I would like to ask to avoid an overlapping of nmrg with OPS area WGs.

Please tell the respective chairs to list those conflicts when =
requesting the slots. For example, NMRG listed:

First Priority: sdnrg nfvrg anima opsarea
Second Priority: netmod netconf nmlrg irtfopen

Lars

--Apple-Mail=_2BC51559-8B17-4A73-9FCD-92E9C5F501F7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYs+xBAAoJEFS1wwm/cMFXczYQAIR5cUHtXJZCKH07qZW0MMUH
Rc4ifticj9C2D5OogC0Xgw0QmczhK1tRJJW5K46B/j2Szb6o7Emt+J01IMP4qNLK
Alnsq5+orogMuODJq13P+uerV9LmV+2cBjrW9sOEIgBSpgHGIiymStoGh5KDoB/O
TXNrXQLEOQ5rdLYRLflNNx5Nl7DjL8v95DUUt1XFXR3J1o2KmVkh6JwWnl2SGx+5
d69Yw6Juuh7IBl71BezGAfT9BliDUuiN+ZeuhyUHGlik6+ufMixn7AUzbdKNWLde
LfpfHhu53bA+5B7MKRp76QFAy6zDqgDcVMT1AgYqRxyxUAnUO5FqoanwJHf+NkWM
jT6H29811sLeAtu/OTSA0JjEPElCq+guXWVvL+pBzVlIW1ldHIX+vZM6PXXUeloW
bXOTZAWHpJfkMBPejFbQRPHErMEweYA2kC2keJjExD+5ew2tlPJuN0W4Sa1vcmdd
h9j7Bra4rpMDwRPTqJ7Vnwqj18wtBYq8wwD93mjbOYs9rVo7mjz31xl2HqMzvOwd
TIiKMjHaLY2UY91694eh+GNlXzFkgjfk6lDBszG6QwDrtmf3p8Vvtjf++X7P/70U
rAgR6fN3u383Rud9Kpd5LujIn/u5aRqRga6dgLtJxkxfbPAjh8rck5DUWv4/1ZV/
0vHGiLgjpua2Etzr673S
=nNvK
-----END PGP SIGNATURE-----

--Apple-Mail=_2BC51559-8B17-4A73-9FCD-92E9C5F501F7--


From nobody Mon Feb 27 02:00:52 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E12129CEB for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 02:00:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.332
X-Spam-Level: 
X-Spam-Status: No, score=-0.332 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 CmR2bfhLPigU for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 02:00:49 -0800 (PST)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 807E9129CE7 for <ietf@ietf.org>; Mon, 27 Feb 2017 02:00:49 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v1RA0lRT042763 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 4133A207ABF for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +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 38214200E98 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:47 +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 v1RA0k4V028667 for <ietf@ietf.org>; Mon, 27 Feb 2017 11:00:46 +0100
Subject: Re: Last Call: <draft-ietf-6man-rfc2460bis-08.txt> (Internet Protocol, Version 6 (IPv6) Specification) to Internet Standard
To: ietf@ietf.org
References: <148599296506.18647.12389618334616420462.idtracker@ietfa.amsl.com> <6dbbbf7d-b3b8-0fbc-c2a3-546472925893@si6networks.com> <9B712605-E180-4F33-806F-9DC5CBAD2E31@steffann.nl> <456cf6e5-a57b-8198-4261-1ff2c0dc1e1c@si6networks.com> <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <fffefb38-476f-8b02-d814-60597b7d2bdd@gmail.com>
Date: Mon, 27 Feb 2017 11:00:33 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <86D1EAA4-237B-46E0-A766-E2D181250695@steffann.nl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kXB3q9rPcCAxo3bbk7yWYdhQugY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 10:00:51 -0000

Le 26/02/2017 à 14:24, Sander Steffann a écrit :
>
>> Op 26 feb. 2017, om 14:05 heeft Fernando Gont <fgont@si6networks.com> het volgende geschreven:
>>
>> On 02/26/2017 09:55 AM, Sander Steffann wrote:
>>> Hi,
>>>
>>>> 2.3.  Address Type Identification
>>>>
>>>>  The type of an IPv6 address is identified by the high-order bits of
>>>>  the address, as follows:
>>>>
>>>>     Address type         Binary prefix        IPv6 notation   Section
>>>>     ------------         -------------        -------------   -------
>>>>     Unspecified          00...0  (128 bits)   ::/128          2.4.2
>>>>     Loopback             00...1  (128 bits)   ::1/128         2.4.3
>>>>     Multicast            11111111             ff00::/8        2.6
>>>>     Link-Local unicast   1111111010           fe80::/10       2.4.6
>>>>     Global Unicast       (everything else)
>>>>
>>>>
>>>> I wonder if this table should explicitly call out ULAs, and provide a
>>>> reference to the corresponding section.
>>>
>>> ULAs are not an address type, they are Global Unicast. Adding them here might confuse people. And if we include ULAs then there is lots more that we should include as well. So while I understand your question, I think it would be better not to.
>>
>> The "confusing" part is that, while globally unique, their scope is not
>> really global -- i.e., they are not meant to be globally routable.
>
> Indeed, globally unique vs globally routable. But if you go into this then it's more complicated than it seems. Whether something is routable and where are an operational choice. Companies choosing to interconnect might route each other's ULA space, while some of my RIPE NCC allocated space is not routed anywhere public. It's difficult to give a fixed definition that doesn't take operational stuff into account.
>
> Of course the intention of how to use ULA should be mentioned somewhere, but probably not in this table.
>
>> Wasn't there at some point an I-D aiming to clarify what "global" meant?
>> -- IIRC, authored by Brian et al.
>
> Sorry, I don't remember.

It was something to correct at IANA about this 'global'.

Alex

>
> Cheers,
> Sander
>


From nobody Mon Feb 27 07:40:50 2017
Return-Path: <lorenzo@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8217B12A16D for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 07:40: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XgUTvnNrEhvM for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 07:40:46 -0800 (PST)
Received: from mail-ua0-x22e.google.com (mail-ua0-x22e.google.com [IPv6:2607:f8b0:400c:c08::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 7E3AE12A17A for <ietf@ietf.org>; Mon, 27 Feb 2017 07:40:46 -0800 (PST)
Received: by mail-ua0-x22e.google.com with SMTP id 40so60325602uau.2 for <ietf@ietf.org>; Mon, 27 Feb 2017 07:40:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tSQdEX7+O90Juw+fmEeDg5KqlnNL/0BfY0TyOVwWTfg=; b=UJnDls6QTMzWHDZx/dtEQnWbCM4ZxOkr9oRKPRoKQBjEqYqvPrtsiuIRCzHOLE5eTV vQwZpn0PL1VrWKo6YlgH1JAU2F19Jng2z/boAdaxMBi/gCLOzncaILlRf0VydODuQSbK neEwKRbst6t5rZQstc4JZRNTOd8gOb25So+6wUcd3Yhreo7wk0c/+0WOxXxLutlVCcKP pfKPcSOfOBN2cp8BHRKK8KQNaLaTAbWXo8rH6UigfTq16rzpdoa+G/IvJ/DaPbAAW2TX BNxva5Y1Qx63hdSObNPCWrZrfrNnNIM/QEocZjHhfUn7+4C/Vd84Fhe53W31ZKw3D2uB XmTw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tSQdEX7+O90Juw+fmEeDg5KqlnNL/0BfY0TyOVwWTfg=; b=OU7OEblgcoCEKtZZYQcVvf0VbBZA6VkUIUccZ8cbFyxbd4rIqX5guTGX2PewqO+rxR M9+MTlSpq/COmp8VMy528gmYsk7a4/aRtkpDz8PxtXtJZF1HjutsK9M4HEElJQ2qKMlD bOlLjkqnitgOnLzsBAeJs0QkesSMIscNojaQ9e5J2L8JK4lPFLLkB9kXBiE7jKTOBp8t Dj0uHfGC3focOL+zY3wiGs82nzT6qJHhCPG5n2xxxCpWffx70wJMx2pbUGqYCdLrb2Q9 VEGLELk9maJ+TQlAYegERzNZy1+ksRHZ0JPrtGA/ZgeO2jBWoAR9NaoLR0VdTLNcCiPC lmQg==
X-Gm-Message-State: AMke39lYA1D051S6/ODTEuw7Ja5o+BSr6u1QBfGsaQVqU3Ob9SNtSKP3O32purM5WTIFG9nrJwzeNKoCWC4H+dLq
X-Received: by 10.159.40.202 with SMTP id d68mr2380244uad.122.1488210045306; Mon, 27 Feb 2017 07:40:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.171.2 with HTTP; Mon, 27 Feb 2017 07:40:24 -0800 (PST)
In-Reply-To: <CAJE_bqe=4KruMwWOnSF7RO7TOQTdx48cG_4uSPkGptkG7R4ckw@mail.gmail.com>
References: <20170221001940.GB84656@Vurt.local> <068ce975-8b1e-a7c5-abba-2bfc1d904d70@gmail.com> <20170221101339.GC84656@Vurt.local> <CAKD1Yr33oQb=gMGaEM++hLgmMtxMdihiDrUihEsjs63vy8qRbA@mail.gmail.com> <54c81141-e4f5-4436-9479-9c02be6c09bb@Spark> <CAKD1Yr28iQHt0iuLvR3ndrT3Hfct=4k9dxjJeu3MAjDjOogEvA@mail.gmail.com> <CAL9jLaZgTp++PJ9KGHEWuPoVm6t3b8QfVDCEhz5h4fv-0fuUAA@mail.gmail.com> <CAKD1Yr3SbR=xt3RPu7+q1o14wKuUuwUc6oG+BgZtEK1O+m5sWw@mail.gmail.com> <4936e96b-fc82-4de0-9188-ced9547deb2f@Spark> <CAKD1Yr3K+SJb_4ksZ96yNypVKJE-fXopuVaXNhhKp1gkh1=QEg@mail.gmail.com> <20170222144147.GC89584@hanna.meerval.net> <7960ff2d-359f-429c-6e82-ef592f90bf53@gmail.com> <CAKD1Yr1W+AVt4Dixo9epB5VazxBsVMD+mrshwaE=n7SuX6eGDw@mail.gmail.com> <5ce34926-6bde-6410-9b1e-3f61e48e9a1d@gmail.com> <CAKD1Yr1yRTUPVTTicaTkA8fAFxHiHxdLG8ZzEHjCUDDzKg5zJg@mail.gmail.com> <CAJE_bqe=4KruMwWOnSF7RO7TOQTdx48cG_4uSPkGptkG7R4ckw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 28 Feb 2017 00:40:24 +0900
Message-ID: <CAKD1Yr3oDODYbXzrdjttWQNWBQqgFJQiJtx-ti0uwK-AwHevPw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-6man-rfc4291bis-07.txt> (IP Version 6 Addressing Architecture) to Internet Standard
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Content-Type: multipart/alternative; boundary=94eb2c12382e1a8680054984e715
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oKnSY4eACSyGlBnPtIBBuH6C3AE>
Cc: draft-ietf-6man-rfc4291bis@ietf.org, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 15:40:48 -0000

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

On Fri, Feb 24, 2017 at 3:45 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <jinm=
ei@wide.ad.jp> wrote:

> Out of curiosity: which code is it, and exactly what does its
> assumption mean?  Does it mean, for example, it allows manual
> configuration of an address but requires its IID length be 64 bits?
>

The first example that came to mind was one in the Android 464xlat
implementation. This takes the IPv6 prefix configured on the interface,
fills the bottom 64 bits with randomness, adjusts the middle bytes to make
the result checksum-neutral, and uses that as the IID. If we change the IID
to !=3D 64 bits, then that code becomes incorrect.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Feb 24, 2017 at 3:45 AM, =E7=A5=9E=E6=98=8E=E9=81=94=E5=93=89 <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jinmei@wide.ad.jp" target=3D"_blank">jinmei@=
wide.ad.jp</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Out of c=
uriosity: which code is it, and exactly what does its<br>
assumption mean?=C2=A0 Does it mean, for example, it allows manual<br>
configuration of an address but requires its IID length be 64 bits?<br></bl=
ockquote><div>=C2=A0</div><div>The first example that came to mind was one =
in the Android 464xlat implementation. This takes the IPv6 prefix configure=
d on the interface, fills the bottom 64 bits with randomness, adjusts the m=
iddle bytes to make the result checksum-neutral, and uses that as the IID. =
If we change the IID to !=3D 64 bits, then that code becomes incorrect.</di=
v></div></div></div>

--94eb2c12382e1a8680054984e715--


From nobody Mon Feb 27 09:11:12 2017
Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6E512A23A for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw0WyQ3U7ZPL for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:11:06 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 EFB3112A24A for <ietf@ietf.org>; Mon, 27 Feb 2017 09:11:05 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 30C3C1A292F; Mon, 27 Feb 2017 17:11:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488215464; bh=ZL9kxGyobsrxfTHOw6bUqPIbPn4t6o+WnQ7QfDU52Z4=; h=Subject:References:Cc:To:From:Date:In-Reply-To:From; b=QzYBDYlrgFYO3cQu68X/HBuWelKd2XnsTYhwrOfTH07iunWMq2JSqD2Ka3k8PtZTu bV1KJ9avjzwaqC4kOjVP6pnZfKPbXOOiJ2Rc8kFufyDGHARerkCeubaCQIVRG3Z9Gv PQ0T01aympJ5ggpA43rZW7cfWaPmD6xxwIgnLtm8=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 745ED400EE
Subject: Re: Mailing list membership.
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
To: IETF discussion <ietf@ietf.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net>
Date: Mon, 27 Feb 2017 14:10:51 -0300
MIME-Version: 1.0
In-Reply-To: <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eYtQ_49Ab2bSIdvWX-sjF-vMV0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:11:07 -0000

Dear Khaled,

there are many speculations like that from Andrew Sullivan. The core is, 
they don't understand the real situation and create big clouds about 
nothing.

Independent, what e-mail service you use, the MTA of the maillist server 
installation have to distribute the emails. And if he can't do it, the 
people with access to the log-files have to look for, why the MTA is not 
able to distribute.

I am not sure, but i think, you are a subscriber in the list and have no 
access to the systemfiles. Therefore, the admin group have to do it. It 
is her job. Not yours.

many greetings, willi
Asuncion, Paraguay


On 27/02/2017 11:37, Khaled Omar wrote:
>> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>
> I think so, because I'm using a free e-mail service and don't have on-premise server, so I have to keep re-enabling my subscription for this sensitive situation.
>
> Khaled
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of willi uebelherr
> Sent: Monday, February 27, 2017 7:12 AM
> To: IETF discussion
> Subject: Re: Mailing list membership.
>
>
> Dear Andrew,
>
> John Levine told us another story. And i know it from some other maillist.
>
> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>
> I don't know, if you are member in the admin group. And i don't know, if John is member in the admin group. Independent, this group have to start the process of analyse.
>
> But John wrote, they work long time for that. And it is absolutly true, "It's a pain, it stinks,...". I wish you to find the real bug.
>
> many greetings, willi
>
>
> On 27/02/2017 01:38, John Levine wrote:
>  >
>  > This is the DMARC problem that has been discussed at length here.
>  > It's a pain, it stinks, we're working on it.
>  > R's,
>  > John
>
> On 26/02/2017 22:18, Andrew Sullivan wrote:
>> On Sun, Feb 26, 2017 at 07:19:13PM -0300, willi uebelherr wrote:
>>>
>>> the first action have to come from the ietf-discuss admin group and
>>> not from Khalid. The admin group have to analyse the bounce-counter
>>> for all list members.
>>
>> No.  Khalid's mail bounced something that came from the ietf mail
>> list, and it came to his mail because he was subscribed to that mail
>> list.  And therefore, the question is why his configuration is
>> bouncing things from the ietf mail server.  And that determination can
>> only be made at his end.
>>
>> A
>>
>
>


From nobody Mon Feb 27 09:26:03 2017
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 145FE129C19; Thu, 23 Feb 2017 15:27:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: Proposed IETF Statement Concerning Personal Data for Review
X-Test-IDTracker: no
X-IETF-IDTracker: 6.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
Date: Thu, 23 Feb 2017 15:27:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qsOCs3Y_kZcIrSX7Z1uipZyDsrE>
X-Mailman-Approved-At: Mon, 27 Feb 2017 09:26:03 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Feb 2017 23:27:10 -0000

The IAOC would like community input on a proposed IETF Statement
Concerning Personal Data.

The policy discusses the following:
  1.  General – Most Personal Data Submitted to the Parties Will Become Public
  2.  You Consent to International Transmission of Your Data 
  3.  Exceptions – Information That We Do Not Release to the Public
  4.  Security
  5.  Children
  6.  Inquiries
  7.  Compliance
  8.  Other Organizations
  9.  Links to other sites.
  10.  Consent

The proposed Privacy Policy is located here:
https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm

The previous policy was posted for community review on 24 February
2016. This new version reflects input received during that community
review and a diff file reflecting the changes since that version is
located here:

https://iaoc.ietf.org/documents/Diff-Privacy-2016-02-24-02-Privacy-23Feb17.pdf

The IAOC will consider all comments received by 9 March 2017.

Ray Pelletier
IETF Administrative Director


From nobody Mon Feb 27 09:43:23 2017
Return-Path: <David.Black@dell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6616C1299A0; Mon, 27 Feb 2017 09:43:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dell.com header.b=jKLTPo/j; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=rE7b/KxP
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aegoWNoCTaJW; Mon, 27 Feb 2017 09:43:16 -0800 (PST)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 006F912A297; Mon, 27 Feb 2017 09:43:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1488216909; x=1519752909; h=from:cc:to:subject:date:message-id:references: in-reply-to:mime-version; bh=re7Py42rwuRK79e6MWTU58HbRHrZd/gl1MX1+tadZEI=; b=jKLTPo/jdd/o6InK2iwJcpzw/PK+rKtT8PxiUGlhYS+KdgQS8fxjkNAo NeTkI8C82o//T1+DqZAAEGVGfm3oZ/Mn5vvg59xIruGwgjmf0u+7/BCmb OY1F8e4P4vTLTwQi6Zh0JK0ourakr7lB/LHT0n6OPT23SshGe3e0KWsOr U=;
Received: from esa5.dell-outbound2.iphmx.com ([68.232.153.203]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2017 11:35:08 -0600
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2017 23:36:29 +0600
Received: from maildlpprd52.lss.emc.com (maildlpprd52.lss.emc.com [10.106.48.156]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v1RHhB9F025060 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Feb 2017 12:43:12 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v1RHhB9F025060
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1488217393; bh=anAjdWrfDa1swjSid9JN2StPolo=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To: Content-Type:MIME-Version; b=rE7b/KxPmavudMsBRCtZUHCKpwd5bRKO3Ht5si2egPwodlTPfKmPKKsluCmvCezkI 31szUiZTPDRJjh9LE/5XyLfHKFFxHV4w0YRVhBiI/y8L244TuucByCq6SuYrJv0MAC 2BpkCrM/Yb/WyruW64hfd3jjnuMXgS4BEeH9AuEs=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v1RHhB9F025060
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd52.lss.emc.com (RSA Interceptor); Mon, 27 Feb 2017 12:42:59 -0500
Received: from MXHUB316.corp.emc.com (MXHUB316.corp.emc.com [10.146.3.94]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v1RHgw3c001695 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Mon, 27 Feb 2017 12:42:58 -0500
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB316.corp.emc.com ([10.146.3.94]) with mapi id 14.03.0266.001; Mon, 27 Feb 2017 12:42:57 -0500
To: Shitanshu Shah <shitanshu_shah@hotmail.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: RE: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjn2hotpFQg8pf0qPmuGxW7GZeaF4QrTwgACFLACABFiS0A==
Date: Mon, 27 Feb 2017 17:42:57 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362F8D16F3@MX307CL04.corp.emc.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com> <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>
In-Reply-To: <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.45.62]
Content-Type: multipart/alternative; boundary="_000_CE03DB3D7B45C245BCA0D243277949362F8D16F3MX307CL04corpem_"
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sd2k8b_EOcl7_omZ58FFAKIq9dc>
Cc: "idr@ietf.org" <idr@ietf.org>, "Black, David" <David.Black@dell.com>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:43:22 -0000

--_000_CE03DB3D7B45C245BCA0D243277949362F8D16F3MX307CL04corpem_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ok, please make that rationale for the L2_OVERHEAD parameter clear in the d=
raft:
> Though for the cases where physical links are not to be over-run, and/or,=
 sla defined are based on l2 rates, the Consumer would
> need to know l2 overhead from the Producer. Otherwise 10 byes of l2 overh=
ead difference on 64 bytes packets can be significant
> compare to on 1400 bytes packets, and thus the Producer does not have a w=
ay to convert rates to ip based (this can cause
> functional issue), since this has to be per packet consideration.
It looks like the result is that if the Producer's L2 overhead is larger th=
an the Consumer's, and the token buckets are specified in IP octets, the co=
nsumer has to calculate a per-packet charge of the L2 overhead difference a=
gainst the IP token bucket (and in the opposite case, there may be a per-pa=
cket credit).   Are there cases where the overhead is not all L2, e.g., SLA=
/TCA Consumer is using a VPN that terminates between Consumer and Producer?

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 1:05 PM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



One response inline ##svshah2

________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Friday, February 24, 2017 8:53 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That's simpler, and a few sentences of discussi=
on about possible L2 framing differences should cover what needs to be done=
 (e.g., if traffic rates are configured in terms of L2 octets, then explain=
 how each entity converts between IP traffic and L2 traffic - the draft alr=
eady effectively contains that explanation).

##svshah2, just to make sure that some of the real use are not left out..

For the traffic conditioning where sla established is for the ip based rate=
s only, it suffices for the Producer to send rates only IP based ignoring a=
ny specific of l2 overheads.

Though for the cases where physical links are not to be over-run, and/or, s=
la defined are based on l2 rates, the Consumer would need to know l2 overhe=
ad from the Producer. Otherwise 10 byes of l2 overhead difference on 64 byt=
es packets can be significant compare to on 1400 bytes packets, and thus th=
e Producer does not have a way to convert rates to ip based (this can cause=
 functional issue), since this has to be per packet consideration.

Regards,
Shitanshu




[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that's an editorial choice - I prefer to explain how something w=
orks before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn't adopted that design is that we don't want to mak=
e assumptions on which data the remote peer will be used for enforcing loca=
l actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That's fine, I wanted to ensure that this had been considered.  The =
discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind't include a context field because we thought that the definit=
ion of the IPFIX attributes is sufficient by itself, but if you do think it=
 is helpful to have such information, we can update the table.
David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it's the link that crosses the re=
levant AS boundary, but that does have to be stated, as it's nowhere to be =
found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??

[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don't see specificatio=
n of what has to be implemented in either the text in the draft or the abov=
e explanations.
        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.


[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the "exercise to the reader"  criticism - one way to be h=
onest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the "outside the scope of this document" statement is wr=
ong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn't catch the reference, RFC 6919 is an April 1 RF=
C ... and the "SHOULD BE considered" language used in the last security con=
siderations paragraph of this draft is accurately characterized as vague in=
 Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------


--_000_CE03DB3D7B45C245BCA0D243277949362F8D16F3MX307CL04corpem_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{mso-style-priority:99;
	mso-style-link:"Balloon Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif";}
p.xmsonormal, li.xmsonormal, div.xmsonormal
	{mso-style-name:xmsonormal;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.BalloonTextChar
	{mso-style-name:"Balloon Text Char";
	mso-style-priority:99;
	mso-style-link:"Balloon Text";
	font-family:"Tahoma","sans-serif";}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Ok, please make that rati=
onale for the L2_OVERHEAD parameter clear in the draft:<o:p></o:p></span></=
p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&gt; Though for the cases where&nbsp;phys=
ical&nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are b=
ased on
 l2 rates, the&nbsp;Consumer would<br>
&gt; need to know l2 overhead from the Producer. Otherwise 10 byes of l2 ov=
erhead difference on 64 bytes packets can be significant<br>
&gt; compare to on 1400 bytes packets, and thus the Producer does not have =
a way to convert rates to&nbsp;ip based (this can cause<br>
&gt; functional issue), since this has to be per packet consideration.<o:p>=
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">It looks like the result =
is that if the Producer&#8217;s L2 overhead is larger than the Consumer&#82=
17;s, and the token buckets are specified in IP octets, the consumer
 has to calculate a per-packet charge of the L2 overhead difference against=
 the IP token bucket (and in the opposite case, there may be a per-packet c=
redit).&nbsp;&nbsp; Are there cases where the overhead is not all L2, e.g.,=
 SLA/TCA Consumer is using a VPN that terminates
 between Consumer and Producer?<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Thanks, --David<o:p></o:p=
></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Shitansh=
u Shah [mailto:shitanshu_shah@hotmail.com]
<br>
<b>Sent:</b> Friday, February 24, 2017 1:05 PM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10<o:p></o:p></sp=
an></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">One response inline ##svshah2<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><o:p>&nbsp;</=
o:p></span></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" noshade=3D"" style=3D"color:black" align=3D"ce=
nter">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black">From:</span></b><span st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"> Black, David &lt;<a href=3D"mailto:David.Black@dell.com">=
David.Black@dell.com</a>&gt;<br>
<b>Sent:</b> Friday, February 24, 2017 8:53 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black">&nbsp;<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Inline ...</span><span style=
=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Thanks, --David</span><span style=3D"co=
lor:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,=
&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:black"=
> Shitanshu
 Shah [<a href=3D"mailto:shitanshu_shah@hotmail.com">mailto:shitanshu_shah@=
hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black">&nbsp;<o:p></o:p></span></p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Hi David,<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Thank you for taking time for the review..<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Please find our response inline ##svshah and [Med]<o:p></o:p></s=
pan></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">&nbsp;<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">Regards,
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black">Shitanshu</span><span style=3D"color:black"><o:p></o:p></span></=
p>
<div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black">From:</span></b><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:blac=
k"> David
 Black &lt;<a href=3D"mailto:david.black@emc.com">david.black@emc.com</a>&g=
t;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black">
</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Reviewer: David Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142">https://en.wikipedia.org/wiki/Service-level_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; That would be good, thanks.</sp=
an><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, the purpose for advertising L2 =
overhead, from the Producer to the Consumer,&nbsp;is to make sure
 traffic is well conditioned, at the egress of the&nbsp;Consumer, to avoid =
possible indiscriminate drops at the ingress of the Producer. In another wo=
rds, the&nbsp;Producer is telling the&nbsp;Consumer to ignore its own link =
level overhead, instead use Producer's provided
 link level overhead while running frames through QoS functions (this is&nb=
sp;relevant in use-cases where l2 overhead of the&nbsp;egress link on Consu=
mer and of ingress link on the Producer are of different size, e.g., in the=
&nbsp;vpn/tunnel connection between two peer&nbsp;nodes
 which physically may be multiple hops away).</span><span style=3D"color:bl=
ack"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">I understand your comments regarding re-u=
sing TSpec without any modification.&nbsp;Do you agree with the
 use-case of l2 differences? If yes, any suggestion how to accommodate that=
?</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Specifying this in terms of I=
P octets implies that L2 overhead is to be ignored on both links.&nbsp;
 That&#8217;s simpler, and a few sentences of discussion about possible L2 =
framing differences should cover what needs to be done (e.g., if traffic ra=
tes are configured in terms of L2 octets, then explain how each entity conv=
erts between IP traffic and L2 traffic
 - the draft already effectively contains that explanation).</span><span st=
yle=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah2, just to make sure that some of=
 the real use are not left out..</span><span style=3D"color:black"><o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">For the traffic conditioning where sla es=
tablished is for the ip based rates only, it suffices for
 the Producer to&nbsp;send rates only IP based ignoring any specific of l2 =
overheads.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Though for the cases where&nbsp;physical&=
nbsp;links are not to be&nbsp;over-run, and/or,&nbsp;sla defined are based =
on
 l2 rates, the&nbsp;Consumer would need to know l2 overhead from the Produc=
er. Otherwise 10 byes of l2 overhead difference on 64 bytes packets can be =
significant compare to on 1400 bytes packets, and thus the Producer does no=
t have a way to convert rates to&nbsp;ip based
 (this can cause functional issue), since this has to be per packet conside=
ration.</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Regards,</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Shitanshu</span><span style=3D"color:blac=
k"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, what you describe below concept=
ually very much makes sense and that is what we attempt to
 achieve. What is unclear though how to capture that using TSpec definition=
 specified in RFC2215. Since that TSpec definition has both minimum-rate an=
d maximum-rate, but no in/out profile marking parameters.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Is your proposal below to define two TSpe=
cs using the same&nbsp;definition from RFC2215? Wouldn't in that
 case we have min/max specified twice? min/max in each TSpec? and thus conf=
using to represent one min and one max through two TSpecs?</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; See RFC 2698 for the desired =
behavior and the parameters needed to specify it.&nbsp; The current
 idr-sla draft is not able to represent the traffic conditioning mechanisms=
 specified in both RFC 2698 and RFC 2697, as each mechanism requires two to=
ken buckets (e.g., there are two burst sizes, but the idr-sla draft TSpec o=
nly contains one).&nbsp; This deficiency
 needs to be dealt with.&nbsp; One possibility for simplification is to dro=
p the max-rate from the RFC 2115 TSpec and assume that the max-rate for bur=
sting is the effective line rate.</span><span style=3D"color:black"><o:p></=
o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt;font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah,&nbsp;It is around the semantics=
 of&nbsp;a single queue with a different threshold for a set of code-points=
,
 where packet for a specific code-point is to be tail dropped if overall qu=
eue-depth hits code-point specific threshold at the arrival of that packet.=
</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">We will add appropriate clarification for=
 this semantics.</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, Sure. Is following clarificatio=
n okay? (some of the wordings taken from RFC2598)</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">A higher priority class of traffic&nbsp;t=
o be served without pre-empted by lower priority&nbsp;class of traffic&nbsp=
;for
 more than a packet time at the configured rate.</span><span style=3D"color=
:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">In the system that implements WRR, the us=
e of relative priority may get restricted where a single queue
 may be used for a&nbsp;higher priority traffic class where that queue &nbs=
p;is configured for the full share of the output bandwidth.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&quot;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; Last sentence basically says that W=
RR weights are out-of-scope.&nbsp; That seems wrong.&nbsp; Will look at
 revision.</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, They are to facilitate hierarch=
y. A specific Traffic Class, can further be divided in a multiple
 &nbsp;subset of&nbsp;Traffic Classes, with their own Traffic Class Element=
s and Traffic Class Services.</span><span style=3D"color:black"><o:p></o:p>=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">Will correct the wording to remove your t=
his specific concern.</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.</span><span style=3D"color:black"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, While&nbsp;eventually &quot;Tra=
ffic Conditioning Agreement&quot; should be translated to the actual forwar=
ding
 qos policy on any vendor specific device, TCA exchange largely carries con=
cepts/semantics that is either standard based or&nbsp;well understood.</spa=
n><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">While we are not aware of any working gro=
up document of QoS Yang Model, we think that &nbsp;concepts of
 Traffic Conditioning should be easily adaptable to any QoS Yang Models sin=
ce they also have to be defined to support those concepts.</span><span styl=
e=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Still want to see cross-check=
 with implementations here.</span><span style=3D"font-size:10.0pt;font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.</span><span style=3D"color:black"><o:p></o:p></=
span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; OK, thanks.</span><span style=
=3D"color:black"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[9] In section 3.2, the &quot;intended for =
the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">UPDATE message&quot; text in the specificat=
ion of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">flags is unclear.&nbsp; I suspect that this=
 is intended to differentiate</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">the two usages described in sections 4.1.1 =
(Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">(Multiple Hops), in which case the parenthe=
sized terms (or similar</span><span style=3D"font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">terminology) should be used with cross-refe=
rences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sections.</span><span style=3D"color:black"=
><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">##svshah, sure will make necessary change=
s, also in the context of earlier comment.</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[10] There needs to be a coherent discussio=
n in one place about how</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">SLA advertisement, update and withdrawal wo=
rk.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">method may suffice on the wire, but the det=
ails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">advertisement, subsequent advertisement (up=
date) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">need to be specified in one place.&nbsp; Th=
e third paragraph of Section 4</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">is a start on this material, but it's too t=
erse;&nbsp;</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] That text is terse because we are reusing the BGP mach=
inery for advertising/withdrawing; we only augment
 it with triggers that are linked to the SLA information. A new SLA will le=
ad to an update message with ADVERTISE, an update of an existing SLA will t=
rigger an update message. We do think this information is already present i=
n the document.
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;This is hard to understand it,=
 as there is no statement that the BGP machinery is being used,
 and the material on SLA usage is spread in different places.&nbsp; I sugge=
st starting section 3 with a discussion of advertisement/update/withdrawal,=
 and how all three are realized via a single ADVERTISE method via BGP UPDAT=
E - this was difficult to figure out
 in reading the current draft.</span><span style=3D"color:black"><o:p></o:p=
></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">it should be expanded</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">into its own subsection, and moved earlier =
to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">ADVERTISE method in Section 3.2.&nbsp; This=
 text from Section 3.2 should be</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">moved into that new subsection and likewise=
 expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] Another option is to move it Section 4. From our standpo=
int, we do think it is straightforward to describe the behavior once the at=
tributes format are defined.&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; Ok, that&#8217;s an editorial=
 choice - I prefer to explain how something works before defining its
 on-the-wire data format.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If an adve=
rtised SLA ID is different from earlier advertised</span><span style=3D"fon=
t-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one,</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the same=
 prefix and from the same Source AS, indicates</span><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F4=
97D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Source</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is advert=
ising new SLA Content to replace the previous one</span><span style=3D"font=
-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised w=
ith the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">In addition, I wonder whether functionality=
 should be added to allow</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">withdrawal of an advertisement by specifyin=
g its SLA ID, although that</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">was not part of the original design.</span>=
<span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt;orphans:2;widows:2"><=
span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;color:bl=
ack">[Med] The reason we didn&#8217;t adopted that design is that we don&#8=
217;t want to make assumptions on which data the remote peer
 will be used for enforcing local actions and also because of this text:</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;c=
olor:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; The SLA ID applies to aggregate traffic to prefixes for a =
given</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;;color:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2;widows:2"><span style=3D"font-si=
ze:10.0pt;font-family:&quot;Courier New&quot;;color:#212121">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; AFI/SAFI that share the same Source AS and SLA ID.</span><=
span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:=
black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; That&#8217;s fine, I wanted to ensu=
re that this had been considered.&nbsp; The discussion of BGP mechanism
 reuse will probably help here.</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[11] Notions of context for interpretation =
of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">in 3.3.1 need to be added, e.g.:</span><spa=
n style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:bla=
ck"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The first three parameters (DSCP, MPLS EXP field in top label,</span><spa=
n style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">802.1q priority) can</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">network path.</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The IP address parameters are rather likely to be VPN-specific when</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">there's more</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN that =
spans or transits the ASs involved.</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- The transport port parameters need specification of which transport</span=
><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">header and where it</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP t=
raffic carried by in VXLAN, is this the</span><span style=3D"font-size:10.0=
pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">inner TCP header</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header in =
VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">There are probably simple approaches to spe=
cifying context in all</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">cases, but that context does need to be spe=
cified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] We dind&#8217;t include a context field because we thoug=
ht that the definition of the IPFIX attributes is sufficient by itself, but=
 if you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Really???&nbsp; Please =
reread the first comment above:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The first three parameters (DSCP, MPLS EXP field in top label, 802.1q p=
riority) can</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-li=
nk or LSP-by-LSP basis along a traffic's network path.</span><span style=3D=
"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt;&nbsp; Taking just DSCP, it ca=
n change on a per-link basis, so something has to specify which link
 (between the SLA Producer and SLA Consumer?) is involved.&nbsp; It probabl=
y suffices to say that it&#8217;s the link that crosses the relevant AS bou=
ndary, but that does have to be stated, as it&#8217;s nowhere to be found i=
n the far more general IPFIX registry.</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">[12] The security considerations (section 1=
0) are severely incomplete</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">and insufficient:</span><span style=3D"colo=
r:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by this statement and=
 recommend a complete rewrite of the security considerations.</span><span s=
tyle=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Discussion of possible abuse of this BGP option for</span><span style=3D"=
font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">denial-of-service and theft-of-service,</sp=
an><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includin=
g possible countermeasures and</span><span style=3D"font-size:10.0pt;font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">mitigations.</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;;=
color:black">[Med] This attack vector is not specific to this attribute; th=
is is valid for BGP in general.</span><span style=3D"color:black"><o:p></o:=
p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; There are additional attacks =
enabled by this attribute.</span><span style=3D"color:black"><o:p></o:p></s=
pan></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- This sentence at the end of the second paragraph in Section 10 is</span><=
span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">content-free:</span><span style=3D"font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is NOT=
 RECOMMENDED to enable this attribute at the</span><span style=3D"font-fami=
ly:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale of =
the Internet unless if means to prevent leaking</span><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F=
497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">sensitive</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informati=
on are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implemen=
ter or admin supposed to do?&nbsp;</span><span style=3D"color:black"><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] An example of what an admin needs to check if this inf=
ormation can be sent to a given peer or not. Some
 of the content of the attribute contains some sensitive information such a=
s contract Id, classes, etc.</span><span style=3D"color:black"><o:p></o:p><=
/span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black=
"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;margin-left:5.25pt;text-indent:30.75pt">
<span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-=
serif&quot;;color:black">How does</span><span style=3D"font-size:10.0pt;fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">one</span><span style=3D"font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imple=
mentation or deployment is&nbsp; &quot;at the</span><span style=3D"font-siz=
e:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F49=
7D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">scale</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??</s=
pan><span style=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:black">[Med] The idea here is to avoid leaking such data in to the =
global routing table. Only entitled peers need receive
 such information with controlled scope.</span><span style=3D"color:black">=
<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot=
;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:#1F497D">David&gt; I understand the idea - the problem=
 is that I don&#8217;t see specification of what has to be implemented
 in either the text in the draft or the above explanations.</span><span sty=
le=3D"color:black"><o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Th=
e next to last paragraph in section 10 is almost content-free, as</span><sp=
an style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">it leaves</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementation=
 and deployment of key security</span><span style=3D"font-size:10.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">functionality as</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the r=
eader&quot; - that's not acceptable.</span><span style=3D"font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt;font-family:&quot;Courier New&quot;;color:black">[Med] I guess =
you are referring to the following text. Validation checks are really deplo=
yment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;;color:black"><o:p></o:p></span></p>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; The attribute may be advertised by a misbehaving node to communicate</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; Though=
</span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the enforcement of SLA parameters is outside the scope of this</span><spa=
n style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; document, it is RECOMMENDED that the SLA Consumer to enforce a set of</sp=
an><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; validation checks before translating the SLA parameters conveyed in</span=
><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; the QoS attributes into provisioning actions.&nbsp; Such validations MAY<=
/span><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; rely on SLA parameters like the origin AS or SLA ID, like generating</spa=
n><span style=3D"color:black"><o:p></o:p></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA ID using pseudo-random schemes [<a href=3D"https://tools.ietf.org/htm=
l/rfc4086" target=3D"_blank" title=3D"&quot;Randomness Requirements for Sec=
urity&quot;">RFC4086</a>].</span><span style=3D"color:black"><o:p></o:p></s=
pan></pre>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:black">&nbsp;</span><span style=3D"color:black"><o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">David&gt; I stand by the &#8220;exercis=
e to the reader&#8221; &nbsp;criticism - one way to be honest about this wo=
uld
 be to change the paragraph to:</span><span style=3D"color:black"><o:p></o:=
p></span></p>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:black"><o=
:p></o:p></span></pre>
<pre><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span><span style=3D"color:#212121">The attribute may be advertised by a m=
isbehaving node to communicate</span><span style=3D"color:black"><o:p></o:p=
></span></pre>
<pre style=3D"orphans:2;widows:2"><span style=3D"color:#212121">&nbsp;&nbsp=
; SLA parameters that are not aligned with the SLA agreements.&nbsp; The</s=
pan><span style=3D"color:black"><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"color:#212121">&nbsp;</span><span style=3D"color:black"=
><o:p></o:p></span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
color:#1F497D">David&gt; That does not change any normative content of the =
original paragraph.&nbsp; My view is that the &#8220;outside the scope of t=
his document&#8221; statement is wrong because all of these parameters are =
being defined in this draft.</span><span style=3D"color:black"><o:p></o:p><=
/span></pre>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;co=
lor:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
- Last, but not least, the final paragraph in Section 10 is a joke</span><s=
pan style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">that will</span><span style=3D"font-family:=
&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security direc=
torate reviewer - to understand why, see</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, and =
take note of the publication date of RFC</span><span style=3D"font-size:10.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">6919.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:#1F497D"><br>
David&gt; For anyone who didn&#8217;t catch the reference, RFC 6919 is an A=
pril 1 RFC ... and the &#8220;SHOULD BE considered&#8221; language used in =
the last security considerations paragraph of this draft is accurately char=
acterized as vague in Section 2 of RFC 6919:</span><span style=3D"color:bla=
ck"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; The phrase &quot;SHOULD CONSIDER&quot; indicates that th=
e authors of the</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto;text-autospace:none">
<span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;color:b=
lack">&nbsp;&nbsp; specification think that implementations should do somet=
hing, but</span><span style=3D"color:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:11.0pt;font-family:&quot;Courier New&quot;;colo=
r:black">&nbsp;&nbsp; they're not sure quite what.</span><span style=3D"col=
or:black"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;margin-bottom:12.0p=
t"><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black">------------------------</span><span style=3D"f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Having noted a dozen major issues, I'll end=
 the review here for now,</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">as I believe a serious revision of the draf=
t is called for, which</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">would be a better starting point to review =
for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">editorial items.</span><span style=3D"font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">David L. Black, Distinguished Engineer</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;col=
or:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">Dell EMC, 176 South St., Hopkinton, MA&nbsp=
; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&nbs=
p; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;;color:black"><br>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black"><a href=3D"mailto:David.Black@dell.com">Dav=
id.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:black"><br=
>
</span><span style=3D"font-size:10.0pt;font-family:&quot;Calibri&quot;,&quo=
t;sans-serif&quot;;color:black">-------------------------------------------=
-------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sa=
ns-serif&quot;;color:black"><br>
<br>
</span><span style=3D"color:black"><o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_CE03DB3D7B45C245BCA0D243277949362F8D16F3MX307CL04corpem_--


From nobody Mon Feb 27 09:44:17 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A3F612A2C2; Mon, 27 Feb 2017 09:44:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P_ZDcKnXasFp; Mon, 27 Feb 2017 09:44:04 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5603E129996; Mon, 27 Feb 2017 09:43:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 47A0FBE83; Mon, 27 Feb 2017 17:43:34 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XT_mbegmtLms; Mon, 27 Feb 2017 17:43:32 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id E5BE6BE73; Mon, 27 Feb 2017 17:43:31 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488217412; bh=S+ZqPRtII8KLf0UfTkusspCBcdffUINQ6GElD9+4Pf8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=KC0oHFbv15KQVI0N19b0ns27XxGXjMfUjCSn0A8KV+hI6t9xrG0PhY2D7uyXs+MMf LepBytC0/JH8jxpfepfdThmCj3gJM9JfzChWdMXcwFmp1vOJtg5+8mx+YZfRCyfEsq CPBsZQY1Tk35/T7e7vSRUDkpWTrpF6WuIhotFhs8=
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
To: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <ecb0fbde-0d96-a469-4f27-0d9fd5a10e10@cs.tcd.ie>
Date: Mon, 27 Feb 2017 17:43:31 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1tF9dPmxD4EsDBVTV1usVNEE11IbRnrbK"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fKs54UjnIeDfjStxNKsFzJrT7NM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:44:16 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--1tF9dPmxD4EsDBVTV1usVNEE11IbRnrbK
Content-Type: multipart/mixed; boundary="Ij6sP9jgJd5i9JHm1rJ9UB4iRwUaWAewK";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
Message-ID: <ecb0fbde-0d96-a469-4f27-0d9fd5a10e10@cs.tcd.ie>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
In-Reply-To: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>

--Ij6sP9jgJd5i9JHm1rJ9UB4iRwUaWAewK
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Some comments:

- "Parties" is a horribly legalistic term (esp. given that
the IETF isn't a legal thing really), I'd much prefer less
legalistic terms be used

- "home address" huh? How do you know where people live?
I think you mean any address supplied, but then in fact we
don't make that public that I recall - what's up there?

- "mailing list managed by the Parties" some WG lists are
not thusly managed still, are all bets off for those?
I've also managed some lists (e.g. TPC lists for IAB
workshops) that'd not clearly fit under here but maybe
should.

- "We do not make such information available to the
public." huh? Shouldn't we be saying something to the
effect that we'll not share that with anyone unless
we're forced to? (Including CF in "forced" as far as
that applies.) Ah, you do say that later, maybe try
a forward reference or align these better.

- "flash cookies, local storage" should be examples as
they'll be (or already are) outmoded (e.g indexeddb is
the new local storage or was last I looked;-)

- "not intended for use by children under 13" - we don't
care, why not say that instead of trying to avoid some
non-existent liability (which is how it looks) - maybe
s/intended for/aimed at/ would be better? (The rest of
the para is fine)

- compliance - can we have a warrant canary? If not, why
not? I think I asked about this before (not 100% sure
if that was public or just chatting with someone)

- I'm also quite surprised there's nothing that has to
be said about CF here - does that mean that they do not
engage in anything that'd violate this practice with
data/traffic related to IETFers? (I may also have asked
about that too:-)

Thanks,
S.



On 23/02/17 23:27, IETF Administrative Director wrote:
> The IAOC would like community input on a proposed IETF Statement
> Concerning Personal Data.
>=20
> The policy discusses the following:
>   1.  General =E2=80=93 Most Personal Data Submitted to the Parties Wil=
l Become Public
>   2.  You Consent to International Transmission of Your Data=20
>   3.  Exceptions =E2=80=93 Information That We Do Not Release to the Pu=
blic
>   4.  Security
>   5.  Children
>   6.  Inquiries
>   7.  Compliance
>   8.  Other Organizations
>   9.  Links to other sites.
>   10.  Consent
>=20
> The proposed Privacy Policy is located here:
> https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm
>=20
> The previous policy was posted for community review on 24 February
> 2016. This new version reflects input received during that community
> review and a diff file reflecting the changes since that version is
> located here:
>=20
> https://iaoc.ietf.org/documents/Diff-Privacy-2016-02-24-02-Privacy-23Fe=
b17.pdf
>=20
> The IAOC will consider all comments received by 9 March 2017.
>=20
> Ray Pelletier
> IETF Administrative Director
>=20
>=20


--Ij6sP9jgJd5i9JHm1rJ9UB4iRwUaWAewK--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYtGVDAAoJEC88hzaAX42iD6cH/R7CGwQJpn7qv8TKNeEoR1Is
TMjqPpVuIL4BCyVHM/VO3gfhMDZIcgQ6TvDtY+COZ3hYdu9MO083vuTOsNCc87MQ
jG1gqdweki0WlmCHfKe6kfX607D+wMslBvcZIDcEWRqvIJ304xfoDEMDS5bJGbOa
qZ1pMe0i00ZFX7LxEhh459SQpFZiA+FnuaZrguF1iQaqfSvNs1fIQJcq4pqAnwuO
NhRbwb+8dggOr/SDhlkKTF+q0+Cq3x8JdfR7UQSXJHjmkIliI3s2IiZBRZTZQsMb
ZNIGHfoUzZqnImdafrrW+0kxnnrwon3VOquMDjS/XdDcZaj+1jMmrLPwjB2Mmkw=
=IypR
-----END PGP SIGNATURE-----

--1tF9dPmxD4EsDBVTV1usVNEE11IbRnrbK--


From nobody Mon Feb 27 09:50:53 2017
Return-Path: <ted.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A1B6129994; Mon, 27 Feb 2017 09:50:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rHOkyWO5pIDV; Mon, 27 Feb 2017 09:50:50 -0800 (PST)
Received: from mail-ot0-x22a.google.com (mail-ot0-x22a.google.com [IPv6:2607:f8b0:4003:c0f::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 24FC11298AA; Mon, 27 Feb 2017 09:50:50 -0800 (PST)
Received: by mail-ot0-x22a.google.com with SMTP id x10so56884101otb.1; Mon, 27 Feb 2017 09:50:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oMWqrS9x/6Yy1OCP+7JkFuljxg4UjNhS7t7XEcAxBYY=; b=uLM62rqitMcRaOblZvlKRYWPCXXFaNpOLKup3e/+oDUQZYjsEQvDL3EjUn1UfiGoyU iCLopf7CWOwtkWnASorjc5JSWgVCQHsZfWwHhjnsOLCP65aBADksGKxkE79x+1dHN3jB TTXtqi/Tbwfs/G1Et9+nHvtg5nv44DANJb7arApXwbb21PDxdY8XN3I98tQ12JF9drt3 /RviJwp4ZpQbP/vGnxQ+olLURE9jilu7b5CN/WKeLlg9q7yducGgOXSOmqRWCSrufqVK WOnftvnD56hm9Qi0jn6pCPMUDzowOYtLQflvHGNaFvgCCuZ1aFoB3b6frrmtVtMfI88v Sr2A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=oMWqrS9x/6Yy1OCP+7JkFuljxg4UjNhS7t7XEcAxBYY=; b=fV8rW8nEyuFBmQckbQ/VbjlPFkhICWeD1/UpZqWpiKoSXo1rck2Fv6my/ICnN6hO8k T4GaFpInUCWkj2qKSeaY9pilHNNK2Q8bCoiwEwVpHoIXlMY8lssfCvSnv9O2N7OMsENd lC7UD/aQrptbLDQXkKcwuCnGop4DpjiiNsIYhX/zOJ19HHfd7A/E2tD4+Sg/R6M+o2Je ER31nQYiT9oegO2u7jGcgEOFbRRZArDBulyTy2RMANFusM+4RC6F6IIoVTF/panpoH30 1CAnH9RZ4KwdIHGZqu5uyEbcQ7P+5kqwaeKxCIG2ofHE0G2L86ynu4Wv6jMNTsW5iN2C qWZw==
X-Gm-Message-State: AMke39kyOQ1I9SKZFIkaV35GSthUm7Ccg3QkY04niMv0SNgIibVSfrtgwO+mrTM6KDXyKFNHwJFoLvkCQW2zRQ==
X-Received: by 10.157.21.26 with SMTP id u26mr4826462otf.187.1488217849248; Mon, 27 Feb 2017 09:50:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.142.85 with HTTP; Mon, 27 Feb 2017 09:50:18 -0800 (PST)
In-Reply-To: <ecb0fbde-0d96-a469-4f27-0d9fd5a10e10@cs.tcd.ie>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com> <ecb0fbde-0d96-a469-4f27-0d9fd5a10e10@cs.tcd.ie>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 27 Feb 2017 09:50:18 -0800
Message-ID: <CA+9kkMCkOfV68rhdKUcY55s-xX=A4P2+QYhcmKnoUxObV6k8UA@mail.gmail.com>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=94eb2c1924f440c0f7054986b828
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5KSB2E23C8IC4O8hqCQpvOm5phI>
Cc: IETF <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:50:51 -0000

--94eb2c1924f440c0f7054986b828
Content-Type: text/plain; charset=UTF-8

On Mon, Feb 27, 2017 at 9:43 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie>
wrote:

>
> - "not intended for use by children under 13" - we don't
> care, why not say that instead of trying to avoid some
> non-existent liability (which is how it looks) - maybe
> s/intended for/aimed at/ would be better? (The rest of
> the para is fine)
>
>
This looks to me like an effort to define the service so that we do not
need to meet the requirements of COPPA (
https://en.wikipedia.org/wiki/Children's_Online_Privacy_Protection_Act).
To the extent that meeting those requirements can be costly and we have no
known participations under 13, then I think it is probably reasonable to
include.

regards,

Ted

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

<div dir=3D"ltr">On Mon, Feb 27, 2017 at 9:43 AM, Stephen Farrell <span dir=
=3D"ltr">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" target=3D"_blank"=
>stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br><div class=3D"gmail_ext=
ra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><br>
- &quot;not intended for use by children under 13&quot; - we don&#39;t<br>
care, why not say that instead of trying to avoid some<br>
non-existent liability (which is how it looks) - maybe<br>
s/intended for/aimed at/ would be better? (The rest of<br>
the para is fine)<br>
<br></blockquote></div><br></div><div class=3D"gmail_extra">This looks to m=
e like an effort to define the service so that we do not need to meet the r=
equirements of COPPA (<a href=3D"https://en.wikipedia.org/wiki/Children&#39=
;s_Online_Privacy_Protection_Act">https://en.wikipedia.org/wiki/Children&#3=
9;s_Online_Privacy_Protection_Act</a>).=C2=A0 To the extent that meeting th=
ose requirements can be costly and we have no known participations under 13=
, then I think it is probably reasonable to include.<br><br></div><div clas=
s=3D"gmail_extra">regards,<br><br></div><div class=3D"gmail_extra">Ted<br><=
/div></div>

--94eb2c1924f440c0f7054986b828--


From nobody Mon Feb 27 09:52:07 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A671129996; Mon, 27 Feb 2017 09:52:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mW4iwB0gdZfJ; Mon, 27 Feb 2017 09:52:03 -0800 (PST)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003: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 7475C1298AA; Mon, 27 Feb 2017 09:52:03 -0800 (PST)
Received: by mail-oi0-x22b.google.com with SMTP id 2so42409443oif.0; Mon, 27 Feb 2017 09:52:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=eQLsqmj0/88EHjn8C31TVAuVu59rKL9LNAMkT2EekoI=; b=pkSD27dO69Gp1GHJFEzvz/N+SQxs32eD+PuwSYGXCM2Gc+MGAZYyGOHAvq6kUaKDJi l51BSmIC4Z9YnBa+HbAjzZBEH2sutgBiuTdCfpTy6cwlcNp75WPxU6IhKp9XUnl14Rwu 4Hc7EQH7unKh+IwApmweNXb4t/0nwet13qxy7wBYER5Ky9FCSEXLGLHsN0uvQBgKq6Fa VWORC4j3H33LKoEk9Xjt8IW9muzXA/vNBHZ2YNKw7Wt4SiLs6Htv3LjJ8WpmwbUIYEUB Shy1QIXWbJl+YkLfFG6Sq/bl2oZZr+sFmZcRExP8ejJv5au3qUtRZ6dj4mPy52AydEWP IbqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eQLsqmj0/88EHjn8C31TVAuVu59rKL9LNAMkT2EekoI=; b=IZ3k/XXWqRQRlU3psQKt/Jt9fJHIsSlEswpgz9mg+Ukou8bmB3FkBK5FHw+R4k3h1t kuCCWoQ1KiKoz61ztBs9AqrpukaKMCifanioME0l6tOfUE64KS/PuPOyz6p9lNagLT+x oc25ag/NXKUSb2FjgHPpTV1JzjEY05uNjPrfgZ0bJffSL85CJiNni/1iPnJczmOxqX0k XMGBZGwEucJDuirRV4ypYJkhCMN141RAJs7PvilirGzB7Zg/afJfN28nd/QOaeTyRXod iZsApempRI5/SdL7XHsuJ2JIOKBTByWZIfW4buNotiV7nIISXvdMAvJb81+xd5Ihl1NA CM8Q==
X-Gm-Message-State: AMke39l2ANILrXYsf+pHmjupKXCRa7wxJn/7JVsBF3b0/H/fN/Gq5PVzst8mf5KfwDYBv5vyNFS225dwd/iLFg==
X-Received: by 10.202.91.139 with SMTP id p133mr1196658oib.181.1488217922767;  Mon, 27 Feb 2017 09:52:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.52.7 with HTTP; Mon, 27 Feb 2017 09:51:42 -0800 (PST)
In-Reply-To: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Mon, 27 Feb 2017 12:51:42 -0500
Message-ID: <CAA=duU0E4EOQOVvvA+fnW420c_83zmns34oz-gnvBtGsJ_xYZQ@mail.gmail.com>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113d5cdea2955b054986bc4e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a77c-M8SGG5vX1chVWLquN_T1gI>
Cc: IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:52:05 -0000

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

Ray,

Physical address information, especially home address, that=E2=80=99s not
explicitly made public by the individual (for example, in the Author=E2=80=
=99s
section of a draft or RFC) should be included in the =E2=80=9CInformation T=
hat We
Do Not Release to the Public=E2=80=9D section.

Thanks,
Andy


On Thu, Feb 23, 2017 at 6:27 PM, IETF Administrative Director <iad@ietf.org=
>
wrote:

> The IAOC would like community input on a proposed IETF Statement
> Concerning Personal Data.
>
> The policy discusses the following:
>   1.  General =E2=80=93 Most Personal Data Submitted to the Parties Will =
Become
> Public
>   2.  You Consent to International Transmission of Your Data
>   3.  Exceptions =E2=80=93 Information That We Do Not Release to the Publ=
ic
>   4.  Security
>   5.  Children
>   6.  Inquiries
>   7.  Compliance
>   8.  Other Organizations
>   9.  Links to other sites.
>   10.  Consent
>
> The proposed Privacy Policy is located here:
> https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm
>
> The previous policy was posted for community review on 24 February
> 2016. This new version reflects input received during that community
> review and a diff file reflecting the changes since that version is
> located here:
>
> https://iaoc.ietf.org/documents/Diff-Privacy-2016-
> 02-24-02-Privacy-23Feb17.pdf
>
> The IAOC will consider all comments received by 9 March 2017.
>
> Ray Pelletier
> IETF Administrative Director
>
>

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

<div dir=3D"ltr">Ray,<div><br></div><div>Physical address information, espe=
cially home address, that=E2=80=99s not explicitly made public by the indiv=
idual (for example, in the Author=E2=80=99s section of a draft or RFC) shou=
ld be included in the =E2=80=9CInformation That We Do Not Release to the Pu=
blic=E2=80=9D section.</div><div><br></div><div>Thanks,</div><div>Andy</div=
><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_qu=
ote">On Thu, Feb 23, 2017 at 6:27 PM, IETF Administrative Director <span di=
r=3D"ltr">&lt;<a href=3D"mailto:iad@ietf.org" target=3D"_blank">iad@ietf.or=
g</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The IAOC would li=
ke community input on a proposed IETF Statement<br>
Concerning Personal Data.<br>
<br>
The policy discusses the following:<br>
=C2=A0 1.=C2=A0 General =E2=80=93 Most Personal Data Submitted to the Parti=
es Will Become Public<br>
=C2=A0 2.=C2=A0 You Consent to International Transmission of Your Data<br>
=C2=A0 3.=C2=A0 Exceptions =E2=80=93 Information That We Do Not Release to =
the Public<br>
=C2=A0 4.=C2=A0 Security<br>
=C2=A0 5.=C2=A0 Children<br>
=C2=A0 6.=C2=A0 Inquiries<br>
=C2=A0 7.=C2=A0 Compliance<br>
=C2=A0 8.=C2=A0 Other Organizations<br>
=C2=A0 9.=C2=A0 Links to other sites.<br>
=C2=A0 10.=C2=A0 Consent<br>
<br>
The proposed Privacy Policy is located here:<br>
<a href=3D"https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm" r=
el=3D"noreferrer" target=3D"_blank">https://iaoc.ietf.org/<wbr>documents/Pr=
ivacy-Statement-<wbr>23Feb17.htm</a><br>
<br>
The previous policy was posted for community review on 24 February<br>
2016. This new version reflects input received during that community<br>
review and a diff file reflecting the changes since that version is<br>
located here:<br>
<br>
<a href=3D"https://iaoc.ietf.org/documents/Diff-Privacy-2016-02-24-02-Priva=
cy-23Feb17.pdf" rel=3D"noreferrer" target=3D"_blank">https://iaoc.ietf.org/=
<wbr>documents/Diff-Privacy-2016-<wbr>02-24-02-Privacy-23Feb17.pdf</a><br>
<br>
The IAOC will consider all comments received by 9 March 2017.<br>
<br>
Ray Pelletier<br>
<span class=3D"HOEnZb"><font color=3D"#888888">IETF Administrative Director=
<br>
<br>
</font></span></blockquote></div><br></div>

--001a113d5cdea2955b054986bc4e--


From nobody Mon Feb 27 09:54:34 2017
Return-Path: <rsk@gsp.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E4212A297 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:54:31 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 cnGMR8V9Yw99 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:54:30 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 CCE5612A2B0 for <ietf@ietf.org>; Mon, 27 Feb 2017 09:54:29 -0800 (PST)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id v1RHsR1L030492 for <ietf@ietf.org>; Mon, 27 Feb 2017 12:54:28 -0500 (EST)
Date: Mon, 27 Feb 2017 12:54:27 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
Message-ID: <20170227175427.GA1098@gsp.org>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uANff18qabLm9wf9G7CMUxH-9XQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:54:31 -0000

On Thu, Feb 23, 2017 at 03:27:10PM -0800, IETF Administrative Director wrote:
> The IAOC would like community input on a proposed IETF Statement
> Concerning Personal Data. [snip]
>
> The proposed Privacy Policy is located here:
> https://iaoc.ietf.org/documents/Privacy-Statement-23Feb17.htm

1. The second paragraph (begins "The parties operate") includes
"(b) home address".  I think it would be better to use "mailing address"
to encompass everyone who uses a business address or other address.

2. Under "Exceptions -- Information That We Do Not Release to the Public",
I think two changes are needed.

	2a) Under "Non-Public Mailing Lists and direct mail to individuals
	at the Parties", I think it would be good to note that the Parties
	cannot control the disclosure of individual messages or entire
	archives of these.  The Parties can certainly request that members
	of those lists keep them private, and can certainly impose sanctions
	if it wishes on those who don't, but it can't stop that disclosure.
	Also worth noting is that security issues -- whether affecting an
	individual on one of those lists or the list mechanism/archive
	itself, could result in full disclosure of their entire contents.

	2b) I think it would be a good idea to stipulate that the Parties
	will not disclose mailing list membership records: email addresses,
	list memberships, date joined, date left, etc.  To put it less
	formally, the Parties won't out the lurkers.  While most of us
	don't have to be overly concerned about such disclosures, there
	are some people for whom it could have negative consequences.

3. Under "Security", I believe there's a typo: "guaranty" should be 
"guarantee".

4. Also under "Security", this phrase: "such release is required by
applicable law, regulation or judicial order" doesn't cover NSLs
or similar instruments, which are none of those.  At the risk of opening
an infinite can of worms, what is the policy w.r.t. NSLs et.al.?

---rsk


From nobody Mon Feb 27 10:31:45 2017
Return-Path: <wangjohnny721@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0071E12999E; Mon, 27 Feb 2017 10:31:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1vO3MoM8MOBs; Mon, 27 Feb 2017 10:31:41 -0800 (PST)
Received: from mail-ua0-x231.google.com (mail-ua0-x231.google.com [IPv6:2607:f8b0:400c:c08::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 9DC2012999D; Mon, 27 Feb 2017 10:31:41 -0800 (PST)
Received: by mail-ua0-x231.google.com with SMTP id 72so44430190uaf.3; Mon, 27 Feb 2017 10:31:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5+kg6iLBgyPA1h9gzG1SDEcAMPQa72B2KtBrvb5migE=; b=hi9R1Qanhc/CpmEAt98bSo5RCLy/Xw7EMxTRLzkOZVAo96HnePVHpwW+ElSmHM5wi5 89UCIJ9x6Bu9a3OqJEw1Nu66U8G5O9BP0+25jzird9HAia/OtHR4ToiteAUA0eEpbqbU r9PYy9RY+it6pNZ0cz3LFqc+P2fw8kX7tlZusiD2FJk0jhuYjOueGoOomYKn33ZvdE8z UK/32ESdUOiweVxuNX31S3YVeu/bzAEdw24P7yqRrUodEiv3n49D0uBgVfr4nUeJuOok 94UhuGvWNzMyAlKGlkydxUb46+uv4Hw8lbLSLDKfxgxkg1rVD+cCc+8Vk1IeNcwV/sX3 9g4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5+kg6iLBgyPA1h9gzG1SDEcAMPQa72B2KtBrvb5migE=; b=j/hUQTmO3sIkWhH5hdIPhBBoQkgOpU7CpJWLLDnvRYMFUnLWgEp+ZIcuO05fBBLvft YWYKX0mFgNcnmOXbxx4unCRhpGL2mc3wEakY7I9gYNK9JK1xZI5lvqoSyit1kPEg1NY/ 3gTzQmZYHVBNMVTGm7D9LkenwBOSUSbsio/3J1hGr8m0OVGJiPqLjYFR+1cy+g1HXNa8 rt+idI0t8r6gkF6YHx6oBOz8+YfkellKzJKK6p76Hzx2zoGh8czpBvU/9ND6SfyPowHr 9QTRxl64QSPLJSBOEvZKH3ScExuxT+olKpb975yhPGjpk4XiLexIftwYvn8iLVuItAE9 Rhtw==
X-Gm-Message-State: AMke39n462w7sRtJp2/Qz2iCEyJBK1F6t3Y/FAlpnuDWmSJiil8WrlR5nAgcRUCnerWjGM0w4h2mK+Zf9RfGpA==
X-Received: by 10.159.37.244 with SMTP id 107mr8262097uaf.9.1488220300689; Mon, 27 Feb 2017 10:31:40 -0800 (PST)
MIME-Version: 1.0
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com> <ecb0fbde-0d96-a469-4f27-0d9fd5a10e10@cs.tcd.ie> <CA+9kkMCkOfV68rhdKUcY55s-xX=A4P2+QYhcmKnoUxObV6k8UA@mail.gmail.com>
In-Reply-To: <CA+9kkMCkOfV68rhdKUcY55s-xX=A4P2+QYhcmKnoUxObV6k8UA@mail.gmail.com>
From: Johnny Wang <wangjohnny721@gmail.com>
Date: Mon, 27 Feb 2017 18:31:29 +0000
Message-ID: <CAA-e5Q0EZ6TExiJz+U0oicpst5iVteCq4JUWXNSQHVA24kOgcA@mail.gmail.com>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
To: Ted Hardie <ted.ietf@gmail.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=001a113df7be5ec9040549874a10
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SGpjt5jAaZIarnhCNMXwyKu8cj4>
Cc: IETF <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 18:31:43 -0000

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

I think we can just say "children under 13 must obtain consent from their
parents or legal guardians". We should be fine in terms of COPPA if parents
agree with the release of personal information.

Btw, I'm new to the list, so hello everyone!

Regards,
Johnny

On Mon, Feb 27, 2017 at 9:50 AM Ted Hardie <ted.ietf@gmail.com> wrote:

> On Mon, Feb 27, 2017 at 9:43 AM, Stephen Farrell <
> stephen.farrell@cs.tcd.ie> wrote:
>
>
> - "not intended for use by children under 13" - we don't
> care, why not say that instead of trying to avoid some
> non-existent liability (which is how it looks) - maybe
> s/intended for/aimed at/ would be better? (The rest of
> the para is fine)
>
>
> This looks to me like an effort to define the service so that we do not
> need to meet the requirements of COPPA (
> https://en.wikipedia.org/wiki/Children's_Online_Privacy_Protection_Act).
> To the extent that meeting those requirements can be costly and we have no
> known participations under 13, then I think it is probably reasonable to
> include.
>
> regards,
>
> Ted
>
-- 
Thanks,
Johnny Wang

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

<div dir=3D"ltr">I think we can just say &quot;children under 13 must obtai=
n consent from their parents or legal guardians&quot;. We should be fine in=
 terms of COPPA if parents agree with the release of personal information.<=
div><br></div><div>Btw, I&#39;m new to the list, so hello everyone!</div><d=
iv><br></div><div>Regards,</div><div>Johnny<br><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr">On Mon, Feb 27, 2017 at 9:50 AM Ted Hardie &lt;<a href=
=3D"mailto:ted.ietf@gmail.com">ted.ietf@gmail.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"><div dir=3D"ltr" class=3D"gmail_msg">On Mon, =
Feb 27, 2017 at 9:43 AM, Stephen Farrell <span dir=3D"ltr" class=3D"gmail_m=
sg">&lt;<a href=3D"mailto:stephen.farrell@cs.tcd.ie" class=3D"gmail_msg" ta=
rget=3D"_blank">stephen.farrell@cs.tcd.ie</a>&gt;</span> wrote:<br class=3D=
"gmail_msg"><div class=3D"gmail_extra gmail_msg"><div class=3D"gmail_quote =
gmail_msg"><blockquote class=3D"gmail_quote gmail_msg" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br =
class=3D"gmail_msg">
- &quot;not intended for use by children under 13&quot; - we don&#39;t<br c=
lass=3D"gmail_msg">
care, why not say that instead of trying to avoid some<br class=3D"gmail_ms=
g">
non-existent liability (which is how it looks) - maybe<br class=3D"gmail_ms=
g">
s/intended for/aimed at/ would be better? (The rest of<br class=3D"gmail_ms=
g">
the para is fine)<br class=3D"gmail_msg">
<br class=3D"gmail_msg"></blockquote></div><br class=3D"gmail_msg"></div></=
div><div dir=3D"ltr" class=3D"gmail_msg"><div class=3D"gmail_extra gmail_ms=
g">This looks to me like an effort to define the service so that we do not =
need to meet the requirements of COPPA (<a href=3D"https://en.wikipedia.org=
/wiki/Children&#39;s_Online_Privacy_Protection_Act" class=3D"gmail_msg" tar=
get=3D"_blank">https://en.wikipedia.org/wiki/Children&#39;s_Online_Privacy_=
Protection_Act</a>).=C2=A0 To the extent that meeting those requirements ca=
n be costly and we have no known participations under 13, then I think it i=
s probably reasonable to include.<br class=3D"gmail_msg"><br class=3D"gmail=
_msg"></div><div class=3D"gmail_extra gmail_msg">regards,<br class=3D"gmail=
_msg"><br class=3D"gmail_msg"></div><div class=3D"gmail_extra gmail_msg">Te=
d<br class=3D"gmail_msg"></div></div>
</blockquote></div></div></div><div dir=3D"ltr">-- <br></div><div data-smar=
tmail=3D"gmail_signature">Thanks,<br>Johnny Wang<br></div>

--001a113df7be5ec9040549874a10--


From nobody Mon Feb 27 11:02:20 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3C1912A2E1; Mon, 27 Feb 2017 11:02:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.79
X-Spam-Level: 
X-Spam-Status: No, score=-1.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=mGECwYOW; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=mUVLTYs1
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oTFA1TU7rGvG; Mon, 27 Feb 2017 11:02:13 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BED1F12A2CD; Mon, 27 Feb 2017 11:02:13 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.208.206]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1RJ1tCP021553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2017 11:02:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1488222132; x=1488308532; bh=O0UxNbc6OYCmT7NrBfp0SDwTNu2+KTWrux63gbihyOE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mGECwYOWgqH45uVP7oJMQK+nOwTqH6ENingU0zscEOxXmuldgH9oNVzW4A75WM7z8 nrFHopzLCnXtmtVpNDl3juhcsNxd7dQBBpBUdAaZ5rAbLRyMFVYPF2kbW3qzjjaJPx Cyjh01doDbUV2n766duq9VYPTTIzbEUMmqEyUQU8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1488222132; x=1488308532; i=@elandsys.com; bh=O0UxNbc6OYCmT7NrBfp0SDwTNu2+KTWrux63gbihyOE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mUVLTYs1rrBPuDlpeHsK9mTgZo4lIutJj7xQ7950pddrN2/AvSDFvVgac3B4hiUNA Ipf4VNSiaIa7xDZNhMX7XKRMwiIP7iEbNObo7o9ZbbTQAEbq1Je99AsoSgY0WLAnuh p17Mth22wU9L/ILnPOqZ+bSFwIOXSQX54zC9GuwQ=
Message-Id: <6.2.5.6.2.20170227103644.0cccd7a0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 27 Feb 2017 10:56:47 -0800
To: Leslie Daigle <ldaigle@thinkingcat.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
In-Reply-To: <148789243004.21178.7922360111519513594.idtracker@ietfa.ams l.com>
References: <148789243004.21178.7922360111519513594.idtracker@ietfa.amsl.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XBkL_fSkJOq4FNymO3v6XIxs1uA>
Cc: iaoc@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:02:14 -0000

Hi Leslie,
At 15:27 23-02-2017, IETF Administrative Director wrote:
>The IAOC would like community input on a proposed IETF Statement
>Concerning Personal Data.

This is the third time that the IAOC has solicited input on a 
proposed statement concerning privacy.  There wasn't any reply to the 
questions which was sent about the second proposed statement.

Could the IAOC please provide a reply to the questions which were 
asked previously?

The proposed statement identifies the Internet Society as a third 
party.  That is at odds with the statement at the bottom of the 
webpage at https://www.ietf.org/

Regards,
S. Moonesamy 


From nobody Mon Feb 27 11:05:53 2017
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 149F2127071; Mon, 27 Feb 2017 11:05:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 ukqgTzyiy8-D; Mon, 27 Feb 2017 11:05:38 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 776D0126579; Mon, 27 Feb 2017 11:05:38 -0800 (PST)
Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id BA36458C543; Mon, 27 Feb 2017 20:05:33 +0100 (CET)
Received: by faui40p.informatik.uni-erlangen.de (Postfix, from userid 10463) id A5AFFB0B874; Mon, 27 Feb 2017 20:05:33 +0100 (CET)
Date: Mon, 27 Feb 2017 20:05:33 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: Joel Halpern <jmh@joelhalpern.com>
Subject: Re: Review of draft-ietf-anima-grasp-09
Message-ID: <20170227190533.GB6222@faui40p.informatik.uni-erlangen.de>
References: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <148805167532.973.2400505933185524637.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TaWAHOR6t5hWEMnFTLMFlvHE_64>
Cc: gen-art@ietf.org, draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:05:40 -0000

Thanks, Joel!

On Sat, Feb 25, 2017 at 11:41:15AM -0800, Joel Halpern wrote:
> Reviewer: Joel Halpern
> Review result: Ready with Nits
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-anima-grasp-??
> Reviewer: Joel Halpern
> Review Date: 2017-02-25
> IETF LC End Date: 2017-03-02
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary:
> 
> Major issues:
> 
> Minor issues:
>      Section 2.2 states that routing protocols mainly consider link
> up/down and that "all nodes need a consistent view of the network
> topology".  the first seems an over-generalization, since all routing
> protocols have metrics, and almost all modern routing protocols carry
> significant additional information about the links and nodes.  The
> second statement about consistency is true for some protocols, but is
> not true for external use of BGP nor, as I understand it, for Babel. 
> So it seems again too strong a characterization.  The following
> sentence about information not normally used also seems to be at odds
> with current practice.
> 
>     Bullet 1 under SN7 in section 2.2  talks about the potential for
> circular dependence, and then says that this protocol will not provide
> any assistance for that.  given that such dependence may be complex. 
> In particular, given that these dependencies result in separate
> negotiations, the chain of efforts would continue even if the initial
> impetus has timed out.  If a single negotiation causes two dependent
> negotiations, this would seem to have the potential to cause a work
> explosion.
> 
>     It is probably considered obvious, but I did not see text
> indicating that GRASP messages with unknown MESSAGE_TYPE should be
> silently ignored.  Or any other definition of the expected behavior
> (should be logged?)
> 
> Nits/editorial comments: 
>     In section 3.1 in the definition of Technical Objective the text
> starts by saying that it is a configurable parameter or set of
> parameters.   Most further text refers to a single value, with
> indications that the value may be a complex structure.  Hence, in the
> first part of the definition, the same construction should be used,
> rather than referring to a set of values.  This gets slightly confused
> when section 3.10.4 goes back to talking about multiple parameters for
> an objective.  Consistency please?
> 
>     The first paragraph of 3.5.4.1 states that upon receiving a
> discovery request, a recipient will respond, either with the data or
> with a divert.  While this is eventually true, it is misleading.  As
> 3.5.4.2 states, the recipient, if it does not have an answer, will
> relay the request in order to get an answer.  Some mention of this in
> 3.5.4.1 would seem helpful.
> 
>     Should the first line of 3.5.5 on negotiation include "(using
> M_REQ_NEG)"?
> 

-- 
---
tte@cs.fau.de


From worley@alum.mit.edu  Sun Feb 26 16:44:44 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 024301294E1 for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 16:44:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 4FtIgBlcMFOm for <ietf@ietfa.amsl.com>; Sun, 26 Feb 2017 16:44:43 -0800 (PST)
Received: from resqmta-po-03v.sys.comcast.net (resqmta-po-03v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:162]) (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 E2D75129A29 for <ietf@ietf.org>; Sun, 26 Feb 2017 16:44:42 -0800 (PST)
Received: from resomta-po-15v.sys.comcast.net ([96.114.154.239]) by resqmta-po-03v.sys.comcast.net with SMTP id i9QUcUvWXyXuHi9Qgcsykz; Mon, 27 Feb 2017 00:44:42 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-15v.sys.comcast.net with SMTP id i9QecmVNWPFGLi9QfcMk9q; Mon, 27 Feb 2017 00:44:42 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1R0iedr001364; Sun, 26 Feb 2017 19:44:40 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1R0idYL001361; Sun, 26 Feb 2017 19:44:39 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dane-smime-15
In-Reply-To: <148811824790.2888.13003369227902377285.idtracker@ietfa.amsl.com> (worley@ariadne.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Sun, 26 Feb 2017 19:44:39 -0500
Message-ID: <87innwmphk.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfJAil5laMlQoI7AP1qZuHwqg5jLsSsUL1K2Ow0SNFoDlRfczxl73mYvnFRc/cOJfaQhysCFkoVkD/YJI/Z2KT5sg0NDFI1nWUOA/kx8dRm/MOAPe2JRL FSgRBac5rdEJDzqILr3mola625uX/msiC2/GFhkRmX66pt4O8WVRka6WSm3ZL7uC/LY7IFtn9tKlIfnFd3a95tzi2QLilR9Js1++xL1/gLLLKUoEdmo9/k7p dY/0mshlajXHLI3/LO5t5A==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jfR5w07f8cY0zksmhAlNEd6H0Lw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 19:20:00 -0000

Dale Worley <worley@ariadne.com> in his review:
> 2. Presumably it was deliberate not to have the first label for an
> SNAMEA record be the canonical UTF-8 string for the local-part, even
> though the DNS architecture (RFC 1035) seems to admit binary labels.

> 3.  Location of the SMIMEA Record
>
>    The DNS does not allow the use of all characters that are supported
>    in the "local-part" of email addresses as defined in [RFC5322] and
>    [RFC6530].
>
> I don't have the full background on this.  My memory ends at RFC
> 1035:
>
>     Although labels can contain any 8 bit values in octets that make up a
>     label, it is strongly recommended that labels follow the preferred
>     syntax described elsewhere in this memo, which is compatible with
>     existing host naming conventions.
>
> I suspect there is by now a defined way to have "UTF-8 labels". Given
> that this draft doesn't use such a mechanism, there's probably a
> discussion out there why just using a UTF-8 string as a label doesn't
> work.  It would be helpful to put a reference to that discussion here,
> because the mechanism in the draft is doing a lot of work to avoid the
> seemingly obvious mechanism.

>From draft-ietf-dane-smime-15:

> 9.2.  Email Address Information Leak
> 
>    The hashing of the local-part in this document is not a security
>    feature.  Publishing SMIMEA records will create a list of hashes of
>    valid email addresses, which could simplify obtaining a list of valid
>    email addresses for a particular domain.  It is desirable to not ease
>    the harvesting of email addresses where possible.
> 
>    The domain name part of the email address is not used as part of the
>    hash so that hashes can be used in multiple zones deployed using
>    DNAME [RFC6672].  This makes it slightly easier and cheaper to brute-
>    force the SHA2-256 hashes into common and short local-parts, as
>    single rainbow tables [Rainbow] can be re-used across domains.  This
>    can be somewhat countered by using NSEC3.

After thinking about this more, it seems to me that the draft is
suffering from conflicting requirements.  On one hand, it wants to not
have the SMIMEA records provide a complete list of local-parts for the
domain name.  On the other hand, simply hashing the local-parts does not
provide enough protection of the local-parts because one dictionary can
be used to attack every domain that uses SMIMEA.  And hashing the
local-parts with the domain name makes it impossible to present the same
set of SMIMEA records for several domain names (that are e-mail
equivalent) using DNAME records.  This, I think, leads to justifying
using hashes as labels for the RRs even though the local-parts are
encoded in UTF-8, and could be used as labels themselves.

It seems to me the way out of this conflict is to salt the hashes of the
local-parts.  That is, each domain has a salt value of e.g. 128 bits (16
octets) which is hashed with the local-part to produce the label for the
RR.  The natural way to distribute the salt is in an RR attached to the
_smimecert domain (which ensures that several domains can use DNAME to
redirect to one tree of SMIMEA records), and it seems that an easy way
to do that is to use an SMIMEA RR with another "certificate usage" value
(presumably 4) to specify that the "certificate association data" field
holds the salt value:

    $origin example.com.

    ; salt
    _smimecert IN SMIMEA 4 0 0 0f215f3ab4a8bd21b831c8316379d5b0
    ; hugh@example.com
    51dfb169b7e8f5eeb4c853bf2cc2d9481cb6e9f3bd156afeb3b1cf42._smimecert (
        IN SMIMEA 0 0 1 
        d2abde240d7cd3ee6b4b28c54df034b97983a1d16e8a410e4561cb106618e971 )

It would even be upward-compatible from the current system if we defined
that if there was no SMIMEA record for the _smimecert domain, then the
hash is unsalted.

Dale


From nobody Mon Feb 27 12:21:26 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E42212A316; Mon, 27 Feb 2017 12:21:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-mpls-residence-time-14
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148822688424.13746.15775745274859586475.idtracker@ietfa.amsl.com>
Date: Mon, 27 Feb 2017 12:21:24 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_PYtjuSPWD8iyi9daTL3UOwpANY>
Cc: mpls@ietf.org, draft-ietf-mpls-residence-time.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 20:21:24 -0000

Reviewer: Robert Sparks
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-residence-time-14
Reviewer: Robert Sparks
Review Date: 2017-02-27
IETF LC End Date: 2017-01-17
IESG Telechat date: 2017-03-02

Summary: (Still) Ready.

My comments have been addressed.

There were some fairly big changes for a document in IETF LC that came
in with this version
based on feedback from the call for review from several other working
groups.  The new text
looks ok to me.



From nobody Mon Feb 27 12:36:50 2017
Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55BD412A321 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 12:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DBSeHdqSKfQT for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 12:36:48 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 4915E12A31E for <ietf@ietf.org>; Mon, 27 Feb 2017 12:36:48 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id CC7051A260D for <ietf@ietf.org>; Mon, 27 Feb 2017 20:36:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488227808; bh=Du0ZPvAQtek/ojGh45m3k5rjnovMVYlKCY38jTUmuCs=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Duw6oBs4THXuq5jjLQas+UIrAN04QITFqgB9pIOrXfCWLU8oYiHl745I0t96ngZko uCI3pyQUHHhABBtUSVj6xNPY1DdFF4MplrxJfe6OC90+YWDa1bfGVGhfD3jj6+H1R6 /qeaAXvAc8DX2uXx+c4n/oryS2CEthUH/zpYt+mA=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id BB64541B9B
Subject: Re: Mailing list membership.
To: IETF discussion <ietf@ietf.org>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net>
Date: Mon, 27 Feb 2017 17:36:11 -0300
MIME-Version: 1.0
In-Reply-To: <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RyPtlsQQC_1Rpu5EP0dHylOfmyQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 20:36:49 -0000

Dear Khaled,

you wrote:
"... but don't forget that this is a repeating issue ..."

I agree with that and therefore, never i will move in a private space 
outside of the list. This is a administration question for the list. And 
all list members need the possibility to read our discussion. Only then 
the other members in the list can participate and explain her experience.

Maybe, there are more poeple with pracitical experience with mailman and 
his modules. But the first step is always to open the discussion and 
stop the private hidden spaces.

many greetings, willi


On 27/02/2017 14:33, Khaled Omar wrote:
> Hi Willi,
>
>> I am not sure, but i think, you are a subscriber in the list and have no access to the systemfiles. Therefore, the admin group have to do it. It is her job. Not yours.
>
> That's correct, but don't forget that this is a repeating issue and as we see it happens for all people who comes to the IETF and uses ind. e-mails so facilities from the admins should be occurred to be easy for all to receive e-mails from other subscribers, we should stand up and solve it.
>
> Khaled
>
> -----Original Message-----
> From: willi uebelherr [mailto:willi.uebelherr@riseup.net]
> Sent: Monday, February 27, 2017 7:11 PM
> To: IETF discussion
> Cc: Khaled Omar
> Subject: Re: Mailing list membership.
>
>
> Dear Khaled,
>
> there are many speculations like that from Andrew Sullivan. The core is, they don't understand the real situation and create big clouds about nothing.
>
> Independent, what e-mail service you use, the MTA of the maillist server installation have to distribute the emails. And if he can't do it, the people with access to the log-files have to look for, why the MTA is not able to distribute.
>
> I am not sure, but i think, you are a subscriber in the list and have no access to the systemfiles. Therefore, the admin group have to do it. It is her job. Not yours.
>
> many greetings, willi
> Asuncion, Paraguay
>
>
> On 27/02/2017 11:37, Khaled Omar wrote:
>>> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>>
>> I think so, because I'm using a free e-mail service and don't have on-premise server, so I have to keep re-enabling my subscription for this sensitive situation.
>>
>> Khaled
>>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of willi uebelherr
>> Sent: Monday, February 27, 2017 7:12 AM
>> To: IETF discussion
>> Subject: Re: Mailing list membership.
>>
>>
>> Dear Andrew,
>>
>> John Levine told us another story. And i know it from some other maillist.
>>
>> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>>
>> I don't know, if you are member in the admin group. And i don't know, if John is member in the admin group. Independent, this group have to start the process of analyse.
>>
>> But John wrote, they work long time for that. And it is absolutly true, "It's a pain, it stinks,...". I wish you to find the real bug.
>>
>> many greetings, willi
>>
>>
>> On 27/02/2017 01:38, John Levine wrote:
>>  >
>>  > This is the DMARC problem that has been discussed at length here.
>>  > It's a pain, it stinks, we're working on it.
>>  > R's,
>>  > John
>>
>> On 26/02/2017 22:18, Andrew Sullivan wrote:
>>> On Sun, Feb 26, 2017 at 07:19:13PM -0300, willi uebelherr wrote:
>>>>
>>>> the first action have to come from the ietf-discuss admin group and
>>>> not from Khalid. The admin group have to analyse the bounce-counter
>>>> for all list members.
>>>
>>> No.  Khalid's mail bounced something that came from the ietf mail
>>> list, and it came to his mail because he was subscribed to that mail
>>> list.  And therefore, the question is why his configuration is
>>> bouncing things from the ietf mail server.  And that determination
>>> can only be made at his end.
>>>
>>> A
>>>
>>
>>
>


From nobody Mon Feb 27 13:01:07 2017
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5CC612A33F for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 13:01:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=opendkim.org header.b=dNFY4u3G; dkim=pass (1024-bit key) header.d=elandsys.com header.b=Jktdpi7t
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rtsb0mPIRDS5 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 13:01:04 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD02412A328 for <ietf@ietf.org>; Mon, 27 Feb 2017 13:01:04 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.208.206]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id v1RL0pOZ029660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2017 13:01:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1488229262; x=1488315662; bh=2PZ6qfoYFTeq0k/l8L5T0OiqzP1tRDyHh3Es8fPsRn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=dNFY4u3GE7S2em7JjFKQp4gMLHVR9UdQ6zNaCfLV+skCbe730VCFh7KITQnz7cFyh kjDI5x+DjuXbKFFakmTNtEVSTXGevP0Ayd/hk8zec78KRdyeNiK+ZMisZMhfWMnjvW kZCaUyE3qbyh0z25vwP9ELSD1Iv+vSb4Qoput1WE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1488229262; x=1488315662; i=@elandsys.com; bh=2PZ6qfoYFTeq0k/l8L5T0OiqzP1tRDyHh3Es8fPsRn0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Jktdpi7t3PVWDSLw16VsspsT4+/gh5YxdPQSldizgBaJ/4+LKslt/BrRQC4DbuFcH 9vWsdPNQaorpcW2yWQZHX0cqqcAuJVqGMOeA6goAM4iYRTNR84Q+3Kp5FfO5vVERNt /WYq6YcfcATCLGsqzszmw6TeW5FOlrQt6pRCQrxI=
Message-Id: <6.2.5.6.2.20170227115336.0cd97680@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 27 Feb 2017 12:29:29 -0800
To: willi uebelherr <willi.uebelherr@riseup.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Mailing list membership.
In-Reply-To: <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pQ_jgrKxnl-wCyEG0ulmuFcpXyA>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 21:01:06 -0000

Hi Willi,
At 14:19 26-02-2017, willi uebelherr wrote:
>the first action have to come from the ietf-discuss admin group and 
>not from Khalid. The admin group have to analyse the bounce-counter 
>for all list members.

The above is different from the suggestion which I made [1].  I took 
into consideration an issue [2] affecting this IETF mailing list when 
I wrote the message [1].  I prefer not to jump to hasty conclusions 
when there wasn't any information to show that the problem 
encountered by the subscriber is related to the issue [2].

I happen to be one of the facilitators for this mailing list.  That 
is why I replied to the subscriber on a Sunday.

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg101762.html
2. There were several threads in 2016 about that issue.  


From nobody Mon Feb 27 13:17:05 2017
Return-Path: <aaron.falk@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812C71293E4; Mon, 27 Feb 2017 13:17:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I8AJ098zrZyS; Mon, 27 Feb 2017 13:17:01 -0800 (PST)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::242]) (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 73148128B37; Mon, 27 Feb 2017 13:17:01 -0800 (PST)
Received: by mail-qk0-x242.google.com with SMTP id s186so20189844qkb.1; Mon, 27 Feb 2017 13:17:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:mime-version; bh=ALcOPEKhnvyOv0ajWKbQNaYW5cEF3z1bkUU82SqM9t0=; b=d00P/YvGbjsdAxD7dOCjbqqNZKBu1tQWdFVVpB1iWBe0DpAlstgUyd63rdvpQ9sQiO YTVyqBYMFIY5m6RFkMJ5YpZFKswo69GK13MxhSLj+fknlrvATMNYgTuG5ICP5xCyPgPf yJHktKZ4bKJNWGmiel4VcYyHciqWm8l2qf5jw+AO4TnXSBeZhaX42gFcKxyHIrxtyV7c p+E9mRWD9y5d+dnpRClL6eaDmwyPr1sDaSVsSTE2bkbH0XfAv2IU+me2Rh+nmwrsB7yv 8cKTQC56Ed3CQwkRXn6o+OcFIh66enCuNLvr9p13MsQX4sTXszFkyqtpNry/UloabAUs y1Bg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:date:message-id:mime-version; bh=ALcOPEKhnvyOv0ajWKbQNaYW5cEF3z1bkUU82SqM9t0=; b=IdjdfsL5CHsMtE0nk0myA3jagJkFSOb3v5yZRJwPLh9+IWAN74ATGyyQknhC2DGqd6 VdRr8YpFoZnUwtpjFXXyJj1zxitWYVa/+P5/IKTO8ZZfWHL4uJ2ISbXY99JtOjW5d2qn wSbuK1loY9R82MK2sKnuOtX1gy0EJ0BNuA9mj+s6iHmcg+cVW+SDYSN0j6CY9xq41nO1 gIzsMxwGWgFi/n7Vhrc5C/TvP/2UV/Eo8xnklsBQg47UrJA3Vuhg7QDcbE2o7H4kRSq/ zkA+09U9m7NUUIYIshaIdR8WIwHMCGwiKh9ttFBXe70ZWnpOveAI+X91I6CQYRmhvJMT tJAw==
X-Gm-Message-State: AMke39kFYdETwOkPfZ24+MSe8ut/HVRRXmef2KPw/AfxXz7lRPMd5KOD2gvi6QEciBvNog==
X-Received: by 10.200.1.142 with SMTP id x14mr19456776qtf.170.1488230220209; Mon, 27 Feb 2017 13:17:00 -0800 (PST)
Received: from [172.19.32.176] ([2001:4878:8000:60:a92e:9639:a73b:dac6]) by smtp.gmail.com with ESMTPSA id w186sm11064608qkw.44.2017.02.27.13.16.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Feb 2017 13:16:59 -0800 (PST)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, 98attendees@ietf.org
Subject: cfp: Bad Attitude PechaKucha in Chicago
Date: Mon, 27 Feb 2017 16:16:57 -0500
Message-ID: <D5E6A630-BC3F-4E09-849C-40E7EE5378B6@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_1DEBA3C2-56FD-499C-A2ED-D68C3611B1CA_="
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c3PnFiLUurfLi3C_qKfjPQaruh0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 21:17:03 -0000

--=_MailMate_1DEBA3C2-56FD-499C-A2ED-D68C3611B1CA_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

This is a heads-up that I=E2=80=99m planning to arrange for another Pecha=
Kucha =

event at IETF-98 in Chicago.  (Sorry for the repeat announcement.)

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin and Seoul PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_1DEBA3C2-56FD-499C-A2ED-D68C3611B1CA_=
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/xhtml; charset=3Dutf-8"=
>
</head>
<body>
<div style=3D"font-family:sans-serif"><div style=3D"white-space:normal">
<p dir=3D"auto">This is a heads-up that I=E2=80=99m planning to arrange f=
or another PechaKucha event at IETF-98 in Chicago.  (Sorry for the repeat=
 announcement.)</p>

<p dir=3D"auto">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin and Seoul PKs can be found <a href=3D"ht=
tp://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_1DEBA3C2-56FD-499C-A2ED-D68C3611B1CA_=--


From nobody Mon Feb 27 13:59:25 2017
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A182129413; Mon, 27 Feb 2017 13:59:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 xGqia-VKIzou; Mon, 27 Feb 2017 13:59:22 -0800 (PST)
Received: from [IPv6:2001:14b8:400:f33:189a:a94c:b286:de35] (unknown [IPv6:2001:14b8:400:f33:189a:a94c:b286:de35]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 06AE212940A; Mon, 27 Feb 2017 13:59:20 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: REMINDER: Agenda and connection details for the IASA 2.0 workshops
From: IETF Chair <chair@ietf.org>
In-Reply-To: <F30556FA-0F6C-4B6C-A824-32682C0435B5@ietf.org>
Date: Mon, 27 Feb 2017 23:59:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <52A88D02-67A7-4BCA-9F14-52DEFB68E5E5@ietf.org>
References: <148701676326.25013.13898050851695958169.idtracker@ietfa.amsl.com> <F30556FA-0F6C-4B6C-A824-32682C0435B5@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TEMDT1By7FG1S5kQwWMK5Ly9CHM>
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 21:59:23 -0000

I wanted to remind everyone of our workshops tomorrow February 28,
relating to collecting feedback from you all regarding our =
administrative
arrangements.

Agenda, slides, mailing list, jabber rooms, connection details, and so =
on
can be found here:

=
https://datatracker.ietf.org/meeting/interim-2017-iasa20-01/agenda/iasa20/=

=
https://datatracker.ietf.org/meeting/interim-2017-iasa20-01/session/iasa20=


For background, see
=
https://www.ietf.org/blog/2017/02/reviewing-and-assessing-the-ietf-adminis=
trative-support-activity/

Jari Arkko, IETF Chair


From nobody Mon Feb 27 14:53:36 2017
Return-Path: <kerlyn2001@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DBBB129447; Mon, 27 Feb 2017 14:53:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level: 
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FORGED_FROMDOMAIN=0.229, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oThYxHMz-KRa; Mon, 27 Feb 2017 14:53:31 -0800 (PST)
Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003: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 8813E129443; Mon, 27 Feb 2017 14:53:31 -0800 (PST)
Received: by mail-oi0-x234.google.com with SMTP id 62so46503920oih.2; Mon, 27 Feb 2017 14:53:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=rnZvXipBZIXrYjhUdgEqkSTJdVXttaMKH3lWdSkRW5M=; b=a8lPX1/9klVmTyI29z1n7b+/zHJul40ca84Iaa0/419n5SRbLB2fTCiSc8YXga00Yz GeeDxHwXcRzgsrTaHsm7EzLIpyncW6cZlZtffCk5pRoTjZxuECbKA+PjBb+ry0chMaDz iUC+r8hSDrjAskyKuqpKjS+SUsrGo7UHm7iTEdPXa/nAMSxORNCuySVPYJKQe7dSSRie Z/IRP7ABQ9elD2lHxbfrsEjrmGNUzY5hIbw5x8THWc0JxrzFTyL0irnPjPrk0Kac0xBx fBkxBUSpn+QqytnMARs/luXvbAn2OGCUt3yx219pvjT6oYYrxrEm/KXoie6vcyxJMa9g 2Auw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=rnZvXipBZIXrYjhUdgEqkSTJdVXttaMKH3lWdSkRW5M=; b=YnyVQT+JkGIrZTFhZxF6X9Xi4z2MzUwq2iZpcUqWB73y7oi3dOj9PmBCmYXcfmNj2/ 8fMuiRguFHTGX4aPlLkW9BRG+Z+TGMcCqm52Prf1TRjkKUUCVfyE8+ctLCJ6whXrDEe5 Cu2BC78XZyh9GVgn4e8Zg3jBrs6ltTdN6gZsGIrtDpDfFCaR3YWnQYNARJSwjV7wbmjQ nX3g2qSqm46JADqdjdzTty8BMai4w+IVW4lrp6h23/ooLzs6iFnkK8Ip4d/xYzBBjNEa 2M+Q+wp4fy+h8xmeB/KGKXpV/KjwfcPyirL+aYndoZSnAidm0CEJfehfi239xyWGcowv PAiA==
X-Gm-Message-State: AMke39nb94rk1jHxJ9YtaFyGaJ+qk4e6IDvjPKEcZWIK+h1wn4veCxjSRJ4ijVDKFfocFB6K62BFKNi0h5Ce2g==
X-Received: by 10.202.245.132 with SMTP id t126mr9008838oih.52.1488236010763;  Mon, 27 Feb 2017 14:53:30 -0800 (PST)
MIME-Version: 1.0
Sender: kerlyn2001@gmail.com
Received: by 10.182.217.38 with HTTP; Mon, 27 Feb 2017 14:53:30 -0800 (PST)
In-Reply-To: <87h97b41wc.fsf@hobgoblin.ariadne.com>
References: <87h97b41wc.fsf@hobgoblin.ariadne.com>
From: Kerry Lynn <kerlyn@ieee.org>
Date: Mon, 27 Feb 2017 17:53:30 -0500
X-Google-Sender-Auth: bHPr6Q-HSgDQnUXrhFNgiWyrin4
Message-ID: <CABOxzu3EeOCF7mmpxB88b4+NE5SzFrPVDzLa=KqOQenwSezQfw@mail.gmail.com>
Subject: Re: [6lo] Last Call: <draft-ietf-6lo-6lobac-06.txt> (Transmission of IPv6 over MS/TP Networks) to Proposed Standard
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary=001a1149526cc37c9b05498af2a2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EewEtFLoekc73X8nDXhAL8MOyXY>
Cc: ietf@ietf.org, draft-ietf-6lo-6lobac@ietf.org, "6lo@ietf.org" <6lo@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 22:53:34 -0000

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

Dale,

Thanks for your thorough review of draft-ietf-6lo-6lobac.  Sorry that it
has taken
so long to get back to you.  Can you take a look at the new version and see
if
it addresses your concerns?  Comments inline...

On Sun, Nov 13, 2016 at 2:26 PM, Dale R. Worley <worley@ariadne.com> wrote:

> Comments on draft-ietf-6lo-6lobac-06
>
> (This is probably the best-written Internet-Draft that I have ever
> read.)
>
> Technical issues:
>
> 6.  Stateless Address Autoconfiguration
>
>    This section defines how to obtain an IPv6 Interface Identifier.  The
>    general procedure for creating a MAC-address-derived IID is described
>    in [RFC4291] Appendix A, "Creating Modified EUI-64 Format Interface
>    Identifiers", as updated by [RFC7136].
>
>    The IID SHOULD NOT embed an [EUI-64] or any other globally unique
>    hardware identifier assigned to a device (see Section 12).
>
> <kel>
Section 6 has been reworked to more clearly distinguish between two types
of IIDs: "MAC-address-derived" and "semantically opaque".  The first is
recommended for link-local addresses because it enables maximum IPv6
header compression efficiency.  Since MS/TP is used primarily as a field
bus, I expect most installations will only ever involve link-local traffic
between
an MS/TP device and a local controller.

For applications where the MS/TP device is a client or server with routable
addresses, the spec strongly recommends generating a semantically opaque
IID, with 64 bits of entropy, for each global address.
</kel>

> I have a hard time correlating these two paragraphs.  At first read,
> the first paragraph describes how an IID is to be constructed from a
> MAC address, and the second one specifies that the IID should not
> contain a MAC address.  Reading more carefully, it seems that the
> intention is to refer to one of the methods of constructing IIDs that
> are listed in section 2 of RFC 7136 which construct IIDs *from* MAC
> addresses but the IIDs do not directly contain them:
>
> <kel>
The recommended method of generating IIDs from the 8-bit node address
is described, so the reference to EUI-64 has been removed as it was
confusing (and MS/TP devices don't typically have static 48- or 64-bit
hardware addresses.)
</kel>

>    In addition to IIDs formed from IEEE EUI-64 addresses, various new
>    forms of IIDs have been defined, including temporary addresses
>    [RFC4941], Cryptographically Generated Addresses (CGAs) [RFC3972]
>    [RFC4982], Hash-Based Addresses (HBAs) [RFC5535], and ISATAP
>    addresses [RFC5214].
>
> Though, strctily speaking, those formats aren't introduced due to RFC
> 7136 updating RFC 4291, but rather by RFC 4941 etc. doing so.
>
> But if my understanding is correct, it would help greatly if this text
> was revised to point more directly to the text that is relevant, as my
> reflexive behavior is to read Appendix A of RFC 4291, which only
> discusses embedding MAC addresses in IIDs.
>
> It would also help to explain what the important difference is between
> "MAC-address-derived" and "embed an [EUI-64] or other globally unique
> hardware identifier" -- I think the critical distinction is that with
> the former, knowing the MAC address is not sufficient for an attacker
> to guess the IID, but I'm left to guess that.
>
> Editorial issues:
>
> 1.  Introduction
>
>    a) MS/TP devices typically have a continuous source of power
>
> I think this isn't quite how you want to phrase it, since a battery is
> a "continuous source of power".  Perhaps "typically have mains power".
>
> 1.4.  Goals and Constraints
>
>    The primary goal of this specification is to enable IPv6 directly on
>    wired end devices in building automation and control networks by
>    leveraging existing standards to the greatest extent possible.  A
>    secondary goal is to co-exist with legacy MS/TP implementations.
>
> This doesn't seem to be as clear as it could be in a number of ways.
>
> One issue is the distinction between "primary goal" and "secondary
> goal".  Naively it seems to me that both are necessary for success,
> but as written it sounds like coexistence has in some way been
> sacrificed or compromised in order to achieve the primary goal.  But
> it seems that draft-ietf-6lo-6lobac provides for complete coexistence.
>
>    Only the minimum changes necessary to support IPv6 over MS/TP were
>    specified in BACnet [Addendum_an] (see Section 1.3).
>
> This sentence seems to mean that Addendum_an contains just enough
> changes to MS/TP to allow draft-ietf-6lo-6lobac to be written.  But
> it's hard to tell what the significance of that is -- if Addendum_an
> is *only* to support draft-ietf-6lo-6lobac, then the partitioning of
> changes between Addendum_an and draft-ietf-6lo-6lobac is arbitrary,
> and Addendum_an could have been made smaller by shifting some of its
> content into draft-ietf-6lo-6lobac.  And that contradicts the claim
> that Addendum_is "minimum".
>
> It seems that what is really meant is that Addendum_an support is
> necessary for draft-ietf-6lo-6lobac support, or perhaps that the only
> use of Addendum_an is to support draft-ietf-6lo-6lobac.
>
>    In order to co-exist with legacy devices, no changes are permitted to
>    the MS/TP addressing modes, frame header format, control frames, or
>    Master Node state machine as specified in BACnet [Clause9].
>
> Another issue is that there are three "levels", as it were, that a
> device can be designed to:
>     1. Clause9 alone
>     2. Clause9 with Addendum_an
>     3. Clause9, Addendum_an, and draft-ietf-6lo-6lobac
> I assume that the three levels are upward compatible, in that you can
> mix devices designed to all three levels on one network, and then any
> two devices will interoperate at the highest level that they share.
> But it seems that this could be stated much more clearly by just
> saying that draft-ietf-6lo-6lobac is upward-compatible with devices
> designed to Clause9 and with devices designed to Clause9 with
> Addendum_an.
>
> <kel>
ANSI/ASHRAE Standard 135-2016 was published late last year.  This
version integrates the changes that were standardized in 135-2012
Addendum an, so there's no longer any jumping back and forth between
references.

Also, I didn't make it clear (outside of 6lo wg) that I can provide a copy
of [BACnet] Clause 9 to anyone who wants to reference it in the course
of reviewing the ID.
</kel>

It's not really clear what the phrase "no changes are permitted to"
> applies to -- is it a description of draft-ietf-6lo-6lobac, or a
> warning that there are certain constraints on devices that aren't
> stated in this document?
>
> <kel>
This is a statement on how to achieve co-existence.  Hopefully the
context is clearer in the current version of the ID.
</kel>


> 2.  MS/TP Mode for IPv6
>
> Must all nodes that support IPv6 be master nodes?
>
> <kel>
Yes, slave nodes cannot initiate async transmission.  MS/TP nodes
are designed to ignore frames they don't understand (e.g. 6LoBAC).
</kel>


>    ... implement the Receive Frame state machine specified in
>    [Clause9] as extended by BACnet [Addendum_an].
>
> There seems to be an alternative use of "BACnet [Clause9]"
> vs. "[Clause9]", and also "BACnet [Addendum_an]" vs. "[Addendum_an]".
> The usage should be made consistent, and also aligned with the
> definition:
>
>    BACnet:  An ISO/ANSI/ASHRAE Standard Data Communication Protocol
>             for Building Automation and Control Networks
>
> Does "BACnet" mean just Clause9 or Clause9 plus Addendum_an, or is it
> a generic that applies to both sets of specifications?
>
> <kel>
Due to the update to the base spec, these references have all been converted
to [BACnet] Clause 9.  There is a single reference to [Addendum_an] for any
historians in the audience.  [BACnet] refers to the latest version,
ANSI/ASHRAE
Standard 135-2016.
</kel>

5.  LoBAC Adaptation Layer
>
>    Implementations MAY also support Generic Header Compression (GHC)
>    [RFC7400] for transport layer headers.  A node implementing [RFC7400]
>    MUST probe its peers for GHC support before applying GHC.
>
> This would probably read better if the second "[RFC7400]" was written
> "GHC".
>
> 6.  Stateless Address Autoconfiguration
>
>    concatenating a node's' 8-bit MS/TP MAC address to the seven octets
>
> s/node's'/node's/
>
> 9.  Multicast Address Mapping
>
>    When represented as
>    a 16-bit address in a compressed header (see Section 10), it MUST be
>    formed by padding on the left with a zero:
>
> This would read more smoothly if "it" was "the broadcast link address"
> and "a zero" was "a zero octet".
>
> 10.  Header Compression
>
>    When a 16-bit address is called for (i.e., an IEEE 802.15.4 "short
>    address") it MUST be formed by padding the MS/TP address to the left
>    with a zero:
>
> Similarly, this would read more smoothly if "a zero" was "a zero
> octet".
>
> Appendix B.  Consistent Overhead Byte Stuffing [COBS]
>
>    The minimum overhead of COBS is one octet per encoded field.  The
>    worst-case overhead in long fields is bounded to one octet per 254,
>    or less than 0.4%, as described in [COBS].
>
> This could be more informative as:
>
>    The minimum overhead of COBS is one octet per encoded field, and
>    the maximum overhead is ceiling(length/254) octets.  In the limit
>    for very long fields, the overhead is less than 0.4%.  For 1280
>    octet fields, the overhead is 0.47% and for 1500 octet fields, the
>    overhead is 0.39%.
>

<kel>
I punted on calculating percentages, assuming the reader could do the math.
I guessing it varies discretely between 50% for a 1-byte field and 0.39% for
a 254 byte field.  The salient fact is the overhead is bounded to six bytes
of
overhead for a 1500-byte MTU, but maybe I need to say that explicitly.
</kel>

>
> Appendix C.  Encoded CRC-32K [CRC32K]
>
>    BACnet [Addendum_an] specifies the CRC-32K (Koopman) polynomial.
>
> "CRC-32K" is not bound at this point.  Perhaps
>
>    BACnet [Addendum_an] specifies one of these, the CRC-32K (Koopman)
>    polynomial.
>
> <kel>
I'm pretty sure I incorporated all of your editorial changes.
</kel>

Thanks again, Kerry


> Dale
>

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

<div dir=3D"ltr">Dale,<div><br></div><div>Thanks for your thorough review o=
f draft-ietf-6lo-6lobac.=C2=A0 Sorry that it has taken</div><div>so long to=
 get back to you.=C2=A0 Can you take a look at the new version and see if</=
div><div>it addresses your concerns?=C2=A0 Comments inline...</div><div cla=
ss=3D"gmail_extra"><br><div class=3D"gmail_quote">On Sun, Nov 13, 2016 at 2=
:26 PM, Dale R. Worley <span dir=3D"ltr">&lt;<a href=3D"mailto:worley@ariad=
ne.com" target=3D"_blank">worley@ariadne.com</a>&gt;</span> wrote:<br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex">Comments on draft-ietf-6lo-6lo=
bac-06<br>
<br>
(This is probably the best-written Internet-Draft that I have ever<br>
read.)<br>
<br>
Technical issues:<br>
<br>
6.=C2=A0 Stateless Address Autoconfiguration<br>
<br>
=C2=A0 =C2=A0This section defines how to obtain an IPv6 Interface Identifie=
r.=C2=A0 The<br>
=C2=A0 =C2=A0general procedure for creating a MAC-address-derived IID is de=
scribed<br>
=C2=A0 =C2=A0in [RFC4291] Appendix A, &quot;Creating Modified EUI-64 Format=
 Interface<br>
=C2=A0 =C2=A0Identifiers&quot;, as updated by [RFC7136].<br>
<br>
=C2=A0 =C2=A0The IID SHOULD NOT embed an [EUI-64] or any other globally uni=
que<br>
=C2=A0 =C2=A0hardware identifier assigned to a device (see Section 12).<br>
<br></blockquote><div>&lt;kel&gt;</div><div>Section 6 has been reworked to =
more clearly distinguish between two types</div><div>of IIDs: &quot;MAC-add=
ress-derived&quot; and &quot;semantically opaque&quot;.=C2=A0 The first is<=
/div><div>recommended for link-local addresses because it enables maximum I=
Pv6</div><div>header compression efficiency.=C2=A0 Since MS/TP is used prim=
arily as a field</div><div>bus, I expect most installations will only ever =
involve link-local traffic between</div><div>an MS/TP device and a local co=
ntroller.</div><div><br></div><div>For applications where the MS/TP device =
is a client or server with routable</div><div>addresses, the spec strongly =
recommends generating a semantically opaque</div><div>IID, with 64 bits of =
entropy, for each global address.</div><div>&lt;/kel&gt;</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex">
I have a hard time correlating these two paragraphs.=C2=A0 At first read,<b=
r>
the first paragraph describes how an IID is to be constructed from a<br>
MAC address, and the second one specifies that the IID should not<br>
contain a MAC address.=C2=A0 Reading more carefully, it seems that the<br>
intention is to refer to one of the methods of constructing IIDs that<br>
are listed in section 2 of RFC 7136 which construct IIDs *from* MAC<br>
addresses but the IIDs do not directly contain them:<br>
<br></blockquote><div>&lt;kel&gt;</div><div>The recommended method of gener=
ating IIDs from the 8-bit node address</div><div>is described, so the refer=
ence to EUI-64 has been removed as it was</div><div>confusing (and MS/TP de=
vices don&#39;t typically have static 48- or 64-bit</div><div>hardware addr=
esses.)</div><div>&lt;/kel&gt;=C2=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
=C2=A0 =C2=A0In addition to IIDs formed from IEEE EUI-64 addresses, various=
 new<br>
=C2=A0 =C2=A0forms of IIDs have been defined, including temporary addresses=
<br>
=C2=A0 =C2=A0[RFC4941], Cryptographically Generated Addresses (CGAs) [RFC39=
72]<br>
=C2=A0 =C2=A0[RFC4982], Hash-Based Addresses (HBAs) [RFC5535], and ISATAP<b=
r>
=C2=A0 =C2=A0addresses [RFC5214].<br>
<br>
Though, strctily speaking, those formats aren&#39;t introduced due to RFC<b=
r>
7136 updating RFC 4291, but rather by RFC 4941 etc. doing so.<br>
<br>
But if my understanding is correct, it would help greatly if this text<br>
was revised to point more directly to the text that is relevant, as my<br>
reflexive behavior is to read Appendix A of RFC 4291, which only<br>
discusses embedding MAC addresses in IIDs.<br>
<br>
It would also help to explain what the important difference is between<br>
&quot;MAC-address-derived&quot; and &quot;embed an [EUI-64] or other global=
ly unique<br>
hardware identifier&quot; -- I think the critical distinction is that with<=
br>
the former, knowing the MAC address is not sufficient for an attacker<br>
to guess the IID, but I&#39;m left to guess that.<br>
<br>
Editorial issues:<br>
<br>
1.=C2=A0 Introduction<br>
<br>
=C2=A0 =C2=A0a) MS/TP devices typically have a continuous source of power<b=
r>
<br>
I think this isn&#39;t quite how you want to phrase it, since a battery is<=
br>
a &quot;continuous source of power&quot;.=C2=A0 Perhaps &quot;typically hav=
e mains power&quot;.<br>
<br>
1.4.=C2=A0 Goals and Constraints<br>
<br>
=C2=A0 =C2=A0The primary goal of this specification is to enable IPv6 direc=
tly on<br>
=C2=A0 =C2=A0wired end devices in building automation and control networks =
by<br>
=C2=A0 =C2=A0leveraging existing standards to the greatest extent possible.=
=C2=A0 A<br>
=C2=A0 =C2=A0secondary goal is to co-exist with legacy MS/TP implementation=
s.<br>
<br>
This doesn&#39;t seem to be as clear as it could be in a number of ways.<br=
>
<br>
One issue is the distinction between &quot;primary goal&quot; and &quot;sec=
ondary<br>
goal&quot;.=C2=A0 Naively it seems to me that both are necessary for succes=
s,<br>
but as written it sounds like coexistence has in some way been<br>
sacrificed or compromised in order to achieve the primary goal.=C2=A0 But<b=
r>
it seems that draft-ietf-6lo-6lobac provides for complete coexistence.<br>
<br>
=C2=A0 =C2=A0Only the minimum changes necessary to support IPv6 over MS/TP =
were<br>
=C2=A0 =C2=A0specified in BACnet [Addendum_an] (see Section 1.3).<br>
<br>
This sentence seems to mean that Addendum_an contains just enough<br>
changes to MS/TP to allow draft-ietf-6lo-6lobac to be written.=C2=A0 But<br=
>
it&#39;s hard to tell what the significance of that is -- if Addendum_an<br=
>
is *only* to support draft-ietf-6lo-6lobac, then the partitioning of<br>
changes between Addendum_an and draft-ietf-6lo-6lobac is arbitrary,<br>
and Addendum_an could have been made smaller by shifting some of its<br>
content into draft-ietf-6lo-6lobac.=C2=A0 And that contradicts the claim<br=
>
that Addendum_is &quot;minimum&quot;.<br>
<br>
It seems that what is really meant is that Addendum_an support is<br>
necessary for draft-ietf-6lo-6lobac support, or perhaps that the only<br>
use of Addendum_an is to support draft-ietf-6lo-6lobac.<br>
<br>
=C2=A0 =C2=A0In order to co-exist with legacy devices, no changes are permi=
tted to<br>
=C2=A0 =C2=A0the MS/TP addressing modes, frame header format, control frame=
s, or<br>
=C2=A0 =C2=A0Master Node state machine as specified in BACnet [Clause9].<br=
>
<br>
Another issue is that there are three &quot;levels&quot;, as it were, that =
a<br>
device can be designed to:<br>
=C2=A0 =C2=A0 1. Clause9 alone<br>
=C2=A0 =C2=A0 2. Clause9 with Addendum_an<br>
=C2=A0 =C2=A0 3. Clause9, Addendum_an, and draft-ietf-6lo-6lobac<br>
I assume that the three levels are upward compatible, in that you can<br>
mix devices designed to all three levels on one network, and then any<br>
two devices will interoperate at the highest level that they share.<br>
But it seems that this could be stated much more clearly by just<br>
saying that draft-ietf-6lo-6lobac is upward-compatible with devices<br>
designed to Clause9 and with devices designed to Clause9 with<br>
Addendum_an.<br>
<br></blockquote><div>&lt;kel&gt;</div><div>ANSI/ASHRAE Standard 135-2016 w=
as published late last year.=C2=A0 This</div><div>version integrates the ch=
anges that were standardized in 135-2012</div><div>Addendum an, so there&#3=
9;s no longer any jumping back and forth between</div><div>references.</div=
><div><br></div><div>Also, I didn&#39;t make it clear (outside of 6lo wg) t=
hat I can provide a copy</div><div>of [BACnet] Clause 9 to anyone who wants=
 to reference it in the course</div><div>of reviewing the ID.</div><div>&lt=
;/kel&gt;</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
It&#39;s not really clear what the phrase &quot;no changes are permitted to=
&quot;<br>
applies to -- is it a description of draft-ietf-6lo-6lobac, or a<br>
warning that there are certain constraints on devices that aren&#39;t<br>
stated in this document?<br>
<br></blockquote><div>&lt;kel&gt;</div><div>This is a statement on how to a=
chieve co-existence.=C2=A0 Hopefully the</div><div>context is clearer in th=
e current version of the ID.</div><div>&lt;/kel&gt;</div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">
2.=C2=A0 MS/TP Mode for IPv6<br>
<br>
Must all nodes that support IPv6 be master nodes?<br>
<br></blockquote><div>&lt;kel&gt;</div><div>Yes, slave nodes cannot initiat=
e async transmission.=C2=A0 MS/TP nodes</div><div>are designed to ignore fr=
ames they don&#39;t understand (e.g. 6LoBAC).</div><div>&lt;/kel&gt;</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
=C2=A0 =C2=A0... implement the Receive Frame state machine specified in<br>
=C2=A0 =C2=A0[Clause9] as extended by BACnet [Addendum_an].<br>
<br>
There seems to be an alternative use of &quot;BACnet [Clause9]&quot;<br>
vs. &quot;[Clause9]&quot;, and also &quot;BACnet [Addendum_an]&quot; vs. &q=
uot;[Addendum_an]&quot;.<br>
The usage should be made consistent, and also aligned with the<br>
definition:<br>
<br>
=C2=A0 =C2=A0BACnet:=C2=A0 An ISO/ANSI/ASHRAE Standard Data Communication P=
rotocol<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 for Building Automation and Contr=
ol Networks<br>
<br>
Does &quot;BACnet&quot; mean just Clause9 or Clause9 plus Addendum_an, or i=
s it<br>
a generic that applies to both sets of specifications?<br>
<br></blockquote><div>&lt;kel&gt;</div><div>Due to the update to the base s=
pec, these references have all been converted</div><div>to [BACnet] Clause =
9.=C2=A0 There is a single reference to [Addendum_an] for any</div><div>his=
torians in the audience. =C2=A0[BACnet] refers to the latest version, ANSI/=
ASHRAE</div><div>Standard 135-2016.</div><div>&lt;/kel&gt;</div><div><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
5.=C2=A0 LoBAC Adaptation Layer<br>
<br>
=C2=A0 =C2=A0Implementations MAY also support Generic Header Compression (G=
HC)<br>
=C2=A0 =C2=A0[RFC7400] for transport layer headers.=C2=A0 A node implementi=
ng [RFC7400]<br>
=C2=A0 =C2=A0MUST probe its peers for GHC support before applying GHC.<br>
<br>
This would probably read better if the second &quot;[RFC7400]&quot; was wri=
tten &quot;GHC&quot;.<br>
<br>
6.=C2=A0 Stateless Address Autoconfiguration<br>
<br>
=C2=A0 =C2=A0concatenating a node&#39;s&#39; 8-bit MS/TP MAC address to the=
 seven octets<br>
<br>
s/node&#39;s&#39;/node&#39;s/<br>
<br>
9.=C2=A0 Multicast Address Mapping<br>
<br>
=C2=A0 =C2=A0When represented as<br>
=C2=A0 =C2=A0a 16-bit address in a compressed header (see Section 10), it M=
UST be<br>
=C2=A0 =C2=A0formed by padding on the left with a zero:<br>
<br>
This would read more smoothly if &quot;it&quot; was &quot;the broadcast lin=
k address&quot;<br>
and &quot;a zero&quot; was &quot;a zero octet&quot;.<br>
<br>
10.=C2=A0 Header Compression<br>
<br>
=C2=A0 =C2=A0When a 16-bit address is called for (i.e., an IEEE 802.15.4 &q=
uot;short<br>
=C2=A0 =C2=A0address&quot;) it MUST be formed by padding the MS/TP address =
to the left<br>
=C2=A0 =C2=A0with a zero:<br>
<br>
Similarly, this would read more smoothly if &quot;a zero&quot; was &quot;a =
zero<br>
octet&quot;.<br>
<br>
Appendix B.=C2=A0 Consistent Overhead Byte Stuffing [COBS]<br>
<br>
=C2=A0 =C2=A0The minimum overhead of COBS is one octet per encoded field.=
=C2=A0 The<br>
=C2=A0 =C2=A0worst-case overhead in long fields is bounded to one octet per=
 254,<br>
=C2=A0 =C2=A0or less than 0.4%, as described in [COBS].<br>
<br>
This could be more informative as:<br>
<br>
=C2=A0 =C2=A0The minimum overhead of COBS is one octet per encoded field, a=
nd<br>
=C2=A0 =C2=A0the maximum overhead is ceiling(length/254) octets.=C2=A0 In t=
he limit<br>
=C2=A0 =C2=A0for very long fields, the overhead is less than 0.4%.=C2=A0 Fo=
r 1280<br>
=C2=A0 =C2=A0octet fields, the overhead is 0.47% and for 1500 octet fields,=
 the<br>
=C2=A0 =C2=A0overhead is 0.39%.<br></blockquote><div><br></div><div>&lt;kel=
&gt;</div><div>I punted on calculating percentages, assuming the reader cou=
ld do the math.</div><div>I guessing it varies discretely between 50% for a=
 1-byte field and 0.39% for</div><div>a 254 byte field.=C2=A0 The salient f=
act is the overhead is bounded to six bytes of</div><div>overhead for a 150=
0-byte MTU, but maybe I need to say that explicitly.</div><div>&lt;/kel&gt;=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Appendix C.=C2=A0 Encoded CRC-32K [CRC32K]<br>
<br>
=C2=A0 =C2=A0BACnet [Addendum_an] specifies the CRC-32K (Koopman) polynomia=
l.<br>
<br>
&quot;CRC-32K&quot; is not bound at this point.=C2=A0 Perhaps<br>
<br>
=C2=A0 =C2=A0BACnet [Addendum_an] specifies one of these, the CRC-32K (Koop=
man)<br>
=C2=A0 =C2=A0polynomial.<br>
<span class=3D"m_779468464667803302gmail-m_7534577338368535667HOEnZb"><font=
 color=3D"#888888"><br></font></span></blockquote><div>&lt;kel&gt;<br>I&#39=
;m pretty sure I incorporated all of your editorial changes.</div><div>&lt;=
/kel&gt;</div><div><br></div><div>Thanks again, Kerry</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><span class=3D"m_7794684=
64667803302gmail-m_7534577338368535667HOEnZb"><font color=3D"#888888">
Dale<br>
</font></span></blockquote></div><br></div></div>

--001a1149526cc37c9b05498af2a2--


From nobody Mon Feb 27 21:19:04 2017
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4867D1294BF for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 21:19: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JaqMTnvVTXDY for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 21:19:02 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 EE4C31294BA for <ietf@ietf.org>; Mon, 27 Feb 2017 21:19:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=iGrW2QkN1iawixdyl/nnYpygg/ZqsxwlfhMH7LiyfHI=;  b=jDq8g3LTDp7yQD3NFWjY2lvPf2Kji7iNpE6fxsT+PrRy49jJOrhTiiLzf82wEdN6nRw2BDTm+owShPGxp1Wn1wtwtKoTBAyEOEYGI8vCNU/tjtHx28oNuElCLqpiG7cKDYGWyXFchygrNKUj2q2kvY8pw6jTzwgsxIP/CZHRl4A=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1ciaBQ-0003U7-Rq; Tue, 28 Feb 2017 05:18:44 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id CBD35C000C1; Tue, 28 Feb 2017 00:18:43 -0500 (EST)
Date: Tue, 28 Feb 2017 00:18:43 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: willi uebelherr <willi.uebelherr@riseup.net>
Subject: Re: Mailing list membership.
Message-ID: <20170228051843.wkh5skthuyrs5pwz@thunk.org>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xX0h0P2Zvl2uwFoCJ68cFJ0KEkk>
Cc: IETF discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 05:19:03 -0000

On Mon, Feb 27, 2017 at 05:36:11PM -0300, willi uebelherr wrote:
> 
> Dear Khaled,
> 
> you wrote:
> "... but don't forget that this is a repeating issue ..."
> 
> I agree with that and therefore, never i will move in a private space
> outside of the list. This is a administration question for the list. And all
> list members need the possibility to read our discussion. Only then the
> other members in the list can participate and explain her experience.
> 
> Maybe, there are more poeple with pracitical experience with mailman and his
> modules. But the first step is always to open the discussion and stop the
> private hidden spaces.

Or, people who are using broken, non-standards compliant mail systems
can move to ones which are compatible with internet mailing lists....

    	    	       	   	      	   - Ted


From nobody Mon Feb 27 23:45:46 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56AF51289B0 for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 23:45:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.821
X-Spam-Level: 
X-Spam-Status: No, score=-0.821 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_DYNAMIC=1.08, SPF_PASS=-0.001] autolearn=no autolearn_force=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 cyloK-Ti6rOU for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 23:45:43 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 402831293F4 for <ietf@ietf.org>; Mon, 27 Feb 2017 23:45:42 -0800 (PST)
Received: (qmail 17502 invoked from network); 28 Feb 2017 07:45:41 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 28 Feb 2017 07:45:41 -0000
Date: 28 Feb 2017 07:45:19 -0000
Message-ID: <20170228074519.7786.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
In-Reply-To: <CAA-e5Q0EZ6TExiJz+U0oicpst5iVteCq4JUWXNSQHVA24kOgcA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4TBhXj5Zgz1_GCepfY-toAJntX4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 07:45:44 -0000

In article <CAA-e5Q0EZ6TExiJz+U0oicpst5iVteCq4JUWXNSQHVA24kOgcA@mail.gmail.com> you write:
>I think we can just say "children under 13 must obtain consent from their
>parents or legal guardians". We should be fine in terms of COPPA if parents
>agree with the release of personal information.

We have no process to obtain, verify, or record parental consent.
Unless someone anticipates an influx of middle school kids
to the IETF, please leave the language alone.

Note that children can read IETF stuff all they want -- they just
can't send messages in.

R's,
John


From nobody Tue Feb 28 00:01:12 2017
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55871294DA for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 00:01:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.302
X-Spam-Level: 
X-Spam-Status: No, score=-4.302 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_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fohgA3OHNoL1 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 00:01:09 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B71251289B0 for <ietf@ietf.org>; Tue, 28 Feb 2017 00:01:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 4AAC0BEAA; Tue, 28 Feb 2017 08:01:07 +0000 (GMT)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UqoAScnPK_oF; Tue, 28 Feb 2017 08:01:01 +0000 (GMT)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 95A22BE79; Tue, 28 Feb 2017 08:01:00 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1488268861; bh=JNB1O3HV7x5dMmVl4CQ9EZrVGyh9Lyeba9f0evW593M=; h=Subject:To:References:From:Date:In-Reply-To:From; b=xRGw9/LUl50iodjPBzm20bekGVMEz7t6utahtwiWX08LEA/29XSPX0B4zAll9SgZ0 VSKUyHiRdWHpmigE1MonewNwCVg8rnP3TCMWmy+1GGlR8FrWzmZvr0OvVq/WDw27A6 YMI9uNzidAQUnria7/A37xeZUjPRM69SR9efywPg=
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20170228074519.7786.qmail@ary.lan>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <0657258a-8690-03fa-9a00-3e8424629d0b@cs.tcd.ie>
Date: Tue, 28 Feb 2017 08:00:59 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <20170228074519.7786.qmail@ary.lan>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PjaVjoXrWQNWtXD9BQSjA3tbholhJbRqa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Io2uoL1Itr92vYxHKifntVhPmA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 08:01:12 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PjaVjoXrWQNWtXD9BQSjA3tbholhJbRqa
Content-Type: multipart/mixed; boundary="bhquGup5fHatQ20vucbBgkAXlwm3EmuHl";
 protected-headers="v1"
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Message-ID: <0657258a-8690-03fa-9a00-3e8424629d0b@cs.tcd.ie>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
References: <20170228074519.7786.qmail@ary.lan>
In-Reply-To: <20170228074519.7786.qmail@ary.lan>

--bhquGup5fHatQ20vucbBgkAXlwm3EmuHl
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



On 28/02/17 07:45, John Levine wrote:
> In article=20
> <CAA-e5Q0EZ6TExiJz+U0oicpst5iVteCq4JUWXNSQHVA24kOgcA@mail.gmail.com>=20
> you write:
>> I think we can just say "children under 13 must obtain consent
>> from their parents or legal guardians". We should be fine in terms
>> of COPPA if parents agree with the release of personal
>> information.
>=20
> We have no process to obtain, verify, or record parental consent.=20
> Unless someone anticipates an influx of middle school kids to the=20
> IETF, please leave the language alone.
>=20
> Note that children can read IETF stuff all they want -- they just=20
> can't send messages in.

Let me try once more. The change I suggest to the IAOC IS:

OLD:

Our websites are not intended for use by children under 13 years old.
We do not knowingly collect personally identifiable information from, or
target our websites to, children under the age of 13.  In accordance
with the United States Children=E2=80=99s Online Privacy Protection Act o=
f 1998,
if we discover that a child under 13 has provided us with personally
identifiable information, without the consent and participation of a
parent or guardian, we will remove it from our systems.

NEW:

Our websites are not aimed at children under 13 years old.
We do not knowingly collect personally identifiable information from, or
target our websites to, children under the age of 13.  In accordance
with the United States Children=E2=80=99s Online Privacy Protection Act o=
f 1998,
if we discover that a child under 13 has provided us with personally
identifiable information, without the consent and participation of a
parent or guardian, we will remove it from our systems.

My reason is that we do in fact intend that our public content
could be used by anyone capable of understanding that content,
independent of age. We just don't specifically include or
exclude or aim to deal with 12 year olds, nor Irish people, nor
any other category.

Perhaps there's a better phrase than "aimed at" but "intended
for" is wrong as I read it. (To save you some time, there's only
that one change in the OLD/NEW above.)

Cheers,
S

>=20
> R's, John
>=20
>=20


--bhquGup5fHatQ20vucbBgkAXlwm3EmuHl--

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

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJYtS48AAoJEC88hzaAX42iXMMH/jpyJKjUpUwO6W5yAEs8xD1o
iVVpqw6IgBFDfYBWejHCRyA/ahybHQVIdxVWmypRNbI1HAPDWR0/66r8rB8i7Uzm
Rxg2W1y/Fa1TGdxxZv4mQyYaFFmQUG0RISriW7C4la2ZW82DZMtIZ6KX0YW0Yf1I
j8L6CiSxaZVr6In+zMVO76I5b/Q/IWjaeYmmjLIeSfupamSoK/FYCk8cdNuOShqF
uoHA2QXgPLfumM9gGiqu5MnQtZ2cJyJzBadev2bfcamTd8W7hxUYXzPMECr4gm8P
/ewbmCWlx11k0dGwbrQwiMuk9fNn1qAaTPoSxIT49WC8fLzQfJWTF8wzkST6eww=
=m2ww
-----END PGP SIGNATURE-----

--PjaVjoXrWQNWtXD9BQSjA3tbholhJbRqa--


From nobody Tue Feb 28 03:11:54 2017
Return-Path: <weihaw@google.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31DF4129516 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 03:11:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FD1U-DoToyYW for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 03:11:50 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::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 7321D12950F for <ietf@ietf.org>; Tue, 28 Feb 2017 03:11:50 -0800 (PST)
Received: by mail-oi0-x231.google.com with SMTP id m124so4140508oig.1 for <ietf@ietf.org>; Tue, 28 Feb 2017 03:11:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=fMSnVllrwhdu4InDGENV7I9/UZSQ8A47sDQaZAERclo=; b=u3jU2J1ex6PrS2tsXIokcNaFbYxb8eJ9shH9kgO76hGaaI5RbS5Cj70CrOXyvLvETQ mtNO52g6hKno9/g0ewQ6ky8DjAl+uvzxn5OnUBuNuRuqWJcekQpP+0MCiviI84dcgHY4 5Bf57Lzu2sbdfVlsazBZn6RDHriQdBQm+ZS7smOry3whIIzbDJf3MLjs47R08/bkOZv9 dP0cMJWdO+WFy+gAF3EFariD/VMmRcFvJbdKGWrQL4GbYLTX4WjEFi5oJhmjbheZ01I/ bpzSq3X64E6Uzq2xXVKMU4vRDGgfmDx+9NaWFwu4pld6xy5SeyXSlhSOW3jf3IcMiRr+ 4YXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=fMSnVllrwhdu4InDGENV7I9/UZSQ8A47sDQaZAERclo=; b=F2s/YIhGyrwzLeZCwMcX7dXKVsyt0ntaz9RhbSwGlJJYqFOTqHb3g6MP1wbW31edJp +usQCRhhna2OCOt408YQcobHyf1KVwNx7DkLHEePq6LsPR8uuGYDilwX+O1vNVwk1Bjn rSeOJOV8Tkg2g44tjl3HW+KfWpmK9uwXeE5+BUxdivpSiHQCn5jpeRDe9SwmYy/HRujm FBr0O2vfo3mGww8OXFej5+Qv91MFAAyVdOq386xrO8YM9zUwP4Qmo6oUOSYnfBOSVwQK CjkUrlyTvMBgut5gyRxRYQ/dTabGwaVHSzSENl/xvH9yv9qp58nOECpQ85PYL8mfsGsc zSqw==
X-Gm-Message-State: AMke39ndytTz67n5RPAboZWegWRLL2Mp0hMFiG69T7JHeDGZIyRpX+Qcm5UDrchBi/SNdp6908Npq+IimNkk1k7r
X-Received: by 10.202.108.212 with SMTP id h203mr887658oic.129.1488280309068;  Tue, 28 Feb 2017 03:11:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.3.108 with HTTP; Tue, 28 Feb 2017 03:11:47 -0800 (PST)
In-Reply-To: <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org>
From: Wei Chuang <weihaw@google.com>
Date: Tue, 28 Feb 2017 03:11:47 -0800
Message-ID: <CAAFsWK2h1phbNhwxx+q5X_PPKe7OrFBC1ScmP91Z=PLxqwEk-Q@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
To: IETF general list <ietf@ietf.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="001a1142ef382a8644054995436a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_6NO1-4KJVIKsfetcuUJ5Dc92qg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 11:11:53 -0000

--001a1142ef382a8644054995436a
Content-Type: multipart/alternative; boundary=001a1142ef38264160054995433a

--001a1142ef38264160054995433a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Thu, Feb 16, 2017 at 10:26 AM, Viktor Dukhovni <ietf-dane@dukhovni.org>
wrote:

>
> > On Feb 16, 2017, at 10:30 AM, Wei Chuang <weihaw@google.com> wrote:
> >
> >> How about if a CA with only rfc822Name constraints can't issue certs
> >> with SmtpUTF8Names at all, and of course vice versa.  If you want both
> >> kinds of names, the CA has to constrain both.
> >
> > I had asked a few folks at Google for an opinion about the name
> constraints.
> > Let me post Ryan Sleevi's (CC'ed) opinion:
> >
> > https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg
> > [the above] basically says option 3 [the acceptable approach of the 3],
> > but unfortunately suffers from 'legacy' - namely, you cannot assume that
> > all rfc822Name clients will be updated to support SmtpUtf8Name, and short
> > of marking it critical (which would mean its undeployable), you can't
> > assume that an SmtpUtf8Name nameConstraint will constrain an rfc822Name.
>
> Given that rfc822Name is a well-known legacy element, while SmtpUtf8Name
> is a novel element, the prescription can be asymmetric.  Specifically,
> all that's really needed (in the simpler model proposed by John) is
> to disallow SmtpUtf8Name altnames when (only) rfc822Name constraints
> are present.
>
> The converse is not required, a parent CA that is SmtpUtf8Name aware
> and wants to issue a child CA with SmtpUtf8Name constraints can and
> should also include appropriate rfc822Name constraints that ensure
> that the desired SmtpUtf8Name constraints are not bypassed via
> unauthorized rfc822Name altnames.
>
> The rfc822Name constraints can either permit only equivalent domain
> names (LDH or A-label forms), or, if no rfc822Name can be compatible
> with the SmtpUtf8Name constraints, permit only something like
> "nouser@nodomain.invalid", thereby excluding all valid rfc822 addresses.
>
> --
>         Viktor.
>

Hi Viktor and everyone else on the thread,

Apologies about being pedantic.  If we specify the CA name constraints as
you describe above with the asymmetric requirements on SmtpUtf8Name, are
you okay with the draft's position on keeping separate name constraint
processing for rfc822Name and SmtpUtf8Name types?  In other words the above
is proposed to be the resolution for the issue raised in your email Feb
11th, second email, para 1-3 i.e. preventing evasion of name constraints.

thanks,
-Wei

--001a1142ef38264160054995433a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Feb 16, 2017 at 10:26 AM, Viktor Dukhovni <span dir="ltr">&lt;<a href="mailto:ietf-dane@dukhovni.org" target="_blank">ietf-dane@dukhovni.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
&gt; On Feb 16, 2017, at 10:30 AM, Wei Chuang &lt;<a href="mailto:weihaw@google.com">weihaw@google.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; How about if a CA with only rfc822Name constraints can&#39;t issue certs<br>
&gt;&gt; with SmtpUTF8Names at all, and of course vice versa.  If you want both<br>
&gt;&gt; kinds of names, the CA has to constrain both.<br>
&gt;<br>
</span><span class="">&gt; I had asked a few folks at Google for an opinion about the name constraints.<br>
&gt; Let me post Ryan Sleevi&#39;s (CC&#39;ed) opinion:<br>
&gt;<br>
&gt; <a href="https://mailarchive.ietf.org/arch/msg/ietf/ngUOjvCHubjcyiG4uZ0w16-5-fg" rel="noreferrer" target="_blank">https://mailarchive.ietf.org/<wbr>arch/msg/ietf/<wbr>ngUOjvCHubjcyiG4uZ0w16-5-fg</a><br>
&gt; [the above] basically says option 3 [the acceptable approach of the 3],<br>
&gt; but unfortunately suffers from &#39;legacy&#39; - namely, you cannot assume that<br>
&gt; all rfc822Name clients will be updated to support SmtpUtf8Name, and short<br>
&gt; of marking it critical (which would mean its undeployable), you can&#39;t<br>
&gt; assume that an SmtpUtf8Name nameConstraint will constrain an rfc822Name.<br>
<br>
</span>Given that rfc822Name is a well-known legacy element, while SmtpUtf8Name<br>
is a novel element, the prescription can be asymmetric.  Specifically,<br>
all that&#39;s really needed (in the simpler model proposed by John) is<br>
to disallow SmtpUtf8Name altnames when (only) rfc822Name constraints<br>
are present.<br>
<br>
The converse is not required, a parent CA that is SmtpUtf8Name aware<br>
and wants to issue a child CA with SmtpUtf8Name constraints can and<br>
should also include appropriate rfc822Name constraints that ensure<br>
that the desired SmtpUtf8Name constraints are not bypassed via<br>
unauthorized rfc822Name altnames.<br>
<br>
The rfc822Name constraints can either permit only equivalent domain<br>
names (LDH or A-label forms), or, if no rfc822Name can be compatible<br>
with the SmtpUtf8Name constraints, permit only something like<br>
&quot;nouser@nodomain.invalid&quot;, thereby excluding all valid rfc822 addresses.<br>
<span class="CSS_CV_TRIMMABLE_"><font color="#888888"><br>
--<br>
        Viktor.<br>
</font></span></blockquote></div><br></div><div class="gmail_extra">Hi Viktor and everyone else on the thread,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Apologies about being pedantic.  If we specify the CA name constraints as you describe above with the asymmetric requirements on SmtpUtf8Name, are you okay with the draft&#39;s position on keeping separate name constraint processing for rfc822Name and SmtpUtf8Name types?  In other words the above is proposed to be the resolution for the issue raised in your email Feb 11th, second email, para 1-3 i.e. preventing evasion of name constraints.  </div><div class="gmail_extra"><br></div><div class="gmail_extra">thanks,</div><div class="gmail_extra">-Wei</div><div class="gmail_extra"><br></div></div>

--001a1142ef38264160054995433a--

--001a1142ef382a8644054995436a
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIIS5wYJKoZIhvcNAQcCoIIS2DCCEtQCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGg
ghBNMIIEXDCCA0SgAwIBAgIOSBtqDm4P/739RPqw/wcwDQYJKoZIhvcNAQELBQAwZDELMAkGA1UE
BhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24gbnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVy
c29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hBMjU2IC0gRzIwHhcNMTYwNjE1MDAwMDAwWhcNMjEw
NjE1MDAwMDAwWjBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xvYmFsU2lnbiBudi1zYTEiMCAG
A1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC
AQoCggEBALR23lKtjlZW/17kthzYcMHHKFgywfc4vLIjfq42NmMWbXkNUabIgS8KX4PnIFsTlD6F
GO2fqnsTygvYPFBSMX4OCFtJXoikP2CQlEvO7WooyE94tqmqD+w0YtyP2IB5j4KvOIeNv1Gbnnes
BIUWLFxs1ERvYDhmk+OrvW7Vd8ZfpRJj71Rb+QQsUpkyTySaqALXnyztTDp1L5d1bABJN/bJbEU3
Hf5FLrANmognIu+Npty6GrA6p3yKELzTsilOFmYNWg7L838NS2JbFOndl+ce89gM36CW7vyhszi6
6LqqzJL8MsmkP53GGhf11YMP9EkmawYouMDP/PwQYhIiUO0CAwEAAaOCASIwggEeMA4GA1UdDwEB
/wQEAwIBBjAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwEgYDVR0TAQH/BAgwBgEB/wIB
ADAdBgNVHQ4EFgQUyzgSsMeZwHiSjLMhleb0JmLA4D8wHwYDVR0jBBgwFoAUJiSSix/TRK+xsBtt
r+500ox4AAMwSwYDVR0fBEQwQjBAoD6gPIY6aHR0cDovL2NybC5nbG9iYWxzaWduLmNvbS9ncy9n
c3BlcnNvbmFsc2lnbnB0bnJzc2hhMmcyLmNybDBMBgNVHSAERTBDMEEGCSsGAQQBoDIBKDA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzANBgkqhkiG
9w0BAQsFAAOCAQEACskdySGYIOi63wgeTmljjA5BHHN9uLuAMHotXgbYeGVrz7+DkFNgWRQ/dNse
Qa4e+FeHWq2fu73SamhAQyLigNKZF7ZzHPUkSpSTjQqVzbyDaFHtRBAwuACuymaOWOWPePZXOH9x
t4HPwRQuur57RKiEm1F6/YJVQ5UTkzAyPoeND/y1GzXS4kjhVuoOQX3GfXDZdwoN8jMYBZTO0H5h
isymlIl6aot0E5KIKqosW6mhupdkS1ZZPp4WXR4frybSkLejjmkTYCTUmh9DuvKEQ1Ge7siwsWgA
NS1Ln+uvIuObpbNaeAyMZY0U5R/OyIDaq+m9KXPYvrCZ0TCLbcKuRzCCBB4wggMGoAMCAQICCwQA
AAAAATGJxkCyMA0GCSqGSIb3DQEBCwUAMEwxIDAeBgNVBAsTF0dsb2JhbFNpZ24gUm9vdCBDQSAt
IFIzMRMwEQYDVQQKEwpHbG9iYWxTaWduMRMwEQYDVQQDEwpHbG9iYWxTaWduMB4XDTExMDgwMjEw
MDAwMFoXDTI5MDMyOTEwMDAwMFowZDELMAkGA1UEBhMCQkUxGTAXBgNVBAoTEEdsb2JhbFNpZ24g
bnYtc2ExOjA4BgNVBAMTMUdsb2JhbFNpZ24gUGVyc29uYWxTaWduIFBhcnRuZXJzIENBIC0gU0hB
MjU2IC0gRzIwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCg/hRKosYAGP+P7mIdq5NB
Kr3J0tg+8lPATlgp+F6W9CeIvnXRGUvdniO+BQnKxnX6RsC3AnE0hUUKRaM9/RDDWldYw35K+sge
C8fWXvIbcYLXxWkXz+Hbxh0GXG61Evqux6i2sKeKvMr4s9BaN09cqJ/wF6KuP9jSyWcyY+IgL6u2
52my5UzYhnbf7D7IcC372bfhwM92n6r5hJx3r++rQEMHXlp/G9J3fftgsD1bzS7J/uHMFpr4MXua
eoiMLV5gdmo0sQg23j4pihyFlAkkHHn4usPJ3EePw7ewQT6BUTFyvmEB+KDoi7T4RCAZDstgfpzD
rR/TNwrK8/FXoqnFAgMBAAGjgegwgeUwDgYDVR0PAQH/BAQDAgEGMBIGA1UdEwEB/wQIMAYBAf8C
AQEwHQYDVR0OBBYEFCYkkosf00SvsbAbba/udNKMeAADMEcGA1UdIARAMD4wPAYEVR0gADA0MDIG
CCsGAQUFBwIBFiZodHRwczovL3d3dy5nbG9iYWxzaWduLmNvbS9yZXBvc2l0b3J5LzA2BgNVHR8E
LzAtMCugKaAnhiVodHRwOi8vY3JsLmdsb2JhbHNpZ24ubmV0L3Jvb3QtcjMuY3JsMB8GA1UdIwQY
MBaAFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQACAFVjHihZCV/IqJYt
7Nig/xek+9g0dmv1oQNGYI1WWeqHcMAV1h7cheKNr4EOANNvJWtAkoQz+076Sqnq0Puxwymj0/+e
oQJ8GRODG9pxlSn3kysh7f+kotX7pYX5moUa0xq3TCjjYsF3G17E27qvn8SJwDsgEImnhXVT5vb7
qBYKadFizPzKPmwsJQDPKX58XmPxMcZ1tG77xCQEXrtABhYC3NBhu8+c5UoinLpBQC1iBnNpNwXT
Lmd4nQdf9HCijG1e8myt78VP+QSwsaDT7LVcLT2oDPVggjhVcwljw3ePDwfGP9kNrR+lc8XrfClk
WbrdhC2o4Ui28dtIVHd3MIIDXzCCAkegAwIBAgILBAAAAAABIVhTCKIwDQYJKoZIhvcNAQELBQAw
TDEgMB4GA1UECxMXR2xvYmFsU2lnbiBSb290IENBIC0gUjMxEzARBgNVBAoTCkdsb2JhbFNpZ24x
EzARBgNVBAMTCkdsb2JhbFNpZ24wHhcNMDkwMzE4MTAwMDAwWhcNMjkwMzE4MTAwMDAwWjBMMSAw
HgYDVQQLExdHbG9iYWxTaWduIFJvb3QgQ0EgLSBSMzETMBEGA1UEChMKR2xvYmFsU2lnbjETMBEG
A1UEAxMKR2xvYmFsU2lnbjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMwldpB5Bngi
FvXAg7aEyiie/QV2EcWtiHL8RgJDx7KKnQRfJMsuS+FggkbhUqsMgUdwbN1k0ev1LKMPgj0MK66X
17YUhhB5uzsTgHeMCOFJ0mpiLx9e+pZo34knlTifBtc+ycsmWQ1z3rDI6SYOgxXG71uL0gRgykmm
KPZpO/bLyCiR5Z2KYVc3rHQU3HTgOu5yLy6c+9C7v/U9AOEGM+iCK65TpjoWc4zdQQ4gOsC0p6Hp
sk+QLjJg6VfLuQSSaGjlOCZgdbKfd/+RFO+uIEn8rUAVSNECMWEZXriX7613t2Saer9fwRPvm2L7
DWzgVGkWqQPabumDk3F2xmmFghcCAwEAAaNCMEAwDgYDVR0PAQH/BAQDAgEGMA8GA1UdEwEB/wQF
MAMBAf8wHQYDVR0OBBYEFI/wS3+oLkUkrk1Q+mOai97i3Ru8MA0GCSqGSIb3DQEBCwUAA4IBAQBL
QNvAUKr+yAzv95ZURUm7lgAJQayzE4aGKAczymvmdLm6AC2upArT9fHxD4q/c2dKg8dEe3jgr25s
bwMpjjM5RcOO5LlXbKr8EpbsU8Yt5CRsuZRj+9xTaGdWPoO4zzUhw8lo/s7awlOqzJCK6fBdRoyV
3XpYKBovHd7NADdBj+1EbddTKJd+82cEHhXXipa0095MJ6RMG3NzdvQXmcIfeg7jLQitChws/zyr
VQ4PkX4268NXSb7hLi18YIvDQVETI53O9zJrlAGomecsMx86OyXShkDOOyyGeMlhLxS67ttVb9+E
7gUJTb0o2HLO02JQZR7rkpeDMdmztcpHWD9fMIIEZDCCA0ygAwIBAgIMZN1N4N3KNCF5ZBTQMA0G
CSqGSIb3DQEBCwUAMEwxCzAJBgNVBAYTAkJFMRkwFwYDVQQKExBHbG9iYWxTaWduIG52LXNhMSIw
IAYDVQQDExlHbG9iYWxTaWduIEhWIFMvTUlNRSBDQSAxMB4XDTE2MTAyNjE4NDI0NVoXDTE3MDQy
NDE4NDI0NVowIjEgMB4GCSqGSIb3DQEJAQwRd2VpaGF3QGdvb2dsZS5jb20wggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDiNpZ5E2IqcxktrcD1X5jWksphe1Ur882fsZM99Y4hiVugSVOb
zIZIxoh3ckmGpUFyK1un6AU9Rxq9GSSkRskGAaSGrGcy7ncPi7Z1NlOJN25oXFmzituZsZeYIs0S
QqT9hlDpLGc95r1CpsuTlaIB8m9Uvi+H6sGecVb2TOuGbRViQIWWf5GWk2AlJYhBFyJv7regqVa8
v3fx6SLkn/hIzBQf7xpVJzG6kAa09ZE0LoPdp5YV+Hv38EqDOWjm+g6Qbh1NADhdGpbmQDp9kdlm
6WZjCMwryQukdCypLKI2BPa08F18LZktaQNlJ2s7VxDJj2ozxomeBpSK6rxSxLAjAgMBAAGjggFu
MIIBajAcBgNVHREEFTATgRF3ZWloYXdAZ29vZ2xlLmNvbTBQBggrBgEFBQcBAQREMEIwQAYIKwYB
BQUHMAKGNGh0dHA6Ly9zZWN1cmUuZ2xvYmFsc2lnbi5jb20vY2FjZXJ0L2dzaHZzbWltZWNhMS5j
cnQwHQYDVR0OBBYEFIMwgx+nNfYP3NyOZfiHYydFyNdQMB8GA1UdIwQYMBaAFMs4ErDHmcB4koyz
IZXm9CZiwOA/MEwGA1UdIARFMEMwQQYJKwYBBAGgMgEoMDQwMgYIKwYBBQUHAgEWJmh0dHBzOi8v
d3d3Lmdsb2JhbHNpZ24uY29tL3JlcG9zaXRvcnkvMDsGA1UdHwQ0MDIwMKAuoCyGKmh0dHA6Ly9j
cmwuZ2xvYmFsc2lnbi5jb20vZ3NodnNtaW1lY2ExLmNybDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0l
BBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMA0GCSqGSIb3DQEBCwUAA4IBAQAO0J2vGX8ye90RegS3
HS+OE2hGEdDYJlR+S9ZSpla5AC9eejUKUc9JZR3y0ocGeQ3FQyXjM5/azBblqz/ajAbj2Fxuge45
SdRXrItDhAGWtQNl3utu2Uhf4y3re4ZRjApnhEBBX1l0E2BJuHf8MmqMhVU70Ko6Lk3lyPxnBeWo
Q3tG2He3CNCkq/SDImq9vf8CNoxKxEkCP+kI+/NaCh5peLygU1h7Dc0ryWAcrxRWn8GUeEOg28MI
vpwttw54cNR4YJYJVuiXCNc6PqkT/JxCiMvHS1woXJuET6QZSPtpNtvhNu90sV68Q7b2m6Vp8QTn
xbzoEIHhiQWIcfphXjbeMYICXjCCAloCAQEwXDBMMQswCQYDVQQGEwJCRTEZMBcGA1UEChMQR2xv
YmFsU2lnbiBudi1zYTEiMCAGA1UEAxMZR2xvYmFsU2lnbiBIViBTL01JTUUgQ0EgMQIMZN1N4N3K
NCF5ZBTQMA0GCWCGSAFlAwQCAQUAoIHUMC8GCSqGSIb3DQEJBDEiBCBCaGFJrhMH4vm2lqhVdxaY
WoilHmYFnBY5I3QxTlr+bDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEP
Fw0xNzAyMjgxMTExNDlaMGkGCSqGSIb3DQEJDzFcMFowCwYJYIZIAWUDBAEqMAsGCWCGSAFlAwQB
FjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwCwYJKoZIhvcNAQEKMAsGCSqGSIb3DQEBBzALBglg
hkgBZQMEAgEwDQYJKoZIhvcNAQEBBQAEggEAnkvN2JQ+bUKb+ZN40/TL72C18m1HHVuqVxrKd03w
9eAGOh5ys+Zd1uU6AdCJuQr+DwvGNz2oFlEiDV7SDN45gmyftfnTRq6f20nYHFPdnuaZ0MIiWPYz
48cpWv5or/yGLk6CE/tYK+wnirXWbDnSfgnP8Dly6HzL0kpnvsjoYOByk3K8/J1klHaGExGVo9KE
+s7AyLocepXRLG5TlsSWEYZ6V7ZPxHKKFkPma36yQcjimZIAgwnCzJoh8aCvhSpfU2cHpRNX8DAe
jjeC7trv0HS7weIQBP3DCnRA3ufzl4e9jAt0TclXbkF9+NLGpIeCHNN126/Um0jQfkZHqNP0tQ==
--001a1142ef382a8644054995436a--


From nobody Tue Feb 28 08:10:54 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AED81295D7 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 08:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.921
X-Spam-Level: 
X-Spam-Status: No, score=-0.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, KHOP_DYNAMIC=1.08, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=exMI8a3p; dkim=pass (1536-bit key) header.d=taugh.com header.b=ZnZLDefF
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8-yJrPn_WtEx for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 08:10:51 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BABFB1294F7 for <ietf@ietf.org>; Tue, 28 Feb 2017 08:10:50 -0800 (PST)
Received: (qmail 4233 invoked from network); 28 Feb 2017 16:10:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1087.58b5a109.k1702; bh=uvu8DUEWKbqQnGEjI+me0siFJqU5in8tAnLAXWaQjq0=; b=exMI8a3po6mEUMimUvf4SlwGlkyxiQYhf/av6M5+1YT3IARLk8PRdej2eWdWkrEIY3+OpKBQ9c+JU2vN098Pvemv3VUiCJK9/a8JyyT33e0kc+rdRp99VqaZyuCkUBlvA9GEkr559vj33gWC3bfSEE08oQg7wq+YThBPmDHUp1Jpztz2nOJrIHEFNAjv33APm9RFD3xx4ZxLegkGmNtLE5/UFFHYoP1qATAXBUl5OodqUfcx3gWvIZRFQBV3E7ww
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=1087.58b5a109.k1702; bh=uvu8DUEWKbqQnGEjI+me0siFJqU5in8tAnLAXWaQjq0=; b=ZnZLDefF0L6VoYKwbYcptMP0nN8Ew1cFIs1PPjbuCDmr4isyf3a9jA3N2v8esMZkaV8lHiL8enlDzVDtqw8qYLVPUsbDc4sxRgEdmw7ndFZBcI2V8vOHsoBkxrilrRLAbN4ja+q9g56IamIdDouUmrsEA7HtcMP0Qdm3Tu/IFJ4ac1rvDlwFCaradzb74R+kWUaaQxsDXUnr34Y6EmmXHylf8w5ORJpFcwV5QHCeL4pSz5L7J2Bw3tBQSqe6iO1N
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 28 Feb 2017 16:10:49 -0000
Date: 28 Feb 2017 08:10:48 -0800
Message-ID: <alpine.OSX.2.20.1702280807180.5224@ary.local>
From: "John R Levine" <johnl@taugh.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Subject: Re: Proposed IETF Statement Concerning Personal Data for Review
In-Reply-To: <0657258a-8690-03fa-9a00-3e8424629d0b@cs.tcd.ie>
References: <20170228074519.7786.qmail@ary.lan> <0657258a-8690-03fa-9a00-3e8424629d0b@cs.tcd.ie>
User-Agent: Alpine 2.20 (OSX 67 2015-01-07)
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="0-415671181-1488298250=:5224"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7CQqmjmX533hqBE3NbjNuKi164g>
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 16:10:53 -0000

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

--0-415671181-1488298250=:5224
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

> Let me try once more. The change I suggest to the IAOC IS:

Really, no.

Keep in mind that COPPA is only concerned with PII, so the only thing it 
would affect is whether 12 year olds can join mailing lists and create 
datatracker accounts.  We do not know or care who is looking at the web 
sites and mail archives.

If you say you allow under-13's to sign up at all, COPPA deliberately 
requires all sorts of record keeping that in practice means we'd have to 
hire one of a handful of specialist COPPA compliance firms.  It is not 
adequate to say we asked her mother who said it's OK.

Just leave the boilerplate alone.  It avoids significant legal exposure, 
and in practice limits nothing.

R's,
John

> We do not knowingly collect personally identifiable information from, or
> target our websites to, children under the age of 13.  In accordance
> with the United States Children’s Online Privacy Protection Act of 1998,
> if we discover that a child under 13 has provided us with personally
> identifiable information, without the consent and participation of a
> parent or guardian, we will remove it from our systems.

--0-415671181-1488298250=:5224--


From nobody Tue Feb 28 08:30:42 2017
Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E73C2129621 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 08:30:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=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 LHsy1U6lNlXO for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 08:30:39 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [108.5.242.66]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E64C0129628 for <ietf@ietf.org>; Tue, 28 Feb 2017 08:30:38 -0800 (PST)
Received: from vpro.lan (cpe-74-71-8-253.nyc.res.rr.com [74.71.8.253]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 236217A330A for <ietf@ietf.org>; Tue, 28 Feb 2017 16:30:38 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-ietf-lamps-eai-addresses-05.txt> (Internationalized Email Addresses in X.509 certificates) to Proposed Standard
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <CAAFsWK2h1phbNhwxx+q5X_PPKe7OrFBC1ScmP91Z=PLxqwEk-Q@mail.gmail.com>
Date: Tue, 28 Feb 2017 11:30:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <437CDE7D-0261-474A-B752-6A5403C34B23@dukhovni.org>
References: <alpine.OSX.2.20.1702111606270.2386@ary.qy> <CAAFsWK0KoeeHeKxay=j=NR8AqbzaHXtjNoQNQqRHwUNT3-Pe_Q@mail.gmail.com> <D237E866-CEC3-4A3C-9D5E-0D1B48F1799B@dukhovni.org> <CAAFsWK2h1phbNhwxx+q5X_PPKe7OrFBC1ScmP91Z=PLxqwEk-Q@mail.gmail.com>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ky0K2re5Be5v-jvCJzv0mjgjIk4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 16:30:41 -0000

> On Feb 28, 2017, at 6:11 AM, Wei Chuang <weihaw@google.com> wrote:
>=20
>> Given that rfc822Name is a well-known legacy element, while =
SmtpUtf8Name
>> is a novel element, the prescription can be asymmetric.  =
Specifically,
>> all that's really needed (in the simpler model proposed by John) is
>> to disallow SmtpUtf8Name altnames when (only) rfc822Name constraints
>> are present.
>>=20
>> The converse is not required, a parent CA that is SmtpUtf8Name aware
>> and wants to issue a child CA with SmtpUtf8Name constraints can and
>> should also include appropriate rfc822Name constraints that ensure
>> that the desired SmtpUtf8Name constraints are not bypassed via
>> unauthorized rfc822Name altnames.
>>=20
>> The rfc822Name constraints can either permit only equivalent domain
>> names (LDH or A-label forms), or, if no rfc822Name can be compatible
>> with the SmtpUtf8Name constraints, permit only something like
>> "nouser@nodomain.invalid", thereby excluding all valid rfc822 =
addresses.
>=20
> Apologies about being pedantic.  If we specify the CA name constraints =
as you describe above with the asymmetric requirements on SmtpUtf8Name, =
are you okay with the draft's position on keeping separate name =
constraint processing for rfc822Name and SmtpUtf8Name types?  In other =
words the above is proposed to be the resolution for the issue raised in =
your email Feb 11th, second email, para 1-3 i.e. preventing evasion of =
name constraints. =20

Works for me.

--=20
	Viktor.


From nobody Tue Feb 28 10:13:55 2017
Return-Path: <stewart@g3ysx.org.uk>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BA623129664; Tue, 28 Feb 2017 10:13:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart@g3ysx.org.uk>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-mpls-tp-temporal-hitless-psm-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148830561976.29462.5646221515903137638.idtracker@ietfa.amsl.com>
Date: Tue, 28 Feb 2017 10:13:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_kmqofU4Lkfq6Ddlv5hqw1nmLjk>
Cc: mpls@ietf.org, draft-ietf-mpls-tp-temporal-hitless-psm.all@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 18:13:40 -0000

Reviewer: Stewart Bryant
Review result: Almost Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-mpls-tp-temporal-hitless-psm-??
Reviewer: Stewart Bryant
Review Date: 2017-02-28
IETF LC End Date: 2017-03-03
IESG Telechat date: 2017-03-16

Summary:

This document is a valid critique of the existing MPLS SPM design, and
sets out a list of requirements that were called up at the time of its
design but not met. As such this is a valid set of requirements. What
is unclear is whether it is feasible to meet the requirements set out
in this document, and if so whether or not this will require a change
to the MPLS architecture. It would be useful to the reader to clarify
the feasibility of a solution in order not to set false expectations.

Major issues:

The title is "Hitless path segment monitoring".  I read the document
hoping to find that this was a solution. It is not, it is a
requirements text and really ought to be titled as such.

Whilst this text describes a list of issues with the existing IETF
design, it should be remembered that the design was the best that
could be accomplished at the time within the constraints of the MPLS
architecture. So that leaves the reader with a question: do the
authors now have an insight into how a solution can now be designed to
meet the requirement,  or do the authors intend to propose a change to
the MPLS architecture, or is the intention to publish this to state
the requirements in the hope that someone will eventually propose a
solution?

The text  says:

"In particular, performance monitoring measurements (e.g.  Delay
Measurement and Packet Loss  Measurement) are sensitive to these
changes."

Whilst technically true, I am not sure the impact on delay is
significant in any engineering sense. We are talking four bytes per
packet over a service that is going at 1 to 400 Gb/s. Again it is hard
to imagine a significant impact on loss. If this is a key point it
need some justification from an engineering perspective.

In Figure 5 it is unclear what the difference between the first and
second on-demand point is. Is this a reference to input and output
interface monitoring. If  so I think that this should be made clear,
together with a note that a lot of MPLS forwarding designs find this
difficult to achieve. 

The text around Figure 8 explains the deficiency in TTL based section
of an OAM monitoring point in MPLS. However the authors give no
indication of a feasible alternative. Do they have one in mind?

Minor issues: None

Nits/editorial comments: 
     From ID-Nits: The abstract seems to contain references
([RFC6371]), which it
     shouldn't.  Please replace those with straight textual mentions
of the
     documents in question.

For exampla in OTN, TCM allows the insertion - Typo example


From nobody Tue Feb 28 10:24:23 2017
Return-Path: <shitanshu_shah@hotmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAF18129662; Tue, 28 Feb 2017 10:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hotmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GqKw278KOWfD; Tue, 28 Feb 2017 10:24:13 -0800 (PST)
Received: from SNT004-OMC3S13.hotmail.com (snt004-omc3s13.hotmail.com [65.55.90.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABFCE129561; Tue, 28 Feb 2017 10:24:12 -0800 (PST)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com ([65.55.90.135]) by SNT004-OMC3S13.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 28 Feb 2017 10:24:11 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=srPayWmpE7secuLtkLNyWe+anURy2chI2BLLhexpE3E=; b=Bn/TEfSjJvAUst/n3hyw1wM5rRT3oMZOoU0Fn7khL1pDr1SQkGmM7RuvuMPqgVANGUn5Lz0EFz6TnT1pgi+GPOD3HQ0lX4HZeHCcoHtw6ABsv1izXIz6BXwQXC8GAWi9KbRfAj4U8xM+sB30fl1wEhBfqYNQu4voyI1Ykp4q34WF05EudrDfOMXmKG7Wcz/JPmdlWfharzWt3uO7d5gfBevdbqy6AvFRnjpF5/pKUjTF2V2q1ji4kcVcsDdysnRCgjMy4vCxng1WBXX+iOQ3g1mWzdFs+YG/YfqsYaXrXTrXgpLqiT26PSF316hoCCIaeoAI3ug7i3XgcblR74f+5Q==
Received: from BN3NAM01FT041.eop-nam01.prod.protection.outlook.com (10.152.66.52) by BN3NAM01HT153.eop-nam01.prod.protection.outlook.com (10.152.67.91) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.919.10; Tue, 28 Feb 2017 18:24:09 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com (10.152.66.55) by BN3NAM01FT041.mail.protection.outlook.com (10.152.67.200) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.933.11 via Frontend Transport; Tue, 28 Feb 2017 18:24:09 +0000
Received: from DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) by DM3PR13MB0604.namprd13.prod.outlook.com ([10.164.8.150]) with mapi id 15.01.0947.011; Tue, 28 Feb 2017 18:24:09 +0000
From: Shitanshu Shah <shitanshu_shah@hotmail.com>
To: "Black, David" <David.Black@dell.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10
Thread-Topic: Review of draft-ietf-idr-sla-exchange-10
Thread-Index: AQHSjJJLT08h8arb7kKXAYa1wCM/2KF32nBggAB4pYCAACEyq4AEtHCAgAGczIA=
Date: Tue, 28 Feb 2017 18:24:09 +0000
Message-ID: <DM3PR13MB0604AF5667DD40C1C569422AE5560@DM3PR13MB0604.namprd13.prod.outlook.com>
References: <148771630812.19122.17152051080250251501.idtracker@ietfa.amsl.com> <DM3PR13MB0604160394059613AD0331AFE5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8C4510@MX307CL04.corp.emc.com> <DM3PR13MB0604865EC77A246609544830E5520@DM3PR13MB0604.namprd13.prod.outlook.com>, <CE03DB3D7B45C245BCA0D243277949362F8D16F3@MX307CL04.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362F8D16F3@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=hotmail.com;
x-incomingtopheadermarker: OriginalChecksum:C194A302BDABDAAAD6B1FE90F31AC2A02EDDABBE46695C56F2ED1D83BE8ADD29; UpperCasedChecksum:22C3832B2723EAB7536AE8D6E7C0513ADC1BD84AE157665AF307ED026C326C87; SizeAsReceived:8293; Count:40
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [u14L/4hIBkDd7t2dFmu0dnthBO/nHB0A]
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-exchange-diagnostics: 1; BN3NAM01HT153; 5:8FgDJIAdZgD3ruzj7PbTGNXEiqF4Fd3z5VFHHDn5fOXts+3QcJX/PutnMmHEWY3sdiNSKqV4NI49Bsu8TjeUJSsJKuxdxivXkgIzTHmx1cw6DPYeYeAG7aewZgEa4qm1Wl3aBPo0WeIc9yGNkEOevg==; 24:W2/q4+j9T8PWNJV0vWehI8J+OvVGbhruKr5Ls5pjTYxKOnQGCQ4mmsEbxpCG7pIW8bpROh1GT9kVSoW4x4BLqL7F4X61t7FdM9ggddKizMY=; 7:Gk+WI4DTMQVAm3cGTQDTYw3jnw1VR369NhmRm23fxYT7vcPeeGhHt3pDMPeF0Cb0m5IjkAEy7DiVJauX947dS3IIrqwG/Sn+93BDDFm+f/xNuYwVq0bfq7KRH1MJgwbDOm8TDIJNxxouM/qO0u/3SPo0qKE8Prj0UtYtNhdg+Zuvzon60ZCpoFC3TmkWsZnIHh0vREVmRk/Ce9u+qR7Dh1xHLpd4LUxDjGaJWtVWBXTpxjVxTn88ZzqdmeMe/9R9kkRMk/S0HwOwrP5SHR8AXMwZNlOggrfSSebmU6T2Mhs0+uNiBN0mt1rHonmCOu+H
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(10019020)(98900012); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3NAM01HT153; H:DM3PR13MB0604.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 0f4c1498-26a1-4c9c-e288-08d46006fcc9
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(1601125254)(1603101448)(1701031045); SRVR:BN3NAM01HT153; 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015087)(444000031); SRVR:BN3NAM01HT153; BCL:0; PCL:0; RULEID:; SRVR:BN3NAM01HT153; 
x-forefront-prvs: 0232B30BBC
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM3PR13MB0604AF5667DD40C1C569422AE5560DM3PR13MB0604namp_"
MIME-Version: 1.0
X-OriginatorOrg: hotmail.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Feb 2017 18:24:09.2148 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3NAM01HT153
X-OriginalArrivalTime: 28 Feb 2017 18:24:11.0814 (UTC) FILETIME=[DBCECC60:01D291EF]
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/irPWBYFJSh48JjafRBgY5fL3s5M>
Cc: "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-sla-exchange.all@ietf.org" <draft-ietf-idr-sla-exchange.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 18:24:17 -0000

--_000_DM3PR13MB0604AF5667DD40C1C569422AE5560DM3PR13MB0604namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


Hi David,


We will add more text to clarify rationale for L2_OVERHEAD.


Do you have a preference or suggest a way to specify L2 rates? We will work=
 on defining 2 TSpecs to specify two rates (min and max).

As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.

Regards,
Shitanshu
________________________________
From: Black, David <David.Black@dell.com>
Sent: Monday, February 27, 2017 10:42 AM
To: Shitanshu Shah; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org; =
Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

Ok, please make that rationale for the L2_OVERHEAD parameter clear in the d=
raft:
> Though for the cases where physical links are not to be over-run, and/or,=
 sla defined are based on l2 rates, the Consumer would
> need to know l2 overhead from the Producer. Otherwise 10 byes of l2 overh=
ead difference on 64 bytes packets can be significant
> compare to on 1400 bytes packets, and thus the Producer does not have a w=
ay to convert rates to ip based (this can cause
> functional issue), since this has to be per packet consideration.
It looks like the result is that if the Producer=92s L2 overhead is larger =
than the Consumer=92s, and the token buckets are specified in IP octets, th=
e consumer has to calculate a per-packet charge of the L2 overhead differen=
ce against the IP token bucket (and in the opposite case, there may be a pe=
r-packet credit).   Are there cases where the overhead is not all L2, e.g.,=
 SLA/TCA Consumer is using a VPN that terminates between Consumer and Produ=
cer?

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 1:05 PM
To: Black, David; tsv-art@ietf.org
Cc: idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@ietf.org
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



One response inline ##svshah2

________________________________
From: Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>
Sent: Friday, February 24, 2017 8:53 AM
To: Shitanshu Shah; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>; Black, David
Subject: RE: Review of draft-ietf-idr-sla-exchange-10

David> Inline ...

Thanks, --David

From: Shitanshu Shah [mailto:shitanshu_shah@hotmail.com]
Sent: Friday, February 24, 2017 4:09 AM
To: Black, David; tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Re: Review of draft-ietf-idr-sla-exchange-10




Hi David,



Thank you for taking time for the review..



Please find our response inline ##svshah and [Med]


Regards,
Shitanshu
________________________________
From: David Black <david.black@emc.com<mailto:david.black@emc.com>>
Sent: Tuesday, February 21, 2017 3:31 PM
To: tsv-art@ietf.org<mailto:tsv-art@ietf.org>
Cc: idr@ietf.org<mailto:idr@ietf.org>; draft-ietf-idr-sla-exchange.all@ietf=
.org<mailto:draft-ietf-idr-sla-exchange.all@ietf.org>; ietf@ietf.org<mailto=
:ietf@ietf.org>
Subject: Review of draft-ietf-idr-sla-exchange-10

Reviewer: David Black
Review result: Not Ready

I've reviewed this document as part of the transport area
directorate's ongoing effort to review key IETF documents. These
comments were written primarily for the transport area directors, but
are copied to the document's authors for their information and to
allow them to address any issues raised. When done at the time of IETF
Last Call, the authors should consider this review together with any
other last-call comments they receive. Please always CC
tsv-art@ietf.org<mailto:tsv-art@ietf.org> if you reply to or forward this r=
eview.

Document: draft-ietf-idr-sla-10
Reviewer: David Black
Review Date: February 21, 2017

Review result: Not Ready

This is an early TSV-ART review of a working group draft, requested by
the IDR Working Group.

This draft defines an extension to BGP to allow exchange of traffic
handling parameters (e.g., configured rates, burst sizes, drop
thresholds).  While this is a useful area of technology to standardize
across network operators, this draft has significant problems, and
parts of it could use some serious rethought.

This reviewer has discussed small portions of this draft with some of
the authors in the past, but this is his first comprehensive reading
and review of the draft.

Major Issues:

[1] The draft is misnamed.  This is not an SLA (Service Level
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -
see the definition of TCA in RFC 2475.  This draft should start from
that definition and generalize the applicability of TCA beyond
Diffserv.  Large areas of SLA content are not covered by this draft -
for more details, see the Wikipedia article on SLA:
https://en.wikipedia.org/wiki/Service-level_agreement .

##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.


David> That would be good, thanks.

[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to
specify a token bucket is a good idea, but it's not a good idea to
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)
octets, as the RFC 2115 TSpec is specified in terms of IP octets.
This change to specification in terms of L2 octets results in needing
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)
framing overhead at sender and receiver of this information.  The
TSpec should be respecified at the IP layer, with L2 framing overhead
left to the Producer and Consumer to factor into their calculations
based on each's direct knowledge of L2 functionality and configuration
in the local AS.  That ought to enable elimination of the L2_OVERHEAD
TLV, thereby reducing complexity.
##svshah, the purpose for advertising L2 overhead, from the Producer to the=
 Consumer, is to make sure traffic is well conditioned, at the egress of th=
e Consumer, to avoid possible indiscriminate drops at the ingress of the Pr=
oducer. In another words, the Producer is telling the Consumer to ignore it=
s own link level overhead, instead use Producer's provided link level overh=
ead while running frames through QoS functions (this is relevant in use-cas=
es where l2 overhead of the egress link on Consumer and of ingress link on =
the Producer are of different size, e.g., in the vpn/tunnel connection betw=
een two peer nodes which physically may be multiple hops away).
I understand your comments regarding re-using TSpec without any modificatio=
n. Do you agree with the use-case of l2 differences? If yes, any suggestion=
 how to accommodate that?

David> Specifying this in terms of IP octets implies that L2 overhead is to=
 be ignored on both links.  That=92s simpler, and a few sentences of discus=
sion about possible L2 framing differences should cover what needs to be do=
ne (e.g., if traffic rates are configured in terms of L2 octets, then expla=
in how each entity converts between IP traffic and L2 traffic - the draft a=
lready effectively contains that explanation).

##svshah2, just to make sure that some of the real use are not left out..

For the traffic conditioning where sla established is for the ip based rate=
s only, it suffices for the Producer to send rates only IP based ignoring a=
ny specific of l2 overheads.

Though for the cases where physical links are not to be over-run, and/or, s=
la defined are based on l2 rates, the Consumer would need to know l2 overhe=
ad from the Producer. Otherwise 10 byes of l2 overhead difference on 64 byt=
es packets can be significant compare to on 1400 bytes packets, and thus th=
e Producer does not have a way to convert rates to ip based (this can cause=
 functional issue), since this has to be per packet consideration.

Regards,
Shitanshu




[3] A token bucket should have two rate-related marking parameters
based on its token fill rate, i.e., min-rate, not the four
rate-related marking parameters in this draft.  The max-rate
parameters in sections 3.3.2.5-6 ought to be specified against a
second token bucket.  In addition, the handling precedence algorithm
in section 3.3.2.7 is an overly complex way to specify the
relationship of two token buckets.  All of this is even more
important, because max-rate, as defined in RFC 2115, is only
applicable to bursting - that max-rate for bursting often turns out to
be an interface line rate, which is not generally useful for the
traffic provisioning purposes of this draft.

##svshah, what you describe below conceptually very much makes sense and th=
at is what we attempt to achieve. What is unclear though how to capture tha=
t using TSpec definition specified in RFC2215. Since that TSpec definition =
has both minimum-rate and maximum-rate, but no in/out profile marking param=
eters.

Is your proposal below to define two TSpecs using the same definition from =
RFC2215? Wouldn't in that case we have min/max specified twice? min/max in =
each TSpec? and thus confusing to represent one min and one max through two=
 TSpecs?

David> See RFC 2698 for the desired behavior and the parameters needed to s=
pecify it.  The current idr-sla draft is not able to represent the traffic =
conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each me=
chanism requires two token buckets (e.g., there are two burst sizes, but th=
e idr-sla draft TSpec only contains one).  This deficiency needs to be deal=
t with.  One possibility for simplification is to drop the max-rate from th=
e RFC 2115 TSpec and assume that the max-rate for bursting is the effective=
 line rate.

The following should be done instead:
        - Define TSpecs for two token buckets, a primary/committed token bu=
cket
                and a secondary/peak token bucket that MUST be nested, i.e.=
, traffic
                that is in-profile for the secondary/peak token bucket is a=
lways
                in-profile for the primary/committed token bucket.  Some of=
 the details
                of how to specify this are subtle, see RFC 2698 for a worke=
d example.
                Use of a secondary/peak token bucket requires use of the pr=
imary/
                committed token bucket, but a primary/committed token bucke=
t can be used
                without a secondary/peak token bucket.
        - For a single token bucket, define two handling TLVs, Committed (i=
n profile) and
                Excess (out of profile).
        - For two token buckets, define three handling TLVs, Committed (in =
profile for both
                token buckets), Peak (out of profile for primary/committed =
token bucket, but in
                profile for secondary/peak token bucket) and Excess (out of=
 profile for both
                token buckets).
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess
terms.

[4] The drop threshold TLV in section 3.3.2.8 is not specified
sufficiently to be implemented interoperably.  For example, I don't
understand what an implementation is supposed to do when it receives 3
drop thresholds.
##svshah, It is around the semantics of a single queue with a different thr=
eshold for a set of code-points, where packet for a specific code-point is =
to be tail dropped if overall queue-depth hits code-point specific threshol=
d at the arrival of that packet.
We will add appropriate clarification for this semantics.

David> Will look at revision

[5] The relative priority TLV in section 3.3.2.9 has the same
insufficient specification problem as the drop threshold TLV,
compounded by a functional incompleteness problem - if the recipient
is using a weighted packet transmission scheduler (e.g., WRR),
priorities cannot be used to configure that scheduler.  Hence, some
specification of weights and scheduling algorithms that use weights
needs to be added.
##svshah, Sure. Is following clarification okay? (some of the wordings take=
n from RFC2598)

"
A higher priority class of traffic to be served without pre-empted by lower=
 priority class of traffic for more than a packet time at the configured ra=
te.

In the system that implements WRR, the use of relative priority may get res=
tricted where a single queue may be used for a higher priority traffic clas=
s where that queue  is configured for the full share of the output bandwidt=
h.
"

David> Last sentence basically says that WRR weights are out-of-scope.  Tha=
t seems wrong.  Will look at revision.

[6] I have no idea what the sub-traffic classes TLV in section
3.3.2.10 is supposed to do, as that TLV is specified based on "Traffic
Class TLVs" which is an undefined term in this draft (e.g., that term
is not used outside of section 3.3.2.10.
##svshah, They are to facilitate hierarchy. A specific Traffic Class, can f=
urther be divided in a multiple  subset of Traffic Classes, with their own =
Traffic Class Elements and Traffic Class Services.

Will correct the wording to remove your this specific concern.

David> Will look at revision

[7] This draft's QoS contents need to be functionally aligned with
work-in-progress on YANG QoS models, in order to provide some
assurance that that this draft is implementable for actual network
switch/router data paths.  The current acknowledgement of the
existence of YANG, NETCONF and RESTConf at the end of Section 1 does
not suffice.
##svshah, While eventually "Traffic Conditioning Agreement" should be trans=
lated to the actual forwarding qos policy on any vendor specific device, TC=
A exchange largely carries concepts/semantics that is either standard based=
 or well understood.

While we are not aware of any working group document of QoS Yang Model, we =
think that  concepts of Traffic Conditioning should be easily adaptable to =
any QoS Yang Models since they also have to be defined to support those con=
cepts.


David> Still want to see cross-check with implementations here.


[8] There are significant complexity and correctness problems caused
by the option to not specify the Source AS - e.g., Section 3.2 defines
an SLA ID as an "identifier which is unique in the scope of Source AS"
which is meaningless if there is no Source AS.  It would be simpler to
always specify Source AS, even in the point-to-point case.

##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in cases.=
 Given specification of Source AS always is more clearer in multiple feed-b=
ack we have gotten so far, we can modify the specification to incorporate t=
hat over the simplicity of implementation for certain cases.

David> OK, thanks.

[9] In section 3.2, the "intended for the peer receiver of the BGP
UPDATE message" text in the specification of bit 0 of the SLA Subtype
flags is unclear.  I suspect that this is intended to differentiate
the two usages described in sections 4.1.1 (Point-to-Point) and 4.1.2
(Multiple Hops), in which case the parenthesized terms (or similar
terminology) should be used with cross-references to those two
sections.
##svshah, sure will make necessary changes, also in the context of earlier =
comment.


[10] There needs to be a coherent discussion in one place about how
SLA advertisement, update and withdrawal work.  A single ADVERTISE
method may suffice on the wire, but the details on how initial
advertisement, subsequent advertisement (update) and withdrawal work
need to be specified in one place.  The third paragraph of Section 4
is a start on this material, but it's too terse;

[Med] That text is terse because we are reusing the BGP machinery for adver=
tising/withdrawing; we only augment it with triggers that are linked to the=
 SLA information. A new SLA will lead to an update message with ADVERTISE, =
an update of an existing SLA will trigger an update message. We do think th=
is information is already present in the document.

David>This is hard to understand it, as there is no statement that the BGP =
machinery is being used, and the material on SLA usage is spread in differe=
nt places.  I suggest starting section 3 with a discussion of advertisement=
/update/withdrawal, and how all three are realized via a single ADVERTISE m=
ethod via BGP UPDATE - this was difficult to figure out in reading the curr=
ent draft.

it should be expanded
into its own subsection, and moved earlier to come before the
ADVERTISE method in Section 3.2.  This text from Section 3.2 should be
moved into that new subsection and likewise expanded:

[Med] Another option is to move it Section 4. From our standpoint, we do th=
ink it is straightforward to describe the behavior once the attributes form=
at are defined.

David> Ok, that=92s an editorial choice - I prefer to explain how something=
 works before defining its on-the-wire data format.

      If an advertised SLA ID is different from earlier advertised one,
      for the same prefix and from the same Source AS, indicates Source
      AS is advertising new SLA Content to replace the previous one
      advertised with the same SLA ID.

In addition, I wonder whether functionality should be added to allow
withdrawal of an advertisement by specifying its SLA ID, although that
was not part of the original design.


[Med] The reason we didn=92t adopted that design is that we don=92t want to=
 make assumptions on which data the remote peer will be used for enforcing =
local actions and also because of this text:

      The SLA ID applies to aggregate traffic to prefixes for a given

      AFI/SAFI that share the same Source AS and SLA ID.

David> That=92s fine, I wanted to ensure that this had been considered.  Th=
e discussion of BGP mechanism reuse will probably help here.

[11] Notions of context for interpretation of all the IPFIX parameters
in 3.3.1 need to be added, e.g.:
        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.
        - The IP address parameters are rather likely to be VPN-specific wh=
en there's more
                than one BGP/MPLS VPN that spans or transits the ASs involv=
ed.
        - The transport port parameters need specification of which transpo=
rt header and where it
                is located (e.g., for TCP traffic carried by in VXLAN, is t=
his the inner TCP header
                or the outer UDP header in VXLAN).
There are probably simple approaches to specifying context in all
cases, but that context does need to be specified ... in all cases.

[Med] We dind=92t include a context field because we thought that the defin=
ition of the IPFIX attributes is sufficient by itself, but if you do think =
it is helpful to have such information, we can update the table.
David>  Really???  Please reread the first comment above:

        - The first three parameters (DSCP, MPLS EXP field in top label, 80=
2.1q priority) can
                and do vary on a link-by-link or LSP-by-LSP basis along a t=
raffic's network path.

David>  Taking just DSCP, it can change on a per-link basis, so something h=
as to specify which link (between the SLA Producer and SLA Consumer?) is in=
volved.  It probably suffices to say that it=92s the link that crosses the =
relevant AS boundary, but that does have to be stated, as it=92s nowhere to=
 be found in the far more general IPFIX registry.

[12] The security considerations (section 10) are severely incomplete
and insufficient:

David> I stand by this statement and recommend a complete rewrite of the se=
curity considerations.

        - Discussion of possible abuse of this BGP option for denial-of-ser=
vice and theft-of-service,
                needs to be added, including possible countermeasures and m=
itigations.

[Med] This attack vector is not specific to this attribute; this is valid f=
or BGP in general.

David> There are additional attacks enabled by this attribute.

        - This sentence at the end of the second paragraph in Section 10 is=
 content-free:

                   It is NOT RECOMMENDED to enable this attribute at the
                   scale of the Internet unless if means to prevent leaking=
 sensitive
                   information are enforced.

                What exactly is an implementer or admin supposed to do?

[Med] An example of what an admin needs to check if this information can be=
 sent to a given peer or not. Some of the content of the attribute contains=
 some sensitive information such as contract Id, classes, etc.

How does one
                figure out whether an implementation or deployment is  "at =
the scale
                of the Internet" ??

[Med] The idea here is to avoid leaking such data in to the global routing =
table. Only entitled peers need receive such information with controlled sc=
ope.

David> I understand the idea - the problem is that I don=92t see specificat=
ion of what has to be implemented in either the text in the draft or the ab=
ove explanations.
        - The next to last paragraph in section 10 is almost content-free, =
as it leaves
                decisions on implementation and deployment of key security =
functionality as
                "an exercise for the reader" - that's not acceptable.


[Med] I guess you are referring to the following text. Validation checks ar=
e really deployment-specific. The text calls out the issue and recommends a=
n action; how to translate this action into detailed actions is realty loca=
l to a domain

   The attribute may be advertised by a misbehaving node to communicate

   SLA parameters that are not aligned with the SLA agreements.  Though

   the enforcement of SLA parameters is outside the scope of this

   document, it is RECOMMENDED that the SLA Consumer to enforce a set of

   validation checks before translating the SLA parameters conveyed in

   the QoS attributes into provisioning actions.  Such validations MAY

   rely on SLA parameters like the origin AS or SLA ID, like generating

   SLA ID using pseudo-random schemes [RFC4086<https://tools.ietf.org/html/=
rfc4086>].

David> I stand by the =93exercise to the reader=94  criticism - one way to =
be honest about this would be to change the paragraph to:



        The attribute may be advertised by a misbehaving node to communicat=
e

   SLA parameters that are not aligned with the SLA agreements.  The

   enforcement of SLA parameters is outside the scope of this document.



David> That does not change any normative content of the original paragraph=
.  My view is that the =93outside the scope of this document=94 statement i=
s wrong because all of these parameters are being defined in this draft.

        - Last, but not least, the final paragraph in Section 10 is a joke =
that will
                be lost on a security directorate reviewer - to understand =
why, see
                Section 2 of RFC 6919, and take note of the publication dat=
e of RFC 6919.

David> For anyone who didn=92t catch the reference, RFC 6919 is an April 1 =
RFC ... and the =93SHOULD BE considered=94 language used in the last securi=
ty considerations paragraph of this draft is accurately characterized as va=
gue in Section 2 of RFC 6919:
   The phrase "SHOULD CONSIDER" indicates that the authors of the
   specification think that implementations should do something, but
   they're not sure quite what.
------------------------

Having noted a dozen major issues, I'll end the review here for now,
as I believe a serious revision of the draft is called for, which
would be a better starting point to review for minor issues and
editorial items.

--------------------------------------------------------
David L. Black, Distinguished Engineer
Dell EMC, 176 South St., Hopkinton, MA  01748
+1 (508) 293-7953     Cell: +1 (978) 394-7754
David.Black@dell.com<mailto:David.Black@dell.com>  <=3D=3D=3D NEW =3D=3D=3D
--------------------------------------------------------


--_000_DM3PR13MB0604AF5667DD40C1C569422AE5560DM3PR13MB0604namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><br>
</p>
<p>Hi&nbsp;David,</p>
<p><br>
</p>
<p>We will add more text to clarify rationale for L2_OVERHEAD.</p>
<p><br>
</p>
<p>Do you have a preference or suggest a way to specify L2 rates? We will w=
ork on defining 2 TSpecs to specify two rates (min and max).&nbsp;</p>
<br>
As far as VPN terminating between Consumer and Producer, I am not aware of =
use-cases, at least in the context of the deployment scenario considered fo=
r the draft.
<div><br>
</div>
<div>Regards,</div>
<div>Shitanshu</div>
<div style=3D"color: rgb(0, 0, 0);">
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Black, David &lt;Davi=
d.Black@dell.com&gt;<br>
<b>Sent:</b> Monday, February 27, 2017 10:42 AM<br>
<b>To:</b> Shitanshu Shah; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</font>
<div>&nbsp;</div>
</div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Ok, please make that ra=
tionale for the L2_OVERHEAD parameter clear in the draft:</span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&gt; Though fo=
r the cases where&nbsp;physical&nbsp;links are not to be&nbsp;over-run, and=
/or,&nbsp;sla defined are based on l2 rates, the&nbsp;Consumer would<br>
&gt; need to know l2 overhead from the Producer. Otherwise 10 byes of l2 ov=
erhead difference on 64 bytes packets can be significant<br>
&gt; compare to on 1400 bytes packets, and thus the Producer does not have =
a way to convert rates to&nbsp;ip based (this can cause<br>
&gt; functional issue), since this has to be per packet consideration.</spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">It looks like the resul=
t is that if the Producer=92s L2 overhead is larger than the Consumer=92s, =
and the token buckets are specified in IP octets, the consumer
 has to calculate a per-packet charge of the L2 overhead difference against=
 the IP token bucket (and in the opposite case, there may be a per-packet c=
redit).&nbsp;&nbsp; Are there cases where the overhead is not all L2, e.g.,=
 SLA/TCA Consumer is using a VPN that terminates
 between Consumer and Producer?</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Thanks, --David</span><=
/p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt; font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0in 0in 0i=
n 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> Shitan=
shu Shah [mailto:shitanshu_shah@hotmail.com]
<br>
<b>Sent:</b> Friday, February 24, 2017 1:05 PM<br>
<b>To:</b> Black, David; tsv-art@ietf.org<br>
<b>Cc:</b> idr@ietf.org; draft-ietf-idr-sla-exchange.all@ietf.org; ietf@iet=
f.org<br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">Hi David,</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">One response inline ##svshah2</span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span=
></p>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:bla=
ck">
<hr size=3D"2" width=3D"98%" noshade=3D"" align=3D"center" style=3D"color:b=
lack">
</span></div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt; font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black">From:</span></b><span =
style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif=
&quot;; color:black"> Black, David &lt;<a href=3D"mailto:David.Black@dell.c=
om">David.Black@dell.com</a>&gt;<br>
<b>Sent:</b> Friday, February 24, 2017 8:53 AM<br>
<b>To:</b> Shitanshu Shah; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf=
.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a>; Black, David<br>
<b>Subject:</b> RE: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"=
>
</span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black">&nbsp;</span></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; In=
line ...</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Thanks, --Da=
vid</span><span style=3D"color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<div style=3D"border:none; border-left:solid blue 1.5pt; padding:0in 0in 0i=
n 4.0pt">
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal" style=3D""><b><span style=3D"font-size:10.0pt; font-=
family:&quot;Tahoma&quot;,&quot;sans-serif&quot;; color:black">From:</span>=
</b><span style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;s=
ans-serif&quot;; color:black"> Shitanshu Shah [<a href=3D"mailto:shitanshu_=
shah@hotmail.com">mailto:shitanshu_shah@hotmail.com</a>]
<br>
<b>Sent:</b> Friday, February 24, 2017 4:09 AM<br>
<b>To:</b> Black, David; <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.o=
rg</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Re: Review of draft-ietf-idr-sla-exchange-10</span><span st=
yle=3D"color:black"></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">Hi David,</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">Thank you for taking time for the review..</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">Please find our response inline ##svshah and [Med]</span></p>
<p><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:black">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">Regards,
</span><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Shitanshu</s=
pan><span style=3D"color:black"></span></p>
<div>
<div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center"><span=
 style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:bla=
ck">
<hr size=3D"2" width=3D"98%" align=3D"center">
</span></div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal" style=3D""><b><span style=3D"font-size:11.0pt; font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">From:</span=
></b><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"> David Black &lt;<a href=3D"mailto:david.bl=
ack@emc.com">david.black@emc.com</a>&gt;<br>
<b>Sent:</b> Tuesday, February 21, 2017 3:31 PM<br>
<b>To:</b> <a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:idr@ietf.org">idr@ietf.org</a>; <a href=3D"mai=
lto:draft-ietf-idr-sla-exchange.all@ietf.org">
draft-ietf-idr-sla-exchange.all@ietf.org</a>; <a href=3D"mailto:ietf@ietf.o=
rg">ietf@ietf.org</a><br>
<b>Subject:</b> Review of draft-ietf-idr-sla-exchange-10</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">
</span><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Reviewer: Davi=
d Black<br>
Review result: Not Ready<br>
<br>
I've reviewed this document as part of the transport area<br>
directorate's ongoing effort to review key IETF documents. These<br>
comments were written primarily for the transport area directors, but<br>
are copied to the document's authors for their information and to<br>
allow them to address any issues raised. When done at the time of IETF<br>
Last Call, the authors should consider this review together with any<br>
other last-call comments they receive. Please always CC<br>
<a href=3D"mailto:tsv-art@ietf.org">tsv-art@ietf.org</a> if you reply to or=
 forward this review.<br>
<br>
Document: draft-ietf-idr-sla-10<br>
Reviewer: David Black<br>
Review Date: February 21, 2017<br>
<br>
Review result: Not Ready<br>
<br>
This is an early TSV-ART review of a working group draft, requested by<br>
the IDR Working Group.<br>
<br>
This draft defines an extension to BGP to allow exchange of traffic<br>
handling parameters (e.g., configured rates, burst sizes, drop<br>
thresholds).&nbsp; While this is a useful area of technology to standardize=
<br>
across network operators, this draft has significant problems, and<br>
parts of it could use some serious rethought.<br>
<br>
This reviewer has discussed small portions of this draft with some of<br>
the authors in the past, but this is his first comprehensive reading<br>
and review of the draft.<br>
<br>
Major Issues:<br>
<br>
[1] The draft is misnamed.&nbsp; This is not an SLA (Service Level<br>
Agreement) draft - it's a TCA (Traffic Conditioning Agreement) draft -<br>
see the definition of TCA in RFC 2475.&nbsp; This draft should start from<b=
r>
that definition and generalize the applicability of TCA beyond<br>
Diffserv.&nbsp; Large areas of SLA content are not covered by this draft -<=
br>
for more details, see the Wikipedia article on SLA:<br>
<a href=3D"https://en.wikipedia.org/wiki/Service-level_agreement" id=3D"LPl=
nk481142" previewremoved=3D"true">https://en.wikipedia.org/wiki/Service-lev=
el_agreement</a> .<br>
<br>
##svshah, sure, we can change the term to TCA (Traffic Conditioning Agreeme=
nt), which fairly represents intention in the draft, if there is no otherwi=
se comment from the working group.</span><span style=3D"color:black"></span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D">David&gt; That would be good, thanks.</=
span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:black"><br>
<br>
[2] Section 3.3.2.1's reuse of the TSpec construct from RFC 2115 to<br>
specify a token bucket is a good idea, but it's not a good idea to<br>
respecify that construct in terms of L2 (link-layer, e.g., Ethernet)<br>
octets, as the RFC 2115 TSpec is specified in terms of IP octets. <br>
This change to specification in terms of L2 octets results in needing<br>
the L2_OVERHEAD TLV to cope with the possible differences in L2 (link)<br>
framing overhead at sender and receiver of this information.&nbsp; The<br>
TSpec should be respecified at the IP layer, with L2 framing overhead<br>
left to the Producer and Consumer to factor into their calculations<br>
based on each's direct knowledge of L2 functionality and configuration<br>
in the local AS.&nbsp; That ought to enable elimination of the L2_OVERHEAD<=
br>
TLV, thereby reducing complexity.</span><span style=3D"color:black"></span>=
</p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, the =
purpose for advertising L2 overhead, from the Producer to the Consumer,&nbs=
p;is to make sure traffic is well conditioned, at the egress of
 the&nbsp;Consumer, to avoid possible indiscriminate drops at the ingress o=
f the Producer. In another words, the&nbsp;Producer is telling the&nbsp;Con=
sumer to ignore its own link level overhead, instead use Producer's provide=
d link level overhead while running frames through
 QoS functions (this is&nbsp;relevant in use-cases where l2 overhead of the=
&nbsp;egress link on Consumer and of ingress link on the Producer are of di=
fferent size, e.g., in the&nbsp;vpn/tunnel connection between two peer&nbsp=
;nodes which physically may be multiple hops away).</span><span style=3D"co=
lor:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">I understand y=
our comments regarding re-using TSpec without any modification.&nbsp;Do you=
 agree with the use-case of l2 differences? If yes, any suggestion
 how to accommodate that?</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Sp=
ecifying this in terms of IP octets implies that L2 overhead is to be ignor=
ed on both links.&nbsp; That=92s simpler, and a few sentences of discussion
 about possible L2 framing differences should cover what needs to be done (=
e.g., if traffic rates are configured in terms of L2 octets, then explain h=
ow each entity converts between IP traffic and L2 traffic - the draft alrea=
dy effectively contains that explanation).</span><span style=3D"color:black=
"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah2, jus=
t to make sure that some of the real use are not left out..</span><span sty=
le=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">For the traffi=
c conditioning where sla established is for the ip based rates only, it suf=
fices for the Producer to&nbsp;send rates only IP based ignoring
 any specific of l2 overheads.</span><span style=3D"color:black"></span></p=
>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Though for the=
 cases where&nbsp;physical&nbsp;links are not to be&nbsp;over-run, and/or,&=
nbsp;sla defined are based on l2 rates, the&nbsp;Consumer would need to kno=
w l2 overhead
 from the Producer. Otherwise 10 byes of l2 overhead difference on 64 bytes=
 packets can be significant compare to on 1400 bytes packets, and thus the =
Producer does not have a way to convert rates to&nbsp;ip based (this can ca=
use functional issue), since this has
 to be per packet consideration.</span><span style=3D"color:black"></span><=
/p>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Regards,</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Shitanshu</spa=
n><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"color:black">&nbsp;</span>=
</p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
[3] A token bucket should have two rate-related marking parameters<br>
based on its token fill rate, i.e., min-rate, not the four<br>
rate-related marking parameters in this draft.&nbsp; The max-rate<br>
parameters in sections 3.3.2.5-6 ought to be specified against a<br>
second token bucket.&nbsp; In addition, the handling precedence algorithm<b=
r>
in section 3.3.2.7 is an overly complex way to specify the<br>
relationship of two token buckets.&nbsp; All of this is even more<br>
important, because max-rate, as defined in RFC 2115, is only<br>
applicable to bursting - that max-rate for bursting often turns out to<br>
be an interface line rate, which is not generally useful for the<br>
traffic provisioning purposes of this draft.</span><span style=3D"color:bla=
ck"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, what=
 you describe below conceptually very much makes sense and that is what we =
attempt to achieve. What is unclear though how to capture
 that using TSpec definition specified in RFC2215. Since that TSpec definit=
ion has both minimum-rate and maximum-rate, but no in/out profile marking p=
arameters.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Is your propos=
al below to define two TSpecs using the same&nbsp;definition from RFC2215? =
Wouldn't in that case we have min/max specified twice? min/max
 in each TSpec? and thus confusing to represent one min and one max through=
 two TSpecs?</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Se=
e RFC 2698 for the desired behavior and the parameters needed to specify it=
.&nbsp; The current idr-sla draft is not able to represent the traffic
 conditioning mechanisms specified in both RFC 2698 and RFC 2697, as each m=
echanism requires two token buckets (e.g., there are two burst sizes, but t=
he idr-sla draft TSpec only contains one).&nbsp; This deficiency needs to b=
e dealt with.&nbsp; One possibility for simplification
 is to drop the max-rate from the RFC 2115 TSpec and assume that the max-ra=
te for bursting is the effective line rate.</span><span style=3D"color:blac=
k"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
The following should be done instead:<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - Define TSpecs for two token bu=
ckets, a primary/committed token</span><span style=3D"font-size:10.0pt; fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">bucket<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; and a secondary/peak token bucket that MUST be nested, i.e.=
,</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">traffic<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; that is in-profile for the secondary/peak token bucket is a=
lways<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; in-profile for the primary/committed token bucket.&nbsp; So=
me of the</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">details<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; of how to specify this are subtle, see RFC 2698 for a worke=
d</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">example.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Use of a secondary/peak token bucket requires use of the pr=
imary/<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; committed token bucket, but a primary/committed token bucke=
t can be</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">used<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; without a secondary/peak token bucket.<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For a single token bucket, def=
ine two handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt;=
 font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">profile) and<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; Excess (out of profile).<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - For two token buckets, define =
three handling TLVs, Committed (in</span><span style=3D"font-size:10.0pt; f=
ont-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">profile for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets), Peak (out of profile for primary/committed =
token</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot=
;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">bucket, but in<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; profile for secondary/peak token bucket) and Excess (out of=
 profile</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">for both<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp; token buckets).<br>
NB: Could use Green/Yellow/Red terms instead of Committed/Peak/Excess<br>
terms.<br>
<br>
[4] The drop threshold TLV in section 3.3.2.8 is not specified<br>
sufficiently to be implemented interoperably.&nbsp; For example, I don't<br=
>
understand what an implementation is supposed to do when it receives 3<br>
drop thresholds.</span><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah,&nbsp=
;It is around the semantics of&nbsp;a single queue with a different thresho=
ld for a set of code-points, where packet for a specific code-point
 is to be tail dropped if overall queue-depth hits code-point specific thre=
shold at the arrival of that packet.</span><span style=3D"color:black"></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">We will add ap=
propriate clarification for this semantics.</span><span style=3D"color:blac=
k"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
[5] The relative priority TLV in section 3.3.2.9 has the same<br>
insufficient specification problem as the drop threshold TLV,<br>
compounded by a functional incompleteness problem - if the recipient<br>
is using a weighted packet transmission scheduler (e.g., WRR),<br>
priorities cannot be used to configure that scheduler.&nbsp; Hence, some<br=
>
specification of weights and scheduling algorithms that use weights<br>
needs to be added.</span><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, Sure=
. Is following clarification okay? (some of the wordings taken from RFC2598=
)</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&quot;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">A higher prior=
ity class of traffic&nbsp;to be served without pre-empted by lower priority=
&nbsp;class of traffic&nbsp;for more than a packet time at the configured
 rate.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">In the system =
that implements WRR, the use of relative priority may get restricted where =
a single queue may be used for a&nbsp;higher priority traffic class
 where that queue &nbsp;is configured for the full share of the output band=
width.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&quot;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; Last sentence basically says that WRR weights are out-of-=
scope.&nbsp; That seems wrong.&nbsp; Will look at revision.</span><span sty=
le=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;; color:black"><br>
<br>
[6] I have no idea what the sub-traffic classes TLV in section<br>
3.3.2.10 is supposed to do, as that TLV is specified based on &quot;Traffic=
<br>
Class TLVs&quot; which is an undefined term in this draft (e.g., that term<=
br>
is not used outside of section 3.3.2.10.</span><span style=3D"color:black">=
</span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, They=
 are to facilitate hierarchy. A specific Traffic Class, can further be divi=
ded in a multiple &nbsp;subset of&nbsp;Traffic Classes, with their own
 Traffic Class Elements and Traffic Class Services.</span><span style=3D"co=
lor:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">Will correct t=
he wording to remove your this specific concern.</span><span style=3D"color=
:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D">David&gt; Will look at revision
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack"><br>
[7] This draft's QoS contents need to be functionally aligned with<br>
work-in-progress on YANG QoS models, in order to provide some<br>
assurance that that this draft is implementable for actual network<br>
switch/router data paths.&nbsp; The current acknowledgement of the<br>
existence of YANG, NETCONF and RESTConf at the end of Section 1 does<br>
not suffice.</span><span style=3D"color:black"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, Whil=
e&nbsp;eventually &quot;Traffic Conditioning Agreement&quot; should be tran=
slated to the actual forwarding qos policy on any vendor specific device,
 TCA exchange largely carries concepts/semantics that is either standard ba=
sed or&nbsp;well understood.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">While we are n=
ot aware of any working group document of QoS Yang Model, we think that &nb=
sp;concepts of Traffic Conditioning should be easily adaptable
 to any QoS Yang Models since they also have to be defined to support those=
 concepts.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><=
span style=3D"color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; St=
ill want to see cross-check with implementations here.</span><span style=3D=
"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; =
color:black"><br>
<br>
<br>
[8] There are significant complexity and correctness problems caused<br>
by the option to not specify the Source AS - e.g., Section 3.2 defines<br>
an SLA ID as an &quot;identifier which is unique in the scope of Source AS&=
quot;<br>
which is meaningless if there is no Source AS.&nbsp; It would be simpler to=
<br>
always specify Source AS, even in the point-to-point case.<br>
<br>
##svshah, okay. Ron Bonica also suggested same in his review earlier. We ha=
d chosen a path of optional Source AS to simplify implementations in&nbsp;c=
ases. Given specification of Source AS always is more clearer in multiple f=
eed-back we have gotten so far, we can
 modify the specification to incorporate that over the simplicity of implem=
entation for certain cases.</span><span style=3D"color:black"></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; OK=
, thanks.</span><span style=3D"color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[9] In section 3.2, the &quot;intended fo=
r the peer receiver of the BGP</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">UPDATE message&quot; text in the specific=
ation of bit 0 of the SLA Subtype</span><span style=3D"font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">flags is unclear.&nbsp; I suspect that th=
is is intended to differentiate</span><span style=3D"font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">the two usages described in sections 4.1.=
1 (Point-to-Point) and 4.1.2</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">(Multiple Hops), in which case the parent=
hesized terms (or similar</span><span style=3D"font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">terminology) should be used with cross-re=
ferences to those two</span><span style=3D"font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">sections.</span><span style=3D"color:blac=
k"></span></p>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">##svshah, sure=
 will make necessary changes, also in the context of earlier comment.</span=
><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[10] There needs to be a coherent discuss=
ion in one place about how</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">SLA advertisement, update and withdrawal =
work.&nbsp; A single ADVERTISE</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">method may suffice on the wire, but the d=
etails on how initial</span><span style=3D"font-family:&quot;Calibri&quot;,=
&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">advertisement, subsequent advertisement (=
update) and withdrawal work</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">need to be specified in one place.&nbsp; =
The third paragraph of Section 4</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">is a start on this material, but it's too=
 terse;&nbsp;</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Courier New&quot;; color:black">[Med] That text is terse because =
we are reusing the BGP machinery for advertising/withdrawing; we only augme=
nt it with triggers that are linked to the SLA information.
 A new SLA will lead to an update message with ADVERTISE, an update of an e=
xisting SLA will trigger an update message. We do think this information is=
 already present in the document.
</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;Thi=
s is hard to understand it, as there is no statement that the BGP machinery=
 is being used, and the material on SLA usage is spread in different
 places.&nbsp; I suggest starting section 3 with a discussion of advertisem=
ent/update/withdrawal, and how all three are realized via a single ADVERTIS=
E method via BGP UPDATE - this was difficult to figure out in reading the c=
urrent draft.</span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Courier New&quot;; color:black">&nbsp;</span><span style=3D"color=
:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">it should be e=
xpanded</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">into its own subsection, and moved earlie=
r to come before the</span><span style=3D"font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">ADVERTISE method in Section 3.2.&nbsp; Th=
is text from Section 3.2 should be</span><span style=3D"font-family:&quot;C=
alibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">moved into that new subsection and likewi=
se expanded:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] Another option is to move it Section 4. From our stand=
point, we do think it is straightforward to describe the behavior once the =
attributes format are defined.&nbsp;</span><span style=3D"color:black"></sp=
an></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Ok=
, that=92s an editorial choice - I prefer to explain how something works be=
fore defining its on-the-wire data format.</span><span style=3D"color:black=
"></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; If an advertised SLA ID is different from earlier advertis=
ed</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&=
quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">one,</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the sa=
me prefix and from the same Source AS, indicates</span><span style=3D"font-=
size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:=
#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Source</span><span style=3D"font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; AS is adve=
rtising new SLA Content to replace the previous one</span><span style=3D"fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; advertised=
 with the same SLA ID.</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">In addition, I wonder whether functionali=
ty should be added to allow</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">withdrawal of an advertisement by specify=
ing its SLA ID, although that</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">was not part of the original design.</spa=
n><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<div>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt; orphans:2; widows:2"=
><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;; colo=
r:black">[Med] The reason we didn=92t adopted that design is that we don=92=
t want to make assumptions on which data the remote
 peer will be used for enforcing local actions and also because of this tex=
t:</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;; color:black"></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2; widows:2"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Courier New&quot;; color:#212121">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; The SLA ID applies to aggregate traffic to prefixes for=
 a given</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-se=
rif&quot;; color:black"></span></p>
<p class=3D"xmsonormal" style=3D"orphans:2; widows:2"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Courier New&quot;; color:#212121">&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp; AFI/SAFI that share the same Source AS and SLA ID.</spa=
n><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; co=
lor:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; That=92s fine, I wanted to ensure that this had been cons=
idered.&nbsp; The discussion of BGP mechanism reuse will probably help
 here.</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[11] Notions of context for interpretatio=
n of all the IPFIX parameters</span><span style=3D"font-family:&quot;Calibr=
i&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">in 3.3.1 need to be added, e.g.:</span><s=
pan style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:=
black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The first three parameters (DSCP, MPLS EXP field in top label,</span><s=
pan style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">802.1q priority) can</span><span style=3D=
"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-=
link or LSP-by-LSP basis along a traffic's</span><span style=3D"font-size:1=
0.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497=
D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">network path.</span><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The IP address parameters are rather likely to be VPN-specific when</sp=
an><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">there's more</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than one BGP/MPLS VPN tha=
t spans or transits the ASs involved.</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - The transport port parameters need specification of which transport</sp=
an><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">header and where it</span><span style=3D"=
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; is located (e.g., for TCP=
 traffic carried by in VXLAN, is this the</span><span style=3D"font-size:10=
.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D=
">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">inner TCP header</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or the outer UDP header i=
n VXLAN).</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">There are probably simple approaches to s=
pecifying context in all</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">cases, but that context does need to be s=
pecified ... in all cases.</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] We dind=92t include a context field because we thought=
 that the definition of the IPFIX attributes is sufficient by itself, but i=
f you do think it is helpful to have such information,
 we can update the table.</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;&nb=
sp; Really???&nbsp; Please reread the first comment above:</span><span styl=
e=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black">&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; - The first three parameters (DSCP, MPLS EXP f=
ield in top label, 802.1q priority) can</span><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and do vary on a link-by-=
link or LSP-by-LSP basis along a traffic's network path.</span><span style=
=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span><span style=3D"co=
lor:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt;&nb=
sp; Taking just DSCP, it can change on a per-link basis, so something has t=
o specify which link (between the SLA Producer and SLA Consumer?)
 is involved.&nbsp; It probably suffices to say that it=92s the link that c=
rosses the relevant AS boundary, but that does have to be stated, as it=92s=
 nowhere to be found in the far more general IPFIX registry.</span><span st=
yle=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"=
><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">[12] The security considerations (section=
 10) are severely incomplete</span><span style=3D"font-family:&quot;Calibri=
&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">and insufficient:</span><span style=3D"co=
lor:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; I =
stand by this statement and recommend a complete rewrite of the security co=
nsiderations.</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - Discussion of possible abuse of this BGP option for</span><span style=
=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">denial-of-service and theft-of-service,</=
span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
 color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be added, includ=
ing possible countermeasures and</span><span style=3D"font-size:10.0pt; fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">mitigations.</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;=
; color:black">[Med] This attack vector is not specific to this attribute; =
this is valid for BGP in general.</span><span style=3D"color:black"></span>=
</p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span><span style=3D"co=
lor:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; Th=
ere are additional attacks enabled by this attribute.</span><span style=3D"=
color:black"></span></p>
</div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - This sentence at the end of the second paragraph in Section 10 is</span=
><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">content-free:</span><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; It is N=
OT RECOMMENDED to enable this attribute at the</span><span style=3D"font-fa=
mily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; scale o=
f the Internet unless if means to prevent leaking</span><span style=3D"font=
-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color=
:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">sensitive</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; informa=
tion are enforced.</span><span style=3D"font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What exactly is an implem=
enter or admin supposed to do?&nbsp;</span><span style=3D"color:black"></sp=
an></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Courier New&quot;; color:black">[Med] An example of what an admin=
 needs to check if this information can be sent to a given peer or not. Som=
e of the content of the attribute contains some
 sensitive information such as contract Id, classes, etc.</span><span style=
=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:11.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">&nbsp;</span=
><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:5.25pt; text-indent:30.75pt"><s=
pan style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black">How does</span><span style=3D"font-size:10.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">one</span><span style=3D"font-family:&quo=
t;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; figure out whether an imp=
lementation or deployment is&nbsp; &quot;at the</span><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">scale</span><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the Internet&quot; ??<=
/span><span style=3D"color:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
black">&nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Courier New&quot;; color:black">[Med] The idea here is to avoid l=
eaking such data in to the global routing table. Only entitled peers need r=
eceive such information with controlled scope.</span><span style=3D"color:b=
lack"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Courier New&quot;; color:#1F497D">&nbsp;</span><span style=3D"col=
or:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#=
1F497D">David&gt; I understand the idea - the problem is that I don=92t see=
 specification of what has to be implemented in either the text
 in the draft or the above explanations.</span><span style=3D"color:black">=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - The next to last paragra=
ph in section 10 is almost content-free, as</span><span style=3D"font-size:=
10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F49=
7D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">it leaves</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions on implementati=
on and deployment of key security</span><span style=3D"font-size:10.0pt; fo=
nt-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">functionality as</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &quot;an exercise for the=
 reader&quot; - that's not acceptable.</span><span style=3D"font-family:&qu=
ot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"color:black"></span></p>
<p class=3D"xmsonormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-=
size:10.0pt; font-family:&quot;Courier New&quot;; color:black">[Med] I gues=
s you are referring to the following text. Validation checks are really dep=
loyment-specific. The text calls out the issue and
 recommends an action; how to translate this action into detailed actions i=
s realty local to a domain</span><span style=3D"font-family:&quot;Calibri&q=
uot;,&quot;sans-serif&quot;; color:black"></span></p>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; The attribute may be advertised by a misbehaving node to communicate</sp=
an><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA parameters that are not aligned with the SLA agreements.&nbsp; Thoug=
h</span><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; the enforcement of SLA parameters is outside the scope of this</span><sp=
an style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; document, it is RECOMMENDED that the SLA Consumer to enforce a set of</s=
pan><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; validation checks before translating the SLA parameters conveyed in</spa=
n><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; the QoS attributes into provisioning actions.&nbsp; Such validations MAY=
</span><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; rely on SLA parameters like the origin AS or SLA ID, like generating</sp=
an><span style=3D"color:black"></span></pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA ID using pseudo-random schemes [<a href=3D"https://tools.ietf.org/ht=
ml/rfc4086" target=3D"_blank" title=3D"&quot;Randomness Requirements for Se=
curity&quot;">RFC4086</a>].</span><span style=3D"color:black"></span></pre>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black">&nbsp;</span><span style=3D"colo=
r:black"></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D""><span style=3D"font-size:10.0pt; font-fam=
ily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">David&gt; I =
stand by the =93exercise to the reader=94 &nbsp;criticism - one way to be h=
onest about this would be to change the paragraph to:</span><span style=3D"=
color:black"></span></p>
<pre><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;</span><span style=3D"color:black">=
</span></pre>
<pre><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot=
;sans-serif&quot;; color:#1F497D">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; </span><span style=3D"color:#212121">The attribute may be advertised by a=
 misbehaving node to communicate</span><span style=3D"color:black"></span><=
/pre>
<pre style=3D"orphans:2; widows:2"><span style=3D"color:#212121">&nbsp;&nbs=
p; SLA parameters that are not aligned with the SLA agreements.&nbsp; The</=
span><span style=3D"color:black"></span></pre>
<pre><span style=3D"color:#212121">&nbsp;&nbsp; enforcement of SLA paramete=
rs is outside the scope of this document.</span><span style=3D"color:black"=
></span></pre>
<pre><span style=3D"color:#212121">&nbsp;</span><span style=3D"color:black"=
></span></pre>
<pre><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;=
 color:#1F497D">David&gt; That does not change any normative content of the=
 original paragraph.&nbsp; My view is that the =93outside the scope of this=
 document=94 statement is wrong because all of these parameters are being d=
efined in this draft.</span><span style=3D"color:black"></span></pre>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; - Last, but not least, the final paragraph in Section 10 is a joke</span>=
<span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans=
-serif&quot;; color:#1F497D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">that will</span><span style=3D"font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be lost on a security dir=
ectorate reviewer - to understand why, see</span><span style=3D"font-family=
:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 2 of RFC 6919, an=
d take note of the publication date of RFC</span><span style=3D"font-size:1=
0.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497=
D">
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">6919.</span><span style=3D"font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:#1F497D"><br>
David&gt; For anyone who didn=92t catch the reference, RFC 6919 is an April=
 1 RFC ... and the =93SHOULD BE considered=94 language used in the last sec=
urity considerations paragraph of this draft is accurately characterized as=
 vague in Section 2 of RFC 6919:</span><span style=3D"color:black"></span><=
/p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt; font-family:&quot;Courier New&quot;; color:black">&nbsp;&nbsp; T=
he phrase &quot;SHOULD CONSIDER&quot; indicates that the authors of the</sp=
an><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"text-autospace:none"><span style=3D"font-si=
ze:11.0pt; font-family:&quot;Courier New&quot;; color:black">&nbsp;&nbsp; s=
pecification think that implementations should do something, but</span><spa=
n style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:11.0pt; font-family:&quot;Courier New&quot;; color:black">&nbsp;&nbsp; =
they're not sure quite what.</span><span style=3D"color:black"></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:10.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:b=
lack">------------------------</span><span style=3D"font-family:&quot;Calib=
ri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Having noted a dozen major issues, I'll e=
nd the review here for now,</span><span style=3D"font-family:&quot;Calibri&=
quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">as I believe a serious revision of the dr=
aft is called for, which</span><span style=3D"font-family:&quot;Calibri&quo=
t;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">would be a better starting point to revie=
w for minor issues and</span><span style=3D"font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">editorial items.</span><span style=3D"fon=
t-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">-----------------------------------------=
---------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">David L. Black, Distinguished Engineer</s=
pan><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; =
color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">Dell EMC, 176 South St., Hopkinton, MA&nb=
sp; 01748</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">&#43;1 (508) 293-7953&nbsp;&nbsp;&nbsp;&n=
bsp; Cell: &#43;1 (978) 394-7754</span><span style=3D"font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:black"><br>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black"><a href=3D"mailto:David.Black@dell.com">D=
avid.Black@dell.com</a>&nbsp; &lt;=3D=3D=3D NEW =3D=3D=3D</span><span style=
=3D"font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:black"><b=
r>
</span><span style=3D"font-size:10.0pt; font-family:&quot;Calibri&quot;,&qu=
ot;sans-serif&quot;; color:black">-----------------------------------------=
---------------</span><span style=3D"font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;; color:black"><br>
<br>
</span><span style=3D"color:black"></span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DM3PR13MB0604AF5667DD40C1C569422AE5560DM3PR13MB0604namp_--


From nobody Tue Feb 28 10:52:55 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B491912967F for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 10:52:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 GKIZt7gBekuC for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 10:52:50 -0800 (PST)
Received: from resqmta-po-11v.sys.comcast.net (resqmta-po-11v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154: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 6D823129681 for <ietf@ietf.org>; Tue, 28 Feb 2017 10:52:49 -0800 (PST)
Received: from resomta-po-06v.sys.comcast.net ([96.114.154.230]) by resqmta-po-11v.sys.comcast.net with SMTP id imsbc3XtmesrQimtEcEeK1; Tue, 28 Feb 2017 18:52:48 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-06v.sys.comcast.net with SMTP id imtCccwy5oqz9imtDcZ86z; Tue, 28 Feb 2017 18:52:48 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1SIqj2W032447; Tue, 28 Feb 2017 13:52:45 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1SIqjDi032444; Tue, 28 Feb 2017 13:52:45 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: Kerry Lynn <kerlyn@ieee.org>
Subject: Re: [6lo] Last Call: <draft-ietf-6lo-6lobac-06.txt> (Transmission of IPv6 over MS/TP Networks) to Proposed Standard
In-Reply-To: <CABOxzu3EeOCF7mmpxB88b4+NE5SzFrPVDzLa=KqOQenwSezQfw@mail.gmail.com> (kerlyn@ieee.org)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 28 Feb 2017 13:52:45 -0500
Message-ID: <87wpcajgg2.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfBpORgYfZ059naQc8GnNOvEEJpWlj7Pm5iEWjb5YGC3KpyT+N4mXwss3C4hkpU8VmOAtTXHOwALm8wCiF7RLU0wyzZoCEcqCREmYw4Py7fRc7Aoplgjk 1Srr6f+/ArEwqfTm2rRtj6wyshQ+G+RvNT6DwLY7hB8zllOXileHlf0x/sWPuIWGam/30XP0nJauhxTa3JkPqG93LogdtBHWeynSvR4FCOln1sjSWN5RuQYR eiwFZMN89amZfRlZQwygOw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nScpEEhGndweBL5KHbNiAofrRJM>
Cc: ietf@ietf.org, draft-ietf-6lo-6lobac@ietf.org, 6lo@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 18:52:51 -0000

Kerry Lynn <kerlyn@ieee.org> writes:
> Thanks for your thorough review of draft-ietf-6lo-6lobac.  Sorry that
> it has taken so long to get back to you.  Can you take a look at the
> new version and see if it addresses your concerns?  Comments inline...

Yes, the -07 cleans up all my concerns.

> Section 6 has been reworked to more clearly distinguish between two types
> of IIDs: "MAC-address-derived" and "semantically opaque".  The first is
> recommended for link-local addresses because it enables maximum IPv6
> header compression efficiency.  Since MS/TP is used primarily as a field
> bus, I expect most installations will only ever involve link-local traffic
> between an MS/TP device and a local controller.
>
> For applications where the MS/TP device is a client or server with routable
> addresses, the spec strongly recommends generating a semantically opaque
> IID, with 64 bits of entropy, for each global address.

Ah, yes, that's the distinction that makes it clear.

> ANSI/ASHRAE Standard 135-2016 was published late last year.  This
> version integrates the changes that were standardized in 135-2012
> Addendum an, so there's no longer any jumping back and forth between
> references.

And so you simplified the references to Std. 135 .

Dale


From nobody Tue Feb 28 12:29:45 2017
Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 119EB1296D0 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 12:29:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level: 
X-Spam-Status: No, score=-2.722 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BH13ayNJz8U6 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 12:29:44 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 267471296CE for <ietf@ietf.org>; Tue, 28 Feb 2017 12:29:44 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 980601A09B6 for <ietf@ietf.org>; Tue, 28 Feb 2017 20:29:43 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488313783; bh=3Cs6SXQx/V+V2d7DxvxlR5uqC0Hl+aJ0ieNDrVI5Jg0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=DIl6T+ZsEfmVbLDIi5aw27mkYR7DEQcpHSUWmuu48rdH2XVmHRN+IiWeOQhn5uTra v5wFvSVCi69VBYM2FP35yuMTL8LRWzkgpDTQZz+rzUpwI3M4A3mpcBHKKLj1V0Q9zG sajUSjZ3J+0xrk1eCIcxNWuQVq9hTyf4/3UwKpWk=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id DD5034014A
Subject: Re: Mailing list membership.
To: IETF discussion <ietf@ietf.org>
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net>
Date: Tue, 28 Feb 2017 17:29:24 -0300
MIME-Version: 1.0
In-Reply-To: <20170228051843.wkh5skthuyrs5pwz@thunk.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sRT5GF_DVE4sGXqAjJlLgxgu-94>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 20:29:45 -0000

On 28/02/2017 02:18, Theodore Ts'o wrote:
> ...
> Or, people who are using broken, non-standards compliant mail systems
> can move to ones which are compatible with internet mailing lists....
> - Ted

Dear Theodore,

related to the problem, what Khaled explained, what is your proposal?

What are your "compatible with internet mailing lists" mail systems?

Yahoo and Hotmail are not "compatible", or?

Mailman never change the "From"-header. Therefore, the From-Header 
always points to the author of the email. What you think, is that the 
correct, compatible way? I think, yes.

many greetings, willi


From nobody Tue Feb 28 12:39:53 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AE4E1296CB for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 12:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=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 WYLBwKONZVha for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 12:39:50 -0800 (PST)
Received: from resqmta-po-06v.sys.comcast.net (resqmta-po-06v.sys.comcast.net [IPv6:2001:558:fe16:19:96:114:154:165]) (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 36C961296E5 for <ietf@ietf.org>; Tue, 28 Feb 2017 12:39:49 -0800 (PST)
Received: from resomta-po-08v.sys.comcast.net ([96.114.154.232]) by resqmta-po-06v.sys.comcast.net with SMTP id ioXMcmZVQLSLVioYmcAh1D; Tue, 28 Feb 2017 20:39:48 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-po-08v.sys.comcast.net with SMTP id ioYkcRaE30ttWioYmc0mZE; Tue, 28 Feb 2017 20:39:48 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v1SKdkqF011080; Tue, 28 Feb 2017 15:39:46 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v1SKdkkJ011077; Tue, 28 Feb 2017 15:39:46 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: gen-art@ietf.org, draft-ietf-dane-smime.all@ietf.org, ietf@ietf.org, dane@ietf.org
Subject: Re: [Gen-art] Review of draft-ietf-dane-smime-15
In-Reply-To: <87innwmphk.fsf@hobgoblin.ariadne.com> (worley@ariadne.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Tue, 28 Feb 2017 15:39:46 -0500
Message-ID: <87o9xmjbhp.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfCHvKlmAm3J0N85SXjYzwuFs5LxA9fegEMMe5ewUZbffN0wOGu+/m0wnbCzc03Od1KxYjGEvxgjDFYXl3zBJ2WfG/YvbppN1YevVLFRV4BhXYoWdiIlA siiXlp0JiVgIBHqMyhPJVpsin2yT2IH1oJkkYRLqLNtvVvAno1o4snp7MQNckgyKQlk0buVCk4tRn6d1Vv9ZLu8Cl0VXDCV45p0ZdDWPiwxSZrIQK4XnnA/E JIpBWqBabcG1rywvcQopCg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Rr7gC47MAm1R_dYJOFI-pHB5M_U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Feb 2017 20:39:50 -0000

worley@ariadne.com (Dale R. Worley) writes:
> [How about salting the hashes?]

OK, this has been discussed...

Dale


From nobody Tue Feb 28 20:50:00 2017
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A424E129476 for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 20:49: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TU7Tug_7fGeS for <ietf@ietfa.amsl.com>; Tue, 28 Feb 2017 20:49:58 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 E4D04129432 for <ietf@ietf.org>; Tue, 28 Feb 2017 20:49:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=5SLPbUwTnE/24xaOqyWH1EqLLBDYUmnUl8dWEaOkAUo=;  b=WpzQ/dOF+aVVdrjmRvopKeqL/SmPMy/1u9qrxu/pvZxpysaDU4H8zLDWHZo+oFm0YFFRYED3/13agse1TEs2nHgmuLuwRultkPfQN3J12RlmUO7m9VYQoabNgua8RcS6/fZ64LnznN57FSv+DoTmZFX3bT6DGzTfWTSWc2s9XwU=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1ciwCp-0003Qd-Ji; Wed, 01 Mar 2017 04:49:39 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id 6E2EFC00227; Tue, 28 Feb 2017 23:49:37 -0500 (EST)
Date: Tue, 28 Feb 2017 23:49:37 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: willi uebelherr <willi.uebelherr@riseup.net>
Subject: Re: Mailing list membership.
Message-ID: <20170301044937.v3vhw3eqgqkxpoup@thunk.org>
References: <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net> <HE1PR04MB14490DE8834559F6D9D05F7EBD570@HE1PR04MB1449.eurprd04.prod.outlook.com> <60cc8784-2815-32df-0cae-7adfffd0b549@riseup.net> <20170228051843.wkh5skthuyrs5pwz@thunk.org> <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bea06868-c7b9-29ec-4f63-1adcca3b9698@riseup.net>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JK6EAYEVAHpA64LJp9gKP7WXys8>
Cc: IETF discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 04:49:59 -0000

On Tue, Feb 28, 2017 at 05:29:24PM -0300, willi uebelherr wrote:
> 
> related to the problem, what Khaled explained, what is your proposal?
> 
> What are your "compatible with internet mailing lists" mail systems?

RFC 2821, Simple Mail Transfer Protocol, section 3.10.2

   "To expand a list, the recipient mailer replaces the
   pseudo-mailbox address in the envelope with all of the expanded
   addresses.  The return address in the envelope is changed so that all
   error messages generated by the final deliveries will be returned to
   a list administrator, not to the message originator, who generally
   has no control over the contents of the list and will typically find
   error messages annoying."

This is the SMTP Envelope From field.  The FROM field is not changed,
but the SMTP return address is changed, so that bounces go to the
mailing list administrator as opposed to the person who sends mail to
the mailing list.

Unfortunately, if you are using a system whose domain requests that
all recipients enforce DMARC alignment, this specifically instructs
recipients to bounce mail if the SMTP Envelope return address doesn't
match the FROM field in the header.  This means that they won't see
mailing list mail as defined by the IETF Standards Track RFC 2821,
which specifically says that is acceptable (and in fact a good thing)
to change the SMTP envelope return address so that bounces (caused by
people changing where they work, etc.) go to an administrator who can
deal with them.  But if the mailing list administrators gets too may
bounces, and it's because the sending domain is requesting that mail
be bounced, the only thing they can do is to unsubscribe the sender or
the recipient.

Hence mailing list systems that enforce DMARC, or request DMARC
processing, are fundamentally incompatible with mailing lists as
defined by section 3.10.2 of RFC 2821.

If you want to participate in such mailing list, one of the best ways
is to change to a mailing list system that doesn't do DMARC.

Best regards,

						- Ted


From nobody Tue Feb 28 21:16:12 2017
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 884331294A0; Tue, 28 Feb 2017 21:16:10 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Peter Yee <peter@akayla.com>
To: <gen-art@ietf.org>
Subject: Review of draft-ietf-6man-rfc2460bis-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148834537055.29494.17692224713818414298.idtracker@ietfa.amsl.com>
Date: Tue, 28 Feb 2017 21:16:10 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k6pCBc4JaELQks8ZzbUKR_FvfHw>
Cc: draft-ietf-6man-rfc2460bis.all@ietf.org, ipv6@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Mar 2017 05:16:10 -0000

Reviewer: Peter Yee
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-6man-rfc2460bis-08
Reviewer: Peter Yee
Review Date: 2017-02-28
IETF LC End Date: 2017-03-01
IESG Telechat date: Not scheduled for a telechat

Summary: Ready with nits.  This Internet-Draft is an update to RFC
2460, the specification for IPv6.  See the following note.

Note that I read this document in the context that it is an update of
RFC 2460, primarily for the purpose of cleaning up minor items (things
that to moved to other documents, for example) and addressing errata. 
I did not do a top-to-bottom review of the document as though it were
a wholly new work.

Major issues: None

Minor issues: None

Nits/editorial comments: 

General:

For RFCs named outside of references (i.e., those that aren't found in
square brackets), separate "RFC" from the following numbers with a
space.  This is especially prevalent in Appendix B.

>From the mailing list discussion back in 2015, I can't determine if an
actual decision was taken as to whether RFC 2119 recommended/expected
language ought to be used in this document.  The discussion mentioned
leaving the topic for IETF LC, but I can't even tell if there was
consensus to do that.  This document does not use RFC 2119 language
primarily because it is minor update to RFC 2460, which itself did not
use RFC 2119 language.  There was a healthy debate on the mailing list
and I feel it came down mostly on the side of using RFC 2119, but
again no consensus was obvious, just a preponderance of opinions.  The
thread starts here:
https://www.ietf.org/mail-archive/web/ipv6/current/msg23284.html

Change all uses of "en-route" to "en route".  Usage is mixed in the
document, but en-route is never used before a noun and as a borrowed
word from French would arguably not even be hyphenated had it appeared
before a noun.  We won't even get into italicizing it. ;-)

Change all uses of "behaviour" to "behavior".  Although both British
and American English are permissible, it seems preferable that only
form be used in any particular document.  Given so many other
Americanized spellings in the document, I'm recommending going with
American English in this case.

Specific:

Page 20, 5th bullet item, 2nd paragraph, 2nd sentence: delete "an"
before "overlapping".

Page 22, Section 4.8, 1st paragraph, append a comma after "because".

Page 23, 1st partial paragraph, 1st full sentence: insert "be" before
"a".

Page 23, 1st full paragraph, 2nd sentence: insert "be" before "a".

Page 23, 2nd full paragraph: consider changing "need to" to "must". 
(Ignoring any decision taken on RFC 2119 usage.)  I don't believe the
"need to" at the top of this page needs to(!) change as it describing
what designers need to do, not placing a restriction on a protocol
element.

Page 23, Header Specific Data definition: change the comma to a
period.

Page 26, 2nd bullet item, 1st sentence: delete the comma after
"node".

Page 26, 3rd bullet item, 2nd sentence: change "use" to "Use" in the
title of RFC 6936.

Page 29, Section 12.1, [I-D.ietf-6man-rfc4291bis] reference: update
-06 to -07 to reflect the current version of that draft.

Page 34, Appendix B title: change to "Changes since RFC 2460".

Page 35, 1st 07) item: change "IPSEC" to "IPsec".

Page 39, 01) item: delete an extraneous space before "and".

